Updating old y01 tablet to 3.11 - Shield Tablet Q&A, Help & Troubleshooting

So I had a recalled tablet that I gutted the Ota updater from so that the kill patch could not be applied. When I got my new tablet I noticed that it had a 3.11 update. I assume my tablet didn't receive the update before I killed the Ota updater. Does anybody know how I would apply the new update without killing my old tablet?
Thanks.

Hello,
Download the OTA 3.1.1 image on nVidia website and fully flash it through fastboot.
At this point, NEVER let the tablet reboot on the stock firmware ! (PARTICULARLY if you have a configured wifi connection)
Once it's done, stay in fastboot and install TWRP as a recovery.
Directly boot to recovery and install nomoreota.zip:
http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Now, you should be safe if you reboot on the stock firmware.
Good luck and don't make any mistake ! (personally, I feel more safe with a custom firmware like Cyanogenmod)

Wouldn't it be easier to install the 3.11 image, then root it and delete the Ota updater? I don't think I need a Internet connection for kingroot.

You don't need root to remove TegraOTA - only a custom recovery (TWRP, CWM).
You also don't need the recovery image - only the Full OTA package.
Install the Full OTA in your custom recovery and then proceed to remove the TegraOTA folder/.apk from the recovery's file manager - if you're uncomfortable deleting the folder/file, then flash nomoreota.zip instead.
If you want/need root, simply flash SuperSU .zip in recovery as well - no need for Kingo, etc.
Sent from my SHIELD Tablet using XDA Free mobile app

Related

[Q] Proper way to upgrade to JB

Brief history of what I've done..I am very new at this, like starting today new.
I unlocked using the asus tool.
Then downgraded to ICS
Rooted using debugfs
Verified using rootchecker, successfully rooted
Installed ota rootkeeper and supersu (also tried once without supersu and just used superuser)
Backed up root using rootkeeper and temp. unrooted
...Now here is where I am not sure...
To upgrade to jelly bean, am i just supposed to download the newest firmware off the asus site, then use rootkeeper to restore root? Because that's what I did a few times, (with and without supersu as noted before)....and i cant restore root.
Or is there a special way to upgrade to jellybean or special firmware file i need to download...
I've heard someone mentioning dlpkgfile but i'm not sure what that is.
Thanks
There are generally two ways to upgrade to JB:
For locked devices, the only way (keeping root) is downgrade to ICS, root, use OTA rootkeeper, and then upgrade using dlpkgfile files. These files are incremental updates that are normally downloaded for OTA updates. Friendly community members have saved them from their /cache partition and uploaded them. Use the search function to find the thread. If you use the firmware download from the Asus site, it will rewrite your complete system partition, overwriting any su backup.
For an unlocked device, everything is much easier. You don't need to keep root, you can root any firmware version directly by first installing a custom recovery via fastboot from your PC, then you need a flashable superuser package (a zip file) and install it from this custom recovery.
Basic steps:
- Get a custom recovery in blob format. Most TF700 users use TWRP, it has a nice touch interface.
- Get the fastboot program for your PC from the Android SDK. For Windows, you also need some ("naked"?) drivers.
- Get a flashable superuser package in zip format and store it on your device.
- Start fastboot mode: turn tablet off, hold down volume-down while turning on, use volume-down to go to the USB icon, use volume-up to confirm. Then from your PC start: fastboot flash recovery yourcustomrecovery.blob
- To start the custom recovery: turn tablet off, hold down volume-down while turning on,use volume-up to start RCK.
- From TWRP, tap "Install", select your flashable superuser zip and confirm.
- Congratulations, you are rooted.
_that said:
There are generally two ways to upgrade to JB:
For locked devices, the only way (keeping root) is downgrade to ICS, root, use OTA rootkeeper, and then upgrade using dlpkgfile files. These files are incremental updates that are normally downloaded for OTA updates. Friendly community members have saved them from their /cache partition and uploaded them. Use the search function to find the thread. If you use the firmware download from the Asus site, it will rewrite your complete system partition, overwriting any su backup.
For an unlocked device, everything is much easier. You don't need to keep root, you can root any firmware version directly by first installing a custom recovery via fastboot from your PC, then you need a flashable superuser package (a zip file) and install it from this custom recovery.
Basic steps:
- Get a custom recovery in blob format. Most TF700 users use TWRP, it has a nice touch interface.
- Get the fastboot program for your PC from the Android SDK. For Windows, you also need some ("naked"?) drivers.
- Get a flashable superuser package in zip format and store it on your device.
- Start fastboot mode: turn tablet off, hold down volume-down while turning on, use volume-down to go to the USB icon, use volume-up to confirm. Then from your PC start: fastboot flash recovery yourcustomrecovery.blob
- To start the custom recovery: turn tablet off, hold down volume-down while turning on,use volume-up to start RCK.
- From TWRP, tap "Install", select your flashable superuser zip and confirm.
- Congratulations, you are rooted.
Click to expand...
Click to collapse
So if I am getting this correctly, I could have just stayed on the latest official JB update from asus, unlocked like I did, and then followed the above steps, instead of downgrading, etc. ?
Thanks for the reply also
mdelongpre said:
So if I am getting this correctly, I could have just stayed on the latest official JB update from asus, unlocked like I did, and then followed the above steps, instead of downgrading, etc. ?
Click to expand...
Click to collapse
Correct.
_that said:
Correct.
Click to expand...
Click to collapse
just wanted to update this real quick...
I installed the latest JB firmware and followed this guide... http://forum.xda-developers.com/showthread.php?t=1938129
now I have JB, root, and can flash custom roms with TWRP
So thank you and good luck to others trying this, PM me because I might have been in the same situation for some of you newbies like me attempting this
mdelongpre said:
I installed the latest JB firmware and followed this guide... http://forum.xda-developers.com/showthread.php?t=1938129
now I have JB, root, and can flash custom roms with TWRP
Click to expand...
Click to collapse
Great that you made it!
Please check that your TWRP version is 2.3 or later (the guide is old and recommends an older version) - otherwise you might run into problems (brick) when you choose "wipe data" in the bootloader menu.

