Revert to hboot 1.40 - HTC EVO 3D

Hi... I tried to update my firmware last night but ended up with a relocked hboot 1.57 s-off. I could have swore I downloaded Freeza's firmware with hboot removed. After hours of searching here I am. If anyone can help me get back to 1.40 I would greatly appreciate it, really need my phone for work. Thanks

Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1192306
Download the 1.40 Hboot link
then boot into fastboot
then run:
fastboot oem rebootRUU
an HTC screen will appear then run:
fastboot flash zip PG86IMG_1.40-hboot.zip
After it finishes flashing, the console will say it is done but the image on the screen may not complete. I usually wait a bit then run:
fastboot reboot-bootloader
It should reboot and you should see 1.40 again

Related

[Q] Rezound Bootloop issue CounterShrike 2.3- recognizes fastboot but not adb

Tried to root and unlock HTC Rezound from 2.3.4 and then flash CounterShrike 2.3 following the Unlockr instructions. Seemed to be going well until it bootlooped at the cyanogen mod screen.
When I connect the phone to the PC and start adb, it only sees the phone in fastboot. What's my best course of action?
Try to flash the kernel off an SD card out of hboot?
Wipe the Countershrike ROM and try to flash the stock ICS?
I've followed the instructions from the developers forum to relock via fastboot, but since I can't access the phone with the adb devices command, I'm hesitant to proceed. Any advice?
Thanks.
Forgot to post the info about the phone from the Fastboot screen:
***Relocked***
Vigor PVT SHIP S-ON RL
HBOOT- 2.11.0000
RADIO- 0.95.00.118r/0.95.00.1223r
OpenDSP- v.10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
purchased the phone of eBay. It was on 2.3.4, so I did a factory reset and was trying to get it rooted and on ICS before activating it.
STEP 2:
Opened command prompt from my platform tools & tried to flash AmonRa recovery via fastboot ("fastboot boot rezound-recovery.img") but received an error message:
downloading 'boot.img'...
OKAY [ 1.49s]
booting...
FAILED <remote:not allowed>
finished.total time 1.525s
can you post the link to the instructions you followed?
instructions followed
The original set of instructions I followed to root & unlock the phone were @ Unlockr.
I'm currently running through NilsP's protocol:
Latest RUU Leak and Installation Instructions
NOTE: This is only needed if you want the latest ICS Firmware (Good Idea)
Quote:
Download the 4.03.605.2 Global RUU: >> Here. MD5 = bcdd450501e390ce323a46b396cd0a49
Rename the RUU to "PH98IMG.zip". Just remove everything in the name before the PH
Copy the renamed ipdate to the root of your external SD Card.
Re-lock the bootloader. Skip this if S-OFF
Open a DOS prompt and change directory to the folder where you have fastboot.exe
Reboot to bootloader
Type "fastboot oem lock" (No Quotes) while you are in bootloader (fastboot usb).
Reboot to bootloader again via recovery menu.
The bootloader should find the PH98IMG.zip file and scan it.
Scanning will take awhile so be patient. When it prompts you say yes. The update will make the first pass. This will take awhile so just watch the progress bar on the right The phone will reboot and sit on the white HTC screen. This could be awhile so be patient and don't get nervous. When it is done it will reboot back to bootloader to run the second pass of the install. Again, this will take some time so just watch the progress bar and OK's on the list. When it is done it will say "press power to reboot" so do it. Now it will boot into the leaked Update.
Once booted skip everything in setup. If you plan to run it stock then just get it set up to your liking
Install Amon Ra recovery version 3.15 (My Preference) If hboot will show tampered at the top but that is normal
Flash my ROM using the instructions in post 1
It's alive running stock...phwew! since I bought it for my wife to replace her DINC that's acting up.:highfive:
Your issue earlier was that you were on gingerbread firmware trying to run an ICS rom. Updating to the newest RUU updated you to ICS firmware.
Sent from my GT-P1010 using Tapatalk 2

Stuck at Boot loader

