FP2: Blue screen at recovery mode

NeoTheThird

If that still fails, please try to take a picture of that "blue screen", this sounds like a new phenomenon. Also, please try to reboot your device into recovery (If UBports recovery fails, reinstall android and use their recovery) by holding down volume up and power until the device reboots. Then connect it to your pc using a micro USB cable, open a terminal and type adb shell. That will open a phone terminal. Then, please run the following commands and copy their output. If it's long, paste it to paste.ubuntu.com.

cat fstab.qcom
df -h
cat /cache/system-image-upgrader.log
cat /cache/recovery/fail_log

advocatux

@bastos777 (I think is @Bastos here) has posted this link [*] in the Telegram group. It seems the problem is a new memory chip.

[*] https://forum.fairphone.com/t/flashing-lineageos-is-not-working/31584

kkr

@advocatux This seems to be exactly what I am experiencing as well. I tried the fixed recovery image that z3ntu posted there, booting into recovery with this image works on my phone (but no surprise - installing ubuntu using the lineageos recovery image does not work).

@NeoTheThird Yes I am using linux, I will try this.

advocatux

@kkr good luck!

kkr

@NeoTheThird: Just to let you know, I`m still working to get you the logs. Even with the original android recovery my system does not see the usb device (therefore the adb shell cannot find the device). But I did not give up yet...
@advocatux Thanks!

NeoTheThird

@kkr said in FP2: Blue screen at recovery mode:

Just to let you know, I`m still working to get you the logs.

No pressure

@kkr said in FP2: Blue screen at recovery mode:

Even with the original android recovery my system does not see the usb device (therefore the adb shell cannot find the device).

Did you unlock adb? Try opening the settings in android, go to "About" and tap the build number 7 times. That will enable developer mode. Go to settings > developer options and enable USB debugging. I'm not sure if that unlocks recovery as well, though...

kkr

@NeoTheThird Yes I did, this does not seem to imply recovery mode. I seems like abd must be enabled persistently in build.prop. I was able to get some logs this way but the content was not satisfying so I tried again to install ubuntu. After doing so, i pushed the current LineageOS recovery image (the one z3ntu published in https://forum.fairphone.com/t/flashing-lineageos-is-not-working/31584).

Finally, here are the logs
The logs you wanted:
1.) cat fstab.qcom:
There is no such file as fstab.qcom. Instead, there are fstab.ranchu and fstab.goldfish
They contain the following:

~ # cat fstab.goldfish
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mtdblock0 /system ext4 ro,barrier=1 wait
/dev/block/mtdblock1 /data ext4 noatime,nosuid,nodev,barrier=1,nomblk_io_submit wait,check
/dev/block/mtdblock2 /cache ext4 noatime,nosuid,nodev wait,check
/devices/platform/goldfish_mmc.0* auto auto defaults voldmanaged=sdcard:auto,noemulatedsd

2.) File system
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 923.1M 20.0K 923.1M 0% /dev
tmpfs 923.1M 16.0K 923.1M 0% /tmp
/dev/block/mmcblk0p15
629.5M 10.4M 619.1M 2% /cache
/dev/block/mmcblk0p20
25.5G 1.7G 22.5G 7% /data
/dev/block/mmcblk0p13
2.0G 32.0M 1.9G 2% /system
~ #

3.) cat /cache/system-image-upgrader.log
~ # cat /cache/system-image-upgrader.log
Starting image Upgrade pre
Processing the command file
Done upgrading: Sun Jan 4 23:02:13 GMT 1970
tune2fs 1.42.9 (28-Dec-2013)
Setting reserved blocks percentage to 5% (339916 blocks)

4.) cat /cache/recovery/fail_log
There is no fail log. See below what`s there:

/cache # ls -a
. lost+found system-image-upgrader.log
.. recovery test.log

kkr

Update: I tried to do the steps from the magic-device-tool manually. Using the lineageos recovery image I was at least able to push the .tar.xz files with ubuntu-device-flash to the cache folder. But ubuntu-device-flash does not continue after pushing the files without giving any comment. Adding -v does not change the output.
Does anyone have any ideas how to continue?
Regards

simon

kkr, I have the exact same problem as you. I can add to what you already said that the blue screen state lets you hear the sounds of ubuntu touch os (low battery)

kkr

@simon Well, then at least its not the fault of my phone! Your comment about the sound is interesting because mine does not produce any sounds at all.

Pierre

Hello,

I confirm this is not specific to your phone @kkr. I experience the same behavior as you do.
My FP2 is also brand new (part of the delayed batch).

Unlike you @simon, I cannot hear any sound when booting in recovery mode and seeing the blue screen.

I can provide additional logs if needed, but even though I am proficient with GNU/Linux system, my knowledge of android tools is quite basic. I'd appreciate if you could detail the commands I need to run in case more logs are required.
Regards.

jaapjansma

Hello,
I can confirm that I have the same problem on a brand new fairphone 2. I flashed ubuntu on it but it has a completly blue screen. I can see my phone when I connect it to my computer.

I also dont hear a sound.

I found this (https://code.fairphone.com/projects/fp-osos/user/fairphone-open-source-os-installation-instructions.html#method-2-using-fastboot) tutorial to install Fairphone Os again and I am trying to do that now.

Jaap

kkr

@NeoTheThird Neo, do you have any news or do you need anything else from us?
Best regards,
kkr

twinkybot

Is this now related to https://github.com/ubports/ubports-touch/issues/253?

Do I understand this correct, that if I even have an old FP2 with a new screen that it will show the blue screen?
If so damn. I could not use UT because my left side of the display was not working. So no menu
No I am waiting for my new Display and wanted to install UT now but then....

jaapjansma

@twinkybot yes that looks like the same problem to me.

oli.sax

This "Blue screen" issue was solved on devel channel Thank you to the team

(sources : UBPorts community update 13 at 19:25, Github issue and Kernel update )