Database Users

MM update brick my phone

I update my phone, but now its stuck on a bootloop, i live in chile now, so i cant send my phone to customer service, i have any option to have the stock firmware and install it?...
Pd: i have the bootloader lock, and i dont have debbuging mode active
Please help me.
Thanks :crying:

Have you tried removing the micro SD then rebooting. That fixed the bootloop for me.

the firmware is corrupted i only can enter to fastboot and recovery mode...

It's unlikely for an OTA to brick a phone. If you flashed any MM ROM, then you should have bootloader already unlocked.
In any case, you can try the MM image from this thread: http://forum.xda-developers.com/moto-x-style/help/howto-enable-band-12-moto-pure-mm-ota-t3267057
You can then boot into recovery and try to sideload the image via "adb sideload name-of-file.zip" to see if that fixes it.

i need the other zip the soak test 24.11.28...

Donkan694 said:
i need the other zip the soak test 24.11.28...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64232697&postcount=774

pinoymutt said:
http://forum.xda-developers.com/showpost.php?p=64232697&postcount=774
Click to expand...
Click to collapse
This is the 23.21.18 thanks... i hate motorola why they didnt upload the OFW

Donkan694 said:
This is the 23.21.18 thanks... i hate motorola why they didnt upload the OFW
Click to expand...
Click to collapse
Actually I believe Moto has a weird naming convention where they name the OTA zip based on the old firmware version, not the new one. There is only one OTA for the Pure and this one should bring you up to the release MM.

pinoymutt said:
Actually I believe Moto has a weird naming convention where they name the OTA zip based on the old firmware version, not the new one. There is only one OTA for the Pure and this one should bring you up to the release MM.
Click to expand...
Click to collapse
I was thinking the same, but for some reason its diferent
Enviado desde mi SM-T320 mediante Tapatalk

Donkan694 said:
I was thinking the same, but for some reason its diferent
Enviado desde mi SM-T320 mediante Tapatalk
Click to expand...
Click to collapse
Just to confirm -- what model are you trying to apply this to -- the Style (which region) or Pure (US)?

pinoymutt said:
Just to confirm -- what model are you trying to apply this to -- the Style (which region) or Pure (US)?
Click to expand...
Click to collapse
It is the pure US....

Donkan694 said:
It is the pure US....
Click to expand...
Click to collapse
Hmm, should be the right one. But the OTA is a patch, meaning you have to have a working stock firmware to update properly. If your firmware is indeed corrupted somehow, the OTA probably won't work correctly -- and like you said there is no official full signed firmware from Moto
If you are bootloader unlocked, you may want to consider flashing one of the MM pre-built ROMs, but if not, you may be screwed for now unless there is a way to fix your firmware (are you able to do a factory reset from the recovery menu?)

i already do the factory reset... the security in this phone its good, but i fail with something the smathphone almost die... i dont lose the hope yet
thanks for everything

WW_20.20.40.164 update

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 **

820 Dual Sim ota probloem

i got a problem thati want to update and i've downloaded a custom rom with android 5.0.2,
so i was told to get a firmware of 5.0.2 then i can flash my custom rom.
But i cant really know how to do.I have now a rooted,unlocked device,and a custom rom only.Please help.

wing90427 said:
i got a problem thati want to update and i've downloaded a custom rom with android 5.0.2,
so i was told to get a firmware of 5.0.2 then i can flash my custom rom.
But i cant really know how to do.I have now a rooted,unlocked device,and a custom rom only.Please help.
Click to expand...
Click to collapse
Welcome to XDA!!
To install custom ROM, you will need to have a S-OFFed device to do so. S-OFFing need hardware tools, and it cost money. XTC2Clip and FireWater are the two known S-OFF tools that work on D820 for now.

iXaidyiu said:
Welcome to XDA!!
To install custom ROM, you will need to have a S-OFFed device to do so. S-OFFing need hardware tools, and it cost money. XTC2Clip and FireWater are the two known S-OFF tools that work on D820 for now.
Click to expand...
Click to collapse
But some in Mainland forums said i can update to 5.0.2 while S-on,they told me to relock the bootloader and flash the firmware(something like files for 5.0.2?) and i can flash a custom rom

