hi all.
need help.
i wanted to revert back to stock.
followed htc1guru tutorial.
downloaded ruu.exe.
i downgraded to hboot 1.44 write my cid back to htc__044 and on s-off
but after executing .exe im getting error 155.
googled it most of the people posted because they having hboot 1.55, so couldnt find any solution for my case.
any help? thanks a lot.
good day
shdin271 said:
hi all.
need help.
i wanted to revert back to stock.
followed htc1guru tutorial.
downloaded ruu.exe.
i downgraded to hboot 1.44 write my cid back to htc__044 and on s-off
but after executing .exe im getting error 155.
googled it most of the people posted because they having hboot 1.55, so couldnt find any solution for my case.
any help? thanks a lot.
good day
Click to expand...
Click to collapse
try this method
This is the instructions posted by Scotty85
I'm just re-posting it for you
Quote:
http://androidforums.com/t-one-all-t...ml#post5864243
Quote:
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,your done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Quote:
here are some directions to flash "rom.zip"
if you're working with a booted,operational phone,you can flash the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboot oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. don't interrupt it while the cmd window shows its writing's,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you don't have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
clsA said:
try this method
Click to expand...
Click to collapse
thanks for the reply. i think i missed something in bootloader status (relocked locked)
according to this tutorial http://forum.xda-developers.com/showthread.php?t=2541082, my bootloader should be locked not relocked. i tried it with relocked.
havent tried it yet, but ill hold on for a few days testing my new radio. if the problem persists, ill use this method. again thanks bro.
shdin271 said:
thanks for the reply. i think i missed something in bootloader status (relocked locked)
according to this tutorial http://forum.xda-developers.com/showthread.php?t=2541082, my bootloader should be locked not relocked. i tried it with relocked.
havent tried it yet, but ill hold on for a few days testing my new radio. if the problem persists, ill use this method. again thanks bro.
Click to expand...
Click to collapse
locked and relocked are the same thing
Related
Im really struggling to carry out an unroot on both my HTC one and S3. I want to sell the devices but need to return them to standard rom.
I have looked and read so many differnt threads that I'm totally confused about which method to use and which files to use.
My HTC is rooted with a TEAM recovery, I've looked at the bootloader and it tells me its s-on. All I want to do is return to stock O/S so the phone can update to the latests release. I don't need any of the settings keeping, infact it's best for it to be completely clean.
Is there an easy to follow guide I can use that points me to all the files I need etc?
If anyone can help me out I would very much appreciate it.
thanks all.
uktivo said:
Im really struggling to carry out an unroot on both my HTC one and S3. I want to sell the devices but need to return them to standard rom.
I have looked and read so many differnt threads that I'm totally confused about which method to use and which files to use.
My HTC is rooted with a TEAM recovery, I've looked at the bootloader and it tells me its s-on. All I want to do is return to stock O/S so the phone can update to the latests release. I don't need any of the settings keeping, infact it's best for it to be completely clean.
Is there an easy to follow guide I can use that points me to all the files I need etc?
If anyone can help me out I would very much appreciate it.
thanks all.
Click to expand...
Click to collapse
Did you read this http://forum.xda-developers.com/showthread.php?t=2358738 this is the guide you are looking for.... and this is the 2nd sticky on this forum....
and btw you should ask your question in the q&a, help and troubleshooting forum next time, not in general forum
Apologies for the wrong position of posting.. I have read this sticky but there are lots of conflicting information in there. Perhaps my geekness is just not what it supposed to be.
Sent from my Z30 using Tapatalk
Sorry hit enter to quickly.
I think in general I'm unsure of some of the terminology used. It also mentions about certain firmware not having touch panel working after unroot etc. So as a non geek type, it does sort of scare you into not doing anything at all. I've looked on YouTube and there are loads of video tutorials but again, most of the links to the correct ruu are broken or old.
Hence my question. Is there an updated thread giving noob step by step instructions.. hope that makes sense?
Sent from my Z30 using Tapatalk
Reboot your phone in bootloader, Select fasboot, then connect phone to pc via usb. Go to your fastboot/adb folder of your computer and start a cmd prompt from there. Type "fastboot getvar all" copy paste info here. Dont paste imei and s/n.
Sent from my HTC One using xda app-developers app
alray said:
Reboot your phone in bootloader, Select fasboot, then connect phone to pc via usb. Go to your fastboot/adb folder of your computer and start a cmd prompt from there. Type "fastboot getvar all" copy paste info here. Dont paste imei and s/n.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That alone had helped. I completely forgot you need to start the command prompt from the adb folder. I've been trying to navigate to it with little success
Sent from my Z30 using Tapatalk
alray said:
Reboot your phone in bootloader, Select fasboot, then connect phone to pc via usb. Go to your fastboot/adb folder of your computer and start a cmd prompt from there. Type "fastboot getvar all" copy paste info here. Dont paste imei and s/n.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for your support so far. Please see attached. If you could point me in the right direction please that would be greatly appreciated.
UPDATE.
I've gained s-off using revone system and I believe I've found the right RUU for my firmware 1.28.401.7 which is this one:
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
How do i know flash this ruu.zip file to the phone? I've tried the steps in the mentioned thread above but keep getting errors.
uktivo said:
Thanks for your support so far. Please see attached. If you could point me in the right direction please that would be greatly appreciated.
UPDATE.
I've gained s-off using revone system and I believe I've found the right RUU for my firmware 1.28.401.7 which is this one:
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
How do i know flash this ruu.zip file to the phone? I've tried the steps in the mentioned thread above but keep getting errors.
Click to expand...
Click to collapse
Now that you are s-off:
1 -I would recommend you tu use the .EXE RUU and not the .ZIP RUU. Will be much easier for you :
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/ just place the .exe on your desktop
2- put your phone back in fastboot mode (reboot using power and vol -, select fastboot, connect to usb computer)
3- open a cmd prompt from your adb/fastboot folder
4- change your cid to supercid by pushing this command:
Code:
fastboot oem writecid 11111111
5- check that your cid changed properly:
Code:
fastboot oem readcid
it should reply something like this:
Code:
(bootloader) cid: 11111111
OKAY [ 0.010s]
finished. total time: 0.011s
6- keep phone connected to pc and reboot it, check you have a good battery charge. launch the ruu.exe and follow instruction from the utility.
7- now your phone is back to stock, you are not rooted anymore and your bootloader is locked. you need the change back your cid to HTC__001 if you want to receive OTA updates.
-put your phone back in fastboot mode (reboot using power + vol -, select fastboot, connect to usb computer)
-open a cmd prompt from your adb/fastboot folder
-
Code:
fastboot oem writecid HTC__001
-check that your cid changed properly:
Code:
fastboot oem readcid
it should reply something like this:
Code:
(bootloader) cid: HTC__001
OKAY [ 0.010s]
finished. total time: 0.011s
8- boot your phone normally, go trough the setup procedure, then download and install all ota updates.
9- factory reset your phone
10- you are rdy to sell it, its now 100% stock, updated and s-off (dont go back to s-on!)
alray said:
Now that you are s-off:
1 -I would recommend you tu use the .EXE RUU and not the .ZIP RUU. Will be much easier for you :
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/ just place the .exe on your desktop
2- put your phone back in fastboot mode (reboot using power and vol -, select fastboot, connect to usb computer)
3- open a cmd prompt from your adb/fastboot folder
4- change your cid to supercid by pushing this command:
Code:
fastboot oem writecid 11111111
5- check that your cid changed properly:
Code:
fastboot oem readcid
it should reply something like this:
Code:
(bootloader) cid: 11111111
OKAY [ 0.010s]
finished. total time: 0.011s
6- keep phone connected to pc and reboot it, check you have a good battery charge. launch the ruu.exe and follow instruction from the utility.
7- now your phone is back to stock, you are not rooted anymore and your bootloader is locked. you need the change back your cid to HTC__001 if you want to receive OTA updates.
-put your phone back in fastboot mode (reboot using power + vol -, select fastboot, connect to usb computer)
-open a cmd prompt from your adb/fastboot folder
-
Code:
fastboot oem writecid HTC__001
-check that your cid changed properly:
Code:
fastboot oem readcid
it should reply something like this:
Code:
(bootloader) cid: HTC__001
OKAY [ 0.010s]
finished. total time: 0.011s
8- boot your phone normally, go trough the setup procedure, then download and install all ota updates.
9- factory reset your phone
10- you are rdy to sell it, its now 100% stock, updated and s-off (dont go back to s-on!)
Click to expand...
Click to collapse
Could not have done this with out your help.. VERY MUCH appreciated.
uktivo said:
Could not have done this with out your help.. VERY MUCH appreciated.
Click to expand...
Click to collapse
No problem, i'm just doing what somebody else here on xda did for me a couple weeks ago.
alray said:
No problem, i'm just doing what somebody else here on xda did for me a couple weeks ago.
Click to expand...
Click to collapse
Only me again. lol.
I'm all updated now thanks. BUT. I noticed my recovery has now gone. I used to use team recovery but I'm happy to install any (easiest). Don't suppose you know how to do this please?
thanks again.
uktivo said:
I noticed my recovery has now gone. I used to use team recovery but I'm happy to install any (easiest).
Click to expand...
Click to collapse
Your recovery isnt gone, The ruu process replaced your custom twrp recovery with the stock recovery of htc. If you want to re-install twrp recovery you have to re-unlock your bootloader trough htcdev.com and then download the twrp.zip and flash it to the recovery partition of your phone.
uktivo said:
All I want to do is return to stock O/S so the phone can update to the latests release. I don't need any of the settings keeping, infact it's best for it to be completely clean.
Click to expand...
Click to collapse
With a custom recovery (like twrp), you will NOT be stock and you will NOT receive future OTA updates. (you will see them but you won't be able to install them because you need stock recovery to install ota)
if you still want to install twrp for some reasons follow those steps:
1- re-unlock your bootloader trough HTCdev.com
refer to this xda video tutorial : http://www.youtube.com/watch?v=xuIq0gmYpFA
2- download lastest version of twrp (openrecovery-twrp-2.6.3.0-m7.img) recovery: http://goo.im/devs/OpenRecovery/m7/
3- place the .img file inside your adb/fastboot folder of your computer
4- reboot phone in bootloader, then select fastboot and connect usb cable
5- open cmd prompt from you fastboot folder
6- type this command to flash twrp:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
7- type this command to reboot into bootloader:
Code:
fastboot reboot bootloader
8- now you can enter the custom recovery
alray said:
Your recovery isnt gone, The ruu process replaced your custom twrp recovery with the stock recovery of htc. If you want to re-install twrp recovery you have to re-unlock your bootloader trough htcdev.com and then download the twrp.zip and flash it to the recovery partition of your phone.
With a custom recovery (like twrp), you will NOT be stock and you will NOT receive future OTA updates. (you will see them but you won't be able to install them because you need stock recovery to install ota)
if you still want to install twrp for some reasons follow those steps:
1- re-unlock your bootloader trough HTCdev.com
refer to this xda video tutorial : http://www.youtube.com/watch?v=xuIq0gmYpFA
2- download lastest version of twrp (openrecovery-twrp-2.6.3.0-m7.img) recovery: http://goo.im/devs/OpenRecovery/m7/
3- place the .img file inside your adb/fastboot folder of your computer
4- reboot phone in bootloader, then select fastboot and connect usb cable
5- open cmd prompt from you fastboot folder
6- type this command to flash twrp:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
7- type this command to reboot into bootloader:
Code:
fastboot reboot bootloader
8- now you can enter the custom recovery
Click to expand...
Click to collapse
Sorry for my delayed thanks but I've been away on business for the last few days and not had chance to catch up on this thread. Thanks again.
Sent from my Z30 using Tapatalk
I was following Vomer's guide on my One, which has been working great. I had HBOOT 1.54, S-Off, SuperCID, and pushed the firmware twice, got the success message, and waited and when it says finished used adb to tell it to reboot. Now I get the splash, with the lock gone, as expected, and then the screen goes black. If I hold power, or power and down, the hardware keys start blinking and then nothing. A few seconds later I get the splash again, then blank again.
It appears to be communicating briefly over USB because my laptop starts trying to install a HTC MTP device (drive is already on the PC and has been fine) before it looses comms and drops out. I can't seem to get adb device to recognize it....
PLEASE tell me someone can help me recover my phone!!! I will be immensely grateful.
And what the HBOOT version you wanted to downgrade to?
Ivanovic said:
And what the HBOOT version you wanted to downgrade to?
Click to expand...
Click to collapse
I wasn't trying to downgrade HBOOT, just rather ensure my firmware was up to date. I'd had mine set up as a GPE and was flashing the DE (after supercid).
By way of an update, I've been able to get into bootloader and I'm a bit scared on what to do next so I dont screw this up. I notice that I still have S-OFF, but HBOOT is now showing 1.56 and it says RELOCKED at the top. My plan was to use rumrunner (just because of the HBOOT, but it is erroring anyway) to unlock bootloader, and then to look up the fastboot commands to push a ROM and recovery. Any advice?
Downgrade to 1.44 and change cid according to the Rom you want. Then unlock or set your bootloader to LOCKED
Here is the file for 1.44 http://www69.zippyshare.com/v/95229262/file.html
Sent from my HTC One using Tapatalk
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
vettejock99 said:
Can you help me with the adb commands to flash that boot zip? Also, should I run " fastboot flash unlocktoken Unlock_code.bin" to unlock my bootloader first?
Click to expand...
Click to collapse
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Ivanovic said:
You can unlock if you want to flash custom recovery.
Place the file i gave you to the fastboot folder. Boot into bootloader and choose FASTBOOT.
Run the following : fastboot oem rebootRUU
fastboot flash zip filename.zip *where filaname the actual filename of the file i gave you
You will get FAILED or sth so do this command again to succesfully flash the firmware.
Click to expand...
Click to collapse
Awesome. So I've got HBOOT 1.44, S-OFF, bootloader unlocked, supercid, and TWRP 2.6.3.3 flashed again, and I tried sideloading ARHD rom. It all looked good but same thing for the moment, I get the splash and then black......I can't figure out why I can't boot into a rom right now. About to try flashing ROM again.
Okay, so didnt' work. After sideload flashing gets to 100% it just does nothing. Manually rebooting gets me back into the splash then blackness bootloop......
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
The former didn't get me anywhere, but I did follow your thinking and decided to use the RUU and start over. I'm happy to report that got me going, and then I was able to get AR HD on. I probably had to do that all along once I wiped the ROM and recovery, as sideloading clearly wasn't going to work (in retrospect) as it has an AROMA installer.
Thanks so much everyone!!
SaHiLzZ said:
Can you issue fastboot clear cache in bootloader and see the outcome?
Also as you are Soff, you can run dev ruu
Click to expand...
Click to collapse
Nice that everything is solved now.
Verstuurd van mijn HTC One
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
You've had an htc one for two years?
BableMan said:
You've had an htc one for two years?
Click to expand...
Click to collapse
No. Started out with my Nexus S, then moved to a Nexus 4, then gave that to my wife and got an HTC One. I love this phone so much I wish I'd had it for two years already, but no.
Do you have any idea of a new path I can try?
misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Sent from my HTC One using Tapatalk
Delgra said:
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Click to expand...
Click to collapse
I have tried both actually. I used Hansoon2000's (I'm at work so hopefully I'm referencing that correctly) all in one toolkit to try to flash the RUU.zip file back to the device. It fails while transferring to the device every single time.
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
How do I flash the RUU.zip from the command line? I have tried using "Install zip from sideload" but I get a Status Error 7 when trying to flash ROM.zip files, and I have tried using ADB PUSH to push the ROM.zip over to the phone but since there's no file structure it doesn't really ever end up anywhere on the phone. (I'm using ROM.zip generically here for my CM ROMs, not RUU) Is there a command line or ADB function to flash the RUU.zip file that I'm not aware of?
Thanks,
Chris
misterasset said:
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
Thanks,
Chris
Click to expand...
Click to collapse
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
nkk71 said:
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
Click to expand...
Click to collapse
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
misterasset said:
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
Click to expand...
Click to collapse
Please:
1- date of bootloader
2- a "fastboot getvar all" (remove IMEI and s/n)
3- link to the RUU you are trying to use.
Don't forget pressing the little thanks button for people who have helped
No offense but it sounds as if you simply aren't running an ruu.zip correctly. I'm not understanding all this hensonn2000 or toolkit talk that you have going on. You flash ruu.zip while the phone is in fastboot oem RUU mode. Not that complicated. Also the error 155 was the bootloader being unlocked if I recall correctly. You have to relock it before flashing or running the appropriate RUU. Specially if youre s-on.
Thanks guys. I ended up getting it all working. I did not have the Bootloader relocked and that was why the RUU kept failing.
Thanks again for the extra direction,
Chris
I want to return to stock so I can take an OTA. I am currently running Sprint 4.3, rooted, unlocked bootloader, S-ON, software version 3.04.651.2.
I have been reading up on the proper way to return to stock and just want to double check that I have the right information before i break something.
1. Download 3.04.651.2 RUU (or do I want 4.06.651.4 or 4.06.651.2?)
2. USB debugging turned on
3. nandriod
4. go into fastboot
5. Connect phone to computer and go to Andriod SDK folder platform-tools and open a command window
6. type fastboot oem lock in the command window
7. go back to fastboot and run the RUU (how exactly do I run the RUU?)
8. Am I done now? Will these steps give me the stock rom, locked bootloader and stock recovery?
is this how I flash the RUU from the command window?
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (if filename = firmware.zip)
Fastboot reboot
Thanks for the clarification.
Kev1jm2 said:
I want to return to stock so I can take an OTA. I am currently running Sprint 4.3, rooted, unlocked bootloader, S-ON, software version 3.04.651.2.
I have been reading up on the proper way to return to stock and just want to double check that I have the right information before i break something.
1. Download 3.04.651.2 RUU (or do I want 4.06.651.4 or 4.06.651.2?)
2. USB debugging turned on
3. nandriod
4. go into fastboot
5. Connect phone to computer and go to Andriod SDK folder platform-tools and open a command window
6. type fastboot oem lock in the command window
7. go back to fastboot and run the RUU (how exactly do I run the RUU?)
8. Am I done now? Will these steps give me the stock rom, locked bootloader and stock recovery?
is this how I flash the RUU from the command window?
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (if filename = firmware.zip)
Fastboot reboot
Thanks for the clarification.
Click to expand...
Click to collapse
If you have a (S-ON) device you can go to OMJ's thread and run the RUU.exe for instructions:
http://forum.xda-developers.com/showthread.php?t=2658910
read the instructions under the image on the page...
If you want to flash the modified firmware you need (S-OFF), then you would follow these instructions:
I downloaded 4.06.651.4..
then renamed 4.06.651.4.zip to "firmware.zip"..
then moved firmware.zip to 'where-ever fastboot & adb are installed'..
then open command prompt in that folder..
then rebooted to bootloader..
plug phone through USB port, phone should say FASTBOOT USB
cmd: "fastboot oem rebootRUU" (without quotes of course)
cmd: "fastboot flash zip firmware.zip"
cmd: "fastboot reboot" (to reboot)
Hope this helps!
predator1584 said:
If you have a (S-ON) device you can go to OMJ's thread and run the RUU.exe for instructions:
http://forum.xda-developers.com/showthread.php?t=2658910
read the instructions under the image on the page...
If you want to flash the modified firmware you need (S-OFF), then you would follow these instructions:
I downloaded 4.06.651.4..
then renamed 4.06.651.4.zip to "firmware.zip"..
then moved firmware.zip to 'where-ever fastboot & adb are installed'..
then open command prompt in that folder..
then rebooted to bootloader..
plug phone through USB port, phone should say FASTBOOT USB
cmd: "fastboot oem rebootRUU" (without quotes of course)
cmd: "fastboot flash zip firmware.zip"
cmd: "fastboot reboot" (to reboot)
Hope this helps!
Click to expand...
Click to collapse
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Kev1jm2 said:
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Click to expand...
Click to collapse
The 4.06.651.4 RUU is the same as taking the OTA but...it will wipe your device
I would suggest getting s-off before you go any further it will save you headaches down the road.
Kev1jm2 said:
The OMJ thread says its for 4.06.651.4. I have 3.04.651.2. Is that a problem or can I still use it?
Click to expand...
Click to collapse
no luck with the s-off way. got a file size error in cmd. trying the s-on version now.
Nope, got another error. Something about using an incorrect ruu. Bootloader is locked now though...And now its unlocked again. going to try OMJ's tool with the 3.04.651.2 ruu
OMJ's tool worked when my software version matched the tool's version. getting the OTA now. Apparently you cant jump software versions.
Thanks for your help.
Kev1jm2 said:
no luck with the s-off way. got a file size error in cmd. trying the s-on version now.
Nope, got another error. Something about using an incorrect ruu. Bootloader is locked now though...And now its unlocked again. going to try OMJ's tool with the 3.04.651.2 ruu
OMJ's tool worked when my software version matched the tool's version. getting the OTA now. Apparently you cant jump software versions.
Thanks for your help.
Click to expand...
Click to collapse
I did not have to relock my phone to RUU it for a repair at HTC. If you run into trouble just reapply your token.bin file to re unlock dev mode and try again. I agree though S-OFF is the way to go if you can sort it out.
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
return to stock rom
Chaos Water2 said:
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
Click to expand...
Click to collapse
Restart from scratch find the ruu.exe for your phone make sure it has the right specs of your phone (android,sense,and service provider) once found follow these instructions
1.) Go to Fastboot
2.) Run the commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
3.) Run the RUU
The first command locks your bootloader (allowing RUU), the third command allows the RUU to run on your phone without having to actually boot all the way (normally it just boots into this screen for you).
This will put you back to ur stock Rom when rooting again make sure to make backups of everything or you will have same problem again
Make sure you have all the updated drivers for your computer
Chaos Water2 said:
I've accidentally erased everything on my HTC One, including the ROM I had on there and the ROM install file. I am now stuck in the Bootloader screen and only options I have are to enter TWRP v2.6.3.3. Is there a way that I can flash a ROM via USB in the Bootloader? I've tried resetting my phone and it comes up with the HTC logo on the white screen and won't boot.
Click to expand...
Click to collapse
adb works in custom recovery, you can push, sideload, or OTG a ROM to your phone,
check the Frequently Asked Question sticky page 3
smokeytime420 said:
Restart from scratch find the ruu.exe for your phone make sure it has the right specs of your phone (android,sense,and service provider) once found follow these instructions
1.) Go to Fastboot
2.) Run the commands
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
3.) Run the RUU
The first command locks your bootloader (allowing RUU), the third command allows the RUU to run on your phone without having to actually boot all the way (normally it just boots into this screen for you).
This will put you back to ur stock Rom when rooting again make sure to make backups of everything or you will have same problem again
Make sure you have all the updated drivers for your computer
Click to expand...
Click to collapse
A RUU.exe file only requires the bootloader locked if S-ON. When the bootloader is locked, the RUU is executed with a double click in Windows. There is no need to do the other steps in 2, they are only needed if the RUU is a zip file. Here are the steps for flashing RUU.zip:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
that is true
majmoz said:
A RUU.exe file only requires the bootloader locked if S-ON. When the bootloader is locked, the RUU is executed with a double click in Windows. There is no need to do the other steps in 2, they are only needed if the RUU is a zip file. Here are the steps for flashing RUU.zip:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
Click to expand...
Click to collapse
That is true method is similar but this is how I got my phone to return to stock be for I could go anywhere else I tryed reflashing a recovery it didn't take I even tryed flashing the ruu.zip through fastboot it always failed on me since I couldn't go any further than that I searched other methods of flashing ruu that's what I came across and it worked for me also if you have s-off this usually turns it back on it did for me on step 2 not all of those steps are needed but the last one is what gets the phone ready to receive the info from the ruu.exe being run on a computer