Closed 5n0wfish closed 1 year ago
Hi, can you share the link to the payload.bin? I checked Pixel 7 and Pixel 8 factory OTA images, they don't have "ZERO" ops. It would be help if you can share some testing images.
oneplus 9 ROM Download Url
On the other way, observing the print described below, I want boot_editor
could unpack the specified partition from payload.bin
, because its so big to unpack all.
[main] INFO cc.cfig.droid.ota.Payload - There are 43 partitions [system, system_ext, product, vbmeta_system, engineering_cdt, cpucp, featenabler, hyp, multiimgoem, oplus_sec, oplusstanvbk, qweslicstore, splash, uefisecapp, vm-bootsys, shrm, boot, vendor_boot, vendor, odm, dtbo, vbmeta, vbmeta_vendor, xbl, xbl_config, aop, tz, modem, bluetooth, abl, dsp, keymaster, devcfg, qupfw, imagefv, my_product, my_engineering, my_stock, my_carrier, my_region, my_bigball, my_heytap, my_manifest]
[main] INFO cc.cfig.droid.ota.Payload - dumping images to build/payload/
The download link always reports error, and today the access token has expired. back luck ~ I searched the ROM in oneplus site: https://service.oneplus.com/global/search/search-detail?id=2096329&articleIndex=1 And tried Oneplus9, Oneplus9 pro, neither of them has ZERO ops. So maybe I have to check the AOSP code directly.
About "unpack the specified partition": No problem.
The oneplus rom is downloaded from:
https://yun.daxiaamu.com/OnePlus_Roms_2/%E4%B8%80%E5%8A%A09/ColorOS%2013.0.0%20F.12/
By the above, the process could not to decompress.
Besides, can
boot_editor
unpack the specified partition from payload.bin, its so big.