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.

Major problem - tf101 bricked

I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)

need more info
what model number do you have, what can you get into, what cant you get into etc

lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.

You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf

baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.

What is the serial number of your tf?
Hopefully it's one that's nvflash compatible

baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90

i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.

I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.

gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?

The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?

roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?

If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.

gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?

joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.

In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??

gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.

Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.

gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...

Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision

[Q] TF300T RCK issues after reflashing stock ROM

So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.

Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!

Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.

tobdaryl said:
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Click to expand...
Click to collapse
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
flumpster said:
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
Click to expand...
Click to collapse
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD

Rojikku said:
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Click to expand...
Click to collapse
The twrp mentioned above can be found here.

tobdaryl said:
The twrp mentioned above can be found here.[/URL]
Click to expand...
Click to collapse
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.

Rojikku said:
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Click to expand...
Click to collapse
Wrong twrp! You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off stock 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Unless the rom you flash is also for 4.2 bootloader. Both are located at teamwin.
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock.
As far as flashing a new rom look at the op and determine if it is for the new stock 4.2 bootloader. If not do not flash over 4.2 but downgrade first. I have upgraded from 10.4.2.20 to stock 4.2 and downgraded from stock 4.2 to 10.4.2.20 several times without issue.
Stock 4.2 includes an assert to only allow upgrade from 10.4.2.20.

tobdaryl said:
Wrong twrp! [/URL]You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Both are located at teamwin.[/URL]
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock and hold a minute or you are going right back where you were or worse. You need slightly more info before going forward and I need to check my notes while you get the proper twrp flashed.
Click to expand...
Click to collapse
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.

Rojikku said:
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Click to expand...
Click to collapse
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.

tobdaryl said:
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
Click to expand...
Click to collapse
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.

Rojikku said:
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Click to expand...
Click to collapse
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?

tobdaryl said:
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
Click to expand...
Click to collapse
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?

I decided to take the risk and reboot it. Everything fine. I flashed the tool, ran the reboot command(Which actually didn't work... >>; But I rebooted it manually and it seems fine...)
On that note, is it actually possible to destroy a device beyond repair accidentally? And the TWRP tool said it flashed fine but I still have the old version. Odd....
I do have the image you said currently installed, I checked the version against my download.

Rojikku said:
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
Click to expand...
Click to collapse
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.

tobdaryl said:
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
Click to expand...
Click to collapse
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?

Rojikku said:
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Click to expand...
Click to collapse
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.

tobdaryl said:
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
Click to expand...
Click to collapse
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.

Rojikku said:
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Click to expand...
Click to collapse
When it asks for the password hit cancel and just ignore the error.

tobdaryl said:
When it asks for the password hit cancel and just ignore the error.
Click to expand...
Click to collapse
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)

Rojikku said:
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Click to expand...
Click to collapse
Thanks for the link. I looked at the info provided for that rom. You don't want to flash that over an encrypted tablet which you now have. The only safe way I have found to go to or from stock 4.2 rom is with stock 10.4.2.20.
To do that you would flash 10.4.2.20 with twrp, boot into os, reboot back to the bootloader which will now be four icons, select usb, use fastboot to flash twrp again, and now flash your new rom.
This sounds long but removes encryption from your tablet and you should be able to flash the jb rom of choice that does not require stock 4.2 bootloader.

[Q] Deleted my OS!!!!!!

So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.

gmermel said:
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
Click to expand...
Click to collapse
You should be alright... Can you try this for me? Holding the power button and volume down at the same time.. You should see your bootloader menu whih has 3 icons... Please let me know if you can get there..:fingers-crossed:

gmermel said:
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
Click to expand...
Click to collapse
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post

berndblb said:
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
Click to expand...
Click to collapse
Wow. 2 minutes and I'm getting help already.
I'm in TWRP. Where do I get the stock rom? I presume I'll download it my computer, but how do I tell the tablet to load it from there?

berndblb said:
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
Click to expand...
Click to collapse
It is not a problem... I think that my device is running the ET so it is a little faster...:silly: Just kidding...
It would be better that you can help him/her.. I am a little busy testing new stuffs.. Thanks for the helps and talk more with you later...

LetMeKnow said:
It is not a problem... I think that my device is running the ET so it is a little faster...:silly: Just kidding...
It would be better that you can help him/her.. I am a little busy testing new stuffs.. Thanks for the helps and talk more with you later...
Click to expand...
Click to collapse
A LITTLE busy testing new stuff??? Haha! Are you doing anything but...?
---------- Post added at 10:48 PM ---------- Previous post was at 10:38 PM ----------
gmermel said:
Wow. 2 minutes and I'm getting help already.
I'm in TWRP. Where do I get the stock rom? I presume I'll download it my computer, but how do I tell the tablet to load it from there?
Click to expand...
Click to collapse
You don't. You have to copy the rom or firmware to your microSD.
Insert the card, boot into TWRP as described earlier.
Choose 'Install" and then navigate to your microSD and the zip you parked there.
Select it, swipe to flash it.
Now: I cringe, when someone on a perfectly fine and unlocked TF700 wants to flash back the Asus firmware. Ouch!
But I understand you only want to sell it and the buyer may not know how much better this tablet is on a custom ROM like CROMi-X. Sigh!
So, if you insist on flashing the latest firmware, go to the Asus support website, the download section, enter Transformer in the search box, select the TF700 and look for the 10.6.1.14.10 firmware. Make sure you select the one for your SKU, meaning US if you're on this continent (and I assume you are since you're awake at this time ), or WW or where ever you are.
Download the firmware and and on your computer, extract that zip file once - the result being another zip file.
It's that once extracted zip you want to copy to your SD, insert in your tab and flash in TWRP.
Ask if I left anything out.

Thanks. You're right, I'm in the US. But I am going to sleep. Will get on this in the AM.
You are correct to cringe. I rooted/C-romix'd a few months ago because I was frustrated by the constant lag on the tab. Figured if I bricked it, well, I wasn't happy with it anyway. I cringed when I went and did it because I knew I was taking a risk what with my capabilities. I've moved on to the Nexus 7 and just love it. Not just the performance. The small platform is just right....
Thanks for the rapid replies and the sophisticated yet understandable directions. Mostly, thanks for not calling me a knucklebrain even though I deserve it.

gmermel said:
Thanks. You're right, I'm in the US. But I am going to sleep. Will get on this in the AM.
You are correct to cringe. I rooted/C-romix'd a few months ago because I was frustrated by the constant lag on the tab. Figured if I bricked it, well, I wasn't happy with it anyway. I cringed when I went and did it because I knew I was taking a risk what with my capabilities. I've moved on to the Nexus 7 and just love it. Not just the performance. The small platform is just right....
Thanks for the rapid replies and the sophisticated yet understandable directions. Mostly, thanks for not calling me a knucklebrain even though I deserve it.
Click to expand...
Click to collapse
Not that long ago, I was exactly where you are now....:silly:

berndblb said:
Not that long ago, I was exactly where you are now....:silly:
Click to expand...
Click to collapse
Problem #1: When I opened the ROM.zip, I didn't get another zip, I got a folder with no zips in it (a blob.exe, several other .exe). When I moved that over to the SD and chose to install it TWRP returned a "failure" notification.
I'd like to get the stock ROM on for the buyer. What should I do
Problem #2: I still have CROM-X on the external card. It is installing, but which kernel should I use?
I'm going to use sbdags stock, and if you think that's a mistake I'll reflash.

gmermel said:
Problem #1: When I opened the ROM.zip, I didn't get another zip, I got a folder with no zips in it (a blob.exe, several other .exe). When I moved that over to the SD and chose to install it TWRP returned a "failure" notification.
I'd like to get the stock ROM on for the buyer. What should I do
Problem #2: I still have CROM-X on the external card. It is installing, but which kernel should I use?
I'm going to use sbdags stock, and if you think that's a mistake I'll reflash.
Click to expand...
Click to collapse
If you get the blob file you extracted once too often. The firmware is a zip inside a zip. You extract the downloaded file ONCE.
Stock kernel is fine.
Sent from my DROID4 using Tapatalk

TF700KL root + new Rom?

Hello,
i have a TF700KL, and i want to flash it.
But i don't find Something about it. Only about TF700.
Can You Help me?
Warm regards

Please Guys, i want help... Please...

Thx for ignore me

TF700 & TF700KL same, KL is the last version and the one listed on Asus's Global Website. All files should work once you A) Update firmware to the latest version B) Unlock bootloader. - NP

I did update it to Version VF_V5.0.4.17 but still can't manage to make the unlock app to get installed.
hard resetted3 times also with no GMAIL account, but still nothing
please help me

