Yes. And out of the blue
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Struck in boot loop
- Thread starter Gandriod
- Start date
-
- Tags
- htc evo 4g
Yes. And out of the blue
You say you had hboot 2.10. How old is your phone? When did you get it, and what hboot did it have when you first got it? What is the hw version, if you know it?
Good enough. I assume you followed this to get the eng bootloader:
[GUIDE] HBOOT 2.10(.02 -?)[</3] Got you Down? - Get 0.76[<3] Back! - xda-developers
Is that correct? Not that it matters, but I'm just curious. Since you already have the eng bootloader, you can try a different method. I'm curious to see what it does. Try this:
RA revovery and ENG hboot in one flash after UR Forever - xda-developers
Basically, you'll be flashing the eng bootloader again and RA recovery. If it works, you can just replace recovery with whatever you want. Try it and see what it does. As usual, you're trying this at your own risk. Don't blame me if it makes things worse.
Yes, I did accept the OTA.
Tried this. Was able to downgrade the hboot 0.76, but the problem still there. Also on the above thread post #18,
xda-developers - View Single Post - [GUIDE] HBOOT 2.10(.02 -?)[</3] Got you Down? - Get 0.76[<3] Back!
recommends trying the following:
How to start over: Fully rooted stock 1.47.651.1 in one shot (no adb!) - xda-developers
This didn't help either. Reboots at the same point.
Just as my bad luck have it, I don't have the insurance.
tried this as well, no luck.
Hm, it almost seems like the partitions got messed up somehow. I trust you didn't try to change the partitions in any way? Basically, that first thing you tried and the second (the one I linked to) were the same basic idea, it's just that one of them was older. Interesting that it didn't help. This might be a shot in the dark, but do you remember what hboot version your phone had when you bought it?
EDIT: Nevermind, you said you got it in June above. I doubt you'd remember the hboot version. It seems that nobody who had this problem was able to fix it by running a RUU. It's the only thing I believe you haven't tried yet. It seems pointless to go too far back, but now that you have hboot .76, you can try running a RUU (in PC36IMG format). Why don't you try this one:
http://www.megaupload.com/?d=CCNDGBAD
That will update your hboot to 0.97, which can easily be downgraded back to the eng bootloader, if you need. Unfortunately, there's no way for you to flash the s-on tool to do this the exact way of unrooting, but it should be as close to a fresh start as you can get. You've basically already tried things like this in bits and pieces, but let's see what it does anyway.
EDIT: Nevermind, you said you got it in June above. I doubt you'd remember the hboot version. It seems that nobody who had this problem was able to fix it by running a RUU. It's the only thing I believe you haven't tried yet. It seems pointless to go too far back, but now that you have hboot .76, you can try running a RUU (in PC36IMG format). Why don't you try this one:
http://www.megaupload.com/?d=CCNDGBAD
That will update your hboot to 0.97, which can easily be downgraded back to the eng bootloader, if you need. Unfortunately, there's no way for you to flash the s-on tool to do this the exact way of unrooting, but it should be as close to a fresh start as you can get. You've basically already tried things like this in bits and pieces, but let's see what it does anyway.
I forgot to mention when I ran the following, ran into the fail-pu error for recovery :
How to start over: Fully rooted stock 1.47.651.1 in one shot (no adb!) - xda-developers
I've noted down the output:
Boot
How to start over: Fully rooted stock 1.47.651.1 in one shot (no adb!) - xda-developers
I've noted down the output:
Boot
It almost sounds like it. I don't see how that could happen out of the blue, though. You were able to flash recovery earlier, though. It was Clockwork, but that doesn't matter. Do you have adb installed? I wonder if it's booting up far enough at all for you to connect via adb and grab something from logcat.
Okay. I have adb. How can I repair my partition tables?
Right, it seems have happened to a few people here and there. It basically shows the splash screen, then the screen goes black, and it goes into a bootloop. It does this when trying to boot up normally and when trying to go to recovery. One of the links from xda I was using for research had a video, I believe. If I can find it again, I'll send it to you. You have any ideas, Mr. Ed?
Update:
So I took the phone to the local sprint store, the technician looked at phone said there is moisture build up inside the phone might caused this problem. He also suggested to call sprint customer service to add TEP. So I called and scored a re-certified replacement
. I am up and running now on the new EVO. Going to wait for few more days before rooting
.
This community is awesome. Especially akazabam...you've been great
. Thanks for all the help.
I am thinking of adding TEP to the new phone, is that a good option?. The sprint rep at the local store indicated it's $7/month+$100 to replace the phone for these kind of issues?...so that doesn't sound very good option to me...any other options?
So I took the phone to the local sprint store, the technician looked at phone said there is moisture build up inside the phone might caused this problem. He also suggested to call sprint customer service to add TEP. So I called and scored a re-certified replacement
. I am up and running now on the new EVO. Going to wait for few more days before rooting.This community is awesome. Especially akazabam...you've been great
. Thanks for all the help.I am thinking of adding TEP to the new phone, is that a good option?. The sprint rep at the local store indicated it's $7/month+$100 to replace the phone for these kind of issues?...so that doesn't sound very good option to me...any other options?
Glad you were able to get a new phone . I still think something else must be going on due to the circumstances under which the problem occurred, and the fact that it's happened to others in similar situations. That being said, only you can decide if you think insurance is worth it. Just remember, if you don't have it, and something like this happens again, you might not come out so lucky next time. In any case, I think I might still do a little research on this one before we consider the issue closed...that is, unless you actually did get your phone wet, and I just never asked 
.
. I still think something else must be going on due to the circumstances under which the problem occurred, and the fact that it's happened to others in similar situations. That being said, only you can decide if you think insurance is worth it. Just remember, if you don't have it, and something like this happens again, you might not come out so lucky next time. In any case, I think I might still do a little research on this one before we consider the issue closed...that is, unless you actually did get your phone wet, and I just never asked .