Database Info

[GUIDE] Official [unroot] guide here

I have seen a lot of unfinished info on UNROOTING so rather than see a bunch of people stuck like I was last night I thought I would toss a little guide together for everyone.
I take no credit for any guides I post just pitching in, if I help you CLICK me a THANKS!
download the asus firmware from here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
extract the blob from the zip file and put it in your adb folder located at something like:
AndroidSDK/platform-tools/
as you did to root the device.
open cmd promt window type the following and return after each.
\cd
\cd AndroidSDK\platform-tools\
adb devices
*adb your device make sure it is hooked up and id'ing your transformer.*
adb push blob /data/local
adb shell
*at the # type the following*
dd if=/data/local/blob of=/dev/block/mmcblk0p4
*wait a few mins to be safe*
now reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob” file. this will remove the clockwork recovery and put your tablet into BOOTLOOP this is ok.
----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Now that your tablet is stuck in a boot loop, put on the root of the micro sd card on your computer-> the update normally found in the asus/update/ folder from the firmware zip you download from asus. I used the .9 US update and it worked fine, you must then rename it to EP101_SDUPDATE.zip make sure you leave it a zip dont change the extension AND->make sure it is on the root of the card.
Now put your card in your transformer, hold the down volume and power till it prompts you in the upper left about wiping or booting to recovery**> let go and push up on the volume, which will load the factory recovery android with a box and a loading bar *** IF IT IS STILL CLOCKWORK RECOVERY THEN YOU MISSED SOMETHING START OVER DO NOT CONTINUE***> it will begin to flash the update do not bother it turn it off or anything else will take up to 10 mins to complete. it will restart and you will see the bar load again on boot up then it will boot to the asus logo and then to the homescreen and your good.
-Ian

Faved for later use when INeed to RMA
Sent from my Transformer TF101

I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.

Thanks for this. I have been holding off trying to root my Tablet until I had some clear indication that there would be a "way back".
I will PM you a link to V8.2.3.9 US Firmware as soon as it's done uploading to MegaUpload (Aborted as someone beat me to it)

I haven't found a need to root my TF yet as all I need for it is running pretty smoothly.
My phone on the other hand gets flashed with a new ROM every few days.
Great to know that I can go back if I do root one day. Thx

I get to this point...
ianandamy said:
...let go and push up on the volume, which will load the factory recovery android with a box and a loading bar...
Click to expand...
Click to collapse
See the box with a loading bar for about three seconds then the screen switches to the image of the android robot logo and an exclamation point within a triangle. I think its because I accidentally wiped my data last night when I was trying to fix the boot loop issue. I'm about to give up on this one...
Edit: Hey it works great, just make sure you don't add a .zip extension to the E101_SDUPDATE rename.

Big Thanks to ianandamy this works great! Got it up and running. The only problem is that I am being prompted to enter a password in order to get it to the homescreen...The second problem is that I never had a security password in order to access the tablet. I have a feeling this has to do with it being rooted by the previous owner before I purchased the tablet. Would the settings return to how he customized it pre-root? If so the password the tablet is asking for would be the one he set before I ever owned the tablet. How do I get around this?!

worked great, and like the profile pic

Added to ultimate thread. Nice job.

isdnmatt said:
I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.
Click to expand...
Click to collapse
Can someone host it and pm me a link to post

It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip

isdnmatt said:
It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
Click to expand...
Click to collapse
GREAT!
I've extrapolated the WW version with that http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_WW_epad_user_8239.zip

This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
I'd do it, but I'm lame and don't have a linux box or VM setup .. that and I sold my eeePad to pay for vet bills... something about 'daddy save the puppy' is haunting me now.
P.S. Thanks for the info, just trying to save time if this is possible

sirmx said:
This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
Click to expand...
Click to collapse
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.

Segnaro said:
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.
Click to expand...
Click to collapse
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!

StirCwazy said:
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!
Click to expand...
Click to collapse
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.

Segnaro said:
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.
Click to expand...
Click to collapse
Sorry to be a bit pesky here, but just want to be real sure: Based on ROM work I've done on my Android phone, unrooting is not the same as going back to a stock ROM. Actually the reverse is true: you can apply a stock ROM< and it will effectively unroot the phone.
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?

ewingr said:
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?
Click to expand...
Click to collapse
Yes, and after a factory reset it would be like when you just took it out of the box.

Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147

b1ackplague said:
Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147
Click to expand...
Click to collapse
Yes, I went from 3.1 direct to .9 without any issue.

[Q] Can't receive update to 8.4.4.11

