I can safety guess that your FP2 is shiny new? Which FP OS version it came with?
I may have a theory, but as it involves some sensitive, non-public Fairphone info (yet), I’ll contact the person who trusted me that info and ask for permission to share it in the public. It has to be with hardware and would explain your situation, if I’m not wrong.
Yes, I am sure, because my delivery was delayed due to the display shortage with Fairphone2 models. This device was delivered with the most recent FairphoneOS FP2-gms-17.07.6.1
EDIT: I will tried out and most interestingly the outcome is even worse. The device rumbles on turning on but the screen stays dark the whole time. No startup splash, nothing. I will return into fastboot mode and reflash the recent Android 6.0 FairphoneOS.
EDIT2: I forgot to wipe beforehand. Stay tuned…
EDIT3: Wiping is not possible due to the fact that I can not get into recovery or use adb while the phone is detected. So this is all I can tell now.
Ok, fine, that fact should prove my theory correct. I’ll return with the info later when I get the permission to share, or some FP staff will reply here with it. Sorry for the delay involved, I don’t want to leak anything to the detriment of Fairphone.
Oops. It seems like my theory does not correspond with your issue after all because the information I had was about a development process not deployed yet. So… I’m out of ideas now,
Well, same here. I am quite sure I tried everything in order.
But just to be sure I will retell my try here, maybe someone notices an error.
I tried flashing the TWRP with OTA Fix as it can be found in this thread via fastboot. This attempt failed, as the screen turns blue when booting into recovery, but the phone is recognized via MTP.
I tried flashing a TWRP without this Fix, directly downloaded at TWRP Project website. Same result.
I learned that Open Source FairphoneOS is delivered with TWRP preinstalled. Its Version is older (3.0.2-0 instead of 3.1.1-0 from point 2), but works like a charm. So I flashed the Open Source FairphoneOS, which works.
I tried flashing LineageOS for FP2 as described in this thread using the TWRP I flashed at point 3. Trying to boot the flashed LineageOS also ends up with that blue screen from points 1&2.
So I finally decided to stay with OpenSource FairphoneOS because I am in control of my device then and can make a living without Googles “Services”. But I would like LineageOS 14.1 to run on my device, because I started to like it on my tablet. Maybe someday, someone has an idea about this. Maybe I forgot to make a vital step while flashing, I have no idea…
It doesn’t seems like that. As you don’t have issues with official software, FP Support won’t give you further support, naturally.
Better ask known community developers to help you debug that. Could you @z3ntu look at this? I’m not sure how to get logs or dmesg or something to debug low-level thingies.
I did reset beforehand, thanks. Forgot to mention that
Unfortunately when having flashed the recent LineageOS version I cannot access the device via adb because lack of authorization.
Is there a way to authorize my laptop prior to booting the (newly flashed) system?
EDIT: I know I can add my adb pubkey to the FP2 /data partition, but in order to boot a new system /data should be wiped right?
If you enter the following command from the recovery, it will disable the adb key authorization: sed -i 's/ro.adb.secure=1/ro.adb.secure=0/' /system/build.prop
Okay, I really do not know what exactly is happening, but I am not able to flash the recent lineageOS version with the TWRP delivered with the FPOpenOS version anymore. So no testing and no logcat, sadly. I read in the thread regarding the LineageOS port, that there are new blobs now coming with sibon-17.07.6? Maybe the now blobs can help with the issue?
EDIT: AFAIK recent lineageOS builds are shipped with blobs from sibon-17.04.8 so maybe an update of the blobs could help?
Thanks for mentioning.
I am actively following the process of development.
Tried the recent LineageOS build from 03.08.17 and the testbuild from 05.08.17.
The first is targeted to blobs 17.04.8 like the ones before. As expected the blue screen is there also. No adb to log something.
The second is also targeted to 17.04.8 but does not flash properly. Flashing stops after data is written and TWRP does not end the flashing process as normally expected. Trying to reboot causes FP2 to bootloop.
I am ashamed I cannot contribute more as of today, because exams are awaiting me coming wednesday. After that I will try to build LineageOS for FP2 myself.
This is exactly what @Roboe meant I think! (It also makes sense, despite that info )
I hope this can be fixed soon
I will stay close to the Porting threads of the forum^^
you’re not alone. I just received my FP2 yesterday, also a delayed delivery. Software version was FP2-gms-17.07.6.1 Today I tried to flash a recent TWRP (3.1.1-0) from the official TWRP site. When trying to enter the recovery mode with this, I get a blue screen too. Also, as you mentioned, the TWRP included in the fp2-sibon release works on my phone. After reading this thread I tried the newest available LineageOS build (lineage-14.1-20170808-UNOFFICIAL-FP2.zip) with the same result: a blue screen.
So I guess we have to wait for the new LCD driver to be integrated into TWRP and LineageOS.
)