Donnie87 said:
I did update it to Version VF_V5.0.4.17 but still can't manage to make the unlock app to get installed.
hard resetted3 times also with no GMAIL account, but still nothing
please help me
Click to expand...
Click to collapse
Took me a few minutes to find it and a few hoops to jump through to extract the archive, but the official apk is still out there. Try to install this:
https://www.androidfilehost.com/?fid=5862345805528055095

AMAZING I MANAGED!!! THANK YOU BROOOOOOOOOOOOOOOOOOOOOOOOOOOO
how can I now install a custom rom? I'd just like to have the original one but faster....
and of coruse no I don't want to lose the 4g support
---------- Post added at 02:42 PM ---------- Previous post was at 02:03 PM ----------
I tried to reboot but even if it's unlocked, I have no bootloader. it still remain with the screen normal version

Donnie87 said:
AMAZING I MANAGED!!! THANK YOU BROOOOOOOOOOOOOOOOOOOOOOOOOOOO
how can I now install a custom rom? I'd just like to have the original one but faster....
and of coruse no I don't want to lose the 4g support
---------- Post added at 02:42 PM ---------- Previous post was at 02:03 PM ----------
I tried to reboot but even if it's unlocked, I have no bootloader. it still remain with the screen normal version
Click to expand...
Click to collapse
You are welcome.
Rest assured you do have a bootloader. You may not have the bootloader interface the other Transformers have and possibly there is no way to get fastboot to work on this thing - I don't know.
There is no custom rom for this tablet, and if you do not want to loose 4G you cannot use one made for another Transformer either (no idea if that is even possible, I do not know the KL).
Your best bet is to gain root and uninstall a bunch of cr**, maybe use Greenify - I don't know. Very limited what you can do on stock....
I seem to recall that people got root with Framaroot on this thing. Google it, the info is out there. If I can find it so can you

berndblb said:
You are welcome.
Rest assured you do have a bootloader. You may not have the bootloader interface the other Transformers have and possibly there is no way to get fastboot to work on this thing - I don't know.
There is no custom rom for this tablet, and if you do not want to loose 4G you cannot use one made for another Transformer either (no idea if that is even possible, I do not know the KL).
Your best bet is to gain root and uninstall a bunch of cr**, maybe use Greenify - I don't know. Very limited what you can do on stock....
I seem to recall that people got root with Framaroot on this thing. Google it, the info is out there. If I can find it so can you
Click to expand...
Click to collapse
ok let me get to the keypoints here that made me ask for help, and so you'll see that i'm not just a lazy person that doesn't use google
1) Some people they say that the KL can accept all the roms of the Tf700T. for example katkiss is saying to use one of their roms
1.a) some say that it will brick the device.
so, first question here, what will happen if i'll get a custom rom of the TF700T?
2) some people say that I should have a version of the "unlock bootloder" after unlocking with the asus app.
Well I don't have anything, I just have a small phrase which is "device unlocked" and that's it. nothing else.
3) some say on google that there is a cyanogen mod for the KL. Unfortunately cyanogenmod wiki and forum are down, so I can't find either assistance, either the files.
nothing to do here, then.
4) let's say I'll follow your guide, and i'll flash a custom rom. will I lose the 4g?
4.a) how can I get to the old rom, even original, in order to get 4g back?
5) about root: i managed to root it a long time ago. Unfortunately, even disabling most of the package and all the bloatware, the device really sucks.
that's the main reason why I abandoned there 3 years ago. now it's full of dust, and as I've been working a lot, I wanted to get it back with basic functions, but without waiting 10 seconds from the moment i press on APPS BUTTON and the actual time for which I see the apps page.
so, here's my google searching experience.

