Go 7 bootloop

[Renate]

So, you wrote your saved super.img back?

Here's manmod.zip
Unzip it

edl /w /psuper manmod.img

Then try to autoupdate

I'm not sure if this will work.
The updating status is in the metadata partition and that's probably a mess too.

Warning for others: This file has no applicability to your device. It is no fix.

[gleboss]

Got the same issue with 11% and no autolog.txt

Also I noticed that my device disconnects and connects back to PC while updating (~2mins after its stuck on 11%). I'm using sdcard to flash firware, so I keep my device connected to PC.

[Renate]

Try the same with the metadata partition.
Save a safe copy, then wipe it with /f

[gleboss]

Same issue..

> .\edl.exe /r /pmetadata meta.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 read meta.img... ok, reading 100% ok
> .\edl.exe /f /pmetadata
Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok
Requesting fill... ok, filling 100% ok
> .\edl.exe /z
Found EDL 9008, requesting reboot... ok
> .\adb.exe shell start autoupdate

...

Completed 270/2433 operations (11%)

[Renate]

Try this new manmod.img
No need to reflash super or anything.

If this doesn't work, we can try flipping slots.
But I'll have to write a utility for that.
You need to pull the GPT.

edl /r /s0 /c34 gpt.img

Zip and post.

[gleboss]

Update process fails with the new manmod.img.

I checked logs (autolog_wo_meta.txt) and decided to flash meta.img back:

> .\edl.exe /w /pmetadata .\meta.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 meta.img... ok, writing 100% ok

Then I've got another error log - autolog_w_meta.txt

[Renate]

Ok, I *think* that I got this correct.
This swaps the slots so you'll be on _a
You should try with everything back to as it was.
You can try various experiments that you already did to see if something is different.
Make sure that you have the custom recovery on _a and _b

edl /w /s0 /c34 main.img
edl /x /s-33 /c33 backup.img

Make sure that you have the whole big raw backup in case of major screwup.

[gleboss]

Thanks a lot for helping me!

Here is what I did step by step:

> .\edl.exe /w /s0 /c0 .\big64gfile.img
> .\edl.exe /w /s0 /c34 ..\both\main.img
> .\edl.exe /w /s-33 /c33 ..\both\backup.img
> .\edl.exe /r /psuper super.img
> .\edl.exe /z
> .\adb.exe shell start autoupdate

Here I've got 11% issue again, next:

> .\edl.exe /f /psuper
> .\edl.exe /z
> .\adb.exe shell start autoupdate

Update process failed with - autolog_f_psuper.txt.

Next steps:

> .\edl.exe /w /psuper super.img
> .\edl.exe /f /pmetadata
> .\edl.exe /z
> .\adb.exe shell start autoupdate

Got the same issue with 11%. Next:

> .\edl.exe /f /psuper
> .\edl.exe /z
> .\adb.exe shell start autoupdate

So - no super, no metadata - autolog_f_super_meta.txt (looks the same as previous log).

Finally:

> .\edl.exe /w /psuper manmod.img
> .\edl.exe /z
> .\adb.exe shell start autoupdate

Got into 11%...

[Renate]

Did you try rebooting to the regular system?
That is restart after clearing misc with /f.
I presume that you flashed misc-recovery in the last post.
Also, keep an eye when you go back to EDL if it switched on you.
You started on _b with all the _a showing inactive.
Then you switched to _a with all the _b showing inactive.

You see that all with edl /g

And you're sure that 11% never terminates?
I said that it should take 5, maybe 10 minutes.
But you have just left it for a long time too?

[gleboss]

Did you try rebooting to the regular system?
That is restart after clearing misc with /f.
I presume that you flashed misc-recovery in the last post.

Sorry, I didn't get you. I tried rebooting to the regular system, but I don't even see loading screen, only Boox main screen flickering.
I tried clearing misc:

> .\edl.exe /f /pmisc

And nothing changed.

Also, keep an eye when you go back to EDL if it switched on you.
You started on _b with all the _a showing inactive.
Then you switched to _a with all the _b showing inactive.

You see that all with edl /g

Yeah, I can see _a paritions as active and _b as inactive.

And you're sure that 11% never terminates?
I said that it should take 5, maybe 10 minutes.
But you have just left it for a long time too?

More than 30 minutes.

Also, I flashed back my previously saved full backup after switching slotsm, smth like that:

> .\edl.exe /w /s0 /c0 .\big64gfile.img
> .\edl.exe /w /s0 /c34 ..\both\main.img
> .\edl.exe /w /s-33 /c33 ..\both\backup.img

// do some other stuff

> .\edl.exe /w /s0 /c0 .\big64gfile.img
> .\edl.exe /w /s0 /c34 ..\both\main.img
> .\edl.exe /w /s-33 /c33 ..\both\backup.img

// do some other staff

Did I mess it up?

I don't fully understand the idea of slots. Is it some sort of replication?

[Renate]

Originally Posted by gleboss

I don't fully understand the idea of slots.

That's alright, nobody does.

When A/B first came up it was two complete copies of the core bits of the operating system.
Simple, easy. Something breaks, just switch to the other slot.

Then they came up with "virtual A/B". One slot is real, the other slot is just a list of differences to the other slot.
As you can see that makes things a lot more complicated.

The ext4 partition /metadata keeps track of all that stuff.

I forget, did you already try with the stock recovery and adb sideload?
Was your device already unlocked? Had you been running Magisk?

I'm still trying to figure out why it says:

Logical partition metadata has invalid geometry magic signature

Because the man.img out of the super that you gave me has the normal two copies of geometry with the correct magic.
I see this problem on other devices but no indication of what it's all about.

You can try wiping out the manifest of super.

edl /f /psuper /c2048

[gleboss]

I forget, did you already try with the stock recovery and adb sideload?

Yep, but I did it with update.upx, not the decypted one and it failed with "signature verification failed"

Was your device already unlocked? Had you been running Magisk?

Nope, it was brand new device with only KoReader installed. I did nothing to it for about 3 months until it occasionaly got bricked.

You can try wiping out the manifest of super

No luck unfortunately - autolog_f_man_super.txt.

Then I tried to wipe meta as well - autolog_f_man_super_meta.txt.