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

Somewhat worried...

Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.

redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!

MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.

redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.

buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.

redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.

buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.

redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)

MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.

Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2

F2 to HE update?

I bought my S3 used and it was already unlocked but from what I can tell still had the stock ROM (base version says it is I535VRLF2 but DEVICE STATUS says it is modified). When it powers up, I do not get a CWM or TWMP screen -- it goes directly to the normal startup so I am not sure what the previous owner loaded/did. I do not see any folders in the root folder (using ES FIle Explorer) for CWM and nothing in DATA/BACKUP (EDIT: just saw build number is VRALG7)...
Today I got a notice about an OTA upgrade (to HE) and got help on how to freeze it (as I did not want to lose root and all the customization I did to some files) but now I am wondering what changes were made from F2 to HE. I did find a post that talks about the HE upgrade.
Was F2 the previous OTA for the S3, or did my phone miss other OTAs? And if so, I am missing out on some important changes where I should let the OTA happen and then go and unlock the phone again? I read a number of threads about 'the new radio' which I assume is software to improve the phone or WIFI. Am I missing out?
Thanks
Frank
Michigan

I don't think you are missing out on anything to be honest. I did update mine and reroot without any issues, but can't really tell a difference. I would still do it so I can have the latest update on my phone since this one doesn't lock anything that we can't get back into.
Sent from my SCH-I535 using xda premium

There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.

sfobrien said:
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
Click to expand...
Click to collapse
Thanks for the reply. Will that break either my root or unlock (actually, I am not sure what state this phone is at since I did not do it -- I do find SuperSU in APPS, and have granted SuperUser to programs like Titanium Pro but there is nothing for CWM or other ROM managers...)?
Frank

If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.

sfobrien said:
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
Click to expand...
Click to collapse
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank

FMinMI said:
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
Click to expand...
Click to collapse
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.

I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?

andimanium said:
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
Click to expand...
Click to collapse
The only way to get stock HE currently is OTA.

sfobrien said:
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
Click to expand...
Click to collapse
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank

FMinMI said:
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
Click to expand...
Click to collapse
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247

Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.

prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
Thanks forgot about GooManager.

sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Click to expand...
Click to collapse
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank

prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank

FMinMI said:
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
Click to expand...
Click to collapse
It is personal choice. I have not had any problems with it and have been running since device was released for pre-order. I run whatever recovery seems to be most stable for the device. CWM for Tbolt. Amon Ra for Rezound. And now TWRP for S3. Have seen more bricks and failed flashes contributed to CWM so I stick with TWRP.

help
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse

FMinMI said:
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
Click to expand...
Click to collapse
The OTA installed with a custom recovery installed? Interesting. Usually OTA's fail if anything but stock recovery is installed. I only lost root but restored root with OTA Rootkeeper with stock recovery. Good to know that custom recovery can be installed and still get OTAs!

masonjb said:
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
Boot loader is locked.
Click to expand...
Click to collapse

prdog1 said:
masonjb said:
Boot loader is locked.
Click to expand...
Click to collapse
OK, I used EZ Unlock 1.2 and it said "unlocked" is there a way to know for sure before flashing if it is unlocked?
Thanks!
Click to expand...
Click to collapse

Something just not right in my attempt to flash roms.

About to tear my hair out at its roots trying to get this thing up to Jellybean. I bought it being told it was Jellybean capable but it had not been upgraded yet and all I had to do was go to the Asus site and get the files.
Well I go to the asus site and sure enough I download the file but thenit does not mention how to do the upgrade process. So I then go to - http://forums.androidcentral.com/an...-jelly-bean-asus-infinity-tf700t-minutes.html and this tells me to get the file needed to make it a specific file name and then do the reboot into the regular bootloader.
Well this worked like a hill of beans. I kept getting an error about the signature being invalid though I downloaded it off the ASUS site and I tried downloading the file three different ways (at work) on my phone and off my home Cablemodem) so if its a file problem its a file problem on the hosted site Asus is using.
I then used the unlocker and I unlocked my Asus it even shows it is unlocked every time it unboots so this part I know I did right.
I then ran DebugfsRoot_Generic_v2.3.zip from the link here - http://dottech.org/78441/how-to-root-asus-transformer-pad-infinity-tf700-debugfs-method-guide/ - and it said that it gave me root access on the OS installed. I however downloaded SU and RootChecker both which indicated I did not have root.
So then I decided if I was going to do this I would go full gusto. So I got a CWM GUI from http://forum.xda-developers.com/showthread.php?t=2094746 because I use CWM on my phones and figured if I stuck with the gui version of this I would be fairly competent on doing a rom replacement.
So then I downloaded a couple of roms from here - http://forum.xda-developers.com/showthread.php?t=1834521
as well as the SU that can be flashed. before boot up but I seem to still not to be able to get root (though the tool I used indicated I have it) on the current system.
The problem I have right now is rigt now anything I try and load from my sd card that is a zip shows -
E: Can't Open /sdcard/filename.zip
(bad)
Installation aborted.
For Filename.zip I have tried CWM-SuperSU-v0.99.zip from http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip as well as multiple ROM files from http://forum.xda-developers.com/showthread.php?t=1834521 as well as a couple from Asus
Things i know 1) I have correct USB from the Tablet to the PC this is evident because I was able to update the bootloader to the CWM GUI. 2) The MicroSD card is a 4 gb card and it works just fine. I have used it in my computer many times and I can open and copy and move files just fine on it any which way. 3) I am unsure as to why DebugfsRoot_Generic_v2.3.zip indicated it was all Rooted but then rootchecker is not showing it as rooted.
Is the fact I don't have Root the main reason for the files not being able to be opened? If so is there a better TF700T root program out there?

So for my clarification you want Jelly Bean rooted?
Is this correct?

Although it could be risky, you can actually toggle file system hashing verifications off in CWM. Make absolutely sure that the file downloaded correctly by verifying the MD5 yourself, other wise you could end up with a brick of the same value but even less practical use than the one you currently have.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.
---------- Post added at 12:50 PM ---------- Previous post was at 12:42 PM ----------
StumpedTechy said:
About to tear my hair out at its roots trying to get this thing up to Jellybean. I bought it being told it was Jellybean capable but it had not been upgraded yet and all I had to do was go to the Asus site and get the files.
Click to expand...
Click to collapse
To answer Thats_OK's question: I read this to mean that the 700 is still ICS, and he wants to get JB on there.
1) I have correct USB from the Tablet to the PC this is evident because I was able to update the bootloader to the CWM GUI.
Click to expand...
Click to collapse
Just to correct a minor error in terminology, just to get it straight: CWM is a recovery, and not a bootloader nor a "GUI" to the bootloader.
2) The MicroSD card is a 4 gb card and it works just fine. I have used it in my computer many times and I can open and copy and move files just fine on it any which way.
Click to expand...
Click to collapse
Not thT IT SEEMS TO BE THE ROOT Cuse here, but what filesystem is it formatted to?
3) I am unsure as to why DebugfsRoot_Generic_v2.3.zip indicated it was all Rooted but then rootchecker is not showing it as rooted.
Click to expand...
Click to collapse
I do not have a clue either -- the script should do everything for you and you should not have to undertake any action afterwards.
Is the fact I don't have Root the main reason for the files not being able to be opened?
Click to expand...
Click to collapse
Nope, an unlocked bootloader and a suitable recovery is all you need. Once those two are in place and working correctly, you should be able to flash anything. Rooting pertains to the access granted to the filesystem once you're 'inside', i.e. with the tablet running the ROM installed.
If so is there a better TF700T root program out there?
Click to expand...
Click to collapse
Nah, this works for pretty much anyone. I've had the error of "bad installation" a few times as well, and I toggled the hashing. Worked like a charm, although, as said, there is a minor risk involved if you do not keep your head cool and forget to verify manually. I haven't had this on the latest version of CWM, though.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.

Go to settings--> about tablet and provide the full build number for your device.

Thats OK said:
So for my clarification you want Jelly Bean rooted?
Is this correct?
Click to expand...
Click to collapse
I want Jellybean, roooted isn't so much a need but would be a plus.
Go to settings--> about tablet and provide the full build number for your device.
Click to expand...
Click to collapse
Build number is IML74K.US_epad-9.4.5.30-20120907
Not thT IT SEEMS TO BE THE ROOT Cuse here, but what filesystem is it formatted to?
Click to expand...
Click to collapse
The card is formatted to fat32
I've had the error of "bad installation" a few times as well, and I toggled the hashing.
Click to expand...
Click to collapse
I am not seeing anythign for hashing i am seeing signiture varification but with this enabled or disabled it is not changing the error I am getting.

If you just want JellyBean have you tried looking here? >>> http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1

Thats OK said:
If you just want JellyBean have you tried looking here? >>> http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Click to expand...
Click to collapse
I appreciate the link but did you read this part of my post?
Well I go to the asus site and sure enough I download the file but thenit does not mention how to do the upgrade process. So I then go to - http://forums.androidcentral.com/and...t-minutes.html and this tells me to get the file needed to make it a specific file name and then do the reboot into the regular bootloader.
Click to expand...
Click to collapse
I have already followed these instructions multiple times and each time it is giving me errors about the files being invalid or something of the sort.
I have tried about 4 different roms to load and each time I get bad file indicators even after comparing md5s and verifying the files are okay.
Is there any way to wipe this thing 100% and just load something on fresh?

StumpedTechy said:
I appreciate the link but did you read this part of my post?
I have already followed these instructions multiple times and each time it is giving me errors about the files being invalid or something of the sort.
I have tried about 4 different roms to load and each time I get bad file indicators even after comparing md5s and verifying the files are okay.
Is there any way to wipe this thing 100% and just load something on fresh?
Click to expand...
Click to collapse
Hmmm..Guess I'm not catching what you have done.
When you downloaded from the Asus website did you rename the file inside the zip to: EP201_768_SDUPDATE.zip then place this on your microSD?
Also I don't see any mention of ADB to push files to the tablet.
Sorry for my confusion.
Just not understanding where your at.
It is possible to wipe the internal SD card (eMMC) memory using TWRP...yet I'd wait until we get things sorted.

Let me go over what I did and what didn't work and let me go over what I finally did that did work now that I have mine all upgraded.
Didn't work -Scenario 1 -
Go into Settings->About Tablet-> System update this did absolutely nothing for getting me jellybean it just sat at a connecting screen that gave me nothing.
Didn't work -Scenario 2 -
Straight from the last link you provided -
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
(when I reached number 8 nothing happened automatically and I had to use the blue screened system recovery and when I pointed it to the SD file it told me it was a bad file.)
Didn't work -Scenario 3 -
Loaded
Transformer ADB Tool v6 and then loaded CWM GUI and then tried loading different rom from all over the place Asus main site, and all over the Index site here for different roms. http://forum.xda-developers.com/showthread.php?t=1834521
Finally however I finally made it work -
I am not sure why ALL the other ways did not work but on mine this is what I had to do.
1) From my first post I got the program from Asus that did the Unlocker I ran that from the Asus site.
2) From the first post I installed CWM GUI and I installed that.
3) From the index site I downloaded Stock Rooted Odex 10.4.4.23 to a USB stick - mainly because it says its rooted and I don't have to worry about rooting it AND I don't mind being .02 revisions behind.
4) I did an MD5 check vrs the download verified all was correct.
5) Tried to install from the MicroSD card and it failed yet again same errors as before.
6) On a whim I rebooted the TF700T and I copied the Stock Rooted Odex 10.4.4.23 to the device directly.
7) I booted to CWM GUI again and this time it installed when I selected to load from the internal SD.
8) I reloaded all my apps on the top.
9) I then loaded the apk of flash that "isn't supported" but works well enough on JB even on my phone.
So basically it would not install from my MicroSD though everything said it should but it would work fine from the internal memory.
This is with me using 2 different MicroSD cards and both are known working ones out of current phones I use all the time.
So I am now up to Jellybean and I am sporting all I needed to be upgraded for. Thanks for the attempts but it was just my constant tenacity that got me through this process.

Sounds like you have loaded my stock rooted rom. Which means you will still be on the old ice cream sandwich bootloader. Recommend you flash the JellyBean bootloaderfrom one of my threads in the ddevelopment section.
The reason your ota Asus updates failed is because you were already unlocked.

sbdags said:
The reason your ota Asus updates failed is because you were already unlocked.
Click to expand...
Click to collapse
Good point. Any idea why the other ROMs were failing as well?
@OP: now you have found a way that works, I suggest to try CROMI.

sbdags said:
Sounds like you have loaded my stock rooted rom. Which means you will still be on the old ice cream sandwich bootloader. Recommend you flash the JellyBean bootloaderfrom one of my threads in the ddevelopment section.
The reason your ota Asus updates failed is because you were already unlocked.
Click to expand...
Click to collapse
Ugh so I actually just made this worse? Basically since I did Stock Rooted Odex 10.4.4.23 over the version 9 ICS I am still running version 9ICSwith files over the top that are from 10.4.4.23 making it now some mixture of the two? So confused because I thought when I did a rom upgrade it wiped out the old and put in the new? it is showing the right version in Settings and it is acting right with what Jellybean should be doing so I am a lot confused right now.

StumpedTechy said:
Ugh so I actually just made this worse? Basically since I did Stock Rooted Odex 10.4.4.23 over the version 9 ICS I am still running version 9ICSwith files over the top that are from 10.4.4.23 making it now some mixture of the two? So confused because I thought when I did a rom upgrade it wiped out the old and put in the new? it is showing the right version in Settings and it is acting right with what Jellybean should be doing so I am a lot confused right now.
Click to expand...
Click to collapse
boot into recovery, when you see 4 icons, take a look at the second line (white text), it should say the version of your bootloader (1.00e is JB bootloader and 2.00e is ICS), then next to it is your JB or ICS version.
What sdbags said is when you flash a premade rom from XDA, it only included the ROM/kernel, but no bootloader. The only way is to flash the full firmware download from Asus site which included everything and bootloader is one of them.

