• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help HTC evo v 4g bootloops, won't recover, won't factory reset. please help!!!

G

garretlars83

Lurker
I've searched post after post and can't seem to get the help and answers I need. same story, had my phone in the charger over night after the ota update and the next morning it wouldn't even turn on. I then got it to bootloop and found out how to get to hboot and fast boot and bootliader but I can't get anything going. I don't have a back up or recovery.img. my hboot says this:
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT 1.57.0000
eMMc-boot
Apr 20 2012, 17:39:22.
Also when I boot into hboot in scrolls really fast this:
SD Checking :
loading PC86DIAG.zip
no image!
loading PC86DIAG.nbh
no image or wrong image
loading PC86IMG.zip
no image!
and etc. with PC86IMG.nbh, .tar, .aes and .enc.
When I run IMAGE CRC I get this as well:
rpm: 0xBD65BCCA
sbl1: 0xA74C19D7
sbl2: 0x83F382E7
sbl3: 0x8B25B72C
tz: 0x98ACC8A7
radio: 0xAFDD966D
hboot: 0x3CA80398
boot: 0x95788539
recovery : 0xE64AE0A1
system : 0x7D722B91.
I just want to leave as much information as possible hoping that this can be fixed. still confused in rooting, s off, recovery images and roms. thank you for your patience and and any help available. I like this phone alot and have had no problems until this happened. also I don't have internet at my house so the $15 extra a month was perfect for wifi hotspots.
 
I've been thinking about this since yesterday. Sorry for the late reply but I was too tired last night to think about it properly. This is a little tricky on the Evo V as there is only one RUU available for your phone and it is from the original release.

This means that it is not backward compatible unless you are fully rooted and s-off...

First thing is first, Thank goodness you are not on the March OTA update! :eek: So the first thing I would do is download the RUU and boot into the bootloader like you have learned to do already. Select fastboot and plug the phone into the PC. It should read fastboot usb in red letters.

Attempt to run the RUU.

It should work if the phone has never been updated. If the November update has been applied you will get an error 140.

Since you are still on hboot 1.57 there is a file you can flash through a custom recovery that will allow you to run the RUU. This would mean that you would need to unlock the bootloader through the htc dev site, then temporarily boot a custom recovery, flash the file, then run the RUU.

The only thing I worry about is if you would even be able to unlock the bootloader without being able to enable USB debugging in the settings menu. But that may not matter if there is nothing on your phone?

It's odd to me that the phone is stuck at the splash screen. It sounds to me like you wiped your rom out but according to the information you provided, your phone is fully stock and has never been rooted. This would mean that you cannot wipe your system which also means that a factory reset should solve the problem.
The only thing that I could think happened is your phone died or something in the middle of the update and you lost your system?

All of this may be more hassle than it's worth. Is there a reason you can't just call VM and tell them your phone is stuck at the splash screen after attempting to take the OTA, and that a factory reset won't solve the problem? I'm sure they would send out a replacement phone and you'd be up and running in a couple days.

Just to be clear, when you were in the bootloader, you actually used the volume keys to navigate to factory reset, and then hit the power button to select factory reset right?
 
werewolfboy said:
What is wrong with the March OTA?
Click to expand...

Nothing is wrong with the ota. It's just that it updates the hboot version which leaves you stuck without an RUU unless you are s-off. This is a completely stock user here stuck at the splash screen.

They likely aren't interested in going s-off just to get booted up, if you can even s-off with a non-functioning phone in the first place.

The March ota is perfectly fine, it just leaves you stuck without an RUU.
 
werewolfboy said:
What is wrong with the March OTA?
Click to expand...

The march ota updates your hboot, unless you're already s-offed the RUU will fail because you would be trying to downgrade the hboot back to 1.57 from the 1.58 included in the last ota. In other words: epic fail! :eek:
OB
Edit: ninja'd again! :D
 
OverByter said:
The march ota updates your hboot, unless you're already s-offed the RUU will fail because you would be trying to downgrade the hboot back to 1.57 from the 1.58 included in the last ota. In other words: epic fail! :eek:
OB
Edit: ninja'd again! :D
Click to expand...

I already flashed the 1.58 hboot last month a ROM messed up my hboot real bad and i did the most recent but I have s-off so am I ok?
 
Palmetto Fellow said:
To clarify, did you mean to say November Update here, or March Update?
Click to expand...

I meant to say November update. He would be on hboot 1.58 if he had taken the March update. So since he is still on 1.57, that means he is either never taken an update or taken the November update.
 
