Dumb question, but it has been so long since i updated, but are the files being posted by @Swap_File and @g33gz compatable with the in1025?
are these for f13 update?I'll give it a try next week, I'm currently traveling and don't want to risk breaking my phone.
Attached is an untested OOS13 boot.img, both patched and unpatched.
The ones I'm sharing are for IN2025. I believe @Swap_File is the same. I'm not sure it will be compatible with any other model.Dumb question, but it has been so long since i updated, but are the files being posted by @Swap_File and @g33gz compatable with the in1025?
Correct, thats for the F.13 update!
that makes one of us!
Extracting my_heytap
Extracting my_preload
Extracting my_manifest
Extracting my_bigball
Traceback (most recent call last):
File "/home/tardo/update_payload_extractor/./extract.py", line 67, in <module>
extract(args.payload, args.output_dir, args.old_dir, args.partitions)
File "/home/tardo/update_payload_extractor/./extract.py", line 45, in extract
helper._ApplyToPartition(
File "/home/tardo/update_payload_extractor/update_payload/applier.py", line 554, in _ApplyToPartition
self._ApplyOperations(operations, base_name, old_part_file,
File "/home/tardo/update_payload_extractor/update_payload/applier.py", line 505, in _ApplyOperations
self._ApplyReplaceOperation(op, op_name, data, new_part_file, part_size)
File "/home/tardo/update_payload_extractor/update_payload/applier.py", line 254, in _ApplyReplaceOperation
out_data = lzma.decompress(out_data)
File "/usr/lib/python3.10/lzma.py", line 343, in decompress
res = decomp.decompress(data)
_lzma.LZMAError: Input format not supported by decoder
@Swap_File when you tried to extract this, did you get any errors at all? Looks like I'm getting this towards the end:
I've used both payload dumpers I have and get similar errors around there
Ah, gotcha. I assumed all the files were required when doing this with an incremental updateYeah, if you let it keep extracting you will get an error.
I always stop the process after the boot image gets extracted, I figure there's no real reason to let it keep going.
btw, seems like this extractor doesnt throw an error and extracts more stuff than the others: https://xdaforums.com/t/tool-a-quick-android-ota-payload-dumper.4173271/Ah, gotcha. I assumed all the files were required when doing this with an incremental update
Have you successfully updated? I'm trying to on my end and keep getting a "There was an issue while preparing to restart. Please try again later" errorJust got a push notification from Oxygen Updater for 2025_11_F.15. 667 megs with the December Security patch and a fairly long list of fixes. Pretty cool. Anyone else?
I have successfully updated, yes. I did a 'complete uninstall' of Magisk which rebooted my phone. Then I checked for updates, which it found. The update installation went smoothly and rebooted. I have not yet sat down to boot with your patched boot.img but will in a few hours.Have you successfully updated? I'm trying to on my end and keep getting a "There was an issue while preparing to restart. Please try again later" error
Ah, I think this was because my battery wasnt charged enough. Rookie mistake on my part!I have successfully updated, yes. I did a 'complete uninstall' of Magisk which rebooted my phone. Then I checked for updates, which it found. The update installation went smoothly and rebooted. I have not yet sat down to boot with your patched boot.img but will in a few hours.
Warp charge it. Wooo!Ah, I think this was because my battery wasnt charged enough. Rookie mistake on my part!
That's odd, the spacing is normal on mine. Have you tried changing the resolution in the settings? maybe switch back and forth?I tried uninstalling Magisk, rebooting, and updating from the built in system updater, but it kept failing part way through with "There was an issue while preparing to restart. Please try again later". I ended up downloading the update via Oxygen Updater, and doing a local update from zip, which worked.
@g33gz 's magisk_patched-25200_ZkH2v.zip worked great once installed.
I did however notice that the date on my lock screen is now spaced incorrectly, this appears to be a common problem.
https://www.reddit.com/r/oneplus/comments/zxb6qg
Anyone else have this lock screen problem? I haven't reset my phone since Android 12, I wonder if I need to do a full reset at some point now that I'm on 13.
After the update I had to re-add my cards to google pay, but it all seems to be working.
Bless you, g33gz! Thank you, thank you, thank you!both stock and magisk patched boot.img for IN2025_13.1.0.585(EX01) are attached
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:No.
Simply download the Prebuild binaries from here.
And download the C.20 update from here.
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?
You have to completely uninstall Magisk... it's a pain in the butt to update now because you'll need your PC to flash the modified boot.imgAnyone else have issues updating to C21? Every time I try manually updating using the system update app it gets to 32% and fails. I turned off all magisk modules and restored image within magisk first.