Flash the global rom of Boox Page for Boox Leaf3 Chinese version

[I_Love_Saigon]

How to reboot to EDL with button? I dont have EDL cable.
My device does not root before.
I can get back to normal, it stuck at white screen.
Can not enter ADB, PC not detect ADB device.

Here the log :

C:\Users\THIEN UY>adb reboot edl

C:\Users\THIEN UY>cd C:\boox

C:\boox>edl
Found EDL 9008

C:\boox>edl /lpage.bin
Found EDL 9008, handshaking... version 2.1
HWID: 0014d0e100000000, JTAG: 0014d0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending page.bin 100% ok, starting... ok, waiting for Firehose...
<log value="ERROR: Call to ufs_open(0, UFS_WLUN_DEVICE) failed:0" />
Ok

C:\boox>
C:\boox>
C:\boox>edl /w /precovery_b rec-custom.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write rec-custom.img... ok, writing 100% ok

C:\boox>edl /z
Found EDL 9008, requesting reboot... ok

C:\boox>adb reboot recovery

C:\boox>adb devices
List of devices attached


C:\boox>adb devices
List of devices attached


C:\boox>adb shell
error: no devices/emulators found

C:\boox>adb shell
error: no devices/emulators found

C:\boox>fastboot devices

C:\boox>adb shell
error: no devices/emulators found

C:\boox>adb devices
List of devices attached

[I_Love_Saigon]

Do you have Telegram or something else to instant chat?

[Renate]

Originally Posted by I_Love_Saigon

Do you have Telegram or something else to instant chat?

No.

Download a new version of my custom recovery.
Flash it with EDL as before.
Go to recovery.
Try ADB.
Try "start ttyscreen"
Try "reboot"

[I_Love_Saigon]

Hi Renate,

Let me try to make EDL cable and re-flash rec.img, then report to you.

Thank you.

[I_Love_Saigon]

Originally Posted by Renate

No.

Download a new version of my custom recovery.
Flash it with EDL as before.
Go to recovery.
Try ADB.
Try "start ttyscreen"
Try "reboot"

Hi Renate,

I have made EDL cable to enter EDL and flashed latest custom recovery image you share already. But the same old. In recovery mode the PC can not detect adb device. Here the log :

C:\boox>edl
Found EDL 9008

C:\boox>
C:\boox>
C:\boox>
C:\boox>
C:\boox>edl /lpage.bin
Found EDL 9008, handshaking... version 2.1
HWID: 0014d0e100000000, JTAG: 0014d0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending page.bin 100% ok, starting... ok, waiting for Firehose...
<log value="ERROR: Call to ufs_open(0, UFS_WLUN_DEVICE) failed:0" />
Ok

C:\boox>edl /w /precovery_b ils-rec_2.img
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting write ils-rec_2.img... ok, writing 100% ok

C:\boox>edl /z
Found EDL 9008, requesting reboot... ok

C:\boox>adb devices
List of devices attached
6C1DD622 device


C:\boox>adb shell
BOOX:/ $ reboot recovery

C:\boox>adb devices
List of devices attached


C:\boox>adb devices
List of devices attached


C:\boox>adb shell
error: no devices/emulators found
-------------------------------------

Do I need to root first? Please help me.

Thank you.

[I_Love_Saigon]

Hi Renate,

Please check private mess, please.

[Renate]

Ok, so now you've got an EDL cable and you know how to make it work. That is one of the problems with trying to make a custom recovery, you can get stuck in recovery. We'll fix that.

First of all, forget that Firehose loader. Use the one for the Page listed here: https://www.temblast.com/ref/onyxldr.htm. That will get rid of the stupid UFS error.

Now go to EDL mode, load the new loader. Then make it stop going to recovery.

C:\>edl /f /pmisc

Now grab the boot image.

C:\>edl /r /pboot_b boot.img

And reboot.

C:\>edl /z

Install Magisk as you would any other app. Push the boot image to sdcard.

C:\>adb push boot.img sdcard

Now run Magisk and convert the boot image. ADB pull the Magisk'ed image, go to EDL and flash it to boot_b and reboot. Go to Magisk app and enable "su" for ADB.

C:\>adb shell
$ su
#

Follow the above instructions for i2cscan and copy the result.

[I_Love_Saigon]

Thanks Renate, let me try and report to you soon.

[I_Love_Saigon]

Hi Renate,

Here the result :

BOOX:/data/local/tmp $ ./i2cscan
/dev/i2c-0 /soc/i2c@4a80000 - failed

/dev/i2c-1 /soc/i2c@4a84000 - failed

/dev/i2c-2 /soc/i2c@4a88000 - failed
--------------------------------------------

[Renate]

You're not running that as root. You need to be seeing #, not $.

C:\>adb shell
$ su
#

[I_Love_Saigon]

Hi Renate,

I update the result :

BOOX:/data/local/tmp # ./i2cscan
/dev/i2c-0 /soc/i2c@4a80000
09 wacom Wacom digitizer
38 W0R0 In use lm3630a lm3630a_bl TI LED controller
3f In use qcom,cam-sensor i2c_camera
40 W0

/dev/i2c-1 /soc/i2c@4a84000
0e wsa881x-i2c-codec
42 W0R0 In use fsa4480 fsa4480-driver Onsemi USB 2 audio multiplexor
44 wsa881x-i2c-codec
58 W0R0 In use
59 W0

/dev/i2c-2 /soc/i2c@4a88000 nozero
08 W1R1 In use focaltech fts_ts FocalTech touch controller
24 tsc
40 W1R1 In use mxo4300 mxo
41 W1R1
43 R1
48 W1R1 In use max17135 max17135 Maxim Eink power management

Thanks

[Renate]

Much better. Hold on for a new recovery...

Don't worry about that post now, but please quote text inside [code] and [/code] in the future.

[Renate]

Sorry, I am so STEWPID!

Download a new recovery and flash it. Get white screen.

C:\>adb shell
# start ttyscreen
# reboot

[I_Love_Saigon]

Hi Renate,

I reflashed the recovery. Now the PC can see adb device in recovery mode.

I run "start ttyscreen" already, but the screen still white, i didn't see any text or wiggly lines.

Thanks.

[Renate]

I think that we've made a lot of progress, but I don't know.

Did you get # ?
Did the reboot command print stuff and work correctly?
What did it print?

Go to recovery again.

C:\>adb shell
# start ttyscreen
# start autoupdate
# reboot