Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

See above for possible solution

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

No, sadly telnet gets refused in recovery mode at 192.168.2.1 regardless the port.

When booted regular into that now failed state i can not successfully connect via USB.
the adapter shows up but no ip is assigned.

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

Phone is always 192.168.2.15, you could manually set an IP on the host, and you need to telnet to port 2323.

Ive restored the old packages, so if you can get in, you should be able to zypper ref && zypper dup to restore them, once the build server has settled down...

In the future, we will move users to the testing: repos so we can break devel without it breaking for you too :)

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

Do not fear Fellfrosch, i have a working Pro¹ again thanks to TheKit fixing it via remote terminal session.

Thanks again.
Hopefully you can find a way to connect into your device and follow Adams instructions, else its about asking TheKit the right questions since he figured out how to get my USB network up short/long enough to be able to do the fix.
Man, that was a terminal blockbuster for humble noob me to watch. Infinity War was boring in comparison.

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

I was able to restore mosen's device by connecting to him via tmate. It seems what should be done is:

1. Boot device by pressing power button with USB cable plugged in
2. After ~15 seconds, telnet 192.168.2.15 2323
3. sed -i -e "s/sde16/sde18/g" /lib/systemd/system/vendor.mount # fix vendor mount
4. iptables -P INPUT ACCEPT && iptables -P OUTPUT ACCEPT && iptables -P FORWARD ACCEPT && iptables -F # allow SSH connection
5. exit
6. wget http://repo.merproject.org/obs/nemo:...22.armv7hl.rpm
7. scp droid-hal-t5-kernel-modules-0.0.6-202001301422.armv7hl.rpm nemo@192.168.2.15:
8. telnet 192.168.2.15 2323
9. zypper in -f /home/nemo/droid-hal-t5-kernel-modules-0.0.6-202001301422.armv7hl.rpm # may complain about dependencies, agree to break them and install anyway
10. reboot
    
    After that it should boot with display and Wi-Fi working again, do "zypper ref && zypper dup" on device to restore rest of packages.

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

While it's a dumb answer to your issues, make sure you have a working TWRP backup of SFOS. I used mine already three times (not due to any SFOS issue, just because I needed tests in stock Android), and knowing I can at all times restore the backup is a huge relief.

https://gist.github.com/Kabouik/f775...d2fa827271b81d

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

Thanks to all for that quick help!!! I had success with TheKit's einstructions. My device is up and running again. Also thanks to Kabouik for his advice to make a TWRP backup and for the instructions how to do it!

I love this community.

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

@mosen Is your SD-Card still recognized after that action? For me I have now the same situation as in the past. SD-Card isn´t shown, instead I see lots of drives...

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

No, the fix has "deprecated" for me also during some of the last updates.
My guess is since we already discussed this on discord a week ago or so the devs are aware.

Re: SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat
 

is there a way to make the PIN unlock pad bigger? It's quite small relative to the screen, compared to the Xperia X or the original Jolla, and hard to unlock with a thumb.