I only missunderstood the 30 seconds warning… always choosed reboot in bootloader to flash again or try something different. But i only had to confirm the warning with power button. stupid shit 
I now got lineageos working, had to do a factory reset after flashing… next i’ll try booting /e/
1 Like
It is a bit weird that current-slot: a is before the flashing lines…
If the errors you’re talking about are Invalid sparse file format at header magic, it doesn’t matter. It is because these images aren’t sparse files but it works.
Please referre to Troubleshooting Tips > To get a slot-success=Yes Post #1
If you see the 30secs warnings, you have to confirm booting with the power button.
ok it works… schame on me, i forget to confirm on the 30sec warning xD
edit: It is a bit weird that current-slot: a is before the flashing lines…
wrong copy paste 
1 Like
“a tip for the first post.”
if fastboot -w fail try fastboot erase userdata
still have to do a factory reset vie recovery afterwards
Maybe “uninstalling” the unnecessary priv apps instead of disabling them could be the better way. In the Thread Google apps keep reinstalling someone mentioned that it would be better to use
adb shell pm uninstall -k --user 0 com.qualcomm.qti.qms.service.telemtry
adb shell pm uninstall -k --user 0 com.qualcomm.qti.qms.service.connectionsecurity
adb shell pm uninstall -k --user 0 com.qualcomm.qti.optinoverlay
adb shell pm uninstall -k --user 0 com.orange.update
adb shell pm uninstall -k --user 0 com.orange.aura.oobe
instead of
adb shell pm disable-user --user 0 com.qualcomm.qti.qms.service.telemetry
adb shell pm disable-user --user 0 com.qualcomm.qti.qms.service.connectionsecurity
adb shell pm disable-user --user 0 com.qualcomm.qti.optinoverlay
adb shell pm disable-user --user 0 com.orange.update
adb shell pm disable-user --user 0 com.orange.aura.oobe
for preventing uncontrolled reactivating of those apps. But maybe this is a stock rom problem only.
By the way: it should be ok to remove com.qualcomm.qti.qms.service.trustzoneaccess as well:
adb shell pm disable-user --user 0 com.qualcomm.qti.qms.service.trustzoneaccess
You should not disable com.qualcomm.timeservice.
works, good guide, thanks for the work @all here.
feel mutch better not longer to be under the surveillance of google & partner, and to be root again
1 Like
I have added adb shell pm disable-user --user 0 com.qualcomm.qti.qms.service.trustzoneaccess and something about pm uninstall to the wiki.
The advantage of disable-user is in case of any problem, it can be reactivate on the phone. And I’ve not seen any reactivation for the moment.
Work your back-camera in LOS 16? In mine only the front-camera is working and the button to switch between Front and back is missing :-/
Does twrp factory reset work for you guys?
ArrowOS won’t boot after a factory reset until I make fastboot -w.
I’m also working on a little installable zip that enables the navbar: https://github.com/basxto/fp3_gsi_patcher
That should make it a bit quicker when you switch between roms regularly.
Tested that zip so far with: ArrowOS, phusson AOSP 9 vanilla nosu, lineage 16.0-20191017
1 Like
You should probably create and submit an overlay instead, which deals with much more aspects than just a missing navbar (e.g. brightness curve, battery usage, ambient display - if there are any issues with them), and will be built into any PHH-based GSI built after its approval.
Refer to this guide and existing overlays at PHH.
Also, hi to the FP community, and thanks for using my (ultimately PHH’s) work. Wish actual (non-GSI) development comes for you guys soon.
6 Likes
Thank you, I will look into it.
And it seems we don’t need magisk to run GSIs.
I’m currently running LOS 16 on 101 kernel without magisk and twrp.
I just did adb disable-verity and adb reboot "dm-verity enforcing" again and again. I don’t know if both are needed or if the rom boots up as soon as the second message disappears.
It also runs on c4y0z’s kernel (hello adb reboot ebl) with twrp without magisk, but it takes ages to boot up, the display has wrong resolution and won’t turn on once it’s gone off, like the stock image did originally.
1 Like
karloff, can you tell which GSI ROM you successfully flashed?
thx
If you are able to run GSI from stock rom with adb disable-verity we should update the wiki 
I’ve built an overlay https://github.com/basxto/vendor_hardware_overlay/releases/tag/v0.1
The navbar works now, haven’t tested it much though.
Just do in twrp: adb push build/treble-overlay-fairphone-fp3.apk /system/overlay/
4 Likes
Nice !
I tried it with LOS 17 (and without magisk ) but it didn’t work
Neither does AOSP10.
And resurrection remix still does not leave the boot animation.
And Havoc still does not boot at all.
current Arrow OS release for Android 9
https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/
the system_arm64_ab.zip file.
I try’d AOSP for Android 9 before, but after flashing every click crash back to screen, so i’d use Arrow OS.
There a few minor issues, but nothing what count in daily use.
PHHusson’s AOSP 9?
Which issues do you have with ArrowOS? I’m currently running that too
Hi,
First post on this forum. I bought a FP3 two weeks ago and successfully installed LineageOS 16 GSI thanks to this thead
I’ve been struggling a bit trying (and finally succeeding) to install & configure microG.
It seems my setup is fine now
Thanks to all of you involved into this documentation.
3 Likes