I rooted my transformer using the pure root method in the development transformer forums for devices that already received 3.1. People have said that they receive their update and unroots their device, but I haven't even received the FOTA. I only rooted my device; without clockwork or a custom rom. I did delete some pre installed programs (bloatware) with titanium backup but I re installed them. Not sure if the damage has been done but I want someone to confirm if that can be the issue and how do I go about to properly reinstall the bloatware.

I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....

Danny80y said:
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Click to expand...
Click to collapse
I am having the exact same problem and a lot of people will. Once you root and try to unroot it appears you cannot receive anymore OTA or make them work for that matter. I have found how to get the notification telling me that the .11 update is available for me. (Place the update file in sdcard/asus/update/) and then rename it US_epad-user-8.4.4.11.zip and rebooting. After this you can choose to make the update but it will not work. It will just go to the stock recovery with the android and the exclamation after a one second loading appearing that it will work. After you turn it off and back on it will tell you (System Update Failed Error (12) )Still trying to figure out why it is not accepting the update.

You can get the update in the "Just got an OTA update" thread.

Thank you for that valuable information. It worked like a charm. Now I just need the original update for the dock.
Sent from my Nexus S 4G using Tapatalk

...................

martijua said:
You can get the update in the "Just got an OTA update" thread.
Click to expand...
Click to collapse
I guess I'll have to manually install. Let's see how it turns out...

for just patiently wait for FOTA or rooted repack... The improvements are not HUGE.

TheIneffable said:
I guess I'll have to manually install. Let's see how it turns out...
Click to expand...
Click to collapse
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms

TheIneffable said:
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
Click to expand...
Click to collapse
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk

Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Guess I'll wait for a rooted 3.2 to come out.

You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.

It's weird because, I downloaded the txt, and rename it, placed it on the root of the so card and the update passed flawlessly.
Sent from my Transformer TF101 using Tapatalk

Fixter said:
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
"Then press volume up when you see the text on the top left of the screen"
I did it just how the instructions stated but I never saw the text on the top left of my screen. It just boots up normally with stock boot animations. The update notification is not present either. I guess I'll try and see if not renaming it might help. Even though I don't think leaving the file extension to just "file" will help. I'll try...

Digiguest said:
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
Click to expand...
Click to collapse
hmm...Probably because you extracted the .zip to the SD card. It just stated to move the .zip to the sd card. Maybe extracting might work.

None of the methods worked. Guess I'll be installing roms. I guess when I deleted some of the preinstalled apps, my device became disqualified for any sort of updates.

I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?

superevilllama said:
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Click to expand...
Click to collapse
Read the first post of this thread to properly flash the update when renamed to ep101_sdupdate.zip:
http://forum.xda-developers.com/showthread.php?t=1171116

Carl LaFong said:
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
Click to expand...
Click to collapse
haha. Who's *****ing? My transformer still works great. Just wanted to diagnose why I wasn't getting an update so I can be more informed about it and see if I should just stick to installing roms or unroot.

Right. That says exactly what I just said, and did. Anyway.. I eventually got it to work. I had to go compeletly back to stock as apparently deleting stuff from the stock rom altered it enough that the update didn't see it as the same rom.
Tried to root after and got froze up at the boot screen like everyone else. Been playing with this too long. Understanding that we risk messing up our devices by rooting and such.. other issues that are in complete control of Asus such as build quality... IE light bleed, bezel issues, freezing, touch screen not sensing touch are making me rethink this product. Sigh. Sucks too because the idea is awesome. Just wish the build quality was there.

Unbricked TF101, but no Updates?

Hey,
My TF101 got bricked by a simple reboot - "encryption unsuccessful" splash screen.
I used the nvflash-package from the devel-section "[Tool] Nvflash unbricking released!" for getting back a fresh, clean install of 3.2.1, which seems to work well.
Sadly, no OTA-Update to ICS is found and no microSD-Update is recognized.
Wipe, another cold-boot tried.
Q:
nvflash repartition and format - thus there couldn't be hassle with my old "broken" Android, right?
Q2:Anyone has an idea why updates dont work? Within the thread mentioned above I found some posts about updates which where recognized.
Searched a lot but nothing specific to the nvflash image solution...
BR / Adarof

NvFlash the RougeXM touch recovery CWM and use that to flash a new ICS firmmware/ROM. That's probably the easiest route to take. You can flash total stock that overwrites the custom recovery if you'd like too. Should fix your ota problem too.

removed

Okay, I have flashed ww-9.2.1.11-CWM-full-rooted.zip.
Wipeing everything tried.
But still no updates...
I found http://forum.xda-developers.com/showthread.php?t=1655976, which are the same log-entries like I found
But no luck on googling further on

