Database Info

[Q] Latest and Greatest Root steps for WiFi ONLY XOOM

My apologies if this post is a dup, but I'm havin a hell of a time trying to find the proper steps to root the WiFi only XOOM i have hangin out next to me.
I am seeing a ton of posts about rooting the XOOM, with a good bit of them telling me different informationDated 27 April 2011)
http://forum.xda-developers.com/showthread.php?t=1010568&highlight=rooting+wifi&page=17 tells me to download the WiFi only image (Tiamat 1.3...), but then later tells me to download the Tiamat 1.4 images. [scribbi, my apologies for using your post as the example. But your post got me second guessing myself a little bit...(mostly cus I'm paranoid)]
I'm sure I am just second guessing myself over nothing, but just to be sure...
Is there a GOLDEN set of steps (or sticky), as of 27 APRIL 2011, that can give us (concerned rooters) the proper steps for rooting the WiFi only XOOM such that we can follow without minimal concern for the well-being of our tabs?
(I'm an embedded SW engineer, so I understand the repercussions of what I'm doing, which is why I'm to double checking the procedures before I attempt something that may brick my hardware)
Thanks for your time and mad props to everyone that was part of the effort to root this device. I wish I could code as well that they can.

I still do it the old fashioned way. I'm already unlocked so I just flash the boot image. With a clean system partition, you need to push a few drivers (.ko files) on plus "su" and the Superuser.apk. Superuser and su work together. And finally you need to create a new folder so that your real sdcard can be mounted. I think they changed the name from "sdcard2" to something new in 1.4.0.
Not exactly step by step but you can see which instructions that mirrors most.
New instructions involve CWM which I have not installed yet. I like to know what's done step by step as I have a Canadian system.img. I don't want that flashed over.

you could use the "one click" method found in the dev section. its really like a one click at a time, but goes slow so you can read and see what's going on. if your not comfy with adb I would suggest this method. then update the kernel with the kernel manager app.

jase33 said:
you could use the "one click" method found in the dev section. its really like a one click at a time, but goes slow so you can read and see what's going on. if your not comfy with adb I would suggest this method. then update the kernel with the kernel manager app.
Click to expand...
Click to collapse
I don't trust the "one click" methods. Me, I need to know how every part works together and what every step does. I'm more comfortable with using adb and fastboot manually than I am with someone's idea of user friendly. I'm also the kind of guy that would fix his own car rather than have a mechanic fix it for free.
I should take a look at it. The way you describe it, it almost sounds like a batch file.
Also, when I understand what's going on, I can apply the steps in different situations. For example, most of the instructions here are for a PC but I can do exactly the same things with my Mac Mini when my PC isn't convenient.

OK, let me propose one of the root method which is not required to flash any boot image but is required to flash ClockworkMod Recovery and to use the recovery for rooting.
Such method (i.e. using custom recovery) may work not only on WiFi US model (which I have), but also on other models (Verizon, WiFi Europe etc). But I tested it on WiFi US.
So the step by step are:
1. Install ClockworkMod Recovery v3.0.2.5 as described here:
http://forum.xda-developers.com/showthread.php?t=1038870
This actualy means that you need to unclock bootloader and flash ClockworkMod Recovery.
2. Download attached Root_Xoom.zip file and put it on SD card
3. Insert SD card into Xoom
4. Boot Xoom in the recovery mode
5. In ClockworkMod Recovery menu choose "install zip from sdcard" and "choose zip from sdcard" and install Root_Xoom.zip
6. Reboot Xoom
Hope you will have Root after that.

ok so since I'm not currently rooted it looks like this should work for me. Gonna give it a shot in a little white once I get me some courage juice...

Al936 said:
OK, let me propose one of the root method which is not required to flash any boot image but is required to flash ClockworkMod Recovery and to use the recovery for rooting.
Such method (i.e. using custom recovery) may work not only on WiFi US model (which I have), but also on other models (Verizon, WiFi Europe etc). But I tested it on WiFi US.
So the step by step are:
1. Install ClockworkMod Recovery v3.0.2.5 as described here:
http://forum.xda-developers.com/showthread.php?t=1038870
This actualy means that you need to unclock bootloader and flash ClockworkMod Recovery.
2. Download attached Root_Xoom.zip file and put it on SD card
3. Insert SD card into Xoom
4. Boot Xoom in the recovery mode
5. In ClockworkMod Recovery menu choose "install zip from sdcard" and "choose zip from sdcard" and install Root_Xoom.zip
6. Reboot Xoom
Hope you will have Root after that.
Click to expand...
Click to collapse
Other than rooting what else does this particular file do? Ovrclock, usb hosting, sd access??
Thanks

fabian29906 said:
Other than rooting what else does this particular file do? Ovrclock, usb hosting, sd access??
Click to expand...
Click to collapse
This is for rooting only (as OP requested). It is just to push su binary and superuser.apk into system partition. Nothing else.

after that, get kernel manager and install 1.3.2 for oc, sdcard etc.... 1.4.0 isn't stable is it?

Yes, if you need oc, sdcard etc..., you can flash the kernel you like. It can be done after or before kernel flashing.

Do you have to have an SD card to CWM/root your Xoom?

Yes, you need SD card. CWM installs file from SD card to make root

[UPDATE] CWM - Stock + Root 8.6.5.13 US / WW

This is the Stock 8.6.5.13 US update repackaged with:
* Clockworkmod support (It does not include CWM, but doesn't reflash the recovery partition either)
* Rooted (includes SuperUser.apk & su 3.0.0)
* Busybox (1.19.2)
This update worked fine on my TF101. I built it using the same method Roach2010 used to make his previous CWM-repacks so it should be ok. I have only tested this on my own tf101. Let us know when it works for yours too!
This will not work unless you have:
1. clockworkmod
2. STOCK firmware (root is fine)
3. the US or WW firmware
4. firmware 8.6.5.9
If this update will not apply, take note of which assert stopped the process. You probably applied some sort of mod to your transformer.
There was an issue in the initial release. If you downloaded it, delete it and download the new one.
CWM package for ASUS FOTA Update 8.6.5.13 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-proper.zip
Problems updating? Customized Transformer? Try the Update checker.
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-checker.zip US
The Update checker will verify all of the same files that the update verifies. It will not stop on the first error. This way, you can see ALL the files which will cause errors and fix them all at once without the tedious reboot / try update / reboot / fix problem / reboot / try update loop.
Courtesy of brk:
CWM package for ASUS FOTA Update 8.6.5.13 WW (with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5

Has this been tested yet??
Thanks
*Offtopic*

delete ffs

same here, stock but with xoom system UI and bloatware deleted.

Sorry, in my haste I didn't update the recovery binary.
Fixed version in testing now.

Updated first post, new zip is available here:
http://bellybuttonporn.com/transformer/kwt-cwm-8.6.5.13-proper.zip

cky2000 said:
for me, it did not work.
I tried from a fresh/clean install (nvflash) of US_epad-user-8.6.5.9. and got this error in CWM:
assert fail: getprop ("ro.product.device") == "EeePad" || getprop ("ro.product.device") "EeePad"
E:Error in /sdcard/kwt-cwm-8.6.13.zip
(Status 7)
Installation aborted.
bellybuttonporn
Click to expand...
Click to collapse
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.

Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John

Cordy said:
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Click to expand...
Click to collapse
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).

Xerravon said:
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Click to expand...
Click to collapse
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)

ryan stewart said:
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Click to expand...
Click to collapse
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?

The issue is I have it back on my device, I found it, and the update is still hanging on that.

daoist said:
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
Click to expand...
Click to collapse
Hi,
Thanks for the help! It worked like a charm, no problems at all.
I am wondering now, do I need to update my CWM recovery, or do I just leave it how it is?
thanks for the file and help!!!
Now I just have to figure out how to get rid of the notification...

Has anyone noticed the web browser performance? Is it still checkerboard on display? Where it displays the page in chunks... and is this android 3.2.1? or just firmware update?

Worked fine on mine, Thx.

daoist said:
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
Click to expand...
Click to collapse
Would it be possible to remove the check and the patch? I am looking at the updater script, what I would love is to just remove its check and attempt at patching the bloatware.
For Example, the Check:
assert(apply_patch_check("/system/app/Finsky.apk", "19a70336522820f20a9e1d9f065ae56a714aa7cf", "690dc80af4303cb2df1991de9d52c269211e1dcf"));
set_progress(0.116486);
assert(apply_patch_check("/system/app/Finsky.odex", "fda5fbff54fc6c35b9210afd4a3b76b6a8862d83", "59412510a7d0a789b1e732dbffdc9feb3245e964"));
set_progress(0.119390);
And the Update:
apply_patch("/system/app/Finsky.apk", "-",
19a70336522820f20a9e1d9f065ae56a714aa7cf, 1070527,
690dc80af4303cb2df1991de9d52c269211e1dcf, package_extract_file("patch/system/app/Finsky.apk.p"));
set_progress(0.135043);
apply_patch("/system/app/Finsky.odex", "-",
fda5fbff54fc6c35b9210afd4a3b76b6a8862d83, 655760,
59412510a7d0a789b1e732dbffdc9feb3245e964, package_extract_file("patch/system/app/Finsky.odex.p"));
set_progress(0.138224);
If I didnt want it to update finksy (bad example but just one I grabbed) could I just delete everything above from the script? In the case of something like Zinio I dont even want the update since I nixed the underlying app.
I actually tried something like that but it failed immediately, no error. Im wondering if I havent zipped it up right.

Yeah, if you search through the update script for the name of the file that's erroring out, there's 2 places. First the assert, then the patch. Get rid of both and you're fine.
I'd google what those files are before you remove them from the script, just to be safe.
Just for example, Finsky is part of Market

Im wondering if there is something I am doing wrong or if there is a trick to zipping it back up. I tried removing those lines (for AWS, not Finsky ) and the update failed without an error (just aborted).
Im wondering, should I be leaving that set progress, zipping using a particular method?

The biggest problem I had was making sure the files were saved with unix line-endings. If you edited it in notepad or something like that it may have defaulted to windows line-endings.

Hi can you add this to 1st post:
CWM package for ASUS FOTA Update 8.6.5.13 WW
(with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
If it gives you an error about some file check, edit update script and put a "#" before the line of that file.

Possible fix for lost root with 8.6.5.21

2nd update today! 4th Jan
Thanks to GLS9 and Baseballfanz for the info. It seems we have a universal root. 'Nachoroot'.
Check it out here if you were left stuck with the other methods. http://forum.xda-developers.com/showthread.php?t=1427838
Mangraa posted this. Hopefully it will help those who have been stuck so far. 4th Jan 2012
- Get Razorclaw and install it, no root needed.
- Get the recovery installer and do the same.
- Check your version info. You'll see a pair of letter which are like the "WW", "UK", "US" pairs in the various update files. It appears, at least when I was trying to do this, that you cannot use unmatched pairs (I don't know about the "WW" one, since I started with US and (accidentally) went to .13 US version).
- Follow the instructions regarding downloading the .13 update (WW version and/or whatever letter pair your tablet uses, in case the WW doesn't work). Unzip, slap on external SD, power off, power on with down volume, volume up to go to recovery, bang. Done.
- Do the same thing with the megaupload file (.19). The second option did fix the problem I had, which was trying to update to a WW.19 firmware from a US.13 - DO THE DOUBLE FILE/RENAME TRICK. It works perfectly.
- Run razorclaw, run recovery installer, and gloat.
Seriously, now knowing how the paired-letters-not-compatible-with-other-letters thing works, the whole process would take maybe 10-15 minutes tops. Thanks for the post!
update. Success does seem to vary and some people have managed to make this work with a different SD and other variations. If my method or Trip's doesn't work for you have a look at some of the tweaks that other guys have used. If you did something different and it works let us know. Thanks.
I have a UK transformer and I lost root after the OTA 8.6.5.21 update. Yes, should have checked before applying.
Wasn't able to root with NVFlash so I downloaded http://www.multiupload.com/X65RBVD2MB the 8.6.6.19 file that was posted by Lizard here http://forum.xda-developers.com/showthread.php?t=1393953&page=3
I unzipped it until I had the WW_epad-user-8.6.6.19.zip file. I placed this on the root directory of the external SD card and when I rebooted it gave me the option to install.
This installed OK so I just re-ran Razorclaw and sorted. I have superuser back.
Warnings and all. This would seem to be the US update but is working fine on my UK B70 (presumably SBK2 pad). I've installed CWM and backed up too. No promises that this won't destroy your pad/steal your gal or boy/shoot your dog.
Card formatting?
Originally Posted by elek_it
For all the people having problem:I was on b80 .21, and tried both methods with no success. Always the green android with yellow exclamation mark.Then, I noticed that when copying files to the sd from windows, it always asked for "permissions". That was formatted with NTFS.Tried another microSD in FAT32, just copied the WW_epad-user-8.6.6.19.zip file and VOILA', all worked flawlessy (method 1).
Step by step
1) Download http://www.multiupload.com/X65RBVD2MB
2) Unzip so you have just have WW_epad-user-8.6.6.19.zip. Keep this zipped and copy to root of external micro SD.
3) Reboot with card in place, don't enter recovery.
4) When it booted back into the OS I had a triangle in the notification bar. I clicked this and it offered to install the update.
5) After tab updated as usual I just re-ran Razorclaw and I had root back.
Update. trippmcnealy had success with a tweak to this. If it doesn't work you might want to follow his method.
1) Download http://www.multiupload.com/X65RBVD2MB
2) Unzip so you have just have "WW_epad-user-8.6.6.19.zip". Keep this zipped and copy to root of external SD.
3) Put another copy of the same file on your external SD card and name it "EP101_SDUPDATE.zip"
4) Put both files "EP101_SDUPDATE.zip" and "WW_epad-user-8.6.6.19.zip" on the root of your internal SD card.
5) Power down your TF
6) Power up into recovery - by pressing the power button and volume down button. Then press volume up when instructed by the screen.
7) You should now see the Android guy with some gears turning. This is good, actually this is GREAT! This will go on for a minute or so and then the device will reboot on its own. It will then go to the boot screen and you should see a bar showing you the progress of the update.
8) Once it has completed, install RazorClaw and root your device.
Tips from Baseballfanz
For those not able to get it working, a few things to check.
1-Make sure you actually extract the WW_epad-user-8.6.6.19.zip within the zip. Inside the file you download is an Asus folder, inside that is an Update folder, inside that is the WW_epad-user-8.6.6.19.zip file you'll be working with.
2-When renaming, if your PC is set to "hide known extension", you'll not see the .zip so if you type in .zip you'll get filename.zip.zip The file manager on the TF should show you the extension
3-Make sure it's on the root of the sd card and not within any folder.
4-Check spelling of files
WW_epad-user-8.6.6.19.zip EP101_SDUPATED.zip
5-Micro sd card is in FAT32 format. Try a different card or format again (after saving your stuffs)
6-File manager on the TF sdcard is internal and Removable/MicroSD is the external sd card.
Suggestions
It would be useful for people to report info with posts about success or not. What SBK, serial number (B70 etc) and current firmware are you on? I'm no dev but hopefully we can make things easier for others.
Resources
Razorclaw
http://forum.xda-developers.com/showthread.php?t=1346180 Gnufabio's recovery installer, suggested by Baseballfanz
Reboot to Recovery Makes it easier to enter recovery after installing CWM.
Please let me know if any info is missing and I'll update.

