I own an EEE PAD Transformer TF101 and its got the 8.6.5.21(WW) firmware and I rooted it via Nachoroot and have installed CWM to be able to make full system backups/restores.
Now in the one hand I'm elated a new Android version called ICS is coming soon but have a couple of 'fears' and questions.
-Will the Tegra2 inside the TF101 run ICS just as smooth as Honeycomb ?
-I want to choose the moment ICS gets updated myself and I hate being forced by OTA but am I right that with Nachoroot and CWM installed it won't work anyways so no fears for that ?
-In that case I still keep getting OTA notifications I guess. Is here a tool to switch that off ?
Would it be wise to use OTA Keeper to backup my root or has OTA Keeper got any drawbacks ?
I bet ICS will at first not be rootable anyways right ?
maicod said:
I own an EEE PAD Transformer TF101 and its got the 8.6.5.21(WW) firmware and I rooted it via Nachoroot and have installed CWM to be able to make full system backups/restores.
Now in the one hand I'm elated a new Android version called ICS is coming soon but have a couple of 'fears' and questions.
-Will the Tegra2 inside the TF101 run ICS just as smooth as Honeycomb ?
-I want to choose the moment ICS gets updated myself and I hate being forced by OTA but am I right that with Nachoroot and CWM installed it won't work anyways so no fears for that ?
-In that case I still keep getting OTA notifications I guess. Is here a tool to switch that off ?
Would it be wise to use OTA Keeper to backup my root or has OTA Keeper got any drawbacks ?
I bet ICS will at first not be rootable anyways right ?
Click to expand...
Click to collapse
Correct. A rooted device most likely will have OTA disabled. To confirm, just go into Settings -> About Tablet and if you see a Check for System Update link, then OTA is probably still enabled. You may have to put a rebuilt Rom like Krakd or Prime 2.11 to have OTA disabled.
I think that Root will come fairly quickly for ICS considering the Source has been released for a long while. So the guys who look for those root exploits probably already have a nice stash lined up for when devices receive their updates.
Tegra 2 is plenty powerful enough to run ICS, that combined with the amount of Ram you shouldn't be to worried about that.
If you want...hop over to the Development threads and grab the latest ICS port from Paul Burton. That way you can check it out and see how you feel about ICS. Note: Paul's build are still considered early and some things may not work as you want, but that doesn't mean they won't work at all once Asus pushes out the official build or when Paul finishes up his port.
if you do flash paul's ROM please ask any questions in this thread HERE, and not in the dev thread. Also, be sure to read everything before flashing. It isn't quite complete and you will want to go back to HC after you flash.
gVibeR said:
Correct. A rooted device most likely will have OTA disabled. To confirm, just go into Settings -> About Tablet and if you see a Check for System Update link, then OTA is probably still enabled.
Click to expand...
Click to collapse
I checked and the update link still works and I'm sure I will still get OTA notifications
One good thing is that I noticed that since the RESCUE partition is replaced with CWM that OTA will fail when it reboots into rescue mode to install the update.
I am not keen on installing these ROMS that you mentioned since I don't know what is removed etc. compared to the original roms.
I was thinking this:
since I have root access isn't there a way to remove the OTA update service from starting up by using "terminal emulator" from the Android Market and edit the config file or directory where the OTA update notification service gets started ? Anyone knows if this is possible and how ?
I moved /system/UpdateLauncher.apk and Updatelauncher.odex into another map but that didn't stop the notifications and renaming ota.certs isnt wise since the new firmware update file will keep downloading again and again.
gVibeR said:
I think that Root will come fairly quickly for ICS considering the Source has been released for a long while. So the guys who look for those root exploits probably already have a nice stash lined up for when devices receive their updates.
Tegra 2 is plenty powerful enough to run ICS, that combined with the amount of Ram you shouldn't be to worried about that.
Click to expand...
Click to collapse
okay cool !
Thanks for the Paul Burton tip but I think I just wait until ICS comes available. I bet it won't take long anymore.
maicod said:
I checked and the update link still works and I'm sure I will still get OTA notifications
One good thing is that I noticed that since the RESCUE partition is replaced with CWM that OTA will fail when it reboots into rescue mode to install the update.
I am not keen on installing these ROMS that you mentioned since I don't know what is removed etc. compared to the original roms.
I was thinking this:
since I have root access isn't there a way to remove the OTA update service from starting up by using "terminal emulator" from the Android Market and edit the config file or directory where the OTA update notification service gets started ? Anyone knows if this is possible and how ?
I moved /system/UpdateLauncher.apk and Updatelauncher.odex into another map but that didn't stop the notifications and renaming ota.certs isnt wise since the new firmware update file will keep downloading again and again.
okay cool !
Thanks for the Paul Burton tip but I think I just wait until ICS comes available. I bet it won't take long anymore.
Click to expand...
Click to collapse
Dont screw with the system its just not good news!!!!!!
If you have cwm recovery ota will check and you will know when ics arrives but it wont install because of the custom recovery not because of root as stated above.
Sent from my Transformer TF101 using xda premium
If you don't want to get the update at all, freeze or disable DMClient app.
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
archonur said:
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
Click to expand...
Click to collapse
I am a newbie too -- bought the tf101 a couple of months ago - loved it -- told my husband he could have it - I was buying the 700 ! and was lucky enough to be able to order one (we live in Canada..... Tiger Direct.ca had them)
I have learned a lot from this forum -- glad I found it --- but I won't be "unlocking" anything ! the only thing I know how to "root" are my house plants !!! lol !! we don't even own smart phones yet -- we still have dumb phones !!! but I have my TF700 !!!
You mean sth like this?
seems hard, but it's not.
It seems tough in the beginning for noob, but actually you're going to get it. You should read the "Index" pointing out by d14b0ll0s to gain some basic knowledge and familiar with the terminology then you should be fine. Couple key words I want to point out that you should know. Currently TF700 came with a locked boot loader, meaning you not able to flash (install) custom firmware from our developers. This is a biggest issue at the moment. Sure there're workaround but it's a pain in the as...and unstable(could brick your pad if you not doing it right). When you see numbers like 21,22,26, they are firmware version number. The latest should be 26. OTA stands for "over the air" and we referred to firmware push to our pad by Asus, not manually download and install ourselves. Rooted is a process that you gain access as a administrator on your pad (you have full access to your phone), with rooted privilege you can almost do anything with your pad, like uninstall Asus embed software, do a full backup of your entire OS (operating system), modified system files etc... CWM is a tool you installed on your pad in order to flash (install) custom firmware. So at the minimum you should have root, and in the future when new custom firmware arrived, you can install cwm and used this tool to flash them. Keep in mind that with locked boot loader, you can't flash custom firmware. Finally, once you're rooted or have custom firmware installed, your pad will no longer can accepted OTA firmware (firmware push to your pad by Asus). In this case you need to roll back to stock (re installed factory firmware and no root), before you can do OTA update. Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
d14b0ll0s said:
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Click to expand...
Click to collapse
Sorry you're right, must not awake yet. ASUS that is. Thanks bro.
Your going to be fine try learning how to build aosp from source in a time limit
Sent from my Galaxy Nexus using xda premium
Skullmonkey said:
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
Click to expand...
Click to collapse
I agree with Skullmonkey on this. Until you are ready for really hacking the system, all you really need is to root the system (run the DebugFS) to get "administrator access to your device".
You might want to read what buhohitr wrote several times as there is much to be gleaned from it. If it helps, copy/paste the contents of buhohitr's repsonse to a notepad text document and go through it word-for-word, isolate those that you find questionable or troublesome, then research what those words are. Anything that is "super difficult" you can just post back here in the Q&A section and I'm sure someone will help you in no time.
another noob question: does rooting the device void manufacturing warranty?
It does not. Only unlocking the device does.
Sent from my Transformer Infinity!
So if I root my Infinity...
...which pre-included apps can I get rid of?
Also which preloaded apps are best to bump off if I dare a root?
I have never dabbled with android down in the file system much for fear of doing something irreparable.
Well, to the OP: we already have quite a few 'basic' threads going on here, and no one forces you to embark on the more advanced stuff, do we? Just read up on it, and when you feel like you can make the jump, pick it up little by little. We're not all experts in here, but most of us can follow directions of the gurus really good, and we have the advantage of knowing how to save our butts when the excrement impacts the ventilator. (And most of us learnt it the hard way, by bricking and breaking...)
You should be fine in the regular forums, and as the others have said, stay out of the development sections until you feel secure enough to dabble around with unlocking and so on.
Sent from my ASUS Transformer Pad TF700T
buhohitr said:
Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Click to expand...
Click to collapse
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
spinaldex said:
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
Click to expand...
Click to collapse
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
spinaldex said:
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
Click to expand...
Click to collapse
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Sent from my DROIDX using xda app-developers app
ekalb10 said:
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Click to expand...
Click to collapse
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
I guess I was just misinformed on the factory reset, sorry if I confused anyone.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
+ 1 I have rooted several tablets/phone over the last two years and backed it up using voodoo rootkeeper with ZERO issues updating firmware/OTAS. The only thing that happens after updating is that I loose root, but that's where voodoo OTA rootkeeper comes to play. Only a handful of people have had problems. Some are legit while others have messed/modded their device prior to updates. (like removeing system apps or modding build. Props)
"60% of the time, it works everytime. "
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unroot it again ??
If there are problems with the tablet and it must be repaired on warranty, then I need to unroot it again.
How do I unroot it again ??
Regards Peder
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Bzktz said:
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Click to expand...
Click to collapse
I'm assuming you still have stock recovery even though you unlocked the tablet. You can't re-lock the tablet so you'll eventually want to start using a custom recovery. However, don't install a custom recovery yet because the firmware upgrades are going to wipe custom recovery every time.
This should help you get started with the upgrade process using only the stock recovery:
Pre-upgrade:
0) HIGHLY RECOMMENDED -- Take the time to make nvflash accessible and make backups so that you'll be able to recover from a brick situation. This is the ONLY chance you have to do this before upgrading to .30:
http://forum.xda-developers.com/showthread.php?t=1901479
0.25) Performing the upgrades shouldn't affect your apps and data, but back them up if you want to just in case.
0.5) Make sure your tablet is charged 60% or higher or is plugged in.
Simple Upgrade Process:
1) Download "Voodoo OTA RootKeeper" from the market to back up your root.
2) Follow these instructions to update to .30:
http://forum.xda-developers.com/showthread.php?t=1755576
3) Reboot the tablet 2 times or so to make sure the .30 update finishes completely -- it updates the camera firmware and some other stuff.
4) Run RootKeeper again and verify you can still restore root. If you have to, re-root and use RootKeeper to back it up. Restoring a backed-up root is is currently the only way to root on Jelly Bean, so this is your LAST chance.
5) Download the appropriate Jelly Bean OTA update zip from here:
http://forum.xda-developers.com/showthread.php?t=1915079
6) Repeat the instructions in step 2, except you can just directly rename the file you downloaded in step 5 (there's no "zip within a zip").
7) After the upgrade is complete, run RootKeeper again and restore root.
8) Install the custom recovery of your choice (edit: when a working one becomes available).
recovery works in JB?
lafester said:
recovery works in JB?
Click to expand...
Click to collapse
sorry my mistake, there isn't one that's working yet.
i tried the manual method and it wont work
i did what the instructions said and in the end when android logo and status bar come out, shortly it display android with red triangle indicating that it failed. it says "ID verification failed." does anyone successfully update their TF700 using this method?
Bzktz said:
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Click to expand...
Click to collapse
If you are still on 26 the first thing i recommend you is to use the NvFlash tool (from the Development forum) so you can recover your device from any soft brick, then update to 30 and JB. Unlocking avoid your warranty so NvFlash tool is a wise thing to go with.
Just went through the motions (Including accessing nvflash)
no worries, I bricked it on purpose and then unbricked it just to make sure. nvflash is rad!
the new JB update, Forget the benchmarks, I don't even care what they say at this point, this is the best user experience I've had on this thing so far and it's just going to get better. at least with nvflash I can still load unsigned bootloaders, that's all I need for native linux experimentation.
yea though I walk through the valley of the shadow of flash I will fear no bricking, for blob.bin art with me. :good:
Thank you very much for the response. I am up to #5 in the process but now I am stuck. I renamed the file and stuck it on my sd card. However I am getting nothing when I then boot in recovery. It tells me SD Installation aborted, and gives me the Red Triangle. What am I doing wrong here?
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
NeoMatrixJR said:
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
Click to expand...
Click to collapse
For unlock your tablet, the only way is to use the UNLOCK TOOL V7
After, once your tablet unlocked without problem
You can just followed this guide : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !.
It's exactly for you.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
Click to expand...
Click to collapse
No way by this side...If you use the Unlock tool, you loose your warranty, it's one fact
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
Click to expand...
Click to collapse
And actually and for my part the most functional as recovery is TWRP, but if you want to use CWM, no problem for use it too
Ok, so I've been in the root/flashing scene for a while.
I'm very experience with locked bootloaders like my Verizon Note3, but I'm not so sure about my Shield tablet.
I know root is easily attainable, and flashing should be about the same as the others.
My question is, in the event things go badly, is there a way to get back on the stock/non-rooted image?
What about updating the software via OTA to keep being able to gamestream? Does it break root and just force me to root again
or does it not allow me to update? If my Shield dies for whatever reason and I have to RMA, can I return it to 100% stock?
I looked over the forums and couldn't find any full answers, so hopefully you guys can help me.
Thanks in advance.
Josh
ForeverZ3RO said:
Ok, so I've been in the root/flashing scene for a while.
I'm very experience with locked bootloaders like my Verizon Note3, but I'm not so sure about my Shield tablet.
I know root is easily attainable, and flashing should be about the same as the others.
My question is, in the event things go badly, is there a way to get back on the stock/non-rooted image?
What about updating the software via OTA to keep being able to gamestream? Does it break root and just force me to root again
or does it not allow me to update? If my Shield dies for whatever reason and I have to RMA, can I return it to 100% stock?
I looked over the forums and couldn't find any full answers, so hopefully you guys can help me.
Thanks in advance.
Josh
Click to expand...
Click to collapse
NVidia posts complete factory images on their website for restoration.
Also, all of their OTAs are full system images instead of patches/deltas. So you can safely update via OTA, root and other modifications won't break the OTA (but the OTA will get rid of any modifications including root.)