maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Jolla1 & TOH (https://talk.maemo.org/forumdisplay.php?f=56)
-   -   Jolla device in a boot loop (https://talk.maemo.org/showthread.php?t=92119)

ZioBilly 2013-12-30 19:41

Re: Jolla device in a boot loop
 
it says
Code:

SIOCSIFADDR: No such device
usb0: ERROR while getting interface flags: No Such Device
SIOCSIFADDR: No such device
usb0: ERROR while getting interface flags: No Such Device


nieldk 2013-12-30 20:23

Re: Jolla device in a boot loop
 
should come up.
1 which sailfish version are you on, I assumed the new release?
2 might be that cdc_ether module is not loaded on PC (sudo modprobe cdc_ether to load manually)
3 if, you are on older release of sailfish you may have the option to boot kernel to restore a backup , however, given that you dont follow how to use USB Networking as is, you probably also dont have backup images of the device , so this is not an option.

try - if you are on latest release, on PC to probe cdc_ether.

also a dmesg output and lsmod would help identifying where the issue is.

ZioBilly 2013-12-30 20:36

Re: Jolla device in a boot loop
 
Last relase, after sudo modprobe cdc_ether this is the lsmod:
Code:

billy@billy-h8-1206el:~$ lsmod
Module                  Size  Used by
cdc_ether              14351  0
usbnet                39495  1 cdc_ether
parport_pc            32701  0
ppdev                  17671  0
rfcomm                69070  12
bnep                  19564  2
nls_iso8859_1          12713  1
x86_pkg_temp_thermal    14162  0
intel_powerclamp      14705  0
coretemp              13435  0
kvm_intel            138538  0
kvm                  431315  1 kvm_intel
crct10dif_pclmul      14289  0
crc32_pclmul          13113  0
ghash_clmulni_intel    13259  0
aesni_intel            55624  2
aes_x86_64            17131  1 aesni_intel
lrw                    13257  1 aesni_intel
gf128mul              14951  1 lrw
glue_helper            13990  1 aesni_intel
ablk_helper            13597  1 aesni_intel
cryptd                20329  3 ghash_clmulni_intel,aesni_intel,ablk_helper
gpio_ich              13476  0
snd_hda_codec_hdmi    41276  4
snd_usb_audio        149162  0
xpad                  18218  0
arc4                  12608  2
snd_usbmidi_lib        25070  1 snd_usb_audio
rt2800pci              18690  0
ff_memless            13573  1 xpad
joydev                17377  0
rt2800lib              79963  1 rt2800pci
rt2x00pci              13287  1 rt2800pci
nouveau              943295  3
rt2x00mmio            13603  1 rt2800pci
rt2x00lib              55238  4 rt2x00pci,rt2800lib,rt2800pci,rt2x00mmio
mac80211              596969  3 rt2x00lib,rt2x00pci,rt2800lib
snd_hda_codec_idt      50341  1
snd_hda_intel          48171  5
mxm_wmi                13021  1 nouveau
snd_hda_codec        188738  3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
wmi                    19070  2 mxm_wmi,nouveau
snd_hwdep              13602  2 snd_usb_audio,snd_hda_codec
btusb                  28267  0
snd_pcm              102033  4 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
video                  19318  1 nouveau
cfg80211              479757  2 mac80211,rt2x00lib
bluetooth            371874  22 bnep,btusb,rfcomm
ttm                    83995  1 nouveau
snd_page_alloc        18710  2 snd_pcm,snd_hda_intel
snd_seq_midi          13324  0
snd_seq_midi_event    14899  1 snd_seq_midi
snd_rawmidi            30095  2 snd_usbmidi_lib,snd_seq_midi
drm_kms_helper        52651  1 nouveau
snd_seq                61560  2 snd_seq_midi_event,snd_seq_midi
eeprom_93cx6          13344  1 rt2800pci
drm                  296739  5 ttm,drm_kms_helper,nouveau
snd_seq_device        14497  3 snd_seq,snd_rawmidi,snd_seq_midi
crc_ccitt              12707  1 rt2800lib
snd_timer              29433  2 snd_pcm,snd_seq
psmouse                97626  0
snd                    69141  23 snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_seq_midi
i2c_algo_bit          13413  1 nouveau
soundcore              12680  1 snd
microcode              23518  0
serio_raw              13413  0
mei_me                18421  0
mei                    77692  1 mei_me
lpc_ich                21080  0
mac_hid                13205  0
lp                    17759  0
parport                42299  3 lp,ppdev,parport_pc
usb_storage            62062  0
hid_generic            12548  0
usbhid                53014  0
hid                  101512  2 hid_generic,usbhid
r8169                  67341  0
ahci                  25819  4
libahci                31898  1 ahci
mii                    13934  2 r8169,usbnet


ZioBilly 2013-12-30 20:38

Re: Jolla device in a boot loop
 
with dmesg it shows:
Code:

[  90.768744] usb 2-1.3: new high-speed USB device number 6 using ehci-pci
[  90.867702] usb 2-1.3: New USB device found, idVendor=2931, idProduct=0aff
[  90.867708] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  90.867711] usb 2-1.3: Product: Sailfish
[  90.867713] usb 2-1.3: Manufacturer: Jolla
[  90.867716] usb 2-1.3: SerialNumber: DU3C600088
[  117.527312] usbcore: registered new interface driver cdc_ether
[  279.792701] systemd-hostnamed[2413]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!

does it means something?

nieldk 2013-12-30 21:01

Re: Jolla device in a boot loop
 
it means your device is alive and communicating :)
Now, after modprobe seems to at least have added cdc_ether module, are you still not able to ?

