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
Related
Hello guys,
I have S-OFF, supercid, relocked bootloader phone
First I installed Firmware package from 2.17.401.1 RUU sucressfully my terminal quoted and then after reboot My phone was not reacting to any tipping on the screen. I only reached the screen where it demands the pin to type in.
So I flashed it again with firmware.zip from 1.29.401.12. Flash sucessfully (terminal quoted) and now it rebooted to the htc one logo and nothing else happens. I even cannot turn it off. Please help.
Update: I managed to reboot it but it is not reacting when i want to put in my PIN
Put the device under direct light (perhaps like a bulb) and press the power and volume down buttons together until the device reboots. While it is under direct light, do not cover the light sensors (on the left of the upper speaker grill) with your hand.
TarekElsakka said:
Put the device under direct light (perhaps like a bulb) and press the power and volume down buttons together until the device reboots. While it is under direct light, do not cover the light sensors (on the left of the upper speaker grill) with your hand.
Click to expand...
Click to collapse
ok i now restarted it but the touchscreen does not react when it asks me to put in the PIN
Reflash ROM..
Sent from my HTC One
Sindroid said:
Reflash ROM..
Sent from my HTC One
Click to expand...
Click to collapse
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Exxorzist said:
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Click to expand...
Click to collapse
I've had the same issue. Which rom do you use? CM wasn't working for me, so I had to flash Sense rom like ARHD 11 or Trickdroid 7.5
I also flashed the older firmware.zip and still no touch responsiveness. You will also have to flash a newer cwm touch recovery if you are using it, helps navigating through aroma http://goo.im/devs/Flyhalf205/M7/Recovery/recovery-clockwork-touch-6.0.3.2-m7.img
Exxorzist said:
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Click to expand...
Click to collapse
You need to flash this firmware: http://www.androidrevolution.nl/downloader/download.php?file=2.17.401.1-custom.zip again, and then flash the custom recovery stated above this post. Next, flash the latest Android Revolution which is on the newest base which other roms don't have yet. This should fix your issue. CM roms cannot be used by your device in its current state, as the touch drivers aren't compatible. You must use a Sense rom
MacHackz said:
You need to flash this firmware: http://www.androidrevolution.nl/downloader/download.php?file=2.17.401.1-custom.zip again, and then flash the custom recovery stated above this post. Next, flash the latest Android Revolution which is on the newest base which other roms don't have yet. This should fix your issue. CM roms cannot be used by your device in its current state, as the touch drivers aren't compatible. You must use a Sense rom
Click to expand...
Click to collapse
I flashed the firmware again sucessfully to 2.17.401.1
Since 2 days my Bootloader is relocked again but I am S-OFF. When I want to flash custom recovery I do have to unlock it again? How do I do that because I am still not able to use touchscreen and type in PIN?
George_Mn said:
I've had the same issue. Which rom do you use? CM wasn't working for me, so I had to flash Sense rom like ARHD 11 or Trickdroid 7.5
I also flashed the older firmware.zip and still no touch responsiveness. You will also have to flash a newer cwm touch recovery if you are using it, helps navigating through aroma http://goo.im/devs/Flyhalf205/M7/Recovery/recovery-clockwork-touch-6.0.3.2-m7.img
Click to expand...
Click to collapse
Exxorzist said:
I flashed the firmware again sucessfully to 2.17.401.1
Since 2 days my Bootloader is relocked again but I am S-OFF. When I want to flash custom recovery I do have to unlock it again? How do I do that because I am still not able to use touchscreen and type in PIN?
Click to expand...
Click to collapse
type fastboot oem flash unlocktoken unlock_code.bin
MacHackz said:
type fastboot oem flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Thanks. I unlocked it and flashed the custom recovery
./fastboot-mac flash recovery recovery.img
sending 'recovery' (7422 KB)... OKAY
writing 'recovery'... OKAY
Then i rebootet it and touchscreen is still not reacting. Shall I now flash the revolution hd rom?
Exxorzist said:
Thanks. I unlocked it and flashed the custom recovery
./fastboot-mac flash recovery recovery.img
sending 'recovery' (7422 KB)... OKAY
writing 'recovery'... OKAY
Then i rebootet it and touchscreen is still not reacting. Shall I now flash the revolution hd rom?
Click to expand...
Click to collapse
Does touchscreen work in recovery mode?
What ROM do you currently have?
MacHackz said:
Does touchscreen work in recovery mode?
What ROM do you currently have?
Click to expand...
Click to collapse
Yes touchscreen works in recovery. I am at the moment not using any rom. I have bought a branded phone and all I did was giving it S-OFF, unlock bootloader, supercid, root.
And now after I flashed firmware 2.17, i simply want to put a rom on it like Revolution HD 11
Exxorzist said:
Yes touchscreen works in recovery. I am at the moment not using any rom. I have bought a branded phone and all I did was giving it S-OFF, unlock bootloader, supercid, root.
And now after I flashed firmware 2.17, i simply want to put a rom on it like Revolution HD 11
Click to expand...
Click to collapse
Flash Android Revolution 11 and it should work! :fingers-crossed:
MacHackz said:
Flash Android Revolution 11 and it should work! :fingers-crossed:
Click to expand...
Click to collapse
Stupid question. How do I get the zip file onto my Phone? Because I cannot type in my pin and then connect it as usual and pulling it via Android File Transfer over to my phone.
Exxorzist said:
Stupid question. How do I get the zip file onto my Phone? Because I cannot type in my pin and then connect it as usual and pulling it via Android File Transfer over to my phone.
Click to expand...
Click to collapse
Check my ADB push guide in my sig, jump to step 3
No need to relock bootloader when S-Off. If you upgrade firmware. If you upgrading to 2.17 f/w u need to flash new recovery as well.
Use sideload in recovery to reflash ROM.
Sent from my HTC One
MacHackz said:
Check my ADB push guide in my sig, jump to step 3
Click to expand...
Click to collapse
You are my hero!!!!!
Everything works great. Is there also the camera update included that was released by HTC in 1.29 because before I had 1.28.
Exxorzist said:
You are my hero!!!!!
Everything works great. Is there also the camera update included that was released by HTC in 1.29 because before I had 1.28.
Click to expand...
Click to collapse
It's all included You can also check the modded camera apk in my signature which allows you to take photos and focus using your volume buttons
Glad it worked
Thank you so much for this tip I thought I was SOL when it went into the WSOD and I couldn't turn it off.
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
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?
bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."
I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?
If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."
OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.
SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!
SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!
Thanks for posting back. Edit your title to [SOLVED]! and enjoy!
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
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
OfficialLocdoGg said:
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
Click to expand...
Click to collapse
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
alray said:
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse
OfficialLocdoGg said:
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
Click to expand...
Click to collapse
its fine to flash a ruu with phone booted in bootloader btw.
alray said:
its fine to flash a ruu with phone booted in bootloader btw.
Click to expand...
Click to collapse
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
OfficialLocdoGg said:
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
Click to expand...
Click to collapse
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Boot into bootloader/FASTBOOT USB
Type:
Code:
[B][I]fastboot oem lock[/I][/B]
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
majmoz said:
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
Click to expand...
Click to collapse
Thanks. This restored the phone to a usable state. I'm going to try firewater now.