If you have anything but a stock recovery, you will not get an OTA. You need to here to get the stock recovery and flash it through CWR. Then when you boot to recovery, using the power+vol down wait to see the text at top right corner and then hit volume up, method, you'll see an android laying on his back with a ! above him. This is stock recovery. Should be able to push OTA through settings after this.

Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Thanks again so far!
BR / Adarof

adarof said:
Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
Click to expand...
Click to collapse
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
adarof said:
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Click to expand...
Click to collapse
All you need from that link I posted above is the SURecovery image and nothing else. You can get the firmware.zips from Asus directly. The SURecovery is universal, meaning it will work no matter what region you are in. It is the ROM/Blobs that are region specific. Don't forget that if you download one from the Asus site, that you need to extract it first and then push the zip that was inside the original file you downloaded.
So it would look like this WW.zip->extract->firmware.zip<<<---This is your ROM
adarof said:
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Click to expand...
Click to collapse
Not sure about these questions.

Woodrube said:
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
Click to expand...
Click to collapse
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Woodrube said:
All you need from that link I posted above is the SURecovery image and nothing else.
You can get the firmware.zips from Asus directly.
Click to expand...
Click to collapse
SURecoverty means the USRecovery.zip, right?
So, in summarize
1) Rogue XM Touch recovery via nvflash from http://forum.xda-developers.com/showthread.php?t=1446019
2) Use RogueXM to flash original asus-firmware (decompressed download archive)
3) Use RogueXM to flash USRecovery.zip from http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
I assume the RogueXM requires a blob-File within the zip, which is not provided by asus-original-downloads?
A bit confused ;-)
BR / Adarof

adarof said:
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Click to expand...
Click to collapse
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs. That way you'll be able to extract the apps from them and push to /system/app on your own (don't forget to set permissions also on the ones you push). If not, I will see if I can pull them from mine, zip them up and them send a link to you, but that won't be until I 1 get home and 2 get some time which unfortunately won't be tonight.
adarof said:
SURecoverty means the USRecovery.zip, right?
Click to expand...
Click to collapse
Yes sorry about that. I was typing too fast. :/
adarof said:
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
adarof said:
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
Click to expand...
Click to collapse
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways. You can root it (if you lose it somehow) with Razerclaw since it is HC.13 (if you accidentally update all the way to ICS .11 without rooting, you can use ViperMod or any of the other root tools out there) Remember that once you root it, you can use OTA Rootkeeper to preserve your Root status, accept the OTA and then restore Root (this is what I have done since HC). Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
I would then uninstall the Recovery Installer to make sure you don't accidentally hit it and you are back where you started. But you'll have the APK to reinstall whenever you want later on.
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Edit::: Check this out too.

Woodrube said:
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs.
Click to expand...
Click to collapse
Well, Ok...since I "just" would like to have back a real stock system, with OTA - there should be another way ;-)
Woodrube said:
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
Click to expand...
Click to collapse
Okay! This explains why I cant find any 1000000 hits on google related to my prop, which seems to me rather "simple" in principle ;-)
Woodrube said:
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways.
Click to expand...
Click to collapse
Agreed...apps should be there. But even the Asus storage app was missing? Thus no stock-apps included?
Its an old Andoroid 3.0.1 and it wouldn't find OTA updates - thats correct?
Woodrube said:
Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
Click to expand...
Click to collapse
Okay, while Power-VolDown -> VolUp (this gave me Rogue XM before but since I installed USRecovery it was overwritten, right?) -> a Droid on its back with a "!" comes up.
...and now?
The .24 update on SDCard is recognized but when I try to install the knocked-out droid with "!" comes on reboot again and next reboot yields to a popup "failed update, reverted to old system" or so.
Woodrube said:
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Click to expand...
Click to collapse
THANKS for your time so far and dont stress anything
I really appriciate it! Im feeling lost on android...even I work with Linux/Unices since a decade or so :-/
Woodrube said:
Edit::: Check this out too.
Click to expand...
Click to collapse
Thats a Win-solution :-/
Most propably I need a stock DE .21 or WW .24 , repacked for flashing with CWM ... right? But that doesnt exists?!?! Cant imagine...
BR - Adarof!

Im still on this problem and have no idea - searched a lot, but havent found any real howtos for DE-tf101 for unbricking.
So my main thoughts are about this Error7, which is really ...strange.
I could flash the repacked, which is available for .11. But I dont have a change to get anz further...
I SHOULD be able to flash a original asus stock Firmware with the Rogue XM Touch recovery, right?
Since Im not able to ... should I try an older version of Rogue XM?
BTW: Is the region info somewhat hard-wired thus it couldnt be changed?
BR - Adarof

There's a WW .24 available for tf101 and I'm making a 9.2.2.6 for the Tf101G,
so there is the latest FW available.

If you are flashing, then that means you have a custom recovery. That is why no OTA.
I'm mobile now but IIRC from before, you flash a working CWR version of the ROM. Thne boot up. Then flash the stock recovery. Then you should be able to OTA after that.
Just make sure whatever ROM you flash is full. If you can nvflash that would be better and then put stock recovery in after your first boot.

Thanks to both of you!
@Woodrube: Flashing means using RogueXM...
Summary:
1) Rogue could flash me either CWR/rooted images or the repacked one - both without OTA.
Just RogueXM is left as bootloader, which shouldnt prevent OTA?!
2) Rogue gives Error7 on flashing the asus-downloaded-onetime-depacked-firmwares, doesnt matter if the DE.21 or current WW.24. :-/
Trying to make the long story short:
For comming back to a "known" system I would like to really go back to a stock system.
I conclude that using nvflash would be the best for this, right?
But where do I get the img-Files for flashing using nvflash?
I just found one package which included a download.sh: It repartitioned, formated and installed a WW android3 (3.2.1) version and deleted the RogueXM. It mentioned its a stock firmware (thus should have all apps).
Sadly no updates afterwards...
I think it could be since its the WW version and I would need a WW .21/.24 (since 21/24 dont distinguish DE and WW anymore) or an older DE-version. But for nvflash I need the img files of these firmwares, which I dont find. ...
Maybe you could simply point me to such img files for nvflash, please?
BR / Adarof

Finally I managed to borrow a win pc and thus could give EasyTool of your posting #8 a try: http://forum.xda-developers.com/showthread.php?t=1688012
After some hassle with the driver I managed to flash asus stock download DE_epad-user-9.2.1.21, which is "DE_Special" for coming to WW of german tf101s. the tf was wiped and boots just fine - it states that it has
IML74L.WW_epad9.2.1.21-20120413 - as I think is fine.
Sadly no update again:
The OTA doesnt find any.
The microSD recognizes WW_epad-user-9.2.1.24.zip, but during rebooting I get the Droid with ! and after another reboot a popup with something like "update failed (12)" (in german Systemaktuallisierung fehlgeschlagen (12)). It mentiones that the new version in not compatible ...but ....the .24 is for the DE_special .21 the next ... ?!
I could flash the .24 using Easytool, but this would mean to loose always all data for an update ....
Installing rogue still gives error7 on flashing stock (once decompressed) .zip

I've been reading and Rouge gives errors with stock otas X.x
You can manually install the stock blobs with adb shell, but they will overwrite recovery and etc..
If you want total stock you need to NvFlash, and for whatever reason your tf does NOT like updates.
Rouge V1.3 will take otas, if you don't mind the downgrade.

Thanks for the hint - but I was to lazs to install the rogue 1.3.
I found a .zip, which I tried to install by Rogue 1.5 hoping for a downgrade overall, but during installation it stated "Returning to recovery" and still 1.5 was installed .
What I finally found is a ww-9.2.1.21-to-9.2.1.24-CWM-v1.0.zip image.
I installed this using rogue 1.5 and got a clean .24 installation.
So I'm using this installation hopeing either
1) OTA will work, if asus releases .24++ or
2) I find an ww-9.2.1.24-to-9.2.1.24++
Still I dont get why the EasyTool .21 installation yields to a non-OTA state ... but ...
So, THANKS all of you for your support and hints!
I'll come back here and report further on, if .24++ is out
BR / Adarof

bad luck
....meanwhile my tf101 has started to ignored the dock battery, while the keyboard still works. I tried cleaning ....no luck, the dock battery does not come up within the menues ...
Thus it was returned and I'm waiting for repairing or refunding ...
BR / Adarof

[Q] Is it possible to root after jellybean update WITHOUT unlocking?

I recently bought my new Transformer Infinity and like an idiot I updated to jellybean without thinking if I wanted to root first.
I've tried several different ways but I can't get my TF700t to root after updating so that leads me to ask if I must unlock before rooting after jellybean?
I've tried downgrading and that is to say I've put the 9.4.5.30 update in my root of the microsd card and when I go to recovery boot i just get the little guy on his back with a red triangle and black exlamation mark.
I realize unlocking will void my warranty which I am a little hesitant, though I never purchased any warranty with my tf700t but i think i can do so now.
I tried following this post:
Thanks for the reply, but i've been working on this for the past couple of hrs and my issue is solved. i'm currently back at 4.1.1 Jellybean again and Root Checker has verified that root is in place. the su binary is also present and all apps that need root work properly (Busybox, Titanium Backup, etc). i've also rebooted and rechecked several times to be sure, it say rooted every time now, whereas it didnt before. I managed to do all of this without unlocking the bootloader as well, even though what i've read elsewhere says it is necessary to do so.
I would have agreed with you before on your point that OTA updates are irreversible, and they usually are, but my experience today shows otherwise. however, you are right that each OTA will probably make it harder to reroot or stay rooted. you're also right that factory reset only wipes data but not firmware, which i just recently figured out today before you posted. i used the "about tablet" section in settings both before and after my steps below to verify that i had indeed downgraded/upgraded firmware/Android versions from JB to ICS and vice versa.
here are the steps i took, in sequential order, so that maybe anyone else with my issue can benefit. i cant gaurantee it will work for everyone:
1. downgraded from 4.1.1 JB firmware to "Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3)". This will roll you back from Jellybean to Ice Cream Sandwich. go to support.asus.com, enter TF700T as the model number, and scroll down until you find this, then download it and unzip the zip file to the root of your sdcard (there is a zip file within the downloaded zip, place that at the root, not the downloaded file itself). if you are using a TF700T that is not US-based then download the appropriate file for your region, just make sure that it has .30 in the file name. I read on a forum somewhere that this is the only firmware update for this device that enables downgrading from higher version to 4.0.3, although it's possible that others may work. then power off your device and do a cold boot (hold down left volume and then followed by power button, do this for about 10 seconds. when you get to the desktop/start screen you will see "Safe Mode" in lower left corner, then your device will notify that an update is available. tell it to apply and let it reboot. when it powers back on you should be back at 4.0.3
2. Do a factory reset, this can be done either before or after the step above, but i did it after. i'm not sure if this is necessary , but just to be on the safe side. back-up all important info, apps, etc beforehand
3. I used the method at Simple Guide to Root TF700T Asus Transformer Pad Infinity : Tips For Tab . this guide can also be found at other websites, but the steps are the same and the files/utilities needed are the same as well. just follow the steps. this will not work if you are still at 4.1.1, you will get the error i detailed in my last post.
4. Download Root Checker (to verify root access) and make sure you have the latest Superuser installed from Play (SuperSU may also work but i'm not sure, i'm using the paid version of Superuser Elite). and also get Voodoo OTA RootKeeper (free), this has a function that will allow you to restore root access after upgrading to 4.1.1. Superuser Elite also has a "ota survival" function that does essentially the same, both worked for me (this software isnt free). and get Busybox and a terminal emulator like Better Terminal Emulator or Android Terminal Emulator. i'm not even sure if these last 2/3 are absolutely necessary, but they install essential must-have functions that all root users should have.
5. then use RootKeeper and make a backup of the su binary, or place a checkmark beside the "ota survival" function in Superuser Elite. either will backup the su info so that it can be restored.
6. Next, do a direct OTA upgrade to 4.1.1 JB , either by using the built-in firmware update function, or by manually downloading from the website and updating using the method listed above. Do NOT do a restore to factory backup state after this point (especially after), it will most likely wipe out the backups of su made by RootKeeper/Superuser Elite.
7. after the upgrade is finished you will be back at start screen at at 4.1.1, use Root Checker and it will say you're not rooted. Then use either of the 2 programs ive outlined to restore the su binary from the backup. in SU(E) just uncheck and recheck the OTA Survival box, or in RootKeeper just restore from backup. Then go back to Root Checker after doing either of these, it should say rooted. reboot and recheck to make sure.
8. That's it! just wash, rinse and repeat when the next firmware update is available, hopefully these same steps should work
Also make sure to keep a backup of the su binaries/app from here onwards, otherwise at some point in the future you may lose the ability to simply restore from backup after each OTA Firmware update. you will have to start over from the beginning.
I'm sure someone figured this out already, but i figured i would post anyways.
Click to expand...
Click to collapse
but i couldn't even downgrade

Beret67 said:
I recently bought my new Transformer Infinity and like an idiot I updated to jellybean without thinking if I wanted to root first.
I've tried several different ways but I can't get my TF700t to root after updating so that leads me to ask if I must unlock before rooting after jellybean?
I've tried downgrading and that is to say I've put the 9.4.5.30 update in my root of the microsd card and when I go to recovery boot i just get the little guy on his back with a red triangle and black exlamation mark.
I realize unlocking will void my warranty which I am a little hesitant, though I never purchased any warranty with my tf700t but i think i can do so now.
I tried following this post:
but i couldn't even downgrade
Click to expand...
Click to collapse
Where did you get the old ROM from? ASUS isnt hosting it anymore and it HAS TO BE a factory original Firmware signed properly or it will not take. In fact you should see "Signature Match" (or maybe its matched) in the top left corner in recovery.
I'm not saying that message is a guarantee you have the right ROM but its a good sign.
The default warranty is like a year so I wouldnt want to unlock either.

hx4700 Killer said:
Where did you get the old ROM from? ASUS isnt hosting it anymore and it HAS TO BE a factory original Firmware signed properly or it will not take. In fact you should see "Signature Match" (or maybe its matched) in the top left corner in recovery.
I'm not saying that message is a guarantee you have the right ROM but its a good sign.
The default warranty is like a year so I wouldnt want to unlock either.
Click to expand...
Click to collapse
I got the update that said: Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3) - 2012.09.21 update
from http://forum.xda-developers.com/showthread.php?t=1946456
And i'm pretty sure it said signature match.

Beret67 said:
I got the update that said: Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3) - 2012.09.21 update
from http://forum.xda-developers.com/showthread.php?t=1946456
And i'm pretty sure it said signature match.
Click to expand...
Click to collapse
Makes me wonder if they have broken downgrade on the 10_4_4_25 firmware then?! The TF201 had that happen on the first JB update. You could no longer downgrade to ICS.
Edit, Adding that I just downloaded the US 9.4.5.30 from that site you linked to and an MD5 check confirmed it matches the one I have used 3 times.

hx4700 Killer said:
Makes me wonder if they have broken downgrade on the 10_4_4_25 firmware then?! The TF201 had that happen on the first JB update. You could no longer downgrade to ICS.
Edit, Adding that I just downloaded the US 9.4.5.30 from that site you linked to and an MD5 check confirmed it matches the one I have used 3 times.
Click to expand...
Click to collapse
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?

Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
The link you supplied that has all the firmwares there are several that say 9.4.5.30
The first one is WW, World Wide. You need to make sure you get the correct one for your device. So if you bough retail in the US get the second one that says "US". The firmware will not work if you don't get the correct one.
An easy way to tell what you need is to go to settings and scroll down to "About" on the left. Tap About and on the right half scroll down to "Build Number" My daughters TF201 says JRO03c.US_epad........
So she has the US one and would need the US Firmware.
If you have a US device and tried to apply the WW firmware from what I have read it will fail, won't work.. dead andy. Make sure you have the right firmware for your device.
Please post back your results as I am sure many would be interested if ASUS broke reverting to ICS.

Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
After you download the zip file, first you have to UNZIP the zip file and you're going to see another zip file. Now rename this new zip to EP201_768_SDUPDATE.zip , then copy this to the root of your sdcard, boot into recovery and try again.

Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
I assumed the file rename was in the directions above

The only device I believe you should ever have to root/unlock /jailbreak is the IOS platform. As you probably know, you are extremely limited to any customization with an IOS device. Under the android platform, I find that there are many flavours of customization under the stock setting already. I've ran the TF700T with the latest updates and firmware for the past few months and performance is still optimal ... I also bet that if you had my tablet side by side next to a rooted/unlocked TF700T tablet, you wouldn't be able to tell the difference from a performance perspective. I'm only speaking from a standard user point of view. I can see where a developer may want root access and or someone who wants to learn how to program the OS, create custom ROMS etc., however for the casual user, I'd leave it the way it is.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Rashar said:
The only device I believe you should ever have to root/unlock /jailbreak is the IOS platform. As you probably know, you are extremely limited to any customization with an IOS device. Under the android platform, I find that there are many flavours of customization under the stock setting already. I've ran the TF700T with the latest updates and firmware for the past few months and performance is still optimal ... I also bet that if you had my tablet side by side next to a rooted/unlocked TF700T tablet, you wouldn't be able to tell the difference from a performance perspective. I'm only speaking from a standard user point of view. I can see where a developer may want root access and or someone who wants to learn how to program the OS, create custom ROMS etc., however for the casual user, I'd leave it the way it is.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I guarantee if you unlocked and installed a custom rom you would be blown away with how slow stock is Seriously, how do you know if you haven't done it? Seems like a strange challenge you have set. BTW I don't know one single person who has unlocked and gone to a custom rom who would go back to locked stock because performance is that different. You just don't know it.

sbdags said:
I guarantee if you unlocked and installed a custom rom you would be blown away with how slow stock is Seriously, how do you know if you haven't done it? Seems like a strange challenge you have set. BTW I don't know one single person who has unlocked and gone to a custom rom who would go back to locked stock because performance is that different. You just don't know it.
Click to expand...
Click to collapse
A significant reason for increased performance on custom ROMS is that the kernel they use allows for overclocking usually to 1.8GHZ. Just FYI in the interest of full disclosure.
It is not the ONLY reason but a big part of why they look/feel so much faster.

hx4700 Killer said:
A significant reason for increased performance on custom ROMS is that the kernel they use allows for overclocking usually to 1.8GHZ. Just FYI in the interest of full disclosure.
It is not the ONLY reason but a big part of why they look/feel so much faster.
Click to expand...
Click to collapse
Yes kernel tweaking brings huge benefits but there are plenty of other tweaks that bring the perks as well outside the kernel

Hello everyone, I just joined XDA and hope to be a successful contributor to this amazing community. This is my first post, hope it will be of help.
I can confirm that 10.4.4.25 did not break the downgrade option. Like others already suggested, make sure you're using the firmware which matches your device (WW/US/etc.) and you should be fine.
I Just got my device tonight from ASUS (RMA due to crashes every 2.5 days on the clock, black lines every few seconds, extremely laggy).
My precious came with 10.4.4.23 and I upgraded it to 10.4.4.25 to check the performance and black lines issue. With 25 it still lags a little but less than 23 and other earlier firmwares. I ran these tests on 23 then on 25:
1. For real life performance (don't care about synthetic benchmarks) I updated all the apps simultaneously. Both firmwares were laggy but 25 was much less than 23.
2. The black line is still there in 25 but much less than 23. I could reproduce it only with the black hole live wallpaper test which is a very good sign as in 23 I reproduced it a couple of times without the black hole live wallpaper.
After these tests I downgraded successfully to 9.4.5.30 (US) in order to root (need that for Avast FW) with no problems at all. Now I will go root it.
Update: Successfully rooted and upgraded back to 10.4.4.25

G0llum said:
After these tests I downgraded successfully to 9.4.5.30 (US) in order to root (need that for Avast FW) with no problems at all. Now I will go root it.
Update: Successfully rooted and upgraded back to 10.4.4.25
Click to expand...
Click to collapse
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.

ils01 said:
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.
Click to expand...
Click to collapse
Are you rooted? If you are you need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090

buhohitr said:
Are you rooted? If you are you need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
Click to expand...
Click to collapse
I am rooted now (but still locked). Can I jump directly to 10.4.4.25 using dlpkgfile without doing other middle steps?
Edit: Tried going straight to 10.4.4.25 and failed. No OTA either.

ils01 said:
I am rooted now (but still locked). Can I jump directly to 10.4.4.25 using dlpkgfile without doing other middle steps?
Click to expand...
Click to collapse
No you can't, you need to upgrade to JB .16, then .18 then you can jump to .25.

buhohitr said:
No you can't, you need to upgrade to JB .16, then .18 then you can jump to .25.
Click to expand...
Click to collapse
Thank you very much. Will do that.

ils01 said:
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.
Click to expand...
Click to collapse
OTA. Immediately after restart the tablet started downloading the update automatically... I postponed the update installation and then rooted, installed voodoo, created su backup, temp un-rooted and only then applied the OTA.

G0llum said:
OTA. Immediately after restart the tablet started downloading the update automatically... I postponed the update installation and then rooted, installed voodoo, created su backup, temp un-rooted and only then applied the OTA.
Click to expand...
Click to collapse
Thanks for the update.
Mine did not see any update regarless of multiple checkings performed (this was done before any rooting attempted). I am in the process of dowloading dlpkgfiles and slowly doing the hard way.
Update: After I reflashed back to 9.4.5.30 to root, I went on and started updating using dlpkgfile started with .16, .18, .20, .23, and finally .25. All is good now. However, I had a few errors when going from .16 to .18 due to getting incorrect/wrong dlpkgfile.
Thank you for everyone's help.

Unable to load webpages after Sunshine (root, S-off)

I used Sunshine, got root and S-Off, flashed a wireless tether zip. Right after, 4G speeds plummeted and no websites would load. Saw the closest to going back was to RUU, couldn't get it to open the file (even in the SDK folder after I downloaded and installed all files). Finally flashed another ROM and wiped everything from my phone.
Still 99% of webpages won't load on 4G. If they do, it takes forever. Not sure if it's anything I did, but just wanted to ask before it turns out to be some huge coincidence with Verizon. Thanks for any help.

Yazzinit said:
I used Sunshine, got root and S-Off, flashed a wireless tether zip.
Click to expand...
Click to collapse
Which one?
Right after, 4G speeds plummeted and no websites would load.
Click to expand...
Click to collapse
Pretty good indicator for what's wrong?
Saw the closest to going back was to RUU, couldn't get it to open the file (even in the SDK folder after I downloaded and installed all files).
Click to expand...
Click to collapse
You have fastboot drivers installed on your PC?
Finally flashed another ROM and wiped everything from my phone.
Click to expand...
Click to collapse
Which one?
Still 99% of webpages won't load on 4G. If they do, it takes forever. Not sure if it's anything I did, but just wanted to ask before it turns out to be some huge coincidence with Verizon. Thanks for any help.
Click to expand...
Click to collapse
Flash CleanROM. It's just like stock only better: debloated and tweaked, tethering enabled and more...

Thanks for the reply.
The wireless tether zip I flashed was: http://forum.xda-developers.com/showthread.php?t=2708548
The ROM I'm currently on is: http://forum.xda-developers.com/showthread.php?t=2716306
- Nothing wrong with it, just don't like the stock look and loading webpages is still not working.
I have fastboot drivers and adb as well as the SDK toolbox on my PC. I've been able to do most things following guides and posts here, but I can't RUU. When I flashboot flash zip 0P6BIMG.zip it gives error: cannot open 0P6BIMG.zip. I guess I could buy an external SD card and reader, but was hoping to fix this tonight/tomorrow.
Trying to download CleanROM for the 5th time tonight. The download stops around 300-400MB and there's no other mirrors for it. Currently at 700MB, maybe this download will go through (on PC). I'm really just trying to fix my webpage issue and go back to stock (or CleanROM is fine if it's similar). I'm willing to even donate a little to someone.

Yazzinit said:
Thanks for the reply.
The wireless tether zip I flashed was: http://forum.xda-developers.com/showthread.php?t=2708548
The ROM I'm currently on is: http://forum.xda-developers.com/showthread.php?t=2716306
- Nothing wrong with it, just don't like the stock look and loading webpages is still not working.
I have fastboot drivers and adb as well as the SDK toolbox on my PC. I've been able to do most things following guides and posts here, but I can't RUU. When I flashboot flash zip 0P6BIMG.zip it gives error: cannot open 0P6BIMG.zip. I guess I could buy an external SD card and reader, but was hoping to fix this tonight/tomorrow.
Trying to download CleanROM for the 5th time tonight. The download stops around 300-400MB and there's no other mirrors for it. Currently at 700MB, maybe this download will go through (on PC). I'm really just trying to fix my webpage issue and go back to stock (or CleanROM is fine if it's similar). I'm willing to even donate a little to someone.
Click to expand...
Click to collapse
Scott's site is not mobile friendly, but he just put up a DevHost mirror:
http://forum.xda-developers.com/showthread.php?p=55135177

The download actually finished, I even checked the MD5 of my download vs. on his site, matched. Wiped and flashed it, got dialer.apk stopped working, hit ok, popped up again, hit ok, phone bootlooped with 3 colored android lights on screen. Rebooted manually, same error, then something like phone.apk or android.google.something stopped working, hit ok, boot loop again. Pretty much have no clue at this point.

Yazzinit said:
The download actually finished, I even checked the MD5 of my download vs. on his site, matched. Wiped and flashed it, got dialer.apk stopped working, hit ok, popped up again, hit ok, phone bootlooped with 3 colored android lights on screen. Rebooted manually, same error, then something like phone.apk or android.google.something stopped working, hit ok, boot loop again. Pretty much have no clue at this point.
Click to expand...
Click to collapse
That sounds as if you dirty flashed CleanROM over the GPE.
Did you wipe cache, Dalvik and data before flashing CleanROM?
If not, do it and reflash the rom.

I may have messed it up, it was late last night. I have TWRP on it after following guides since I somehow lost the OS while trying to RUU different ways. Can anyone confirm everything I need to wipe so that I can flash CleanRom without wiping it from my internal storage? Don't have an external SD card and it won't sideload for some reason (I get error: cannot open romname.zip).
Edit: That worked. Except now it says CleanROM 1.3 in my settings lol and I swear I downloaded 1.4, since it was from the developer's site directly.

You do not need to flash a tether zip on that ROM or any other custom ROM
Sent from my HTC One VZW using Tapatalk 4

You're right. At the time I just wanted to add tethering and not change anything or flash any ROMs. Beyond that point now lol. CleanROM looks fine and is working well, it just says 1.3 in settings when I know I downloaded 1.4 from the OP's site last night.

Yazzinit said:
You're right. At the time I just wanted to add tethering and not change anything or flash any ROMs. Beyond that point now lol. CleanROM looks fine and is working well, it just says 1.3 in settings when I know I downloaded 1.4 from the OP's site last night.
Click to expand...
Click to collapse
It's a typo. ?
Scrosler provided a zip to change the version number. I believe it's in post 2

berndblb said:
It's a typo. ?
Scrosler provided a zip to change the version number. I believe it's in post 2
Click to expand...
Click to collapse
You are correct and thank you for the kind reply, unlike another in that topic who took the same amount of time to be rude for no reason. Thanks to all for their help, looking good now and working good, and extra features to boot.