Donnie87 said:
1) Some people they say that the KL can accept all the roms of the Tf700T. for example katkiss is saying to use one of their roms
1.a) some say that it will brick the device.
so, first question here, what will happen if i'll get a custom rom of the TF700T?
Click to expand...
Click to collapse
I'd say the first question is: Is there a compatible custom recovery for the KL and how to install it? I do not know that there ever was a custom recovery made for the KL and using one made for another Transformer may or may not brick your device. I do not see a single post from anyone stating that they successfully installed a custom rom or recovery on the KL, so my guess is: It cannot be done unless you develop a custom recovery for this tablet and find a way to flash it.
2) some people say that I should have a version of the "unlock bootloder" after unlocking with the asus app.
Well I don't have anything, I just have a small phrase which is "device unlocked" and that's it. nothing else.
Click to expand...
Click to collapse
Well, there's the first difference to other Transformers: Most of them have a bootloader menu from where you can boot into recovery or into Android and perform a data wipe. Booted into the bootloader you also have fastboot access. The KL does not seem to have any of this. Do you have fastboot working on your PC? Try it, boot with Vol down or Vol Up and then check if you have fastboot access to the tablet. I doubt it....
3) some say on google that there is a cyanogen mod for the KL. Unfortunately cyanogenmod wiki and forum are down, so I can't find either assistance, either the files.
nothing to do here, then.
Click to expand...
Click to collapse
I've only seen post users expressing hope or wishes for CM for the KL. I don't think there ever was a working CM rom for the KL
4) let's say I'll follow your guide, and i'll flash a custom rom. will I lose the 4g?
Click to expand...
Click to collapse
You cannot follow my guide unless you figure out a way to get fastboot working. You could try to flash TWRP recovery using their app or Flashify, but which TWRP?? Which version might be compatible with your bootloader? Nobody knows it seems. But heck! What have you got to loose? You are not going to use the tablet in its current state anyway, so if you brick it - who cares?
But to answer your question: Yes, you would definitely loose the 4G. The software for your modem has its own partition and no rom made for the wifi-only Transformers even knows this partition exists, let alone about the hardware
4.a) how can I get to the old rom, even original, in order to get 4g back?
Click to expand...
Click to collapse
Again: Untested territory. If you had a custom recovery or fastboot you might be able to flash the Asus firmware in either. Maybe

you won't believe me
I was away for 1 month
got back
installed framaroot
installed greenify
now it runs with like 10 apps total (including the keyboard)
tablet STILL UNUSABLE, takes 1 minutes to open youtube, 2 mins to open play store
Id really like to brick it rather than keep it like that
Well, there's the first difference to other Transformers: Most of them have a bootloader menu from where you can boot into recovery or into Android and perform a data wipe. Booted into the bootloader you also have fastboot access. The KL does not seem to have any of this. Do you have fastboot working on your PC? Try it, boot with Vol down or Vol Up and then check if you have fastboot access to the tablet. I doubt it....
Click to expand...
Click to collapse
tried but the max i get is the screen wghere
"press volume button to select
1) enter sd down mode
2) factory reset
3) exit update mode
press power button to enter"
so i then flashed with flashify, read after
berndblb said:
You cannot follow my guide unless you figure out a way to get fastboot working. You could try to flash TWRP recovery using their app or Flashify, but which TWRP?? Which version might be compatible with your bootloader? Nobody knows it seems. But heck! What have you got to loose? You are not going to use the tablet in its current state anyway, so if you brick it - who cares?
But to answer your question: Yes, you would definitely loose the 4G. The software for your modem has its own partition and no rom made for the wifi-only Transformers even knows this partition exists, let alone about the hardware
Click to expand...
Click to collapse
I then flashed the TWMR
when i rebooted it said
"no usb connected"
i then connected to the PC
and it say
"READY FOR DOWNLOAD" with an android picture
i can't boot it up again
what should i do now?
when i now do the FASTBOOT DEVICES command on pc, I see the serial of the asus
it's the first time fastboot sees it
I tried doing "fastboot update kitkatnougatellaxxxx.zip"
but it say that android-info.txt & android-product.txt not find so not flashable
what now, then? I can't even use it with the old OS

You need to boot into the TWRP that you flashed, hold the volume button down and press the power button (hold both) until you get the fastboot screen, the square with [RCK] should be blinking. Now press the volume up button to enter the TWRP recovery console. - NP

Nektopoli said:
You need to boot into the TWRP that you flashed, hold the volume button down and press the power button (hold both) until you get the fastboot screen,
Click to expand...
Click to collapse
this is what i get when i press the button normal boot button
this is what i get when i press the volum down + boot button
I just did flashifty with the latest TMWR recovery for TF700T

help pliz

best bet would be to do a factory reset, I don't believe this rom will work on the KL model. - NP

it doesn't even allow the factory reset, as if i press it it gives the NO USB CONNECTED screen
i'd say it's bricked

Donnie87 said:
it doesn't even allow the factory reset, as if i press it it gives the NO USB CONNECTED screen
i'd say it's bricked
Click to expand...
Click to collapse
Try selecting [1] "Enter SD down mode" which is Enter SD download mode and see if you get to the next menu. - NP

I can't

I mean it doesn't get to the next menu

I've been trying to find the threads on how to re-flash the stock ASUS ROM from the SD cardseeing this is the only way to get the TF700k working but I can't find it know. It involved have the ROM in the root directory on the SDcard and giving it a specific name, this name triggers the tablet to update itself. - NP