I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
BloodRaven2011 said:
I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
Click to expand...
Click to collapse
You said you tried moonshine to get s-off? did it not work?
You need to be a bit more clear. You are trying to go complete stock or use moonshine to unlock and soff? What error do you get when trying to use ruu?
Hit thanks if I helped! Check out my site at www.circuitsaviors.com
Use moonshine to s off. Go to the thread on how to go back to stock. Follow the directions. The signature is obviously failing because you are s on...
Sent from my HTC6500LVW using xda app-developers app
You might want to check out my thread (http://forum.xda-developers.com/showthread.php?t=2438199), but it's not good news...
jtag is ur only answer. I have a htc dna sitting in my drawer because of this very same reason. I've looked and looked. Sorry
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Phaded said:
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Click to expand...
Click to collapse
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
BloodRaven2011 said:
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
Click to expand...
Click to collapse
You could've downgraded your hboot... This also needs to be done before issuing any s-on commands
I am unable to issue a new hboot , i got the signature verification failed. If anyone know how to , it be great , JTAG is my last option tho
Check your PMs. I'd be interested in your results.
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
xaalfx said:
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
i am unable to use adb command.
I've been reading thru that before i ask this question
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
all the above failing due to higher fw
and this causing sgnature verification fail
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
fr4nk1yn said:
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Click to expand...
Click to collapse
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
BloodRaven2011 said:
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
Click to expand...
Click to collapse
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
beaups said:
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
Click to expand...
Click to collapse
I wish i can execute adb command
What seems to be an issue
i dont have any ROM installed now , and the only thing that i can use is fastboot command
I am familiar with adb , and plus i've created custom ROM before but not for HTC
trying to help a cousin but hell , JTAG here is unfamiliar with this model ( not available in Malaysia )
so i would think , this is a deadend but i never gave hope.
Will try to figure something and all help is much appreaciated.

[Windows/Linux/MacOSX] Easy Soft Brick Fix.

I spent a day fixing a soft brick to my DNA. I haven't tracked down exactly what happened to it but it would continually soft brick trying to flash a custom ROM.
I found this method worked for me, it's easy, should work on any computer that has the proper drivers and fastboot working including Linux and MacOSX.
I've done this with the eng HBOOT and a custom splash screen. It seems to do no checks as the RUU utility does making it super simple.
Try it out report back if it did or didn't work so we can refine the steps if necessary.
This isn't to return to stock, it's to fix a phone that needs to be RUU'd. Let's start.:
If you're already unlocked and S-Off and haven't done it yet, SuperCID now so you can get back to it.
Boot into fastboot, open a terminal type fastboot oem writecid 22222222 then sign up at htcdev.com and go through the steps to submit and get an unlock token.
Download this file and check the MD5: rom.zip: http://www.adrive.com/public/8kYyds/rom.zip MD5: f5a0745a3dee9ac02e261dd42ac67291
Copy the rom.zip to wherever you have your adb/fastboot files. (use this link if needs to be installed: http://forum.xda-developers.com/showthread.php?p=42407269).
The phone should still be in fastboot type into a terminal fastboot oem rebootRUU, then fastboot flash zip rom.zip
When done your DNA should be back to factory.
At this point you might want to flash the 2.06 OTA firmware, (a link can be found in the Monnshine OP), to re-update the radios and Hboot. Same proceedure as flashing "rom.zip"
Unlock with the HTCDEV code from earlier:
Put the phone into fastboot again,
place the Unlock_code.bin from the HTC email with the adb/fastboot files,
type in terminal fastboot flash unlocktoken Unlock_code.bin, accept the warnings, it will wipe the internal storage!,
boot into fastboot one more time and flash whichever recovery you like.
DONE. If everything goes at it should have the phone has been RUU'd and unlocked again Plus you now have a permanent unlock method.

From S-OFF to 100% Stock S-ON Hboot 1.33

http://forum.xda-developers.com/showthread.php?t=2293919&page=15&nocache=1
Followed the tutorial above to revert back to stock and couldn't get my Hboot to 1.15 and i was stuck on 1.33. Anyway spent some of today and got it figured out and worked 100%.
The problem was step - 3. run the RUU as admin (right click, run as administrator) ** If you get an Image 158 error during RUU, try flashing the stock hboot -SEE POST 4**
1. download 1.15 stock hboot: 1.15 stock hboot MD5: B4B8555C20724E12C3B9D33820746E50
2. Rename stock hboot file to : PL83IMG.zip and place in the folder that contains your fastboot.exe file (On your computer)
3. Flash hboot.
after installation do the following -
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Kept on getting error 158 and couldn't change Hboot so i tried run the command to write the cid "fastboot oem writecid VZW__001" then ran the ruu again and it worked. Its wasn't working because the phone wasn't recognized because of the CID. I couldn't reply in that thread because i don't have 10+ posts. Please hit the thanks button if it works for you as well.
Its my second post so take it easy on me if its been covered already.
Not true. With supercid any RUU can be flashed.
I RUU'd two days ago with supercid. Hboot does need to be stock if using the HTC program to flash.
Abu. said:
http://forum.xda-developers.com/showthread.php?t=2293919&page=15&nocache=1
Followed the tutorial above to revert back to stock and couldn't get my Hboot to 1.15 and i was stuck on 1.33. Anyway spent some of today and got it figured out and worked 100%.
The problem was step - 3. run the RUU as admin (right click, run as administrator) ** If you get an Image 158 error during RUU, try flashing the stock hboot -SEE POST 4**
1. download 1.15 stock hboot: 1.15 stock hboot MD5: B4B8555C20724E12C3B9D33820746E50
2. Rename stock hboot file to : PL83IMG.zip and place in the folder that contains your fastboot.exe file (On your computer)
3. Flash hboot.
after installation do the following -
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Kept on getting error 158 and couldn't change Hboot so i tried run the command to write the cid "fastboot oem writecid VZW__001" then ran the ruu again and it worked. Its wasn't working because the phone wasn't recognized because of the CID. I couldn't reply in that thread because i don't have 10+ posts. Please hit the thanks button if it works for you as well.
Its my second post so take it easy on me if its been covered already.
Click to expand...
Click to collapse
Changing the cid was only needed for the jtag or face palm methods...

Somehow deleted hboot

Many new ROMs I've installed on this phone bootloop. I found out that if I flash a new hboot (version 1.4), it would fix the problem. After putting the PG86IMG.zip that contained the hboot version on the root of my SD, hboot recognized it at flashed it. Rebooted the phone, and now the screen is just black but the buttons on the bottom still light up. Won't go into hboot and about 30 seconds of trying to boot it reboots itself. How can I fix this? Need help fast, as this isn't my phone and I really hope I didn't permanently brick it. Phone was on S-OFF with JBear's 1.57.5757 hboot before I flashed the new one.
Jay_P11 said:
Many new ROMs I've installed on this phone bootloop. I found out that if I flash a new hboot (version 1.4), it would fix the problem. After putting the PG86IMG.zip that contained the hboot version on the root of my SD, hboot recognized it at flashed it. Rebooted the phone, and now the screen is just black but the buttons on the bottom still light up. Won't go into hboot and about 30 seconds of trying to boot it reboots itself. How can I fix this? Need help fast, as this isn't my phone and I really hope I didn't permanently brick it. Phone was on S-OFF with JBear's 1.57.5757 hboot before I flashed the new one.
Click to expand...
Click to collapse
I've fixed it myself. What I had to do was keep trying to enter fastboot until my computer recognized the device in fastboot mode. I pulled a 1.50 hboot file from an official 2.17 RUU for the phone, and put it in a zip with a file named android-info.txt that I was missing that I got from the 1.4 hboot zip I had flashed. the file contained this string in a single line:
modelid: PG8610000cidnum: SPCS_002mainver: 1.11.651.2hbootpreupdate:12DelCache:1
Then I ran these commands:
fastboot erase cache
fastboot OEM rebootRUU
fastboot flash hboot_1.50.000_signedbyaa.zip
The file flashed and I got my hboot back and fastboot up and running again. I'll post an attachment to the file if anyone ever even experiences what I have, or is looking for a 1.50 hboot flashable update zip through the same command process.

Categories

Resources