[Q] unroot with firmware number 2.04.605.2? - HTC Droid DNA

Alright, I hate having to post a new thread on this topic, but I cannot find any solution, or anything close to a solution for this. my problem is that i cant get back to stock from the newest firmware. I had unlocked, rooted, and gotten s-off all before the update. After that, i flashed a few things, and ended up updating to the newest radio and firmware number (2.04.605.2, and 1.01.01.0110). now i want to go back to stock and start fresh, but nothing seems to work. Trying the RUU method only gets me to a 158 Image error about 3 minute into the process, and i cant seem to get back to 1.15. any help is much appreciated. I've been at it, searching for 5 days. if i missed something, or missed a thread, please let me know, thank you in advance

Flash the ENG Hboot then you will be able to run the RUU. Making sure you have the bootloader drivers installed. I generally boot into the bootloader and verify the drivers are loaded BEFORE running the RUU. I can say I have flashed the RUU numerous times so I know it works with the ENG hboot.

Yeap zone is correct, flash the Eng RUU or relock your bootloader either way and then run the RUU. It won't run on a stock hboot that's unlocked.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2

zone23 said:
Flash the ENG Hboot then you will be able to run the RUU. Making sure you have the bootloader drivers installed. I generally boot into the bootloader and verify the drivers are loaded BEFORE running the RUU. I can say I have flashed the RUU numerous times so I know it works with the ENG hboot.
Click to expand...
Click to collapse
Thank you! worked like a charm, i appreciate your quick response I've been running in circles for days now, i can finally get back on track!

Glad I could help.

ENG Hboot & unroot
I'm having the same problem as the op. I downloaded the updates, and i'm trying to unroot my device and put it back to stock (I broke my screen and I want Verizon to fix it, without giving me grief about my software). I have the RUU and Its giving me an 158 Image Error. Sounds like I need to flash eng Hboot and then run the ruu.
Two Questions:
1. Where can I get / download eng Hboot for my DNA?
2. Which version of Hboot do I need? I currently have hboot 1.33.0001.

Related

Rezound stuck in hboot after relock

I wanted to return my rezound to stock after running ics and roms for several months now.
I relocked the phone without issue and read in many forums, once this is done, to use the factory RUU from February to return to stock.
However once relocked and back in hboot, I could only go between the bootloader and fastboot.
I have run the RUU while in fastboot usb and it recognized the phone, however I ran into the Main Ver problem.
I have further read that this is fixable via http://forum.xda-developers.com/showthread.php?t=1467099
But to do that I need the phone to boot into Android and I cannot figure out how to do that or any other way around these problems.
I am grateful for any help.
JK503 said:
I wanted to return my rezound to stock after running ics and roms for several months now.
I relocked the phone without issue and read in many forums, once this is done, to use the factory RUU from February to return to stock.
However once relocked and back in hboot, I could only go between the bootloader and fastboot.
I have run the RUU while in fastboot usb and it recognized the phone, however I ran into the Main Ver problem.
I have further read that this is fixable via http://forum.xda-developers.com/showthread.php?t=1467099
But to do that I need the phone to boot into Android and I cannot figure out how to do that or any other way around these problems.
I am grateful for any help.
Click to expand...
Click to collapse
I suggest fixing the MainVer problem by flashing this: https://dl.dropbox.com/u/30190874/Se... (1).zip rename to ph98img
I got it from Scottsroms website.
However, if you are S-on and have flashed an ICS RUU, then you can't go back to GB unless you S-off.
topgun1953 said:
I suggest fixing the MainVer problem by flashing this: https://dl.dropbox.com/u/30190874/Se... (1).zip rename to ph98img
I got it from Scottsroms website.
However, if you are S-on and have flashed an ICS RUU, then you can't go back to GB unless you S-off.
Click to expand...
Click to collapse
Alright, I had trouble with the dropbox link. I kept running into an error.
I am fine with it saying relocked. If I have a Gingerbread RUU and reset the MainVer and am on ICS firmware I cannot flash a Gingerbread RUU?
Can I rename the file ph98img.zip and flash it that way?
Edit - I reunlocked the phone. I have setmainverlow.zip. I have been reading on scottsroms that after running this and re-relocking int, I should be able to run the Gingerbread RUU.
Edit- That got me past the main ver problem. Now it says the hboot is to old. Is there something I can flash to revert to an older hboot?
JK503 said:
Alright, I had trouble with the dropbox link. I kept running into an error.
I am fine with it saying relocked. If I have a Gingerbread RUU and reset the MainVer and am on ICS firmware I cannot flash a Gingerbread RUU?
Can I rename the file ph98img.zip and flash it that way?
Edit - I reunlocked the phone. I have setmainverlow.zip. I have been reading on scottsroms that after running this and re-relocking int, I should be able to run the Gingerbread RUU.
Edit- That got me past the main ver problem. Now it says the hboot is to old. Is there something I can flash to revert to an older hboot?
Click to expand...
Click to collapse
I'll see what others have to say but I think you need to be s-off to do that.
Will someone confirm?
topgun1953 said:
I'll see what others have to say but I think you need to be s-off to do that.
Will someone confirm?
Click to expand...
Click to collapse
If you are S-On and have flashed the ICS firmware you cannot go back.
Chyrux said:
If you are S-On and have flashed the ICS firmware you cannot go back.
Click to expand...
Click to collapse
Good to know, thanks for your response.

