Author Topic: N9 Kernel for Dual-Boot  (Read 151712 times)

Offline gleimesonjean

  • NITDroid novice
  • *
  • Posts: 6
Re: N9 Kernel for Dual-Boot
« Reply #150 on: March 29, 2012, 03:05:47 am »
windows does not install drivers dispoditivo where can I find the drives for the windows recognize the boot mode.

 windows 7 32bit

Offline pissis

  • NITDroid novice
  • *
  • Posts: 9
Re: N9 Kernel for Dual-Boot
« Reply #151 on: March 29, 2012, 08:12:42 pm »
hello i have little proble with the zimage as i have tried now couple calculators and all give me

fa82ad3d8a19f79f918ccb53d19a830e

so it not kinda right?

and another problem i cant start the flasher itself (was thinking becose im using vista 64bit and its for 32bit so is there any flasher atm that works with vista64bit AND n9?
flasher just blinks and closes.

Offline Sniper_swe

  • Administrator
  • I know all there is to know!
  • *****
  • Posts: 264
Re: N9 Kernel for Dual-Boot
« Reply #152 on: March 29, 2012, 08:26:15 pm »
in cmd: cd path_to_directory_which_contains_your_flasher (ex. cd C:\program files\nokia\flasher )
Then execute the kernel command.

Offline tezine

  • NITDroid novice
  • *
  • Posts: 4
Re: N9 Kernel for Dual-Boot
« Reply #153 on: March 29, 2012, 10:16:58 pm »
Hi,
I'm trying to install the dual boot under my N9 Pr1.2, but whenever I execute flasher -a DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_001-OEM1-958_ARM.bin -k zImage --flash-only=kernel -f -R, I get the result below, but I had already set the Autolock to off!
Despite of that, the N9 boots with the yellow triangle with the message that I lost my warranty and It doesn't connect automatically to my email accounts. When I try to install the sillyboot, I get acess denied on /sbin/prenit even using devel-su and typing the password rootme. Can anybody help me?
Thanks/Bruno.

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.

Picked ape-algo from a FIASCO file
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_30.2012.07-1_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 10933 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 15 %, continuing.

    image        [state    progress         transfer     flash speed]
---------------------------------------------------------------------
[ ] kernel       [pending      0 %       0 /       0 kB      NA     ]
ERROR: SU_BEGIN_IMAGE_UPDATE_REQ terminated with error code 10: Security failure

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
Devicelock ON: cannot flash unsigned image
========================================

ERROR: Failed to flash images


Offline vital

  • NITDroid novice
  • *
  • Posts: 4
Re: N9 Kernel for Dual-Boot
« Reply #154 on: March 30, 2012, 12:23:45 am »
Has anyone fixed the Simlock ON: cannot flash unsigned image issue? I have searched all over the web with no luck yet  :'(

Offline e-yes

  • Administrator
  • I know all there is to know!
  • *****
  • Posts: 263
Re: N9 Kernel for Dual-Boot
« Reply #155 on: March 30, 2012, 12:55:32 am »
Sorry, you are out of luck, seems to be your device is locked by operator (do you have any obligatory contract?). Please, contact Nokia or operator representatives/support for more information.
cat support_request.pm > /dev/null

Offline vital

  • NITDroid novice
  • *
  • Posts: 4
Re: N9 Kernel for Dual-Boot
« Reply #156 on: March 30, 2012, 03:56:36 am »
Sorry, you are out of luck, seems to be your device is locked by operator (do you have any obligatory contract?). Please, contact Nokia or operator representatives/support for more information.

I have already went to Telcel offices (my carrier in Mexico), they doesn't seem to know what I was talking about, first they told me the unlock code came with the manual, then they gave me the default PIN code which I already had and then they asked me if what I nedeed is the PUK which I don't need, then the employee went to ask to "the engineer" and the engineer told him the only thing they could do was a fresh install, I told them already done that and they send me with Nokia support, I called Nokia support and they gave me the default cell phone unlock code "12345" which didn't work and they told me I had changed it, but I never did such a thing, then they sent me back with my carrier for "service" to the phone so I'm stuck between Nokia technical suport and Telcel technical support, I'm reading about inception to see if it's there's a way...

I forgot to mention that I have an obligatory 18 months contract.
« Last Edit: March 30, 2012, 03:58:34 am by vital »

Offline roccolocko

  • NITDroid novice
  • *
  • Posts: 9
Re: N9 Kernel for Dual-Boot
« Reply #157 on: March 30, 2012, 05:26:27 am »
Sorry, you are out of luck, seems to be your device is locked by operator (do you have any obligatory contract?). Please, contact Nokia or operator representatives/support for more information.

I have already went to Telcel offices (my carrier in Mexico), they doesn't seem to know what I was talking about, first they told me the unlock code came with the manual, then they gave me the default PIN code which I already had and then they asked me if what I nedeed is the PUK which I don't need, then the employee went to ask to "the engineer" and the engineer told him the only thing they could do was a fresh install, I told them already done that and they send me with Nokia support, I called Nokia support and they gave me the default cell phone unlock code "12345" which didn't work and they told me I had changed it, but I never did such a thing, then they sent me back with my carrier for "service" to the phone so I'm stuck between Nokia technical suport and Telcel technical support, I'm reading about inception to see if it's there's a way...

I forgot to mention that I have an obligatory 18 months contract.

I'll try nokia here in Monterrey and let you know if I had better luck.

Offline pissis

  • NITDroid novice
  • *
  • Posts: 9
Re: N9 Kernel for Dual-Boot
« Reply #158 on: March 30, 2012, 10:46:39 am »
when i use

cd C:\Program Files\Nokia\Flasher
flasher -a DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_001-OEM1-958_ARM.bin -k zImage --flash-only=kernel -f -R

at cmd it asks for permission to start the flasher after i allow it,  it blinks and nth happens...

i got all the files at right place but the zimage md5 is =fa82ad3d8a19f79f918ccb53d19a830e
and the flasher is 32bit while im using 64bit windows

so any1 got some idea on how to help me out? ;)

