Go 7 attempted root and now stuck on boox logo

[Grimbly1024]

My Go 7 Gen 2 should be arriving tomorrow - very keen to root it to remove all the spyware. Just wanted to ask if there's a full tutorial on how to do this on my mac ?

Just installing the software has been challenging!

[Renate]

Most people seem to go the Magisk route, er, root.
It's well documented and similar for all.
Just make sure that you use the boot image that is actually on your device.

[dcarvil]

Originally Posted by Grimbly1024

My Go 7 Gen 2 should be arriving tomorrow - very keen to root it to remove all the spyware. Just wanted to ask if there's a full tutorial on how to do this on my mac ?

Just installing the software has been challenging!

Make sure to read the posts on the previous page about rooting firmware 4.1.1 with magisk. That firmware version broke Magisk.

Also, rooting guides mentioning "fastboot flash" are outdated. Boox crippled fastboot several updates ago. Unless you are on older firmware, you will have to use edl to flash the patched boot image.

[Grimbly1024]

Hi All,

Sorry to appear stupid, but I got a bit lost with my first attempt and could do with a bit of help.

Firstly - what OS are you using ?

I tried using terminal on my mac and ended up with loads of issues with getting EDL to work.

I also tried various flavours of Linux and they all presented their own unique issues - some didn't like installing EDL.

I'm assuming that I also need to get the android (adb) stuff installed as well.

Once I've got the OS sorted am I correct that I need to get the BOOX into EDL mode by connecting the usb cable in EDL mode and then issue the adb reboot edl command ?

Thank you all so much in advance for your help.

[dcarvil]

Originally Posted by Grimbly1024

Hi All,

Sorry to appear stupid, but I got a bit lost with my first attempt and could do with a bit of help.

Firstly - what OS are you using ?

I tried using terminal on my mac and ended up with loads of issues with getting EDL to work.

I also tried various flavours of Linux and they all presented their own unique issues - some didn't like installing EDL.

I'm assuming that I also need to get the android (adb) stuff installed as well.

Once I've got the OS sorted am I correct that I need to get the BOOX into EDL mode by connecting the usb cable in EDL mode and then issue the adb reboot edl command ?

Thank you all so much in advance for your help.

I use Fedora and edl from https://github.com/bkerler/edl. That site also hosts a LiveDVD that has everything already packaged. If not using the LiveDVD, you'll need Android Platform Tools from https://developer.android.com/tools/...platform-tools.

Don't know what "connecting the usb cable in EDL mode" means, but yes, "adb reboot edl" is one way to get into edl mode.

I can't help with Mac.

[Grimbly1024]

Some progress - got Fedora up and running and have adb and edl running.

Got the Boox to respond to an edb reboot edl and was able to check which partition was active.

Then, the following.

sudo edl --loader=gocolor7_loader.bin r boot_a boot_a.img
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2025.
main - Using loader gocolor7_loader.bin ...
main - Waiting for the device
main - Device detected
main - Mode detected: firehose
DeviceClass - USBError(5, 'Input/Output Error')
DeviceClass - USBError(19, 'No such device (it may have been disconnected)')
DeviceClass - USBError(19, 'No such device (it may have been disconnected)')
DeviceClass - USBError(19, 'No such device (it may have been disconnected)')
Traceback (most recent call last):

any ideas ?

Thanks in advance.

I have a feeling it may be related to getting the device in EDL mode - is there a knack to this or just trial and error ?

[Renate]

If this is a Go Color (Gen 2) then you're using the wrong Firehose.
https://github.com/bkerler/Loaders/b...1d8a_fhprg.bin

[Grimbly1024]

Hi,

Thanks for the reply.

So, I was using that Bin file.

I've tried lots of ways to get the device to boot into EDL mode and nothing happens.

I'm using a decent four wire USB cable.

Is there a confirmed way to get the Boox into EDL mode ?

Thank you.

[dcarvil]

Originally Posted by Grimbly1024

Some progress - got Fedora up and running and have adb and edl running.

Got the Boox to respond to an edb reboot edl and was able to check which partition was active.

Then, the following.

sudo edl --loader=gocolor7_loader.bin r boot_a boot_a.img
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2025.
main - Using loader gocolor7_loader.bin ...
main - Waiting for the device
main - Device detected
main - Mode detected: firehose
DeviceClass - USBError(5, 'Input/Output Error')
DeviceClass - USBError(19, 'No such device (it may have been disconnected)')
DeviceClass - USBError(19, 'No such device (it may have been disconnected)')
DeviceClass - USBError(19, 'No such device (it may have been disconnected)')
Traceback (most recent call last):

any ideas ?

Thanks in advance.

I have a feeling it may be related to getting the device in EDL mode - is there a knack to this or just trial and error ?

Once edl fails, you have to reboot the Boox to clear the failure, then put it back in edl mode again.

It should not make a difference, but breaking "sudo edl --loader=gocolor7_loader.bin r boot_a boot_a.img" into separate commands is how I did it.

sudo su -
change to whatever directory you were using before
edl --loader=gocolor7_loader.bin
edl r boot_a boot_a.img
edl reset

If that doesn't work, there may be a clue in the logs (sudo dmesg).

[Serdar1st]

Originally Posted by doomgoatman

Kept trying, was able to recover without the go7-rec.img. Go 7 (B/W) is recovered.
Flashing original boot images back via EDL did not fix it.

What worked:

EDL cable to get back into 9008 mode (no software path from fastboot to EDL exists on this device)
Flashed FP4 ABL, frp_oemunlock, stock boot/recovery from decrypted 4.1.1 firmware, and Renate's misc-recovery via EDL
Erased devinfo partition (frp_oemunlock alone was not enough to unlock, devinfo wipe was required)
fastboot reboot recovery from the now-functional FP4 ABL
Recovery screen rendered on e-ink. Page turn buttons work as volume up/down. Selected "Factory data reset"
Device booted. Restored stock ABL/FRP/devinfo from backups via EDL.

For anyone else in this situation: buy an EDL cable. It's the only way back in once you're stuck in fastboot with the locked stock bootloader. I used bkerler's Python edl tool from WSL2 since Windows fastboot had persistent driver issues with this device.

What is fairphone abl