wing90427 said:
But some in Mainland forums said i can update to 5.0.2 while S-on,they told me to relock the bootloader and flash the firmware(something like files for 5.0.2?) and i can flash a custom rom
Click to expand...
Click to collapse
If so, why dont you ask that guy from The Mainland forum, he should be the most well known of his own ROM.
Afaik, without S-OFF you can hardly do any modification to the system.

iXaidyiu said:
If so, why dont you ask that guy from The Mainland forum, he should be the most well known of his own ROM.
Afaik, without S-OFF you can hardly do any modification to the system.
Click to expand...
Click to collapse
I tried of course,but that guy is like vanished.So i must have to s-off before i try to OTA?Any other ways to update to 5.0.2?

wing90427 said:
I tried of course,but that guy is like vanished.So i must have to s-off before i try to OTA?Any other ways to update to 5.0.2?
Click to expand...
Click to collapse
OTA (Over The Air) and flashing ROM are of totally two different thing, OTA came from HTC herself while ROM are created by people like us. So now which one is you proceed to do, OTA or flashing ROM?

iXaidyiu said:
OTA (Over The Air) and flashing ROM are of totally two different thing, OTA came from HTC herself while ROM are created by people like us. So now which one is you proceed to do, OTA or flashing ROM?
Click to expand...
Click to collapse
I wanna flash a rom which is 5.0.2,im now in 4.4.4.I flashed a few custom rom and seems that i messed up the system.So i want to flash that rom and i think i have to update to 5.0.2 in order to flash that,right?

wing90427 said:
I wanna flash a rom which is 5.0.2,im now in 4.4.4.I flashed a few custom rom and seems that i messed up the system.So i want to flash that rom and i think i have to update to 5.0.2 in order to flash that,right?
Click to expand...
Click to collapse
Yes, you can search the web with your phone's CID and download the corresponding fw, after that rename the zip according to your phone MID, and place it onto your external SD Card, then boot into bootloader. The fw should be automatically flashed then.

iXaidyiu said:
Yes, you can search the web with your phone's CID and download the corresponding fw, after that rename the zip according to your phone MID, and place it onto your external SD Card, then boot into bootloader. The fw should be automatically flashed then.
Click to expand...
Click to collapse
https://forum.xda-developers.com/de...ock-lollipop-5-0-2-ruus-guide-mt6752-t3279089
Is this what i am looking for?I wonder if a TWRP backup can fix any problem?

wing90427 said:
https://forum.xda-developers.com/de...ock-lollipop-5-0-2-ruus-guide-mt6752-t3279089
Is this what i am looking for?I wonder if a TWRP backup can fix any problem?
Click to expand...
Click to collapse
Want to know if it is suitable or not? Use your CID to identify!
A TWRP backup can fix almost everything but not all.
Sent from my D6503 using XDA Labs

iXaidyiu said:
Want to know if it is suitable or not? Use your CID to identify!
A TWRP backup can fix almost everything but not all.
Sent from my D6503 using XDA Labs
Click to expand...
Click to collapse
I tried to flash the RUU in the previous link and failed.IT said device halted due to large image update.What should i do?

wing90427 said:
I tried to flash the RUU in the previous link and failed.IT said device halted due to large image update.What should i do?
Click to expand...
Click to collapse
You may directly address your question at that thread. More people will be able to notified in such case.
Sent from my D6503 using XDA Labs

iXaidyiu said:
You may directly address your question at that thread. More people will be able to notified in such case.
Click to expand...
Click to collapse
What do you mean:crying:

Ask the questions you raised again in the thread you downloaded the ROM previously. In there, more people will get attention on your problem.

iXaidyiu said:
Ask the questions you raised again in the thread you downloaded the ROM previously. In there, more people will get attention on your problem.
Click to expand...
Click to collapse
Alright,thanks for that!

Relock BL

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!

PPWS29.116-11-13 update failed to install

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