Database Info

[Q] Downgrade

Is there a way to downgrade from .13 to 8.2.3.9 to get root? if so can you guys direct me where to get the files and how to run the downgrade?
Thanks in advance.

I found the update, but don't know how to run the update from the SD card. I tried rebooting and holding down the volume down key, but that does't appear to be reading from the SD card.
Do I have to name the update a certain name? Is there a key combination I need to press to restore it from SD? The update said look in the manual, but I don't see anything in there.

Sorry for the multiple replies. After it booted up I had a notification saying it found the update file and if I would like to run it. I answered yes.

kingdruid said:
Sorry for the multiple replies. After it booted up I had a notification saying it found the update file and if I would like to run it. I answered yes.
Click to expand...
Click to collapse
Extract the 8.2.3.9 zip file to the root of the microsd card on the pc. This should create a folder called ASUS with the update in there. Then insert it while the tablet is running. Then you will see an exclamation notification on the bottom right or the task bar. Tap that and follow the instructions.

Bump! I am looking for the 8.2.3.9 file also! I cannot seem to find it anywhere. That or has any new methods been released to root .13 yet? Just got my transformer and I am anxious to achieve root!

[Q] Downgrade from 8.6.6.23 to 8.6.6.19 or 8.6.6.15

Any way to downgrade?
Serial No. BAOKAS...., SBKv3, Model TF101G
Other tutorials in the forum are outdated.
Thx a lot.

Found a way, so it's solved.

why you want downgrade?

Furzbirre said:
Found a way, so it's solved.
Click to expand...
Click to collapse
Post a link? Thanks

Maybe they fixed the root exploit in the new ota and he just got hes tf??
Sent from my tf Enigmatic V1 Alpha 1.59Ghz Panda.test

Furzbirre said:
Found a way, so it's solved.
Click to expand...
Click to collapse
Tell us please.

Would like to know also - why keep secret ?

Furzbirre said:
Found a way, so it's solved.
Click to expand...
Click to collapse
Can you share some link or explanation, please??

LuisMiguelVD said:
Can you share some link or explanation, please??
Click to expand...
Click to collapse
Try here
http://forum.xda-developers.com/showpost.php?p=20468602&postcount=43

Thanks, I'm trying this immediatly !

Furzbirre said:
Found a way, so it's solved.
Click to expand...
Click to collapse
Hey Furzbirre,
I tried everything here - no luck. Could you please tell me what you exactly did?
I have a 8.6.6.23 / BA0 / TF101G (seems pretty the same version you have).
Thank you very much, Thomas
PS: What I tried already:
- downgrade with 8.6.6.19 version floating around on multiupload
- unzipped the epad...zip from the download
- put it on microsd, internal sd, renamed it to EP101_SDUPDATE.zip
- rebooted with vol-down/power, then vol-up: android update started
- yellow sign: no update possible - still 8.6.6.23
-> what have you done diffrently?

baseballfanz said:
Try here
http://forum.xda-developers.com/showpost.php?p=20468602&postcount=43
Click to expand...
Click to collapse
I try downgrade my TF101G serial BAO... and dont work. In recovery mode appears a yellow triangle when try load a EP101_SDUPDATE.zip

Nachoroot
Use Nachoroot, it works, no downgrade necessary
http://forum.xda-developers.com/showthread.php?t=1427838

Hello,
I have the same TF101g than tsch with 8.6.6.23 ROM.
I used NachoRoot and I have successfully rooted my TF101G.
But now I don't know how to install ClockWork Mode ?

See the link in my signature for assistance with CWM.

in some thread i found this method: after you unzip file, you make name one copy of this file ""EP101_SDUPDATE"" then you make another copy of this same file and name ""WW_epad-user-8.6.6.19"" so on the end you have 2 same files with diferent names, now you copy this 2 files to micro sd card
and another copy 2 files to tablet sdcard, root folder
after going to recovery mode is installing with no problem, just done 2 days ago
and dont forget to remove this files after instalation and reboot
i hope is gonna work for you ether

