Go 7 attempted root and now stuck on boox logo

[jd27]

Hi,

I had purchased a new Go 7, and attempted to root the device using this guide noting that someone on reddit stated that the same guide worked for the Go 7. My device now unfortunately does not boot - it shows the BOOX logo but nothing else happens.

I have bought a EDL cable, and can still access EDL but not adb or fastboot.

Could someone provide any advice on (a) how I can get back a functioning device, and (b) what I should do to be able to root this device?

What I did to get into a not working state:

• Bought a brand new device, did not connect to wifi.
• Turned USB debug mode on
• Downloaded edl utility from here (https://www.temblast.com/edl.htm), and using this loader for Go 7 (https://www.temblast.com/ref/onyxldr.htm). Note for subsequent commands, I didn't use /u as I read that Go 7 does not use UFS.

.\platform-tools\adb.exe reboot edl
.\edl.exe /lgo7-2.bin
.\edl.exe /g
.\edl.exe /r /pboot_a go7_boota_unrooted.img
.\edl.exe /r /pboot_b go7_bootb_unrooted.img
.\edl.exe /z
.\platform-tools\adb.exe install magisk.apk 
(I then used magisk to patch boota_unrooted.img and bootb_unrooted.img)

.\platform-tools\adb.exe pull
.\platform-tools\adb.exe reboot edl
.\edl.exe /w /pboot_a magisk_patched-30600_vn0oa_boota.img
.\edl.exe /w /pboot_b magisk_patched-30600_8rklr_bootb
.\edl.exe /z

At this point the device restarted and is stuck on the BOOX logo. I can access EDL, but not adb devices or fastboot.

What I did to try to recover (Method 1 - did not work):
Using an EDL cable:

C:\Users\Em\Desktop\boox-root> .\edl.exe /lgo7-2.bin
Found EDL 9008, handshaking... version 2
HWID: 0013f0e100000000 (x3), JTAG: 0013f0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending go7-2.bin 100% ok, starting... ok, waiting for Firehose... ok

.\edl.exe /w /pboot_a go7_boota_unrooted.img
.\edl.exe /w /pboot_b go7_bootb_unrooted.img
.\edl.exe /z

Same as above, device is stuck on BOOX logo.

What I did to try to recover (Method 2 - also did not work):

• Downloaded the latest firmware for Go 7: http://en-data.onyx-international.cn/api/firmware/update?where={"buildNumber":0,"buildType":"user"," deviceMAC":"","lang":"en_US","model":"Go7","submod el":"","fingerprint":""}
  
• The JSON response stated this was Version 4.1.1:

  "fingerprint":"Onyx/Go7/Go7:11/2025-11-10_16-08_4.1.1-rel_1110_d8cf44fd7/6191:user/release-keys","buildType":"user","buildNumber":6191,"buildDisplayId":"2025-11-10_16-08_4.1.1-rel_1110_d8cf44fd7","

• Ran decryptBooxUpdateUpx (https://github.com/Hagb/decryptBooxUpdateUpx) to convert update.upx to update.zip. Extracted to get payload.bin
• Ran payload-dumper-go (https://github.com/ssut/payload-dumper-go) to get the following files: abl.img, boot.img , dtbo.img , modem.img, odm.img, product.img , recovery.img, system.img, system_ext.img, vbmeta.img, vbmeta_system.img, vendor.img, xbl.img
  
• Based on what I read for other android devices, I used edl to rewrite as:
  
  1. boot_a / boot_b: boot.img
  2. vbmeta_a / vbmeta_b: vbmeta.img
  3. vbmeta_system_a / vbmeta_system_b: vbmeta_system.img
  4. dtbo_a / dtbo_b: dtbo.img
  5. abl_a / abl_b: abl.img
  6. xbl_a / xbl_b: xbl.img
  7. recovery_a / recovery_b: recovery.img
  8. modem_a / modem_b: modem.img

I'm stuck here because guides tell me to also write 'super.img', but I don't have this file.

Are there any suggestions? I'm grateful for any advice people can offer, and thanks in advance.

[darkwill]

YMMV - Look at the Air 5c thread for details, and try switching A and B when you write the unrooted images back one at a time.

https://www.mobileread.com/forums/sh...3&postcount=18

[Renate]

Try this. You already have the decrypted update.zip.

edl /l~~~~~~ <-- your loader
edl /w /pmisc misc-recovery.img
edl /z
adb sideload update.zip

The file ends in .prc, just rename it .img (not that it matters).

[jd27]

Thanks, I can get into edl mode and can write misc-recovery.img, but then do not know how to get adb to work.

PS C:\Users\Em\Desktop\boox-root> .\edl.exe /lgo7-2.bin
Found EDL 9008, handshaking... version 2
HWID: 0013f0e100000000 (x3), JTAG: 0013f0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending go7-2.bin 100% ok, starting... ok, waiting for Firehose... ok
PS C:\Users\Em\Desktop\boox-root> .\edl.exe /w /pmisc .\misc-recovery.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 misc-recovery.img... ok, writing 100% ok
PS C:\Users\Em\Desktop\boox-root> .\edl.exe /z
Found EDL 9008, requesting reboot... ok

The screen then flashes black and comes back to the Boox logo.
I then run:

PS C:\Users\Em\Desktop\boox-root> .\platform-tools\adb.exe sideload .\update-4.1.1.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found

I've tried also holding down the power button + page up + page down after edl /z, and other combinations, but I still can't seem to get into recovery / or able to use adb.

[jd27]

@darkwill: Thank you for your info - I have also tried switching A and B a few times but no luck.

@Renate:

I have writing the custom recovery (~57 mb file) to both recovery_a and recovery_b partitions, then writing misc-recovery.img to misc partition (to try to get it to boot to recovery on next boot).

PS C:\Users\Em\Desktop\boox-root> .\edl.exe /lgo7-2.bin
Found EDL 9008, handshaking... version 2
HWID: 0013f0e100000000 (x3), JTAG: 0013f0e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending go7-2.bin 100% ok, starting... ok, waiting for Firehose... ok
PS C:\Users\Em\Desktop\boox-root> .\edl.exe /w /precovery_a go7-rec.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 go7-rec.img... ok, writing 100% ok
PS C:\Users\Em\Desktop\boox-root> .\edl.exe /w /precovery_b go7-rec.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 go7-rec.img... ok, writing 100% ok
PS C:\Users\Em\Desktop\boox-root> .\edl.exe /w /pmisc misc-recovery.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 misc-recovery.img... ok, writing 100% ok

PS C:\Users\Em\Desktop\boox-root> .\edl.exe /z
Found EDL 9008, requesting reboot... ok
PS C:\Users\Em\Desktop\boox-root> .\platform-tools\adb.exe devices
List of devices attached

after edl.exe /z, I've tried (a) just letting it reboot, (b) holding down power + volume up (or volume down, or both). The screen flashes and returns to the BOOX logo, but every time the next step (adb devices) shows nothing, and adb sideload doesn't work.

[Renate]

Does fastboot (i.e. bootloader) work?
You can select that with /misc
Flash misc-bootloader.img to /misc

[jd27]

Hi Renate,

I'm able to flash to /misc, then edl /z. The screen then flashes and the boox logo comes back. fastboot devices shows nothing though.

Just so I am clear, is there anything I need to do after edl /z to get into fastboot?

[Renate]

But is this a case of the Windows fastboot device driver not loaded?
Does anything pop up when it goes to the Boox logo?
You can pull the USB and see if it "bongs" when you plug it back in.
You might have a 05c6/900e kernel crash.

If you have the update you can use a Python dumper to get xbl and abl.
You can flash them to both slots.

Try recovery, try bootloader.

[jd27]

Originally Posted by Renate

But is this a case of the Windows fastboot device driver not loaded?

I think I have verified fastboot works - I can put my phone in fastboot mode and see it on fastboot devices.

Originally Posted by Renate

Does anything pop up when it goes to the Boox logo?

Nothing pops up, it just flashes black then the BOOX logo comes back (this is after edl /z).

Originally Posted by Renate

You can pull the USB and see if it "bongs" when you plug it back in.

It bongs (connect) when I go into EDL mode. When I run edl /z, it first bongs (disconnect), and again then after the screen flashes (connect). Once it restarts, if I pull the usb cable it bongs when I unplug (disconnect), and bongs when I replug (connect).

Originally Posted by Renate

You might have a 05c6/900e kernel crash.

If you have the update you can use a Python dumper to get xbl and abl.
You can flash them to both slots.
Try recovery, try bootloader.

I have just tried flashing the misc-bootloader.prc above to /misc, and the xbl.img to /xbl_a and xbl_b, and abl.img to /abl_a and /abl_b.

Same thing happens after edl /z: I can hear 1 bong for disconnect, screen flashes and goes back to BOOX logo, I can hear 1 bong for connect, but fastboot devices shows nothing.

Any other suggestions are definitely welcome

[Renate]

It could be that you just don't have the Windows device driver for fastboot loaded.

Did you try flashing the stock recovery? Does that work?

I have about a dozen Onyx custom recoveries but I can never keep track of problems because a lot of people never report back.

Try using my UsbLog.exe (in the Windows section of my sig).
But it will only show devices for which there are Windows drivers loaded.

[jd27]

Originally Posted by Renate

It could be that you just don't have the Windows device driver for fastboot loaded.

Did you try flashing the stock recovery? Does that work?

I have about a dozen Onyx custom recoveries but I can never keep track of problems because a lot of people never report back.

Try using my UsbLog.exe (in the Windows section of my sig).
But it will only show devices for which there are Windows drivers loaded.

Using UsbLog.exe, when I go into EDL mode it shows:

Ins, Dev, VID: 05c6, PID: 9008, Location/ID: 5&26c13e2d&0&9, Name: QUSB_BULK_CID:041B_SN:355FFEF2

I have then reflashed the recovery.img from the 'stock' (decrypted update), and reflashed misc-bootloader. When I run edl /z, USBLog shows:

Del, Dev, VID: 05c6, PID: 9008, Location/ID: 5&26c13e2d&0&9, Name: QUSB_BULK_CID:041B_SN:355FFEF2

Ins, Dev, VID: 18d1, PID: d00d, Location/ID: eebba4d, Name: Android

But cannot access fastboot.

[Renate]

Well, it says you got fastboot, "dood".

Apparently it has a Windows driver loaded too.

So, either it has the wrong Interface GUID or your fastboot executable is bad.

PM me your fastboot.exe and I'll patch it for you.

[jd27]

Hi Renate,

Thanks for your message - please find attached fastboot.exe. I cannot see how to send you an attachment via PM.

JD