Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
Related
Damn near burst a vessel earlier, doods. I had downloaded the newest darchdroid, and was looking forward to some oc'd, jit-enabled, vanilla goodness. I booted into recovery, wiped everything, and tried to install. Ut oh! Got a bad download. No es bueno. But, imma careful sob, so I have like 4 nandroids sitting on my SD....2 from flipz' latest betas, 1 from the original fresh toast, and one from dc 2.0.8. And it was a damned good thing, too! The backups off the newest would NOT boot. They kept looping. I tried rewiping, nothing. No good. Finally, I tried one of the other nandroids, and It worked first try. Because I'm a curious person, I then immediately booted to recovery and tried my most recent nandroid (the first one that bootlooped). This time it worked like a charm. Consider this evidence that having more than one nandroid in storage is never a bad idea. Anyone with a clue about what might have happened, and why the nandroid wouldn't work...until suddenly it did?
dood, Nandroids are for pansies.
Maybe it has a bad temper, too.
-------------------------------------
Sent from your mom!
@Kcarpenter- Well, paint me pink and stick me in a pot! (i was gonna make a joke about your wife and my root, but in this current climate, it prolly would have gotten me banned for being off topic in my own thread)
@jerry- you're prolly right. I know it has my sense of humor, cause it keeps effing with me when I'm drunk....
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
phenicks said:
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
Click to expand...
Click to collapse
Na. I had a totally bad download. It never even finished installing. I'll try it again this afternoon, when I'm near a computer.
I am not sure if this will help, but I had a loop problem and I noticed it started when I installed an app. This was in my nandroid back up. If you boot, it will go into loop.
Through adb start removing programs in the /system/app/. I ended up removing the program (apk and/or odex) and it stopped the loop without rebooting. Not sure why it did this.
Once you find the program that may cause this, restore your nandroid and only remove that apk or odex.
Just try it and see if this works.
you should wipe and clear data before nandroiding back. probably why you had a boot loop. With recovery theres no reason why you cant take 5 seconds and wipe everything before nandroid. If you did do a wipe and clear data before hand then my sincere apologies.
Yeah, I rewiped MULTIPLE times (each time I tried to nandroid recover, so, like, 6 times or so). Thanks, though.
I tried to uninstall Voodoo and now when I restart my phone it shows the galaxy
s and verizon animations, then loads up to a black screen and lit up capacitive icons. I can reboot into recovery, but I can't seem to mount the sd card and i keep getting errors when I try to mount any extensions. Please tell me there is something that I can do to fix this.
try wiping?
try instructions from "how to remove voodoo completely" thread. i cwm flashed the file from there when i had the same problem as u.
Take a deep breath. If you can see any thing at all on your screen, it's not bricked.
Just follow the instructions here;
How to remove voodoo
And your phone will be like new.
I would specifically follow the instructions that i give on page three, as adrynalyne's auto removal script still doesn't work 100%.
http://forum.xda-developers.com/showthread.php?t=804784&page=3
i had a similar problem when i tried to remove the old lag fix.
screen turned black on bootup and lights would come on but nothing else...
i had to use odin to restore everything and i had to wipe the cache and data from recovery.
Sometimes pixie dust works...or just listen to them
Sent from my sharks with fricking lazers on their backs
Thank you for the replies. I was able to finally mount the phone after doing a nandroid. It was force closing like crazy, but I kept with it until I was able to mount the phone from the os. Then I put in the voodoo lagfix uninstall folder and wiped and rebooted. Then I was able to nandroid to another backup and wiped, then did a odin restore, wipe and nandroid data restore. Now it's running like new and voodoo is uninstalled. This is an interesting experience coming from the hero and droid. I am a champ at those phones and I have never bricked a phone and I bricked this one twice. Kind of reminds me of the first time I started playing with my hero. It's a way to get the blood pumping.
emplox said:
I would specifically follow the instructions that i give on page three, as adrynalyne's auto removal script still doesn't work 100%.
http://forum.xda-developers.com/showthread.php?t=804784&page=3
Click to expand...
Click to collapse
This. My removal utility is a pain in my ass
I found it works, but then you gotta battery pull and nandroid back. A clean wipe wont cut it.
I disabled voodoo lagfix and the phone would not boot. I tried to use Odin and now all I get is force close when the phone boots up and it will not let me mount the card. any ideas?
Since I initially wrote this thread, I tried Voodoo one more time and when I removed it, this time with an app to see if it was user error, it once again made my phone non-responsive, it seems that it just is a bit unstable when being removed. With that said, I was where you are now and I was able to restore it. I did a factory wipe of my phone and cache through clockwork and then replaced my kernel and put the full stock image on the phone through Odin. Then I went into clockwork and went to my last backup and restored data. The phone loaded up, but it was as if I did a factory reset. I skipped everything, mounted my phone to my cpu and deleted voodoo files manually (the file needed to remove vodoo was just sitting there too). I went back into clockwork and just restored data under the advanced settings and I was back in business. Hopefully this can help you too. It may be overkill, but it worked.
You did NOT brick your phone. Will people please stop saying they bricked their phone when they haven't? Bricked means YOU CAN NOT RECOVER!!!! Stop scaring and confusing people! pretty please.
I'm not sure who that was directed to, but when this first happened,for a while it seemed that no matter what I did, the phone would not become operable. So for all intents and purposes, it is bricked. It doesn't matter if it can be restored, if you can't fix it, then it is bricked. I don't understand why people are so stuck on semantics. If that is the case, then no phone can be truly bricked, because once you send it to Samsung, they can restore it with their proprietary software. If your phone is nonresponsive and you can't fix it, it's bricked. I kept at it and was able to restore my phone, but I've read that there are people on here who couldn't figure it out and gave their phone in for another one. Because restoring the phone is above their skill level, they bricked their phone.
Kamar234 said:
I'm not sure who that was directed to, but when this first happened,for a while it seemed that no matter what I did, the phone would not become operable. So for all intents and purposes, it is bricked. It doesn't matter if it can be restored, if you can't fix it, then it is bricked. I don't understand why people are so stuck on semantics. If that is the case, then no phone can be truly bricked, because once you send it to Samsung, they can restore it with their proprietary software. If your phone is nonresponsive and you can't fix it, it's bricked. I kept at it and was able to restore my phone, but I've read that there are people on here who couldn't figure it out and gave their phone in for another one. Because restoring the phone is above their skill level, they bricked their phone.
Click to expand...
Click to collapse
I believe the preferred term is "soft-bricked"...LOL
Just do a wipe. I used adrenalines uninstaller. Worked like a charm. Voodoo is a pain in my butt
Sent from my SCH-I500-Fascinate using XDA App
Haha, yes, I've seen people use the term soft bricked here. Voodoo's instability is interesting though. I haven't felt this way since I started using smart phones in 03'. Just something I can't seem to get to work. Good thing the payoff isn't that great. To the person who is having trouble with their phone, I hope I, or someone else here, was able to help.
I just removed lagfix and it worked perfectly. Lol my phone never had lag until I installed lag fix. But I do love the kernal And boot animation provided.
Wanted to say I removed voodoo tonight by adding the remove file via adb. Everything worked as planned. Took about 10 minutes to get off step 2 but everything completed and booted up.
Sent from my SCH-I500 using XDA App
I can only offer <3 support... When I tried to remove Voodoo the first time, ugh I went through hell. I was stuck on my loading screen with Samsung just staring me in the face. Followed the complete remove by Adrynalyne, and everything was ok in the end.
There is no way to rule out GB as the cause of this failure right now. All we have is theories and the best fitting one is an emmc chip failure. Until we can find a user with a brick, who is still s-off, we can not learn more.
DO NOT FLASH OVER BRICKS, We need you to have s-off for trouble shooting.
UPDATE
We need info from brickers and non brickers please see
Please see here http://forum.xda-developers.com/showthread.php?t=1098363
--old post--
It has came to our attention, over the last few days that the recently leaked Gingerbread radios maybe causing a oddly large number of bricked phones.
This can affect any Thunderbolts running Gingerbread (except CM7 users), even after running fine for several days.
The cause at this point is not completely understood, and AndIRC as a whole recommends you revert back to Froyo until we understand it, or have a new leak.
When bricked, the phone is sent into an endless bootloop, no matter if you are booting into Android itself, or into the recovery. Trying to revert after the bootloop does not fix this issue.
Theories:
GB Radio causing corruption on the emmc:
Undisclosed chipset issue (Sorry no details will be coming unless verified)
GB miss reporting battery stats, aka just dead battery (Debunked by ryan2600 and I)
"Not sure if its the radio, i got a bootloop experience this morning after tethering my tablet on a freshly charged tbolt, few minutes later the phone died and stuck in a bootloop, there are times i can go to bootanimation sometimes it goes up to HTC screen and dies, I can go to HBOOT but before i can do anything the phone dies.
Good thing i have a 2 extra battery and an external charger from ebay, I swapped the battery and my phone is back to life, it seems like the GB roms are not charging the battery properly and reporting that the battery is around 80-90%" http://www.reddit.com/r/Android/comments/hk54l/if_youre_using_the_leaked_gingerbread_build_or/
Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App
I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!
Awww fiddlesticks! Well at least I get my baby back. Landscape Rosie is the girl for me.
swimminsurfer256 said:
I was under the impression that a bricked phone was a phone that doesn't turn on at all... Wouldn't you be able to put the PG05IMG file on your SD card through your computer if this ever happens and then do a battery pull and boot into bootloader and revert then?
*edit* I've also had an endless bootloop on GB and flashing a new ROM after wiping data/cache/dalvik fixed it... No more reboots yet at least.. maybe it wasn't the same thing that you're talking about!
Click to expand...
Click to collapse
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.
Wow this sucks, I don't really wanna go back to froyo
Thanks jcase and Team AndIRC! I nearly flashed the latest BAMF GB update. I'm glad that I stuck with 1.6.3
Wow, mine just started 2 mins before this thread went up. I was sitting at my desk and saw it reboot and now it won't stop. It actually loads up Android entirely, gets to Lockscreen and then restarts.
zskate311 said:
Does this affect current users or just new flashers of the gb stuff?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone using the GB Radios (ie everyone on GB but CM7 users)
jcase said:
The instructions are for reverting for those who are not bricked.
These bricked phones will turn on, but we can not find a way to prevent them from bootlooping nor repair them.
You cant wipe data/cache/dalvik when you are in this type of reboot loop, as recovery reboots as well.
Click to expand...
Click to collapse
Ah didn't see that. Does bootloader not work?
Well crap, back to froyo I go then, just to be safe.
*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.
I actually think I read about this somewhere else in the forums. I don't know if he was running gb but I'm guessing so. Thanks for this, I'll be reverting back later.
Sent from my ADR6400L using XDA Premium App
adrynalyne said:
*sighs at jcase*
What happened to, "They will blame you and I" conversation?
/me goes off to cry in a corner.
Click to expand...
Click to collapse
It's all your fault.
Sent from my ADR6400L using XDA Premium App
reverting now... can I just flash a froyo radio and rom or do I have do the whole process in OP?
Thanks for looking out for us
Sent from my ADR6400L using XDA App
Thanks for the heads-up!
Might as well Nandroid my Ginger builds so I have them for when we get a more stable radio release. Curses Verizon! I will miss my Sense 3 elements!
This sucks! Thanks for the heads up, though, Justin!
Bootloader works. I ran into this problem once. Have a backup of the ruu handy. It will get you back to a stock rooted froyo state
Btw...I'm staying on gb. Ill take a risk.
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
I believe you're answering yourself. If you wiped everything and flashed different ROMs, but problem persisted - it means that your phone is most likely faulty.
k15goose said:
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
Click to expand...
Click to collapse
The question is, what other roms have you tried? I seem to get the same problems on sense 3.5 roms which is why i am not using them currently. If this is happening on a clean install of cm7 or miui as well as sense then you may genuinely have a problem.
Things to try: full wipe system/data/cache/dalvik/sdcard
reboot recovery after wipe to start clean. verify md5sum of the rom you are flashing to eliminate possibility of error. dont install any of your own apps for 1 to 2 days and then if you still have the problem then you may want to unroot and try to get a warranty exchange if at all possible. Good Luck!
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
k15goose said:
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
Click to expand...
Click to collapse
Well that's good to hear that it isn't happening on all roms. I usually fix the market problems by doing a data wipe and then force close it. Usually will start being able to download after a fc. To check the md5sum on a file download mand5 free from the market and check the file that way.
Sent from my HTC Glacier using xda premium
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
TWRP2.0 is an evo killer as far as I know there is no fix for a TWRP brick I'm pretty sure it messes up something in the partitions possibly boot or system partition which is why it bootloops
We are legion, for we are many
Unfortunately your phone is toast. Had the same problem, and really there is no way to recover. You should have bit the bullet in used insurance instead of going through Sprint since the Evo is past EOL. You maybe waiting a long time to get a replacement where as going through Ausion (sp) you either would have gotten either a new Evo, a refurb'ed Evo, or a new Evo3D (most likely).
Sent from my ICS-less Transformer TF101 using Tapatalk
Art2Fly said:
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
Click to expand...
Click to collapse
scottspa74 said:
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
Click to expand...
Click to collapse
It's been a busy week for me, but I am still alive, and still using my previously-soft-bricked device .
I can link you to what I was able to do to get mine working (HERE), but if you can't get the device to boot up at all, you might be in dire straits. What is your HBOOT status? (version, NAND status)
hey Cap'n, you need some kind of superhero shield in your user icon
sent from AOKP heaven