Hosed - could not leave well enough alone

Okay, folks. I need some help. I was not able to flash new Cyanogen ROM's so I tried updating my TF300T to the latest US firmware. Here are the results and where I stand now.
1. TWRP 2.5 is loaded in recovery.
2. Latest ASUS firmware is installed.
3. Lost root.
4. Tried to re-root and cannot. SuperSU fails every time I try to update the binary.
5. I wipe everything and can boot into recovery.
6. I tell TWRP to flash the latest ASUS firmware zip file.
7. Firmware flashes but then when I go to reboot in TWRP it says that no OS is available!!
8. I can swipe the lock and reboot into 4.2.1 but obviously no root.
9. I have tried flashing the signed superuser file and it flashes and says successful.
10. When I use root checker pro to see if I have root it tells me that I do not have root.
What in the hell is going on????????? Any help or outline of steps would be appreciated.
bshpmark said:
Okay, folks. I need some help. I was not able to flash new Cyanogen ROM's so I tried updating my TF300T to the latest US firmware. Here are the results and where I stand now.
1. TWRP 2.5 is loaded in recovery.
2. Latest ASUS firmware is installed.
3. Lost root.
4. Tried to re-root and cannot. SuperSU fails every time I try to update the binary.
5. I wipe everything and can boot into recovery.
6. I tell TWRP to flash the latest ASUS firmware zip file.
7. Firmware flashes but then when I go to reboot in TWRP it says that no OS is available!!
8. I can swipe the lock and reboot into 4.2.1 but obviously no root.
9. I have tried flashing the signed superuser file and it flashes and says successful.
10. When I use root checker pro to see if I have root it tells me that I do not have root.
What in the hell is going on????????? Any help or outline of steps would be appreciated.
Click to expand...
Click to collapse
Bootloader info plz. Unless you were using the experimental CM10.1 build (or a select few others), it sounds like you tried to flash a ROM compatible only with an older bootloader onto the "latest" build (from your description).

