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

[Q] Can't Sync Windows 8 with DInc

I am trying to sync my DInc with Windows 8 Pro to unlock it through the HTC developer site. Unrevoked wont work due to the version of my baseband being 2.15.10.12.20. Software version 2.3.4.
I have USB debugging enabled, fastboot off, performed a factory reset, cleared cache through HBOOT, and the computer DOES reckognize the phone and I am able to select open files and do whatever I need to do with the phone... it just wont display on HTCSync so I can go through the process of rooting it and getting JB on it.
I have also tried running HTCSync in compatability mode. I have been working on getting this working for days now, and have searched this and many other forums for solutions to no avail.
Any ideas would be greatly appreciated, and any more information you need will be provided asap.

Check the unrevoked site for the proper drivers of you haven't already. You don't need HTCSync to work, just adb.

PonsAsinorem said:
Check the unrevoked site for the proper drivers of you haven't already. You don't need HTCSync to work, just adb.
Click to expand...
Click to collapse
The baseband for this particullar device isn't supported by unrevoked, so I'm looking for other solutions. Ate there any other ways you know of to get jb on this phone?

cyborggold said:
The baseband for this particullar device isn't supported by unrevoked, so I'm looking for other solutions. Ate there any other ways you know of to get jb on this phone?
Click to expand...
Click to collapse
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.

PonsAsinorem said:
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
Click to expand...
Click to collapse
I can connect the phone and browse files through Windows explorer, I guess I'm just not familiar with adb yet, ill try to find more information on that and give it a try, thanks!

Still Lost
PonsAsinorem said:
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
Click to expand...
Click to collapse
I've been looking for the adb tool you had mentioned, but the only reference I am finding is for ICS/JB. I'm currently running Gingerbread (2.3.4 to be exact) Your last comment mentioned using a command 'adb devices' which makes me think adb is actually a command in windows or a linux application... I'm sure something I've said already has made you laugh at me so I'll stop now and just ask... can you give me a link to the process I need to follow to get this resolved, because for whatever reason, I can't find what I think you were trying to direct me towards.
Thanks!

cyborggold said:
I've been looking for the adb tool you had mentioned, but the only reference I am finding is for ICS/JB. I'm currently running Gingerbread (2.3.4 to be exact) Your last comment mentioned using a command 'adb devices' which makes me think adb is actually a command in windows or a linux application... I'm sure something I've said already has made you laugh at me so I'll stop now and just ask... can you give me a link to the process I need to follow to get this resolved, because for whatever reason, I can't find what I think you were trying to direct me towards.
Thanks!
Click to expand...
Click to collapse
How To Set Up Android ADB & Fastboot On Windows [Tutorial]
The only note on this guide I'd make, is not to use the C:\ drive. It's always a bad idea to put stuff in your root directory. Myself, I installed the sdk (which installed itself to C:\Program Files) then I added that to the system path. Also, you might have to reboot (or at least log off and log back on) to reset your PATH.

adb issues. tough case.

ok, I am really in dead end here. I think I spent on it more than 4 days, trying to figure it out. No luck, hopefully someone here can help.
My One isn't recognized under adb fastboot. And what I mean: under device managers it shows that the device is installed fine ( no yellow exclamation marks ). But when I try to adb, no luck. No devices recognized.
wait.. before you refer me to gadzillions of links - I've been there, seen them. What I did so far:
1) Installed linux ( live cd and normal ). When in the OS, I can browse my sd card. Once I reboot into fastboot, adb devices returns empty list.
2) installed htc drivers, naked drivers, universaladb drivers, intel usb3 drivers ( tried on both usb2 and usb3 ports )
3) various laptops and pcs
no luck. I am running out of ideas. What am I missing ? pliz help, I am desperate to adb to update recovery.
PS. Tried that on windows 7, 8, 8.1 and linux

If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en

mercer24 said:
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Click to expand...
Click to collapse
checking it right now. thank you

ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..

pRuben said:
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
Click to expand...
Click to collapse
I don't recall seeing it mentioned in any of the recipes, cookbooks or how-to postings, but I found that in Linux, you should run your adb and fastboot instructions either logged in as root, or using sudo.

Make sure you don't have any phone software installed on the computer as well. HTC sync and Kies can cause problems with adb. Also make sure that adb debugging is turned on in developer settings. You probably already did that, but ya never know, I overlook the simple stuff all the time.

