Quote:
Originally Posted by yokos
Incremental updates don't have any boot.img. Just a patch file is included
After updating firmware you have to use dd, using a booted older rooted boot.img
Warning: flashing an older boot.img (after a x.x.+1 firmware revision) on Max Lumi caused severe finger touch problems. Therefore we need the latest boot.img.
|
In the update file a have payload.bin that's 1.2GB large.
I had no luck with EDL on various platforms. Unfortunately, I can't devote any more time trying to figure out why EDL isn't working and getting the boot.img via it.
Maybe someone with a Note Air 2 could post the patched img file. That worked like charm last time. Maybe @Cascade94 will grace us with his presence and give us the juice
Update:
After doing a quick search I found what dd kinda means. After inputting the following command (just hooking up my devices normally, no recovery mode, EDL etc.):
Code:
dd if=/dev/block/bootdevice/by-name/boot_a bs=64M of=/sdcard/boot_a.img
I got:
100663296 bytes (96 M) copied, 6.301492 s, 15 M/s
NoteAir2:/ # dd if=/dev/block/bootdevice/by-name/boot_a bs=64M of=/sdcard/boot_a.img
1+1 records in
1+1 records out
100663296 bytes (96 M) copied, 0.484554 s, 198 M/s
Then I did:
PHP Code:
d if=/dev/block/bootdevice/by-name/boot_b bs=64M of=/sdcard/boot_b.img
1+1 records in
1+1 records out
100663296 bytes (96 M) copied, 0.468288 s, 205 M/s
as I saw there are two boot files (boot_a and boot_b). In my file explorer on the devices, these files do NOT have file endings. Not sure if that matters or not. I couldn't open these file on my Mac.
I also managed to pull of the system.img. Not sure if system.img is different from boot.img. Both boot.img are 100MB and system is 300MB.
Are these the boot files (currently still on v3.2) the ones we're looking for? However, when I update to v3.2.1 I wouldn't have root and couldn't pull this off on the new version. Or am I missing something?