Related
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Thankyou!
Just wanted to say I'm the guy that messed up his phone and needed Jason's help. He got me into a Sense ROM and was able to then get clockwork running again and restore my Nand. Really save my bacon.
Also, I've followed your advice. I now have a rooted AND S-off hero running Gingerbread.
Thanks again!
jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
Really? Thanks for the Info... Helpful, and Good to Know!!
Sent from my Hero using XDA App
wow, this is valuable information. couldnt this be put into the wiki or something? i tend to go to the wiki often, but i dont know how to properly edit a wiki.
jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.
Houndog101 said:
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.
Click to expand...
Click to collapse
Which bootloader version do you have, and where did you get the fastboot binary?
jasonmaloney said:
Which bootloader version do you have, and where did you get the fastboot binary?
Click to expand...
Click to collapse
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..
hey Jason here's some background on his problem, I linked him this thread, hopefully you have more patience than me, but you know me, I don't really and I'm a dink http://forum.xda-developers.com/showthread.php?t=984688
Houndog101 said:
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..
Click to expand...
Click to collapse
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.
jasonmaloney said:
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.
Click to expand...
Click to collapse
Jason, Thanks a million times, That was a problem, I d/l your fast.boot and it got me to the Black with silver htc screen. I'll see what I can do from here. Just want to get it to where I can boot into recovery.. Thanks again for helping me.
I've followed all the instructions but with a slightly different problem. I can't get to bootloader at all, but if I plug my hero to my pc and turn it on then it will say "fastboot usb" in a red rectangle at the top left, but is still otherwise the white HTC screen. when I do "fastboot oem rebootRUU" the terminal says okay, but the phone reboots into the same state instead of the black and silver screen I am hoping to see. Is it a brick or is there another option?
I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.
beand1p said:
I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.
Click to expand...
Click to collapse
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Yea It's Me Again With the
Modified Hero
laie1472 said:
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Click to expand...
Click to collapse
I get the same error even with that zip. I am S-OFF also. I have HBOOT-1.47 with radio 2.42.01.04.27.
I've tried almost everything to unroot and get back to stock. I am about ready to throw in the towel.
Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]
dpeeps74 said:
Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]
Click to expand...
Click to collapse
All the stock RUU's I have tried always give me the RUU Error [140]: BOOTLOADER VERSION ERROR
EDIT
I was able to RUU after using this method: http://forum.xda-developers.com/showthread.php?t=843544
I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.
zbach said:
I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.
Click to expand...
Click to collapse
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.
jasonmaloney said:
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.
Click to expand...
Click to collapse
I have the zip file in the android file along with the fastboot.exe program. I still get a "Cannot load" error message
thank you x100000.
I couldnt flash the original ruu because of the weird bootloader issue, but this worked like a charm and i was able to flash with a .zip of the ruu.
Thanks again.
If you're constantly getting ERROR 155 when trying to flash an RUU even though you've already returned your phone to stock, you also need to RELOCK the bootloader!
I'm writing this because for some reason just getting the phone back to stock (i.e. restore image of stock ROM through custom recovery then flash stock recovery) didn't work for me. It only worked after I RELOCKED the bootloader.
Step 0. Restore your phone to stock FIRST, i.e. restore stock ROM from image using custom recovery then flash stock recovery.
Step 1. Restart your phone into bootloader either by hard-off (i.e. keep power button pressed for min. 10 sec) then volume up + power button or by adb at the command prompt:
Code:
C:\> adb reboot-bootloader
Step 2. Type this command at the command prompt:
Code:
C:\> fastboot oem lock
Don't worry if it says FAILED anywhere in the output, it should all be fine regardless. The phone should reboot automatically into bootloader and should say RELOCKED.
Now you can flash any RUU (EDIT: only if compatible with your CID) and you can also check for and install OTA updates. Once you've done this, your HBOOT and RADIO should be updated to the latest version so you can UNLOCK again using the HTCDev method and then flash whatever you want to flash.
Hope this helps you guys!
P.S. I think it's worth also trying this for other ERROR codes... you never know, it may help.
Getting error 131 didn't help. But much thanks for trying help
i hear voices in my head
Any RUU or still only the specific carrier RUU?
Sent from my HTC One S using xda premium
I think the prob is that i have VODAP102 CID in ruu 1.5... and 1.78
i hear voices in my head
had that error too, worked for me with locking bootloader
again, starting ruu-exe after that.
thanks
ovimunt said:
If you're constantly getting ERROR 155 when trying to flash an RUU even though you've already returned your phone to stock, you also need to RELOCK the bootloader!
I'm writing this because for some reason just getting the phone back to stock (i.e. restore image of stock ROM through custom recovery then flash stock recovery) didn't work for me. It only worked after I RELOCKED the bootloader.
Step 0. Restore your phone to stock FIRST, i.e. restore stock ROM from image using custom recovery then flash stock recovery.
Step 1. Restart your phone into bootloader either by hard-off (i.e. keep power button pressed for min. 10 sec) then volume up + power button or by adb at the command prompt:
Code:
C:\> adb reboot-bootloader
Step 2. Type this command at the command prompt:
Code:
C:\> fastboot oem lock
Don't worry if it says FAILED anywhere in the output, it should all be fine regardless. The phone should reboot automatically into bootloader and should say RELOCKED.
Now you can flash any RUU (EDIT: only if compatible with your CID) and you can also check for and install OTA updates. Once you've done this, your HBOOT and RADIO should be updated to the latest version so you can UNLOCK again using the HTCDev method and then flash whatever you want to flash.
Hope this helps you guys!
P.S. I think it's worth also trying this for other ERROR codes... you never know, it may help.
Click to expand...
Click to collapse
now I get error 132 : signature error. I have superCID help?
I don't know how you can sort out the CID issue. I have a SIM free phone so I haven't really looked into that. Sorry....
are you refering to recovery stock (step 1)?
i get error 155 but i have stock recovery and locked bootloader,
my bootloader says security warning though which is strange.
current rom is the ir1 modaco stock rom
i had 155, i put stockrecovery back and relocked bootloader, then 155 changed to battery too low error, so turned it off, charged for 2hrs, and the ruu worked for the first time
I have HTC One S z560e and i want to go back to stock but even with the bootloader unlocked i still get 155error.... what should i do?
Hey people.
Can someone tell what version of RUU i can use for HTC one S4 im in portugal?
Tks
i have a rogers it was at 3.17 i unlocked the bootloader and then installed twrp now i cant get past that screen
what can i do i need my phone
thanks
p.s it was at 2.14 hboot also
babarnard said:
i have a rogers it was at 3.17 i unlocked the bootloader and then installed twrp now i cant get past that screen
what can i do i need my phone
thanks
p.s it was at 2.14 hboot also
Click to expand...
Click to collapse
what command did you run to flash twrp? "fastboot flash recovery <twrpfilename>.img" if you ran "fastboot flash boot <twrpfilename>.img" then you need to run "fastboot flash boot boot.img" to allow you to boot again then run the correct command "fastboot flash recovery <twrpfilename>.img" to flash recovery.
i used the hasoon 2000 aio kit if that means anything
thanks for your quick reply though
So is it just chilling at twrp curtain pull down? Can you navigate through twrp?
i can navigate through twrp but thats all i can do and i am lost now
babarnard said:
i used the hasoon 2000 aio kit if that means anything
thanks for your quick reply though
Click to expand...
Click to collapse
sorry i haven't used the kit, did you hit reboot system in twrp?
yes and i try reboot system and recovery and it still just goes to the teamwin and thats it
babarnard said:
yes and i try reboot system and recovery and it still just goes to the teamwin and thats it
Click to expand...
Click to collapse
i think recovery is flashed where boot is supposed to be, you need to flash boot.img from fastboot.
Reflash everything manually reflash recovery reflash boot.I'mg
i am new to this stuff so please be patient with me
how do i reflash manually
thanks
look at my first post and this post for the files http://forum.xda-developers.com/showpost.php?p=38217541&postcount=297
ok sorry but im confused i tried to reflash but i get nothing to happen its the same as before stuck on teamwin screen
so you confirmed flashing in fastboot recovery to recovery and boot to boot? if so, i would just fastboot oem lock then run ruu and start over without the kit this time. all you need to do afterwards is use ur token to reunlock, flash recovery in fastboot then copy rom to sdcard and flash, if you get booted into sense somehow turn off fast boot in power and turn on usb debugging in developer options then issue adb reboot bootoader or adb reboot recovery depending on where you are trying to go.
i dont have the ruu for rogers 3.17 though any idea where i can find this
thanks for your patience so far
hi guys i really hate to be such a pain but i need my phone back can anyone give me a idiots guide to getting it back working again i am still stuck at the teamwin screen or the fastboot screen cant go anywhere else
thanks in advance guys
babarnard said:
i dont have the ruu for rogers 3.17 though any idea where i can find this
thanks for your patience so far
Click to expand...
Click to collapse
http://spadacapa.blogspot.co.uk/2012/06/at-and-rogers-htc-one-x-lte-stock-ruu.html
AT&T HTC OneX
Android 4.1.1
ViperXL
how do i install it now that i downloaded it
Fastboot oem lock than run the ruu
really new to this what do i run the ruu with
thanks
No offense but that's simple computer knowledge... But exe files on the computer can be ran just double click on it and run it
Okay so I have been running CM10 fine for months. But I got a notification about an OTA update to CM10.1 and decided to let it install... bad idea.
the install process failed somehow and then my phone was stuck at the HTC screen when booting. Booting into recovery wouldn't work because it would try to install the ROM but always fail. So I figured I could just flash my recovery and restore. So I download the newest TWRP and flasht he recovery. Once I get into TWRP I couldn't read the SDCARD or find any of my files. But if I use an adb shell I can see CM10.1 and Gapps for 4.2.2 So I tried restarting recovery a couple times but I could never get the recovery to see the files. I figured I would just relock the bootloader, run RUU, then start the rooting/unlocking process fresh as I have done in the past when I got into trouble. Only problem now is that I get error 155 when trying to run the RUU utility, and can't boot into recovery since I re-locked my bootloader. I can still use fastboot but that's it, HALP!
What ruu are you using? Error 155 usually means its the wrong ruu.
iElvis said:
What ruu are you using? Error 155 usually means its the wrong ruu.
Click to expand...
Click to collapse
I tried this one. http://forum.xda-developers.com/showthread.php?t=1814217
SkuzeeII said:
I tried this one. http://forum.xda-developers.com/showthread.php?t=1814217
Click to expand...
Click to collapse
Do you have an AT&T phone? Or something else?
I was able to get the RUU to work last time, but when I try to unlock using the X_Factor root it doesn't actually unlock the bootloader. I've done this plenty of times before and followed the steps correctly. Any idea what's going on?
SkuzeeII said:
I was able to get the RUU to work last time, but when I try to unlock using the X_Factor root it doesn't actually unlock the bootloader. I've done this plenty of times before and followed the steps correctly. Any idea what's going on?
Click to expand...
Click to collapse
unlock yourself using "fastboot flash unlocktoken Unlock_code.bin"
Right, just push your unlock token again. Once you unlock the first time, subsequent unlocks are a simple fastboot command.
iElvis said:
Right, just push your unlock token again. Once you unlock the first time, subsequent unlocks are a simple fastboot command.
Click to expand...
Click to collapse
I've been at the same issue myself.
Have tried using the toolkit and pushing manually. I can get to the screen where you choose yes/no to unlock, which I choose yes. Then the phone just shuts off. When I turn it back on, the factory reset is done but I'm still stuck at "RELOCKED". I've probably tried this 20 times tonight and do not know what I'm missing. My CID is still all 1s.
FYI, using 2.20 RUU (had a similar issue... CM10 nightly bricked phone completely so used 2.20 RUU to restore phone)
i sometimes have alot of problems getting token to stick. try booting into bootloader without phone plugged up to computer, once booted into bootloader plug in phone, then push the token.
I've found that you need to unplug and reboot your phone before pushing the token. When I do this, it always takes the first time.
Sent from my HTC One X using Tapatalk 2
So I found that I was rebooting the phone myself when I shouldn't have during the unlock process. So I've got it unlocked now, and I can install recovery like TWRP or CWM but now I'm trying to get a ROM to load. I'm using the last Evita CM10 build but it always gets stuck on the booting screen. I think maybe I need an update.zip or need to use adb to get root from fastboot or recovery but I can't remember how and searching hasn't helped me yet...
I'm going to try to do a fastboot flash boot boot.img with the boot.img file from my CM10 zip file. Maybe that's what I was missing
I really should just be more patient before creating a thread. I got into CM10 then got S-OFF so now I'm on CM10.1
no access to recovery
I've got big problem. My One Mini is fine until I try to go into recovery. It refuses to go there.
I get fastboot and bootloader menus fine. It enters bootloader, but if I try to go into recovery, it just goes back to the main bootloader menu.
The problem started when I flashed CWMRecovery. Fastboot and adb recognise my phone, and accept commands, but when I try to fastboot flash recovery in it sends an error message. File not found.
I tried " fastboot boot recovery.img" but that just froze the machine .
When I try to get into recovery from rom manager or ROM toolbox pro, it takes me to the fastboot menu, not into recovery, and we're back to square one, as above.
Running android 4.3 Sense 5.5 software 2.12.401.1 Supercid 11111111
rooted and unlocked
To get the phone to work again, I have to hold power down for about 10 secs direct from fastboot/bootloader...may have to do this several times before it boots into Android.
If I turn power off from bootloader, it returns to bootloader when I power up again.
If I don't turn the phone off, once in main application, it's all OK.
Ho hum.
As I say , it works like a dream until I want to go into recovery.
Any ideas, please?
Thanks
Hi
Boblud said:
I tried " fastboot boot recovery.img" but that just froze the machine .
Click to expand...
Click to collapse
The correct command to flash the recovery is
Code:
fastboot flash recovery your_recovery_image.img
see also: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Booting into recovery should be possible with
Code:
adb reboot recovery
I didnt tried CWM on the Mini, but used it on my old Marvel. I'm satisfied with TWRP for the Mini.
greetings
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Boblud said:
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Click to expand...
Click to collapse
lock the bootloader RUU back to stock and start over ?
clsA said:
lock the bootloader RUU back to stock and start over ?
Click to expand...
Click to collapse
Thanks, will do when I can find ruu to download! Any pointers, please?
Uhm.... have u read Frequently Asked Questions by @KidCarter93 ?
KidCarter93 said:
[SIZE=+1]Q11: I have a custom recovery installed but I can't boot into it.[/SIZE]
Use the command - fastboot erase cache.
You should now be able to boot into recovery.
Click to expand...
Click to collapse
Maybe it helps.
Boblud said:
Thanks, will do when I can find ruu to download! Any pointers, please?
Click to expand...
Click to collapse
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
clsA said:
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
Click to expand...
Click to collapse
Thanks for help all round.
The RUU wouldn't run: it reported an unknown error, but having done so, it must have done something, as when I rebooted, I had access to recovery once again...briefly! Then it went again.
Anyway, I re locked / unlocked , locked a few times, and hey presto, it's sprung back into life!