Reply
Thread Tools
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#1
So after having a 16GB since forever, I recently gave it away & obtained a 64GB as a secondary smartphone.
Few Qns, since I've not been a ultra heavy Maemo/MeeGo user for 12mth+ now:

(1)
Is there a way to tell exactly what batch my N9 came from? (i.e. when/where it was manufactured)

(2)
How to tell which PR I have? (I knew once, but my memory's like a sieve)
I suspect PR1.0 looking at the version no: 10.2011.34-1.299.1_PR_299

(3)
To flash to PR1.3, do I seriously have to do so in Windows, OS X definitely not a option?
(I'm pretty certain of the answer to this, but I resent having to install Windows just to complete one task >.>)

I'll be disappointed if this N9 turns out to be from a much older batch than my other N9, but I guess in-the-end it shouldn't matter too much.

(4)
Finally, one thing I'm noticing about this new N9 that (somewhat) irks me...
The entire left & right sides of the glass overlay rise up quite sharply, so the thumb does not travel smoothly from the body over to the screen.
The bottom & top ends of the glass overlay do not exhibit this same problem*, the transition from body to display is nice & smooth.
Also the buttons seem to be way more recessed & of lesser quality, especially the power button.
I'm quite sure my N9 16GB was never like this, alas I don't have it on hand right now to compare.

That's it for now, but I'm sure many other questions will pop into my head over the coming days, thanks comrades!

P.S.
For those on the hunt for one again, I've a list of retailers, telcos, & telco resellers in Oz that may still have at least 1x N9 16GB or 64GB

*actually the top does a tiny bit, & the entire RHS of the overlay isn't as bad as the LHS

Last edited by jalyst; 2013-06-13 at 15:21.
 

The Following User Says Thank You to jalyst For This Useful Post:
Posts: 7 | Thanked: 7 times | Joined on May 2012
#2
I am unsure of how to tell which batch it comes from, but it definitely is not necessary to use Windows to flash.

(In fact, I had some weird corruption issues last weekend with my 64GB N9, and I successfully reflashed PR1.3 through OS X.)

If the alignment of the screen and the sharp rise is bothersome, you could try lifting the screen out and re-seating it to see if you can get a better fit.
 

The Following User Says Thank You to rpcameron For This Useful Post:
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#3
 

The Following 2 Users Say Thank You to thedead1440 For This Useful Post:
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#4
Navifirm's no longer usable right... reviewing this atm...
http://talk.maemo.org/showthread.php...16#post1172316

Found alt. way to obtain image but seems way too broken up (Northern EU black 64gb i.e. PR_001):
http://mrcrab.net/nokia/Nokia_N9.htm...n=40.2012.21.3
And not yet clear if one can get content/eMMc images from there too.

*EDIT* All good, I see them both now....
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin

Why's the PR code different for the eMMC image, it says 40.2012.13-7, not 40.2012.21-3 like the fw image, is that the latest release for eMMC image?
Can anyone point to the naming schema for all the major releases for both the fw & eMMC/content images? I knew it once, but alas forget.

In the guide here, is everything after this heading up-to-date & applicable to OSX: PREPARE TO FLASH

Bed Time.

Last edited by jalyst; 2013-06-13 at 19:10. Reason: bed time.
 

The Following User Says Thank You to jalyst For This Useful Post:
Loepoes's Avatar
Posts: 56 | Thanked: 25 times | Joined on Apr 2012 @ Cape Town,South Africa
#5
Originally Posted by jalyst View Post
Navifirm's no longer usable right... reviewing this atm...
http://talk.maemo.org/showthread.php...16#post1172316

Found alt. way to obtain image but seems way too broken up (Northern EU black 64gb i.e. PR_001):
http://mrcrab.net/nokia/Nokia_N9.htm...n=40.2012.21.3
And not yet clear if one can get content/eMMc images from there too.

*EDIT* All good, I see them both now....
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin

Why's the PR code different for the eMMC image, it says 40.2012.13-7, not 40.2012.21-3 like the fw image, is that the latest release for eMMC image?
Can anyone point to the naming schema for all the major releases for both the fw & eMMC/content images? I knew it once, but alas forget.

Still like to know what batch my N9's from, i.e. when/where it was made, if anyone has a clue, please do advise.
Got myself a second 16GB N9 yesterday as most retailers are now getting rid of their old stock.
Mine was still on PR 1.0 and as I was unable to update myself I took it to the local Nokia care place where they're going to update to PR 1.3.
It is a Finnish made phone, you can find place of manufacture on the sim tray.
 

The Following User Says Thank You to Loepoes For This Useful Post:
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#6
Yeah mine's Chinese, I know that much, but it'd be cool to know exact plant & more importantly; how old or recent the batch was that it came from...
I think mine's PR1.0 (I'm not 100% sure until I know the naming schema for all the releases), so that at least tells me that mine's probably from quite a early batch (grumble).
I can't recall if the newest batches shipped with PR1.2/1.3, or whether we had to update to them from PR1.1/1.2, if the latter, then mine being PR1.0 doesn't necessarily prove it's from a "1.0 batch".

Night.

Last edited by jalyst; 2013-06-13 at 19:27.
 

The Following User Says Thank You to jalyst For This Useful Post:
Posts: 646 | Thanked: 1,124 times | Joined on Jul 2010 @ Espoo, Finland
#7
Originally Posted by jalyst View Post
Why's the PR code different for the eMMC image, it says 40.2012.13-7, not 40.2012.21-3 like the fw image, is that the latest release for eMMC image?
Yeah, during preparation of PR 1.3 the last image for eMMC was the 13-7 (there was no further change of contents afterwards so they kept that version).
 

The Following 2 Users Say Thank You to minimos For This Useful Post:
Posts: 1,033 | Thanked: 1,013 times | Joined on Jan 2010
#8
Originally Posted by jalyst View Post
Yeah mine's Chinese, I know that much, but it'd be cool to know exact plant & more importantly; how old or recent the batch was that it came from...
I think mine's PR1.0 (I'm not 100% sure until I know the naming schema for all the releases), so that at least tells me that mine's probably from quite a early batch (grumble).
I can't recall if the newest batches shipped with PR1.2/1.3, or whether we had to update to them from PR1.1/1.2, if the latter, then mine being PR1.0 doesn't necessarily prove it's from a "1.0 batch".

