Go 7 attempted root and now stuck on boox logo - Page 3

Renate · 03-25-2026, 12:38 PM

Actually, that wasn't too bad.
Do we have any brave volunteers to try unlocking using fastboot?

doomgoatman · 03-25-2026, 01:37 PM

I'll give it a shot. Since I've got the EDL cable on the way I should be able to recover that way if stuff goes bad.

Renate · 03-25-2026, 01:42 PM

Quote:

Originally Posted by doomgoatman

I'll give it a shot. Since I've got the EDL cable on the way I should be able to recover that way if stuff goes bad.

Yes, but you'll need EDL to flash abl.

doomgoatman · 03-25-2026, 01:43 PM

oh duh, ok well I'm willing to give it a shot after my cable arrives then lol

Renate · 03-25-2026, 01:50 PM

You could get the scissors out and make an EDL cable.

jd27 · Yesterday, 01:30 AM

Quote:

Originally Posted by Renate

What did you flash to recovery?

I flashed your 57 mb go7-rec.img

Quote:

Originally Posted by Renate

Actually, that wasn't too bad.
Do we have any brave volunteers to try unlocking using fastboot?

I can do this - I have an EDL cable, and I have fastboot working?

Thanks,

JD

Renate · Yesterday, 03:45 AM

Quote:

Originally Posted by jd27

I flashed your 57 mb go7-rec.img

Well, then is it working?
You should be able to restore the stock system with that.

The unlocking should not have anything to do with putting in custom recovery with EDL.

jd27 · Yesterday, 05:31 AM

Quote:

Originally Posted by Renate

Well, then is it working?
You should be able to restore the stock system with that.

The unlocking should not have anything to do with putting in custom recovery with EDL.

I see. That makes sense.

How do I restore the stock system? After recovery I can access fastboot (and EDL), but cannot access adb?

I have seen suggestions to run 'adb sideload update.zip', but I don't know what the next steps are if I don't have adb.

Thanks, JD

Renate · Yesterday, 05:40 AM

You flashed my recovery.
Did you go to my recovery?
Did you flash misc-recovery?
Did you get ADB?
Did you get autoupdate?
Did you have the decrypted upx (zip)?

I never said/tried/cared about adb sideload.

jd27 · Yesterday, 05:57 AM

Quote:

Originally Posted by Renate

You flashed my recovery.
Did you go to my recovery?
Did you flash misc-recovery?
Did you get ADB?
Did you get autoupdate?
Did you have the decrypted upx (zip)?

I never said/tried/cared about adb sideload.

What is supposed to happen when I flash your recovery (and misc-recovery)? After flashing recovery then misc-recovery, then edl /z: the Boox logo flashes, but then goes back to the Boox logo. I don't see anything else, and I cannot get ADB.

After I flash your recovery, how do I "go to your recovery"?

When running custom recoveries on other devices (phones), I have seen that it goes to a menu on the device, but I've never been able to get any such menu on my boox - only ever the boox logo.

Thanks, JD

Renate · Yesterday, 06:15 AM

There are no menus, but there should be no logo, only a white screen and ADB.

jd27 · Yesterday, 06:20 AM

No white screen, and no adb

I only see the boox logo flash and then go back to the boox logo. I hear 1 'bong' for a disconnect, and 1 'bong' for a reconnection.

Would you have any other suggestions?

Renate · Yesterday, 06:46 AM

Yeah, find out what it's reconnecting as.
If things are totally screwed it's probably going to fastboot.
But you tell me.

jd27 · Yesterday, 06:49 AM

I've just checked and yes, it is reconnecting as fastboot every time I plug it in.

Code:

$ fastboot devices
eebba4d	 fastboot

I thought it going to fastboot mean't that your recovery worked - clearly this isn't the case.

Renate · Yesterday, 08:53 AM

There are many partitions that I know little about which could break things.
There's rpm, tz, cmlib, cmnlib64, uefi stuff...
These partitions are not normally included even in full updates.
Your best source is the full backup you made on the day you unwrapped your new device.

