Database Users

Will I not be able to install future updates if I root/unlock?

I know the S3 you can't install updates if you unlock the bootloader. But if I unlock/root I can still get future updates right?

Why does it matter? If you are unlocked and rooted then you will be running a ROM someone made, so all you have to do is install a new version of whatever ROM you want when a new update is released. Custom ROM's are pretty much always up to date with the latest source.

There are plenty of reasons to root without installing custom roms. I only root my devices to get wireless debugging.
My unlocked Galaxy Nexus got the latest ota. It broke root, but is still unlocked. I've not rooted my nexus 10 yet.

You'll be able to install OTA updates cleanly as long as you're using stock recovery and haven't modified any system files that the update expects to be there.

Fromako said:
You'll be able to install OTA updates cleanly as long as you're using stock recovery and haven't modified any system files that the update expects to be there.
Click to expand...
Click to collapse
I can verify this. I just got my Nexus 10 and in order to move saved game data and some other stuff I rooted and unlocked the bootloader so I could run Titanium backup. I didn't change system settings or anything and I am not running a custom rom. About 10 minutes after I had finished rooting and moving saves from my Samsung GTab 10.1 I received the 4.2.1 OTA Update. No issues so far and as far as I can tell it's still rooted.

adb backup w/out root

Anyone tried and confirmed working the old adb backup method that doesn't require root?
http://forum.xda-developers.com/showthread.php?t=1420351
Was hoping to use this method to backup before unlocking. I got into the usual problem of not wanting to unlock right away (in case issues etc.) then once I was comfortable with the unit too lazy to want to set up all up again from scratch....

Use helium. Backup each app individually. There are some apps that will Bork restore.
Sent from my Nexus 7 using XDA Premium HD app

bummer screw that for a joke then LOL
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.

wintermute000 said:
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
Click to expand...
Click to collapse
Unlocking doesn't prevent you from getting the OTAs.
If you want root to be compatible with OTAs, see this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339

yeah I know that, I know I can reflash stock recovery and unroot etc. just too lazy to be bothered setting up all my apps losing saves etc. at this point short of mucking around with carbon. TBH if the multitouch issue is fixed or at least toned down there's not a lot of incentive to root for me aside from adblock.
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.

wintermute000 said:
yeah I know that, I know I can reflash stock recovery and unroot etc.
Click to expand...
Click to collapse
My point is you don't need to unroot nor flash stock recovery (though it is safest to flash stock recovery)
The JSS15J OTA update will flash fine with root and twrp with just the small fix I referenced.
wintermute000 said:
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
Click to expand...
Click to collapse
JSS15J already included firmware updates, it updated aboot, sbl, tz, and rpm. Bootloader went from 3.05 to 3.14 and it flashed ok with root and twrp (though again, personally I suggest using stock recovery)
Also you don't need to install twrp persistently to root. I just boot into twrp one-time by using fastboot boot twrp.img to install the root files and leave stock recovery on the tablet.
With the one simple fix referenced above, you can have stock recovery, root, and be totally compatible with future OTAs, no need to revert anything. Of course after the OTA is successful, just re-run the SuperSU zip and the fix to set yourself up with root and await the next OTA.
On this nexus, you need to unlock even to do the official factory restore google published. The official images don't come with signatures.

To answer the question re adb bu, yes it works just fine.
Sent from my Nexus 7 using Tapatalk 4

OTA updates with Unlocked Bootloader

Hello,
after I've unlocked the bootloader can I still get OTA updates?
I'll just be on stock ROM with root. I also make a backup with nothing on except TWRP.

Lets hope so

LanceM said:
Lets hope so
Click to expand...
Click to collapse
have you tried it?

Yes you'll be able to get new updates with unlock bootloader.

DrakenFX said:
Yes you'll be able to get new updates with unlock bootloader.
Click to expand...
Click to collapse
Can you elaborate on this? The last I heard unlocking the bootloader (using the official procedure) stops OTA. Has this changed ?

mh127 said:
Can you elaborate on this? The last I heard unlocking the bootloader (using the official procedure) stops OTA. Has this changed ?
Click to expand...
Click to collapse
I never said Official getting OTA's , but i believe this is going to change staring with the new Unlock Bootloader procedure.

DrakenFX said:
I never said Official getting OTA's , but i believe this is going to change staring with the new Unlock Bootloader procedure.
Click to expand...
Click to collapse
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.

mh127 said:
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
Click to expand...
Click to collapse
In my experience, what makes the difference - so far - is the recovery. Official ZTE updates and ROMS only flash through the stock recovery.
Unlocked bootloader has made no difference to me.

mh127 said:
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
Click to expand...
Click to collapse
If you try to flash Official OTA yes will fail, cuz isn't modded to skip partitions check.

