Reply
Thread Tools
Posts: 213 | Thanked: 414 times | Joined on Nov 2010
#151
Originally Posted by Fellfrosch View Post
I updated my pro1 via zypper ref and zypper update. Now it doesn't start anymore. It is just booting to the bootscreen. Any chance to get it to work again, other than reflash?
See above for possible solution
 

The Following 3 Users Say Thank You to piggz For This Useful Post:
mosen's Avatar
Community Council | Posts: 1,669 | Thanked: 10,225 times | Joined on Nov 2014 @ Lower Rhine
#152
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.
Code:
➜  ~ ifconfig
enp0s20u6 Link encap:Ethernet  HWaddr 9A:81:AC:92:B6:E8
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:592  TX bytes:11933
the adapter shows up but no ip is assigned.
 

The Following 3 Users Say Thank You to mosen For This Useful Post:
Posts: 213 | Thanked: 414 times | Joined on Nov 2010
#153
Originally Posted by mosen View Post
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.
Code:
➜  ~ ifconfig
enp0s20u6 Link encap:Ethernet  HWaddr 9A:81:AC:92:B6:E8
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:592  TX bytes:11933
the adapter shows up but no ip is assigned.
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
 

The Following 5 Users Say Thank You to piggz For This Useful Post:
mosen's Avatar
Community Council | Posts: 1,669 | Thanked: 10,225 times | Joined on Nov 2014 @ Lower Rhine
#154
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.
 

The Following 6 Users Say Thank You to mosen For This Useful Post:
Posts: 194 | Thanked: 1,167 times | Joined on May 2016
#155
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.
 

The Following 9 Users Say Thank You to TheKit For This Useful Post:
Posts: 1,335 | Thanked: 3,931 times | Joined on Jul 2010 @ Brittany, France
#156
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

Last edited by Kabouik; 2020-03-16 at 09:47.
 

The Following 7 Users Say Thank You to Kabouik For This Useful Post:
Fellfrosch's Avatar
Posts: 1,092 | Thanked: 4,995 times | Joined on Dec 2009 @ beautiful cave
#157
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.
 

The Following 2 Users Say Thank You to Fellfrosch For This Useful Post:
Fellfrosch's Avatar
Posts: 1,092 | Thanked: 4,995 times | Joined on Dec 2009 @ beautiful cave
#158
@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...
 

The Following 3 Users Say Thank You to Fellfrosch For This Useful Post:
mosen's Avatar
Community Council | Posts: 1,669 | Thanked: 10,225 times | Joined on Nov 2014 @ Lower Rhine
#159
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.
 

The Following 3 Users Say Thank You to mosen For This Useful Post:
Posts: 958 | Thanked: 3,426 times | Joined on Apr 2012
#160
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.
 

The Following 2 Users Say Thank You to taixzo For This Useful Post:
Reply

Tags
fxtec pro1, sailfish os


 
Forum Jump


All times are GMT. The time now is 12:20.