That’s after using LOS, going to recovery, and doing reset there before reformatting user data. Although, this reformatting is the same as factory reset in recovery. So, I don’t have much hope…
Probably telnet debug will be needed to check up where it breaks on boot.
Looks like the same thing with factory reset: black screen after SFOS logo and no led.
I’ll try telnet, but not sure I will get to that today.
With internet search being as it is today I did not get a lot of results. I did find this: Getting In - Sailfish OS Hardware Adaptation Development Kit
Somehow it looks as if the telnet doesn’t finish setting up on the phone, all I’m getting is:
[1819616.833220] usb 1-6: new high-speed USB device number 105 using xhci_hcd
[1819616.960298] usb 1-6: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 5.10
[1819616.960318] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1819616.960329] usb 1-6: Product: init-debug in real rootfs
[1819616.960337] usb 1-6: Manufacturer: Mer Boat Loader
[1819616.960344] usb 1-6: SerialNumber: Mer
[1819616.964640] rndis_host 1-6:1.0 eth0: register 'rndis_host' at usb-0000:00:14.0-6, RNDIS device, 9e:da:0d:fb:53:e6
[1819616.974919] rndis_host 1-6:1.0 enp0s20f0u6: renamed from eth0
And even with lsusb -v | grep iSerial it keeps stuck at “Mer”:
$ lsusb -v | grep iSerial
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
iSerial 1 0000:00:14.0
iSerial 1 2326LZ50MH88
Couldn't open device, some information will be missing
iSerial 0
Couldn't open device, some information will be missing
iSerial 0
iSerial 3 Mer
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
iSerial 1 0000:00:14.0
iSerial 1 0000:04:00.0
iSerial 1 0000:04:00.0
I’m not getting anything like Mer Debug telnet on port 23 on rndis0 192.168.2.15 - also running udhcpd and telnetting to the IPv6 address reported by ip addr does nothing even with trying different ports like 22, 23, 24, 2323.
Also no IPv4 ever shows up.
I looked into history at my laptop. As root, I had to run on laptop:
ip addr add 192.168.2.14/24 dev enp0s20f0u4
Just replace here with enp0s20f0u6 - looks like that is your device.
After that, telnet 192.168.2.15 2323 should work.
PS: fingers crossed
@aerique , just in case, I have added older .62 release to Github releases (under 0.2). You can try to test with that as well. I am not sure whether I used that image to flash my device.
And with stock, did you had the latest stock ROM installed? Although, I guess wrong stock would have had issues with LOS too.
Telnet remained unresponsive for me.
The .62 image also gave me the same issue of a black screen after the SFOS logo.
Maybe it’s my phone? I’ve reflashed to LOS now and will keep that running for a while.
Morning! Pity. As they are the same in terms of results on your phone, I’ll remove .62.
You haven’t replied regarding stock version. Did you update to the last available version before unlocking? Or flashed the last version after unlocking?
I updated to the latest version before unlocking.
(But I did not write down which version that was.)
Then its somewhat a mystery with what is going on with your install.
Hello! I have a problem with my Xperia 5 IV (XQ-CQ72 Taiwan) where it will boot fine on lineageos however as soon as I try to flash sailfish os using the guide on the wiki, it gets stuck on the sony logo. I left it for about 10 minutes and its still stuck.
Have you enabled init debug from the flashing guide? When I did that I got ‘stuck’ on the Sony logo as well since it was waiting for a telnet connection.
See: Sony Nagara (Xperia 1IV and 5IV) port - #256 by rinigus
I don’t know, if you scroll back you’ll see I ultimately failed in my flashing attempts.
It is rather strange that you both fail to get SFOS booting. Same device has been flashed based on the instructions as in XQ-CT72 support (1 IV with dual physical SIMs) · Issue #65 · sailfishos-sony-nagara/main · GitHub .
Re dtbo: DTBO from stock should work just fine - no need to flash it.
I start wondering whether your active slot is A or B. On my device, I took latest stock and flashed it on the both slots. As an active slot, I have A. Which slot do you have? This you can see by booting into fastboot mode and checking with fastboot command.
How did you update your device? Did you update via SONY OTA or used newflasher or Sony’s software for it? When using newflasher in flash mode, you can flash in one slot, then change slot using fastboot command while staying in flash mode, and then flashing in this changed slot.
If you used OTA, slots are swapped on each update and you may end up having different firmware. I expect that copy-partitions as described on LOS flashing page should help. But if you are on slot B, it would make sense to test using slot A. Just have to do it carefully to avoid bricking it - at least that is my constant fear with it.
Not sure if this is relevant but I am currently reflashed to your LOS image:
$ sudo fastboot getvar current-slot
current-slot: b
Before my SFOS flashing attempts I had updated using a Sony OTA update.
I don’t know how to be careful though 
Anyway, I’ll try again tomorrow in slot A. (but is there anything I need to do with slot B first?)
I’ll have to think about ‘careful’ bit. Main fear is bricking the device. So.don’t rush with jumping a slot as it has been am issue for one SODP user/developer.
My active slot is A. This was after I already flashed Sailfish OS. This time I didnt flash the dtbo image that was provided and used stock instead.
I updated it to the latest firmware via newflasher (if it helps with anything, it original ran on the TW firmware and I changed it to SEA.) So what do i do with the flashing and how do i do it step by step when my current slot is A.
Alright, I downloaded XQ-CT54_Customized_EU_UK_64.2.A.2.258 with XperiFirm and flashed it to both slots. Booted in Xperia Android, rebooted into it again because I read that somewhere.
Then set slot a to active and flashed lineage-21.0-20251108-SFOSBASE-pdx223.zip as described in Flashing Lineage OS · sailfishos-sony-nagara/main Wiki · GitHub (except for init debug!). Booted and rebooted into LOS.
Made sure slot a was active all the time.
Flashed sailfishos-Xperia-1-IV-XQCT54-5.0.0.71-testing.zip as described in Flashing Sailfish OS · sailfishos-sony-nagara/main Wiki · GitHub .
Booted into SFOS, the screen went dark again… but the LED stayed on and SFOS is now working on my Xperia 1 IV!
Hello how did you flash the firmware in both slots? And how did you set it to slot a and flashed the lineage zip?
sudo fastboot set_active a (or b) and then run newflasher.