yashsingh1/xdaforums huggingface dataset:
[Asus Zenfone 9] Treklof:
Thanks for sharing!

Where did you put the OTA? root/data/ota ? Or just the internal memory?

Update-service does not pick up my file:

UL-ASUS_AI2202-ASUS-33.0804.2060.165-user-1.1.1-2308-user.zip

Im trying to go from 142->165

Can you see, what im missing? Thanks for helping!

Ok: Sorry the name was still wrong:

UL-ASUS_AI2202-ASUS-33.0804.2060.165-1.1.1-2308-user.zip was picked up but did fail!

How did you flash the whole 142 again? Sideload with the original recovery or TWRP?

Perhaps it would be sufficient to flash the original 142 boot-image?
[Asus Zenfone 9] sunchau:
sd root
[Asus Zenfone 9] andlommy:
You can only flash these OTA files over original ROM, no twrp or anything

Download Asus firmware from Asus site, put it to root of internal memory, install it when Asus picks it up (rename the file to represent higher version of it doesn't). Then you can flash these OTA files
[Asus Zenfone 9] reyqn:
Do you lose root or any user data flashing the full firmware? Can I flash 142 over 100 or should I find the 100 firmware?
[Asus Zenfone 9] andlommy:
You loose root, but if you have unlocked bootloader, you can always get magisk back. Suggest to do it after after all the ota.
[Asus Zenfone 9] andlommy:
You need to install full stock firmware before flashing OTAs. It tells you your boot partition hash doesn't match what it expects.
[Asus Zenfone 9] Makavelli-:
Thanks for the information! I'm going to do a flash campaign with all the OTAs very soon, but would like to be prepared as best as possible.

For the Update from 218 to A14 you mentioned the issue with the security levels (which is understood so far). But how did you solve it that the phone is picking the first A14 file up? Did you just put a "fake" date in the filename?

Furthermore, during flash of the initial 142 all data on the phone will be lost, right?

Last question: what about the "rom extention" number, how do i know it? Its understood that the middle number need to be a 1 in any case (e.g. 1.1.1), but what about the other numbers, does it not matter or did i need to translate the correct number from somewhere?

Cheers
[Asus Zenfone 9] andlommy:
Just use UL-ASUS_AI2202-ASUS-99.9999.9999.999-9.9.9-2912-user.zip whenever renaming the files.

Data is not lost during update, but you MUST flash over an entirely yncustomized image. Any twrp, magisk or anything alike will prevent you from updating. If customized phone, make sure to flash Asus full firmware first. That doesn't wipe your data either
[Asus Zenfone 9] Makavelli-:
Tried the first update from 142 to 165 and it worked well so far.

But renaming the file to "UL-ASUS_AI2202-ASUS-99.9999.9999.999-9.9.9-2912-user.zip" did not work, need to rename it according the txt fileand placeds just a 1.1.1 for the "rom extention" number.

Will further proceed with the other ones...

Edit: Finally done with all updates, have the latest A14 now. Thanks for providing the files and support, great to have at least a good working Community 👌💪
[Asus Zenfone 9] reyqn:
I'm still not sure how you plan to upgrade now. Can you flash the full 142 firmware over your android 14 installation?
[Asus Zenfone 9] andlommy:
If you upgrade from stock 142 all the way to A14 ver 75, you'll have stock A14 ver 75. You can then extract boot.img, patch it and get magisk if you need to. If new update from Asus comes around, flash stock boot to slots a and b (I think that's what you missed in your previous post), apply Asus ota, then repeat the procedure of extracting boot, repatching it for magisk and flashing over stock boot...
[Asus Zenfone 9] Dillenger:
You all are the best! Thanks everyone! My phone is finally up to date from June! Keep it up XDA crew!

Dillenger
[Asus Zenfone 9] anang1979:
it takes time to understanding rename the file, once got it it is easy peasy. thanks som_bbs!
[Asus Zenfone 9] reyqn:
Ok thanks, so you don't actually need a full firmware, just a stock boot.img of your version.

