Had Tiamat xoom 1.1 + Tiamat Kernel. Trying to get back to stock
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
anyone have any ideas how to recover from this? I've tried changing usb ports as one thread for a very slightly similar issue stated. Didn't work.
UPDATED: managed to get on stock 3.1.. eventually. huge PITA but it's done.
holtenc said:
Had Tiamat xoom 1.1 + Tiamat Kernel. Trying to get back to stock
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
anyone have any ideas how to recover from this? I've tried changing usb ports as one thread for a very slightly similar issue stated. Didn't work.
UPDATED: managed to get on stock 3.1.. eventually. huge PITA but it's done.
Click to expand...
Click to collapse
I am running into a similar issue. Coming from Tiamet 2.2 + Tiamet kernel I am unable to flash back to system. I can flash boot, recovery, and userdata images, but the system image gives the same error (Failed to process command error (0x120000)).
Could you please share how you made it back to stock (if you can remember, I know it's been a few months
Recover from Failed to process command error (0x120000)
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
Alrighty, it took me 2 days but I finally figured out how to get past this dreaded error.
My Fastboot was unable to flash system.img (but successfully flashed boot, recovery, and userdata) to my rooted, unlocked US Xoom Wi-Fi Only running 3.1, 3.2, and/or 3.21 (yes I tried from all 3 versions using various update.zip methods).
I was attempting to revert to stock using the methods described in multiple threads on XDA, but couldn't get past the 0x120000 error when trying to flash the system.img.
Disclaimer:
This was done on an unlocked, rooted US Wi-Fi Only Xoom running HC 3.1. While this fixed my issue, I take no responsibility if the method does not work on 3G/4G versions, non-US versions, or just plain works differently between different devices. Using dd to flash images is not the safest route, but for me it was the only route.
Prerequisites:
Have adb access (preferably through installing the Android SDK)
Have CWM Recovery installed on Xoom
Steps:
Download the stock HWI69 images from bwcorvus' sticky http://forum.xda-developers.com/showthread.php?t=1049485
Extract the image files into your platform-tools directory in the android-sdk
Reboot into recovery
Code:
adb push boot.img /sdcard/
adb push system.img /sdcard/
adb push recovery.img /sdcard/
adb push userdata.img /sdcard/
adb shell
su (if it doesn't bring you into root # prompt)
busybox dd if=/sdcard/boot.img of=/dev/block/mmcblk1p7
busybox dd if=/sdcard/system.img of=/dev/block/mmcblk1p8
exit
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Follow lock instructions on device
Related
My Xoom has had an odd problem. When I got it new, I unlocked the bootloader and rooted.
However, any pushed updates from Moto such as HLK55 caused my Xoom to boot and show the unhappy !Android icon. I had to shut down cold, and reboot. In other words, it never updated properly.
Now that ICS is out, I have Kang 1/15 running but have some non-crash issues. I'd like to flash to try to update to the factory ICS push file but fear that my XOOM won't complete as well.
Any ideas?
So long as you flash back to complete stock using the Motorola files you should be able to upgrade your way up to ICS (via 3.1 and 3.2).
Get the files from http://developer.motorola.com/products/software/
And as on that page, get ADB running and make sure it detects your device then run these commands.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Make sure you get the right version for your device.
So i have been an avid follower of Droid-Life for quite some time now and they have just recently posted their guide to installing Lollipop. I have flashed custom roms in the past and sideloaded things as well, all successfully, but not with this device. So i found that i needed to have fastboot enables to do the adb sideload. i found a like and followed the directions to a T and tried to install the .zip and its telling me that
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Here is the walkthrough i used:
http://forum.xda-developers.com/showthread.php?t=2277112
I have no idea what im doing now and my device wont reboot to factory either. im desperate, please help.
Step-by-step, what did you do? Sideloading is done through adb while in recovery. Fastboot commands are executed while in bootloader.
Wakamatsu said:
Step-by-step, what did you do? Sideloading is done through adb while in recovery. Fastboot commands are executed while in bootloader.
Click to expand...
Click to collapse
I ran through all the steps in this link all the way to
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip (where superawesomerom had been changed to the .zip file that i got from Droide-life)
and it wouldnt install
I think i went with the instructions for installing a custom rom when i wanted to sideload the OTA update and screwed everything up and now i cant figure out how to get back to my factory image
FIXED IT!!!!! Used fastboot to flash the factory image that Google just released! Got the phone back and its Lollipop!
So I tried to return back to stock with the Factory Images and I keep running into a problem. It won't let me and now I am stuck in a bootloop. I tried the flash-all script provided by Google and it failed after flashing the Bootloader and Radio. I also tried the toolkit located in the Development section and I get the same thing!
Any help would be great. I am used to flashing from command line but now there are so many img. I don't know which is what.
Edit:
I downloaded the new ADB and Fastboot drivers from Google and then I was able to restore my phone with Google's flash-all script.
I have not done it yet, but here is my recommendation. Reboot the phone into bootloader. Check the active slot (a or b). Let's assume a is active. These should get your back to stock.
fastboot flash boot_a boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
If you want it back to a brand new phone (not setup) then add the below as well.
fastboot flash userdata userdata.img
Make sure your adb drivers are up to date. You need sdk version 25. 24 and older has issues with the new partitions.
dbrohrer said:
Make sure your adb drivers are up to date. You need sdk version 25. 24 and older has issues with the new partitions.
Click to expand...
Click to collapse
Yeah, that actually worked for me.
so i have a mtk device in which i mistakenly flashed a wrong custom recovery using mobile uncle tools. now i have no working recovery in this device & device wont even factory reset as it tries to reboot into recovery mode then fails to boot into corrupted recovery & again reboots into operating system without doing any reset.
so im here to know if there is any way to recover my built-in recovery system or atleast factory reset my device without using any recovery. i have tried using adb but faced the following error:
PS C:\adb> adb devices
List of devices attached
0123456789ABCDEF device
PS C:\adb> adb root
adbd cannot run as root in production builds
PS C:\adb> adb shell
[email protected]:/ $ wipe data
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
[email protected]:/ $
Khaled786 said:
so i have a mtk device in which i mistakenly flashed a wrong custom recovery using mobile uncle tools. now i have no working recovery in this device & device wont even factory reset as it tries to reboot into recovery mode then fails to boot into corrupted recovery & again reboots into operating system without doing any reset.
so im here to know if there is any way to recover my built-in recovery system or atleast factory reset my device without using any recovery. i have tried using adb but faced the following error:
PS C:\adb> adb devices
List of devices attached
0123456789ABCDEF device
PS C:\adb> adb root
adbd cannot run as root in production builds
PS C:\adb> adb shell
[email protected]:/ $ wipe data
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
[email protected]:/ $
Click to expand...
Click to collapse
You need to obtain a copy of your stock recovery and then flash that copy of stock recovery onto your device. If you can find a copy of your stock firmware, you can try extracting a copy of stock recovery from the firmware and use that copy to flash the device.
Sent from my SM-S767VL using Tapatalk
I have searched a lot and found one copy of my stock firmware (still not 100% sure about the rom) and it contained recovery.bin file (but I need recovery.img) image file to flash with mobile uncle or flashify.
So I used SP flashtool to flash only the recovery file into my device. But it showed some error (PMT has changed of this rom) and failed the flash. After searching for solution, people were telling me to erase my full device including boot & bios with SP flash tool then flash the new copy of my downloaded stock firmware. But I can't take the risk of erasing my device and bricking it (as I already told I have doubts about the downloaded rom)
Droidriven said:
You need to obtain a copy of your stock recovery and then flash that copy of stock recovery onto your device. If you can find a copy of your stock firmware, you can try extracting a copy of stock recovery from the firmware and use that copy to flash the device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
what if the downloaded rom is also corrupted like the custom recovery i tried to flash........ im trying to avoid this kind of risky steps. i have heard mobile uncle tools flashes custom recovery temporarily & the stock recovery is still there somewhere which can be found using root explorer. so i was asking is there any way i can extract that stock recovery from system files and use it OR just any other way to factory reset my device using adb/fastboot
Khaled786 said:
what if the downloaded rom is also corrupted like the custom recovery i tried to flash........ im trying to avoid this kind of risky steps. i have heard mobile uncle tools flashes custom recovery temporarily & the stock recovery is still there somewhere which can be found using root explorer. so i was asking is there any way i can extract that stock recovery from system files and use it OR just any other way to factory reset my device using adb/fastboot
Click to expand...
Click to collapse
I told you what you needed to do, now, you just need to accept it and do it.
Sent from my SM-S767VL using Tapatalk
So i goofed up and wiped everything under advanced when I was switching Roms. I was able to get the original recovery image installed (nv-recovery-st-wx-na-wf-5.2.0.zip) but if i reinstall TWRP and attempt to install any rom, the device name is still "" instead of "ShieldTablet". Is there anyway to restore the device name? I have been digging around on the forums (Including other device forums) but installing recovery is all I have been able to find. (Note: There was some guides advising removal of the device name check from the script within the image file, then re-zipping it. But this seems to always fail with a bad image error.)
Recovery was installed manually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Recovery image pulled from https://developer.nvidia.com/shield-open-source
More info to issue.
Boot into bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Boot into OS. (everything works.)
EnableUSB debug
adb shell settings get global device_name (Gives back "SHIELD Tablet")
Reboot into bootloader
fastboot flash recovery twrp-3.5.1_9-0-shieldtablet.img
Reboot into twrp
Copy on Rom and attempt to install.
Error text:
E3004: This package is for device: shieldtablet; this device is .
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Lineage-14.1-20210312-unofficial-shieldtablet.zip'
Note: above error text occurs when trying to install any ROM.
I am trying to figure out where "E3004: This package is for device: shieldtablet; this device is ." is pulling the device name. That is the part that I need to fix somehow.
Hi did you try to use a older version of twrp ? I also had my issues with the 9.5.1 version as it doesnt recognize my sdcard so i reflashed the version 9.5.0
You beautiful person! Downgrading from twrp-3.5.1_9-0-shieldtablet.img to twrp-3.5.0_9-0-shieldtablet.img allowed the img to install!
Checking in with the same problem. Thank you for the solution listed of downgrading to 3.5.0_9-0.
Currently flashing!