Yeah, just don't bother putting them on the internal memory, it doesn't search the root of that drive, it checks the system/cache (I think) folder for official Asus updates, stick with keeping it on external memory, especially if unrooting because if you place these files on your internal and return it if someone else roots the device and finds these files it is a smoking gun that it has been rooted in the past. Just in case...keep it on your external (and that might have been my post you read that in, I have found that the EP101_SDUPDATE file is not even necessary )

luna_c666 said:
See the link in my signature for assistance with CWM.
Click to expand...
Click to collapse
Yes thank you. I found the RecoveryInstaller.
All is ok now.
Regards.

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

[Q] Difficulting Rooting

So I just got my TF101 and I am also relatively new to Android. I am on version 3.2.1, Kernel 2.6.36.3 ([email protected] #1), Build number HTK75.US_epad-8.6.5.13, and my Serial number starts with B80KA.
Since I am on 8.6.5.13, I can't use Razorclaw, which is unfortunate.
I have tried using the Transformer Root Toolkit v7.1, but I can not get it to recognize the device when it is in APX mode so I am stuck there.
I also looked at this thread and followed those steps to no avail. Should I grab the OTA update and try those steps again? Or is there an easier way?
Thanks!
Edit: Fixed Serial.

First of wrong serial number.
Use the serial number on the bottom of your tablet or the back of your box.
Any how try this
http://forum.xda-developers.com/showthread.php?p=20809986

The link you posted is almost identical to the one I did. So that suggests that I should just grab the OTA update and then root it?

SimonSaysBleed said:
The link you posted is almost identical to the one I did. So that suggests that I should just grab the OTA update and then root it?
Click to expand...
Click to collapse
if you grab the OTA you'll get 8.6.5.21 which definitely is NOT rootable with Razorclaw.
seems like the two methods is almost similar but slight different, i would at least try both to see which one work if any.
Sent from my Transformer TF101 using Tapatalk

You should search for OTA .19, I think it was posted around here somewhere or maybe via google, so you can update to .19 and use Razorclaw's tool.

Well I have 8.6.6.19 (in the form of UpdateLauncher_WW_epaduser8_6_6_19.zip), so does it matter that it is the one for the TF101G and not the TF101?
Also, what exactly do I do with that zip file to install the update? I tried booting into recovery but that didn't do much.

SimonSaysBleed said:
Well I have 8.6.6.19 (in the form of UpdateLauncher_WW_epaduser8_6_6_19.zip), so does it matter that it is the one for the TF101G and not the TF101?
Also, what exactly do I do with that zip file to install the update? I tried booting into recovery but that didn't do much.
Click to expand...
Click to collapse
Do exactly like this post
http://forum.xda-developers.com/showpost.php?p=20809986&postcount=1

baseballfanz said:
Do exactly like this post
http://forum.xda-developers.com/showpost.php?p=20809986&postcount=1
Click to expand...
Click to collapse
But now I can't get into recovery mode. I could get into it yesterday but it didn't work, but now I can't get in at all...

baseballfanz said:
Do exactly like this post
http://forum.xda-developers.com/showpost.php?p=20809986&postcount=1
Click to expand...
Click to collapse
I try this and not works
I have a TF101G serial BAO... with firmware 8.6.6.23. When I enter in recovery mode, after a few seconds appears a yellow triangle (yellow warning) inside android body and don't install nothing...
Any sugestion?

dinotav said:
I try this and not works
I have a TF101G serial BAO... with firmware 8.6.6.23. When I enter in recovery mode, paste a few seconds appears a yellow triangle (yellow warning) inside android body and don't install nothing...
Any sugestion?
Click to expand...
Click to collapse
Did you extract the content of the zip file or did you just use the file you download?

baseballfanz said:
Did you extract the content of the zip file or did you just use the file you download?
Click to expand...
Click to collapse
1) Extract and copy "WW_epad-user-8.6.6.19.zip" to my microSd card
2) copy the same file with the name "EP101_SDUPATED.zip"
3) copy this 2 files for internal sdcard of my TF101G
4) Enter in recovery mode. Power On + Vol Down, then Vol Up
I think that i make the things right....

