@Renate: I did some more testing. And I was able to read/write partition images with Palma 2 loader listed at your site. So you were right, it does work too.
For some reason it started to work when I removed SDcard from Palma 2 Pro. Or maybe I just did something wrong. Just remove any memory cards from device next time - just to be safe.
I also ended with "bricked" Palma for some time (after flashing magisked boot_b.img) booting only into fastboot mode (Boox logo on screen stuck). And unbricked the palma flashing back original boot image.
But it was weird. I probably messed something up - it is very possible. For now I am done testing until I can try that Windows EDL version. So I am posting my notes here for any fellow adventurer who might be willing to sacrifice device when trying.
It is not my invention, I just repeated process described many times.
Here for example.
Rooting - Unsuccessful
Code:
wget -O palma2pro.bin 'https://github.com/bkerler/Loaders/raw/refs/heads/main/lenovo_motorola/0000000000000000_bdaf51b59ba21d8a_fhprg.bin'
adb reboot edl
edl --loader=palma2pro.bin --memory=ufs r devinfo partitions/devinfo.img
edl --loader=palma2pro.bin --memory=ufs r boot_a partitions/boot_a.img
edl --loader=palma2pro.bin --memory=ufs r boot_b partitions/boot_b.img
edl --loader=palma2pro.bin reset
adb reboot bootloader
# Now it will be stuck with BOOX logo on screen
fastboot getvar all
# note the "current-slot" value
# For me it was current-slot:b
# So I will work with boot_b partition
fastboot reboot
# Boot back to Android
adb push partitions/boot_b.img /sdcard/
# upload extracted partition to phone
# Now just patch image using Magisk in phone
# I used Magisk v30.6 https://github.com/topjohnwu/Magisk/releases/tag/v30.6
adb pull /sdcard/Download/magisk_patched-30600_WosxU.img partitions/boot_b_patched.img
# Download patched image from phone
adb reboot edl
edl --loader=palma2pro.bin --memory=ufs w boot_b partitions/boot_b_patched.img
edl --loader=palma2pro.bin reset
At this point I ended up with "bricked" device with stuck Boox logo on screen. Not booting any further.
But I was lucky, device was constantly booting into fastboot. I was able to do:
Code:
## Fastboot check
fastboot devices
fastboot getvar all
How to get from fastboot to EDL
When I ended up with device stuck in fastboot mode, I tried numerous things. This procedure worked for me to get it back into EDL.
Keep device connected to computer and issue some EDL command. I used this:
Code:
edl --loader=palma2pro.bin printgpt
Press and hold power button until Palma starts rebooting - screen flashes.
Then immediately release power button and press and hold VolUp + VolDown. Device gets recognized by computer and is put into EDL mode.
Flashing back stock images
To recover device back to working state I did this:
Code:
edl --loader=palma2pro.bin w boot_b partitions/boot_b.img
edl --loader=palma2pro.bin setactiveslot a
edl --loader=palma2pro.bin reset
# Repeat process to get from fastboot to EDL
edl --loader=palma2pro.bin setactiveslot b
edl --loader=palma2pro.bin reset
I do not know why, but without setting that active slot back and forth Palma refused to boot. (But doing same procedure with magisked boot_b.img does not work - tested that)
Questions
This process left some unanswered questions for me. I probably did something wrong. Or it might be that this linux EDL does not work properly. Not sure.
Main question. Why is there two boot partitions A and B? I was thinking that it is safety measure for updates and content in both slots should be same. When update fails, device can return to other slot which is intacted and able to boot.
But aparently this is not true. When my Palma failed to boot after flashing magisked boot_b.img first thing I tried was just to set activeslot to A. But device did not boot after that.
Any ideas if Palma bootloader can be unlocked somehow?
Does anyone have info how to boot into Palma 2 (Pro) recovery menu?
Any link to download Palma 2 Pro firmware? Tried procedure described in
decryptBooxUpdateUpx. But without luck.