Would it be possible to install OTA updates if I choose to root the phone?
From what I've read, this is definitely impossible if I flash custom recovery.
But what if I leave stock recovery? Do I just need to reroot after the OTA, or is there another method to update?
Thanks
On my Galaxy Nexus, I get around that by just booting Clockwork Recovery (fastboot boot recovery.img instead of fastboot flash recovery recovery.img). Then I flash the OTA, re-flash su and I'm good.
If you are rooted with no custom recovery, your phone will still accept the OTA. When you install the OTA, you lose root. You can use something like OTA Rootkeeper to keep root, or reroot after the fact.
I am new to nexus devices... how often do they release OTA updates?
1234568 said:
I am new to nexus devices... how often do they release OTA updates?
Click to expand...
Click to collapse
If you have a custom recovery like "ClockworkMod, Twrp etc" then you can't get OTA's.. some say if you have Superuser you can't get OTA's either..
You would need to install a stock recovery and download the OTA file and flash it..
OTA updates don't happen that often.. when the phone first release you might see a couple to address certain issues.. or if the AOSP code changes you'll see a update..
plumcakk said:
Would it be possible to install OTA updates if I choose to root the phone?
From what I've read, this is definitely impossible if I flash custom recovery.
But what if I leave stock recovery? Do I just need to reroot after the OTA, or is there another method to update?
Thanks
Click to expand...
Click to collapse
On the Galaxy Nexus, you can update via OTA while rooted. Everything else must be stock. The update will usually break your root, but it's pretty simple enough to re-root on Nexi.
1234568 said:
I am new to nexus devices... how often do they release OTA updates?
Click to expand...
Click to collapse
They send out OTAs whenever they update Android versions. For the GNex, I think I got 4 version updates since I bought it last June (4.0.4 -> 4.1 -> 4.1.1 -> 4.1.2 -> 4.2)
YoungAceAtlanta said:
If you have a custom recovery like "ClockworkMod, Twrp etc" then you can't get OTA's.. some say if you have Superuser you can't get OTA's either..
You would need to install a stock recovery and download the OTA file and flash it..
OTA updates don't happen that often.. when the phone first release you might see a couple to address certain issues.. or if the AOSP code changes you'll see a update..
Click to expand...
Click to collapse
any way you can flash the OTA update with clockwork?
i know the flash images for 4.3 are available now but wouldnt it be easier to wait for the OTA update? and the process will be simpler? or am i missing something? Also if I have a custom kernel but stock rom all I need to do for the OTA update is go back to stock kernel correct?
Cjshino said:
i know the flash images for 4.3 are available now but wouldnt it be easier to wait for the OTA update? and the process will be simpler? or am i missing something? Also if I have a custom kernel but stock rom all I need to do for the OTA update is go back to stock kernel correct?
Click to expand...
Click to collapse
You will need to be 100% stock to get the OTA the normal way, otherwise you'll have to flash it manually via adb sideload or a custom recovery
EddyOS said:
You will need to be 100% stock to get the OTA the normal way, otherwise you'll have to flash it manually via adb sideload or a custom recovery
Click to expand...
Click to collapse
so you mean like No custom roms, custom kernels or root apps? or root or unlock bootloader?
100% stock means exactly that. You can leave the bootloader unlocked but the main system itself has to be exactly how it was brand new as the OTA patches the original files. If they're not there the OTA will fail
EddyOS said:
100% stock means exactly that. You can leave the bootloader unlocked but the main system itself has to be exactly how it was brand new as the OTA patches the original files. If they're not there the OTA will fail
Click to expand...
Click to collapse
Can i just go back to stock kernel and delete root apps? or do i have to flash 4.2.2
Cjshino said:
Can i just go back to stock kernel and delete root apps? or do i have to flash 4.2.2
Click to expand...
Click to collapse
If i upgrade to 4.3 with the factory image am i still rooted? Can i still use my apps that require root lets says auto hide soft keys?
You can get OTA update even when you have root (assuming you haven't touched any system files), but you will lose root after the update. It's pretty easy to re-root though.
Sent from my Nexus 4 using Tapatalk 4 Beta
I still dont have it via OTA yet.
Is it just the US at the moment ?
If it says software status official does that mean I have the official rom not rooted and able to receive ota updates even if my boot loader is unlocked? How can I relock bootloader?
No, you should be with locked bootloader. You can read this thread, it helped me to get stock system, and also to relock bootloader so I can get OTA update to 6.0 Marshmallow.
tecnikstr0be said:
If it says software status official does that mean I have the official rom not rooted and able to receive ota updates even if my boot loader is unlocked? How can I relock bootloader?
Click to expand...
Click to collapse
To take OTA locked bootloader is NOT NECESSARY.
If you have a unmodified system partition and stock recovery you are good to take OTA.
Unlocked boot loader helps you to flash files through fastboot.
I updated my Z008 to the new LP Ota update 2.20.40.155, not rooted nor unlocked before. And now I can't unlock my bootloader using ASUS's tool. I used to successfully unlock my bootloader via that method on 2.20.40.149. Does any one have the same problem like me?
Tried: reboot, reinstall tool => doesn't work
Your bootloader must be already unlocked. Try to flash and start TWRP.
RealYoti said:
Your bootloader must be already unlocked. Try to flash and start TWRP.
Click to expand...
Click to collapse
Before updating, it hadn't been unlocked. And on the new firmware, I can't unlock it
Never mind, i unlocked it by one click tool
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.