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] Flash system over cmd

I just erased everything on my sdcard (emulated) and the system. The only things left are recovery and bootloader. I read about sideload but it doesn't work for me, because my adb doesn't act out the command (My adb version is 1.0.29). So how could I transfer the rom onto my not existing sdcard? (If I do adb push all it says is: "E: /sdcard/ : is a directory")
Please help me as quick as possible. Thanks!

Try pushing it to
adb push c:/rom_name.zip /data/media
Click to expand...
Click to collapse

acreatorius said:
I just erased everything on my sdcard (emulated) and the system. The only things left are recovery and bootloader. I read about sideload but it doesn't work for me, because my adb doesn't act out the command (My adb version is 1.0.29). So how could I transfer the rom onto my not existing sdcard? (If I do adb push all it says is: "E: /sdcard/ : is a directory")
Please help me as quick as possible. Thanks!
Click to expand...
Click to collapse
I managed it by downloading the factoryimage from google and flashing userdata.img, but thanks for the quick reply

[q] SOLVED: ADB ROM PUSH ERROR: DEVICE NOT FOUND

EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1

lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways

lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app

when i tried to push error device not found lol

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.

If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.

Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks

lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.

sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.

tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*

xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.

UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1

Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again

HELP - full wiped my phone

_-_

phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/

_-_

adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??

_-_

Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....

_-_

phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj

Trying to Flash the Stock Rom Via ADB sideload

I am Trying to flash the stock rom via side load i flashed that few days back to at that time it was flashed success fully but now it always gives me error
Code:
"C:\android-sdk\platform-tools>adb sideload OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip
loading: 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip'
* cannot read 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip' *
C:\android-sdk\platform-tools>adb sideload <OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip>
The syntax of the command is incorrect.
C:\android-sdk\platform-tools>"

Mine would not sideload either. I downloaded the zip file to my PC, connected the phone to the PC, put the phone in USB mode, dragged the zip file from the PC to the phone root directory, disconnected from the PC, and flashed the ROM from the phone hard drive.

Faulty ADB drivers I guess. If you have TWRP you can try adb push name /sdcard/

Puddi_Puddin said:
Faulty ADB drivers I guess.
Click to expand...
Click to collapse
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.

bulletmark said:
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.
Click to expand...
Click to collapse
Second one is a invalid command because of those <> first command mainly happenda with wrong drivers, I and many other get the error it is quite unexplainable.

Any resolution to this? I'm getting the same problem, saying it cannot read the zip file when I try to sideload

trying to update my wifes phone now. getting the same issue. i typed in adb devices and it shows up, so i know its not driver related. wonder if its a faulty image? ill keep trying
---------- Post added at 03:59 AM ---------- Previous post was at 03:55 AM ----------
funny i think i just foud the issue. someone posted saying older adbs cant see larger than 1gb (i have a opo so never even heard of this). ill give it a try and report back...
this is the adb ill be using https://forum.xda-developers.com/showthread.php?t=2317790

Okay, now that may work for others but I could not get it... Sorry
I ended up just removing the encryption, flashing twrp, and flashing OOS that way. Make sure to make a backup... I made a backup of everything... Except contacts because I thought gmail handled that like on my phone. I left my wife a note saying sorry for when she wakes up ha.
At least the annoying updates available message will be gone that we've had since Aug or something

I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!

shoemocker said:
I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!
Click to expand...
Click to collapse
I used the same tool