So I have an AT&T HTC One M7 that is S-Off, unlocked, and rooted (used revone). Needless to say it cannot receive OTA updates, they fail with a red x and for some reason it constantly checks for updates and forces an install after 3 postpones. The phone is currently on 4.1.2 (1.26.502.10) and has HBOOT 1.44.
So I'm trying to update it by using an RUU (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), this seems to fail at "Waiting for bootloader".
Process:
Have phone booted normally
Plug phone into computer, verify connectivity with "adb devices"
Run RUU and get to the point where it reboots the phone to the silver logo and then it stays at "Waiting for bootloader" until I reset the phone
When it's on the silver logo I tested "fastboot devices" and it does display the phone as connected
Any ideas on how to proceed?
billy_rud10 said:
So I have an AT&T HTC One M7 that is S-Off, unlocked, and rooted (used revone). Needless to say it cannot receive OTA updates, they fail with a red x and for some reason it constantly checks for updates and forces an install after 3 postpones. The phone is currently on 4.1.2 (1.26.502.10) and has HBOOT 1.44.
So I'm trying to update it by using an RUU (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), this seems to fail at "Waiting for bootloader".
Process:
Have phone booted normally
Plug phone into computer, verify connectivity with "adb devices"
Run RUU and get to the point where it reboots the phone to the silver logo and then it stays at "Waiting for bootloader" until I reset the phone
When it's on the silver logo I tested "fastboot devices" and it does display the phone as connected
Any ideas on how to proceed?
Click to expand...
Click to collapse
You are probably using windows 8 which is, by default, not compatible with hboot 1.44 hence why the ruu is waiting for fastboot connection forever. Use a windows 7 computer. I know there is a way to fix this issue in windows 8 but I never tried it. I think clsA could help you with this.
i'm actually on Windows 7. I was able to fix this by running the RUU for 4.3 and then doing a "fastboot flash zip" for the rom.zip from 4.4
Related
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
budron said:
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
Click to expand...
Click to collapse
adb won't work when you are in bootloader (It won't work until Linux is up). "fastboot" will work over USB in bootloader->Fastboot.
I believe RUU will work on fastboot mode.
I'm trying to relock my bootloader and unroot because I cracked my screen and wish to use my insurance to get a new DNA. My computer recognizes my phone when the phone is on, but when i boot into bootloader, the computer does the two beeps like a connection has been found but then is followed by 3 low pitched beeps like it failed. I'm S-ON. I can't do any work on my phone when in bootloader. When I try to enter the command "fastboot oem lock," it just says <waiting for device> I've installed the latest version of HTC Sync Manager so i'm sure the drivers are up to date.
HosstaLaVista said:
I'm trying to relock my bootloader and unroot because I cracked my screen and wish to use my insurance to get a new DNA. My computer recognizes my phone when the phone is on, but when i boot into bootloader, the computer does the two beeps like a connection has been found but then is followed by 3 low pitched beeps like it failed. I'm S-ON. I can't do any work on my phone when in bootloader. When I try to enter the command "fastboot oem lock," it just says <waiting for device> I've installed the latest version of HTC Sync Manager so i'm sure the drivers are up to date.
Click to expand...
Click to collapse
Try a different usb port. Uninstall HTC Sync, as I have seen sync cause problems before. Also try using a different cable if you have one. I have an old T-Bolt cable that will let you charge and transfer, but will not recognize phone in bootloader.
when in bootloader make sure that you are in fastboot and it says "fastboot usb"
I've had this phone for about a good 4 months now, was getting bored so i decide to unlock the bootloader, root, and install a new rom. Then i heard youwer able to activate the HTC logo button to wake and sleep your device with using a different kernel. tbaldens kernel v3.6. I have TWRP recovery installed with trickdroid as my rom.After i ran threw all the procedures to flash in Aroma installer. My phone won't turn on, when i connect it to my computer it shows up as a MTP device. When I do get it to power on its stuck at the "quietly brilliant" screen. cant get into recovery to restore from back up. PLEASE HELP! SOLDIER DEPLOYED!!!!!!!! dont have the means of sending it in. Any suggestion. Mac is my primary means of rooting. windows 8 drivers are kinda funky:crying::crying::crying::crying::crying::crying::crying:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
crashfocus said:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
Click to expand...
Click to collapse
can i do this from a mac? and i can't get into fastboot because it wont go past the htc logo screen. it is identified as a MTP device in windows
Ahhhh thankfully i was able to get into my bootloader and flash my recovery! but thanks for the reply bro
Hey guys I need help. My HTC One is stuck in bootloader mode. I was trying to upgrade to the latest T-Mobile update. I tried downgrading with an RUU and I tired to flash stock recovery. I'm not all too sure what exactly happened, but I have no OS or recovery mode. All I have is bootloader mode. When I try to reboot to OS there is a bootloop. When I try to go into recovery a picture of a phone shows up with a red triangle and exclamation point. When I enter Fastboot in the bootloader it shows up on the phone as Fastboot USB. Although it says Fastboot USB, the phone is not recognized on the computer. When I try to enter fastboot commands, the prompt says "waiting for device" no matter what command I type.
If I could get the computer to recognize the phone, I could flash a recovery and a ROM or run an RUU. But that is only if I could get it to recognize the phone and I can't. I have searched for days and I can't find anything that works.
I have no OS, no recovery mode, and the bootloader isn't recognized on the computer. Please help! any help/advice will be greatly appriciated!
Please and thank you! :good:
amkivb said:
Hey guys I need help. My HTC One is stuck in bootloader mode. I was trying to upgrade to the latest T-Mobile update. I tried downgrading with an RUU and I tired to flash stock recovery. I'm not all too sure what exactly happened, but I have no OS or recovery mode. All I have is bootloader mode. When I try to reboot to OS there is a bootloop. When I try to go into recovery a picture of a phone shows up with a red triangle and exclamation point. When I enter Fastboot in the bootloader it shows up on the phone as Fastboot USB. Although it says Fastboot USB, the phone is not recognized on the computer. When I try to enter fastboot commands, the prompt says "waiting for device" no matter what command I type.
If I could get the computer to recognize the phone, I could flash a recovery and a ROM or run an RUU. But that is only if I could get it to recognize the phone and I can't. I have searched for days and I can't find anything that works.
I have no OS, no recovery mode, and the bootloader isn't recognized on the computer. Please help! any help/advice will be greatly appriciated!
Please and thank you! :good:
Click to expand...
Click to collapse
keep on rebooting until it's seen in the PC. Make sure the driver is installed (or forcible install it if it's an unknown device).
After that, once you're able to see it... re-flash the unlock token (fastboot flase unlocktoken unlock_code.bin). That will get you back into the ROM. At least, that's what did for me:
http://forum.xda-developers.com/showthread.php?t=2665481
But I can't reflash an older RUU at all, so I can't downgrade.
Drashna said:
keep on rebooting until it's seen in the PC. Make sure the driver is installed (or forcible install it if it's an unknown device).
After that, once you're able to see it... re-flash the unlock token (fastboot flase unlocktoken unlock_code.bin). That will get you back into the ROM. At least, that's what did for me:
http://forum.xda-developers.com/showthread.php?t=2665481
But I can't reflash an older RUU at all, so I can't downgrade.
Click to expand...
Click to collapse
I figured it out. All I needed was windows 7 instead of 8 for some reason. After I installed 7 I just ran the 4.3 RUU. Now I have a different problem. Originally this all happened because I was going to upgrade to the new 4.4.2. Now I can't flash stock recovery. I have cwm but I need stock recovery to upgrade to 4.4.2. Since there is no 4.4.2 RUU I don't know what to do now.
So, in an attempt to return my device back to stock using the firmware1 and firmware2 method with Fastboot own rebootRUU instead of the simple executable (stupid me, right?)
I had to downgrade my HBOOT from 1.54 to 1.33 to run the RUU. However, upon downgrading it, it said that I had to immediately flush the firmware to the phone for preupdating or whatever, but by that time the Fastboot connection broke for some reason and I wasn't able to type in anymore commands. So I had to restart my phone, and now I am unable to establish a Fastboot connection in bootloader anymore. For some reason the drivers work absolutely fine when booted into android. But when I'm in the bootloader, the My HTC driver loads with a Code 10 this device could not be started error, and using the RUU exe just gets stuck on the black HTC screen because it can't run any Fastboot commands.
XDA, wat do?
Thanks!
Anyone? =/