ADB issue - Nexus 5 Q&A, Help & Troubleshooting

Does adb push work in recovery or fastboot mode. I've seen a lot of forms use this method but it did not work for me. In recovery mode the device is not been recognized when i type in adb devices, it throws no devices found. but all the adb commands works fine during normal run.

blackuse said:
Does adb push work in recovery or fastboot mode. I've seen a lot of forms use this method but it did not work for me. In recovery mode the device is not been recognized when i type in adb devices, it throws no devices found. but all the adb commands works fine during normal run.
Click to expand...
Click to collapse
You need to enable ADB mode in recovery for it to work.
fastboot is for bootloader mode only.

Adb push works in recovery, not fastboot. You need to get the drivers installed while your in recovery. Ate you on Windows pc? Open device manager and you'll see a device with an exclamation make on it. You need to installs the drivers for that. Go to browse for drivers and there will be an option to install from a list on the computer. Find the android adb drivers
Sent from my Nexus 5 using XDA Free mobile app

Just a note:
adb doesn't work in stock recovery other then when using adb sideload.
Custom recoveries support all adb commands.

El Daddy said:
Just a note:
adb doesn't work in stock recovery other then when using adb sideload.
Custom recoveries support all adb commands.
Click to expand...
Click to collapse
Good point
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Adb push works in recovery, not fastboot. You need to get the drivers installed while your in recovery. Ate you on Windows pc? Open device manager and you'll see a device with an exclamation make on it. You need to installs the drivers for that. Go to browse for drivers and there will be an option to install from a list on the computer. Find the android adb drivers
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i did as per ur instruction and now it shows the device in adb devices but i'm not able to perform any commands. i use CWM.

blackuse said:
i did as per ur instruction and now it shows the device in adb devices but i'm not able to perform any commands. i use CWM.
Click to expand...
Click to collapse
Please elaborate on "i'm not able to perform any commands"

rootSU said:
Please elaborate on "i'm not able to perform any commands"
Click to expand...
Click to collapse
only "adb devices" works when i use adb push it does not throw any error but the file is not found in the device.Is there any restriction to the commands used in the recovery mode.

blackuse said:
only "adb devices" works when i use adb push it does not throw any error but the file is not found in the device.Is there any restriction to the commands used in the recovery mode.
Click to expand...
Click to collapse
Put the file you're trying to push in the same folder as abd.exe. Open a command window in that folder. It's sounds like you have a path issue and adb is not finding the file
Sent from my Nexus 5 using XDA Free mobile app

blackuse said:
only "adb devices" works when i use adb push it does not throw any error but the file is not found in the device.Is there any restriction to the commands used in the recovery mode.
Click to expand...
Click to collapse
Could you screenshot the cmd prompt please?

the adb push works fine in normal run. but none of the command seems to work during recovery.adb commands works fine even in fastboot mode

blackuse said:
the adb push works fine in normal run. but none of the command seems to work during recovery.adb commands works fine even in fastboot mode
Click to expand...
Click to collapse
What recovery are you using? If you're using cwm, it mounts /sdcard incorrectly as /data/media instead of /data/media/0
Mount data and ls /data/media
Sent from my Nexus 5 using Tapatalk

rootSU said:
What recovery are you using? If you're using cwm, it mounts /sdcard incorrectly as /data/media instead of /data/media/0
Mount data and ls /data/media
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
YES i'm using CWM . "Mount data and ls /data/media" how do I do that

blackuse said:
YES i'm using CWM . "Mount data and ls /data/media" how do I do that
Click to expand...
Click to collapse
in recovery, go to "mounts and storage" and press "mount data".
Then in command prompt type
Code:
adb shell
to get into adb shell
Then type
Code:
ls /data/media
Thats LS in lower case and yes, it is case sensitive.
This will list the contents of /data/media - which is the location cwm uses as /sdcard. This hasn't been /sdcard since android 4.1.2 though.... I bet ls lists all those missing files you've been pushing.
This is one reason you should use either Philz or TWRP. Antiquated settings in CWM

blackuse said:
YES i'm using CWM . "Mount data and ls /data/media" how do I do that
Click to expand...
Click to collapse
Instead of push /sdcard use push /data/media
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Instead of push /sdcard use push /data/media
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thats the same.. push /data/media/0
Although just change recovery from cwm and continue to use /sdcard
Otherwise Nandroid backups will go missing too
Sent from my Nexus 5 using Tapatalk

