I've already read the forums in search of a solution, I've uninstalled all htc drivers and reinstalling a single htc one driver. adb push wont work cause it can't find the device... What had happen was, I installed viper one "successfully" and it kept rebooting after starting up, so I went into recovery and wiped everything so it kept bringing me back to bootloader, Now i can't install a rom cause of this "device not found" issue. I hate this so much, it happen before and somehow it randomly worked, but this time it seems like luck isn't on my side... halp.
nibblemynutz said:
I've already read the forums in search of a solution, I've uninstalled all htc drivers and reinstalling a single htc one driver. adb push wont work cause it can't find the device... What had happen was, I installed viper one "successfully" and it kept rebooting after starting up, so I went into recovery and wiped everything so it kept bringing me back to bootloader, Now i can't install a rom cause of this "device not found" issue. I hate this so much, it happen before and somehow it randomly worked, but this time it seems like luck isn't on my side... halp.
Click to expand...
Click to collapse
check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
nkk71 said:
check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried that, that's what i meant when i said i uninstalled the driver. and when I plugged it in without a driver it didn't say "one" anything, just unknown device.
As you can see the device is correctly installed. but still can't be found, and it isn't displaying under my computer.
nibblemynutz said:
Tried that, that's what i meant when i said i uninstalled the driver. and when I plugged it in without a driver it didn't say "one" anything, just unknown device.
As you can see the device is correctly installed. but still can't be found, and it isn't displaying under my computer.
Click to expand...
Click to collapse
looks like your phone is booted in bootloader, you must be booted in custom recovery to use adb commands. My phone is listed as ''My HTC'' when booted in OS or in bootloader and under ''Android adb interface'' when booted in recovery.
Cancel pc security and firewall...
Sent from my HTC One using xda premium
alray said:
looks like your phone is booted in bootloader, you must be booted in custom recovery to use adb commands. My phone is listed as ''My HTC'' when booted in OS or in bootloader and under ''Android adb interface'' when booted in recovery.
Click to expand...
Click to collapse
Tried it in fastboot/bootloader/ recovery twrp/
device still could not be found.
horst81, I disabled firewall and tried. no good.
Someone should just release an aio for this issue, it seems so easy to solve but then again nothing i've tried seems to be working.
Solved!!! I uninstalled the drivers and rebooted then tried everything again. this time I went into recovery mode and it actually worked.
Thanks alray.
Related
Okay, Im at a loss and need some help.
I tried to load a ROM and it went bad. I can access bootloader and TWRP recovery.
I dont have a nandroid backup. The ROM I attempted to install is corrupt.
I cant seem to MOUNT in TWRP or PUSH a new ROM.zip through recovery with ADB.
I believe this is because of losing debugging when I attempted to install the corrupt ROM.
FUBAR and dont know what to do!
Any suggestions or help would be greatly appreciated.
3.04.651.2 RUU
3.05.651.5 RUU
BD619 said:
3.04.651.2 RUU
3.05.651.5 RUU
Click to expand...
Click to collapse
BD, Ive tried to PUSH these with ADB but ADB isnt working, Im thinking this is due to debugging not being turned on. I cant turn it on because I have no operating system to boot into...
ChaseQ said:
BD, Ive tried to PUSH these with ADB but ADB isnt working, Im thinking this is due to debugging not being turned on. I cant turn it on because I have no operating system to boot into...
Click to expand...
Click to collapse
In ADB when I try adb usb I get,
ADB server is out of date. killing...
* daemon started successfully *
error: device not found
ChaseQ said:
In ADB when I try adb usb I get,
ADB server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
You run these from your PC while booted to bootloader
BD619 said:
You run these from your PC while booted to bootloader
Click to expand...
Click to collapse
yes.
This is what I get if i try any commands in ADB
Im thinking this is an issue with not being able to turn on debugging due to a corrupt ROM I cant get into.
ChaseQ said:
yes.
This is what I get if i try any commands in ADB
Im thinking this is an issue with not being able to turn on debugging due to a corrupt ROM I cant get into.
Click to expand...
Click to collapse
Read the instructions posted in the 3.04 RUU thread
DB, Ill buy ya a case of beer if you get this mess Ive caused fixed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BD619 said:
Read the instructions posted in the 3.04 RUU thread
Click to expand...
Click to collapse
OKAY! Giving that a try in the morning. If Im back up and running, beer money is on its way my friend!
Didnt work...I think Im having a driver issue or something. Fastboot and ADB just wont seem to see the device..
Not sure what you doing, but adb probably isn't all that interesting yet. You should be going to the bootloader, selecting fastboot, plugging your cable in, then running "fastboot devices" to check connectivity.
If no device shows up, try updating the drivers to the most recent bigdaddy619 posted in his various threads. One way or another, need fastboot working.
Also try Killing off ADB.exe in Win task manager. Then try again with a fresh one. When Flashing ViperOne 3.5, this helped me tremendously with the RUU.
Give us some details about your OS? Are you using Windows 7/8/8.1? 8 and 8.1 require different drivers.
Sent from my HTC Butterfly s using Tapatalk
Most of your useful adb work will probably be in a custom recovery (TWRP or CWM) at this stage; just saying that whether or not you've got debugging working really has no relevance at this point.
Did you get your phone up and running?
I don't know much about rooting but hear me out. I rooted my device successfully and was using it for a month or two. Decided to change the ROM which stopped letting me go into recovery mode. Whenever I tried to go into recovery mode on my device, it would just start it up normally. I thought maybe if I flash a new 'img' to the device it would fix it. So I used flashify and used a Clockwordmod recovery img which I downloaded on the internet. That's when the issue occurred. It Flashify came up with a sign saying it needs a reboot so obviously I rebooted it but now it doesn't turn on, it gets suck of the white HTC screen and does absolutely nothing! Help me out?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Huss4513 said:
I don't know much about rooting but hear me out. I rooted my device successfully and was using it for a month or two. Decided to change the ROM which stopped letting me go into recovery mode. Whenever I tried to go into recovery mode on my device, it would just start it up normally. I thought maybe if I flash a new 'img' to the device it would fix it. So I used flashify and used a Clockwordmod recovery img which I downloaded on the internet. That's when the issue occurred. It Flashify came up with a sign saying it needs a reboot so obviously I rebooted it but now it doesn't turn on, it gets suck of the white HTC screen and does absolutely nothing! Help me out?
View attachment 3153427
Click to expand...
Click to collapse
Can you get into fastboot by holding down vol- and pwr?
Can you give me the exact link of the cwm image you flashed?
To what partition did you flash the cwm image?
dummie999 said:
Can you get into fastboot by holding down vol- and pwr?
Can you give me the exact link of the cwm image you flashed?
To what partition did you flash the cwm image?
Click to expand...
Click to collapse
I can go into fastboot but lets say I try to do something like reboot the device, it would just reboot but freeze at the loading screen. If I try to open recovery mode, It freezes on a HTC screen which says Entering recovery and nothing happens even after a long time!
Here is my device in fastboot
Not sure which img it was but I googled something along the lines of clockworkmod img download. I don't mind resetting the whole phone if there is a way to do that? and thanks for your interest!
Huss4513 said:
I can go into fastboot but lets say I try to do something like reboot the device, it would just reboot but freeze at the loading screen. If I try to open recovery mode, It freezes on a HTC screen which says Entering recovery View attachment 3158990 and nothing happens even after a long time!
Here is my device in fastboot View attachment 3158995
Not sure which img it was but I googled something along the lines of clockworkmod img download. I don't mind resetting the whole phone if there is a way to do that? and thanks for your interest!
Click to expand...
Click to collapse
Install my cwm from here: http://forum.xda-developers.com/showpost.php?p=53901911&postcount=3, for hboot 1.03
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Please any help is greatly appreciated I have been up now for nearly 20 Hours trying to get this done.
Exactly like this
dugie33 said:
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Click to expand...
Click to collapse
Because you are boote din bootloader mode. ADB can't work when in bootloader mode, only from custom recovery or from a booted rom + usb debug on. Here a nice table I made last week to explain the same thing to another guy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei and sn before posting)
I'm trying to unlock bootloader. Checked all options in dev options like USB debugging and enable unlock bootloader.
Installed all the drivers. Booted into bootloader.
But when trying to see "adb devices", it doesn't show any devices.
For sometime, it shows some kedacom usb driver. I tried googling and tried to uninstall it and use google driver also. Even in device manager, it shows Android Device - Android ADB Interface, but still it shows nothing in list of devices attached in adb.
Also tried this thread - https://forums.oneplus.net/threads/solved-adb-is-not-working.347296/, but still doesn't work. Can someone help me out here?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you have TWRP installed? In that case flashing Super Su or Magisk from within TWRP should get you rooted. If TWRP isn't installed, Check for Funk Wizards thread in the official forum https://forums.oneplus.net/threads/...a-help-thread-ask-your-questions-here.477285/
Also, adb doesn't work from bootloader. It's fastboot in the bootloader. Enter recovery and check then
Seems like your phone is in bootloader/fastboot mode instead of in-rom ADB or TWRP ADB mode. This is the mode you're phone has to be in to be able to flash other recoveries like TWRP which however also requires your phone to be OEM bootloader unlocked (which completely wipes your phone), and from there you enter TWRP recovery using bootloader menu or power plus volume down, and there flash the latest 2.79 SR3 SuperSU to archive root/sudo functionality.
Either that or you actually did activate ADB under development options and accidentally installed the ADB device using the fastboot/bootloader driver instead of the ADB device driver.
When your in fastboot, you need to use fastboot devices as the command and other fastboot commands. You use adb devices command when your using adb, and connected with phone in recovery or booted.
I just installed the drivers that are on the phone when you plug it in in windows and minimal adb and fastboot from xda.
Thank you all. I followed ur inputs and now it worked fine. I installed a custom rom too.
Thanks again.
Akhyll said:
Thank you all. I followed ur inputs and now it worked fine. I installed a custom rom too.
Thanks again.
Click to expand...
Click to collapse
Excellent, enjoy.
Hey guys
I just bought a new Mi 9 Lite and instantanously wanted to unlock it.
so i did all the steps and then tried to connect with mi unlock the first time to see how long the waiting period is
After i booted into fastboot with volume down + power i connected the phone to the computer and it suddenly went black.
Only in the upper corner it showed a cut off text saying: "any key to shut down" -> see attached photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mi Unlock didnt detect it, and neither did Adb fastboot...
Do you know a fix? i really dont want to send it back...
And im pretty certain this was not my mistake, as i tried it multiple times
Same happens when you try to boot into fastboot with "adb reboot bootloader" ?
BTW to see if your device is properly recognized while you are in Fastboot you should use "Fastboot devices" not "adb devices"
Also make sure you installed all required drivers (Qualcomm ones and the drivers you install from within MiFlash)
the reason is windows 10, on 7 it works
k3lcior said:
Same happens when you try to boot into fastboot with "adb reboot bootloader" ?
BTW to see if your device is properly recognized while you are in Fastboot you should use "Fastboot devices" not "adb devices"
Also make sure you installed all required drivers (Qualcomm ones and the drivers you install from within MiFlash)
Click to expand...
Click to collapse
Thanks for your fast answer!
I just tried it again, and adb as well as fastboot devices do recognize the phone.
The blackscreen from fastboot only appears upon opening the mi flash unlock tool... In the exact same moment...
As you said i tried "adb reboot bootloader", but the same happened upon opening the tool.
I couldnt find the qualcomm ones though, didnt know where to install them from...
Btw. if it helps i have Windows 8.1
But havent had Problems with the Mi9 or Redmi 4 Prime unlock (which just now worked fine)
Romancier said:
I couldnt find the qualcomm ones though, didnt know where to install them from...
Click to expand...
Click to collapse
https://androidfilebox.com/tool/qualcomm-qdloader-hs-usb-driver-32-bit-64-bit/
k3lcior said:
androidfilebox....com/tool/qualcomm-qdloader-hs-usb-driver-32-bit-64-bit/
Click to expand...
Click to collapse
Installed it, and even re-installed all the usual drivers. Still, the black screen pops up as soon as i open the unlock tool...
Check if your phone isn't fake one.
This is unusual for an official Xiaomi device.
arvarobert said:
Check if your phone isn't fake one.
This is unusual for an official Xiaomi device.
Click to expand...
Click to collapse
How would i check?
Also its not from china, but from a well known german vendor so guarantee would be no problem. But everything is fine and believable, so i would have no reason to be suspicious.
I guess i will try with another computer next week or something. Maybe its USB 2.0 or something..
At least thats what that thread suggests: https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
Thanks for your suggestions!!!
Romancier said:
How would i check?
Also its not from china, but from a well known german vendor so guarantee would be no problem. But everything is fine and believable, so i would have no reason to be suspicious.
I guess i will try with another computer next week or something. Maybe its USB 2.0 or something..
At least thats what that thread suggests: https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
Thanks for your suggestions!!!
Click to expand...
Click to collapse
Is your phone recognized in device manager when you are in fastboot?
Also i heard there is some bug/incompatibility with Ryzen CPU's, do you have Ryzen or Intel?
k3lcior said:
Is your phone recognized in device manager when you are in fastboot?
Also i heard there is some bug/incompatibility with Ryzen CPU's, do you have Ryzen or Intel?
Click to expand...
Click to collapse
Indeed it is recognizes in adb as well as in fastboot.
It's an old Thinkpad im working on, so its an Intel. I still only have simple Usb-ports.
But im surprised as it has worked with the Mi 9 also a few weeks ago...