How to flash radio with S-ON HBOOT 1.15

I successfully installed Fresh Evo LTE 5.3.1 on my phone.
One of the suggestions is to update the Radio but I'm having a tough time doing that.
Here are my specs:
HBOOT 1.15.0000
S-ON
FreshEVO 5.3.1 ROM
I went to the link from the FreshEVO LTE 5.3.1 page to update the radio and have tried the following to install the Radio:
Attempt 1
Downloaded the Full Firmware zip file
Rename it "PJ75IMG"
Place it in the root of my SD card
Reboot into Bootloader
The PJ75IMG.zip file is detect but I only get 'Parsing PJ75IMG.zip' and then the Fastboot, Recovery, etc. options are displayed.
Attempt 2
From the same page where I downloaded the Full Firmware zip file, I also tried:
Download the Boot.img Only (signed) file
Flash it through the command prompt while in Fastboot ("fastboot flash boot boot.img")
Go into Bootloader
The PJ75IMG.zip is detected but still get the "Parsing..." message and nothing else happens.
Attempt 3
I have also tried going into my TWRP recovery and installing the Full Firmware zip AND the Radio 1.12.11.0809 Only.zip file but the installation fails.
Any pointers or a link to a video or a post would be much appreciated.
Thanks and sorry if this is a duplicate post but I really couldn't find any post that showed step-by-step process.
revert to stock and accept the ota, you can then fastboot recovery again and reflash. hboot 1.15 can not directly flash any firmware
edit: you may have to relock your hboot but ive seen users state they didnt. if you decide to relock the phone you will have to unlock the bootloader again to enable fastboot
om4 said:
The easiest way to update your firmware is to revert to stock and accept the ota, you can then fastboot recovery again and reflash
Click to expand...
Click to collapse
I don't have my stock backup anymore.
I've heard stuff about using RUU or something like that. Any quick guide on how to revert back to stock?
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Rxpert said:
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Click to expand...
Click to collapse
Thanks for the warning.
Since I'm pretty new to all this, I'll play it safe and stick to what I have.
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
The new radios aren't worth losing the possibility, no matter how small
Sent from my EVO using Tapatalk 2
True...
om4 said:
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
Click to expand...
Click to collapse
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
RamesisX said:
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
Click to expand...
Click to collapse
I havent yet done it myself but users have said they didnt need to relock, how ever as captain said there is no real need to update right now. If you decide to go ahead it would be a good idea to relock ( fastboot oem lock ) just to make sure, you can unlock afterwards. I neglect to mention this in my guide because most phones now are on 1.19 anyway and those still on 1.15 are holding out for soff
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Rxpert said:
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
RamesisX said:
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
Click to expand...
Click to collapse
there is no simpler method for relocking hboot, simply fastboot oem lock
om4 said:
there is no simpler method for relocking hboot, simply fastboot oem lock
Click to expand...
Click to collapse
Used that and it worked great.
Evo 4G LTE
h-boot 1.19, s-on, HTCDev unlocked

return to stock gsm evo 3d, downgrade bootloader? s-off?

