Not sure what you mean by the download server not being accessible.
Looks fine to me:
Or did I misunderstand something?
Oups sorry, it seems that the issue was on my side.
I get a message that the page is not accessible. But after clearing the cache of my browser the link is working again.
So my last question to @mmustermann is do you have any news from Android File Host regarding your issue to upload your last release?
Is there a chance to get your release of the 20.10.2022?
Thanks for your feedback
Sadly androidfilehost didn’t reply yet.
I’m currently compiling a new build for November. Will share that instead.
I’m planning to upload my new builds to https://ufile.io/ until my upload issue is resolved. However, they will only stay online for 30 days. Does anyone know a better alternative that hosts files longer, doesn’t restrict downloads and isn’t shady?
Thanks for your quick reply. I look forward to trying this new release.
Until now I’m very happy with your release of LOS19. 1
Maybe there is Mega. But I don’t know the details of the limitations for the free account. It’s not clear the amount of data transfer for the free account.
And I don’t know how this cloud is serious or not
New LOS 20 build for November is up. LOS 19.1 will follow soon.
Download
sha256sum lineage-20.0-20221110-UNOFFICIAL-FP4.zip recovery-20.0-20221110-UNOFFICIAL-FP4.img
7c9704725843126f1b22d44ebe5cb5d24ee86b43a104454a2ba48773addced1f lineage-20.0-20221110-UNOFFICIAL-FP4.zip
384019eeb57fd7d2ee58baefe36360ae727cf0adaf5b9260c760615d9cfba8d3 recovery-20.0-20221110-UNOFFICIAL-FP4.img
6 Likes
Hey, wanted to ask whether anyone has a clue why SafetyNet fails with CTS profile mismatch using microG on the LOS 20 November (or any other) build provided by @mmustermann above? I’ve spoofed the device ro.build.fingerprint, ro.build.version.security_patch, and model (i. e., enforced BASIC key attestation) properties through MagiskHidePropsConf. The fingerprint is derived from the latest Fairphone OS build for FP3 (Fairphone/FP3/FP3:11/8901.4.A.0017.3/gms-15368f27:user/release-keys), as is the security patch date (2022-10-05). I also have Universal SafetyNet Fix installed (although I assume this to be superfluous given my usage of MagiskHidePropsConf’s BASIC key attestation?).
How are you upgrading? I seem to be having issues each time I try. Gapps crashing and now bootloops. I’m sideloading the new .zip is this wrong?
Flashed the new recovery, then the new lineage update. Rebooted then reflashed MindTheGapps and it now works. Some apps still crash, not sure why or what they have in common.
I’ve been using mmustermann’s builds since he started to upload them, never had any issue.
Only thing is, I proceed with extra steps since for some reason los recovery refuses to flash any GApps version on my device.
Everytime there’s a new build I do the following:
- flash LOS recovery
- adb sideload los_build
- flash TWRP recovery
- wipe cache/dalvik
- adb sideload NikGApps
- flash patched_boot (for root)
- reboot
and it always goes flawlessly.
1 Like
Since I don’t use any SafetyNet related features myself, I probably won’t be able to help you. But why are you using the Fingerprint of FP3 for FP4? Could that be the problem?
I upgrade by rebooting into revovery and flashing the new zip via adb sideload. Never had issues. But I don’t use gapps either.
Currently compiling LOS 19.1. If no one complains this will be my last 19.1 build, since LOS 20 seems to be fully functional now.
1 Like
I’m using the same, as MagiskHidePropsConf doesn’t offer any FP4 verified signature for some unknown reason.
SafetyNet passes without issue on my device though. I’m not using MicroG since I’m rolling with GApps.
@anon62833029 did you enforce exclusion list in Magisk and add Play Store as well as Google framework to Magisk’s exclusion list ?
I remember having to:
- wipe all cache/data for those apps while being in airplane mode
- adding them to exclusion list in Magisk
- setting verifed FP3 signature with MagiskHidePropsConf
- rebooting
to get everything working.
Hey @zocker1999net, thank you for providing the images! Today I tried installing your ROMs, which fails for the most current. The last but one works fine. Also, the OTA-Update fails. Can you confirm that or is it particularly me?
EDIT: The device is stuck on the boot logo on most current version.
It must be an issue with MindTheGapps. Is there a way to switch Gapps? Might have to try NikGApps.
Last 19.1 build, if no one complains.
Download
sha256sum lineage-19.1-20221114-UNOFFICIAL-FP4.zip recovery-19.1-20221114-UNOFFICIAL-FP4.img
acaebe80fc1ed13f310637a599d2058bff9318769eacad0e2277c0e183331e2d lineage-19.1-20221114-UNOFFICIAL-FP4.zip
5d6c216dfae5ef26ea28406d4e0585cd2962b85ed7159f427bafb5cb2fcc73c4 recovery-19.1-20221114-UNOFFICIAL-FP4.img
4 Likes
It should be the same issue as for the official LOS FP3 release. Here’s my workaround to fix it.
Not sure about if it’s only related to MindTheGapps, but it’s a permission problem after the update. Maybe it’s caused of the security fixes inside the LOS update. But as stated above, I posted a workaround for it.
Personally if you want to switch to a new Gapps supplier, you should do a full wipe and a clean install. Otherwise you have old configs and scripts which can cause problems in the future.
1 Like
Thank you for the heads up. I relate to the microG version, which might well feature a similar issue as the GApps version. Reflashing of the microG unfortunately is no option, as I didn’t flash something additionally in the first place.
To clarify: The (then initial) boot also failed on fresh install.
All I wanted to say is that this isn’t only you which is affected. It seems like a bigger “problem” with the OTA-Update (FP3/FP4).
When GApps are installed during the use of your phone, you have to reinstall them via the recovery. It’s not a definition when you installed them, it’s a definition if you installed them. Then you have to overwrite the app settings with this reflash of the package.
Sorry for my question, but did you tried the workaround and did it solve the problem when using the new build?
1 Like
Thank you! Though this is reassuring, it’s sad to hear.
If I read your workaround correctly, the solution is based on reflashing GApps to get rid of the boot loop. As the ROM I used already includes microG, it isn’t flashed separately. Hence, re-flashing a “microG package” is not feasible to the extend I understand the matter.
Edit:
Typos II
I don’t know too much about microG, but maybe there is an “integration” package available somewhere so you can flash it?
Second option but I’m not quite sure if it’s possible during recovery mode is to remove the microG packages with following adb command:
adb shell pm clear PACKAGENAME
e.g. for Google Play Services
adb shell pm clear com.google.android.gms
to get rid of the microG variant of the Google Play Services. Don’t forget to do this for all of the microG-packages listed on their homepage or which was integrated in your ROM.
After that, download the newest packages from the homepage and reinstall the microG-packages with this command:
adb install -d DOWNLOADEDPACKAGE
e.g. for their newest Google Play Services variant it would be:
adb install -d com.google.android.gms-223616050.apk
DO NOT RESTART before you have reinstalled all the packages, otherwise some unpredictable errors could happen.
1 Like
Turns out my issues were permission related. Due to the number of messed up apps I did a factory reset. Still not sure how to prevent this from happening in the future.