I have a NS (i9023) with stock 4.0.3. I want to connect by ADB so that I can unlock my bootloader. I followed this guide: http://forum.xda-developers.com/showthread.php?t=1007782
I enabled USB debugging (settings, developer options), downloaded the SDK (v17), added the following to android_winusb.inf
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
later I also tried adding:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&MI_01
When I connect & start up my NS with power/volume up, it triggers the installation of the ADB drivers & in device manager I get 'android ADB interface' listed.
If I then go to a command prompt, go to the platform-tools folder & run 'adb devices' it shows that no devices are connected.
Any suggestions where I've gone wrong?
Try install pdanet drivers
http://junefabrics.com
You don't need install pdanet app on ur phone as long u have drivers u might get some errors if u press not install but will work anyway.
Hope this will help.
Sent from my Nexus S using Tapatalk
No go I'm afraid - I tried installing it, it added a new USB driver, but when I connected the phone, it still wasn't detected by ADB. In fact the ADB driver is still listed as the google one in device manager....
You definitely in recovery mode when trying to connect via adb right?
Sent from my Nexus S using Tapatalk
So when the phone is fully booted up into proper android, I have adb access - adb devices lists it correctly & I can issue commands correctly.
When I reboot the phone & hold down volume/power, I get to a menu that has the options 'reboot bootloader, reboot, recovery'. At that point I do not have adb access - adb devices doesn't list anything.
If I select 'recovery' then I get the google logo, a picture of andoid with an exclamation mark over it, then the screen goes blank because of the well known backlight issue in 4.0.3. At that point, I still do not have adb access - adb devices does not list anything. I can't see whether there is anything on the screen because there's no backlight.
According to what I've read, I should have adb access at the 'reboot, recovery' menu, shouldn't I?
You'll definitely have adb access in a custom recovery, though i'm not sure about stock recovery as i've never tried it. You can use a bright lamp to view the recovery, at first it'll be that exclamation and android. It will stay like that until you press Power + Vol. Up (note, power first), then it will be into stock recovery. Try after doing that extra step to get adb working, though i wouldn't be surprised if that doesn't work.
At the bootloader menu (reboot, recovery, power off, etc) fastboot should be working, not adb. You can do "fastboot devices" and it should show your phone.
Doh! I can't believe it was that simple - from all the guides I read I just assumed that ADB worked in both environments. I didn't realise fastboot & ADB were different things. Thanks for the help
richstant said:
Doh! I can't believe it was that simple - from all the guides I read I just assumed that ADB worked in both environments. I didn't realise fastboot & ADB were different things. Thanks for the help
Click to expand...
Click to collapse
Happy to help
Related
have tried to figure out how to turn off aria when connecting the usb and adb devices does not list device. reboot is the next step (volume up and power) and device always reboots and it seems impossible to hold down volume and power and get back into HBOOT / RECOVERY
question is, is it possible to reboot directly into HBOOT ?
Cancel the loop, reboot the phone, and send "adb reboot bootloader" from the prompt, when the HTC Quietly Brilliant screen appears.
seboj said:
Cancel the loop, reboot the phone, and send "adb reboot bootloader" from the prompt, when the HTC Quietly Brilliant screen appears.
Click to expand...
Click to collapse
how can I send *any* adb commands when I am unable to see device?
Can you see the phone in adb when it is powered on normally for use? If you can then when the HTC Quietly brilliant screen comes up your computer should be able to connect to the phone through adb. If it does not then you will want to uninstall HTC Sync and re-install it.. ( if you are running Window) make sure you have no anti-virus or malware scanners running/active as those create havoc causing HTC Sync to not install correctly and the drivers necessary for Windows to see the phone properly to not get installed.
Yes, I can see when normally connected but that was not my original question.
I do not have HTC Sync installed, only SDK USB drivers.
Repeat of my original question:
"..how to turn off aria when connecting the usb and adb devices does not list device. reboot is the next step.."
The reason I ask this, is that as I sit on the REBOOT screen and LOOP is running in background, if adb devices does not see phone, when I press power it will automatically reboot and power up all the way to main menu where I have to (again) do a total power shutdown in order to see HBOOT and RECOVERY.
I am trying to get faster to HBOOT and RECOVERY since adb devices is not listing device.
Is that clear now?
Your question was already answered in post 2. Use adb reboot bootloader at the quietly brilliant screen.
hi2u2 said:
Your question was already answered in post 2. Use adb reboot bootloader at the quietly brilliant screen.
Click to expand...
Click to collapse
wonderful. if only it worked, which it does not since adb (anything) does not work since adb (any command) does not see device
xdafly said:
wonderful. if only it worked, which it does not since adb (anything) does not work since adb (any command) does not see device
Click to expand...
Click to collapse
Have you actually tried though?
If you can see your phone in adb devices when it is loaded into Android, then you should be able to send the adb reboot bootloader after you reboot from recovery. The fact that the phone doesn't list during the loop is irrelevant. Once you've rebooted the phone from recovery, and the phone displays the Quietly Brilliant logo, then it has loaded enough to be recognized by the computer, and the adb command will work, and instantly reboot the phone into the hboot screen.
If the command doesn't work, double check to make sure your command prompt is in the right directory with all the right files, try installing Sync, and / or try reinstalling your driver.
My vibrant is stuck on the vibrant logo after I tried to use the one click unroot program. The only solution I found after two days searching on the net, is to use odin. The first problem is that my phone is locked, so I can't use the vol up+down+power button combo to get into recovery or download mode.
Now comes the issue, I want to use adb to reboot the phone, but adb can't see my device. After installing the samsung USB Drivers, I see that the adb drivers are not installed (The drivers for this device are not installed. (Code 28)), and even when I try to manually install them from the SDK drivers (I checked the "include subfolders) it says that it can't find them.
I have windows 7 x64
Anyone have suggestions to how to install the adb drivers and make the adb see my device?
Can you get into download mode? Have you tried to Odin back to stock? If you want to set up ADB type ADB for dummies in search and you should find everything you need.
Here is the link from the sticky thread for help with drivers:
http://forum.xda-developers.com/showthread.php?t=728929
I just figured out a neat trick to get phone to work even if it's stuck on the vibrant screen.
Just connect it to the usb, wait until the grey battery picture appears.
After 5 seconds, take the battery out and put it right back, (leave usb in) and wait again. Do it once more, until you see that the battery picture turns green. After that take the battery out and unplug the usb, and turn the phone on.
It should work now.
The thing is that, next time you turn the phone off and on, it would be stuck again, so do something to fix it like odin.
That how it worked for me.
And about the adb driver problem, I just pointed manually the driver update to the "USB Drivers" that TGA_Gunnman posted here (I can't post link. just search usb drivers here in the forum) and after that adb worked like a charm, rebooted instantly to download mode - it's crucial for those like me that have hardware locked phones.
The thing is, that all the other posts say to point it to the sdk drivers, but that dosen't work.
Good luck to all others.
installing the samsung drivers and installing adb are two different things. the samsung drivers should install normal by double clicking the driver package (you may have to still tell windows where to look). installing adb is simply downloading the sdk, however, if you want adb to work everywhere (instead of just the sdk/tools folder) you need to put the sdk/tools folder in your path.
then 'adb devices' should show your device in win powershell, but will only work if you are in the sdk/tools folder or have added it to your environment variables.
So I was following the tutorial HERE to install TWRP, after successfully installing root via the previous tutorial.
I got to the step where you have to hit "reboot" on the kindle screen, and then press any key in the CMD prompt. I waited till it was on the yellow triangle screen, with text at the bottom stating I can press power button for recovery. I hit "space" to progress my installation, and it got stuck at "activating normal <4000>" as the video said might happen.
Following the instructions, I opened Device Manager and sure enough, the kindle was displaying a missing driver icon (although mine was still called kindle, in the video it was called something else.) I told it to reinstall the drivers, and this is where it got strange. It claimed the driver was up to date, but still displayed the yellow driver error symbol. Now, when I plug in the kindle, it shows up as "unknown device" and when I try to install the driver, it claims my driver for unknown device is up to date.
Meanwhile, the kindle itself it chilling on the yellow fire/triangle screen.
wat do
It says your drivers are up to date? You shouldn't be trying to auto install drivers, you have to do it manually, or are you trying but its just not letting you?
I am manually selecting the folder in the Device Manager dialog, and it tells me that the driver for "unknown device" is up to date
I have found that if I turn the kindle off by holding the power button down, then plugging it in(while off) it will show up as "ADB Device" (not ADB Composite Device), but nothing works, and if at this point it is unplugged and re-plugged in, it returns to Unknown Device giving an error code 43
Okay getting to adb device works, reinstall the drivers like your supposed to under that and then use KFU to try to get it to boot normally
googlelover said:
Okay getting to adb device works, reinstall the drivers like your supposed to under that and then use KFU to try to get it to boot normally
Click to expand...
Click to collapse
well, I got it to display "ADB Composite Interface, but when I run the KFU, it says ADB Status: Offline.
Furthermore, when I run "adb devices" my kindle does not show up
What device IDs do you have listed in %userprofile%\.android\adb_usb.ini? I know most people only list one ID but I found that a surefire way to get the driver working is to have both 0x1949 and 0x18D1. You also need to have those IDs in android_winusb.inf
This was the only way I could get my Kindle to be recognized while in recovery
SirVilhelm said:
What device IDs do you have listed in %userprofile%\.android\adb_usb.ini? I know most people only list one ID but I found that a surefire way to get the driver working is to have both 0x1949 and 0x18D1. You also need to have those IDs in android_winusb.inf
This was the only way I could get my Kindle to be recognized while in recovery
Click to expand...
Click to collapse
I added the 0x18D1 to adb_usb.ini, and I beleive it was already in the other .inf file. Now, my kindle is connected, and device manager sees adb composite device, but adb devices says nothing is connected. Im feeling a reboot might be necessary, which sucks because my computer doesnt reboot well (long story)
You can try adb kill-server and try again
Trouble
Having trouble getting TWRP to install on my Kindle Fire, I had no problems getting it Rooted and getting the Market installed, but trying to run the TWRP program it just hangs at the waiting for device and the Kindle hung at the KindleFire logo. I'm running Window's 7 64 bit is this suitable for TWRP
Thanks for any help.
SirVilhelm said:
You can try adb kill-server and try again
Click to expand...
Click to collapse
it is still not seeing the kindle connected. Anyway, how do I use KFU to restore the device?
I fixed my device using the info I found in a thread: http://forum.xda-developers.com/showthread.php?t=1431785
fastboot oem idme bootmode 4000
fastboot reboot
Unplug your Fire from USB, turn it off (hold the power button ~30 sec), run the first fastboot command above, then plug it in. If the first command completes, do the second.
Click to expand...
Click to collapse
It's weird.
I had my HD8-6G on v5.3.1.0 (now, v5.3.1.1).
I installed the Amazon Fire Drivers that were on the Amazon developer website. But, my Win7x64 PC complained that it still didn't recognize the HD8 device while it was in ADB mode. So, I manually selected the Amazon.com ADB Composite Device for my updated driver. This works ... partially
If I booted the HD8 into "adb sideload" mode, the HD8 was properly recognized, and I was able to install the v5.3.1.1 update. However, the tablet is still not visible when I did an adb devices command. in my ADB / Fastboot shell. I tried running KingoRoot, and the tablet wasn't discovered.
How can I get ADB working properly on Win7x64?
¿GotJazz? said:
It's weird.
I had my HD8-6G on v5.3.1.0 (now, v5.3.1.1).
I installed the Amazon Fire Drivers that were on the Amazon developer website. But, my Win7x64 PC complained that it still didn't recognize the HD8 device while it was in ADB mode. So, I manually selected the Amazon.com ADB Composite Device for my updated driver. This works ... partially
If I booted the HD8 into "adb sideload" mode, the HD8 was properly recognized, and I was able to install the v5.3.1.1 update. However, the tablet is still not visible when I did an adb devices command. in my ADB / Fastboot shell. I tried running KingoRoot, and the tablet wasn't discovered.
How can I get ADB working properly on Win7x64?
Click to expand...
Click to collapse
this might be silly, but make sure you have developer mode enabled/adb enabled. also enable unknown sources in security. I would think it should show up when you issue adb devices..how strange.
* also I like to check stay awake.
Those are the very same drivers (fire usb for everything except recovery, and the android ones for the adb composite for recovery) I used and I'm on Windows 7 64 Bit.
* I just put my device in recovery mode and yeah it says android composite adb interface 10/27/2014 1.4.0.0 Amazon Services
hmm..actually it says the same when i reboot
smokejumper76 said:
this might be silly, but make sure you have developer mode enabled/adb enabled. also enable unknown sources in security. I would think it should show up when you issue adb devices..how strange.
* also I like to check stay awake.
Those are the very same drivers (fire usb for everything except recovery, and the android ones for the adb composite for recovery) I used and I'm on Windows 7 64 Bit.
* I just put my device in recovery mode and yeah it says android composite adb interface 10/27/2014 1.4.0.0 Amazon Services
hmm..actually it says the same when i reboot
Click to expand...
Click to collapse
I have all the same settings you list above, but the ADB device isn't being found.
I also don't get prompted for an RSA key. Could that be related? I may have been prompted previously, but I don't think so. This is the first time I think I did any ADB stuff on this tablet.
¿GotJazz? said:
I have all the same settings you list above, but the ADB device isn't being found.
I also don't get prompted for an RSA key. Could that be related? I may have been prompted previously, but I don't think so. This is the first time I think I did any ADB stuff on this tablet.
Click to expand...
Click to collapse
yes, you must get prompted for RSA key. If you disable usb debugging, then reenable it (with tablet still connected) you should get a prompt and check remember. That definitely is an issue if that never was applied.
* also I like to make sure stay awake is on. In addition, whenever you reboot the tablet, upon rebooting, I like to make sure the screen is unlocked and sometimes you need to quickly unplug it, then replug it back it once it's rebooted for the device to show up in my computer.
Choose Files
So I have been flashing android devices for a few years. I would not call my self an expert, but I know a little about ADB and follow directions well.
So I have a New Shield pro, and when I go to boot into recovery I get the Dead Android sign "NO Command" and directions updated on the 1/17 said this is to be expected hold the power button down and navigate to the next menu. So when I get to the next menu I only have one option that allows connection to ADB apply update from ADB, So if I select that I get send packages to the device with ADB sideload. I can check adb connection and I have my string of numbers, but I can't get it to respond to any ADB commands If I do the oem unlock command it just sits there and says waiting on device. Won't log into fastboot either.
Any suggestions would be appreciated.
Delete please seems to have been a bad driver.
Then please edit the title and add [SOLVED] at the beggining
Enviado desde mi Moto X via Tapatalk!
how did you fix exactly? because i have correct adb connection (it sees device properly) but fastboot drivers arent working, no fastboot connection. it has a yellow exclamation in device manager.
dontbeweakvato said:
how did you fix exactly? because i have correct adb connection (it sees device properly) but fastboot drivers arent working, no fastboot connection. it has a yellow exclamation in device manager.
Click to expand...
Click to collapse
Since no one is replying, I'll help. You need the Shield Family USB drivers, or the standard android drivers for fastboot. Then you select the driver manually, not just the folder, but point it to the right .inf file, android_winusb.inf, from where you choose to install Android Bootloader Interface. So, add driver manually.
mr-tee said:
Since no one is replying, I'll help. You need the Shield Family USB drivers, or the standard android drivers for fastboot. Then you select the driver manually, not just the folder, but point it to the right .inf file, android_winusb.inf, from where you choose to install Android Bootloader Interface. So, add driver manually.
Click to expand...
Click to collapse
Yes I fixed it that day I think. I have a new win 10 computer and wasn't used to it. But I figured out how to point it to the driver's. Man it was a pain in the ass