MobileRead Forums - View Single Post

ArkVlad · 10-18-2024, 06:24 PM

Hello there!

I would like to root my Poke 5 (FW 1.3.5) as well, however I do not have that much experience with EDL (more with adb & fastboot). For me it was the same situation, that I could not write the Magisk patched "boot.img" file, neither "vbmeta" (a & b) through the fastboot.

Could someone control me, that I have done a correct plan (nothing except backup was done) to fix it through the EDL?

1) We connect to the Reader in EDL mode, by typing:

Code:

edl /l001860e100000000_d9357db88795b5a8_Qcm2290_ddr_fhprg.elf (the loader Renate linked in the first page of this thread)

2) Secondly, we make a backup, just in case something goes wrong:

Code:

edl /r backup.img

3) Here I am unsure. Do we write the Magisk patched boot.img only (depending if it is A or B partition, of course)?

Code:

edl /w /pboot_a patched-boot.img

4) Do we need to disable vbmeta's verification thing through EDL?
In case yes, how do we do it?
I have found a tool that patches vbmeta files, but I am not sure, if it is the correct solution, or if we tamper the "boot.img" partition with EDL, do we need to do something with the vbmeta partitions?
If it is fine, do we simply do like that?

Code:

edl /w /pvbmeta-a patched-vbmeta.img

Also, where does "poke5.bin" come from? Is it simply the backup we took earlier? If so, why does it have ".bin" extension then? ><

Code:

C:\>edl /lpoke5.bin

P.S.: Do I understand correctly, that EDL utility is taken from here?

(Pardon if formatting is wrong, first time I am using a forum.)

10-18-2024, 06:24 PM	#37
ArkVlad Junior Member Posts: 6 Karma: 10 Join Date: Oct 2024 Location: Sweden Device: Onyx Boox Poke 5, Kobo Aura One	Hello there! I would like to root my Poke 5 (FW 1.3.5) as well, however I do not have that much experience with EDL (more with adb & fastboot). For me it was the same situation, that I could not write the Magisk patched "boot.img" file, neither "vbmeta" (a & b) through the fastboot. Could someone control me, that I have done a correct plan (nothing except backup was done) to fix it through the EDL? 1) We connect to the Reader in EDL mode, by typing: Code: edl /l001860e100000000_d9357db88795b5a8_Qcm2290_ddr_fhprg.elf (the loader Renate linked in the first page of this thread) 2) Secondly, we make a backup, just in case something goes wrong: Code: edl /r backup.img 3) Here I am unsure. Do we write the Magisk patched boot.img only (depending if it is A or B partition, of course)? Code: edl /w /pboot_a patched-boot.img 4) Do we need to disable vbmeta's verification thing through EDL? In case yes, how do we do it? I have found a tool that patches vbmeta files, but I am not sure, if it is the correct solution, or if we tamper the "boot.img" partition with EDL, do we need to do something with the vbmeta partitions? If it is fine, do we simply do like that? Code: edl /w /pvbmeta-a patched-vbmeta.img Also, where does "poke5.bin" come from? Is it simply the backup we took earlier? If so, why does it have ".bin" extension then? >< Code: C:\>edl /lpoke5.bin P.S.: Do I understand correctly, that EDL utility is taken from here? (Pardon if formatting is wrong, first time I am using a forum.)