adb push filename.xxx not working for me! - Nexus 5 Q&A, Help & Troubleshooting

Hi all,
I want to learn to push files to my phone through adb push command, so I load into bootloader, then type "fastboot devices" , my phone showed up with no problem, but then i type
adb push rom.zip /sdcard/rom.zip
it gives me a message
"error: device not found"
did I do something wrong?

Can't use ADB in bootloader.
Sent from my Nexus 5 using Tapatalk

0dBu said:
Can't use ADB in bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
didn't I use adb in bootloader to install the teamwin recovery? ( i mean as i remembered)
ok, now its another issue, assuming i need to use adb in recovery mode. when i boot into recovery, my win 7 own't recongnize my device, but when i am in the 4.4 operatiing system or bootloader mode, my pc recongnize my device with no problem

david0916 said:
didn't I use adb in bootloader to install the teamwin recovery? ( i mean as i remembered)
ok, now its another issue, assuming i need to use adb in recovery mode. when i boot into recovery, my win 7 own't recongnize my device, but when i am in the 4.4 operatiing system or bootloader mode, my pc recongnize my device with no problem
Click to expand...
Click to collapse
Force install the driver. I had the same problem.

david0916 said:
didn't I use adb in bootloader to install the teamwin recovery?
Click to expand...
Click to collapse
No. You used fastboot. Fastboot commands in fastboot. Adb commands in recovery or android
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

Dr Tone said:
Force install the driver. I had the same problem.
Click to expand...
Click to collapse
Thanks for your reply, what do you mean by force install the driver? and do you have the link to the driver or is it included in the SDK already?

david0916 said:
Thanks for your reply, what do you mean by force install the driver? and do you have the link to the driver or is it included in the SDK already?
Click to expand...
Click to collapse
The one in the SDK.
Sent from my Nexus 5 using Tapatalk

If you're still having problems I recommend reading this guide. How to Use “adb sideload” to Update a Nexus Without Root or Custom Recovery
But when you get to the part of the guide where you have to type in "adb sideload <filename.zip>", you might have to refer to this to solve it.
I myself have just installed 4.4.2 using this method. Camera SO much faster now.

Related

[Q] Fastboot does nothing!

Hey,
i just wanted to flash the newest clockworkmod but my fastboot.exe does nothing.
Phone is in fastbootmode, please help
Windows 7 x64...but it worked the other day
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Fmbl said:
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Click to expand...
Click to collapse
i can flash the recovery fia ROMManager, and also can boot into it, but when i boot the phone into bootloader/fastboot mode i can't flash a new recovery, because when i hit enter after "fastboot" i get no output in cmd
If you don't get anything back on fastboot devices, then you either don't have the proper drivers installed, don't have the phone in fastboot mode, or don't have the phone connected via USB. Probably the first one.
Easiest way to get the fastboot drivers is to simply install PDA Net on your computer and follow the on screen prompts. It will automatically install the appropriate drivers for your device.
Sent from my Nexus S using XDA App
thanks, i will try when i am at home again
Sent from my Nexus S using XDA App
Check in device manager that the ADB Bootloader driver is installed.
zero383 said:
Check in device manager that the ADB Bootloader driver is installed.
Click to expand...
Click to collapse
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
eiabea said:
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
Click to expand...
Click to collapse
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
matt2053 said:
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did it very carefully, but no success
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
ericshmerick said:
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
Click to expand...
Click to collapse
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
zero383 said:
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
Click to expand...
Click to collapse
Yes and yes.
May want to continue here:
http://forum.xda-developers.com/showthread.php?t=1303522
Had the same issues, although drivers were installed. After including "C:\android-sdk-windows\tools"
and "C:\android-sdk-windows\platform-tools"
in the path of win7 (systemvariables)
and a restart adb and fastboot worked.

Rooted Phone, But Have To Issue SU To See In ADB?

