Related
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
koty2012 said:
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
Click to expand...
Click to collapse
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
LesbianSeagull said:
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
Click to expand...
Click to collapse
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Bizarre1 said:
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
Click to expand...
Click to collapse
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
LesbianSeagull said:
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
Click to expand...
Click to collapse
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
*Edit: I believe the drivers will install if you install HTC sync. Unfortunately I cant post the link to it, but just do a Google for HTC Evo 3D drivers. It's on HTC's website
koty2012 said:
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Click to expand...
Click to collapse
PM'd and thanked
Bizarre1 said:
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
Click to expand...
Click to collapse
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Click to expand...
Click to collapse
That's really strange. Just to make sure you have the right drivers, go to Control Panel and then to Device Manager and see if your phone is there. It should be under "Android USB devices" or the like. Also, is USB debugging on before the going into hboot?
*Edit: Some more little things, HTC Sync should be uninstalled from your computer, and your phone should be locked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
laie1472 said:
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I used the instructions and download links from androidadvices(dot)com/update-htc-evo-3d-cdma-leaked-ics-403-firmware/. Reading the instructions now I see that I didn't put the phone into USB recovery mode. I can't get back into the ROM to do so and I can't get into my recovery either.
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
iTzLOLtrain said:
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
Click to expand...
Click to collapse
I'm trying that now. Hopefully it works!
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
LesbianSeagull said:
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
Click to expand...
Click to collapse
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
koty2012 said:
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
Click to expand...
Click to collapse
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
LesbianSeagull said:
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
Click to expand...
Click to collapse
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Bizarre1 said:
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Click to expand...
Click to collapse
Tried it, still gave me the signature verification error. I think it's because the bootloader is locked.
bump
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
LesbianSeagull said:
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
Click to expand...
Click to collapse
You have to be unlocked to flash the recovery image. Does it not say its unlocked at the top of HBOOT after using the HTC method?
Sent from the mobile paperweight itself!
Hi
I'm a noob and messed up my DNA here is the thing:
Followed this tutorial http://forum.xda-developers.com/showthread.php?t=2109862 to get bootloader unlocked after that installed this this rom http://forum.xda-developers.com/showthread.php?t=2359803&highlight=google+play this rom it's awsome but it keeps rebooting on my phone by the way the phone before unlocking bootloader and installing TWRP was like out of box and with no update because I can't get the updates from VZW outside the US anyway I changed my mind and tried to go back stock so with that in mind after installing TWRP and before installing the new ROM made a nandroiod backup (saved it to my computer) and when I tried to restore my original ROM I have this issues:
-Phone storage (like for music photos etc....) appears like "storage/emulated/legacy" and won't let me write any file or make a new folder from my computer and in gallery says "insert SD"
-Wifi show turning on and then error
Everything else seems to work fine
------Update: managed to solve this issues flashing the kernel (boot.img) from my backup again but I'm leaving this in case someone else is in a similar situation and want to know how to solve the problem-----
and when googing to bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
MONARUDO PVT SHIP S-ON
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Of course is an ENG Hboot
What can I do to get back to full stock???
l also tried this without success
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) CD to directory containing hboot zip (i.e. cd C:\sdk\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute the following ***
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
from the thread http://forum.xda-developers.com/showthread.php?t=2293919 [How-To] From S-OFF to 100% Stock S-ON [Facepalm/JTAG/RevOne/Moonshine]
by the way I tried to flash the RUU and didn't worked it said error 170 (don't know because I tried in Windows 8 64bit, the cable or what happened) and thinking this twice I don't know if relocking and running the RUU will brick or do something else to my device (because the CID 22222222 or whatever)
So what would you recommend to me for getting back to stock ( recovery and Hboot stock)
sorry for my english I'm not a native speaker
Thanks for your help
luisrojito said:
Hi
I'm a noob and messed up my DNA here is the thing:
Followed this tutorial http://forum.xda-developers.com/showthread.php?t=2109862 to get bootloader unlocked after that installed this this rom http://forum.xda-developers.com/showthread.php?t=2359803&highlight=google+play this rom it's awsome but it keeps rebooting on my phone by the way the phone before unlocking bootloader and installing TWRP was like out of box and with no update because I can't get the updates from VZW outside the US anyway I changed my mind and tried to go back stock so with that in mind after installing TWRP and before installing the new ROM made a nandroiod backup (saved it to my computer) and when I tried to restore my original ROM I have this issues:
-Phone storage (like for music photos etc....) appears like "storage/emulated/legacy" and won't let me write any file or make a new folder from my computer and in gallery says "insert SD"
-Wifi show turning on and then error
Everything else seems to work fine
and when googing to bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
MONARUDO PVT SHIP S-ON
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Of course is an ENG Hboot
What can I do to get back to stock???
l also tried this without success
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) CD to directory containing hboot zip (i.e. cd C:\sdk\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute the following ***
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
from the thread http://forum.xda-developers.com/showthread.php?t=2293919 [How-To] From S-OFF to 100% Stock S-ON [Facepalm/JTAG/RevOne/Moonshine]
by the way I tried to flash the RUU and didn't worked it said error 170 (don't know because I tried in Windows 8 64bit, the cable or what happened) and thinking this twice I don't know if relocking and running the RUU will brick or do something else to my device (because the CID 22222222 or something else)
So what would you recommend to me for getting back to stock or have a 100% functional Droid DNA again
sorry for my english I'm not a native speaker
Thanks for your help
Click to expand...
Click to collapse
Try running the RUU in the bootloader if you are getting that 170 error.
Phaded said:
Try running the RUU in the bootloader if you are getting that 170 error.
Click to expand...
Click to collapse
thanks for your reply i'll try it.....
so it's safe to run the ruu in CID 2222222 and Hboot ENG S-on?
You might be able to write the cid and s-off, then do whatever you need
IMMEDIATELY STOP WHAT YOU ARE DOING AND FLASH A SHIP HBOOT BEFORE YOU HARD BRICK YOUR DEVICE!!!!!!!!
Phew...
Sent from my Nexus 7 using XDA Premium HD app
EDIT* Blue Link in the Sig
.torrented said:
IMMEDIATELY STOP WHAT YOU ARE DOING AND FLASH A SHIP HBOOT BEFORE YOU HARD BRICK YOUR DEVICE!!!!!!!!
Phew...
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
This times 15 million! Why did you not just do moonshine? Have you tried doing moonshine? If you RUU with the ENG hboot you will likely brick.
.torrented said:
IMMEDIATELY STOP WHAT YOU ARE DOING AND FLASH A SHIP HBOOT BEFORE YOU HARD BRICK YOUR DEVICE!!!!!!!!
Phew...
Sent from my Nexus 7 using XDA Premium HD app
EDIT* Blue Link in the Sig
Click to expand...
Click to collapse
Thanks for the advice.... should I use this http://forum.xda-developers.com/showthread.php?t=2000896 HTC Droid DNA All-In-One Tool Kit 2.1 to restore the hboot???
luisrojito said:
Thanks for the advice.... should I use this http://forum.xda-developers.com/showthread.php?t=2000896 HTC Droid DNA All-In-One Tool Kit 2.1 to restore the hboot???
Click to expand...
Click to collapse
I personally wouldn't recommend using toolkits. "ADB" is much easier, I've even put instructions in the blue link in my sig how to flash those specific files. Also to run the RUU you will need to flash version 1.15 hboot
.torrented said:
I personally wouldn't recommend using toolkits. "ADB" is much easier, I've even put instructions in the blue link in my sig how to flash those specific files. Also to run the RUU you will need to flash version 1.15 hboot
Click to expand...
Click to collapse
Hi tried the steps mentioned in the blue link and have this output on the cmd prompt
sending 'zip' (434 KB)...
OKAY [ 0.206s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 0.278s
whats wrong?
luisrojito said:
Hi tried the steps mentioned in the blue link and have this output on the cmd prompt
sending 'zip' (434 KB)...
OKAY [ 0.206s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 0.278s
whats wrong?
Click to expand...
Click to collapse
I guess I should have read OP a little better cause it seems you already tried that... very strange... let me think a little bit and see if I can figure out what to do...
Edit* Go into bootloader and type all of the current info that you see for me please. Is it still the same as what you have in the OP?
.torrented said:
I guess I should have read OP a little better cause it seems you already tried that... very strange... let me think a little bit and see if I can figure out what to do...
Edit* Go into bootloader and type all of the current info that you see for me please. Is it still the same as what you have in the OP?
Click to expand...
Click to collapse
yes it's the same:
*** TAMPERED ***
*** UNLOCKED ***
MONARUDO PVT SHIP S-ON
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
so what can I do? the phone is fully functional by now but if htc and vzw release sense 5 and 4.2/4.3 update i want to be able to flash that ruu if they release it of course
luisrojito said:
Hi tried the steps mentioned in the blue link and have this output on the cmd prompt
sending 'zip' (434 KB)...
OKAY [ 0.206s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 0.278s
whats wrong?
Click to expand...
Click to collapse
When you get this error, I'm pretty sure you're supposed to run the same command again and it'll work.
Sent from my HTC6435LVW using Tapatalk 4
luisrojito said:
yes it's the same:
*** TAMPERED ***
*** UNLOCKED ***
MONARUDO PVT SHIP S-ON
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
so what can I do? the phone is fully functional by now but if htc and vzw release sense 5 and 4.2/4.3 update i want to be able to flash that ruu if they release it of course
Click to expand...
Click to collapse
I think you need to S-OFF at this point, if you have SuperCID (22222222) all you need to do is finish these steps, since the bootloader is already unlocked just go ahead and follow these steps in this tutorial (oh and by the way it says MONARUDO PVT SHIP S-ON which means stock bootloader so you are ok there you do not have an ENG which is a good thing the SHIP means it's a standard bootloader)
Just for saftey make sure you have SuperCID 22222222 by running this command in the bootloader
Code:
fastboot oem readcid
beaups said:
Welcome to Facepalm S-Off for the HTC Droid DNA
Download modified boot.img:
http://d-h.st/pQy
Download signed firmware:
http://d-h.st/nOo 8fa1cf193559d34279d2b1c1aa8c29
1)
Code:
adb reboot bootloader
2)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
3)
Code:
fastboot flash zip PL8320000-DNA.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
4) Immediately issue the following command:
Code:
fastboot boot DNA-rescue.img
5) After android is FULLY booted
Code:
adb reboot bootloader
6) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Getting an error 99 instead of error 92 after step 3?
Perform a few FULL power-downs and boots. Also, others have reported clearing caches in recovery helps as well.
Click to expand...
Click to collapse
Original Thread for Credit: http://forum.xda-developers.com/showthread.php?t=2155069&highlight=facepalm
.torrented said:
I think you need to S-OFF at this point, if you have SuperCID (22222222) all you need to do is finish these steps, since the bootloader is already unlocked just go ahead and follow these steps in this tutorial (oh and by the way it says MONARUDO PVT SHIP S-ON which means stock bootloader so you are ok there you do not have an ENG which is a good thing the SHIP means it's a standard bootloader)
Just for saftey make sure you have SuperCID 22222222 by running this command in the bootloader
Code:
fastboot oem readcid
Original Thread for Credit: http://forum.xda-developers.com/showthread.php?t=2155069&highlight=facepalm
Click to expand...
Click to collapse
Thanks my DNA is S-OFF now
MONARUDO PVT SHIP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
but one last question.....
It would be a problem if I flash the radio from your post:
2.06.605.1 OTA Radio: Download Here
MD5: 63537AAFA4BE4D5CE9362E7A149F997E
or
2.04.605.2 OTA Radio: Download Here
MD5: 42A32022381C70E060E1B5671A2E5C70
I'm getting tired of the SIM problem
Just an fyi running RUU on eng hboot wouldn't brick
Setting security flag to s-on on eng would...
luisrojito said:
Thanks my DNA is S-OFF now
MONARUDO PVT SHIP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.00.00.1023_3
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
but one last question.....
It would be a problem if I flash the radio from your post:
2.06.605.1 OTA Radio: Download Here
MD5: 63537AAFA4BE4D5CE9362E7A149F997E
or
2.04.605.2 OTA Radio: Download Here
MD5: 42A32022381C70E060E1B5671A2E5C70
I'm getting tired of the SIM problem
Click to expand...
Click to collapse
You can try both radios, some say one is better than the other and vice versa.
Phaded said:
Just an fyi running RUU on eng hboot wouldn't brick
Setting security flag to s-on on eng would...
Click to expand...
Click to collapse
Agreed, or I'd be bricked a couple times now.
Tapatalked from my HTC DNA - MoKee
One last question
So tu put end to this thread I managed to get s-off but when I go to recovery it says:
"This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission
Failure to comply may
lead to legal action"
and in my bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
MONARUDO PVT SHIP S-OFF
CID-22222222
HBOOT-1.33.0001
RADIO-1.01.04.0308
OpenDSP-v4.120.240.0920
eMMC-boot
Oct 23 2012,21:34:05
Am I in ENG boot???
Is there any risk to brick my phone trying to return to sock or something?
Thanks
You will only ever have an ENG Hboot if you find, download and flash one.
To answer your question, no you dint have one and yes you're fine for whatever you want to do
Okay guys. I unlocked with Moonshine, was on a Carbon ROM 10.1, updated last night to a 10.2 based Carbon ROM and lost my data. I found out to get it back, I needed to RUU back to stock. Downloaded the RUU and tried to run but it tells me that fastboot.exe and adb.exe have stopped working (I am on Windows 8). In the meantime, I missed a step and re-locked the bootloader early.
Trying to re-unlock with Moonshine and it continually reboots my phone at the "Launching Temproot" stage. Tried to unlock with Facepalm and it worked fine except it didn't fail (as it's designed too) Try to run the next step from Facepalm (The boot stage) and it fails.
Now when I hard reboot get out of the HTC screen from Facepalm, it hangs on the splash screen which is custom. Also after I performed Facepalm, it overwrote my custom recovery so that's gone and it won't let me write another one because the bootloader is locked.
I'm am at a complete loss here and am very afraid that my DNA it toast but I know there is a glimmer of hope because I can access fastboot. Any help from the masters here at XDA would be great.
Snowman1771 said:
Okay guys. I unlocked with Moonshine, was on a Carbon ROM 10.1, updated last night to a 10.2 based Carbon ROM and lost my data. I found out to get it back, I needed to RUU back to stock. Downloaded the RUU and tried to run but it tells me that fastboot.exe and adb.exe have stopped working (I am on Windows 8). In the meantime, I missed a step and re-locked the bootloader early.
Trying to re-unlock with Moonshine and it continually reboots my phone at the "Launching Temproot" stage. Tried to unlock with Facepalm and it worked fine except it didn't fail (as it's designed too) Try to run the next step from Facepalm (The boot stage) and it fails.
Now when I hard reboot get out of the HTC screen from Facepalm, it hangs on the splash screen which is custom. Also after I performed Facepalm, it overwrote my custom recovery so that's gone and it won't let me write another one because the bootloader is locked.
I'm am at a complete loss here and am very afraid that my DNA it toast but I know there is a glimmer of hope because I can access fastboot. Any help from the masters here at XDA would be great.
Click to expand...
Click to collapse
Wow! 1)..RUU does totally format, erase and finally restore the original system that came with the phone as new. so you loose everything
2) Try it from Windows 7 PC
3) Return to stock on Moonshine S-Off > http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Okay, Tried RUU from a Windows 7 pc and no dice, I get error 170 (USB connection) but no fastboot or adb failures. I was able to flash the stock 1.15 HBOOT but when I go to fastboot it tells me my HBOOT is version 1.33.
Tried Facepalm to no avail, It still won't fail after the first command as its supposed to. Tried Moonshine as well but wouldn't work because debugging isn't enabled.
Found a guide that said to find the RUU rom in the temp files and put that on the sd-card which I can't do because it won't boot, but thought I would try to flash it and this is what it did - P.S. The Rom is the PB99IMG file
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot fla
sh zip PB99IMG.zip
sending 'zip' (913111 KB)...
OKAY [ 40.273s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 46.433s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>
Snowman1771 said:
Okay, Tried RUU from a Windows 7 pc and no dice, I get error 170 (USB connection) but no fastboot or adb failures. I was able to flash the stock 1.15 HBOOT but when I go to fastboot it tells me my HBOOT is version 1.33.
Tried Facepalm to no avail, It still won't fail after the first command as its supposed to. Tried Moonshine as well but wouldn't work because debugging isn't enabled.
Found a guide that said to find the RUU rom in the temp files and put that on the sd-card which I can't do because it won't boot, but thought I would try to flash it and this is what it did - P.S. The Rom is the PB99IMG file
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot fla
sh zip PB99IMG.zip
sending 'zip' (913111 KB)...
OKAY [ 40.273s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 46.433s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>
Click to expand...
Click to collapse
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
letschky said:
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
Click to expand...
Click to collapse
IDK it may work, worked in a different phone, but have to be pushed to the sd card
http://forum.xda-developers.com/showthread.php?p=32574569
letschky said:
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
Click to expand...
Click to collapse
Here is the link to what I used to get the PB99IMG.zip - It is the same one finanandroid posted
http://forum.xda-developers.com/showthread.php?p=32574569
And my Bootloader is locked because I was following this guide (http://forum.xda-developers.com/showthread.php?t=2293919) and spaced out and locked the bootloader without realizing I needed to flash the stock HBOOT and Splash screen, That's what I get for trying to do it at 11:30 at night.
Snowman1771 said:
Here is the link to what I used to get the PB99IMG.zip - It is the same one finanandroid posted
http://forum.xda-developers.com/showthread.php?p=32574569
And my Bootloader is locked because I was following this guide (http://forum.xda-developers.com/showthread.php?t=2293919) and spaced out and locked the bootloader without realizing I needed to flash the stock HBOOT and Splash screen, That's what I get for trying to do it at 11:30 at night.
Click to expand...
Click to collapse
Where are you currently?
s-off?
locked?
whats your CID read as in fastboot?
Also are you on windows 8 or 8.1 and do you have working drivers to begin with.
I have S-ON and Bootloader is locked,Problem,i have Software 1.15 but i flash the HBoot,Boot.img ... To make Moonshine S-OFF.This is the 2.06 Kernel with Software 1.15 and i have Problem with Wifi and the Screen flackered white.And the next Problem,i can't unlock the Bootloader witn Hboot 1.33,i hope you understand me.
jake.corey.jacobs said:
Where are you currently?
s-off?
locked?
whats your CID read as in fastboot?
Also are you on windows 8 or 8.1 and do you have working drivers to begin with.
Click to expand...
Click to collapse
My bootloader screen reads,
"Tampered
Locked
Monarudo pvt ship s-off
CID-VZW_001
HBOOT-1.33.0001
RADIO-1.01.01.0110"
I am on Windows 8 (and have access to a Windows 7 desktop) and yes, I have working drivers.
Moonshine and face palm are failing because you're already s-off
Try a different usb port and flash the stock splash screen, then run RUU
Phaded said:
Moonshine and face palm are failing because you're already s-off
Try a different usb port and flash the stock splash screen, then run RUU
Click to expand...
Click to collapse
Okay I tried both of my 2.0 USB slots and neither worked, Here is what I get -
C:\Users\Matt\Desktop\adt-bundle-windows-x86_64-20130522\sdk\tools>fastboot flas
h splash1 splash.img
sending 'splash1' (4050 KB)...
OKAY [ 0.616s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.653s
You need to unlock... Um try htcdev and go for an unlock token. Since you're s-off it may work.
Fastboot oem unlock might work as well. Try that first, then if no go try htcdev
Phaded said:
You need to unlock... Um try htcdev and go for an unlock token. Since you're s-off it may work.
Fastboot oem unlock might work as well. Try that first, then if no go try htcdev
Click to expand...
Click to collapse
Just tried to OEM unlock and nothing, it gives me this.
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010s
The command is "fastboot oem unlock" isn't?
Just looked into HTC Dev and the DNA is not listed as being supported.
Snowman1771 said:
Just looked into HTC Dev and the DNA is not listed as being supported.
Click to expand...
Click to collapse
you have to select other devices.
Like Jake said, scroll to the other devices part, then try
jake.corey.jacobs said:
you have to select other devices.
Click to expand...
Click to collapse
Just tried and it failed, here is what it said.
Error Code: 160.
Error Reason: MID Not Allowed.
Snowman1771 said:
Just tried and it failed, here is what it said.
Error Code: 160.
Error Reason: MID Not Allowed.
Click to expand...
Click to collapse
does your CID say vzw_001 or 111111 or 222222
You may be able to write the cid since you're s-off. Don't hold me to that tho.
jake.corey.jacobs said:
does your CID say vzw_001 or 111111 or 222222
Click to expand...
Click to collapse
The CID says VZW_001.
Hello all, I've been trying to restore my droid dna back to stock for a warranty return. I have relocked my bootloader using http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19 method and restored with the stock 1.15 RUU. Now this is where the problems start. I had achieved "Relocked" with no tampered or security warnings in my bootloader. However, I wanted to see if I could achieve "Locked" to cover all tracks of tampering with the software. I tried the moonshine method of s-offing and it continuously failed. I would get to moonshining (10) before my phone would completely freeze with screen on and CMD showing "Waiting for device" never moving on to another step. OFC to moonshine I had to update to the 2.06 which I think has now caused all the problems. I cannot downgrade using the original 1.15 RUU because I get Error 158 (image error) after it tried to update signature. I have tried http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19 by flashing the hboot which gives the error:
C:\android-sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.201s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.255s
lastly I tried HTC dev, the original method of rooting I used. Trying from the start as well as just simply trying to use the original unlock code file.
C:\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.126s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.134s
No luck and I'm running out of time because if I don't mail my phone tomorrow I will be charge for the replacement. Im begging for help. :[
Bootloader reads:
Tampered
Relocked
Monarudo pvt ship s-on
Hboot 1.33.0001
Radio-1.01.04.0308
OpenDSP-v4.120.240.0920
emmc-boot
Mar 9 2013,17:46:45:-1
Try rumrunner to s-off again.
Sent from my DNA using my mind.
Uzephi said:
Try rumrunner to s-off again.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Thanks for the reply!
I checked out the website and read all the prereqs,
"Your device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)"
My phone is no longer rooted, and the issue is I cannot figure out how to unlock it. My phone was never s-off if that matters. It was rooted through htcdev before anyone found out how to s-off.
Nevx said:
Thanks for the reply!
I checked out the website and read all the prereqs,
"Your device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)"
My phone is no longer rooted, and the issue is I cannot figure out how to unlock it. My phone was never s-off if that matters. It was rooted through htcdev before anyone found out how to s-off.
Click to expand...
Click to collapse
"Unless using a device blocked by htcdev". Our device is blocked. You are good to go. Keep on reading the instructions after that, and follow them exactly.
Edit: after s-off is achieved, follow the guide "how to return to stock s-on" thread.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my DNA using my mind.
Uzephi said:
"Unless using a device blocked by htcdev". Our device is blocked. You are good to go. Keep on reading the instructions after that, and follow them exactly.
Edit: after s-off is achieved, follow the guide "how to return to stock s-on" thread.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Alright, I'm giving it a try. Everything is working smoothly so far. Now, after I have rebooted and s-off unlocked boot loader, I can restore to factory stock everything and boot loader will show "locked" instead of relocated and tampered etc?
EDIT: It worked, when I used the relock method and that worked fine, but now I have tampered above locked. The tampered remove method didn't work
.
RUU and keep everything stock. Should remove tampered tag
Sent from my DNA using my mind.
Uzephi said:
RUU and keep everything stock. Should remove tampered tag
Sent from my DNA using my mind.
Click to expand...
Click to collapse
RR worked beautifully, everything worked after following a few methods on the RUU, Hboot, recovery, and what not. Droid DNA is stock, S-ON Locked and ready for warranty return.
So much trouble for a non functioning audio jack...
Thank you for your help Uzephi!
EDIT: Thread good to be marked as resolved and locked if need be!
I have Sprint CDMA Evo 3D NOT ROOTED
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
Software Version: 2.95.651.6 710RD
I have been stressing for hours trying to figure this out!
I tried following a tutorial to root the phone and I get stuck trying to unlock the bootloader following htcdev.
After I enter the commands I do not get a dialog on my phone screen asking to unlock bootloader. After googling the issue i found that many people have this problem and running the RUU will fix the problem. I ran the 2.89.651.2 RUU and it failed saying that I have the wrong RUU. The problem is There is no RUU for my current version. I googled this problem as well and barley found answers, the answers I did find said I had to downgrade to 2.89.651.2 I had no idea how to do this and when i looked up how to do it I found an answer that said running the RUU while in temproot state will work (which i tried and got the same outcome as before) I found another answer that said I have to install a recovery and then flash a file that would lower my version and allow me to RUU. I got the img file for the recovery and put it in PG86IMG.zip and put that on my sd card and when i went into hboot it says checking PG86IMG.zip but then it just goes back to the regular hboot screen. Then i looked up an ADB method to flash recovery, I put the img with my fastboot and ran the commands and ended with
C:\Users\Yianni\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platf
stboot flash recovery recovery.img
sending 'recovery' (6914 KB)...
OKAY [ 1.787s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.759s
Now im lost
Breakdown:
Im trying to root
I need to unlock bootloader first
I need to RUU before I unlock bootloader but i cant without downgrading
I cant successfully downgrade
****
Any help is greatly appreciated!!