Hi guys,
So today I got the 4.4 OTA update on my HTC One M7.
Of course I downloaded it and the phone entered into boot loop - "No command" and "Error".
Via pressing POWER + VOLUME DOWN I entered into the service screen, where I have the following options:
***LOCKER***
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSP-v31.120.274.0617
OS-3.07.1700.1
eMMC-boot 2048 MB
Aug 19 2013, 21:01:47.0
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGECRC
SHOW BARCODE
I have tried doing FACTORY reset, but to no luck the phone goes into Erasing mode and then again into the "No command" and "Error" loop.
I don't have the htc one USB drivers currently on my Windows 8.1 laptop.
Could you advice me how to proceed.
Thanks in advance.
I am offering a reward for any help.
You need to fix your driver issue FIRST..
Then unlock bootloader using fastboot oem unlock
As you are S-OFF, you can then run the fastboot flash ruu.zip. Follow the steps from: http://forum.xda-developers.com/showthread.php?t=2358781
Hello,
After installing the new rom of ViperOne 6.1.0. my Mobile gets in a Loop of restarts.
(mobile HTC one separte SIM t-mobile)
After I installed the Viperone 6.1.0 its says Install FAILED.
So i rebooted the Phone and after that its stay stuck ad Rebooting and trying to get to Recovery.
First i get the Normal HTC text with red text on the bottom and after that it will go black and goes to HTC screen with Pink/purple recovery on the top. There is a constant loop on/off
When the screen goes black it says clockworkmods 6.0.4.3.
Is there a recovery file for this version ??? and can i fastboot it with flash from ADB??
The things I tried
Getting to Fastboot was no trouble.
1.I did a factory reset (not working)
2.Connecting to Fastboot USB on phone it says fastboot USB (PC doesn't recognized the USB driver When i already installed it WIN7)
3.Trying to connect with ADB (didn't find devices)
3.1 When i do the command fastboot devices its says FA34XW905611
4.Wait when the power went down and recharged it.
mobile info.
HTC one
UNLOCKED
M7_UL PVT SHIP S-OFF RH
CID-HTC_102
HBOOT-1.44.0000
RADIO-4A.14.3250.13
openDSP-v26.120.274.0202
eMMC-boot
Apr 20 2013
Can somebody Help me.
Thank you and greets,
From the Netherlands.
Can't get my phone to be detected in fastboot or adb or anything at all.
I have TWRP 2.7.1.1 installed and I have been trying to get it to connect to the PC. This has happened before and I somehow got it to work again. This has probably something to do with fast charge or something.
Anyone has any ideas to this and is there a way to upgrade the firmware of my device without fastboot? The OS - Line in my fastboot is blank also.
Tried over 4 different cables, no difference.
Using both Windows and OS X.
Both see nothing in either adb or fastboot.
I had USB Fast Charge enabled but I've since tried to flash other ROMs to see if that would solve the problem but it doesn't.
If I remember correctly, the only way to solve the problem was to flash a full default RUU over. I can't do it because fastboot usb isn't even detecting my phone
I was running GPE 4.4.4 with Elemental X 15.1 Kernel.
I'm having a similar issue with my wife's m7. I've previously rooted and s-off'd her m7. I can connect to it via adb and maintain a stable adb shell connection . Rebooting via adb reboot-bootloader or vol down+power and choosing fastboot, I'm unable to see the device under fastboot. fastboot devices returns nothing. fastboot reboot-bootloader returns < waiting for devices >. When fastboot connects via USB, I get a "USB Device Not Recognized" bubble from Windows 7. I've used device manager to uninstall the driver, but it returns on next connection as "Unknown Device". She's on stock 4.3.
Meanwhile, fastboot devices plugged into my old m7 returns a device ID and fastboot reboot-bootloader proceeds immediately. I know that I've got the drivers installed correctly because I have no trouble connecting my old m7 via adb or fastboot, nor my m8.
What in the world could be causing the first m7 to identify incorrectly to Windows as an unknown device when the second identifies as an Android USB device? I've installed and reinstalled drivers a dozen times before testing the second m7 and everything working flawlessly - updated Windows 7 as well after reading a topic regarding Windows 8.1 fastboot issues, just to be safe. Still nothing. In the course of writing this post, I was able to connect via adb while in recovery with no issues. I did a factory reset from recovery and still have no fastboot connection.
Code:
Wife's m7 (no fastboot):
CWM Recovery v6.0.4.3
Android Version 4.3
Sense 5.0
Software number 2.10.605.1 CL278010 release-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.15
eMMC-boot 2048mb
NOV 8 2013
Code:
My m7 (all working):
TWRP v2.8.0.2
Android Version 4.4.4
CM 11-20141112-SNAPSHOT-M12-m7vzw
Build number cm_m7vzw-userdebug 4.4.4 KTU84Q 8708283ec1 test-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.56.0000
RADIO-1.13.41.1109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048mb
Jan 20 2014
---------- Post added at 02:54 PM ---------- Previous post was at 02:44 PM ----------
Using basic troubleshooting skills that I thought I'd ruled out by getting both the m8 and other m7 to work fine, I swapped cables and ports. The original cable (an official HTC cable, possibly from my HTC Incredible) in the two test ports failed. A Nexus 7 2012 cable in both ports works fine. If I don't survive the project I'm working on right now, let it be known that Google killed me.
Tilgare said:
I'm having a similar issue with my wife's m7. I've previously rooted and s-off'd her m7. I can connect to it via adb and maintain a stable adb shell connection . Rebooting via adb reboot-bootloader or vol down+power and choosing fastboot, I'm unable to see the device under fastboot. fastboot devices returns nothing. fastboot reboot-bootloader returns < waiting for devices >. When fastboot connects via USB, I get a "USB Device Not Recognized" bubble from Windows 7. I've used device manager to uninstall the driver, but it returns on next connection as "Unknown Device". She's on stock 4.3.
Meanwhile, fastboot devices plugged into my old m7 returns a device ID and fastboot reboot-bootloader proceeds immediately. I know that I've got the drivers installed correctly because I have no trouble connecting my old m7 via adb or fastboot, nor my m8.
What in the world could be causing the first m7 to identify incorrectly to Windows as an unknown device when the second identifies as an Android USB device? I've installed and reinstalled drivers a dozen times before testing the second m7 and everything working flawlessly - updated Windows 7 as well after reading a topic regarding Windows 8.1 fastboot issues, just to be safe. Still nothing. In the course of writing this post, I was able to connect via adb while in recovery with no issues. I did a factory reset from recovery and still have no fastboot connection.
Code:
Wife's m7 (no fastboot):
CWM Recovery v6.0.4.3
Android Version 4.3
Sense 5.0
Software number 2.10.605.1 CL278010 release-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.15
eMMC-boot 2048mb
NOV 8 2013
Code:
My m7 (all working):
TWRP v2.8.0.2
Android Version 4.4.4
CM 11-20141112-SNAPSHOT-M12-m7vzw
Build number cm_m7vzw-userdebug 4.4.4 KTU84Q 8708283ec1 test-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.56.0000
RADIO-1.13.41.1109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048mb
Jan 20 2014
---------- Post added at 02:54 PM ---------- Previous post was at 02:44 PM ----------
Using basic troubleshooting skills that I thought I'd ruled out by getting both the m8 and other m7 to work fine, I swapped cables and ports. The original cable (an official HTC cable, possibly from my HTC Incredible) in the two test ports failed. A Nexus 7 2012 cable in both ports works fine. If I don't survive the project I'm working on right now, let it be known that Google killed me.
Click to expand...
Click to collapse
I love the design of this phone but I've had more problems than i can count. So frustrated with this. I had a working device but since adb nor fastboot was working, I made a mistake and I wiped the internal system. Now i have no operating system on the phone. Essentially all i have on it now is the GPE firmware + TWRP Recovery. I still can't get a ROM on it because I can't transfer any files into the internal storage and adb nor fastboot is working. USB OTG seems to give some response in TWRP Terminal Emuatlor when I do "lsusb" but I still can't mount it.
ZaneChua said:
I love the design of this phone but I've had more problems than i can count. So frustrated with this. I had a working device but since adb nor fastboot was working, I made a mistake and I wiped the internal system. Now i have no operating system on the phone. Essentially all i have on it now is the GPE firmware + TWRP Recovery. I still can't get a ROM on it because I can't transfer any files into the internal storage and adb nor fastboot is working. USB OTG seems to give some response in TWRP Terminal Emuatlor when I do "lsusb" but I still can't mount it.
Click to expand...
Click to collapse
don't try and mount the usb-otg just boot into twrp and choose install / tap where it says Internel Storage xxxxxxmb / this will drop down and you can choose USB-OTG. now install your rom
clsA said:
don't try and mount the usb-otg just boot into twrp and choose install / tap where it says Internel Storage xxxxxxmb / this will drop down and you can choose USB-OTG. now install your rom
Click to expand...
Click to collapse
That was obviously the first thing to do. But USB-OTG is still showing me 0MB. So hence why I said i was trying to mount it. By i say mount it, it's not clicking mount in twrp. It's mounting via command line.
I've formatted the USB to NTFS, exFat and FAT32. Neither filesystem seems to be able to mount. But the OTG is clearly detected.
Tilgare said:
I'm having a similar issue with my wife's m7. I've previously rooted and s-off'd her m7. I can connect to it via adb and maintain a stable adb shell connection . Rebooting via adb reboot-bootloader or vol down+power and choosing fastboot, I'm unable to see the device under fastboot. fastboot devices returns nothing. fastboot reboot-bootloader returns < waiting for devices >. When fastboot connects via USB, I get a "USB Device Not Recognized" bubble from Windows 7. I've used device manager to uninstall the driver, but it returns on next connection as "Unknown Device". She's on stock 4.3.
Meanwhile, fastboot devices plugged into my old m7 returns a device ID and fastboot reboot-bootloader proceeds immediately. I know that I've got the drivers installed correctly because I have no trouble connecting my old m7 via adb or fastboot, nor my m8.
What in the world could be causing the first m7 to identify incorrectly to Windows as an unknown device when the second identifies as an Android USB device? I've installed and reinstalled drivers a dozen times before testing the second m7 and everything working flawlessly - updated Windows 7 as well after reading a topic regarding Windows 8.1 fastboot issues, just to be safe. Still nothing. In the course of writing this post, I was able to connect via adb while in recovery with no issues. I did a factory reset from recovery and still have no fastboot connection.
Code:
Wife's m7 (no fastboot):
CWM Recovery v6.0.4.3
Android Version 4.3
Sense 5.0
Software number 2.10.605.1 CL278010 release-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.15
eMMC-boot 2048mb
NOV 8 2013
Code:
My m7 (all working):
TWRP v2.8.0.2
Android Version 4.4.4
CM 11-20141112-SNAPSHOT-M12-m7vzw
Build number cm_m7vzw-userdebug 4.4.4 KTU84Q 8708283ec1 test-keys
From bootloader:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.56.0000
RADIO-1.13.41.1109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048mb
Jan 20 2014
---------- Post added at 02:54 PM ---------- Previous post was at 02:44 PM ----------
Using basic troubleshooting skills that I thought I'd ruled out by getting both the m8 and other m7 to work fine, I swapped cables and ports. The original cable (an official HTC cable, possibly from my HTC Incredible) in the two test ports failed. A Nexus 7 2012 cable in both ports works fine. If I don't survive the project I'm working on right now, let it be known that Google killed me.
Click to expand...
Click to collapse
I just realised something abouit your wife's m7. The hboot 1.54 has always had issues with fastboot in Windows 8.1. I have never gotten it working on Windows 8.
ZaneChua said:
I just realised something abouit your wife's m7. The hboot 1.54 has always had issues with fastboot in Windows 8.1. I have never gotten it working on Windows 8.
Click to expand...
Click to collapse
Interesting. I wonder if that somehow was related to my problem. Now that I've updated the hboot, I wonder if I'd have the same issues connecting with my usual USB cable or in particular USB ports. Might have to test if I can nab her phone from her - she's really digging her new Lollipop install.
Tilgare said:
Interesting. I wonder if that somehow was related to my problem. Now that I've updated the hboot, I wonder if I'd have the same issues connecting with my usual USB cable or in particular USB ports. Might have to test if I can nab her phone from her - she's really digging her new Lollipop install.
Click to expand...
Click to collapse
Your problem isn't as serious as mine. lol. Try having a phone which doesn't detect at all through device manager or anything.
Can you update or change the hboot without using usb-fastboot? I have 1.54 and its giving me the same issue with not detecting on Windows 8
det0ur said:
Can you update or change the hboot without using usb-fastboot? I have 1.54 and its giving me the same issue with not detecting on Windows 8
Click to expand...
Click to collapse
You don't have usb fastboot working?
Have you tried to completely uninstall the drivers in your computer and then reinstall them? I've had that work on more than one occasion...
Go to control panel/system, and where it says your windows rating or whatever, look up in the top left corner for device manager. You can completely uninstall the drivers from there.
On Windows 8,you may even be able to type "device manager" into that stupid little search thing in the start screen. Or download classic shell from the site that pops up in Google and get a real live start menu back...
Hope it helps. Seems like a driver issue more than a phone issue to me.
ATDavis said:
Have you tried to completely uninstall the drivers in your computer and then reinstall them? I've had that work on more than one occasion...
Go to control panel/system, and where it says your windows rating or whatever, look up in the top left corner for device manager. You can completely uninstall the drivers from there.
On Windows 8,you may even be able to type "device manager" into that stupid little search thing in the start screen. Or download classic shell from the site that pops up in Google and get a real live start menu back...
Hope it helps. Seems like a driver issue more than a phone issue to me.
Click to expand...
Click to collapse
Definitely not a driver issue. It's a phone issue. OTG doesn't even work. Device Manager doesn't even detect my phone or any kind of USB device when i attach my phone.
ZaneChua said:
You don't have usb fastboot working?
Click to expand...
Click to collapse
Nope. It doesn't work.
I fixed this problem with installing Kies.
Tobirexy said:
I fixed this problem with installing Kies.
Click to expand...
Click to collapse
What has Kies have to do with the HTC One? Isn't Kies for Samsung only phones? I don't believe HTC phones have an ODIN download mode.
Sorry that was the wrong post.
So for anyone who wanted to know what was wrong, it was definitely the usb port. I replaced it and now it works fine.
Hi
when i was going to root my HTC One Dual Sim in the middle of the project my phone died
First i unlocked bootloader, BUT when i want to s-off with moonshine in command prompt (distiller.exe) it cant continued and said "read again" and "press enter to exit"
now i'm in the middle of nowhere, my phone just can boot to HBoot...
i also install recovery.img
and this is my info on hboot screen:
***TRAMPERED***
***UNLOCKED***
M7CDUG PVT SHIP S-ON RL
HBOOT-2.49.0000
RADIO-U3.15.3509.12
OpenDSP-v32.120.274.0909
QSC-E1237.29.35.0108
OS-5.17.402.6
eMMC-boot 2048MB
May 30 2014, 17:47:49.0
i also want to install a RUU that i downloaded and i think it's ok for my phone from recovery mode but that failed. somewhere i read that's because my phone is not s-off.
Any Help or suggestion ??!
Update:
i tried with "rumrunner" (that's like "moonshine") and it gets error like moonshine, but in its error it said "no adb connection to device. Debugging on? Drivers?"
how it's possible cause i installed drivers and turned off usb debugging for unlocking process!!!
VahidMX said:
Hi
when i was going to root my HTC One Dual Sim in the middle of the project my phone died
First i unlocked bootloader, BUT when i want to s-off with moonshine in command prompt (distiller.exe) it cant continued and said "read again" and "press enter to exit"
now i'm in the middle of nowhere, my phone just can boot to HBoot...
i also install recovery.img
and this is my info on hboot screen:
***TRAMPERED***
***UNLOCKED***
M7CDUG PVT SHIP S-ON RL
HBOOT-2.49.0000
RADIO-U3.15.3509.12
OpenDSP-v32.120.274.0909
QSC-E1237.29.35.0108
OS-5.17.402.6
eMMC-boot 2048MB
May 30 2014, 17:47:49.0
i also want to install a RUU that i downloaded and i think it's ok for my phone from recovery mode but that failed. somewhere i read that's because my phone is not s-off.
Any Help or suggestion ??!
Update:
i tried with "rumrunner" (that's like "moonshine") and it gets error like moonshine, but in its error it said "no adb connection to device. Debugging on? Drivers?"
how it's possible cause i installed drivers and turned off usb debugging for unlocking process!!!
Click to expand...
Click to collapse
Wha?> You turned of USB debugging? Heres the problem. ADB works only if you have debugging turned. on. You won't make S-Off if you have USB debugging turned off
Bruce666 said:
Wha?> You turned of USB debugging? Heres the problem. ADB works only if you have debugging turned. on. You won't make S-Off if you have USB debugging turned off
Click to expand...
Click to collapse
No man, my usb dibugging should be on now! cause I can command adb or fastboot commands on my phone!
Hey there!
So I'm trying to get a HTC One M7 fixed here, and I have a problem. I was updating to Lollipop (stayed on KitKat for a while) then it froze then it rebooted. It had the new logo in the start screen, but it wouldn't boot to the OS at all. I've tried resetting via recovery, doesn't work. Resetting cache doesn't work. ADB + Fastboot with drivers doesn't work. I've tried so many things, like using a toolkit, using ADB + fastboot, going in bootloader and trying adb, nothing works. I'm stuck here. It's a M7 T-Mo variant. I haven't rooted it and it's on stock recovery and the bootloader information is:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDsp-v32.120.274.0909
OS-6.10.531.10
eMMC-boot 2048MB
Dec 15 2014,17:31:16.0
I've tried everything. Please help? I have a new phone already, but I want this to get working so I can at least sell it for some money
i would suggest unlocking the bootloader and installing a custom recovery, like twrp. Then you can restore from a stock backup file (im sure people here have them).
If that doesnt work... well...
Like I said, my PC doesn't recognize my one m7. Even other PCS don't... So I can't unlock the bootloader
go to htc.com/us/support/htc-one-t-mobile/news/
Look carefully at instructions, download file at bottom, run file, follow wizard instructions, should return device to stock.
Will delete data.
I know you said PC doesnt recognize it, but the RUU app should recognise your phone even if the PC doesnt. And if it doesnt, boot into fastboot and try
Hope this helped