I'm curious if anyone has attempted to root their Note Air 2. I'm guessing that the process would be similar to what others have described for other Onyx devices on this forum. I wondered if rooting the Note Air 2 would even be worth the effort, but I can see a couple of possibilities.
If anyone has experience or suggestions, please pass them on.
If you have ADB working, please try this: (Sorry if I've asked this already.)
Code
C:\>adb shell grep Hardware /proc/cpuinfo
My Poke3 says: Qualcomm Technologies, Inc SDM636
If it's the same (or close), you can use EDL mode to download and subsequently modify the boot image.
What I get is Qualcomm Technologies, Inc BENGAL
Not sure how close that is!
Huh? It seems that's a code name for the new Snapdragon 662
There's a 660 driver here
https://github.com/bkerler/Loaders/tree/main/qualcomm/factoryNot sure how compatible that is.
I’ve never worked with EDL mode before. Do you know of some kind of step-by-step guide as to how I’d root my device this way? I assume it involves Magisk and getting a boot image!
Rule #1: There is no need to write anything to flash. You can run a boot image that is not in flash, so hold off writing anything.
Rule #2: If you've got the space, make a full backup on your desktop, then you're bomb-proof.
Do you have ADB working? Have you used UsbView.exe (presuming that you are running Windows? Linux is actually easier with lsusb.)
Step #1: Determine if you can get to EDL. This does no harm but you will have to do a LONG power press to restore usage.
Code
Does it go off into voodoo-land but the screen remains the same (frozen)?
Does UsbView.exe show VID/PID 05c6/9008? That's EDL mode.
If you want you can use my UsbLog.exe which is found on my website up a level, down to the Windows section. It's quite handy to figure out where all the Windows "bongs" are coming from.
Quote Renate
Rule #1: There is no need to write anything to flash. You can run a boot image that is not in flash, so hold off writing anything.
Rule #2: If you've got the space, make a full backup on your desktop, then you're bomb-proof.
Do you have ADB working? Have you used UsbView.exe (presuming that you are running Windows? Linux is actually easier with lsusb.)
Step #1: Determine if you can get to EDL. This does no harm but you will have to do a LONG power press to restore usage.
Code
Does it go off into voodoo-land but the screen remains the same (frozen)?
Does UsbView.exe show VID/PID 05c6/9008? That's EDL mode.
If you want you can use my UsbLog.exe which is found on my website up a level, down to the Windows section. It's quite handy to figure out where all the Windows "bongs" are coming from.
I have a Mac that has a Windows VM on it. This may or may not complicate the process. I haven't done anything yet! I could set up an Ubuntu VM if that would make anything easier - and assuming that the Ubuntu VM can connect with the Note Air.
I have ADB working on Mac and have ample room on my Mac to back up my Note Air 2. I set up ADB on my Windows VM, but I haven't been able to get Windows to see my Note Air 2 yet. That keeps me from using USBView. There is probably a Mac alternative out there.
I tried adb reboot edl. It goes the voodoo-land route. I was able to reboot it into normal mode before too long.
That's where things are as of now.
The Mac is fine. Stick with that and skip the VM stuff.
You can run "lsusb -v" on the command line and look for the 9008=good, 900e=not good.
If you have that you can follow the instructions here for install:
https://github.com/bkerler/edlCode
python edl.py --loader=try-that-660-file.bin --memory=emmc
python edl.py print-gpt --memory=emmc
python edl.py r boot boot.img --memory=emmc
Quote Renate
The Mac is fine. Stick with that and skip the VM stuff.
You can run "lsusb -v" on the command line and look for the 9008=good, 900e=not good.
If you have that you can follow the instructions here for install:
https://github.com/bkerler/edlCode
python edl.py --loader=try-that-660-file.bin --memory=emmc
python edl.py print-gpt --memory=emmc
python edl.py r boot boot.img --memory=emmc
When I ran "lsusb -v", I didn't see (exactly) either alternative you gave! here's what I got:
USB 3.1 Bus:
Host Controller Driver: AppleT8103USBXHCI
BENGAL-IDP _SN:C3253440:
Product ID: 0x4ee2
Vendor ID: 0x18d1 (Google Inc.)
Version: 4.19
Serial Number: XXXXXXXX
Speed: Up to 5 Gb/s
Manufacturer: QUALCOMM
Location ID: 0x00200000 / 1
Current Available (mA): 900
Current Required (mA): 896
Extra Operating Current (mA): 0
Yeah, but you have to do that when you're in EDL mode!