did you take 4.3 update
If you did I have same issue with adb but fastboot options work just fine as long as your s-off if you need any help let me know i went and reloaded hboot and a cwm and also wrote my cid to super and unlocked through htc dev then changed my cid back to verizons

thanks guys, yep, HTC sync manager was installed /uninstalled. Not sure what what's kies. Also I executed sudo on linux. Nothing freaken works. I am s-off unlocked via sonic. Drives me insanely mad. Seems like this phone just refuse to work with me.

I know this might seem like a dumb idea but have you tried a different cable? Are you using the one that came with the phone?

I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app

xenakis said:
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Once in a while I get humbling experience, that reminds me that simple solutions are right in the front of me Xenakis. You are correct, I was trying to get adb under fastboot, which didn't return anything. Fastboot devices did. From there it was all straight up road to what I needed. Sorry to bother you guys with this, I though it was more complicated that this. It just appears like my ignorance of basic adb commands got the best of me. Thank you for helping me out.
Merry Christmas

Why does Android hate Linux so

No seriously
5 Hours later and I have been unable to root... I want to kill something.
I remember the days of copy zip across, reboot, load zip, reboot all done.
Now I can't adb over mtp for god knows why, once I get around that now I can't upload files because permission denied and the only lollipop workarounds I have found are for windows (ftlog, why do I bother).
Has anyone here managed to root their D855 on linux (Android 5.0+)
Why LG, I went through this with the S4. Don't ruin a good thing before it's begun

Have you enabled USB debugging in the developer options on Android. And are you using sudo or su with adb on Linux?
Sent from my LG-ls990 using XDA Free mobile app

smokey_circles said:
No seriously
5 Hours later and I have been unable to root... I want to kill something.
I remember the days of copy zip across, reboot, load zip, reboot all done.
Now I can't adb over mtp for god knows why, once I get around that now I can't upload files because permission denied and the only lollipop workarounds I have found are for windows (ftlog, why do I bother).
Has anyone here managed to root their D855 on linux (Android 5.0+)
Why LG, I went through this with the S4. Don't ruin a good thing before it's begun
Click to expand...
Click to collapse
I rooted my device in Linux with PurpleDrake when I had Kitkat, now I'm upgrading only with TWRP (stock bumped zip file), but nevertheless ADB works for me even after upgrade to Lollipop.
When the phone is connected with PC, you should select PTP mode.
If the phone is not recognized by ADB command, follow this guide.

mister_no said:
I rooted my device in Linux with PurpleDrake when I had Kitkat, now I'm upgrading only with TWRP (stock bumped zip file), but nevertheless ADB works for me even after upgrade to Lollipop.
When the phone is connected with PC, you should select PTP mode.
If the phone is not recognized by ADB command, follow this guide.
Click to expand...
Click to collapse
Thanks man, managed to get ADB working over PTP. Is there any drawback to this?
I also discovered my fatal mistake was using a kit kat guide that was butchered to be a lollipop guide. Lack of sleep and over-excitedness led to a bootloader lock. Flashed the stock kit-kat ROM, rooted and I'm finally running CM12 nightlies.
No major bugs that irritate me, smooth and responsive. Very happy with the G3

smokey_circles said:
Thanks man, managed to get ADB working over PTP. Is there any drawback to this?
Click to expand...
Click to collapse
Not to my knowledge.
Actually when the device is in bootloader the connection protocol is MTP.
You can check it yourself with lsusb command that device's USB ID (idVendor & idProduct) is different for PTP than for MTP. In bootloader device has the same USB ID as when it is running normally and MTP mode is selected.

Question How to install factory image using Linux

