Database Info

Issue with unlocking bootloader

i did all necessary stuff according to this tutorial: (windows 7, 64 bit)
http://forum.xda-developers.com/showthread.php?t=1583427
just after typing: fastboot oem get_identifier_token
cmd says: <waiting for device>
and now it just freezes at this point, i don't get any further
anybody got some advice?

garldehildehar said:
i did all necessary stuff according to this tutorial: (windows 7, 64 bit)
http://forum.xda-developers.com/showthread.php?t=1583427
just after typing: fastboot oem get_identifier_token
cmd says: <waiting for device>
and now it just freezes at this point, i don't get any further
anybody got some advice?
Click to expand...
Click to collapse
Sure. This happened to me at first. Try connecting your phone to a different USB port? Did you get a taskbar notification that a device had been connected? (Did you here the little dings? ha)
When cmd says waiting for device, it either means that your phone isn't in fastboot (which I assume it is, since you were following the directions), or that the device isn't connected.
Also, did you install the software package HTC sync? It's a fairly large download, but it might be a necessary one to get the required drivers to connect the phone.
Let me know if this helps.

Make sure you've installed the usb drivers required by selecting the check box for USB in the Extras.

Yep I got this error too and just had to install HTC sync from the HTC website to fix it. Easy peasy

Just use this guy's toolkit. Worked on my U.S one S.
http://forum.xda-developers.com/showthread.php?t=1604677
Sent from my HTC VLE_U using xda premium

well i downloaded this htc-sync stuff you said and everything just works fine
thanks a lot guys!!

[Q] Help root on 2.20 plz

hi i recently bought a htc one x from att and i want to root it.. so i downloaded everything and i ran the .bat file so far everything went ok but when i pres enter or any key while it rebooted to fastboot i get stuck all it says is waiting for device please help me i need to root

install the correct drivers for your operating system.

mbh87 said:
install the correct drivers for your operating system.
Click to expand...
Click to collapse
i have already done so from the begining btw im on windows 8... i installed 32bit

if it's stuck on waiting for device then the drivers for fastboot aren't installed.

mbh87 said:
if it's stuck on waiting for device then the drivers for fastboot aren't installed.
Click to expand...
Click to collapse
Try running the latest version of HTC Sync (installer). This will usually ensure you have the latest drivers installed. Another thing to consider is that some of these drivers may not be tested on Windows 8, so you may have to do this on a Windows 7 computer. Just throwing some thoughts out there

Ahhh... Another windows 8 user....
Win8 has a problem with drivers. You won't be able to root your phone with Win8. You'll have to dual boot/liveCD Ubuntu, get rid of windows8 crap and install Windows 7. Then you'll be able to root your phone no problem.
For future use of fastboot drivers, I would say that if you like Win8 then dual boot with Ubuntu and use Ubuntu to root and what not on your phone. If you don't like Win8( which I hope you don't), then go find a copy of Win7 and get rid of the crap you already have(win8). If you don't have the money for a $75 copy of Win7, dual boot Ubuntu.
Sent from my One X using xda app-developers app

[Q] Pull data with a smashed screen

Just after updating to lollipop I completly smashed my screen. It doesn't show any usefull information and touch is not working.
Since I'm not in the mood to buy a new screen because I already bought a Note 4, I wanted to pull the data from the phone. It's pin protected but fastboot is still working, adb however is not.
After reading up a bit I found that going into cwm recovery I would still be able to acces adb.
So I with fastboot I booted cwm recovery (fastboot boot recovery.img) only to find that adb still won't find my devices.
Is there any way left to pull the data from my phone? I also have acces to a external keyboard/mouse with a otg cable but that won't seem to work either.

Boot into recovery and with your device plugged into your pc go to device manager. Do you see your device there?
Sent from my Nexus 9 using XDA Free mobile app

In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.

Wiisper said:
In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.
Click to expand...
Click to collapse
Google 15 second adb install xda. It has drivers as well as sets up adb and fastboot on your pc which you'll need if you can get your device detected
Edit, also download the twrp image from here and boot into it fastboot boot twrp.img (use the full name of the twrp image file) cwm sucks. http://techerrata.com/browse/twrp2/hammerhead
Sent from my Nexus 9 using XDA Free mobile app

I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.

Wiisper said:
I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.
Click to expand...
Click to collapse
Np, glad it seems to be working
Sent from my Nexus 9 using XDA Free mobile app

Okay got all the files from the phone!
Thanks for helping.

Recovery mode seems to clobber the USB driver on Windows 10

Similar questions to this have been asked before but got no replies so, in desparation, am asking again.
Bought my phone second hand. On starting, it shows the Vodafone logo so assume it's branded.
About Phone -> Software Information shows:
Android Version: 2.3.5​HTC Sense version: 3.0​Software number: 2.10.161.5​
HBOOT shows:
*** UNLOCKED ***​SAGA PUT SHIP S-ON RH​HBOOT-2.00.0002​
Now for the problem:
I'm trying to set S-OFF and root the phone but my PC, running Windows 10, is unable to communicate with the phone when it's in Recovery mode.
The entry for My HTC under Android USB Devices in Device Manager disappears once I start the phone in Recovery mode and connect it to my PC via a USB cable.
At this point Device manager on my PC shows under USB Controllers an entry for an unknown USB Device (Device failed enumeration) and the Hardware Ids show as USB\UNKNOWN.
I'd really appreciate someone familiar with this area throwing some light on what could be going on here and perhaps giving me some pointers on how to resolve this.

there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE

Layer_DE said:
there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE
Click to expand...
Click to collapse
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.

