hi all
Forgot to charge my EVO 3D (CDMA) and battery completely drained. Even after using another fully charged battery my phone goes to bootloop - just shows the HTC logo and reboots again and again. Here is what I have:
hboot : 1.5 (S-ON)
radio : 1.06.00.1216
ota : 2_17.651_5
(I am using this phone in India activated on Reliance)
As the phone doesn't boot I can't access it thru adb to give command 'adb reboot bootloader'
I can get bootloader by pressing vol_down+power
When I run the 2_17.651_5 RUU (exe) from my computer while phone is on fastboot, it completes successfully without errors. But still on reboot it just stays at the htc screen and reboots (guess it's becoz stock kernel not getting flashed as the phone is s-on)
kindly help to get back my phone boot again
thanks and regards
ananth
R.I.P
Sent from my HTC.EVO.3D.Xda Premium
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
jdeoxys said:
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
Click to expand...
Click to collapse
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
ananth001 said:
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
Click to expand...
Click to collapse
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Sent from my PG86100 using Tapatalk
megabiteg said:
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Click to expand...
Click to collapse
thanks. extracted boot.img from freeza's kernel and flashed from fastboot after unlocking. But still doesnt solve problem. Can you give me a link for boot.img
Pleassssssse HELP !!!!!!
I have the exactly the same problem, a full reboot result in boot loop, and can not fix it by now.
I guest the phone is rooted before OTA, so OTA can not flash kernel successfully because the wrong signature, and the phone will not boot because the wrong kernel.
I have tried ruu, fastboot boot recovery.img and etc, all failed.
The key point is that, the phone is rooted and you tried OTA. HTC OTA must have a stupid bug, it can not recovery from a partial update, or automatically roll back becasuse of the partial update, dem!
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
ananth001 said:
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
Click to expand...
Click to collapse
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I wonder the same thing all I saw was 1.5
Sent from my PG86100 using xda premium
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Reliance has both CDMA as well as GSM service in India. Mine is a Reliance CDMA MDN.
thanks and regards
reaper24 said:
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Click to expand...
Click to collapse
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
ananth001 said:
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
Click to expand...
Click to collapse
Have you tried to just run the RUU like you said boot turn debug on .... Then go to hboot flash your recovery...
Then fastboot boot recovery.img.
This should work I have unrooted my phone 3 times already in the past month Trial and Error on my part adb always found my phone...
I am tryin to figure out what is going wrong on the last part with TWRP...
Since you said after you do that it was a no go? What happend ? Adb should still be working since you just flashed the recovery...
Anyways I hope you get it solved man I am tryin to figure this problem out.
Do you have a rom already ready to be flashed on your SD card?
Problem is, since i’m not able to android boot I can't reboot bootloader from adb, as I can't connect adb without the phone normal booting. When I boot it just stays at the HTC white screen.
I have flashed twrp recovery from fastboot, but when I give command 'fastboot boot <twrpxxxxx>.img it just boots back to the HTC splash screen
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Android Cowboy said:
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Click to expand...
Click to collapse
As I mentioned in earlier post, have tried flashing PG86IMG.zip from bootloader, but still phone doesn't boot properly and is in a bootloop.
You've used the following file and done these exact steps and allowed the phone to boot to full stock OS? (assuming 2.17.651.5 is correct version)
OPTION 2 - RUU.zip info:
I prefer the .exe version but xHausx’s “FULL” PG86IMG_2.17.651.5.zip may work for you (must be renamed PG86IMG.zip). Make sure you have plenty of battery/charge left!
- (XDA) Xhausx full PG86IMG.zip RUU images (651.5 zips)
PG86IMG_2.17.651.5.zip http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564
MD5: 8F82C2D8F98C077AF775266064BACB5D
From Scrosler's zip Directions : http://forums.androidcentral.com/htc-evo-3d-rooting-roms-hacks/107641-how-return-100-stock-all-versions.html
Scrosler; said:
USE ONLY FOR EMERGENCY PURPOSES. THIS OVERWRITES EVERYTHING!!!!
**THIS WILL RETURN YOU TO FRESH OUT OF THE BOX**
You will not need any special drivers loaded, etc...
1.Download the stock ROM ZIP image from here: and rename it "PG86IMG.zip"
2.Copy it to SD Card
3.Reboot phone into hboot mode by holding volume down and then press power.
Keep volume down held until you boot into hboot mode.
4.In hboot mode the phone will scan the SD card with the image. Once it finds it will ask you if you want to update. Press "Power" to update.
5.Wait.... For a while. When it gets to "system" it will loop a few times. Its quite nerve wracking actually but after about 5 or 6 times it will complete.
6.Once the entire flash is complete it will prompt you to "press power to reboot." Press power and your phone will reboot to 100% stock ROM.
Click to expand...
Click to collapse
Related
For people who came for an answer, here it is.
download android sdk
download fastboot drivers
get clockworkmod img and rename to imgfile.img
put img in adb tools
put adb, adbwinapi, fastboot, and the img file in c:/Android
plug your phone to the computer
enter the bootloader
click on recovery or fastboot doesnt matter since both will now take you to fastboot
goto computer
type in run in start menu
type cmd in run and hit enter
type cd c:\Android
type fastboot boot imgfile.img
you are now in recovery
go to mounts and storage and mount your device as a disk drive
download any rom to your computer doesnt really matter and put in on your sdcard. If you already have a rom on there then just use that.
unmount your phone
go to wipe data/factory reset and when it finishes flash the rom
once rom is done flashing reboot into android again.
your phone is partially fixed
now go to the market (if you flashed cm then flash the gapps.zip) and download "rom manager"
Then click on download clockworkmod 5.0.0.2 or something like that (first option)
Now go to rom manager and restore your backup that u made (If there was 1 before)
now it will be fixed and your bootloader will take u to recovery instead of fastboot when you click recovery xD
thanks xda
I flashed a rom and the rom must have been corrupted or something and now my phone is stuck rebooting and when I try to go to recovery or any option it takes me to fastboot so now my phone is basically bricked
Your phone is not bricked since your still able to turn it on.
Can you enter fasboot USB?
Send from my Evo 3D using Tapatalk
well it doesnt really turn on its a boot loop but whatever and fastboot is weird it doesnt want to work.
If your bootloader is unlocked make sure you flash the boot.img through fastboot and make sure you wipe
Sent from my ADR6425LVW using XDA
fastboot doesnt work I already tried too flash it
Guys please help!!!!!!!!!!!!!!!!!!
What do you mean by fastboot is wierd. Did you pull the battery?
fastboot doent work cmd always says waiting for device
if i click recovery it takes me to fastboot, btw.
Have you tried an ruu?
anobahar said:
fastboot doent work cmd always says waiting for device
Click to expand...
Click to collapse
Do you have the proper drivers installed
Sent from my ADR6425LVW using XDA
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
k2buckley said:
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
Click to expand...
Click to collapse
Sounds like the drivers arn't installed right.. Like you said if he is S-ON and relocked he can run a RUU exe if he is CDMA...
If you are s off then you just need to reload another recovery. And then access a backup of a rom! Or just flash a new one. I had a issue just like this yesterday where my recovery was broken for some reason and had to go from twrp. 2.1 back to 1.1.1 and load another rom.
Sent from my PG86100 using xda premium
Well i put the sdcard in a bberry but a pg6img.img in my sdcard but bootloader doesnt do anything
I am cdma, s-off unlocked with revolutionary kernel 1.4
oops not kernel hboot
Ok, fail, i dont think i hav fastboot drivers downloading now
now cmd is stuck on "sending recovery"
Did you place a copy of the img into your fast boot folder and one in your adb tools folder ???
#Root-Hack_Mod*Always\
OK heres the issue I used the htc unlock method and htc dumlock and things were fine for months to make a long story short I forgot what recovery I was using and couldn't nandroid so I went to the market and got rom manager out of habit then the next day my phone flipped out and basically bricked I realized I needed TWRP so know I have that but roms will not load they either freeze or just lead to a boot loop and when I try to re-flash the recovery using the HTCdumlock option so it has the recovery on both for the workaround it will just continue to run and never end. Also when I try to nandroid restore now it will say completed in 0 seconds
I am now without a phone and everything altogether I have been here for a while and know if anyone can help me its u guys and gals.
Thanks
Just get a recovery and flash using fastboot flash recovery recoveryname.img for recoveryname is what ever recovery u wanna flash and also get the boot.img from a ROM and flash using fastboot flash boot boot.img and then reboot recovery and and flash ROM and it will be fine...the best recovery is 4EXT recovery smartflash s-on witch u can flash roms regular using the recovery hope it helps
Sent from my PG86100 using xda premium
Thanks I actualy used fastboot and flashed back to the old twrp recovery and was able to run my nan backups but they run and the phone just goes back to boot looping i have tried everything i can think and its just back and forth from recovery to boot looping for 2 days streaight now. I'll try the recovery you mentioned though thanks I'll let you know if it works but at this point Im starting to think that I somehoe removed my boot partition and im flashing to nothing
I finaly solved this issue and I want to share for those who may have it.
My main problem was that I had an unlocked bootloader I could not use an RUU without an error and everything I did no matter what let to bootloop.
I simply had to relock my bootloader (To re-lock your bootloader, in the command prompt, type: fastboot oem lock.) Then run the RUU. Aparently RUU's will not work on an unlocked bootloader and now after 2 days finaaly everything is all back to normal.
adambomb_13 said:
I finaly solved this issue and I want to share for those who may have it.
My main problem was that I had an unlocked bootloader I could not use an RUU without an error and everything I did no matter what let to bootloop.
I simply had to relock my bootloader (To re-lock your bootloader, in the command prompt, type: fastboot oem lock.) Then run the RUU. Aparently RUU's will not work on an unlocked bootloader and now after 2 days finaaly everything is all back to normal.
Click to expand...
Click to collapse
You really should try the brick downgrade method no more hassles with fast boot crap. Love my phone now
from my downgraded 3EVO
adambomb_13 said:
I finaly solved this issue and I want to share for those who may have it.
My main problem was that I had an unlocked bootloader I could not use an RUU without an error and everything I did no matter what let to bootloop.
I simply had to relock my bootloader (To re-lock your bootloader, in the command prompt, type: fastboot oem lock.) Then run the RUU. Aparently RUU's will not work on an unlocked bootloader and now after 2 days finaaly everything is all back to normal.
Click to expand...
Click to collapse
You always have to relock before using a RUU otherwise you will get a error ..
Like the other user said
You can
fastboot flash recovery recovery.img and your set Also works to flash a rom and kernel together if your hboot 1.5
Fastboot boot recovery.img wipe and flash.
And twrp has issue's your better off using 4ext for your custom recovery I'm willing to bet thats the cause of the problem
Sent from my HTC EVO 3D X515m using xda premium
This phone has never been rooted and has never had s-off. Phone will not boot into recovery or system. Only bootloops HTC logo or hboot. I used hboot and fastboot to get the bootloader unlocked. I have tried stock, ext4, and custom recoveries and none will boot. I have tried every ruu.exe and PG86IMG.zip from 1.17 to 2.89. None will work. I have used fastboot to flash boot and still will not boot up. When I try to run ControlBear it just
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
Connect device and install drivers
Press ENTER to exit.....
Nothing else.
I have seen a couple others with this issue in 1.50 and another with 1.58 but he was LOCKED and hasn't responded to his thread in a couple of days after suggesting having sprint look into it. I unfortunately have a crack in my touchscreen so sprint does nothing to help. Any idea or suggestions would be great.
PS sorry for any double posts or answered questions. I have been looking since 11 and trying different things with nothing working yet.
EDIT: I have looked into trying the unknownforce hboot downgrade but 2.17 will not install since its an older version. 2.89 files I find will load but when it trys to parse the phone just goes back to the bootloader menu.
I suggest you lock the bootloader first and then run the 2.17 ruu.exe. This will put you back to stock GB. Then you can unlock again and get s-off if you choose.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
I suggest you lock the bootloader first and then run the 2.17 ruu.exe. This will put you back to stock GB. Then you can unlock again and get s-off if you choose.
Click to expand...
Click to collapse
I have tried that and I tried it again. Relocked the phone, ran the update and got a bootloader version error and the phone says RUU Update Fail! Going to try to PG86IMG.zip version of the update now and see if its any different.
EDIT: PG86IMG.zip fails with
Main Version is older!
Update Fail!
Press <power> to reboot.
any .zip files I have found with 2.89 will get to parsing then just go straight to bootloader menu.
I have the same issue, I update to ICS with the OTA update, then did the HTC Dev unlock. But with every rom I tried to flash It just stays stuck at the splash screen. If I try to use the RUU, it gives error 140 I believe, If I try to flash PG86IMG It gives me a main version older failure. S-On
Currently phoneless for the past few days :$
TheSeanR said:
I have the same issue, I update to ICS with the OTA update, then did the HTC Dev unlock. But with every rom I tried to flash It just stays stuck at the splash screen. If I try to use the RUU, it gives error 140 I believe, If I try to flash PG86IMG It gives me a main version older failure. S-On
Currently phoneless for the past few days :$
Click to expand...
Click to collapse
Got this from Tribulattifather page :
1st, ReLock Your bootloader.:
1. Enter FASTBOOT, and then connect to your computer (FASTBOOT USB will be shown).
To do this, hold your volume down key while pressing power. when you've seen the bootloader. Then hook up the phone to the computer. Make sure you have android usb drivers installed.
2. Open command prompt in your computer
3. Relock your device by typing "fastboot oem lock", device will reboot.
4. Enter FASTBOOT again (you will see *** RELOCKED ***)
Then get yourself flashed to a stock rom - <--place on sd card
..Download this one:
http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_208230_signed.exe
Then press the power button on your phone and you should see Fastboot USB. Once you see this, runn the RUU.exe
Let that work it's way through.
Once that is done then it will boot to the rom.
From here, you can accept the OTA'
Read the rest here:
http://forum.xda-developers.com/showthread.php?t=1808332
^^^ Exactly what I said in post 2 but with more detail.
Save the Drama for your Mama with Tapatalk 2
finally past
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
kuroyoma said:
This phone has never been rooted and has never had s-off. Phone will not boot into recovery or system. Only bootloops HTC logo or hboot. I used hboot and fastboot to get the bootloader unlocked. I have tried stock, ext4, and custom recoveries and none will boot. I have tried every ruu.exe and PG86IMG.zip from 1.17 to 2.89. None will work. I have used fastboot to flash boot and still will not boot up. When I try to run ControlBear it just
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
Connect device and install drivers
Press ENTER to exit.....
Nothing else.
I have seen a couple others with this issue in 1.50 and another with 1.58 but he was LOCKED and hasn't responded to his thread in a couple of days after suggesting having sprint look into it. I unfortunately have a crack in my touchscreen so sprint does nothing to help. Any idea or suggestions would be great.
PS sorry for any double posts or answered questions. I have been looking since 11 and trying different things with nothing working yet.
EDIT: I have looked into trying the unknownforce hboot downgrade but 2.17 will not install since its an older version. 2.89 files I find will load but when it trys to parse the phone just goes back to the bootloader menu.
Click to expand...
Click to collapse
Try the following steps,
1. go to recovery > wipe & factory reset, wipe cache, wipe dalvik, go to mounts and storage, wipe system, data, cache, sd card... everything u can find there... wipe all..
2. in recovery DO NOT REBOOT, turn off phone
3. go to android development of evo 3d gsm, find a rom, for example mikrunny 1.06, open the archive extract the boot.img from the kernel folder.
4. assuming u have android sdk installed on ur computer, make a new folder and from the android sdk tools copy adb.exe, fastboot.exe, adbwinapi.dll (exact same files u used to unlock bootloader). also in this folder put that boot.img you extracted from the rom
5. put that folder in C:\
6. get back to phone , still DO NOT BOOT UP YET, and power up phone in bootloader mode (vol down & power) and go to fastboot
7. connect phone to pc in fastboot usb mode
8. open command prompt, type cd c:\"folder" ("folder" = folder u created with the sdk tools)
9. type in cmd: fastboot flash boot boot.img
10. after it's completed, go to recovery, still do not boot up phone
11. in recovery go to mounts and storage, usb storage and now copy the whole rom and nothing but the rom on the sd card
12. install zip from sdcard, select rom and let it install, it should boot up automatically
steps were given by SeptimiuB, I am just replying to your query because I've gone through the same mess and recovered as well.
Just unlock your bootloader and install a recovery before trying the above steps.
Cheers.
Yea listen to that dude connect yur phone up fastboot boot boot.img and do the wire trick till it works. It will it takes several times and a lot of cursing but it'll work
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Xsavior said:
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
Click to expand...
Click to collapse
After flashing the boot.img, will it be OK to flash the rom from the img it is taken from?
I'm having the same problem as the OP.
---------- Post added at 07:19 PM ---------- Previous post was at 07:09 PM ----------
Xsavior said:
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
Click to expand...
Click to collapse
Duuuuude, you totally saved me from minor stress and the headache I was going through. If you had PayPal, I'd send you $1. x-)
Sent from my Xoom using xda app-developers app
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
SOLVED
Hey, I have htc evo 3d gsm (shooteru). I unlocked the bootloader using htcdev.com and installed clockworkmod recovery. Then I changed cid to HTC__001 and tried to flash a gingerbread ROM in preparation for using the flashmaniac tool to downgrade my hboot (1.53.0007 -> 1.49.0007).
But when I tried to flash the gb rom the recovery said that installation finished but the phone did nothing after reboot. So I took out the battery and went into bootloader and everything looked the same as before the flash attempt. So I tried once again with same result. Then I powered off the phone and now when I turned it on again it only shows the HTC logo for a few seconds and then nothing (the buttons at the bottom have their lights turned on though).
Any ideas?
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
randomguyhtc said:
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
Click to expand...
Click to collapse
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I know , it just didn't work for some reason before.
So I flashed the boot.img and now it's stuck in a boot loop. Tried going to cwm recovery and wiping various caches etc and flashing again, and flashing boot.img again but it still goes into boot loop.
I would just use the flashmaniac's tool anyway because I don't care about any data on the phone or anything, but it seems that it requires the phone to be booted before it can start the downgrade.
What should I do? Try to flash other roms maybe? The one that I have now is EU_Shooter_U-1.20.401.8_ROOTED.
So I extracted a rom.zip from a RUU but it won't flash from cwm "Can't open /sdcard/rom.zip (bad)", should I try to flash it with adb/fastboot? I'm worried that the zip may be broken (even though archive manager integrity check says its fine).
Would this work with shooteru/GSM?
[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset)
I'm thinking it might be a way to sidestep the boot loop problem that I have now, just relock the bootloader and follow the instructions until I get HBoot 1.40.something like the guy in the video?
Do I need some special drivers when using the RUU executables on Windows?
So I've got it to work. The problem was what jcfunk said (both of the things he mentioned, actually), I was trying to flash a GB rom when I should have tried an ICS rom instead (lol). After going to ICS RUU, I did the wire trick (unlimited.io) and now everything works nicely and I can get the latest roms.
Glad to hear.