Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 6 hrs, 19 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 10 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 23 hrs ago -
n770 youtube video (0)
to General by nmdv - 5 days, 22 hrs ago - more...
marcaurell |
2012-12-06
, 16:58
|
|
Posts: 33 |
Thanked: 11 times |
Joined on Aug 2012
|
#21
|
Originally Posted by eljonker
PLEASE PLEASE post a Guide for downgrade
|
|
2012-12-06
, 18:48
|
|
Posts: 1,067 |
Thanked: 2,383 times |
Joined on Jan 2012
@ Finland
|
#22
|
Originally Posted by marcaurell
hopefully nobody will ever release a guide for that, since if you mess up with CAL too much, you can end up with permant brick of your device (even nokia care is not able reflash perm bricked devices). (And if there is ever PR upgrade it would force Nokia to lock CAL even in normal mode)...
PLEASE PLEASE post a Guide for downgrade
__________________
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
Last edited by rainisto; 2012-12-06 at 18:52.
| The Following User Says Thank You to rainisto For This Useful Post: | ||
|
|
2012-12-06
, 22:31
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#23
|
That's actually the reason inception is more dangerous than open mode.
I was thinking about this one day, what lead me to this was some time back somebody had a weird problem, IMEI of the device was corrupted.
The fact that cal is locked when running in open mode helps to protect from random faults that could wreck havoc by writing something to a critical area by mistake. In normal mode, under inception/opensh there is no such protection.
I was thinking about this one day, what lead me to this was some time back somebody had a weird problem, IMEI of the device was corrupted.
The fact that cal is locked when running in open mode helps to protect from random faults that could wreck havoc by writing something to a critical area by mistake. In normal mode, under inception/opensh there is no such protection.
|
|
2012-12-06
, 22:46
|
|
Posts: 1,067 |
Thanked: 2,383 times |
Joined on Jan 2012
@ Finland
|
#25
|
Originally Posted by pali
Well in short there is no way.
@rainisto: is there any way how to repair perm bricked devices? and who can that if nokia care not?
However if you have done backup from your CAL then you could in theory restore CAL from your backup. BUT before you get your hopes up, only Nokia employees with R&D certificate can backup&restore CAL areas, and all the people that could generate R&D certificates for N9 have already left the company.
And factory line jtag flasher, but its quite unlikely that you get access inside the production factory (and those factory lines are already ramped down anyways).
So in short if you happen to mess up your CAL, you can throw the device in garbage for spare parts and buy a new phone.
__________________
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
|
|
2012-12-07
, 08:55
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#26
|
Originally Posted by rainisto
This is propably the only viable way of doing it. BTW, I thought Nokia Service shops would be able to flash the device via JTAG interface...? I mean if there is some repairs done to the RFU the phone needs to be recalibrated, right?
And factory line jtag flasher, but its quite unlikely that you get access inside the production factory (and those factory lines are already ramped down anyways)
For JTAG flashing you actually do not need fancy equipment, just a cheapy ~200 eur USB/JTAG adapter and some soldering skills is required
|
|
2012-12-07
, 10:58
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#27
|
Ok, so I must be very very carefull to not damage CAL...
|
|
2012-12-07
, 11:03
|
|
Posts: 1,225 |
Thanked: 1,905 times |
Joined on Feb 2011
@ Quezon City, Philippines
|
#28
|
Originally Posted by rainisto
This would break lock code functionality. Or, they could store the lock code in a file, which is arguably a lot more insecure than storing it in an obscure database no one's bothered to write a library to interface with.
(And if there is ever PR upgrade it would force Nokia to lock CAL even in normal mode)...
Originally Posted by juiceme
IIRC the IMEI is stored on the BB5 chip, which runs completely separate from the SoC. All the SoC side of the system does is talk to the BB5 over the OMAP's SSI interface.
I was thinking about this one day, what lead me to this was some time back somebody had a weird problem, IMEI of the device was corrupted.
Something else may have been broken, but it sure isn't corruption of the IMEI.
And if the N9 is just like the N900, you could probably flash_erase /dev/mtd1 and CAL would be able to partially rebuild itself (kids, don't try this at home!)
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
|
|
2012-12-07
, 11:14
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#29
|
OK, if that is so, then where is the MFG calibration data for RFU stored?
I kinda thought it would be in CAL (that it is an abbreviation for CALibration, but maybe I was mistaken...)
I kinda thought it would be in CAL (that it is an abbreviation for CALibration, but maybe I was mistaken...)
|
|
2012-12-07
, 11:33
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#30
|
Originally Posted by Hurrian
Did you already tried to erase CAL in N900?? Or why are you sure, that N900 CAL can rebuilt it itself?
And if the N9 is just like the N900, you could probably flash_erase /dev/mtd1 and CAL would be able to partially rebuild itself (kids, don't try this at home!)
| The Following User Says Thank You to pali For This Useful Post: | ||