I have managed to fix AD!

Note: The root cause: the default user nemo has changed to defaultuser.
Therefore this change is only needed on new installs.
If you OTA to release 3.4.0.24 (not available yet) you probably won't need to do this, as the nemo will be kept as default user.

So, to make it work, you need to edit two files:

• /opt/alien/system/script/alien_start_guard.sh
  change:
  Code:

  SYSTEM_USER_NAME=nemo

  to:
  Code:

  SYSTEM_USER_NAME=defaultuser

• /opt/alien/system/script/platform_envsetup.sh
  everywhere in this file change: nemo
  to: defaultuser

After these changes AD should start as normal.

Awesome! I'll give this a shot tomorrow, thanks for your amazing work as always

Worked great, excellent work! 👍

I am glad it works. Enjoy.

If somebody interested I have created a boot logo.
To install you need to flash the edp17-hammerhead_sfos-bootimage.zip in recovery.

When my phone boots it looks like:


When it is on the charger:


If you would like to go back to (slightly) original, just flash this: hammerhead_no-padlock-bootimage.zip. (In this one, there is no padlock image at the bottom.)

Enjoy.

Followed the instructions exactly but can't get past the bootlogo, the modified CM12.1 won't boot either, any ideas?

A few questions:[LIST][*]What instructions exactly have you followed? Instaling SFOS on the Nexus 5, upgrading an SFOS version to another or changing the boot logo?[*]How do you mean "modified CM12.1"?[*]Multirom or single rom environment are you using?[*]Are you using kexec kernel? (Recommend to read this topic.)[*]What Android version was it on the device before you started?[*]Sili question, is that device a Nexus 5 or a 5X?
[/LIS]

Hi, I'm having the same issue in a single rom environment, without kexec kernel, it was on stock before I started and it's definitely a Nexus 5

This instruction has helped somebody else, so you too can try.

I think the problem is the kernel.

I would go back to Android (6.0) and start everything from scratch again. (Root, multirom, then install secondary roms.)

This is how I set up and use my Nexus 5:
(I mentioned Ubuntu Touch here because I started with that first, then I moved to Sailfish OS.)

1. unlock boot loader
- adb reboot bootloader
- fastboot oem unlock
2. root (Info)
CF-Auto-Root
3. MultiRom with Ubuntu Touch repo (Info and Info about multirom):
- install 1-MultiROMMgr_withUT.apk (multirom with UbuntuTouch repo) with adb (Info):
- adb install 1-MultiROMMgr_withUT.apk
4. reboot recovery and install:
- kernel: kernel_kexec_hammerhead_601.zip
- multirom recovery: multirom-20160207-v33-hammerhead.zip
5. reboot android, start MultiRom and install Ubuntu Touch
6. SailFish OS (Info):
- boot into recovery: Advanced -> MultiROM -> Add ROM
- Choose "SailfishOS" as ROM type.
- Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.

I have uploaded all files to my storage and made them available for you. So you don't need to hunt them together from the websites I linked in as Info at each step. However, I recommend to read them to get an overview.

I usually use one of these twrps. (With the newer one you can install Ubuntu Touch but cannot flash a zip on a secondary from. With the older you can flash a zip on a secondary from, but cannot install UT.): TWRP_multirom_hammerhead_20150630 or TWRP_multirom_hammerhead_20160210

Thanks for all the great work!

I seem to have the same problem as LinuxLounge (and probably as iKevinES and monkeyisland who posted in the CM13 thread). I cannot boot my Nexus 5 with the 20160704-UNOFFICIAL 12.1 image linked here, it gets stuck on the boot logo.

I found another image which does work. However, when flashing the SFOS 3.4 image on top of that, it hangs on the boot logo again. Interestingly, when connected by USB on boot, my Ubuntu machine sees a phone device with the cryptic name "init debug in real rootfs", which it cannot access: "Unable to open MTP device “001,065”".

Could the issue be that I am not using multirom?