Quote:
Originally Posted by Renate
Jeez, this is a horse of a different color.
This is not what I see from a NoteAir2 from 6 months ago.
The partitions for boot/recovery are 100 MB.
The image for boot/recovery are 100 MB because they stick a dozen bytes on the end.
If they didn't the images could be 70-77 MB shorter. 
(Because they do this AVB0 signing.)
Ok, moving beyond that. Both boot & recovery have the identical kernel (as to be expected).
But the kernel has increased in size from 35 MB to 50 MB from 6 months ago.
So much for New Year's resolutions to lose some weight.
The dtb sections are the same. There are 3 DTB's in them. And you have a dtbo partition.
So, backtracking a bit. This all started when you tried to Magisk with a boot image you pulled off using EDL? Maybe they started to enforce the AVB0 in abl?
I see that your recovery there has /system/bin/update_engine_sideload which is the new software for working with update.zip with payload.bin
I'm not sure how to use that, but you could try using the decrypted update.zip
Code:
C:\>adb sideload update.zip
I see that xbl is using standard Qualcomm factory signing. |
Holy **** sideloading worked. And it boots up! The UI looks completely different, all my data is gone and it announces itself as "BENGAL-IDP" and not as "Note Air 2" but it is functional again!
Already saw myself enrolling electical engineering studies ... I will definitely donate some coffee if you send me your paypal address via pm.
One last question. How did you get to the download link for the update.upx for this device? Could be useful also for others struggling with similar issues.
