* build rolled back , if you have any issues with it , let me know below !

alonsoj636 said:

sorry , but i only test clean installations because i switch from roms very often

you must follow this steps to flash gapps on a clean installation :
> Format Data
> Flash ROM
> Reboot to Recovery
> Flash GApps Package
> Reboot

never flash gapps after system boot... this can cause problems

That's the correct steps that i always use... yes! you can use NikGApps Core which is lighter (80 MB) here is the link

Click to expand...

Reinstalled without issue using the last version

alonsoj636 said:

* build rolled back , if you have any issues with it , let me know below !

I've got the lineage-19.1-20220716-UNOFFICIAL-mojito rom version installed. can you give me a bit more details as to why you've reverted back to x0714 version? what should I be aware of?

Zirila said:

I've got the lineage-19.1-20220716-UNOFFICIAL-mojito rom version installed. can you give me a bit more details as to why you've reverted back to x0714 version? what should I be aware of?

about play protect certification not available after some hours of usage , if you are using the rom without GMS then don't worry but i suggest you to update once i release a new build probably tomorrow. Also will release LineageOS 18.1 as well

Update... 19/07/2022
* LineageOS 18.1 added back (Signed Build)
* LineageOS 19.1 added back (Signed Build)

alonsoj636 said:

Update... 19/07/2022
* LineageOS 18.1 added back (Signed Build)
* LineageOS 19.1 added back (Signed Build)

I tried upgrading to this 19.1 build now but it failed. After upgrading lineageos recovery showing up telling me it can't read android system anymore. I tried reflashing this build several times now always with the same result. I always have to manually switch back to the backup slot of the previous install to get it running again. does anybody else have these problems too? maybe there is something corrupt on the rom/partition sizes when upgrading? I'm just guessing.
the lineageos recovery even suggests to factory reset if the problem consists, but I was not willing to reinstall everything from scratch, so for now I switched back to previous version.

Zirila said:

I tried upgrading to this 19.1 build now but it failed. After upgrading lineageos recovery showing up telling me it can't read android system anymore. I tried reflashing this build several times now always with the same result. I always have to manually switch back to the backup slot of the previous install to get it running again. does anybody else have these problems too? maybe there is something corrupt on the rom/partition sizes when upgrading? I'm just guessing.
the lineageos recovery even suggests to factory reset if the problem consists, but I was not willing to reinstall everything from scratch, so for now I switched back to previous version.

uff sorry about that... i only tested the clean installation because i was on another rom.
i reverted some changes but nothing related to partitions... i guess clean flash is needed sometimes

try using ofox beta... if you have any error code there share it

alonsoj636 said:

uff sorry about that... i only tested the clean installation because i was on another rom.
i reverted some changes but nothing related to partitions... i guess clean flash is needed sometimes

try using ofox beta... if you have any error code there share it

the situation is a bit unclear.. I have 19th july lineagos rom sitting on slot b. I upgrade through lineageos recovery as I did before.
one time upon flashing I got error code 3 in los-recovery afterwards - unsucessful flash. but I guess this was due to my PC went into screensaver mode while flashing.
the second time flashing it the same way i got error code 0, successful flash. But then it got stuck when trying to boot up. it successfully switches to slot a, but system on a seems to be corrupt then.

I can try flashing july 14th version of the rom, maybe it works. if it doesnt, then maybe something is corrupt with slot a system partition.

but I don't have backups right now to risk a reset or clean install...

tried rolling back to july 14th version.. the same problem as before: seems like something corrupted slot a.. Idk what.. maybe the july 19th version? if it says data is corrupt, it maybe just means some system settings that are stored in the data partition doesn't fit for the new rom version?
slot b is working fine if I revert back to it with the previous version.
seems like I have to wait until I have the time to backup everything and make a clean flash with MIUI reinstall inbetween...

Yes , you should flash stock miui rom and then comeback to custom rom once you backup everything. Probably the partition table is messed up and need a clean miui installation.

it happened with other users too including me (but with other error code on twrp/ofox)

Once you're ready with everything, install the rom with ofox beta (format data > flash rom > flash ofox zip > reboot to recovery > flash gapps if you want > reboot to system)

yeah.. but meh, that kinda sucks.. I'd rather try and find what the source of the problem is than reinstalling and reconfiguring all app and system stuff again..

I wonder if I could fix system slot a, just by applying:
Clearing existing QTI Dynamic partition sizes... fastboot resize-logical-partition system_a 4096 fastboot resize-logical-partition system_ext_a 4096 fastboot resize-logical-partition product_a 4096 fastboot resize-logical-partition vendor_a 4096

..and then applying the update from slot b.

but anyway.. I'm not going to try without backing everything up.. and I have not that much time right now.

So I had to bite the bullet.. backed up everything and reflashed MIUI before trying a new install.

After having flashed LineageOS from July 19th it's booting up fine in a clean state, so the ROM is working if flashed from fresh and clean state.

Just to give it a try and to spare some time, I tried reflashing a /data partition backup from the July 16th version that I had installed right before. Usually it should work and I don't need to install and configure everything manually by hand..

However, after flashing /data and trying to boot up, I get the same error as in the screenshot posted above: "Can't load Android System. Your data may be corrupt (...)"

Now that's interesting.
Because that means there was actually NO problem with partition tables or the like.
It's rather an indicator that there is an incompatibility issue with system-settings stored in /data when upgrading lineageOS from lineage-19.1-20220716-UNOFFICIAL-mojito to lineage-19.1-20220719-UNOFFICIAL-mojito.
Something (services, filesystem protocol, kernel stuff, etc.) must have been changed that caused incompatibility. Something that requires adjusted configs from /data settings or it won't boot anymore.

@alonsoj636 maybe you have an idea what it could be?

also a thought:
in these builds you tried changing something and then reverting back to it:
lineage-19.1-20220714-UNOFFICIAL-mojito <- original state
lineage-19.1-20220716-UNOFFICIAL-mojito <- something changed
lineage-19.1-20220719-UNOFFICIAL-mojito <- reverted back to original state

maybe the lineage-19.1-20220716-UNOFFICIAL-mojito introduced new or different services or protocols that changed system settings that are then incompatible when flashing back to a version with original state (14th or 19th)?

yes , i'm aware of that... probably the build fingerprint , signing , rootdir or other misc changes i did was the culprit of breaking /data

I'll check everything and switch permanently to LineageOS to make the required tests

alonsoj636 said:

yes , i'm aware of that... probably the build fingerprint , signing , rootdir or other misc changes i did was the culprit of breaking /data

I'll check everything and switch permanently to LineageOS to make the required tests

indeed, must have been something like fingerprints or signatures. but would be good to know what exactly it was and how to prevent or mitigate it. if you know the details, you can probably prevent it and still use other roms inbetween.
but admittedly, I'm no expert on that.. if you ever find out, let me know, I'm eager to learn the details.

in the meanwhile, I've setup a new phone principally. unfortunately there are more and more apps where no backup helps, because they're using androids own vault, which always gets lost after a complete wipe (apps like Signal, covid app, etc..) it's a mess to setup them all again.