Can not connect to recovery mode

Get Started
#1

can not connect to recovery mode

Hello, for Sailfish OS 4.5.0.18 I have too little memory. I have only 550 MB free.

According to the instructions https://together.jolla.com/question/222126/guide-installing-sailfish-x-on-xperias/#222126-332a-on-devices-sailfish-os-releases-without-home-volume-encryption

I should go into the recovery mode. But here only the first part works. I can not log in via TELNET. This has not worked from 2 PC. Attached the LOG.

localhost:/home/user/Programme/Linux/Sailfish OS/Sailfish_OS-Jolla-4.4.0.72-xqbt52-1.0.0.176 # fastboot boot hybris-recovery.img
Sending ‘boot.img’ (28004 KB) OKAY [ 0.890s]
Booting OKAY [ 5.135s]
Finished. Total time: 6.053s
localhost:/home/user/Programme/Linux/Sailfish OS/Sailfish_OS-Jolla-4.4.0.72-xqbt52-1.0.0.176 # telnet 10.42.66.66
Trying 10.42.66.66…
telnet: connect to address 10.42.66.66: Connection timed out
localhost:/home/user/Programme/Linux/Sailfish OS/Sailfish_OS-Jolla-4.4.0.72-xqbt52-1.0.0.176 #

Can someone give me a tip. Otherwise I can only start to uninstall software, or is there another way to create space?

#2

Have you prepared your PC according the docs? Recovery Mode | Sailfish OS Documentation

If you did, can you please paste the log from ifconfig or if the first is not installed: ip address show

#3

You can also look at Resizing root directory - telnet connection problems

#4

localhost:/home/user/Programme/Linux/Sailfish OS/Sailfish_OS-Jolla-4.4.0.72-xqbt52-1.0.0.176 # fastboot boot hybris-recovery.img
Sending ‘boot.img’ (28004 KB) OKAY [ 0.909s]
Booting OKAY [ 5.136s]
Finished. Total time: 6.072s
localhost:/home/user/Programme/Linux/Sailfish OS/Sailfish_OS-Jolla-4.4.0.72-xqbt52-1.0.0.176 # telnet 10.42.66.66
Trying 10.42.66.66…
^C
localhost:/home/user/Programme/Linux/Sailfish OS/Sailfish_OS-Jolla-4.4.0.72-xqbt52-1.0.0.176 # ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 50:e5:49:37:35:d9 brd ff:ff:ff:ff:ff:ff
altname enp5s0
inet 192.168.1.50/24 brd 192.168.1.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::52e5:49ff:fe37:35d9/64 scope link noprefixroute
valid_lft forever preferred_lft forever
localhost:/home/user/Programme/Linux/Sailfish OS/Sailfish_OS-Jolla-4.4.0.72-xqbt52-1.0.0.176 #

localhost:/home/user/Programme/Linux/Sailfish OS/Sailfish_OS-Jolla-4.4.0.72-xqbt52-1.0.0.176 # ip address list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 50:e5:49:37:35:d9 brd ff:ff:ff:ff:ff:ff
altname enp5s0
inet 192.168.1.50/24 brd 192.168.1.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::52e5:49ff:fe37:35d9/64 scope link noprefixroute
valid_lft forever preferred_lft forever

Unfortunately I can’t find a new device without address with the described commands.

#5

yes, i have prepared the PC

#6

Obviously there is something wrong with your PC. It doesn’t get correctly configured.
Like suggested above: you should try out the following Resizing root directory - telnet connection problems - #3 by olf

#7

The output is hard to read but it seems you are not getting a nettwork device for the USB connection.

Maybe some setting is preventing that, or the kernel lacks support for it. Check dmesg and other logs.

I’m guessing something udev-related.

#8

I will see if I can find out, but I think that exceeds my Linux knowledge.

Is there anyone in the triangle Braunschweig Bielefeld Bremen who could help me with his PC? Then I could come by on a weekend for half an hour. If possible best by train. Car would also work if necessary.

#9

Just picked up a Windows 10 laptop from the corner. There are two devices under Other. “Android” and “Broadcom USH”. No matter which of the two I convert, I get when I want to assign these two “devices” as RNDIS network adapters, only the error 10 and afterwards an exclamation mark that something is wrong. Putty directs me therefore also only into the empty.

CMD of Windows 10 knows itself TELNET strangely also not.

What can be uninstalled / deleted besides the apps before an update to create enough space?

I’ll send a screenshot of the file manager.

#10

Bildschirmfoto_20230219_001
Bildschirmfoto_20230219_0011080×1920 353 KB

Bildschirmfoto_20230219_002
Bildschirmfoto_20230219_0021080×1920 510 KB

#11

On linux you just need to run dhclient eth0 as long as ip address show outputs eth0 as an interface. If the non loop interface is something different, replace eth0 with that.
Another way would be to set the ip address in the network connection settings explicit to 10.42.66.0 as long as you try to conenct.
By the way: are you sure, that your home partition is not encrypted?

Edit: it’s basically what olf is describing in the link suggested by phklrz in this thread above.
Did you tried that out already?

#12

I’ll answer briefly now.
I will try the suggested solutions tonight.
As a test, I will change the network as suggested. I will not have time for further tests until Saturday.

With the encrypted partition I have probably had a thinking error, because I tried at the beginning of the console from the cell phone. I think you are right and I am wrong.

#13

I just wonder what sort of OS you are doing this from. Win? Mac? Linux? Linux in a VM? Could there be a firewall issue?