I'm not sure how you extract boot.img for 34.0304.2004.75 since you're not root, so I just patched the 142 boot.img with the payload data from each OTA on my computer. Curious how you got it.
[Asus Zenfone 9] Dillenger:
https://xdaforums.com/t/rooting-zenfone-9-with-magisk.4484715/

This should work to get magisk reinstalled on 34.0304.2004.75
[Asus Zenfone 9] reyqn:
Kind of, but when you extract boot.img from an OTA payload, you get a diff than you must patch onto a full stock boot.img from the previous version (which is what I did).

I was just wondering if there was another way to get the 34.0304.2004.75 stock boot.img
[Asus Zenfone 9] andlommy:
You can extract boot.img from .142 then patch it with all the ota diffs with a python script shared earlier in the thread, or in a parallel thread
[Asus Zenfone 9] o0otnto0o:
How will Asus pick it up? I have TWRP on my phone, do I have to install original recovery first?

Update: Got it, once I boot to Android, Asus will recoginze the firmware.
[Asus Zenfone 9] o0otnto0o:
I'm stuck at A13 218. How did you guys overcome this?

Was I suppose to update from A13 204 directly to A14 42?
[Asus Zenfone 9] o0otnto0o:
I wanted to go through these OTA updates again and try a different OTA updating path, so I tried installing TWRP on A13 218, and I installed 33.0804.2060.142 (from Asus support page).

My phone now is dead, and it shows "QUSB_BULK_SN:26F4E65C" in Windows Device Manager when I plug it.

Please be advised.
[Asus Zenfone 9] andlommy:
You decided to downgrade from a version that is not downgradable (218 -->142). If you manage to get all the parts of the 218 firmware rebuilt, using a python script mentioned in this topic before (patching abl, boot, sbl etc using ota files from 142 all the way up to 218) you may have luck flashing them using fh_loader, but this sounds daunting
[Asus Zenfone 9] einfachgaer:
Is 142 the last A13 which you can downgrade from?
[Asus Zenfone 9] sunchau:
Get Update already
[Asus Zenfone 9] reyqn:
OP updated the mega directory, just updated to 34.0304.2004.87, works flawlessly. Thanks!
[Asus Zenfone 9] gruber_69:
Can you provide a link? The one in the thread provides updates up to 75.
[Asus Zenfone 9] reyqn:
The last file in A14 directory is 75 to 87

Zenfone 9 FOTA links

Hello! ZF9 unlocked bootloaders prevent usage of OTA. In fact, Asus server will reject client requests from devices that have bootloader unlocked. Apparently, ASUS maintain a list of unlocked devices (probably by servial numbers). With some help...

xdaforums.com
[Asus Zenfone 9] gruber_69:
Thanks. Now I see it.

Is it better to go:

A13 142->165->189->204->218->A14 62 -> 75 -> 87

Or

A13 142->165->189->204->A14 42 -> 54 ->62 -> 75 ->87.

Does it matter which path I choose?
[Asus Zenfone 9] gruber_69:
Hi. Can you provide any link or guide on how to do it? I would like to get stock boot and recovery partitions for .87 version.
[Asus Zenfone 9] svenagain:
I used https://github.com/CaptainThrowback/update_payload_extractor to generate the partition imgs from the stock firmware. An old version of the full firmware is publicly released https://www.asus.com/us/supportonly/zenfone 9/helpdesk_download/ and @som_bbs has gathered the OTA updates https://mega.nz/folder/tfIymZJQ#-QqyCWNvHdhKSZxaKErKlQ

Use the --old-dir argument to use the full firmware to generate the next version using the OTA then using that for the next version until reaching the final version. The dynamic partitions have hash error so either use --skip_hash --ignore_block_size or select the partitions:

./extract.py --partitions abl aop aop_config bluetooth boot cpucp devcfg dsp dtbo featenabler hyp imagefv keymaster modem multiimgoem qupfw qweslicstore recovery shrm tz uefi uefisecapp vbmeta vbmeta_system vendor_boot xbl xbl_config xbl_ramdump xrom --old_dir 142 --output_dir 165 165.bin
[Asus Zenfone 9] gruber_69:
Do both methods give same results (--skip_hash, --ignore block size vs select all partitions)? Now I only succeeded in extracting the 142 image but when I try to update errors appear.