rootSU said:
Thats the same.. push /data/media/0
Although just change recovery from cwm and continue to use /sdcard
Otherwise Nandroid backups will go missing too
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i tried out lots of adb push commands and finally understood "/sdcard/" which is supposed to be "/data/media/0/" is still "/data/media/ in CWM and yes all my CWM nanodroid backups are located in "data/media/CWM". how do i permanently make CWM to use "/data/media/0/" for sdcard
and i assume adb reboot does not work in recovery mode

blackuse said:
i tried out lots of adb push commands and finally understood "/sdcard/" which is supposed to be "/data/media/0/" is still "/data/media/ in CWM and yes all my CWM nanodroid backups are located in "data/media/CWM". how do i permanently make CWM to use "/data/media/0/" for sdcard
and i assume adb reboot does not work in recovery mode
Click to expand...
Click to collapse
You can't with cwm. Use philz or twrp though twrp won't be compatible with your existing backups.
Sent from my Nexus 5 using Tapatalk

Related

ADB won't recognize phone/bootloader/Can't replace recovery HELP!

So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
AIndoria said:
So basically I found out just today we have Cyanogenmod 10.2 >.<
I downloaded the Joilaroi version, flashed it in TWRP 2.6xx and then suddenly "E: Error in updating binary script" did a bit of googling and found out that it's a common problem with TWRP > 2.3.3.0
So I was about to downgrade it to 2.3.3.0 or temp boot into CWM. Connected my phone to my laptop and went to bootloader, then did Adb devices....the list was empty.
Reinstalled HTC drivers, used different USB port...nothing.
TL;DR : Phone doesn't get recognized in Bootloader mode, Can't flash ROM, Can't replace recovery. Help!
Click to expand...
Click to collapse
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Taha Haq said:
Why don't you flash with terminal emulator?
Just put recovery.img in the root of your sdcard
Open terminal type
su
cd sdcard
flash_image recovery recovery.img
That's it
Sent from my gt-1900 using xda premium
Click to expand...
Click to collapse
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
install htc drivers and make dure you cleared the all registry and files from your previous installation and connect your device
open cmd and go to the folder where you placed adb and type command
adb kill-server =>it will close all adb processes running at that time
adb start-server => it will start new adb process
adb devices=> to reconize your device
if it shows your device then through fastboot command flash the recovery
but make sure you have all neccessary binary files in that folder for adb and fastboot
hit thanks if helped
AIndoria said:
That's what I'm doing now but I need a proper solution :/ Basically Windows won't recognize my phone through fastboot. I'd rather not keep installing CM9 again and again after a failed flash, you know?
Click to expand...
Click to collapse
You can try installing the newer Drivers.
Else your usb port may be broken. that is also a possiblity

[Q] Froze velvet.apk