Ah, this seems interesting! I also have a uk transformer and will give it a go.
So you don't need anything else but stock? I will try this now, and does it wipe your data? Used asus backup just in case.

Cool
Hi,
thanks for the info. As far as I know the WW-version is not US only, but should match the version you have (you can check that in the settings/about tablet).
As far as I know WW stands for WorldWide and actually means US and (most of) Europe. There are special versions for Taiwan, Germany and Canada though...
I will try this later with my transformer (bought in switzerland) - i should work!
Regards, Thomas

Yeah I was thinking that. It comes with all the country files anyway.

I tried this a couple of days ago and it didn't work, turns out I unzipped the wrong file.
Unzip the .19 update to the root of your sdcard and reboot the transformer if it doesn't detect the update.
Now I haz root.

whitekidney said:
I tried this a couple of days ago and it didn't work, turns out I unzipped the wrong file.
Unzip the .19 update to the root of your sdcard and reboot the transformer if it doesn't detect the update.
Now I haz root.
Click to expand...
Click to collapse
So external or internal? And just reboot or recovery? Vol down+power then vol up? Thanks, sorry for the questions!

Hi there,
I unzipped to external and rebooted with the card in place. I didn't use recovery. The OS detected the update and offered to install. Just proceeded from there.
I mentioned the US update as the file is 8.6.6.19 not 8.6.5.19
Good luck.

