Database Users

[Updata]WW-4.21.40.223(andriod M)

ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V4.21.40.223 for WW SKU only* (andriod M)
Improvement Item:
1)Improve Wi-Fi/Bluetooth stability
2)Update Security patch
3)Improve system stability
4)Support India SOS call (India only)
Full Rom Download Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-4.21.40.223-user.zip

Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks

fredlamour said:
Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks
Click to expand...
Click to collapse
It is, but not if your bootloader is unlocked.

Rodepo said:
It is, but not if your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks.
bootloader unlocked so no way.
I am thinking about jumping into a lineage rom.

VoLte support?? in this new update....

I felt like this was happening today! came in and here it is. Updating right now.
Thanks

any update for this update of asus zenfone 2

optimumgiant said:
any update for this update of asus zenfone 2
Click to expand...
Click to collapse
Hello. This forum is for galaxy 8.07. We don't know about zendroid 2 or whatever you ask.
Just joking. This IS for zenfone 2.
I'm currently using the update. Screen flickering has stopped for the time being.

i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance

crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
it seems you are first. Give it a try and find it out for yourself and let us know!

crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
My way is unroot and uninstall Xposed first, than sideload the whole rom with stock recovery.
I had failed to OTA many times because I modified some system files (forgot to restore them), so now I just reflash rom to save the trouble.

Wifi auto-connect problem seems fixed and the phone has more available ram after "power and boost".
It's worth to update imo.
Battery life seems the same

All sensors working with this version in my brazilian zenfone 2 z00a.

Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.

I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit

audit13 said:
After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
I had unlocked the BL before so i updated and directly tried regaining root and xposed but failed (softbrick at asus loading screen), I confirm that applying the whole ota from sideload sort of relocks the bootloader and you must do it again, now it is booting and rebuilding the dalvik cache.

audit13 said:
I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
In conclusion you did only flashed stock recovery and, from that, you flashed the whole zip in the first post, right?
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

timbernot said:
Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.
Click to expand...
Click to collapse
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642

timbernot said:
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
can you please share your adblock app with us.
thanks

crownpiyush said:
can you please share your adblock app with us.
thanks
Click to expand...
Click to collapse
its a add-on downloaded and installed from ` tools ` in firefox browser settings :good:
ps, i had trouble using adblockplus add-on from firefox ,when viewing XDA pages ..they turned out blank , XDA i think prevented the use of such adblock , so now i use the less blocking add-on in firefox called `uBlock`
its good enough

Unexpected Android system update, booted into TWRP

Hello,
Today I received a Motorola Android system update. I did not expect this to happen, because my device has an unlocked bootloader and is rooted, and I have TWRP installed. I never received a system update before in the 1,5 years that I have it.
After the update was downloaded, it started installing by verifying the update and then initiated a reboot. The reboot however ended up in TWRP.
What should I do now? Just reboot? Will that cancel the update or break anything?
Is there any way that I can manually complete the installation of the update?

if you are rooted with twrp installed, just copy update file from /cache to your internal storage. Then unroot your device (discard any changes in /system partition via flashing stock system.img), flash stock recovery and apply update from recovery.
I suppose, file you have being downloaded is just security update.
Please pm me, if this file large than 500MB ;

The update file is named Blur_Version.24.61.52.lux_reteu.reteu.en.EU.zip. It is 69,5 MB (69514015 bytes).
This is the first time I receive a system update (I unlocked the bootloader and rooted my phone right at the start). Strange thing is that the contents of the file all have a timestamp of 14 februari 2014 17:43. I can't believe I received a three year old update. The Moto X Play did not even exist three years ago.

I installed the update. It was 24.201.5.en.EU, containing the security patches of october 2016. So your assumption was right. Still strange that this is the first update I received in 1,5 year.

gewe said:
I installed the update. It was 24.201.5.en.EU, containing the security patches of october 2016. So your assumption was right. Still strange that this is the first update I received in 1,5 year.
Click to expand...
Click to collapse
Hello there, could you let me know how you installed the update (step-by-step if possible), I am having the same problem while updating as my moto x play tries to reboot during the install and I get the TWRP interface. Thanks

