Jolla won't power on

[fravaccaro]

Hello everybody,

After I updated my Jolla to Sailfish OS 2.0.0.45 I had pretty bad luck. I played around for a whole day, switching my phone off and on, rebooting it, with no issues at all.

Suddenly tho, it can't no longer power on. I tried to access to the recovery mode with no luck, the only glimpse of life (an LED blink) occurs when I plug an USB chord in with no battery inserted.

If I plug an USB cable with the battery inserted, lsusb shows:

Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

while dsmesg outputs:

[342062.964718] usb 2-4: new high-speed USB device number 6 using ehci-pci
[342063.092797] qcserial 2-4:1.0: Qualcomm USB modem converter detected
[342063.093020] usb 2-4: Qualcomm USB modem converter now attached to ttyUSB0

Any chance to bring it back to life?

[coderus]

wow, seems your phone is really bricked now. contact jolla care is the only way.

[fravaccaro]

Yay, I digged on TMO for hours, it's nice to be the "first one" to have such an issue!

I'll post here any info I get, hoping to be useful to people who may run into this situation.

Thank you for your quick reply :)

[pichlo]

It might be worth trying a different battery first if you have an access to one.

[nieldk]

This, is really really bad.
Some research on that mode.
forum.xda-developers.com/showthread.php?t=2086142

[fravaccaro]

Trying a different battery unluckily doesn't work :(

Do you think this would be useful?

https://github.com/aureljared/unbrick_8960

[nieldk]

Trying a different battery unluckily doesn't work :(

Do you think this would be useful?

https://github.com/aureljared/unbrick_8960

Probably not. Research is needed for Jolla. And, very likely, the bin files reffered to is different for Jolla.
This, is also mentioned in the readme.

[nieldk]

Allthough, may not be impossible. We seem to have a similar structure (SBL1, SBL2, ...)
http://talk.maemo.org/showpost.php?p=1404348&postcount=243

[fravaccaro]

So do you think using a dump from a working Jolla may work?

[Schturman]

Once have similar problem, jolla replaced my device...

[fravaccaro]

Weeeeell I opened a ticket on zendesk, but since my phone is from 2014 I doubt it's covered by any warranty. And the Jolla C is (hopefully) on its way, so I'd rather use my device as a 'cavy' to help posterity which may stumble upon such issue (and since you too had it it may not be that uncommon, unluckily) - and if it works I'll have a secondary phone to continue my programming tests and community will have a fix :)

[nodevel]

Weeeeell I opened a ticket on zendesk, but since my phone is from 2014 I doubt it's covered by any warranty. And the Jolla C is (hopefully) on its way, so I'd rather use my device as a 'cavy' to help posterity which may stumble upon such issue (and since you too had it it may not be that uncommon, unluckily) - and if it works I'll have a secondary phone to continue my programming tests and community will have a fix :)

I am very sorry to hear your device is bricked. Let's hope you'll find a way to revive it.

I indeed hope that your case is going to be a warning for everyone who might think about installing pre-pre-pre-release version the shady way. PSA: There is no reason to install them, so don't do it, guys.
No "Don't install it unless you really need it." or "Don't install it unless you know what you're doing", just "Don't.".

I don't think anything good can come from installing these releases even if nothing goes wrong. People share info about new features in the release, which A) spoils all surprises B) motivates new people to try to install it, because they feel left behind. And the argument about developers being able to test their apps against the changes is IMHO invalid, as an official pre-release program already exists.

Then they spam TJC with bug reports which have little to no value, because they have no connection to Jolla's internal bugs - when a pre-release version is announced officially, you always get info about known issues and if the issue you're experiencing is not among them you can be pretty sure it is not tracked by Jolla and your bug report is needed and valuable. Without such connection, it just fills TJC and confuses potential customers who might visit TJC and see those critical bugs.
Also everyone who follows these pre-pre-pre-release TMO threads can see how many people have problems with partial upgrades (almost everyone) and it is quite likely that a good part of their reported bugs is a result of this rather than a bug in the release itself.

