FP2: Blue screen at recovery mode



  • Hello everyone, I have troubles with installing Ubuntu on my new FP2.
    I tried the magic device tool as well as the CPT.
    Device detection in fast boot mode works, both tools can erase from/write data to the phone. The output says that boot- and recovery-images are transmitted successfully.
    But when booting into recovery mode or starting normaly, the only thing I get is a blue screen.
    If I try to continue the porting process (ignoring the hint that I need to see the Ubport recovery screen), the process continues but either the tar.xz files cannot be written or freezes after writing.
    Going back to the original Fairphone OS works.
    Any ideas?

    Best regards.



  • @kkr There is a bug with the bootloader on fairphone devices. Are you following this instructions?

    https://wiki.ubports.com/wiki/Installation-of-ubuntu-touch-on-fairphone/2b6cf75



  • Hi advocatux,
    thanks for answering. The procedure mentioned in your link is quite the same the magic-device-tool performs. The link to the tar.xz resource in the wiki-link is broken.
    Has anyone else different boot and recovery images?
    Best regards



  • @kkr oops I don't have an FP2 but I remember that bug, and that wiki page, but evidently I didn't check the link to dropbox. Sorry.

    Are you in the Telegram group? If the answer if no, I can ask there for you.

    Edit: I've posted your installation problem in the Telegram group. Hopes that helps.

    Edit 2: I've found this site Ubuntu 4 Fairphone 2 I don't know who they exactly are but maybe they can help you (I'll leave that link for information purpose but it seems that project has little to no activity).


  • Community

    @advocatux

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

    @kkr There is a bug with the bootloader on fairphone devices. Are you following this instructions?

    https://wiki.ubports.com/wiki/Installation-of-ubuntu-touch-on-fairphone/2b6cf75

    That page is really old, i'm not sure what stage of a recovery.img that is... Might not work.

    Maybe you could try using the UBports Installer. It's still in beta, but it usually works pretty well, since it has a lot of automatic detection built into it: https://github.com/ubports/ubports-installer/releases/tag/0.1.4-beta

    Should work on Linux, Windows and Mac.


  • Community

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

    Edit 2: I've found this site Ubuntu 4 Fairphone 2 I don't know who they exactly are but maybe they can help you (I'll leave that link for information purpose but it seems that project has little to no activity).

    That site is part of UBports as well, it should have been merged with ubports.com some time ago... Sorry for the confusion. I will ping the website people about this.



  • Thank you both of you. I tried the installer, it seems to me that it does the same as the mdt and the cpt. The come out is the same for me, a blue screen and when I continue pushing anyways it stops at file 3, 16% and freezes.
    @NeoTheThird Are there any other boot/recovery images I could try?


  • Community

    @kkr That's odd, we're looking into the issue. Is your phone new? Did it come with Android 6 installed? When did you receive it?



  • @NeoTheThird, Yes it is, just arrived. I think it did but I never actually started it to the end before trying to install ubuntu.


  • Community

    @kkr Ok, we're looking into it. It seems like it's just the fault of Android 6 and probably a new recovery, since i don't see anything about new hardware on FP's website...

    I'll ping you as soon as i know more.



  • @NeoTheThird Thank you very much!


  • Community

    @kkr Ok, i don't have a new FP2 (from the latest batch) here, so i just installed latest Android 6 and the UBports Installer managed to install it just fine from that.

    One thing you might also want to try: Before installation, fire up Android, open the settings, go to "About" and tap the build number 7 times. That will enable developer mode. Go to settings > developer options, enable USB debugging and bootloader unlocking. Then reboot your phone to Fastboot/Bootloader mode (hold volume down and power until the device reboots), connect it to your PC (i'm assuming you're running Linux of some sort?) and run sudo fastboot oem unlock from a terminal. Then reboot to system and try installing again using a different Micro-USB cable and a different USB socket on your computer to connect your phone to your PC.

    If that fails, we will need some logs and further information, but first try the above.


  • Community

    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


  • @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



  • @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.



  • @kkr good luck!



  • @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!


  • Community

    @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...



  • @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

    ~ # 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



  • 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


Log in to reply
 

Looks like your connection to UBports Forum was lost, please wait while we try to reconnect.