Hey guys,
I was trying to update while keeping root and made a mistake. i don't think my phone is hard bricked, as it does boot, it just never actually reaches the stock
When device boots, it says "device is corrupt, it can't be trusted and may not work properly". This happened after I tried to utilize the Master-Root.img file. Not sure exactly how this happened, I will investigate later, but right now trying to get something on my phone (right now it just doesn't boot past the error message I just mentioned)
I looked online, and I've heard methods about using a flash-all.bat and flash-all.sh file within the factory image. However, I'm using linux, not windows, these files so not seem to work.
for the record:
bootloader is unlocked
phone was rooted prior to this happening
i don't deny i made some kind of mistake that resulted in this happening, i just don't know what yet. i will investigate, but right now just trying to recover my phone. there does not appear to be an OS on it, or it is corruped
i will post any images that are needed, im just under a time constraint
i have the factory image on my computer already. what do i need to do to get this installed? i looked up tons of guide, but it only seems to be applicable for windows.
thanks so much in return btw!

You can use Android Flash Tool. Flash-all.sh should work on LInux as well. But Android Flash Tool is probably the easiest way.

Lughnasadh said:
You can use Android Flash Tool. Flash-all.sh should work on LInux as well. But Android Flash Tool is probably the easiest way.
Click to expand...
Click to collapse
is Android Flash Tool a windows only program? or does this work on Linux too? because linux is all i have at the moment.

pojr said:
is Android Flash Tool a windows only program? or does this work on Linux too? because linux is all i have at the moment.
Click to expand...
Click to collapse
Yes, supports Linux.
Android Flash Tool | Android Open Source Project
source.android.com

Lughnasadh said:
Yes, supports Linux.
Android Flash Tool | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thanks so much. I will try this out. For the record, I actually did go into flash-all.bat and I noticed the individual terminal commands it wanted me to put in. So I tried putting them in manually, but after I finished the commands and rebooted the phone, I still received the same message "device is corrupted, it can't be trusted".
I will still try the tool that you linked though, but I'm nervous it won't help because I tried running the commands individually that were within the flash-all file.
Later on I will go into more detail on what I mean, but I'm at work right now and I don't have a lot of time to type.

pojr said:
I looked online, and I've heard methods about using a flash-all.bat and flash-all.sh file within the factory image. However, I'm using linux, not windows, these files so not seem to work.
Click to expand...
Click to collapse
I'm on linux (fedora) and the flash-all.sh script will work, but you have to ensure adb and fastboot drivers are installed system-wide or you run your terminal from platform-tools. If you want to be able to run the script from any directory, you'll have to edit your bash config to point to the directory of your platform-tools. You may also need to edit your udev rules.
Bash
sudo nano .bashrc
export PATH=${PATH}:/home/YOUR-USERNAME/path/to/adb
udev Rules
See github page for instructions, assuming your distro requires it.
Linux Fix Fastboot "no permissions, verify udev rules"
Linux Fix Fastboot "no permissions, verify udev rules" - fbootfix.md
gist.github.com
Edit: If you're on any distro with an up-to-date version of android-tools, you can install the package and it will automatically install the adb/fastboot drivers system-wide and you can skip the above manual process. Otherwise, if android-tools is too old, fastboot won't work and the shell script will end abruptly as it's out-of-date compared to the most recent A12 or A13 builds.

pojr said:
Thanks so much. I will try this out. For the record, I actually did go into flash-all.bat and I noticed the individual terminal commands it wanted me to put in. So I tried putting them in manually, but after I finished the commands and rebooted the phone, I still received the same message "device is corrupted, it can't be trusted".
I will still try the tool that you linked though, but I'm nervous it won't help because I tried running the commands individually that were within the flash-all file.
Later on I will go into more detail on what I mean, but I'm at work right now and I don't have a lot of time to type.
Click to expand...
Click to collapse
One method to get rid of the corrupt message that has worked for people is to flash the boot image from the prior month in fastboot (it will likely not boot) and then flash your current boot image.

Lughnasadh said:
One method to get rid of the corrupt message that has worked for people is to flash the boot image from the prior month in fastboot (it will likely not boot) and then flash your current boot image.
Click to expand...
Click to collapse
I will try that as a last resort (if all else fails)
To go into more detail, when I opened up terminal, I migrated to the folder that has the flash-all files (both the .bat and .sh) by typing "cd [folder name]", however I didn't know how to run those scripts in terminal, even after googling. So I opened the .bat file in text editor and notice the script had 3 or 4 fastboot commands.
Since I couldn't get flash-all file to run on its own, I tried manually typing in fastboot commands right into the terminal. The first fastboot commands seems to run without any problems, but then the final fastboot command seems to have issues. While it ran, they were a bunch of files it could not find. But still, it didn't give a error or anything. So once the three or four fast food commands were ran, then I rebooted the device, and still received the "device is corrupted, device cannot be trusted" error.
Still haven't downloaded that program you linked to yet, I apologize. I have to wait until lunch to try this because I'm at work. Don't you hate it when you're running to issues right before work? Haha.

pojr said:
To go into more detail, when I opened up terminal, I migrated to the folder that has the flash-all files (both the .bat and .sh) by typing "cd [folder name]", however I didn't know how to run those scripts in terminal, even after googling. So I opened the .bat file in text editor and notice the script had 3 or 4 fastboot commands.
Click to expand...
Click to collapse
Use the batch file (.bat) on windows and use the shell script (.sh) on linux. They both execute the same commands based on the OS.
To run the shell script from terminal, type:
sh flash-all.sh

lottarake said:
Use the batch file (.bat) on windows and use the shell script (.sh) on linux. They both execute the same commands based on the OS.
To run the shell script from terminal, type:
sh flash-all.sh
Click to expand...
Click to collapse
thank you. i just tried this. says "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
not a problem. you did mention i need to install the latest platform tools. so i did, and tried again. same error message, fastboot too old. now i'm on the latest platform-tools, so not sure why i'm receiving that message.
currently installing android flash tool right now. having difficulties because (for some reason) chrome is required. i'm on firefox. but i will update once it's all installed. thanks again for the support btw.
Update: On the android flash tool right now. So far I like what is happening. Didn't realize how easy this is. I am a little concerned though, because while the site appears to be working as intended, my phone is still on the fastboot screen with nothing on it, but that might be normal. I'll keep waiting and see what happens.

pojr said:
thank you. i just tried this. says "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
not a problem. you did mention i need to install the latest platform tools. so i did, and tried again. same error message, fastboot too old. now i'm on the latest platform-tools, so not sure why i'm receiving that message.
currently installing android flash tool right now. having difficulties because (for some reason) chrome is required. i'm on firefox. but i will update once it's all installed. thanks again for the support btw.
Click to expand...
Click to collapse
If the latest adb/fastboot drivers aren't system-wide and you're running the commands from any other directory other than from the platform-tools folder, you'll get the out-of-date error. If you want to run it from the directory, make sure to add "./" (without quotes) before adb/fastboot.
Example:
./adb devices
If you edit your bash config to point to the new platform-tools folder, it'll execute adb/fastboot from the latest you've downloaded as system level versus what was installed on your OS previously.

lottarake said:
If the latest adb/fastboot drivers aren't system-wide and you're running the commands from any other directory other than from the platform-tools folder, you'll get the out-of-date error. If you want to run it from the directory, make sure to add "./" (without quotes) before adb/fastboot.
Example:
./adb devices
If you edit your bash config to point to the new platform-tools folder, it'll execute adb/fastboot from the latest you've downloaded as system level versus what was installed on your OS previously.
Click to expand...
Click to collapse
Thank you. I will look into that.
So at the moment, I'm running the Android flash tool. Seems to be pretty straightforward, but the download keeps starting over. Is that supposed to happen? Or is there something wrong? My apologies if I'm sounding like an idiot right now

pojr said:
Thank you. I will look into that.
So at the moment, I'm running the Android flash tool. Seems to be pretty straightforward, but the download keeps starting over. Is that supposed to happen? Or is there something wrong? My apologies if I'm sounding like an idiot right now
Click to expand...
Click to collapse
Not quite sure the reason it's restarting tbh. It should only download the zip once and then proceed to flash as long as it's properly connected to the phone. When using the Android Flash Tool, I stick to Chrome since it seems to work properly for me. I haven't tested it with Firefox yet. You could always reset the adb access to Firefox by disconnecting the phone and closing the browser, then from terminal run "adb kill-server" before reconnecting and granting adb to Android Flash Tool again.

lottarake said:
Not quite sure the reason it's restarting tbh. It should only download the zip once and then proceed to flash as long as it's properly connected to the phone. When using the Android Flash Tool, I stick to Chrome since it seems to work properly for me. I haven't tested it with Firefox yet. You could always reset the adb access to Firefox by disconnecting the phone and closing the browser, then from terminal run "adb kill-server" before reconnecting and granting adb to Android Flash Tool again.
Click to expand...
Click to collapse
I'm on Chrome now. I think it might just be poor USB connection. I moved it to a safer position, so hopefully that will fix the problem. Seems like it's installing now. I'm having some really bad luck today lol.

Good news. I checked my phone just now, it is now booted without any issues. Thank god. Long story short, I ran into some issues trying to perform an OTA update while keeping root access, but ran into issues while following the directions. So I started troubleshooting the problem and went a little too far with it. Thanks so much @lottarake and @Lughnasadh for helping me out.
Not sure if the OS will remain on there if I reboot the device. I assume so, because the OS was installed, not just flashed.