Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 3 days, 12 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 5 days, 9 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 6 days, 6 hrs ago - more...
|
2013-09-17
, 13:26
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#952
|
Originally Posted by MONVMENTVM
The PR1.2 link you posted is also a v2 variant (430)... Can you try finding in other countries but T-Mobile variants too and try one of those images?
Thanks, yes it's a t-mobile austria variant. The one I was trying to install apparently was v2 of the firmware while the one installed is the v1 (which probably is why the original variant number is 350 and now 430 despite having the same product code 059L6C3).
http://www.mrcrab.net/nokia/Nokia_N9...on=30.2012.7.1
I can't find the T-Mobile Austria v1 firmwares with the 350 variant other than in older PRs. For PR1.3 I can only find the v2 (430)
|
|
2013-09-17
, 13:42
|
|
Posts: 145 |
Thanked: 91 times |
Joined on Jun 2010
|
#953
|
Oh yes posted the wrong link when I was checking older PRs.
I already tried T-Mobile Hungary variant which is 40.2012.21-3.373.1_PR_LEGACY_373 (which is relatively low but still higher than the installed 350) but still no luck. Could it be that OTA updates messed up the timestamps on the system or something?
I already tried T-Mobile Hungary variant which is 40.2012.21-3.373.1_PR_LEGACY_373 (which is relatively low but still higher than the installed 350) but still no luck. Could it be that OTA updates messed up the timestamps on the system or something?
|
|
2013-09-17
, 14:15
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#954
|
You did an OTA to PR1.3? It's possible that screwed the timestamp then... I would advice trying to use Nokia Software Updater for Windows as it seems to restore factory firmware from what others have mentioned although I haven't personally ever tried it...
|
|
2013-09-17
, 15:20
|
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#955
|
Using another kernel than zImage, the zImage_2.6.32.54-openmode_l2fix solved USB problem even using backupmenu.
But then even if as user:
disclaimer-cal remove View-openmode
AND the --suppress-warranty-warnings
Every time reboot this irritating warning appears
and tried flash twice.
Does I really need to use old zImage.PR13 to get it to work or...?
C:\Programmer\nokia\Flasher>flasher.exe -a DFL61_HARMATTAN_40.2012.21-3.340.04.1
_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin -k zImage_2.6.32.54-openmode_l2fix --fl
ash-only=kernel --suppress-warranty-warning -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan
Picked ape-algo from a FIASCO file
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.340.04.1_PR_340
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 13427 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 <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped
Battery level 55 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2712 / 2712 kB 2032 kB/s]
Updating SW release
Success
C:\Programmer\nokia\Flasher>
Last edited by Garp; 2013-09-17 at 16:07.
But then even if as user:
disclaimer-cal remove View-openmode
AND the --suppress-warranty-warnings
Every time reboot this irritating warning appears
and tried flash twice.
Does I really need to use old zImage.PR13 to get it to work or...?
C:\Programmer\nokia\Flasher>flasher.exe -a DFL61_HARMATTAN_40.2012.21-3.340.04.1
_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin -k zImage_2.6.32.54-openmode_l2fix --fl
ash-only=kernel --suppress-warranty-warning -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan
Picked ape-algo from a FIASCO file
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.340.04.1_PR_340
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 13427 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 <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped
Battery level 55 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2712 / 2712 kB 2032 kB/s]
Updating SW release
Success
C:\Programmer\nokia\Flasher>
__________________
OK
OK
Last edited by Garp; 2013-09-17 at 16:07.
|
|
2013-09-17
, 17:15
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#956
|
Originally Posted by Garp
not sure, but might be wrong zImage.
HELP! My USB connection dont work besides charging after flashing openmode.
My N9 chrashed and needed to flash. After flash to standard mode the USB worked OK.
Then i used zImage from here to flash openmode
http://wiki.maemo.org/Ubiboot#Moving...g_Filebox_Root
C:\Programmer\nokia\Flasher>flasher.exe -a DFL61_HARMATTAN_40.2012.21-3.340.04.1
_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin -k zImage --flash-only=kernel --suppres
s-warranty-warning -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan
Picked ape-algo from a FIASCO file
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.340.04.1_PR_340
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 14798 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 <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped
Battery level 92 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2834 / 2834 kB 1971 kB/s]
Updating SW release
Success
C:\Programmer\nokia\Flasher>
Then installing Backupmenu_1.1.9_tar and restored from backup as before but USB only charging
In terminal:
accli -I
Current mode: open
uname -r
2.6.32.54-dfl61-20121301
Suggest you try this one
http://maemo.cloud-7.de/HARM/N9/1.3/openmode-kernel/
| The Following User Says Thank You to For This Useful Post: | ||
|
|
2013-09-17
, 17:28
|
|
Posts: 145 |
Thanked: 91 times |
Joined on Jun 2010
|
#957
|
Originally Posted by thedead1440
Doesn't work because apparently NSU needs the phone to be able to boot, while the flasher does not. As I've booted into Windows anyway now I've downloaded NaviFirm+ and downloading the firmware again (maybe it's timestamped differently). I really hope this works... while googling for solutions I've found this btw.:
You did an OTA to PR1.3? It's possible that screwed the timestamp then... I would advice trying to use Nokia Software Updater for Windows as it seems to restore factory firmware from what others have mentioned although I haven't personally ever tried it...
http://my-symbian.com/forum/viewtopic.php?t=43973
Exactly what happened to me. Can't believe I have this N9 for a couple of weeks (after my N900 died of hardware failure) and this thing is already bricked after surfing the web.
EDIT: Nope does not work either. What could I try next?
Last edited by MONVMENTVM; 2013-09-17 at 17:48.
|
|
2013-09-17
, 22:52
|
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#958
|
Originally Posted by nieldk
Thanks you were right this one function without USB or Warnings trouble, even if I dont know why
not sure, but might be wrong zImage.
Suggest you try this one
http://maemo.cloud-7.de/HARM/N9/1.3/openmode-kernel/
__________________
OK
OK
|
|
2013-09-18
, 10:35
|
|
Posts: 145 |
Thanked: 91 times |
Joined on Jun 2010
|
#959
|
Originally Posted by MONVMENTVM
Nobody else did the mistake to upgrade to PR1.3 via OTA and then had to reflash? I really don't know how to unbrick my device now.
Doesn't work because apparently NSU needs the phone to be able to boot, while the flasher does not. As I've booted into Windows anyway now I've downloaded NaviFirm+ and downloading the firmware again (maybe it's timestamped differently). I really hope this works... while googling for solutions I've found this btw.:
http://my-symbian.com/forum/viewtopic.php?t=43973
Exactly what happened to me. Can't believe I have this N9 for a couple of weeks (after my N900 died of hardware failure) and this thing is already bricked after surfing the web.
EDIT: Nope does not work either. What could I try next?
|
|
2013-09-18
, 17:57
|
|
Posts: 145 |
Thanked: 91 times |
Joined on Jun 2010
|
#960
|
Ok finally fixed it and for people having similar issues flashing their n9 this might come in handy.
It appears that not only does the variant number have to be higher or equal, also the following numbers have to be higher. For example I had
DFL61_HARMATTAN_40.2012.21-3.350.3
installed. It appears that this actual firmware does not really exist for my product code. It did for a previous PR but got changed to variant 430, but as I updated via OTA the firmware variant never got changed to the correct 430. It kept the 350.3 part and replaced the 40.2012.21-3 to resemble the PR1.3.
Having to flash my phone now there is only this 430 variant available for my product code which is precisely:
DFL61_HARMATTAN_40.2012.21-3.430.01.1
One would think coming from a 350, flashing to 430 wouldn't be a problem because the variant number is higher. But no, it doesn't work because of big a** version numbering inconsistency fail. As you can see it's actually variant 350.3 vs 430.01(.1) and apparently the numbers following the 350 and 430 variant codes ALSO WILL BE COMPARED.
So I was looking around for a firmware that has both the variant number and what follows after it at equal or higher numbers and I found this N9 Rm-696 Optimus Pt V1-black - 16g firmware named:
DFL61_HARMATTAN_40.2012.21-3.398.3
And voilá that damned thing works again.
Last edited by MONVMENTVM; 2013-09-18 at 18:00.
It appears that not only does the variant number have to be higher or equal, also the following numbers have to be higher. For example I had
DFL61_HARMATTAN_40.2012.21-3.350.3
installed. It appears that this actual firmware does not really exist for my product code. It did for a previous PR but got changed to variant 430, but as I updated via OTA the firmware variant never got changed to the correct 430. It kept the 350.3 part and replaced the 40.2012.21-3 to resemble the PR1.3.
Having to flash my phone now there is only this 430 variant available for my product code which is precisely:
DFL61_HARMATTAN_40.2012.21-3.430.01.1
One would think coming from a 350, flashing to 430 wouldn't be a problem because the variant number is higher. But no, it doesn't work because of big a** version numbering inconsistency fail. As you can see it's actually variant 350.3 vs 430.01(.1) and apparently the numbers following the 350 and 430 variant codes ALSO WILL BE COMPARED.
So I was looking around for a firmware that has both the variant number and what follows after it at equal or higher numbers and I found this N9 Rm-696 Optimus Pt V1-black - 16g firmware named:
DFL61_HARMATTAN_40.2012.21-3.398.3
And voilá that damned thing works again.
Last edited by MONVMENTVM; 2013-09-18 at 18:00.
| The Following 4 Users Say Thank You to MONVMENTVM For This Useful Post: | ||
http://www.mrcrab.net/nokia/Nokia_N9...on=30.2012.7.1
I can't find the T-Mobile Austria v1 firmwares with the 350 variant other than in older PRs. For PR1.3 I can only find the v2 (430)