Database Info

[Q] OTA updates after root/unlock?

Will I continue to get OTA software updates if I root and unlock the boot loader (to install TWRP)?
Thanks,
Hish747

Yes, make sure to untick to update the recovery in the debug options
Send from OnePlus One using Tapatalk

Yes.Of course.But it happened to me that the update script showed some errors. I had to fix them by downloading the original files and replacing my system files.

want to love this device but it seems like its always something.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
Sorry wrong thread...

Satras said:
Yes, make sure to untick to update the recovery in the debug options
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Can I dirty flash the nightlies from CM11S if I have just unlocked the bootlader and rooted?

There is no nightly for CM11s just for CM11.
I recommend to do a clean install including factory reset.
Keep in mind that after flashing something, you need to flash root at the end too
Send from OnePlus One using Tapatalk

So we will still get OTA's great! Great phone for costumizations.

ZTube said:
Yes.Of course.But it happened to me that the update script showed some errors. I had to fix them by downloading the original files and replacing my system files.
Click to expand...
Click to collapse
That does not happen if you just unlock, root and install a custom recovery.
Also a custom kernel would be fine
Send from OnePlus One using Tapatalk

Sorry if this is a bit of a n00b question (I know people are sensitive about that!) but I have searched around a bit and not found a solution to this issue. Here's the situation...
So what i've done so far is unlocked the bootloader, installed TWRP, and SuperSU (so I have root). I also unchecked the update recovery box in dev options. When told I need to update I downloaded the update, hit install, the phone reboots and takes me to TWRP. When in TWRP I hit install, navigate to the cache and try to install the update /cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip
When I do that, I get the following:
"
E:Error installing zip file '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Done processing script file
Installing '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error executing updater binary in zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Error flashing zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Updating partition details...
"
Anybody got any ideas?

Seems TWRP expects a MD5 file.
I use CWM as recovery and can install the update OTA. Maybe try CWM recovery
Send from OnePlus One using Tapatalk

Satras said:
Seems TWRP expects a MD5 file.
I use CWM as recovery and can install the update OTA. Maybe try CWM recovery
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Most people that ive read about are using twrp and had no problem updating.

aamir.m.ali said:
Sorry if this is a bit of a n00b question (I know people are sensitive about that!) but I have searched around a bit and not found a solution to this issue. Here's the situation...
So what i've done so far is unlocked the bootloader, installed TWRP, and SuperSU (so I have root). I also unchecked the update recovery box in dev options. When told I need to update I downloaded the update, hit install, the phone reboots and takes me to TWRP. When in TWRP I hit install, navigate to the cache and try to install the update /cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip
When I do that, I get the following:
"
E:Error installing zip file '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Done processing script file
Installing '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error executing updater binary in zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Error flashing zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Updating partition details...
"
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, you gotta open the zip on your pc, modify META-INF/com/google/android/updater-script and remove the code (its in the top part) that mentions the incompatible data error. Then try flashing again.

aamir.m.ali said:
Most people that ive read about are using twrp and had no problem updating.
Click to expand...
Click to collapse
Yeah, I don't like TWRP and got CWM installed, so I can only give support about that [emoji213]
Send from OnePlus One using Tapatalk

Unable to flash CM12 nightlies (STATUS 1)

