Boox Leaf 2 general discussion

[Renate]

I forget where we left all this.
Did you try this one? It's new.
Or the two 0014's here. One is new.

I don't remember if we determined whether you were Secure Boot or not.
If you weren't then you don't have to worry about the hash bit.
OTOH, since a single Firehose loader can cover multiple HWID you've got about 700 possibilities.

[denisuu]

Originally Posted by Renate

I forget where we left all this.
Did you try this one? It's new.
Or the two 0014's here. One is new.

I don't remember if we determined whether you were Secure Boot or not.
If you weren't then you don't have to worry about the hash bit.
OTOH, since a single Firehose loader can cover multiple HWID you've got about 700 possibilities.

I don't think we figured out if it's secure boot or not.

Sending 0014d0e100720000_1bebe3863a6781db_fhprg.bin 100% Ok
Waiting for Firehose... No response, poking...

Sending 0014d0e100720000_1bebe3863a6781db_fhprg.bin 100% Ok
Waiting for Firehose... No response, poking...

PS C:\Android Tools> .\edl.exe /l0014d0e100000000_d40eee56f3194665_FHPRG.bin
Found EDL 9008
Received unexpected 12 command
Resetting Sahara
Received unexpected 04 command

No luck with those, should I try B. Kerler's EDL application?

[Renate]

Originally Posted by denisuu

No luck with those...

You didn't have a clean test of the d40eee.
Do a reset and try again.

[denisuu]

Originally Posted by Renate

You didn't have a clean test of the d40eee.
Do a reset and try again.

I rebooted the device and tried again, still no luck though.

Sending 0014d0e100000000_d40eee56f3194665_FHPRG.bin 100% Ok
Waiting for Firehose... No response, poking...
Could not write device

[Renate]

Originally Posted by denisuu

... still no luck though.

Correct, but if it doesn't even try to load the Firehose we can't tell anything.

Many of the processors are similar enough that a loader for one will work on another.
OTOH, major hardware difference (RAM, power management) will prevent a loader from working.
(I hadn't known off-hand, but I just checked. Firehose, like xbl does use DRAM. This makes Firehose loaders more particular as to type and mapping. PBL obviously does not use DRAM because it can have no knowledge of it.)

What is the latest model Onyx for which we have a working Firehose loader?
Has Onyx gotten hardnose on SecureBoot? I don't know.

Still, I wish that I had bought a case of Poke3's so that I could just remain blissfully ignorant and in the past.

[denisuu]

There's a new boot image in the last update for the Leaf2 (2023-04-20_11-32_3.3.2_9916cdce0). Here are the updated instructions to root the Leaf2.

1. Test if ADB and Fastboot are working, if the commands below don't work, install ADB and the Google USB drivers

PS C:\00 - Standalone\ADB> .\adb.exe devices
List of devices attached
1EED4B07        device

PS C:\> adb reboot bootloader
PS C:\>  .\fastboot.exe devices
1EED4B07        fastboot

PS C:\>  .\fastboot.exe reboot
rebooting...

finished. total time: -0.000s

2. Download decryptBooxUpdateUPX from Github

3. Open Powershell or CMD and run:

pip install pycryptodome

4. Download the update from the Boox website or from your device.

5. Add the update.upx to the decryptBooxUpdateUPX folder and run the following command in Powershell:

python DebooxUpx.py Leaf2

6. Extract the payload.bin from the update.zip file.
7. Download Payload Dumper GUI
8. Extract the payload.bin
9. Move the extracted boot.img to the internal storage on your Leaf2
10. In Magisk tap: 'Install' > 'Next' > 'Select and Patch a File' > (Select your boot.img) > 'Let's Go'
11. Once complete, copy the 'magisk_patched-xxxxx_xxxxx.img to your PC

12. In Powershell run:

adb reboot bootloader

13. Wait a bit and run the following commands (with the correct image name ofcourse):

PS C:\> adb reboot bootloader

PS C:\>  fastboot devices
1EED4B07        fastboot

PS C:\> fastboot boot .\magisk_patched-26100_P0gYT.img
downloading 'boot.img'...
OKAY [  2.130s]
booting...
OKAY [  0.143s]
finished. total time: 2.274s

14. If the device successfully boots you can install the patched boot image from magisk
15. In Magisk tap: 'Install' > 'Next' > 'Direct Install (Recommended) > 'Let's Go'

[popej]

Which version of Magisk are you using?
Magisk 25.2 works, but I wonder if upgrade to 26.1 is safe.

[denisuu]

I'm using 26.1 didn't notice any problems.

Btw: You're also using AFWall+ right? Do you know if there's a way to make it survive killing all applications in the multitasking switcher? There are unlocked icons next to the running apps in the new update, so I would asume there's a way to lock them. It sucks that killing everything closes AFWall+ so you have to kill all the apps separately.

[popej]

Thanks.
I haven't updated system yet. I don't know how to kill all apps, is there a possibility? Killing manually only AFWall+ works, but it is what you should expect.

[livewirerc]

I recently updated my Boox Leaf 2 to the latest firmware, and now I can no longer access the epub files (or anything else for that matter) on my SD card, either via Moon+ Reader, or via my preferred file manager FX File Explorer.

Using the built-in reader and file explorer "works", so it seems that the files are still there and accessible, but not via other applications. Does anybody have any tips on how to properly access files on the SD card under the latest firmware?

In FX File Explorer, when I click "Connect to Storage" in the three dot menu, any time I navigate to the root of the SD card and click "Use This Folder", I get "To protect your privacy, choose another folder". This is frustrating as it worked days ago prior to the firmware update.

[Renate]

Originally Posted by livewirerc

I can no longer access the epub files...

Did you check (stock Google) Settings > Apps > Whatever > Permissions?

C:\>adb shell am start -n com.android.settings/.Settings

[livewirerc]

Originally Posted by Renate

Did you check (stock Google) Settings > Apps > Whatever > Permissions?

C:\>adb shell am start -n com.android.settings/.Settings

I've not done the command line method, but if I go into App Management > App Info > FX > Permissions, I've confirmed that Files and Media: All Files is allowed. Is this what you're referring to?

Additionally, I've found that I can mount directories from my SD Card directly within FX File Explorer, but I can't mount the root of the SD card. For instance, my card is called LEAF1TB, so I can mount LEAF1TB\Books, and it shows up as "Books" on my home screen in FX File Explorer, which is progress, but I'd much rather mount the root of the card so I can navigate it like I used to be able to.

[livewirerc]

Originally Posted by Renate

Did you check (stock Google) Settings > Apps > Whatever > Permissions?

C:\>adb shell am start -n com.android.settings/.Settings

I've not done so via ADB, but did go into app management for FX and confirmed files and media access was allowed. Is this what you're referring to? That lets me see files on the device itself but I still can't read the SD card.

[Renate]

Oh, you're talking about a physical SD card?
You shouldn't have to do any mounting yourself.
It should be mounted already as extsd.
What does "mount" say?

[denisuu]

Originally Posted by popej

Thanks.
I haven't updated system yet. I don't know how to kill all apps, is there a possibility? Killing manually only AFWall+ works, but it is what you should expect.

I meant the gesture when swiping up (Settings.png) There must be a way to lock AFwall+? Why is there a lock icon next to the apps otherwise?

It would be nice to just be able to push the trash icon and kill all apps without it killing AFwall+.