DrakenFX said:
If you try to flash Official OTA yes will fail, cuz isn't modded to skip partitions check.
Click to expand...
Click to collapse
This is getting confusing. "Getting OTA updates" (as OP asks) usually means that the update installs "on its own" by tapping notification rather than flashing via recovery, which is a bit more complicated process.
So back to the OP question: With root and TWRP can one get over-the-air official updates from ZTE without going to the recovery manually? I believe the answer to that is NO.
That said, there is probably a work around in getting the update, probably by manually flashing partitions that have changed in the update.
Is this right?

mh127 said:
This is getting confusing. "Getting OTA updates" (as OP asks) usually means that the update installs "on its own" by tapping notification rather than flashing via recovery, which is a bit more complicated process.
So back to the OP question: With root and TWRP can one get over-the-air official updates from ZTE without going to the recovery manually? I believe the answer to that is NO.
That said, there is probably a work around in getting the update, probably by manually flashing partitions that have changed in the update.
Is this right?
Click to expand...
Click to collapse
Well OPs Question actually was if OTA Updates are possible with unlocked boot-loader...
Root and TWRP is a whole different scenario and won't work with OTA for sure as OTA needs stock recovery and will check for unmodified system (not rooted)...
But if you are on stock with unlocked bootloader you should get notified about OTAs (as until now it did not check for bootloader lock status, but that could change in future) although I don't know if it will install correctly

Gachmuret said:
Well OPs Question actually was if OTA Updates are possible with unlocked boot-loader...
Root and TWRP is a whole different scenario and won't work with OTA for sure as OTA needs stock recovery and will check for unmodified system (not rooted)...
But if you are on stock with unlocked bootloader you should get notified about OTAs (as until now it did not check for bootloader lock status, but that could change in future) although I don't know if it will install correctly
Click to expand...
Click to collapse
OP mentioned that he used TWRP to make a backup, I assumed he has replaced stock recovery with TWRP, but that may not necessarily be the case.

