Root for Note Air 2?

[Renate]

Dear BazookaJoe: You are a pleasure to work with. Of course.

I just did a Poke3 3.2.2 update using the autoupdate method (just because).
Of course I had to redo all my patches but it took a lot less time than I thought.
My criteria is always that I can screw my device up any amount as long as I can return to my current book and have everything exactly how it was and everything is good.

[downeaster59]

@Renate

I've recently picked up a Windows 11 tablet. I'm trying out your edl.exe on this tablet with my Note Air 2 just to see if it will work. I've used Zadig and I believe I have the correct driver installed. I put my Note Air 2 into edl mode. I enter the following: edl.exe /lnoteair2.bin Then I get the following message: Could not find EDL device.

My first guess is that I have a driver problem somewhere. Anything else that could be wrong? Thanks!

[Renate]

You could try uploading usblog.exe (in the sig). (Go up to Windows)
When you plug in a device in EDL mode it should come up as 05c6/9008.
Note that EDL is persnickety and you can't disconnect and reconnect the cable. You have to go to EDL mode with the cable connected and start fresh.
Windows 11 could be an issue.

I have a utility to check this, but it's not so disimilar from edl.exe as to really tell you anything. Still, it could be useful if this can't be resolved.

C:\>winusb 05c6 9008
Found generic device at 05c6/9008
Path: \\?\usb#vid_05c6&pid_9008#8&1203f332&0&10#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
In bulk endpoint 81
Out bulk endpoint 01
Everything ok

[downeaster59]

Thanks for the reply! I have another way to do EDL that works for me, but I wanted to try out your edl.exe on Windows. I'll give your suggestions a try!

[Renate]

I had to read through this whole thread again to remember what happened.

The Note Air 2 does have an SDM662, also named "Bengal", but more specifically named "SM_KAMORTA_H". There are multiple "SDM662"s and "Bengal"s. There are also many model numbers with "KAMORTA" in them, like: QCM_KAMORTA, QCS_KAMORTA, QRB_KAMORTA, SM_KAMORTA, SMP_KAMORTA, SM_KAMORTA_H, SMP_KAMORTA_H.

Apparently the best loader is the one in this post: https://www.mobileread.com/forums/sh...&postcount=107
Qualcomm_662_loader.elf, 668,796 bytes
MD5 = cd7a91985353e0a1a6d581b423e1325c
QC_IMAGE_VERSION_STRING=BOOT.XF.4.1-00200-KAMORTALAZ-1

The one in the bkerler/Loaders/qualcomm/factory/sdm662/ is not the right one for us.
0014d0e100000000_d40eee56f3194665_FHPRG.bin, 660,620 bytes
MD5 = 1e7c8fbadbab7127b8982bbcd344f646
QC_IMAGE_VERSION_STRING=BOOT.XF.4.1-00187-KAMORTALAZ-2

[Cascade94]

3.2.2 - patched boot image:

https://drive.google.com/file/d/1XEA...ew?usp=sharing

[bazookajoe]

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:

git clone https://github.com/bkerler/edl
cd edl
git submodule update --init --recursive
pip3 install -r requirements.txt

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:

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:

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:

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:

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:

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:

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.

[Renate]

The "ERROR"s on GPT 6 is just because there isn't a GPT 6.
I've been just enumerating GPTs until I get an error then I know how many there are.
The new bit with the "Querying info" will tell me that so I don't have to search blindly.
In any case, it's an anticipated error.
I don't own any Qualcomm things with UFS which is why I have to ask you so that I can plug the responses into my EDL server emulator so that I can work on/test my EDL client.

One reason things get so tricky with this Qualcomm stuff is that with Sahara the device is supposed to speak first and with Firehose the host is supposed to speak first.
Normally you know whether you have loaded the loader already so there's not much confusion.
I could try to make it try to find its way through, but I've learned that there is so much flakiness in all this EDL stuff that it might only work for some chips and not others.

When you do an "edl /z" it should disconnect immediately. For a normal reboot on an unlocked device there is a built-in 30 second delay before it boots anything after that.
If you still get no response that's probably because the image that it is booting to is broken.

Since I have the reed switch on my EDL test points I can do this all day long (with the switch activated):