Hey guys, I decided to go for CM12 since I read about its features. I downloaded the last nightly build (cm-12-20150120-NIGHTLY-falcon.zip) and I booted to recovery mode (clockworkmod 6.0.5.1), then I wiped data/factory reset and flashed the zip. I got these errors:
-- Wiping data . . .
Formatting /data . . .
Formatting /cache . . .
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure . . .
Data wipe complete.
Dalvik Cache wiped.
-- Wiping cache . . .
Formating /cache . . .
Cache wipe complete.
Formatting /system . . .
Done.
-- Installing: /sdcard/0/cm-12-20150120-NIGHTLY-falcon.zip
Finding update package . . .
Opening update package . . .
Installing update . . . (it took about 10 sec)
E: Error in /data/media/0/cm-12-20150120-NIGHTLY-falcon.zip
(Status 1)
Installation aborted.
Click to expand...
Click to collapse
- I also tried with an unofficial build from a post here on xda. I got the same as above.
- I found the official guide to install cyanogenmod (it doesn't specify which version) but I cannot post links so I'm gonna quote the part which I followed:
. . . 6. Select wipe data/factory reset.
7. You have two options for transferring and installing the installation packages. The sideload method is more universal across devices, whereas the push and install method is more commonly used:
Sideload method: select install zip > install zip from sideload. Follow the on-screen notices to install the package. The installer does not necessarily display an "Install complete." message. You can tell the install is complete if there were no fatal error messages and you have regained control over the menu . . .
Click to expand...
Click to collapse
and it showed this:
Sideload started . . .
Now send the package you want to apply to the device with "adb sideload <filename>" . . .
Restarting adbd . . .
Finding update package . . .
Opening update package . . .
Installing update . . .
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed; no such volume
E: Error in /tmp/update.zip
(Status 1) (again)
Installation aborted.
Click to expand...
Click to collapse
GUYS, I will be very gratefull if you help me to solve this

I'm getting this error too but I have a different phone.

I fixed it
Sunjay140 said:
I'm getting this error too but I have a different phone.
Click to expand...
Click to collapse
Hey, I fixed it. You just have to download CM11 latest build and flash it. At least it worked for me!
Then if you want cm12 just update it from the updater.
I hope it works for u :laugh:

deivideliseo88 said:
Hey, I fixed it. You just have to download CM11 latest build and flash it. At least it worked for me!
Then if you want cm12 just update it from the updater.
I hope it works for u :laugh:
Click to expand...
Click to collapse
+1 Thanks
This is so strange but it worked. I thought of installing CM11 then going to CM12 but I thought that it would have been pointless but it worked after all. I have a S4 Mini so it's probably a bug in CM12. Thanks again.

I am having this same problem, I have 41.18 bootloader, after converting my 1034 to a 1032 gpe. Now I can have 4.44 moto stock, 4.4.4 gpe stock, cm11, but not CM12, have tried all recoveries, to no avail. Same as OP.
However I tried going to CM11, then upgrading, but it never makes it past the boot screen after failing the flash with status 1

Hello friends.
I have the same error.
try to update a lollipop in every possible ways.
I CM11-20150103 since the last CM can not be downloaded from the website.
The RECOVERY I use is the (TWRP 2.8.1).
I would appreciate if someone makes a detailed step by step tutorial or load the last NIGHTLY of CM11.
Thank You!

Download link for cm11
CM's official website does not link to a cm 11 download, please could someone post a download link please

HERE IS YOUR FIX, be careful!!
FIRST THING FIRST, THIS IS DANGEROUS. DO IT AT YOUR OWN RISK.
Myself and one other person have successfully done this. If you have success as well, please post here. What you DO NOT want to flash, and is the cause of bricks is motoboot.img that is older than what you have now. Just dont mess with it.
What you can do, is flash gpt.bin to get the partition tables re-partitioned to get you back to be able to flash roms from CWM, TWRP, Philz, etc.
That being said, this is my PERSONAL experience, and am only sharing because it got me out of GPE lollipop hell, and I was terrified of the bricks, like everyone else. I will attempt to be more clear in my OP.
I have an XT1034 that I converted to GPE to flash 5.0 Lollipop OTA and it gave me the new bootloader 41.18. I couldnt get to CM12 due to Status 7, and I could only flash 4.4.4 stock, lollipop stock, or CM11, any flashing to CM12 always gave errors about Status 7. Others have reported not being able to wipe /data or /system or mount either in any recovery. The problem is the updated partition table and here is the solution:
IF YOU DO NOT FOLLOW THIS DIRECTION YOU WILL HARD BRICK. DO NOT RUN THE BATCH FILE IN THE DOWNLOAD. IT CONTAINS 4.4.2 motoboot.img and YOU WILL BRICK. ONLY RUN THE COMMANDS LISTED BELOW!!!
ALSO DO NOT use an older gpt.bin, it must be 4.4.2 or newer!! Use the link below to get a 4.4.2 XT1034 stock rom.)
I flashed a 4.4.2 GPT.bin from this: US_retail_XT1034_KXB20.9-1.8-1.4_CFC.xml.zip (http://motofirmware.com/files/getdow...-14-cfcxmlzip/)
If you want to try the same thing, you can extract gpt.bin from the zip and run this: (ONLY!!)
Code:
fastboot flash partition gpt.bin
then download philz here: http://fs1.d-h.st/download/00145/DEw...8.7-falcon.img
rename to philz.img
fastboot flash recovery philz.img
Hold vol - and power, to reboot into recovery, then
format /system
format /data
Download the latest nightlies and gapps and push them like this:
adb push cm-10-10-1000.zip /data/media/0
Reboot into recovery, and flash cm12 and gapps.

WOW d33dvb!!!!
You are AWESOME!!!.....
Just came GPE 4.4.4 STOCK I put into my MOTO G.
And then always put CM11. Now I'm sure you indicate that the problem is damaged partition tables.
How do I know the bootloader i have?
Another thing that happens to me and I guess that is the partition table. When I flashed some recovery is automatically deleted after a while.
When I encourage you indicate me do what I notice.
Again thank you very much for your great contribution !!!
Sorry for my bad english My from is Argentina....

At last came the day !!
Today I did what you recommended d33dvb.
It worked all right. Right now I'm enjoying CM12.
I flash the GPT from 4.4.4.
Great HELP!! Thanks!! THANKS VERY MUCH!!
I happy!!!

[Q] Error trying to install 5.1 OTA

I am trying to install the 5.1 OTA. I am stock & non-rooted. I recently booted into TWRP but I didn't flash it. When the OTA starts to install I get the Android with the exclamation mark. The only word is Error. I press the power button and volume-up and the error is...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
Apparently even doing a fastboot boot into TWRP mucked up something. Anyway to correct that file to take the OTA again? I really don't wanto to do a factory reset.

xda6969 said:
I am trying to install the 5.1 OTA. I am stock & non-rooted. I recently booted into TWRP but I didn't flash it. When the OTA starts to install I get the Android with the exclamation mark. The only word is Error. I press the power button and volume-up and the error is...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
Apparently even doing a fastboot boot into TWRP mucked up something. Anyway to correct that file to take the OTA again? I really don't wanto to do a factory reset.
Click to expand...
Click to collapse
You don't need to do a factory reset. Just remove -w from flash-all.bat and flash factory image without loosing data.
P:S: Also there are a lot OTA update threads yet.

zagorteney said:
You don't need to do a factory reset. Just remove -w from flash-all.bat and flash factory image without loosing data.
P:S: Also there are a lot OTA update threads yet.
Click to expand...
Click to collapse
Will this method correct the install-recovery.sh file so future OTA updates will apply?

xda6969 said:
I am trying to install the 5.1 OTA. I am stock & non-rooted. I recently booted into TWRP but I didn't flash it. When the OTA starts to install I get the Android with the exclamation mark. The only word is Error. I press the power button and volume-up and the error is...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
Apparently even doing a fastboot boot into TWRP mucked up something. Anyway to correct that file to take the OTA again? I really don't wanto to do a factory reset.
Click to expand...
Click to collapse
zagorteney said:
You don't need to do a factory reset. Just remove -w from flash-all.bat and flash factory image without loosing data.
Click to expand...
Click to collapse
Flash-all can be used to automate the process of flashing a factory image, but OP is having issues with OTA.
xda6969 said:
Will this method correct the install-recovery.sh file so future OTA updates will apply?
Click to expand...
Click to collapse
Read this thread's first post to know how you can upgrade to 5.1.
I think you can flash the ota update file (once it downloaded, it should be somewhere in your device - EDIT: zagorteney posted the exact location below, /cache) with TWRP, like you would a normal custom rom, and TWRP will output more information about why the OTA isn't applying.

@beekay201
You are wright. I've thought that OP just want to update to 5.1 anyway. Update.zip is located in /cache.

I had the same issue, then when I made the decision to use the flash-all script, I got another error about missing the system.img when it was in the same folder as everything else. I ended flashing all the files manually.

Ki77erB said:
I had the same issue, then when I made the decision to use the flash-all script, I got another error about missing the system.img when it was in the same folder as everything else. I ended flashing all the files manually.
Click to expand...
Click to collapse
It's common problem with flashing 5.1.

zagorteney said:
It's common problem with flashing 5.1.
Click to expand...
Click to collapse
I think I'm going to do the flash-all.bat. I've done that before and since I can save my app data by omitting -w then this method should be fine. I am going to make sure I have the latest adb and fastboot first so hopefully I don't get the common missing system.img error. Once I do this, will it correct the install-recovery.sh file so I can take future OTAs again? Also, the -w retains all app settings and data right?....it just doesn't preserve the internal SD card data?

xda6969 said:
I think I'm going to do the flash-all.bat. I've done that before and since I can save my app data by omitting -w then this method should be fine. I am going to make sure I have the latest adb and fastboot first so hopefully I don't get the common missing system.img error. Once I do this, will it correct the install-recovery.sh file so I can take future OTAs again?
Click to expand...
Click to collapse
As I know, you shouldn't be rooted or make any other modifications with system to get OTA.

zagorteney said:
As I know, you shouldn't be rooted or make any other modifications with system to get OTA.
Click to expand...
Click to collapse
That's correct. I am no longer rooted and I haven't modified any system files intentally. Somehow, just booting into TWRP made a change to that file. I never had this issue when I was using CR.

zagorteney said:
As I know, you shouldn't be rooted or make any other modifications with system to get OTA.
Click to expand...
Click to collapse
Yep; SuperSU for example modifies /system/etc/install-recovery.sh (or /system/bin/install-recovery.sh) and a couple more files.
xda6969 said:
That's correct. I am no longer rooted and I haven't modified any system files intentally. Somehow, just booting into TWRP made a change to that file. I never had this issue when I was using CR.
Click to expand...
Click to collapse
Never heard of TWRP modifying /system on its own.

beekay201 said:
Yep; SuperSU for example modifies /system/etc/install-recovery.sh (or /system/bin/install-recovery.sh) and a couple more files.
Never heard of TWRP modifying /system on its own.
Click to expand...
Click to collapse
Ahh...I did install SuperSU to unroot. But I also installed it on a N10 to unroot it and it took the OTA without a hitch.
I did the flash-all.bat after removing the -w. Everything went fine. I hope the install-recovery.sh file was corrected. Thanks all for the help!

Problem while updating CM12

Since I've CM12 in my OPO I can't update the nightlies using OTA. I can download the update but when it restarts to recovery to install the new update I have always the same error and I have to do the wipes with each update to solve it. I've been looking for a solution in xda but I haven't found it. See the attachment please. Thanks in advance.

it's the same for me as I have red lines after reboot and upade is installed

Jjul said:
it's the same for me as I have red lines after reboot and upade is installed
Click to expand...
Click to collapse
I've the error but the ROM doesn't update

I got the error too, manually flash the file that gets downloaded into the cmupdater folder and it updates.

Kitch16 said:
I got the error too, manually flash the file that gets downloaded into the cmupdater folder and it updates.
Click to expand...
Click to collapse
Yeah. I've tried it before but when I restart the OPO after install manually the zip, the screen stuck at "Finishing boot" and I have to do wipes again

[7.0/8.0][WW] ZE520KL FOTA Update Links

Moving forward, let's add OTA Update links here for users who cannot receive OTA notifications.
Flash via stock recovery. If your system has been modified, you may need to flash stock system image or the stock firmware.
IMPORTANT: Do not boot to system immediately!! Flash the no-verity file via TWRP first, then reboot:
No-verity file
[7.0] ZE520KL OTA (for WW SKU only)
WW_14.2015.1701.13
WW_14.2020.1703.28
WW_14.2020.1704.38
WW_14.2020.1706.53
WW_14.2020.1708.56
WW_14.2020.1709.68
WW_14.2020.1711.75
WW_14.2020.1711.80
WW_14.2020.1711.81
WW_14.2020.1712.85
[8.0] ZE520KL OTA (for WW SKU only)
WW_15.0410.1712.31 (Initial release. Expect some bugs. Must be on latest Nougat build.)
WW_15.0410.1801.40
WW_15.0410.1802.44
WW_15.0410.1803.53
WW_15.0410.1803.55
WW_15.0410.1804.61
WW_15.0410.1804.62
WW_15.0410.1806.65
WW_15.0410.1806.68
credits:
@gkillershots for the WW_14.2015.1701.13 link
@spica1234 for the WW_14.2020.1703.28 and .38 links
@Eng.Raman for the WW_14.2020.1706.53, .56, .68, .75, .80, .81 and WW_15.0410.1712.31, .40, .44, .53, .61, .65, -68 links
@vaidhy2007 for the WW_14.2020.1712.85 link
@AL_IRAQI for the WW_15.0410.1803.55 link
@pop4xda for the WW_15.0410.1804.62 link
(Still looking for anyone who wish to provide FOTA links for ZE552KL.)

How about link for ZE552KL (Z012D)?

cdanthien said:
How about link for ZE552KL (Z012D)?
Click to expand...
Click to collapse
I tried to get it too, but since my phone is the z017, it can only see ota's for itself.
but the ota only patches system, boot and radio, so if someone is couraged to port, it may be not that hard.
for z017 ota links, mention me everytime a new one appears and i'll give the link for it.
if someone unlocked a z012 with unofficial method, contact me so I help you get the link to post here and help the community.

gkillershots said:
I tried to get it too, but since my phone is the z017, it can only see ota's for itself.
but the ota only patches system, boot and radio, so if someone is couraged to port, it may be not that hard.
for z017 ota links, mention me everytime a new one appears and i'll give the link for it.
if someone unlocked a z012 with unofficial method, contact me so I help you get the link to post here and help the community.
Click to expand...
Click to collapse
Give me guide for Z012D, i will guide again to my friend. Thanks

cdanthien said:
Give me guide for Z012D, i will guide again to my friend. Thanks
Click to expand...
Click to collapse
hit the update button, It'll give you the update notification, then open the folder /data/data/com.asus.dm/files/
If you don't want to continue from here, just pass me the tree.xml
If you want, open it on an editor like notepad++
then look into the <value> that has a link inside.
example: <value>http://fota.asus.com/delta_package/phone/WW_Phone/formal/14.2015.1701.8-user-WW_Phone-14.2015.1701.13-user-WW_Phone-QWWSSS/WW_ZE520KL-14.2015.1701.8-14.2015.1701.13-fota-user.zip.dd_20170317_151859.dd</value>
copy ONLY the link, put into the browser and It'll download you an dd file
ex: http://fota.asus.com/delta_package/...5.1701.13-fota-user.zip.dd_20170317_151859.dd
open this dd file on notepad ++
the <objectURI> is the link for the ota

gkillershots said:
hit the update button, It'll give you the update notification, then open the folder /data/data/com.asus.dm/files/
If you don't want to continue from here, just pass me the tree.xml
If you want, open it on an editor like notepad++
then look into the <value> that has a link inside.
example: <value>http://fota.asus.com/delta_package/phone/WW_Phone/formal/14.2015.1701.8-user-WW_Phone-14.2015.1701.13-user-WW_Phone-QWWSSS/WW_ZE520KL-14.2015.1701.8-14.2015.1701.13-fota-user.zip.dd_20170317_151859.dd</value>
copy ONLY the link, put into the browser and It'll download you an dd file
ex: http://fota.asus.com/delta_package/...5.1701.13-fota-user.zip.dd_20170317_151859.dd
open this dd file on notepad ++
the <objectURI> is the link for the ota
Click to expand...
Click to collapse
I edited ZE520KL to ZE552KL, but i received "File not found"

cdanthien said:
I edited ZE520KL to ZE552KL, but i received "File not found"
Click to expand...
Click to collapse
I tought you would do it on a ze552kl
if it were that simple, I would've done it myself

any guide how to install this? using twrp or stock recovery?

updated Tizen V2.1 here : https://forum.xda-developers.com/zenfone-3/development/rom-tizen-rom-nougat-1701-8-ze552kl-t3573231

gkillershots said:
i tried to get it too, but since my phone is the z017, it can only see ota's for itself.
But the ota only patches system, boot and radio, so if someone is couraged to port, it may be not that hard.
For z017 ota links, mention me everytime a new one appears and i'll give the link for it.
If someone unlocked a z012 with unofficial method, contact me so i help you get the link to post here and help the community.
Click to expand...
Click to collapse
thank you so much!!

Z520KL : 14.2020.1703.28
14.2020.1703.28

Thanks for uploading the new update, we are appreciate it :good:

can I update? I am rooted, no changes made except flashing TWRP

mecoromeo said:
can I update? I am rooted, no changes made except flashing TWRP
Click to expand...
Click to collapse
Make a backup first, flash stock recovery, then flash the OTA updates. Remember to flash no verity file before first boot

animaanimus said:
Make a backup first, flash stock recovery, then flash the OTA updates. Remember to flash no verity file before first boot
Click to expand...
Click to collapse
Is the flashfire app effective? I tried it and updated to the latest ze520kl update. Everything went smoothly, but, I am not sure why but my wifi was disabled. I tried clearing cache and did not work. Not sure if the app did not work correctly or if it was an issue with the latest update. That said i downgraded using the same tool and got everything working again.
I think there is an issue with the new update. What do you guys think? Did any of you guys also had an issue with the new update?
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
spica1234 said:
Z520KL : 14.2020.1703.28
14.2020.1703.28
Click to expand...
Click to collapse
I had an issue with the update wherein my wifi was disabled and i couldn't figure out how to fix it. I rebooted, clearing cache, i even tried flashing it again and resetting everything. None worled.
I went back to the previous version and now my phone is working fine.
Did anyone else encounter this issue with this update? If so, please help me to avoid it from happening, i want to try this update

mecoromeo said:
Is the flashfire app effective? I tried it and updated to the latest ze520kl update. Everything went smoothly, but, I am not sure why but my wifi was disabled. I tried clearing cache and did not work. Not sure if the app did not work correctly or if it was an issue with the latest update. That said i downgraded using the same tool and got everything working again.
I think there is an issue with the new update. What do you guys think? Did any of you guys also had an issue with the new update?
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
I had an issue with the update wherein my wifi was disabled and i couldn't figure out how to fix it. I rebooted, clearing cache, i even tried flashing it again and resetting everything. None worled.
I went back to the previous version and now my phone is working fine.
Did anyone else encounter this issue with this update? If so, please help me to avoid it from happening, i want to try this update
Click to expand...
Click to collapse
This is what I do follow while applying Delta OTA.
No need to flash back stock boot/recoveries and no need as well to reinstall twrp back.
Steps using FlashFire, Flash as zip/ota option:
1. Load 'UL-ASUS_Z017D_1-WW-14.2015.1701.8-user'
2. Load 'WW_ZE520KL-14.2015.1701.8-14.2015.1701.13-fota-user'
3. Load 'WW_ZE520KL-14.2015.1701.13-14.2020.1703.28-fota-user'
4. Remove tickmark from 'Inject SuperSU'
5. Add SuperSU zip, Which I've modded according to asus ramdisk of ours. Which is attached in here under my post.
Flash!
Note: FlashFire will take a minute or two to load flash, have patience.
* Reason I've to edit standard SuperSU package was for 'init.asus.rc' file in our ramdisk, which unset PATH during 'on init' event. So i added those params back in supersu's zip to append '/su/bin' in PATH

spica1234 said:
This is what I do follow while applying Delta OTA.
No need to flash back stock boot/recoveries and no need as well to reinstall twrp back.
Steps using FlashFire, Flash as zip/ota option:
1. Load 'UL-ASUS_Z017D_1-WW-14.2015.1701.8-user'
2. Load 'WW_ZE520KL-14.2015.1701.8-14.2015.1701.13-fota-user'
3. Load 'WW_ZE520KL-14.2015.1701.13-14.2020.1703.28-fota-user'
4. Remove tickmark from 'Inject SuperSU'
5. Add SuperSU zip, Which I've modded according to asus ramdisk of ours. Which is attached in here under my post.
Flash!
Note: FlashFire will take a minute or two to load flash, have patience.
* Reason I've to edit standard SuperSU package was for 'init.asus.rc' file in our ramdisk, which unset PATH during 'on init' event. So i added those params back in supersu's zip to append '/su/bin' in PATH
Click to expand...
Click to collapse
Thanks. Haven't tried it yet, but i will though.
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"

mecoromeo said:
Thanks. Haven't tried it yet, but i will though.
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"
Click to expand...
Click to collapse
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"

mecoromeo said:
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"
Click to expand...
Click to collapse
I'm facing the same issue after OTA update!
My fone is rooted too!

mecoromeo said:
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"
Click to expand...
Click to collapse
Hello,
Sorry for that I got it now why it's happened.
Follow an extra step.
Extract ".28" firmware replace META-INF folder with attached below.
Zip the '.28' firmware back and rename it as 28_dummy.zip
Now follow above flashfire load 1-4 steps and as a 5th step add '28_dummy.zip' and as a 6th step as above supersu step and it'd definately work.