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] Recovery error

Hey sorry i am new to the forums not new to rooting phones but i guess a tablet is all new ballgame i just received the asus transformer tf700t on ebay and tried to root it and it wont root as after i click into RCK it goes to installing system upate and then the red triangle android guy shows up saying error (i guess i cannot recovery mode the device either)
ok i was able to root my device but i am unable to install custom roms as my recovery boot im assuming is corrupt
Please note as i received it this way

Try this:
Boot Loop/No Boot Version (Can also be used to downgrade but always backup all apps and data.)
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
ASUS - Tablet & Mobile
The zips are under Tablet(your model), Downloads/Support. then under Android.
Also, they removed the 4.2.1 zips from their website. Here are Mirrors.
TF700 Zips (10.6.1.14.4)
Stock 4.2.1 US
Stock 4.2.1 US Mirror
Stock 4.2.1 WW
Stock 4.2.1 WW Mirror
Stock 4.2.1 TW
Stock 4.2.1 TW Mirror
I'll explain what your seeing a little bit more. The android guy on your back IS the stock recovery, it is not an interface. 10.6.1.14.4 is your your android version. 4.2.1 is the base, 10.6.1.14.4 is the package that ASUS creates and names it, so nothing is incorrect. Just try this method and it should get the tablet up and running.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Tylorw1 said:
Try this:
Boot Loop/No Boot Version (Can also be used to downgrade but always backup all apps and data.)
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Also, they removed the 4.2.1 zips from their website. Here are Mirrors.
I'll explain what your seeing a little bit more. The android guy on your back IS the stock recovery, it is not an interface. 10.6.1.14.4 is your your android version. 4.2.1 is the base, 10.6.1.14.4 is the package that ASUS creates and names it, so nothing is incorrect. Just try this method and it should get the tablet up and running.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
i didnt everything but as soon as i select RCK it says installing update and then it says error the tablet is working fine other than the recovery mode not working

darkcroc said:
i didnt everything but as soon as i select RCK it says installing update and then it says error the tablet is working fine other than the recovery mode not working
Click to expand...
Click to collapse
Error how? The android guy laying of his back? That is not an error. The stock recovery has NO interface, so you CANNOT go INTO the stock recovery. All the stock recovery can do is update if you have a ROM on your sdcard.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Tylorw1 said:
Error how? The android guy laying of his back? That is not an error. The stock recovery has NO interface, so you CANNOT go INTO the stock recovery. All the stock recovery can do is update if you have a ROM on your sdcard.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I dont know bro it shows the android guy on his back with the red triangle and underneath him it says "Error!" i don't understand why

darkcroc said:
I dont know bro it shows the android guy on his back with the red triangle and underneath him it says "Error!" i don't understand why
Click to expand...
Click to collapse
Then you didnt follow the instructions/naming properly. Try renaming it on a PC first then put it on the MicroSD card and doing the process. Also make sure you have the correct SKU and name down.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Tylorw1 said:
Then you didnt follow the instructions/naming properly. Try renaming it on a PC first then put it on the MicroSD card and doing the process. After make sure you have the correct SKU and name down.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
A common error is to download the file and rename it without extracting it first. Its a zip in a zip. The one inside is the one you need to rename, not the one you downloaded.
The other common error is not having FAT32 format for your MicroSD card, which is the Removable one, not the internal sdcard. When you get a MicroSD card out of the box, the standard format is exFAT which does not work for recovery (flashing ROMs or firmware).
The dead android means that your recovery cannot find the update.zip file in the root directory of your MicroSD card.

Tylorw1 said:
Then you didnt follow the instructions/naming properly. Try renaming it on a PC first then put it on the MicroSD card and doing the process. Also make sure you have the correct SKU and name down.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
well im sorry to say this method is not working i did everything u said to do and its not getting fixed bro and my micro is a fat32 just checked

darkcroc said:
well im sorry to say this method is not working i did everything u said to do and its not getting fixed bro and my micro is a fat32 just checked
Click to expand...
Click to collapse
well i did everything manually for the recovery and got twrp to work and rooted with motochopper so alls well that ends well thanks guys but i got it done on my own

darkcroc said:
well i did everything manually for the recovery and got twrp to work and rooted with motochopper so alls well that ends well thanks guys but i got it done on my own
Click to expand...
Click to collapse
That's great! Can you briefly outline what you did differently to make it work for you? It may be helpful for the "next guy".

elfaure said:
That's great! Can you briefly outline what you did differently to make it work for you? It may be helpful for the "next guy".
Click to expand...
Click to collapse
Looks to be he installed a custom recovery. However in the OP, he never mentioned of being unlocked. I thought he was fully stock, so it is an entirely different situation. So my answer to him was for people who were purely stock.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Tylorw1 said:
Looks to be he installed a custom recovery. However in the OP, he never mentioned of being unlocked. I thought he was fully stock, so it is an entirely different situation. So my answer to him was for people who were purely stock.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Gotcha. But he did mention in the OP that he was trying to install a custom rom, and that can only be done if unlocked. But it also looks like he added that statement as an edit after the OP. Weather or not he knew that is unclear. Makes it hard to help someone when you only get partial info from the user about their problem I agree.

