Database Info

VRALG7 Update Question

I am relatively new to the rooting experience but am a big fan of the benefits. I only do basic stuff and am too paranoid to try flashing ROMs or anything too advanced. I recently downloaded the most recent update and it didn't go as I had anticipated.
I was taken to the reboot screen as if I was using Clockwork Mod. It asked me questions that I had to answer in order to proceed but the choices were strange. It would ask me, "do you want to install this unfamiliar zip?" and the answers would be, "No, No, No, No, No, No, Yes, No, No, No, Go Back." I picked yes for the 3 different choices and it completed the install.
After the phone rebooted there was a message saying that the update had failed. I called my brother who has an unrooted phone and checked to see that I in fact do have the update. I am wondering if this is what will happen each time I get an update and if there is anything I should be worried about. The phone is still rooted and I don't notice anything different, but I am just paranoid that rooting my phone will make it so I am unable to install the jellybean update next month. Thanks for the advice in advance!

that sounds like CWM or it might be the factory download mode but either way i dont think you should have to do that for a factory update

So you are on stock, but rooted? Usually the rule of thumb is not not accept the OTA updates, but rather flash one of the stock, rooted roms when an update comes out. You might wnat to try something like the root66 rom, if not somehting like Synergy or CleanRom, which are still stock-based.
As far as this particular issue, as far as I knew, the OTA updates will usually always install. The problem is that they will sometimes revert back to un-rooted, and sometimes will even block the root exploit so you're stuck.

update will fail if you are using a custom recovery, i.e. cwm

wwjdd44 said:
update will fail if you are using a custom recovery, i.e. cwm
Click to expand...
Click to collapse
Is there any way to remove clockwork mod? I don't really need it.

[Q] How can I protect root on 4.4 with locked bootloader?

I bought a Droid Maxx on eBay. It came rooted, running 4.4, with a locked bootloader. I got the phone a day or so too late to get in on the chance to buy a bootloader unlock code.
So, how can I protect root? I'm worried about upgrades or anything else Verizon might push down that'd overwrite root. I don't know how the phone was rooted (I assume it was rooted on 4.2.2 and then updated to 4.4 but don't know for sure). I have the paid version of Titanium Backup so if there's something I need to freeze or uninstall I'll do that. If there's a setting I can change to make sure that my phone doesn't accept an update that loses root I'll do that. I know that there's no method to re-root a Droid Maxx on 4.4 with a locked bootloader so I want to take whatever precautions I can to prevent losing root. I've read just about everything on the Motorola Droid Ultra forum and I have not found an answer to this question.

lesdense said:
I bought a Droid Maxx on eBay. It came rooted, running 4.4, with a locked bootloader. I got the phone a day or so too late to get in on the chance to buy a bootloader unlock code.
So, how can I protect root? I'm worried about upgrades or anything else Verizon might push down that'd overwrite root. I don't know how the phone was rooted (I assume it was rooted on 4.2.2 and then updated to 4.4 but don't know for sure). I have the paid version of Titanium Backup so if there's something I need to freeze or uninstall I'll do that. If there's a setting I can change to make sure that my phone doesn't accept an update that loses root I'll do that. I know that there's no method to re-root a Droid Maxx on 4.4 with a locked bootloader so I want to take whatever precautions I can to prevent losing root. I've read just about everything on the Motorola Droid Ultra forum and I have not found an answer to this question.
Click to expand...
Click to collapse
Use Titanium to freeze the app MotorolaOTA and you'll be good to go
Sent From Droid Ultra

Yes, freezing the MotorolaOTA is the way to go. You may never get updates in future (even bug fix updates). But hey, you got root in 4.4, which is good, especially when unlocking BL is impossible.
If you really want to get any update in later stage via OTA, then unfreeze the same app and unroot your phone. Then accept the OTA, but you will loose root and may never gain again.

I found and froze MotorolaOTA using Titanium Backup, as suggested. Thank you. Now, can I install TWRP? I've read a fair amount about TWRP on this forum but I'm not confident that I'm separating what can be done with TWRP if you have an UNlocked bootloader and what (if anything) can be done with TWRP if you have a locked bootloader (as I do). All I really want to be able to do is to reboot to Recovery in order to either make a backup of my ROM or to wipe cache and Dalvik cache, as that sometimes seems to smooth out operations if an app installation doesn't go well. I would use CWM for that if necessary but on other devices TWRP is my preference. So -- if I DO have root but I do NOT have an unlocked bootloader, can I install TWRP to reliably perform those functions?