I'm still getting the dreaded triangle when trying this fix, any suggestions?

Hi Samuel
Can you talk us through what you did and your setup? I'm no expert but hopefully we can find out what's awry.

Nice 1 m8. Do yo think this will work with B40 model? Where in leeds are you from? I in pudsey.

Should this work with the TF101G (B90 / DE / 8.6.6.10) too?
Gesendet von meinem HTC Desire mit Tapatalk

pjfriend said:
Hi there,
I unzipped to external and rebooted with the card in place. I didn't use recovery. The OS detected the update and offered to install. Just proceeded from there.
I mentioned the US update as the file is 8.6.6.19 not 8.6.5.19
Good luck.
Click to expand...
Click to collapse
But is it ok/safe? Guessing it is. Just popped up saying there is an update for me as well, going to give it a go now.
The honeycomb upgrading 'droid is so cool! I think its working fine!
If anyone could make a Uk one, that would be great. I am thinking the reason why this is working is because of the increase in firmware numbers, from x.x.5 to x.x.6.

Hi Seg2012
Only tried on mine until others can update to say it worked. You should be able to root with NVFlash though.
I'm from Morley but live nearer to Dewsbury now. Small world!

Going to flash this to my B90 US tablet, will report back-

This is great, worked perfectly! Now onto a custom rom! Revolver I think!

