Nokia Software Updater fixes the security problems(?)
Looks like Nokia is getting active: I got a new Nokia Software Updater which doesnt use the same folder anymore, now the image is in:
And it downloads the updates everytime from their server. (More secure, they think?)
But guess what: you can still simply run the dd command after the C01 has downloaded, while it's downloading the other files. This is almost too easy!
And for the AlternativeCodeSigningOID, I recently noticed that it's for Nokia Content Signing, so you might want to keep that option there to be able to install TRK etc. Here's what I use currently as swipolicy.ini:
And for dd command, I'm using dd (GNU fileutils) 3.16
C:\Documents and Settings\All Users\Application Data\Nokia\Nokia Service Layer\A\nsl_service_module_00001\vpls\www.dsut.online.nokia.com.oti.caresuite\Products\ra-6\RA6p_072403.C01
And it downloads the updates everytime from their server. (More secure, they think?)
But guess what: you can still simply run the dd command after the C01 has downloaded, while it's downloading the other files. This is almost too easy!
And for the AlternativeCodeSigningOID, I recently noticed that it's for Nokia Content Signing, so you might want to keep that option there to be able to install TRK etc. Here's what I use currently as swipolicy.ini:
AllowUnsigned = false
MandatePolicies = false
MandateCodeSigningExtension = false
Oid = 1.2.3.4.5.6
Oid = 2.3.4.5.6.7
OcspMandatory = false
OcspEnabled = true
AllowGrantUserCapabilities = true
AllowOrphanedOverwrite = true
UserCapabilities = AllFiles DiskAdmin NetworkServices LocalServices ReadUserData WriteUserData ReadDeviceData WriteDeviceData UserEnvironment PowerMgmt MultimediaDD TrustedUI ProtServ NetworkControl SwEvent Location SurroundingsDD CommDD
AllowPackagePropagate = true
AlternativeCodeSigningOID = 1.3.6.1.4.1.94.1.49.1.2.2.1 1.3.6.1.4.1.94.1.49.1.2.2.5
PhoneTsyName = phonetsy
And for dd command, I'm using dd (GNU fileutils) 3.16
posted by manko at
Monday, October 29, 2007
18 Comments:
hi
this i thought :) fast fix-hack from nokia.
but a decent fix will follow. or nsu will need a re-design.
until then we will see no new updates via nsu i guess !
buy
we've got still the phoenix... ;)
hi
can you install SIP_VoIP_Settings_v1_0_en.zip from www.forum.nokia.com (use search and search for sip )?
with the modded firmware it is not possible ?!
ciao
For this problem, I did it modifying the rom with an hex editor. The steps are:
-Conect the phone
-Start NSU and start to download firmware.
-NSU will say after the download an error.
-Modify the ROM
-Conect the phone and click "retry"
Also there is lot of third party flashers available on the market and servers which host firmware packages...
I have the same problem as "blankname" on N95 -- it becomes a brick :__(.
through previous posts, I thouhgt "blankname" succeed on the N80, but failed two days later...
maybe the update to 1.4.14 has some effect on this hack?
any ideas?
My n80 is still working and I did it well now.
If the NSU failed when it was writing in your phone and it bricked, the solution is only go to a Nokia service point and say them that your nsu failed, the warranty covers it. They will repair your phone.
Hi Guys,
I tried that on E60 as i came a bit too late i have to deal with the updated NSU, so what i'm doing is that i wait till the file is downloaded and i'm running a short EXE on it that will patch it, we have made 3 differents files (with ALL, or the full list, matching the comments we read there)
and we run that EXE when it's downloading the other file, we also have a verification EXE that we run after the flash is complete to make sure the right file was flashed.
Everything seems to go well but when we tried to install "ANY apps" even DEV cert signed app, we get the corrupted message.
Do you know if Nokia have fixed something already ?
I just sucesful flashed E60 version 2.0.618 to all files!
No, you must create a self-sign cert. You can see how in the y brownser post, the makekeys section.
I tried with N95 and the result is : PHONE BRICKED!
The only solution ( a part from Nokia Service...) IS ( i did) reflash with JAS box via FBUS.
From that point i started to to experiment various User Capabilities padding the unused space with "0d0a" (crlf) and the file .cr0 is perfect in dimension with the original, but the result is always "phone bricked".
So let me tell that it seems there is a sort of crc in some part of the firmware itself when the phone does the boot procedure...
@blankname: have you any idea about it ?
If you haven't modified anything else, ít must have a protection.
If there isn't any new firmware for n95, the nsu must have done it, but it is very strange.
I don't know if a bad modification of swipolicy can brick the phone, remember that nokia won't let modificate his phones.
Hi,
i did this:
1) open .C0R with ultraedit
2) modified (for example) the RnWaitTimeoutSeconds = 600 into RunWaitTimeoutSeconds = 601
3) saved .C0R
4) flashed with JAF and FBUS cable
Result Phone bricked
If i re-edit the .C0R with original value 600 and reflash, all goes...
It MUST be some crc.... so , WHERE??
Dear sir,
Still on E60
We tried using a self signed file like you explained in Ybrowser post. We did the exact same thing.
We also tried other file that install normally on any OS9 the results are always the same.
As soon as we apply any change to the firmware and flash it, we end up with a working phone but it will give a corrupted message with any files we tried to install, your way (self signed) or normal way (through symbiansigned.com).
Just flashing firmware normally without changes will let the phones works normally and accept the usual files.
Right now the purpose of this for us is to get access to SYS and ressources file, as we would like a copy of all API included by default in the phone.
If anyone have done this yet, please let us know.
If someone have it working and need a software that will dump the files on the MMC or through BT, let us know, we can supply the software.
I'll give it a try now and tell you in a few hours
Thanx for your advice !
Btw, do you know if any one got copy of SYS and ressources directories ?
Hey guy ! You was absolutely right ! we did it as you suggested and it worked as a charm, using Ybrowser select all files, sent by bluetooth and now we have complete backup of SYS and RESOURCE DIR !
Guy make a donation page you deserve $
We spend API partnering request with Nokia and they stole our money with FLAT bitch excuse ! your solution will help us to write our own DLL/API !
FUCK THEM !
i used to use call recording application called livepvr on my e60 which is a s60 3rd. since i changed to a nokia e51 this application records calls with a reminder restriction so that every couple of seconds a beep is sent into the conversation. is there a way removing this restriction as it was with symbian 9.1?
Post a Comment
Subscribe to Post Comments [Atom]
Links to this post:
Create a Link
<< Home