Boy, this is frustrating! So after fixing Windows broken drivers, HTC's inability to support Windows 8, and about a dozen other things that have gone wrong, I am now trying to understand why, after rooting my phone, SU permissions is not granted automatically from the bootloader.
I'm just trying to update to a newer version of CM. When I issue "adb devices", nothing. Finally, I figured something out. If the phone is booted into CM, I got into the emulator, and issue "su" - and the prompt changes from $ to #, bingo, device shows up in ADB devices. I wouldn't be able to switch to SU if the phone weren't rooted right? I mean, I'm already running CM, so phone must be rooted?
I can't really issue "SU" from bootloader.
Not sure what to do. Can someone assist?
Thanks so much!
You don't use adb in bootloader, you use fastboot
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
You don't use adb in bootloader, you use fastboot
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Yes, sorry, that is what I meant. I was in fastboot. It says fastboot usb. I see "My HTC" in the device manager. But adb devices is empty. If I boot it up, start term mon, and issue "su", then adb devices shows the phone.
demkantor said:
You don't use adb in bootloader, you use fastboot
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Or, are you saying I wouldn't even need to see it as a device in ADB devices in order to issue the fastboot command you specified above?
Correct, you should not be using adb when in bootloader, use fastboot, adb is only for in recovery and os
Sent from my Nexus 4 using Tapatalk 2

[Q] Nexus 5 bricked and USB cable not working

I bricked my Nexus 5 by installing the kernal from touchcontrol.
I can get into recovery mode.
I can not mount the USB storage or access any of my phones files
I've tried installing ADB drivers but that didn't help.
Anyone know what I should do to fix this?
BleachFan21 said:
I bricked my Nexus 5 by installing the kernal from touchcontrol.
I can get into recovery mode.
I can not mount the USB storage or access any of my phones files
I've tried installing ADB drivers but that didn't help.
Anyone know what I should do to fix this?
Click to expand...
Click to collapse
Download the stock kernel zip from here https://www.androidfilehost.com/?fid=23269279319202404 and place it in the fastboot folder. Then reboot in recovery and choose adb sideload. Open cmd and type : adb sideload namekernel.zip and press enter and that should do it, then reboot.
gee2012 said:
Download the stock kernel zip from here and place it in the fastboot folder. Then reboot in recovery and choose adb sideload. Open cmd and type : adb sideload namekernel.zip and press enter and that should do it, then reboot.
Click to expand...
Click to collapse
How do I place it in the fastboot folder?
BleachFan21 said:
How do I place it in the fastboot folder?
Click to expand...
Click to collapse
Copy it to the android-sdk/platform-tools
gee2012 said:
Copy it to the android-sdk/platform-tools
Click to expand...
Click to collapse
Is that a type of program? USB isn't working on my phone as even though it makes the connecting sound when I plug it in it's not appearing on the explorer
BleachFan21 said:
Is that a type of program? USB isn't working on my phone as even though it makes the connecting sound when I plug it in it's not appearing on the explorer
Click to expand...
Click to collapse
Sorry, you`re right. Well without usb you can`t do anything. Have you made a nandroid backup to restore in recovery?
gee2012 said:
Sorry, you`re right. Well without usb you can`t do anything. Have you made a nandroid backup to restore in recovery?
Click to expand...
Click to collapse
no
BleachFan21 said:
no
Click to expand...
Click to collapse
Well then there is nothing i can tell that can help you mate, good luck
Hello,
When the phone is in recovery mode, the file explorer won't show up with your nexus files... The fact that a sound is coming proves that the phone is being detected...
If you have setup a working adb environment you can follow what @gee2012 has said and sideload the kernel and flash it... If you haven't then download the android sdk and make sure you have downloaded the usb_driver package as well...
BleachFan21 said:
no
Click to expand...
Click to collapse
First, don't yet think your phone it's bricked. The actual solution is to get the proper driver on the computer. Remember that nexus 5 does not have Sdcard and there's not way to mount to the computer via recovery. Only ADB PUSH and ADB SIDELOAD will put a Rom into your phone.
You have to check on device manager to see the status of the driver. if t shows as Nexus 5, you will have to update the driver to and adb compatible one. If it says ADB........ then, you are good to go
EDIT: @vin4yak, one day I'll go to ninja school too
1.) If your device is actually bricked then a USB cable will do you absolutely no good. Fixing a "bricked" device is something that will need to be JTAG'd for it to work again. I think you might be mistaken about what a bricked device is. Its pretty hard to brick a nexus device so I highly doubt you're device is bricked.
2.) You have to get into fastboot mode. Just search for how to do so. Then you can flash the stock img's through fastboot and you'll be back in business. I have no clue about what drivers you'll need for your setup as I haven't run windows in 9 years or so. Just get the drivers, fastboot, and get your nexus back.
Why don't you just flash a boot.img from the stock rom? Or going back to stock?
You cannot mount sdcard to the pc in recovery. You have to use adb push or adb sideload.
To make adb work in recovery you need naked usb drivers 0.73.
Then you can adb sideload a rom, or push a rom to /sdcard.
Anyway download my attachment, put your phone to fastboot mode and double click on flash.bat then report me back
Check out this thread. If you can boot into recovery, then you should be able to boot into fastboot and restore your N5 back to stock.
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5 using Tapatalk

