Develop Bugs

ADB doesn't work for my Galaxy Nexus

Hi,
I realize a lot of people might have the same problem as I have, but haven't found the answer after searching for many hours. So here's my problem:
windows vista x64
installed android SDK and all related drivers
GN is recognized with correct driver in both fastboot mode and regular "on" mode.
GN is recognized as a device in regular on-mode with 'adb devices'
GN is recognized as a device in fastboot mode with 'fastboot-windows devices'
HOWEVER, when GN is put into fastboot mode, NO devices are found with 'adb devices' even though the icon for 'safely removing hardware' pops up with 'Android ADB Interface', which means the driver is correctly installed.
Someone please help explain why the device is not recognized by 'adb devices' command under fastboot mode even though it's recognized by the computer!
Summary:
GN is found with 'adb devices' for normal boot, but GN is not found under 'adb devices' for fastboot mode. I have reinstalled the android ADB driver, but still the same problem.
I am stressed out! Please help me

I have noticed exactly what you are talking about however what I have found is that it doesn't seem to need to be able to respond to the adb devices command. I was still able to unlock,root and flash multiple different boot.img and radio.img files through fastboot without the computer returning the device while in fastboot. Hope this helps.
Justin
P.S. while you are in fastboot mode it seems you may be looking for something different than standard adb commands. Fastboot is primarily used in this situation so a command for you will typically look something like this"
fastboot-windows flash boot boot.img
or
fastboot-windows flash radio radio.img (the radio.img and boot.img files used in these examples you would want located in the same folder as fastboot-windows)
if you want to try the software out without flashing it "permanently" try:
fastboot-windows radio radio.img (just forget the flash portion)
for unlocking the bootloader the command will look something like this:
fastboot-windows oem unlock

ADB isn't used in fastboot mode, fastboot.exe is.
ADB is for when the phone is running Android or recovery only.

Phone doesn't recognize ADB in fastboot
Phone doesn't recognize ADB in fastboot - have used every conceivable method - downloaded Samsung drivers. Downloaded PDANet. Uninstalled Samsung and tried Naked Samsung. I got the phone unlocked. But I CANNOT get the PC 64 to recognize ADB when I am in fastboot. HELPPPPPPP. I've been working on this for TWO DAYS, and it is RUINING my Christmas holiday.

Have you tried the driver installation/troubleshooting section of this post?

Unfortunately, yes. I tried the Samsung drivers. Then I tried the PDANet. I also tried the Samsung naked drivers. I was sure that MSKIPS toolkit was going to work, but when I typed in "2" for rooting, NOTHING happened. I'm at my wits end.

HeathCliffR said:
Phone doesn't recognize ADB in fastboot - have used every conceivable method - downloaded Samsung drivers. Downloaded PDANet. Uninstalled Samsung and tried Naked Samsung. I got the phone unlocked. But I CANNOT get the PC 64 to recognize ADB when I am in fastboot. HELPPPPPPP. I've been working on this for TWO DAYS, and it is RUINING my Christmas holiday.
Click to expand...
Click to collapse
Of course it doesn't.
AS STATED MULTIPLE TIMES IN THIS THREAD, YOU MUST USE FASTBOOT.EXE.
Please, read thread then reply.

When phone is turned ON - use adb
When in FASTBOOT mode - use (surprise surprise) fastboot

