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
Related
So I made a mistake and I tried to flash the newest aokp build 3 without a backup. I got my new phone a while back and never made a backup.
I flashed build 3 and (accidentally) some old gapps and I kept getting stuck on the Google screen.
Next I tried pushing files through the Gnex tool kit and manually through fastboot. I keep getting errors that there is no insecure boot or that the device is not connected. attempts at a temporary insecure boot on the tool kit fail.
Next I tried a wipe and then just installing build 3 without google apps so I could add the correct one after boot, but it is again stuck.
So now I'm really not sure what to do. Any suggestions?
Rule number 1 : STOP using toolkits!!
now, can you get into cwm recovery?
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
You could eithther try to flash back to stock or you could boot into TWRP & adb push a different ROM. (You did try Wipe Data / Factory Reset right?)
MK17 said:
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
Click to expand...
Click to collapse
I think what thegtfusion was trying to say was: if you wouldn't have used a toolkit in the past, you would have known how to fix your bootloop.
Buy anyway:
1) Boot into recovery and plug into your PC
2) Open a command prompt (in the folder where you have adb.exe and fastboot.exe)
3) Push the ROM (and kernel if it doesn't come with it) you want to flash to your device: adb push /path/to/ROM.zip /sdcard/
4) Reboot into fastboot mode
5) Erase your old ROM: fastboot erase system
6) Erase your old kernel: fastboot erase boot
7) Reboot into recovery
8) Wipe /data and /cache
9) Flash your ROM & kernel in recovery
10) Reboot. Done.
EDIT: Ninja'd by 3rdstring!
Screwing up is part of the learning process. It's actually a great way to learn how your phone really works.
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
MK17 said:
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
Click to expand...
Click to collapse
Try uninstalling all drivers and reinstalling them.
Sent from my Galaxy Nexus using xda premium
Drivers
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
MK17 said:
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
Click to expand...
Click to collapse
did you install android-sdk (and added adb/fastboot to your $PATH) or are you using binary versions of adb and fastboot downloaded elsewhere?
if it's the latter, commands should be run from the directory where you extracted them.
about the drivers, i think you need to go to device manager and update drivers manually to the ones you installed (refered here in the post before mine), assuming you're on windows.
sent from my i9250
You're booted into TWRP when trying adb?
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
MK17 said:
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
Click to expand...
Click to collapse
he didnt have usb debugging on.
sent from my i9250
Just for understanding, USB debugging is only activated through recovery?
It's also under settings >> developer options so you can use adb while the android is running.
3rdstring said:
It's also under settings >> developer options so you can use adb while the android is running.
Click to expand...
Click to collapse
Of course,but that is hard to get to when your phone doesn't boot
MK17 said:
Of course,but that is hard to get to when your phone doesn't boot
Click to expand...
Click to collapse
USB Debugging needs to be enabled in Android for ADB to work in Android.
CWM and TWRP have USB Debugging enabled by default, so ADB will work fine in recovery with no other action from the user.
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
I have a problem with my computer, I have a GNEX and I cannot get the commands from ADB to work. Once I tried to root my phone manually and I did not work, then I tried Wug's tool and it did not work either. I tried another computer and it worked. Both PC's have win7 and the drivers installed correctly. ADB does detect the phone.
When I type a command, the cursor just blinks and nothing happens. I can keep typing characters and still nothing happens.
Sounds like you're not running the command prompt as admin.
diobando said:
I have a problem with my computer, I have a GNEX and I cannot get the commands from ADB to work. Once I tried to root my phone manually and I did not work, then I tried Wug's tool and it did not work either. I tried another computer and it worked. Both PC's have win7 and the drivers installed correctly. ADB does detect the phone.
When I type a command, the cursor just blinks and nothing happens. I can keep typing characters and still nothing happens.
Click to expand...
Click to collapse
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
bk201doesntexist said:
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
Click to expand...
Click to collapse
I have 4.2.2 right now, but I tried it before with 4.0.2, 4.0.4 and 4.1.1. I have updated de sdk and the commands still do not work.
diobando said:
I have 4.2.2 right now, but I tried it before with 4.0.2, 4.0.4 and 4.1.1. I have updated de sdk and the commands still do not work.
Click to expand...
Click to collapse
Premise not to use almost never win7 ... I still tried for the first time tonight sdk-platform-tools on windows and adb and fastboot commands work normally ... the phone must have the bootloader unlocked (otherwise fastboot does not work ) is launched from the promt with administrator privileges and inside the folder where resides and the phone must be in fastboot / bootloader mode to acknowledge the command but also the drivers for the Nexus should be properly installed (try uninstalling and riinstallarli maybe installing some toolkit - gnextoolkit or Nexus Root Toolkit)
bk201doesntexist said:
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
Click to expand...
Click to collapse
Maxmaximus said:
Premise not to use almost never win7 ... I still tried for the first time tonight sdk-platform-tools on windows and adb and fastboot commands work normally ... the phone must have the bootloader unlocked (otherwise fastboot does not work ) is launched from the promt with administrator privileges and inside the folder where resides and the phone must be in fastboot / bootloader mode to acknowledge the command but also the drivers for the Nexus should be properly installed (try uninstalling and riinstallarli maybe installing some toolkit - gnextoolkit or Nexus Root Toolkit)
Click to expand...
Click to collapse
Bootloader is unlocked. The phone is not the problem, I was able to unlock, root and push updates and ROMs in another computer. I just can get the commands to work in my computer. I tried doing any of this procedures with Wug's toolkit, and that does not work either.
At the risk of sounding silly, do you have usb debugging enabled?
bodh said:
At the risk of sounding silly, do you have usb debugging enabled?
Click to expand...
Click to collapse
Yes
Sent from my Galaxy Nexus using xda premium
Try another USB cable and/or port, and be sure you are running ADB with admin privilege.
Sent from my Galaxy Nexus using xda app-developers app
diobando said:
Bootloader is unlocked. The phone is not the problem, I was able to unlock, root and push updates and ROMs in another computer. I just can get the commands to work in my computer. I tried doing any of this procedures with Wug's toolkit, and that does not work either.
Click to expand...
Click to collapse
sounds like a problem with the toolkit not being updated.
considering you just said you got it to work on your pc with command prompt.
Zepius said:
sounds like a problem with the toolkit not being updated.
considering you just said you got it to work on your pc with command prompt.
Click to expand...
Click to collapse
Sorry, I had a typo. I meant I can't in "I just can get the commands to work in my computer..."
Hi am trying to sideload the GNex's 4.2.2 update and i can't seem to get it to sideload onto my phone. I updated all the drivers and installed them, updated the android sdk, i did a "adb devices" check on the CMD and it shows the device.
I am currently running the stock 4.1.1 on my phone.
I am not rooted and do not want to root the phone because i do not want to have to wipe the phone. I get the device into recovery mode and get it ready to sideload. I am doing it from the platform-tools folder of the SDK folder. type the correct command "adb sideload 5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip and then i get the whole adb help menu pop up and does not install the update.
Does anyone know what i am doing wrong? (please don't say not rooting it lol) i have tried it on 2 different computers and i am still getting the same results. Any suggestions or tips would be appreciated.
Update: i just used the "adb devices" command it right after it said that the adb server was out of date and was killing it. then the device connected.
You have to pull up the recovery menu when in recovery and select the sideload option. The key combination I don't know. I did it after looking it up but don't know exactly how I did it.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
You have to pull up the recovery menu when in recovery and select the sideload option. The key combination I don't know. I did it after looking it up but don't know exactly how I did it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply, I do select "install using adb" once in recovery then connect the phone to the computer.
When the help message pops up in adb, what version is listed at the top [I have 1.0.31]? I know you said you updated your sdk, but it sounds like adb does not recognize the sideload command. Perhaps you have more than one version of adb in the folder you'e working out of?
On Device Manager (Window 10). Were updating the driver, I can only see ADB interface but no Fastboot interface. I'm on the latest version SDK from Google and have OnePlus driver installed. I can command ADB but not fastboot. What am I missing? My device is OnePlus 7T TMobile is sim unlocked and I can toggle OEM unlocking and is on.
Not sure what mean, but fastboot only works when you're booted in bootloader. (Adb reboot bootloader)
Sent from my OnePlus7TPro using XDA Labs
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
PesTicide. said:
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
Click to expand...
Click to collapse
I myself have never had this problem, I can only suggestion reinstalling OnePlus drivers.
Hopefully you figure this out
Sent from my OnePlus7TPro using XDA Labs
I reinstalled couple of times. Still no go! This is the first time that this happening. Never had problem since day one on Nexus devices. I'm going to try again and search more around.
You can also use the universal drivers by clockworkmod https://adb.clockworkmod.com/
Here's what I did.
1) Extract the android sdk platform tools and put on your c:// drive
2) Install the universal usb drivers
3) Enable usb debugging on your one plus and connect to computer. Switch to usb debugging mode and accept the popup on your one plus to allow the connection.
4) Open cmd and run "cd C:\platform-tools", then run "adb devices" to ensure that your devices is connected properly
5) Run "reboot bootloader" and device will restart into bootloader mode and fastboot will now work
*This is all assuming that you've already oem unlocked your devices as well already*
It work till fastboot. Still stuck at "waiting for device".
PesTicide. said:
It work till fastboot. Still stuck at "waiting for device".
Click to expand...
Click to collapse
Are you trying to open? Command shell? In windows 10 right? So for your information in windows 10 it's not supported , you have to open that platform tool folder which you installed already named as adb, platform tools , sdk may go into that folder and you will see a folders directory above there .. just click on that and type cmd and hit enter and cmd will pop up now you can use all your commands it's not your fault it's windows 10 fault ..maybe hope it may work for you
That how I done it. Fastboot Command appear on my Google Pixel 2 and 3 but I can't do it on my 7T. I don't get it
Thanks for the help! I tried working on Device Manager on PC yet doesn't work. Adb shell command work but no Fastboot command.
I found the solution! This is what I did and it worked for me! Here's the link for anyone who has the same issue I went through. Here you go and follow the instruction. http://www.wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Mod you can close this thread. Thanks again for everyone who tried to help me. :highfive: