Database Info

[GUIDE] Official [unroot] guide here

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

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

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

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

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

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

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

worked great, and like the profile pic

Added to ultimate thread. Nice job.

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

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

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

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

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

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

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

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

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

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

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

[Q] First-time rooting questions from a noobie

I've never rooted a device, but have found an app I need that requires root access. So, before going through with the process, I just want to cover my bases to make sure I don't end up with a bricked device. So, first, a few questions:
- Is unlocking the bootloader the same thing as rooting? Are the terms synonymous, or are they two separate things? If the latter, which comes first?
- Do I need to back up my apps somewhere before going through the process? In other words, does rooting wipe the phone? If so, can I still download the apps that are stored in "My Apps" in Google Play?
- After rooting, will I still have access to and be able to download apps from Play?
- Does rooting make the device more vulnerable to viruses and malware attacks? No change from unrooted?
- Are there any general risks or drawbacks to rooting (aside from the potential of bricking the device)? Any standard functionality I lose by rooting?
Finally, I found ChainFire's root process. Seems to be pretty simple/straightforward. Is that all I need to do to gain root access? Anything else I should be sure to do?
Thanks!

Have you read the stickies at the top of this forum and the top of general? All your answers are there.

flick0416 said:
I've never rooted a device, but have found an app I need that requires root access. So, before going through with the process, I just want to cover my bases to make sure I don't end up with a bricked device. So, first, a few questions:
- Is unlocking the bootloader the same thing as rooting? Are the terms synonymous, or are they two separate things? If the latter, which comes first?
- Do I need to back up my apps somewhere before going through the process? In other words, does rooting wipe the phone? If so, can I still download the apps that are stored in "My Apps" in Google Play?
- After rooting, will I still have access to and be able to download apps from Play?
- Does rooting make the device more vulnerable to viruses and malware attacks? No change from unrooted?
- Are there any general risks or drawbacks to rooting (aside from the potential of bricking the device)? Any standard functionality I lose by rooting?
Finally, I found ChainFire's root process. Seems to be pretty simple/straightforward. Is that all I need to do to gain root access? Anything else I should be sure to do?
Thanks!
Click to expand...
Click to collapse
1. Unlocking the bootloader is just that - giving you access to the partitions on the phone. Gaining root access is like having administrator privileges on a Windows PC - you can install/do anything to the OS
2. Unlocking the bootloader wipes the phone, rooting does not (as the phone is already unlocked)
3. Yes, although some apps don't work on a rooted phone
4. Of sorts, yes, but so long as you're careful you'll be OK
5. Not really, and you'll usually gain functionality if you move to a custom ROM

I hadn't
rootSU said:
Have you read the stickies at the top of this forum and the top of general? All your answers are there.
Click to expand...
Click to collapse
I hadn't, but since you pointed it out, I'm finding abaaaabbbb63's FAQ post to be helpful. Thanks for the direction.

flick0416 said:
I hadn't, but since you pointed it out, I'm finding abaaaabbbb63's FAQ post to be helpful. Thanks for the direction.
Click to expand...
Click to collapse
No probs.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

Thanks
EddyOS said:
1. Unlocking the bootloader is just that - giving you access to the partitions on the phone. Gaining root access is like having administrator privileges on a Windows PC - you can install/do anything to the OS
2. Unlocking the bootloader wipes the phone, rooting does not (as the phone is already unlocked)
3. Yes, although some apps don't work on a rooted phone
4. Of sorts, yes, but so long as you're careful you'll be OK
5. Not really, and you'll usually gain functionality if you move to a custom ROM
Click to expand...
Click to collapse
Thanks for the info. Also, regarding #3, how do you tell if an app <i>won't</i> work on a rooted phone? Just trial and error?

Also
Is ChainFire's process the easiest way for me to get what I need (namely, root access to download an app)?

flick0416 said:
Is ChainFire's process the easiest way for me to get what I need (namely, root access to download an app)?
Click to expand...
Click to collapse
I have always done the following:
1. Unlock bootloader (make sure you back up any files on your phone before hand as they WILL be deleted)
2. Flash CWM/TWRP (I've always been a CWM man myself, but it's your choice) through fastboot using 'fastboot flash recovery recovery.img' - where 'recovery.img' is the name of the file you downloaded. I always rename mine 'recovery' purely for ease of use
3. Boot the phone and copy this to the phones memory - http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip?retrieve_file=1
4. Boot into CWM/TWRP and flash the file you've just copied to the phone
5. Reboot and enjoy!

Haha
EddyOS said:
I have always done the following:
1. Unlock bootloader (make sure you back up any files on your phone before hand as they WILL be deleted)
2. Flash CWM/TWRP (I've always been a CWM man myself, but it's your choice)
3. Boot the phone and copy this to the phones memory - ttp://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip?retrieve_file=1
4. Boot into CWM/TWRP and flash the file you've just copied to the phone
5. Reboot and enjoy!
Click to expand...
Click to collapse
Haha, that's way above my head. I'll try to break down what you said:
1. This is done by turning the phone off, then holding Power + Volume down, correct?
2. Are these custom ROM's? I don't really care about a custom ROM right now, just having root access.
3. When you say Boot, do you mean turn it off again, then turn back on normally? Also, would I turn it off again after copying the SuperSU file?
4. No idea what you mean by this.
5. Getting there slowly...

flick0416 said:
Haha, that's way above my head. I'll try to break down what you said:
1. This is done by turning the phone off, then holding Power + Volume down, correct?
2. Are these custom ROM's? I don't really care about a custom ROM right now, just having root access.
3. When you say Boot, do you mean turn it off again, then turn back on normally? Also, would I turn it off again after copying the SuperSU file?
4. No idea what you mean by this.
5. Getting there slowly...
Click to expand...
Click to collapse
1. Check this thread out - it outlines the entire process http://forum.xda-developers.com/showthread.php?t=2507905
2. No - that is custom recovery that you need to perform nandroid backups (full system backup)
3. Yes
4. Go back into your newly installed recovery (step 2) to install the SuperSU file
But again, check out the link I provided above - fairly straightforward.

jj14 said:
1. Check this thread out - it outlines the entire process http://forum.xda-developers.com/showthread.php?t=2507905
2. No - that is custom recovery that you need to perform nandroid backups (full system backup)
3. Yes
4. Go back into your newly installed recovery (step 2) to install the SuperSU file
But again, check out the link I provided above - fairly straightforward.
Click to expand...
Click to collapse
OK cool, I think it's all starting to make sense. I could really accomplish the same end result without flashing a custom recovery, right? I most likely will flash a custom recovery, but as I understand it, a customer recovery isn't an essential part of the process, correct? The essentials are:
1) Unlock bootloader
2) Copy the SuperSU file to the phone
3) Boot back into recovery mode, flash the SuperSU file
Is that accurate?

flick0416 said:
OK cool, I think it's all starting to make sense. I could really accomplish the same end result without flashing a custom recovery, right? I most likely will flash a custom recovery, but as I understand it, a customer recovery isn't an essential part of the process, correct? The essentials are:
1) Unlock bootloader
2) Copy the SuperSU file to the phone
3) Boot back into recovery mode, flash the SuperSU file
Is that accurate?
Click to expand...
Click to collapse
That is correct. Only 'issue' is that you won't be able to take a full system backup (aka nandroid) before rooting.
(make sure that after you start your phone up after step 3, and get your accounts set up, update the SU app from the play store - new vulnerabilities were fixed)

jj14 said:
That is correct. Only 'issue' is that you won't be able to take a full system backup (aka nandroid) before rooting.
(make sure that after you start your phone up after step 3, and get your accounts set up, update the SU app from the play store - new vulnerabilities were fixed)
Click to expand...
Click to collapse
Cool, thanks. Would it be correct to say that Chainfire's thing automated steps 2 and 3?

flick0416 said:
Cool, thanks. Would it be correct to say that Chainfire's thing automated steps 2 and 3?
Click to expand...
Click to collapse
not sure which thing you are referring to - chainfire developed the SU app. Not sure what automation you are referring to.
In my opinion, run those commands manually - not that complicated, and you know what it is doing

jj14 said:
not sure which thing you are referring to - chainfire developed the SU app. Not sure what automation you are referring to.
In my opinion, run those commands manually - not that complicated, and you know what it is doing
Click to expand...
Click to collapse
This. The CF-Auto Root.

flick0416 said:
This.
Click to expand...
Click to collapse
yep - it should

jj14 said:
yep - it should
Click to expand...
Click to collapse
Alright cool, thanks. Now that I feel like I have a better conceptual understanding of what each step is doing, I think I'd rather go through it manually, too.

flick0416 said:
Alright cool, thanks. Now that I feel like I have a better conceptual understanding of what each step is doing, I think I'd rather go through it manually, too.
Click to expand...
Click to collapse
This is the important thing - read up and make sure you understand what you're doing and be comfortable with it all. Once you do it a few times it becomes second nature

an advice which came useful to me:
use original usb cable!
i've spent hours by trying to install custom recovery after unlocking bootloader.. tried number of times but having the error logo while booting to recovery.. then switched to original usb cable and everything worked fine at first attempt.
maybe this will helps =)

Recovery is important
I'd suggest this procedure:
1) Unlock bootloader
2) Copy the SuperSU file to the phone
3) Boot back into recovery mode, flash the SuperSU file
4) Flash a recoverylike cwm

Rooting the TF300TG

Hello, I own a TF300TG which mounts 4.2.1 android version, 10.6.2.11 fw.
I'm trying to root it with SRS root (eset32 detected it as trojan, btw) but it keeps failing.
VROOT doesn't even install on my PC (i don't know why, it's written in chinese).
how can I obtain root privileges?

xperiaL said:
Hello, I own a TF300TG which mounts 4.2.1 android version, 10.6.2.11 fw.
I'm trying to root it with SRS root (eset32 detected it as trojan, btw) but it keeps failing.
VROOT doesn't even install on my PC (i don't know why, it's written in chinese).
how can I obtain root privileges?
Click to expand...
Click to collapse
The easiest way is to unlock your bootloader, install a custom recovery like TWRP and then flash the SuperSU ZIP from that recovery.
Make sure you double-check that you picked the right recovery version for your bootloader.
Sent from my TF300T using Tapatalk

I've found some threads linking to twrp but the link shared in them refer to the tf300t, not tg. I mean this. Is it the same? I'm worried about bricking my device, because it isn't only mine
so where can I get the correct files to download for my tablet?
sorry if Iook like a noob but my phone was waaaaaayyyy easier to root...

xperiaL said:
I've found some threads linking to twrp but the link shared in them refer to the tf300t, not tg. I mean this. Is it the same? I'm worried about bricking my device, because it isn't only mine
so where can I get the correct files to download for my tablet?
sorry if Iook like a noob but my phone was waaaaaayyyy easier to root...
Click to expand...
Click to collapse
Yeah, it is tricky to pick the right recovery version with all those incompatible bootloaders and the new KitKat ROMs needing yet another one to flash properly.
There are other options for rooting, search for motochopper and similar tools, but personally I don't regard them as simple and some of them have been reported to contain malware.
To help you find the right recovery version, first need to know the version of your bootloader. You can find it at the top left of the bootloader screen. The interesting part are the numbers starting with 10. or 9. for really old ones. Then need to know, what ROM you want to root. Using stock Asus ROM?
You can safely use a recovery for TF300T; it is much more important to pick the right version for your bootloader.
Sent from my TF300T using Tapatalk

I've found this guide (-> http://forum.xda-developers.com/showthread.php?t=2617298) which seems pretty good, but the version reported working is WW_epad-10.6.2.10, while mine is 10.6.2.11-20131213
what do you suggest me to do? Go ahead and try it or hope one day a more specific version will be released?

xperiaL said:
I've found this guide (-> http://forum.xda-developers.com/showthread.php?t=2617298) which seems pretty good, but the version reported working is WW_epad-10.6.2.10, while mine is 10.6.2.11-20131213
what do you suggest me to do? Go ahead and try it or hope one day a more specific version will be released?
Click to expand...
Click to collapse
The guide looks good to me and should work fine for your boot loader.
Instead of the attached TWRP, you can safely use any TWRP for the TF300T, as long as it has -42 in the name. 2.6.0.0 might be a little buggy, not sure.
Sent from my TF300T using Tapatalk

xperiaL said:
I've found some threads linking to twrp but the link shared in them refer to the tf300t, not tg. I mean this. Is it the same? I'm worried about bricking my device, because it isn't only mine
so where can I get the correct files to download for my tablet?
sorry if Iook like a noob but my phone was waaaaaayyyy easier to root...
Click to expand...
Click to collapse
Just to confirm that i have TF300TG with JB 4.2.1 and my bootloader is 10.6.2.11 and i have used the link that you quoted in this reply (this) and all work for me just fine.:good:

Kingo (google it) apparently works. so if you dont want to unlock the bootloader and whatnot, try that.

thanks for your answers, first I will try kingo and if it doesn't work I will try the method on the link I posted!

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...

TF700KL root + new Rom?

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

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

Thx for ignore me

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

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

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

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

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

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

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

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

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

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

help pliz

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

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

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

I can't

I mean it doesn't get to the next menu

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