buhohitr said:
boot into recovery, when you see 4 icons, take a look at the second line (white text), it should say the version of your bootloader (1.00e is JB bootloader and 2.00e is ICS), then next to it is your JB or ICS version.
What sdbags said is when you flash a premade rom from XDA, it only included the ROM/kernel, but no bootloader. The only way is to flash the full firmware download from Asus site which included everything and bootloader is one of them.
Click to expand...
Click to collapse
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.

StumpedTechy said:
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.
Click to expand...
Click to collapse
You could flash just JB bootloader with custom recovery from here: http://forum.xda-developers.com/showthread.php?t=2049274

StumpedTechy said:
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.
Click to expand...
Click to collapse
I uploaded sbdags' version I used to DropBox for you: https://www.dropbox.com/s/js0m8nas00ts95h/tf700t-WW-JB-bootloader-only.zip
It's just a matter of flashing this (and update your recovery, if applicable), and then reflash any ROM you'd like.
https://www.dropbox.com/s/js0m8nas00ts95h/tf700t-WW-JB-bootloader-only.zip

Thanks guys I went ahead I went ahead and downloaded it from the link right on the website that sbdags was talking about just did a quick forum search and found the proper JB bootloader. So now I have a CWM GUI recover, JB bootloader and the sdbags stock rooted JB rom on it.
Now I know this is a loaded question and someone has already mentioned CleanROM Inheritance 3.2
But are there any clear cut "great" JB roms that run pretty much flawlessly on the TF700T that are prerooted? Just checking because as I mentioned I have tried quite a few roms on my Samsung S2 and used AOKP, SuperNexus, and am now on ShoStock3. Are the roms on the TF700Ts about the same in "feel" to their galaxy s counterparts? E.G. AOSP TF700T like a AOKP Galaxy S2? (assuming AOSP and AOKP are the same developer?
Thanks for everyone sticking with me through this. This has been such a learning curve over my phone which was simply install CWM (non gui) and download the rom and then flash. Didn't have to worry about unlocking anything, didn't have to worry about where I was installing the rom from and all that.

StumpedTechy said:
Thanks guys I went ahead I went ahead and downloaded it from the link right on the website that sbdags was talking about just did a quick forum search and found the proper JB bootloader. So now I have a CWM GUI recover, JB bootloader and the sdbags stock rooted JB rom on it.
Click to expand...
Click to collapse
Good job -- wherever you got it from, it served you well. I'll keep the JB bootloader on that DropBox link for a while so others can benefit from it too.
Now I know this is a loaded question and someone has already mentioned CleanROM Inheritance 3.2
Click to expand...
Click to collapse
Yup.
But are there any clear cut "great" JB roms that run pretty much flawlessly on the TF700T that are prerooted?
Click to expand...
Click to collapse
Pretty much all of them are preooted, but in my opinion, none of them is as smooth as CROMI. BBB7 has been quite a bufggy experience for most of the people that tried it (or so I gather from the thread), and although the CM team is making nice progress on their 10.x version, some minor niggles remain (and sometimes resurface, such as shortcut keys on the dock being broken every once in a while). Also, CROMI is developed actively in the meantime as well, and you can take the mods with it that disable those annoying notifications.
Just checking because as I mentioned I have tried quite a few roms on my Samsung S2 and used AOKP, SuperNexus, and am now on ShoStock3.
Click to expand...
Click to collapse
I agree that the SGS2 was a breeze to flash compared to the TF700 -- I was in the same boat as you. Flashed away without a care, then had to learn how to do it anew with the Infinity.
Are the roms on the TF700Ts about the same in "feel" to their galaxy s counterparts? E.G. AOSP TF700T like a AOKP Galaxy S2? (assuming AOSP and AOKP are the same developer?)
Click to expand...
Click to collapse
The differences are greater, because the TF700 has a lot of pixels to push and therefore its hardware is more hard-pressed than the SGS2's. The Exynos in the SGS2 is a VERY good chip, so it handles itself quite nicely in lots of scenarios. The Tegra3, I am pained to say, has impressed me less in everyday use than the numbers on paper did. With CROMI, it's pretty good, so I'm happy as it is now, but it should have been better out-of-the-box.
Thanks for everyone sticking with me through this. This has been such a learning curve over my phone which was simply install CWM (non gui) and download the rom and then flash. Didn't have to worry about unlocking anything, didn't have to worry about where I was installing the rom from and all that.
Click to expand...
Click to collapse
All I worried about was that darned yellow triangle. Thanks to Chainfire we could disable that too, so I was a happy camper.