sudo ifconfig usb0 192.168.2.18 netmask 255.255.255.0 up

if not , are you able to see usb0 with

sudo ifconfig -a

ZioBilly 2013-12-30 21:06

Re: Jolla device in a boot loop
 
it shows eth0, lo and wlan0

nieldk 2013-12-30 21:40

Re: Jolla device in a boot loop
 
you did press volume down? while powering on, and not volume up?

ZioBilly 2013-12-30 21:49

Re: Jolla device in a boot loop
 
it shows fastboot

nieldk 2013-12-30 21:59

Re: Jolla device in a boot loop
 
I believe you have the old unlocked bootloader.
Possible you didnt upgrade ?

Try to download https://github.com/djselbeck/jollare...net-initrd.img

and - as root - issue

fastboot -i 0x2931 boot boot-telnet-initrd.img

from where you downloaded boot-telnet-initrd.img

You might need to apt-get install fastboot :)

Output should be either

1. device boots that image with no errors
In this case, you can get telnet access (see https://wiki.merproject.org/wiki/Sailfish/Backup_Device) and create backups - which will be useless, as your device wont boot. Possibly you can get a copy of all 28 partitions, or at least the root file system to restore this way. However, it is 16GB of data :)

2. device tells you 'not allowed' in whicg case, you do have the newly locked bootloader. If USB net doesnt work, afraid we are ATM in the situation that you will need to return to service.

So, what does fastboot -i 0x2931 boot boot-telnet-initrd.img tell ?

juiceme 2013-12-30 22:26

Re: Jolla device in a boot loop
 
Just one note, with linux you need to use "sudo fastboot <command>" as unlike with adb, fastboot doesn't have usb write access as user :)

nieldk 2013-12-30 22:27

Re: Jolla device in a boot loop
 
Just noticed
You seem to be missing modules usbcore and rndis_host. Might be the issue with USB0 net (assuming you are using a newer Ubuntu)

nieldk 2013-12-30 22:28

Re: Jolla device in a boot loop
 
Quote:

Originally Posted by juiceme (Post 1402290)
Just one note, with linux you need to use "sudo fastboot <command>" as unlike with adb, fastboot doesn't have usb write access as user :)

right :) Thanks for pointing that out

ZioBilly 2013-12-30 22:43

Re: Jolla device in a boot loop
 
how do i put the img file in the root?
i don't know what "from where you downloaded" means :/

nieldk 2013-12-30 22:50

Re: Jolla device in a boot loop
 
ok, do like this

Code:

sudo su
wget https://github.com/djselbeck/jollare...net-initrd.img
fastboot -i 0x2931 boot boot-telnet-initrd.img

(You might need to install wget and fastboot by
apt-get install wget
apt-get install fastboot)