If your device has an bootloader that was unlocked "unofficially" (either via sideloading the official unlock method or DrakenFX & Unjustifieddev's method), but is still completely stock (stock System, stock Boot, stock Recovery, stock everything besides the unlocked bootloader), you can still receive and apply OTAs. However, if you changed any of the partitions, like boot.img (root), recovery.img (TWRP), system.img (changes to system), you will still receive the OTA, but you won't be able to apply it, the update will fail. If you went through the official bootloader unlocking process, which involved you submitting a form to ZTE with your device's IMEI, you would no longer be able to receive OTAs.
What I did was sideload the official B20_Boot on by B20 device, unlocked my bootloader, flashed TWRP, flashed the TWRP Stock B20 dumps that were posted here on XDA, and reflashed stock recovery. This made my device completely stock B20 besides the unlocked bootloader. I then applied the official B27 OTA update, and it installed fine. I then reflashed TWRP (since my bootloader was still unlocked) and re-rooted my device.
If a new update comes out, I can just reflash the stock B27 TWRP dump posted here on XDA, reflash stock recovery, (if needed, reflash stock fastboot), and apply OTA.

xtermmin said:
...
What I did was sideload the official B20_Boot on by B20 device, unlocked my bootloader, flashed TWRP, flashed the TWRP Stock B20 dumps that were posted here on XDA, and reflashed stock recovery. This made my device completely stock B20 besides the unlocked bootloader. I then applied the official B27 OTA update, and it installed fine. I then reflashed TWRP (since my bootloader was still unlocked) and re-rooted my device.
If a new update comes out, I can just reflash the stock B27 TWRP dump posted here on XDA, reflash stock recovery, (if needed, reflash stock fastboot), and apply OTA.
Click to expand...
Click to collapse
So, with this procedure, do you lose all the app installations/other customizations? I believe that all of the application data is on a non-system partition (/data?) but did you need to go through all of the setting up of the phone after you did the upgrade this way?

rayman2k1 said:
So, with this procedure, do you lose all the app installations/other customizations? I believe that all of the application data is on a non-system partition (/data?) but did you need to go through all of the setting up of the phone after you did the upgrade this way?
Click to expand...
Click to collapse
Yes. Unlocking the bootloader does a factory reset, and doing a TWRP restore of a stock image (which overwrites your current partitions) overwrites what you had before.
EDIT: Actually, I think Internal Storage gets erased as well, but your microSD card will be fine.

xtermmin said:
Yes. Unlocking the bootloader does a factory reset, and doing a TWRP restore of a stock image (which overwrites your current partitions) overwrites what you had before.
EDIT: Actually, I think Internal Storage gets erased as well, but your microSD card will be fine.
Click to expand...
Click to collapse
Hmm, had guessed as much. I knew the bootloader unlocking did a wipe, but was hoping that recovery-flashing would do a backup/restore, as if the update had been applied through the in-ROM update procedure. Unless the OTA process only gets deltas and flashes them, leaving fs intact.

rayman2k1 said:
Hmm, had guessed as much. I knew the bootloader unlocking did a wipe, but was hoping that recovery-flashing would do a backup/restore, as if the update had been applied through the in-ROM update procedure. Unless the OTA process only gets deltas and flashes them, leaving fs intact.
Click to expand...
Click to collapse
Yeah, the OTA doesn't straight-up replace partitions, it checks and patches the existing partitions, so if a partition has been changed, the OTA install will fail.

Can't update my Moto G5 Plus after rooting. How to unroot it easily?

Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?

It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175

acejavelin said:
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
Click to expand...
Click to collapse
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?

dt.dragonborn said:
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
Click to expand...
Click to collapse
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.

dt.dragonborn said:
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
Click to expand...
Click to collapse
Which OTA(s) isn't installing?
Sent from my Moto G Plus (5th Gen) using XDA Labs

cdysthe said:
Which OTA(s) isn't installing?
Click to expand...
Click to collapse
I am not much of a tech guy but the update says
New Version-NPN25.1 37-67
Improved audio in Video Capture
Data traffic improvements

acejavelin said:
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
Click to expand...
Click to collapse
Thank you for this. I unlocked the bootloader, and installed TWRP and Magisk to gain root. This worked fine. However, I decided I wanted to go back to complete stock yesterday. So I uninstalled Magisk and flashed stock firmware using ADB. My phone is now unrooted, has a locked bootloader, and is running stock firmware which is what I wanted. Once I get the phone to boot, almost everything functions normally. However, it seems as though I now do not have any recovery whatsoever (and I assume that's because I did not specifically replace TWRP with stock recovery). So when I boot my phone, it goes to the bootloader and stops. If I then hit "start" on the bootloader, the ROM loads up normally after that. f that were the only issue, I could live with it. But not being able to get to recovery is concerning. And I am not able to get OTAs at the moment.
So, I'll check the other thread you mentioned. I assume I will need to flash stock recovery in order to get where I need to be.
Thank you for the post!

RS988 21d OTA in the wild

The RS988 finally has a new OS update with Google patch level Dec 1st, and that means that we are finally good against blueborne and krack!
Sent from my RS988 using Tapatalk

I just installed it. It's about time. I was beginning to wonder if they had stopped support on the RS988. I hear the LG G5 is supposed to get Oreo, but I have a feeling that the RS988 will get left out based on how the updates have gone so far.

Hi! Has the modem changed?

I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?

Nispero said:
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Click to expand...
Click to collapse
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk

kattolo said:
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader

spinoza_web said:
Hi! Has the modem changed?
Click to expand...
Click to collapse
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info

Nispero said:
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
Click to expand...
Click to collapse
the best source of full stock roms as well as info on the phone I could find so far is https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648

The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.

kattolo said:
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Click to expand...
Click to collapse
Here's the baseband version with RS98821c: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.88674.1.101802.1
The numbers are slightly different at the end compared to RS98821d , but I'm not sure what if anything might have changed.

maybe, for getting OTA should we just get unroot? How to do it properly?

If recovery is not the stock one, it will not be possible to install the OTA.
Alternatively you might need to wait for someone to make a flashable zip you could flash with TWRP, but given the fact development on this phone is not too active you might need to wait for a while before is available
Sent from my RS988 using Tapatalk

Awkydee said:
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
Click to expand...
Click to collapse
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.

brewerywagon said:
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
Click to expand...
Click to collapse
First I flashed the magisk uninstaller and rebooted back to recovery. Then I flashed the 21c COMPLETE ZIP and didn't flash magisk so it would replace TWRP with the stock recovery on reboot. Then I rebooted and when I tried to update it went to the stock and threw up an error then rebooted. Upon reboot it displayed a message saying that I couldn't update because my device had been rooted. So I rebooted back in to bootloader and flashed TWRP again. Then I flashed 21a COMPLETE ZIP and no magisk so that the stock recovery would replace TWRP. I rebooted and went through setup and took OTA updates until I was on 21d. Then rebooted back into bootloader and flashed TWRP. Then rooted and we've through setup. I tried every other way but this was the only way that worked for me. I hope it helps!

should be an easier way. Did u see some changes to the radio?

Some of you may remember that last year I had the misfortune of installing the Brightpoint ROM on my Unlocked G5, which completely messed the phone up by not allowing it to connect to AT&T's LTE. It was a process to re-flash the older ROMs/Bootloader and then rebuild it to a stable 21c. I had used it for a while like that, and the only problem I had was that when ending a voice call (HSPA) it would take a while to change back to LTE.
I ended up going with the S8 over the summer (Samsung discount + Note 2 trade in) which got it for $18/month. I've been using it ever since and the LTE to HSPA Voice to LTE change-off on the S8 is done within a second, unlike the G5.
My mom had been using an unlocked Samsung S5 for almost a year now, and it's constantly dropping calls, and this past week it froze on her and required a battery pull, so was thinking of having her try out my (unused) G5 to see if she liked it more. When I turned the G5 on today, I updated all the apps, and then installed the 21d OTA update. The hand-off from voice to LTE still is not as fast as my S8, but seems to be improved from the 21c firmware.

ROM Posted
Just to let you all know, I have posted the latest 21d stock ROM in my thread here: https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907

Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.

ingressor said:
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
Click to expand...
Click to collapse
I'm not having any reboot issues when playing music.