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
Okay.. so I've tried the new one click method and the manual method but everytime it tries to flash a recovery it says "sending 'recovery' <4136 KB>... FAILED (command write failed (Uknown error))
Any help?
try root toolbox https://play.google.com/store/apps/details?id=com.lukemovement.roottoolbox.free you can flash recoverys via that app. or get a terminal app for you fone https://play.google.com/store/apps/...251bGwsMSwxLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ.. the put the recovery .img on the root of your sdcard and in the treminal app do:
Code:
su
flash_image recovery /sdcard/{file name with .img} (dont use {})
if you get no error turn off fone then hold Vol. Up and Power till' recovery boots
Well to be able to do that, I'd need a recovery to flash the su.zip. I'm not roooted yet just havean unlocked bootloader.. I can't flash the customer recovery to flash the such file.
I think you are having hardware problems
Hello!
So, this is my first post here at XDA, so bear with me if my question has already been answered somewhere else. If so, pretty please point me to it and I'd be forever grateful, 'cause I really have searched for it without really getting somewhere. Of course, that might because I'm a real beginner at this and just cannot patch the bits and pieces of info together properly.
Background to problem
I have a TF300TG. I have unlocked the bootloader via official channels, and flashed CWM 5.5.0.4. Then I flashed CM9 stable, and got stuck in a bootloop. This was solved by a wiping of cache/dalvik and maybe a factory reset (don't really remember). Anyway, i managed to boot is, and realized that i could no use the 3G functions. Stupid i know, should have read more about it, but I finally realized that there are almost no custom ROMs for the 3G version of this transformer. So, what I now wanted to do was flash to something that would work.
I've read that it's only stock or the Hydroponic roms that are available for the TG-version, so I chose to try the Hydro. However, I read somewhere that I should use TWRP instead of CWM to flash, due to some kernel update-thingies, that CWM would not be able to do. If I understand it correctly, I needed to update the kernel back to the stock kernel, since I came from a cyanogenmod with a different kernel (?).
Flashing TWRP via fastboot was easy, and then I flashed the hydro TG rom from TWRP, which gave me bootloops again. Now I could not solve the bootloops via wiping cache or factory resets, nothing solved them. I tried reflashing several times, and also tried flashing after reverting to CWM again. This flash also worked, but I still got the bootloops.
Where I'm at at the moment
I have tried to flash the stock ROMs from Asus, both 9.4.4.40 and 9.4.4.28. However, they do not flash at all from recovery. I get a Status 7 error no matter if I use CWM or TWRP. And yes, i have extracted the downloaded .zip once, before flashing.
I have tried the fastboot -i 0x0b05 update update.zip command, but only get this:
Code:
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
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
[COLOR="Red"]Failed to process command flash: system error(0x170003)[/COLOR]
I have wiped system, cache, data etc from fastboot, so the pad is pretty much clean from everything except recovery partition. Maybe there's somehing wrong with the partitions, 'cause when I try to format them - system for example - i get the following:
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.005s
My questions are these:
How do I flash back to stock, with a stock kernel, if the above things have not worked? Is there a way to flash via ADB that could work, instead of recovery or fastboot?
What's the deal with sometimes flashing the .zip files, sometimes .blob files, and sometimes .img files? I'm confused.
What does the status 7 error mean? Don't really get it from what I've found in my searches.
Can i somehow use the /staging partition to install? If so, how do I push the file there, and which file exacly should I use?
If anyone has any suggestions, I'd be forever grateful. And remember, I'm not an experienced android tinkerer, I have only a Desire HD with CWM and CM7 since before, which was done pretty much by following step-by-step guides and not much understanding from my side. ;P
If you need more info, just let me know.
Cheers!
Niklas
Update:
I managed to flash the hydro rom via CWM. It is still stuck on the Nexus 7-like bootanimation, though. Can't understand why it does not boot all the way into the OS. Ideas?
Update 2
I followed the tip here., and it seems to work. I managed to flash the non-3G version of the hydro rom, and could boot into the OS. Then id somehow worked to flash the 3G version, without any wipes. This time it said "updating android" and then booted! It does not recognize the SIM card, though, but I'm getting more confident that I will be able to fix this now.
So, I have been able to update to the Hydro rom, and can use the tablet, but since 3G is not working in those ROMs, I want to revertto stock ICS. However, I still get the Status 7 error when trying to flash the stock zip from Asus siste. Have tried .40 and .28 WW SKU, none of which is working. Cannot flash the roms in either TWRP, CWM or via fastboot.
Does anyone know what the problem could be? Can it be that the files are not really base roms, but only meant as updates to previous installs? If so, where can I get a base stock ROM?
Nah the work as full recoveries. What boot loader version do u have?
You can reflash stock kernel, by flashing stock ROM through fast boot.
naelme said:
Nah the work as full recoveries. What boot loader version do u have?
You can reflash stock kernel, by flashing stock ROM through fast boot.
Click to expand...
Click to collapse
Hey, thanks for answering. Where do I see the bootloader version? Kernel version is 2.6.39.4-00003-gafee6c5 [email protected] #1
I tried flashing the stock rom via fastboot, using the blob inside the update package
Code:
fastboot -i 0x0b05 flash system blob
I've also tried flashing the ZIP in CWM and TWRP, and I have unzipped the downloaded zip one time as the instructions say.
When you load in recovery mode it tells you boot loader 9.1 or 10.4
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ah, OK. It says bootloader (2.10 e) released by "WW-epad-9.4.4.40-20120704" A03.
I would try to load jb..
Just visiting the threads with the custom Roms for this device makes my device brick...
I'm sure you can bring it back, another thing you can do is let the battery in the unit fully die then try.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
naelme said:
I would try to load jb..
Just visiting the threads with the custom Roms for this device makes my device brick...
I'm sure you can bring it back, another thing you can do is let the battery in the unit fully die then try.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
OK, then I just have to wait patiently for Asus to release JB for the TG-version. Had hoped to be able to solve it beforehand, but hopefully that will finally solve it for good.
Thank you for your time.
hello
after this
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
Failed to process command flash: system error(0x170003)
=> that the error arrive sometime ... try to do one again and that pass, i have the same error and on the second test i have the success
see link here => http://forum.xda-developers.com/showthread.php?t=1750861
that ok if you dont have go on JB update before ....
hakkukakt said:
hello
after this
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
Failed to process command flash: system error(0x170003)
=> that the error arrive sometime ... try to do one again and that pass, i have the same error and on the second test i have the success
see link here => http://forum.xda-developers.com/showthread.php?t=1750861
that ok if you dont have go on JB update before ....
Click to expand...
Click to collapse
too many details, none of which I was looking for
but here's my questions/recommendations
1. Are you on ICS? If yes what version of TWRP did you install there's 1 for ICS and 1 for JB
I recommend making sure you've installed TWRP for ICS and use TWRP to flash the official ICS firmware from the asus website
once everything is confirmed working then install Hydro for ICS TF300TG
2. If you're on JB. Unfortunately there is currently no going back to ICS. Also the Hydro JB Rom to my knowledge currently does not suport TF300TG, and I'm not aware of any ROM for TF300TG that is running JB
I recommend making sure the correct version of TWRP is install then, use it to flash the official ASUS ROM
hello
yes i'm on ICS
1. i use CWM
hum that's not me that have problem
i answered on the last post ...
sorry for my bad english, i speak normaly in french
Hi nikwid,
thanks for the detailed description!
Here's my story: my TF300TG is on stock 9.4.4.22, and I can't update to stock 9.4.4.28 nor 9.4.4.40. It's working normally, except the ugly screen flicker in the left lower corner and WIFI reconnect delays. The latest ASUS update promises to fix these issues, that's why I really would love to flash it.
History
Unlocked device
Flashed Root + CWM
Everything went flawless up to this point. The TF300TG is still on stock ASUS system.
Current situation
When flashing with CWM and TWRP I get:
Code:
Finding update package...
Opening update package...
Installing update...
script aborted (no error message)E:Error in /sdcard/WW_epad-user-9.4.4.40.zip
(Status 7)
Installation aborted.
fastboot outputs (no matter if flashing to system or staging):
Code:
writing 'system'...
FAILED (remote: ()
finished. total time: 142.102s
I don't dare to try `format` with fastboot, as I don't want to brick the Transformer.
I would be happy for any hint how to successfully update from stock to stock?
See you,
Berny
I seem to be stuck in the same situation.
I cannot install "WW_epad-user-9.4.4.40.zip" from within TWRP2 (2.6, 2.5 and 2.4 tried) and I cannot do "fastboot" as I get the same error messages as the others reported here.
This thread is old, but maybe today someone knows the answers?
I successfully installed WW_epad-user-10.4.3.9.zip by editing META-INF/com/google/android/updater-script in the zip and removing everything except the line
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
Later on I installed the other two packages (SAM_6260_ALL.fls and TF300TL_AMSS.MRP) one by one.
After this I successfully installed WW_epad-user-10.6.2.3.zip by just removing all "show_progress" and "set_progress" lines in the updater-script.
Finally the original WW_epad-user-10.6.2.6.zip installed without editing it (TWRP 2.5.0.0).
Now I can even check for new updates using the tablet, this didn't work since installing root and CWM
HTH!
Berny
gaga-man said:
I successfully installed WW_epad-user-10.4.3.9.zip by editing META-INF/com/google/android/updater-script in the zip and removing everything except the line
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
Later on I installed the other two packages (SAM_6260_ALL.fls and TF300TL_AMSS.MRP) one by one.
After this I successfully installed WW_epad-user-10.6.2.3.zip by just removing all "show_progress" and "set_progress" lines in the updater-script.
Finally the original WW_epad-user-10.6.2.6.zip installed without editing it (TWRP 2.5.0.0).
Now I can even check for new updates using the tablet, this didn't work since installing root and CWM
HTH!
Berny
Click to expand...
Click to collapse
By the way, I think that deleting all lines in "META-INF/com/google/android/updater-script" except the following one
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
will do the same as extracting the "blob" file and flashing it with
Code:
fastboot flash staging blob
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
forcemaker said:
I seem to be stuck in the same situation.
I cannot install "WW_epad-user-9.4.4.40.zip" from within TWRP2 (2.6, 2.5 and 2.4 tried) and I cannot do "fastboot" as I get the same error messages as the others reported here.
This thread is old, but maybe today someone knows the answers?
Click to expand...
Click to collapse
Current status: I can install an Asus Stock ROM by extracting the blob file and flashing that with
Code:
fastboot flash staging blob
The fastboot command never reports finishing (in this situation), so I stop it by pressing Ctrl+C in the console window, but only after giving it enough time, e.g. 10 minutes, to finish.
Code:
sending 'staging' (800933 KB)...
OKAY [135.726s]
[COLOR=Red]writing 'staging'...[/COLOR] [I](here it stays forever)[/I]
From this moment on no fastboot commands (e.g. "fastboot --reboot") are accepted until I manually reboot by pressing the "Power" button for 10-11 seconds . During reboot there will be a progress bar underneath the ASUS logo, which moves to completion within 10 minutes. After that the system reboots and the clean Stock ROM is installed.
I tried this on my TF300TG by
resetting it by "full wipe",
then via nvflash to an Android 4.0 Bootloader (if you are on a 4.0 Bootloader, go here: http://forum.xda-developers.com/showthread.php?t=1894867 !!!)
and with the latest Asus Stock ROM
4.0.3 (TF300TG: WW_epad-user-9.4.4.40.zip) and
4.2.1 (TF300TG: WW_epad-user-10.6.2.6.zip).
for TF300T (without 3G) there are different Asus ROM version numbers, you can find them here: http://forum.xda-developers.com/showthread.php?t=1697227
Remember, going to Asus Stock ROM 10.6.*.* will give you Bootloader for Android 4.1 and 4.2 which are not downgradeble to 4.0 unless you already have the nvflash backup files created with 4.0.
has anyone already tried to root there official ics Rom that was released yesterday? And how?
Sent from my HTC Desire S using xda premium
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
anyone can confirm this is working?
mayurh said:
anyone can confirm this is working?
Click to expand...
Click to collapse
Yes. I can - that's why I posted the solution.
Or you can just use the search button. :banghead:
SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you
linqdesires said:
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you
Click to expand...
Click to collapse
No, my DS was S-Off - done with XTC-Clip 18 months ago.
Go to recovery mode;
choose .zip from sd card
Flash this
100%
potencia said:
Go to recovery mode;
choose .zip from sd card
Flash this
100%
Click to expand...
Click to collapse
give thanks is for free
For the people, like me, who have only done the HTCdev unlock ( S-ON ), it's quite easy to update the software/ROM using the RUU.
After downloading the RUU from here : http://forum.xda-developers.com/showthread.php?t=1857478 I just immediately ran it, but it failed with an error along the lines of : RUU, security fail! update fail!
So after a bit of googling around I figured that the RUU might simply not be happy with the phone being in an unlocked state, so after doing the following the RUU ran successfully :
1. Re-lock the bootloader with the "fasboot oem lock" command. The output after running the command shows the lock process was successful but moaned about something else failing, still not sure what that was. So after doing this my phone was kinda stuck in the bootloader, where it says ***relocked*** at the top and ***security warning!*** right underneath it. Everytime I reboot or powercycle it would just boot straight back into the bootloader with the warnings, which worried me a little bit.
2. In the bootloader I selected fastboot and connected the USB cable, and then I ran the RUU again. This time it completed successfully after some time. My HTC sync was installed but not running, so seems like that isn't even needed ?
And that's actually it. This process obviously puts the phone in a relocked state, and an overall factory configuration, it also restores the recovery ROM to the factory image or whatever.
No success
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?
w_hy said:
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?
Click to expand...
Click to collapse
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.
steps made by me
SimonTS said:
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.
Click to expand...
Click to collapse
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.
w_hy said:
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.
Click to expand...
Click to collapse
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?
Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Sent from my Desire S using xda app-developers app
c.m.b said:
Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Click to expand...
Click to collapse
Yes
SimonTS said:
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?
Click to expand...
Click to collapse
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b
w_hy said:
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b
Click to expand...
Click to collapse
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip
SimonTS said:
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip
Click to expand...
Click to collapse
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?
w_hy said:
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172
SimonTS said:
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172
Click to expand...
Click to collapse
So:
hboot: 2.02.0002
s-off /xtc clip/
recovery.img: what you said /puted in new directory togeather with adb.exe and fastboot.exe/
command: as before
result: the same:
G:\0\4>fastboot flash recovery recovery.img
sending 'recovery' (5624 KB)... OKAY [ 0.987s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.988s