I'm trying to install the 4.4.1 update but my device isn't being detected in recovery mode and thus adb sideload is not working. Would really appreciate some help. I've tried almost every solution that I've googled and nothing seems to be working.
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Sent from my Nexus 5 using xda app-developers app
jkimbro said:
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Click to expand...
Click to collapse
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
You just need the Google drivers from their website:
http://developer.android.com/sdk/win-usb.html
I had to force the installation of the drivers for the "AOSP on Hammerhead" device in the device manager.
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
I used USB ADB Composite Interface or something like that by pointing the device manager's Update Driver dialog to the USB drivers from the SDK that EddyOS pointed at.
Windows 7 x64
Yep, had issues with my work PC (Win 7 Pro x64) - had to manually point Device Manager to the android_winusb.inf so it would find the drivers. Bit of a ballache but all working after that!
greenkabbage said:
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
Click to expand...
Click to collapse
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
a hammerhead wrote this.
beekay201 said:
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
Click to expand...
Click to collapse
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
jt3 said:
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2513339
jt3 said:
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
Click to expand...
Click to collapse
Try it. Select "apply update from ADB", and then try to get a ADB prompt like you would normally, you know, ls /sdcard/, something.
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
Hey folks.
I have been trying to get my wife's NS4G back to stock to get the JB OTA. I have downloaded all drivers multiple times on multiple computers (windows). I have tried 3 or 4 different USB cables. I have downloaded pdanet. I have downloaded the JAVA SDK and updated everything about it.
My computers cannot connect to the NS4G.
USB debugging is on. When I try to turn on tether, it tells me USB is not plugged in.
I have been able to restore the stock ROM (2.3.7) via CWM, but now I no longer have a recovery. It is still rooted and unlocked. Rom Manager is installed and it will not download CWM Recovery.
I need some way to get a recovery onto it. CMW or stock.
Does ANYONE have any suggestions?
Thanks in advance for all suggestions and particularly to the one that will work.
SemperFratres said:
Hey folks.
I have been trying to get my wife's NS4G back to stock to get the JB OTA. I have downloaded all drivers multiple times on multiple computers (windows). I have tried 3 or 4 different USB cables. I have downloaded pdanet. I have downloaded the JAVA SDK and updated everything about it.
My computers cannot connect to the NS4G.
USB debugging is on. When I try to turn on tether, it tells me USB is not plugged in.
I have been able to restore the stock ROM (2.3.7) via CWM, but now I no longer have a recovery. It is still rooted and unlocked. Rom Manager is installed and it will not download CWM Recovery.
I need some way to get a recovery onto it. CMW or stock.
Does ANYONE have any suggestions?
Thanks in advance for all suggestions and particularly to the one that will work.
Click to expand...
Click to collapse
If you are running Windows 7 hold down the shift key and right click then select open command prompt here. type ADB devices and if your drivers are installed then you will see your serial number. Remember to be in fastboot when you install drivers. then use ADB to reboot bootloader. when in fastboot type "fastboot devices" and you should again see your serial number to know that your drivers are all installed correctly. You need to fastboot flash a new recovery image. Hope that helps
ken3669 said:
If you are running Windows 7 hold down the shift key and right click then select open command prompt here. type ADB devices and if your drivers are installed then you will see your serial number. Remember to be in fastboot when you install drivers. then use ADB to reboot bootloader. when in fastboot type "fastboot devices" and you should again see your serial number to know that your drivers are all installed correctly. You need to fastboot flash a new recovery image. Hope that helps
Click to expand...
Click to collapse
Drivers are installed, as I can see my S3 fine as well as adb getting my serial number. The computer, nor adb, can see my NS4G. I have tried a desktop as well as 2 laptops.
Will be trying Vaelek's idea of wireless adb this evening.
Thanks for the suggestion.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
SemperFratres said:
Drivers are installed, as I can see my S3 fine as well as adb getting my serial number. The computer, nor adb, can see my NS4G. I have tried a desktop as well as 2 laptops.
Will be trying Vaelek's idea of wireless adb this evening.
Thanks for the suggestion.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
Click to expand...
Click to collapse
Drivers are NOT installed properly then. Drivers are installed on a per device basis. If your phone doesn't get recognized, then they are not installed.
Chances are your device ID isn't found in the .inf file of the drivers. I know back when I rooted my phone over a year ago I had to manually change the inf file and add my device.
If you start your phone in fastboot mode and plug it in, when you go in device manager you should see an unrecognized device with a yellow question mark. Right click it, then Properties, then Details tab. Give me the information in the Device Instance Path.
Will check this out and post info when I get home tonight. Thanks for the input.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
polobunny said:
Drivers are NOT installed properly then. Drivers are installed on a per device basis. If your phone doesn't get recognized, then they are not installed.
Chances are your device ID isn't found in the .inf file of the drivers. I know back when I rooted my phone over a year ago I had to manually change the inf file and add my device.
If you start your phone in fastboot mode and plug it in, when you go in device manager you should see an unrecognized device with a yellow question mark. Right click it, then Properties, then Details tab. Give me the information in the Device Instance Path.
Click to expand...
Click to collapse
Started phone in fastboot mode. Plugged it in and watched Device Manager. Closed device manager and re-opened it for a good refresh. I get nothing new. No unrecognized device and no Android Device like when I plug in my S3. ADB Wireless wont connect.
OK... I just cleared my sd card and was able to install CWM. One hurdle cleared...
I still need to get stock ROM and recovery. Is there anyway to do this WITHOUT being able to connect via adb?
Thanks again for any input.
Hey all,
I've got a new-to-me TF700. Got CROMBi-KK installed, which took some backflips as I could not get fastboot connectivity.
I'd like to be setup for NvFlash (but then never need it), so even though I don't need fastboot right now, I'm feeling the lack.
Data transfer works fine.
ADB (not fastboot) works fine (adb shell gets me a shell, etc, etc)
When I put the phone in fastboot/bootloader "fastboot devices" gets an empty response "fastboot reboot" gets no response.
In Win7 device manager, the TF700, which appears in the "portable devices" section normally when I plug it in, does not appear.
So... probably device drivers.
Have you had this problem on your w7/64 box? How did you fix it? Sorry, but "install linux" isn't all that helpful.
Thanks!
From a semi-related question I'd asked, berndblb mentioned
berndblb said:
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?
Click to expand...
Click to collapse
Yep, I get an "unknown device" in the USB section when I connect a TF700 in fastboot. Win can't find an appropriate driver. I've tried (manually) ASUS_Android_USB_Drivers and Universal_Naked_Driver_0.72 (both, AFAIR, from the xda tf700 forums). Neither worked.
So... if you got this going, what driver did you use? Thx!
I have a Win7 32 bit laptop and this cool little tool installed the drivers for me:
http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I'd installed that previously (easiest way to setup fastboot). Re-downloaded, re-installed. Went fine. Still no fastboot.
Unzipped the exe, looked at the drivers being installed - labeled "google". No google driver in the driver cache (so no device ever associated with it.)
Looked at the driver error again. Code 43. That means hardware or driver. I'd been taking it to mean driver, but... switched the USB cable to a port in the rear of the PC - and it worked.
Thanks!
So, for anybody with a similar issue, install the package above. If that doesn't work, maybe try a different USB port.
It works when booted into the OS but in recovery ADB is not recognized.
What drivers are you all using ?
stanglx said:
It works when booted into the OS but in recovery ADB is not recognized.
What drivers are you all using ?
Click to expand...
Click to collapse
On my mac ADB would not work in the stock recovery but it would work in CWM and fastboot. Think it is a driver issue.
I cant get it work anywhere and now I cant get stock recovery to work!
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS
stanglx said:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS
Click to expand...
Click to collapse
Thank you so much for this, I was pissed that I couldn't sideload.
On another note, does anybody see their device without the driver as "wx_un_mo"? I didn't think this was a valid model number considering the post at http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116 says it's a modem/wifi version.
Yes.. it was showing up as this for me too when in recovery but when in android OS it was fine... that is just the device ID . I kept uninstalling it until it showed as shield tablet with an ! in front of it. Now I think that was over kill.
Make sure your using the Nvidia Windows driver... There are two drivers that load
1. Bootloader driver
2. ADB Composite Driver
1 loads in fast boot only (bootloader)
2 loads in andorid OS (no issues typically) but when in recovery you have to force the driver install. If it doesnt work when in android OS (ie Lollipop, etc.) then do the same.. pick ADB composite driver.
MidgetMob said:
Thank you so much for this, I was pissed that I couldn't sideload.
On another note, does anybody see their device without the driver as "wx_un_mo"? I didn't think this was a valid model number considering the post at http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116 says it's a modem/wifi version.
Click to expand...
Click to collapse
stanglx said:
Yes.. it was showing up as this for me too when in recovery but when in android OS it was fine... that is just the device ID . I kept uninstalling it until it showed as shield tablet with an ! in front of it. Now I think that was over kill.
Make sure your using the Nvidia Windows driver... There are two drivers that load
1. Bootloader driver
2. ADB Composite Driver
1 loads in fast boot only (bootloader)
2 loads in andorid OS (no issues typically) but when in recovery you have to force the driver install. If it doesnt work when in android OS (ie Lollipop, etc.) then do the same.. pick ADB composite driver.
Click to expand...
Click to collapse
Yea I figured out the driver install fortunately, I was just curious as to why it was showing up as such. I didn't think that the specific model number was valid and was curious if anyone else had the same thing.
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.