Update 51, 8/12/13 402.6MB

There is a new update out. Is there anything special we need to do to preserve root if we are rooted? I don't have CWM installed.
Would it be advisable to use OTA rootkeeper?
EDIT - OTA rootkeeper didn't work and root was lost. The update must wipe /system. I guess I'll have to try rooting when I get home again. Hopefully that remains the same. I didn't want to have to flash recovery and jump through hoops updating the Shield which is why I left the stock recovery on there... Oh well. Bootloader remains unlocked so I suppose it should be easy as entering the one fastboot line I used from Gnurou...
Edit 2 - Root using Gnurou's instructions worked.
Evo_Shift said:
There is a new update out. Is there anything special we need to do to preserve root if we are rooted? I don't have CWM installed.
Would it be advisable to use OTA rootkeeper?
EDIT - OTA rootkeeper didn't work and root was lost. The update must wipe /system. I guess I'll have to try rooting when I get home again. Hopefully that remains the same. I didn't want to have to flash recovery and jump through hoops updating the Shield which is why I left the stock recovery on there... Oh well. Bootloader remains unlocked so I suppose it should be easy as entering the one fastboot line I used from Gnurou...
Click to expand...
Click to collapse
I have an idea that might help keep root, let me check it out.
UPDATE
It won't work in this case. The update patches recovery and flashes a new boot.img
UPDATE2
If you have CWM Recovery installed, after flashing the update it will ask if you want to disable recovery flash and then if you want to root.
Yes, you will have to re-run the fastboot command after each OTA. Preserving root after an OTA would require a custom recovery (like CWM). I tried to apply this OTA with the version of CWM agrabren uploaded and it failed, so until this is fixed I guess the best thing to do it just re-root after each OTA
Gnurou said:
Yes, you will have to re-run the fastboot command after each OTA. Preserving root after an OTA would require a custom recovery (like CWM). I tried to apply this OTA with the version of CWM agrabren uploaded and it failed, so until this is fixed I guess the best thing to do it just re-root after each OTA
Click to expand...
Click to collapse
Did it fail with status 7?
EDIT
It would have (failed with status 7) agrabren called the shield thor in his recovery and nvidia called it roth in the update. So the update was expecting roth for the device name and got thor.
Thats why it worked for me because i renamed it roth when i modded the recovery.
IF agrabren complains I will remove the link but for now.
Modded version is here
The ota zip is here

update 68 or any update and root shield

i tried to install update 68, the shield reboots get me to the screen with the android on its back, select the update install, then it errors out?
is the device being rooted causing the issue o the bootloader.
also if this or any small update installed correctly would i lose my root access,
if i lose root, will i always have to start from a factory rest and lose all my information to root it again.
thanks
An unlocked bootloader is not the problem. If you somehow modified the system image ( like rooted/removed apps, integrated updates into ROM, installed custom recovery or something else) the update process will fail because of it. That might have to do with the fact its an incremental update which checks if it is modified/rooted and/or will update apps which aren´t there anymore.
One way to solve this is to backup your apps and data. Then flash stock recovery and stock image via fastboot and install all updates from the beginning.
The other way is to go to Nvidias Support Page for the Shield. Then download the latest Update for it. It´s an sh package which needs to be extracted under Ubuntu or special tool for windows. Then you can flash the newest image and recovery directly with fastboot. Didn´t try that.
Hope i was able to help you.

Samsung Galaxy S8 unroot

Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
minalm said:
Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
Click to expand...
Click to collapse
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
you have given a very detailed explanation and i fell like a simple thank you would be enough. you helped me out now and i feel somewhat obliged to thank you this way.
cheers
Is the things still the same... namely unrooting will not return KNOX and can not use Samsung warranty?
hi
i have a rotted phone s8..i flashed a stock rom, but phone is still rooted. Some apps like us google pay,mcdonalds tell me that phone is rooted..What i can do?

Categories

Resources