maemo.org - Talk - Jolla device in a boot loop

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)

Re: Jolla device in a boot loop

I guess you are speeking of your guide : https://wiki.merproject.org/wiki/Sai...prebuilt_image

Unfortunately, this is not for me: I have windows :(

Well, it seems I need to go the Linux way... for a lot of reasons.

Re: Jolla device in a boot loop

Boot loop here as well.

Code:

dmesg [ 1273.480188] usb 2-1: new high-speed USB device number 8 using ehci_hcd

Code:

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

downloading 'boot.img'...

OKAY [  0.434s]

booting...

FAILED (remote: access denied. need privilege!)

finished. total time: 0.437s

Code:

telnet 192.168.2.18

Trying 192.168.2.18...

telnet: Unable to connect to remote host: No route to host

Sigh.

Re: Jolla device in a boot loop

My Jolla is R.I.P. Stuck in 5 second logo ON, 1 second off reboot loop no damn way to recover it seems.

Re: Jolla device in a boot loop

Quote:

Originally Posted by shanttu (Post 1409801)

Boot loop here as well.

Code:

dmesg [ 1273.480188] usb 2-1: new high-speed USB device number 8 using ehci_hcd

Code:

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

downloading 'boot.img'...

OKAY [  0.434s]

booting...

FAILED (remote: access denied. need privilege!)

finished. total time: 0.437s

Code:

telnet 192.168.2.18

Trying 192.168.2.18...

telnet: Unable to connect to remote host: No route to host

Sigh.

you cant fastboot with updated firmware. It is locked!
You can however boot recovery and to some factory reset

Push and hold the volume down button
Push and hold for a while the power button until the phone vibrates, release all buttons
connect USB cable
telnet 192.168.2.15

Re: Jolla device in a boot loop

Quote:

Originally Posted by nieldk (Post 1409860)

you cant fastboot with updated firmware. It is locked!
You can however boot recovery and to some factory reset

Push and hold the volume down button
Push and hold for a while the power button until the phone vibrates, release all buttons
connect USB cable
telnet 192.168.2.15

Thanks, but already made those steps. care@jolla.com got mail. I live 10 km away from Optima service so maybe I'll just give the device for them to reflash.

Re: Jolla device in a boot loop

Yea, we need unlocked bootloader asap or a way to flash the device on our own. This reboot loop and send them in to care sucks hard.

Re: Jolla device in a boot loop

Quote:

Originally Posted by Nekron (Post 1409885)

Yea, we need unlocked bootloader asap or a way to flash the device on our own. This reboot loop and send them in to care sucks hard.

Why do that help in any way? If reboot loop and not connects usb network how would "flash yourself" help in any way? I mean you need atleast USB network to flash it and in most cases it seems not even that seems work.

My Linux box find "new USB device" but Jolla seems not activate USB network profile but find unmountable /dev/sdb hmmm

Code:

Jan 30 22:37:31 ThinkPad-X230 kernel: [45186.661079] usb 3-2: Product: Recovery

Jan 30 22:37:31 ThinkPad-X230 kernel: [45186.661082] usb 3-2: Manufacturer: Jolla

Jan 30 22:37:31 ThinkPad-X230 kernel: [45186.661085] usb 3-2: SerialNumber: 123456789

Jan 30 22:37:31 ThinkPad-X230 kernel: [45186.663232] rndis_host 3-2:1.0 eth1: register 'rndis_host' at usb-0000:00:14.0-2, RNDIS device, 00:01:02:03:04:05

Jan 30 22:37:31 ThinkPad-X230 kernel: [45186.663585] usb-storage 3-2:1.2: USB Mass Storage device detected

Jan 30 22:37:31 ThinkPad-X230 kernel: [45186.663689] scsi19 : usb-storage 3-2:1.2

Jan 30 22:37:31 ThinkPad-X230 mtp-probe: checking bus 3, device 57: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"

Jan 30 22:37:31 ThinkPad-X230 mtp-probe: bus: 3, device: 57 was not an MTP device

Jan 30 22:37:32 ThinkPad-X230 kernel: [45187.660936] scsi 19:0:0:0: Direct-Access     Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2

Jan 30 22:37:32 ThinkPad-X230 kernel: [45187.661461] sd 19:0:0:0: Attached scsi generic sg1 type 0

Jan 30 22:37:32 ThinkPad-X230 kernel: [45187.662497] sd 19:0:0:0: [sdb] Attached SCSI removable disk

Re: Jolla device in a boot loop

This situation is stinky. Unacceptable.

If Jolla wants to make his mark in the smartphone world, they need the continued support of developers. Not being able to recover easily from a boot loop certainly doesn't help.

For the next SW update, I would like to see only 1 improvement: to be able to recover from a boot loop. No fancy features. Just this.

Re: Jolla device in a boot loop

If using developer mode this is the correct ip when connect to Jolla:

Code:

sudo ifconfig eth1 192.168.2.14 netmask 255.255.255.0 up

telnet 192.168.2.15

However in my case I am now lost in:

Code:

re you really SURE? If you continue, ALL DATA (pictures, videos, messages, accounts and all the personal data) stored in the device memory WILL BE ERASED! [y/n]

y

[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.

so my Jolla is doomed :(

Re: Jolla device in a boot loop

Quote:

Originally Posted by mikecomputing (Post 1409889)

Unlocked bootloader would help, because you can boot your own recovery image and have access to the raw filesystem with a busybox shell. You can revert the changes which brick your device. Also you can dd you backuped system image, if you have one