First off I downloaded the WW_epad-user-8.6.6.19.zip file. I placed this on the root directory of the micro SD card. Secondly I reboot my new baby using the power button and the down rocker of the volume button.I then pressed the up rocker to get into the recovery mode, now I only then get the green android with the yellow triangle with exclamation. My Asus tf is HTK7.WW.EPAD-8.6.521-20111216 any help would most appreciated.

I didn't use recovery. Just rebooted and the tab detected it. I clicked the triangle in the bar, it offered to update and went from there.
Sent from my GT-I9100 using xda premium

I didn't even need to reboot!
If you clear up the op with slightly clearer instructions this is sticky worthy. Helpful!

pjfriend said:
I didn't use recovery. Just rebooted and the tab detected it. I clicked the triangle in the bar, it offered to update and went from there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Not working here, I've an italian TF101g updated w/ 8.8.6.23, I've unzipeed the 8.6.6.19 firmware to the root of my microSD but I've got any update notification

pjfriend said:
Hi Seg2012
Only tried on mine until others can update to say it worked. You should be able to root with NVFlash though.
I'm from Morley but live nearer to Dewsbury now. Small world!
Click to expand...
Click to collapse
Cheers anyway m8. Ill give it a go shortly and post back.
Yeah it is a very small world. Lol
Seg

