I downloaded ota image for 8.1 and sideload from adb. It's showing error. Any suggestions?
Everyone was getting this, and the OTA has since been taken down.
Related
Im trying to sideload magio rom rc6 on my htc one s. I start adb, i go to my computer and open cmd and then i ran the command "adb sideload magiorom_RC6.zip" i kept on getting "error:closed". I tried it multiple times but i still got the same error. Now im getting a message that says "error: more than one device and emulator". What should i do. Please Help!
_______________________________________________________________________________________________________
SOLVED:
What i did is before doing adb sideload rom.zip i did adb usb. That fixed the error
I know this might not be the best section for this but here goes.
I've got a Samsung Galaxy Tab 2 10.1. I have TWRP 2.8.6.0 installed and I would like to update that to 2.8.7.0. I need perform this update via adb sideload as the new version of my rom of choice doesn't seem to want to boot. I use CM12.1 by the way. Anyway, I have a laptop that came with Windows 8.1 and I went ahead and took the update to 10. Now my problem is I cannot figure out how to update adb from version 1.0.31 to 1.0.32 or better so I can use adb sideload on twrp 2.8.6.0. Anyone here familiar with what I need to do to get this accomplished?
Thanks for any help in advance.
Update.
I finally figured out how to update adb via the command prompt. So 1.0.32 is up and running on my machine now. I updated twrp to 2.8.7.1 via odin. My machine still does not detect any devices when I plug my tablet in and start adb sideload. Any thoughts?
Hi,
My phone was rooted with TWRP installed. Then I decided to go back to my Stock Rom as I was not receiving OTA updates. But in the process, I messed up the things and accidentally deleted my OS too. Then I found this ROM https://docs.google.com/uc?id=0B5uo5LCdnblrVlhsRmdyeDRYV1E&export=download. I renamed the zip file as "update.zip". Then, I followed the instructions by eg0097 described here http://forum.xda-developers.com/showthread.php?t=2662719&page=2 and entered the commands in fastboot mode. But this deleted my TWRP. However, I am able to access stock recovery and trying to install stock rom using adb sideload. I downloaded ROM from here https://drive.google.com/file/d/0B4Cs-21Ur-CARW9hazNLajduQWs/edit and entered into stock recovery mode. There using apply update from ADB. I entered command in command Prompt: "adb sideload MGXT1032DV1.zip". After copying 100% to the device. I get the "Installation Aborted" after "Verifying Update Package".
Am I doing something wrong. Please help.
Thanks
arpit.agrawal said:
Hi,
My phone was rooted with TWRP installed. Then I decided to go back to my Stock Rom as I was not receiving OTA updates. But in the process, I messed up the things and accidentally deleted my OS too. Then I found this ROM https://docs.google.com/uc?id=0B5uo5LCdnblrVlhsRmdyeDRYV1E&export=download. I renamed the zip file as "update.zip". Then, I followed the instructions by eg0097 described here http://forum.xda-developers.com/showthread.php?t=2662719&page=2 and entered the commands in fastboot mode. But this deleted my TWRP. However, I am able to access stock recovery and trying to install stock rom using adb sideload. I downloaded ROM from here https://drive.google.com/file/d/0B4Cs-21Ur-CARW9hazNLajduQWs/edit and entered into stock recovery mode. There using apply update from ADB. I entered command in command Prompt: "adb sideload MGXT1032DV1.zip". After copying 100% to the device. I get the "Installation Aborted" after "Verifying Update Package".
Am I doing something wrong. Please help.
Thanks
Click to expand...
Click to collapse
see
http://forum.xda-developers.com/moto-x/general/moto-x-roll-thread-t3124594
and
http://forum.xda-developers.com/moto-x/moto-x-qa/help-thread-moto-x-question-t3032022
Sent from my XT1254 using XDA Labs
sd_shadow said:
see
http://forum.xda-developers.com/moto-x/general/moto-x-roll-thread-t3124594
and
http://forum.xda-developers.com/moto-x/moto-x-qa/help-thread-moto-x-question-t3032022
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
Thanks for redirecting me in the right direction I am new here, so didn't know about the particular device's forum.
Thanks
I'm trying to go NMF26U from NMF26O (rooted, stock rec) and I have the ~48mb OTA file. I boot to recovery, to go apply update from ADB and attempt to sideload. I get to Step 1/2 and then says error applying update 20 kDownloadState InitializationError and then E:unknown volume for path. Installation aborted. What am I missing?
km8j said:
I'm trying to go NMF26U from NMF26O (rooted, stock rec) and I have the ~48mb OTA file. I boot to recovery, to go apply update from ADB and attempt to sideload. I get to Step 1/2 and then says error applying update 20 kDownloadState InitializationError and then E:unknown volume for path. Installation aborted. What am I missing?
Click to expand...
Click to collapse
Just flash the whole image from Google. Edit the flash all bat file and remove -w from the file so you save your data and apps.
Then reroot.
Get the full OTA from here - Full OTA Images for Nexus and Pixel Devices
I had the same issues. Made sure I had the latest ADB/Fastboot executables and correct drivers from Google. Lastly for me I also had to be on a USB2.0 port on my PC since it won't work on a USB3.0 port on my machine.
I ended up doing the full OTA image in the link via ADB. Still rec'd the E:unknown volume error but everything installed correctly and works as expected.
FYI: I have unlocked boot loader but everything else is stock (stock bootloader, stock recovery, stock system, etc.)
TonikJDK said:
Just flash the whole image from Google. Edit the flash all bat file and remove -w from the file so you save your data and apps.
Then reroot.
Click to expand...
Click to collapse
Hmm... Okay I will try this if next method fails. Thanks.
mrZoSo said:
Get the full OTA from here - Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
donslade said:
I had the same issues. Made sure I had the latest ADB/Fastboot executables and correct drivers from Google. Lastly for me I also had to be on a USB2.0 port on my PC since it won't work on a USB3.0 port on my machine.
I ended up doing the full OTA image in the link via ADB. Still rec'd the E:unknown volume error but everything installed correctly and works as expected.
FYI: I have unlocked boot loader but everything else is stock (stock bootloader, stock recovery, stock system, etc.)
Click to expand...
Click to collapse
So did you still adb sideload the Zip? Did that wipe the device?
km8j said:
Hmm... Okay I will try this if next method fails. Thanks.
So did you still adb sideload the Zip? Did that wipe the device?
Click to expand...
Click to collapse
Yes and it did not wipe the device.
Here's a nice little walkthrough
Pixel: How to Manually Sideload an OTA Update
mrZoSo said:
Here's a nice little walkthrough
Pixel: How to Manually Sideload an OTA Update
Click to expand...
Click to collapse
That guide says use Minimal Fastboot. That is bad advice. It may work for a sideload, but many of the new fastboot commands are not in it, and it does not support our larger partitions. Or our dual partitions.
So sub the Google versions of fastboot and adb in that guide.
This worked. Thanks all!
TonikJDK said:
That guide says use Minimal Fastboot. That is bad advice. It may work for a sideload, but many of the new fastboot commands are not in it, and it does not support our larger partitions. Or our dual partitions.
So sub the Google versions of fastboot and adb in that guide.
Click to expand...
Click to collapse
True, but the guide was written just for sideloading the OTA, and works at this point.
Moving forward, you can always get the platform tools w/ADB, Fastboot from Google, without having to get the whole SDK or Android Studio.
Latest Platform Tools from Google for Windows
Hello,
Earlier today, I flashed the Google OTA on my Pixel 2 (walleye) using TWRP’s sideload feature and the following adb command
Code:
adb sideload ota.zip
Previously, after flashing that zip file, I always reboot, let the phone finish the system update, then reboot to the bootloader where I use Fastboot to boot the TWRP image file so I can re-root the phone with Magisk. Today, I tired to do this same thing, but it did not work. First I rebooted to the boot loader using
Code:
adb reboot bootloader
That command worked. Then I ran
Code:
fastboot devices
That worked as well and my phone was recognized. I then tried to boot the TWRP image with
Code:
fastboot boot twrp.img
This is where the problem occurred. The error code I received was:
Code:
Sending ‘boot.img’ (32768 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
I have no way to boot TWRP right now, any chance you know what to do about this error? I need some way to boot TWRP on my phone.
Thank you in advance!
Can't help, but I'm glad I checked the forum before updating, otherwise I may have run into the same problem. Guess I'll wait until someone responds or you respond with a solution. I usually wait until Sultan posts his kernel update anyway, so I'm in no big hurry.
Edit:
Actually, I noticed you flashed the OTA via ADB. You might try downloading the full image from Google's Pixel factory image page and flashing that via Deuce's boot loop script. Just be sure to pay attention to the prompts and don't accidentally wipe your device.
It's a pretty simple process. Just unzip the contents of the Pixel Image into your ADB folder along with the contents of the zip file inside the image, and then run deuce.bat from the command line initiated from your ADB folder. Then, after it's finished, reboot the device once, update play services, reboot into fastboot, and boot from TWRP to do the rest of your flashing. That's how I update every month and I never run into problems.
jallenhayslett said:
Can't help, but I'm glad I checked the forum before updating, otherwise I may have run into the same problem. Guess I'll wait until someone responds or you respond with a solution. I usually wait until Sultan posts his kernel update anyway, so I'm in no big hurry.
Edit:
Actually, I noticed you flashed the OTA via ADB. You might try downloading the full image from Google's Pixel factory image page and flashing that via Deuce's boot loop script. Just be sure to pay attention to the prompts and don't accidentally wipe your device.
It's a pretty simple process. Just unzip the contents of the Pixel Image into your ADB folder along with the contents of the zip file inside the image, and then run deuce.bat from the command line initiated from your ADB folder. Then, after it's finished, reboot the device once, update play services, reboot into fastboot, and boot from TWRP to do the rest of your flashing. That's how I update every month and I never run into problems.
Click to expand...
Click to collapse
Thank you so much!! This worked when nothing else would! I will keep this in mind for next time :good: