[Q] Downgrade from 8.6.6.23 to 8.6.6.19 or 8.6.6.15 - Eee Pad Transformer Q&A, Help & Troubleshooting

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.

Related

[ROM](Working Update.zip) -> Defy Update.zip Cookie Cutter Rom

Defy Froyo 3.4.2 Cookie Cutter Rom​
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.
um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you
this Zip File is for what ?
Thanks
Greetings
you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App
So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse
eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.
what exactly is the benefit of this new method?
drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx
drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene
I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App
psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market
Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App

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] B90

I have tried to root my TF doing it the way trippmcnealy say and to no success. I would get the android with gears turning then it would turn into an exclamation point and after a bit boot normally.
Anyone has the same issue? If not and you successfully rooted, feed back would be great. Oh when I got it, I updated without thinking.
Build# HTK75.US_epad-8.6.5.21
Any help would be great appreciated.
You can't root a b90 on .21, you have to downgrade to .19 and root with razor claw.
Brand New said:
You can't root a b90 on .21, you have to downgrade to .19 and root with razor claw.
Click to expand...
Click to collapse
Is there a method that you are aware of at this point in time that allows you to downgrade from .21? If so could you provide a link?
CobraBytez said:
Is there a method that you are aware of at this point in time that allows you to downgrade from .21? If so could you provide a link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=20799328
baseballfanz said:
http://forum.xda-developers.com/showthread.php?p=20799328
Click to expand...
Click to collapse
Already tried that multiple times and it didn't work.
felix8787 said:
Already tried that multiple times and it didn't work.
Click to expand...
Click to collapse
Double check your file to make sure it's not filename.zip.zip if your PC is set to hide known extension and you rename it to filename.zip you're gonna get the extra .zip behind it.
Also it seems like the 2nd method by trippmcnealy getting better results for peoples
Did that too. I caught the .zip.zip and changed it. Still nada. Will try again. Another thing, from the external sd card, you take the file and copy and paste to filemanager and not in a folder correct? Cause I wasn't putting it in a folder and just added to the filemanager.
Yes it has to be on the root of the sd card, don't put it in any folder.
It will scan the sd card but not scan inside any folder.
Seems like you need two files on the external sd card and two files on the internal sd card as per trippmcnealy's method
So I leave the USB hooked up also as it's recovering? Will try now but with the US .13 first then update to WW .19.
No you don't need the USB connected.
Also after you downloaded the file you did unzip to get
WW_epad-user-8.6.6.19.zip out of the zip file correct?
Pasted onto root of internal..........powered down......volume down/power then up when prompted...nothing.
felix8787 said:
Pasted onto root of internal..........powered down......volume down/power then up when prompted...nothing.
Click to expand...
Click to collapse
you pasting one or two files to the internal sd card?
2, EP101_SDUPDATE and the WW_epad-user-8.6.6.19, still getting the yellow triangle with the exclamation point.
felix8787 said:
2, EP101_SDUPDATE and the WW_epad-user-8.6.6.19, still getting the yellow triangle with the exclamation point.
Click to expand...
Click to collapse
You can try this to see, someone said they changed the WW to US and it worked for them. Outside of that I'm not sure what else you can do.
Thats exactly what I was getting ready to do....let you know how it goes.
Quick update, nothing, I did notice that when I do a recovery it says something about recovering kernel and not update?
wait a min...........well, this is what it tells me.
System Update
The update package is not compatible with your current software, please check your software version and version number in Settings and try the correct update package.
System is restored to previous configuration.
After you download the file, did you extract the file within or are you using the file as is?
I transfer both files without extracting anything. Going to try and do the US.13.
Well that didn't work, looks like I will have to wait for a fix, thanks for you time and help!

[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

[ROOT] TF101 ICS from OTA

Hello,
This is a new root method.
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
[COLOR="Red"]Mod Edit: removed link[/COLOR]
EDIT: This has been confirmed working on the TF201 and TF101 so its a Universal root for all transformers
EDIT: Adding a step by step guide here.
A) Install an app from market any app. (I choose rootchecker)
B) Open the app-draw and select the asus backup utility and backup rootchecker
C) follow the scripts instructions
D) When it asks you to do another backup. Go into the backup utility from the TF101/TF201 (from the app-draw) go to back and RE-BACKUP the SAME app (Rootchecker in my case)
E) The system will reboot and you will have root. Do this all while the script is running. It will pause and ask you do the above items.
Thanks!
Reserved for later
well adapted it to windows in case anyone needs it
Just extract the zip file, execute the run.bat and follow the onscreen instructions.
chan32167 said:
well adapted it to windows in case anyone needs it
Just extract the zip file, execute the run.bat and follow the onscreen instructions.
Click to expand...
Click to collapse
Both you and the OP are legends. worked like a charm.
THANK YOU
bungknees said:
Both you and the OP are legends. worked like a charm.
THANK YOU
Click to expand...
Click to collapse
Thanks............
I'm already rooted, but I like the technique- it's quite clever and a wonderful hack.
I don't recall there ever being so many root exploits for a single device. It's like a tablet with a free puzzle that keeps giving. People are going to start buying the TF just to root it.
I tried another way to root but when i rebooted i have cwm 3101 and su which updated but not the binaries. When i try anything its telling me i don't have root access.
Now when i try to rerun it or this it hangs right at waiting for device in the beginning. Any thoughts?
Windows 7 x64 machine
B50
frankwhite8536 said:
I tried another way to root but when i rebooted i have cwm 3101 and su which updated but not the binaries. When i try anything its telling me i don't have root access.
Now when i try to rerun it or this it hangs right at waiting for device in the beginning. Any thoughts?
Windows 7 x64 machine
B50
Click to expand...
Click to collapse
Dont know much about windows sorry. I used my method here to root on ICS. Started from stock -> Ota X 3 or 4 then root.
so this will root the official update? if so, i may be interested, but i need to know what kernel version is included in the official FOTA package. if it's still 2.6, i won't bother
sarreq said:
so this will root the official update? if so, i may be interested, but i need to know what kernel version is included in the official FOTA package. if it's still 2.6, i won't bother
Click to expand...
Click to collapse
Yes, This roots the current OTA as stated in the OP / Thread Topic
but what kernel version is in the FOTA?
sarreq said:
but what kernel version is in the FOTA?
Click to expand...
Click to collapse
2.6.39.4-00002
Neptune #1
sarreq said:
but what kernel version is in the FOTA?
Click to expand...
Click to collapse
Kernel is 2.6.39
rhcp0112345 said:
Dont know much about windows sorry. I used my method here to root on ICS. Started from stock -> Ota X 3 or 4 then root.
Click to expand...
Click to collapse
Thanks. I was able to flash this
http://forum.xda-developers.com/showthread.php?t=1334673
And I'm working as god intended.
frankwhite8536 said:
Thanks. I was able to flash this
http://forum.xda-developers.com/showthread.php?t=1334673
And I'm working as god intended.
Click to expand...
Click to collapse
Nice, Good
frankwhite8536 said:
2.6.39.4-00002
Neptune #1
Click to expand...
Click to collapse
rhcp0112345 said:
Kernel is 2.6.39
Click to expand...
Click to collapse
thank you both.
you'd think they would've updated that, since ICS proper is supposed to run on a 3.x kernel.
so, will a honeycomb CIFS.KO work with the FOTA? or is there an ICS specific CIFS module somewhere out there? / nevermind, found it here nope, wrong again, that's for the tfprime, and causes a bootloop when it loads. i guess we have to wait for one to be ported, then?
update: resolved. Didn't know about the App Backup Utility
Worked as promised. Remember you must run the Asus Backup Utility twice!
rhcp0112345 said:
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
http://www.mrcellphoneunlocker.com/V2/tf101_ics_root.tar.gz
Click to expand...
Click to collapse
Great job! thanks
tomdot said:
update: resolved. Didn't know about the App Backup Utility
Worked as promised. Remember you must run the Asus Backup Utility twice!
Click to expand...
Click to collapse
what's this utility? never seen it before
WOrks!
Working Perfectly.

Categories

Resources