Database Info

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

Rooting my tablet on latest firmware WW 10.4.2.18

HI
Iv finally desided to do something about my slow-ass stock TF300T. I have been reading a thread by some guy asking the same question except that he has 10.4.2.18. Can i do the same thing that is said in that post? If not, any tips?
Post: http://forum.xda-developers.com/showthread.php?t=2029364
EDIT, been reading that i cant follow that post because im using the WW and not US... Any tuts for WW version?
EDIT 2, i have been reading a tutorial that shows how to switch from WW to US, but its not explained easily enough for me to understand, as im fairly new to this

grimsonfart said:
HI
Iv finally desided to do something about my slow-ass stock TF300T. I have been reading a thread by some guy asking the same question except that he has 10.4.2.18. Can i do the same thing that is said in that post? If not, any tips?
Post: http://forum.xda-developers.com/showthread.php?t=2029364
Click to expand...
Click to collapse
The process is exactly the same since you are already on stock JB. Just follow the guide and if you get stuck just ask.

Ramrod421 said:
The process is exactly the same since you are already on stock JB. Just follow the guide and if you get stuck just ask.
Click to expand...
Click to collapse
Thanks for reply, but just found out that because i dont use the US version this might not work, im on WW

grimsonfart said:
Thanks for reply, but just found out that because i dont use the US version this might not work, im on WW
Click to expand...
Click to collapse
I'm on WW too. Worked for me.

Ramrod421 said:
I'm on WW too. Worked for me.
Click to expand...
Click to collapse
OK thank you il report back

Installing recovery worked
Rooting worked
Installing CleanRom 2.7 WORKED!

grimsonfart said:
Installing recovery worked
Rooting worked
Installing CleanRom 2.7 WORKED!
Click to expand...
Click to collapse
Nice! I'm glad it worked for you. Enjoy your new tablet!

I want to root using this method: http://forum.xda-developers.com/showthread.php?t=1845377
"Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)"
if i press Shift + right mouse in the folder I don't get a command prompt. Do I need to select both files and the run as administrator? I don't get the command promt option.
I am running Windows 8
EDIT: Shift key don't do anything..

Can you please share your stock build.prop file? Important for me

Lirkaren said:
I want to root using this method: http://forum.xda-developers.com/showthread.php?t=1845377
"Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)"
if i press Shift + right mouse in the folder I don't get a command prompt. Do I need to select both files and the run as administrator? I don't get the command promt option.
I am running Windows 8
EDIT: Shift key don't do anything..
Click to expand...
Click to collapse
When you have your fastboot folder open press shift and then right click. One of the options in the menu should be "open command window here". That should do it unless Windows 8 has changed this.
Try the link at the top of this post.

TF300T UK Model Build 10.4.2.18
I apologise if help is on another thread which I could not find.
I cannot find on any other forum a hard and fast answer.
My TF300T is a UK model.
It has arrived with Build 10.4.2.18 already installed.
I want to root it and install a custom ROM. Like many others I want to remover some of the pre-installed apps such as Chrome.
I've rooted 4 HTC phones with no problem but I just cannot find a hard and fast post with instructions to rid this 10.4.2.18 of its factory installed ROM.
I have unlocked the device using the ASUS website.
I appreciate your feedback.
Regards

easy
just dl this file
http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.2.2.0-tf300t-JB.blob
TWRP Recovery for JB Bootloader. Its an older Versions which runs without any problems. The 2.3 or CWM are giving many problems to many User, so i recommend the 2.2
Take a look here
http://www.teamw.in/project/twrp2/97
on how to installe via adb or fastboot.
After that you can just go into TWRP recovery with turning on while Power and Vol- pressed at the same time
Than switch to RCK with Vol- and choose it with Vol+.
Once in Recovery you can install all JB Bootloader compatible Roms like you are used to

sthEn said:
Can you please share your stock build.prop file? Important for me
Click to expand...
Click to collapse
Not exactly how i can do that, and now that im unlocked, rooted and have a custom rom im dont think that its "stock" anymore. If i still have what you need il do my best to get it

Ramrod421 said:
Nice! I'm glad it worked for you. Enjoy your new tablet!
Click to expand...
Click to collapse
Thanks So far the performance is just so much better (especially surfing using Chrome and playing games), but performance mode can make my tablet crash (i installed the Infinitys 1.8Ghz kernel so normal i guess?), especially when doing heavy stuff like benchmarking.

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.

ASUS TF700T unlock and root JB 4.2.1 stock

FOR ANYONE THAT EITHER JUST BOUGHT THE TF700 OR UPGRADED OTA TO 4.2.1 JB AND WANTS TO UNLOCK AND/OR ROOT THE DEVICE
LINKS WILL BE AVAILABLE.
WARNING: UNLOCKING THE DEVICE WILL VOID YOUR WARRANTY WITH ASUS, I DONT KNOW IF IT WILL VOID IT WITH SQUARETRADE OR OTHER WARRANTIES. ALSO, I AM NOT RESPONSIBLE FOR ANY DAMAGES TO ANY TABLET, EVEN THOUGH I HAD NO TROUBLE OR PROBLEMS WHATSOEVER.
(ROOTING IS REVERSIBLE AND DOES NOT VOID WARRANTY)
TO UNLOCK
TO UNLOCK THE DEVICE, GO AND USE THE ASUS UNLOCK TOOL FROM THEIR WEBSITE.
CLICK THE LINK PROVIDED
CHOOSE OS: ANDROID
UNDER "UTILITES" THE SECOND SAYS VERSION 7 ASUS UNLOCK TOOL (YES I'M AWARE IT SAYS FOR ICS ONLY BUT I HAVE TRIED IT AND IT WORKS WITH JB 4.2.1)
DOWNLOAD IT EITHER FROM THE TABLET ITSELF OR LOAD IT TO AN SD CARD.
IT IS AN APK FILE SO IT WILL INSTALL AS AN APP.
RUN IT, AND *SCROLL DOWN TO THE END* ON THE TERMS AND CONDITIONS, AND AGREE TO IT. THE TABLET WILL REBOOT AND ON THE TOP LEFT CORNER IT WILL SAY "UNLOCKING DEVICE" GIVE IT 5 MINS DONT FREAK OUT. ONCE DONE, IT WILL SAY "DEVICE UNLOCKED" AND THERE YOU GO. YOU'RE OFFICIALLY UNLOCKED!!
If you are going to install custom ROMS, after unlocking and rooting, you need to install TWRP. I suggest to install GOOMANAGER from the playstore and doin it from there. Just click on the right corner and choose install openrecovery script and choosing twrp.
LINK TO ASUS WEBSITE: http://support.asus.com/download.as...Infinity+TF700T&os=&hashedid=fq2B3oq64av1O95u
_________________________________________________________________________________________________________________
TO JUST ROOT YOUR DEVICE
TO ROOT YOUR DEVICE ON 4.2.1 JB
FIRST PREPARE YOUR TABLET,
GO TO SETTING, UNDER SYSTEM CLICK ON "DEVELOPER OPTIONS" AND MAKE SURE YOU HAVE CHECKED THE "USB DEBUGGING"
IF YOU DONT HAVE A"DEVELOPER OPTIONS" CLICK ON "ABOUT TABLET" AND WHERE IT SAYS "BUILD NUMBER" CLICK ON IT UNTIL IT SAYS " CONGRATULATIONS NOW YOU ARE A DEVELOPER" IT SHOULD BE AROUND 5-10 TIMES, AFTER THAT YOU SHOULD BE ABLE TO SEE THE "DEVELOPER OPTIONS ON THE LEFT" RIGHT ABOVE "ABOUT TABLET" (THEN ENABLE USB DEBUGGING"
NEXT, UNDER "PERSONAL" CLICK THE TAB THAT SAYS "SECURITY" AND ENABLE "UNKNOWN SOURCES"
ONCE DONE WITH THIS, CONNECT YOUR TABLET TO YOUR LAPTOP/PC
DOWNLOAD MOTOCHOPPER FROM THE LINK PROVIED
EXTRACT IT AND RUN THE FILE THAT SAYS "RUN"
ONCE YOU RUN IT JUST FOLLOW THE SIMPLE STEPS ON THE SCREEN
IF ALL GOES WELL, YOUR DEVICE SHOULD BE ROOTED AND YOU SHOULD HAVE SUPERSU INSTALLED
EDIT!: IF YOU UPGRADED OR YOUR TABLET CAME WITH BUILD NUMBER 10.6.1.14.10, MOTOCHOPPER WONT WORK TO ROOT. YOU WILL NEED TO DOWNGRADE TO 10.6.1.14.08 AND THEN ROOT WILL BE AVAILABLE
LINKS FOR MOTOCHOPPER:
http://www.mediafire.com/?f4lipgd1hh3jug2
(I ATTACHED THE LINK TO THIS FORUM AS WELL JUST IN CASE)
PLEASE ASK ANY AND ALL QUESTIONS I WILL BE GLADLY TO ANSWER THEM TO THE BEST OF MY KNOWLEDGE, IF NOT I WILL HELP YOU FIND THE ANSWER.
ALSO, I WOULD LIKE TO THANK ALL XDA FORUM MEMBERS AND DEV AND MODERATORS FOR HELPING ME LEARN.
SPECIAL THANKS TO
Tylorw1 said:
tylor
Click to expand...
Click to collapse
FOR GUIDING ME IN TIME OF NEED
inky2020 said:
inky
Click to expand...
Click to collapse
FOR HELPING
buhohitr said:
buhohitr
Click to expand...
Click to collapse
FOR HELPING FINDING OUT IT WORKS
Morlok8k said:
morlok8k
Click to expand...
Click to collapse
FOR PROVIDING DOWNLOAD LINKS TO MOTOCHOPPER

rickymh19 said:
YES I'M AWARE IT SAYS FOR ICS ONLY BUT I HAVE TRIED IT AND IT WORKS WITH JB 4.2.1
Click to expand...
Click to collapse
Unlock tool confirmed working on JB 4.2.1 - just unlocked the bootloader on my totally stock TF700T JB 4.2.1 (WW). Now to flash CROMI-X! :victory:

Stupid easy (locked-root)
Enable USB debugging.
Plug in TF700T.
Windows 7 loaded all of the drivers.
D/L the file.
Extract.
Double click run.bat.
Answer a couple of questions.
Root in under a minute.
:laugh::victory:

Thanks for the motochopper link. Worked perfect on my 4.2.1 tf700, could not have been easier.
Runs a whole lot better with all the bloat frozen and memory cache tweaks.

Thanks you for this. Noon here and will try your tutorial soon

Wont Root
Hey Haven't dont any rooting on the TF700 yet, so bear with me.
Did a 4.2 OTA update (stock)
Unlocked it,
Used Motochopper
But stuck on
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Help?
Thanks in Advance!

Gave you a thanks for the post.

darkskoliro said:
Hey Haven't dont any rooting on the TF700 yet, so bear with me.
Did a 4.2 OTA update (stock)
Unlocked it,
Used Motochopper
But stuck on
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Help?
Thanks in Advance!
Click to expand...
Click to collapse
when you're running motochopper, you get that message?
if so, make sure you have "usb debugging" enabled under setting>developer options.
also, try reinstalling the drivers for the tf700
connect it via usb, before running motochopper, on the folder of motochopper there is
a file that says "adb" run that before running the "run" file.
usually that message is for a bad driver or because adb isnt reading your tablet.
hope that helps keep me updated.

rickymh19 said:
when you're running motochopper, you get that message?
if so, make sure you have "usb debugging" enabled under setting>developer options.
also, try reinstalling the drivers for the tf700
connect it via usb, before running motochopper, on the folder of motochopper there is
a file that says "adb" run that before running the "run" file.
usually that message is for a bad driver or because adb isnt reading your tablet.
hope that helps keep me updated.
Click to expand...
Click to collapse
Hey thanks for the reply, but still nothing! :*(
I have done everything but install new drivers. (My drivers are working properly)
But is there a chance there are 4.2 drivers? Which might be the problem? Not sure..

darkskoliro said:
Hey thanks for the reply, but still nothing! :*(
I have done everything but install new drivers. (My drivers are working properly)
But is there a chance there are 4.2 drivers? Which might be the problem? Not sure..
Click to expand...
Click to collapse
Hmm...I would suggest deleting the drivers, and downloading the drivers from the Asus website. And then make sure your ADB can find your tablet. Run the adb file first and then the run file. You should have no problem. Try cold booting your device as well and make make sure you have usb debugging checked.
If this fails, the most probable solution would be going to another thread and downloading the debugfs tool for tf700. I'm not at my computer now so I can't give you the direct link. But if you search for it you'll find it. I did a while back.
Keep me updated.

That is the quickest and easiest root I've ever done on a device! Thanks for keeping it simple :good::good:

HI -
I followed the instructions on this thread and was ulocked/rooted in less than five minutes - installed TWRP - made a nandroid backup - then did something I am afraid was incredibly stupid. I was going to do a wipe per instructions before installing a ROM and I selected "Advanced" and wiped everything instead of just doing a factory wipe.
Now when powered on it is stuck at the ASUS initial screen.
Hoping this can be fixed - can anyone help me out.
Thanks!
Ted

tgatlinjr said:
HI -
I followed the instructions on this thread and was ulocked/rooted in less than five minutes - installed TWRP - made a nandroid backup - then did something I am afraid was incredibly stupid. I was going to do a wipe per instructions before installing a ROM and I selected "Advanced" and wiped everything instead of just doing a factory wipe.
Now when powered on it is stuck at the ASUS initial screen.
Hoping this can be fixed - can anyone help me out.
Thanks!
Ted
Click to expand...
Click to collapse
If you had a rom downloaded, you wiped it
Download the rom you want to flash to a microSD, insert it into your tablet, reboot into TWRP, select the microSD and install the zip.
Make sure you have a compatible recovery and rom combination.
What's your recovery version and what rom do you want to flash?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Thanks for this. Initially, I was stuck on adb not finding the device - I killed the batch file and then ran
Code:
adb devices
and sure enough, nothing there.
I had to manually uninstall the drivers and then let Windows find them again - this time there was an unknown device, and then Windows found the MTP device and loaded it.
Then it took all of 27 seconds from start to finish lol.
Thanks again - Now I owe Djrbliss yet another contribution....

berndblb said:
If you had a rom downloaded, you wiped it
Download the rom you want to flash to a microSD, insert it into your tablet, reboot into TWRP, select the microSD and install the zip.
Make sure you have a compatible recovery and rom combination.
What's your recovery version and what rom do you want to flash?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
tgatlinjr said:
HI -
I followed the instructions on this thread and was ulocked/rooted in less than five minutes - installed TWRP - made a nandroid backup - then did something I am afraid was incredibly stupid. I was going to do a wipe per instructions before installing a ROM and I selected "Advanced" and wiped everything instead of just doing a factory wipe.
Now when powered on it is stuck at the ASUS initial screen.
Hoping this can be fixed - can anyone help me out.
Thanks!
Ted
Click to expand...
Click to collapse
hey, sorry i took so long to reply, but like bern said, you're in no trouble. just do what he said and you should be fine.
just download the ROM you want or the stock rom of asus (which i wouldnt install. try cromix or parandroid or black bean theyre very good.)
put it on an sd card and boot to recovery. then the twrp should pop up, and install the rom.
if you need help on choosing the options let me know when you'll do it and ill be glad to guide you.

Thanks Everyone!
rickymh19 said:
hey, sorry i took so long to reply, but like bern said, you're in no trouble. just do what he said and you should be fine.
just download the ROM you want or the stock rom of asus (which i wouldnt install. try cromix or parandroid or black bean theyre very good.)
put it on an sd card and boot to recovery. then the twrp should pop up, and install the rom.
if you need help on choosing the options let me know when you'll do it and ill be glad to guide you.
Click to expand...
Click to collapse
Thanks for the replies?
I got every thing up and going again.
Ted

tgatlinjr said:
Thanks for the replies?
I got every thing up and going again.
Ted
Click to expand...
Click to collapse
good to hear.

Bee Waiting
I've been waiting for this..worked with my eyes closed. TF700T Locked and Rooted!!!

This worked great. Finally decided to root my tf700. I appreciate this thread so much.
Sent from my SCH-I605 using xda app-developers app

Awesome, super easy thanks!
Sent from my GT-N7000 using xda premium

Nvidia Shield- How Can I Avoid The Kill Switch?

I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...

treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)

If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.

I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...

Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.

Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.

Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...

You need to root to flash twrp?

EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.

amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.

oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing

oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?

Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...

says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.

l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?

l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.

frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....

Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...