Database Users

computer can't find phone in fastboot mode

Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon

Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net

Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.

What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).

kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.

Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!

Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.

i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you

mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.

glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?

also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on

http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode

mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App

which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?

mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.

Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers

noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?

deleted!!!!!!!!!!

I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.

Okay, so put it in fastboot mode and try to run a fastboot devices real quick.

[Q] Problems with Download Mode

Hi guys
I bricked my galaxy Spica a while a go und it was lieing around for a while no. I thought i could give it a try to unbrick it again.
The situation at the moment:
When I start it, bootloop.
Recovery isent working.
I can get it to download mode, but if i connect it to my win7 computer per usb, the pc doesent get a connection. The drivers are installed, but Odin cant connect to it.
I allso tryied AdamOutlers one click unbrick, but dident get a connection eather. http://forum.xda-developers.com/showthread.php?t=1153310
I also tried to get it connected over ADB. With the command ADB devices I ony get "list of al atached devices" followed by nothing.
Anybody here has an idea what else i could do to get the phone connected to the computer? Or do you think its a permanent brick?
Greetz Hilmy

Did you try remove battery then after some minutes put it back and try download mode?

I tried that to. Dident help.
Any other ideas?

Hilmy said:
Hi guys
I bricked my galaxy Spica a while a go und it was lieing around for a while no. I thought i could give it a try to unbrick it again.
The situation at the moment:
When I start it, bootloop.
Recovery isent working.
I can get it to download mode, but if i connect it to my win7 computer per usb, the pc doesent get a connection. The drivers are installed, but Odin cant connect to it.
I allso tryied AdamOutlers one click unbrick, but dident get a connection eather. http://forum.xda-developers.com/showthread.php?t=1153310
I also tried to get it connected over ADB. With the command ADB devices I ony get "list of al atached devices" followed by nothing.
Anybody here has an idea what else i could do to get the phone connected to the computer? Or do you think its a permanent brick?
Greetz Hilmy
Click to expand...
Click to collapse
May be you need to make youself a jig!!!!

All you should need is download mode after a full charge (!) and then either do a full reset (use the options in Odin to reset apart from EFS clear ;-) ) and then you should be able to use download mode properly.
For the drivers, how does it show up in Device Manager?? I had this myself a while back and it was simply that the drivers didn't match how it was showing up. After searching around for a while I found various packages on samdroid.net and the right ones for me then worked fine. Either the Kies ones, the google ones or the Nexus S drivers from tom3q's CM7 build...

Samsung drivers

Hi .
does anyone know other drivers i can use for the i9505 device?
The drivers installed from keis do not work under Recovery mode from TWRP .
When i connect my device to my windows 8 machine, on device manager it complains that it cannot find the drivers for the phone yet when the device is booted into a working rom of any kind, it detects it?
Thanks in advance

Google, Samsung usb drivers.

usb drivers
jonneymendoza said:
Hi .
does anyone know other drivers i can use for the i9505 device?
The drivers installed from keis do not work under Recovery mode from TWRP .
When i connect my device to my windows 8 machine, on device manager it complains that it cannot find the drivers for the phone yet when the device is booted into a working rom of any kind, it detects it?
Thanks in advance
Click to expand...
Click to collapse
Ok here you go, the official Samsung usb drivers for your phone: http://www50.zippyshare.com/d/74240052/114177/Samsung_USB-Driver_for_Mobile_Phones-1.5.27.0.exe (direct download link)
Install it and reboot the computer, then plug usb cable in and wait til windows recognizes .your phone.
Good luck!

Misterjunky said:
Ok here you go, the official Samsung usb drivers for your phone: http://www50.zippyshare.com/d/74240052/114177/Samsung_USB-Driver_for_Mobile_Phones-1.5.27.0.exe (direct download link)
Install it and reboot the computer, then plug usb cable in and wait til windows recognizes .your phone.
Good luck!
Click to expand...
Click to collapse
tried the above steps and did not work
windows still cant detect my phone.
edit: even on my windows 7 laptop it wont detect it

Did you kill or uninstall Kies? If so, try a different cable.

Might be Windows 8 ( wouldn't be surprised ) try running kies in Win7 or XP mode etc? Have you allowed USB debugging?

i've tried a different cable and even a different computer all together where i installed win7 on that laptop only a week ago so still fresh. im about to try it on my imac .
If this doesnt work then surely the drivers in question are not correct!
will find the mac drivers

i've tried a different cable and even a different computer all together where i installed win7 on that laptop only a week ago so still fresh. im about to try it on my imac .
If this doesnt work then surely the drivers in question are not correct!
will find the mac drivers.
edit: how can u enable debug mode from recovery?

jonneymendoza said:
i've tried a different cable and even a different computer all together where i installed win7 on that laptop only a week ago so still fresh. im about to try it on my imac .
If this doesnt work then surely the drivers in question are not correct!
will find the mac drivers.
edit: how can u enable debug mode from recovery?
Click to expand...
Click to collapse
Sorry I've read it wrong, didn't realize what TWRP was till I did a bit of research... I suggest emailing TeamWin Projects about it, theirs a few people on their with the same problem, hope you get it sorted.
http://www.teamw.in/project/twrp2/182

Bricked Elife E7, Human Interface Device (HID) Detection Help

Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:

Steps Parku said:
Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:
Click to expand...
Click to collapse
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck

Still Not Helpful.
andresplata94 said:
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck
Click to expand...
Click to collapse
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks

did u fix it??

U can fix ? I have the same problem since three weeks and nothing... this a a sh*t... only recognized by HID... In other ocassion before of this, i can flash my Gionee but now i cant:crying:

Another one here who saw how the phone bricked after being flashed with GnQc, now when I plug the Usb on the Pc or with wall charger, the red light keep lit and it seems like it will like this forever. I am thinking of trying to get out the screen and disconnect the battery, seems like the phone is stuck on some strange mode.
Thanks.

This feel that not have solution....

Can any one fix it ?

i also got stuck . have given to gionee care they are unable to figure what was the actuall problem

Steps Parku said:
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks
Click to expand...
Click to collapse
the problem for me is that it have recovery stock english(e3) and i can't do anything...
anyone fixed the problem? i have my gionee bricked....

Any body have the driver for BP TOOLS mode on nexus 6P？

connect QPST need this driver

eudemonky said:
connect QPST need this driver
Click to expand...
Click to collapse
I'm also searching for this. I will update here if any finding.

I got the drivers installed for the 3 devices that appear when booting the device in BP Mode.. I got them from a gsm-forum post, you can google "first in the world nexus 6p" to find it, sorry I would have made your life easy but I can't post links yet. You have to disable driver cert security for them to install, and choose manually which driver to install for each of the 3 devices. I'm still not able to connect using any of the Qualcomm tools though, been searching for a solution for quite some time now.