[HowTo] Restore Stock Recovery and Install .26 OTA Manually with Unlocked Bootloader

All credit goes to original posters- this information was compiled from a few different threads to make things easier.
Info came from the following threads:
http://forum.xda-developers.com/showthread.php?t=1803090
http://forum.xda-developers.com/showthread.php?t=1492887
** As always, this has risks. You could brick your device. Do this at your sole discretion. This worked just fine for me, but it might not work for everyone.
** What this does is replace TWRP with the stock recovery, enabling OTA updates to be applied again. It does NOT re-lock your bootloader. It also overwrites your /system image and build.prop with the original .22 image, which should enable the .26 update to be successful.
** This did NOT overwrite any of my settings or apps- that may not always be the case. It's best to expect that this will result in a factory reset, even though in my experience it didn't. Better to be prepared and pleasantly surprised.
** This assumes you installed TWRP or another recovery and need to revert to Stock recovery. Although I'd recommend running the full process anyway, as this ensures you have a fully stock /system partition, build.prop, etc. You can try skipping to step 10 if you're still on stock recovery.
1: Run a TWRP and/or Titanium backup, just in case. Grab everything including recovery if using TWRP.
1a: To be on the safe side, make sure you don't have any other update zips at the root of your external SD or internal storage.
2: Download the appropriate 9.4.5.22 file for your device from here:
3: Extract files from within zip
4: Extract files again from the extracted zip
5: Copy extracted "blob" file to root of folder of the removable Micro SD card or some other folder
6: Through ADB shell or Terminal Emulator, run the following: (May take from 5 to 20 minutes)
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
If copying the "blob" file to the SD card in the keyboard dock, use: dd if=/Removable/SD/blob of=/dev/block/mmcblk0p4
If copying it to the internal memory, use: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
7: Reboot only if the following is displayed (exact numbers may be different):
Code:
1068769+1 records in
1068769+1 records out
547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
Update process will automatically launch
8: Once booted up, root device by using debugfs root here
9: Do not make any other changes to build.prop or the /system directory
10: Download the appropriate dlpkgfile. The US version of the update can be downloaded here. I'll add any others as they are posted.
11: Use root explorer to copy "dlpkgfile" into /cache/ directory. Alternatively you could save the "dlpkgfile" in a microSD then open up a adb shell session.
Code:
su
cat /Removable/MicroSD/dlpkgfile > /cache/dlpkgfile
12: Create the file called "command" under /cache/recovery/ directory.
13: Write this statement in the file /cache/recovery/command
Code:
--update_package=/cache/dlpkgfile
14: Finally reboot into recovery kernel by shutting down first, then press and hold "Volume down" + "Power" once it vibrates release "Power" keep holding "Volume down" until there are some text shown on the boot logo screen. Then press "Volume up" within 5 seconds after releasing "Volume down". The update process should start... wait for it to complete. (This will take a little while, as the dalvik-cache will be rebuilt and your camera firmware will be updated. Once it completes, you should have the updated firmware installed on your tablet
15: Once the update is complete and you're at your home screen, you'll need to re-root. Just follow step 8 again.
16: Once rooted again, you can reinstall TWRP according to the original instructions, or just leave stock recovery on for now to avoid having to do this again once the next OTA comes out.

thanks for taking the risk and trying all this out. i just ran through all the steps and it worked perfectly. (i also had TWRP)

Really stupid question incoming, skip this post if you're in a cranky mood...
How can I tell if I'm running TWRP? I used the unlock tool from Asus then the debugfs root method from another thread in this sub. When I boot into recovery I get a red exclamation point over my surgery table android. It just says something along the lines of Android recovery, so I assume that's stock.

Headcase_Fargone said:
Really stupid question incoming, skip this post if you're in a cranky mood...
How can I tell if I'm running TWRP? I used the unlock tool from Asus then the debugfs root method from another thread in this sub. When I boot into recovery I get a red exclamation point over my surgery table android. It just says something along the lines of Android recovery, so I assume that's stock.
Click to expand...
Click to collapse
Yeah, it sounds like you're on standard recovery, and maybe there's an update file on your SD card or in cache that's failing.
If you follow the OP, it should enable you to update if you haven't yet. It'll pretty much do everything back to default .22 except relocking the bootloader.

Oh, as an afterthought, make sure you don't have any other update zips at the root of your external SD or internal storage, just to be safe.

followed all steps and seems to work. However, in the last step after I created the command file with root explorer, I booted into stock recovery and recovery screen is now just blinking with the Android icon. This does not seem correct! Any suggestions?

rsbuffalo said:
followed all steps and seems to work. However, in the last step after I created the command file with root explorer, I booted into stock recovery and recovery screen is now just blinking with the Android icon. This does not seem correct! Any suggestions?
Click to expand...
Click to collapse
How do you mean blinking? Does the android icon have a red triangle?

i think he may have missed the part where he needs to hit volume up after volume down.

Thanks eoh7678! I did have some update zips at root sdcard that seemed to be causing an issue. I deleted the files and uninstalled busybox. Then I redid the command file. Update was successful!!! About tablet now shows IML74K.US_epad-9.4.5.26-20120720.

Nice work. I was not aware you could go back to stock recovery. I may give this a go. I'm really blown away that somebody hasn't released a flashable zip that is custom stock ready yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

newellj79 said:
Nice work. I was not aware you could go back to stock recovery. I may give this a go. I'm really blown away that somebody hasn't released a flashable zip that is custom stock ready yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I actually have one mostly ready to go, according to what I've read, but to be honest, I've only ever made update zips for samsung or HTC phones. I've never tried this whole blob thing. TBH, I'm scared to death to try flashing my own creation.

Thank you for posting the howto (you saved me from having to write my method) I did everything from my TF700 using terminal and remote explorer to get recovery reverted and .26 OTA installed.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?

newellj79 said:
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
Click to expand...
Click to collapse
I haven't tried the manual update with this one, as I received it OTA before this one was posted, but it erased my su. Happily RootKeeper preserved it.

newellj79 said:
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
Click to expand...
Click to collapse
For me, at least, restoring .22 from the blob removed su. Probably rootkeeper would have solved, but honestly, I figured the safest bet was just to reroot between to make it easier and less prone to problems.

eoh7678 said:
For me, at least, restoring .22 from the blob removed su. Probably rootkeeper would have solved, but honestly, I figured the safest bet was just to reroot between to make it easier and less prone to problems.
Click to expand...
Click to collapse
Kewl. Just curious. Almost done.
Edit... worked great. Thanks!

Having an issue.... Once i move dlpkgfile to cache, make the command file, and reboot to recovery i just get the android with the red triangle. Also once it reboots and i check the cache folder the command file is gone. So at the moment im stuck on 22
Sent from my unlocked and rooted TF700T using the XDA Premium App

cctaylor410 said:
Having an issue.... Once i move dlpkgfile to cache, make the command file, and reboot to recovery i just get the android with the red triangle. Also once it reboots and i check the cache folder the command file is gone. So at the moment im stuck on 22
Sent from my unlocked and rooted TF700T using the XDA Premium App
Click to expand...
Click to collapse
I was having the same problem. My issue was when I downloaded the dlpkgfile a .bin extension was added to the file name. Make sure there is no extension on the filename.

DroidEris1981 said:
I was having the same problem. My issue was when I downloaded the dlpkgfile a .bin extension was added to the file name. Make sure there is no extension on the filename.
Click to expand...
Click to collapse
Im mildly retarded cause the file was 0kb lol. Re-downloading and trying again
EDIT: every copy method i try dlpkgfile ends up as 0kb, not sure what is going on. Using root explorer and terminal fail.
Sent from my unlocked and rooted TF700T using the XDA Premium App

cctaylor410 said:
Im mildly retarded cause the file was 0kb lol. Re-downloading and trying again
EDIT: every copy method i try dlpkgfile ends up as 0kb, not sure what is going on. Using root explorer and terminal fail.
Sent from my unlocked and rooted TF700T using the XDA Premium App
Click to expand...
Click to collapse
I used ES File Explorer (make sure to check the options in settings to tell it you have a rooted phone) to do everything (including creating the file) and it worked great. ES File Explorer is *awesome* - check it out.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Just picked up a sidekick 4G. Need to know what to do.

I recently sold my galaxy note for 400 but the kid only had 375 but gave me his sidekick as well.
And I want to know what i need to do in order to instal Glorious Overdose or w/e.
What exactly should I do? Do i need to root it first? Or something else?
Please give me a nice list of what exactly I need to do , and in what order.
Also any recommendations for what to instal.
Thank you.

antisouless said:
I recently sold my galaxy note for 400 but the kid only had 375 but gave me his sidekick as well.
And I want to know what i need to do in order to instal Glorious Overdose or w/e.
What exactly should I do? Do i need to root it first? Or something else?
Please give me a nice list of what exactly I need to do , and in what order.
Also any recommendations for what to instal.
Thank you.
Click to expand...
Click to collapse
You need root to install a custom ROM in all phones. This post might be helpful:
eMJaaay said:
Firstly you need root. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery. In clockworkmod recovery, there are many options, one of them being mounts and storages. Going on to that option will bring up your mounts and storages, where the most important one you need to check is SYSTEM which should always say UNMOUNT. If it says MOUNT SYSTEM, click on it and it should say UNMOUNT SYSTEM.
For ROOT, use SuperOneClick. You can download the file here -> link (scroll to the end of the post). I used version 2.2 and everything worked fine. Look at this guide by ayoteddy for more information -> link. You need to choose psneuter as your exploit. Windows detects this app as a virus so make sure all your anti-virus / firewall software is off. If it doesn't work, try and try again. Change USB cables and try some more!
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
I recently rooted and got custom recovery and installed a fresh ROM (GOV 3.2) and all I can say is, be patient and follow everything step by step and you'll be fine. I'll also advise you to partition your SD card BEFORE installing a ROM just to be safe, because I've heard some people having issues with it. I did it and had no problem, but again I don't know if this is a placebo or actually helped. After installation / rebooting, etc ... don't touch your phone for a couple of minutes. If you reply in the appropriate threads, I'm sure someone will help you out if it doesn't work.
Click to expand...
Click to collapse

Ok I'm having a little trouble.
http://forum.xda-developers.com/showthread.php?t=1275116
I'm following this. I reached the part where i need to turn off my phone and go into recovery mode.
But when i choose to reinstall. It says E: signature verification failed .
Any help?

antisouless said:
Ok I'm having a little trouble.
http://forum.xda-developers.com/showthread.php?t=1275116
I'm following this. I reached the part where i need to turn off my phone and go into recovery mode.
But when i choose to reinstall. It says E: signature verification failed .
Any help?
Click to expand...
Click to collapse
Did you put the recovery in the system/bin?
And the update in the root of your SD?

antisouless said:
Ok I'm having a little trouble.
http://forum.xda-developers.com/showthread.php?t=1275116
I'm following this. I reached the part where i need to turn off my phone and go into recovery mode.
But when i choose to reinstall. It says E: signature verification failed .
Any help?
Click to expand...
Click to collapse
When it gives that message it usually means you haven't correctly pushed recovery to your /system. You can only push recovery after you have successfully rooted (get a free root checking app from the Play Store to check). Once you've rooted, you need to push the recovery file you get after you extract the recovery zip from the download links I've sent. You can move it from the root of your SD card to your phone using adb or root apps such as root explorer (very simple, but its a paid app). You also need to download the update.zip file from the link I sent (same place you downloaded the recovery file) and put it at the root of your SD card (don't unzip it). That should work!

Ok thanks . I'm going to try this now.