I am yet another idiot that wiped my tab 10.1, and then went to flash the ROM I had downloaded to it. So of course now I'm left with no OS installed and no files on board. I have TWRP installed and can still get to that. I can get to advanced > Adb Sideload. I can type adb devices in the command prompt, and my device is found successfully. But when I type adb Sideload ROM.zip, it states transferring then immediately says 0.00x transferred in the command prompt, and failed in red on the device.
I have never run into this and have googled to no end, but every post I find is related to Nexus devices. Can somebody please offer some insight so I'm not forever stuck in TWRP purgatory
Rather than use adb sideload, why not just use adb push to transfer the .zip file and then flash it normally?
As a last resort, you can also use Odin to flash a stock Samsung ROM or one of Pershoot's old Odin-friendly CM Roms too.
Sent from my GT-N5110 using Tapatalk
Related
Hey all,
So I have a rooted Eris (checked positively using terminal emulator) running a 2.1v3 ROM. What I'd like to do is eventually get to the 2.1 OTA ROM.
Earlier I downloaded ROM Manager which, after some searching gave me some problems other people have been having. I can't flash to the ClockworkMod recovery image as it gives me a "Error occurred while attempting to run privileged commands!" message. I tried reinstalling, fixing permissions etc. all with the same results.
So now i'm trying to flash Amon's recovery image instead using Terminal Emulator and the command line:
su
flash_image recovery /sdcard/file_name_here.img
only to yield the message that the file could not be found or something. I'm on a mac and I saw another way on here that involves running commands from your computer to your phone using the skd. I started to do that only to run into a "permission denied" when attempting the first "adb" command line.
Am I missing something? I'm trying to read and re-read as closely as I can. I'm not entirely comfortable with this whole process but I'm trying to take the time to really understand it and i'm still having difficulties.
Well I only have a small bit of advice on this because I don't completely understand what you're doing, but when I was trying to run adb commands on my mac, I found that I couldn't get adb to work by running "adb shell" from within the tools directory of the SDK, but if I navigated up one directory into the main SDK folder then ran "tools/adb shell" or whatever, the adb commands worked.
If I go that route, I'll give it a shot.
What I'm trying to do in a nutshell is get Amon's (or any) recovery image on my Eris so I can load ROMS easier. Right now, if I were to boot into Recovery, I get the littly android guy next to a /!\ .. :/
Last night I tried flashing through FASTBOOT and my command prompt window stuck at
<waiting for device>
for about 20 minutes before I pulled the battery.
Hello all, So I went to flash a rom through CWM and something went wrong.. long story short it ended up being wiped in fastboot, and loosing my backup in cwm. I AM able to get into my CWM recovery and fastboot. CWM shows "no files found" when I go into install .zip from sdcard. Ive spend the last few nights trying to push a rom .zip via ADB to install in CWM, and here is my problem. Ive have done my research, have ADB running correctly, my device shows up as serial # and recovery in adb, ive placed my the rom .zip in C:/SDK/platform-tools and renamed it simply "prime.zip". When I open my command prompt from platform-tools and put in "adb push prime.zip/sdcard" I simply get a list of the adb commands.No file push progress or anything. I have searched for an answer and not found much, I apologize if the answer is simple and ive missed it in my searching. Thanks for any help you can give me!!
mxrider657 said:
Hello all, So I went to flash a rom through CWM and something went wrong.. long story short it ended up being wiped in fastboot, and loosing my backup in cwm. I AM able to get into my CWM recovery and fastboot. CWM shows "no files found" when I go into install .zip from sdcard. Ive spend the last few nights trying to push a rom .zip via ADB to install in CWM, and here is my problem. Ive have done my research, have ADB running correctly, my device shows up as serial # and recovery in adb, ive placed my the rom .zip in C:/SDK/platform-tools and renamed it simply "prime.zip". When I open my command prompt from platform-tools and put in "adb push prime.zip/sdcard" I simply get a list of the adb commands.No file push progress or anything. I have searched for an answer and not found much, I apologize if the answer is simple and ive missed it in my searching. Thanks for any help you can give me!!
Click to expand...
Click to collapse
Use
adb push prime.zip /sdcard/prime.zip
You shouldn't use CWM - use TWRP instead, because CWM has many problems on TFP and isn't compatible with JB bootloader.
Sent from my LT30p using Tapatalk 2
I was on CleanROM 1.5 for AT&T, but decided to switch to ARHD for continued updates. Flashed the ROM and the problem began. I've since tried to go back to cleanrob via pushing the rom with adb, no go. I've wiped the phone countless times. I've erased the fastboot cache. I've switched TWRP/CWM neither changed anything. Fixed permission, flashed the boot images associated with each rom. Let it hang on the HTC screen for 30 minutes. I've exhausted the extent of google. Can anyone help?
Did you try adb sideload. Open clockwork and click install from sideload. Then go to command prompt, the adb directory and type adb sideload romname.zip.
Try Cleanrom, works for me.
zsamuels28 said:
Did you try adb sideload. Open clockwork and click install from sideload. Then go to command prompt, the adb directory and type adb sideload romname.zip.
Try Cleanrom, works for me.
Click to expand...
Click to collapse
I've tried everything, apparently something is wrong with partitions. No one seems to know how to fix it.
my device is stuck in bootloop with no backup and is not showing up in adb for me to push rom to phone? suggestions????
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
NasaGeek said:
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
Click to expand...
Click to collapse
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
jizang said:
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
1.0.31 and tried both twrp and cwm
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
NasaGeek said:
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
Click to expand...
Click to collapse
yea ridiculous amount times
I had the same problem i could not adb sideload a Rom,in the end i had to flash stock ruu to save my phone
Sent from my HTC One X+ using xda premium
indie12 said:
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
Click to expand...
Click to collapse
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
reaper90 said:
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
Click to expand...
Click to collapse
doesn't work with twrp either,
also forgot to mention is odd that adb doesn't find device since i can flash new recovery / kernal via fastboot?
adb discovering my device in sideload now but not allowing the sideload? how can i push the rom to sdcard via adb?
indie12 said:
doesn't work with twrp either
Click to expand...
Click to collapse
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
reaper90 said:
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
Click to expand...
Click to collapse
its just worked, transfering the rom now, no idea what caused it to work this time but it is so thanks
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.