hey forum
i really need some help now. i have a gsm evo 3d unlocked up and running a custom rom (nonsense). now i want to return to stock, ive tried flashing the ruu for several times, but each time it says bootloader version error. so i guessed that i have to downgrade my hboot version from 1.53.0007 to something 1.49.007 or similiar. i just cant get it to work, neither with flashmaniacs way, or the manual way. in bootloader when loading the PG86IMG ist says version older update fail.each time i fail i reunlock the bootloader, so atleast i can use my phone. the worst and most foolish part of me: no nandroid backup. so i recognize my fault.
Do you have the newest ruu.exe for your region/carrier? Once you get it, boot into bootloader, connect to computer (should say fastboot usb), lock bootloader, then run ruu. That should put you at stock.
Test shooter u ruu for ics?
coal686 said:
Do you have the newest ruu.exe for your region/carrier? Once you get it, boot into bootloader, connect to computer (should say fastboot usb), lock bootloader, then run ruu. That should put you at stock.
Click to expand...
Click to collapse
i dont know wether its the newest or not, ive tried the one i got from file factory its called
RUU_Shooter_U_HTC_Europe_1.20.401.8_Radio_10.59.9020.00_10.15.9020.06_M_release_219793_signed.exe
im not sure, but i think its gingerbread. ive been searching for an ics ruu fpr europe, but havent found one yet, only one "test ruu" which is official, should i give it a go? it seems to have some minor bugs.
heres the thread
http://forum.xda-developers.com/showthread.php?t=1669104
do you know where to get a stock ics ruu for sure?
I'm in the US, so I don't know exactly. Did you look here: http://forum.xda-developers.com/showthread.php?t=1208485
Have you relocked your bootloader before flashing ruu? Bootloader must locked or relocked if you want to flash stock soft. I've flashed RUU named:
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
It's stock ics rom. Here is direct link:
http://www.filefactory.com/file/2hw...00U_11.25.3504.06_M_release_262714_signed.exe
c000ler said:
Have you relocked your bootloader before flashing ruu? Bootloader must locked or relocked if you want to flash stock soft. I've flashed RUU named:
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
It's stock ics rom. Here is direct link:
http://www.filefactory.com/file/2hw...00U_11.25.3504.06_M_release_262714_signed.exe
Click to expand...
Click to collapse
yes i relocked my bootloader each time i tried to flash. thanks alot! ive been looking for a ICS ruu for quite some while, gonna download it and try it out. hope itll work out fine.
the ones i downloaded from the filefactory link somehow didnt work, dont know why.
i really appreciate your help, thanks guys
it worked, im back to stock, so it was the old ruu which created problems. thanks

hboot main version is older, update failed

Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
flybub said:
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
Click to expand...
Click to collapse
Hem... that's the current bootloader. Are you s-on or off ?
dottat said:
Hem... that's the current bootloader. Are you s-on or off ?
Click to expand...
Click to collapse
I'm S-On. I downloaded the PH98 file again thinking maybe it was bad, but no dice. I get the same error message. I can't get anything to boot. I was able to flash a recovery so I flashed Infection 2.5 but I keep getting stuck at the Android looking screen (yes boot.img was flashed in fastboot). I flashed a couple different ICS roms but none of them boot up. I figured if I could get back to stock I would just go s-off and be done with it but I think this phone is done.
Edit: Gave the phone to a friend of mine who is much better at this stuff than I am. Maybe he can figure it out. Thanks for the help
Hm, if you flashed the kernel you should be able to boot up.
If you're s-on and on hboot 2.28 there's no RUU as of yet you can run. There's a stock OTA ROM of the lates OTA in the dev section you can run that and see if that helps. You probably can s-off on that but don't take my word for it, especially since you're on 2.28 hboot.
I would make a nandroid before so you can always get back to that if needed.
If you really want to run an RUU you need to s-off, but confirm that it's still going to work on the latest OTA before trying it.

Process to fix

I've been restraining myself from posting this for a few days, while browsing and looking through threads trying to figure out my answers. Something is wrong within my device, something is corrupted. Phone keeps rebooting on phone calls, and my UI is trashed, its all zoomed out and looking crazy. Flashing different ROMs has not helped. I have taken under advisement to RUU. However, I just want to make sure there is nothing I need to do before RUU'ing to keep from screwing up the device. Here is my current status: the only things I have done to this device since I got it last may are root and unlock using moonshine. So I have had no OTAs that I know of. This is the RUU I have:
RUU_DLX_WL_JB_50_S_VERIZON_WWE_3.06.605.4_Radio_1.01.01.1112_NV_VZW_4.46_002_release_340974_signed_2
I just want to make sure I only need to run that, and don't need to flash anything else (such as hboot, etc)
Thanks.
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
lemonoid said:
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
Click to expand...
Click to collapse
Manually boot the phone to the bootloader before you start and it will go. For whatever reason it doesn't do it itself so manually doing it will give you success.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
lemonoid said:
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
Click to expand...
Click to collapse
error 158= wrong Hboot ; Solution *You need to Update Hboot to 1.54 in order to Run RUU 3.06
http://forum.xda-developers.com/showpost.php?p=42352912&postcount=4
Jaggar345 said:
Manually boot the phone to the bootloader before you start and it will go. For whatever reason it doesn't do it itself so manually doing it will give you success.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I started the RUU with the phone in fastboot. I'm going to try to upgrade to 1.54 then RUU

Categories

Resources