Of course it could be my custom recovery too.
Stock recovery is in the update, flash that, flash misc-recovery, see if it gets the stock menu.

Yesterday, 06:49 AM	#44
jd27 Member Posts: 15 Karma: 10 Join Date: Feb 2026 Location: Australia Device: go7	I've just checked and yes, it is reconnecting as fastboot every time I plug it in. Code: $ fastboot devices eebba4d fastboot I thought it going to fastboot mean't that your recovery worked - clearly this isn't the case.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Trying to root a Boox Note 2, stuck at fastboot boot image.img. Could use some help.	soypherpunk	Onyx Boox	10	12-11-2025 01:30 PM
Aura H2O 1st edition having wifi troubleshoot and after firmware update loading logo stuck	Kobo4Life	Kobo Developer's Corner	16	02-13-2024 02:43 PM
Stuck with a shop logo as wallpaper.	Wyre	Kobo Reader	7	07-06-2017 11:57 AM
Pocketbook Ultra 650 stuck at boot logo	Dandan7932	PocketBook	6	10-02-2015 03:40 AM
360 Stuck at startup logo with endless loading	darkforce	PocketBook	0	07-02-2011 02:42 PM

03-25-2026, 12:38 PM	#31
Renate Onyx-maniac Posts: 4,373 Karma: 20878213 Join Date: Feb 2012 Location: Germany Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Actually, that wasn't too bad. Do we have any brave volunteers to try unlocking using fastboot?

03-25-2026, 01:37 PM	#32
doomgoatman Junior Member Posts: 7 Karma: 10 Join Date: Mar 2026 Device: Boox Go 7 BW	I'll give it a shot. Since I've got the EDL cable on the way I should be able to recover that way if stuff goes bad.

03-25-2026, 01:43 PM	#34
doomgoatman Junior Member Posts: 7 Karma: 10 Join Date: Mar 2026 Device: Boox Go 7 BW	oh duh, ok well I'm willing to give it a shot after my cable arrives then lol

03-25-2026, 01:50 PM	#35
Renate Onyx-maniac Posts: 4,373 Karma: 20878213 Join Date: Feb 2012 Location: Germany Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	You could get the scissors out and make an EDL cable.

Yesterday, 05:40 AM	#39
Renate Onyx-maniac Posts: 4,373 Karma: 20878213 Join Date: Feb 2012 Location: Germany Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	You flashed my recovery. Did you go to my recovery? Did you flash misc-recovery? Did you get ADB? Did you get autoupdate? Did you have the decrypted upx (zip)? I never said/tried/cared about adb sideload.

Yesterday, 06:15 AM	#41
Renate Onyx-maniac Posts: 4,373 Karma: 20878213 Join Date: Feb 2012 Location: Germany Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	There are no menus, but there should be no logo, only a white screen and ADB.

Yesterday, 06:20 AM	#42
jd27 Member Posts: 15 Karma: 10 Join Date: Feb 2026 Location: Australia Device: go7	No white screen, and no adb I only see the boox logo flash and then go back to the boox logo. I hear 1 'bong' for a disconnect, and 1 'bong' for a reconnection. Would you have any other suggestions?

Yesterday, 06:46 AM	#43
Renate Onyx-maniac Posts: 4,373 Karma: 20878213 Join Date: Feb 2012 Location: Germany Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Yeah, find out what it's reconnecting as. If things are totally screwed it's probably going to fastboot. But you tell me.

Yesterday, 08:53 AM	#45
Renate Onyx-maniac Posts: 4,373 Karma: 20878213 Join Date: Feb 2012 Location: Germany Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	There are many partitions that I know little about which could break things. There's rpm, tz, cmlib, cmnlib64, uefi stuff... These partitions are not normally included even in full updates. Your best source is the full backup you made on the day you unwrapped your new device. Of course it could be my custom recovery too. Stock recovery is in the update, flash that, flash misc-recovery, see if it gets the stock menu.