elfaure said:
That's great! Can you briefly outline what you did differently to make it work for you? It may be helpful for the "next guy".
Click to expand...
Click to collapse
well i rooted the tablet with motochopper then downloaded goo manager into it after word i downloaded the Twrp Blob file (most recent) and then downloaded terminal emulator and typed su for super user and installed the blobs file threw it and rebooted and flashed cw rom onto it to verify it worked and wah la and yes i did unlock the device sorry for not inputing it (it wasnt working after i unlocked it either so thats when i decided to install custom recovery)

darkcroc said:
wah la
Click to expand...
Click to collapse
You mean "voilà"? </grammar nazi mode>
Your summary makes it look easy, which it would have been if you had supplied full information timely and upfront. Meh.

darkcroc said:
well i rooted the tablet with motochopper then downloaded goo manager into it after word i downloaded the Twrp Blob file (most recent) and then downloaded terminal emulator and typed su for super user and installed the blobs file threw it and rebooted and flashed cw rom onto it to verify it worked and wah la and yes i did unlock the device sorry for not inputing it (it wasnt working after i unlocked it either so thats when i decided to install custom recovery)
Click to expand...
Click to collapse
Sorry i hav the same problem. But can you tell me more specificity what code you typed in?

ivansong said:
Sorry i hav the same problem. But can you tell me more specificity what code you typed in?
Click to expand...
Click to collapse
Can you be a lot more specific please?
You have what problem? You did what and want to accomplish....??
And always mention what bootloader/recovery/rom you are currently running.

TF300T not recognizing keyboard /dock after update to 10.6.1.27.1-20130711

Not sure if this is the correct place to post my issue or not, but ever since updating to JOP4OD.us_epad 10.6.1.27.1-20130711 the tablet no longer recognizes the dock/keyboard when docked and charging no longer works when tablet is docked and charger is plugged into dock. Charges just fine when plugged directly into tablet.
TF300T - Stock - Locked - Unrooted.
Only thing I've noticed is when doing a Cold Boot the line of text at the top of the screen shows "Android cardhu-user" - "bootloader1.00e" - "key driver not found...booting os" - "start fastboot usb download protocol"
Not sure if that will help anyone, I'm wondering if I should download the update and try installing it again if that's even possible?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Did you try downgrading to the previous release? That might help...
______________________________
HTC Evo 4G LTE

aarsyl said:
Did you try downgrading to the previous release? That might help...
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I'm new to Asus Tablets, so I'm not sure how to do that!
Is there a way to do it that doesn't require using either fastboot or ADB?
Thank you for your response.

musthunt said:
I'm new to Asus Tablets, so I'm not sure how to do that!
Is there a way to do it that doesn't require using either fastboot or ADB?
Thank you for your response.
Click to expand...
Click to collapse
No problem at all. We're here to help.
Go to the ASUS support website (support.asus.com), and download the previous release of Android from the support page.
Then search for your device, and look for V10.6.1.15.3 of your variant (US, JP, CN, WW, TW). Unzip it once, and you will find another zip file. Load the inner file to the root of an external sd card. Then load it into the tablet, and reboot. It should alert you that a downgrade was found, and request your permission to downgrade.
But BE CAREFUL! There are manuals on the website also. You do not want to end up with a brick. I'm assuming that you aren't familiar with ADB/Fastboot, or you don't have access to them. A brick is not what you would want.

aarsyl said:
No problem at all. We're here to help.
Go to the ASUS support website (support.asus.com), and download the previous release of Android from the support page.
Then search for your device, and look for V10.6.1.15.3 of your variant (US, JP, CN, WW, TW). Unzip it once, and you will find another zip file. Load the inner file to the root of an external sd card. Then load it into the tablet, and reboot. It should alert you that a downgrade was found, and request your permission to downgrade.
But BE CAREFUL! There are manuals on the website also. You do not want to end up with a brick. I'm assuming that you aren't familiar with ADB/Fastboot, or you don't have access to them. A brick is not what you would want.
Click to expand...
Click to collapse
I have an older version of ADB installed on my laptop at home, not sure about fastboot, but I haven't taken the time to get familiar with either one. My primary phone is the Gnex and I use the Gnex Toolkit tool and it does a lot of the stuff for me, I wish there was a similar tool GUI for the Asus tablets.
Question, do I need to rename the inner zip file? and will it automatically install on reboot? Also by reboot are you referring to power off and then on, or do I need to boot into recovery?
Sorry for all the questions but I don't want to wind up with a brick / frisbee!!
Thanks for your patience!

Frisbee...lol.
Actually, I had to downgrade my tab, since I have trouble rooting the newest version. Just unzip to the root of the SD card. No need for reboot. The tablet will recognize it.
However, I just learned that it wipes the internal memory and all saved data. So backup whatever you can online, or on the SD.
______________________________
HTC Evo 4G LTE