C:\>edl.exe /lpoke3 /z
C:\>edl.exe /lpoke3 /z
C:\>edl.exe /lpoke3 /z

It takes about 4 seconds a complete cycle.

[Renate]

Also, for the Python stuff: You need to be more explicit. If you have a file association then you need to have edl be named edl.py

C:\>edl.py

Or else just do it like this:

C:\>\somewhere\or\other\python.exe edl.py

[bazookajoe]

Changing the file extension of edl to.py was a start! I'm still a bit overwhelmed and not getting it working. Anyway I'm still much happier using Renate's edl.exe

I do need help to test boot my patched boot image and then to flash it.

If I follow Cascade94's post:

adb reboot fastboot
fastboot devices (yes it returns my device fine)
fastboot reboot bootloader
fastboot boot mypatched.img

I get the dreaded <waiting for any device> message and it just hangs and nothing happens. Now, if it just takes forever please let me know but I waited a good while on three attempts and that's not usually how that goes with booting/flashing. I tried using Cascade's image and my own patched image.

I tried the method that I use on my Boox Leaf:

adb reboot fastboot
fastboot devices (yes returns device)
fastboot boot mypatched.img

I get:

Sending 'boot.img' (98304 KB)                      OKAY [  0.384s]
Booting                                            FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed

I assume is something to do with having boot_a and boot_b and not a straight up boot partition?

If I get to adb reboot fastboot alone, I can't actually manually select to get into bootloader (or recovery for that matter) because I have no dang volume buttons to change the selection (do not get me started on this case it is horrible).

Is there another way? I could work out how to flash with Renate's edl.exe tool but the thing that worries me that way is I can't test the boot before flash like I usually do.

If people have suggestions that would be lovely thanks, otherwise Renate, if I have to go with edl.exe best I wait for a recovery just in case yeah?

Thanks all.

[Renate]

No, it looks like there is something wrong with your bootloader command processing.
The "gold standard" is always flashing, then rebooting normally.
OTOH, this is not a good idea if your image is actually bad for some reason.
OTOH, since you know your way around EDL there is not too much risk as long as you don't destroy the partitioning.

As much as I'm a partisan of edl.exe there is not a world of difference between that and edl.py

[mergen3107]

Originally Posted by bazookajoe

I'd love is someone could write a tutorial on how to get bkerler's edl to work on Windows 10

Here is how I managed to get it working on my Onyx Boox Kon-Tiki 2. It has the same platform as Onyx Boox Nova 3. Get the loader according to your device.

EDL setup
(+ Delete all Qualcomm and UsbDk stuff)
+ Install zadig https://zadig.akeo.ie/ WinUSB driver for QUSB_BULK after connected in edl.
+ Fresh reboot to edl again (adb reboot edl).
+ Load the prepeared loader (present in the edl package):

python edl.py --loader=QC_SDM636.bin --memory=eMMC

It should say "main - Mode detected: sahara".
Then after each command it will say: "main - Mode detected: firehose".

+ to dump all partitions to directory dumps for device with emmc and skipping userdata partition, write rawprogram0.xml:
python edl.py rl dumps --skip=userdata --genxml
+ or one by one:
python edl.py r boot 1boot.img
python edl.py r recovery 2recovery.img
python edl.py r system 3system.img

+ re-write partitions to their respective places
python edl.py w boot boot.bin
python edl.py w system system.bin

+ to write all files from "dumps" folder to according partitions to flash:
python edl.py wl dumps

+ reboot from edl
python edl.py reset

[bazookajoe]

@mergen3107 thanks that's very kind! I will give that a play in the next few days.

Everyone, what do you think the issue could be with bootloader then? In Developer Options the OEM unlocking is greyed out saying it's already unlocked, just like my Boox Leaf.

I just tested on my Leaf in case something has go awry with drivers but that's working fine also my drivers are all up-to-date and it's latest SDK. I'm using their supplied cable too.

Do any other NoteAir2 users have this problem? When you boot to fastboot, do you get the image attached on my last post? I'll add it again to this post just in case you don't see it. So that's what happens on adb reboot fastboot. It goes to that menu (which I can't use anyway!), seems to reboot to bootloader OK (at least fastboot says it did so OK and it then changes to the ONYX screen) but then won't accept commands as stated previously.

