Related
I'm having freeing issues on my phone when I shut it off or even try the reboot command. The only time it doesn't get stuff on goodbye tmobile msg when I reboot to the recovery from ROM manager app. Is it the software/rooted roms issue or hardware related issues? Anybody else has seen/experienced that? Should I get it replaced from T-mobile before I switch to GS3? I'm using Infamous 2.6.5 Rom. I didn't flash any kernel on this rom yet. I do remember flashing Darkside kernel on my previous rom didn't change anything either! Any suggestions?
Flash darkside cache wipe (not super wipe!) and it should fix the problem. It pretty much happens with all ICS roms.
+1
Sent from my SGH-T989 using xda premium
Yeah, do what Ash said. It's a problem with the Cache wiper in CWM-based recoveries... boot into recovery and flash this zip: https://downloads.sourceforge.net/p...PE.zip?r=&ts=1339897719&use_mirror=hivelocity
It'll do the job.
I have a maybe similar problem, My phone fell off my hands and now it doest boot, it shows darkside loading screen then screen goes blank and then phone keeps vibrating, tried to go into recovery but it doesnt. Though it still goes to download mode. I guess internal sd got pulled out due to fall. Any suggestions?
I have T989D
Nilay, you should go ahead and completely restore your phone back to stock, then.
Follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1414341
Once you're back to stock, you can go ahead and root/flash recovery and go back to whatever rom you were using.
dutman said:
Nilay, you should go ahead and completely restore your phone back to stock, then.
Follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1414341
Once you're back to stock, you can go ahead and root/flash recovery and go back to whatever rom you were using.
Click to expand...
Click to collapse
and i can see download mode starting but when I continue by pressing vol up key a blue screen flashes and then phone keeps vibrating every second with blank screen.
Thanks!!
xAshxMoneyx said:
Flash darkside cache wipe (not super wipe!) and it should fix the problem. It pretty much happens with all ICS roms.
Click to expand...
Click to collapse
It worked flawlessly after the dark-side cache wipe. Now it reboots and turn off like factory rom.
GillBostonian said:
It worked flawlessly after the dark-side cache wipe. Now it reboots and turn off like factory rom.
Click to expand...
Click to collapse
So it no longer pauses at the "goodbye!" anymore?
Mine does that for about 10 - 20 seconds, was wondering if it was normal....
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
EDIT: Missed the fact that this is a Verizon Nexus so removing this comment.
asawoszc said:
Have you tried a stock version of Jelly Bean from the files on XDA? Sorry but it just sounds like you've tried custom ROM's. My other suggestion would be to put on 4.0.4 takju from Google's site and see if you get the Jelly Bean OTA update and if it resolves the issues in the short term. If it does then it must be the process you're going thru to put on the ROM's..... might be missing something simple like Dalvik cache wipe, etc. Just speaking in very general terms.
Click to expand...
Click to collapse
no, he shouldnt do any of what you said. he is on a VERIZON nexus. not a GSM. if he flashed takju there could be serious problems.
Apologies... I missed the last line. Will edit out my comment.
lacesout said:
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
Click to expand...
Click to collapse
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Zepius said:
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Click to expand...
Click to collapse
Thanks Zepius but I already did this. It's the only way for me to recover. My phone is fine now on AOKP M5 but I want to use Jelly Bean. Is there any reason JB would cause boot loops after 24 hours? It's just a pain in the ass because I can't simply recover through CWM. I need a PC. The first time this happened I had to back up my SDCARD from ADB. This took forever!!
BTW, I know how to Root, ROM, etc. I always do everything twice. Wipe Data/Dalvik/Cache and install the ROM twice.
just curious... which version of CWM are you using?
Oh man I have the same issue I just get stuck at the Google screen or the jb splash screen on my cdma nexus I tried everything and wiped every last thing on my phone I just gave up and said ile wait for the official update I guess. Anyway I hope this thread shed some light on the situation we having
Sent from my Galaxy Nexus using xda app-developers app
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Zepius said:
just curious... which version of CWM are you using?
Click to expand...
Click to collapse
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
XfrostX said:
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
Click to expand...
Click to collapse
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
akira02rex said:
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Click to expand...
Click to collapse
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
lacesout said:
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
Click to expand...
Click to collapse
Is it getting wet??
akira02rex said:
Is it getting wet??
Click to expand...
Click to collapse
Lol nope. The shark fishing trip was the third boot loop for me.
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Interesting that you got it to work once, because I have the same issue you do but have never gotten it to boot past the Google animation. Wonder if there was a Rom that we flashed that caused the issue to begin with. I have tried so many JB roms now that I don't know which one I started with, but I think it was Vicous JB since that was the first one I saw released at the time. Just wish someone out there that has had our symptoms and finally got past them could tell us what they did.
Well at least I'm not the only having this issue. Hopefully someone can shed some light.
@nothingshocking
Its the [email protected]_jelly jb rom that I flash when this things all starts.. the vicious rom works for me since v1 to v3.. I'm trying other rom because of grs issue in vicious at that time. I'm not afraid to flash or be in softbrick because I know I can always use my backup and restore or there's toolkit just in case ,but this thing I'm really puzzled this is so weird.. I can flash any ics rom but not the jb rom.. someone suggest me to use jb bootloader and I did and same results.. I'm really hoping that someone of our bright dev can look in to this and help us..
Sent from my Galaxy Nexus using XDA Premium App
Same exact problem here. I would boot loop anytime I rebooted or powered down my phone. Today, I flashed the new clockwork recovery (v.6.0.0.?). So of course I rebooted my phone to see what it looked like. Well it looked cool but when I went to reboot my phone it was just stuck on the google screen. Wouldn't boot at all. Tried wiping data/cache/dalvik cache/format system/format cache/fix permission. Got desperate cuz nothing worked. Backups wouldn't restore. Got "installation aborted error". Finally did like the op and flashed stock image. Works fine now. Just seems like my phone doesn't like the JB at all. Has done this on every JB I flashed.
Sent from my Galaxy Nexus using xda premium
had this happen on my cdma toroplus any ics rom will install and work fine but no jelly bean rom will boot past the bootanimation
Maybe it has to do with hardware version? For those of you with problems like me, are you on a launch Nexus? That is what I have.
My SKU is SCHI515MSV
I am not sure if they redesigned the hardware at some time.
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Odin back to stock, or flash twrp and try that. Also this should not be in this section bud. Prepare to be flamed by the community
Sent from my SGH-T989 using xda app-developers app
I had the same thing happen to me when I updated to the latest one, it would freeze at either restoring, or wiping cache. Luckily I was able to just reboot, and everything was fine on the phone, I then downgraded to 5.XXX
I've been having the same issue on stock recovery, where it sometimes it freezes at wiping, then flash the one from rom manager and its all good. by the way mods please move the thread to Q/A
Wrong section bro. Please see the noob video.
Sent from my SGH-T989 using xda premium
You don't have to Odin stock or any of that stuff, just fastboot flash the 6.0.0.5 version (or that last one that worked for you) and you should be fine.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
kangelov said:
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
Click to expand...
Click to collapse
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
Look, I'm sorry for your troubles but there is a good reason why we have four different sections. This thread being in DEVELOPMENT is only causing clutter. You will get much better help if its moved to its proper place, Q&A or general. Please PM a Mod to move this.
Sent from my SGH-T989 using xda premium
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
kangelov said:
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
Click to expand...
Click to collapse
I dont really know where to find 5.0.2.7. the website doesnt seem to have it. I used revolutionary
Thank you for your contribution to the development of the gs2.
Sent from my SGH-T989 using xda premium
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Rushing said:
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
spuzwuzzel said:
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
Click to expand...
Click to collapse
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ya Odin flash the recovery tar is probably the easiest way to go
Sent from my Galaxy Nexus using xda app-developers app
Odin is a tool used internally by Samsung. As such, you can't expect Samsung to write you a manual. Be very careful, you can cause a lot of damage with it. It is powerful, though: it can bring your phone back from the brink of death. Or it can take a healthy phone and send it over the edge. What you are doing now is something every rooter does on day 1, and only after days and days of research. I am uncomfortable with what you are going to do now given that you have never done this before, but you have no choice: it's this or a useless phone.
Here's the rundown:
A PIT file is something like the Master Boot Record of your harddisk. Problem is, the first partition is something like your computer's BIOS: it tells your phone how to bootstrap. It can bootstrap into the normal mode, which runs Android, or it can initiate Download mode. Download mode is what ODIN needs to replace parts or all of your phone's software. If something goes wrong with that bootloader, your phone is something called a hard brick: it won't power on, it won't even run Download mode so that you can recover it back to stock. It is dead. If that ever happens, you need something called a JTAG flash: you send your phone out somewhere, and someone takes it apart, hopefully carefully, plugs a programmer into an engineering port on your phone's logic board, and reprograms the bootloader back again). Now with PIT file having the major potential to trash things completely, you really have to pay attention you don't load the wrong one. Problem is, the ODIN you just downloaded DOES come with a PIT file, and that PIT file is WRONG for your device. Follow the instructions! Follow the instructions really really carefully. Don't check off extra things! Don't uncheck things that should be checked! Don't add PIT files! Make sure you load the right file to the right place in ODIN. Your phone depends on it.
ODIN will program your phone from scratch, but you wouldn't want to use it too often. It's a dangerous tool, as you can imagine, and it is meant to replace your phone's software, not maintain it! That's why we have Recovery. Recovery is what you use to do basic maintenance to Android, such as factory reset and clean cache and stuff. With those custom recoveries out there, you gain the added ability to flash custom ROMs and a few other things as well, which is what this forum is all about. So, step one in anyone seeking to root their phone is, flash a custom recovery using ODIN, since you need Download mode for that. In an ideal world, you will never need to use ODIN again after you flash your custom recovery. Well, in the real world, you should needed it only very infrequently.
Your phone first got its custom recovery from a tool designed to automate things for you, and sent you flashing without ever giving you an idea how your phone works. Now you don't know how to recover your phone from a flash gone wrong: in the long run that tool did not do any favours to you. The steps I gave you will bring your phone back to life, it brought mine several times already. Something about those new JB ROMs corrupts every recovery I have tried. I don't know why, I don't know how, but it does it. To make matters worse, ODIN without a proper PIT file cannot repartition your phone and fix whatever mess caused the problem to begin with, so restoring stock directly won't do the trick, you need to flash custom recovery, to fix recovery, and then Superwipe to recreate and realign your system, data and cache partitions: that's a good chunk of your phone. So, after you do this, you should be back in business. From beginning to end, if you know what you are doing, the entire process should not take more than 30 minutes, but don't rush. Take your time: take hours, take days. Take all the time you need.
Read before you do anything, and ask if you don't understand.
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
gypsy214 said:
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
Click to expand...
Click to collapse
I have had the problem you describe as well. Some ROMs like certain recoveries better than others and if you end up with the wrong combo, they don't boot. Flashing the right recovery after that fixes it instantly, without even a need to reflash the ROM. No, this is a different problem.
We are talking about a problem where flashing a ROM corrupts your recovery so it will stop working on you completely: it just hangs, it won't restore, it won't flash anything. Also, one or more of the ROM partitions on your phone get corrupted somehow so that even ODIN back to stock doesn't get your phone working again (you end up with a fully stock phone that doesn't boot). Maybe the two are related, but I will let those who know more speak. I am just a regular guy who fiddles with his phone a lot more than he should.
As for the problem being on JB only: I've only had it when flashing JB ROMs. I first noticed it with MIUI, but then AOKP started acting up, and when I finally dared to flash a CM10 unofficial nightly for the first time, it happened too... And then I noticed it doesn't happen always, only sometimes, and other times it just leaves me with a JB ROM that doesn't boot, and in some rare occasions: it works without a hitch. Go figure.
---First off, let me preface this by acknowledging the fact that, yes, I am indeed a noob. And I'm sure some of the info I'm going to put in here probably isn't needed, but as I said, I am a noob, and thus am not entirely sure what is relevant and what is not. I also apologize if some of what I say and/or what I did doesn't make sense and/or is idiotic, but again, noob. That being said I don't have any techie friends and never really had a nack for this kind of stuff, but hey gotta start somewhere right? So, that being said, here's my dilemma:
This all started last week when I was downloading the CyanogenMod Nightlies *Rom. The download started and was going along just fine when my phone suddenly turned off and starting vibrating and then wouldn't turn back on. Everything I would press power it would just start vibrating in regular one second intervals over and over. Finally I remove the battery. It turns back on fine. Download resumes. And... Bam! Happens again. This time I try the same remove to no avail and about 15 minutes later I'm thinking that this is it for my phone when it finally reboots. So I decide, alright, lemme just download this Rom and try to flash it, or at the very least just restore the phone and hope this is a software issue. So I had also just downloaded Rom Manager and was going into recovery via Clockworkmod recovery as the instructions prompted me to in the CyanogenMod tutorial. Now every other time I have installed a new Rom I just manually boot into recovery as the phone turns on. This time I boot into the Clockworkmod recovery though cuz I wanna follow the directions to the "T" and I proceed to selecting the factory reset and it wipes the data and freezes when wiping the cache. So I'm sitting there like, "Oh s**t, what do I do now?" I let it sit for fifteen minutes hoping it will magically unfreeze and all will be right in the world, but it doesn't and I reset the phone via the power button. Then it boots up and tells ne there a issue with my custom OS and I'm not really are what to do here. So, i reboot it and it acts like the reset was successful and prompts me to set up my phone like I just flashed the Jedi Mind Trick Rom I've been using. So I tried again, and same thing. Got stuck on clearing the cache. Luckily it lets me set up the phone again after I interrupt the frozen factory reset. This time I try to boot into recovery manually, pressing the hard keys, and all the phone does is restart. So I try again. And again. And again to no avail. I look up the key sequence thinking I may have forgotten it and am doing it wrong, but after trying every combo I can find online, it still doesn't work. So I give up and go into recovery via clockworkmod and restore my phone to my very first nandroid backup I made before I ever started messing with custom roms, and everything goes fine it seems until it gets to a command about something revolving cache and it freezes again! I eventually have to reset it and it gets stuck in a loop where the Samsung logo comes up, it makes a loud annoying beeping noise for a few seconds before it turns off and does it all over again. Now I'm sure I've bricked my phone. I take out the battery, wait, put it back in, but still nothing. I do this a few more times, wait and hour, and it finally boots up. So now I try to go into recovery manually again, but still just get the phone resetting. I try to go uninstall clockworkmod and go into recovery via Rom toolbox pro, but I still get the clockworkmod recovery rather than the phone's normal recovery I used to be able to get to before I ever installed clockworkmod. So I'm stuck here. I know that's a lot of info, but I didn't want to leave anything out incase it was important. Thanks in advance for any advice and/or directions you can give me. *
P.S. I read in someone's post here that the first issue of the phone turning off and vibrating could be the result of a bad power sensor. So I wanted to add that since this two mysterious restarts and vibrations, nothing like that has happened in the... Approximately 5 days since (for whatever that's worth). *
Thanks again, and I apologize for any ignorance you have encountered while trying to read this post.
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
whatiznt said:
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Ok. Checked it out and got twrp. I clicked install openrecoveryscript. It downloaded. Didn't restart or anything. Now can I just flash the new Rom I want directly from there then? All it says it that I must have installed the recovery script. Just wanted to know though, is it still right that when I reboot into recovery it goes to the cwm recovery? Just wanna make sure before I go messing up my phone.
Thanks!
mintharis said:
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
Click to expand...
Click to collapse
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
VoiD_Dweller said:
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
Click to expand...
Click to collapse
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
jalight27 said:
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
Click to expand...
Click to collapse
Yes, the darkside scripts were used in older cwm recoveries because the default wipes didn't do the job. As for switching away from cwm I'm guessing you want to jump to twrp. You can do that by following the instructions at http://teamw.in/project/twrp2/101
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Thanks for the steps there. Pretty much did a combo of what everyone was saying. Went back to an older version of cwm and used darkside wipes. Then wouldn't you know? It worked! Yay for me. So I'll just keep my older version of cwm, for now at least. Well, anyway, thanks to everyone for helping me figure this out. Much obliged!
jalight27 said:
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
Click to expand...
Click to collapse
Forever like being 10 minutes min, maybe 15
ClaireH said:
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Click to expand...
Click to collapse
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
fe1ixs said:
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
Click to expand...
Click to collapse
Yep, same thing I ended up doing, thought I posted that but I guess I never did. I ended up using the darkside wipes and going back to an older version like you and someone else said. Now everything's just fine. And btw, to get into recovery from boot just restart it holding power, volume up, and volume down at the same time. Then once you see the Samsung logo let go of the power button but keep holding volume up and down till you see the recovery menu.
Hi xda,
I ran into a problem I've never faced today. Before you start assuming, I've done my research. I've searched all over the forums, tried multiple solutions (none worked) and... potentially permabricked it?
Rooted for 7 months, running Jedi Mind Tricks v5.1 Android 4.0.3
How it happened: Today I noticed my phone running really wierdly. It would crash apps constantly, which didn't happen yesterday. So I put it on *close all apps after exiting* on developer options and limited it to run 2 background apps. Throughout the day, my phone would just restart out of absolutely nowhere: in the middle of a text, after unlocking my phone. Each time progressively got shorter between the restarts. It would also freeze a lot of the time. This never happened before today. Maybe a freeze or two, but not this bad.
Did a few battery pulls, no dice. Then this is where it gets worse. The time between boot loops were from 1-2 minutes now. I was getting pissed, so I decided I needed to wipe it and install a new rom. I enter recovery mode CMW 5.0 and do an initial factory reset. Half way through, it crashes again. Now all it does is vibrate constantly until I turned it back on into recovery. Launches recovery. I try to super wipe it. Half way through, crashes again. I try this several times in conjunction with battery pulls. Doesn't work.
I pull sim card, SD card and battery out, let it rest before I reset it.
Then I tried to Odin its ass. I bricked it into the yellow warning screen about a updated system error because I fail with Odin. I searched around to find a solution. I redid Odin to stock kernel it. When it revived, it went into the loading screen. Yes! Progress! It was 99% done with loading when it froze on it. Fml. Battery pull, reboot, and it goes back into its habitual boot loop pattern. I can still access CMW, but it still crashes when I try to super wipe/wipe it.
I have to fix this because, well I bought this from someone with no warranty and using a no contract provider.
Help?
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
eaudexs said:
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
Click to expand...
Click to collapse
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've been looking through some how-to's but I can't seem to find how to upgrade recovery using odin. I can only find the .img file and instructions on how to do it via command lines. Any advice?
Thanks
Good suggestion but better yet ...... I had the same issue on cwm.... get twrp 2.2 look for the flashable download....... 2.3 has a few bugs so stick wit .2
Sent from my SGH-T989 using xda app-developers app
Definitely get twrp on it. Flashing twrp solved 99% of my problems running cm10. Zero rr in weeks. If I were you I would go back to stock for your device. After confident its running like it should. Then root and and go nuts.
I've personally never really had to pull the battery, very rarely. I'm worried about your ram. Could it b corrupted? A short somewhere? All unrecoverable.
I wonder if you could somehow mount your device using Linux. And run memory tests or drive diagnostics.(just thinking out loud).
Twrp is definitely a must. Good luck
Sent from my cm_tenderloin using xda app-developers app
Try doing complete wipes and reflashing a different more stable rom and see if it happens again. There are scripts to do complete and total wipes just to make sure you get a clean install (kind of like the others suggested) atleast yours can turn on so your not hard-bricked.
That's great how you guys are saying twrp solved your issues! It's really funny when cm10 supports cwm recovery. But op, let me see if I still have mine.
Sent from my SGH-T999 using Tapatalk 2
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
my sgs2 did this last month i did the same you did. after no fix i installed a cwmtouch through odin just to be able to restore a back up and worked flawlessly. After that i switched to TWRP again flashed it with no problem through odin and my s2 has been working fine ever since, but fyi i updated twrp to its 2.3.1.1 version and now i get errors can still restore but cant flash jb roms and can only do dirty flashes of ics roms
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
eaudexs said:
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
Click to expand...
Click to collapse
what version of TWRP are you trying to use? NO it does not bootloop
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Nah my man you do not use the script with CWM6 thats your problem right there
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Come on now the flashable version is in the thread...tisk tisk tisk also there are a few version in flashable form in there as well my friend. Got to get your hands dirty sometimes.... LOL Good luck
http://forum.xda-developers.com/showpost.php?p=32984410&postcount=380
Thank you my friend. I was able to finally find a 2.2 TWRP and I flashed it via odin. Did full wipes, full cache wipes, flashed a rom. Fixed permission and all that good stuff. Left it off for 10 minutes. Came back, it started running through initialization. About 4 minutes in, it crashes again. I'm starting to think this could be hardware problem.
eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
Do not use scripts with the new CWM 6 as it will cause this. Manually wipe everything and do not use scripts. You can use scripts with twrp but not the latest cwm
Sent from my SAMSUNG-SGH-T989 using xda premium