Hey I finally got it to boot into recovery...and it worked! And I'm rooted! Woohoo, thanks everyone.
Now my last question is hopefully more simple. What do I do since my TF downloaded the OTA update? Is there a way to permanently postpone the update install? Will it go away if I install a custom ROM?

SimonSaysBleed said:
Hey I finally got it to boot into recovery...and it worked! And I'm rooted! Woohoo, thanks everyone.
Now my last question is hopefully more simple. What do I do since my TF downloaded the OTA update? Is there a way to permanently postpone the update install? Will it go away if I install a custom ROM?
Click to expand...
Click to collapse
If you install a custom ROM it will go away. Alternatively you can install the latest stock ROM with root by installing this "custom" stock+root ROM. The system will be left exactly like you had somehow rooted the latest stock ROM.

You could flash a rooted stock rom or you can go into
Settings>Applications>Manage application>All>DMClient>Clear data.
Could also use Titanium Backup to freeze DMClient
---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------
dinotav said:
1) Extract and copy "WW_epad-user-8.6.6.19.zip" to my microSd card
2) copy the same file with the name "EP101_SDUPATED.zip"
3) copy this 2 files for internal sdcard of my TF101G
4) Enter in recovery mode. Power On + Vol Down, then Vol Up
I think that i make the things right....
Click to expand...
Click to collapse
Double check you files and make sure it's not filename.zip.zip

baseballfanz said:
You could flash a rooted stock rom or you can go into
Settings>Applications>Manage application>All>DMClient>Clear data.
Could also use Titanium Backup to freeze DMClient
---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------
Double check you files and make sure it's not filename.zip.zip
Click to expand...
Click to collapse
Confirmed that the filename have only one ".zip"
My microSD card is FAT32 format... Have to be in NTFS?

dinotav said:
Confirmed that the filename have only one ".zip"
My microSD card is FAT32 format... Have to be in NTFS?
Click to expand...
Click to collapse
FAT32 is correct format.
Make sure it's on the root of the sd card and not in any folder
File name:
Code:
WW_epad-user-8.6.6.19.zip
EP101_SDUPATED.zip
Maybe try a different sd card if you have one.
Also just double checking but when entering recovery,
are you waiting to see the words at the top left of the screen prompting
you before pushing Vol up.

baseballfanz said:
FAT32 is correct format.
Make sure it's on the root of the sd card and not in any folder
File name:
Code:
WW_epad-user-8.6.6.19.zip
EP101_SDUPATED.zip
Maybe try a different sd card if you have one.
Also just double checking but when entering recovery,
are you waiting to see the words at the top left of the screen prompting
you before pushing Vol up.
Click to expand...
Click to collapse
Ok, i gona try with a different sd card. Yes i know, i see the words, then I push Vol up to load boot.
Remember that I have a TF101G and not TF101.

dinotav said:
Ok, i gona try with a different sd card. Yes i know, i see the words, then I push Vol up to load boot.
Remember that I have a TF101G and not TF101.
Click to expand...
Click to collapse
Yes the files that everyone is using is actually made for the TF101G
but it's also working on the TF101.

baseballfanz said:
Yes the files that everyone is using is actually made for the TF101G
but it's also working on the TF101.
Click to expand...
Click to collapse
I tried a different sd card but give me the same error. I saw the Android guy with some gears turning but 10/15 seconds later appears a yellow triangle

Hi dinotav,
I don't think we (those with TF101G/8.6.6.23) have any options at this point.
dinotav said:
I tried a different sd card but give me the same error. I saw the Android guy with some gears turning but 10/15 seconds later appears a yellow triangle
Click to expand...
Click to collapse