C:\Users\Gruber\Desktop\update_payload>python ./extract.py --partitions abl aop aop_config bluetooth boot cpucp devcfg dsp dtbo featenabler hyp imagefv keymaster modem multiimgoem qupfw qweslicstore recovery shrm tz uefi uefisecapp vbmeta vbmeta_system vendor_boot xbl xbl_config xbl_ramdump xrom --old_dir 142 --output_dir 165 165.bin
Extracting abl
Extracting aop
Traceback (most recent call last):
File "C:\Users\Gruber\Desktop\update_payload\extract.py", line 84, in <module>
extract(args.payload, args.output_dir, args.old_dir, args.partitions, args.skip_hash, args.ignore_block_size)
File "C:\Users\Gruber\Desktop\update_payload\extract.py", line 45, in extract
helper._ApplyToPartition(
File "C:\Users\Gruber\Desktop\update_payload\update_payload\applier.py", line 557, in _ApplyToPartition
self._ApplyOperations(operations, base_name, old_part_file,
File "C:\Users\Gruber\Desktop\update_payload\update_payload\applier.py", line 513, in _ApplyOperations
self._ApplyDiffOperation(op, op_name, data, old_part_file,
File "C:\Users\Gruber\Desktop\update_payload\update_payload\applier.py", line 414, in _ApplyDiffOperation
subprocess.check_call(bspatch_cmd, close_fds=False)
File "C:\Program Files (x86)\Python312-32\Lib\subprocess.py", line 408, in check_call
retcode = call(*popenargs, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files (x86)\Python312-32\Lib\subprocess.py", line 389, in call
with Popen(*popenargs, **kwargs) as p:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files (x86)\Python312-32\Lib\subprocess.py", line 1026, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files (x86)\Python312-32\Lib\subprocess.py", line 1538, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: [WinError 193] %1 nie jest prawidłową aplikacją systemu Win32

I'm mainly interested in boot and recovery partitions (should i select only the two of them?), for use with magisk and probably twrp and be able to reflash them back when doing ota.

Edit:

As @reyqn suggested in windows WSL has to be used, else you can get errors as above.

One last thing. Is the boot.img updated from .142 to .87 really a stock factory image? It's gaining a little in size during updating process.
[Asus Zenfone 9] gruber_69:
Hi.

Have you updated this directory? It says 14 files now but no A14 folder is visible.

BTW.

.87 is available as full image on the Asus website
[Asus Zenfone 9] adeklipse:
I was just about to say. I'm gonna try putting in /sdcard/ root, and see if it detects and will want to update it. Fingers crossed!

EDIT:

It said unable to update. I suspect its because of some sort of hash mismatch. Gonna try reflashing the 142 update from scratch.
[Asus Zenfone 9] gruber_69:
There is some weird statement that this has to be updated from 218 firmware. Also watch out when flashing 142 on 218. It would not work properly and possibly create a bootloop or brick due to anti rollback. If you're on 142 just follow it from there, flash 142 again (change in version to 143 worked, it just says update failed after update but files are reverted back to original state and now the FOTA files will work. You just have to name the files correctly.

I used the A13 142->165->189->204->A14 42 -> 54 ->62 -> 75 ->87 way ,because 218 has higher security patch than 62. But now I would go to 218 and then flash .87, that saves you some reboots.
[Asus Zenfone 9] adeklipse:
I w

I was still on 142 when I made the comment.

Turns out I was using a Magisk-patched boot.img, and it didn't uninstall itself properly.

When I flash 142's original boot.img, it still wouldn't let me flash the A14 87 build, but it did allow me to update via the increments.

142 > 165 > 189 > 204.

The Mega folder didn't have (maybe still doesn't) A14 files. But I tried putting the A17 87 full package image downloaded from Asus, and it could update.

So I was able to go from A13 204 straight to A14 87. So that's the version I'm on right now. Hooray!

Still don't know why I couldn't just update from 142 to A14 87 straight away.
[Asus Zenfone 9] Ethan_01:
.87 on the Asus website is always broken,can you provide updates up to 87. thx
[Asus Zenfone 9] paullueders223:
Just went through the process and worked flawlessly. I started from Rooted 33.0804.2060.142 and then upgraded to 34.0304.2004.87. Process was as follows:

Extracted with PayloadDump original 142 boot image and flashed stock Boot Image via fastboot from 142 (to clear root temporarily and allow OTA upgrades to work)

Loaded 165 to root of internal storage, renamed, rebooted, and installed 165 (File Renamed to UL-ASUS_AI2202-ASUS-33.0804.2060.165-1.1.2-2308-user.zip)

Deleted 165 from internal storage, then loaded 189 to root of internal storage, renamed, rebooted, and installed 189 (File Renamed to UL-ASUS_AI2202-ASUS-33.0804.2060.189-1.1.3-2309-user.zip)

Deleted 189 from internal storage, then loaded 204 to root of internal storage, renamed, rebooted, and installed 204 (File Renamed to UL-ASUS_AI2202-ASUS-33.0804.2060.204-1.1.4-2311-user.zip)

Deleted 204 from internal storage, then loaded 218 to root of internal storage, renamed, rebooted, and installed 218 (File Renamed to UL-ASUS_AI2202-ASUS-33.0804.2060.218-1.1.5-2401-user.zip)

Deleted 218 from internal storage, then loaded full Android 14 image 87 to root of internal storage, rebooted, and installed A14 87 (Available from Asus Support website as of 3/1/2024, file name is UL-ASUS_AI2202-ASUS-34.0304.2004.87-1.1.1-2402-user.zip, no renaming needed)

Used PayloadDump to extract Boot Image from A14 87 full image, used Magisk to patch image, then flashed boot image through fastboot

Now at Android 14 (version 87), latest version from ASUS, and fully rooted without losing my previous files or root setup. You still need to do some of the OTA upgrades as the image posted on ASUS website only works with 218 or higher versions. Hopefully this helps people get their phones up to date.
[Asus Zenfone 9] Ethan_01:
hi can you provide full Android 14 image 87 . 87 on the Asus website is always broken when i download. thx！
[Asus Zenfone 9] Treklof:
Just want to say a big THANK YOU !

I finally had some time and went all the way from 142 to 218 with your FOTAs.

I didnt clean-install the 142 but just flashed the unrooted boot.img before starting with the 165.

After 218 I installed the new WW-34.0304.2004.87 from the support side.

Then rooted again with magisk.

Big hug!

One word: What does Asus think when they put up only the 142 of Android 13 and then an Android 14 update which needs the 218 version of Android 13 ??? That sucks !!!
[Asus Zenfone 9] Ethan_01:
...hi can you provide full Android 14 image 87 . 87 on the Asus website is always broken when i download. thx！
[Asus Zenfone 9] Treklof:
Sorry! Already on my way again. But the Firmware on the support-site is working. Probably there is a different issue...
[Asus Zenfone 9] Ethan_01:
thx i tried again ，but the file is still corrupted...
[Asus Zenfone 9] Ethan_01:
hi can you provide full Android 14 image 87 . 87 on the Asus website is corrupted when i download. thx！
[Asus Zenfone 9] adeklipse:
I can try to upload it when I get access to a computer, maybe in 12 hours or so.

How do you figure that your download is corrupted? Does it say "Unable to upgrade" or something like that?
[Asus Zenfone 9] Ethan_01:
thank you！！

im 218，but when i reboot phone, and the phone automatically pick up the update file and faild update. i suspect there's something wrong with the 87zip.so I decompress it showing that the file was corrupted.
[Asus Zenfone 9] adeklipse:
Ah, I also encountered that error. I'm pretty sure the file isn't corrupted.

You have to update your phone to the latest Android 13 version (I think it's 218 or 204), then you can update to Android 14.

I shared similar concerns on my previous post.

EDIT:

It can also be caused by:

1. A modified partition, like boot. In my case, I uninstalled Magisk without restoring the proper boot images, so I flashed 142's boot.img first.

2. A corrupted partition, in which case you'll have to reflash the entire phone.

But I'd suggest making sure you're on the latest Android 13 first, and/or making sure your boot partition is correct.
[Asus Zenfone 9] Ethan_01:
im now 218，can i flashed 142's boot.img？
[Asus Zenfone 9] adeklipse:
I wouldn't recommend it.

Are you able to dump .218's payload.bin and see if it has a boot.img?
[Asus Zenfone 9] Ethan_01:
no， the boot dump from ota cannot use
[Asus Zenfone 9] Ligmoff:
Heyo, mega says files removed, any chance of uploading em again? i didnt manage to download them last night :(
[Asus Zenfone 9] som_bbs:
Since the full firmware came out, these files are no longer needed.

Maybe those who have already downloaded will share?
[Asus Zenfone 9] iskorotul:
But I also need . 218 fw file since the official.87 can only be updated from .218. Im on 142. Hope anyone can share them soon.
[Asus Zenfone 9] Ligmoff:
Yes, the full firmware is on the support page, but not the 218 thats needed to use it. Even tested it, just says "update failed" instantly without anything happening.

This version needs to be upgraded from WW-33.0804.2060.218

Asus in their great wisdom released update that users with unlocked bootloaders cant even use.

The great clowns replied to my support request in december by saying they wont give any support to users with bootloaders unlocked.
[Asus Zenfone 9] paullueders223:
Below is a link to all the files I used for my process, (Update Process Post - 3/5/24), if that is of help to anyone. All were sourced from this thread or from ASUS directly.

https://mega.nz/folder/qUMhlKoR#LNo2OcMhDTaY08pbcC5lsQ

I considered making a new thread but I'll leave it as a post unless people think otherwise.
[Asus Zenfone 9] Ethan_01:
thx！ a14 087.zip works！
[Asus Zenfone 9] Hermann2306:
Thx from me too, worked.

Root is no problem, does twrp also work with A14?
[Asus Zenfone 9] gruber_69:
Yes it works. I used image from official site. It decoded partitions with no problem.
[Asus Zenfone 9] reyqn:
34.0304.2004.108 was released
[Asus Zenfone 9] palamosteliaro:
No .zip file on Asus's website unfortunately.
[Asus Zenfone 9] paullueders223:
ZIP is on their website now, Security Update is for April 5, 2024, updated no problem via standard Full Image method. Added the ZIP to the Mega Drive Link from above:

https://mega.nz/folder/qUMhlKoR#LNo2OcMhDTaY08pbcC5lsQ
[Asus Zenfone 9] Hermann2306:
Where did you see it on their website? Cant find it.
[Asus Zenfone 9] paullueders223:
Zenfone 9 - Support

www.asus.com
[Asus Zenfone 9] Hermann2306:
thx, the us in the url did it.
[Asus Zenfone 9] palamosteliaro:
It actually fixed the only bug I had in 14: Getting a black screen when swiping to see the recent apps.
[Asus Zenfone 9] Absarock:
Hello. I followed your method. But first instead of flashing boot.img. I uninstalled Magisk from app and selected "restore images". Update was detected (165) but failed at 1%.

So I began again with flashing boot.img. Again it the update failed at 30.x percent. Any idea how I can fix that?

(Cant use fastboot because there is idk what bug. Charging isnt working except PD fast charging. Also phone isnt connecting to PC, thats why I want to update)
[Asus Zenfone 9] williamcll:
Failed at 0% going from 142 to 165. What am I doing incorrectly? Using stock with magisk
[Asus Zenfone 9] fityanferry:
for me, flash original boot and recovery .imgs from .142 version first, before flash .165.
[Asus Zenfone 9] pimav:
First things first: I'm already sorry, if my question sounds stupid...

I have the current 2004.108 *.zip file, as well as the 2060.142 as backup (which is the version running on the phone atm). The phone is rooted, as i get this as message when booting.

under Win 10:

``adb devices`` is showing "XX_SERIAL_XX device", when the phone is running normaly and USB Debugging active . Booting into recovery mode and connecting results into "XX_SERIAL_XX unauthorized".

From here on:

How to do this """ standard Full Image method """ ?

What do i do to get things going?
[Asus Zenfone 9] gruber_69:
During reboot phone should stay connected all the time to be authorized. Or you have to allow always authorize from this PC.

Also message informs you that bootloader is unlocked not about root status.

For OTA files to work if you are rooted or have changed partitions from stock you first need to flash .142 file (may need to rename to make phone pick it up as update) to bring back stock status.

You don't flash full image through PC but place it in the internal memory main directory, then phone updates itself after he picks it up. For me that was after reboot.

Read the guide and thread carefully as you clearly haven't, because you will not be able to update from 142 to 108 directly as files are incremental updates and need to be flashed in specific order.
[Asus Zenfone 9] takobaba:
I am trying to download Android 14 image, but mega doesnt let me download for free. Can anybody help uploading it to somewhere else, like google drive maybe?

Note: Actually no need, from the latest A13 version, I just downloaded the latest A14 from Asus website and I could upgrade directly.
[Asus Zenfone 9] homanw104:
Thanks for sharing!

I started upgrading from Android 12. Following the order of the shared A13 packages: 142 -> 165 -> 189 -> 204 -> 218, I upgraded to the latest A13 version.

After that, you can directly install the latest A14 updates from Asus. As for now, the latest is 34.0304.2004.108.
[Asus Zenfone 9] pimav:
Just to report:

Had to start the update process twice. First one did fail somewhere along the road.

Using the Zip files provided and start from 142 as discribed above did work.

Full thing takes about 1 hour and 30 % battery.

Sidenotes:

- Lock Screen, then unlock Screen is enough for me for the phone to recognize the zip file

- After each restart, the phone has to do some stuff "finishing the update". Leave it alone until it tells you its done, then check the "software version page" to see if it worked.

As stated before:

- the bootloader is unlocked (see my last post and gruber_69 response)

- im pretty sure its rooted, as some banking stuff does not work and i found stuff pointing to "Magisk". But I'm

NOT sure

Heres the long story as "log File":

Downloaded ZIP file with the A13 files.

All are on the phone now in a subfolder "firmware"

I' running 142 atm, but i used the 142 zip file (by renaming it to i.e. 143) to update to 142 (again).

Moving file from firmware to internal storage as described above.

-> Update is starting, takes about 5-10 minutes and I'm rebooting after its done.

Then it says "Update failed"

Copied the zip file back to the subfolder firmware after restart.

Phone wanted to reboot again

Still says "update failed"

I tried to upgrade to 165, ignoring the Failure message. It runs, it restarts,then "update failed" again.

Ignoring that as well tried to run 189. That was not possible. Here i got stuck

Then did the whole thing again:

- starting with the 142 (renaming to 143, copy to internal store, etc. )

165 -> 189 ->204 -> 218

up to here was flawless
[Asus Zenfone 9] Absarock:
Hello. Thank you for the helpful information. My Zenfone 9 was rooted and has TWRP recovery. I have reset it and unrooted it fully. But still while installing the update file (from build 142 to 165) the it shows an error 'System update failed" upon reaching 29 percent. Is it because the phone has custom recovery? How can I remove the recovery?
[Introductions] xxx111a:
I came here just for make firends with people who share the same hobbies
[Introductions] Sib64:
Hi xxx111a,

Welcome aboard the xda forum.

Which hobbies do you want talking ?

I invite you to consult the links in my Sig and especially the link below if you have any questions.

XDA New user Guide

Have a nice day ;)
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] xxx111a:
This module(ADB Fastboot for Android NDK-1.0.39 103918 (SFILE.MOBI).zip) works in magisk,but doesn' work in kitsune mask.Pls,help me.And I dont't need "pkg install android-tools".How to solve this problem