So I have a rooted g1 and have successfully setup ADB on my computer, but my problem is getting fastboot to work correctly. I am trying to install files found here via fastboot as it says.
I have read countless threads and guides (including the one posted in XDA) on how to set it up and its just not taking. When I am in command prompt (and my phone is in fastboot mode, USB debugging turned on, etc.) and I go to the SDK tools folder I can type 'fastboot devices' and it shows that I AM connected, but when I type 'fastboot shell' I just get the list of available commands rather than the "#" like all of the guides said I should get.
Any input would be very much appreciated. I have been spending hours and hours of time searching, reading, educating myself, and I still haven't gotten this to work correctly. Anybody out there have any ideas what the problem could be?
Related
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?
You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.
Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.
Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.
There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?
I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse
I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)
The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.
Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.
Hello
I am trying to unlock my bootloader according to the instructions on htcdev.com, when I reach the stage where I have to execute the 'fastboot oem get_identifier_token' command I run into trouble, namely I see the following '...' and then the command hangs.
I have since established the device is visible to fastboot, when I run 'fastboot devices' I get the following, the output remains constant when I run the command with or without superuser privileges (I'm using Arch Linux).
Code:
HT338W902280 fastboot
As far as I can tell it seems my device is recognised by my laptop but that the commands being issued to it via fastboot aren't being received/executed, a conclusion further confirmed by the fact that when I run 'fastboot getvar all' the command hangs with no output being returned whatsoever.
I've tried running the commands as a normal user and as Su and in a couple of different terminals but the end results are identical. If anyone could suggest a solution or needs further information to help I'd be delighted to hear from you.
Thanks in advance!
OK, just got my nexus 6 yesterday, and said goodbye to Samsung..
first, plugged my phone into my windows 10 machine, and it instantly showed up in windows explorer, and was able to see all the directories on my phone, so that was good.
I then followed the instructions for installing the ADB/Fastboot installation stuff from here,
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Opened the command prompt, typed in these commands, cd Desktop/android-sdk-windows/platform-tools
adb version, and adb version showed up just fine.
Turned off my phone, held down volume and power and entered fastboot mode, but after typing the proper commands, my phone serial number doesnt show up..
I have enabled developer mode, turned on USB debugging, enabled OEM unlock, but still no serial number shows up.
I'm not a rookie, and understand how to use ADB, but I am afraid that windows 10 is the issue..
Anyone have any suggestions?
Thanks for your input:good:
Mod Edit:
Solution found and thread closed at OPs request
You can't use adb in fastboot mode. You can only use fastboot in fastboot mode. Adb only works in android or recovery
thanks, I got it sorted out by installing this..
http://forum.xda-developers.com/showthread.php?t=2588979
man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason
You can't use adb commands when in fastboot mode and vice versa.
knives of ice said:
man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason
Click to expand...
Click to collapse
I have same problems. Please explain how you have solved. Which drivers the Mi Mix needs in fast boot mode?
basically, you have to watch your device manager for the ANDROID to pop up and it should have a yellow exclamation. you have to fix the drivers, but the problem is at least in my case you have to complete and fix the drivers before the mix puts itselt out of fastboot and into charging (which it does quite quickly when not connected)
install this:
http://forum.xda-developers.com/showthread.php?t=2588979
and follow the guide that he posts in the pictures on what you need to change
here
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
as soon as you have the drivers fixed windows will tell you and the mix will stay connected