Ok, I see now. Thanks for the info.
I have successfully installed the v4 version, which is the chinese firmware. I did it by pushing the encrypted update to /sdcard/ and triggering it manually, as you advised. It worked.
If I wanted to clean install this version, to be sure to be on a fresh install, would I do that through recovery ? What would be the procedure ?
Also, here is my partition table:
Code:
PS D:\Downloads\OnyxBoox> .\edl.exe /u /g
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 1 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 2 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 3 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 4 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting GPT 5 header... ok, receiving... ok, requesting entries... ok, receiving... ok
LUN # Name Start Count Type
─── ── ──────────────── ────────── ────────── ────────────────────
0 1 ssd 6 2 Secure SW download
0 2 persist 8 8192 Persist
0 3 misc 8200 256 Misc
0 4 keystore 8456 128 Key store
0 5 frp 8584 128 FRP
0 6 super 8712 1048576 Super
0 7 recovery_a 1057288 24576 Recovery
0 8 recovery_b 1081864 24576 Recovery B
0 9 vbmeta_system_a 1106440 16 VB meta system
0 10 vbmeta_system_b 1106456 16 VB meta system B
0 11 metadata 1106472 4096 Metadata
0 12 onyxconfig 1110568 6144 System
0 13 userdata 1116712 13402579 User data
1 1 xbl_a 6 896 Bootloader
1 2 xbl_config_a 902 32 Boot config
1 3 last_parti 934 1109 Empty
2 1 xbl_b 6 896 Bootloader
2 2 xbl_config_b 902 32 Boot config
2 3 last_parti 934 1109 Empty
3 1 ALIGN_TO_128K_1 6 26 fde1604b
3 2 cdt 32 32 CDT
3 3 ddr 64 256 DDR
3 4 last_parti 320 32443 Empty
4 1 rpm_a 6 128 Inactive
4 2 tz_a 134 1024 Inactive
4 3 hyp_a 1158 128 Inactive
4 4 modem_a 1286 46080 Inactive
4 5 bluetooth_a 47366 256 Inactive
4 6 mdtpsecapp_a 47622 1024 Inactive
4 7 mdtp_a 48646 8192 Inactive
4 8 abl_a 56838 256 Inactive
4 9 dsp_a 57094 8192 Inactive
4 10 keymaster_a 65286 128 Inactive
4 11 boot_a 65414 24576 Inactive
4 12 cmnlib_a 89990 128 Inactive
4 13 cmnlib64_a 90118 128 Inactive
4 14 devcfg_a 90246 32 Inactive
4 15 qupfw_a 90278 16 Inactive
4 16 vbmeta_a 90294 16 Inactive
4 17 dtbo_a 90310 6144 Inactive
4 18 imagefv_a 96454 512 Inactive
4 19 uefisecapp_a 96966 512 be8a7e08
4 20 featenabler_a 97478 32 741813d2
4 21 multiimgoem_a 97510 8 Inactive
4 22 rpm_b 97518 128 Resource/power mgmt
4 23 tz_b 97646 1024 TrustZone
4 24 hyp_b 98670 128 Hypervisor
4 25 modem_b 98798 46080 FAT32
4 26 bluetooth_b 144878 256 Bluetooth
4 27 mdtpsecapp_b 145134 1024 MDTP secure
4 28 mdtp_b 146158 8192 MDTP
4 29 abl_b 154350 256 Android bootloader
4 30 dsp_b 154606 8192 DSP
4 31 keymaster_b 162798 128 Key master
4 32 boot_b 162926 24576 Boot
4 33 cmnlib_b 187502 128 Common lib
4 34 cmnlib64_b 187630 128 Common lib64
4 35 devcfg_b 187758 32 Device config
4 36 qupfw_b 187790 16 QUP firmware
4 37 vbmeta_b 187806 16 VB meta
4 38 dtbo_b 187822 6144 DTBO
4 39 featenabler_b 193966 32 Inactive
4 40 imagefv_b 193998 512 Image FV
4 41 uefisecapp_b 194510 512 Inactive
4 42 multiimgoem_b 195022 8 e126a436
4 43 devinfo 195030 1 Device info
4 44 dip 195031 256 DIP
4 45 apdp 195287 64 APDP
4 46 spunvm 195351 2048 Spun VM
4 47 splash 197399 8356 Splash
4 48 limits 205755 1 Limits
4 49 toolsfv 205756 256 Tools FV
4 50 logfs 206012 2048 Log FS
4 51 cateloader 208060 512 STI
4 52 rawdump 208572 32768 RAM dump
4 53 logdump 241340 16384 Log dump
4 54 storsec 257724 32 Store secure
4 55 multiimgqti 257756 8 846c6f05
4 56 uefivarstore 257764 128 165bd6bc
4 57 secdata 257892 7 76cfc7ef
4 58 catefv 257899 128 Cate FV
4 59 catecontentfv 258027 256 Cate content FV
4 60 last_parti 258283 790288 Empty
5 1 ALIGN_TO_128K_2 6 26 6891a3b7
5 2 modemst1 32 512 Modem ST1
5 3 modemst2 544 512 Modem ST2
5 4 fsg 1056 512 Modem storage
5 5 fsc 1568 32 FSC
5 6 last_parti 1600 31163 Empty
In the guide for NoteAir4, the boot partitions are named pboot_a and pboot_b.
From the partition table, I guess mine are simply boot_a and boot_b ? I would be sure to not flash the wrong ones after I patched them.
I tried to pull them, I am having the following error
Code:
PS D:\Downloads\OnyxBoox> .\edl.exe /u /r /boot_a boota.img
Operations on UFS raw devices (vs. partitions) requires LUN specified