Finally, if more bricks occur, it might push Jolla to prevent this by locking the repositories access to Jolla accounts or even devices IMEIs... Which is something nobody wants. And also each brick means one device that could have been used by someone in this community - it is sold out in Jolla's E-shop and obtaining a used one is becoming more difficult already. I'm guilty of recently killing one Jolla with a drop on concrete floor and I don't feel good about it either :rolleyes:

[fravaccaro]

Thanks :)

You're absolutely right and I sincerely agree on everything you said. I've actually been testing pre-release software from the 1.1.6 update onwards and:

- I've never advertised such a way to install updates on jollait (which is the community I'm of course more focused on) nor shared my way to sniff unreleased software.
- My reviews/posts where posted after the early access release date, to avoid spoilers or people trying to update and flood tjc with bug reports related to non-final products.

I used to update in this fashion both to prepare the stuff I need for the blog well in advance, instead of rushing to post a weak, incomplete and superficial article/video (I'm not a member of any pre-release group unluckily - albeit such a program would benefit bloggers too) - and of course because I'm a curious human being (oh and it was useful to test my DynCal, DynClock, tps scripts against the changes done on the 2.0.1, too).

I decided to openly talk about my issue also because this pre-release software bubble's already exploded (tmo, tjc, telegram) and although I'm still not sure whether it can be linked to 2.0.2 I prefered to admit my mistake and try to warn other people (as my post on the 2.0.2 thread) with a direct experience about the risks they take when they update.

It's not that hard actually - RCH has some refurbished and unsold Jolla1 in stock if you still need one!

[pichlo]

nodevel, whilst I can understand and even agree with some of your sentiments, I would not see it so black and white.
Here is why:
With Jolla, I feel like living on the edge all the time, like hurtling at 90 mph down a narrow country lane with a 40 mph speed limit. Anything can happen at any time. Installing an unofficial release is like speeding up from 90 to 95 mph: it increases the risk but not that much.
With Jolla, every system update is a game of Russian roulette. Just read the posts here or on TJC after every update. My first and only black screen happened on a brand new Jolla freshly out of the box, signed in to my home network and accepted the update.
2.0.2.4x is not some random build Jolla never meant for us to see. It has been released and given out with "development and community" devices. Jolla must have felt confident enough to do that, otherwise they would either not give out the devices or give them out with some older build. Or release the devices with whatever build but not make the build accessible for anyone else. In short, they could have done a lot of things but they did not deem it necessary.
Calling 2.0.2.4x bug reports on TJC "spam" and "useless" smacks of Dave999's style. Unless told otherwise, I assume that Jolla appreciates the reports exactly because it is a pre-early release. They even reply to some of those reports.
Lastly, I am not convinced that fravoccaro's problem has anything to do with 2.0.2.4x. I am not even convinced that it has anything to do with any system update, let alone an update to any specific build. He said he has rebooted a number of times after the update before the brick. I suspect his Jolla was already on the way out and the update was a red herring.


This is not to say that I would encourage people to rush into random updates. Please only do that if you are willing to accept the risk and do not do it if you need your Jolla's for anything important. But if you use them only for playing and do not mind losing your data, I don't see why not.

[nodevel]

nodevel, whilst I can understand and even agree with some of your sentiments, I would not see it so black and white.

I know it isn't black & white, but I think it's better portrayed that way rather than how it is portrayed now. I personally don't care if people have a newer version or not and I think that you and fravaccaro know the risks, but then I see bunch of other people who have no idea what they're doing (definitely the vocal ones in those threads) and they are going to ruin it for the rest. We've seen how mad had some people gotten over the tablet fiasco, so I can only imagine how would it be if more bricks occurred, those people turned to Jolla Care and naturally got told that it's not covered by the warranty.

The problem I have is with the threads portraying it as normal and as easy as 2-3 commands in the terminal.

2.0.2.4x is not some random build Jolla never meant for us to see. It has been released and given out with "development and community" devices. Jolla must have felt confident enough to do that, otherwise they would either not give out the devices or give them out with some older build.

For all you know, it is a random build, especially if you have the first Jolla. Let's list some facts:

This release is essential for some of the functionality of the Intex Aquafish/Jolla C (dual SIM).
The Intex phone has been quite delayed. Yes, it could be a problem on Intex's side, but since the software update hasn't been released yet, I think that Jolla is definitely to blame as well.
The Intex partnership is crucial for Jolla and every delay on their side is hurting it.
Jolla (1) is now 30 months old - it's great that we are still getting updates, but we can hardly expect it to be a priority for the company, especially in their financial situation.
Guys who have installed the new release report newer hardware adaptation version for Jolla (1).
I haven't seen any of the important bug reports (non-functioning sound recorder (https://together.jolla.com/question/136851/20245-bug-new-call-recording-feature-records-silence/), bricked device, no alarm sound (https://together.jolla.com/question/136835/alarm-clock-no-sound20243/), screen wakeup (https://together.jolla.com/question/136804/20245-bug-background-network-change-wakes-up-the-screen/) being reported by the Jolla C owners.

I am pretty sure Jolla C/Aquafish was the target device for this release and the optimizations for Jolla (1) will follow, but it is not made for it and since there are changes needed in the hardware adaptation, bricks and other problems are more than likely.

EDIT: Here you go, my conclusion is spot on. (https://together.jolla.com/question/136850/i-kindly-ask-to-avoid-bug-reports-for-20243/?answer=136929#post-id-136929)


Calling 2.0.2.4x bug reports on TJC "spam" and "useless" smacks of Dave999's style. Unless told otherwise, I assume that Jolla appreciates the reports exactly because it is a pre-early release. They even reply to some of those reports.


I can only speak for myself, but if I had an app on Github and someone built a version on OpenRepos after each of my commits and then people reported a dozen of issues after each of those commits, I would be pretty unhappy about the situation. Either way, it I could not tell people "don't report bugs", because I would not want to be rude and I would still appreciate more experienced eyes on my code. But like in other cases, 90% of the issues raised would likely come from people unfamiliar with the code or the difference between commits and releases, so I would probably stop commiting publicly which would be bad for me (no code overview) and for those who know how to build it and want to see new features while knowing it's not a final version.

Why would I stop?

I would not want regular people to have bad experience with my app - if I install an app and it works poorly, I don't give it a second chance very often.
If I tried to reply to all those bug reports, it would take me more time than coding.
If I did not reply to them, people would turn away and wouldn't report bugs once a real testing version is released.

[pichlo]

EDIT: Here you go, my conclusion is spot on. (https://together.jolla.com/question/136850/i-kindly-ask-to-avoid-bug-reports-for-20243/?answer=136929#post-id-136929)

Interesting. My reading of that post is that my conclusion was spot on :)

EDIT:
Re-reading your last post, I think you refer to the line above the one I quoted. In which case I fully agree with you. I was referring to this:

2.0.2.4x is not some random build Jolla never meant for us to see. It has been released and given out with "development and community" devices. Jolla must have felt confident enough to do that, otherwise they would either not give out the devices or give them out with some older build. Or release the devices with whatever build but not make the build accessible for anyone else. In short, they could have done a lot of things but they did not deem it necessary.
Calling 2.0.2.4x bug reports on TJC "spam" and "useless" smacks of Dave999's style. Unless told otherwise, I assume that Jolla appreciates the reports exactly because it is a pre-early release. They even reply to some of those reports.


This is not to say that I would encourage people to rush into random updates. Please only do that if you are willing to accept the risk and do not do it if you need your Jollas for anything important. But if you use them only for playing and do not mind losing your data, I don't see why not.

They even use the exact same words. It is almost uncanny ;)

[nodevel]

Interesting. My reading of that post is that my conclusion was spot on :)

