Go 7 bootloop

[Renate]

Sorry, you jumped the gun, I found another error.
Just a sec...

[Renate]

Sorry, something is still wrong....

[gleboss]

11%...

[Renate]

Yeah, yeah, there's still something wrong.

[Renate]

Is lpunpack still showing 131072 for odm.img?
Could you run that again?
I'm getting that also with 7zip, not particularly a reputable source on LP, but certainly another opinion.

Your lpunpack in #43 is screwed up.
It's not paying attention to the logical block size.
It's using 512 when the geometry clearly uses 4096.
Where did you get that from, some Debian thing?

There were two rounds of screw-ups on my part:
1) a typo
2) a mismatch on starting point because of that 1 MB vs 8 MB thing.

But the last time should have been correct.

I don't know how you "got ADB" before.
Were you talking to the stock system, but without the Android subsystem running?
Or stock recovery? Or custom recovery.

As I said before, zip up the /metadata and post it.

[gleboss]

Is lpunpack still showing 131072 for odm.img?

Yep

Where did you get that from, some Debian thing?

Here - https://github.com/Rprop/aosp15_partition_tools

I don't know how you "got ADB" before.

Stock recovery - "Apply update from ADB" option (only sideload was available)

As I said before, zip up the /metadata and post it.

Sure

[Renate]

Okay, flash the unzipped to metadata.
If you are unclear if super was modified somehow with an failed update, flash the latest manmod and the five.

[gleboss]

Got new error

[Renate]

Thanks. I think that the problem is resolved.
My tools were working fine, my brain wasn't.
Flash meta_clean, flash manmod, flash:

edl /w /psuper manmod.img
edl /w /psuper /s2048 odm.img
edl /w /psuper /s4096 product.img
edl /w /psuper /s1236368 system.img
edl /w /psuper /s7295944 system_ext.img
edl /w /psuper /s8239792 vendor.img

(You know you can just copy/paste that whole block in one fell swoop?)

It might even boot normally (if you wipe misc).

[gleboss]

Stuck on 11% again. What's interesting - it's loading into recovery immediately after turning on.
I tried to flash stock recovery and now I see error loading android system.

[Renate]

What happens if you flash all again, clear misc and reboot without trying to update?

[gleboss]

It loads into recovery automatically again (I guess corrupted data again)

[Renate]

Well, if you're data isn't valuable you can try the factory reset.

When the device boots it looks to see if there is any unmerged updates.
If there are it tries to merge them.
I don't think that you mentioned that there was any delay in starting all the previous times.
It appears that by getting rid of the snapshots in metadata that at least that seems to have improved.
There could be corruptions/problems in /data preventing it from starting the normal system.
I still don't understand this 11% business.
If it was well written it would finish (with errors) and not stall no matter what the problem was.

[gleboss]

Tried factory reset from default recovery - it wiped /data and /metadata. Now I can finally see the default loading screen, but it hangs and constantly reboots.
Tried adb sideload again from default recovery - same issue with verification error.

[Renate]

And autoupdate? Still 11%

This is a normal Go7, right?