Develop Bugs

[Q] Command line troubles

I'm trying to manually install the 4.2 update. My GNex is stock 4.1.2 and my computer is running Windows 8 Pro. The problem is that when the phone is on, I can type in "adb devices" and it see my device, but when I get into recovery and to the point where it tells me to sideload, I type in "adb devices" and my device is no longer detected. Any ideas for a solution? Thanks!

aaronmcd1214 said:
I'm trying to manually install the 4.2 update. My GNex is stock 4.1.2 and my computer is running Windows 8 Pro. The problem is that when the phone is on, I can type in "adb devices" and it see my device, but when I get into recovery and to the point where it tells me to sideload, I type in "adb devices" and my device is no longer detected. Any ideas for a solution? Thanks!
Click to expand...
Click to collapse
You need other drivers for fastboot I believe, check for info in one of the stickies in this section.
Swype'ed on my CM10 Galaxy Nexus

I uninstalled all the drivers and stuff that I had and reinstalled all the ones I could find and I'm still having issues. I've been able to root and unlock and all that before but for some reason it doesn't want to see it with stock recovery. I'm too impatient to wait for the OTA! lol

you need to re-install (manually, through device manager or whatever) the same drivers again, when device is in recovery

OK so I reboot into recovery and then just install drivers like I did the first time or are they different drivers?
Sent from my Galaxy Nexus using xda premium

Ok so I got the drivers reinstalled and the device is recognized but now when I enter "adb sideload e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13" it just gives me the help menu....

NVM guys, tried the "clear data and force stop" trick and got it the first time

First make sure you extract adb from the latest SDK distribution because older adb versions did not support the sideload command. (I also had to do this to run sideload.)
Second, if you use stock recovery, make sure you select "update from adb" from the menu before issuing the adb sideload command on your computer.
Sent from my Galaxy Nexus using Tapatalk 2

I might have had an older version of adb. I didn't think of that. Oh well, I was able to force the OTA by clearing and stopping the framework app so all is well. Thanks for the help!
Sent from my Galaxy Nexus using xda premium

[Q] ADB recognizes device but not in recovery

Hi! I want to update my girlfriend's GNex by pushing update via recovery. I have adb working and recognizing device when it's turned on (with debugging mode). But when I go to recovery (adb reboot recovery), I can't get my device recognized again - "adb devices" shows nothing. I figured it can't be problem with drivers (since the device is recognized when turned on?), I must be doing something else wrong? But I have no idea where to look.
Sorry for the (probably) common question, but all I've found (using search) is adb not recognizing devices at all. I've been only using "fastboot" commands so far, and I never had problems with recognizing.

Joplisan said:
Hi! I want to update my girlfriend's GNex by pushing update via recovery. I have adb working and recognizing device when it's turned on (with debugging mode). But when I go to recovery (adb reboot recovery), I can't get my device recognized again - "adb devices" shows nothing. I figured it can't be problem with drivers (since the device is recognized when turned on?), I must be doing something else wrong? But I have no idea where to look.
Sorry for the (probably) common question, but all I've found (using search) is adb not recognizing devices at all. I've been only using "fastboot" commands so far, and I never had problems with recognizing.
Click to expand...
Click to collapse
what recovery are you using? in twrp, in advanced menu, theres a adb sideload option.

The problem is that her phone is locked, everything is stock. The only option is adb sideload (as far as I know). Any suggestions? I really don't have a clue.
Sent from my Galaxy Nexus using my thumbs.

Stock recovery does not offer the ADB interface, so adb commands will not work. You need to flash a custom recovery such as CWM or TWRP.

Ahhh, I didn't know that. I guess I have to wait for the ota, then, since I can't flash or use custom recovery. Thank you for your help!
Sent from my Galaxy Nexus using my thumbs.

Actually you can use adb commands in stock recovery - this works on build number JRN84D and newer only (JRN84D corresponds to 4.1, the first Jelly Bean build).
1) Reboot your device into the stock recovery (i.e., the screen with the Android on its back with the "!");
2) Access the stock recovery menu by pressing power and volume up;
3) Select "Apply update from ADB";
4) Download the correct update for your build and place it in the same directory as your ADB binary;
5) Open a command prompt in the same directory as your ADB binary;
6) Type adb devices to make sure that your device is recognized;
7) Type adb sideload name-of-file.zip
8) Reboot. Done.
Click to expand...
Click to collapse
This is from Method 4 in http://forum.xda-developers.com/showthread.php?t=1419170
Hope this helped

HELP pushing files

hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.

Chyrio said:
hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.
Click to expand...
Click to collapse
Try /storage/sdcard0
But if that doesnt work, reboot to bootloader and flash stock userdata.img through fastboot; reboot to recovery right after that, push rom.
Sent from my i9250

I ran into the same problem, I erased my internal memory and i'm now stuck with the google screen
i have TWRP recovery but there is nothing on the sd card to flash from, how do i push files to the sd card from the computer?
I tried use the nexus root toolkit but i get "fastboot device not found" even though the bootloader says that it is in fastboot mode.
please help

nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!

Chyrio said:
nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!
Click to expand...
Click to collapse
I tried to use your sideload command but it didn't work. It said "ERROR: CLOSED"
i'm really anxious and worried if i can get the phone to work at all:crying:. any help will be greatly appreciated!

Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool

italbomber said:
Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool
Click to expand...
Click to collapse
Thank you. I tried doing that but it wasn't any help. however, i figured how to sideload using the TWRP setting. It took a little trial and error but finally got it to work.

i don't see how can you guys not get it to work through normal adb, other than you're using Windows, but glad you got it to work.

Glad to hear you are up and running again. Sorry i just always had great luck with his toolkit. Adb was always failsafe too.
Sent from my Galaxy Nexus using Tapatalk 2

