Go 7 attempted root and now stuck on boox logo

[Renate]

I think that flashing stuff from Fairphone is a bad idea.

Over and out.

[doomgoatman]

@Serdar1st happy to have been able to help!

@Renate not trying to be combative, just curious why? It was the only way I could figure out that allowed me to recover my device after I made a series of mistakes. I’ve been reading on it ever since I got it back and haven’t noticed anything wrong.

[ardy]

Originally Posted by Eamonnator

i was following the guide on buduroiu.com and after patching with magisk and pushing the patched image to boot slot a it is now stuck on the boox logo and i have now idea how to recover/fix it

At this point if the writer of that blog is following these forums they should put up a big red banner on top of that post saying applying their steps will cause the device to brick so more people don't brick their devices like you and I did.

As for the device, it is perfectly recoverable by following the steps in this guide by doomgoatman, EXCEPT the only difference is that as an owner of Go Color 7 Gen 2, you need to go to

http://en-data.onyx-international.cn/api/firmware/update?where={"buildNumber":0,"buildType":"user","deviceMAC":"","lang":"en_US","model":"GoColor7_2","submodel":"","fingerprint":""}

to download the upx file, and you are going to need an EDL cable to be able to perform the initial EDL commands. If you need help, just let me know, good luck!

[nam43t]

Thank god for this place! I was also following buduroiu's guide, and bricked my Go 7 Color 2nd Gen from the point of flashing the magisk-patched boot img to the device.

I have now ordered an EDL cable and hope to follow doomgoatman and ardy's instruction to try to at the minimum get it booted again.

I've just sent an email to the person running that site to let them know that they may wish to add a warning/disclaimer and have linked to the posts here of people bricking their devices after following the page.

[buduroiu]

Originally Posted by ardy

At this point if the writer of that blog is following these forums they should put up a big red banner on top of that post saying applying their steps will cause the device to brick so more people don't brick their devices like you and I did.

As for the device, it is perfectly recoverable by following the steps in this guide by doomgoatman, EXCEPT the only difference is that as an owner of Go Color 7 Gen 2, you need to go to

http://en-data.onyx-international.cn/api/firmware/update?where={"buildNumber":0,"buildType":"user","deviceMAC":"","lang":"en_US","model":"GoColor7_2","submodel":"","fingerprint":""}

to download the upx file, and you are going to need an EDL cable to be able to perform the initial EDL commands. If you need help, just let me know, good luck!

Hi, author here. Thanks nam43t for notifying me about the issues in my blog. I've been following the thread and trying to understand which part of the rooting process fails and causes people's devices to become bricked, and which process should be followed instead.

Has the rooting process changed significantly since the publication of my blog post?

Cheers

[ardy]

Originally Posted by buduroiu

Hi, author here. Thanks nam43t for notifying me about the issues in my blog. I've been following the thread and trying to understand which part of the rooting process fails and causes people's devices to become bricked, and which process should be followed instead.

Has the rooting process changed significantly since the publication of my blog post?

Cheers

Hello! I apologize if my previous posts had a confrontational tone, my only plea was to prevent more people from bricking their devices. My primary theory is that, at a certain point after your blogpost, there was a firmware update that locked the bootlodader by default, but the post proceeds with the assumption that the bootloader is unlocked. EDL can still modify the underlying file system as usual but cannot prevent ABL from rejecting the modified bootlodader and halt the booting process, so following the tutorial directly causes ABL to trip up instantly. The spirit of the current fix is to replace the ABL with a donor bootloader image extracted from a fairphone where it is unlocked by default.

[nam43t]

Okay, I've just tried following the procedure after receiving an EDL cable.

Everything seemed to have written to the Go just fine

I got to the point of doing:

fastboot reboot recovery
Rebooting into recovery                            OKAY [  0.009s]
Finished. Total time: 0.209s

But it only shows the Boox logo on the e-ink screen, even after waiting several minutes.

Actually, it seems I am unable to turn off the device now. It just loops the white/black then back to boox logo. Before I was able to turn it off by holding the power button for about 20 seconds until the power LED flashed twice

For note:
- I didn't see an A15 build for FP4, so I assumed the latest A14 was fine. I extracted the abl.img from the zip file and used that. (IMG-e-3.7.1-a14-20260414608789-official-FP4.zip)
- I used the update.upx from ardy's onyx link

[nam43t]

Ahh I got to recovery!! (and figured out how to power off the device in the previous state - just keep holding the power button and ignore the fact the screen doesn't go blank!)

I read through the thread again - my boot was also set to slot b, same as ardy!

I did this:

fastboot --set-active=a
Setting current slot to 'a'                        OKAY [  0.011s]
Finished. Total time: 0.013s

fastboot reboot recovery
Rebooting into recovery                            OKAY [  0.008s]
Finished. Total time: 0.108s

It's factory resetting now.

[nam43t]

Argh. After doing the wipe/factory reset, it just reboots a couple of times and then stays on the boox logo forever.

I tried flashing all of the bootloader pieces again, but still the same.

[ardy]

Originally Posted by nam43t

Argh. After doing the wipe/factory reset, it just reboots a couple of times and then stays on the boox logo forever.

I tried flashing all of the bootloader pieces again, but still the same.

I remember having gotten stuck at this position but I don't exactly remember how I ended up exiting it, but if you could check if you're stuck at fastboot or the recovery by sending the adb commands and checking the responses (it should be either one of them, most likely fastboot) I could try to recommend a more precise strategy. I think it should be a combination of both of the following conditions:

* misc partition being freshly flashed
* the correct partition being active for the next reboot

it might be caused by the bootloader image flashing flipping the partition to the other one, and the misc file only executes correctly if a certain partition is active. this is my fringe theory and I'm completely counting this off my head instead of remembering the events of that day or basing it on any technical expertise (I don't have any) so correct me if I'm wrong (renate is the absolute expert of all of this complexity)

because i remember wiggling with it for a long time and trying a lot of different stuff at this position. in the end it was changing the active partition that got me out; but because i didn't keep track of what i was doing and introduced a lot of side effects i don't know the consequences of my previous commands to provide an exact prescription.

[ardy]

Originally Posted by ardy

I remember having gotten stuck at this position but I don't exactly remember how I ended up exiting it, but if you could check if you're stuck at fastboot or the recovery by sending the adb commands and checking the responses (it should be either one of them, most likely fastboot) I could try to recommend a more precise strategy. I think it should be a combination of both of the following conditions:

* misc partition being freshly flashed
* the correct partition being active for the next reboot

it might be caused by the bootloader image flashing flipping the partition to the other one, and the misc file only executes correctly if a certain partition is active. this is my fringe theory and I'm completely counting this off my head instead of remembering the events of that day or basing it on any technical expertise (I don't have any) so correct me if I'm wrong (renate is the absolute expert of all of this complexity)

because i remember wiggling with it for a long time and trying a lot of different stuff at this position. in the end it was changing the active partition that got me out; but because i didn't keep track of what i was doing and introduced a lot of side effects i don't know the consequences of my previous commands to provide an exact prescription.

Edit: you already stated that you finished the recovery stage. I'm sorry, I misread the post and tried to provide suggestions for the misc image instead. I'll try to remember what happened that day and if I got stuck here as well, because i can't remember clearly.

[ardy]

Originally Posted by nam43t

Argh. After doing the wipe/factory reset, it just reboots a couple of times and then stays on the boox logo forever.

I tried flashing all of the bootloader pieces again, but still the same.

Have you been able to get past this? I'm sorry I couldn't offer you a definitive suggestion but if you have any other observations from recovery and fastboot commands etc. I'd try to do my best.