Jolla device in Boot Loop [not relevant]

Question

9

Jolla device in Boot Loop [not relevant]

asked 2014-01-10 19:21:35 +0300

ZioBilly
1052 ●14 ●20 ●24

updated 2014-07-12 00:36:54 +0300

simo

29079 ●345 ●466 ●481

http://reviewjolla.blogsp...

My phone ran out of battery and now if i try to turn it on it goes in a boot loop. It boots up, shows the Jolla logo with white led, the led switch off, the screen switch off, the led turns red and it reboots.
I tried Jolla Recovery, as said here http://talk.maemo.org/showthread.php?t=92119 but it didn't work.
I emailed Jolla Care, but since the 31st of December they still didn't answered.. Anyone can help?

EDIT

Sent to care and they fixed the phone. it happened at the end of January, in two week i had a fixed phone.

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by simo
close date 2014-07-12 00:36:41.861202

Comments

This boot loop issue is not yet fixed and it seems to be an OS bug (probably related to the charging module) at least on my phone. Unless it's not fixed by Jolla or cleared what's the real reason this issue should be kept open.

Manankanchu ( 2014-04-12 19:29:20 +0300 )edit

Just contact jolla care, they can fix it, so they know about the issue, they're probably already workin on it. Do you have the same problem with the latest software update? If no, since they released 3 updates since when i had the problem, i think they may have fixed even the OS bug.

Just my opinions though, i'm not a programmer nor anyone really expert in this..

ZioBilly ( 2014-04-12 20:42:07 +0300 )edit

Release notes on 1.0.5.16 says: "Some of the device reboot issues have been addressed though it does not eliminate the problem completely. We are striving to find a fix to resolve the issue permanently. " ... leaving this topic open might help to collect additional findings ...

Manankanchu ( 2014-04-12 20:53:58 +0300 )edit

3

Tested the issue today again on 1.0.5.16 and problem is still the same. When Battery level goes below 50 % phone looses "sync" between real battery charge situation and the charge situation the OS thinks it has. Phone goes through a few reboot loops, charging level suddenly drops to 4% and jumps back to 49%. Connecting to charger load up to 100% in a much too short time. Disconnecting from charger starts reboot loop again after 20 minutes dropping the charge level to a few % ....

Manankanchu ( 2014-04-14 18:59:06 +0300 )edit

I'm sorry for yout situation, but this is not the issue i had, my phone shut down and never woke up, you may open another issue. See also this thread, https://together.jolla.com/question/7144/jolla-randomly-shuts-down/ maybe is related.. I also had this other issue and fixed it, as said in that thread, putting a folded paper under the battery, to exert more pressure on the pins

ZioBilly ( 2014-04-14 20:58:35 +0300 )edit

This boot loop issue is not yet fixed and it seems to be an OS bug (probably related to the charging module) at least on my phone. Unless it's not fixed by Jolla or cleared what's the real reason this issue should be kept open.
Manankanchu ( 2014-04-12 19:29:20 +0300 )edit
Just contact jolla care, they can fix it, so they know about the issue, they're probably already workin on it. Do you have the same problem with the latest software update? If no, since they released 3 updates since when i had the problem, i think they may have fixed even the OS bug.
Just my opinions though, i'm not a programmer nor anyone really expert in this..
ZioBilly ( 2014-04-12 20:42:07 +0300 )edit
Release notes on 1.0.5.16 says: "Some of the device reboot issues have been addressed though it does not eliminate the problem completely. We are striving to find a fix to resolve the issue permanently. " ... leaving this topic open might help to collect additional findings ...
Manankanchu ( 2014-04-12 20:53:58 +0300 )edit
Tested the issue today again on 1.0.5.16 and problem is still the same. When Battery level goes below 50 % phone looses "sync" between real battery charge situation and the charge situation the OS thinks it has. Phone goes through a few reboot loops, charging level suddenly drops to 4% and jumps back to 49%. Connecting to charger load up to 100% in a much too short time. Disconnecting from charger starts reboot loop again after 20 minutes dropping the charge level to a few % ....
Manankanchu ( 2014-04-14 18:59:06 +0300 )edit
I'm sorry for yout situation, but this is not the issue i had, my phone shut down and never woke up, you may open another issue. See also this thread, https://together.jolla.com/question/7144/jolla-randomly-shuts-down/ maybe is related.. I also had this other issue and fixed it, as said in that thread, putting a folded paper under the battery, to exert more pressure on the pins
ZioBilly ( 2014-04-14 20:58:35 +0300 )edit

Answer 1

2

answered 2014-04-19 19:18:05 +0300

Manankanchu

9022 ●42 ●54 ●50

http://www.manankanchu.co...

updated 2014-04-20 17:53:19 +0300

Reboot loop on my Jolla is related to phone functionality / SIM card access

when I key in PIN after reboot Jolla accesses SIM card and phone starts
right after start of phone functionality (or a few minutes later) Jolla reboots
when I hit"cancel" on PIN keyboard and then "continue" on display "SIM card not in use" Jolla works perfectly for hours
as soon as I activate SIM card (e.g. through settings) Jolla reboots instantly
this behaviour is perfectly reproducable
can't exclude relation to battery management as after reboot battery status jumps from 4 % to 60 % and back

I put it back to life through the following procedure:

took out the SIM card and started a few apps
let it run until battery was REALLY empty (the usual 4% battery status in the display was obviously not correct and never counted down, it took a few hours until it suddenly displayed 10 % counting down)
at 2% it said shutting down due to low battery, display got dark, LED went red for a minute or so
connected it to charger and it steadly loaded to 100%
put in the SIM card and phone worked normally (well, reboot loop returned today 3 weeks after I did that, but same procedure did the job again)

edit flag offensive delete publish link

Comments

Young just Waves my holla to Update to 11

dash72 ( 2015-03-02 19:22:19 +0300 )edit

Sorry written with iPhone while jolla boots. I hate iPhone's autocorrection

dash72 ( 2015-03-02 19:38:14 +0300 )edit

Accepted Answer

1

answered 2014-01-10 22:08:51 +0300

juju_des_highlands

4967 ●51 ●57 ●66

http://jujudeshighlands.c...

I had this kind of problem and @Stskeeps saved my life and my Jolla. You can contact him on Twitter (@Stskeeps) or on IRC (#sailfishos on freenode.net) or maybe he will see this thread. Good luck!

edit flag offensive delete publish link

Comments

Please share! How did he solve it?

00prometheus ( 2014-04-20 15:44:03 +0300 )edit

I made him the promise to not share it because it could irreversibly brick your device. Anyway Jolla recovery is the key.

juju_des_highlands ( 2014-04-20 16:02:57 +0300 )edit

Answer 3

1

answered 2014-03-29 18:27:14 +0300

bilgy_no1
7008 ●55 ●100 ●104

I had the same thing today. What helped in my case was to plug the phone into the charger.

Here's what happened:

I unlocked the phone and opened the browser. Battery level was at 70%.

While opening a new tab, the phone switched off.

I rebooted and the phone got into the loop like you describe. It would sometimes get to the PIN unlock screen, but then reboot again.

In one instance, after about 5 minutes of looping, it briefly showed the lock screen and battery life at 4%. Very strange, because minutes earlier it was at 70%!

I plugged the charger and the phone booted normally. Now, the lock screen showed the battery level at 68% again...

Strange phenomenon, that seems to be related to the battery level read out, or a buggy battery perhaps?

I hope my case helps shed some light on the matter. This was the first time it happened on my Jolla, and I hope it's a one off thing...

edit flag offensive delete publish link

Comments

I notified Jolla about the issues in my phone and they replied that they sent my observations to R&D. Let's see...

bilgy_no1 ( 2014-04-09 22:17:08 +0300 )edit

1

Taking out the battery for ten minutes helped keep this issue away for about two weeks. Today, the phone got onto a reboot loop.again. Previously, I noticed the issue got progressively worse, and I expect it do so so again.

bilgy_no1 ( 2014-04-20 02:07:12 +0300 )edit

Answer 4

0

answered 2014-01-10 23:03:48 +0300

foss4ever
13056 ●97 ●134 ●141

Did you try to get the phone to boot with.'Recovery Mode'? https://together.jolla.com/question/3612/release-notes-software-update-2-1025-edit-01012014/

edit flag offensive delete publish link

Comments

He said he already tried apparently.

juju_des_highlands ( 2014-01-10 23:09:21 +0300 )edit

Oh, didn't realize that the TMO-link has the ssme content as the official Release Notes of 1.0.2.5 where the way to enter Recocery Mode is described.

foss4ever ( 2014-01-10 23:11:45 +0300 )edit

Yes i tried, it had this error:

    mount: mounting /dev/mmcblk0p28 on /mnt failed: Invalid argument
[ERROR] Can't mount '/dev/mmcblk0p28' to '/mnt'

ZioBilly ( 2014-01-11 00:20:26 +0300 )edit

1

@ZioBilly Ok, then do as the Answer by @juju_des_higlands suggests ;)

foss4ever ( 2014-01-11 00:23:46 +0300 )edit

1

@ZioBilly So it seems to be the same problem I had, a kind of system corruption. Contact Stskeeps, he knows what to do :)

juju_des_highlands ( 2014-01-11 00:24:20 +0300 )edit

Jolla device in Boot Loop [not relevant]

The question has been closed for the following reason "question is not relevant or outdated" by simo
close date 2014-07-12 00:36:41.861202

Comments

4 Answers

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

Jolla device in Boot Loop [not relevant]

The question has been closed for the following reason "question is not relevant or outdated" by simo close date 2014-07-12 00:36:41.861202

Comments

4 Answers

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "question is not relevant or outdated" by simo
close date 2014-07-12 00:36:41.861202