Offline vital

  • NITDroid novice
  • *
  • Posts: 4
Re: N9 Kernel for Dual-Boot
« Reply #159 on: March 30, 2012, 05:08:48 pm »
when i use

cd C:\Program Files\Nokia\Flasher
flasher -a DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_001-OEM1-958_ARM.bin -k zImage --flash-only=kernel -f -R

at cmd it asks for permission to start the flasher after i allow it,  it blinks and nth happens...

i got all the files at right place but the zimage md5 is =fa82ad3d8a19f79f918ccb53d19a830e
and the flasher is 32bit while im using 64bit windows

so any1 got some idea on how to help me out? ;)

Seems you're not runing flasher as administrator from the begining, right click on flasher.exe then select run as administrators

Offline pissis

  • NITDroid novice
  • *
  • Posts: 9
Re: N9 Kernel for Dual-Boot
« Reply #160 on: March 31, 2012, 11:58:37 am »


Seems you're not runing flasher as administrator from the begining, right click on flasher.exe then select run as administrators
[/quote]
 does the same thing flasher starts just barely for me to see it and closesup takes like 0.1sec...

Offline marinisaac1

  • NITDroid novice
  • *
  • Posts: 1
Re: N9 Kernel for Dual-Boot
« Reply #161 on: March 31, 2012, 06:33:01 pm »
Excuse me, does someone could give me a link to download de Fiasco Image?
I mean, I've tried with the one that it's on the post (http://tablets-dev.nokia.com/moslo.php) but it sends me an error when I'm about to download  :(

I have a N950 RM-680

Thanks!
« Last Edit: March 31, 2012, 06:40:04 pm by marinisaac1 »

Offline gesh

  • NITDroid novice
  • *
  • Posts: 1
Re: N9 Kernel for Dual-Boot
« Reply #162 on: April 01, 2012, 11:22:38 am »
guys in i have a problem when i run the flash process in the command line the program starts but just dis-pears and when i remove the phone it shows me the warning bout having changed to os and all but i cant dual boot,i have got all the files bout it just wont flash and write success.what should i do???

Offline tass

  • NITDroid novice
  • *
  • Posts: 1
Re: N9 Kernel for Dual-Boot
« Reply #163 on: April 02, 2012, 01:53:57 am »
For people having problems with flasher disappearing, try start the command prompt as administrator.

* Hit start button,
* Type 'cmd'
* Right-click on 'command prompt', select 'Run as administrator'.
* Change to the flasher directory: cd \Program Files\Nokia\Flasher
* Run flasher: flasher -i

This worked for me, where otherwise the flasher opened in a new window and quickly disappeared.

Offline be.cool

  • NITDroid novice
  • *
  • Posts: 22
Re: N9 Kernel for Dual-Boot
« Reply #164 on: April 02, 2012, 03:00:19 am »
Hi,
I'm trying to install the dual boot under my N9 Pr1.2, but whenever I execute flasher -a DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_001-OEM1-958_ARM.bin -k zImage --flash-only=kernel -f -R, I get the result below, but I had already set the Autolock to off!
Despite of that, the N9 boots with the yellow triangle with the message that I lost my warranty and It doesn't connect automatically to my email accounts. When I try to install the sillyboot, I get acess denied on /sbin/prenit even using devel-su and typing the password rootme. Can anybody help me?
Thanks/Bruno.

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.

Picked ape-algo from a FIASCO file
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_30.2012.07-1_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 10933 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 15 %, continuing.

    image        [state    progress         transfer     flash speed]
---------------------------------------------------------------------
[ ] kernel       [pending      0 %       0 /       0 kB      NA     ]
ERROR: SU_BEGIN_IMAGE_UPDATE_REQ terminated with error code 10: Security failure

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
Devicelock ON: cannot flash unsigned image
========================================

ERROR: Failed to flash images



Try to do this:

1-
Code: [Select]
flasher -F DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_001-OEM1-958_ARM.bin -f -R2-
Code: [Select]
flasher -a DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_001-OEM1-958_ARM.bin -k zImage --flash-only=kernel -f -R
It seems that if you had previously enabled the lock, this error is shown, even if you had disabled it.