When phone is turned on or in recovery - use adb (check it with "adb devices" ,without " in cmd)
When in FASTBOOT mode - use fastboot (check it with "fastboot devices" ,without " in cmd)
In order to work fastboot you must have the fastboot.exe preferably in the same folder with adb

Try this
I tried installing PDAnet but no Joy.. but went to device manager and selected adb drivers and samsung from the list and that did the trick...

[Q] HTC Desire HD not recognised - can't install custom ROM's problem with fastboot

So basically i followed this guide - wiki.cyanogenmod.org/w/Install_CM_for_ace
Let's start from the first part wiki.cyanogenmod.org/w/Install_CM_for_ace
I plug in phone, i can see it in my PC as D drive but nothing more, after command "fastboot devices" i get 0 info - just like no devices were connected, but after i write "adb reboot-bootloader" my phone goes into this white screen. After this message about unrecognised device connected to USB appears. From now i can't use command "astboot flash recovery your_recovery_image.img"
I also has question, what does command "fastboot oem get_identifier_token" stands for? After writing this command i get info "waiting for device....".
I've also has question - why I unlock phone? What does it stands for? Does unlock means the same as rooting phone?
My System is Windows 8.1 64 bit.
Maybe i should install some HTC drivers or something like this? I installed HTC Sync, then uninstalled it, so just pure drivers should be left on PC but it still do not help me :/
USB debugging is on.

Fastboot issue on windows 8.1
I'm experiencing exactly the same problem as you. I'm on windows 8.1 and am unable to use the fastboot command. Have you been able to find a solution to it? Or have you been able to root your mobile? The HTC Desire HD community here seems to be not very helpful since your thread is months old and nobody has cared to help you with it.

maciek1o3s said:
So basically i followed this guide - wiki.cyanogenmod.org/w/Install_CM_for_ace
Let's start from the first part wiki.cyanogenmod.org/w/Install_CM_for_ace
I plug in phone, i can see it in my PC as D drive but nothing more, after command "fastboot devices" i get 0 info - just like no devices were connected, but after i write "adb reboot-bootloader" my phone goes into this white screen. After this message about unrecognised device connected to USB appears. From now i can't use command "astboot flash recovery your_recovery_image.img"
I also has question, what does command "fastboot oem get_identifier_token" stands for? After writing this command i get info "waiting for device....".
I've also has question - why I unlock phone? What does it stands for? Does unlock means the same as rooting phone?
My System is Windows 8.1 64 bit.
Maybe i should install some HTC drivers or something like this? I installed HTC Sync, then uninstalled it, so just pure drivers should be left on PC but it still do not help me :/
USB debugging is on.
Click to expand...
Click to collapse
make sure you have a working usb cable
1) your phone must be unlocked to flash a new rom
2 )Our phones are locked by HTC to protect the phone from unwanted things
3) HTC official web site helps you to unlock your phone ,follow the instructions as they have mentioned,it is too easy
http://www.htcdev.com/bootloader
every thig is explained here
3) for root try this
http://forum.xda-developers.com/showthread.php?t=2169515
4) download rom you want and copy it to sd card
shut down your phone ,push power+volume down button
on bootloader screen you must see UNLOCKED
choose fastboot
plug it to PC
you LL see fastboot Usb
On PC ,copy and paste the boot.img file of the rom to fast boot folder (it is in the nameofrom.zip )
open a command windows on this folder
write fastboot devices
fastboot flash boot boot.img
Enter
:good::good::good:here are the some links and videos to help you on flashing boot.img
http://www.youtube.com/watch?v=5xVl2dBTnmI
http://d-h.st/6LC
4) then go recovery on phone
wipe data factory cache dalvik cache and install zip from sd card
choose the rom
and restart your phone
5) identifier_token is kind a code which HTC sends you , it belongs your phone to unlock your phone
6) Root and Unlock are different things also there is another guy, it name is S-off
7) Windows 8 maybe will have problem , but windows 7 and windows xp are OK
8) make sure close antivrus and firewall
I hope these will help you

[Q] adb/fastboot can't find device in bootloader, but they can do it when booted

Dear all,
I have worked on building Android from source code for few weeks. It used to be fine to me with my galaxy nexus, I can connect to my device via adb and fastboot and flash either the factory ROM or ROM built by me into my device. However, when updating the phone into 4.3, I forgot to extract drivers into the built directory and flash the built image into my device. Is surely can't work, and the screen turn off once "Google" is shown, so I would like to reflash it back to other image. However, my laptop can't recognize my Nexus S anymore in the bootloader. I can use "adb shell" once the device is normally booted (even without screen), but once I type "adb reboot bootloader", the connection is lost! Both "adb and fastboot devices" show nothing....
I have searched the forum and stackoverflow all day but can't find helpful information. There are many threads talking about unable to connect devices but 70% of them are driver-related issue and 30% of them, ex: sudo adb, just don't work for me. I think I am not facing the driver issue because I still can use "adb shell" once the device is normally booted (not in bootloader mode). Moreover, I also tried few debrick tools contributed by xda community but with no luck.
I am wondering if there is any way that I can reflash image to my device without accessing it in bootloader mode? (ex: push image in to device via adb shell when device is normally booted?). I am also wondering if there is any way to fix this problem. Any suggestion is very appreciated!: crying:
Thanks
Yu-Chih
ps. the most closed thread I found is called "ADB can discover devices but not fastboot" in stackexchange (I am not allowed to post the link)
but it seems there is no answer in this thread

I'm not a expert, but do you know how is the DD command ?,
I wonder, is you can DD the boot loader into the nexus partition?

