Situation:
TWRP works. TWRP reports no OS and phone will not boot. Looking to reload/recover this phone. Everything I've tried has failed. Is there a step by step easy way out of this? All help GREATLY Appreciated!!
Some more info would be helpful. Are you S-on or S-off? What is your Hboot version? What ROM are you trying to install? What version of TWRP do you have installed?
Magnum_Enforcer said:
Some more info would be helpful. Are you S-on or S-off? What is your Hboot version? What ROM are you trying to install? What version of TWRP do you have installed?
Click to expand...
Click to collapse
S- ON
Hboot 1.19.00
Trying to install any ROM that might work
TRWP Version 2.3.1.0
Thank you for your help
If I were you I'd run the RUU for the Android 4.3 update. Hit the top link in my sig and read the RUU section. Then download the RUU for Android 4.3, which can be found at the bottom of the first post of my bootloader guide. Afterwards, reinstall TWRP with the latest version. The version you have is very outdated, as is your bootloader version & firmware. You can download the latest version of TWRP from the link below.
http://techerrata.com/file/twrp2/jewel/openrecovery-twrp-2.8.4.0-jewel.img
I tried the RUU 4.3 and got the following message:
Error [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Sxottie said:
I tried the RUU 4.3 and got the following message:
Error [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse
Relock your bootloader and try again, being s-on your bootloader needs to be locked to ruu.
Fastboot oem lock I believe it is
gstanke said:
Relock your bootloader and try again, being s-on your bootloader needs to be locked to ruu.
Fastboot oem lock I believe it is
Click to expand...
Click to collapse
That was the piece of the puzzle I was missing. After downloading the Android-SDK to run ADB I'm all set now. The RUU worked flawlessly!!! Thank you everyone for your help!!!
Related
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
drknrgy said:
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
Click to expand...
Click to collapse
you can pull the rom.zip from the ruu, and run that in hboot.. or just unlock the bootloader again
drknrgy said:
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
Click to expand...
Click to collapse
Yes, you can run the RUU via pc in fastboot. That's how I ran it . Just as long as it says fastbootusb , it will work.
I was stuck in Hboot as well.. so not sure how you avoid it. Easy enough to run the RUU out of fastboot though.
andybones said:
you can pull the rom.zip from the ruu, and run that in hboot.. or just unlock the bootloader again
Click to expand...
Click to collapse
Can I run the RUU.exe directly on pc while in fastboot usb?
"you can pull the rom.zip from the ruu, and run that in hboot." not sure what that means if you run RUU.exe on pc How could I "pull the rom.zip from the ruu" if I cant run recovery??
Never ran RUU
Ok Just to make sure then.. Am I running the correct RUU? Will this further effect me if trying to run the wrong RUU file ? I guess my question is, to be more specific, does my listed RADIO in hboot need the correct RUU file ??
drknrgy said:
Ok Just to make sure then.. Am I running the correct RUU? Will this further effect me if trying to run the wrong RUU file ? I guess my question is, to be more specific, does my listed RADIO in hboot need the correct RUU file ??
Click to expand...
Click to collapse
It won't let you run the wrong RUU.. if you havent taken the OTA yet, the correct RUU is 1.06.xxxxx
Yes, you run the exe on the PC while in fastboot.
mjh68 said:
It won't let you run the wrong RUU.. if you havent taken the OTA yet, the correct RUU is 1.06.xxxxx
Yes, you run the exe on the PC while in fastboot.
Click to expand...
Click to collapse
Is there a way to determine the correct RUU? This one>>>>
WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_ 8k_1.12_9k_1.83_V_APT_release_2215<<<<
FAILED
"ERROR [140] BOOTLOADER VERSION ERROR"
Would the latest > new RUU for 2.01.605.11 < WorK?
drknrgy said:
Is there a way to determine the correct RUU? This one>>>>
WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_ 8k_1.12_9k_1.83_V_APT_release_2215<<<<
FAILED
"ERROR [140] BOOTLOADER VERSION ERROR"
Would the latest > new RUU for 2.01.605.11 < WorK?
Click to expand...
Click to collapse
Did you update with the OTA or have your main ver updated ? Sounds like you had a partial update with the bootloader being updated to 2.11 maybe.
Try the new RUU see if it will run it.
mjh68 said:
Did you update with the OTA or have your main ver updated ? Sounds like you had a partial update with the bootloader being updated to 2.11 maybe.
Try the new RUU see if it will run it.
Click to expand...
Click to collapse
I do not have the new OTA. I was root/unlocked. I tried doing wipe from ra and then run CleanRom GBE 1.6OTA zip from sd. Then I think I ran fastboot boot.img...
I have lost track of my steps at this point but the bootloader still states HBOOT-2.10.0000 on the white security warning screen w/3 droids at the bottom
BTW...Is there a direct link for new RUU available? DpBox??
drknrgy said:
I do not have the new OTA. I was root/unlocked. I tried doing wipe from ra and then run CleanRom GBE 1.6OTA zip from sd. Then I think I ran fastboot boot.img...
I have lost track of my steps at this point but the bootloader still states HBOOT-2.10.0000 on the white security warning screen w/3 droids at the bottom
BTW...Is there a direct link for new RUU available? DpBox??
Click to expand...
Click to collapse
It is in the developement forum.. Sticky thread for the Vigor rom collection. It was on the last page.. might have been bumped back a page or so.
Hmm , not sure why it is giving you that error if you still have hboot 2.10 , let me check and make sure that first RUU was the right one. Yes, you quoted the same RUU I used when I did the process.
mjh68 said:
It is in the developement forum.. Sticky thread for the Vigor rom collection. It was on the last page.. might have been bumped back a page or so.
Hmm , not sure why it is giving you that error if you still have hboot 2.10 , let me check and make sure that first RUU was the right one. Yes, you quoted the same RUU I used when I did the process.
Click to expand...
Click to collapse
Thanks for the D/L on the latest RUU.. almost finished. If I run this one via .exe and still get a failure re: bootloader what are my other options? I have other options don't I? Can I use a cmd to "push"? Any ideas? Thanks for all the help!
before running the RUU...
current image Version:
2.01.605.11
(same as latest RUU) crossing fingers now..
drknrgy said:
Thanks for the D/L on the latest RUU.. almost finished. If I run this one via .exe and still get a failure re: bootloader what are my other options? I have other options don't I? Can I use a cmd to "push"? Any ideas? Thanks for all the help!
before running the RUU...
current image Version:
2.01.605.11
(same as latest RUU) crossing fingers now..
Click to expand...
Click to collapse
Looks like somehow your mainver did get updated so the newest RUU should work. If this one fails I am out of ideas, I am fairly new to this myself so learning as I go. RUU's are similar to SBF's from motorla to return phone to stock out of the box condition. The way they work I don't think you can force push it to restore as far as I know.
This one worked perfectly and included the OTA . I am however complete stock now, lost root. My mind is a bit warped from all this confusion. How do I get root back again..? Flash amon ra ? go into Developer and install su. ?
drknrgy said:
This one worked perfectly and included the OTA . I am however complete stock now, lost root. My mind is a bit warped from all this confusion. How do I get root back again..? Flash amon ra ? go into Developer and install su. ?
Click to expand...
Click to collapse
Yes, just go into amon ra install su and superuser , then reboot. Might have to still download superuser from the market and install ,but then you should be good to go.
mjh68 said:
Yes, just go into amon ra install su and superuser , then reboot. Might have to still download superuser from the market and install ,but then you should be good to go.
Click to expand...
Click to collapse
Thanks for the great advice. I am back up and running w/OTA and root. Just need to nan-restore now. Bring on ICS!
i have read this post and my problem is somewhat similar. i can't seem to get my computer to read my phone. my sd port isn't coming up. i have my phone connected and using hasoon2000 all in one tool kit. my hboot version is 20225.0000 and radio is 1.22.10.0421r/1.22.10.042r. how can i get my phone off this white screen and also how can i get my phone and computer to read each other??? im also relocked i tried to unlock it using hasoon 2000 all in one tool kit but can't get it to kick in. and when i go into the cmd command prompt it tells me device error. the phone isn't reading.
Hello. I have searched the net and these forms and am not finding the answer.
I need to RUU back to stock, currently running CM10. S-on, Hboot 1.15
Do I need to install the stock recovery or can I just run the RUU with TWRP?
Thanks!
bojutt said:
Hello. I have searched the net and these forms and am not finding the answer.
I need to RUU back to stock, currently running CM10. S-on, Hboot 1.15
Do I need to install the stock recovery or can I just run the RUU with TWRP?
Thanks!
Click to expand...
Click to collapse
just relock bootloader and run from fastboot, it rewrites all software on the phone
om4 said:
just relock bootloader and run from fastboot, it rewrites all software on the phone
Click to expand...
Click to collapse
Thanks!!
Which RUU should we use? The only one I've been able to find is an other one for a much older firmware. Or does it really matter which version it is?
It should at the very least match your current software, if you can't find it at all, htcdev offers ruu for the latest firmware
As om4 mentioned, only install one that is the same or newer.
http://stockroms.net/file/HTCEvo4GLTE/RUU
or
http://www.filefactory.com/f/b6eb73c80cc97030/
I have installed CM 10.2 (Android 4.3) and have tried running an RUU (both through fastboot and the executable) to which they both end up failing. The fastboot states too many threads when writing the bootloader and the Windows executable gives an error 155.
[SOLVED] Look below!
Anyone able to help I am just starring at my boot loader screen all day. TWRP will not even allow me to sideload says cannot mount anything.
So after two days of not having a phone, I solved the issue.
It seems the RUU would not run with the newer version of HBOOT found in the GE version of the rom. So I reflashed HBOOT 1.44 (see attached) and BOOM RUU worked and back to stock!
Hope this helps someone
https://mega.co.nz/#!XhRlXBhB!V8In4VJhp5MXwj9r9gyleTCFiUIbKWxDFmcmn8v3zIU
is that the latest version? I am kind of new to rooting and stuff, I guess when you flash TWRP it replaces HBOOT so that is why you had to reflash HBOOT? I am going to install Android Revolution HD and would like to get all the info beforehand.
schn1tt3r said:
is that the latest version? I am kind of new to rooting and stuff, I guess when you flash TWRP it replaces HBOOT so that is why you had to reflash HBOOT? I am going to install Android Revolution HD and would like to get all the info beforehand.
Click to expand...
Click to collapse
Custom recovery does not replace hboot. You shouldn't have to replace hboot to flash ARHD. You don't even have to unlock the bootloader. Just S-off, flash custom recovery, nandroid backup, and flash ARHD. After Rom is flashed, flash new firmware to update your 1.29 firmware to 2.24
Sent from my HTC One using xda premium
Trying to go back to stock. I too tried the 4.3 firmware and hboot, radio. So right now I am on hboot 1.54 and firmware 3.06.1700.10
I want to go back to stock...any help?
Hello members,
Looking for some confirmation please as I am finding conflicting information on the forums.
I am currently running 4.1.2 (1.27.531.8). The phone is rooted and s-on (never saw a reason for s-off if anyone is curious) I am also running the ClockworkMod Recovery v6.0.3.2 and hboot 1.44
My phone currently sees the 1.27.531.11 update available, but fails to update. I'm guessing this is because I have a custom recovery installed.
What do I need to do to get to 4.3 (3.24.531.3)?
Do I need to flash stock recovery before I run the official update from HTC? Do I need to upgrade to 1.27.531.11 and then 3.24.531.11?
Most importantly, what happens if I run the official 4.3 update from HTC right now?
Thanks in advance,
Zx
Any insight?
Thanks,
Zx
If I were you I would s-off first, then flash the RUU off HTC's site.
blackangst said:
If I were you I would s-off first, then flash the RUU off HTC's site.
Click to expand...
Click to collapse
What is the benefit of going s-off prior to updating? Do you suppose having a custom recovery is a non issue?
Thanks for the reply.
zx6rrninja said:
What is the benefit of going s-off prior to updating? Do you suppose having a custom recovery is a non issue?
Thanks for the reply.
Click to expand...
Click to collapse
If youre s-off you dont have to worry about flashing stock recovery and hboot.
edit: actually, Im incorrect. You can just run the RUU. Download to desktop, plug phone in while its on, and run RUU. It'll take about 10 mins. You'll then be unrooted stock.
blackangst said:
If youre s-off you dont have to worry about flashing stock recovery and hboot.
edit: actually, Im incorrect. You can just run the RUU. Download to desktop, plug phone in while its on, and run RUU. It'll take about 10 mins. You'll then be unrooted stock.
Click to expand...
Click to collapse
FYI, That failed wonderfully with Error 155 Looks like I may have to lock the boot loader? Mmmm....
Troubleshooting...
After locking the boot loader the RUU successfully upgraded my phone.
zx6rrninja said:
After locking the boot loader the RUU successfully upgraded my phone.
Click to expand...
Click to collapse
Great!
blackangst said:
Great!
Click to expand...
Click to collapse
Indeed! Thanks again blackangst.
Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
ab1009 said:
Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
Click to expand...
Click to collapse
Do you want to get back to stock Sense? Download and run this RUU while in fastboot
https://docs.google.com/file/d/0B32gqnbh2ZecSHM2VXJoY2tFUU0/edit?usp=sharing
Or you can sideload a ROM .zip from CWM and install it.
Thank you duffman for reply, I downloaded the RUU and excute it but I got error 155, I tried other RUU also I got the same error, how to avoid this error?
br
ab1009 said:
Thank you duffman for reply, I downloaded the RUU and excute it but I got error 155, I tried other RUU also I got the same error, how to avoid this error?
br
Click to expand...
Click to collapse
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
ibsk8 said:
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
Click to expand...
Click to collapse
Exactly. Download the DNA toolkit. http://forum.xda-developers.com/showthread.php?t=2219175
Use it to flash the 3.06 hboot
After that, try the 3.06 RUU again.
ibsk8 said:
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
Click to expand...
Click to collapse
duffman452001 said:
Exactly. Download the DNA toolkit. http://forum.xda-developers.com/showthread.php?t=2219175
Use it to flash the 3.06 hboot
After that, try the 3.06 RUU again.
Click to expand...
Click to collapse
thank you ibsk8 and duffman,
I treid what you wrote but I got this error: FAILED (remote: 99 unknown fail) what is my mistake??
br
ab1009 said:
thank you ibsk8 and duffman,
I treid what you wrote but I got this error: FAILED (remote: 99 unknown fail) what is my mistake??
br
Click to expand...
Click to collapse
Hmmm I just realized you're s-on. When you say you tried the other RUU, did you try the alternate 3.06 RUU or the 1.15 RUU?
1.15 RUU: https://docs.google.com/file/d/0B32gqnbh2ZecSHM2VXJoY2tFUU0/edit?usp=sharing
That really should work since you're on the 1.15 hboot and radio. If not, can you send a screenshot of the error?
Hi duffman,
I tried to Flash the 1.15 RUU but I got 155 error. please see my pics.
br
looks like you may have been trying to s-off? which did not complete.
rerun s-off and try different usb port
Thank You DJ_MiX for reply,
I used Moonshine to S-Off, I puted the Droid DNA in "Fastboot USB" mode, I did all as in instruction, I got Error: run distiller again and READ.
I used Rumrunner and I see now: "no ADB connection to device, Debugging on?" but I cannot boot the device in normal android and choose "USB debugging". I can boot to HBoot/Fastboot or Recovery Mode.
can you help me to s-off this phone (can I use RUU with s-off phone??)
br
Error 155 is due to attempting to RUU while unlocked. To apply an RUU you must be locked. In order to lock your device connect to your pc and enter fastboot usb mode. use the command "fastboot oem lock". Once you are locked you can RUU using the current version as reported by the RUU utility or a higher version.
After this is successful you should obtain s-off, as this will save you in the future from the current issue you created for yourself. Alternatively you can apply all the OTAs and fully update to kit-kat firmware.
Note: once you are locked again you will not be able to boot (no change there) and you will not be able to enter recovery due to the non-factory recovery.
Thank you all espcially TheRealDeadApe,
My phone is now alive again. I have flashed it with RUU 1.15 but with RUU 3.06 I get ERROR (158) IMAGE ERROR. now I have Android 4.1.1 can I upgrade to 4.4.2 if I live outside USA?
br
Bump. I'm in the exact same situation.
ab1009 said:
Thank you all espcially TheRealDeadApe,
My phone is now alive again. I have flashed it with RUU 1.15 but with RUU 3.06 I get ERROR (158) IMAGE ERROR. now I have Android 4.1.1 can I upgrade to 4.4.2 if I live outside USA?
br
Click to expand...
Click to collapse
As for the OTAs you can apply them anywhere you are if you download the zip files and flash them using the stock recovery. Search this forum.
Personally I would s-off. I used moonshine on the 1.15 firmware when I did it. Then you can flash RUUs without restrictions so you can update easier or update the firmware only and flash a custom rom.
For Flashing Custom ROM to Dead DNA
ab1009 said:
Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
Click to expand...
Click to collapse
This is for future reference since this has been solved. This method is from my own experiences and will work if you absolutely need functionality as soon as humanly possible.
What you can do is plug your phone while it is in recovery and select install zip from sideload.
find a custom rom you want with the corresponding GAPPS if needed,
put the rom.zip and your gapps.zip (if applicable) at the root directory of your adb. (rightclick adb on desktop click go to file location)
Rename your rom.zip to literally just rom.zip (makes it a lot easier later) and the gapps.zip to gapps.zip
check to see if your pc sees your device after selecting install zip from sideload by running "adb devices". you should see a long id number with SIDELOAD to the right.
If your device shows up, then run "adb sideload rom.zip", once finished do not hit reboot system until you flash gapps if needed.
for gapps run 'adb sideload gapps.zip" then reboot your phone. Your phone should now have functionality restored. :good: