My phone reboot during a update and now fails to boot [answered]

Question

3

My phone reboot during a update and now fails to boot [answered]

asked 2013-12-27 20:52:30 +0300

Kilian
41 ●2 ●6 ●9

updated 2013-12-27 20:59:58 +0300

My Jolla phone reboot downloading Sailfish update 2 (1.0.2.5), and after that, the reboot process stays stopped on the splash screen (the screen with text Jolla). After waiting half an hour I have tried to reset the device by removing the battery but nothing changes. What I can do? I'm afraid I could I bricked the device. Any chance of reinstalling the firmware from scratch?

Thanks very much.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kilian
close date 2014-01-06 00:00:40.835465

Comments

Answer 1

2

answered 2013-12-27 22:27:36 +0300

Stskeeps

8994 ●62 ●67 ●71

http://twitter.com/stskee...

Are you able to access IRC? come by irc.freenode.net channel #jollamobile and talk to Stskeeps.

edit flag offensive delete publish link

Answer 2

1

answered 2013-12-27 21:20:42 +0300

penpen
2133 ●21 ●36 ●37

See the recovery mode at the release notes

edit flag offensive delete publish link

Comments

Thanks a lot. There is any tutorial about recovery mode? Following instructions the device boot and show this text:

ERROR: Invalid boot image header ERROR: Could not do normal boot. Reverting to fastboot mode. fastboot mode
Manufacturer: Jolla Product: Jolla

But I can't connect to 192.168.2.15 or 10.42.66.66 using USB...

Kilian ( 2013-12-27 21:54:14 +0300 )edit

Have you enabled RNDIS from your computer?

penpen ( 2013-12-27 22:05:38 +0300 )edit

Same here. 192.168.2.15 "no route to host", 10.42.66.66 "timed out"

I did not give up: I put power on pushing sound down.

--dmesg:

[ 7677.833634] usb 1-1.4: Product: Recovery [ 7677.833636] usb 1-1.4: Manufacturer: Jolla [ 7677.833638] usb 1-1.4: SerialNumber: DU3BR00217 [ 7677.836458] rndis_host 1-1.4:1.0: eth1: register 'rndis_host' at usb-0000:00:1a.0-1.4, RNDIS device, 00:01:02:03:04:05 [ 7677.836938] scsi11 : usb-storage 1-1.4:1.2 [ 7678.834801] scsi 11:0:0:0: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2 [ 7678.836377] sd 11:0:0:0: Attached scsi generic sg3 type 0 [ 7678.837716] sd 11:0:0:0: [sdc] Attached SCSI removable disk

It is alive and seen.

lasse@janika:~$ telnet 10.42.66.66 Trying 10.42.66.66... telnet: Unable to connect to remote host: Connection timed out

lasse@janika:~$ nmap -Pn 10.42.66.66

Starting Nmap 6.00 ( http://nmap.org ) at 2013-12-28 16:21 EET Nmap scan report for 10.42.66.66 Host is up (0.048s latency). All 1000 scanned ports on 10.42.66.66 are filtered

Nmap done: 1 IP address (1 host up) scanned in 10.93 seconds

So! It is autistic. I'm clueless, olen liimaton.

lasse ( 2013-12-28 10:20:40 +0300 )edit

Couldn't connect with a simple telnet 10.42.66.66, mine was on port 23 (showed by nmap, thanks for that).

fawz ( 2014-01-08 18:08:09 +0300 )edit

Answer 3

1

answered 2013-12-29 19:07:27 +0300

Kilian
41 ●2 ●6 ●9

updated 2013-12-29 19:51:26 +0300

@lasse Turn off the device, take out the usb cable, take out the battery, then put in the battery, hold down volumen down and turn on the device (the splash screen with "jolla" text should remain fixed). Then plug USB from device to PC (in Linux should see new messages at syslog):

sudo tail -f /var/log/syslog

Next test that related modules was loaded:

sudo lsmod usbnet

And a new interface was up:

sudo ifconfig -a

Depending upon the assigned IP, telnet to 192.168.2.15 or 10.42.66.66 and you should see something like that:

----------------------------
     Jolla Recovery v0.1     
-----------------------------
Welcome to the recovery tool!
The available options are:
1) Reset phone to factory settings
2) Reboot phone
3) Exit
Type the number of the desired action and press [ENTER]:

