Related
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
haltemien said:
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
I'm on skype ATM, so if anyone is gentle enough to try an errorsearch with me, call me on my username snorre.andre.nergaard
Click to expand...
Click to collapse
When I reinstalled my SDK i hadnt noticed that ./adb had been moved to a different directory, and the SDK no longer comes with ./fastboot. If you do a quick google search, or a search on XDA, there are forums out there with links and uploaded copies. Actually I'll just put mine up here in a .zip archive. I moved ./adb and ./fastboot back in to my tools folder since it's what I'm used to.
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
haltemien said:
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
Click to expand...
Click to collapse
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
krohnjw said:
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
Click to expand...
Click to collapse
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It's fastboot oem unlock
Sent from my Nexus S using xda premium
krohnjw said:
It's fastboot oem unlock
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It doesn't use ADB at all. That may be what you have your local binary named, but it's fastboot. You need to be in the bootloader (where adb cannot work).
Fastboot is the utility used for unlocking the bootloader, flashing/erasing partitions, booting images (such as a kernel or recovery) without installing to the device.
ADB is the Android Debug Bridge.
This is just for clarity here, there's seemingly a lot of confusion.
Thanks for the clarification bud
Sent from my Nexus S 4G using xda premium
kdepro said:
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
Click to expand...
Click to collapse
Yeah. I was in bootloader mode. So then i guess the fastboot "path". that could be the problem then. Ill check it out when i get back from work. Thanks
Okay long story but here I go trying to shorten it up. My on xl is stuck with no backup, no rom, and my laptop that had the drivers on it broke. So I have been trying to get ADB working so i could push a rom onto it to flash but i havent had any luck. I installed the Jdk and sdk. Set up the path variable. Installed HTC SyncManager then ended the process. But it wont find my device. "adb devices" will just show nothing. However, in bootloader when i go to fastboot and i plug the usb in, it changes to Fastboot USB. But yeah, any suggestions?
ADb willonly work while in recovery or while the phone is fully booted you could just mount storage in twrp
OP, what machine are you using? Windows 7, 8, or XP?
Sent from my One X using Tapatalk 2
Hi there,
I am rooted but wanted to install SuperCID so that I could s-off. It has been awhile since I have rooted and installed TWRP recovery but now after trying to install SuperCID I seem to have trouble executing fastboot commands, in bootloader I see 'Fastboot USB" after connecting to my primary USB ports (heck, I tried all 4 from my motherboard) but the commands do not seem to sync with my device (other commands seem to work such as me checking my CID [currently Rogers001]) so I do not know what happened...
Sorry for the potential lack of xda-vocabulary... I don't do this often.
TIA
an_xda said:
Hi there,
I am rooted but wanted to install SuperCID so that I could s-off. It has been awhile since I have rooted and installed TWRP recovery but now after trying to install SuperCID I seem to have trouble executing fastboot commands, in bootloader I see 'Fastboot USB" after connecting to my primary USB ports (heck, I tried all 4 from my motherboard) but the commands do not seem to sync with my device (other commands seem to work such as me checking my CID [currently Rogers001]) so I do not know what happened...
Sorry for the potential lack of xda-vocabulary... I don't do this often.
TIA
Click to expand...
Click to collapse
Your computer need htcsync and ADB installed to run fastboot
Did you download and install both of this software to ur computer?
And you need to lead to the folder where you store fastboot and adb, running CMD in this folder.
You are using Roger HTC 1x as same as me, so i can help you a lot hahaha
thinhletien said:
Your computer need htcsync and ADB installed to run fastboot
Did you download and install both of this software to ur computer?
And you need to lead to the folder where you store fastboot and adb, running CMD in this folder.
You are using Roger HTC 1x as same as me, so i can help you a lot hahaha
Click to expand...
Click to collapse
Yes, I have the drivers (ADB/Fastboot) in a folder on C:\ and have pointed to that folder in cmd prompt (I should mention I have successfully leveraged the commands in the past).
However, I do not have HTC Sync installed so let me give that a shot...
Edit - after installing HTC Sync and connecting the phone (after unlocking the PIN, of course) - it could not connect to my device. Any advice/suggestions? This is probably going to tie into the same reason why I cannot connect via fastboot to my device.
Side note is that I am running CleanROM 6.5 if it makes any difference (stock kernel or whatever the roms come with).
Do you have debugging enabled on your phone?
Sent from my HTC One XL using xda premium
Venomtester said:
Do you have debugging enabled on your phone?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yes, USB debugging is enabled in developer options.
Still having no luck.
Hi guys
I accidently wiped my whole phone (Caches, Data, Internal Storage & System).
After reading trough the forum I found out that I need to flash the Stock image via adb/fastboot.
The problem is that adb won't recognize my phone due the lack of enabled USB Debugging (no OS installed).
I already tried it, on both, Mac and Windows.
I have no idea what I should do now. I would really appreciate it, if you could help me guys.
Thanks in advance.
YM
1) you do not flash stock images using adb. Adb is not fastboot. They are different things
2) you can only use adb in android or recovery. USB debugging is an android only setting. It is NOT needed to use adb in recovery. Adb will not work in the bootloader
3) fastboot only works in the bootloader. It is fastboot to flash stock images.
Sent from my Nexus 5 using Tapatalk
rootSU said:
1) you do not flash stock images using adb. Adb is not fastboot. They are different things
2) you can only use adb in android or recovery. USB debugging is an android only setting. It is NOT needed to use adb in recovery. Adb will not work in the bootloader
3) fastboot only works in the bootloader. It is fastboot to flash stock images.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you for your fast answer.
But ./adb devices doesn't shows any devices.
And neither does ./fastboot devices.
Let's stick with Windows for now
So boot into bootloader. Adb devices won't work here as explained. Fastboot devices should. If it doesn't you need to read the adb and fastboot drivers thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
Let's stick with Windows for now
So boot into bootloader. Adb devices won't work here as explained. Fastboot devices should. If it doesn't you need to read the adb and fastboot drivers thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It doesn't work.
I read this thread http://forum.xda-developers.com/showthread.php?t=2588979 and installed the drivers.
I also found out that my Nexus doesn't even show up in the Windows Device Manager.
What could be the reason for that?
Windows, drivers, cables.. It have to keep trying. It's the only way
Sent from my Nexus 5 using Tapatalk
rootSU said:
Windows, drivers, cables.. It have to keep trying. It's the only way
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do you ever get sick of saying this?? I'm amazed at how many times you are willing to say it. Good on ya.
Let me know if I can help you out at all.
Have you tried using external micro usb flash drive with a rom + apps? I'm assuming your recovery is intact. If you're trying via win8 it's a pain #drivers.
Sent from my X9006 using XDA Premium 4 mobile app
Bronyr said:
Have you tried using external micro usb flash drive with a rom + apps? I'm assuming your recovery is intact. If you're trying via win8 it's a pain #drivers.
Sent from my X9006 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not everyone has a Micro USB flash drive or OTG cable.
I didn't have to try anything to get drivers working after I clean installed Windows 8.1U1, it worked as soon as I installed the Google USB driver lol. If you can't get it to work, you're doing it wrong.
Hey all, so I bought a nexus 5 about a week ago(loving it!) and it came with boot loader unlocked. Basically I'm tryna install twrp through fastboot so I can flash SuperSU and root. Andriod version is 5.1 lollipop and I'm trying to install 2.8.5.2 twrp. I can get cmd to recognize the andriod SDK platform and is recognizes the fastboot recovery command but it says waiting for device. Do I press start on my phone or should it do this itself?
KentuckyGuy447 said:
Hey all, so I bought a nexus 5 about a week ago(loving it!) and it came with boot loader unlocked. Basically I'm tryna install twrp through fastboot so I can flash SuperSU and root. Andriod version is 5.1 lollipop and I'm trying to install 2.8.5.2 twrp. I can get cmd to recognize the andriod SDK platform and is recognizes the fastboot recovery command but it says waiting for device. Do I press start on my phone or should it do this itself?
Click to expand...
Click to collapse
You have to install drivers from here first: http://developer.android.com/sdk/win-usb.html
Is your phone booted to fastboot?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
Is your phone booted to fastboot?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
Fastboot is waiting on device if there isn't wright driver installed.
Enable use debugging
Install drivers and adb using adbinstaller.exe. Google it.
Then try "adb devices" in cmd
Yes my device was booted to fastboot. I already installed the android SDK, and the PC already installed driver. I'm gonna enable USB debugging as I forgot though. Will look into all of this and let you guys know. Just curious as to what is the start option in the fastboot menu on my phone?
Turns out I do need the drivers for adb. Thanks zagorteney! I'm gonna install them and see what happens.
Adb is irrelevant in fastboot mode
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
KentuckyGuy447 said:
Turns out I do need the drivers for adb. Thanks zagorteney! I'm gonna install them and see what happens.
Click to expand...
Click to collapse
Ben36 said:
Adb is irrelevant in fastboot mode
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
That's true. Adb and fastboot are two different things. In fastboot you don't need USB debugging enabled. You need to install drivers, when you are allready in fastboot mode (booted in bootloader).
zagorteney said:
That's true. Adb and fastboot are two different things. In fastboot you don't need USB debugging enabled. You need to install drivers, when you are allready in fastboot mode (booted in bootloader).
Click to expand...
Click to collapse
OK so when I use the adb devices command it doesn't pick up my device? Do I have to press the start option on my phone in bootloader? Also as I said when I use the fastboot recovery command it just keeps saying waiting for device. Should I press start on my device in the bootloader mode?
Try fastboot devices and see what it says
Sent from my Nexus 5 using Tapatalk
KentuckyGuy447 said:
OK so when I use the adb devices command it doesn't pick up my device? Do I have to press the start option on my phone in bootloader? Also as I said when I use the fastboot recovery command it just keeps saying waiting for device. Should I press start on my device in the bootloader mode?
Click to expand...
Click to collapse
If the phone is running normally, try the "adb devices" command and see if your device is recognized. Or if booted in to the bootloader, do "fastboot devices". Either way you should see your device as an alphanumeric string. If either recognizes your device, you have the correct drivers installed.
You will fastboot flash a custom recovery in bootloader mode.
Lots on good info in these threads:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
upndwn4par said:
If the phone is running normally, try the "adb devices" command and see if your device is recognized. Or if booted in to the bootloader, do "fastboot devices". Either way you should see your device as an alphanumeric string. If either recognizes your device, you have the correct drivers installed.
You will fastboot flash a custom recovery in bootloader mode.
Lots on good info in these threads:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Away from a working PC for a couple of days but when I get access to one, will try it and let you guys know what happens.
Alright guys thanks! Got the custom recovery installed and phone is rooted! Solution was installing the Naked (United?) Drivers for nexus 4(yes they work for nexus 5 too!) Fastboot recognized the device and installed recovery susscessfully! Now it seems I have another question,I installed elementalx kernel and reverted back to stock as stock is way easier on my battery. Just wondering when changing the settings in the elementalx installer and then reverted to stock did the config stick or revert? I noticed my phones running hotter than usual which leads me to be leave the thermel throttling didn't revert. Thanks!
EDIT: It seems battery is draining faster too!
KentuckyGuy447 said:
Alright guys thanks! Got the custom recovery installed and phone is rooted! Solution was installing the Naked (United?) Drivers for nexus 4(yes they work for nexus 5 too!) Fastboot recognized the device and installed recovery susscessfully! Now it seems I have another question,I installed elementalx kernel and reverted back to stock as stock is way easier on my battery. Just wondering when changing the settings in the elementalx installer and then reverted to stock did the config stick or revert? I noticed my phones running hotter than usual which leads me to be leave the thermel throttling didn't revert. Thanks!
EDIT: It seems battery is draining faster too!
Click to expand...
Click to collapse
Probably best if you opened a new thread for separate issues.
EDIT: Yep, so nice to be ignored.
There's no way elementalx is worse on battery than stock. It's far better.
Use options for custom hotplugging
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
There's no way elementalx is worse on battery than stock. It's far better.
Use options for custom hotplugging
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
I reinstalled to test thoughly. I see where I can disable mpdecision and use custom hotplugging in the elementalx config, is that it or is there other steps I need to take besides that? Any advice or threads on this?
EDIT: I'm guessing the overheating is causing the battery drain. Stock didn't heat my device like this. Its not bad overheating but it does get significant and the battery seems to plummet when it happens. Usually happens after playing games, although stock didn't heat up this bad or drain battery that bad while playing games. It may also be the new charger I got, will charge with stock charger to see what happens.
beekay201 said:
Probably best if you opened a new thread for separate issues.
Click to expand...
Click to collapse
True but I don't want mods thinking I'm trying to spam or troll.
Thanks guys, I've done all I needed to do. As suggested by Ben using custom hotplugging and adjusting thermal throttling, device settled back down and is running smooth and heatfree(besides heavy gaming which is usual.) Thanks everyone! Guess it'll hold me over till official Cyanogenmod 12.1 nightlies start rolling out.