nisprog reflash utility

murphys_law · **Joined:** Tue May 24, 2016 1:45 am **Posts:** 216

savarenova wrote:

Well, well, well! So i got something right now. Now i got "No global l0. Please select + configure l0 first" error with your nisprog.ini (copied from youtube). and i've adressed to scantool_manual and find out that i have to set some Dumb driver. Plz give me a hint. I need to champion this app ))) I have CH340 KKL

You'll probably need to post the command window with all the commands that you entered to get help.

savarenova · **Joined:** Fri Feb 10, 2017 6:46 am **Posts:** 70

murphys_law wrote:

savarenova wrote:

Also, anyone heard of NDS2's hidden ability to download rom?

Yes, it's not much of a well kept secret.

Its also not needed as nisprog is much better for dumping and flashing.

can u explain me on how to do it? if you know plz PM me ) im going down to take my laptop from car.

savarenova · **Joined:** Fri Feb 10, 2017 6:46 am **Posts:** 70

murphys_law wrote:

savarenova wrote:

Well, well, well! So i got something right now. Now i got "No global l0. Please select + configure l0 first" error with your nisprog.ini (copied from youtube). and i've adressed to scantool_manual and find out that i have to set some Dumb driver. Plz give me a hint. I need to champion this app ))) I have CH340 KKL

You'll probably need to post the command window with all the commands that you entered to get help.

APF the screenshot

fenugrec · **Joined:** Wed Jan 08, 2014 11:07 pm **Posts:** 652

savarenova wrote:

can u explain me on how to do it?

Open your nisprog.ini
you're missing the "set interface dumb" and "set port" commands

Then, read USING.txt (again)

and in nisprog, do

Code:

help nc
help dump
help set
set
help interface

Next time, don't use "plz", "u", and other lazy shortcuts. If you can't spend 2 seconds typing a word, people will not want to spend >2 seconds answering.

savarenova · **Joined:** Fri Feb 10, 2017 6:46 am **Posts:** 70

fenugrec wrote:

savarenova wrote:

can u explain me on how to do it?

Open your nisprog.ini
you're missing the "set interface dumb" and "set port" commands

Then, read USING.txt (again)

and in nisprog, do

Code:

help nc
help dump
help set
set
help interface

Next time, don't use "plz", "u", and other lazy shortcuts. If you can't spend 2 seconds typing a word, people will not want to spend >2 seconds answering.

That means commands in my nisprog.ini is written incorrect?
Attached please find the screenshot of my ini. Ok, I will try tomorrow. Thanks.

murphys_law · **Joined:** Tue May 24, 2016 1:45 am **Posts:** 216

savarenova wrote:

fenugrec wrote:

savarenova wrote:

can u explain me on how to do it?

Open your nisprog.ini
you're missing the "set interface dumb" and "set port" commands

Then, read USING.txt (again)

and in nisprog, do

Code:

help nc
help dump
help set
set
help interface

Next time, don't use "plz", "u", and other lazy shortcuts. If you can't spend 2 seconds typing a word, people will not want to spend >2 seconds answering.

That means commands in my nisprog.ini is written incorrect?
Attached please find the screenshot of my ini. Ok, I will try tomorrow. Thanks.

The "#" in your ini indicates that particular line will not be read by the program.

You need to remove it for those commands to be run.

murphys_law · **Joined:** Tue May 24, 2016 1:45 am **Posts:** 216

Before you ask the next question, you will need to check and see which com port your adapter is actually hooked up to on your pc and specify that as well.

Odds are it is not port 1.

savarenova · **Joined:** Fri Feb 10, 2017 6:46 am **Posts:** 70

murphys_law wrote:

Before you ask the next question, you will need to check and see which com port your adapter is actually hooked up to on your pc and specify that as well.

Odds are it is not port 1.

I know how to change com port in system properties. So that wont be an issue. More question will arise tomorrow. Thanks for everyone =)

savarenova · **Joined:** Fri Feb 10, 2017 6:46 am **Posts:** 70

Gents, so I've finally dowloaded the rom. Configured com port, deleted this things # from .ini and finally got connected to ecu, with previously warmed up engine and on IGN ON position of key (before this I tried to dump with engine running - that was mistake :mrgreen:

).

But then i've faced to "setkeys" issue. Obviously championed over this issue (actually I was lucky, because 2nd key in the list, permitted me to upload kernel to RAM). :wink:

Then i've started the process which took me 200 seconds approximately. Actually i've entered name of rom with bin extention, think its not a problem (advise me).

Then i got "full metall panic" :shock:

, because after dumping process, nisprog was terminated by windows (something like application shutdown) without stopkernel command (fans were working all the way since kernel upload). Smoked 3 cigarettes while trying to reconnect with ECU, unfortunately I'd failed.

Then just opened hood and reconnected battery after a minute. Everything came into status quo. Engine is running well. :mrgreen:

That is a short story of how i got instant heart attack. Can you dig in my ECU? Advise on further actions?

murphys_law · **Joined:** Tue May 24, 2016 1:45 am **Posts:** 216

savarenova wrote:

Gents, so I've finally dowloaded the rom. Configured com port, deleted this things # from .ini and finally got connected to ecu, with previously warmed up engine and on IGN ON position of key (before this I tried to dump with engine running - that was mistake :mrgreen:

).

But then i've faced to "setkeys" issue. Obviously championed over this issue (actually I was lucky, because 2nd key in the list, permitted me to upload kernel to RAM). :wink:

Then i've started the process which took me 200 seconds approximately. Actually i've entered name of rom with bin extention, think its not a problem (advise me).

Then i got "full metall panic" :shock:

, because after dumping process, nisprog was terminated by windows (something like application shutdown) without stopkernel command (fans were working all the way since kernel upload). Smoked 3 cigarettes while trying to reconnect with ECU, unfortunately I'd failed.

Then just opened hood and reconnected battery after a minute. Everything came into status quo. Engine is running well. :mrgreen:

That is a short story of how i got instant heart attack. Can you dig in my ECU? Advise on further actions?

Definition added.

https://github.com/murphyslaw05/NissanD ... 4198b13c4b

savarenova · **Joined:** Fri Feb 10, 2017 6:46 am **Posts:** 70

murphys_law wrote:

savarenova wrote:

Gents, so I've finally dowloaded the rom. Configured com port, deleted this things # from .ini and finally got connected to ecu, with previously warmed up engine and on IGN ON position of key (before this I tried to dump with engine running - that was mistake :mrgreen:

).

But then i've faced to "setkeys" issue. Obviously championed over this issue (actually I was lucky, because 2nd key in the list, permitted me to upload kernel to RAM). :wink:

Then i've started the process which took me 200 seconds approximately. Actually i've entered name of rom with bin extention, think its not a problem (advise me).

Then i got "full metall panic" :shock:

, because after dumping process, nisprog was terminated by windows (something like application shutdown) without stopkernel command (fans were working all the way since kernel upload). Smoked 3 cigarettes while trying to reconnect with ECU, unfortunately I'd failed.

Then just opened hood and reconnected battery after a minute. Everything came into status quo. Engine is running well. :mrgreen:

That is a short story of how i got instant heart attack. Can you dig in my ECU? Advise on further actions?

Definition added.

https://github.com/murphyslaw05/NissanD ... 4198b13c4b

Thanks man.
I suspect this is not all tables from rom that could be edited? Correct me if Im wrong.
One more question: How to find "Setkey value" from rom?
Kudos to everyone )

murphys_law · **Joined:** Tue May 24, 2016 1:45 am **Posts:** 216

savarenova wrote:

murphys_law wrote:

savarenova wrote:

Gents, so I've finally dowloaded the rom. Configured com port, deleted this things # from .ini and finally got connected to ecu, with previously warmed up engine and on IGN ON position of key (before this I tried to dump with engine running - that was mistake :mrgreen:

).

But then i've faced to "setkeys" issue. Obviously championed over this issue (actually I was lucky, because 2nd key in the list, permitted me to upload kernel to RAM). :wink:

Then i've started the process which took me 200 seconds approximately. Actually i've entered name of rom with bin extention, think its not a problem (advise me).

Then i got "full metall panic" :shock:

, because after dumping process, nisprog was terminated by windows (something like application shutdown) without stopkernel command (fans were working all the way since kernel upload). Smoked 3 cigarettes while trying to reconnect with ECU, unfortunately I'd failed.

Then just opened hood and reconnected battery after a minute. Everything came into status quo. Engine is running well. :mrgreen:

That is a short story of how i got instant heart attack. Can you dig in my ECU? Advise on further actions?

Definition added.

https://github.com/murphyslaw05/NissanD ... 4198b13c4b

Thanks man.
I suspect this is not all tables from rom that could be edited? Correct me if Im wrong.
One more question: How to find "Setkey value" from rom?
Kudos to everyone )

Not even close to "all" and likely all of them will never be known.

The keys are already known as you ran the kernel already.

savarenova · **Joined:** Fri Feb 10, 2017 6:46 am **Posts:** 70

Noooooo, this is very sad :cry:

swami · **Posted:** Sat Mar 18, 2017 7:48 pm

took a crack at running the kernel today
vq23 ecu from a jdm J31

got the error
Using 3908 byte payload, padding with garbage to 3936 (0x0F60) bytes.
SID 27: seed = 0x00 0x00 0x2A 0x98 ; using NPT_DDL algo (scode=0x3C24EB50),
got bad 27 02 response : General_Error, Requested_SID_securityAccess Error_inval
idKey
sid27 problem

murphys_law · **Joined:** Tue May 24, 2016 1:45 am **Posts:** 216

swami wrote:

took a crack at running the kernel today
vq23 ecu from a jdm J31

got the error
Using 3908 byte payload, padding with garbage to 3936 (0x0F60) bytes.
SID 27: seed = 0x00 0x00 0x2A 0x98 ; using NPT_DDL algo (scode=0x3C24EB50),
got bad 27 02 response : General_Error, Requested_SID_securityAccess Error_inval
idKey
sid27 problem

That's means the kernel doesn't have the security keys from your rom.

RomRaider

Forum rules

nisprog reflash utility

Who is online