The most recent update PPWS29.116-11-13 has OTA downloaded, but failed to install (even after factory reset). All previous updates had always installed without any problem.
I have XT1926-7 "Evert" (from Amazon) with unlocked BL, but otherwise stock un-rooted, unmodified PPWS29.116-11-11.
Could unlocked BL be a reason?
The unlocked BL can't be the reason for this. Try flash the 116-11-11 FW and just boot your device without any changes. Then you will be able to install the update.
WoKoschekk said:
flash the 116-11-11 FW
Click to expand...
Click to collapse
Why? Wha's the rationale here? It's already 116-11-11
rybshik said:
Why? Wha's the rationale here? It's already 116-11-11
Click to expand...
Click to collapse
Moto OTA update s have been failing for many model s
Seems like the only solution is to reflash the current version of firmware that phone and try OTA again
Or see is new version is posted on
https://mirrors.lolinet.com/firmware/moto
Just download the correct software channel version.
Flash with Rsd lite or fastboot.exe
Sent from my mata using XDA Labs
sd_shadow said:
reflash the current version of firmware that phone....
https://mirrors.lolinet.com/firmware/moto
Click to expand...
Click to collapse
Will EVERT_RETAIL_9.0_PPWS29.116-11-11 be good for AT&T and T-mobile frequency bands?
I do not care too much about LTE though
sd_shadow said:
Seems like the only solution is to reflash the current version of firmware that phone and try OTA again
Click to expand...
Click to collapse
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
System integrity is compromised
Android version: 9
Current version: PPWS29.116-11-13
Security patch: November 1, 2019
As your device system integrity is compromised is compromised, it is no longer eligible for software updates
Click to expand...
Click to collapse
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "retla".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root
rybshik said:
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "LA".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root
Click to expand...
Click to collapse
I'm not sure.
Someone else posted same warning, that had unlocked bootloader.
It's not a normal warning.
Sent from my Cosmo_Communicator using XDA Labs
sd_shadow said:
Someone else posted same warning, that had unlocked bootloader.
Click to expand...
Click to collapse
so folks need to be careful when updating to PPWS29.116-11-13
rybshik said:
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "retla".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root
Click to expand...
Click to collapse
Install Magisk and this message will disappear.
This a normal warning screen caused by a corrupted AVB due to your unlocked bootloader. Magisk will fix it by the AVB 2.0/dm-verity option.
WoKoschekk said:
This a normal warning screen caused by a corrupted AVB due to your unlocked bootloader..
Click to expand...
Click to collapse
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11
rybshik said:
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11
Click to expand...
Click to collapse
Yes, there is. Everytime I flashed a new FW and Magisk wasn't installed the system showed me this warning. As soon as Magisk is installed this error will disappear. Just try it.
Since the moto g6 plus was updated to Pie you got this error.
rybshik said:
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11
Click to expand...
Click to collapse
Yes I think this is a new thing.
Sent from my mata using XDA Labs
Related
WW_20.20.40.164_20160107
73.66 MB update
any improvements?
android lover 2000 said:
any improvements?
Click to expand...
Click to collapse
no log provide yet,but I see
Fixed video sound issue
fixed a sdcard issue
android lover 2000 said:
any improvements?
Click to expand...
Click to collapse
no log provide yet,but I see
Fixed video sound issue
fixed a sdcard issue
New kernel.
Release note:
【Version】
V2.20.40.164_20160107_6983(MR9.13)
【Model Name】
ZenFone2 (ZE551ML)
【Release Date】
2016/01/18
【Release Note】
1.Fixed video sound issue.
2.Fixed google play stop service .
3.Fixed SD cards issue.
4.Fixed SmartBox not read the phone issue.
5.Fixed can not control the volume of YouTube when using miracast.
6.Fixed the issue of displaying wrong operator name when roaming and searching network.
7.Fixed phone hang-up issue in Russia
8.Fixed PosteMobile NFC issue (ZE551ML only)
9.Support Android for Work
10.Improve ASUS ZenUI Launcher stability
11.Improve Cell Broadcast stability
12.Fix the failure to share Photo Collage picture via Email
13.Several Apps update
14.Improve power usage of Email App
# New Features
1.Add Screenshot sound settings
My bootloader has unlocked but I recently flashed stock recovery and full stock rom. Can I install the new update with OTA?
Sent from my ASUS_Z00AD using Tapatalk
Any download link?
atahanali_57 said:
My bootloader has unlocked but I recently flashed stock recovery and full stock rom. Can I install the new update with OTA?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Yes.
Links for ZE550ML?
Aaaannd i just sent my phone to RMA just before seeing this thread :|
Check your power manager extended standby apps, because i think all went to off.
thedavefitzy said:
Yes.
Click to expand...
Click to collapse
how ? i think if bootloader have been unlocked then we cant update with OTA
VinzNguyen said:
how ? i think if bootloader have been unlocked then we cant update with OTA
Click to expand...
Click to collapse
Having an unlocked bootloader is fine, not having the correct recovery or the stock ROM is what causes it not to work.
I have an unlocked bootloader and have just updated using the OTA an hour ago.
thedavefitzy said:
Having an unlocked bootloader is fine, not having the correct recovery or the stock ROM is what causes it not to work.
I have an unlocked bootloader and have just updated using the OTA an hour ago.
Click to expand...
Click to collapse
do you use superSU ? xposed ? or only stock rom with unlocked bootloader ?
thedavefitzy said:
Having an unlocked bootloader is fine, not having the correct recovery or the stock ROM is what causes it not to work.
I have an unlocked bootloader and have just updated using the OTA an hour ago.
Click to expand...
Click to collapse
That's incorrect.. i guess you dont have an unlocker bootloade, or you're lying
If you use the official unlock method, you can't update via OTA.
atahanali_57 said:
My bootloader has unlocked but I recently flashed stock recovery and full stock rom. Can I install the new update with OTA?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
thedavefitzy said:
Yes.
Click to expand...
Click to collapse
VinzNguyen said:
how ? i think if bootloader have been unlocked then we cant update with OTA
Click to expand...
Click to collapse
thedavefitzy said:
Having an unlocked bootloader is fine, not having the correct recovery or the stock ROM is what causes it not to work.
I have an unlocked bootloader and have just updated using the OTA an hour ago.
Click to expand...
Click to collapse
gREENNNNN said:
That's incorrect.. i guess you dont have an unlocker bootloade, or you're lying
Click to expand...
Click to collapse
Sent from my GT-I9500
gREENNNNN said:
That's incorrect.. i guess you dont have an unlocker bootloade, or you're lying
Click to expand...
Click to collapse
i think too
So... any1 can provide us OTA link? for ze551 and 550
gREENNNNN said:
That's incorrect.. i guess you dont have an unlocker bootloade, or you're lying
Click to expand...
Click to collapse
That is not incorrect, my bootloader is unlocked via the unofficial method. OTA updates work fine this way and always have done.
I have recently gone back to stock from CM13 by flashing over TWRP with the stock recovery image and then sideloading the stock ROM via ADB, this was about five days ago. I received the update notification this morning and it ran correctly, like it always does.
If you have used the official method to unlock bootloader then you should already know that OTAs probably will not work as this was stipulated in the terms of using the official method.
For 550
fota.asus.com**/delta_package/phone/WW_Z008/formal/WW_2.20.40.136_20151225_8331_user_rel-user-WW_Z008-WW_2.20.40.138_20160107_6192_user_rel-user-WW_Z008-20160108/WW_Z008-20151225-20160107-20160108**.zip
Sorry can't post links, remove the **
Hi,
Yesterday I went back to factory image of MM for XT1572 EU, then I flashed Beta-Super-SU 2.62 for systemless root.
This morning I have a message on phone about security update publish the 9 February..
What I have to do to apply it ?
I was thinking, go into Super-Su, then stick "fully unroot" ( I wonder if after I have to flash back the normal boot image and recovery ? since Super-Su had patched the boot for root..)
Any advices ?
Thanks
psxmail said:
This morning I have a message on phone about security update publish the 9 February..
Click to expand...
Click to collapse
What's your system version? I also own european model xt1572 but I'm missing the OTA, still on Nov., release.
dani_mola said:
What's your system version? I also own european model xt1572 but I'm missing the OTA, still on Nov., release.
Click to expand...
Click to collapse
it's
24.11.18.clack_reteu.reteu.en.EU.retfr
MHP24.49-18
dani_mola said:
What's your system version? I also own european model xt1572 but I'm missing the OTA, still on Nov., release.
Click to expand...
Click to collapse
it's just february security patch nothing else.
c3drik 67 said:
it's just february security patch nothing else.
Click to expand...
Click to collapse
Yes it was in my title, but do I need to unroot to apply it ?
psxmail said:
Yes it was in my title, but do I need to unroot to apply it ?
Click to expand...
Click to collapse
I'll go for a secure way, and IMHO I'll go stock (you can flash stock w/o wiping user data) and after that, apply the OTA.
I think you have to reflash boot and stock recovery.
c3drik 67 said:
I think you have to reflash boot and stock recovery.
Click to expand...
Click to collapse
Just go to supersu and stick unroot completly.
During the install of supersu, the original boot.img is backup. When uroot the supersu restore the boot.img and the recovery.
Then I update succefully the system I will put again TWRP when I back at home.
When I reboot to bootloader i see that the software is modifoed but I flashed the stock rom via fastboot and i see the same, i cant search any software upade, any solution?
Wait for an update or flash an official OTA
Ismael034202 said:
When I reboot to bootloader i see that the software is modifoed but I flashed the stock rom via fastboot and i see the same, i cant search any software upade, any solution?
Click to expand...
Click to collapse
Relock the bootloader.
Official status only show with bootloader locked.
Junior Passos said:
Relock the bootloader.
Official status only show with bootloader locked.
Click to expand...
Click to collapse
Hmmm...
Junior Passos said:
Relock the bootloader.
Official status only show with bootloader locked.
Click to expand...
Click to collapse
That is not correct.
'Official' status will be shown as long as you don't modify the system or boot partitions.
Unlocking bootloader is an official feature offered by Motorola (though it voids warranty) so that does not do anything to the status.
⌲ from my Moto G⁴ Plus / Tapatalk
1chrome said:
That is not correct.
'Official' status will be shown as long as you don't modify the system or boot partitions.
Unlocking bootloader is an official feature offered by Motorola (though it voids warranty) so that does not do anything to the status.
⌲ from my Moto G⁴ Plus / Tapatalk
Click to expand...
Click to collapse
Ok man.
The point here's to solve the problem.
Sent from my XT1572 using XDA-Developers Legacy app
Junior Passos said:
Ok man.
The point here's to solve the problem.
Click to expand...
Click to collapse
2nd post told how to solve the problem. Flash the factory firmware...then take an OTA. You can have system less root and it still say official. Once you change something on the system partition or flash TWRP it will say modified.
Junior Passos said:
Ok man.
The point here's to solve the problem.
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
The point is definitely to solve the problem, which is why we are helping each other here right?
But giving unnecessary instructions will not solve it either. If you don't have a solution, it's best to educate someone on what the implications of the situation is
Unlocking, Custom Recovery, Systemless Rooting.. These do not change it to modified, but changing in system, oem or other partitions do (debloating, xposed or i dont remember all)
According to me, that status doesn't matter, nowhere in daily use...
Best & only way to make it official is to Downgrade to lower version of official ROM than available by OTA (as now available ROM is NPJ25.93-14 install NPJ25.93-11 or lower, not '25.93-14' )
Than you will receive OTA update to latest one '25.93-14' and completing that will result in official status...
NOTE: Installing update by zip, (available here) will not do anything.. And versions that i mentioned are of INDIAN variant, so check & take care of outside variants...
1chrome said:
The point is definitely to solve the problem, which is why we are helping each other here right?
But giving unnecessary instructions will not solve it either. If you don't have a solution, it's best to educate someone on what the implications of the situation is
Click to expand...
Click to collapse
What I meant was that my intention was to help. I already edited the comment.
At no point did he want to disturb. Have fun.
I'm on NPN25. 137-33. Flashed back to my stock backup for various reasons, am now getting a notification for whatever update is available.....a couple of things. How do I disable the update? And is there a stock rom of the latest build available for the US variant that's TWRP flashable? I don't see it. I was on the stock debloated rom which seemed fine but I couldn't get it to root with superuser or magisk.
carnivalrejectq said:
I'm on NPN25. 137-33. Flashed back to my stock backup for various reasons, am now getting a notification for whatever update is available.....a couple of things. How do I disable the update? And is there a stock rom of the latest build available for the US variant that's TWRP flashable? I don't see it. I was on the stock debloated rom which seemed fine but I couldn't get it to root with superuser or magisk.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B6-Tz_7kDyxsczVpLTFjZW9vR28/view
Flash in twrp its latest. 67
dayask said:
https://drive.google.com/file/d/0B6-Tz_7kDyxsczVpLTFjZW9vR28/view
Flash in twrp its latest. 67
Click to expand...
Click to collapse
Thank you. Will it break TWRP though and is it root able?
carnivalrejectq said:
Thank you. Will it break TWRP though and is it root able?
Click to expand...
Click to collapse
Yes u need to flash through twrp... And I think its rootable
.67 is for the Indian G5+, but works on the US variant (RETUS). .35-5 is the most current firmware and .43 is for Verizon users (fixes call/VoLTE issues) of RETUS but is a March security patch instead of May like .35-5. The .67 has a different kernel source and March security patch. I'd go with .35-5. It's available here. But none of these are flashable through TWRP. You can fastboot though...
atrac17 said:
.67 is for the Indian G5+, but works on the US variant (RETUS). .35-5 is the most current firmware and .43 is for Verizon users (fixes call/VoLTE issues) of RETUS but is a March security patch instead of May like .35-5. The .67 has a different kernel source and March security patch. I'd go with .35-5. It's available here. But none of these are flashable through TWRP. You can fastboot though...
Click to expand...
Click to collapse
You lose recovery if you flash through fast boot though right? And so the one posted above you through retus isn't compatible with twrp?
carnivalrejectq said:
You lose recovery if you flash through fast boot though right? And so the one posted above you through retus isn't compatible with twrp?
Click to expand...
Click to collapse
I believe the one posted above linked via gdrive is flashable through TWRP and was created by @GtrCraft and is based off RETIN or RETUE. You loose TWRP, but fastboot it right back.
I was just trying to help answer your original question about the most up to date RETUS firmware. Moto has made it difficult to track with all the variants.
atrac17 said:
I believe the one posted above linked via gdrive is flashable through TWRP and was created by @GtrCraft and is based off RETIN or RETUE. You loose TWRP, but fastboot it right back.
I was just trying to help answer your original question about the most up to date RETUS firmware. Moto has made it difficult to track with all the variants.
Click to expand...
Click to collapse
Thanks for all. What is the fasboot command to flash a zip?
My apologies if this isn't the right place to ask, but the discussion seems to be right in line with my issue. I'm running -35 (RETUS), rooted (SuperSU) and TWRP. I got the notification to update yesterday, and being partly distracted by screaming kids, I accepted.
It, of course, failed. But more importantly, now any power/boot cycle dumps me into TWRP every time. The only way back to the OS is to boot to bootloader and click "start". I honestly could care less about the security update (as I'm sure a TWRP friendly version is on the horizon). But having to go through the bootloader to simply power up/reboot the phone is a royal PITA.
Is there a quick fix to the hook that seems to redirect to the recovery? As bad as that is, I'd live with it if it means I don't have to wipe and start from scratch.
erkme73 said:
My apologies if this isn't the right place to ask, but the discussion seems to be right in line with my issue. I'm running -35 (RETUS), rooted (SuperSU) and TWRP. I got the notification to update yesterday, and being partly distracted by screaming kids, I accepted.
It, of course, failed. But more importantly, now any power/boot cycle dumps me into TWRP every time. The only way back to the OS is to boot to bootloader and click "start". I honestly could care less about the security update (as I'm sure a TWRP friendly version is on the horizon). But having to go through the bootloader to simply power up/reboot the phone is a royal PITA.
Is there a quick fix to the hook that seems to redirect to the recovery? As bad as that is, I'd live with it if it means I don't have to wipe and start from scratch.
Click to expand...
Click to collapse
I'd start from scratch and make a backup of your current now, flash stock .35-5 that I linked above with RSDlite (update if on Verizon - your choice), fastboot TWRP again and restore. I accidentally did it with .35 and this was the process I did to get out of bootloop recovery hell. Hope that helps...
I posted the .43 update if you don't get the update and required it for Verizon.
Hi guys, can I relock the bl again flashing the mm stock? Thanks
Itemt said:
Hi guys, can I relock the bl again flashing the mm stock? Thanks
Click to expand...
Click to collapse
Don't relock bootloader with MM ROM.
(if you already have N firmware, right now)
After flashing MM, you will receive OTA for N, and it will brick your device.
Do it with latest N september patch (available in guide section)
____Mdd said:
Don't relock bootloader with MM ROM.
(if you already have N firmware, right now)
After flashing MM, you will receive OTA for N, and it will brick your device.
Do it with latest N september patch (available in guide section)
Click to expand...
Click to collapse
But, i'm gonna stay on mm, can't i relock again?
Itemt said:
But, i'm gonna stay on mm, can't i relock again?
Click to expand...
Click to collapse
You can, but you need to remember that "don't take OTA in future, never tap update notification"
Also if you sell or give your phone to someone else, give them latest N.
____Mdd said:
You can, but you need to remember that "don't take OTA in future, never tap update notification"
Also if you sell or give your phone to someone else, give them latest N.
Click to expand...
Click to collapse
Thanks bro, Can I use the same nougat flashing (with lock) codes?
Itemt said:
Thanks bro, Can I use the same nougat flashing (with lock) codes?
Click to expand...
Click to collapse
Yes, fastboot commands are same.
hi! i know this is something irrelevant but since this is related to bootloader unlocking,i wanted to question that if i wanted to relock my bootloader which was on the sept 01 patch when unlocked;would i have to flash the same build from the fastboot again to relock it?and will it be safe to install ota updates after relocking the bootloader and reverting to the stock rom?
GeekyTanuj said:
hi! i know this is something irrelevant but since this is related to bootloader unlocking,i wanted to question that if i wanted to relock my bootloader which was on the sept 01 patch when unlocked;would i have to flash the same build from the fastboot again to relock it?and will it be safe to install ota updates after relocking the bootloader and reverting to the stock rom?
Click to expand...
Click to collapse
Only for taking OTA, locked bootloader is not necessary, you can take OTA with unlocked bootloader too.
things to take care of,
don't flash older firmwares than you have at the moment,
As you have september patch, flash september (while relocking too), don't downgrade.
If you downgrade, then don't take OTA. Warned..
____Mdd said:
Yes, fastboot commands are same.
Click to expand...
Click to collapse
Bro, Why am I getting this error?
https://i.imgur.com/hY9Oaab.png
Itemt said:
Bro, Why am I getting this error?
https://i.imgur.com/hY9Oaab.png
Click to expand...
Click to collapse
My bad!
GPT and bootloader won't get flashed if you downgrade, it will fail, you can't flash older versions.
I don't know if it's possible to lock without flashing them, You can try flashing without GPT and Bootloader.
Just a suggestion! You don't need to flash the firmware again, if you are already on it. For eg, If you are already on Sept patch and want to relock, you don't need to flash the ROM again to relock it. Just use the fastboot commands.
I would recommend to leave it unlocked, because if anything went wrong with your device, atleast you will be able to save the data of internal memory atleast!
____Mdd said:
My bad!
GPT and bootloader won't get flashed if you downgrade, it will fail, you can't flash older versions.
I don't know if it's possible to lock without flashing them, You can try flashing without GPT and Bootloader.
Click to expand...
Click to collapse
Thanks bro!