So I was following this tutorial: youtube.com/watch?v=jcp4pP5hJIc&list=FLtqiX2Ucq289tObh2PMsn5g&index=1
and I had no problems till 4:21. After the bootloader screen my computer doesn't recognize the device and in the cmd prompt is says "waiting for device." Any help would be appreciated. Thanks!
And in my device manager I have: Android Devices
> My HTC
if that helps.
It's usually safe to stay away from YouTube tutorials for our phone..can you link me to the Rom thread or say the title of the rom
Here is the thread I was following: http://forum.xda-developers.com/showthread.php?t=1952038
It was sucessful up to step 6. And it loaded into bootloader but once in bootloader my device disconnects.
basically when my phone enters the bootloader menu my phone isn't recognized.
You have the att one x right? One sec lemme look at that thread
yup
Did you get the set acid message that was mentioned in step 6?
yea i got everything and everything works but as soon as it rebooted into the bootloader screen my phone disconnects and the computer can't recognize it.
use this app and uninstall the entries for your phone, the drivers probably just need to be reinitialized. the app does not uninstall the physical drivers just how they are setup this will work for any usb devices you are having trouble.
USBDeview v2.21
Related
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
You don't use adb in bootloader. You use fastboot.
Locking the bootloader does not unroot by the way.
crespo80 said:
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
Click to expand...
Click to collapse
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Leauwie said:
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Click to expand...
Click to collapse
This is true, I've used Wugfresh toolkit too but I had some problem...
I've Nexus S 9023, with wug toolkit I had no problem to install driver with its very complete guide, this part can solve your problem but make attention on other function, for example with it I've also unlocked my phone but when I tried to root my device freeze.
So maybe that not all toolkit function will work well on all Nexus S.
Please stop with this toolkit nonsense.
Its not a driver issue at this point. Its the user using ADB instead of fastboot.
Remove this and that when he is just using the wrong command. This is the nonsense you see when all people know is some toolkit.
Yeah, I'm an idiot, that was not a driver issue
it's just because I usually root/unroot/unlock/lock my android phones once in a while (when I first buy and when I sell them), so I always forget some basic procedures and searching through the forums is always a mess, I spent three hours doing that, before posting...
I had forgotten ADB and fastboot weren't the same... anyway, I solved with WugFresh (I didn't know it, thanks for the tip) but I could have solved even with plain fastboot commands, I know
Anyway, I'm surprised to realize that the real stock ROM is more stable than the rooted and deodexed stock ROM I was using before, now the 3G/2G/airplanemode swithing is blazing fast and the performance drops on some games are gone... I'll never figure out this Android world
Thanks for all your help :victory:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL
Venomtester said:
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.
Windows XP makes life easier
chriscerv90 said:
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.
Click to expand...
Click to collapse
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL
Venomtester said:
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.
chriscerv90 said:
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.
Click to expand...
Click to collapse
I know this may sound silly at this point but did you try moving it to a different usb port? I have seen that work before.
AT&T HTC OneX
Android 4.1.1
ViperXL
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
I had to use a different Micro-USB cable to get it work. Try that.
Yeah I actually have tried all those steps. Thanks for the replies guy. I check out that application.
I'm starting to think something is wrong with my HOX
Sent from my HTC One X using xda app-developers app
DvineLord said:
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Click to expand...
Click to collapse
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:
glad you got it fixed, check out his other apps they are life savers and they work how "real" windows apps should work.
I have the same problem
chriscerv90 said:
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:
Click to expand...
Click to collapse
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??
abhilashlinge said:
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??
Click to expand...
Click to collapse
If your on Windows 8 problems will occur but there are methods you need to look into. Windows 7 is your ally.
First Uninstalled the drivers for the device using the program in the previous post. Second, make sure your cable is working correctly. Third, make sure you have the correct drivers for you phone on the computer - - HTC Sync causes problems sometimes. Fourth, plug in the phone in while it's on and let the drivers install correctly. Fifth, place the phone in fastboot and let drivers install. Should work.
Remember sometimes you need to restart your computer and try different USB ports. Some users have said 3.0 ports cause problems.
Good luck.
Sent from my SM-N900A using XDA Premium 4 mobile app
chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
I ws installing a Ruu zip but process got failed and hboot version changed to 1.54.000 . my device is in now relocked status and bootloader is not reconised by hp envy. adb still showing my device my i lost fastboot mode completely. Any solution there???
I already tried several drivers method. Error is something HTCAND4 in driver events log.
What did u do?
Hello,
this is my first post here.
I recently rooted my LG G2 AT&T (D800). It was running D80020y.
Also recently AT&T offered the update to Lollipop (D80030f). I did not accept the update but ATT pushed it anyway when I rebooted the phone.
After that the phone would not boot, it would just go into recovery mode. I have TWRP v2.8.5.1.
Many of the posts addressing situations like this require installing the D800 drivers in computer, and installing adb.
I am trying to solve this problem from a PC running Windows 7 Pro. The PC is not able to see the device.
"adb devices" returns nothing. Not an errror, but an empty list.
When I connect the G2 to the PC, the (windows) device manager lists it twice:
1) Under "portable devices there is an entry "LG-D800", and there I get "this device is working properly", and it uses Microsoft drivers under C:\windows\system32\ and under C:\windows\system32\DRIVERS.
2) Under "Other Devices" there is an entry like before, "LG-D800", with an error sign. When I open that entry I get:
"The drivers for this device are not installed. (Code 28)
There is no driver selected for the device information set or element.
To find a driver for this device, click Update Driver."
Even if I click "update driver" and navigate to the installed LG drivers they won't load. The PC says that nothing was found.
I've tried this also on Windows 8.1 with the same results.
However, with the phone plugged into the PC I can see its contents with Windows Explorer, and I can copy files into it.
I just can't run adb or fastboot.
Of course, I am not able to change to "USB debugging" mode because I can't boot the phone. For the same reason I can change to PTP mode.
So the larger question is how to get my phone back to booting, and I've seen references to that in xda-developers, but all of them use adb,
and for that I need the PC to be able to see my G2.
Thanks!
Asttor
Can you access download mode?
By powering off your phone and then press and hold volume up button and connecting usb from your pc.
Sent from my LG-D800 using XDA Free mobile app
Mustafa Jafri said:
Can you access download mode?
By powering off your phone and then press and hold volume up button and connecting usb from your pc.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know what Download Mode is but I tried what you suggested. It took me to the same place, i.e., it loads TWRP. TWRP seems to be fully functional.
Thanks for answering
Go to LG and download the latest USB drivers and try connecting again.
Thanks for the answer. I had tried that and it did not change the results.
However, I don't really have more time to devote to this. I have spent a lot of hours during the last week.
I thank for the answers though.
How do I close this thread?
Asttor
Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?
I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up
Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated
my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.