:)

I meant my conclusion about how it is not a release Jolla meant to see on Jolla (1) or Jolla Tablet, as it is mainly targeted for Jolla C. I'm sure now that the first Jolla C devices are out, they will try to adapt it to Jolla (1) as well.

And I take it they appreciate the 2.0.2.43 bug reports from Jolla C (I haven't seen many of those yet).

EDIT: Reading your edit, I think we pretty much much agree. I was merely trying to take a more uncompromising stance in order to discourage the less experienced from installing these updates. I'm not sure if those will read such long posts, though :D

[nthn]

A) spoils all surprises
If you use software for the surprises, I guess it must get boring really quickly. Maybe spoiling surprises is also not always a bad thing, either (in fact, I recall reading that spoilers actually enhance rather than diminish enjoyment of whatever was spoiled). I don't think many people would complain getting the surprise spoiled that the new update deletes all your files when you connect to the internet, either.

With Jolla, I feel like living on the edge all the time, like hurtling at 90 mph down a narrow country lane with a 40 mph speed limit. Anything can happen at any time. Installing an unofficial release is like speeding up from 90 to 95 mph: it increases the risk but not that much.
Ha!

[objectifnul]

Just for information, my device was also bricked after upgrade from Saimaa to Taalojärvi failed then recovery mode/factory reset failed too after having returned "Recovery procedure terminated SUCCESSFULLY! Now cleaning up..." (then nothing happened until I removed the battery, two hours later).