How to update to JB and keep root (Locked Bootloader)

Ok, From now on if i see people asking how to update / how to keep root im going to link you to this thread, im tired of answering it.
This works if you are on STOCK RECOVERY. If you are unlocked there are lots of other options for you (such as flashing a rooted kernel) so go to development and find that. Since im not unlocked i had to do it the hard way. This method works if your OTA updates are screwed up. If you HAVE OTA updates you can just use OTA rootkeeper to backup and disable root, make sure all stock apps are restored, and proceed with root.
Note for the updater: The OTA updater is a DIFFERENCE updater, if files are missing or different versions the update will fail. Best practices say to update sequentially, never skip an update. It might not cause problems now but could cause problems in the future.
If your OTA updates have failed or for whatever reason you can not get OTA's, you have a LOCKED bootloader, or for whatever reason want to manually update and keep root then this guide is for you. Also please note the process for going from .16 to .18 is the same as going from .30 to .16.
First: Make sure you have all stock apps restored, no custom build.prop, etc.
If your not sure, wipe the tablet and reinstall. Better safe than sorry.
To reset the tablet if you dont have stock apps:
Determine which version you are running. For me it was .30WW
Go to www.asus.com and download the firmware for your version
plug your tablet into the usb on your computer, unzip the firmware and put it in the root of your tablet (Dont use USB memory sticks or SD cards, just transfer it directly)
restart your tablet, it SHOULD load the file and go about resetting the tablet to stock.
If that does not work, try starting the tablet holding power and volume down, on the splash screen press volume up and reset the tablet that way.
Once your tablet is returned to stock you can proceed.
Click to expand...
Click to collapse
Make sure you are ROOTED. Use whatever method works for you.
Now would be a good time to make sure superuser is updated, mine was old so a quick update on the market and its all good.
Use OTA Rootkeeper to backup root
Download the DLPKG file apropriate for your version.
If you want to update to JB you must have .30 installed and download the .16 file, WW or US, depending on your region. Other packages are provided for convenience (This method can be used to spoof the OTA update to any version as long as you have the file)
DLPKG for .26 WW HERE
DLPKG for .30 WW HERE
DLPKG for .16 WW HERE or HERE or HERE
DLPKG for .16 US HERE or HERE
DLPKG for .18 WW HERE or HERE
DLPKG for .18 US HERE or HERE
(Make sure you only take the file for the version you want to update to, only one step at a time, so if you are on .30 WW you need .16WW before you can do .18WW)
DLPKG for US .20 HERE
DLPKG for WW .20 HERE
DLPKG for US .23 HERE or HERE or HERE or HERE
DLPKG for WW .23 HERE
DLPKG for .25 WW HERE
You will also need the command file HERE or HERE
Transfer the files to your tablet using the USB cable.
If you use a USB memory stick or SD card make sure its formatted FAT32.
Please note there have been reported problems with people using USB memory sticks or SD cards, often the files fail. I have had best success using the USB cable provided with my tablet and directly transferring the file. YMMV.
Click to expand...
Click to collapse
Once the files are on the tablet use Root Explorer or your favorite root file browser to move the two files
(NOT THE STOCK FILE BROWSER IT CANT SEE THE ROOT DIRECTORY)
"command" goes to /cache/recovery
"dlpkgfile" goes to /cache
Make sure the files are named exactly as shown above. No capitals, no file extensions, etc.
Make sure the permissions for both files are changed to RW-R-R for both.
Note: There has been a little confusion about "root directory" so i will explain a little further. The root directory is generally protected. You will have to be rooted (by definition, having root access, kind of like administrator access in windows) and use a file browser like root explorer. The stock file browser only lets you see a few specific areas and will not let you access the root directory of the tablet. Root explorer will also let you modify permissions which the stock browser will not let you do. Im sure there are other browser applications that work equally well as root explorer, thats just the one i have had success with. As always, Your Milage May Vary.
Click to expand...
Click to collapse
Go into OTA Rootkeeper and TEMP UNROOT.
Shut down the tablet. Remove the USB cord. Remove any USB memory sticks. Eject your Micro SD card. UNdock the tablet. Lets not let anything go to chance.
Press and hold both the power and volume down buttons (volume down is closest to the power button in case you forgot like me)
Soon as the splash screen comes up you should see some text on the left side, release the power and volume down buttons and press volume up.
Now just sit back and wait, this can take a while. I got myself a snack and took this time to stretch a little.
Once your all booted up you should be running JellyBean. Open OTA Rootkeeper and restore root.
Please note i did not come up with the steps in this guide. I did not originate the files. I am nowhere near smart enough to do all this on my own. I meerly collected the information and links to files and pieced it all together. I wrote this so even my father could follow these instructions so hopefully you all succeed! If something needs clarification please let me know.
- Edit -
Added notes on restoring tablet to stock.
- Edit -
Added .18 links. Thanks to xcal321 for providing them.
- Edit -
Cleaned up the guide a little. Hopefully its less wordy and easier to follow.
- Edit -
Added links to my personal google drive for nearly all the files, should have no problem for overseas users with limited access to mediafire
- Edit -
Sorry it took so long, added files for .20 US and WW. Will copy them to my personal Gdrive when i have more time.
- Edit -
Still alive, added .25 WW. Nearly all the files are uploaded to my personal google docs account so if something goes screwy let me know via PM