So, I did something really stupid. While trying to freeze unnecessary aps, I froze the velvet.apk Which I think is part of the launcher in 4.4.2. After that the phone gets stuck at the boot-up screen (specifically at the four colored circles) and nothing ever happens.
So, I found that there's a command I can use to unfreeze apks: "pm enable velvet.apk"
But I need someone to teach me where and how to use it. The phone doesn't boot up and when I connected to fastboot and used "adb shell su" I got a "device not found error" I already had drivers installed to root phone!
Any quick answer is definitely appreciated!
nivakis said:
So, I did something really stupid. While trying to freeze unnecessary aps, I froze the velvet.apk Which I think is part of the launcher in 4.4.2. After that the phone gets stuck at the boot-up screen (specifically at the four colored circles) and nothing ever happens.
So, I found that there's a command I can use to unfreeze apks: "pm enable velvet.apk"
But I need someone to teach me where and how to use it. The phone doesn't boot up and when I connected to fastboot and used "adb shell su" I got a "device not found error" I already had drivers installed to root phone!
Any quick answer is definitely appreciated!
Click to expand...
Click to collapse
A could of things, you can't use adb commands in fastboot. You need to use fastboot commands. A little more brute force then you're looking for but,
fastboot flash system system.img will solve the problem. System.img is from the factory image
Sent from my Nexus 5
jd1639 said:
A could of things, you can't use adb commands in fastboot. You need to use fastboot commands. A little more brute force then you're looking for but,
fastboot flash system system.img will solve the problem. System.img is from the factory image
Sent from my Nexus 5
Click to expand...
Click to collapse
Well, it could work but remember that I didn't uninstall the app, I just froze it, so I guess flashing the partition wouldn't do much good because info on frozen apps are stored elsewhere, right?
EDIT:
Is there a way to push via fastboot another velvet.apk or launcher, just to boot the phone and fix the problem?
nivakis said:
Well, it could work but remember that I didn't uninstall the app, I just froze it, so I guess flashing the partition wouldn't do much good because info on frozen apps are stored elsewhere, right?
EDIT:
Is there a way to push via fastboot another velvet.apk or launcher, just to boot the phone and fix the problem?
Click to expand...
Click to collapse
I wasn't familiar with the pm command but it looks like if you boot into recovery and then do
adb shell
pm enable /system/priv-app/velvet.apk
it should work
Edit, I'm getting a pm not found error
The other option would be to adb push the apk
Sent from my SAMSUNG-SGH-I727
jd1639 said:
I wasn't familiar with the pm command but it looks like if you boot into recovery and then do
adb shell
pm enable /system/priv-app/velvet.apk
it should work
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
So the million dollar question is, since I don't have any recoveries installed, is there a recovery that includes a terminal to try this command?
nivakis said:
So the million dollar question is, since I don't have any recoveries installed, is there a recovery that includes a terminal to try this command?
Click to expand...
Click to collapse
Well, the two million dollar question is, is your bootloader unlocked?
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Well, the two million dollar question is, is your bootloader unlocked?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Well, in order to root using CF-auto-root, it was needed to unlock the bootloader, so, yes!
nivakis said:
Well, in order to root using CF-auto-root, it was needed to unlock the bootloader, so, yes!
Click to expand...
Click to collapse
Good. Download twrp recovery from http://d-h.st/nbu and put it in the same folder as fastboot.exe is in. Boot into the bootloader then type
fastboot flash recovery recovery-2.6.3.4.img in a cmd window opened in the same folder a fastboot.exe is on
Sent from my Nexus 5
jd1639 said:
Good. Download twrp recovery from http://d-h.st/nbu and put it in the same folder as fastboot.exe is in. Boot into the bootloader then type
fastboot flash recovery recovery-2.6.3.4.img in a cmd window opened in the same folder a fastboot.exe is on
Sent from my Nexus 5
Click to expand...
Click to collapse
I think you meant "fastboot"
good, now I am into Team Win Recovery Project. I push: Advanced > Terminal Command and it asks to select a starting folder. Which should I choose? If I don't choose the correct one, when I type adb shell, it says:
/ # adb shell
sh:
adb: not found
nivakis said:
I think you meant "fastboot"
good, now I am into Team Win Recovery Project. I push: Advanced > Terminal Command and it asks to select a starting folder. Which should I choose? If I don't choose the correct one, when I type adb shell, it says:
/ # adb shell
sh:
adb: not found
Click to expand...
Click to collapse
You don't need the terminal in twrp. You just needed a recovery that allows you to use adb commands from your computer. Leave your device in twrp and then open a command window on your pc. Run the commands from there
Sent from my Nexus 5
jd1639 said:
You don't need the terminal in twrp. You just needed a recovery that allows you to use adb commands from your computer. Leave your device in twrp and then open a command window on your pc. Run the commands from there
Sent from my Nexus 5
Click to expand...
Click to collapse
Drivers for "AOSP on Hammerhead"?
EDIT:
Scratch that. I found them and I am about to try the commands
EDIT 2:
Grrrr, I get a /sbin/sh: pm: not found
I tried downloading the Android SDK manager but can't get over this...
Well, I finally fixed it! Thank you jd1639, you've been VERY helpful.
To sum it up, after failing with the adb commands, I used the file browser at the recovery to copy the frozen velvet.apk to system/app. Then I booted my phone and while it was stuck at the booting animation, I called my phone and that gave me access to the taskbar. Then I unfroze the original velvet.apk in /system/priv-app and deleted the one in /system/app
I'll be sure to double-check what I freeze next time!
nivakis said:
Well, I finally fixed it! Thank you jd1639, you've been VERY helpful.
To sum it up, after failing with the adb commands, I used the file browser at the recovery to copy the frozen velvet.apk to system/app. Then I booted my phone and while it was stuck at the booting animation, I called my phone and that gave me access to the taskbar. Then I unfroze the original velvet.apk in /system/priv-app and deleted the one in /system/app
I'll be sure to double-check what I freeze next time!
Click to expand...
Click to collapse
Glad you got it fixed. Pretty clever way to do it
Sent from my Nexus 5
jd1639 said:
Glad you got it fixed. Pretty clever way to do it
Sent from my Nexus 5
Click to expand...
Click to collapse
Well I am told to be resourceful when needed! But I couldn't have done it without your help!

