I just got the NS, coming from the Vibrant. I installed the sdk and drivers. Adb see's my device because I get a serial # when I "adb devices" but when I go to fastboot oem unlock I get "waiting on device".
Do you have the phone in fastboot mode? Turn phone off hold volume up and power on...
Sent from my Nexus S using XDA App
make sure you have the fastboot file in your tools directory and that you are in the tools directory while trying to give the command. that is all I know to try.
I do have a fastboot file in the tools and I do have the phone in fastboot mode. Could the "path" have anything to do with it? For some reason I didnt have a path file under variables so I just created one. I'm assuming since I get a serial # that the drivers and path are correct.
Yeah not sure since it recognized device...
Sent from my Nexus S using XDA App
debug mode?
I'm on windows 7, not sure if that has anything to do with it or not. For the life of me I cant figure out what is going on. I've used adb extensively only g1, never needed it on my vibrant but it has something to do with the drivers I think.
I'm in debug mode
did you update your SDK?
and is your enviorment variable PATH along the lines of
C:\...\...\AndroidSDK\platform-tools
Click to expand...
Click to collapse
If you think you may be having trouble with your path, just cd to the folder where you have fastboot and try it there.
EDIT: I just ran into the same problem when trying to flash the cm7 boot image with ext4 hack. I had booted into bootloader using quick boot. I rebooted, powered off, and powered on with volume up button and everything worked fine. Not sure why this happened but I got the same "waiting" issue you had.
I got it to work. I uninstalled the drivers, put the device in download mode then plugged it in THEN installed the drivers. All is well, root, superuser and 2.3.1. Thanks to everyone who posted to help out.
If your phone is in fastboot mode, you will NOT get your serial number when you do a "adb devices".
So there you go, you're not in fastboot mode.
Turn the phone off.
HOLD volume up and then HOLD power.
You'll get to the bootloader. THAT is fastboot mode.
Now type "fastboot devices" and you'll see your serial number come up, then you can do "fastboot oem unlock".
FYI: adb command ONLY works when your phone is on and booted up OR in recovery.
fastboot command ONLY works in Bootloader.
Related
Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.
ejnahuj said:
Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.
Click to expand...
Click to collapse
Hello
1. you need to install a ROM with fastboot the most common is europe + fastboot (KDZ) ROM.
http://www.mediafire.com/?96nu9lb6afx22a7
2. once its finished phone will reboot, then fast login into fastboot mode CAMERA + POWER
3. You are missin 1 thing, OEM usb drivers not GOOGLE usb drivers as some tutorial says, those are just for Android Developer Phones (ADP), Nexus One, and Nexus S.
LG_Android_USB_Driver_Rebuilt
http://www.mediafire.com/?pbigrb8cimmxa4d
* these drivers are for your pc to recognize your phone in fastboot mode, they are not the normal LG usb drivers
4. for install the drivers abouve follow these smll tutorials
* if using windows 7:
http://developer.android.com/sdk/win-usb.html#Win7
* if using windows XP:
http://developer.android.com/sdk/win-usb.html#WinXp
once is installed plug your phone in fastboot mode to your pc, now your pc has to recognize your phone wait until it finish installing the drivers and read it properly
5. unzip the new ROM files into C:\*SDK\tools
6. open CMD Terminal and go to C:\*SDK\tools, type:
cd C:\*SDK\tools
7. once in, type
fastboot flash recovery recovery_clockwork_3.x.x.x_swift.img"
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
*Just in case it drops you an error AdbWinApi.dll missing here is the file. place it in C:\*SDK\tools and try again
http://www.mediafire.com/?3s3z5uym2rw5r7u
Any other question PM me
fastboot "waiting for device"
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance
murthy.krishna00 said:
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance
Click to expand...
Click to collapse
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App
Quinny899 said:
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Can you please clearly explain it, I couldnt get that. The prob was even though I installed the diver fastboot cannot detect the device..
Turn the phone off normally and when you'from holding down power to turn it on, also hold down camera until you get a black screen.
Sent from my GT540 using XDA App
So I am having a lot of problems with trying to root my nexus 7. I'm pretty sure it boils down to a driver issue but I'm not sure. I have tried installing the correct drivers over and over again also uninstalling other hardware manufacturers drivers and I cannot get adb to recognize my device when it is shut off and in the boot loader.
When the tablet is on and I have debugging on, adb shows up and is recognized, however my problem is that whenever I reboot into the boot loader I lose adb recognition. So therefore I can't root or do anything else. Fast boot commands work fine its only the issue with adb.
If anyone has any suggestions as to what I can do I would really appreciate it. I don't know if its just a hardware issue or something I am doing wrong on my end.
This is also not my first time manually unlocking/rooting a device
When you initially connect, the device shows up as a "Nexus 7".
When you reboot into the boot loader, the device name changes, and there is no driver for that device.
As far as I could tell, I would have to do the root process under Linux to avoid this issue.
As for me, I just ignored the issue. By the time you reboot the bootloader, you are already rooted.
The only thing you do after the reboot is rename a file. For now I am missing that step...
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
kevlars9 said:
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
Click to expand...
Click to collapse
Like I said - I think you are done...
Install a terminal on the Nexus and see what it says to "su". I use one called "terminal emulator". Works fine.
I think fastboot uses adb.
If you connect your Nexus, and type "adb devices" in a command window what does it say?
I believe it says devices attached or something like that. (Not at my computer) but doesn't give me a serial # like I think it should.
If you do not have USB Debugging checked, "adb devices" will just show the List of devices line.
If I set USB debugging on, "adb devices" also shows the Nexus serial number.
If you don't see that, I would double check the device driver you are using.
Under Device Manager, Android Phone, Android Composite ADB Interface it shows:
Driver: Google Inc.
Date: 5/24/2012
Version: 6.0.0.0
Digital Signer: google inc.
Well if I have USB debugging on and tablet on and do adb devices I get the serial # but once I go into boot loader and do adb devices I don't get the serial #.
For device manager I can choose adb interface or adb original interface. I'll have more info when I get out of work and at my computer. Do you have a link to the drivers you used? Or where to find them. Because I have tried a couple of different drivers posted around to no avail.
BTW thanks for helping me out.
I would not use any posted driver - you don't know where that thing has been.
Download the SDK from Google; the correct driver is in there.
Just point the device manager to it when you install drivers.
There are a lot of good descriptions on installing drivers in the other nexus forums
But - again - I think your device driver is fine. You will not be able to talk to the Nexus from ADB after you boot the bootloader
Bootloader has a different device name which ADB can't use under Windows.
Use Linux if you want to do that.
ok, so pretty much what happens is when my tablet is powered on with usb debugging everything is fine and ADB is recognized. Now my problem seems to be when i reboot into the bootloader it seems as though the drivers dont stick and it asks me to install the drivers again and this is where i have had all of my issues. When i type in adb devices in, it just tells me "list of devices attached" and wont let me do anything else (fastboot works). Like i said i was able to unlock my bootloader but i cant flash recovery or do anything else.
When i go into device manage to select the drivers it gives me the option of choosing between adb interface, adb bootloader interface, adb orignal interface and nexus 7 bootloader interface. I have tried all options and nothing seems to work. I have tried multiple usb cords and ports.
If anyone else has any suggestions it would be much appreciated.
I didn't read through everything but your initial problem is adb doesn't work in the bootloader that's where you use fastboot commands either boot into a custom recovery or just boot up normal and make sure debugging is checked.
Try running fastboot devices and see if it shows up. What you need to do is have bootloader unlocked and dismiss the super user zip floating around here pot that on sd card download cwm recovery image floating around boot into bootloader then
fastboot devices
fastboot flash recovery name_of_file.img
fastboot reboot bootloader
select recovery from the menu
Flash the super user zip
Or download a rom that has root and put that on sd card instead of super user zip and after doing the steps above then selecting super user zip select the rom you downloaded and flash. If you're on Linux run sudo first.
Sent from my Galaxy Nexus using xda premium
Delete
hi,
trying to flash the breadcrust recovery using my linux pc, but the Z1 doesn't appear in the list of devices when running adb devices. Image attached. Normally I would get a request to accept the RSA key for a trusted pc when enabling usb debug. But I don't get this option.
- Adb tools are loaded and working on my linux laptop
- My nexus 7 responds to ADB devices and shows up ok
- tried on wifes windows laptop with adb/sdk tools loaded and no joy there too
- i have developer USB debug options enabled, i've tripple checked this
could it be the cable? I'm using the one which came with the phone, so that should be ok?!!
cheers
SOLUTION - I ran this One Plus Two script modified with the Z1 device ID and now I can see my device in adb devices and interact with it. I get the SHA screen to allow access and can run commands from linux terminal. YAY!
See the attachments for script.
I think it´s a driver fault. Did u install them in windows?
im using linux, i dont get any rsa pop up confirmation either!
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
and that was the reason, why i installed windows last night. as long you dont get rsa pop up, the device will not listed (i think so)
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
But u said, that u tried ur wifes Windows notebook. Did u install the drivers there?
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
MKKLR21 said:
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
Click to expand...
Click to collapse
Good tip - I'll give it a go.
My nexus 7 works as expected on all PCs and laptops Linux/windows so it must be the phone
Sent from my Nexus 7 using Tapatalk
Maybe sudo or check this:
http://1.bp.blogspot.com/-rDdBnJTh870/U-hxVzxMf3I/AAAAAAAAKwQ/WrZkaMjaReo/s1600/Unlock-Bootloader-linux-terminal-xperia-z.png[img/]
Source: [url]http://linuxwelt.blogspot.de/2014/08/cyanogenmod-unter-linux-installieren.html[/url]
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader, but the device doesn't boot into fastboot, just reboots as normal!
I could also hold down up/down volume buttons and get into the bootloader, but again the device isn't picked by any fastboot oem checks for unlocking!!
arrrgh!!!
You'll have to add -i switch followed by the device ID to your fastboot command. I don't have it at hand, so just read the TWRP thread.
ok! Some progress...ish.
running "adb reboot bootloader"command in windows worked when I switched Cyanogen recovery updates off in developer options. The Z1 reboots into bootloader.
Running "fastboot -i 0x2b4c oem get-device-info" returns nothing just "....."
So I tried "fastboot -i 0x2b4c oem unlock" an error returns cannot unlock use command "fastboot -i 0x2b4c oem unlock-go" which works. The phone wipes data and reboots back into OS.
I re-enable the developer options and adb debug. and reboot into bootloader
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
weird!
Your commands are simply wrong, thats why they don´t work.
It is:
fastboot -i 0x2b4c oem device-info
fastboot -i 0x2b4c oem unlock-go
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
Click to expand...
Click to collapse
Flashing does NOT work on the international version, you have to boot into it directly from fastboot.
fastboot -i 0x2b4c boot z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
Should be correct instead of the flash command.
EggZenBeanz said:
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader...
...
Click to expand...
Click to collapse
What made the change? I was able to see the RSA screen only once, but after device restored to defaults I can't get it back. same drivers installed, and it appears in the device manager.
I honestly don't know, it just worked after many attempts. I read somewhere about USB 3 ports with Linux so might be the same for windows?
Sent from my Z1 using Tapatalk
It's an USB 3.0 issue. Plug the phone into an USB 2.0 port, or an USB 2.0 hub plugged into an USB 3.0 port and it will magically start working. God knows why this is the case...
Ironically, fastboot works fine even on USB 3.0...
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Planet X said:
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Click to expand...
Click to collapse
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
MrColdbird said:
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
Click to expand...
Click to collapse
Okay, I have found out that it is impossible to boot from TWRP as log as the bootloader is locked. It just took me 2 hours to setup my phone again after unlock.
Have a look at this thread, I am going to give it a try later.
http://forum.xda-developers.com/showthread.php?t=2408802
This did the trick on Linux (Ubuntu):
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in
- run on terminal "adb kill-server" and "adb start-server"
And run the fastboot commands with "sudo".
So recently I did nothing with my Nexus 4 and can not boot up. I have tried everything to go back to sock but my PC does not detect the phone anymore. I do not remember having USB debugging on but even if I did not I can't make the change now. I can boot to custom recovery but that does not help. I though It was the USB port so I got a new one and that still did not help.
Boot into fastboot mode to see if it is detected using "fastboot devices" in a command prompt window.
audit13 said:
Boot into fastboot mode to see if it is detected using "fastboot devices" in a command prompt window.
Click to expand...
Click to collapse
Yeah thats my problem. No fastboot. My PC does not see ADB device at all so I cant even Install the drivers. I even changed the USB port to make sure that was not the problem. Before this I could not get my PC to even see the internal SD card. Though It was the OS so I reset it but somehow lost it completely.
You're running adb commands from command prompt? They may not work unless the phone is running in recovery or the phone is booted into the rom.
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
It sounds like you may not have the latest drivers for the Android SDK or ADB toolkit.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
When you are in bootloader, you can use fastboot commands.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
JustPlayingHard said:
When you are in bootloader, you can use fastboot commands.
Click to expand...
Click to collapse
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
RonaldusMagnus said:
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
Click to expand...
Click to collapse
It's not adb fastboot.. It's just fastboot.
teh roxxorz said:
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
Click to expand...
Click to collapse
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
RonaldusMagnus said:
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
JustPlayingHard said:
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
Click to expand...
Click to collapse
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
No worries, it's probably me that's being dense.
That should work fine
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
or plug your phone in (while its booted normally, into its OS)
type: adb reboot bootloader
once phone reboots to bootloader, type: fastboot devices
He must have came from a HTC bc he's looking for the option Fastboot in Bootloader.
Sent from my Nexus 6P using Tapatalk
Thanks for your help everyone. I'm back up and running now. My problems stemmed from a misunderstanding that once in the bootloader I'm already able to execute fastboot commands and didn't need to select a fastboot option from the bootloader. And I had a misunderstood how to execute the fastboot commands from the command prompt.
Many thanks to everyone setting me straight!