Help me rooting the Go Color 7

[SleepWithMachine]

sure, can i do this via edl ? can you pass me the full command line pls

[Renate]

Nope. Don't use any of those Firehose loaders.

Tell me when you're ready to try a new one.

[Renate]

Ok, let's see some action here!
The GoCo7 should use the standard procedures as anything else.
The GoCo7 and the Go103 use the same processor, SM6225 (and the same Firehose loader).
The GoCo7 is eMMC and the Go103 is UFS.
The Firehose loader for both is (temporarily) https://github.com/bkerler/Loaders/issues/97

First, enable Developer options, enable USB debugging, install Windows ADB drivers.

adb reboot edl

Go to http://www.temblast.com/edl.htm, read, download Zadig, download edl.exe, install Zadig WinUSB

edl /lsm6225.bin
edl /g                    -- just for fun and a sanity check
edl /r /pboot_a boot.img
edl /z

That's enough for now.

[borosilikat]

Hello Renate and SleepWithMachine!

Thank you for making this thread and all the work.

I successfully rooted my Boox Go Color 7 today using the instructions here, I was able to flash a magisk patched boot.img using edl.

Thanks guys!

[Renate]

Hey, you Go users! Please try/use the Firehose loader here (new version):
https://github.com/bkerler/Loaders/issues/97

[hotrungnhan]

Originally Posted by Renate

Ok, let's see some action here!
The GoCo7 should use the standard procedures as anything else.
The GoCo7 and the Go103 use the same processor, SM6225 (and the same Firehose loader).
The GoCo7 is eMMC and the Go103 is UFS.
The Firehose loader for both is (temporarily) https://github.com/bkerler/Loaders/issues/97

First, enable Developer options, enable USB debugging, install Windows ADB drivers.

adb reboot edl

Go to http://www.temblast.com/edl.htm, read, download Zadig, download edl.exe, install Zadig WinUSB

edl /lsm6225.bin
edl /g                    -- just for fun and a sanity check
edl /r /pboot_a boot.img
edl /z

That's enough for now.

Hello Renate, i’m really appreciate on yours contribution to all of boox user.

I got a problem in leaf 3c, the chinese versions of Go7Color.

After using fastboot to flash some firwmare.
I think i made some mistake.
1. delete-logical-partition system_b
2. fail flash on system_a
3. Current slot is a, while the previous bootable is b

Currently: it only boot loop to fastboot (not fastbootd), non of flash command work, the set slot not work as well.
I just order an edl cable just in case.
I need yours advise, please help if possible

[Renate]

Yes, recent abl's have had some fastboot commands ripped out of them.

There might be EDL test points inside, but the OEM has been making them more obscure.
It's also a question of how easily the device opens up.

You can get to EDL by killing xbl, but that could be risky.

An EDL cable would probably work, but that's up to the OEM too.
You can make an EDL easily enough, but timing and wakkliy connections can make life more difficult.

[hotrungnhan]

Originally Posted by Renate

Yes, recent abl's have had some fastboot commands ripped out of them.

There might be EDL test points inside, but the OEM has been making them more obscure.
It's also a question of how easily the device opens up.

You can get to EDL by killing xbl, but that could be risky.

An EDL cable would probably work, but that's up to the OEM too.
You can make an EDL easily enough, but timing and wakkliy connections can make life more difficult.

I have the EDL cable now, Renate. what should i do to access EDL ?

[Renate]

Originally Posted by hotrungnhan

I have the EDL cable now, Renate. what should i do to access EDL ?

Disconnect the device from USB
Power down the device
Connect the EDL cable to desktop
Push and hold the EDL cable button
Plug the EDL cable to the device
Wait two seconds
Release the EDL cable button

[hotrungnhan]

Originally Posted by Renate

Disconnect the device from USB
Power down the device
Connect the EDL cable to desktop
Push and hold the EDL cable button
Plug the EDL cable to the device
Wait two seconds
Release the EDL cable button

I've try.
The devices status now is
* led indicator in the power button is on pinky-purple (bootloader is blue)
* no fastboot, no adb, no usb found (not even an ?), edl tools can't find it as well ?

is it really bad ?

[Renate]

We've got a Firehose loader for this so it can always be rescued.
It's just a question of how much trouble.

I can guarantee that if it were here I could get it working within half an hour.

There are EDL test points inside.
If anybody pops one of these puppies open I'd like some good photos.

[lcchy]

Hey I just wanted to say thanks very much to you @Renate!

I managed to root my GoColor 7 thanks to the edl loader that you wrote, and I wouldn't have been ready to use my device without root, so thanks a lot!

To those who are struggling to understand the process like me before, here is a little explanation:

# Rooting works by patching the boot.img firmware partition with magisk
# To obtain (and flash) the boot.img we extract it directly from the device using EDL mode and a specific loader
# The custom loader can be found here: https://github.com/bkerler/Loaders/issues/97

# Extract boot.img via edl
edl --loader=sm6225.bin r boot_a boot.img

# Patch the extracted boot.img with magisk, the usual way

# Flash the patched image
edl --loader=sm6225.bin w boot_a $HOME/Downloads/tmp_boox/magisk_patched-boot.img

I also have a question, if anyone can help: when flashing I actually flash to both slots A and B, as just A does not seem to be enough.
I don't have great experience with android, is this how it supposed to be or do I miss a step in the process ?


PS: the commands I gave above may vary depending on your OS etc, its more to describe the process.

[dcarvil]

Originally Posted by lcchy

I also have a question, if anyone can help: when flashing I actually flash to both slots A and B, as just A does not seem to be enough.

If flashing to only slot A does not work, that probably means A is not the active slot. The active slot can alternate between A and B, depending on how you update.

You can determine which slot is active with this adb command:

adb shell getprop ro.boot.slot_suffix

It will return _a or _b.

There is probably a way to get the active slot with edl, but I don't know how offhand.

[Renate]

Originally Posted by dcarvil

There is probably a way to get the active slot with edl, but I don't know how offhand.

I'm not sure how other EDL clients report this stuff, but mine makes it pretty clear:

edl /g

 #  Name                   Start       Count  Type
──  ────────────────  ──────────  ──────────  ────────────────────
 1  xbl_a                 131072        7168  Inactive
 2  xbl_b                 138240        7168  Bootloader
 3  xbl_config_a          262144         256  Inactive
 4  xbl_config_b          262400         256  Boot config
 5  tz_a                  393216        8192  Inactive
 6  tz_b                  524288        8192  TrustZone
...

So this shows me on the B slot.