Brian706 said:
I meant to say November update. He would be on hboot 1.58 if he had taken the March update. So since he is still on 1.57, that means he is either never taken an update or taken the November update.
Click to expand...

But would he get an error with the Nov update? I didn't know the Nov update caused an error when running the RUU...?
 
Palmetto Fellow said:
But would he get an error with the Nov update? I didn't know the Nov update caused an error when running the RUU...?
Click to expand...

Yes because the November updated the main version which you also can't downgrade via RUU. It will cause the RUU to fail. Luckily all it takes is the flash of a zip to change your mainversion and trick the RUU into running.
 
Brian706 said:
Yes because the November updated the main version which you also can't downgrade via RUU. It will cause the RUU to fail. Luckily all it takes is the flash of a zip to change your mainversion and trick the RUU into running.
Click to expand...

Wow, look at all those little things I get to miss out on by getting s-off immediately after rooting .
 
I bought this phone in Dec. 2012 and the update was in march. The phone did die in the middle of the update. I did vol. down then power to get to HBOOT, used the vol up and down keys and tried recovery and factory reset, everything I tried gets me bootlooping the splash screen.
 
From my first reply I think the only option that you can even try is unlocking the bootloader, flash or boot a custom recovery, flash the setmainverlow zip, relock bootloader, run ruu.

The only part I am unsure about is whether or not you can unlock the bootloader with a non bootable phone. I've never known anyone to try, and it may not be possible.

I would call your carrier and get a replacement. You could have already had it most likely.
 
I know this is a month later but I'm having the same problem as the original poster. My phone is rooted, but not s-off, with Midnight Rom Sense (I can't remember which version). The battery died while I was at work today and now it's constantly looping the HTC Evo 3D Beats splash screen and won't boot. I had Juice Defender on so it shouldn't have died or even been close to dying. I booted into recovery and all of those .imgs were also missing. I didn't attempt to do any OTA updates and as far as I know the phone can't do it on its own, especially with no data connection (thanks to Juice Defender) so I don't know if what's happened to my phone is related.

My question is: do I restore a file from recovery (which is going to hurt, the last one I did was in February) or run the RUU mentioned in the thread (because it is or might be related)?
 
Take the rom.zip for whatever rom you are using and take the boot.img from it. Put it in your adb/fastboot folder on the pc and use fastboot flash boot boot.img

See if it will boot after that.

You can also try a clean install of the rom or restoring a backup but with having such old backups, you might as well flash fresh again. If you have titanium backup or similar, you should be able to restore your apps without losing too much.

I would save the RUU as a last resort. It's more of a hassle. You have to re-root after the RUU.
 
Well unfortunately flashing the boot.img with fastboot didn't work .___. I do have Titanium Backup but I'm thinking that the last time I did any backups was about the time I did the last recovery backup, February/March.

I was happy with the performance of Midnight (turns out it's 1.4.9) so I saw no reason to do additional recovery backups, as I'd not intended to flash any more ROMs.

Thank you for your help.
 
Sorry to hear that :(

One feature you might want to take advantage of in the future is the titanium backup scheduling. I have mine set to backup every night while I'm asleep.

You never know when disaster will strike. I learned that the hard way and vowed to never lose my app data again. I can redo my settings and set up my home screens but losing all app data is just a bummer.

Unfortunately I don't have anything else to try that won't wipe your data.

Actually you could try dirty flashing the rom. Just wipe /system and cache but not the data partition. Then flash the rom again. If it boots up your data should still be in tact.
 
I actually did have Titanium Backup to run on a schedule, overnight so it wouldn't affect my use of the phone, unfortunately it messed up my alarm (not all the time, every once in a while, I still haven't figured that one out, but it caused me enough stress) so I stopped it and kind of forgot to do manual backups >_>

Also, I did try a dirty install - that didn't work either. I kept getting the splash screen loop. Doing a clean install finally did work.
 
Well I'm glad you are up and running! Sorry you had to lose everything, I can sympathize. I guess now you see the importance of backups. I'm not sure why TB would affect the alarm?! That's odd :confused:

To me the app backups are the big thing. Probably good to make a backup in recovery every so often. I try to do one every few days. Just pick a time where you son need your phone. Like start a nandroid backup in the morning right before you get in the shower. It'll be done by the time you are out.

What exactly happened to your alarm? Would like to try and help you figure that out so you can take advantage of scheduling again :)
 
You must log in or register to reply here.
Back
Top Bottom