chongns said:
I'm not a expert, but do you know how is the DD command ?,
I wonder, is you can DD the boot loader into the nexus partition?
Click to expand...
Click to collapse
Thanks for the reply. I am not sure what I should do with dd command? Could I use it to reinstall the drivers into device?
by the way, I found there is a error showing up in the bottom of screen in fastboot mode, "Fastboot Command Read Error -2147483647", and many closed threads (sorry that I am not allowed to post url because I am new). Some suggests are to reinstall drivers (even thought I don't get if they mean reinstall the usb driver for laptop or for android), but it seems not solved yet.
Yu-Chih

Dear all, I think I have tried all potential solution about "fastboot command read error -2147483647" that I can find at internet......
Here is what solution I have tried:
1. sudo the command of adb and fastboot
2. update drivers
3. update sdk
4. use another cable
5. install other drivers (win7), ex: naked driver
6. Wug's root kit
What I can't try:
1. enable USB debug mode at phone (because I don't have screen of it but only adb shell)
2. remove(uninstall) other software such as PDA net...etc (I don't try this because my system is clean-installed win7/MAC/ubuntu)
I think this problem is kind of common but my situation seems slightly different from others, that I can find the device when my device is normally booted but I can't recognize it when it is rebooted into bootloader (showing "fastboot command read error -2147483647" at bottom). I am starting to believe it either be the problem that I don't activate the USB debugging in my new flashed image (but I can connect it with adb when the device is normalled booted) or the usb driver in my device is broken.
Anyone has any idea.....:crying:
eddyxdxda said:
Thanks for the reply. I am not sure what I should do with dd command? Could I use it to reinstall the drivers into device?
by the way, I found there is a error showing up in the bottom of screen in fastboot mode, "Fastboot Command Read Error -2147483647", and many closed threads (sorry that I am not allowed to post url because I am new). Some suggests are to reinstall drivers (even thought I don't get if they mean reinstall the usb driver for laptop or for android), but it seems not solved yet.
Yu-Chih
Click to expand...
Click to collapse

Dear all,
This is my latest update. I wipe out the whole system of Ubuntu and Win7 and restart everything from the first step. Magically, the new Win7 + Wug's root kit can successfully flash new image into my phone. But also magically, the ubuntu system faces the same issue as I described (no connection in bootloader with the error code but connection is fine after the device is booted). The bright side of this is that I am finally able to try other solutions, e.g., enabling debugging mode, but the sad part is that I still get no luck at Ubuntu and MAC.........can't believe it works at Win7 but not at Ubuntu and MAC.....
Yu-Chih
eddyxdxda said:
Dear all, I think I have tried all potential solution about "fastboot command read error -2147483647" that I can find at internet......
Here is what solution I have tried:
1. sudo the command of adb and fastboot
2. update drivers
3. update sdk
4. use another cable
5. install other drivers (win7), ex: naked driver
6. Wug's root kit
What I can't try:
1. enable USB debug mode at phone (because I don't have screen of it but only adb shell)
2. remove(uninstall) other software such as PDA net...etc (I don't try this because my system is clean-installed win7/MAC/ubuntu)
I think this problem is kind of common but my situation seems slightly different from others, that I can find the device when my device is normally booted but I can't recognize it when it is rebooted into bootloader (showing "fastboot command read error -2147483647" at bottom). I am starting to believe it either be the problem that I don't activate the USB debugging in my new flashed image (but I can connect it with adb when the device is normalled booted) or the usb driver in my device is broken.
Anyone has any idea.....:crying:
Click to expand...
Click to collapse

fastboot never start after update to android 6

Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!

Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english

No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.

bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?

krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.

bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.

i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?

bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.

Here is screenshot from minimal adb...
Phone must be in MTP mode.

And here is phone in fastboot

Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.

bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.

TWRP installed but no OS. Udev problem?

Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
Code:
I: cannot find file /sys/class/android_usb/android0/idProduct
I: cannot find file /sys/class/android_usb/android0/idVendor
When is in appear/disappear loop:
Code:
I:[MTP]Mtpserver::run fd: 20
E:[MTP] request read returned -1, errno: 5 , exiting MtpServer::run loop
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things

Shugui said:
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
When is in appear/disappear loop:
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Click to expand...
Click to collapse
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.

NickTheSickDick said:
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
Click to expand...
Click to collapse
Commands "adb devices" and "fastboot devices" return no devices founded.
Click to expand...
Click to collapse
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Have you tried different machine to do adb devices/ fastboot devices?

ArcOnFire said:
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Click to expand...
Click to collapse
You right
ArcOnFire said:
Have you tried different machine to do adb devices/ fastboot devices?
Click to expand...
Click to collapse
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.

Shugui said:
You right
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Click to expand...
Click to collapse
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.

mArIuS% said:
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
Click to expand...
Click to collapse
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back

Shugui said:
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Click to expand...
Click to collapse
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess

Fahrilubis said:
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Click to expand...
Click to collapse
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure

Shugui said:
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Click to expand...
Click to collapse
Thx brother solv