I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.
Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App
That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.
And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.
Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx
teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!
tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7
HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
No, MIUI is not based on CM. It's a completely different ROM
Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!
I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....
I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.
Related
Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
riley614 said:
Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
What is your HBOOT version?
Hboot 0.92
Radio 2.15.00.07.28
Clockwork 2.5.1.2
Un.Rev. 3
Un.Rev. Forever
Incredibly re-engineered 2.2
Update -
Managed to get Un.Rev. to install with cw. And installed a Rom. Now I still get random reboots. Everything will be fine...ill update and install a bunch of apps. and I can use the phone for a while. Then all of a sudden it reboots over and over. To get it to stop, I have to re-do everything. Wipe cache, wipe dalvik, wipe battery stats, data/factory reset. I get an error after dalvik clear though "can't mount /dev/block/mmeblk12 (file exists)"
That puts me to square one.
Everything will be ok and then.....reboots...randomly at different points. sometimes right away and some times after an hour or two. No real pattern. I have a gut feeling it has to do with onboard memory?
Are you overclocking? What kernel are you using?
Try installing a different kernel, make sure it is a sense based kernel as you are using a sense based rom.
You can pick one from here - http://forum.xda-developers.com/showthread.php?t=866736
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
I had the exact same issue when i received my refurbished phone. It is not uncommon that these issues - and others, will occur. Even before rooting i was having the issue.
I did notice that it will happen when i pushed the phone a bit, like talking and trying to download something from the market at the same time.
My suggestion is to unroot, everything stock, test the phone and see if it happens again. The Verizon representative tried to reset the phone and it started boot looping right in front him! And then they order another refurbished phone, which also had issues. Long story short, they gave me a new phone after i begged. (thank u VZ local store, which btw i sent a few customers your way )
According to some inside people i talked to, the 3rd party companies (or individuals) that fix these phones do a terrible job at it and the Verizon stores see quite a few people everyday with similar issues. I have no way of verifying this, just what i was told.
riley614 said:
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
Click to expand...
Click to collapse
I would still try another kernel first, HeyItsLou or Ziggy IMO. If you still have the problems then, flash back to complete stock and take it to Verizon.
Yea, ill give that a try. If I have no luck, ill send it back. After unrooting of course.
Sent from my ADR6300 using XDA App
Riley, were you able to fix it? I'm really interested in some analysis of the problem and investigating issues with refurbished phones boot looping. Someone else just posted a similar problem.
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
riley614 said:
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
Click to expand...
Click to collapse
Sorry to hear that, as i said i had the same issue and i had to get another one. if you get a second "lemon" refurb go to Verizon and talk to a manager. They might do an out of the box replacement and put it in the system as defective under warranty. Good luck.
out of the blue, my phone began to reboot , and turn off and reboot again.
in the forum ive found a lot of fixes but nothing that helps me!
when im trying to go to recovery it goes to the white screen and loops again,
and by the way it reads in green letters pc36100img no found.
help please!!!
thanks
have u tried dropping the 100 and naming it "pc36img" instead of "pc36100img"? i believe thats what it should be named. What rom were u running when this happened?
haha sorry about that
i was running cm7 nightly build 8
also ive tried putting the pc36img.zip on the sd card but nothing, it doesnt read it !!
It has to be all caps as in PC36IMG.zip, and then boot into the boot loader.
im sorry im an idiot, yeah i put the PC36IMG (all caps)on the sd card, it updates but same problem, i even pulled out the battery to brick it! but dammit the same problem!! urgh!!
chinoapple said:
im sorry im an idiot, yeah i put the PC36IMG (all caps)on the sd card, it updates but same problem, i even pulled out the battery to brick it! but dammit the same problem!! urgh!!
Click to expand...
Click to collapse
You're not the first person I've seen that happen to recently on certain nightlies. Unfortunately, in all of the other cases I saw, they weren't able to recovery. RUU didn't work, PC36IMG didn't work, formatting the sd card didn't work, it just looped at the splash screen every time. PC36IMG flashes even appeared to be successful, but it would never get past the looping splash screen. I'm not sure if anyone ever came up with a fix, but when I was following the thread, one dude threw the phone out the window of his car and told sprint he lost it. The other guy went through insurance and shelled out the $100 to get a new replacement. I hope you have better luck. I would try flashing PC36IMG again, or setting hte phone in fastboot mode, and running an RUU. If that doesn't work, I don't think there is too much else to try, that I'm aware of at least. Here is a link to all of the RUU's and PC36IMG's. http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Yeah cm7 seems to do that to some peoples phones, including mine. I found no solution, as far as I could tell ur only option is a new phone.
Sent from my PC36100 using XDA App
So my phone fudge up and I had to buy another one, I really want to root again and reflash roms. Anyone recommends a good gingerbread rom. That doesn't screw up after 3 weeks
Sent from my PC36100 using XDA App
Well I would say CM7, cuz i have never had any issues.
Altternatives:
King's Ultra [gingerbread edition]
MIUI [gingerbread edition]
Evervolv
Salvage Mod
I just saw this in here for the first time today, but I am seeing it alot!!!
Just glad I went back to sense a few weeks ago....
This afternoon I received my replacement phone from Asurion and like and good Android user, I attempted to root it with the Universal root method that had worked really well on my old phone. For some reason, the root did not work and I attempted to restore the phone to stock using the PC36IMG for 3.70 to go along with the 2.10 hboot. Everything seemed to have gone fine until the phone booted up. After a few minutes, it froze and rebooted itself. On top of that, when it does boot it recognizes neither the sdcard nor usb.
I can get into the bootloader and seem to have access to the sdcard from there but any attempts I've made to adb into it have come up with a "no device found" error.
If I attempt to go into recovery, it reboots then goes to the screen with the evo with the red exclamation point on it.
I have no idea what could be the problem or even where to go to try to fix it. I've tried searching the forums but anything I can find about reboots usually has to do with custom roms and any solutions to the other problems seem to revolve around being to adb into the phone while its booted up which does not work due to the lack of usb.
Check k2buckleys post out HERE n report back.
hgelpke said:
This afternoon I received my replacement phone from Asurion and like and good Android user, I attempted to root it with the Universal root method that had worked really well on my old phone. For some reason, the root did not work and I attempted to restore the phone to stock using the PC36IMG for 3.70 to go along with the 2.10 hboot. Everything seemed to have gone fine until the phone booted up. After a few minutes, it froze and rebooted itself. On top of that, when it does boot it recognizes neither the sdcard nor usb.
I can get into the bootloader and seem to have access to the sdcard from there but any attempts I've made to adb into it have come up with a "no device found" error.
If I attempt to go into recovery, it reboots then goes to the screen with the evo with the red exclamation point on it.
I have no idea what could be the problem or even where to go to try to fix it. I've tried searching the forums but anything I can find about reboots usually has to do with custom roms and any solutions to the other problems seem to revolve around being to adb into the phone while its booted up which does not work due to the lack of usb.
Click to expand...
Click to collapse
When you enter recovery, and get the red triangle screen, adb should recognize the phone from there. Also, if you set the phone into 'fastboot' mode, from the bootloader, does fastboot see the device?(fastboot devices) As blake directed you to another post of mine, you see one of the questions is if you are S on or S off. Whats the result there?
also, not sure if some of this may help or not, because you're phone is freezing up, but see this thread in regards to SD card and USB not being recognized.
Whatever the issue is, Z4root also causes the phone to freeze/reboot almost immediately as I run it. I think the problem is that some files got flashed during the attempted root that are still lingering a causing the issues. By all accounts the phone is restored to stock in that it reads the PC36IMG file just fine and restores everything that needs to be restored. It even says that recovery is restored. The problem is that recovery is not restored at all.
I'm quite baffled by it. If I can't fix it, I was hoping to bring it into Sprint for an exchange since it does show s-on and appears to be completely stock. My concern is that it is in asurion replacement and if they send it off, are they going to discover something when it gets back to them, I don't want to get hit with a large sum of $$$.
hgelpke said:
Whatever the issue is, Z4root also causes the phone to freeze/reboot almost immediately as I run it. I think the problem is that some files got flashed during the attempted root that are still lingering a causing the issues. By all accounts the phone is restored to stock in that it reads the PC36IMG file just fine and restores everything that needs to be restored. It even says that recovery is restored. The problem is that recovery is not restored at all.
I'm quite baffled by it. If I can't fix it, I was hoping to bring it into Sprint for an exchange since it does show s-on and appears to be completely stock. My concern is that it is in asurion replacement and if they send it off, are they going to discover something when it gets back to them, I don't want to get hit with a large sum of $$$.
Click to expand...
Click to collapse
If your phone is S on, you have nothing to worry about. Just don't send it in with a bunch of "root related" stuff on your SD card, and you'll be fine. How did you get s on?
Sent from my PC36100 using XDA App
I reflashed the RUU to get the phone back to stock. And by all accounts, it worked. Except that it didnt.
hgelpke said:
I reflashed the RUU to get the phone back to stock. And by all accounts, it worked. Except that it didnt.
Click to expand...
Click to collapse
So running the RUU seemed successful, but it still didn't work? But it did turn you back to S on? Had you used Unrevoked before?
Sent from my PC36100 using XDA App
I did the autoroot found here:
http://forum.xda-developers.com/showthread.php?t=838448
If I'm not mistaken, it uses some of or all of unrevoked, but I'm not sure.
I have not used the files from the unrevoked website though.
Can you attach the autorootlog.txt file to a post for me to take a look at? If you got a refurb phone it may have had something still messed up by the previous owner.
Sent from my PC36100 using XDA Premium App
I'll get the log file when I get home from work. Hopefully there is something telling in there. It didn't really dawn on me that the phone could have been rooted by a previous owner, thereby doing something to my attempt.
It's pretty rare anymore but definitely not unheard of. When the new hardware came out there were a ton of people bricking them by forcing their hboot to downgrade or trying to root with the old unrevoked. And, you could definitely tell with some of the refurbs.
From my personal experiences with asurion, along with those of quite a few people I've talked to, they don't really fix the refurbs as much as just get them back to a useable state so they can be pawned off on someone. The minute you try to root or flash an upgrade/ota it is going to start acting up again.
Sent from my PC36100 using XDA Premium App
Since I'm getting another Asurion phone, what can I do to avoid it in the future?
Depends on what is wrong with it. Although, if it boots to the bootloader then odds are it is fixable.
Sent from my PC36100 using XDA Premium App
Xhausx, I want you on whatever subforum is my hone forum. when this man speaks, . ... listen.
Sent from my PC36100 using XDA App
I decided to get an Epic last weekend from Bestbuy since they're offering the free deal and I really needed a switch from a two year old blackberry. The first thing I did when I got home was look in to rooting the phone.
I pulled up XDA, found the Syndicate ROM and decided to give it a go. I rooted with clockwork and the phone booted up fine. Super user was in the applications and everything seemed to be okay.
I go to restart the phone holding Vol+, Camera, and Power and all it does is boot normally. I realized Its supposed to be Vol-, not Vol+, so I shutdown and try the right keys. The Samsung splash comes up but then the phone just sits there. The soft keys at the bottom never light up. I took out the battery for a bit then put it back in and tried to boot normally, same result.
I ended up taking the phone back to Best Buy to exchange it. I took it in before I tried to root it saying I had connectivity issues and they updated it so I could use that as an excuse for if the phone ****ed up. Long story short, the mobile guys at Bestbuy are idiots and I got a replacement.
I'm trying to figure out what I did wrong before I attempt this on my second Epic. I used the Samsung micro USB cable to root, I've seen some people say not to use it. I'm currently connecting via my blackberry cable.
I have a good feeling the first Epic was refurbished. When I got the phone it was already updated to 2.2 and the keyboard seemed to randomly go unresponsive for a few seconds. The second Epic was 2.1 when I opened the box and the keyboard is working a lot better. I'm wondering if there was a preexisting condition with the first phone that may have caused it to brick on me.
The x64 drivers are installed and I'm redownloading both CWM and SFR1.1.1 in case they were bad downloads. I downloaded the files through my phone while I was at the mall so that may be a possibility.
Thoughts? I really want to try out these ROMs, as I am not a fan of Sprint bloatware and this Carrier IQ I keep reading about.
what version of cwm did you use? 3.0.2.5? If so 3.0.2.5 changes the file system to ext4 i think so that is why you had the initial issue. Did you copy the ROM to the SD card? <--- important step root with cwm 3.0.2.5 it will reboot the power down and give the 3 finger salute cam-vol down-power then choose wipe/data 3 times and wipe cache 3 times then choose install zip from sd card and brows to the rom and install you should be good to go.
Also excellent choose for your first ROM on that phone.
If best buy gave you a refurb. for starting a new contract, then that is cause for serious complaint. You are entitled to a new phone for a new contract.
With that being said, they probably didn't give you a refurb because New Epics come stock with 2.2 EC05. I'm surprised that you got one with 2.1 EB13, that must be an older one.
95% of the time, someone bricks a phone, its user error. You probably did something wrong (OEM cable or not) and made best buy cough up another phone for you. With that being said, your previous phone was probably salvageable with ODIN, and not really bricked.
Follow the qbking's instructions stickied in the general section and you can't go wrong.
tazfanatic said:
what version of cwm did you use? 3.0.2.5? If so 3.0.2.5 changes the file system to ext4 i think so that is why you had the initial issue. Did you copy the ROM to the SD card? <--- important step root with cwm 3.0.2.5 it will reboot the power down and give the 3 finger salute cam-vol down-power then choose wipe/data 3 times and wipe cache 3 times then choose install zip from sd card and brows to the rom and install you should be good to go.
Also excellent choose for your first ROM on that phone.
Click to expand...
Click to collapse
I did use 3.0.2.5 to root. CWM never booted so I don't think it ever changed anything other than giving me root access. Correct me if I'm wrong?
futureprospect said:
If best buy gave you a refurb. for starting a new contract, then that is cause for serious complaint. You are entitled to a new phone for a new contract.
With that being said, they probably didn't give you a refurb because New Epics come stock with 2.2 EC05. I'm surprised that you got one with 2.1 EB13, that must be an older one.
95% of the time, someone bricks a phone, its user error. You probably did something wrong (OEM cable or not) and made best buy cough up another phone for you. With that being said, your previous phone was probably salvageable with ODIN, and not really bricked.
Follow the qbking's instructions stickied in the general section and you can't go wrong.
Click to expand...
Click to collapse
Well we got 4 Epics on the same day. My girlfriend and her parents got a 3-way family plan and I started a new contract. All of theirs were 2.1 but mine came out of the box 2.2, and it didn't have any of that plastic covering around the phone. The accessories also came in resealable baggies instead of the ones I got the second time. Guess it doesn't matter now anyway.
I'll follow the rooting and ROM videos in that sticky and see if it helps.
What should I do if the same issue happens?
Ron_91 said:
I did use 3.0.2.5 to root. CWM never booted so I don't think it ever changed anything other than giving me root access. Correct me if I'm wrong?
Click to expand...
Click to collapse
I think it converts to ext4 that is why you need the ROM on SD. I could be wrong been wrong before.
Ron_91 said:
What should I do if the same issue happens?
Click to expand...
Click to collapse
Get back to us with what happened.
Click on the link in my signature. I made guides for all of the stuff you need to know.
Sent from my SPH-D700 using XDA App
qbking77 said:
Click on the link in my signature. I made guides for all of the stuff you need to know.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
His videos are awesome. And if you can boot into download mode you are not bricked...it is sponged. Waiting to soak up a new system.
Do you BONSAI?
I did the exact same thing as last time and everything worked. SFR1.1.1 is installing right now.
Thanks for the help. I love this forum already.
it sounds like they gave you a working display one that possible got the update. and the reason that the rest was on 2.1 was they didnt sell that many. glad you got your phone to root. and welcome to the community
Hey Guys-
Couldnt find a thread similar so I'll start my own.
6 days ago i updated my rom to CM 7.0.3 and the newest version of Savaged Zen Kernel (dont remember version). Everything was fine until leaving work last night and it began to boot loop in my pocket while driving home. Phone had worked as normal all day (web, text, talk), no changes made to phone either. The only thing i can do is get into the bootloader (by holding power and volume up). Although when i try to enter recovery from there to flash a backup, it just puts me back into the boot sequence again. Any help guys?
http://api.viglink.com/api/click?fo...ersonic-v2.3 - xda-developers&txt=PC36IMG.zip
download that rename PC36IMG and put on root of sd card now go into bootloader go into fastboot and it should stay start update press volume up for yes and then when its done put yes it gonna reboot now take out battery put it in evo again and go into bootloader againthen from bootloader go into recovery from there and you should see amon-ra and from there try to do a nandroid or flash a new rom
I got the update to go through, but now when it prompts me for a reboot it just keeps looping. Even when i select no i dont want to reboot and then try and go into recovery, it loops.
try taking out battery for 2 hours and try again
cool will let it rest and let you know the results when I try again.
ar4senal said:
cool will let it rest and let you know the results when I try again.
Click to expand...
Click to collapse
Do you have insurance on your Evo? Is it still within it's 1 year warranty? It sounds like you got the eternal bootloop of death. Is your bootloader S-on or S-off? The condition you're experiencing is unexplained and usually not fixable. running an RUU is your only hope, and if that failed...your pretty much out of luck.
See this thread: http://forum.xda-developers.com/showthread.php?t=1009672&highlight=boot+looping+no+recovery+access
Yea I'm pretty sure it is still under warranty. I got the phone last August. My bootloader is S-Off. Ill check that thread out.
All you should need to do is wipe and re flash cm7... Our write and re store a back up
Sent by Supersonic!
could be the battery is bad and it is just not getting a constant connection, thus boot looping. i had this issue with a bad battery, swapped it out, no problems
For the record, I mis-spoke...
Sent by Supersonic!
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
First, there are a lot of instances of this happening. Well, not a LOT, but there are several threads about it.
Anyhow, give me a few minutes to upload a file to my mediafire. It's a walk through someone on here wrote that is very detailed and it takes some work, but if everything else fails, it has been known to work.
I'll post the link in a few.
http://www.mediafire.com/download.php?9zc41jsfs7sm1qf
That's it.
You said that you installed the new recovery and still getting loops. That's because you didn't do anything in recovery. Go into recovery and try wiping cache/dalvik cache. See if it boots. If it doesn't go back into recovery go to the wipe menu and wipe everything except SD card and rotate settings. Reflash cm7 and it should work. Loops are a common thing and easy fix
P.s. I don't know if you did this but ill throw it in there anyway. You have to wipe cache and dalvik cache when flashing new kernels.
Sent from my PC36100 using XDA Premium App
ar4senal said:
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
Click to expand...
Click to collapse
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
The issue is that I cannot get into recovery AT ALL. Have tried numerous things. It just wont go into recovery. I bit the bullet and took it into the Sprint Store, they pulled up bootloader and never noticed the S Off at the top. Unfortunately my phone had undergone some sort of water damage. (?) So they were unable to do anything for me, looks like ill be paying the $100 deductible for the refurb.
On a side note the tech at the store told me he has been harvesting parts from evos and epics, and has amassed quite a collection of odds and ends, and that if I ever needed a screen replaced, etc. He would do it under the table for a small charge instead of going through the insurance company. Since i still have the phone ill try all these things again just to see if I can get it working again.
@HipCat- Posted before i read your post....Ill try those steps here in a minute. Thats something I have not tried.
PhxkinMassacre said:
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I cant get into recovery.....