[Q] Nexus 5 wiped need help

Hello
I've installed TWRP on my nexus 5, then I fully wiped my phone with TWRP, is there way to install any rom now? How could I transfer rom to nexus storage?
Thanks
halo3333 said:
Hello
I've installed TWRP on my nexus 5, then I fully wiped my phone with TWRP, is there way to install any rom now? How could I transfer rom to nexus storage?
Thanks
Click to expand...
Click to collapse
If you flashed the latest TWRP 2.8.1.0, you can boot into recovery and enable MTP mode. Then drag the files across exactly like when you plug in and use MTP in android.
rootSU said:
If you flashed the latest TWRP 2.8.1.0, you can boot into recovery and enable MTP mode. Then drag the files across exactly like when you plug in and use MTP in android.
Click to expand...
Click to collapse
Thanks for quick answer.
I've flashed TWRP v2.7.1.1 :crying:
halo3333 said:
Thanks for quick answer.
I've flashed TWRP v2.7.1.1 :crying:
Click to expand...
Click to collapse
So flash 2.8.1.0 then.
_MetalHead_ said:
So flash 2.8.1.0 then.
Click to expand...
Click to collapse
Yeah...
I installed twrp using [ROOT] Rashr - Flash Tool from Google Play. Now i have no OS installed and fully wiped nexus 5, how could i do that? Sorry im newbie. Panic
halo3333 said:
I installed twrp using [ROOT] Rashr - Flash Tool from Google Play. Now i have no OS installed and fully wiped nexus 5, how could i do that? Sorry im newbie. Panic
Click to expand...
Click to collapse
fastboot flash recovery [recovery name].img
On a side note, this is exactly why toolkits are discouraged. Had you taken the time to learn how to do it manually, you would have known how to get yourself out of this (very minor) predicament.
_MetalHead_ said:
fastboot flash recovery [recovery name].img
On a side note, this is exactly why toolkits are discouraged. Had you taken the time to learn how to do it manually, you would have known how to get yourself out of this (very minor) predicament.
Click to expand...
Click to collapse
Again, yeah..
There is a fastboot thread in the "guides and info" link in my signature
halo3333 said:
Hello
I've installed TWRP on my nexus 5, then I fully wiped my phone with TWRP, is there way to install any rom now? How could I transfer rom to nexus storage?
Thanks
Click to expand...
Click to collapse
Well? Did you get your problem worked out?
Almost there
Flashed TWRP v2.8.1.0, enabled MTP, but there is no device: i.img ur.com/cG261Qi.png
How it looks like in Device Manager: i.img ur.com/nGMCLV8.png (can not post links having less than 10 posts)
Phone is currently in TWRP.
Also tried to flash zip using command prompt:
C:\androidsdk\sdk\tools>adb sideload zipname.zip
error: closed
error: closed
halo3333 said:
Flashed TWRP v2.8.1.0, enabled MTP, but there is no device: i.img ur.com/cG261Qi.png
How it looks like in Device Manager: i.img ur.com/nGMCLV8.png (can not post links having less than 10 posts)
Phone is currently in TWRP.
Also tried to flash zip using command prompt:
C:\androidsdk\sdk\tools>adb sideload zipname.zip
error: closed
error: closed
Click to expand...
Click to collapse
Need to sort drivers out. Read the "adb and fastboot" thread which you can get to via "guide and info threads" link in my signature
rootSU said:
Need to sort drivers out. Read the "adb and fastboot" thread which you can get to via "guide and info threads" link in my signature
Click to expand...
Click to collapse
Transfered slimcat rom using adb push name.zip /sdcard/ - Phone was recognized by adb and fastboot
Tried to flash rom using TWRP v2.8.1.0, failed; couldn't mount /data
After then tried that http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
6. Use ADB to launch a root shell from within Philz recovery
a. Ensure that the drivers are now detecting your device as an ADB ready device by entering: ‘adb devices’. If it returns “<serialnumberofdevice> recovery” then you are ready to proceed. If it does not, please verify your ADB driver installation and check again.
b. Enter: ‘adb shell’ to gain full root shell access to the Android file system. (You should see a “~#” prompt to show that you’re now in a root shell)
Click to expand...
Click to collapse
Now phone isn't recognized by adb and fastboot in Philz Touch 6, ClockworkMod v6.0.5.1
http://i.img ur.com/SwRv1wE.png
halo3333 said:
Transfered slimcat rom using adb push name.zip /sdcard/ - Phone was recognized by adb and fastboot
Tried to flash rom using TWRP v2.8.1.0, failed; couldn't mount /data
After then tried that http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Now phone isn't recognized by adb and fastboot in Philz Touch 6, ClockworkMod v6.0.5.1
http://i.img ur.com/SwRv1wE.png
Click to expand...
Click to collapse
Cant help ya. Not sure why you did that.
You'll need to get it in fastboot somehow and flash stock.. Maybe you should post in the thread you followed.
halo3333 said:
Transfered slimcat rom using adb push name.zip /sdcard/ - Phone was recognized by adb and fastboot
Tried to flash rom using TWRP v2.8.1.0, failed; couldn't mount /data
After then tried that http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Now phone isn't recognized by adb and fastboot in Philz Touch 6, ClockworkMod v6.0.5.1
http://i.img ur.com/SwRv1wE.png
Click to expand...
Click to collapse
Exactly what ROM did you try to flash? Post the link.
And what recovery do you have now? Did you flash Philz or ClockworkMod?
Downloaded and extracted stock rom: hammerhead-krt16m-factory-bd9c39de.tar, then extracted hammerhead-krt16m-factory-bd9c39de.tgz, copied files to adb and fastboot files, launched flash-all.bat and it worked
facepalm
Thanks for help

[Q] ADB sideload Error:Closed

Despite hours of searching, I cannot find someone with my exact problem and a solution.
I have a nexus 5
It started bootlooping for no reason
I tried to flash the stock image, everything flashed but it still won't boot.
I tried to download kitkat but I'm using easy tether and I can't use HTTPS and nobody has mirrors.
I've done both the long way by flashing each individual file at a time
I've tried flash all and both fail, I do not get any errors I was not told to ignore during those processes.
Now, I'm fed up and want a new phone anyway. So I want to set the tamper flag to false so I an take it back.
I start following a guide, tells me to download the bootunlocker script and flash it with TWRP.
I flash TWRP with no problems and open it up
Open adb sideload
Open cmd
Type ADB devices
Serial pops up with the active state
I type adb usb
Restarts in usb mode
Type Adb push filename <location> <remote>
Daemon started successfully on port 5037
Error: Closed
I am on windows 7 using adb version 1.0.32.
Can someone please help me?
Why are you using ADB thru TWRP?
If you can flash things your device is already unlocked.
Boot your N5 to bootloader mode and flash stock images from there.
I haven't read one guide that says to use TWRP and use ADB that way.
Flash stock images thru bootloader and use the guides provided here on XDA.
You might of messed up your devices by flashing that bootunlocker. I've never heard of that or heard of flashing something thru recovery to unlock your phone.
jayRokk said:
Why are you using ADB thru TWRP?
If you can flash things your device is already unlocked.
Boot your N5 to bootloader mode and flash stock images from there.
I haven't read one guide that says to use TWRP and use ADB that way.
Flash stock images thru bootloader and use the guides provided here on XDA.
You might of messed up your devices by flashing that bootunlocker. I've never heard of that or heard of flashing something thru recovery to unlock your phone.
Click to expand...
Click to collapse
I think you misunderstood. I haven't been able to flash bootunlocker yet because of the error with sideload.
I've already tried many times flashing the stock images in fastboot mode. My phone is unlocked but I just want to reset my tamper flag now, I'm not trying to fix it anymore.
RaggleFraggles said:
I think you misunderstood. I haven't been able to flash bootunlocker yet because of the error with sideload.
I've already tried many times flashing the stock images in fastboot mode. My phone is unlocked but I just want to reset my tamper flag now, I'm not trying to fix it anymore.
Click to expand...
Click to collapse
Why are you trying to flash bootunlocker?
jayRokk said:
Why are you trying to flash bootunlocker?
Click to expand...
Click to collapse
In the how to flash factory images guide, it tells me that's how you set you tamper flag to false
RaggleFraggles said:
In the how to flash factory images guide, it tells me that's how you set you tamper flag to false
Click to expand...
Click to collapse
I know that but are you planning to return the device? I should have been more clear.
Also when flashing stock images, are you wiping everything before/after flashing?
Also take note boot up time can be up to 10 minutes.
jayRokk said:
I know that but are you planning to return the device? I should have been more clear.
Also when flashing stock images, are you wiping everything before/after flashing?
Also take note boot up time can be up to 10 minutes.
Click to expand...
Click to collapse
Yes I want to return it and jump. And yes i wipe before and after flashing
Bump
You can simply reset the flag with the root app "bootunlocker"
rootSU said:
You can simply reset the flag with the root app "bootunlocker"
Click to expand...
Click to collapse
I can't boot. to android
Bump
Why are you using adb usb? Just boot the recovery then:
adb device
If it shows just choose sideload then:
adb sideload "bootunlocker".zip
I've never used an adb usb command on any device whether pushing or sideloading.
theesotericone said:
Why are you using adb usb? Just boot the recovery then:
adb device
If it shows just choose sideload then:
adb sideload "bootunlocker".zip
I've never used an adb usb command on any device whether pushing or sideloading.
Click to expand...
Click to collapse
That's because it doesn't exist, AFAIK.
I'm still very confused.
RaggleFraggles said:
I'm still very confused.
Click to expand...
Click to collapse
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just did and still getting error closed message. Do you have teamveiwer?
jd1639 said:
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Now my phone is saying "unable to find partition for path sdcard.
And unable to mount persist
RaggleFraggles said:
Just did and still getting error closed message. Do you have teamveiwer?
Click to expand...
Click to collapse
You don't need team viewer you need to read more. When you type adb devices what do you get?
theesotericone said:
You don't need team viewer you need to read more. When you type adb devices what do you get?
Click to expand...
Click to collapse
It shows me my serial number and the status of the device.

Categories

Resources