USB Device not recognized in fastboot mode - Windows 8.1 - One (M7) Q&A, Help & Troubleshooting

So, I've been searching around for two days now. And nothing seems to work. I'm hoping that there is a fix for my problem that I seem to have missed.
I wan't to sell my HTC One (M7). Of course I have a rooted phone with S-OFF. I wan't to restore my phone to stock, but I haven't used it in quite some time. I'm following this tutorial: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
Everything went great, my bootloader is locked and I even removed the tempered banner:
*** LOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-HTC__E11
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013,00:54:00.14316
I still need to remove the root, return the stock ROM and kernel with RUU. I also need to put S-ON. The problem is that my HTC isn't recognized by the computer when it's in Fastboot mode.
Tried it on three computers, all on windows 8 or 8.1. Installed HTC Sync drivers (removed sync) but also tried other ways to install the drivers. The phone is recognized fine when booted up, just not in fastboot. Using the supplied USB cable in a USB 2.0 port.
Is there any know fix besides using Windows 7? Or is there any other way to install the stock ROM and kernel AND turning S-ON?

KobrakaiMM said:
So, I've been searching around for two days now. And nothing seems to work. I'm hoping that there is a fix for my problem that I seem to have missed.
I wan't to sell my HTC One (M7). Of course I have a rooted phone with S-OFF. I wan't to restore my phone to stock, but I haven't used it in quite some time. I'm following this tutorial: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
Everything went great, my bootloader is locked and I even removed the tempered banner:
*** LOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-HTC__E11
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013,00:54:00.14316
I still need to remove the root, return the stock ROM and kernel with RUU. I also need to put S-ON. The problem is that my HTC isn't recognized by the computer when it's in Fastboot mode.
Tried it on three computers, all on windows 8 or 8.1. Installed HTC Sync drivers (removed sync) but also tried other ways to install the drivers. The phone is recognized fine when booted up, just not in fastboot. Using the supplied USB cable in a USB 2.0 port.
Is there any know fix besides using Windows 7? Or is there any other way to install the stock ROM and kernel AND turning S-ON?
Click to expand...
Click to collapse
First you should follow nkk71's guide (linked in my signature) instead of this outdated guide you have linked.
You will have fastboot issue using win 8.1 + hboot 1.44, so yes using win 7 is the best option imo. I know there is a driver fix somewhere but I never used it and I don't know where is that guide. (I think cIsA used this method so you might want to ask him). You could also use a MacOS computer or simply use a live cd or live usb of ubuntu on your win 8 computer.

I have a MacBook, but I never thought about trying that, since it normally never works (or there aren't any tools for it). Big surprise this time that everything went flawlessly and within a couple of minutes. Also thanks to the SuperGUIDE!
So many, many thanks!

Related

One/M7 stuck after TMOB upgrade to Kit-Kat

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).

[Q] Have I now botched my M7 beyond repair?

And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Looks like your OS is gone. Did you try and reflash twrp?
---------- Post added at 08:25 AM ---------- Previous post was at 07:55 AM ----------
24.531
polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Try running this 3.24.531.3 ruu, instructions on page.
http://forum.xda-developers.com/showthread.php?t=2375223
Thanks very much folks. Somehow, I was able to reflash twrp. From there, I realized that one mistake I made was overlooking that I needed s-off activated before flashing the ROM. (I think that was the beginning of my difficulties.)
Before reflashing twrp, I tried the RUU suggestion (TY!), but that needed bootloader turned back on, which in turn needed s-off...quite a procedure.
Anyway, With s-off done (thanks to the very persistent rumrunner_HTC_0.5.0.zip !), a second flash attempt of the rom at http://forum.xda-developers.com/showthread.php?t=2341395 worked seemingly perfectly. I now just trying to figure out whether I can get wifi calling working reliably (should be able to in theory, and at least one poster in that thread says he's done so).
Getting the HTC one properly modded is not a simple process relative to my prior experiences. I'm grateful for the help!
All of that work in the beginning was not needed. All you had to do was unlock bootloader, S-Off, change CID to 11111111, and run the GPE RUU from HTC. That's it. I had an ATT version that saw every different incarnation of software and it was that easy every time. Went from ATT to GPE, to T-Mobile, to Dev Edition and back without a problem. Well, red triangles of death be damned, but it never slowed me down, and the only time I got those was when I mis-matched the recovery img, or tried an update with a HBoot higher that 1.44, those are the only thinga to watch for. Make sure your ducks are in a row and update away. Stock recovery and lower Hboot worked awesome. I probably should put together a master file of everything I have for DL because I have it all and would make life so easy if someone hasn't done it already.

[Q] Help not sure what I did

