Develop Bugs

[Q] ADB shell error 'adb error device not found'

Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.

I have always had to use "fastboot devices". Not sure if that is what u are looking for.
Sent from my Galaxy Nexus using Tapatalk 2

Uninstall all drivers and install those from the naked driver thread over in development.
'fastboot devices' is used only when on bootloader.
Sent from my i9250

no luck
No luck. Always get 'no drivers for you phone found'. I guess I should have mentioned that I'm on W7/64 I did notice that mentioned a lot in the threads........ Any need to select the type of USB connection (none is not an option) ?
TIA, Jeff

getting there......
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff

Try this drivers bro
Galaxy Nexus AOKP m5 Franco kernel m3

[email protected] said:
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Click to expand...
Click to collapse
That is because you just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, not the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.

Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff

[email protected] said:
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
Click to expand...
Click to collapse
Use the version of su.zip from this post. I just made it yesterday with the latest binary and app, so that one will work.

Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff

[email protected] said:
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
Click to expand...
Click to collapse
grab a cm9 nightly zip and extract apk from /system/app

pm setinstall location 2
if you want to set install location to sd card and move all apps to sd then read my thread http://forum.xda-developers.com/showthread.php?t=1754722

Bricked asus transformer prime
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks

NewDev4IOS said:
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
Click to expand...
Click to collapse
what tablet? this here is galaxy nexus q&a forum, thread was created 2 months ago.
oh and adb isnt available in bootloader, only recovery and android. boot to recovery.
Sent from my i9250

Solution
[email protected] said:
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
Click to expand...
Click to collapse
Make sure that you have your drivers properly installed. View this guide to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless : http://goo.gl/2Ehso
Hope it helps

adb won't list my Galaxy Nexus

Hi there,
I got the latest version of adb and have installed the latest pc driver for Galaxy Nexus from samsung's website under device SCHI515
But "adb devices" is still not showing the device. I can see the device listed in My Computer. I have gone thru "Computer/Manage/update the device driver" routine as well
and yes, I have searched thru the forums and none of the suggestions have helped me
Any ideas?

You need the adb drivers from the SDK.
Sent from my DROID RAZR MAXX HD

I looked into that as well. Apparently I am supposed to have a google directory in the "adb/sdk/extras" but there isn't one. There is only an "android" directory.
spencer88 said:
You need the adb drivers from the SDK.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse

mianbarray said:
Hi there,
I got the latest version of adb and have installed the latest pc driver for Galaxy Nexus from samsung's website under device SCHI515
But "adb devices" is still not showing the device. I can see the device listed in My Computer. I have gone thru "Computer/Manage/update the device driver" routine as well
and yes, I have searched thru the forums and none of the suggestions have helped me
Any ideas?
Click to expand...
Click to collapse
Which version of the SDK are you running? The 32 or 64.

do you have usb debugging turned on? sometimes an easy thing to skip over

mianbarray said:
I looked into that as well. Apparently I am supposed to have a google directory in the "adb/sdk/extras" but there isn't one. There is only an "android" directory.
Click to expand...
Click to collapse
1) get the "universal_naked_driver" from the GNEX forums
2) the fastboot/adb folder is sdk/platform-tools; rename the playform-tools folder into Android and move to the root of your C: drive
3) ???
4) profit

mianbarray said:
I looked into that as well. Apparently I am supposed to have a google directory in the "adb/sdk/extras" but there isn't one. There is only an "android" directory.
Click to expand...
Click to collapse
You need to launch the SDK manager and select the drivers from the list of things to download. After they download, they will be in that directory you listed.
Note: you need java installed in order to launch the sdk manager.

Can't install drivers.

Ok, this isn't my first rodeo as I've owned many android devices including the old nexus 7. I'm trying to unlock and root this but I can't install the drivers. I tried the device manager method and when I search it can't find anything and I tried a website to manually do it by downloading a zip and choosing it to no avail. Any one have the link to the drivers as that website may not of been accurate or anyone have any other suggestions?

You need to unzip it first.

Username invalid said:
You need to unzip it first.
Click to expand...
Click to collapse
Yes I did that and it only had two folders that showed up while browsing in the update drivers part in device manager. One was AMD86 and the other was i3 something and neither of those matched the picture in the steps but I used the link given within the same tutorial.

