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.
Related
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
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
**Resolved** I managed to resolve this by re-enabling all apps I'd disabled using the normal android option in settings (just google newsstand etc.), It wouldn't update from an OTA or a full package of a later version but it would accept an update from YNG1TAS2I3 that it was already on, it updated over the top of itself and after that OTA's seem to be working, there's a lot to do though.
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬
Hi, I'm trying to update a family members phone from YNG1TAS2I3. The phone is completely stock, it's never been modified or rooted at all. It only runs apps from Google Play and it was updated to this version by OTA.
Recovery gives the following error when installing the update:
/dev/block/platform/msm_sdcc.1/by-name/system has been remounted r/w; reflash drvice to reenable ota updates
Any ideas? I really really don't want to have to factory reset it, root it or put a custom recovery on it? Can I force flash it over the top to marshmallow without unlocking the bootloader or anything? I've also tried flashing the full rom from stock recovery but that doesn't seem to work either.
Thanks,
How do I manually update through OTA my honor 8 after rooting?I dont want to flash full rom.Where does the downloaded update will be saved?
Ragesh77 said:
How do I manually update through OTA my honor 8 after rooting?I dont want to flash full rom.Where does the downloaded update will be saved?
Click to expand...
Click to collapse
You can't really "manually" update your Honor 8 the way you mean it. You can't just flash the downloaded content from TWRP.
Anyway I'll guide you on how to update without full ROM reflash. You WILL need recovery image and you can try without stock boot image. Installing update with rooted device(modified boot image) is reported to not work for some people but for me it does work with no issues. If you make a full backup you also won't run into any problems.
So to update your device find stock recovery img of your current ROM version. I recommend extracting it from UPDATE.zip which you can download with Huawei extractor. You flash the stock recovery from fastboot. I will assume you know how to get to fastboot since you already are rooted and have unlocked bootloader which is OK and won't give us problems.
After flashing stock recovery proceed with OTA normally as if you did not modify your device in any way.
BUT YOU have to select full system image download. Not partial small 200-300 mb update. You have to select full 2GB system image.
If you run into an error and it refuses to update you will need to find stock boot image from the previously mentioned UPDATE.zip. So flash both stock recovery and stock boot, then proceed with normal OTA update same as said above with full system image.
By doing the above you will not lose your DATA partition. You will not lose your apps. You WILL lose root access. All you need to do to regain root access it is to first reflash TWRP via fastboot and then reflash Magisk/SuperSU/(your root alternative). Before reflashing TWRP I recommend making stock recovery backup so you won't need to extract it again from UPDATE.zip for the future OTA updates.
If you have any questions or I was not clear on something please ask for further guidance. Do not forget to make a full backup before the process. You can not hard brick your device with anything I wrote here but you can lose your data if you have no backup.
Can't I just flash the 300mb file rhrough twrp?
Ragesh77 said:
Can't I just flash the 300mb file rhrough twrp?
Click to expand...
Click to collapse
Of course You can't. I wrote that at the beginning of the post. If that was possible nobody would ever have issues with updating their rooted device lol.
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Uxlewl said:
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Click to expand...
Click to collapse
Yes, if you used TWRP to create a backup of your stock ROM before you flashed a custom ROM, you just use TWRP to restore the backup of stock ROM.
Or, if you didn't use TWRP to backup your stock ROM, you can flash your device's stock firmware using the flashtool designed to be used with devices made by your device's manufacturer.
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Uxlewl said:
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Click to expand...
Click to collapse
No, installing TWRP does not require root. Yes, TWRP and root prevent the installation of OTA updates.
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Uxlewl said:
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Click to expand...
Click to collapse
To be more specific, installing TWRP does not necessarily prevent a device from actually receiving/downloading OTA updates, it prevents the actual installation of OTA updates because part of the OTA update includes automatically booting into stock recovery to apply the update. If you have TWRP installed, the OTA update can possibly be downloaded to the device but when the device automatically tries to reboot into recovery, it is trying to boot into stock recovery but if you have TWRP installed, it can't boot into stock recovery to apply the update and when it tries to boot into TWRP, it will try to apply the update but it will fail, resulting in a bricked device and the device will have to be restored.
When it comes to OTA updates, all that is required is an unmodified stock system partition(meaning, no root or any other kind of modifications to the system partition), stock recovery(meaning, no TWRP) and the update has to be offered by your carrier if they offer the update for your specific device.
If a device is rooted, has other system modifications and/or has TWRP installed and you want to apply a stock OTA update, you have to remove root and any other system modifications and you must replace TWRP with the original stock recovery before you can apply the update. If you have TWRP and or root and you remove them to apply an OTA update, you can root the device again and install TWRP again after the update, provided that the OTA does not come with a locked bootloader that can not be unlocked, in this case, you will not be able to reinstall TWRP or root because the bootloader will be locked, which prevents you from installing TWRP again. Sometimes, users remove root and TWRP to apply OTA updates with the intention of rooting and/or installing TWRP again after the update but then get stuck in a position where they can no longer root the device or install TWRP because the bootloader gets locked during the update and there is no way to unlock the newly updated bootloader, from then on, they are stuck with stock with no way to get root, TWRP and custom ROMs reapplied to the device because they were not aware that the update came with a locked bootloader that can not be unlocked by any means.