First.. that suggested topics thing is pretty awesome guys!
But anyway... I've been rooting my phone following the steps of the noob proof guide for a while now (http://forum.xda-developers.com/showthread.php?t=1016084). However after this procedure and flashing cyanogen (7...) my phone seems to make a habit of regularly overheating and then rebooting. It has happened a few times already that it ended up stuck at the "why so serious" boot screen, while not being able anymore to access recovery.
I've managed to reflash till now, but still it seems safer to avoid the problem. While using the stock rom right now my phone has not overheated once! However it highly annoys me that I can run somthing like NO app at all...
I wonder: Is it a cyanogen issue? Might it be due to the method of rooting? Somebody with a similar experience?
I suppose there are some easier ways to root by now anyway?
Related
About a week ago my evo started randomly rebooting, and would continue rebooting until I hard reset. I nand restored and that would work for a little bit, but only a little bit. Eventually I managed to unroot my evo and took it to sprint. They seemed to fix it (not sure what they actually did, other than reflashing everything, I think by using an RUU, which I had already done) but as soon as I rooted my evo, the problem came back.
I like to think I'm not a noob, but I'm not a genius about this either. I tried several different ROMs and none worked. I'm back to an unrooted stock 2.1 evo and I haven't encountered any problems.
I've tried finding anything I could. I don't use the exchange something, that was what I read was causing most of the problems. I don't think the GPS bug was affecting me either. I dont think it's a faulty battery or anything along those lines, my evo never restarted in bootloader or a recovery.
Can anyone possibly help me out?
what recovery are you using? you may want to try amon since it does a better job with wiping / clearing the lint.
is this happening with all roms?
Yeah every ROM is doing it, including stock rooted ROMs. I've tried amon and clockword, neither fixed it.
MagicalSandwich said:
but as soon as I rooted my evo, the problem came back.
Click to expand...
Click to collapse
Did you followed the same guide for rooting before and after you got the phone fixed? if so, then that guide was wrong, or might be old, or you didn't followed the steps properly.
Find the best and most trusted guide to root for your evo. Ask and review,
Read as much replies as you can before you use that guide.
_________________________________________________
¤I slide with Syle¤
¤-MyTouch 3G Slide- HTC Espresso Sense¤
¤SlideMEROOT5 Rom¤
Well I could not get out the bootloader and bootloop after running the stock ruu.exe and updating several recovery images PC36img none of em work so I had to go to sprint to order a new one. I really want to come back to MYN ROm when I get my new Evo..But I do not want to brick it again. The only dilemma is I really do not have the total idea of what made my phone just crash force close android and start bootlooping.
I used the unrevoked one click root method and the unrevoked forever to nand unlock it. I was flashing several different kernels at first. When I saw still no improvement in battery life I went to start off flashing Fresh, then AVA then Myn. I had got a force close to with AVA rom and bootloop but i was able to get into recovery and to the splash screen. I wished I had pay attention to what kernel I flashed which was 24hrs before my phone crashed same thing happened when I flashed Myn's rom. However, I was getting crazy bootloops when I first used the battery tweak and after I saw the battery drain I tried a different kernel. At first i was wiping both cache in between but since so many kernels even the stock kernel was giving me a loop at the splash screen (where myn warm 2.2. would come up) I started wiping less just to finally get a kernel which would be stable. The last kernel I flashed I remember was netarchy 4.1.8 cfs fresh compatible around saturday 3pm and around 3am the phone just crashed android crashed and the worst bootloop started happening.
So can anyone give me some feedback please that has their device running smooth with this Rom and/or have had this issue before? Do you recommend unrevoked forever? Does anyone may think its due to flashing so many kernels?
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
At a lost but luckily I did not have to pay for a new phone
omegasun18 said:
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
Click to expand...
Click to collapse
I agree I do not think i bricked it but I have tried so many PC36IMG and different bootloaders I am now way more familiar with android and recovery than before lol. I saw your posts in another thread about a guy with the same issue flintr i think but the toast 2 eng still was not working however those were the first i was trying it may work now since I'm sure I was using a different hboot the 97 version then.
I am not sure if there is anyway its going to work now since even though it still says im Ship S-off I have tried running the stock ruu. I tried the fastboot and i flashed an older hboot to get my fastboot commands..so i ran the command fastboot flash recovery recovery-1.8ra. img but it still would not get into recovery i really do not have any idea what happened.
I really think somehow my kernel is affecting everything. I tried to flash a kernel through fastboot and i was getting error it could also be though i do not have the right format for my kernel file.
potna said:
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I can't get into recovery..as soon as i select recovery it starts bootlooping.
I'm not paying for the new phone I went to a small sprint store so they just looked at it tried to clear data in bootloader and then ordered me a new phone.
Fair enough, sometimes a fresh start can be good. Good luck
Sent from my PC36100 using XDA App
So I've done some searching, and have yet to find a solution to the issue I'm having. GF's phone is the HTC Incredible as you can probably already guess by what subforum this is posted in. It's been running the CyanogenMod 7.1.0 Rom for quite some time alright. From everything I've seen, most people that have had issues with bootloops is because they have been flashing to a new rom/radio and skipped something/pulled the battery/or something along those lines. This phone has been running fine, and then out of nowhere I guess, started to restart itself continuously yesterday. I can get into HBOOT no problem, but that's about it. When I try to select Recovery, it just kicks right back into the bootloop. Anyone have any suggestions??? Phone isn't under warranty anymore, and her contract ends in a month and a half, so we don't want to have to buy a new phone before then if at all possible.
try reflashing recovery.
first start with a freshly formatted FAT32 sd card, download this file and place it on it
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
this should be the only file on your SD card. now turn off your phone and put the sd card in. now boot into hboot (vol down+power) and it should prompt you to update by pressing vol up. do this and when it boots back into hboot, remove the sd card and delete the file. then try booting into recovery
Tried it and still no change
there was a similar situation (stangely similar ) here
http://forum.xda-developers.com/showthread.php?t=1628585
both cases happened to be running cm 7 too...and randomly started boot looping and stuck with no recovery.
i would read through that thread and see if any of the steps will help you
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
downwardzspiral said:
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
Click to expand...
Click to collapse
you can try doing the steps in that thread. you may have better luck. Perhaps someone else on this board knows of another method that may help
Just because it didnt work for that guy, dosent mean it wont work for you. Are you s-off? Have you tried reflashing recovery yet?
it's S-Off and I've tried to reflash recovery
How about an ruu?
tried that. tried through the pc and the computer wouldn't recognize it. tried by updating it in HBOOT, and after the update, it would still just bootloop
Sounds like another possible hardware failure. My only other sugestion would be to try the fastboot flash of the misc img, but it probably wont work either. Its very strange, i have seen this 4 or 5 times now in the past couple months, all on cm7, and all unfixable. I dont want to start a war, but mabey something with cm7 or cm7 and a certain program or combination of programs, is causing this. Or mabey its just cause these phones are getting up there in age.
i too find it odd each one is cm7..
Well thanks for all the help anyways. A new phone it is I guess
the basic problem is CM 7 (for the Dinc). it is extremely common. i have seen it happen to so many people now. it drives me insane when i see people suggesting CM 7 "stable" to others (for the Dinc). i have tried to communicate this here and other places too... i have given up hope of people ever accepting this obvious situation. the "stable" version of CM 7 is simply not stable.
however...
a reflash of clockwork recovery has always gotten people out of the CM 7 bootloop. then they are able to get a working rom installed.
i don't understand why you can't get a recovery re-flashed.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
hey guys!
i will realy appriciate any help on this one:
i am in a light panic attack as i might bricked my first phone..
today i have updated my t989 to ics 4.0.4 via kies, and then rooted it.
of course the root was so i can flash a rom. i chose to try cm9.
any ways, in order not to get the phone stuck in boot loop, i have tried to install the touch version of the cwm recovery.
i did it through the zip on sd option.
the version i used was: CWM6013-TOUCH-CM9-recovery (file size 4.201)
it seemed ok at first.
but then when i retsrted the phone, i noticed that every app i am trying to launch takes forever to respond (about a minute)...
i have tried to do factory reset and it did not help - the phone was sluggish even on the first setup screens..
now i am in the process of downloading the stock version again, to unroot. is this the way to go? did i miss something?
please let me know what info i can provide so you will be able to help me.
again, and i can't say it enough: every help will be very much appreciated. so, did i brick my phone?
thanks!
cvbn
Dude wrong section.
cvbn52 said:
hey guys!
i will realy appriciate any help on this one:
i am in a light panic attack as i might bricked my first phone..
today i have updated my t989 to ics 4.0.4 via kies, and then rooted it.
of course the root was so i can flash a rom. i chose to try cm9.
any ways, in order not to get the phone stuck in boot loop, i have tried to install the touch version of the cwm recovery.
i did it through the zip on sd option.
the version i used was: CWM6013-TOUCH-CM9-recovery (file size 4.201)
it seemed ok at first.
but then when i retsrted the phone, i noticed that every app i am trying to launch takes forever to respond (about a minute)...
i have tried to do factory reset and it did not help - the phone was sluggish even on the first setup screens..
now i am in the process of downloading the stock version again, to unroot. is this the way to go? did i miss something?
please let me know what info i can provide so you will be able to help me.
again, and i can't say it enough: every help will be very much appreciated.
thanks!
cvbn
Click to expand...
Click to collapse
What all did you do to install the ROM?
Something like this happened to me on my original Galaxy S when I updated it via Kies to the new stock version. Everything was running extremely sluggish. I don't remember what I ended up doing to fix it but I most certainly did not keep the stock update on there. I rebooted it and let it sit for about 30mins and then rebooted it again and tried using it. It was a bit better but still not good so I just flashed another Rom and then it was lightning quick.
The good news is you didn't brick it if you can still boot up and run stuff. I'd suggest updating your recovery to TWRP as that seems to be the preferred one now a days, it's the one I've been using to flash countless Roms without any problems, and most Devs recommend it. Apart from that, follow the install instructions precisely and you shouldn't have a problem. To be sure, after upgrading your recovery to TWRP, you could do the wipes (cache/dalvik/factory reset/system) 2-3 times before installing your new Rom, that seems to help some people coming from previous troublesome Roms.
I've noticed a few problems people seem to have around here come from the recovery, mainly those not using TWRP and/or using some form of outdated or beta CWM. Hopefully you can fix your problem, I know first hand how awful that sluggish feeling is. Good luck!
I've searched and found lots of evidence that this issue should be fixable (which is great!)
What I'd like to know is: if a Gnex successfully boots to the Google splash but does not go any further, is there any way that it WOULDN'T be salvageable? If so, how, and is there any easy way to determine this with phone in hand?
It might be obvious by the nature of this question, but I'm looking at buying a Gnex as described. I have 2 already so I'm well familiar with the Gnex tool suite here, just wanted to see how likely the chance of truly getting a brick is.
Thanks!
Hate to "bump" this but might be buying this device tonight. Anyone?
it all depends of why its not booting. it can be as simple as flashing another kernel or rom(if its not booting) or it could be a brick(the real kind, a paperweight).
try to go to recovery or CWM, wipe date n cache. restart. before that, stock rom or custom rom? me too face this kind of problem after it drop to the floor but after wipe data in recovery(im using stock JB) restart the device and everything back to normal. the worst part is all the data is gone.
t3mp3st said:
I've searched and found lots of evidence that this issue should be fixable (which is great!)
What I'd like to know is: if a Gnex successfully boots to the Google splash but does not go any further, is there any way that it WOULDN'T be salvageable? If so, how, and is there any easy way to determine this with phone in hand?
It might be obvious by the nature of this question, but I'm looking at buying a Gnex as described. I have 2 already so I'm well familiar with the Gnex tool suite here, just wanted to see how likely the chance of truly getting a brick is.
Thanks!
Click to expand...
Click to collapse
I guess you'll never know for sure until you have the device to test.
http://forum.xda-developers.com/showthread.php?t=1812959
Best thing, if you're just buying it, is to try and get to fastboot. If you can do that then try and flash the factory image. If that boots then at least you know phone is working and you can then go about flashing a new ROM if that's the route you wanna take