[Q] How to push rom via adb

i flashed gpe version on xt1033 with TWRP 2.7.1.0
after copying all the files back to sdcard i rebooted into TWRP
in TWRP i changed the file system to f2fs for system, data and cache.
unfortunately i lost everything on my internal memory.
i don't mind flashing the stock firmware again but if i do so than i will again try to convert the partitions to f2fs and i will again be in the same problem.
i tried to push rom via by following command
adb sideload rom.zip
it showed and error "error:closed"
again i tried with another command
adb push rom.zip /sdcard
it showed that the file has been pushed in command prompt with transfer bitrate but the phone didn't react anything
still i tried to reboot into recovery via long press power button
i succesfully rebooted into recovery but i was unable to find the rom zip
i tried it several times but had no luck.
Before sideloading you need to be in sideload mode i think
Also /sdcard might not be the correct path to the sdcard. I'm not sure what the correct path on this phone is.
adizz4 said:
Before sideloading you need to be in sideload mode i think
Also /sdcard might not be the correct path to the sdcard. I'm not sure what the correct path on this phone is.
Click to expand...
Click to collapse
I tried with adb side loading enabled.
I wrote that command prompt showed file transferred but nothing was visible on phone.
Sent from my Moto G using XDA Premium 4 mobile app
antarix said:
I tried with adb side loading enabled.
I wrote that command prompt showed file transferred but nothing was visible on phone.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Restart ur pc n reboot ur mobile to recovery n try again
abhi0502 said:
Restart ur pc n reboot ur mobile to recovery n try again
Click to expand...
Click to collapse
Tried it but no solution.
Sent from my Moto G using XDA Premium 4 mobile app
I don't know why it doesn't happen? I thought f2fs file system is much better than ext4 but I want to use ROM which is incompatible with dual Sim version.
sent from xt1033 with RenderBroken's kernel
Push rom.Zip to sdcard
adb push rom.zip /sdcard/
After pushing do a normal install. Dont use side load option
Sent from my Moto G using Tapatalk
antarix said:
I don't know why it doesn't happen? I thought f2fs file system is much better than ext4 but I want to use ROM which is incompatible with dual Sim version.
sent from xt1033 with RenderBroken's kernel
Click to expand...
Click to collapse
When u plug ur mobile to pc via usb is there pop up coming saying something about software installation??
abhi0502 said:
When u plug ur mobile to pc via usb is there pop up coming saying something about software installation??
Click to expand...
Click to collapse
Nope cause the software is already installed. I flashed stock at last but I am looking for a solution to this so that I can change file system to f2fs.
reversegear said:
Push rom.Zip to sdcard
adb push rom.zip /sdcard/
After pushing do a normal install. Dont use side load option
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
I tried this method but the file doesn't show up in internal memory. After the command prompt says the file has been transferred I cancel adb and it shows failed.
sent from xt1033 with RenderBroken's kernel
antarix said:
Nope cause the software is already installed. I flashed stock at last but I am looking for a solution to this so that I can change file system to f2fs.
I tried this method but the file doesn't show up in internal memory. After the command prompt says the file has been transferred I cancel adb and it shows failed.
sent from xt1033 with RenderBroken's kernel
Click to expand...
Click to collapse
I was asking because after that it says some .dll file missing
On my pc adb sideload is working but not on my laptop because of that .dll file
abhi0502 said:
I was asking because after that it says some .dll file missing
On my pc adb sideload is working but not on my laptop because of that .dll file
Click to expand...
Click to collapse
It didn't pop up anything.
It showed adb device in command prompt.
sent from xt1033 with RenderBroken's kernel
@ankitxperia I didn't understand your command adb push C:\ROM /sdcard
sent from xt1033 with RenderBroken's kernel
antarix said:
@ankitxperia I didn't understand your command adb push C:\ROM /sdcard
sent from xt1033 with RenderBroken's kernel
Click to expand...
Click to collapse
i wil be explaning with as much as detail as possible first boot into recovery then open cmd and navigate to adb tool and open a cmd window from there(as usual) i am using Minimal adb flashtool
Now type adb devices it should show some info like serial no etc if not then you cant proceed check your drivers etc if the problem presists then uninstall all drivers and try again if the problem still presists then install pda net this will definetly solve your problem here is the link http://www.dominantwire.com/2012/11/how-to-solve-adb-device-not-found-error.html#.U5L5C3KSxA0
NOW to PUSH files from Pc to internal storage use Push command
adb push C:\ROM /sdcard
what this command will do is that my Rom files i hav stored in C:\ROM and /sdcard will move the to files to your internal sd card
here is the good tutorial regarding using push pull command http://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965
HOPE this helps btw an you Tell me how did you convert Ext4 partion to F2fs also can you give me theWhich TWRp recovery have you installed also the download link too if possible
ankitxperia said:
HOPE this helps btw an you Tell me how did you convert Ext4 partion to F2fs also can you give me theWhich TWRp recovery have you installed also the download link too if possible
Click to expand...
Click to collapse
Use twrp 2.7.1.0
It had option to change file system in advanced wipe section.
sent from xt1033 with RenderBroken's kernel
Here is the link
https://www.google.co.in/url?sa=t&s...L7gyYo2PCFqMjZuYA&sig2=EQGoC6cGznYJyhLusrWjRg
sent from xt1033 with RenderBroken's kernel
antarix said:
Here is the link
https://www.google.co.in/url?sa=t&s...L7gyYo2PCFqMjZuYA&sig2=EQGoC6cGznYJyhLusrWjRg
sent from xt1033 with RenderBroken's kernel
Click to expand...
Click to collapse
ok just flashed the 2.7.1 TWRP also do ihave to convert /Data and all other directories to f2fs or Only /system to F2fs ???
udate i tried converting System to f2fs but it still shows pation as Ext4
ankitxperia said:
ok just flashed the 2.7.1 TWRP also do ihave to convert /Data and all other directories to f2fs or Only /system to F2fs ???
udate i tried converting System to f2fs but it still shows pation as Ext4
Click to expand...
Click to collapse
Once you have converted system than reboot to recovery it will show f2fs. I changed everything that's why had to push rom coz it formats that partition.
sent from xt1033 with RenderBroken's kernel
adb sideload shoud do the trick..google for the detailed steps and wait for the file to b flashed..n if it doesn't then check whether there is sideload.zip on ur sd card
ankitxperia said:
i wil be explaning with as much as detail as possible first boot into recovery then open cmd and navigate to adb tool and open a cmd window from there(as usual) i am using Minimal adb flashtool
Now type adb devices it should show some info like serial no etc if not then you cant proceed check your drivers etc if the problem presists then uninstall all drivers and try again if the problem still presists then install pda net this will definetly solve your problem here is the link http://www.dominantwire.com/2012/11/how-to-solve-adb-device-not-found-error.html#.U5L5C3KSxA0
NOW to PUSH files from Pc to internal storage use Push command
adb push C:\ROM /sdcard
what this command will do is that my Rom files i hav stored in C:\ROM and /sdcard will move the to files to your internal sd card
here is the good tutorial regarding using push pull command http://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965
HOPE this helps btw an you Tell me how did you convert Ext4 partion to F2fs also can you give me theWhich TWRp recovery have you installed also the download link too if possible
Click to expand...
Click to collapse
You, sir, saved my life! Thank you! I did the pda.net and worked...
My problem was that I did factory reset, and forgot i had no rom in sd card, neither a backup. x.x
Tried to push rom via adb push command, but 'device not found' message appeared.
Then tried to adb sideload the rom, but the same error appeared...
So i uninstalled all motorola drivers, and installed pda.net. Tried to push again the rom, but didnt worked. Sideloaded again, and did worked! I was using minimal adb tool...