and tell us if that produces an error :)

ZioBilly 2013-12-30 22:56

Re: Jolla device in a boot loop
 
ehm..
FAILED (remote: access denied. need privilege!)

i'm getting mad with this :/
however thanks for your awesome help so far =)

nieldk 2013-12-30 22:59

Re: Jolla device in a boot loop
 
could you try to load those two modules i mentioned a few posts back. Then, see if usb0 interface will com alive

ZioBilly 2013-12-30 23:01

Re: Jolla device in a boot loop
 
with apt-get install usbcore and then rndis_host ?
If so it says unable to locate package

nieldk 2013-12-30 23:05

Re: Jolla device in a boot loop
 
sudo modprobe usbcore
sudo modprobe rndis_host

afraid it might be that the new recovery partition got damaged, which does only leave a return to jolla care :(

ZioBilly 2013-12-30 23:08

Re: Jolla device in a boot loop
 
after i write
sudo modprobe usbcore
sudo modprobe rndis_host
it doesn't display anything
and then sudo ifconfig -a doesn't show usb0

it eved said unable to locate package fastboot with apt-get install fastboot

for tonight i give up, thanks for your help =)

djselbeck 2013-12-30 23:53

Re: Jolla device in a boot loop
 
Just a quick note,

there are some linux distributions which doesn't name USB net devices with usb prefix. Some name them wlp...s... something for example. You should definitely check if there is a new interface. Also you could have a look in dmesg after you boot recovery mode.

Another thing is that usbcore often is compiled into kernel and not as an module which means it doesn't show up in lsmod ;)

juiceme 2013-12-31 06:58

Re: Jolla device in a boot loop
 
Quote:

Originally Posted by ZioBilly (Post 1402321)
it eved said unable to locate package fastboot with apt-get install fastboot

The android development tools, fasboot and adb, are not included in the main repositories of Ubuntu.
You need to either get them from a tarball or install a ppa (a kind of community repository)
The easiest way is do this:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

ZioBilly 2013-12-31 08:51

Re: Jolla device in a boot loop
 
Quote:

Originally Posted by djselbeck (Post 1402328)
Some name them wlp...s... something for example. You should definitely check if there is a new interface.

How can i do this?
sudo ifconfig - a shows this, and i guess these are the devices it can use:
Code:

eth0      Link encap:Ethernet  HWaddr e8:40:f2:81:8d:cd 
          inet6 addr: fe80::ea40:f2ff:fe81:8dcd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:55414 (55.4 KB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:553 errors:0 dropped:0 overruns:0 frame:0
          TX packets:553 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:51084 (51.0 KB)  TX bytes:51084 (51.0 KB)

wlan0    Link encap:Ethernet  HWaddr 9c:b7:0d:fd:3b:4d 
          inet addr:192.168.1.175  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::9eb7:dff:fefd:3b4d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8620 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5460 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10337241 (10.3 MB)  TX bytes:770879 (770.8 KB)

@juiceme i did as you said, but fastboot -i 0x2931 boot boot-telnet-initrd.img stil displays
FAILED (remote: access denied. need privilege!)

juiceme 2013-12-31 09:37

Re: Jolla device in a boot loop
 
@ZioBilly, use "sudo fastboot -i 0x2931 boot boot-telnet-initrd.img"

djselbeck 2013-12-31 11:53

Re: Jolla device in a boot loop
 
Quote:

Originally Posted by ZioBilly (Post 1402385)
How can i do this?
sudo ifconfig - a shows this, and i guess these are the devices it can use:
Code:

eth0      Link encap:Ethernet  HWaddr e8:40:f2:81:8d:cd 
          inet6 addr: fe80::ea40:f2ff:fe81:8dcd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:55414 (55.4 KB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:553 errors:0 dropped:0 overruns:0 frame:0
          TX packets:553 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:51084 (51.0 KB)  TX bytes:51084 (51.0 KB)

wlan0    Link encap:Ethernet  HWaddr 9c:b7:0d:fd:3b:4d 
          inet addr:192.168.1.175  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::9eb7:dff:fefd:3b4d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8620 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5460 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10337241 (10.3 MB)  TX bytes:770879 (770.8 KB)

@juiceme i did as you said, but fastboot -i 0x2931 boot boot-telnet-initrd.img stil displays
FAILED (remote: access denied. need privilege!)

Your bootloader seems to be locked, it has nothing to do with sudo.

Your only chance of recovery is jollas recovery. For this you need usb networking working.

Boot your device in recovery:
  • Power off device with no usb cable
  • Press volume down and hold, then press power and hold until "Jolla" shows up
  • wait for recovery to boot
  • connect to pc via usb

If connected to pc can you send the output of "dmesg|tail -n200" ?

ZioBilly 2013-12-31 13:46

Re: Jolla device in a boot loop
 
it is stuck on Jolla logo after "Press volume down and hold, then press power and hold until "Jolla" shows up"

nieldk 2013-12-31 13:56

Re: Jolla device in a boot loop
 
supposed to be :)
now, you need to get USB0 up to telnet to the device

ZioBilly 2013-12-31 13:58

Re: Jolla device in a boot loop
 
This is the output of dmesg|tail -n200 :
Code:

[  153.730181] usb 2-1.3: new high-speed USB device number 6 using ehci-pci
[  153.829157] usb 2-1.3: New USB device found, idVendor=2931, idProduct=0aff
[  153.829163] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  153.829166] usb 2-1.3: Product: Sailfish
[  153.829169] usb 2-1.3: Manufacturer: Jolla
[  153.829171] usb 2-1.3: SerialNumber: DU3C600088
[  318.402679] audit_printk_skb: 144 callbacks suppressed
[  318.402684] type=1400 audit(1388479103.006:72): apparmor="STATUS" operation="profile_replace" parent=2709 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2713 comm="apparmor_parser"
[  318.402695] type=1400 audit(1388479103.006:73): apparmor="STATUS" operation="profile_replace" parent=2709 profile="unconfined" name="/usr/sbin/cupsd" pid=2713 comm="apparmor_parser"
[  318.403610] type=1400 audit(1388479103.006:74): apparmor="STATUS" operation="profile_replace" parent=2709 profile="unconfined" name="/usr/sbin/cupsd" pid=2713 comm="apparmor_parser"
[  568.236698] usbcore: registered new interface driver cdc_ether
[  966.145171] usb 2-1.3: USB disconnect, device number 6
[19332.727013] usb 2-1.3: new high-speed USB device number 7 using ehci-pci
[19332.820120] usb 2-1.3: New USB device found, idVendor=18d1, idProduct=d001
[19332.820125] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[19332.820128] usb 2-1.3: Product: Recovery
[19332.820131] usb 2-1.3: Manufacturer: Jolla
[19332.820133] usb 2-1.3: SerialNumber: DU3C600088
[19332.821601] usb-storage 2-1.3:1.2: USB Mass Storage device detected
[19332.821794] scsi7 : usb-storage 2-1.3:1.2
[19332.845279] rndis_host 2-1.3:1.0 eth1: register 'rndis_host' at usb-0000:00:1d.0-1.3, RNDIS device, 00:01:02:03:04:05
[19332.845309] usbcore: registered new interface driver rndis_host
[19332.857626] usbcore: registered new interface driver rndis_wlan
[19333.819447] scsi 7:0:0:0: Direct-Access    Linux    File-CD Gadget  0000 PQ: 0 ANSI: 2
[19333.819756] sd 7:0:0:0: Attached scsi generic sg7 type 0
[19333.824284] sd 7:0:0:0: [sdg] Attached SCSI removable disk
[19337.647355] usb 2-1.3: USB disconnect, device number 7
[19337.649541] rndis_host 2-1.3:1.0 eth1: unregister 'rndis_host' usb-0000:00:1d.0-1.3, RNDIS device
[19337.873849] usb 2-1.3: new high-speed USB device number 8 using ehci-pci
[19337.967076] usb 2-1.3: New USB device found, idVendor=18d1, idProduct=d001
[19337.967082] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[19337.967085] usb 2-1.3: Product: Recovery
[19337.967087] usb 2-1.3: Manufacturer: Jolla
[19337.967090] usb 2-1.3: SerialNumber: DU3C600088
[19337.969282] rndis_host 2-1.3:1.0 eth1: register 'rndis_host' at usb-0000:00:1d.0-1.3, RNDIS device, 00:01:02:03:04:05
[19337.969696] usb-storage 2-1.3:1.2: USB Mass Storage device detected
[19337.969946] scsi8 : usb-storage 2-1.3:1.2
[19338.970255] scsi 8:0:0:0: Direct-Access    Linux    File-CD Gadget  0000 PQ: 0 ANSI: 2
[19338.970606] sd 8:0:0:0: Attached scsi generic sg7 type 0
[19338.973079] sd 8:0:0:0: [sdg] Attached SCSI removable disk

