Re: probably broke my n9
 

can you give me quick steps for the process i need to do to rewrite cert-sw as i probably am stuck on pr006 itll be really helpful if you could explain a little about what i have to do

BTW i have got the n9 back (but on pr006 which sucks as no cmt)
i have developer mode
and have aegis

Re: probably broke my n9
 

From the third link I gave you:

Step 1: Obtain an older cert.
A: Dump it from your /dev/mtd1 or B: use the cert from that post.

Step 2: rename the the cert and place it in '/root/' so you end up with '/root/cert.bin'

for example:
Step 3: Install that deb (compile it yourself from source, if you want)
note it has to be installed from com.nokia.maemo origin. So you need to have aegis-install hack.

Step 4: Invoke cal-writer as root from command-line.


NO GUARANTEES as I never tried it myself.

Re: probably broke my n9
 

i did the steps you said but it gives an error

Error: open(/dev/mtd1): permission denied
couldnt open cal for writing

and before you say yes i did install it by doing
aegis-dpkg -i <file address>
also i did have the cert.bin in the root directory and yes i did run it as root

EDIT: i tried it out with inception privleges and it probably worked
the last thing it says is
debug: 2: nand_write: 4096 bytes to 0x000e3000 retval : 0
is that a good sign? even if it is or isnt ima try flashing and tell please gimme the news while im flashing

Re: probably broke my n9
 

You can't be in openmode, as it disables writing to CAL. Are you?
Else try this and try again

If that doesn't work you need to figure out why you don't have all rights to write to CAL. I can't think of what's blocking that.

If it works you need to change the owner of mtd1 back:

Re: probably broke my n9
 

my man it worked im on pr001 now im just waiting for zeroise to finish its thing so that i can check if the cmt flashing of the pr003 works damn thanks man youre a genius i might just use my n9 as a daily driver now

inception does actually add a whole new level of accessibility

Re: probably broke my n9
 

heres the output of the flash
cmt still wont flash if theres any fix for that will have the n9 back to speed

Re: probably broke my n9
 

edit: just realised that this is repeating info, sorry.

If the phone has ever been flashed with 003, cmt might only be flashed using 003, as you see here.

Re: probably broke my n9
 

Oh boy you have damaged CMT hardware or software. In your case it's software because only CMT-mcusw fails, the other CMT parts ARE flashed, actually a good sign.
Basically if you flash new RPL file specifically for your phone it might be fixed. Unfortunately, we can't get these files from Nokia anymore. We wouldn't anyway because they were only sold to repair-shop owners / Nokia Service Centers. So that option is striked.
For users that have a working N9, there are tools out there that can backup RPL. Google RPL + BB5.
Addition from what I read; It seems that you can create RPL from PM backup. Making a PM backup and then make RPL from it and write RPL might fix it too.

The thing is we need to flash CMT of 003 variant. But we are running a bit out of options, unfortunately.

But there things you can try, what happens if you upgrade everything to 003?

Else we must resort to more experimental methods and that's a long time ago for me. In the symbian days we could use JAF over USB to flash almost everything. Now we need sort of the same thing, to force flash the right CMT.

The options are listed below, again no guarantees.

I would start to examine JAF, you probably need windows XP for this, 7 may work too but I am not sure of win10. You might one to tick dead-phone/usb mode.

Maybe Cyclone Box software can be hacked to work over USB too.Or maybe it works out of the box over USB. I don't know.

Otherwise BB5 service tool by Infinity Team might help you.

Really these are experimental waters, to see if we can revive it.
As last option would be to optain a flash-box, but then no guarantees that that will work.


EDIT: I'm trying to examine the errors from your logs. Then I found this: https://bugs.maemo.org/show_bug.cgi?id=7433. Some suggest to try different PC / OS. Might help.
Suggestion 2:
Also try with --no-preserve
Suggestion 3: Check if firmware files are not corrupt.

Re: probably broke my n9
 

i tried using --no-preserve got the same result heres the output so --no-preserve didnt help i also tried with windows 7 same result
so it seems that when i accedintally flashed the 006 firm it mustve overwritten my cmt-mcusw as i did the zeroise thing and wont let me reflash the cmt completely even on another zero hmm interisting probably needs more checking i dunno if even inception can help at this point as i dunno what state its in

Re: probably broke my n9
 

also the files are good i downloaded around 3 of the same firmware from diffrent sources(the chinese 003 firm) and all gave the same result probably not the file's fault