Just a note you were probably getting an error because you didn't Mount the sdcard in recovery before trying to push to it.
Sent from my Galaxy Nexus using xda premium

I did a full wipe of the phone and SD card and was unable to see my phone in adb while in CWM recovery.
I run the push command any way and it did push to the file to the phone.
I push the file to /data/media/ no need to mount SDcard as it doesn't have a real one, in the past (while using ics) I have had to mount data to push files to /sdcard/

Can you ADB push files to the sd card without an OS installed???

I just accidentally wiped my SD card and my system and now I don't know how to get a rom onto my phone due to the lack of an SD card slot. Can anyone help me get a rom on the internal so I can flash? I have TWRP still but I have no clue how to get a rom to my sd card. Am I screwed? Cause I read a forum that had to have usb-debugging on and I have no system lol. Thank you guys so much

You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app

mrgnex said:
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing

jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
First use TWRP not fastboot. Once you are in recovery plug the phone in and type "adb devices" (without the quotes) in command prompt or terminal. If it returns with letters and numbers (can't remember might be a combination of both) your good to go. Type "adb push c:\downloads\Rom.zip /sdcard" type out the directory where the file is instead of downloads change it to where your rom is. If you type adb devices and nothing happens you need to work on your drivers.

jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip

mickeyflip said:
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Cool story he's trying to use adb not fastboot two totally different things.

DR3W5K1 said:
Cool story he's trying to use adb not fastboot two totally different things.
Click to expand...
Click to collapse
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...

mickeyflip said:
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
Click to expand...
Click to collapse
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.

DR3W5K1 said:
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
Click to expand...
Click to collapse
No worries - it's possible that they do. But the drivers I linked are the ones that worked for me consistently. The Samsung ones seemed to stop working each time I disconnected the handset and plugged it back in via USB.
In any case, those are the only ones I have installed right now and everything is working great for me connection/recognition wise.
Any luck yet jtl_777?
To push files to the handset, use the command: adb push filename.ext destination-folder
Explained further here: http://developer.android.com/tools/help/adb.html#copyfiles

Just for future reference so people reading these threads don't get super confused, your computer won't recognize your phone through adb commands unless you are in adb sideload through your custom recovery, or if you're booted up and running in an operating system. You could also use adb push commands in your custom recovery. This has nothing to do with drivers or whatnot. If in bootloader your device isn't recognized through adb commands, that's completely normal, because it never would be, but your device should be recognized in bootloader with fastboot commands.
IF your phone is NOT recognized in your booted up phone, or in adb sideload through your custom recovery, or with adb push commands in your custom recovery, with adb commands, then you have driver issues.
ALSO IF your phone is NOT recognized while in bootloader, with fastboot commands, then you have driver issues.
To answer the OP's question:
If you have an unlocked bootloader and you are in TWRP, you can mount your phone onto your computer and copy and paste the rom zip onto the phone and then install it through TWRP once on the phone. If that doesn't work, then you can try using adb push commands while in TWRP (or maybe need to be in adb sideload through TWRP) to push the rom to your sd card and then run it through TWRP. If that doesn't work, you can also try flashing the rom zip through bootloader with fastboot commands, but all these commands might be device specific, that's why I won't tell you the commands I know for the HTC One X, but the processes are the same no matter what. Hope that helps

You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5

Pirateghost said:
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Click to expand...
Click to collapse
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.

EsoteRIcalfreaK said:
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
Click to expand...
Click to collapse
Adb shell as well as numerous other commands work just fine
Sent from my Nexus 5

Trouble Installing March Update OTA via ADB Sideload

Hello,
I downloaded the March OTA .zip from the thread in the general forum with the intention of installing via ADB sideload for the first time. I've installed the Android .sdk and confirmed that adb does work. Typing "adb devices" in the command prompt gives me the serial number.
I've used that to reboot to bootloader, go next to recovery, and click the "install via adb" option, at which point it instructs me to go back to the computer and push the file. I shift+right click on the folder containing platform-tools to open a command prompt tied to this folder (which also contains the downloaded OTA update, renamed "update" for convenience).
When I enter the command "adb sideload update.zip" it tells me that the device cannot be found. I've rebooted a few times and adb recognizes the device when it's on, but does not recognize it the moment I'm booted into bootloader or recovery. Has anyone run into this issue before?
Device is stock, unrooted, bootloader locked. I wanted to try this before messing with fastboot and the binary images to get my feet wet, but it's been a headache inducing afternoon so far. I know the OTA will arrive in a few days anyway, but I'd love to know how to do this correctly as the guides on here have been unsuccessful for me.
Thanks in advance!

Try putting the OTA zip file in the same folder as the adb.exe file (in the platform-tools directory)

Moonboots said:
I've rebooted a few times and adb recognizes the device when it's on, but does not recognize it the moment I'm booted into bootloader or recovery. Has anyone run into this issue before?
Click to expand...
Click to collapse
Are you using a Windows machine? I am far from an expert on these matters, but my sense is that failing to "see" the phone in recovery is usually a driver issue. See if this thread helps.
Moonboots said:
I know the OTA will arrive in a few days anyway, but I'd love to know how to do this correctly as the guides on here have been unsuccessful for me.
Click to expand...
Click to collapse
My experience has been that the only hard part of sideloading OTAs is the initial step of getting ADB running on a windows computer. Once you sort that out, it is very easy and also very liberating to not have to wait for updates over-the-air. Good luck!

Thanks for the help, all! The trick was letting Windows find its own driver (not the automatic setting, had to select this option) when the phone was in adb sideload mode. It's a different driver than fastboot and with the phone on.
Sideloaded the update last night and we're going strong! ?