gamoraw said:
Hello there, could you let me know how you installed the update (step-by-step if possible), I am having the same problem while updating as my moto x play tries to reboot during the install and I get the TWRP interface. Thanks
Click to expand...
Click to collapse
I followed the instructions I found here, with the following changes:
skip flashing bootloader.img and logo.bin (unlocked bootloader);
skip flashing recovery.img (you want to keep TWRP);
skip erase userdata (keep your data).
Some people advise against not erasing useradata, but I never had a problem skipping that step.

[SOLVED] Official update after relocking bootloader?

Hello!
So, you've been able to get official update (through System > Update) after relocking bootloader?
Like one month ago I've relocked the bootloader by installing B320 firmware from Firmware Finder. However, System > Update wasn't showing any update. I'm not sure, but perhaps I had to wait some time like 1-2 days to check for update?
I'm thinking to try this again as I wanna try the new B350 update. Yeah, I know that there are download links for that firmware, but I'd like to get it through the official way.
SOLUTION: here.

I got my Ota while I was rooted, had twrp with unlocked bootloader. This was in marshmallow. I unrooted, flashed the official recovery L11 recovery (my phone is L12) and relocked (causing a low level format of the data partition. After this, I booted back into the cleaned marshmallow without my sim card. I inserted the sim card after and rebooted. Checked for the update which I had previously downloaded B330 , but it wasn't detected and was re-downloaded. The update ran successfully without issues at all. Everything seems to work as it should, including themes.
I haven't rooted yet. I'll have a go at it this evening if I have some time.

#Henkate said:
Hello!
So, you've been able to get official update (through System > Update) after relocking bootloader?
Like one month ago I've relocked the bootloader by installing B320 firmware from Firmware Finder. However, System > Update wasn't showing any update. I'm not sure, but perhaps I had to wait some time like 1-2 days to check for update?
I'm thinking to try this again as I wanna try the new B350 update. Yeah, I know that there are download links for that firmware, but I'd like to get it through the official way.
Click to expand...
Click to collapse
rodlane said:
I got my Ota while I was rooted, had twrp with unlocked bootloader. This was in marshmallow. I unrooted, flashed the official recovery L11 recovery (my phone is L12) and relocked (causing a low level format of the data partition. After this, I booted back into the cleaned marshmallow without my sim card. I inserted the sim card after and rebooted. Checked for the update which I had previously downloaded B330 , but it wasn't detected and was re-downloaded. The update ran successfully without issues at all. Everything seems to work as it should, including themes.
I haven't rooted yet. I'll have a go at it this evening if I have some time.
Click to expand...
Click to collapse
Im sorry, i have forgot to mention that i have solved my problem.
Ive wrote here how ive relocked bootloader and updated to B350.

update to android O using flashfire

Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.

mousefai0922 said:
Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.
Click to expand...
Click to collapse
There is a thread on this ongoing at literally this moment. My experience is that FF with the OTA does not work. Others have reported that it does. So YMMV. The fastboot method worked for me. FF with full factory images may work, but since radio is still recommended to be flashed via fastboot you might as well do everything via fastboot.

mousefai0922 said:
Hi guys
Currently, i have a nexus 6p, 7.1.2, rooted and bootloader unlocked.
Got the android O ota updates on my phone. however, wanted to know is it safe to upgrade now using flashfire?
1st, any problems when using flashfire to do the updates
2nd, any problems on android O itself?
3rd, do i still have root after the udpate?
Thanks.
Click to expand...
Click to collapse
I was trying FF this morning, lastest update 0.71, rooted with Magisk , TWRP and it failed.
Got stuck on a black screen for more than five minutes until I forcefully rebooted the device.
waiting for the factory images I guess.

wizardwiz said:
I was trying FF this morning, lastest update 0.71, rooted with Magisk , TWRP and it failed.
Got stuck on a black screen for more than five minutes until I forcefully rebooted the device.
waiting for the factory images I guess.
Click to expand...
Click to collapse
it seem like the android O have bugs and problem itself, and with now the failing flashfire problems... i think i should wait

GroovyGeek said:
There is a thread on this ongoing at literally this moment. My experience is that FF with the OTA does not work. Others have reported that it does. So YMMV. The fastboot method worked for me. FF with full factory images may work, but since radio is still recommended to be flashed via fastboot you might as well do everything via fastboot.
Click to expand...
Click to collapse
it seem like the android O have bugs and problem itself, and with now the failing flashfire problems... i think i should wait

I just used FF ver. 0.72 on 2 rooted, twrp'd, supersu'd Nexus 6P's and flashed the full factory Sept. 2017 OPR6 image that was published this morning. FF worked like a champ. Just don't update the bootloader and radio with FF.

I am still on 6.0.1 (Build MTC20L), upgraded using FF. If i want to move to 8.0.0 (OPR6.170623.017, Sep 2017), what builds do I need to stop at along the way? I was guessing at the very least 7.1.1 (NUF26N, Mar 2017, Verizon Only), but want to be sure.

states_enemy said:
I am still on 6.0.1 (Build MTC20L), upgraded using FF. If i want to move to 8.0.0 (OPR6.170623.017, Sep 2017), what builds do I need to stop at along the way? I was guessing at the very least 7.1.1 (NUF26N, Mar 2017, Verizon Only), but want to be sure.
Click to expand...
Click to collapse
No, just use the latest full Google 8.0 image with FF. Untick the bootloader and modem partitions. Your phone will boot up with 8.0, then update the bootloader and modem (radio) separately. Best to flash with fastboot, but there are TWRP flashable zips around here.

v12xke said:
No, just use the latest full Google 8.0 image with FF. Untick the bootloader and modem partitions. Your phone will boot up with 8.0, then update the bootloader and modem (radio) separately. Best to flash with fastboot, but there are TWRP flashable zips around here.
Click to expand...
Click to collapse
I'll be using FF, however I don't recall ever updating the bootloader or modem in the past. I don't need to do that, do I?

states_enemy said:
I'll be using FF, however I don't recall ever updating the bootloader or modem in the past. I don't need to do that, do I?
Click to expand...
Click to collapse
You know what they say about not fixing it if it's not broken, but.... While bootloader and modem are independent of the android version itself, you should generally try to keep them up to date. Not sure how a bootloader would be improved, but there are constant tweaks to the radio going on. If you don't have a current, working version of ADB/fastboot on your PC this would be a good time to get it set up and working properly ( ie. when you are NOT having a problem). There is virtually no way you can screw up flashing these, and they take less than a second or two each. You can find the *.img files in the root of any full Google image. As a primer, open up the flash-all.bat file there and read the script. Change the file extension from *.bat to *.txt and open with Notepad. There you will find the fastboot commands for flashing these two. Best of luck.

Device failed verification - is there a way to clear this message?

Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?

Sovjohn said:
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Click to expand...
Click to collapse
Hello,
my doubt is that you flashed a different firmware version from the one you had, thus corrupting the device's oem file. Could you post which was the latest complete firmware without this problem and the last one you downloaded and flashed? ( ex. L21CxxxB382 & LxxCxxxB506 ).
Let me know this info ...

Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.

Sovjohn said:
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Click to expand...
Click to collapse
Yep, you used correct file but anyhow the firmware has been corrupted.
I think you have some ways to solve...
1 - if you have stock recovery, reboot into it and
download and flash the same latest firmware.
If you do not have it, you can extract (with huawei update extractor) it
(should be recovery1.img) from B506 firmware (update.zip) you already got,
then can be flashed via fastboot commands.
2 - Flash a previous or B380 firmware via HuRUpdater, then
update to latest via Firmware Finder with dns/vpn method.
3 - Repeat the whole job you done with B506 firmware. (via HuRupdater)
4 - Reboot recovery, reflash L21OEMinfo file, dual sim one, then the latest firmware again...
P.S.: method 1, 2, 4 will re-lock the bootloader, no problem if still you got the code...
Beware method 4, after you flash the oeminfo file do not shout down, reboot to bootloader
and unlock it again with the code. Device will reboot into twrp, then flash B506 firmware.
Good luck and let the community know..