Root for Note Air 2?

[downeaster59]

Originally Posted by readandread

@downeaster59 @Renate Will the firmware update on the BOOX just download it so I can pull it off the devices via USB first or does it automatically apply is? If former is the case I'll play around with it this weekend.

The update downloads, and then you are given the option of updating now or later. If you choose 'later', you can play around with the update to your heart's content!

[Renate]

Well, if you know what your device is called you can download the update to your desktop directly.
I know that my Poke3 is actually "Poke3".
I see that the NA is, in fact "NoteAir".
I don't think that the NA2 is "NoteAir2", "NoteAir 2", "Note Air2" or "Note Air 2"

[readandread]

Originally Posted by downeaster59

The update downloads, and then you are given the option of updating now or later. If you choose 'later', you can play around with the update to your heart's content!

Since you also have Note Air2, maybe this is helpful...

I just had 15 minutes of free time and tried your launcher and this command again:

python3 edl.py --loader=Qualcomm_662_loader.elf printgpt

and additionally, with the other loader (prog_firehose_life_ddr_patched.elf), I got from a Github issue.

And got a bunch of text back. I also tried adding the --memory=ufs tag at the end. Here's the result. printgpt.rtf

Doesn't t tell me much, but maybe @Renate has some insight.

I seem to have gotten much further than before. I've never been able to get this much info via the terminal

[Renate]

@readandread Could you please try this (using whatever is your best loader)?

edl.exe /u /lwhatever.bin
edl.exe /u boota.img 14245878
edl.exe /u bootb.img 14343382

[readandread]

Originally Posted by Renate

@readandread Could you please try this (using whatever is your best loader)?

edl.exe /u /lwhatever.bin
edl.exe /u boota.img 14245878
edl.exe /u bootb.img 14343382

I've been having more success with on my Mac (see this post). I Win I get:

C:\Users\David\edl>edl.exe /u payload.bin
Found EDL 9008
Could not write device

C:\Users\David\edl>edl.exe /u boota.img 14245878
Found EDL 9008
Could not write device

C:\Users\David\edl>edl.exe /u bootb.img 14343382
Found EDL 9008
Could not write device

In terms of bin I used the one in the update.upx zip file with the following structure.

[readandread]

Originally Posted by downeaster59

Ah, now I see your point. I was focused on another side of this. I'll see if I can do this manually.

Have you been able to get further on this? I've had no problems decrypting the 180MB update. But haven't got further than this. I'm still a bit confused if I need the boot.img from the new v3.2.1 first, as there isn't one included.

Or do I:

Update from 3.2 --> 3.2.1 and lose my root
Pull the boot.img from the device that is now on 3.2.1 (this is something I haven't been able to do at all )
Patch it via Magisk?
Have root?

[downeaster59]

Originally Posted by readandread

Have you been able to get further on this? I've had no problems decrypting the 180MB update. But haven't got further than this. I'm still a bit confused if I need the boot.img from the new v3.2.1 first, as there isn't one included.

Or do I:

Update from 3.2 --> 3.2.1 and lose my root
Pull the boot.img from the device that is now on 3.2.1 (this is something I haven't been able to do at all )
Patch it via Magisk?
Have root?

You won't need a new boot.img. The one from 3.2 should work fine.

As for me, I was in touch with Onyx customer service. They ended up posting a much larger update file for 3.2.1 (1.2 GB). I successfully updated using this. I lost root in the process. I was able to pull boot.img from my device through edl, patch the boot.img with Magisk and flash the patched img, thus restoring root.

[Renate]

Originally Posted by readandread

I've been having more success with on my Mac... In Win I get:

C:\Users\David\edl>edl.exe /u payload.bin
Found EDL 9008
Could not write device

You never loaded a loader. Remember that bit about "/l" ?
I really would appreciate it if you tried this; I don't have access to a multi-partition Onyx device.
You have to start fresh, load a loader and if there's no response at all there's no point in giving any more commands.
You've seen that this does work to the extent of more than "Could not write device".

[downeaster59]

@Renate: In response to your PM. I hope this is what you're looking for, If not, I'll try again!

[Renate]

Thanks, that's fine.
It's showing the same thing that I see on the Poke3.
There's one DOS partition of 2 Terabytes.

I don't understand why the first? GPT table has only 13 entries.

I'll have to look some more.

Short interpretation:

0x0000 DOS MBR 2 Terabyte single partition
0x1000 GPT header for 32 GPT partitions
0x2000 GPT table with 13 entries

I'm clearly operating on inadequate knowledge.
The Poke3 has all 48 partitions in one GPT table.

[readandread]

Originally Posted by Renate

You never loaded a loader. Remember that bit about "/l" ?
I really would appreciate it if you tried this; I don't have access to a multi-partition Onyx device.
You have to start fresh, load a loader and if there's no response at all there's no point in giving any more commands.
You've seen that this does work to the extent of more than "Could not write device".

Like this?

edl.exe /lprog_firehose_life_ddr_patched.elf /u payload.bin

[readandread]

Originally Posted by downeaster59

You won't need a new boot.img. The one from 3.2 should work fine.

As for me, I was in touch with Onyx customer service. They ended up posting a much larger update file for 3.2.1 (1.2 GB). I successfully updated using this. I lost root in the process. I was able to pull boot.img from my device through edl, patch the boot.img with Magisk and flash the patched img, thus restoring root.

Ok, thanks. Just let me wrap my head around this process. The whole process of pulling boot.img patching it and applying isn't something I'm used to. I apologize I'm still confused a bit.

I understand the get the update and install it part, obviously.

Do you pull the boot.img via edl from the v3.2 or after the update (from v3.2.1)?

Do you then take that boot.img as is and copy that to the root directory of the devices, open Magisk and patch it and then apply it after that?

[Renate]

Hello, @readandread
The first step is to extract the boot.
Ok, you may have done that some other way, but your experience may help someone else.
Could you please try what I indicated above?
[See post #128]

[mergen3107]

Originally Posted by readandread

Ok, thanks. Just let me wrap my head around this process. The whole process of pulling boot.img patching it and applying isn't something I'm used to. I apologize I'm still confused a bit.

I understand the get the update and install it part, obviously.

Do you pull the boot.img via edl from the v3.2 or after the update (from v3.2.1)?

Do you then take that boot.img as is and copy that to the root directory of the devices, open Magisk and patch it and then apply it after that?

In few words:
1) Apply update.upx as usual
2) From decrypted update.zip get boot.img
3) Put it to device, Magisk - install - patch the boot.img
4) Now flash this patched image to device via fastboot or edl.
5) Open device, Magisk - install again - but this time around use “Direct install”. This option is not available on stock boot.img, so you won’t confuse it.
6) Reboot and you should have root.

[readandread]

Originally Posted by mergen3107

In few words:
1) Apply update.upx as usual
2) From decrypted update.zip get boot.img
3) Put it to device, Magisk - install - patch the boot.img
4) Now flash this patched image to device via fastboot or edl.
5) Open device, Magisk - install again - but this time around use “Direct install”. This option is not available on stock boot.img, so you won’t confuse it.
6) Reboot and you should have root.

OK, thanks that makes it much clearer. I did steps 1-2 which worked fine before as well, but I only a few folders and a big .bin file not an img file.