So, I have been around for quite some time with Windows Mobile, but this is my first Android phone.
Anyways - I installed S-Off and rooted my phone, and now when I try to install the t-mobile system update, after the phone restarts it gets stuck on a screen with a picture of an android and a yellow exclamation mark.
I'm going to assume it doesn't install because it's rooted? I am not too familiar with the android world....
yep, that's what happens when you try and install an ota update on a rooted phone with custom recovery... ya can't do it. if you want the update, you would need to be on unrooted stock.
There's a reason that CWM doesn't let you install OTA packages. You could ruin your device.
You CAN install any OTA update; there is nothing in CWR stopping you.
Of course you need to adapt META-INF/com/google/android/updater-script before you do since it usually contains checks on the bootloader and recovery version that will fail.
Get titanium backup.
Type in filter: Updater.
When the updater X.X.X shows, freeze it.
You will never have to worry about an update again.
Related
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.
Just got the Sheild Tablet and after unlocking the bootloader, installing CWM and rooting, the OTA update reboots to install version 2.2, but boots to CWM. It shows the 'fix root' y/n dialog and I've chosen both at this point and it will not install or advance past 2.1 and perpetually downloads the 2.2 update. Any ideas?
nednarbackwards0 said:
Just got the Sheild Tablet and after unlocking the bootloader, installing CWM and rooting, the OTA update reboots to install version 2.2, but boots to CWM. It shows the 'fix root' y/n dialog and I've chosen both at this point and it will not install or advance past 2.1 and perpetually downloads the 2.2 update. Any ideas?
Click to expand...
Click to collapse
That's because you need to download full OTA and flash it like a normal zip via your CWM. Then re-flash SuperSU to keep root.
Where do we get the full ota update I tried Google with no luck
I have had an issue where I cannot receive OTA updates. Whenever I check for updates the reply is: Software up to date as of <date,time>
I have rooted my tablet using the fastboot method however I originally accidentally flashed the OS to blank and softbricked my tablet. After installing the 5.0.1 factory image and installing it using fastboot, I then used CWM recovery to install SuperSU.zip to root the device, after doing this I could receive OTA updates. When I went to install them CWM aborted the update. I booted normally and selected "Clear update data", rebooted and now it always says that the device is up to date despite being on the 5.0.1 factory image.
My question is how can I go about getting OTA updates again? Also, will this involve further tweaking of files which may be risky as I have already messed everything up once.
Thank you.
EDIT: I have only just realised the grammatical error in the title but I can't change it now.
Just for clarification, are you trying to flash/sideload the OTA or are you attempting to use the tablet's built-in updater?
Nvidia pulled the 5.1 update. 5.0.1 is up to date.
Sent from my SHIELD Tablet using XDA Free mobile app
You can't get an OTA while rooted .. This is a very basic principle/consequence of rooting. There is no new 5.1 update since it was pulled a few months ago. I'm still waiting for it to get fixed but we might just get M at this rate. Rooting isn't risky if you understand what you are doing and what you shouldn't do. If you are responsible with the "power" of having a rooted device then I wouldn't worry about it.
I am waiting for the ability to flash the new OTA that was pushed on 29th. But yeah cannot pull and download the OTA while rooted.
Good evening, look nere: https://youtu.be/bT82lX40fuc
I just downloaded and installed while rooted with TWRP installed, no problem. I did have to re-flash TWRP and root, but TWRP had no trouble with the auto update.
Sent from my SHIELD Tablet using XDA Free mobile app
I have the original Android 8.0 system and software version 2.33.401.19. Two days ago, my HTC announced that there is a new update to android 9.0. It downloads it and tries to install it. After reboot, TWRP starts and I choose to restart the system. Nothing is updated, and after a while I see a message that the update file is damaged.
A few weeks ago I unlocked the bootloader, ripped the phone and installed TWRP and MagiskManager. I suspect that the unlocked bootloader causes these problems. What should I do to install this update?
Szturwal said:
I have the original Android 8.0 system and software version 2.33.401.19. Two days ago, my HTC announced that there is a new update to android 9.0. It downloads it and tries to install it. After reboot, TWRP starts and I choose to restart the system. Nothing is updated, and after a while I see a message that the update file is damaged.
A few weeks ago I unlocked the bootloader, ripped the phone and installed TWRP and MagiskManager. I suspect that the unlocked bootloader causes these problems. What should I do to install this update?
Click to expand...
Click to collapse
not the unlocked boot loader, it's because you have twrp installed. you need stock recovery(and what ever you do don't relock your bootloader)you can get back to stock by flashing the oreo ruu, then you'll recieve the ota and it will install.you need the ruu for your phone.that's it.
this will wipe your internal, so if you have something on there you want to keep, back it up to your pc, then you can restore, also, you'll need to reinstall twrp and magisk after you install the ota.
Thanks for answer. I'm going to do this ....
Hi,
Is there a way I can just flash the stock recovery and try to OTA? Really don't want to backup 80GB and restore back.
Hey all
So a while back I wanted to use a certain app on my Motorola One Hyper that required root privileges, so I rooted my phone using Magisk for it. I didn't need the app later so I unrooted my phone, but now when I try to update my phone to a newer version, I get an error message saying "Package verification failed. The update package being downloaded is not compatible with the current software version on the device".
I'm not sure if me rooting the device has anything to do with it or not, but I'm guessing it is since I never had this issue before the root. Any way to fix this? Thanks in advance!
BlobTea said:
Hey all
So a while back I wanted to use a certain app on my Motorola One Hyper that required root privileges, so I rooted my phone using Magisk for it. I didn't need the app later so I unrooted my phone, but now when I try to update my phone to a newer version, I get an error message saying "Package verification failed. The update package being downloaded is not compatible with the current software version on the device".
I'm not sure if me rooting the device has anything to do with it or not, but I'm guessing it is since I never had this issue before the root. Any way to fix this? Thanks in advance!
Click to expand...
Click to collapse
Yes, it probably is the root.
If you are trying to update the stock rom, it probably will not work. You may have to manually flash the stock rom again. Then, you may be able to upgrade to android 11. Otherwise you can just manually install android 11.
RVR said:
Yes, it probably is the root.
If you are trying to update the stock rom, it probably will not work. You may have to manually flash the stock rom again. Then, you may be able to upgrade to android 11. Otherwise you can just manually install android 11.
Click to expand...
Click to collapse
Ahh gotcha. Looks like I'm gonna have to flash the stock rom then. Thanks a lot for your help!
Does having a SafetyNet fix have something to do with it? Maybe unrelated, maybe not but when I check off the software update on the Magisk DenyList, exit and then come back, it becomes unchecked and I don't know why. Perhaps if the OTA updates werent detecting root, I could update to a security patch.
BlobTea said:
Ahh gotcha. Looks like I'm gonna have to flash the stock rom then. Thanks a lot for your help!
Click to expand...
Click to collapse
Stock updates usually can't be applied to rooted devices or devices with custom recovery, root has to be completely removed and stock recovery has to be reinstalled. If those aren't corrected before applying the update, it will fail because it checks the system partition for modifications and requires stock recovery to apply the update, whether it actually boots into recovery or not during the update process.