So lets start out with I was using Beanstalk and really enjoyed it till my internet was malfunctioning. So I was checking out how to do a PLR update and noticed that the version I had didn't support it. So in turn I decided to look for a rom that had the Sense, so I chose the Viper rom. I went through the the CWM to load it and it wouldn't work (multiply tries.) I then tried using an older version of TWRP, I think 2.6, and it was working but then it would fail at status 7. I did some research and there were a few posts that mentioned to use the newest version. So I downloaded it, it gets as far as installing the rom and I still get the status 7 failure. So then the phone would only boot into the bootloader, so I reinstalled TWRP, it worked but wont load the rom. I reinstall the rom and I get as far as the bootloader again and need to reinstall TWRP. Now my phone is locked in the bootloader, it says at the top:
TAMPERED
RELOCKED
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.000
OpenDSP-v26.120.274.0202
eMMC-boot
May 8 2013,16:30:08:-1
Yes I do know that when I did the previous rom it will always say tampered but I don't know why it is relocked and S-ON. It should have been unlocked and s-off. So I am not sure what I need to do. I was wondering if anyone could help. By the way I was using the One In All Kit v3.1 program off my computer to help me with all of my roms flashing.
Tsvallette said:
TAMPERED
RELOCKED
M7_WLW PVT SHIP S-ON RH
HBOOT-1.44.000
OpenDSP-v26.120.274.0202
eMMC-boot
May 8 2013,16:30:08:-1
Yes I do know that when I did the previous rom it will always say tampered but I don't know why it is relocked and S-ON. It should have been unlocked and s-off. So I am not sure what I need to do. I was wondering if anyone could help. By the way I was using the One In All Kit v3.1 program off my computer to help me with all of my roms flashing.
Click to expand...
Click to collapse
your phone is M7_WLV variant which means its not a gsm variant (M7_UL or M7_U) so you must use recoveries and roms specifically for your phone variant, M7_WLV
bootloader doesnt lock back by itself, so you probably did by mistake, same for s-on/s-off.
learn how to use adb and fastboot and get rid of this toolkit. always better to use adb and fastboot directly from the terminal
then
unlock bootloader
flash the correct recovery for your phone variant
flash a compatible rom for your phone variant
here is the coorect forum for your phone: http://forum.xda-developers.com/verizon-htc-one
I have a Sprint HTC One... And currently I am loading / downloading SDK and all of its components. I do appreciate in info. It seems as though that the programs that I am trying to use are older and outdated. The version of SDK that I had could have been one of the reasons why I am having issues connecting between the computer and my phone.
Tsvallette said:
I have a Sprint HTC One... And currently I am loading / downloading SDK and all of its components. I do appreciate in info. It seems as though that the programs that I am trying to use are older and outdated. The version of SDK that I had could have been one of the reasons why I am having issues connecting between the computer and my phone.
Click to expand...
Click to collapse
you don't need full sdk
Just need adb mini tool that's enough for all process
from HTC One

[Q] Bootloop and other problems

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

[Q] Can I save my phone?

Hey xda-developers, can you please help me save my phone from the dead?
I have a HTC One M7_UL PVT SHIP S-OFF RH phone.
It's LOCKED thanks to HTC1Guru reset (which I'm part way through)
S-OFF is paid to Sunshine
I'm no longer in position to give you any numbers on anything but:
CID: HTC__001
HBOOT_ 1.44.0000
Radio: 4T.29.3218.08
OpenDSP: v32.120.274.0909
eMMC-boot
These numbers may or may not be stock, I've changed CID a couple of times before.
My big problem is that I failed a RUU-flash as the device started automatically after the preflash and I missed to run the command immediately.
I can only boot into HBOOT, FASTBOOT and RECOVERY(TWRP-v2.8.0 - red flag).
I left the fastboot option in my phone off last time I did any modding with it, so I can not connect fastboot to my PC. The common <waiting for device> showing. Only fix is to change the settings in the phone.
I am able to do the old UPDATE.ZIP method by mounting my phone with MTP in RECOVERY-mode. But I don't know and could not find any guide form my phone. I've never been able to get adb sideload working but adb push is just enough.
I have a backup, I think before I did S-OFF, and all my files is accessible if I cared more about them. (Most things are stored in clouds anyway and settings are easily adjusted on the go.)
I didn't read up to much, but I really hope there is a way to save my phone so it can help me with school and other things. (I have all my calenders and alarms telling me what to do.)
OskyEdz said:
Hey xda-developers, can you please help me save my phone from the dead?
I have a HTC One M7_UL PVT SHIP S-OFF RH phone.
It's LOCKED thanks to HTC1Guru reset (which I'm part way through)
S-OFF is paid to Sunshine
I'm no longer in position to give you any numbers on anything but:
CID: HTC__001
HBOOT_ 1.44.0000
Radio: 4T.29.3218.08
OpenDSP: v32.120.274.0909
eMMC-boot
These numbers may or may not be stock, I've changed CID a couple of times before.
Click to expand...
Click to collapse
You need to unlock the bootloader again to get started.
Slight problem.
eyeyousee said:
You need to unlock the bootloader again to get started.
Click to expand...
Click to collapse
I can't change it as I can't connect to fastboot from my PC . My PC is Windows 8.
I've tried with Windows 7 laptop without success.
OskyEdz said:
I can't change it as I can't connect to fastboot from my PC .
Click to expand...
Click to collapse
as you are now on HBOOT 1.44 you MUST USE A windows 7, XP or Linux distro for the computer to see your phone, anything 8 / 8.1 or 10 doesn't work.
Seanie280672 said:
as you are now on HBOOT 1.44 you MUST USE A windows 7, XP or Linux distro for the computer to see your phone, anything 8 / 8.1 or 10 doesn't work.
Click to expand...
Click to collapse
Thanks, I have a Windows 7 laptop that I could just send the files over.
But isn't it strange that I could use adb on a Windows 8?
Edit: I could not get my Win7 Lap to see adb or fastboot. I did install drivers manually first with adb's drivers then I also tried some universal Andriod drivers (uninstalled in between)
Backup Restored
I had a backup in my disposal, but the problem from orgin is that I've uninstalled HTC Sense launcher but I take that in another thread.
Rule #1: Always make backups.

Categories

Resources