do i have to go with
sudo ifconfig usb0 192.168.2.16 netmask 255.255.255.0 up
telnet 192.168.2.15
?

djselbeck 2013-12-31 14:03

Re: Jolla device in a boot loop
 
i think the interface is eth1 not usb0 ;)

ZioBilly 2013-12-31 14:05

Re: Jolla device in a boot loop
 
Yes! Jolla recovery has started! now i think i have to do reset, right? =)

nieldk 2013-12-31 14:09

Re: Jolla device in a boot loop
 
yes,it registered as eth1
so, replace USB0 with eth1 in ifconfig

but, it seems from the log like you pressed volume up insted of volume down if ifconfig eth1 ... fails try to do the procedure again, and ensure you use volume down when power on

nieldk 2013-12-31 14:10

Re: Jolla device in a boot loop
 
i was late :)
yes, press reset to factory

ZioBilly 2013-12-31 14:10

Re: Jolla device in a boot loop
 
this is the output
Code:

[CLEANUP] Starting cleanup!
[CLEANUP] Umounting top volume...
[CLEANUP] Deleting /mnt
[CLEANUP] Cleanup done.
Mounting /dev/mmcblk0p28 on /mnt
mount: mounting /dev/mmcblk0p28 on /mnt failed: Invalid argument
[ERROR] Can't mount '/dev/mmcblk0p28' to '/mnt'
[CLEANUP] Starting cleanup!
[CLEANUP] Umounting top volume...
[CLEANUP] Deleting /mnt
[CLEANUP] Cleanup done.
Connection closed by foreign host.

i'm pretty sure i pressed the volume down.. i'll try with the other :/

nieldk 2013-12-31 14:13

Re: Jolla device in a boot loop
 
no, you did correct. Now just reboot device

ZioBilly 2013-12-31 14:16

Re: Jolla device in a boot loop
 
nothing changed, still in boot loop

nieldk 2013-12-31 14:20

Re: Jolla device in a boot loop
 
aav, not good
Something is damaged so that the factory restore is not enough.
I guess root filesystem is not completely restorable :(
Afraid this means it needs service at Jolla for a complete reflash :(

fl4f 2013-12-31 14:22

Re: Jolla device in a boot loop
 
Stskeeps helped me out.

This was when I was on the 10.0.1.x version of the os.

The
mount: mounting /dev/mmcblk0p28 on /mnt failed: Invalid argument

Error message is most likely due to corrupted filesystem on /dev/mmcblk0p28

Maybe you should contact Jolla Care ?

If you are able to get a prompt when connected to the device, its fixable.

ZioBilly 2013-12-31 14:24

Re: Jolla device in a boot loop
 
where can i contact jolla care?

nieldk 2013-12-31 14:26

Re: Jolla device in a boot loop
 
since the restore worked, a prompt should be possible (fastboot boot)
what did stskeep tell to fix it?

fl4f 2013-12-31 14:30

Re: Jolla device in a boot loop
 
Quote:

Originally Posted by nieldk (Post 1402509)
since the restore worked, a prompt should be possible (fastboot boot)
what did stskeep tell to fix it?

The restore is not working in ZioBilly's case ?
/dev/mmcblk0p28 is not mountable

We mounted with other paramters.

But I think they are working on a fix for this one actually. This thread proves that I'm not the only one experiencing these problems.

fl4f 2013-12-31 14:31

Re: Jolla device in a boot loop
 
Quote:

Originally Posted by ZioBilly (Post 1402507)
where can i contact jolla care?

care@jolla.com


All times are GMT. The time now is 06:13.

vBulletin® Version 3.8.8