View Full Version : [HOWTO] Comprehensive Firmware Flashing Guide for N9
What do you expect with this step? For me it seems the only big differences are the preinstalled apps? Which you can change yourself! And language and all the other stuff is also in this image!
So whats the main gail in flashing an european fw? (I don't say it works cause I actually don't know)
The serial number corresponds to the firmware image localisation. .. So if you type in a serial from a chinese version N9 you can expect to get a chinese firmware image ;)
just choose another image...
darylaselp
2013-12-20, 15:44
My Nokia n9 can't boot I stucked on Nokia logo when I turn on the device,I accidentally remove the roots in terminal using this code.
devel-su
Root me
rm -rf \
What can I do now..
Need help...
Pls help me..:(
Reflash with flasher.
http://talk.maemo.org/showthread.php?t=82693
Follow that thread's instructions.
kikujiro0208
2013-12-21, 01:40
I am currently using 2 N9 China versions. Last month, I have flashed one into a 005 Asia Pacific version with success...
Flashing is no rocket science and is fun too...
dak_sriv
2013-12-23, 18:40
My Nokia n9 can't boot I stucked on Nokia logo when I turn on the device,I accidentally remove the roots in terminal using this code.
devel-su
Root me
rm -rf \
What can I do now..
Need help...
Pls help me..:(
OMG look into what commands you execute m8... xD
I need help related to flashing N9.
I have done it multiple times before but suddenly I am facing issue with getting N9 in flash mode.
This issue started after I installed Phoenix and tried dead phone flash with it, but since it didn't work I uninstalled that along with all other nokia softwares(connectivity drivers etc.)
Now I am unable to get N9 in flash/update mode.
Whenever I put command and press enter and connect phone. It doesnt go in update mode, it displays USB icon and later big battery charging icon. Earlier it used to vibrate and used to start flashing.
I am guessing that somehow flashing driver is not getting installed.
I tried to install it manually by using option 3 in this link but that also didnt help.
http://everythingn9.com/update-pr1-2-nokia-n9/
Even pressing power button for over 8 seconds is not working.
I am really not having any clue about how to resolve this.
Please help.
I need help related to flashing N9.
I have done it multiple times before but suddenly I am facing issue with getting N9 in flash mode.
This issue started after I installed Phoenix and tried dead phone flash with it, but since it didn't work I uninstalled that along with all other nokia softwares(connectivity drivers etc.)
Now I am unable to get N9 in flash/update mode.
Whenever I put command and press enter and connect phone. It doesnt go in update mode, it displays USB icon and later big battery charging icon. Earlier it used to vibrate and used to start flashing.
I am guessing that somehow flashing driver is not getting installed.
I tried to install it manually by using option 3 in this link but that also didnt help.
http://everythingn9.com/update-pr1-2-nokia-n9/
Even pressing power button for over 8 seconds is not working.
I am really not having any clue about how to resolve this.
Please help.
I guess you are using windows, right?
Probably your windows USB drivers are botched, you did something or other and managed to get the drivers misaligned. (common thing with windows, I wonder why it is so easy to break it?)
@juiceme Thanks for reply, yes I am using Windows 7. This is drivers related issue but I am unable to understand how to fix it.
I do have Linux Mint but I don't use it much nowadays.
Is there anyway to remove all N9 related drivers and start all over again?
I had installed Phoenix and then uninstalled it along with nokia connectivity drivers. This issue started after that.
Please check attached screenshot.
peterleinchen
2013-12-25, 08:33
Uninstall everything (EVERYTHING) related to Nokia (suite, connectivity, flasher, map loader, whatever , ...).
Download PC Suite Cleaner exe
Run it as admin.
Reboot.
Run it once more.
Install flasher (in case you like also Nokia Suite) again.
Run flasher as admin
Connect N9
(if it does not flash, disconnect, power off and connect once more).
Common problem with Windoze ... :eek: (at least some versions!)
OMG look into what commands you execute m8... xD
LOL thats an effective way ....
@peterleinchen I will try as you have suggested but most surprising thing was I also faced similar issue when I tried in kubuntu on same laptop.
It gave following error.
It worked finally after doing steps as mentioned by peterleinchen.
Many Thanks.
wrong section - moved post
Hello,
I tried to follow the recommended steps to flash, using a Mac. This is what I get:
Bogdans-MacBook-Pro:059H2M6_RM-696 NDT 64GB ROW BLACK root# flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin -f
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 1501
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 30069 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. 1501
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 93 %, 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 2922 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 1762 kB/s]
[x] rootfs [finished 100 % 1170282 / 1170282 kB 12270 kB/s]
Updating SW release
Success
Bogdans-MacBook-Pro:059H2M6_RM-696 NDT 64GB ROW BLACK
root# flasher -f -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin -F DFL61_HARMATTAN_40.2012.13-7.NOMAPS_EMMC_NOMAPS.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. 1501
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 93 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] mmc [finished 100 % 261587 / 261587 kB 19949 kB/s]
Success
Bogdans-MacBook-Pro:059H2M6_RM-696 NDT 64GB ROW BLACK
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. 1501
Server implements softupd protocol version 1.8
Success
Bogdans-MacBook-Pro:059H2M6_RM-696 NDT 64GB ROW BLACK root#
Success as far as the eye can see, but when I boot the device I get yellow waring sign and an error like:
"Device not working properly
Try updating the device software with Nokia Software Updater...
Security problem (aegis-exec):
/usr/lob/libaegis_crypto.so.1.0.0"
Any idea on how to fix this ? I tried the suggested NSU on Windoze, but it fails at the end of the update - after it reboots the device gets hung on the NOKIA logo.
Also I should mention, that flashing on Mac seems to randomly fail at various percentage of completion. The run above is a rare struck of luck, after a few retries.
What's the normal usage for "flasher -R" ? Should the phone be left connected to USB after it boots ? I read at http://talk.maemo.org/showpost.php?p=1121975&postcount=1 that it should be yanked out of USB.
Any help would be much appreciated.
Thanks !
Interresting update to recovery mode
From
https://together.jolla.com/question/3612/release-notes-software-update-2-1025/
Does it apply also to the N9 ?
Does it apply also to the N9 ?
####¤%!! No, wrong sections, should have been in Jolla flashing thread :)
Guess I need some weekend somewhere, with no kids, wife - just devices and compilers :)
Hi all,
I decided to write here, because I have a big problem.
My N9 (product code: 059J203) suddenly stopped reading the SIM cards two days ago. Moreover, system is freezing and IMEI info is not visible.
I decided to reflash the phone. This is the log:
C:\Program Files\Nokia\Flasher>flasher.exe -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin -f
flasher 3.12.1 (Oct 6 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...
Device is in Sync and connect mode, sending ADL reboot.
ERROR: ReadFile(65540) GetOverlappedResult() error 2 timeout 4975 ms
Unable to detect flashing interface: standing by for device reboot.
Suitable USB interface (bootloader) not found, waiting...
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 9276 kB/s)
Suitable USB interface (phonet) not found, waiting...
ERROR: CreateFile, error = 5
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
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 92 %, 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 ]
[_] cmt-algo [init 100 % 789 / 789 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1376 kB/s]
[_] rootfs [writing 0 % 28672 / 1170282 kB 1766 kB/s]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[f] cmt-algo [init 0 % 789 / 789 kB NA ]
[-] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1376 kB/s]
[x] rootfs [finished 100 % 1170282 / 1170282 kB 10085 kB/s]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 6] Finishing in error state with status 1
========================================
ERROR: Failed to flash images
C:\Program Files\Nokia\Flasher>flasher.exe -F DFL61_HARMATTAN_40.2012.13-7.CENTRALEUROPE_EMMC_CENTRALEUROPE.bin -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Image SW version <none>
Image cert-sw not present
Image cmt-2nd not present
Image cmt-algo not present
Image cmt-mcusw not present
Image xloader not present
Image secondary not present
Image kernel not present
Image moslo not present
Image rootfs not present
Image tar not present
Image config skipped
Battery level 92 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] mmc [finished 100 % 1463443 / 1463443 kB 10908 kB/s]
Success
Do you have any ideas what can I do?
Thanks.
Same problem here, since NOKIA released the cmt update...
So Nokia bricked my N9 with their last update :-/
I flashed the phone with a higher higher release number (I think swiss firmware version), but also there I wasn't able to correctly flash cmt.
I think, I need a way to completely erase and restore the whole device but I don't think this will ever be possible.
Same problem here, since NOKIA released the cmt update...
So Nokia bricked my N9 with their last update :-/
What cmt update???
so many N9s faced same issue - suddenly faced SIM error without any real reason. Unable to flash cmt.
Similar issues I have read about N900.
Can any expert from Nokia MeeGo team can help here? Any way to fully fix this? downgrade again?
There must be some way.
If someone can come up with idea, it will help many users here. I am ready to donate/pay some $ for getting my N9 fixed.
rainisto
2013-12-29, 11:29
Hello,
Any help would be much appreciated.
Thanks !
Well 1st of all, you should never ever user --flash-only=mmc, why are you flashing with 2 seperate commands? Right way to do full flash is to use just one command.
flasher -f -F main.bin -F emmc.bin -R
If you get those aegis security errors even after that command, then your RAM chip is having hardware errors, and you can say goodbye to that device.
rainisto
2013-12-29, 11:38
so many N9s faced same issue - suddenly faced SIM error without any real reason. Unable to flash cmt.
Similar issues I have read about N900.
Can any expert from Nokia MeeGo team can help here? Any way to fully fix this? downgrade again?
There must be some way.
If someone can come up with idea, it will help many users here. I am ready to donate/pay some $ for getting my N9 fixed.
My guess would be that you have used some non-standard flasher like Phoenix to break it (quite many people have ****ed their device with Phoenix), when in fact you should always just use flasher 3.1.12.
Have you tried cold flashing with normal flasher, since thats your only hope vs throwing it into the trashcan? Paste cold flash output?
rainisto
2013-12-29, 11:42
@peterleinchen I will try as you have suggested but most surprising thing was I also faced similar issue when I tried in kubuntu on same laptop.
It gave following error.
those commands need to be runned as root, or with sudo.
those commands need to be runned as root, or with sudo.
Yes, realised that later. Issue is resolved now.
My guess would be that you have used some non-standard flasher like Phoenix to break it (quite many people have ****ed their device with Phoenix), when in fact you should always just use flasher 3.1.12.
Have you tried cold flashing with normal flasher, since thats your only hope vs throwing it into the trashcan? Paste cold flash output?
Well, I wasn't able to flash with Phoenix at all :) Only flasher.
Strange thing is chinese cmt flash worked sometimes , like 100% success. And that only works now. Otherwise if I use any other files for cmt then I get SIM error. Sometimes after flashing chinese cmt, I was able to use phone for 2 days before issue appearing again.
I think I had tried cold flash earlier.(not sure) but I can try again.
But I really curious to know cause and if someone can fix it, if someone can take it up as challenge :)
rainisto
2013-12-29, 15:58
Well, I wasn't able to flash with Phoenix at all :) Only flasher.
Strange thing is chinese cmt flash worked sometimes , like 100% success. And that only works now. Otherwise if I use any other files for cmt then I get SIM error. Sometimes after flashing chinese cmt, I was able to use phone for 2 days before issue appearing again.
I think I had tried cold flash earlier.(not sure) but I can try again.
But I really curious to know cause and if someone can fix it, if someone can take it up as challenge :)
After flashing chinese cmt, there is no way to flash europen cmt ever never again. Your can only flash chinese cmt the remaining life for that device. So 0% change of flashing 001 variant.
It has been stated meny times, that flashing chinense cmt is non-reversible action, that is the only thing that cannot be reversed.
Any other variant can be reversed and even downgraded. So the big failure happened the second the chinese cmt was flashed to the device.
But you can try reflashing chinese cmt if you download the china variant image.
Thanks for reply, I flashed chinese cmt after trying 26 other variants :)
But since now I know it the only thing which can't be reversed, can you please tell me how I was able to successfully flash it some times and not successfully most of the times ?
I mean what are factors for successful flashing ?
I have swiss(480) variant as main flash file.
marmistrz
2013-12-29, 16:34
Can't we just
flasher -f -F main.bin -F emmc.bin -R
or
flasher -f -F main.bin
flasher -f -F emmc.bin -R
?
Thanks for reply, I flashed chinese cmt after trying 26 other variants :)
But since now I know it the only thing which can't be reversed, can you please tell me how I was able to successfully flash it some times and not successfully most of the times ?
I mean what are factors for successful flashing ?
I have swiss(480) variant as main flash file.
I'd imagine your troubles are caused by the fact that you have chinese CMT and swiss rootfs.
Even as in theory they could be compatible in practice you propably can have problems when you mix-n-match components from different country variants.
It is just as @rainisto has said many times, you should not mess up with flasher unless you really know what you are doing, there are some things you cannot reverse once you do them
This includes; delibrately flashing incompatible components delibrately erasing/overwriting your MTD partitions burning your CPU with overclocking burning your flash eraseblocks with unwise swap partitioning ...maybe something else?
Well 1st of all, you should never ever user --flash-only=mmc, why are you flashing with 2 seperate commands? Right way to do full flash is to use just one command.
flasher -f -F main.bin -F emmc.bin -R
If you get those aegis security errors even after that command, then your RAM chip is having hardware errors, and you can say goodbye to that device.
rainisto, thank you for your reply.
Unless I'm missing something, I believe the 2-step flashing, using that --flash-only=mmc option is shown as the "Comprehensive reset" method in the original post of this thread - which is supposed to be the authoritative guide for flashing. Given the random errors I've been getting while flashing, I think splitting them in 2 gives them a better chance to succeed individually.
I'm pretty sure I tried the usage you suggested above, with the same end result.
Eventually I managed to flash it using Nokia Software Updater, after making sure I closed the Nokia Suite (which I believe was trying to use the same USB port, causing troubles). But although the phone boots I'm getting frequent freezes and spontaneous reboots. You may be right about some hardware failures. Either that or Maemo took a turn for the worse from the days of Nokia 770, which was the last time I've used it.
No wonder Elop jumped off the burning platform. Maybe he had a similar experience. Brand new device. Makes for a nice paperweight with a clock.
I'd imagine your troubles are caused by the fact that you have chinese CMT and swiss rootfs.
Even as in theory they could be compatible in practice you propably can have problems when you mix-n-match components from different country variants.
It is just as @rainisto has said many times, you should not mess up with flasher unless you really know what you are doing, there are some things you cannot reverse once you do them
This includes; delibrately flashing incompatible components delibrately erasing/overwriting your MTD partitions burning your CPU with overclocking burning your flash eraseblocks with unwise swap partitioning ...maybe something else?
Thanks for reply, but as i said since default variants failed to flash to to some reasons I tried various others and ended up with combo of swiss+chinese.
Thing which I am unable to understand is - how these SIM error appear out of nowhere suddenly?
rainisto
2013-12-31, 15:18
Thanks for reply, I flashed chinese cmt after trying 26 other variants :)
But since now I know it the only thing which can't be reversed, can you please tell me how I was able to successfully flash it some times and not successfully most of the times ?
I mean what are factors for successful flashing ?
I have swiss(480) variant as main flash file.
This has been explained in several posts in the forum. Each variant binary has a creation timestamp for the firmware certificate and for cmt certificate. So some variants have been created later than the other so they have never timstamps and allow flashing 'as system think its a upgrade) (cmt firmware is same in european variants, so it always succeeds, untill someone flashes chinense cmt (which was always created later than european/vanilla cmt, so it never can be downgraded because of timestamp certificate check).
rainisto
2013-12-31, 15:27
rainisto, thank you for your reply.
Unless I'm missing something, I believe the 2-step flashing, using that --flash-only=mmc option is shown as the "Comprehensive reset" method in the original post of this thread - which is supposed to be the authoritative guide for flashing. Given the random errors I've been getting while flashing, I think splitting them in 2 gives them a better chance to succeed individually.
Well the 'authorative' guide is somewhat lacking on that part, and it doesn't even tell how to do cold flashing (last time when I read the guide).
PS. if your wondering why to believe me and not the guide, I can say that I've read the source code of the flasher and bootloader, so I have pretty good idea what lower level is doing in Harmattan. And I've flashed hundreds of Harmattan phones back in the days when I was still working for Nokia Meego R&D. (I've even flashed the device over serial cable back in the days before there was USB flasher available for it) :)
This has been explained in several posts in the forum. Each variant binary has a creation timestamp for the firmware certificate and for cmt certificate. So some variants have been created later than the other so they have never timstamps and allow flashing 'as system think its a upgrade) (cmt firmware is same in european variants, so it always succeeds, untill someone flashes chinense cmt (which was always created later than european/vanilla cmt, so it never can be downgraded because of timestamp certificate check).
rainisto, so what can I do with my problem?
http://talk.maemo.org/showpost.php?p=1401246&postcount=1021
Thanks for reply.
Ok, finally I gave up and sold my N9 for about $160, not bad for device which can't function as phone.
May be in future I will pick another if I can get it cheap.
Thanks to all who tried to help me to understand and resolve issues :)
I flashed my N9 about 2 months ago. Then last month the phone crashed in Whatsup and cannot be started again. So I want to reflash it again. But it failed. Here is the log from the flasher. Anyone can help? Thx.
C:\Program Files\Nokia\Flasher>flasher -i
flasher 3.12.1 (Oct 6 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...
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Success
C:\Program Files\Nokia\Flasher>flasher -f -F main.bin -F emmc.bin --flash-only=mmc
flasher 3.12.1 (Oct 6 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...
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 18337 kB/s)
Suitable USB interface (phonet) not found, waiting...
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_006
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 77 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[_] mmc [init 0 % 32768 / 1829147 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[f] mmc [init 0 % 32768 / 1829147 kB NA ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not exec '/sbin/dosfslabel /tmp/sudmmcqlZFyn/internal0p1 "Nokia N9"'
mmc: Unable to remove mount point '/tmp/sudmmcqlZFyn/mnt/home': No such file or
directory
mmc: Could not remove mount directory /tmp/sudmmcqlZFyn/mnt: No such file or dir
ectory
[Pipe 1] Finishing in error state with status 1
========================================
ERROR: Failed to flash images
thedead1440
2014-01-04, 10:00
sasacy,
If you want to reflash it, why are you flashing only the emmc?
Instead issue the following command:
flasher -f -F main.bin -F emmc.bin --no-preserve
Once successful, either plug out your cable and boot it up or issue "flasher -R" to do so...
rainisto
2014-01-04, 10:12
rainisto, so what can I do with my problem?
http://talk.maemo.org/showpost.php?p=1401246&postcount=1021
Thanks for reply.
Hardware broken, so trashcan or sell device as parts.
Hi thedead1440,
Honestly I don't know what is the correct way. Anyway I tried your suggestion but failed. What should I do?
C:\Program Files\Nokia\Flasher>flasher -f -F main.bin -F emmc.bin --no-preserve
flasher 3.12.1 (Oct 6 2011) Harmattan
Warning: --no-preserve is not recommended, instead use erase commands
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_006
Image moslo not present
Image tar skipped
Image config skipped
Battery level 90 %, 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 ]
[_] cmt-mcusw [init 84 % 6050 / 6050 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1194 kB/s]
[_] rootfs [init 0 % 20480 / 978983 kB NA ]
[ ] mmc [pending 0 % 0 / 0 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error
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 3087 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 1194 kB/s]
[f] rootfs [init 0 % 21504 / 978983 kB NA ]
[-] mmc [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
Update content failed to verify against cert: SW certificate not updated
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not exec 'tune2fs -L rootfs /tmp/sudmmc35Gf4L/internal0p2'
mmc: Could not remove mount directory /tmp/sudmmc35Gf4L/mnt: No such file or dir
ectory
[Pipe 4] Finishing in error state with status 1
========================================
ERROR: Failed to flash images
sasacy,
If you want to reflash it, why are you flashing only the emmc?
Instead issue the following command:
flasher -f -F main.bin -F emmc.bin --no-preserve
Once successful, either plug out your cable and boot it up or issue "flasher -R" to do so...
Hi,
Getting "Device not working properly" message when trying to boot my N9
as shown here: http://talk.maemo.org/showpost.php?p=1263477&postcount=1
This happened right after uninstalling warehouse app and re-booting (as recommended by Custodian for re-installing a newer version).
I suspect I did not wait long enough for uninstall to complete before rebooting, but not sure.
I tried using the recommended method of "flasher --enable-rd-mode ...",
but the phone still displays the message during boot.
Is there anything that can be done to salvage the phone in this state, without resorting to a full re-flash that will wipe out the data?
Any help is appreciated.
Will some experts can give me insights? Thx.
Hi thedead1440,
Honestly I don't know what is the correct way. Anyway I tried your suggestion but failed. What should I do?
C:\Program Files\Nokia\Flasher>flasher -f -F main.bin -F emmc.bin --no-preserve
flasher 3.12.1 (Oct 6 2011) Harmattan
Warning: --no-preserve is not recommended, instead use erase commands
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_006
Image moslo not present
Image tar skipped
Image config skipped
Battery level 90 %, 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 ]
[_] cmt-mcusw [init 84 % 6050 / 6050 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1194 kB/s]
[_] rootfs [init 0 % 20480 / 978983 kB NA ]
[ ] mmc [pending 0 % 0 / 0 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error
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 3087 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 1194 kB/s]
[f] rootfs [init 0 % 21504 / 978983 kB NA ]
[-] mmc [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
Update content failed to verify against cert: SW certificate not updated
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not exec 'tune2fs -L rootfs /tmp/sudmmc35Gf4L/internal0p2'
mmc: Could not remove mount directory /tmp/sudmmc35Gf4L/mnt: No such file or dir
ectory
[Pipe 4] Finishing in error state with status 1
========================================
ERROR: Failed to flash images
rainisto
2014-01-09, 15:44
Will some experts can give me insights? Thx.
That error usually happens only in 2 cases:
a) your main.bin has corrupted bit, please redownload PR006 image (maybe check md5checksum) and try again
b) your flash memory has broken down, and then your out of luck.
Tried download firmware and flash again but same problem.
Seems my N9 is dead.
That error usually happens only in 2 cases:
a) your main.bin has corrupted bit, please redownload PR006 image (maybe check md5checksum) and try again
b) your flash memory has broken down, and then your out of luck.
muscat.lover
2014-01-14, 04:24
Hello!
After flash my " N9 " can't enable two things :
1- device lock
2- developer mode
:(:confused:
rainisto
2014-01-20, 19:14
Hello!
After flash my " N9 " can't enable two things :
1- device lock
2- developer mode
:(:confused:
Are you sure that your device date and clock is on current time. As enabling developer mode will fail if date is not correct.
I tried to flash my n9 and although it flashes successfully I get a nokia logo with a tool showing bootreason: sw_rst or pwr_key
so I guess I have a hardware problem and there is no way I can make it boot. I have only flashed -f F main.bin since I was hoping to preserve my data.
anyone had the same issue?
Hi,
My N9 went off network all of a sudden and when I tried to reboot to sort it out, it has been showing SIM card error. Tried flashing with different combinations but stuck in the same place. Phone boots but gives SIM error. Trying different SIMs does not help.
I have gone through this entire thread but unable to find a solution. If I could get some help on steps that I could take on trial-and-error and hopefully revive the phone, that would be great. Many thanks.
Snipped output from flashing:
C:\Program Files\Nokia Flasher>flasher -i
flasher 3.12.1 (Oct 6 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...
Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Success
C:\Program Files\Nokia Flasher>flasher -f -F DFL61_HARMATTAN_40.2012.21-3_PR_LEG
ACY_001-OEM1-958_ARM.bin
flasher 3.12.1 (Oct 6 2011) Harmattan
...
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
MTC_POWER_OFF not received
CMT RFS failed
[Pipe 7] Finishing in error state with status 1
========================================
ERROR: Failed to flash images
Full output is posted here:
https://www.dropbox.com/s/lql59p5uv4g6jmb/Flasher%20output.txt
Any additional information I could provide to get some troubleshooting help. Many thanks to all for your time.
Aiyush
mikecomputing
2014-02-06, 20:01
I did have two N9 sold one last week. The one left is locked to TRE Sweden so cant flash firmware I have on my HD.
And I can't find the damn TRE locked firmware on the internet. Since the mirror site has been closed also.
I hate Nokia for killing N9 if only sailfish and 3G worked on n9 I would be happy. Because my Jolla also broken.
So back at my N900 until my Jolla get returned(still waiting for jolla care send me info how to ship it)
chilango
2014-02-06, 20:19
ofcourse you can flash other fw with greater number. i made it multiple times. or tre sweden is the greatest number?
my fw version was country variant 420 and for less i found a 430 number.
chilango
2014-02-08, 19:47
It seems that the downloadpage for flasher is offline.
Someone have the flasher for debian or a new link?
http://www.swagman.org/juice/flasher_3.12.1_i386.deb
chilango
2014-02-08, 23:30
Perfect. Thanks
sorry for asking, it may be posted somewhere, but I will ask anyway, is there any chance to backup files, so you can flash backup?
Hi.
I'm trying to reflash my device with DFL61_HARMATTAN_40.2012.21-3_PR_009 but I cannot download this version cause the server is down and I only have
version DFL61_HARMATTAN_40.2012.21-3_PR_001 to flash:
Anyone knows any other sources to download?
Thanx in advance.
O.K. I'm back with my experience.
The problem was that I was trying to downgrade the software version.
In order to get the appropriate version I started Nokia Suite and clicked on 'reinstall' option. This downloaded the latest version of the firmware in a folder called Ovi inside my user's folder.
This is the file I used to reflash the device with flasher under linux, becuase Nokia Suite was complaining about problems doing backup of messages/applications etc.
Now, back to the duty of setting everything as it was in the first place .... :(
If someone needs this file, I can provide it :D
Regards.
EgyptRocks265
2014-02-27, 08:23
hey guys does anyone possibly have the 64bit windows version of flasher since mirror site is down and i just got new pc :/ please !!:confused:
https://www.google.com/search?q=WinFlasher_3.12.1.exe
peterleinchen
2014-02-28, 22:19
After downloading from any internet download site one should at least check md5sum of flasher package.
Needs to be updated with md5sums (of course), but do not have to files atm. So of anybody wants to, go ahead ...
xaccrocheur
2014-03-02, 15:26
O.K. I'm back with my experience.
The problem was that I was trying to downgrade the software version.
In order to get the appropriate version I started Nokia Suite and clicked on 'reinstall' option. This downloaded the latest version of the firmware in a folder called Ovi inside my user's folder.
This is the file I used to reflash the device with flasher under linux, becuase Nokia Suite was complaining about problems doing backup of messages/applications etc.
Now, back to the duty of setting everything as it was in the first place .... :(
If someone needs this file, I can provide it :D
Regards.
Pasko, I don't have access to a windows machine, so I'm unable to DL any image (NaviFirmEx is down, all sites are down, it's cold out there) so please yes, make this file available somewhere.
From the first post: Navifirm has restricted access so get images from here (http://mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696)
This site is still active (albeit currently very slow for some reason), and still has the firmware files on it.
xaccrocheur
2014-03-02, 18:49
From the first post:
This site is still active (albeit currently very slow for some reason), and still has the firmware files on it.
Solved (http://talk.maemo.org/showthread.php?t=92813). Thank you, Eztran.
Hi all :D
I downloaded these two big files:
61A8E22C_DFL61_HARMATTAN_40.2012.13-7.DACH_EMMC_DACH
D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM
Now I would like to checksum these files. It's been a while I am looking for it but I cannot manage to find it. Anyone to help me ?
Thanks already,
pmeuh
-edit-
Solution: there are some VPL where you can find the CRC file ;)
for those having problems flashing their rootfs
I have now an N9 that have this problem
i got the "mmc: sfdisk returned status 1" error
also when using the moslo kernel to mount the eMMC
I got errors on accessing the partitions
I remembered i had a similar problem happen on my last N900 (flashing the rootfs failing)
the solution was to remove the battery for a one day or two
and the retry flash and it worked
the N900 was also because of battery drain
so somehow the battery cause the eMMC to not work proprely
I have disconnected the battery from my 16G N9 ( I bought another one with 64G ;) )
and I'll report in 2 days
Well I have flashed my nokia several time with the right main.bin and emmc.bin but it doesn't seem to boot. It stays on nokia logo and do nothing else. All these after replacing the main speaker. Any suggestions before I sell it for spare parts? Thanks
Have you tried disabling watchdogs & enaling RD mode?
how to disable watchdogs?
just updated my n9 last evening anf now it wont start , it just keeps showing the nokia screen thats it ...any suggestions what i might be doing wrong ?
Greendts
2014-03-18, 07:08
Please add more details, it is very difficult to assess what could be wrong... What exactly did you update etc...
i just updating Meego phone software..huhuhu
i just update the MeeGo phone software..
i just update the MeeGo phone software..
Just as @Greendts said, please provide more details.
"I just updated MeeGo phone software" <<-- This means NOTHING!
- What version did you have?
- What version did you update to?
- OTA or wired flashing?
- What is your variant?
- etc...
- etc...
Version that i have 20.2011.40.4 = PR1.1
Version 40.2012.21.3 = PR1.3
OTA
the Variant i dont remember maybe 003..
Version that i have 20.2011.40.4 = PR1.1
Version 40.2012.21.3 = PR1.3
OTA
the Variant i dont remember maybe 003..
OK, obviously something went amiss with the OTA update. That can happen even though it is fairly robust method.
Since OTA failures cannot be undone/redone, what you need to do now ir so reflash it manually.
Tell me the variant code (it is written under the simtray) and I will give you download links to the firmware & emmc images.
Variant Code: 059J245
That's "RM-696 NDT Malaysia Black 16GB", right?
The files are here:
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0312/7076665785/A6D5F456_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_005-OEM1-958_ARM.bin
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0312/7076666921/59BEC3BC_DFL61_HARMATTAN_40.2012.13-7.SEAP_EMMC_SEAP.bin
Yes! :D
Thanks..
after i click that link..then what? :confused:
Yes! :D
Thanks..
after i click that link..then what? :confused:
OK, so this thread got moved to the correct place, to discussion of flashing a N9 device. :D
Now, you need to read this thread from the beginning, there is advice on how to flash your device in the first posts.
MarcAnton
2014-03-18, 09:45
Yes!
Thanks..
after i click that link..then what?
if you never flashed N9 manually, the easiest way is reinstalling firmware with Nokia Suite.
can i ask u again if I dont knw the step @juiceme?
@MarcAnton
the problem is.. my phone cannot turn ON..so i cannot use USB Mode..as far as i knw..hehe
if you never flashed N9 manually, the easiest way is reinstalling firmware with Nokia Suite.
@MarcAnton how can i reinstalling using Nokia Suite?
can i ask u again if I dont knw the step @juiceme?
Sure, but it is fairly straightforward to do.
I assume you propably have some sort of Windows machine? The biggest trick is to install the flasher there, I guess. The rest is easy.
I am sorry I cannot help you with the Windows installation, since I only have Linux machines. In case you have a Linux machine, I can help you better with that :)
what do you mean by Windows Machine? is it like Windows 7? :confused:
what do you mean by Windows Machine? is it like Windows 7? :confused:
Yes, to flash N9 you need a computer to connect to the USB port of your phone.
It is possible to use WinXP, Win7, Linux, maybe MAC.
rainisto
2014-03-18, 13:01
for those having problems flashing their rootfs
I have now an N9 that have this problem
i got the "mmc: sfdisk returned status 1" error
also when using the moslo kernel to mount the eMMC
I got errors on accessing the partitions
I remembered i had a similar problem happen on my last N900 (flashing the rootfs failing)
the solution was to remove the battery for a one day or two
and the retry flash and it worked
the N900 was also because of battery drain
so somehow the battery cause the eMMC to not work proprely
I have disconnected the battery from my 16G N9 ( I bought another one with 64G ;) )
and I'll report in 2 days
Or you can just use --no-preserve or repartition by hand with sfdisk with ubiboot.
i already follow all the instruction.. and the flasher said it was success.. but why i still can't turn on my phone?
i already follow all the instruction.. and the flasher said it was success.. but why i still can't turn on my phone?
How does it behave now?
Which flasher commadn did you use?
it's still same..
i just follow the first thread command..
it's still same..
i just follow the first thread command..
You mean, you used commmand "flasher -f -F main.bin", right?
That is the safest flasher option, but unfortunately does not fix all things.
Now, there are at least 2 ways to proceed:
You can either wipe the device all clean, and lose your data, or attempt to rescue data first.
Which way to do, depends on if there is valuable data to hou in the phone.
Rescuinc is possible, but requirds knowledge.
OMG!! maybe my phone broke alredy because i just type main.bin and emmc.bin without changing it.. OMG OMG OMG..
right now i just follow the instruction and chnge the "main.bin" to (comprehensive command) and change the "emmc.bin" with (059J245) but still nothing change.. please help me..Huhuhuhu
@juiceme i want wipe clean. i dont hve valuable data in that phone.. how to do it?
@juiceme i want wipe clean. i dont hve valuable data in that phone.. how to do it?
See the 1st post.
I am travelling now, with intermittent net access, cannot help much.
@juiceme i dont knw what to do.. could u please tell me what should i need to do..i still dont get it..huhuhu
just now i do the flashing by using "replace operating system" command and 059J245 as emmc.bin command.. is the command I am using is correct?:confused:
@juiceme what is this?
59BEC3BC_DFL61_HARMATTAN_40.2012.13-7.SEAP_EMMC_SEAP.bin
DFL61_HARMATTAN_22.2011.44-2_PR_LEGACY_006-OEM1-958_ARM.bin
are this the command?
:confused:
@juiceme.. Thanks GOD my phone its OK now..huhuhu i dont knw what to say.. i'am very very happy right now..hahaha.. thanks again..
Hi, i accidentally downloaded and flashed my n9 with version 40.2012.21-3.280.04.1_PR_280 and I cant revert back to my orginal version due to downgrade disallowed. Is there a higher version than this image in English?. Its frustrating to change the settings everytime i flash my phone
Hi, i accidentally downloaded and flashed my n9 with version 40.2012.21-3.280.04.1_PR_280 and I cant revert back to my orginal version due to downgrade disallowed. Is there a higher version than this image in English?. Its frustrating to change the settings everytime i flash my phone
For what country/operator does that PR_280 seem to be?
For what country/operator does that PR_280 seem to be?
Varian Name : Rm-696 Ndt Mea4 Black 64gb
As a few times I struggled to convert between product name (059XXXX), variant (NNN), variant name, etc, I went on the mrcrab.net pages, fetched with wget all description pages related to PR.1.3 variants and armed with awk & perl I generated this csv file that for each variant contains in order:
- product name (e.g. 059L5D0)
- variant (e.g. 232)
- name (e.g. N9 RM-696 Country Variant Switzerland CH Black 16GB V1)
- variant ID (e.g. 7134691506, not much used)
- fiasco file (DFL61_HARMATTAN_40.2012.21-3.232.05.2_PR_LEGACY_232_ARM_RM-696_PRD_signed.bin)
- emmc file (DFL61_HARMATTAN_40.2012.21-3.ALPS.14_EMMC_ALPS.bin)
http://pastebin.com/zhJSn6K1
It's a csv file so you can grep it or import it in a spreadsheet.
theking2
2014-03-24, 20:04
None of the links seem to work anymore.
How can I recover from a "Device not working properly" error?
Please somebody provide a solution as to why my phone keeps getting stuck at 0% and 32768kb when trying to flash either rootfs or emmc.
Thanks in advance!
fredddurs
2014-03-28, 18:25
Hi everyone, My english is very poor, but I try to be accurate.
I'm trying to flash my N9 but ultimately always throws me an error. My black 16GB N9 is. I'm going to leave some links to see pictures of the error.
I'm from Venezuela.
https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tLzdEYnA5eH cucG5nFMAHFKYIABYAEgA&s=4QKSGtIuljW_clyAfViFJ5VQHvEVG9HNZUh31Kkkp6E
:confused::confused:
peterleinchen
2014-03-28, 18:48
Did you change partition layout, then this one should be corrected by giving the additional parameter
--no-preserve
Let us know if it worked out.
fredddurs
2014-03-28, 19:20
Sorry, then how would the command to flash?.
Could you copy it here?.
peterleinchen
2014-03-28, 19:43
Just add the bold part of: additional parameter
--no-preserve
What about letting us know how you did it? And answering my question about partition layout (moslo kernel / ubiboot)?
But rereading your picture I may be wrong and you should check your firmware download again (maybe broken). Otherwise I fear a broken eMMC. But go ahead ...
fredddurs
2014-03-28, 19:48
Just add the bold part of:
What about letting us know how you did it? And answering my question about partition layout (moslo kernel / ubiboot)?
But rereading your picture I may be wrong and you should check your firmware download again (maybe broken). Otherwise I fear a broken eMMC. But go ahead ...
ok, I'll check and to try again.
peterleinchen
2014-03-28, 20:34
Seems like you have the same problem (http://talk.maemo.org/showthread.php?p=1418939#post1418939) :(
fredddurs
2014-03-28, 23:14
Just add the bold part of:
What about letting us know how you did it? And answering my question about partition layout (moslo kernel / ubiboot)?
But rereading your picture I may be wrong and you should check your firmware download again (maybe broken). Otherwise I fear a broken eMMC. But go ahead ...
Dude, put the command as you indicated and I have an error that is not how to solve it persists.
I'll post a picture of the MS-DOS window, then another image with the files you download to flash the phone.
https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tL3NDbkRBWG wucG5nFIQVFPQKABYAEgA&s=d-aMtIW8qY9txKEWbU2z0Lc3AQpWu6s3aMPU7nx1rJY
https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tL3FEWkZqV3 EucG5nFJAPFMwGABYAEgA&s=ftIuybGx6DTrTwZwb0NO_yH1iZMHY7kr4EfaZnAVhLQ
fredddurs
2014-03-29, 01:18
Just add the bold part of:
What about letting us know how you did it? And answering my question about partition layout (moslo kernel / ubiboot)?
But rereading your picture I may be wrong and you should check your firmware download again (maybe broken). Otherwise I fear a broken eMMC. But go ahead ...
Dude, I did as you said, and just throws me the same error .. I'll post some pictures of the MS-DOS window and the descargasdos files.
https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tL3NDbkRBWG wucG5nFIQVFPQKABYAEgA&s=d-aMtIW8qY9txKEWbU2z0Lc3AQpWu6s3aMPU7nx1rJY
https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tL3FEWkZqV3 EucG5nFJAPFMwGABYAEgA&s=ftIuybGx6DTrTwZwb0NO_yH1iZMHY7kr4EfaZnAVhLQ
fredddurs
2014-03-29, 01:38
Seems like you have the same problem (http://talk.maemo.org/showthread.php?p=1418939#post1418939) :(
My n9, I rarely dropped. Could not hit or damage any fall?
fredddurs
2014-03-29, 02:22
I had trouble downloading these 2 files from my pc with ubuntu 13.10 download does not start, but the other files if you boot to download, does anyone have that?. I'm testing with firmware Version RM-696 NDT 16GB BLACK LTA 40.2012.21.3 059J260
files:
-simlock maemo deB allowed2 3gstandard bb5 multi asic0.bin
-simlock maemo deB allowed2 3gstandard bb5 multi asic1.bin
TonyUkuk
2014-03-29, 10:43
Hi everyone, My english is very poor, but I try to be accurate.
I'm trying to flash my N9 but ultimately always throws me an error. My black 16GB N9 is. I'm going to leave some links to see pictures of the error.
I'm from Venezuela.
https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tLzdEYnA5eH cucG5nFMAHFKYIABYAEgA&s=4QKSGtIuljW_clyAfViFJ5VQHvEVG9HNZUh31Kkkp6E
:confused::confused:
hi to Venezuela :)
what is product code of your n9? also, is your n9 now working, i mean is it booting - can you go to settings>about product? if not please make flasher -i and put here pic.
Also you can see there a barcode and when you are reading this barcode with an barcode scanner (I did it with my N8) then you get the IMEI and product code as well - sometimes the product code wrighted on sim-holder not correct,the rigthest way is :
1) to scan with barcode scanner the barcode in settings>productinfo (if phone working)
2)if phone not working,the way is NSS - check it with this program,you can also check in dead mode. i'll put here instructions if needed. I see that rootfs failed to flash, thats' mean 99% problem in firmware(version or wrong product code),first think we must check that the firmware with which we are trying to flash N9 is 100% right.
fredddurs
2014-03-29, 14:41
hi to Venezuela :)
what is product code of your n9? also, is your n9 now working, i mean is it booting - can you go to settings>about product? if not please make flasher -i and put here pic.
Also you can see there a barcode and when you are reading this barcode with an barcode scanner (I did it with my N8) then you get the IMEI and product code as well - sometimes the product code wrighted on sim-holder not correct,the rigthest way is :
1) to scan with barcode scanner the barcode in settings>productinfo (if phone working)
2)if phone not working,the way is NSS - check it with this program,you can also check in dead mode. i'll put here instructions if needed. I see that rootfs failed to flash, thats' mean 99% problem in firmware(version or wrong product code),first think we must check that the firmware with which we are trying to flash N9 is 100% right.
Ok, I also think it is the firmware, I think there was an error downloading, and right now the'm downloading again with a download manager. Another thing, when I pull the sim-card, I notice that there is a code back and reads: (059J260) is black and 16Gb version LatinAmerica.
TonyUkuk
2014-03-29, 19:55
Ok, I also think it is the firmware, I think there was an error downloading, and right now the'm downloading again with a download manager. Another thing, when I pull the sim-card, I notice that there is a code back and reads: (059J260) is black and 16Gb version LatinAmerica.
yea, but as i sad it can be so that the code on sim-holder not right. i have had this problem with my last (3rd) N9 :) so it must be correctly find out the product code of your N9.
also i always downloaded the firmwares directly, i mean without download managers, just directly with browser - i think it is safest way in my practice.
fredddurs
2014-03-29, 23:26
hi to Venezuela :)
what is product code of your n9? also, is your n9 now working, i mean is it booting - can you go to settings>about product? if not please make flasher -i and put here pic.
Also you can see there a barcode and when you are reading this barcode with an barcode scanner (I did it with my N8) then you get the IMEI and product code as well - sometimes the product code wrighted on sim-holder not correct,the rigthest way is :
1) to scan with barcode scanner the barcode in settings>productinfo (if phone working)
2)if phone not working,the way is NSS - check it with this program,you can also check in dead mode. i'll put here instructions if needed. I see that rootfs failed to flash, thats' mean 99% problem in firmware(version or wrong product code),first think we must check that the firmware with which we are trying to flash N9 is 100% right.
The only lights N9 shows nokia logo, white LED flashes a few times and turns off. I think I could clear the emmc, I say this because now when on, displays the nokia logo and then displays a warning message text. Here is the image with the "flasher-i" phone.
https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tL3JRSkt1cE suanBnFNYMFJAEABYAEgA&s=0ot9Gegp_RtugV6u3UbJURnsEv2zanrR5Snl_2139K8
TonyUkuk
2014-03-30, 09:51
The only lights N9 shows nokia logo, white LED flashes a few times and turns off. I think I could clear the emmc, I say this because now when on, displays the nokia logo and then displays a warning message text. Here is the image with the "flasher-i" phone.
https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tL3JRSkt1cE suanBnFNYMFJAEABYAEgA&s=0ot9Gegp_RtugV6u3UbJURnsEv2zanrR5Snl_2139K8
so your N9 booting but OS not working,not openning. hm...
by the way,from your pic https://o.twimg.com/2/proxy.jpg?t=HBgeaHR0cDovL2kuaW1ndXIuY29tLzdEYnA5eH cucG5nFMAHFKYIABYAEgA&s=4QKSGtIuljW_clyAfViFJ5VQHvEVG9HNZUh31Kkkp6E I see there is attemting to change country variant - DFL61....001 & DFL61...006. Thats why i'm strongly recommending to findout 100% correct product code for your N9. If you know the program Phoenix (with 2012.24.000.48366 version) with this program you can find out the product code of your N9,all instroctions are in the help section of this program.
Also do all flashes with these commands
flasher -f -F firmware.bin --erase-user-data=secure
flasher -f -F firmware.bin -F emmc.bin --flash-only=mmc
Hi.
I just got a bricked device I cannot bring back to life.
When I run "flasher -i" I get this version:
DFL61_HARMATTAN_40.2012.21-3.480.04.1_PR_480
However, the device has code 059K126 corresponding to a cyan 16GB from Thailand.
Now I'm a bit confused:
I've been trying all day with the site mrcab.net but seems to be down....I also tried with NaviFirm, but it provides version:
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_005-OEM1-958_ARM
which is obviously not working.
What country variant has the device inside?
Which one shoud I try to fix it?
Regards.
480.04.1 is the Switzerland 64GB/black variant 059L5D4
Here are the dowdnload links:
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1210/1013/7099258288/3290ADCC_DFL61_HARMATTAN_40.2012.21-3.480.04.1_PR_LEGACY_480_ARM_RM-696_PRD_signed.bin
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1210/1013/7099259904/09F33F15_DFL61_HARMATTAN_40.2012.21-3.ALPS.15_EMMC_ALPS.bin
O.K.
I finally managed to flash an image but the problem is:
The device won't boot at all. It gets stuck with the Nokia Logo.
This is the output I'm getting.
Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.454.6_PR_454
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 11958 kB/s)
Suitable USB interface (phonet) not found, waiting...
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1507
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3.454.6_PR_454
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped
Battery level 19 %, 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 3137 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 1214 kB/s]
[x] rootfs [finished 100 % 1193453 / 1193453 kB 4652 kB/s]
Updating SW release
Success
Am I missing something?
Regards
First, why are you flashing 21-3.454.6 to your device?
That is the Vietnam variant (059L9X6, 059L9K0, 059M024, 059L9J9, 059N151)
Second, as your flasher says "success" it should indeed be so. How does the device behave?
What flasher commands did you try, did you try to flash it clean? From your output I see you probably only flashed the OS.
Hi.
The vietnam version is the only one which is being accepted by the device without problems.
Now I'm testing the next command:
LAPTOP2:~$ sudo flasher -f -F /home/fernando/Descargas/43AD05DD_DFL61_HARMATTAN_40.2012.21-3.454.6_PR_LEGACY_454_ARM_RM-696_PRD_signed.bin -c
And this was the result:
Got HWID: RM-696:1507
Suitable USB interface (bootrom) not found, waiting...
USB device found at bus 001, device address 040.
Device identifier: (null) (SN: N/A)
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 bf
fb 62 c1 3b f4 d7 12 52 f2 7b 1c 0b 23 9c c3 43
5c 25 0b 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
Sending 2nd image (26112 bytes)... done.
Sending ping... pong.
Sending ape-algo (7273728 bytes)... done.
Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 001, device address 041.
Device identifier: 357923XXXXXXXXX (SN: N/A)
Error claiming USB interface: Device or resource busy
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1507
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3.454.6_PR_454
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped
Battery level 88 %, 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 3377 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 1907 kB/s]
[x] rootfs [finished 100 % 1193453 / 1193453 kB 10822 kB/s]
Updating SW release
Success
I don't know why, after returning success, the device is stuck with the Nokia logo.
I have also tried with the '--erase-user-data', '-c' and flashing EMMC image: it works in the same way.
Regards.
peterleinchen
2014-04-11, 20:56
To me it looks like you "managed" to downgrade from 480 (Switzerland, the absolutely highest FW version). but the device does not "honor" it. :(
Under normal circumstances a downgrade is prohibited, so please elaborate how you "managed" to do so.
If I were you I would try once more with 480 variant (works fine in Europe), but ...
Hi.
For some reason the device is refusing to flash anything different from the Vietnamesse version.
However, I'm now checking the posibility of a broken partition table, since I don't know the exact origin of the device.
Regards.
peterleinchen
2014-04-12, 10:11
With this (http://talk.maemo.org/showpost.php?p=1421018&postcount=52) information I would guess yes your partition layout is broken.
Please search a 16GB Vanilla image matching your needs (it does not matter if same code, just you will have different maps on it. IIRC there should be a 'global' vanilla image out that even does not have any maps on it. Flash it with the option --no-preserve. This will wipe the full device andthe flash again the firmware (or better do it in one step).
OK.
I've been tinkering for a while with no success. :(
However, I managed to flash a ubiboot kernel (as stated in the thread to install sailfish on N9) and the device booted the ubiboot kernel.
That way I have been able to reconstruct the partition table, according to my still-working N9, then reflashed again to no avail....
Now I'm trying to go back to the Switzerland version to see if I can go ahead.....nothing, still says the Switzerland version is a downgrade ¿?
I'm starting to think I just got a brick instead of an N9 :(
Regards.
With this (http://talk.maemo.org/showpost.php?p=1421018&postcount=52) information I would guess yes your partition layout is broken.
Please search a 16GB Vanilla image matching your needs (it does not matter if same code, just you will have different maps on it. IIRC there should be a 'global' vanilla image out that even does not have any maps on it. Flash it with the option --no-preserve. This will wipe the full device and the flash again the firmware (or better do it in one step).
Thank you.
However I've been trying with the --no-preserve option and it didn't work either.
Will try it again to see what happens with the Vanilla Image.
peterleinchen
2014-04-12, 10:46
Now I'm trying to go back to the Switzerland version to see if I can go ahead.....nothing, still says the Switzerland version is a downgrade ¿?
This is impossible!??? :confused: (unless you have a PR1.2 image of course. what is the name of image?)
And what does flasher -i tell you now?
To tell you the truth, I don't know.
This is what I'm getting from 'flasher -i':
LAPTOP2:~$ sudo 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 001, device address 040.
Device identifier: 357923042601874 (SN: N/A)
Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.454.6_PR_454
Success
This is the only image that flashes without problems, but upon reboot, the screen show the logo and stays there forever....
The name of the files I'm flashing are:
43AD05DD_DFL61_HARMATTAN_40.2012.21-3.454.6_PR_LEGACY_454_ARM_RM-696_PRD_signed.bin
09F33F15_DFL61_HARMATTAN_40.2012.21-3.ALPS.15_EMMC_ALPS.bin
Being the first one the Vietnam rootfs (it is a country variant according to mrcrab.net, BTW) and the EMMC file for Switzerland the second.
Now I'm reading the thread about ubiboot for N9, since I have been able to boot the MOSLO and Ubiboot kernel sometimes, but I'm stuck....none of them is able to boot the actual OS.
Regards.
peterleinchen
2014-04-12, 19:19
That is weird.
You do have 456 installed but 480 is claimed to be a downgrade? :confused: But you had that Switzerland (480) once installed, right?
BUT the eMMC image is the one for a device with 64GB and should not be used for a 16GB afaik. This could explain the 'missing' partition.
So as I wrote earlier search a vanilla image for a 16GB device and flash it as said:
flasher -F emmc.bin -F firmware.bin -f -R --no-preserve
That is weird.
You do have 456 installed but 480 is claimed to be a downgrade? :confused: But you had that Switzerland (480) once installed, right?
Yes. The first version was 480. The seller didn't know much about this. He was selling it for parts.
BUT the eMMC image is the one for a device with 64GB and should not be used for a 16GB afaik. This could explain the 'missing' partition.
So as I wrote earlier search a vanilla image for a 16GB device and flash it as said:
flasher -F emmc.bin -F firmware.bin -f -R --no-preserve
I made it with the same results. Even tried a UAE version with number 468 (higher than 456): didn't flash either.
I think I'll try to see if Ubiboot can help. I already posted a pair of questions in the thread.
Thankyou.
Regards.
peterleinchen
2014-04-13, 11:28
It seems you still do not get me.
Find any emmc image (NOT the firmware) matching a 16GB model and flash this together with your 456 firmware image.
--
Or am I plain wrong and mixing with N900 where partition layout was written by eMMC image?
Some kind soul may confirm or correct me!
It seems you still do not get me.
Find any emmc image (NOT the firmware) matching a 16GB model and flash this together with your 456 firmware image.
--
Or am I plain wrong and mixing with N900 where partition layout was written by eMMC image?
Some kind soul may confirm or correct me!
I already tried the eMMC image corresponding to version 456 altoghether with the firmware. Got it from the mrcrab.net site. They are listed one after the other (I mean firmware and eMMC).
The flashing proccess goes ok, but the device won't boot afterwards. I'll try to post the command line logs later.
Regards
Hi.
Here are the command logs:
LAPTOP2:~$ sudo flasher -F Descargas/main.bin -F Descargas/emmc.bin -f -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 001, device address 010.
Device identifier: 357923XXXXXXXXX (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1507
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3.454.6_PR_454
Image moslo not present
Image tar skipped
Image config skipped
Charging battery, 10 % battery level (11 % required). Ctrl-c to exit
Battery level 11 %, 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 3133 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 1766 kB/s]
[x] rootfs [finished 100 % 1193453 / 1193453 kB 10889 kB/s]
[x] mmc [finished 100 % 1946679 / 1946679 kB 16556 kB/s]
Updating SW release
Success
And these are the files (main.bin is the firmware and emmc.bin is the emmc image :) )
43AD05DD_DFL61_HARMATTAN_40.2012.21-3.454.6_PR_LEGACY_454_ARM_RM-696_PRD_signed.bin
DFL61_HARMATTAN_40.2012.21-3.454.5_EMMC_454.bin
Maybe the 'Product Revision: 1507' has something to do with the downgrading issues?
If I remember correctly my 'live' device has revision 1609.
Regards.
peterleinchen
2014-04-13, 21:27
I am out of ideas. Sorry.
Only thing we did not try is to enable R&D mode with flasher. Worth a try. So please do that (commands easily to find here on TMO, even in this thread also).
I am out of ideas. Sorry.
Only thing we did not try is to enable R&D mode with flasher. Worth a try. So please do that (commands easily to find here on TMO, even in this thread also).
O.K.
I'll give it a try this afternoon.
Thank you.
Regards.
Please N9 gurus,
Im just about to spend usd150,00 on a n9 in reboot loop. I would like to know how big are the chances to end up with an expensive Brick. If it were a n900 i wouldnt think twice but i really dont have idea if the n9 is "always flashable" like her older sister.
What do you tell me ?
Thanks again! :)
fredddurs
2014-04-16, 02:32
Hey guys, new here. Even I could not solve the problem of my n9, not flashing. I'll hang some pictures again to see that review I get. I used the Phoenix nokia and nothing at all, I have also used the winflasher with the same result, the phone does not work. I use linux. I've noticed that in the process, the rootfs throws an error, and I think this sector is the one that makes the phone reboot all the time.
Remember that it is a black N9 16GB.
1)http://t.co/IdZat2c9pB
2)http://t.co/k4skmfJ3sg
3)http://t.co/bal0i7DjGz
4)http://t.co/LmoxoRrB8W
Please N9 gurus,
Im just about to spend usd150,00 on a n9 in reboot loop. I would like to know how big are the chances to end up with an expensive Brick. If it were a n900 i wouldnt think twice but i really dont have idea if the n9 is "always flashable" like her older sister.
What do you tell me ?
Thanks again! :)
The chances that you can fix it are very good but not 100%.
It would help to know what kind of reboot loop it is in, as there are differences in difficulty.
I think the price is too high, however. For a known-very-good-condition 64G device I'd pay maybe 100 eur tops.
@ALL
Successfully Flashed Hongkong N9 64gb.
To INDIA version FW.
then i have downloaded original Files also to flash cmt of Hongkong because it cant detect sim if you have INDIAN FW :)
INSTALLED NITDROID 5 Also.
Hello, I am from India as well, got myself a nokia n9 black 16gb from a dealer in hongkong on ebay last week. Realised skype, fb was missing, and ovi music login had issues with my indian id.... Saw ur post.... Can u please guide me wat files to flash.... Thanks a lot....
fredddurs
2014-04-17, 04:08
Hey guys, new here. Even I could not solve the problem of my n9, not flashing. I'll hang some pictures again to see that review I get. I used the Phoenix nokia and nothing at all, I have also used the winflasher with the same result, the phone does not work. I use linux. I've noticed that in the process, the rootfs throws an error, and I think this sector is the one that makes the phone reboot all the time.
Remember that it is a black N9 16GB.
1)http://t.co/IdZat2c9pB
2)http://t.co/k4skmfJ3sg
3)http://t.co/bal0i7DjGz
4)http://t.co/LmoxoRrB8W
Does anyone know if the sector is a rootfs file?, Which can download and use to repair the n9.
And MrCrab.net is down too!
I guess I downloaded a corrupt image. RootFS couldn't be flashed. Checked the mirror site again to find it down. Yet, the download link of the firmware image is working well. The index is gone - mrcrab!
fredddurs
2014-04-17, 13:17
And MrCrab.net is down too!
I guess I downloaded a corrupt image. RootFS couldn't be flashed. Checked the mirror site again to find it to down. Yet, the download link of the firmware image is working well. The index is gone - mrcrab!
mrcrab.net has dropped, any other option to download the firmware.??:(
mrcrab.net has dropped, any other option to download the firmware.??:(
The site is up, back again! Grab the download links soon :D
fredddurs
2014-04-17, 21:33
Friends, can you help me fix a rootfs N9?.
Friends, can you help me fix a rootfs N9?.
Sure.
Just state your problem so we understand.
fredddurs
2014-04-18, 21:51
Sure.
Just state your problem so we understand.
I'm trying to make a flashing my N9, but always throws me an error in the rootfs. Usage on Linux flasher. I downloaded the latest firmware and nothing at all, the phone will not boot and always gets the same error. The N9 one day I turn and I did not want anything more, from there I wanted to see if you flash it to work again but and accomplished nothing. I would appreciate the help. In a previous note I put pictures of the error that throws me, I'll post the links again.
1)http://t.co/IdZat2c9pB
2)http://t.co/k4skmfJ3sg
3)http://t.co/bal0i7DjGz
4)http://t.co/LmoxoRrB8W
fredddurs
2014-04-18, 21:52
And another thing friend, my English is poor. If something is not necessary to let me know.
I'm trying to make a flashing my N9, but always throws me an error in the rootfs. Usage on Linux flasher. I downloaded the latest firmware and nothing at all, the phone will not boot and always gets the same error. The N9 one day I turn and I did not want anything more, from there I wanted to see if you flash it to work again but and accomplished nothing. I would appreciate the help. In a previous note I put pictures of the error that throws me, I'll post the links again.
1)http://t.co/IdZat2c9pB
2)http://t.co/k4skmfJ3sg
3)http://t.co/bal0i7DjGz
4)http://t.co/LmoxoRrB8W
OK, the way you post the pictures is a bit difficult to read, but I see you had some errors relating to bb5 certificate handling.
Next time, could you please post a log file to some paste site (or directly here as text)
Some thoughts:
Are you sure you have downloaded the correct firmware file for your device?
Are you sure the file is OK, not corrupted when downloaded?
Did you try to wipe the device while flashing, or do you have some important data you do not want to lose?
@Fredddurs, This might come in handy to check if the files you downloaded are corrupt as juiceme said.
http://talk.maemo.org/showpost.php?p=1392281&postcount=993
I just figured out that the firmware image I downloaded was corrupt.
fredddurs
2014-04-20, 20:32
@Fredddurs, This might come in handy to check if the files you downloaded are corrupt as juiceme said.
http://talk.maemo.org/showpost.php?p=1392281&postcount=993
I just figured out that the firmware image I downloaded was corrupt.
Friend, how do I know if the firmware download is corrupt me? Should I expect any special output "crc32" command?. Could you give me an example of how the instruction?. My N9 is black model code 059j260 16Gb.
fredddurs
2014-04-20, 20:34
With what files should I run the crc32 instruction?, Should I do the check for each file?
fredddurs
2014-04-20, 20:38
OK, the way you post the pictures is a bit difficult to read, but I see you had some errors relating to bb5 certificate handling.
Next time, could you please post a log file to some paste site (or directly here as text)
Some thoughts:
Are you sure you have downloaded the correct firmware file for your device?
Are you sure the file is OK, not corrupted when downloaded?
Did you try to wipe the device while flashing, or do you have some important data you do not want to lose?
Hello friend, someone told me to use crc32 to check the downloaded firmware was corrupted, I have searched the internet and all that, but not to wait when executing the instruction with crc32. I guess that's kind instruction must "crc32 RM696_059J260_40.2012.21.3_001.vpl" and results in this: "a1cd9a23". Now as if the firmware is corrupted descargardo with this?
the file you are trying to flash - at least from your crc post is RM696_059J260_40.2012.21.3_001.vpl - that is not the file to flash.
its name should be like RM696_059J260_40.2012.21.3_001.bin
You will notice that the correct file is MUCH bigger
Friend, how do I know if the firmware download is corrupt me? Should I expect any special output "crc32" command?. Could you give me an example of how the instruction?. My N9 is black model code 059j260 16Gb.
059J260 is NDT LTA 16GB/Black, right?
The files to download are:
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1205/2811/7048829758/DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0309/7076653702/09DC0677_DFL61_HARMATTAN_40.2012.13-7.LTA_EMMC_LTA.bin
fredddurs
2014-04-20, 21:34
the file you are trying to flash - at least from your crc post is RM696_059J260_40.2012.21.3_001.vpl - that is not the file to flash.
its name should be like RM696_059J260_40.2012.21.3_001.bin
You will notice that the correct file is MUCH bigger
I put this in the terminal "crc32 main.bin" and gave me this: "8c9ea3a3". Is it corrupt?
I put this in the terminal "crc32 main.bin" and gave me this: "8c9ea3a3". Is it corrupt?
The correct CRC code corresponding to each file is given in the VPL file. Open the VPL file you downloaded. You'll see the CRC code corresponding to each file.
Hello,
I bought a nokia n9 from hk thru ebay. It had China S/W variant 003. I followed the instructions, used flasher and flashed firmware 005 (indian) and also flashed eMMC image for india.
I opened nokia music. I logged on with my old account. It logged on, but I am unable to download songs, saying there is an error to register this device with unlimited music service.
I tried creating a new account, but the same error.
I called nokia CC in india, they asked me for my imei number and then told me its a china based imei, so i cant use nokia music india service on this phone.
Is there a way to get around? Searched the forums, could not find anything. Pls help.....:confused:
I called nokia CC in india, they asked me for my imei number and then told me its a china based imei, so i cant use nokia music india service on this phone.
Now that's odd, I have been under the impression that IMEI is not tied to any specific country, rather it contains a genetic TAC part that identifies the device and the manufacturer, and the SN part that is manufacturer-specific (usually serial number and factory information)
What did they exactly say about the IMEI, how did they determine it was "Chinese IMEI"? Maybe you told them you originally had Chinese FW on it, and they took the lazy way out and told you it is not supported because they did not bother to solve the problem...?
Now that's odd, I have been under the impression that IMEI is not tied to any specific country, rather it contains a genetic TAC part that identifies the device and the manufacturer, and the SN part that is manufacturer-specific (usually serial number and factory information)
What did they exactly say about the IMEI, how did they determine it was "Chinese IMEI"? Maybe you told them you originally had Chinese FW on it, and they took the lazy way out and told you it is not supported because they did not bother to solve the problem...?
No, I did not tell them I got the phone from China. I called them up, and told them I already have a nokia phone, with an active nokia music subscription that I have been using for over 2 years, recharging via vouchers. I told them I got a new nokia phone and I tried logging on to my nokia music account, and it kept saying that the phone could not be registered to nokia music. Then they asked me for the imei number, and i answered. After a pause, they told me its imported from china, and nokia music can only be activated in China only.
Actually, i am confused here. I ve flashed my country specific eMMC file as well, and yet there is this problem. I thought since I am using this nokia account in another phone, that might be the cause for problem. So I created another account, but it says the same thing.
Has anyone imported a n9 from outside the country (?India) and had this problem? Pls throw some light....:confused:
Now that's odd, I have been under the impression that IMEI is not tied to any specific country, rather it contains a genetic TAC part that identifies the device and the manufacturer, and the SN part that is manufacturer-specific (usually serial number and factory information)
What did they exactly say about the IMEI, how did they determine it was "Chinese IMEI"? Maybe you told them you originally had Chinese FW on it, and they took the lazy way out and told you it is not supported because they did not bother to solve the problem...?
that is true, but since part of TAC identify manufacturer plant, it is possible for eg Nokia, to map that to a region.
that is true, but since part of TAC identify manufacturer plant, it is possible for eg Nokia, to map that to a region.
Possible, yes, but fairly strange.
I thought it does not matter where manufactured, devices could be shipped anywhere to be sold.
Unless this is something cooked up in India locally, for example they have an embargo on Chinese produced goods?
Well, on the interwebs you find this kind of posts (from 2003!) http://www.howardforums.com/showthread.php/160351-Nokia-IMEI-country-of-origin
So, apart of whether the table is accurate and to devices it applies, it can well be that large vendors IMEI do contain some type of geographical information.
Well, on the interwebs you find this kind of posts (from 2003!) http://www.howardforums.com/showthread.php/160351-Nokia-IMEI-country-of-origin
So, apart of whether the table is accurate and to devices it applies, it can well be that large vendors IMEI do contain some type of geographical information.
Yes but that denotes the manufacturing country, there is nothing that should intrest carriers or service providers there.
Unless, indeed, it is forbidden to use made-in-China devices in India, which I seriously doubt!
"They told me its imported
from china, and nokia music can only be activated
in China only."
Could a Chineese proxy be used in this kinda a case to activate Nokia Music? After activation it should work normal *well, guessing* At least that is what they said.
Hi.
Just speculating but, Doesn't this look like the restrictions already in place to stream video from countries different from the one you're in? (i.e: I can't stream video from US's Disney homepage, I'm redirected to my home country's page)
However your IP address is in the same country as it was with your other device...:confused:
This could mean the proxy is an option.
A friend of mine uses a UK's IP address and a VPN to stream video from the UK to Spain...
Just my 2 cents.
Regards.
But these things should have nothing at all to do with the IMEI of the device.
Chinese-made N9's were exported everywhere, AFAIK.
It just cannot be so that for these devices "nokia music can only be activated in China only."
That is insane!
chilango
2014-04-25, 14:50
Yes but this is the way the industrie thinking.
I bought some time ago a Sony Flatscreen. Not for have a big TV but to use Internet-TV for my foreigner.
Sony told my that i have only american Internet-TV. For use the European Internet-TV, please nuy another Sony-TV in Europe and bring it to America.
For me es F--- Y...
Now i have a Raspberry Pi with Openelec and the TV is only a thumb Monitor.
Also with Nokia, it isnt posible for me to install some Europe Apps why its an american Phone.
What is the result. For reason that Nokia dont allow me to buy this App in Nokia Store, i find it ilegal in Internet and install that.
The user is forced for the stupid Industry to do ilegal things.
The Industry likes to convert the Internet in national Net and the user only can use the national websites.
Whne you type in amercian continent
google.fr, google redirects you for the columbian Google page, exept you another time click in "yes, french google"
Hello,
I bought a nokia n9 from hk thru ebay. It had China S/W variant 003. I followed the instructions, used flasher and flashed firmware 005 (indian) and also flashed eMMC image for india.
I opened nokia music. I logged on with my old account. It logged on, but I am unable to download songs, saying there is an error to register this device with unlimited music service.
I tried creating a new account, but the same error.
I called nokia CC in india, they asked me for my imei number and then told me its a china based imei, so i cant use nokia music india service on this phone.
Is there a way to get around? Searched the forums, could not find anything. Pls help.....:confused:
Ok, a step in improvement.... Went around some nokia customer care centres, did some backdoor work, and found out there is already an account attached to this imei of this phone.... I ve got the account user id, but i dont have the password..... The user id is china based.... What next??? :confused::rolleyes: Any way to get the password (short of hacking??) or anyway to reset the user id? I did a master reset, and flashed my country centric eMMC image, dont know wat else will suffice....
Hi guys. I'm going to visit Israel in a couple of days. Recently I've found out that my device (firmware image 006 - Middle East) doesn't contain any relevant maps for Israel.
I was told that eurasian emmc contains maps I'm looking for. As far as I understand it's possible to mix different firmware images with various content ones. That said, could someone confirm/suggest if:
1) Indeed, Israel map is in such-and-such content image
2) It's safe to flash device again with the said emmc (no need to flash with another image).
3) My data will be left intact.
Thanks.
Upd (Solved).
After I manually updated few maps (manage maps - check for updates - download), lo, all of a sudden Israel maps became visible. I managed to install them without no problem. Hope, it will help someone too.
Upd (Solved).
After I manually updated few maps (manage maps - check for updates - download), lo, all of a sudden Israel maps became visible. I managed to install them without no problem. Hope, it will help someone too.
Exactly.
You should never need to flash your device to get some maps for it, even the idea is funny :)
The different country variants just contain the default set of maps for their area, you can alway load extra maps to the device.
Hi.
To whoever might by interested, I can confirm that the scale to determine if a new version is a downgrade is as stated here (http://talk.maemo.org/showpost.php?p=1375115&postcount=963)
For instance: I was on 40.2012.21-3.454.6_PR_LEGACY_454 and now I am in : 40.2012.21-3.100.17_PR_LEGACY_100
This is because the bolded digits are checked before the three-digit version numbers, and also explains why I was able to 'downgrade' from 480.04 to 454.6.
So, my guess is that the 'higher' firmware version so far is 100.17, which is Portugal VODAFONE (and I suppose has operator lock), and not 480.04 as stated before.
Regards.
fendetto
2014-04-29, 07:40
guys just wanna ask..
C:\Program Files\Nokia>WinFlasher_3.12.1.exe -f -F main.bin --erase-user-data=se
cure
flasher 3.12.1 (Oct 6 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...
Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_005
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 19128 kB/s)
Suitable USB interface (phonet) not found, waiting...
stuck on this ..look like the 1st part done correct but second part stuck forever..
robthebold
2014-04-30, 02:52
Just bricked my N9.
Had been updating Ubuntu boxes all day, was tired, did a dist-upgrade on N9 (ugh), answered "yes" when I shouldn't have (ugh), it shut down and won't reboot. Pretty sure I "agreed" to remove something I shouldn't have. Now stuck on the "NOKIA" logo until I get the "Too many reboots" message.
Do I reflash now, or is there a less drastic course to start with? (flasher -i finds the phone with no errors) I ask now so I don't do another stupid thing to compound my problems.
[edit]
Flashing rootfs was necessary and sufficient. Installed applications need re-installed, of course, but most settings and data still there. And of course now I have a good backup of all my partitions.
@robthebold, kind of a similar thing happened with me a few days back. I was fiddling with my phone and it showed an update was available and something else shall be removed. Yes, me too did the mistake of pressing yes. Nothing happened at that very moment. But later, when I was removing a package it didn't end there. While I was staring at my home screen I could see the default phone applications disappearing one by one. Even the settings icon disappeared. A few seconds later, the whole theme layout messed up. I restarted the phone, only to find it stuck at Nokia logo. A Root-fs flash helped me bring the device back to life.
Hi, another person needing help:
I do this: FLASH THE PHONE
Run the following command, then connect the phone to your PC.
Code:
flasher -i
The current firmware version of your phone should appear. It is now time to flash.
What happens next is another c: window opens and closes in less than a second, leaving the flasher window as it was (reading c:\Program Files\Nokia\Flasher>)
I don't get anything else.
Secondly, (what is probably causing the problem) is I don't know where the DFL...bin files should be; now they're in downloads\navifiirmplus_3.2\NaviFirm+\Fw\059L698 should I just copy pasta them to the flasher folder? should I put the 059L698 folder in there? where???
Dear all,
I just purchased a used N9 and am trying to figure out which FW variant it is on and which all FW can be installed on this. Look forward to some guidance on this. Thanks as always.
flasher -i
Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.468.1_PR_468
Success
Dear all,
I just purchased a used N9 and am trying to figure out which FW variant it is on and which all FW can be installed on this. Look forward to some guidance on this. Thanks as always.
flasher -i
Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.468.1_PR_468
Success
That seems to be the UAE variant.
Here are the firmware files you need.
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/1719/7087361810/841EA260_DFL61_HARMATTAN_40.2012.21-3.543.1_EMMC_543.bin
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/1719/7087361801/670D5405_DFL61_HARMATTAN_40.2012.21-3.468.1_PR_LEGACY_468_ARM_RM-696_PRD_signed.bin
That seems to be the UAE variant.
Here are the firmware files you need.
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/1719/7087361810/841EA260_DFL61_HARMATTAN_40.2012.21-3.543.1_EMMC_543.bin
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/1719/7087361801/670D5405_DFL61_HARMATTAN_40.2012.21-3.468.1_PR_LEGACY_468_ARM_RM-696_PRD_signed.bin
Thank you. Will you pl tell me how did you figure this out?
Thank you. Will you pl tell me how did you figure this out?
There's a SW called "NaviFirmEx.exe" that you can use to find details of different firmwares for Nokia devices. (not just N9, also symbian)
Unfortunately it is a windows-only program, which makes it a bit difficult to use for me as I do not use/have any Windows computers, but the bright side is that it runs quite well with Wine :D
There's a SW called "NaviFirmEx.exe" that you can use to find details of different firmwares for Nokia devices. (not just N9, also symbian)
Unfortunately it is a windows-only program, which makes it a bit difficult to use for me as I do not use/have any Windows computers, but the bright side is that it runs quite well with Wine :D
I know about Navifirm. But once I list all the N9 FWs, is there a way to find out which one is PR_468 short of checking each one out individually? Thanks for helping.
I know about Navifirm. But once I list all the N9 FWs, is there a way to find out which one is PR_468 short of checking each one out individually? Thanks for helping.
I am a quick reader :)
dekelley1
2014-05-08, 21:18
I got some help with flashing my phone and I got the N9 to be recognized then ran the following to reset the lock code:
C:\>winflasher_3.12.1.exe -f -F c:\DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_005-OE
M1-958_ARM.bin
Then the nokia and usb icons went away on the phone and the CMD window looks like this:
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may res
in permanently damaging your device or losing the warranty.
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_005
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 29084 kB/s)
It's just sitting there with a blinking cursor, no directory. Been that way for about 30min now. Did I do something wrong? I scared to touch anything. According to someone else I may have ran the wrong command is this is true how can I remedy this?
dekelley1
2014-05-08, 22:55
okay I finally got through the process with no errors. however, when my phone rebooted it is still asking me for a lock code. What happened, what did I not do?
C:\>flasher -f -F c:\DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_005-OEM1-958_ARM.bin
-F DFL61_HARMATTAN_40.2012.13-7.SEAP_EMMC_SEAP.bin
okay I finally got through the process with no errors. however, when my phone rebooted it is still asking me for a lock code. What happened, what did I not do?
C:\>flasher -f -F c:\DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_005-OEM1-958_ARM.bin
-F DFL61_HARMATTAN_40.2012.13-7.SEAP_EMMC_SEAP.bin
To remove the lock code you need to totally wipe the device. (So make sure there's nothing you forgot to backup before doing so...)
If you still have stuff on the device you want to get out, boot it first to MOSLO or ubiboot maintanance console and make backups.
dekelley1
2014-05-09, 18:07
To remove the lock code you need to totally wipe the device. (So make sure there's nothing you forgot to backup before doing so...)
If you still have stuff on the device you want to get out, boot it first to MOSLO or ubiboot maintanance console and make backups.
Hey juiceme, do you think you can update the sticky to clairify that the tags are actually part of the syntax and not just a description, that was my problem this whole time. I'm new to the CMD line and work with cisco devices, so when I saw the -- I immediately thought they were just describing what the command does.
Hey juiceme, do you think you can update the sticky to clairify that the tags are actually part of the syntax and not just a description, that was my problem this whole time. I'm new to the CMD line and work with cisco devices, so when I saw the -- I immediately thought they were just describing what the command does.
Unfortunately this topic's been started by @itsnotabigtruck and he's left TMO for good I think, he was last seen here over 1.5 years ago. (Maybe something's happened to him?)
Only the creator of a posting and moderators can edit postings.
Arthur1010
2014-05-16, 09:51
I downloaded Navi plus but it seems I cant use it without donating money. I would have donated but my country ( Zimbabwe) doesn't have online payments. how can I use go ahead without donating? i need to flash my phone
I downloaded Navi plus but it seems I cant use it without donating money. I would have donated but my country ( Zimbabwe) doesn't have online payments. how can I use go ahead without donating? i need to flash my phone
What's the difference between NaviFirm plus and NaviFirmEx, then?
At least NaviFirmEx works without any grants AFAIK, so you might want to try that...?
Hello to all members!
Is there any other way to figure out the appropriate product code
if the code printed on sim tray is missing?
Thank you.
The three ways I know are:
- you can read it on the sim tray (but that would be 100% correct only if it's still the original f/w)
- if the phone can still boot to Harmattan you can look in Settings -> About Product
- if the phone is not totally bricked you can use "flasher -i" command
The three ways I know are:
- you can read it on the sim tray (but that would be 100% correct only if it's still the original f/w)
- if the phone can still boot to Harmattan you can look in Settings -> About Product
- if the phone is not totally bricked you can use "flasher -i" command
Thank you for your answer.
The device is fully functional but because the product code from sim tray is missing i don't know which firmware to download.
I have read in a guide that it doesn't matter which color or capacity (16/64 GB) you select - the files are the same for all models.
But this stands up for both files or it is only for the emmc image?
As far as I remember there is no difference at all neither in fiasco file nor in emmc.
If your device is functional, just look at the About Product page. It's even more accurate info than what you can deduct via sim tray.
Flasher link seems to be down. Does anyone have the 64bit .deb file?
Flasher link seems to be down. Does anyone have the 64bit .deb file?
once more
https://coderus.openrepos.net/flasher/
pistachio
2014-06-21, 11:35
I downloaded Navi plus but it seems I cant use it without donating money. I would have donated but my country ( Zimbabwe) doesn't have online payments. how can I use go ahead without donating? i need to flash my phone
Navifirm is not accepting free account from last few days,so any one wants to download firmwares can go here..:)
http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696
malmostoso
2014-08-02, 07:28
Hey everybody,
I wanted to flash my N9 for resale, so I followed the instructions for the "zeroize device" process. This is what I did:
root@nostromo:/home/jack/nokia/059K772_RM-696 NDT SWITZERLAND BLACK 64GB# flasher -f -F D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin --erase-user-data=secure
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 003, device address 018.
Device identifier: 357923041408628 (SN: N/A)
Found device RM-696, hardware revision 1501
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_009
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 40093 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 003, device address 019.
Device identifier: 357923041408628 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8
Battery level 67 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_009
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped
Battery level 68 %, 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 3016 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 1796 kB/s]
[x] rootfs [finished 100 % 1170206 / 1170206 kB 11969 kB/s]
Updating SW release
Success
root@nostromo:/home/jack/nokia/059K772_RM-696 NDT SWITZERLAND BLACK 64GB# flasher -f -F D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin -F 030AF44E_DFL61_HARMATTAN_40.2012.13-7.ALPS_EMMC_ALPS.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 003, device address 019.
Device identifier: 357923041408628 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_009
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 69 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] mmc [finished 100 % 1629459 / 1629459 kB 20283 kB/s]
Success
I do not see any errors, but the erasing process took 5 minutes. Is this normal?
I am also not sure I picked the correct files for flashing. As a "main.bin" I selected the 1.2GB "D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin", and as "emmc.bin" I used the 1.7GB "030AF44E_DFL61_HARMATTAN_40.2012.13-7.ALPS_EMMC_ALPS.bin".
Is this all correct?
When I rebooted the phone was flashed and all my data seems to be gone, but I'm just unsure since it took such a short time.
Thank you!
Yes, you are good to go
Hey everybody,
I wanted to flash my N9 for resale, so I followed the instructions for the "zeroize device" process. This is what I did:
root@nostromo:/home/jack/nokia/059K772_RM-696 NDT SWITZERLAND BLACK 64GB# flasher -f -F D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin --erase-user-data=secure
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 003, device address 018.
Device identifier: 357923041408628 (SN: N/A)
Found device RM-696, hardware revision 1501
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_009
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 40093 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 003, device address 019.
Device identifier: 357923041408628 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8
Battery level 67 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_009
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped
Battery level 68 %, 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 3016 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 1796 kB/s]
[x] rootfs [finished 100 % 1170206 / 1170206 kB 11969 kB/s]
Updating SW release
Success
root@nostromo:/home/jack/nokia/059K772_RM-696 NDT SWITZERLAND BLACK 64GB# flasher -f -F D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin -F 030AF44E_DFL61_HARMATTAN_40.2012.13-7.ALPS_EMMC_ALPS.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 003, device address 019.
Device identifier: 357923041408628 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_009
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 69 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] mmc [finished 100 % 1629459 / 1629459 kB 20283 kB/s]
Success
I do not see any errors, but the erasing process took 5 minutes. Is this normal?
I am also not sure I picked the correct files for flashing. As a "main.bin" I selected the 1.2GB "D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin", and as "emmc.bin" I used the 1.7GB "030AF44E_DFL61_HARMATTAN_40.2012.13-7.ALPS_EMMC_ALPS.bin".
Is this all correct?
When I rebooted the phone was flashed and all my data seems to be gone, but I'm just unsure since it took such a short time.
Thank you!
If you don't use the erase flag flashing only takes a few moments....
I am trying to do a fresh install. USB charging is working when connect to PC but the phone is not recognized (Windows 8.1 OS). Am getting the following error message in phone
"Not enough power from the USB in order to charge the device"
I also check the other thread and it did not work
http://talk.maemo.org/showthread.php?t=84167
After switching off the phone (8 sec hold), started flasher and am stuck with no progress
------------
D:\Mobile\NokiaN9\Flashing>Flasher.exe -F DFL61_HARMATTAN_40.2012.21-3.335.1_PR_
LEGACY_335_ARM_RM-696_PRD_signed.bin -f -c -R
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.
Using 1st image to detect HW
Suitable USB interface (bootrom) not found, waiting...
------------
Can someone help please?
35805
what to do??? help!
what to do??? help!
What was the exact command line you used?
What was the exact command line you used?
flasher -f -F main.bin
i have done everything i can.. my brains freeze :D
no i have in this point...35806
so now when i open phone, it says "install correct "software" or something.. it say that finnish language and my english is bad :D
flasher -f -F main.bin
i have done everything i can.. my brains freeze :D
no i have in this point...
so now when i open phone, it says "install correct "software" or something.. it say that finnish language and my english is bad :D
Okay, so what I'd suggest is you should back up your phone and then flash device with both emmc and firmware, which pretty much resets the device to factory condition.
Do you have the correct BIN files? What is the country variant of your device, I suppose it is finnish?
(You can find the country variant number written under the simcard tray.)
Okay, so what I'd suggest is you should back up your phone and then flash device with both emmc and firmware, which pretty much resets the device to factory condition.
Do you have the correct BIN files? What is the country variant of your device, I suppose it is finnish?
(You can find the country variant number written under the simcard tray.)
simtray = 059J187
i download those bin files with navifirm+. but when i flash, it give me error and "cant flash" or something like that.
Okay, so what I'd suggest is you should back up your phone and then flash device with both emmc and firmware, which pretty much resets the device to factory condition.
Do you have the correct BIN files? What is the country variant of your device, I suppose it is finnish?
(You can find the country variant number written under the simcard tray.)
toimiiko tää vastaus prkl
toimiiko tää vastaus prkl
hyvin toimii :D
nonni :) onnistusko jeesi tän perhanan puhelimen suhteen, ei tarvis englanniks yrittää säätää :D
nonni :) onnistusko jeesi tän perhanan puhelimen suhteen, ei tarvis englanniks yrittää säätää :D
FI: Tottahan toki, kunhan pääsen himaan. Oon junassa nyt keskellä eimitään.
ENG: Sure, I can help you further when I get back home. Am presently in a train practically middle of nowhere...
nice! thanx! jos sais eloon tuon luurin vihdoin ja viimein :)
nice! thanx! jos sais eloon tuon luurin vihdoin ja viimein :)
English version:
Okay. So your device is 059J187 which is "NDT North Europe Black 64GB" model.
The correct files to download are the following:
firmware: http://nds2.fds-fire.nokia.com/p/d/fds_fire/1205/2811/7048829758/DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
EMMC: http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0317/7076769035/29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin
If you downloaded the correct files, it might be that you had corruption during download. (I always suggest using curl or wget to download large BIN files rather than browser)
You might want to check the md5sum of the files you downloaded, to make sure they are not corrupted.
(firmware = 53fcefc0033875661c19160e16999b3e)
(EMMC = b289c1e9fdcdd5528adf5f82c29e39e0)
After you have verified the files are correct, or downloaded new files, you can try flashing again.
------
Sama suomeksi:
Sun malli 059J187 on itseasiassa sama kun mun kapula, Musta/64G.
Oikeat filet löytyypi täältä:
firmware: http://nds2.fds-fire.nokia.com/p/d/fds_fire/1205/2811/7048829758/DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
EMMC: http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0317/7076769035/29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin
Tarkista että ne fiilut jotka oot ladannu ei ole korruptoitunu matkalla, mikä on hyvinkin mahdollista jos oot käyttäny jotain selainta lataamiseen. Etenki IE on niin paska ettei sillä voi edes persettään pyyhkiä.
Ite käytän aina wgettiä tai curlia isojen fiilujen lataukseen.
Tässä on oikeiden fileiden md5summat:
(firmware = 53fcefc0033875661c19160e16999b3e)
(EMMC = b289c1e9fdcdd5528adf5f82c29e39e0)
Kun oot tarkistanu että sulla on ehjät fileet tai ladannu uudet, voit koittaa flashata luurin uudestaan. Jos ei vieläkään onnistu niin kysy lisää, on nimittäin useampikin keino alustaa luuri defaulttiin.
laitoin lataukseen!
millä komennolla flashaan sit?
laitoin lataukseen!
millä komennolla flashaan sit?
English version:
Now, the following things are going to wipe your device to factory default. Be sure to have backups before doing it, or else prepare to lose everything you have on the device.
First, to make it easier and to have the commands a bit shorter and easier to write it is best that you rename the files you downloaded to for example emmc.bin and firmware.bin
emmc.bin = 29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin
firmware.bin = DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
As for flashing, first you might try the following command. This is the basic "write binaries to flash" command:
flasher -F emmc.bin -F firmware.bin -f -R
If the above command does not work, you can try the next one. This will take longer as the device also formats the flash partitions before flashing:
flasher -F emmc.bin -F firmware.bin -f -R --erase-user-data=secure
If neither of those work, You can try the "cold flashing" command which does force recreation of partition table:
flasher -F emmc.bin -F firmware.bin -f -R --cold-flash
----------
Sama suomeksi:
Okay, nämä seuraavat komennot sitten tyhjentää luurin kokonaan. Eli sulla on paras olla backupit kaikesta mitä haluat säilyttää koska tän jälkeen laite on ihan pakasta vedetty.
Ensimmäiseksi kannattaa muuten nimetä ne lataamasi tiedostot uudelleen vähä helpommiksi, kun on senverran vaikeata kirjoittaa noita pitkiä komentoja. Yleensä on tapana käyttää nimiä emmc.bin ja firmware.bin.
emmc.bin = 29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin
firmware.bin = DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
Flässäyksestä; ensin kannatta kokeilla tätä komentoa. Tämä on peruskauraa, laitteeseen vaan kirjoitetaan uudet imaget:
flasher -F emmc.bin -F firmware.bin -f -R
Jos ylläoleva kometo ei auttanu, voit koittaa tätä seuraavaksi. Tämän komennon ajaminen kestää muuten sitten aika pitkään, koska se formatoi flässin:
flasher -F emmc.bin -F firmware.bin -f -R --erase-user-data=secure
Jos kumpikaan noista ei pelannu OK, niin voit koittaa "kylmäflashata" värkin. Tämä komento uudelleenkirjoittaa flashin partitiotaulut:
flasher -F emmc.bin -F firmware.bin -f -R --cold-flash
English version:
Now, the following things are going to wipe your device to factory default. Be sure to have backups before doing it, or else prepare to lose everything you have on the device.
First, to make it easier and to have the commands a bit shorter and easier to write it is best that you rename the files you downloaded to for example emmc.bin and firmware.bin
emmc.bin = 29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin
firmware.bin = DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
As for flashing, first you might try the following command. This is the basic "write binaries to flash" command:
flasher -F emmc.bin -F firmware.bin -f -R
If the above command does not work, you can try the next one. This will take longer as the device also formats the flash partitions before flashing:
flasher -F emmc.bin -F firmware.bin -f -R --erase-user-data=secure
If neither of those work, You can try the "cold flashing" command which does force recreation of partition table:
flasher -F emmc.bin -F firmware.bin -f -R --cold-flash
----------
Sama suomeksi:
Okay, nämä seuraavat komennot sitten tyhjentää luurin kokonaan. Eli sulla on paras olla backupit kaikesta mitä haluat säilyttää koska tän jälkeen laite on ihan pakasta vedetty.
Ensimmäiseksi kannattaa muuten nimetä ne lataamasi tiedostot uudelleen vähä helpommiksi, kun on senverran vaikeata kirjoittaa noita pitkiä komentoja. Yleensä on tapana käyttää nimiä emmc.bin ja firmware.bin.
emmc.bin = 29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin
firmware.bin = DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
Flässäyksestä; ensin kannatta kokeilla tätä komentoa. Tämä on peruskauraa, laitteeseen vaan kirjoitetaan uudet imaget:
flasher -F emmc.bin -F firmware.bin -f -R
Jos ylläoleva kometo ei auttanu, voit koittaa tätä seuraavaksi. Tämän komennon ajaminen kestää muuten sitten aika pitkään, koska se formatoi flässin:
flasher -F emmc.bin -F firmware.bin -f -R --erase-user-data=secure
Jos kumpikaan noista ei pelannu OK, niin voit koittaa "kylmäflashata" värkin. Tämä komento uudelleenkirjoittaa flashin partitiotaulut:
flasher -F emmc.bin -F firmware.bin -f -R --cold-flash
Ei toimi ei.. voiko olla flasheri väärä kenties? hrmph...
nyt tuo odottelee puhelinta tuossa coldflashis.. mitään ei tapahdu.. kuva täsä
35812
Ei toimi ei.. voiko olla flasheri väärä kenties? hrmph...
flasher 3.12.1 on kyllä just oikea versio.
nyt tuo odottelee puhelinta tuossa coldflashis.. mitään ei tapahdu.. kuva täsä
Hmmh, ei sen pitäis kyl odottaa tuossa sen pitempään. Irrotitko puhelimen piuhasta ennekun annoit komennon, ja sitten laitoit kiinni? Ja olihan puhelin sammutettuan kun teit tuon?
Nuo certificate errorit kyl vähän huolestuttaa. Eihän tuo ole simmilukittu puhelin? Tosin nitä ei mun mielestä oo suomessa myyty lukittuna.
ei oo simlukittu.. ja puhelin oli kiinni kun tuon tein, piuhan kun laitoin käynnisti puhelimen ja näyttöön tuli vaan "asenna hyväksytty käyttöjärjestelmä uudestaan"
ei oo simlukittu.. ja puhelin oli kiinni kun tuon tein, piuhan kun laitoin käynnisti puhelimen ja näyttöön tuli vaan "asenna hyväksytty käyttöjärjestelmä uudestaan"
Jos puhelin on OFF ja laitat USB-piuhan kiinni niin että flasher on käynnistetty, ei näyttöön pitäisi kyllä tulla mitään.
Flasher haistaa puhelimen kytkennän ja työntää sinne ensimmäisen stagen boottiloaderista oman vastakappaleensa.
Käytätkö windowssia vai linuxia? Ittelläni on vain linux mut periaatteessa kyl sen pitää toimia windowsillakin ihan samalla tavalla.
se avaa ainoastaan puhelimen kun kokeilen coldflashia. nuo muut se lähtee flashaa mutta huuta lopuks erroria! :S windowsia käytän juu..
tai sit coldflashilla ei tapahdu mitään.. jurraa vaan että etsii HWtä
irulestar
2014-09-25, 16:09
Sorry. How to remove singtel logo!?
Please help
thedead1440
2014-09-25, 16:16
Sorry. How to remove singtel logo!?
Please help
Where is the singtel logo? Do you mean on the low-power screen when the screen is locked? If so, then you can just install any one of the numerous apps for customizing the low-power screen.
andreas1
2014-09-25, 21:52
English version:
... The correct files to download are the following:
firmware: http://nds2.fds-fire.nokia.com/p/d/fds_fire/1205/2811/7048829758/DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
EMMC: http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0317/7076769035/29FAD658_DFL61_HARMATTAN_40.2012.13-7.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin
...
Hei, onko näissä uusin versio pr1.3 / does these have the latest version pr1.3?
Hei, onko näissä uusin versio pr1.3 / does these have the latest version pr1.3?
As you can read from the first post in this thread, 40.2012.21-3 is the PR1.3 version for the firmware. The "40" string indicates the PR1.3 release.
The link provided to the EMMC is also the latest for PR1.3.
Kishijin
2014-10-11, 06:02
im having a problem flashing N9
while flashing using:
flasher -f -F main.bin
%stop around 30-45
my thought that the phone disconnects while flashing?
(and the usb that i use isnt faulty or anything, tried 3 usbs(2new))
my thought that the phone disconnects while flashing?
Please post a screenshot of the error (if the spam filter allows you) and the details of what you use to flash the phone.
i tried to flash my n9 from win7 64bit
but the flasher can't detect the phone and my phone boot when i connect the phone to my PC
any way to fix that ?
peterleinchen
2014-10-25, 08:11
Please read the thread! :cool:
I would say either there was an Asian/Chinese firmware (cmt) flashed. Then I guess you are out of luck.
But probably it is just a bad download, so try download once more (and please check md5sum against the ones posted somewhere here in forum).
skyjumper
2014-11-08, 00:35
Hi,
So I'm trying to flash my phone (rootfs) on a fedora 64 bit machine.
My phone variant is: DFL61_HARMATTAN_40.2012.21-3.249.1_PR_249
I have flashed successfully before using this command (flasher 3.12.1)
flasher -f -F main.bin -R
This time I get:
Sending ape-algo image (7103kb)...
Write failed after 0 bytes
usb_bulk_write: Connection timed out
ERROR:L Failed to upload APE algorithm
edit: well I re-downloaded the rootfs file and this time did:
flasher -f -F ./main.bin and it worked. :-)
abdosh9997
2014-11-23, 09:17
:madThe error message "Downgrade Disallowed" is the reason.
You need to flash the device with the same or later version than what's in the device currently.
"DFL61_HARMATTAN_40.2012.21-3_PR_001" is smaller version than "DFL61_HARMATTAN_40.2012.21-3.335.1_PR_335"
i have like his problem exactly put i do not know product code because i misses sim tray .... please help:)
salamisami
2014-11-24, 18:49
Flasher mirror (skeiron) seems down. Anywhere else I could fetch the flasher?
pistachio
2014-11-24, 19:02
Flasher mirror (skeiron) seems down. Anywhere else I could fetch the flasher?
You can get it from here maybe.
https://coderus.openrepos.net/flasher/
salamisami
2014-11-24, 20:00
You can get it from here maybe.
https://coderus.openrepos.net/flasher/
Thank you! I am still confused, however. Which of these files do I need to flash the latest firmware?
http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696&releaseID=7048842309&variantID=7076921285&productCode=059M5R3&version=40.2012.21.3
There are so many of them and the guide doesn't tell which one(s) I require. Most of the files are under 10 kb in size but there's also two over 1 GB files.
pistachio
2014-11-24, 20:24
Thank you! I am still confused, however. Which of these files do I need to flash the latest firmware?
http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696&releaseID=7048842309&variantID=7076921285&productCode=059M5R3&version=40.2012.21.3
There are so many of them and the guide doesn't tell which one(s) I require. Most of the files are under 10 kb in size but there's also two over 1 GB files.
If you want to flash the emmc, you need both 1.55 and 1.16 gb file, otherwise only DFL61 HARMATTAN 40.2012.21-3 PR LEGACY 001-OEM1-958 ARM.bin
EDIT: You dont need those files in KBs..
salamisami
2014-11-24, 20:57
If you want to flash the emmc, you need both 1.55 and 1.16 gb file, otherwise only DFL61 HARMATTAN 40.2012.21-3 PR LEGACY 001-OEM1-958 ARM.bin
EDIT: You dont need those files in KBs..
thanks, that did it.
by the way, is there any reason to register a Nokia account anymore? earlier I was unable to install developed more, i wonder if not having Nokia account had anything to do with it.
pistachio
2014-11-25, 03:21
thanks, that did it.
by the way, is there any reason to register a Nokia account anymore? earlier I was unable to install developed more, i wonder if not having Nokia account had anything to do with it.
Yes, You need nokia account to download apps from nokia store. No relation between nokia account and developer mode AFAIK.
I want to remind that NaviFirm+ is actually still useful for getting the firmware for N9. http://www.symbian-toys.com/NaviFirm.aspx
I downloaded the latest J260 images from mrcrab.net website. At least it seems to be the latest. But it fails to flash. The phone was updated over the air (years ago). I suspect I need a later variant but I don't know where to find it. Any help would be appreciated.
This is from the mrcrab.net website:
[Phone Name : Nokia N9
Product Type : RM-696
Variant ID : 7076654744
Varian Name : RM-696 NDT LTA BLACK 16GB
Product Code : 059J260
Software Version : 40.2012.21.3
[/FONT]
Here is the log for flashing:
drwx------ 36 rick rick 4096 Dec 31 1969 Nokia N9
rick@rick-CT14:/media/rick/big2/N9-16GB$ 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 003, device address 023.
Device identifier: 357923043093089 (SN: N/A)
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Success
rick@rick-CT14:/media/rick/big2/N9-16GB$ flasher -f -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin --erase-user-data=secure
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 003, device address 023.
Device identifier: 357923043093089 (SN: N/A)
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 36579 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 003, device address 024.
Device identifier: 357923043093089 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Battery level 86 %, continuing.
Erasing, this may take a while.
Erase done.
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 90 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[_] cert-sw [init 0 % 0 / 0 kB NA ]
[ ] cmt-2nd [pending 0 % 0 / 0 kB NA ]
[ ] cmt-algo [pending 0 % 0 / 0 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[ ] xloader [pending 0 % 0 / 0 kB NA ]
[ ] secondary [pending 0 % 0 / 0 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 10: Security failure
image [state progress transfer flash speed]
---------------------------------------------------------------------
[f] cert-sw [init 0 % 1 / 1 kB NA ]
[ ] cmt-2nd [pending 0 % 0 / 0 kB NA ]
[ ] cmt-algo [pending 0 % 0 / 0 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[ ] xloader [pending 0 % 0 / 0 kB NA ]
[ ] secondary [pending 0 % 0 / 0 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1338190008)
[Pipe 0] Finishing in error state with status 10
========================================
ERROR: Failed to flash images
rick@rick-CT14:/media/rick/big2/N9-16GB$
peterleinchen
2014-11-25, 15:37
Your log clearly states: you have variant 006 on device and you want to flash with an image of variant 001.
You need to grab an image with variant number 006 (best, or higher).
Yes, I understand that. The problem is - where are the variants and how can you tell what the variant is? I don't see anything clearly marked as variant 006 for the 059J260 model. On the mrcrab.net site there is a variant ID but it doesn't appear to correspond to 001 or 006.
Best guess, you need this one (seems you have middle east FW on the device)
http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696&releaseID=7048842309&variantID=7076936024&productCode=059J231&version=40.2012.21.3
Thank you. Could you explain how you know this? The code on the sim tray is 059J260 not 059J231.
Thank you. Could you explain how you know this? The code on the sim tray is 059J260 not 059J231.
Can you scan that barcode in Settings-> About
The N9 won't boot because the flash failed.
Try with another usb port and cable?
Best guess, you need this one (seems you have middle east FW on the device)
http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696&releaseID=7048842309&variantID=7076936024&productCode=059J231&version=40.2012.21.3
Thanks - I don't understand how you knew which files to download but it worked.
Thanks - I don't understand how you knew which files to download but it worked.
As @peterleinchen noticed from your log, you have variant 006 of firmware on phone, you, or someone owning the phone before you, flashed that version - never mind the product cofe.
If you look here http://wiki.maemo.org/Flashing_N9 you will see variant 006 is middle east version FW.
Sp, simply search on all firmwares on mrcrabb, and locate one that have "006" in filename. Size and color doesnt matter really.
Note that the number on the simtray indicates only what variant of the firmware was *originally* shipped with the phone.
Because it's possible to flash a variant with a higher revision number than the existing one (as explained at top of the thread) and because the simtray may have been swapped with a different one, it's not reliable to use the simtray number to guess the firmware variant.
If you want to know the existing firmware version, use the flasher command with option -i .
Anyway in your flashing attempt the first thing flasher has done is spell out the device identification, i.e. what your device currently is/has:
Device identifier: 357923043093089 (SN: N/A)
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Hi guys.
I am wondering how secure the secure erase feature really is. I flashed my phone using the --erase-user-data=secure option but the whole process only took a few minutes. Is it any different from standard Windows quick formatting? Does it really make it impossible (or at least difficult) to recover erased data? An why did it only need such a short time to complete? The guide states that "it will take a very long time" but I've heared from other users that securely flashing their phones also took only a few minutes.
Cheers.
Hi guys.
I am wondering how secure the secure erase feature really is. I flashed my phone using the --erase-user-data=secure option but the whole process only took a few minutes. Is it any different from standard Windows quick formatting? Does it really make it impossible (or at least difficult) to recover erased data? An why did it only need such a short time to complete? The guide states that "it will take a very long time" but I've heared from other users that securely flashing their phones also took only a few minutes.
Cheers.
Well, it does the best to erase the flash data but due to the way flash memory is constructed it is highly likely that some data remains on the device. Reliably Erasing Data From Flash-Based Solid State Drives (https://www.usenix.org/legacy/event/fast11/tech/full_papers/Wei.pdf)
As for why it is cited to take a long time and it actually takes less than that; few minutes is actually awfully long time.
It also depends on whether you have a 16G or 64G device, it takes 4 times longer to erase the larger device.
vBulletin® v3.8.8, Copyright ©2000-2025, vBulletin Solutions, Inc.