Hello --
My US T-Mobile HTC One received the Kit-Kat update today (first day of upgrade). It is stuck on the white "HTC One" screen and cannot go past it. Phone is (was?) stock T-Mob Android rooted. I went back to the stock recovery to ensure the update happened properly. That whole process of rooting, using custom recovery, etc went pretty smoothly. Now it is just stuck on that boot screen. T-Mobile logo appears very briefly looks corrupt/scrambled. I can issue ADB commands so I know it is talking to the device, however the device says "offline" and I cannot get it go "online". I tried other USB cables, kill-server, start-server and nothing is bringing it back online. Screen has now been on over an hour (I cannot get it to turn off completely in the boot screen). I figured being it is talking still to the device (although offline) maybe all is not lost.Anyone with any advice on how to get this up and running before I have to return this to T-Mobile and pay hefty probably for this.
If anyone can help, maybe the below will be helpful:
M7_VL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-3.24.531.3
eMMC-boot 2048MB
Oct 4 2013, 17:31:32.0
I upgraded ADB, and now instead of OFFLINE it says UNAUTHORIZED (although I have used ADB before on this same computer/device and it was fine -- consistently have used other ROMs before, etc)
LAChris67 said:
If anyone can help, maybe the below will be helpful:
M7_VL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-3.24.531.3
eMMC-boot 2048MB
Oct 4 2013, 17:31:32.0
I upgraded ADB, and now instead of OFFLINE it says UNAUTHORIZED (although I have used ADB before on this same computer/device and it was fine -- consistently have used other ROMs before, etc)
Click to expand...
Click to collapse
Did you figure out how to solve the problem?
Can you get into the bootloader and wipe the device?
adzenith said:
Did you figure out how to solve the problem?
Click to expand...
Click to collapse
I used Guru Reset from http://www.htc1guru.com/downloads/stock-rom-downloads/, then used a USB OTG cable and a mouse to get the first update, then got the second update, then reflashed TWRP, then rooted.
If I did it again I think I'd go the RUU route to save me from having to use the mouse and do two updates.
adzenith said:
Did you figure out how to solve the problem?
Click to expand...
Click to collapse
Thanks for asking. After a couple of hours of panic and then reading on here, (if I remember correctly) I kept powering it until it gave me the option to fastboot (vol-down, power -- but I had to keep trying it because it would not take or boot properly consistently). I was able to flash RUU onto it, somehow lost all the data on the memory card (maybe this is normal?) and then was able to take the update. Not sure what happened there, but once I did the RUU, it was able to take the boot and update and re-boot itself to complete the install. For me, it seems like something was wrong with recovery. I flashed the stock one, but perhaps I loaded the wrong one (although I had been booting/rooted practically since I had the device a year ago).
Hello,
I had installed viper one 5.8.0 and everything was working fine. I tried to install viperdark theme 6.1.1 and it just sat at the HTC One screen and always came up with a dialer error. Then I tried to update to viperone 6.1.0 thinking it might just need the latest rom version. Same results. After going back and forth trying to do reinstalls of updates I am now stuck at the quietly brilliant screen.
I tried to do a flash recovery using the Hasson kit and downloaded the ML_U7 from the android files site and when I try to flash it says image failed.
I tied to run the RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Rad io_4A.23.3263.28_10.38r.1157.04L_release_351317_si gned_2.exe file but it also give me an image error.
I do have twrp 2.7.0.0 installed on the phone.
Here are my phone specs
M7UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP=v26.120.274.0202
eMMC-boot
May 4 2013,14:29:10:-1
I tried many different links and no matter what I try it doesn't seem to work.
Any help would be greatly appreciated.
Thanks in advance
I really need help please. I have been trying to fix this now for 2 days.
I have tried to run the above ruu file but I get an image mismatch. My image is version 1.29.631.17 and the one thats trying to install is version 4.19. I thin kthis is the problem with this ruu.
Then i tried to download other ruu's such as
m7-jb-crc-3.4.10-cl164589.zip
Now when I look in the TWRP there is nothing there so know I think I have no more OS installed.
I am trying to install these through the Hasoon2000 utility and i keep getting a signature mismatch. I have googled and tried the steps in many different posts and youtube videos as well, and nothing seems to work.
Help pleeeeease
It's been awhile since I've messed with ROMs, and much has changed. I think I might have bit off more than I can chew, but hopefully it's a quick fix. I've been trying to scan for solutions, but so far no luck.
About a week ago I decided I was tired of avoiding apps that had crazy permissions and decided to get root on my phone so I could use AppOpps. I went through the HTCDev route and unlocked the bootloader. I got stuck when firewater, temproot & Weaksauce wouldn't work.
So, I relocked the bootloader (shows **relocked**) and figured I'd wait until someone pushed an updated tool. Got an OTA notice, and now I can't update the software. The update fails about 1/3 of the way through, going from green circled arrows to red triangled exclamation.
I've tried using fastboot to push the OTA ROM, but have had no success. I can flash the newest firmware successfully (as noted here http://forum.xda-developers.com/showthread.php?t=2766604), but still no joy on the OEM ROM.
Do I really have to go to the trouble of flashing older firmware, downgrading the HBoot and ROM to an older version, etc.. to get up and running with a **locked** phone that will get OTA update?
Such a PITA to get control over my data/permissions.
Thanks in advance for help.
So just RUU and call it a day
Sent from my HTCONE using Tapatalk
Weaksauce does not work on the Sprint variants.
I would give Firewater another shot as s-off will save you headaches like this down the road. I would also suggest doing it before you update HTC has a way of making thing harder for us with every OTA.
If your phone is inoperable at the moment use this guide to get up and running.
http://forum.xda-developers.com/showthread.php?t=2503646
Recent RUU
olorolo said:
So just RUU and call it a day
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
At the moment, all I can find is an older RUU, not the latest/greatest.
I've found a Sprint_HTC_One_m7wls_4.06.651.4_RUU download, but my phone is reporting Software version 4.06.651.9
Would this be close enough?
xenor said:
At the moment, all I can find is an older RUU, not the latest/greatest.
I've found a Sprint_HTC_One_m7wls_4.06.651.4_RUU download, but my phone is reporting Software version 4.06.651.9
Would this be close enough?
Click to expand...
Click to collapse
If your running Sprint it should be fine
Sent from my HTCONE using Tapatalk
Phone is working OK
BD619 said:
Weaksauce does not work on the Sprint variants.
I would give Firewater another shot as s-off will save you headaches like this down the road. I would also suggest doing it before you update HTC has a way of making thing harder for us with every OTA.
If your phone is inoperable at the moment use this guide to get up and running.
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
So far, the phone seems to be working fine, other than deleting my Amazon saved games
If I run the RUU as suggested: Sprint_HTC_One_m7wls_4.06.651.4_RUU, will I still be in a good position to try firewater again?
xenor said:
So far, the phone seems to be working fine, other than deleting my Amazon saved games
If I run the RUU as suggested: Sprint_HTC_One_m7wls_4.06.651.4_RUU, will I still be in a good position to try firewater again?
Click to expand...
Click to collapse
That RUU won't work it's older then the software you are currently on.
Give firewater a try without using weaksauce
Update information
BD619 said:
That RUU won't work it's older then the software you are currently on.
Give firewater a try without using weaksauce
Click to expand...
Click to collapse
You are correct, the RUU did not work. It failed completely on Windows 8.1 x64, so I ran in on Windows 7 x64, and it stopped at about 4%. The phone screen was black with the HTC logo and it just stayed like that for over an hour (I took the dog for a walk).
The Boot reports the following:
*** RELOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v32.120.274.0909
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014, 16:31:22.0
Once the phone is booted up, the Settings->About reports the following:
Software version: 4.06.651.9
Android 4.4.2
HTC Sense 5.5
Can an OTA flash the firmware and die before updating the software?
Do I need to flash the firmware to match the reported software in the system?
xenor said:
You are correct, the RUU did not work. It failed completely on Windows 8.1 x64, so I ran in on Windows 7 x64, and it stopped at about 4%. The phone screen was black with the HTC logo and it just stayed like that for over an hour (I took the dog for a walk).
The Boot reports the following:
*** RELOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v32.120.274.0909
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014, 16:31:22.0
Once the phone is booted up, the Settings->About reports the following:
Software version: 4.06.651.9
Android 4.4.2
HTC Sense 5.5
Can an OTA flash the firmware and die before updating the software?
Do I need to flash the firmware to match the reported software in the system?
Click to expand...
Click to collapse
I've never personally did an OTA so not sure.
If you use the guide I posted and use the 5.03.651.3 s-on firmware and rom it will be just like taking the OTA
OK, it took a little bit of research, because you probably assume most folks already know how to do this, but I got through your tutorial. Getting the latest TWRP was a bit confusing. At first I thought I had to have the TWRP app from the Google Play Store, which requires root, but then I found the TWRP page pointing to GooManager which automatically found the latest file and installed.
After that, it took a minute to figure out I had to go into HBOOT and select recovery to get the TWRP tool. I thought I was going to be using an Android utility to accomplish this (I guess I mean to say an app from the play store, not a BIOS like utility).
Lastly, for some reason the Android MyHTC driver died, so I had to manually remove and re-install. Re-running HTC Sync Manager install did not help. Once I got that figured out, I was able to adb push the file to the SDCard (Too bad one can't just drag and drop, but I'm guessing MTP dies with the flash?) and then load it from TWRP.
At the moment, I'm happy. I have the newer software and plenty to play with. I will give Firewater a try again, but I'm guessing it will be more difficult with the newest firmware/ROM?
I started with this guide a few days ago, but didn't push forward when I couldn't figure out the TWRP information. It might help to update that part of the guide, unless you want to avoid too many noobs getting into trouble.
Thanks for your help, and pointing me back in the right direction so quickly.
Hey guys,
So first sorry for my bad English but I’m from Germany And also I’m a total amateur with Android and roots and all that stuff.
Now back 2 topic.
So I bought my HTC One (M7) almost a year ago. I rooted it, unlocked it and also got S-Off. Yesterday I tried to get it back to stock so I could finally get some OTA-Updates. When I first entered the bootloader (if that’s the name of the white screen) everything seemed normal. But after I left my One got stuck in a Bootloop. I thing I know the cause for that but I will come back to that later.
My big problem is that while I’m in the bootloader my PC cant connect with the One. The device-manager says something like “cant start the device (code 10)”. So I cant use RUUs and the likes to get it back to stock. I tried all kinds of drivers and all USB-Slots I got. Nothings changes.
Another problem is, that my Phone is back to S-On, though I have no clue what I could have done to do that. And that brings me back to the Bootloop. After I wiped all my Data I could start my phone and had no Bootloop, everything worked just fine (though no APPs where left of course). But I got the message I should Install SuperSU. The second I did that I was back in the loop. So I think S-On and SuperSU is not a good combination. But since I cant connect the One via Fastboot I also have no clue how to S-Off it again.
If I just could connect the Phone with my PC via fastboot I would probably be able to get stock back. Does anyone know what the problem might be?
I don’t know if it helps but the bootloader says:
Tampered
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
And I also use Windows 8.1
Change computer
Windows 7
from HTC One
Try on other PC. If you get it to connect to fastboot, keep that PC and run the ruu.
Sent from my HTC One using XDA Premium 4 mobile app
Hello XDA Wizards,
I am desperately in need of some help and advice. Let me start by telling you that this is for my housemate and we have been trying for days to repair it with no success.
Basically what has happened is that he installed a custom rom, Viper i think and everything was fine, he then left the country and when he came back to the uk the phone massively messed up. It was restarting every 2-3 mins and i noticed the imei had disappeared.
The phone is,
Tampered
Unlocked
S-ON
HBOOT - 1.57.0000
Radio - 4T.27.3218.14
OpenDSP-v32.120.274.0909
OS - MISSING!!!
eMMC-boot - 2048MB
I am pretty much a noob to this whole thing so please forgive any stupidity. I have researched and came accorss this thread however i have no idea which RUU i should use if any? http://forum.xda-developers.com/showthread.php?t=2728428
I have tried installing the latest version on Viper Rom and it boots but after that it restarts ever 2 mins and never properly goes into the OS. It has the latest version of TWRP and ADB sideload works fine.
Is this device bricked or can it be saved, (i dont care so much as im on a NEXUS 5 ) but i would get some serious bro points if i could fix it for him.
Anyway please enlighten me as im out of suggestions for the device.
THANKS YALLLLLL