edit flag offensive delete publish link

Comments

Same situation, but... I just get:

Product: Boston Manufacturer: Qisda Serial number: XXXXXXXX device5: "sys/devices/pci0000:00/000:00:ld.7/usb1/1-3" device: 5 was not an MTP device

And that's it. No usbnet module.

And no fstab changes nor sdcard ever on device.

arigr ( 2013-12-29 21:25:39 +0300 )edit

Can you try to load manually the usbnet module with:

modprobe usbnet

Kilian ( 2013-12-29 22:23:21 +0300 )edit

No luck with manual start of usbnet

arigr ( 2013-12-29 22:30:55 +0300 )edit

My Jolla is refusing telnet connection. I tried also ssh but what is the password? I don't have any. Tried even pin which did not work.

lasse ( 2013-12-30 09:27:36 +0300 )edit

Then you have setup a usbnet? Any of your NIC have already assigned a IP like 192.168.2.XX or 10.42.66.XX? (check with 'ifconfig -a"). Thereis not password.

Kilian ( 2013-12-31 04:22:17 +0300 )edit

Accepted Answer

0

answered 2013-12-28 00:13:40 +0300

Kilian
41 ●2 ●6 ●9

updated 2013-12-28 00:27:52 +0300

Finally was my fault. Manually changed '/etc/fstab' file in developer mode (for automount sdcard partitions) and this crash the boot. Thanks @Stskeeps for the support.

edit flag offensive delete publish link

Answer 5

0

answered 2013-12-29 20:01:51 +0300

WK
51 ●2 ●3 ●5

I'm having the same-ish problem; with recovery tool I can only get

-----------------------------
     Jolla Recovery v0.1     
-----------------------------
Welcome to the recovery tool!
The available options are:
1) Reset phone to factory settings
2) Reboot phone
3) Exit
Type the number of the desired action and press [ENTER]: 
1

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

Phone just turned off while I was trying to take a picture with camera.

edit flag offensive delete publish link

Comments

Are you playing with your '/etc/fstab' file or insert a new sd-card? Maybe you can retry the reset without sd.card.

Kilian ( 2013-12-29 20:11:49 +0300 )edit

Fails whether card installed or not.

WK ( 2013-12-29 20:19:41 +0300 )edit

1

If that happened when taking a picture and you didn't change anything with development mode / terminal between last reboot and taking a picture, I would suspect some kind of hardware problem. I think you should try to contact Stskeeps via IRC.

penpen ( 2013-12-30 15:34:00 +0300 )edit

No, nothing weird - my friend actually rebooted the phone on accident earlier that day (not familiar with the controls) and it worked out fine! Talked with the guy, and it seems the only fix is to bring it for reflash at Care.

WK ( 2013-12-30 17:22:05 +0300 )edit

I have this issue after taking a photo my phone started reboot loop. Only thing I done i with devmode after reboot is: set password in developermode to nemo and do: service tohd stop but those commands was done long before take the photo. Battery was around 13% when I took photo.

mike7b4 ( 2014-01-31 23:46:09 +0300 )edit

My phone reboot during a update and now fails to boot [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kilian
close date 2014-01-06 00:00:40.835465

Comments

5 Answers

Comments

Comments

Comments

Question tools

Stats

Related questions

My phone reboot during a update and now fails to boot [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kilian close date 2014-01-06 00:00:40.835465

Comments

5 Answers

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by Kilian
close date 2014-01-06 00:00:40.835465