Active Topics
-
Porting apps to Leste (32)
to Maemo 7 / Leste by Arno_11 - 4 days, 3 hrs ago -
[ANNOUNCE] CSSU-thumb thread - stable Thumb2 on N900 (2,264)
to Maemo 5 / Fremantle by panjgoori - 5 days, 21 hrs ago -
Full linux distros on Sailfish OS (254)
to SailfishOS by qoh - 6 days, 19 hrs ago - more...
D.Cent |
2012-02-27
, 21:22
|
|
Posts: 99 |
Thanked: 42 times |
Joined on Jan 2011
@ Germany
|
#221
|
Originally Posted by codix
No, don't do that - it will corrupt your system (as you can see for yourself!).
|
|
2012-02-27
, 21:29
|
|
Posts: 4 |
Thanked: 0 times |
Joined on Feb 2012
|
#222
|
Originally Posted by D.Cent
Why? Everything works fine.
No, don't do that - it will corrupt your system (as you can see for yourself!).
+ It's the only way you can update the device under certain circumstances.
Last edited by codix; 2012-02-27 at 21:41.
|
|
2012-02-27
, 21:31
|
|
Posts: 617 |
Thanked: 338 times |
Joined on Mar 2011
|
#223
|
Originally Posted by jleholeho
You better start a thread here because people are too excited with the new update so they don't pay attention .
I don`t believe it...
my N9 rebooted after unsuccesful downgrade via NaviFirm and the app menu suddenly got back...I can sroll down again and work with my folders...
but the KEYBOARD is still not there...
No active input method to choose, installed input methods (0)...???
|
|
2012-02-27
, 21:35
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#224
|
Hi everybody,
Just a little question, I updated my N9 to PR1.2 with WinFlasher, about one hour ago, and the N9 hasn't still rebooted, it is currently with a black screen and a flashing white led.
Do I have to worry?
Thanks for the help.
Just a little question, I updated my N9 to PR1.2 with WinFlasher, about one hour ago, and the N9 hasn't still rebooted, it is currently with a black screen and a flashing white led.
Do I have to worry?
Thanks for the help.
|
|
2012-02-27
, 21:44
|
|
Posts: 4 |
Thanked: 0 times |
Joined on Feb 2012
|
#225
|
Originally Posted by romu
Hi everybody,
Just a little question, I updated my N9 to PR1.2 with WinFlasher, about one hour ago, and the N9 hasn't still rebooted, it is currently with a black screen and a flashing white led.
Do I have to worry?
Thanks for the help.
another question: where did you get the firmware for flashing?
|
|
2012-02-27
, 21:44
|
|
Posts: 314 |
Thanked: 107 times |
Joined on Feb 2012
@ Bratislava, Slovakia
|
#226
|
There`s PR1.2 on NaviFirm??
I have NF1.6 and I can`t see that...
I have NF1.6 and I can`t see that...
|
|
2012-02-27
, 21:49
|
|
Posts: 198 |
Thanked: 82 times |
Joined on Oct 2011
@ Dubrovnik, Croatia
|
#227
|
OTA update for Austrian product code
OTA update NOT for Slovenian product code
OTA update for Croatian product code
guess product code of mine!... #&'%$#(')#...
OTA update NOT for Slovenian product code
OTA update for Croatian product code
guess product code of mine!... #&'%$#(')#...
|
|
2012-02-27
, 21:53
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#228
|
Originally Posted by jleholeho
Yep, you're right. I was stupid enough to reflash the PR1.1
There`s PR1.2 on NaviFirm??
I have NF1.6 and I can`t see that...
But my question remains.
|
|
2012-02-27
, 21:54
|
|
Posts: 7 |
Thanked: 1 time |
Joined on Feb 2012
|
#229
|
Originally Posted by darrenup
Have U tried royster70 tips
I can't install the update, I'm receiving the message:
Update Failed
Updated Interrepted
try again
Cancel.
When I clic on try again the process take about 5 min then the same message. somebody knows why?
Forgive my english
Originally Posted by royster70
I got the same error, but that actually seems to work for me (installing @ 29%)
I was getting a similar error getting stuck 0% and then failing with the OTA update.
In addition to disabling the repositories after seeing the comment earlier in the thread (I had a app for that- MeeCatalog), I also disabled developer mode in security - and that seemed to work for me and the update worked.
I disabled repositories using MeegCatalog and switched off dev. mode in one go - so I cannot be sure if this is was the change needed to get the update to continue.
Edit: Succsess!!
Last edited by Swerige; 2012-02-27 at 22:23. Reason: Succsess
|
|
2012-02-27
, 22:02
|
|
Posts: 18 |
Thanked: 23 times |
Joined on Nov 2011
@ Singapore
|
#230
|
Hi all, I think/hope I may have figured out a way to force update to PR1.2.
I need help testing my theory. I need the following
1. A product code which successfully updated to PR 1.2.
2. For the N9 in (1), in Terminal, give me the contents of the following command
> ls /etc/apt/sources.list.d
(You will see a file that looks like aegis.ssu-keyring-XXX.list. Take note of this file name)
> cat /etc/apt/sources.list.d/aegis.ssu-keyring-XXX.list
(Change XXX appropriately. Please send me the contents of this cat command)
Once I get these, will keep you guys posted whether I am successful
My current is PR1.1 Singapore 005 variant
I need help testing my theory. I need the following
1. A product code which successfully updated to PR 1.2.
2. For the N9 in (1), in Terminal, give me the contents of the following command
> ls /etc/apt/sources.list.d
(You will see a file that looks like aegis.ssu-keyring-XXX.list. Take note of this file name)
> cat /etc/apt/sources.list.d/aegis.ssu-keyring-XXX.list
(Change XXX appropriately. Please send me the contents of this cat command)
Once I get these, will keep you guys posted whether I am successful
My current is PR1.1 Singapore 005 variant