Night.
Mine was a Vietnamese country variant and shipped with PR1.2 when I bought it last year. Exact manufacturing date is printed on my box which said June 2012, don't remember the day. I bought it in end of July.
 

The Following 2 Users Say Thank You to patlak For This Useful Post:
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#9
Originally Posted by patlak View Post
Mine was a Vietnamese country variant and shipped with PR1.2 when I bought it last year.
Exact manufacturing date is printed on my box which said June 2012, don't remember the day. I bought it in end of July.
Lucky bugger, I suspect mine's much, much, older...
Where on the box does it say this? It certainly doesn't say it on my box.

Originally Posted by jalyst View Post
Can anyone point to the naming schema for all the major releases for both the fw & eMMC/content images? I knew it once, but alas forget.
*BUMP* this! Thanks.

Last edited by jalyst; 2013-06-14 at 06:53.
 
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#10
All done, piece of piss, forgot how easy it all was:

jalyst-rMBP:N9_Flash root# flasher -i
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 29, device address 7.
Device serial number is N/A
Found device RM-696, hardware revision 1601
NOLO version 2.0.49
Version of 'sw-release': DFL61_HARMATTAN_10.2011.34-1.299.1_PR_299
Success

************************************************** ************************************************** ************************************************** *

jalyst-rMBP:N9_Flash root# flasher -f -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 29, device address 7.
Device serial number is N/A
Found device RM-696, hardware revision 1601
NOLO version 2.0.49
Version of 'sw-release': DFL61_HARMATTAN_10.2011.34-1.299.1_PR_299
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 30720 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 29, device address 7.
Device serial number is
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_001
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 85 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 2959 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1986 kB/s]
[x] rootfs [finished 100 % 1170282 / 1170282 kB 12220 kB/s]
Updating SW release
Success

************************************************** ************************************************** ************************************************** *

jalyst-rMBP:N9_Flash root# flasher -f -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin -F 29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin --flash-only=mmc
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 29, device address 7.
Device serial number is
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_001
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image tar skipped
Image config skipped

Battery level 87 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] mmc [finished 100 % 1627219 / 1627219 kB 21006 kB/s]
Success

************************************************** ************************************************** ************************************************** *

jalyst-rMBP:N9_Flash root# flasher -R
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 29, device address 7.
Device serial number is
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Success

As luck would have it, my cable broadband has become very unreliable for the 1st time in mths, just when I need it to be reliable for at least a few days, grrrr.

Last edited by jalyst; 2013-06-14 at 06:58.
 
Reply

Tags
nokia n9


 
Forum Jump


All times are GMT. The time now is 08:44.