Related
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.
I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks
Thalias said:
I download the packacke via OTA and restart device. Then it boots to TWRP. I have to reboot device again and it goes back 6.0.1 with failed update notification. My deivice is unroot and still lock bootloader. Is there anyone having the same issue with me? And possible way to fix?
Thanks
Click to expand...
Click to collapse
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
Thanks. I am downloading again. Hope it works this time.
bkores said:
You have to restore stock B29 recovery. You can't accept an OTA with TWRP.
Click to expand...
Click to collapse
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.
Thalias said:
It still fails. After restarting device it boots into installing screen with miFavor logo instead of TWRP. The processing bar runs to about 24% then stops to reboot. I notice that the log at bottom screen say mismatch. And I got message system update package does not match the phone.
Click to expand...
Click to collapse
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat
Teet1 said:
You modified /system . You should probably flash official b29 firmware from ZTE and then update to nougat
Click to expand...
Click to collapse
I got b29 from zte website. Can I install it with stock recovery?
Thalias said:
Is there a link to download it?
Click to expand...
Click to collapse
https://www.zteusa.com/axon-7
Go under Support<Software Updates.
bkores said:
https://www.zteusa.com/axon-7
Go under Support<Software Updates.
Click to expand...
Click to collapse
Can I install it with stock recovery?
Thalias said:
Can I install it with stock recovery?
Click to expand...
Click to collapse
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".
bkores said:
You have to install it in stock recovery. Put it on your FAT32 sdcard and then in stock recovery select "Apply update from sdcard".
Click to expand...
Click to collapse
I got following message at bottom left of screen
Supported API: 3
Sorry, you can't sd upgrade
I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.
MiMtnBiker said:
I think you have to enable OEM unlock in developer options, first. Then, you can install B29 via SDCard.
Click to expand...
Click to collapse
Thanks. I forgot to unzip the file and put it in the root of sd card and I have done what you said too. It is running installation now.
I'm failing now? I went from ZAD v.3 back to stock B29 (I have an unlocked bootloader). I do have the MiFavor recovery (not TWRP)
I got the notification there was an upgrade, it took 6 hours to download... but the update "failed". I tried applying the update via SD card, but I get about 32% in and says "Update failed"......It also lists "Status 8" and "system partition has unexpected contents".
Sounds like y'all are having a hell of a time between the slow OTA speeds and then getting it to actually flash.
So I think I'll hold off for now. Hopefully we can get some TWRP-flashable zips soon enough... I think DrakenFX is already busy with all that
You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?
gpz1100 said:
You guys are making this way too complicated.
The full B29 firmware will flash just fine with twrp.
Only OTA *updates* require the stock recovery. The difference is the update patches existing files while the full firmware contains full partition images.
Be aware if you download the full b29 firmware from zte, it will also replace your recovery and bootloader. You won't be able to flash recovery from the bootloader/fastboot screen then. Also, it wipes all your data.
DrakenFX put out a modified version of the full firmware file which doesn't modify the bootloader. I believe it also leaves the recovery intact.
Click to expand...
Click to collapse
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.
tele_jas said:
No more complicated than it's turned out to be....
I followed DrakenFX's guide to B29 stock... The Nougat OTA downloaded, in 6 hours, but failed. So, I tried the SD card method, and it also failed at 32%.
Not sure what else I can do? Just wait for DrakenFX to make ZAD v.4 is my plan for now since I already wasted about 11 hours trying to upgrade today, and another 3 restoring back 6.0.1 and all my apps.
Click to expand...
Click to collapse
No problem upgrading using the OTA on an sdcard here. Flashed the draken stock_system zip, then fastboot flashed the B29 stock recovery. Reboot to recovery (which is now stock) and update from sd card. If you've messed with other partitions, you may need to flash more B29 .img's.
Thalias said:
After flashing official A2017U B29 firmware from ZTE the signal network service is lost. I ignore this and continue to upgrade to Nougat successfully and I get lost signal. I notice that Dual Sim Setting is working. Does official firmware overwrite original chinese baseband/bootstack? Can someone please upload chinese baseband/bootstack A2017 please?
Click to expand...
Click to collapse
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too
yosef019 said:
hey why you flashed us version firmware on chinise version?
i have aslo chinise version of the phone with b09G firmware im afraid loose signal too
Click to expand...
Click to collapse
I don't know Chinese so I prefer Eng community with support and US region always get latest update first.
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.
ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.
TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?
3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.
TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?
koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.
Yee!
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.
Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store
TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk
mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.
Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason
I received the May OTA update earlier today, and since I'm rooted I decided to flash it with Flashfire. As soon as I opened Flashfire I was prompted to click a button to install the OTA. However, I then recieved a warning message "warning: it has been detected that you may be trying to flash a block-level ota, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail!"
However, I clicked "ignore" and continued anyways, since I interpreted "flash to fail" to mean "will either not update (abort and stay the same) or update correctly." However, now my phone is stuck on the booting screen. I should at least still have TWRP installed, since I believe the "preserve recovery" box was automatically checked.
What can I do to fix the issue? I'm thinking if I download the full OTA and flash in recovery, maybe that will work?
If you can still boot into the bootloader (not recovery), do that and run through the manual install of the factory image (via the fastboot command - see the install instructions in the general forum). Again, do this manually (which requires downloading the factory image, extracting the files out, and manually flashing each file (bootloader, boot, etc.)) as that's really the only way you're going to get back to normal. You will have to re-root, etc., but that isn't that much work and saves the pain of going through what you just went through.
jeffrey123987 said:
I received the May OTA update earlier today, and since I'm rooted I decided to flash it with Flashfire. As soon as I opened Flashfire I was prompted to click a button to install the OTA. However, I then recieved a warning message "warning: it has been detected that you may be trying to flash a block-level ota, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail!"
However, I clicked "ignore" and continued anyways, since I interpreted "flash to fail" to mean "will either not update (abort and stay the same) or update correctly." However, now my phone is stuck on the booting screen. I should at least still have TWRP installed, since I believe the "preserve recovery" box was automatically checked.
What can I do to fix the issue? I'm thinking if I download the full OTA and flash in recovery, maybe that will work?
Click to expand...
Click to collapse
Fixed
johnhazelwood said:
If you can still boot into the bootloader (not recovery), do that and run through the manual install of the factory image (via the fastboot command - see the install instructions in the general forum). Again, do this manually (which requires downloading the factory image, extracting the files out, and manually flashing each file (bootloader, boot, etc.)) as that's really the only way you're going to get back to normal. You will have to re-root, etc., but that isn't that much work and saves the pain of going through what you just went through.
Click to expand...
Click to collapse
Thanks, I actually just flashed the full factory OTA and now everything is working fine once again. I did lose root access though, so I have to reflash superSU as well. Thank you for trying to help though! If flashing the full OTA in TWRP had also failed, my Plan B was to just flash the factory image as you suggested.
jeffrey123987 said:
Thanks, I actually just flashed the full factory OTA and now everything is working fine once again. I did lose root access though, so I have to reflash superSU as well. Thank you for trying to help though! If flashing the full OTA in TWRP had also failed, my Plan B was to just flash the factory image as you suggested.
Click to expand...
Click to collapse
Or next time just use the full image (not OTA) with FF (with select flash firmware package). You won't have any issues plus will retain root/recovery. You'll be back up and running in one minute.
Glad you got it back up and running. Also, as mentioned, you could flash the full package via flashfire, just don't flash the bootloader using it.
Just switched on my Moto G 2015 (US Retail, XT1540 2GB) for the first time in a week or two and got an update notification...
April 1 2017 security update, Build Number MPIS24.65-25.1-19 and System Version 24.221.19.osprey_retus_2gb.retus.en.US.retus
Is this news to people, or am I just way behind?
I have the same model, just did check system for updates and the update notification popped up. No notification before checking.
you are just way behind........got this update months back
RijuSarkar said:
you are just way behind........got this update months back
Click to expand...
Click to collapse
But you have something different than a 1540. I believe 1540 was the last to get the January update, while there are other models with 6.01 which the 1540 most likely will never get.
I've never got an update.
Just got mine today, 6/26/17. Also have an XT1540.
So I followed the same instructions here as I did for the last security update to a rooted device. It worked perfectly with the exception of the unlocked boot loader warning. The dark logo I used survived the January security system update, but was lost with this update.
@MrTooPhone
What do you mean by restored data partition I your instructions,I am not getting that.i am on stock not rooted but unlocked bootloader
25vikasp said:
@MrTooPhone
What do you mean by restored data partition I your instructions,I am not getting that.i am on stock not rooted but unlocked bootloader
Click to expand...
Click to collapse
If you are on stock ROM, unrooted, and stock recovery, you should be able to take the OTA upgrade with no issue regardless if your bootloader is locked or not.. I had to restore my unrooted stock ROM prior to accepting the OTA update. Than using TWRP, I restored the data partition from my last saved rooted ROM.
MrTooPhone said:
If you are on stock ROM, unrooted, and stock recovery, you should be able to take the OTA upgrade with no issue regardless if your bootloader is locked or not.. I had to restore my unrooted stock ROM prior to accepting the OTA update. Than using TWRP, I restored the data partition from my last saved rooted ROM.
Click to expand...
Click to collapse
Thanks for reply,i forgot to mention I have twrp installed.in order to update I just restored my non rooted nandroid backup.so currently it is asking me to update so should I proceed and how to take backup for data partition
25vikasp said:
Thanks for reply,i forgot to mention I have twrp installed.in order to update I just restored my non rooted nandroid backup.so currently it is asking me to update so should I proceed and how to take backup for data partition
Click to expand...
Click to collapse
I would not proceed if TWRP is installed. You need the stock recovery installed for the OTA upgrade successfully install. Once stock recovery is installed, you can boot into TWRP and complete all actions as if TWRP was installed. I never installed TWRP.
MrTooPhone said:
I would not proceed if TWRP is installed. You need the stock recovery installed for the OTA upgrade successfully install. Once stock recovery is installed, you can boot into TWRP and complete all actions as if TWRP was installed. I never installed TWRP.
Click to expand...
Click to collapse
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong
25vikasp said:
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong
Click to expand...
Click to collapse
That is correct. I still have stock recovery installed, but I use fastboot commands to boot into TWRP recovery.
After connecting the phone to the usb, using Linux, I do the following commands from the same directory where my TWRP img file is located.
Code:
./adb reboot bootloader
sudo ./fastboot boot twrp-osprey-3.1.0-r1.img
This loads TWRP in your phone but does not install it.
From windows I think the commands basically the same without the "./"
25vikasp said:
Without twrp how u managed to get root access.for installing stock recovery do I have to flash the entire firmware. Above line indicates that our phone can boot into two recoveries correct me if I am wrong
Click to expand...
Click to collapse
You can boot TWRP without flashing it to get root.