Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Porting Sailfish to N9

    Reply
    Page 49 of 205 | Prev | 39   47     48   49   50     51   59 | Next | Last
    rainisto | # 481 | 2013-12-09, 07:33 | Report

    Originally Posted by flotron View Post
    So simlocked n9s can't install Sailfish. Even if you unlock it after contract. Must be factory unlocked

    Can anyone confirm this?
    Are you sure that that the device doesnt have devicelock enabled? As that one prevents doing to open mode also (and has the same error message on flasher). 1st you need to disable devicelock and then you can go to open mode.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to rainisto For This Useful Post:
    ZogG

     
    Alecsandru | # 482 | 2013-12-09, 07:33 | Report

    how about n900?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    rainisto | # 483 | 2013-12-09, 07:36 | Report

    Originally Posted by flotron View Post
    after using


    I still get "Simlock ON: cannot flash unsigned image"

    So this is the end of my adventures with Sailfish and n9?
    erase-mmc should not be needed as erase-user-data also erases mmc partition, flasher might get confused as you are trying to erase mmc two times in same command so:

    flasher -f -F main.bin --erase-user-data=secure -F emmc.bin

    And make sure that you dont have devicelock enabled in the harmattan.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    flotron | # 484 | 2013-12-09, 07:41 | Report

    Originally Posted by rainisto View Post
    erase-mmc should not be needed as erase-user-data also erases mmc partition, flasher might get confused as you are trying to erase mmc two times in same command so:

    flasher -f -F main.bin --erase-user-data=secure -F emmc.bin

    And make sure that you dont have devicelock enabled in the harmattan.
    I'm very sure no device lock.

    I get "Simlock ON: cannot flash unsigned image" when i try to:

    flasher -a main.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R

    Edit | Forward | Quote | Quick Reply | Thanks

     
    rainisto | # 485 | 2013-12-09, 07:42 | Report

    Originally Posted by plourde View Post
    I have tried to reflash to factory since i messed up and after the moslo kernel was installed since the partition is different I am having issues reflash since there is a mismatch how can i fix this

    Partition table mismatch (start=112672768, sum=104480768). You may want to use the no-preserve option or flash an erase image

    thank you
    Most of the people here just point to you to generic flashing instructions that unfortunately wont help you. You should just do what the error message tells you to do.

    ADD "--no-preserve" to your flashing command, that will repartition the device for you. Normal flashing instructions fail to mention this.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 4 Users Say Thank You to rainisto For This Useful Post:
    amandalam, mattaustin, mikecomputing, nokiabot

     
    rainisto | # 486 | 2013-12-09, 07:47 | Report

    Originally Posted by flotron View Post
    I'm very sure no device lock.

    I get "Simlock ON: cannot flash unsigned image" when i try to:

    flasher -a main.bin -k zImage_2.6.32.54-openmode_l2fix --flash-only=kernel -f -R
    Then your out of luck, since the only occasion when ""Simlock ON: cannot flash unsigned image" error is supposed to come is:

    a) operator sim lock is not unlocked properly

    b) end user has set devicelock code for example from default empty string to "12345"(or whatever) and they have forgotten to clear it back to default empty string with --erase-user-data=secure when they have reflashed the default factory image for secure mode.

    So if flashing back to normal secure mode with:
    "flasher -f -F main.bin -F emmc.bin --no-preserve --erase-user-data=secure" doesn't solve the problem, then you are stuck with Harmattan.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to rainisto For This Useful Post:
    flotron

     
    flotron | # 487 | 2013-12-09, 07:51 | Report

    Originally Posted by rainisto View Post
    Then your out of luck, since the only occasion when ""Simlock ON: cannot flash unsigned image" error is supposed to come is:

    a) operator sim lock is not unlocked properly

    b) end user has set devicelock code for example from default empty string to "12345"(or whatever) and they have forgotten to clear it back to default empty string with --erase-user-data=secure when they have reflashed the default factory image for secure mode.

    So if flashing back to normal secure mode with:
    "flasher -f -F main.bin -F emmc.bin --no-preserve --erase-user-data=secure" doesn't solve the problem, then you are stuck with Harmattan.
    The phone is unlocked (not factory unlocked)

    Well... i have a nice harmattan clock now

    Edit | Forward | Quote | Quick Reply | Thanks

     
    billranton | # 488 | 2013-12-09, 08:09 | Report

    You could try setting the lock code from harmattan, then setting it to an empty string?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    flotron | # 489 | 2013-12-09, 08:14 | Report

    No lockcode, is simlock

    Edit | Forward | Quote | Quick Reply | Thanks

     
    nieldk | # 490 | 2013-12-09, 08:29 | Report

    Originally Posted by flotron View Post
    No lockcode, is simlock
    Wow, this is something to dig into, ....
    hopefully a solution can be found for this situation

    one thing, dont really think its an issue, but, have you enabled a SIM PIN Code?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 49 of 205 | Prev | 39   47     48   49   50     51   59 | Next | Last
vBulletin® Version 3.8.8
Normal Logout