I tried using fastbogus too and that doesn't work. I did run this command because reasons (it was in a post of Renate's) and that's also saying bootloader is unlocked but also unknown right at the bottom, just like my menu says bootloader is unknown:

C:\fastbogus>fastbogus getvar all
(bootloader) cpu-abi:arm64-v8a
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) is-logical:ssd:no
(bootloader) is-logical:misc:no
(bootloader) is-logical:sda:no
(bootloader) is-logical:xbl_b:no
(bootloader) is-logical:devcfg_a:no
(bootloader) is-logical:mdtpsecapp_b:no
(bootloader) is-logical:abl_a:no
(bootloader) is-logical:xbl_config_b:no
(bootloader) is-logical:featenabler_b:no
(bootloader) is-logical:recovery_a:no
(bootloader) is-logical:modem_a:no
(bootloader) is-logical:sdc:no
(bootloader) is-logical:cmnlib64_a:no
(bootloader) is-logical:mdtpsecapp_a:no
(bootloader) is-logical:modem_b:no
(bootloader) is-logical:userdata:no
(bootloader) is-logical:boot_a:no
(bootloader) is-logical:bluetooth_b:no
(bootloader) is-logical:hyp_a:no
(bootloader) is-logical:vbmeta_a:no
(bootloader) is-logical:mdtp_a:no
(bootloader) is-logical:abl_b:no
(bootloader) is-logical:keymaster_a:no
(bootloader) is-logical:metadata:no
(bootloader) is-logical:qupfw_a:no
(bootloader) is-logical:hyp_b:no
(bootloader) is-logical:mdtp_b:no
(bootloader) is-logical:bluetooth_a:no
(bootloader) is-logical:tz_a:no
(bootloader) is-logical:qupfw_b:no
(bootloader) is-logical:vbmeta_system_a:no
(bootloader) is-logical:cmnlib_b:no
(bootloader) is-logical:xbl_config_a:no
(bootloader) is-logical:uefisecapp_b:no
(bootloader) is-logical:devcfg_b:no
(bootloader) is-logical:rpm_a:no
(bootloader) is-logical:uefisecapp_a:no
(bootloader) is-logical:imagefv_a:no
(bootloader) is-logical:sdb:no
(bootloader) is-logical:featenabler_a:no
(bootloader) is-logical:rpm_b:no
(bootloader) is-logical:imagefv_b:no
(bootloader) is-logical:sdd:no
(bootloader) is-logical:cmnlib64_b:no
(bootloader) is-logical:dsp_a:no
(bootloader) is-logical:keymaster_b:no
(bootloader) is-logical:tz_b:no
(bootloader) is-logical:dtbo_a:no
(bootloader) is-logical:sde:no
(bootloader) is-logical:xbl_a:no
(bootloader) is-logical:dsp_b:no
(bootloader) is-logical:cmnlib_a:no
(bootloader) is-logical:super:no
(bootloader) is-logical:recovery_b:no
(bootloader) is-logical:vbmeta_system_b:no
(bootloader) is-logical:vbmeta_b:no
(bootloader) is-logical:boot_b:no
(bootloader) is-logical:dtbo_b:no
(bootloader) is-logical:system_b:yes
(bootloader) is-logical:system_ext_b:yes
(bootloader) is-logical:product_b:yes
(bootloader) is-logical:vendor_b:yes
(bootloader) is-logical:system_b-cow:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4417
(bootloader) off-mode-charge:0
(bootloader) treble-enabled:true
(bootloader) is-userspace:yes
(bootloader) partition-size:ssd:0x2000
(bootloader) partition-size:misc:0x100000
(bootloader) partition-size:sda:0xDD4800000
(bootloader) partition-size:xbl_b:0x380000
(bootloader) partition-size:devcfg_a:0x20000
(bootloader) partition-size:mdtpsecapp_b:0x400000
(bootloader) partition-size:abl_a:0x100000
(bootloader) partition-size:xbl_config_b:0x20000
(bootloader) partition-size:featenabler_b:0x20000
(bootloader) partition-size:recovery_a:0x6000000
(bootloader) partition-size:modem_a:0xB400000
(bootloader) partition-size:sdc:0x800000
(bootloader) partition-size:cmnlib64_a:0x80000
(bootloader) partition-size:mdtpsecapp_a:0x400000
(bootloader) partition-size:modem_b:0xB400000
(bootloader) partition-size:userdata:0xCC3DD3000
(bootloader) partition-size:boot_a:0x6000000
(bootloader) partition-size:bluetooth_b:0x100000
(bootloader) partition-size:hyp_a:0x80000
(bootloader) partition-size:vbmeta_a:0x10000
(bootloader) partition-size:mdtp_a:0x2000000
(bootloader) partition-size:abl_b:0x100000
(bootloader) partition-size:keymaster_a:0x80000
(bootloader) partition-size:metadata:0x1000000
(bootloader) partition-size:qupfw_a:0x10000
(bootloader) partition-size:hyp_b:0x80000
(bootloader) partition-size:mdtp_b:0x2000000
(bootloader) partition-size:bluetooth_a:0x100000
(bootloader) partition-size:tz_a:0x400000
(bootloader) partition-size:qupfw_b:0x10000
(bootloader) partition-size:vbmeta_system_a:0x10000
(bootloader) partition-size:cmnlib_b:0x80000
(bootloader) partition-size:xbl_config_a:0x20000
(bootloader) partition-size:uefisecapp_b:0x200000
(bootloader) partition-size:devcfg_b:0x20000
(bootloader) partition-size:rpm_a:0x80000
(bootloader) partition-size:uefisecapp_a:0x200000
(bootloader) partition-size:imagefv_a:0x200000
(bootloader) partition-size:sdb:0x800000
(bootloader) partition-size:featenabler_a:0x20000
(bootloader) partition-size:rpm_b:0x80000
(bootloader) partition-size:imagefv_b:0x200000
(bootloader) partition-size:sdd:0x8000000
(bootloader) partition-size:cmnlib64_b:0x80000
(bootloader) partition-size:dsp_a:0x2000000
(bootloader) partition-size:keymaster_b:0x80000
(bootloader) partition-size:tz_b:0x400000
(bootloader) partition-size:dtbo_a:0x1800000
(bootloader) partition-size:sde:0x100000000
(bootloader) partition-size:xbl_a:0x380000
(bootloader) partition-size:dsp_b:0x2000000
(bootloader) partition-size:cmnlib_a:0x80000
(bootloader) partition-size:super:0x100000000
(bootloader) partition-size:recovery_b:0x6000000
(bootloader) partition-size:vbmeta_system_b:0x10000
(bootloader) partition-size:vbmeta_b:0x10000
(bootloader) partition-size:boot_b:0x6000000
(bootloader) partition-size:dtbo_b:0x1800000
(bootloader) partition-size:system_b:0x65498000
(bootloader) partition-size:system_ext_b:0x13012000
(bootloader) partition-size:product_b:0x1B686000
(bootloader) partition-size:vendor_b:0x1F1DD000
(bootloader) partition-size:system_b-cow:0x4D1F2000
(bootloader) version-vndk:30
(bootloader) partition-type:ssd:raw
(bootloader) partition-type:misc:raw
(bootloader) partition-type:sda:raw
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-type:abl_a:raw
(bootloader) partition-type:xbl_config_b:raw
(bootloader) partition-type:featenabler_b:raw
(bootloader) partition-type:recovery_a:raw
(bootloader) partition-type:modem_a:raw
(bootloader) partition-type:sdc:raw
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-type:modem_b:raw
(bootloader) partition-type:userdata:raw
(bootloader) partition-type:boot_a:raw
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-type:abl_b:raw
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-type:metadata:raw
(bootloader) partition-type:qupfw_a:raw
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-type:tz_a:raw
(bootloader) partition-type:qupfw_b:raw
(bootloader) partition-type:vbmeta_system_a:raw
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-type:xbl_config_a:raw
(bootloader) partition-type:uefisecapp_b:raw
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-type:uefisecapp_a:raw
(bootloader) partition-type:imagefv_a:raw
(bootloader) partition-type:sdb:raw
(bootloader) partition-type:featenabler_a:raw
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-type:imagefv_b:raw
(bootloader) partition-type:sdd:raw
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-type:tz_b:raw
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-type:sde:raw
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-type:super:raw
(bootloader) partition-type:recovery_b:raw
(bootloader) partition-type:vbmeta_system_b:raw
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-type:boot_b:raw
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-type:system_b:raw
(bootloader) partition-type:system_ext_b:raw
(bootloader) partition-type:product_b:raw
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-type:system_b-cow:raw
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:sda:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:mdtpsecapp:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:xbl_config:yes
(bootloader) has-slot:featenabler:yes
(bootloader) has-slot:recovery:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:sdc:no
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:userdata:no
(bootloader) has-slot:boot:yes
(bootloader) has-slot:bluetooth:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:mdtp:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:metadata:no
(bootloader) has-slot:qupfw:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:vbmeta_system:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:uefisecapp:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:imagefv:yes
(bootloader) has-slot:sdb:no
(bootloader) has-slot:sdd:no
(bootloader) has-slot:dsp:yes
(bootloader) has-slot:dtbo:yes
(bootloader) has-slot:sde:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:system_ext:yes
(bootloader) has-slot:product:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:system_b-cow:no
(bootloader) security-patch-level:2020-11-05
(bootloader) vendor-fingerprint:Onyx/NoteAir2/NoteAir2:11/2021-11-22_11-01_3.2_0ae74d7d5d/31272:user/dev-keys
(bootloader) hw-revision:0
(bootloader) current-slot:b
(bootloader) serialno:2B3EFD8F
(bootloader) product:NoteAir2
(bootloader) version-os:11
(bootloader) first-api-level:30
(bootloader) slot-count:2
(bootloader) max-download-size:0x10000000
(bootloader) version:0.4
(bootloader) version-baseband:
(bootloader) secure:yes
(bootloader) variant:NA
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:Onyx/NoteAir2/NoteAir2:11/2021-11-22_11-01_3.2_0ae74d7d5d/31272:user/dev-keys
(bootloader) version-bootloader:unknown
(bootloader) unlocked:yes
all:
Finished. Total time: 0.908s