Recovery mode now unavailable. No device detected on USB.

Submitted a ticket at Zendesk, but they are in vacation from June 18 until August 1st. Ticket closed automatically. So we have one and a half month with zero customer support.

Anyway I should have done like for previous upgrades: factory reset FIRST (after back-up of course). Fortunately I do have a back-up of /home and /etc.

[coderus]

Try this: http://pastebin.com/dWwdkwyx :)

[fravaccaro]

I tried this procedure too but unluckily my pc can't detect the phone (maybe it can't go to fastboot mode) :/

EDIT

I found this tools for Xiaomi devices stuck on QDL 9008 mode. Would it work even for Jolla, given the right partition table?

http://forum.xda-developers.com/mi-2/orig-development/flashtools-miflash4linux-recovery-qdl-t3036730

[nieldk]

Well, looking at this

forum.xda-developers.com/showthread.php?p=33017800#post33017800

And we have the partition layout, we can create the needed xml file.

The mbn files, located in /boot may be useful also

rpm.mbn, tz.mbn, emmc_appsboot.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn

And these .hex files
/system/etc/firmware/cyttsp_8064_mtp.hex
/system/etc/firmware/cyttsp_8960_cdp.hex

[fravaccaro]

So I guess I need a working Jolla to extract those files, don't I?

[nieldk]

Or, a friendly share

If im not beaten, will do tomorrow ;)

[fravaccaro]

That would be great, thanks :) Take your time ;)

[nieldk]

Look what I found

https://mega.nz/#!k4dgwSKa!NyAbM6tJOOI8bS8KOsaQ-uH_UsGZdvjTgjJe9m8DLv4

[fravaccaro]

What a coincidence :)

Mhmm...so should I use the content of /boot with https://github.com/aureljared/unbrick_8960 or this http://forum.xda-developers.com/showthread.php?t=2263391 ?

http://imgur.com/SOzYMZG

[nieldk]

Dont know. We have a puzzle to put together.
Start with giving us output from

dmesg
lsusb

From a terminal, in linux, after you connect device to usb ...

[fravaccaro]

lsusb shows:

Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

while dsmesg outputs:

[342062.964718] usb 2-4: new high-speed USB device number 6 using ehci-pci
[342063.092797] qcserial 2-4:1.0: Qualcomm USB modem converter detected
[342063.093020] usb 2-4: Qualcomm USB modem converter now attached to ttyUSB0

unbrick_8960 seems to correctly recognize the device (but of course it outputs the devices it has the bits from).

Having a quick look at unbrick.sh it just ls the folders in the devices folders, so we may easily add jolla to that list. The hexmbn may also contain something useful to us (just guessing).

[nieldk]

lsusb shows:

Bus 002 Device 006: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

while dsmesg outputs:

