Database Develop

Please help, possible brick after following guide to flash firmware

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

[Q] Quick unroot question

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.

HTC One Stuck on Bootloader

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

Help Reverting back to stock/flashing RUU

Hello, I need some serious help here! So ive modded the hell out of my phone and now I need to go back to stock. I am trying Mike return to stock guide (which Ive used before successfully) but I keep getting error 155 over and over and phone gets stuck on grey HTC screen (no exclamation marks), I don't know if it has anything to do anything with my firmware having been updated via fastboot to get rid of the red warning. CID is stock, running latest att stock rooted, s-off unlocked bootloader and ive tried 2 different RUUs giving me the same issue
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
I will post my bootloader screen and if someone can help me out I appreciate it much!

DroidManIc said:
Hello, I need some serious help here! So ive modded the hell out of my phone and now I need to go back to stock. I am trying Mike return to stock guide (which Ive used before successfully) but I keep getting error 155 over and over and phone gets stuck on grey HTC screen (no exclamation marks), I don't know if it has anything to do anything with my firmware having been updated via fastboot to get rid of the red warning. CID is stock, running latest att stock rooted, s-off unlocked bootloader and ive tried 2 different RUUs giving me the same issue
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
I will post my bootloader screen and if someone can help me out I appreciate it much!
Click to expand...
Click to collapse
downgrade hboot to 1.44 and flash the 1.26.502.12 ruu.exe
or flash any x.xx.502.xx decrypted ruu.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip
fastboot reboot
do not use windows 8 if using a 1.xx.502.x ruu

alray said:
downgrade hboot to 1.44 and flash the 1.26.502.12 ruu.exe
or flash any x.xx.502.xx decrypted ruu.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip
fastboot reboot
do not use windows 8 if using a 1.xx.502.x ruu
Click to expand...
Click to collapse
Nice man thanks so much! Now to get it up to date? It's not showing me an OTA notifications even when I check do I have to flash updates incrementally?
Sent from my HTC One_M8 using XDA Free mobile app

Can't flash custom recovery on my S-OFF, locked, M7

hello guys. i've recently bought a M7_UL (i believe it's the unlocked, international version) that has S-OFF with locked bootloader. some people say you still can flash recovery since you're S-OFF, others, that even if when S-OFF, you still have to unlock bootloader in order to flash a recovery. well, i can't do none of these. everything is properly installed (device drivers, most recent Mini ADB and Fastboot and TWRP) but some commands such as "adb devices" (though changing "adb" to "fastboot" actually shows my device) and "fastboot flash recovery xxx.img", simply doesn't work. i've also tried the HTCdev method but "fastboot oem get_identifier_token" command gives me nothing. also tried this tutorial here --> https://forum.xda-developers.com/showthread.php?t=2470340 but the cmd doesn't even recognize this "echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 " line. what am i doing wrong?
i really didn't want to create this topic and did quite a research, but every tutorial i've found so far didn't work for me. heeelppp :crying:

manofawker said:
hello guys. i've recently bought a M7_UL (i believe it's the unlocked, international version) that has S-OFF with locked bootloader. some people say you still can flash recovery since you're S-OFF, others, that even if when S-OFF, you still have to unlock bootloader in order to flash a recovery. well, i can't do none of these. everything is properly installed (device drivers, most recent Mini ADB and Fastboot and TWRP) but some commands such as "adb devices" (though changing "adb" to "fastboot" actually shows my device) and "fastboot flash recovery xxx.img", simply doesn't work. i've also tried the HTCdev method but "fastboot oem get_identifier_token" command gives me nothing. also tried this tutorial here --> https://forum.xda-developers.com/showthread.php?t=2470340 but the cmd doesn't even recognize this "echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 " line. what am i doing wrong?
i really didn't want to create this topic and did quite a research, but every tutorial i've found so far didn't work for me. heeelppp :crying:
Click to expand...
Click to collapse
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver HTC logo
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
Code:
fastboot reboot-bootloader
I can make you a "firmware.zip" file if you're unsure how to do it. If you need it just reply what custom recovery version you need and post your "fastboot getvar all" output so I know your phone info (hide your imei)
Once the recovery is flashed, you can boot in recovery and unlock the bootloader using the tutorial you've linked. This method of unlocking the bootloader will not wipe your phone.

alray said:
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
Code:
fastboot oem rebootRUU
phone will reboot in ruu mode, a black screen with silver HTC logo
Code:
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
Code:
fastboot reboot-bootloader
I can make you a "firmware.zip" file if you're unsure how to do it. If you need it just reply what custom recovery version you need and post your "fastboot getvar all" output so I know your phone info (hide your imei)
Once the recovery is flashed, you can boot in recovery and unlock the bootloader using the tutorial you've linked. This method of unlocking the bootloader will not wipe your phone.
Click to expand...
Click to collapse
hi, alray, thanks for taking the time to answer me. i'd like you to make this firmware.zip for me but "fastboot getvar all" gives me this
Code:
C:\miniadb_m7>fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.005s
what's wrong?

manofawker said:
The first thing you need to know is that adb commands will only works when the phone is booted in a custom recovery or when booted in the rom (the "USB debugging" option must be turned on to use adb from the rom, not required when using from a custom recovery).
When the phone is booted in bootloader mode, only fastboot commands will work (and fastboot commands will not works when in recovery or when in the rom).
If your phone is S-OFF you can definitively flash a recovery even if the bootloader is locked. But the method used to flash it is different then the usual method (the "fastboot flash recovery name_of_recovery.img" command will only work with an unlocked bootloader). You'll need to zip the custom recovery .img file with an android-info.txt file matching your phone info and flash that zip file from RUU mode.
i.e:
phone will reboot in ruu mode, a black screen with silver HTC logo
where "firmware.zip" is the file containing your recovery .img file and the android-info.txt file
hi, alray, thanks for taking the time to answer me. i'd like you to make this firmware.zip for me but "fastboot getvar all" gives me this
what's wrong?
Click to expand...
Click to collapse
Are there only one android device connected to your computer ("fastboot devices" listing only your phone?)

alray said:
Are there only one android device connected to your computer ("fastboot devices" listing only your phone?)
Click to expand...
Click to collapse
yes, just the one i'm trying to flash recovery

manofawker said:
yes, just the one i'm trying to flash recovery
Click to expand...
Click to collapse
what about:
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg
Tried on another computer?

alray said:
what about:
Code:
fastboot oem dmesg
and
Code:
fastboot oem last_dmesg
Tried on another computer?
Click to expand...
Click to collapse
none of these worked. strangely enough, commands like "fastboot reboot" and "fastboot devices" actually do something... i've tried to execute the cmd in compatibility mode, but it was in vain. tomorrow i'm gonna try all of this on my friend's PC and let you know if i have any success.