I'm having problems connecting to my phone through ADB. I've flashed back and forth between 4.1.2 and 4.2.2 roms multiple times and had no problems with wiping everything (to ensure the proper file structure etc.) and then sideloading a zip to flash. However this time, I rebooted into recovery (TWRP 2.6.3.0), wiped everything (factory reset, then wiped data, then advanced wipe with the first 5 selected) and when I went to ADB sideload my new rom, I couldn't connect to my phone. I've followed multiple guides that attempt to establish a connection between the phone and Windows 7. I've installed multiple people's "updated USB drivers that fix the problem," but no go. While in recovery, the phone shows up in my device manager under "Other Devices > M7WLS" with the '!' icon under it. While in fastboot it connects under "Android Devices > My HTC" but no ADB commands will work here. And everything is already wiped so I currently can't use my phone until I get this fixed. Any help is greatly appreciated!! Fastboot will connect though so if I have to RUU, I can.
Solved!
If anyone else is having this problem, flash recovery back to TWRP 2.5.0.0 and then you will be able to connect to ADB through recovery. Hope this helps!
hamiltoes said:
I'm having problems connecting to my phone through ADB. I've flashed back and forth between 4.1.2 and 4.2.2 roms multiple times and had no problems with wiping everything (to ensure the proper file structure etc.) and then sideloading a zip to flash. However this time, I rebooted into recovery (TWRP 2.6.3.0), wiped everything (factory reset, then wiped data, then advanced wipe with the first 5 selected) and when I went to ADB sideload my new rom, I couldn't connect to my phone. I've followed multiple guides that attempt to establish a connection between the phone and Windows 7. I've installed multiple people's "updated USB drivers that fix the problem," but no go. While in recovery, the phone shows up in my device manager under "Other Devices > M7WLS" with the '!' icon under it. While in fastboot it connects under "Android Devices > My HTC" but no ADB commands will work here. And everything is already wiped so I currently can't use my phone until I get this fixed. Any help is greatly appreciated!! Fastboot will connect though so if I have to RUU, I can.
Click to expand...
Click to collapse
Use this
http://forum.xda-developers.com/showthread.php?t=2386956
Delete every other driver including HTC sync and set those as your drivers.
Do this by going to control panel, then to device management. Find your HTC and update drivers then find the folder you downloaded, and set it to that.
Sent from my HTCONE using XDA Premium 4 mobile app
twrp 2.5.0.0 unresponsive to touch
hamiltoes said:
If anyone else is having this problem, flash recovery back to TWRP 2.5.0.0 and then you will be able to connect to ADB through recovery. Hope this helps!
Click to expand...
Click to collapse
so i was having this same problem. i flashed 2.5 like you suggested, and it did read the adb, but now the recovery is unresponsive to touch... so close this time. any suggestions?
Related
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
bboybtek said:
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
Click to expand...
Click to collapse
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
alray said:
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
Click to expand...
Click to collapse
The only weird thing is, I used the 2.7.1.1 to flash the sense rom in first place and everything worked fine :/ . Anyway, thanks for the shout! :good: I'll give it a try right now and see how it goes.
Right, I'm having problems installing the drivers for some reason. The ones downloaded from this thread don't seem to be doing anything at all. When click on them they show up for a split second in task manager and then they disappear. No install wizard no nothing. So i downloaded the ones for Windows 7 from here but this just gives me a message that "Windows could not find driver software for your device." . I mean, what the hell?
Edit: Right, after a lot of struggle I've managed to successfully bring my phone back to life! I have no idea what caused the issues with installing the drivers. I've spent ages deleting every trace of HTC drivers, then installed Windows 7 ones and somehow it worked. Then flashed t.w.r.p 2.6.3.3 and venom and it seems to be working smoothly! Hopefully no more problems . Thanks a lot for helping out man!
Hi guys. I've had my HTC one for a while now and it had TWRP flashed on it. About a week ago I flashed the android revolution rom, worked well but my camera went really weird if I looked back at some recordings. So I wanted to revert back to stock everything. I flashed a stock recovery for the M7, after that I had the problem of not being able to connect my device to the computer when I fastboot mode. Simply wouldn't pick it up when I typed ADB devices in cmd. My device wouldn't show up after installing stock recovery. And it doesn't want to restore any roms either in stock recovery mode. I can't even access my folders in that mode to flash any roms. I click either apply from sd card, apply from phone storage. Says for a split second check CID failed or something and reboots itself.
I cannot flash TWRP back cause my computer since it can't pick it up. I've tried everything. Changing USB ports, uninstalling my drives for htc. Changing computers, unlocking, relocking bootloader. No result. I'm screwed cause I'm stuck on this android revolution rom, rooted. Just wanna flash custom recovery. I can connect it to my computer, access folders and add things to it but soon as I turn it off and go into fastboot mode it says fastboot usb and can hear the noise when its connected but it doesn't show up in adb devices and when I flash the TWRP it starts send then comes up with FAILED. Help please, would be appreciated!
Stevo001457 said:
Hi guys. I've had my HTC one for a while now and it had TWRP flashed on it. About a week ago I flashed the android revolution rom, worked well but my camera went really weird if I looked back at some recordings. So I wanted to revert back to stock everything. I flashed a stock recovery for the M7, after that I had the problem of not being able to connect my device to the computer when I fastboot mode. Simply wouldn't pick it up when I typed ADB devices in cmd. My device wouldn't show up after installing stock recovery. And it doesn't want to restore any roms either in stock recovery mode. I can't even access my folders in that mode to flash any roms. I click either apply from sd card, apply from phone storage. Says for a split second check CID failed or something and reboots itself.
I cannot flash TWRP back cause my computer since it can't pick it up. I've tried everything. Changing USB ports, uninstalling my drives for htc. Changing computers, unlocking, relocking bootloader. No result. I'm screwed cause I'm stuck on this android revolution rom, rooted. Just wanna flash custom recovery. I can connect it to my computer, access folders and add things to it but soon as I turn it off and go into fastboot mode it says fastboot usb and can hear the noise when its connected but it doesn't show up in adb devices and when I flash the TWRP it starts send then comes up with FAILED. Help please, would be appreciated!
Click to expand...
Click to collapse
Adb only works if you'te booted to OS or custom recovery. Command you're looking for in bootloader menu is "fastboot devices"
Fala Puno. Ja sam raditi sada. I'm of Croatian decent in Australia. I'll try this later when I return home
Fixed it! I'm an idiot, I didn't realise I was flashing the m8 twrp instead of m7. That's why it failed. Lol. Anyway thanks
Hey guys,
hope you can help me. Have a little problem: After trying to root my fire, it is in a bootloop and i don't know what to do. Hope you can help me. I guess it is bricked.
Thanks
EDIT:
I tried to sideload the software bin, but it didn't worked. Also my computer doesn't show the devices with "adb devices".
Also my computer doesn't show the devices with "adb devices".
Click to expand...
Click to collapse
Others have found that the fire will only show up on your pc after you select the sideload option on the fire. If it still doesn't show, try unplugging / replugging the usb. It seems to help some people to get it to appear. Also note that some devices will intentionally not allow you to flash bin if the battery level isn't high enough. It's a safety measure since running out of battery during a flash = brick. Be sure you're fully charged.
thanks, but..
Thank you for your response. I've tried everythin you said, but it didn't worked. Don't know what to do
cl.lio said:
Thank you for your response. I've tried everythin you said, but it didn't worked. Don't know what to do
Click to expand...
Click to collapse
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Hello, I'm a long time user of the forums I haven't had a new device to root since 2013 when I did my Nexus 7 FHD. I have always followed directions correctly and never bricked anything.... until now.
So anyway just got this tablet black friday sale and within minutes of opening the package I started to read up on rooting it.
I got into fastboot and started up TWRP_Fire_2.8.7.0 I made a backup on the device without error.
Then I installed UPDATE-SuperSU-v2.46 and tried to install open_gapps-arm-5.1-pico-20151129 but it failed.
I wiped cache/dalvik and rebooted. Now the tablet tries to boot into normal mode in a loop without success.
I have tried to get into recovery mode (volume down and power) but it fails and loops back to normal mode.
I can get into fastboot mode (volume up and power) and then back into TWRP however restoring the backup doesn't fix the boot loop.
I downloaded update-kindle-37.5.2.2_user_522053820.bin however I can't seem to figure out how to load it with TWPR sideload, and as I said I can't get into recovery mode.
Can anybody help me? @sd_shadow
EVOL-LOVE said:
Hello, I'm a long time user of the forums I haven't had a new device to root since 2013 when I did my Nexus 7 FHD. I have always followed directions correctly and never bricked anything.... until now.
So anyway just got this tablet black friday sale and within minutes of opening the package I started to read up on rooting it.
I got into fastboot and started up TWRP_Fire_2.8.7.0 I made a backup on the device without error.
Then I installed UPDATE-SuperSU-v2.46 and tried to install open_gapps-arm-5.1-pico-20151129 but it failed.
I wiped cache/dalvik and rebooted. Now the tablet tries to boot into normal mode in a loop without success.
I have tried to get into recovery mode (volume down and power) but it fails and loops back to normal mode.
I can get into fastboot mode (volume up and power) and then back into TWRP however restoring the backup doesn't fix the boot loop.
I downloaded update-kindle-37.5.2.2_user_522053820.bin however I can't seem to figure out how to load it with TWPR sideload, and as I said I can't get into recovery mode.
Can anybody help me? @sd_shadow
Click to expand...
Click to collapse
change update-kindle-37.5.2.2_user_522053820.bin to
update-kindle-37.5.2.2_user_522053820.bin.zip, place on sd card, install with twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
sd_shadow said:
change update-kindle-37.5.2.2_user_522053820.bin to
update-kindle-37.5.2.2_user_522053820.bin.zip, place on sd card, install with twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
Click to expand...
Click to collapse
:good: Awesome thank you very much, I thought about doing just that but figured I better ask the pros first.
I somehow missed that post on unbricking... :silly:
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Relock bootloader and run an RUU.
HTC One M9
Jtsessions said:
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Click to expand...
Click to collapse
Go back to TWRP and flash the stable SuperSU 2.65. Beta bootlooped for me too and then I went back to TWRP and flashed 2.65 and it was fine.
When you're in TWRP you should be able to connect the device to your computer and copy the 2.65 to phone storage and then be able to flash it.
I'm trying to backup my system directly to PC on my OnePlus 3T. I have FreedomOS CE 2.6 installed with TWRP 3.1.0-1. Rooted, unlocked bootloader, USB debugging enabled and everything.
But when i try to turn on ADB sideload so that i can run the commands, it fails. Am i missing anything? I'm not sure how this might help, but i tried sideloading with and without "wipe dalvik and Cache" enabled but both options didn't work....
Is there an error message when it fails?
I'll assume you've got the path and syntax right (sounds like you know what you're doing). So beyond that, sideload can be very finicky from what I've seen on my past devices. I've seen folks having problems with sideload, when simply putting a zip on the phone and flashing it the "standard" way works without a hitch.
I also think it sounds like you know what you're doing but are the adb drivers installed does the phone say it's in adb mode? I have seen people reporting issues with both windows 8 and 10 and sideload, so a little more info may help like whats the error message is it on pc or phone.
Helhound0 said:
I'm trying to backup my system directly to PC on my OnePlus 3T. I have FreedomOS CE 2.6 installed with TWRP 3.1.0-1. Rooted, unlocked bootloader, USB debugging enabled and everything.
But when i try to turn on ADB sideload so that i can run the commands, it fails. Am i missing anything? I'm not sure how this might help, but i tried sideloading with and without "wipe dalvik and Cache" enabled but both options didn't work....
Click to expand...
Click to collapse
your missing to tell us what actually happens
"it fails" means pretty much nothing...
can you connect to the device (adb devices)
do you get any error message?
is your mobile catching fire?
maddler said:
your missing to tell us what actually happens
"it fails" means pretty much nothing...
can you connect to the device (adb devices)
do you get any error message?
is your mobile catching fire?
Click to expand...
Click to collapse
Haha sorry about that.
I can use ADB normally. Like "adb devices" on CMD returns my device ID and everything when I'm booted into Android. This is the first time I'm doing this but to my understanding, I have to be in TWRP for the "adb backup --twrp" command to work. So that's why I'm trying to turn on ADB sideloading using TWRP... Which results the phone to be stuck in "enabling ADB sideloading". After a few minutes of this I get a "failed" in red lettering (literally, that's it.).. and the buttons to reboot and go back...
Helhound0 said:
Haha sorry about that.
I can use ADB normally. Like "adb devices" on CMD returns my device ID and everything when I'm booted into Android. This is the first time I'm doing this but to my understanding, I have to be in TWRP for the "adb backup --twrp" command to work. So that's why I'm trying to turn on ADB sideloading using TWRP... Which results the phone to be stuck in "enabling ADB sideloading". After a few minutes of this I get a "failed" in red lettering (literally, that's it.).. and the buttons to reboot and go back...
Click to expand...
Click to collapse
I think I had something similar when I 1st tried the --twrp option, but that worked next time.
Didn't try again so far.
I'll give it try later today.
I don't think you're supposed to start adb sideloading for this. Just be booted to TWRP.
I updated from 4.0.3 to beta 4 via local, but now I want to go back because of the battery drain problem. I tried several times via adb sideload to flash the zip but I keep getting the same error <cannot read 4.0.4.zip> over and over again. Even after installing the drivers, I got a little yellow exclamation triangle near the driver in device manager. Honestly I'm starting to give up, I think I wiped my phone more than 5 times in order to flash via sideload, only to get the same error continuously. as far as I know, I cannot go back to 4.0.3 via local from beta 4 right?
Please help...