lesdense said:
I found and froze MotorolaOTA using Titanium Backup, as suggested. Thank you. Now, can I install TWRP? I've read a fair amount about TWRP on this forum but I'm not confident that I'm separating what can be done with TWRP if you have an UNlocked bootloader and what (if anything) can be done with TWRP if you have a locked bootloader (as I do). All I really want to be able to do is to reboot to Recovery in order to either make a backup of my ROM or to wipe cache and Dalvik cache, as that sometimes seems to smooth out operations if an app installation doesn't go well. I would use CWM for that if necessary but on other devices TWRP is my preference. So -- if I DO have root but I do NOT have an unlocked bootloader, can I install TWRP to reliably perform those functions?
Click to expand...
Click to collapse
If your bootloader is locked you'll need to use safestrap recovery. Basically has same functionality as TWRP as far as back ups and wiping. Just do some reading up on it. Not sure how current the attached thread is and I haven't used safestrap for this device.
http://forum.xda-developers.com/showthread.php?t=2503897
[RECOVERY] Safestrap Recovery [MAXX / ULTRA]
Sent From Droid Ultra

[Q] Moving SCH-I535 Verizon S3 from 4.1.2 rooted to 4.4.2 rooted

I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?

loonytoon500 said:
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
Click to expand...
Click to collapse
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk

ShapesBlue said:
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
Click to expand...
Click to collapse
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).

loonytoon500 said:
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
Click to expand...
Click to collapse
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk

ShapesBlue said:
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
Click to expand...
Click to collapse
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.

loonytoon500 said:
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
Click to expand...
Click to collapse
After all the reading I've done in order to take the OTA you have to unroot. I don't know the complete process as I am not on any OTA
From my S3 running BlissStalk

Even if you dont care about custom ROMs right now you may in the future when there are no updates released for the phone or you want to sell it and could have gotten a higher price with the lower system version. Before you update try some of the ROMs out and see if there are some you like and if you dont like any then update.
That being said I have updated using ODIN and the firmware I got from this site. look around and you will find the stuff you need.

i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?

loonytoon500 said:
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
Click to expand...
Click to collapse
Sure it's possible, but unlikely. To put into perspective, I don't believe there has been a bootloader unlock for Verizon Notes 2-4 and Galaxy S4-5 (which would allow one to natively run AOSP without Safestrap) so the likelihood is low.
Sent from my SCH-I535 using Tapatalk

Urgent problem with ota update 5.0

HI was downloading the new update 5.0 but it stopped and now the tablet says me "your system is updated" but with the 6.0.1.I can't restart the download now,what i have to do???

Same thing happened to me. Don't know why yet.

Same here. Where are you from?

Nvidia might have pulled it to fix something wait patiently it will come.

I had a similar problem as well. I got the notification to download the update, and when I clicked on the "Download" button in the notification, it did nothing. When I went into my settings and opened the OTA updater, it kept telling me that "Your system is up to date," even after repeatedly pressing the "Check Now" button, selecting "Clear data," rebooting, and messing with the advanced settings. I hope they fix this soon, I was really excited about this update!

Exact same issue here.

If you haven't root/twrp etc:
Download from here:
https://forum.xda-developers.com/shield-tablet/general/5-0-update-nougat-incoming-t3553612/page2 (there are two version - k1 & standard).
Paste it to internal memory, boot into recovery and apply update from zip.

Just wait a little. That's what NVIDIA calls "staggered rollout".

Just wanted to update and say that I got my OTA this morning and will apply it later this afternoon. Guess, just as suggested earlier, they staggered them. It's strange though that they actually pulled it back, but then again it might have been an issue with it.

if you have "nougat launcher apk" just delete it.

Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?

My 2 cents: if the root is confirmed to work, there is no "process" per se.
D/L the root zip to the tablet, boot into recovery, flash that zip and reboot into system.
Should be within 2-3 min the whole thing.

Wayno-san said:
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
Click to expand...
Click to collapse
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/

pucka said:
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
Click to expand...
Click to collapse
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.

Wayno-san said:
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Click to expand...
Click to collapse
Yes you can just apply the update and there's no need to flash stock first. If you want to flash TWRP I would recommend getting root first by sideloading (like in the guide) and then using the TWRP app to flash TWRP.
I'm now rooted again with TWRP as custom recovery.

Cons of rooting Pixel 3a?

Hello,
I've been out of the rooting scene for a while now (last phone had a damn permalocked bootloader!) and wanted to be clear on a few things before rooting this phone.
1. I am aware that doing any sorts of modifications to the system will disable OTA updates and those have to be done manually, the question is when I restore my phone (removing root, going back to stock recovery, etc) will automatic OTA updates be re-enabled? Is the stock recovery image even available, or is this even possible? because...
2. When I am looking to sell the phone in the future, I want to be sure that the phone doesn't show any signs of tampering. I am wondering this because the last phone I rooted was the Motorola z2 force, which was the first phone I've ever seen with that "unlocked bootloader" warning when powering on. And with that phone even after all the images were returned to stock, there was still a "your device has loaded a different os" warning, even if it was the stock image. The CTS system functioned similarly to Samsung's knoxs system, where once it was tripped, there was no going back and I wasn't aware of this...
TL;DR: If I ever wish to sell the phone to completely stock (relocked bootloader, stock recovery img, etc), will the phone be permanently tainted with a message like with the image attached? thanks!

