Hi,
Some updates on NoteAir2 with bkerler and Renate's edl.exe tool.
I'd love is someone could write a tutorial on how to get bkerler's edl to work on Windows 10 because this is the second time I've tried with no luck. I installed python 3.9 via .msi installer, then git, I successfully did all this:
edl -h won't even work. I'm in the edl folder, even a simple edl -h should return the programs options with or without a device connected (which I have tried both anyway) but it just gives "
'edl' is not recognized as an internal or external command, operable program or batch file."
Anyways on to
@Renate's edl.exe. At first I kept getting:
Code:
Found EDL 9008
Could not read device
I tried 3 different loaders (665, 662, 662 patched).
That was with Zadig driver which is my normal method (screenshot below). Now, I don't know if it's just because I've messed about with UsbDk as well and that was causing me issues with drivers OR it was because I'm an idiot and used the wrong loader (though I don't think so I treid all 3 multiple times with /u and without /u) or if it was because I went into UsbDk (It's in Program Files>UsbDk Runtime Library yeah, the instructions on bkerler are not at all clear why this exists and how to do the thing) and opened a new command prompt inside that folder and ran "UsbDkController -n" and got this:
Code:
C:\Program Files\UsbDk Runtime Library>UsbDkController -n
Enumerate USB devices
Found 4 USB devices:
0. FilterID: 1, Port: 16, ID: 045e:0306, Configs: 1, Speed: 4
USB\VID_045E&PID_0306 201209010309
Descriptor for configuration #0: size 44
1. FilterID: 1, Port: 5, ID: 1286:204c, Configs: 1, Speed: 3
USB\VID_1286&PID_204C 0000000000000000
Descriptor for configuration #0: size 177
2. FilterID: 1, Port: 7, ID: 045e:09c0, Configs: 1, Speed: 2
USB\VID_045E&PID_09C0 7
Descriptor for configuration #0: size 41
3. FilterID: 1, Port: 13, ID: 05c6:9008, Configs: 1, Speed: 4
USB\VID_05C6&PID_9008 13
Descriptor for configuration #0: size 44
Did nothing to help bkerler's edl but it did get Renate's edl.exe running! So, I thought I'd post that just in case it's helpful, like if you have that tool on your Windows 10 device trying to get bkerler to work and you can't get Renate's tool to work with Zadig and are getting a similar error, this might be why. I could have been dumb on the loader but I don't think so because I screenshotted the correct working loader error (screenshot attached) so I think it was something else that fixed it and possibly UsbDk. Just throwing it out there.
It works with the 662 patched loader
here (thanks @downeaster59!!!!) I ended up renaming it for ease of use below:
Code:
C:\edl>edl.exe /l662patched.elf
Found EDL 9008
Serial: f53feefb
HWID: 0014d0e100000000, QC: 0014d0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955
Sending 662patched.elf 100% Ok
Waiting for Firehose... Ok
Partition table from 3.2.2 is as follows for reference, though I did get some errors that I don't understand that might be of interest to Renate:
Code:
C:\edl>edl.exe /u /g
Found EDL 9008
Configuring... 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
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
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 89a12de1
0 7 recovery_a 1057288 24576 d504d6db
0 8 recovery_b 1081864 24576 352b8083
0 9 vbmeta_system_a 1106440 16 1344859d
0 10 vbmeta_system_b 1106456 16 fe3ab853
0 11 metadata 1106472 4096 988a98c9
0 12 onyxconfig 1110568 6144 System
0 13 userdata 1116712 13385171 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 rpm_b 97510 128 Resource/power mgmt
4 22 tz_b 97638 1024 TrustZone
4 23 hyp_b 98662 128 Hypervisor
4 24 modem_b 98790 46080 FAT32
4 25 bluetooth_b 144870 256 Bluetooth
4 26 mdtpsecapp_b 145126 1024 MDTP secure
4 27 mdtp_b 146150 8192 MDTP
4 28 abl_b 154342 256 Android bootloader
4 29 dsp_b 154598 8192 DSP
4 30 keymaster_b 162790 128 Key master
4 31 boot_b 162918 24576 Boot
4 32 cmnlib_b 187494 128 Common lib
4 33 cmnlib64_b 187622 128 Common lib64
4 34 devcfg_b 187750 32 Device config
4 35 qupfw_b 187782 16 QUP firmware
4 36 vbmeta_b 187798 16 Verified Boot meta
4 37 dtbo_b 187814 6144 DTBO
4 38 featenabler_b 193958 32 Inactive
4 39 imagefv_b 193990 512 Image FV
4 40 uefisecapp_b 194502 512 Inactive
4 41 devinfo 195014 1 Device info
4 42 dip 195015 256 DIP
4 43 apdp 195271 64 APDP
4 44 spunvm 195335 2048 Spun VM
4 45 splash 197383 8356 Splash
4 46 limits 205739 1 Limits
4 47 toolsfv 205740 256 Tools FV
4 48 logfs 205996 2048 Log FS
4 49 cateloader 208044 512 STI
4 50 rawdump 208556 32768 RAM dump
4 51 logdump 241324 16384 Log dump
4 52 storsec 257708 32 Store secure
4 53 multiimgoem 257740 8 e126a436
4 54 multiimgqti 257748 8 846c6f05
4 55 uefivarstore 257756 128 165bd6bc
4 56 secdata 257884 7 76cfc7ef
4 57 catefv 257891 128 Cate FV
4 58 catecontentfv 258019 256 Cate content FV
4 59 last_parti 258275 790296 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
@Renate I'll PM you my two recovery images and boot images once I get them all uploaded I got this off of 3.2.2 (which I upgraded to because I'm an IDIOT and wasn't thinking and I should have probably tried from out of the box nvm). The boots are 16MB each, the recoveries are 23MB each. I'm concerned that they're so small because @Cascade94's supplied ones are much bigger in size. Is it because I truncated with the /t? (Update: never mind it's /t truncation. Fullsize is the same size as @Cascade94).
Also I did get some errors doing the pulls just as I did with call for partition table which you might want to look at:
Code:
C:\edl>edl.exe /u /r /precovery_a reca.img /t
Found EDL 9008
Configuring... 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
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
Requesting header... Ok, receiving... Ok
Android2: 5899 / 24576 = 24.0%
Requesting read reca.img... Ok, receiving 100% Ok
C:\edl>edl.exe /u /r /precovery_b recb.img /t
Found EDL 9008
Configuring... 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
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
Requesting header... Ok, receiving... Ok
Android2: 5899 / 24576 = 24.0%
Requesting read recb.img... Ok, receiving 100% Ok
C:\edl>edl.exe /u /r /pboot_a boota.img /t
Found EDL 9008
Configuring... 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
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
Requesting header... Ok, receiving... Ok
Android2: 4117 / 24576 = 16.8%
Requesting read boota.img... Ok, receiving 100% Ok
C:\edl>edl.exe /u /r /pboot_b bootb.img /t
Found EDL 9008
Configuring... 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
Requesting GPT 6 header...
<log value="ERROR: Failed to open the UFS Device slot 0 partition 6" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:6 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 203949180" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:6 error:3" />
Nope
Requesting header... Ok, receiving... Ok
Android2: 4199 / 24576 = 17.1%
Requesting read bootb.img... Ok, receiving 100% Ok
Sidenote @Renate, some minor errors here regarding rebooting out of edl.exe on the NoteAir2. At first I thought it was due to the inclusion of the flag /u, but actually it doesn't matter whether you use a flag or don't, or a mix between the two, the only way it will reboot is if you do a reboot command twice in a row:
Code:
C:\edl>edl.exe /z
Found EDL 9008
Requesting reboot... Ok
C:\edl>edl.exe /z
Found EDL 9008
Requesting reboot...
Could not write device
That first one just does nothing even if you wait for ages. I've tested this twice now and it does the same thing. It only reboots after the second try.
P.S I might need help with flashing I'm having issues with Fastboot rn but I'll write another post if I can't fix it in the next couple of days.
Edit: Zadig screenshot didn't upload.