[342062.964718] usb 2-4: new high-speed USB device number 6 using ehci-pci
[342063.092797] qcserial 2-4:1.0: Qualcomm USB modem converter detected
[342063.093020] usb 2-4: Qualcomm USB modem converter now attached to ttyUSB0

unbrick_8960 seems to correctly recognize the device (but of course it outputs the devices it has the bits from).

Having a quick look at unbrick.sh it just ls the folders in the devices folders, so we may easily add jolla to that list. The hexmbn may also contain something useful to us (just guessing).

Yes, looks doable. We need to use QPST tool to generete an image from the mbn files, as he links to.

[fravaccaro]

Mhmm

C:\Users\Utente\Desktop\jolla\rom>emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M

C:\Users\Utente\Desktop\jolla\rom>-f = 8660_msimage.mbn
-x = partition_boot.xml
-s = 1073741824
-t =
-f : Beginning image build...
-x : Parsing partition description file...
CExParsePartition
-x : error parsing partition description file: Document error on element type "root" and name/value "<image> tag no longer supported"



EDIT The error is gone following this thread http://forum.xda-developers.com/showthread.php?t=2136738&page=43 but still no file's been created, I get an "failed to connect to qpst server" error.

[nieldk]

Mhmm

C:\Users\Utente\Desktop\jolla\rom>emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M

C:\Users\Utente\Desktop\jolla\rom>-f = 8660_msimage.mbn
-x = partition_boot.xml
-s = 1073741824
-t =
-f : Beginning image build...
-x : Parsing partition description file...
CExParsePartition
-x : error parsing partition description file: Document error on element type "root" and name/value "<image> tag no longer supported"



EDIT The error is gone following this thread http://forum.xda-developers.com/showthread.php?t=2136738&page=43 but still no file's been created, I get an "failed to connect to qpst server" error.

I believe that is because driver is not installed and/or the serialport for the Jolla is not configured in QPST tool.

[balta]

Hey, did you find a solution? I'm stuck at the same situation... :(

(and by the way I was still at 2.0.1.11)

[ganpat]

my jolla is bricked too....have the latest version.... the phone wont start on pressing the power button. unable to go to recovery mode or fast mode either. just the LED blinks once if I connect to charger without battery. that's it.

[fravaccaro]

Unluckily I'm stuck at the partition boot xml file.

[shinchim0]

any update on it? I face the same issue, phone bricked.....

should I said "welcome to the party"? lol

anyway, hope you guys can figure it out a way to bring jolla phone to life again

[nieldk]

Unluckily I'm stuck at the partition boot xml file.

Tricky ...
Takes a bit of math, but, since we know the partition layout (names, sizes, offsets ...) it should be possible to hack together

[nieldk]

Also, it's possible we need another version of qpsttools

[Amboss]

well, seems I am in this club too since this morning. My phone got unresponsive and panicked, i rebooted but it never came up again. Dead brick, except this qualcomm USB modem thingy showing in dmesg.

Is there any solution to this? btrfs-balancing issue?

EDIT say: And I am not on any EA, just official release, can't lookup version number obviously ;)

[smatkovi]

i had the same issue, but instead of rebooting i took the battery out

well, seems I am in this club too since this morning. My phone got unresponsive and panicked, i rebooted but it never came up again. Dead brick, except this qualcomm USB modem thingy showing in dmesg.

Is there any solution to this? btrfs-balancing issue?

EDIT say: And I am not on any EA, just official release, can't lookup version number obviously ;)

[Tsippaduida]

Sounds a bit like what happened when I issued halt from the command line (long time ago). Had to give proper airing to the battery. After 15 minutes airing I reinserted the battery and Jolla woke up. But you have probably tried this already.

[Amboss]

yep, did try this kinda all day now.

[Amboss]

Just a small update:
I contacted jolla and they want me to send it in for reflash. Instructions are to send an email to mobylife.fi and then send the device. But mobylife doesn't answer the mail, so I am reluctant to send my precious Jolla without confirmation.