Reply
Thread Tools
Posts: 1,289 | Thanked: 4,318 times | Joined on Oct 2014
#71
Originally Posted by bandora View Post
Sorry to be the one to say this, but it'll never happen. Doesn't make any sense to do so (business wise).
perhaps not on its own, but maybe, just maybe, it can assist if our board of directors want to take this further.
 

The Following User Says Thank You to nieldk For This Useful Post:
bandora's Avatar
Posts: 1,338 | Thanked: 1,055 times | Joined on Oct 2009 @ California, USA / Jordan
#72
Just throwing some ideas here, wouldn't it be better to request those assets from Nokia/(Microsoft?) and then host it ourselves?
__________________
FarahFa.com
 

The Following 3 Users Say Thank You to bandora For This Useful Post:
Posts: 1,289 | Thanked: 4,318 times | Joined on Oct 2014
#73
Originally Posted by bandora View Post
Just throwing some ideas here, wouldn't it be better to request those assets from Nokia/(Microsoft?) and then host it ourselves?
Better , yes. But.
It would require loads of storage
Bandwith
$$$ to maintain due to that
 

The Following 2 Users Say Thank You to nieldk For This Useful Post:
Posts: 10 | Thanked: 62 times | Joined on Jan 2016
#74
Torrents would be nice for storage/bandwidth, I suppose.
Too bad Nokia servers went down just as I wrote the tool
 

The Following 4 Users Say Thank You to feuerplatz For This Useful Post:
Posts: 204 | Thanked: 443 times | Joined on Jul 2012 @ Germany - Potsdam
#75
Hi, I found on an old hdd a backup.

@nieldk do you still need files for testing?

DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_001-OEM1-958_ARM.bin
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
with all files from the firmwareserver (.dcp, .vpl, .bin) for model 059J1V4 (austria, for my N9, was not sold in germany) and a german firmware with all files for 059J1V7:
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin

I never did the change from 001 to 009, because I read about "no return".

and an empty emmc (don't know the source)
DFL61_HARMATTAN_40.2012.13-7.NOMAPS_EMMC_NOMAPS.bin

and flasher 3.12.1 linux 32 and 64 bit .deb, who needs windows? ;-)

all round about 4GB.
 

The Following 3 Users Say Thank You to meemorph For This Useful Post:
Posts: 128 | Thanked: 105 times | Joined on Dec 2014 @ Hungary
#76
and i guess you have no reason to change from 001 to 009.
 

The Following 2 Users Say Thank You to ViBE For This Useful Post:
Posts: 28 | Thanked: 68 times | Joined on Jul 2021 @ Blueberry World
#77
Originally Posted by feuerplatz View Post
Hi there everyone, long time user, first time writing (used maemo since N900 but never felt the need to write before) but maybe I may be of help now.
I've got my Jolla stolen and feels they are out of stock here in Russia so I went for used N9. Somehow it was stuck with Vietnamese FW and I was unable to downgrade to the European version, so I found this thread with instructions in it, I tried to slap some stuff up to be able to write older certificates to be able to downgrade.

The CAL structure itself contains the older certificates but uses only the latest version. You can dump your own certificates yourself, they're located on /dev/mtd1. CAL structure itself starts with ConF signature. I basically watched the code at https://github.com/community-ssu/lib...b/master/cal.c and explored the hexdump. I didn't want just to zero out cert-sw because of mentioned lock code problems.

The cert-sw section starts as follows and cert itself starts as a3959780.
Code:
436f 6e46 0200 0000 6365 7274 2d73 7700  ConF....cert-sw.
0000 0000 0000 0000 1c05 0000 3a08 d376  ............:..v
c2d5 0f00 a395 9780 0200 0000 2623 0298  ............&#..
b2e4 5d4e bdc3 3d00 d089 9d00 6401 0000  ..]N..=.....d...
d003 0000 1b05 0000 022e 4fb0 aa27 b5e4  ..........O..'..
The length of cert field is 1308 bytes (0x51c, the 1c05000 sequence due to endianness). I extracted mine from mtd dump first seeking the offset with hex viewer and then with dd if=calinfo of=cert-early.bin bs=1 offset=$((0x16b24)) count=1308.

Then I wrote simple libcal program, compiled it with Qt SDK. Never managed to get around aegis without putting it in deb first, however. The code itself is selfdescriptive and the sources are there if you have your own Qt SDK and want to compile yourself. I've also attached my compiled deb and some of the certificates I've dumped from my N9's CAL area. It reads cert file from /root/cert.bin and then writes it to CAL to the newest slot.

Please be careful and only use it if you're absolutely absolutely sure what are you doing. I've managed to downgrade my N9 that way. Please don't shoot yourself in the feet. It's more of an informational post to the question discussed than everyday easy solution.
I just bought a Nokia N9 and it was a Chinese variant (came with carrier firmware, here's the ver num: DFL61_HARMATTAN_40.2012.21-3.418.2_PR_418)

Even worse, it has all the latest updates so the classic upgrade doesn't work.

I tried your application and when I read the version number, it claims to be on DFL61_HARMATTAN_10.2011.34-1_PR_001

From there, I was able to flash a region 00X firmware and successfully got a working device without any carrier branding!

Thank you so much, this will definitely help out a lot of us.
__________________
Piano keys might be machines.
 

The Following 5 Users Say Thank You to Danct12 For This Useful Post:
Posts: 252 | Thanked: 282 times | Joined on Oct 2021 @ Poland
#78
Well, I successed.
I had PR_LEGACY_342 version.
I did that:
Flash firmware with the same version to return to closedmode
Enable dev mode of course
Install cal-writer program
Put cert with PR 1.3 001 version in /root/ (as cert.bin)
Chown /dev/mtd1 to root:root
Open cal-writer
Chown /dev/mtd1 to cal:cal
Flash 001 version of PR 1.3.
Now I have first EU firmware for PR 1.3.



But, is it possible to downgrade to PR 1.1/1.2?
I heard about CMT problem then. Has someone tried that?
Maybe I could try? I have one N9 in very bad state, that has not working SIM slot, I use it for modding.
__________________
My Telegram group (Maemo / MeeGo / Sailfish):
https://t.me/linuxmobile_world
Channel for Maemo/MeeGo:
https://t.me/maemomeegoapps
 

The Following User Says Thank You to dredlok706 For This Useful Post:
Posts: 252 | Thanked: 282 times | Joined on Oct 2021 @ Poland
#79
I'm also looking for this file:
DFL61_HARMATTAN_10.2011.34-1_PR_LEGACY_001-OEM1-958_ARM.bin
__________________
My Telegram group (Maemo / MeeGo / Sailfish):
https://t.me/linuxmobile_world
Channel for Maemo/MeeGo:
https://t.me/maemomeegoapps
 

The Following User Says Thank You to dredlok706 For This Useful Post:
Posts: 1,289 | Thanked: 4,318 times | Joined on Oct 2014
#80
Originally Posted by dredlok706 View Post
I'm also looking for this file:
DFL61_HARMATTAN_10.2011.34-1_PR_LEGACY_001-OEM1-958_ARM.bin
That is hard to find.
but, here you are

https://mega.nz/file/FhUS2aYa#viyH2R...ajMg0Jhfxu4-I0
 

The Following 3 Users Say Thank You to nieldk For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 21:04.