[solved] ADB pull help? - EVO Shift 4G Q&A, Help & Troubleshooting

So I installed the newest radios from the dev forum using the PG06IMG.zip.
Well now my phone wont boot because I need to restore, but I can't get into recovery because the bootloader always asks if I want to install PG06IMG.zip
What is the ADB Pull command to remove the file?
Also, when can I use ADB pull? When my phone is stuck at the bootscreen or the bootloader?
I do the following
cd C:\AndroidSDK\platform-tools
then >adb
then I do
adb pull /sdcard/PG06IMG.zip
keeps saying remote object "file" does not exist
what's the correct process of removing this file?

nevermind, I figured it out by just booting directory to recovery from command prompt
adb shell boot recovery

Related

[Q] Installing Cyanogenmod, Fastboot wont work.

So, trying to root and install cyanogenmod on my friends Evo **** 4g 2.3.3.
Following instructions per the cyanogenmod install wiki and a few other places.
I am using linux for everything and have adb setup correctly. I downloaded the fastboot from htc's dev website. [Everyone links you to the website but forgets to mention that you have to create an account and click on 'unlock bootloader' and scroll through a few pages]
Anywho, I did that and extracted the file to my android sdk directory. {for me it's [androidsdk/platform-tools]}
Now, when I try to run the fastboot command after running the adb reboot command to get into the bootloader, it returns with an error. "Fastboot command not found"
Now, I double checked and I marked the permissions for the fastboot file to be allowed to execute as a program.
What else am I doing wrong? If someone that has done this before, could help me out, that would be fantastic!
Again, I am running on ubuntu 11.04 linux with adb set up properly. Thanks.
cehck to see if you are in the same directory as fastboot. If you are in the platform-tools/ directory, do cd ../tools
fastboot *command here
Indirect said:
cehck to see if you are in the same directory as fastboot. If you are in the platform-tools/ directory, do cd ../tools
fastboot *command here
Click to expand...
Click to collapse
I was indeed in the same directory as fastboot, but fastboot would not recognize as a command. Even when I tried it with my atrix.
Try chmod 777 fastboot
Sent from my PC36100 using XDA Premium App
Trying this now. Will let you know in a sec.
Edit:
Still getting fastboot: Command not found

Wiped and can't start now (Help)

I used a Super Wipe Full and my new ROM was in the internal storage (Not on SD) So I lost everything plus the new ROM that I should use to install now.
So I have nothing to install on it now. It doesn't start up, the only thing I can do is go at ClockworkMod (Vol+Down) and travel there but doing nothing very useful.
How can I copy and past my ROM to the SD?
From windows.
Thank you, sorry I am dumb, =/
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
+1 Been there done that.
D
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
Thanks, gonna try later and edit here.
Edit. 1
So for Nakeddrivers should I download this one?
http://forum.xda-developers.com/showthread.php?t=1514942
And do what this guy says?
http://forum.xda-developers.com/showthread.php?t=2139767
Thank you.
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
I got a problem, when I type "adb push "ROM".zip /sdcard/"
It says: (by the first try)
"adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:"
(Second and other)
"adb server is out of date. killing...
* daemon started successfully *
protocol failure"
I downloaded this SDK:
http://developer.android.com/sdk/index.html
And this NakedDrivers:
http://forum.xda-developers.com/showthread.php?t=1514942
Help please =/
Did you get the ADB drivers installed?
I often get the same errors on ADB but it should eventually work.
What happens if you type:
adb devices
It should find your tablet.
frederuco said:
Did you get the ADB drivers installed?
I often get the same errors on ADB but it should eventually work.
What happens if you type:
adb devices
It should find your tablet.
Click to expand...
Click to collapse
After 3 errors with "adb devices" I got this:
"adb server is out of date. killing...
* daemon started successfully *
list of devices attached
37c624242616657 recovery"
What now?
type this:
adb shell
ls -l
see what the ouput is. Is there a sdcard directory listed?
If so, type exit so you are out of the ADB shell, then type:
adb push ROM.zip /sdcard/
frederuco said:
type this:
adb shell
ls -l
see what the ouput is. Is there a sdcard directory listed?
If so, type exit so you are out of the ADB shell, then type:
adb push ROM.zip /sdcard/
Click to expand...
Click to collapse
With "adb shell" I got few errors listed above and then this:
"adb server is out...
* daeomon started successfully *
~ #"
Thats all.
What happens if you type "ls -l" at the # prompt?
frederuco said:
What happens if you type "ls -l" at the # prompt?
Click to expand...
Click to collapse
Got a lot of suff:
http://img267.imageshack.us/img267/2112/31377010.jpg
If this helps, my deviece is a Asus Transformer TF101
I am trying to install the android revolution HD 3.6 rom
Filipebergami said:
Got a lot of suff:
http://img267.imageshack.us/img267/2112/31377010.jpg
If this helps, my deviece is a Asus Transformer TF101
I am trying to install the android revolution HD 3.6 rom
Click to expand...
Click to collapse
Perfect.
Now, download the android revolution HD 3.6 ROM if you have not done so. rename it to ROM.zip and put it in the c:\dev\adt\sdk\platform-tools directory.
Next, at the c:\dev\adt\sdk\platform-tools> prompt type:
adb push ROM.zip /sdcard/
It should then push the file ROM.zip to your internal SD card directory. It will say how many bytes were pushed succesfully when it finishes. If you get an error that it failed to start the daemon, just keep issuing the adb push ROM.zip /sdcard/ command until it works.
frederuco said:
Perfect.
Now, download the android revolution HD 3.6 ROM if you have not done so. rename it to ROM.zip and put it in the c:\dev\adt\sdk\platform-tools directory.
Next, at the c:\dev\adt\sdk\platform-tools> prompt type:
adb push ROM.zip /sdcard/
It should then push the file ROM.zip to your internal SD card directory. It will say how many bytes were pushed succesfully when it finishes. If you get an error that it failed to start the daemon, just keep issuing the adb push ROM.zip /sdcard/ command until it works.
Click to expand...
Click to collapse
YES !!!
After about 30 tries it worked, I got a bit scared when after * daemon thingy * got no answer for few minutes, but I manage to install it throught CW.
Thank you a lot.

Help tf101g

hello peopleI need your help without any information someone deleted all my files tf101g
TF101G entering recovery mode with cwm
cwm 5.5.0.4 but this does not allow me to upgrade from external sd card. I tried to flash from w7 with some programs, wheelie, nvflash, tubuntu, oneclickrecovery among others.
adb shell
exec ' system bin sh' failed no such file or directory 2
pushing something. permission denied
NVFLASH
rcm version 0x4 command send failed (usb write failed)
can someone help me
Since you have a TF101G, NVFlash is not an option.
Does your device show up as an ADB device in windows when you boot to recovery?
Another thought- if you hold VOL DOWN and POWER for 12-15 seconds and release when you see the white text (and don't hit vol up to enter RCK), does it boot up?
If so, you just have a recovery bootloop and can boot using this method until we fix it.
If not, back to my first thought - if it shows in the device manager, update the drivers using the naked drivers 0.72.
Then try typing "adb devices" at a command prompt and see if it is recognized via USB.
If so, push your firmware using the following:
adb push firmware.zip /sdcard/
If that succeeds, you should be able to flash the firmware from recovery.
frederuco said:
Since you have a TF101G, NVFlash is not an option.
Does your device show up as an ADB device in windows when you boot to recovery?
Another thought- if you hold VOL DOWN and POWER for 12-15 seconds and release when you see the white text (and don't hit vol up to enter RCK), does it boot up?
If so, you just have a recovery bootloop and can boot using this method until we fix it.
If not, back to my first thought - if it shows in the device manager, update the drivers using the naked drivers 0.72.
Then try typing "adb devices" at a command prompt and see if it is recognized via USB.
If so, push your firmware using the following:
adb push firmware.zip /sdcard/
If that succeeds, you should be able to flash the firmware from recovery.
Click to expand...
Click to collapse
when i try
adb push firmware.zip /sdcard/
adb push firmware.zip /sdcard/ permission denied
Try fixing permissions in CWM. I think it is under advanced.

Messed up rooting Pixel 2 XL and need some help (didn't adb pull my patched boot img)

So, I was following a rooting guide.
Things were going fine, until I needed to pull the patched_boot.img with the adb command:
adb pull /sdcard/MagiskManager/patched_boot.img
What I accidentally typed is:
adb /sdcard/MagiskManager/patched_boot.img
I continued following the guide, but when I got to the step where I need to enter the adb command:
fastboot flashboot file/path/patched_boot.img
I realized the file was never copied to my computer.
I tried to go back and install Magisk_Manager and repatch my boot image, but it failed since it now has a different boot image.
How can I fix this and properly root my Pixel 2 XL?
Thanks.
Highfiverobot said:
So, I was following a rooting guide.
Things were going fine, until I needed to pull the patched_boot.img with the adb command:
adb pull /sdcard/MagiskManager/patched_boot.img
What I accidentally typed is:
adb /sdcard/MagiskManager/patched_boot.img
I continued following the guide, but when I got to the step where I need to enter the adb command:
fastboot flashboot file/path/patched_boot.img
I realized the file was never copied to my computer.
I tried to go back and install Magisk_Manager and repatch my boot image, but it failed since it now has a different boot image.
How can I fix this and properly root my Pixel 2 XL?
Thanks.
Click to expand...
Click to collapse
I'm not sure I'm understanding this completely. If you typed the command you said you typed (without pull in it), the file wouldn't be copied to your PC. Then you typed fastboot flash boot /path to boot.img, you'd get an error message saying something to the effect file not found. Perhaps that's how you realized you didn't type the correct command to copy it to your PC? In any case, if this is what happened, you wouldn't have a different boot image because nothing has changed. The original patched boot image should still be on the phone. Have you tried pulling it to your PC and flashing it again? That's all you should have to do unless you deleted the original patched image.
robocuff said:
I'm not sure I'm understanding this completely. If you typed the command you said you typed (without pull in it), the file wouldn't be copied to your PC. Then you typed fastboot flash boot /path to boot.img, you'd get an error message saying something to the effect file not found. Perhaps that's how you realized you didn't type the correct command to copy it to your PC? In any case, if this is what happened, you wouldn't have a different boot image because nothing has changed. The original patched boot image should still be on the phone. Have you tried pulling it to your PC and flashing it again? That's all you should have to do unless you deleted the original patched image.
Click to expand...
Click to collapse
Got it all figured out now, but will post what I did for anyone else who happens to see this thread:
>you'd get an error message saying something to the effect file not found. Perhaps that's how you realized you didn't type the correct command to copy it to your PC?
Correct and correct.
What I meant to say is that when I went to flash patched_boot.img, it didn't exist, and I was worried I wouldn't be able continue at all without it.
For whatever reason Magisk was unable to repatch my original boot.img, so what I did was to:
- reflash the original boot.img
- then go back into Magisk
- patch my boot.img again
- ACTUALLY adb pull the patch_boot.img this time
- boot into bootloader
- then finally flash patched_boot.img
After this, I was good to go.
Obviously, you probably know this, just leaving a paper trail for anyone that happens upon this thread.

I need help with ADB/Fastboot commands from a powers shell window

i am very new so please speak to me like i have 50 IQ points (im actually not far off). i can get the powershell to open on my pc then when i try
PS C:\platform-tools> adb devices
List of devices attached
R9WN113HXVJ device
it works, but when i try any commands that start with fastboot, the window just hangs. Do i need to be in the bootloader for fastboot? does TWRP need to be installed first?
#2. I am trying to get an image off of my tablet and the tutorial says i need to enter....
" adb pull /sdcard/Download/magisk_patched.img " I am assuming its supposed to mean....
"adb pull /sdcard/Download/NAME OF FILE ON TABLET.tar"... which is "magisk_patched_ZRwve.tar"
if i am trying to "pull" from the tablet, where does it put this file on my PC?
scampo77 said:
i am very new so please speak to me like i have 50 IQ points (im actually not far off). i can get the powershell to open on my pc then when i try
PS C:\platform-tools> adb devices
List of devices attached
R9WN113HXVJ device
it works, but when i try any commands that start with fastboot, the window just hangs. Do i need to be in the bootloader for fastboot? does TWRP need to be installed first?
#2. I am trying to get an image off of my tablet and the tutorial says i need to enter....
" adb pull /sdcard/Download/magisk_patched.img " I am assuming its supposed to mean....
"adb pull /sdcard/Download/NAME OF FILE ON TABLET.tar"... which is "magisk_patched_ZRwve.tar"
if i am trying to "pull" from the tablet, where does it put this file on my PC?
Click to expand...
Click to collapse
No worries friend, everyone starts somewhere and IQ is not a real scientific measurement. Now let's clear some things:
You're not in fastboot mode if you didn't recognize it immediately. To enter fastboot from adb, use:
Code:
adb reboot fastboot
and no you don't need twrp to access fastboot mode.
The correct way to use pull looks like this:
Code:
adb pull <path of file to pull> <path of destination on pc>
for example:
Code:
adb pull /sdcard/Download/YOURFILENAME C:\platform-tools\
Also from context of your question, i assume you want to root your phone. Something helpful to remember, you don't need to flash TWRP to root, you can just boot into it without permanently changing your recovery by using this command in fastboot:
Code:
fastboot boot nameoftwrp.img
from there flash magisk and you're done
Slim K said:
No worries friend, everyone starts somewhere and IQ is not a real scientific measurement. Now let's clear some things:
You're not in fastboot mode if you didn't recognize it immediately. To enter fastboot from adb, use:
Code:
adb reboot fastboot
and no you don't need twrp to access fastboot mode.
The correct way to use pull looks like this:
Code:
adb pull <path of file to pull> <path of destination on pc>
for example:
Code:
adb pull /sdcard/Download/YOURFILENAME C:\platform-tools\
Also from context of your question, i assume you want to root your phone. Something helpful to remember, you don't need to flash TWRP to root, you can just boot into it without permanently changing your recovery by using this command in fastboot:
Code:
fastboot boot nameoftwrp.img
from there flash magisk and you're done
Click to expand...
Click to collapse
i am being told that there is no fastboot for Samsung devices, however your commands within powershell all worked, i managed to drag my file over. thank you!
you said "now flash magisk" like its something everyone knows. I have magisk manager on my tablet now and I have a magisk.zip on my PC. I am using a program called ODIN for flashing Samsung devices but i cant seem to put all of these pieces together to root or flash my phone.
any advice?

Categories

Resources