[Q] Accidentally wiped the system and now my Nexus 5 says No OS installed!

I wiped the system thinking it was part of the system factory reset in TWRP but i didnt know that it would result in it saying NO OS INSTALLED. i read other similar threads about this problem but dont exactly understand what to do and how to restore my phone. i have a nandroid backup but its on my pc and not the internal storage on the phone. im fairly new to this so those replying, please explain exactly what to do. Im so scared about what to do now :crying::crying::crying:
Don't be scared its common and very, very easy to fix
Now I don't use TWRP so I have no idea of the directory structure so I can't advise you exactly.
But what you will essentially do is use adb push to get the files on your phone.
Click the link in my signature to go to the sticky roll up thread. All the important threads are linked there. Y
In that thread you'll quickly find my adb info thread. This should be most of what you need to know
Sent from my Nexus 5 using Tapatalk
First relax, your phone is not ruined. I assume you have a custom recovery. You're going to have to either side load a rom zip using adb or adb push a rom zip onto your phone and flash it in recovery.
Edit, OP you'll want to push the rom to /sdcard/Download. That'll put it into the folder twrp defaults to look for it.
Sent from my Nexus 5 using XDA Free mobile app
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
http://www.koushikdutta.com/post/universal-adb-driver
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
https://developers.google.com/android/nexus/images
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
raptir said:
]
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
All these guys have it spot on! I just wanted to mention that when you install a ROM system gets wiped automatically as this is a parameter in the zip's updater-script.
So in other words there is really no reason to wipe system manually. Just let the install process do it for you. If u wipe system manually and then you realize you do not have a ROM zip or a nandroid only ADB can save you. So this way you can save yourself a headache
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
\
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
thauri said:
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
Click to expand...
Click to collapse
Did you or did you not read my adb and fastboot thread?
And WHY are you going for the last resort first???
You really need to chill out and read things because I don't think you're thinking straight
Sent from my Nexus 5 using Tapatalk
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
rootSU said:
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i did download the 15 second ADB installer but my computer isnt detecting the phone connected when i ran the flash-all . bat file.
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
rootSU said:
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok yes im reading your thread and doing the ADB commands. i have a question though, the multi-line input for the code to ADB push goes in cmd right? how is that possible?
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
thauri said:
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
Click to expand...
Click to collapse
If "mount data" shows device or resource busy, then that usually means it is already mounted.
rootSU said:
If "mount data" shows device or resource busy, then that usually means it is already mounted.
Click to expand...
Click to collapse
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Messing up is scary but it's a great opportunity to learn. I think you'll get through this just fine.
thauri said:
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Click to expand...
Click to collapse
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
rootSU said:
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did, I put it in the backup folder in TWRP where all the other backups usually were
thauri said:
I did, I put it in the backup folder in TWRP where all the other backups usually were
Click to expand...
Click to collapse
Take a new backup, then delete everything in the new backup folder and move everything from your old backop into the new backup folder,
So for example
Code:
adb shell
mount /data
cd /data/media/0/TWRP/backups
ls
^^ This should list the contents... You should see your old backup and your new backup (which will be mostly empty).
Lets pretend your new backup folder is 22222222 and your old backup folder is 11111111
Code:
rm -Rf 222222222/*
mv 111111111/* 222222222
The first command is a remove (recursive) of the contents of the new backup. second command mvs contents of old backup into new backup folder,
Try that.
I don't know TWRP so my assumptions of the path may be incorrect
Someone else posted twrp default path as /sdcard/downloads - try that.

adb sideload update.zip and "error: insufficient permissions for device"

Hi guys,
Just an existential doubt... I'm trying to sideload a zip file from recovery. The thing is, I'm using twrp custom recovery. The sideload command can only be used with stock recovery? I read some thing about this command, but not convinced yet.
My device is recognized in the custom recovery, but when choose the adb sideload option in twrp my device isn't recognized anymore and i get the insufficient permissions for device error .
I'm using ubuntu 12.04...
Thanks in advance!
What does adb devices throw out?
nunojsa said:
Hi guys,
Just an existential doubt... I'm trying to sideload a zip file from recovery. The thing is, I'm using twrp custom recovery. The sideload command can only be used with stock recovery? I read some thing about this command, but not convinced yet.
My device is recognized in the custom recovery, but when choose the adb sideload option in twrp my device isn't recognized anymore and i get the insufficient permissions for device error .
I'm using ubuntu 12.04...
Thanks in advance!
Click to expand...
Click to collapse
Try to sideload as root with sudo su command or add privilages to your user. This guide worked for me http://forum.xda-developers.com/showthread.php?t=921169
Sent from my Nexus 5 using XDA Free mobile app
bitdomo said:
Try to sideload as root with sudo su command or add privilages to your user. This guide worked for me http://forum.xda-developers.com/showthread.php?t=921169
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, I was able to run it with the guide that you provide. Just needed to create the android file on udev. And then just found out that i was running an older adb version lol.

Categories

Resources