That is very helpfull !! Thanks for that !! Just one question: What about if I downgrade to .30 with clean system, root my device, update superuser app, then use OTA Rootkeeper to backup my root, next Temp unroot via OTA Rootkeeper and use upgrade to JB with OTA (not using files that you put above )?? It still works, any ideas ??
Regards
Doncieslacco

doncieslacco said:
That is very helpfull !! Thanks for that !! Just one question: What about if I downgrade to .30 with clean system, root my device, update superuser app, then use OTA Rootkeeper to backup my root, next Temp unroot via OTA Rootkeeper and use upgrade to JB with OTA (not using files that you put above )?? It still works, any ideas ??
Regards
Doncieslacco
Click to expand...
Click to collapse
If OTA works for you after that then use OTA. For a large portion of us OTA did not want to work so these are the steps i used. Essentially its the same thing, OTA downloads the same files and puts them in the directories mentioned. Just make sure you do the temp unroot before updating as forgetting to do that step has lost some people root.

This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.

Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?

Syn010 said:
This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.
Click to expand...
Click to collapse
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
john85D said:
Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?
Click to expand...
Click to collapse
are you unlock or locked? did you try to upgrade from .30 to JB?

buhohitr said:
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
are you unlock or locked? did you try to upgrade from .30 to JB?
Click to expand...
Click to collapse
I'm unlocked and started the process on. 30 rooted. I did downgrade from JB though and wanted to be rooted again. Should I try to upgrade to JB manually? How should it update to JB, OTA download?

buhohitr said:
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
Click to expand...
Click to collapse
I used a USB cable 2.0 to transfer the files directly to tablet. Also, the cache folder is created on the root level of the tablet right, because originally I never had a cache folder on the tablet at the root level. thanks and cheers.

Here's what I did, and it worked beautifully.
I had unlocked with the guide, rooted .30, ran OTA root keeper, downloaded the JB file from Asus, flashed it in twrp, never lost root
Sent from my Galaxy Nexus using xda premium

Jimmah555 said:
Here's what I did, and it worked beautifully.
I had unlocked with the guide, rooted .30, ran OTA root keeper, downloaded the JB file from Asus, flashed it in twrp, never lost root
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
TWRP implies unlocked, this method is for locked bootloaders.
If you are still getting the dead android try restoring the tablet to factory condition before proceeding. If you have any frozen apps, if you removed any stock apps, if you have a modified build.prop, etc. it can cause the update to fail.
i will update OP with instructions to return to stock.