bacoms said:
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.
Click to expand...
Click to collapse
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices

Layer_DE said:
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices
Click to expand...
Click to collapse
If I can drum up any enthusiasm to continue, I'll try and borrow a PC running Windows 7 and try again.

oneplus one hardbrick doesnt show as QHSUSB_BULK,unable to install qualcom2012 driver

I bricked my Oneplus One while flashing CM11 via fastboot using manual commands on cmd.
After giving all the commands for fastboot flash, during reboot the phone did not reboot and it just got bricked.
The big issue with the brick is that the phone is not being recognized as QHSUSB_BULK but it is showing as Unrecognised Device ... i am not able to update the drivers to qualcom 2012 the windows is giving an error as "Windows was unable to install your unknown device".
I've turned on the Testing Mode to install unsigned drivers and the gpedit policy to stop windows automatically installing drivers is also enabled. Also i've changed the setting in control panel Devices and printers -> Device Installation Settings to "Let me choose what to do "and "never install driver software from windows update".
Still the problem persists Please HELP Me.

praik96 said:
I bricked my Oneplus One while flashing CM11 via fastboot using manual commands on cmd.
After giving all the commands for fastboot flash, during reboot the phone did not reboot and it just got bricked.
The big issue with the brick is that the phone is not being recognized as QHSUSB_BULK but it is showing as Unrecognised Device ... i am not able to update the drivers to qualcom 2012 the windows is giving an error as "Windows was unable to install your unknown device".
I've turned on the Testing Mode to install unsigned drivers and the gpedit policy to stop windows automatically installing drivers is also enabled. Also i've changed the setting in control panel Devices and printers -> Device Installation Settings to "Let me choose what to do "and "never install driver software from windows update".
Still the problem persists Please HELP Me.
Click to expand...
Click to collapse
Okay,calm down!
Which windows are you using? Are you sure you're not able to boot to fastboot mode?

I'm using windows 8.1 64bit version.
Mr.Ak said:
Okay,calm down!
Which windows are you using? Are you sure you're not able to boot to fastboot mode?
Click to expand...
Click to collapse
When i press power button + vol. up for 10sec the windows recognizes the device but shows it as Unknown Device and then the Driver Update is not being done. What should i do?

praik96 said:
What should i do?
Click to expand...
Click to collapse
Did you even read my question?
Sent from my A0001 using Tapatalk

faced that too a while ago, try to use win 7 ( best is xp ) with driver signature thing off, now google hardbrick opo recovery and u will find a website with the steps along with a mi flaasher tool for windows , now download the color os hradbrick recovery zip and also the latest cos 13.1.2 fastboot zip.
U willl eb able to bring back ur opo to life by using that color os zip along with the mi flasher tool but then the screeen behaves really weird ( happened to me )
but everything got normal after i flashed the cos 13.1.2 zip by fastboot

Kartike said:
faced that too a while ago, try to use win 7 ( best is xp ) with driver signature thing off, now google hardbrick opo recovery and u will find a website with the steps along with a mi flaasher tool for windows , now download the color os hradbrick recovery zip and also the latest cos 13.1.2 fastboot zip.
U willl eb able to bring back ur opo to life by using that color os zip along with the mi flasher tool but then the screeen behaves really weird ( happened to me )
but everything got normal after i flashed the cos 13.1.2 zip by fastboot
Click to expand...
Click to collapse
That's why I was asking him about which windows he use.Windows XP is hassle free for this driver's issue.
Sent from my A0001 using Tapatalk

Mr.Ak said:
That's why I was asking him about which windows he use.Windows XP is hassle free for this driver's issue.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm using windows 8.1, earlier i mentioned it in the title.

praik96 said:
I'm using windows 8.1, earlier i mentioned it in the title.
Click to expand...
Click to collapse
find a Xp system and you'll not have any issues.
Sent from my A0001 using Tapatalk

Mr.Ak said:
find a Xp system and you'll not have any issues.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
If i install xp on my laptop via dual boot and what drivers will i need other than Qualcom 2012 ? or the xp's inbuilt windows driver will do the trick along with Qualcom 2012 drivers?

praik96 said:
If i install xp on my laptop via dual boot and what drivers will i need other than Qualcom 2012 ? or the xp's inbuilt windows driver will do the trick along with Qualcom 2012 drivers?
Click to expand...
Click to collapse
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk

You should download One Plus USB drivers.
If you prefer you should use One Plus Toolkit.

Mr.Ak said:
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Can anyone direct me to safest way to dual boot windows xp s3 on windows 8.1 already installed with UEFI mode?
I dont want to end up with screwing my laptop too.

praik96 said:
Can anyone direct me to safest way to dual boot windows xp s3 on windows 8.1 already installed with UEFI mode?
I dont want to end up with screwing my laptop too.
Click to expand...
Click to collapse
Youtube
Sent from my A0001 using Tapatalk

Mr.Ak said:
Yes qualcomm 2012 drivers will work just fine.
Make sure you launch the tool with administrator rights.It may take a few refresh and try before flashing starts but it works.
You don't need adb drivers here because this tool uses usb debugging port instead of fastboot/adb.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Tip1: Use correct usb cable.
I thought the error was is usb drivers but it seems that the error was in usb cable. I lost my oneplus usb cable quite a while ago and was using third party usb cable for data transfer and charging. Tried to connect the bricked OPO with that cable only.
Just ought to try connected with different cable here used Amazon Basics micro usb cable and VOILA!!! The drivers were automatically installed by windows this time.It worked on current windows 8.1. Dont know it was luck or really dumb choice of USB cable.
But thank you very much for helping me out.