PhantomSoul said:
Hello,
I've been out of the rooting scene for a while now (last phone had a damn permalocked bootloader!) and wanted to be clear on a few things before rooting this phone.
1. I am aware that doing any sorts of modifications to the system will disable OTA updates and those have to be done manually, the question is when I restore my phone (removing root, going back to stock recovery, etc) will automatic OTA updates be re-enabled? Is the stock recovery image even available, or is this even possible? because...
2. When I am looking to sell the phone in the future, I want to be sure that the phone doesn't show any signs of tampering. I am wondering this because the last phone I rooted was the Motorola z2 force, which was the first phone I've ever seen with that "unlocked bootloader" warning when powering on. And with that phone even after all the images were returned to stock, there was still a "your device has loaded a different os" warning, even if it was the stock image. The CTS system functioned similarly to Samsung's knoxs system, where once it was tripped, there was no going back and I wasn't aware of this...
TL;DR: If I ever wish to sell the phone to completely stock (relocked bootloader, stock recovery img, etc), will the phone be permanently tainted with a message like with the image attached? thanks!
Click to expand...
Click to collapse
If you flash stock image and relock bootloader no one will ever know.
As far as otas while rooted, this device will allow you to accept, it will just overwrite root.
Sent from my Pixel 3a using Tapatalk

In your image it's because it's a Motorola, not a good manufacturer with bootloader (but not the worst).
There is 3 big ways with bootloader:
#1 (the best) : The unlock method is 100% in the "code" and you can unlock and relock it yourself (Google with Nexus and Pixel)
#2 (good but not the best) : The unlock method is in the code BUT the manufacturer has a part of the method (an unique code) and you can't do it without register your IMEI on the website, so the manufacturer know it, you lose the warranty... (Motorola, Sony).
#3 (the worst) : You just can't because the manufacturer doesn't want. (Nokia)

jmtjr278 said:
If you flash stock image and relock bootloader no one will ever know.
As far as otas while rooted, this device will allow you to accept, it will just overwrite root.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.

alliance1975 said:
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
Click to expand...
Click to collapse
Yes, sir. I'm not sure what method you used other than flashing the rooted boot.img but if am update comes out either patch the new kernel or wait for pbanj to post the modified img. That's it. Easy peasy
Sent from my Pixel 3a using Tapatalk

alliance1975 said:
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
Click to expand...
Click to collapse
You can't install ota on rooted phone. It will fail in recovery.
The steps you need to do is as follows:
1. boot to bootloader, use fast boot to flash stock boot.img
2. go to recovery, apply ota.zip using adb sideload
3. boot back to bootloader, flash the patched boot.img with root
4. reboot and enjoy with root and all your apps/data intact.

googlephoneFKLenAsh said:
You can't install ota on rooted phone. It will fail in recovery.
The steps you need to do is as follows:
1. boot to bootloader, use fast boot to flash stock boot.img
2. go to recovery, apply ota.zip using adb sideload
3. boot back to bootloader, flash the patched boot.img with root
4. reboot and enjoy with root and all your apps/data intact.
Click to expand...
Click to collapse
Wow a slightly different procedure. So it would appear I need the stock boot image when I want to do an OTA. Thanks.

There have been lots of issues with Google pay and securehub (if you work at a big company and want company email on your phone) and unlocked bootloader. Yes, magisk does eventually find workarounds, just depends on how much time you want to spend screwing around knowing it'll break relatively often. Also, we don't have many developers on board yet, so as far as custom roms and kernels go, it's slim pickings.
All that being said, rooted stock is great as long as you don't mind resetting everything to unlock the bootloader.

As you have noted, if you unlock the bootloader you will get the warning when booting. However, unlike your previous phone, you can reflash to stock and relock your bootloader very easily.
Obtaining root and then accepting OTA updates is also much easier with the Pixel phones (and really any phone that is now using A/B partitions). Here is a to some magisk tutorials that show you how easy it is to take an OTA update. https://topjohnwu.github.io/Magisk/tutorials.html
Also as noted previously, it can be tricky to get Google Pay set up with a rooted device. It is possible, but it takes some effort. Personally I don't use Google Pay, so it's no loss to me and I haven't bothered trying to get it to work. Otherwise root is very important to me. I use several mods/apps that are very important to me. Viper4Android, Advanced Charging Control, Ad blocking, Youtube Vanced, and Active Edge Mod (a unique mod for Pixel devices with the active edge gesture) as well as root explorer, tasker (and related apps like secure settings) and titanium backup.
To me, having access to those mods and apps are well worth seeing the warning message and having to manually accept a OTA update and having an extra step or two in the update process.