I'm wondering if it's a 3.2.2 problem, like they're deliberately trying to make it harder to root or something? I'm wondering if I reset back down to factory 3.2 (I think) to see if there's a difference there out of curiosity but I've got it all set up nice now I don't really want to do that if I don't have to also I don't have this issue with my Leaf which is already on 3.2.2.

As it's a new product I just bought, I also wonder if they're cracking down some other way that earlier models don't to make it harder to root?

Could UsbDk or libUSB be interfering?

Edit: Is the secure boot thing a problem?

I'd really rather have a fully working fastboot if I can this makes me anxious (and it bothers me in principle) and I don't really know anything about this otherwise.

[Renate]

I'm confused (normal state for me).
EDL is working ok since you can grab images.
The fastboot that you are showing is the fastbootd of recovery which is not really the same as regular "reboot bootloader".
Are you having some problem?

[bazookajoe]

This is what I tried like Cascade94 said:

adb devices = fine, device is present
adb reboot fastboot = produces that menu picture I uploaded on my screen. I've tried this 10 times at minimum. Same result every time.
fastboot devices = to check if fastboot is working and device read (yes it does)
fastboot reboot bootloader = appears to work get an OK message. Screen turns to ONYX hooray.
fastboot boot mypatched.img

<waiting for any device>.

I've also tried going directly to bootloader:

adb devices
adb reboot bootloader
fastboot boot mypatched.img

<waiting for any device>

I've tried no bootloader at all:

adb devices
adb reboot fastboot
fastboot devices
fastboot boot mypatched.img

That just gives an error because it doesn't recognise "boot" because bootloader and I have boot_a and boot_b blah blah.

I'm not really willing to try fastboot flash boot_a mypatched.img, if I can't even get it to boot to check if the .img works. I just won't. I've always booted up to see if root worked in Magisk before properly flashing/installing. Always.

Maybe there's a special syntax that I'm not understanding because of two boot partitions but still, Cascade94 apparently gets their images to boot to test and see if it works unless things have changed since their last guide.

I understand I could flash through edl but I'd really rather work out fastboot first/understand my device properly.

Edit: and how to boot a patched image first before flashing. That's always been an option available I want to understand how that works on a device with two boot partitions.