Syn010 said:
This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.
Click to expand...
Click to collapse
Windows security and linux permissions are two VERY different things.
Use something like root explorer to modify the permissions of the files once they are on the tablet. Once you transfer the files to your SD card or even via USB to the tablet the permissions get changed to RW-RW-RW or similar. As far as i know you can not do this in windows.

Syn010 said:
I used a USB cable 2.0 to transfer the files directly to tablet. Also, the cache folder is created on the root level of the tablet right, because originally I never had a cache folder on the tablet at the root level. thanks and cheers.
Click to expand...
Click to collapse
Use an application like root explorer. Regular file explorers can not usually see the root directory of the tablet. If you are just using the stock file browser it will not work.

pileot said:
First: Make sure you have all stock apps restored, no custom build.prop, etc.
If your not sure, wipe the tablet and reinstall. Better safe than sorry.
Click to expand...
Click to collapse
Thanks for the OP. I am having trouble getting the JB OTA.
I am running rooted and locked at .30 with some minor tweaks using Titanium backup. Those tweaks are removing ASUS and Google bloat app. In order to get JB OTA, do I have to reinstall the bloat apps or reflash .30? Does all the stupid bloat have to be there for OTA to occur? If so, I hate that.

john85D said:
Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?
Click to expand...
Click to collapse
I've got the same...kind of pissed. Am I just SOL without root now?
Edit: Nevermind...just ran through the whole root process again and got it back.

quartercirclebak said:
I've got the same...kind of pissed. Am I just SOL without root now?
Edit: Nevermind...just ran through the whole root process again and got it back.
Click to expand...
Click to collapse
What did you use to gain root again? As far as I know, rebuffs does not work with JB. Or are you unlocked?

everytime i do, i get back to .30 and when i check /cache
dlpkgfile still there with rw-r-r
but command in /cache/recovery/ disappear
what i mistaken?

-lukin- said:
Does all the stupid bloat have to be there for OTA to occur?
Click to expand...
Click to collapse
Yes. Since the OTA is a "difference file patcher", the original files need to be where they are expected to be, otherwise the instructions as to which areas of which files should be patched with which values will be invalid. There is no way a difference file patcher can operate if the files are missing or modified - it's in the nature of the beast.
That's why the only option for people who have modified their /system partition is to reflash the entire /system partition (ie. a full update, not one that relies on what is already there).
The reason for using a difference file patcher is that the update will be much smaller if it only contains the differences from the existing setup instead of a completely new file. The downside is that the existing contents needs to be present and unmodified.

HeartWare42 said:
Yes. Since the OTA is a "difference file patcher", the original files need to be where they are expected to be, otherwise the instructions as to which areas of which files should be patched with which values will be invalid. There is no way a difference file patcher can operate if the files are missing or modified - it's in the nature of the beast.
That's why the only option for people who have modified their /system partition is to reflash the entire /system partition (ie. a full update, not one that relies on what is already there).
The reason for using a difference file patcher is that the update will be much smaller if it only contains the differences from the existing setup instead of a completely new file. The downside is that the existing contents needs to be present and unmodified.
Click to expand...
Click to collapse
Makes sense, thanks for the the concise explanation.

Thank you so very much. kept trying to root jelly bean before, and ended up bricking tab somehow. thankfully best buy exchanged under factory defect cause after bricking, it got super HOT. I'll donate some adult beverage money when i get paid.
thank you again.

Hello !
First of all, thank you for your post.
I have a question "Yes or No". I translated your method (thank you again) in french for the french users, and I told them that they could unlock the bootloader once the firmware is back to ICS (.30). I am not sure about it, I would like you to confirm this ?
Then the method would be :
Downgrade to ICS (v9.4.5.30 WW)
Root with RootDebugfs.bat
Unlock Bootloader
Temp unroot with OTARootKeeper
Upgrade to JB (v10.4.4.16 WW) with OTA
Restore root with OTARootKeeper​