Hi, so i have no OS on my HTC One, but i have TWRP fully functional.
I have tried using adb and fastboot on my laptop (all drivers installed), to no avail
on TWRP, the battery indicator has a plus next to the number, indicating my laptop is charging it. But it does not show up on ADB when i try to see ADB devices.
On fastboot it does not show Fastboot USB.
Any Advice ?
mrsimpson321 said:
Hi, so i have no OS on my HTC One, but i have TWRP fully functional.
I have tried using adb and fastboot on my laptop (all drivers installed), to no avail
on TWRP, the battery indicator has a plus next to the number, indicating my laptop is charging it. But it does not show up on ADB when i try to see ADB devices.
On fastboot it does not show Fastboot USB.
Any Advice ?
Click to expand...
Click to collapse
Try a different cable, be careful though, some cables are only for charging, they don't all support data, if all other cables fail then its your phones micro USB port.
Related
I messed up my phone a while ago by trying to update to 4.4 while being S-off. Due to several things I ended up with a phone that stays in a bootloop. I can still get to the Fastboot Menu, but even when I try to go into Recovery the phone boots and for a fraction of a second I can see the Clockworkmod Logo before the devices reboots again (so I assume I messed up Clockworkmod as well).
So I tried to sideload Clockworkmod via USB but ADB doesn't seem to recognize the phone in Windows 8. I installed the official HTC package, but the device doesn't show up when I use 'adb devices', so I can't sideload anything (phone was connected to a USB 2.0 port on the rear panel). I tried the same thing on my MacBook Retina with Windows 7 on Bootcamp, same problem. I read there might be problems with USB3 but my MacBook doesn't have USB2 ports any more. I havent tried getting into my phone in OSX or Linux yet since I couldn't find a decent guide, I only know a few basics with the Unix terminal.
Can anyone give me any tip how to get my phone to work again? I also have a USB OTG Adapter, maybe that helps?
Here is a video of my phone with the Clockworkmod Logo bootcycle (can't post links yet so please copy-paste it).
youtu.be/TjG50x7EcUw
cecay said:
I messed up my phone a while ago by trying to update to 4.4 while being S-off. Due to several things I ended up with a phone that stays in a bootloop. I can still get to the Fastboot Menu, but even when I try to go into Recovery the phone boots and for a fraction of a second I can see the Clockworkmod Logo before the devices reboots again (so I assume I messed up Clockworkmod as well).
So I tried to sideload Clockworkmod via USB but ADB doesn't seem to recognize the phone in Windows 8. I installed the official HTC package, but the device doesn't show up when I use 'adb devices', so I can't sideload anything (phone was connected to a USB 2.0 port on the rear panel). I tried the same thing on my MacBook Retina with Windows 7 on Bootcamp, same problem. I read there might be problems with USB3 but my MacBook doesn't have USB2 ports any more. I havent tried getting into my phone in OSX or Linux yet since I couldn't find a decent guide, I only know a few basics with the Unix terminal.
Can anyone give me any tip how to get my phone to work again? I also have a USB OTG Adapter, maybe that helps?
Click to expand...
Click to collapse
adb doesn't work in the bootloader .. never has
Post results of fastboot getvar all minus you SN and IMEI
Download TWRP 2.6.3.3 > http://techerrata.com/browse/twrp2/m7
flash it (unless you have a sprint or Verizon phone Then STOP)
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
your bootloop should be gone now boot to recovery and adb should work fine again
Hi guys,
I have an HTC One with S-OFF and GPE ROM, I'm trying to get pretty much everything back to stock now. I've identified my CID and downloaded the appropriate RUU exe, the drivers are installed properly and the device is recognized when I run adb devices. However, when I try the RUU it gives me error 170, and on the last step it shows this which is pretty weird "abd dfksfsafjsdfkklsj". Any ideas? Thanks.
Edit: It seems to give that error even when I don't have the phone plugged in at all:
"1. Connect the Smartphone to the USB cable
abd dfksfsafjsdfkklsj"
enduu said:
Hi guys,
I have an HTC One with S-OFF and GPE ROM, I'm trying to get pretty much everything back to stock now. I've identified my CID and downloaded the appropriate RUU exe, the drivers are installed properly and the device is recognized when I run adb devices. However, when I try the RUU it gives me error 170, and on the last step it shows this which is pretty weird "abd dfksfsafjsdfkklsj". Any ideas? Thanks.
Edit: It seems to give that error even when I don't have the phone plugged in at all:
"1. Connect the Smartphone to the USB cable
abd dfksfsafjsdfkklsj"
Click to expand...
Click to collapse
Error 170 = usb connection error either because a bad cable, drivers installed incorrectly etc. etc... Try a different cable, re-install drivers correctly and use usb 2.0 ports only.
Ok so after digging through the error logs I found something really weird:
The reason it fails is that when the RUU runs adb devices from C:\Program Files\HTC\HTC Sync 3.0\ it outputs the device number + offline. I know this is true since I tested it in a prompt. However, when I run the command from a mini-sdk I have placed somewhere else, it recognizes the device properly ( device number + "device").
Does anyone have an idea what's going on? I've installed HTC Sync but I tried HTC Sync Manager as well earlier, same problem.
alray said:
Error 170 = usb connection error either because a bad cable, drivers installed incorrectly etc. etc... Try a different cable, re-install drivers correctly and use usb 2.0 ports only.
Click to expand...
Click to collapse
This is the second cable I'm trying, different port, I have no idea how many times I've reinstalled the drivers today lol. I'm using the latest HTC Sync & Driver version
enduu said:
This is the second cable I'm trying, different port, I have no idea how many times I've reinstalled the drivers today lol. I'm using the latest HTC Sync & Driver version
Click to expand...
Click to collapse
Try another computer, another ruu. Make sure the usb cables you are using are not only charging cables. Maybe a defective usb port on the phone.
error 170 is usb connection error, so troubleshoot everything related to this:
usb ports
usb cables
usb drivers
phones drivers
RUU
computer
phone usb port
alray said:
Try another computer, another ruu. Make sure the usb cables you are using are not only charging cables. Maybe a defective usb port on the phone.
Click to expand...
Click to collapse
Well this is the only computer I have access to for the next couple of days, and the only ruu I could find. I am not sure what you mean with the cables though.
Here's the thing, if I replace the adb file from htc sync ( 159kb ) with the one from the mini-sdk ( 800kb) it recognizes the device, and I'm thinking it will probably run the RUU as well. Do I risk messing up something if I do this? This is in regards to http://forum.xda-developers.com/showpost.php?p=54529900&postcount=3 . Thanks.
enduu said:
Well this is the only computer I have access to for the next couple of days, and the only ruu I could find. I am not sure what you mean with the cables though.
Click to expand...
Click to collapse
Some usb cable only have +5v and ground to provide power and charge devices. Data usb cable have 4 connections: +5V, Ground, Data +, Data -.
Here's the thing, if I replace the adb file from htc sync ( 159kb ) with the one from the mini-sdk ( 800kb) it recognizes the device, and I'm thinking it will probably run the RUU as well. Do I risk messing up something if I do this? This is in regards to http://forum.xda-developers.com/showpost.php?p=54529900&postcount=3 . Thanks.
Click to expand...
Click to collapse
Never keep htc sync installed when you flash things on your phone, only install it for the drivers, then uninstall the program (drivers will not be removed). HTC sync might be the problem here.
alray said:
Some usb cable only have +5v and ground to provide power and charge devices. Data usb cable have 4 connections: +5V, Ground, Data +, Data -.
Never keep htc sync installed when you flash things on your phone, only install it for the drivers, then uninstall the program (drivers will not be removed). HTC sync might be the problem here.
Click to expand...
Click to collapse
Well I did remove htc sync but after checking the logs I noticed the problem was still the same. For some reason, every time the device failed to be recognized with the adb devices command, what fixed it for me was putting the it in fastboot, weird.
enduu said:
Well I did remove htc sync but after checking the logs I noticed the problem was still the same. For some reason, every time the device failed to be recognized with the adb devices command, what fixed it for me was putting the it in fastboot, weird.
Click to expand...
Click to collapse
device offline when booted into a rom error is either drivers, out of date adb / fastboot, but normally it will tell you if its out of date or finally you don't have usb debugging enabled properly, this also applies to the 170 error, easy way to test if its the usb cable or ports etc is to try fastboot getvar all, if you get a result, then its not cables or ports.
adb commands don't work in the bootloader, only fastboot commands.
Hello Reader(s),
Im trying to help a friend recover his HTC M7 (one) to a working phone. Right now the phone will not get recognized, neither ADB nor Fastboot in Windows 10, Ubuntu or Windows 7. I've tried 5 diffrent cables on 2 diffrent PC's/ USB slots (usb 2.0/3.0). The phone has TWRP v2.8.6.0 installed is S-OFF and has Super CID installed. USB -OTG mounting isnt working, tried FAT/FAT32/exFAt on 3 diffrent usb devices. The only working thing atm is Busybox using TWRP Terminal command . Help appreciated
zibbi3 said:
Hello Reader(s),
Im trying to help a friend recover his HTC M7 (one) to a working phone. Right now the phone will not get recognized, neither ADB nor Fastboot in Windows 10, Ubuntu or Windows 7. I've tried 5 diffrent cables on 2 diffrent PC's/ USB slots (usb 2.0/3.0). The phone has TWRP v2.8.6.0 installed is S-OFF and has Super CID installed. USB -OTG mounting isnt working, tried FAT/FAT32/exFAt on 3 diffrent usb devices. The only working thing atm is Busybox using TWRP Terminal command . Help appreciated
Click to expand...
Click to collapse
Sounds like a defective usb port...You might want to replace the usb/mic board.
Is the phone still able to be recharged? When in bootloader and connected to a computer does is say FASTBOOT AC or FASTBOOT USB ?
Okay was thinking the same, defectice usb port. However it will charge via usb, fastboot only shows AC.
zibbi3 said:
fastboot only shows AC.
Click to expand...
Click to collapse
So the phone act like its connected to a wall charger instead of a computer...
Did you cleaned the usb port?
alray said:
So the phone act like its connected to a wall charger instead of a computer...
Did you cleaned the usb port?
Click to expand...
Click to collapse
Indeed, it charges when connected to a wall charger and connected to a computer it charges from usb. I cleaned the port with 96% denaturelized Alcohol still no go.
Hello,
I was on 10.0.7 version, rooted with magisk.
I had error while installing 10.0.8 version, then I downloaded 10.0.7 full rom, and used flash_all_except_data.bat.
Then after rebooting, it runs infinitely on loading animation (colors bar).
When I enter in fastboot, fastboot logo is displayed, but pc doesn't recognize phone anymore (fastboot devices show nothing).
[UPDATE]
I managed to boot with wiping data from recovery (Xiaomi stock recovery).
Now I can use the phone, but I don't have wifi (maybe something messed with vendor).
And I can't flash it because it is not recognized in fastboot mode (tried 3 W10 PCs, and 1 W7, it doesn't show in device manager)...
Can you help me ?
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
MIN313 said:
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
In fastboot mode nothing shows in device manager, with 3 different cables, with 4 different computers (3x W10, 1xW7).
I tried connecting with a live cd of CentOS.
Same results, adb connect when phone is started, but when I go in fastboot mode nothings shows in lsusb or dmesg...
Looks like the phone doesn't connect to pc in fastboot, very very strange...
Hi,
Using Lineage beckham jleebl 20191007, unlocked and working previously.
Charging over USB works fine.
USB debugging enabled.
Default USB configuration set to file transfer
HTML:
adb devices
results in "List of devices attached" & no devices
HTML:
fastboot devices
returns nothing
Above commands tried OS and bootloader, same results.
Cannot connect to transfer files, or adb push.
I have gone over many of the proposed solutions for file transfer not appearing as an option, none have worked. I took the phone to an repair shop, they cleaned the USB port, but essentially said, "lol, you're phone's broke". Said there was no obvious hardware issue.
Trying to boot into recovery mode just dumps me back into the bootloader. Can't push boot TWRP as fastboot can't communicate with device.
Any help would be SOOOO appreciated. Not being able to update the OS is causing many problems.
Thanks!!
hexagface said:
Hi,
Using Lineage beckham jleebl 20191007, unlocked and working previously.
Charging over USB works fine.
USB debugging enabled.
Default USB configuration set to file transfer
adb devices
results in "List of devices attached" & no devices
fastboot devices
returns nothing
Above commands tried OS and bootloader, same results.
Cannot connect to transfer files, or adb push.
I have gone over many of the proposed solutions for file transfer not appearing as an option, none have worked. I took the phone to an repair shop, they cleaned the USB port, but essentially said, "lol, you're phone's broke". Said there was no obvious hardware issue.
Trying to boot into recovery mode just dumps me back into the bootloader. Can't push boot TWRP as fastboot can't communicate with device.
Any help would be SOOOO appreciated. Not being able to update the OS is causing many problems.
Thanks!!
Click to expand...
Click to collapse
Wait, you took your phone to a repair shop, they told you it's busted,. So you are here looking for a magician, to whammy your phone? When you find one, please ask for lotto numbers, and forward them to me.
Check that you are using data capable usb cable, some cheap cables are only charge capable.
Otherwise, light a candle.
just 4 causes: 1.- moto drivers and Usb debugg ,2.- usb PC, 3.- Usb phone or 4.- usb cable. The option 4.- need repair.