View Single Post
Old 05-14-2022, 02:50 AM   #3
nonex
Junior Member
nonex began at the beginning.
 
Posts: 3
Karma: 10
Join Date: May 2022
Device: NovaAirC
Thanks for the link. I decrypted the upx file, and dumped the partitions inside payload.bin. I tried flashing on both a and b partitions, but this unfortunately did not fix the issue. I also tried flashing all partitions inside. (aside from system, vendor and product, because I don't see those partitions.)

I noticed, that the boot.img of the update is the same as my boot_b, but all the a-Partitions are marked as active. Maybe It would help, if I can set the b-partition as active? The Python edl-tool has that option but it does not seem to be working. When calling "edl --loader=662.elf setactiveslot b" I got:
Code:
firehose - [LIB]: Error:['INFO: Calling handler for patch', 'ERROR: patch size too large 128']
Do you have any more ideas?
nonex is offline   Reply With Quote