aarsyl said:
Frisbee...lol.
Actually, I had to downgrade my tab, since I have trouble rooting the newest version. Just unzip to the root of the SD card. No need for reboot. The tablet will recognize it.
However, I just learned that it wipes the internal memory and all saved data. So backup whatever you can online, or on the SD.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
Sorry for the delay in respondin.
I've tried downgrading the firmware to that suggested with no luck, tablet may or may not recognize keyboardwhen docked. If it does recognize the keyboard, the first time it's undocked for any reason it will not recognize the keyboard ever again when docked.

musthunt said:
Sorry for the delay in respondin.
I've tried downgrading the firmware to that suggested with no luck, tablet may or may not recognize keyboardwhen docked. If it does recognize the keyboard, the first time it's undocked for any reason it will not recognize the keyboard ever again when docked.
Click to expand...
Click to collapse
Hmmmm....I remember dealing with that same issue after I upgraded to the 4.2 Bootloader. I don't remember the solution, however.
Maybe try erasing everything from the tab using fastboot.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Worth a shot, I guess.

my tf300t has not drivers?

So after a installed android 4.2.1 OTA nothing seems to right anymore. once a while i get the error: com.android.settings stopped. I can't connect him to my pc when i do this just nothing happend. It seems like he has no 'driver' for battery status he will not show how many time left and how much the dock is charged also it feels like he is more lagging now, the brightness can't be turned on automatic all those things doesnt seems to work anymore after i updated from 4.1 to 4.2.1
build number is ww 10.6.1.27.5

Skulltec said:
So after a installed android 4.2.1 OTA nothing seems to right anymore. once a while i get the error: com.android.settings stopped. I can't connect him to my pc when i do this just nothing happend. It seems like he has no 'driver' for battery status he will not show how many time left and how much the dock is charged also it feels like he is more lagging now, the brightness can't be turned on automatic all those things doesnt seems to work anymore after i updated from 4.1 to 4.2.1
build number is ww 10.6.1.27.5
Click to expand...
Click to collapse
Have you done anything on the tablet yet (install apps, settings) or just installed the OTA update. Usually the official OTA is rather stable

cmendonc2 said:
Have you done anything on the tablet yet (install apps, settings) or just installed the OTA update. Usually the official OTA is rather stable
Click to expand...
Click to collapse
yes ota and then after it i resetted the factory settings ( i wanted to clean everything apps, files ect ) but that's all what i've done..
i just want to get the usb working so i can go back to android 4.1 again or is there anyway i can do that from sd card or something i dont need usb connection with?

Skulltec said:
yes ota and then after it i resetted the factory settings ( i wanted to clean everything apps, files ect ) but that's all what i've done..
i just want to get the usb working so i can go back to android 4.1 again or is there anyway i can do that from sd card or something i dont need usb connection with?
Click to expand...
Click to collapse
I'm pretty sure you can copy the ROM file onto an sdcard and install it from there. Is your tablet unlocked with recovery or just stock?

cmendonc2 said:
I'm pretty sure you can copy the ROM file onto an sdcard and install it from there. Is your tablet unlocked with recovery or just stock?
Click to expand...
Click to collapse
I think it is unlocked i can do the power on/volume down trick to get in recovery well since i can't store it with usb i must download it from with the tablet right? so i've trying doing that but it gives me an error when i want to start the installation perhaps it's not in the right map. I read somewhere that you must store it in / (before sdcoard) ?

Skulltec said:
I think it is unlocked i can do the power on/volume down trick to get in recovery well since i can't store it with usb i must download it from with the tablet right? so i've trying doing that but it gives me an error when i want to start the installation perhaps it's not in the right map. I read somewhere that you must store it in / (before sdcoard) ?
Click to expand...
Click to collapse
what is the exact command you are using to flash?
also to check if it is unlocked, look in the top left corner of the screen during boot up. It will say:
Code:
This device is unlocked.

cmendonc2 said:
what is the exact command you are using to flash?
also to check if it is unlocked, look in the top left corner of the screen during boot up. It will say:
Code:
This device is unlocked.
Click to expand...
Click to collapse
He must be locked then i don't see any text.. i don't do any comment for flash right now because i'm not sure how it works. Are you sure that i can do a installation from the sdcard without using a usb cable to the pc?
And now i found out that he is probably not unlocked, how can that be done? Thanks by the way for your responses
Edit: i thought i had the tf300t which is not i have the tf300tg

Skulltec said:
He must be locked then i don't see any text.. i don't do any comment for flash right now because i'm not sure how it works. Are you sure that i can do a installation from the sdcard without using a usb cable to the pc?
And now i found out that he is probably not unlocked, how can that be done? Thanks by the way for your responses
Edit: i thought i had the tf300t which is not i have the tf300tg
Click to expand...
Click to collapse
now when i try to unlock it says an unknown error occurs which may be a network issue please try later again.. i downloaded the unlock installer from the asus website..

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