I went through the whole process again, got exactly the same results. I wonder if the problem is with the encryption of the userdata partition - when I booted into TWRP the first few times it asked me to unlock the encryption (using the password I set when I booted up the stock OS), but after I flashed the system image (and ran fastboot erase userdata ) it no longer did. Does the FP3 use metadata encryption? That might explain our invalid block sizes wouldn’t it?
Just one short question: Will there be any chance to use a customrom on the FP3 and pass the safetynet-check? (or will it always be that way that -> if custom -> sefetynet-check fail -> some apps won’t work?)
At least it will be the case that even if you somewhen somehow can get this to work, Google can break it at any time again, and most probably will.
If you consider trying this, think about your dependencies on affected Apps beforehand carefully.
This would be in the “Nice to have” category, not in “Reliable solution”.
Hm, I thought that it will be that way. Unfortunantly I am using some apps, which rely on a passed SafetyNet check. So no custom rom for me. But:
I had got LinageOS on my FP3 worked like a charm, but the SafetyNet check ruined it. So I went back to stock.
Keep up the good work.
Hi! Does this means, that ones i got root on my FP3 i can’t unroot that and bring backt to Stock ROM and should Be never able to Update Stock ROM OTA?
Or is it possible to do that?
Thanks towards your answer
For anyone else getting the error along these lines:
Invalid erase-block-size 512: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
I found that this was not a problem with the phone but with the fastboot program - I switched from Ubuntu (18.04) to Windows 10 and I found I could run fastboot -w with no problem. The problem seems to have been that I installed the Android SDK platform tools through apt-get rather than downloading them from developer.android.com. Hope that helps someone.
6 Likes
TL;DR: RTFM 
.
To be fair … quoting from /e/'s install instructions …
“Requirements
[…]
2. Make sure your computer has working adb and fastboot . Setup instructions can be found here.”
… where here is a page explicitly telling you to download adb and fastboot directly from Google.
One issue is Linux distributions offering seemingly outdated or otherwise unfit adb and fastboot commands.
Another issue is interested users not following written instructions telling them to “make sure” something works, and how exactly to achieve that if in doubt.
No act of moderation here will fix either issue.
Perhaps /e/'s install instructions could use some bold, signal red lettering in the right place instead.
1 Like
Sorry for the noise, post deleted.
This was neither necessary nor my intention. Your post was not noise.
Anyway, I created a topic over at the /e/ forum, let’s see whether something can be done to make it clearer the instructions are really to be followed to avoid trouble.
2 Likes
I’m sorry if there’s a running Lineage thread somewhere, but I couldn’t find the current status of Lineage for FP3.
I saw on the official page that there were a few nightlies for FP2, but is there an active group of people unofficially curating an FP3 version? Or is it more advisable to install /e/ at the moment and customize from there?
I could have sworn there was a thread here but I can’t find it anymore.
EDIT: thanks @Ingo!! I had only searched in Discuss and Help, but forgot about Development. 
In the new firmware (v0120 at the time of writing), there is a vendor.img. Can’t I just flash it on the vendor partition with fastboot instead of reflashing everything?
1 Like
I just joined the forum and wanted to send a big Thank You 
for writing this post. That was massively helpful for me as a new Android user, and without this (and the TWRP port) I probably wouldn’t have been able to run Resurrection Remix for the last few months 
2 Likes
I don’t know if you are still having an issue with fastboot -w but it is probably because your mke2fs tool is out of date like me. I fixed it by installing the platform tools strait from Google rather than the Debian repos like they recommend in the LineageOS guide here: https://wiki.lineageos.org/adb_fastboot_guide.html
1 Like
I’ve added a custom GSI build of /e/ Android 10 to the list in the first post.
Have not checked it out yet, it’s absolutely fresh. It’s provided by a heavy contributor of custom /e/ builds.
1 Like
Hi all,
I just posted an issue regarding receiving texts on my FP3. I am not sure if it is related to the GSI ROM I have installed so I thought to post it here to confirm or rule this out. AOSP GSI: Can't receive texts (but sometimes can)
Someone found a way to get the Android 10 based GSIs running: https://github.com/phhusson/treble_experimentations/issues/1146#issuecomment-687783797
Tried it myself with LOS 17.1 GSI just now and it seems to be working fine so far.
Edit: now that Android 10 has arrived for the FP3 I wonder if it would help to use the new vendor partition instead of copying a few libraries from another phone…
3 Likes
@pigpig: phhusson has added a hardware overlay for the FP3 on my pull request. So with the next GSI builds by phhusson or AndyCGYan installation should become easier. You may want to replace steps 3.-6. simply by fastboot --disable-verity flash vbmeta_a vbmeta.img && fastboot --disable-verity flash vbmeta_b vbmeta.img - there would be no further need to enter twrp…
BTW, on the most recent 0045 firmware LineageOS 17.1 works smoothly - at least my own build which is based on the same sources like AndyCGYan’s but includes a quick & dirty OTA option.
3 Likes
Nice to hear that !
I may haven’t notice but this is a wiki post, that means everybody can edit it
Is this the only solution to get LOS17.1 on the FP3 or will there be an official version for the FP3?