-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Evo stuck in bootloop after flashing savaged zen 2.0
- Thread starter jcflowers
- Start date
-
- Tags
- htc evo 4g
evomattnc
Android Expert
evomattnc
Android Expert
evomattnc
Android Expert
I bought it in June 2010. It has been updated to the latest HTC Evo software (2.2 OS). Then a few days ago, I rooted with Unrevoked3 and installed the Cyanogenmod 7.0.2.1 ROM. Everything was peachy. Last night the batter was at around 30%, so I plugged it in (AC Power) and went to bed. This morning I woke up, the light was green. I pushed the power button and I got the white HTC Evo screen followed by a black screen etc... and the boot looping started.
Well hboot was 2.10, last running 3.7 software...in gonna guess novemberish
Thanks for dropping in friend, seems like our one infamous hboot loop.
I brought Akaza in he is the best around here...
Thanks Matt. Hey Akaza, nice to meet you.
I never explicitly installed it, so unless it was there originally (stock) or part of an automatic update I would have to say no. But really, I don't know.
Okay, then you never did. You'd know if you did. Here's the thing - I've seen mixed results with people getting out of this by going to different hboot versions, or the eng bootloader, specifically. Unfortunately, it's going to be difficult for you to get there with hboot 2.10. This is the method you have to follow once you have hboot 2.02 or greater, and is only an option if you had an older phone to begin with (which is why I asked). The problem is that the second part requires recovery. So, if that first part doesn't help anything, you may be in an even worse spot. It's up to you if you want to try it, but I won't take any responsibility for that one 
. Beyond that, it's sort of pointless to ask, but what if you current baseband radio version?
. Beyond that, it's sort of pointless to ask, but what if you current baseband radio version?Okay, then you never did. You'd know if you did. Here's the thing - I've seen mixed results with people getting out of this by going to different hboot versions, or the eng bootloader, specifically. Unfortunately, it's going to be difficult for you to get there with hboot 2.10. This is the method you have to follow once you have hboot 2.02 or greater, and is only an option if you had an older phone to begin with (which is why I asked). The problem is that the second part requires recovery. So, if that first part doesn't help anything, you may be in an even worse spot. It's up to you if you want to try it, but I won't take any responsibility for that one
I read the link you provided and the bad parts of the mixed results sound scary. Maybe I should just bring it into a Sprint Store for them to do something with it (??). My radio version is 2.15.00.11.19.
Bringing your phone in to Sprint when it's broken while rooted is one of those things where you really take your chances. Since you have S-OFF, and a phone that will not boot, there is a greater likelihood that they'll blame you for it. I know Sprint is usually pretty good about it, but I'd be very careful with a case like this. I normally wouldn't recommend it, but you may have to try a RUU. Theoretically, it's no different than what you did earlier with the PC36IMG.zip, but we can try it.
As far as I know, the only way to RUU is have the phone booted up into the OS, connect it to the computer and run the RUU executable. As you know my phone is boot looping. The one thing I did try is to switch to HBOOT USB mode. My computer detected my phone and installed the drivers. However, in windows explorer I don't see a drive for the sd card thats in the phone. Regardless, when I run the RUU exe at this point, I get an error message stating that the ROM Update Utility cannot connect to my phone.
Looks like I'm going to have to downgrade my HBOOT.
One question though, in the instructions to downgrade theres this:
THIS WILL HURT YOUR PHONE (TEMPORARILY) - YOU NEED TO HAVE A RECOVERY INSTALLED BEFORE YOU DO THIS!
My recovery is useless at this point, so does this mean I can't do this?
Also, out of curiosity, what does the downgraded HBOOT get me that the version I have doesn't?
Thanks.
Well, you're way ahead of me on the RUU, then. That is what I was going to suggest your try. That's unfortunate that it says that. As for the eng bootloader, it has extended fastboot commands (i.e. remote). The thing is, I don't know what will happen if you do the first part, then can't do the rest if you still can't get to recovery. It's unfortunate that you don't have hboot 0.97 or under, still, as that would make the process pretty easy. I'll have to think of some new ideas on this one. I've been through this, now, with maybe 4 or 5 people, and I have yet to come up with a good solution.
Well, given that I had no other choice, I walked into a Sprint store today and told them that my phone won't boot up. The repair guy attempted to do a "hard reset" as he called it by selecting the clear storage option from HBOOT. That didn't resolve the boot loop so he asked if I have TEP which I did and he ordered me a new phone which should be arriving in the next couple of days or so. And thats that.
Thanks a lot for your help Akaza, I really appreciate it. I'm thankful to people like you on the forums who go out of their way to help people like me. You're awesome dude. And if you're tracking this Matt, thank you as well for taking the time to help and connecting me with Akaza.
I'm glad to hear you're getting a new one. I'll figure this problem out one way or another. It's just difficult since it's somewhat rare, and seemingly impossible to recreate at will. One of these days, we'll get this one figured out. If it ever ends up happening to my phone, and I find a solution, I'll be sure to share it.
evomattnc
Android Expert
Well, given that I had no other choice, I walked into a Sprint store today and told them that my phone won't boot up. The repair guy attempted to do a "hard reset" as he called it by selecting the clear storage option from HBOOT. That didn't resolve the boot loop so he asked if I have TEP which I did and he ordered me a new phone which should be arriving in the next couple of days or so. And thats that.
Thanks a lot for your help Akaza, I really appreciate it. I'm thankful to people like you on the forums who go out of their way to help people like me. You're awesome dude. And if you're tracking this Matt, thank you as well for taking the time to help and connecting me with Akaza.
Lol yeah I follow
. You just happened to have the one issue we haven't solved yet the ruu was my last shot when that failed we needed bigger brains . Thought we would give akaza another crack at his nemesis problem . Glad you are getting a new phone.