http://developer.android.com/sdk/win-usb.html

Username invalid said:
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Ok I still cannot install the drivers. When I downloaded the file provided in that link, there are no driver options at all. There are only two folders in which I described in my previous post and neither have drivers in them. I'm no noob and have done this plenty of times, I even tried to adb reboot bootloader and it says device not found and yes USB debugging is on so I'm assuming I can't do anything until I some how install the drivers.

Which website guide are you looking at?

Username invalid said:
Which website guide are you looking at?
Click to expand...
Click to collapse
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-

C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
If nothing else works, you might consider partitioning your hard drive and installing a secondary OS. Both Windows 8.1 and Ubuntu worked for me no problem.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads

C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...

I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.

C-4Nati said:
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...
Click to expand...
Click to collapse
Fastboot is all you need to root your device.

C-4Nati said:
I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.
Click to expand...
Click to collapse
I'm having a similar problem with drivers, why don't you post how you solved it? I am trying on 2 different windows 7 machines. google drivers don't load, asus drivers don't load. Device manager just says "windows could not find driver software for your device."
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
I figured it out, have to turn MTP on, then install drivers - then you can turn MTP back off if you want.

[Q] Hard Bricking

What are the odds of hard-bricking the Nexus 7 while rooting and istalling a custom kernel? And if it bricks, is there a way to fix it?
I ask this because I want to root it, but I'm really worried.
Also, how can you fix a soft brick?

I think you should really care of these questions if you somehow corrupt both bootloader and recovery. I don't really know, but bootloader isn't a thing that is modified during rooting or changing kernel. Just carefully read the thread about rooting programs, follow the instructions and everything should be ok. The most potentially harmful thing that can be done is corrupting the recovery. It can be solved if you have a computer with adb and drivers installed. Just a sшmple command and recovery is reflashed. Unlocking the bootloader is a kind of thing that doesn't really change anything so you couldn't boot or something. It just clears the storage and changes something deep inside. Flashing ROMS/Kernels is a kind of coping files and if something goes wrong you can always reflash it from recovery or with adb or some app from the rooting kit. And also you can always flash everything stock. Just read and think of what you're doing. Good luck.

Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?

LittleConfucy said:
Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?
Click to expand...
Click to collapse
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.

rtfpessoa said:
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.
Click to expand...
Click to collapse
So, what do I have to do?! Sorry, I'm a complete noob xD

LittleConfucy said:
So, what do I have to do?! Sorry, I'm a complete noob xD
Click to expand...
Click to collapse
Just run:
sudo fastboot oem unlock

rtfpessoa said:
Just run:
sudo fastboot oem unlock
Click to expand...
Click to collapse
It doesn't recognize sudo as a command

LittleConfucy said:
It doesn't recognize sudo as a command
Click to expand...
Click to collapse
Are you on windows?
If yes, are you on bootloader mode?
If not:
1-Power off
2-Power On + Vol. Down
Then you execute "fastboot oem unlock"
If it doesn't work try to use any of the auto tools that you can find all over XDA forums

LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.

Do you have any idea where can I see the drivers that were installed on the computer?

Slavon-93 said:
LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.
Click to expand...
Click to collapse
So I have to copy the file, paste it in the same directory, without deleting the previous file, and change its name?

Need help...
After I rooted, I opened BusyBox and it said:
"There was a problem opening a shell with root acces. This is either being caused by superuser/supersu or by a device that is inproperly rooted."
I downloaded root checker, and it says that it's not proprly rooted

Cant get fastboot to work!

I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?

Digital signature of the driver or wrong drivers is the problem

joedoctor said:
I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Click to expand...
Click to collapse
u are not saying mutch about how u are trying to enter fastboot
u do know the phone must be turn into fastboot right ?

...
same here, done everything i can...

mockneygeeza said:
same here, done everything i can...
Click to expand...
Click to collapse
to get fastboot to work u need to reboot the phone into fastboot

-fluffy- said:
to get fastboot to work u need to reboot the phone into fastboot
Click to expand...
Click to collapse
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol

moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
I'm going to try the above, it's never too late ?

moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers

-fluffy- said:
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
Click to expand...
Click to collapse
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.

moeq123 said:
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
Click to expand...
Click to collapse
im on windows 10 also an my adb devices also show nothing but i can still flash recovery an all