It was expected that all bin files would be empty. But I want to know if after running dumper v0.17 there appears string "HELLO NOEMAN" at offset 5 in gupdate.gcd.
dumper-0.17 with BIN created by dumper-0.15 (and RGN13.BIN just created) runs for 4 min but do nothing. All BINs are zero lenght.
Sorry.
It was expected that all bin files would be empty. But I want to know if after running dumper v0.17 there appears string "HELLO NOEMAN" at offset 5 in gupdate.gcd.
No string appeared on the display, except one something like "hei charlie, why don't you buy a TomTom and install it? f*k*ff!"".
On the display? No, I'm talking about gupdate.gcd file If you can't quickly open it with a HEX editor, then can you send it to me after running dumper v0.17?
Hi one thing, no one could make that dumper would read the full contents of the EPROM and duplicating in cf?
In other words as a list and copy in msdos
regards
Spanish:
Hola una cosa, no se podria hacer que ese dumper leyese el contenido completo de la eprom y lo duplicase en la cf?
O sea como un list y copy en msdos
Saludos
We can dump flash regions one by one and save them on CF card, thus dumping the whole flash chip contents. The problem is we haven't yet found a way to write big amounts of data to CF card. Currently we can only create files with specified names on CF card, but we can't write to those files! Weird device..
I not sure this is what you are asking but I looked at dump 0.17 with Ultraedit and found "Hello Noeman" at 0124f0 hex.
I am running 4.5 on a 2006 in the US let me know if I can help.
I haven't done any real programming in years but will be glad to do what I can.
I will be leaving for a day trip in about an hour but will be back this evening. Will check back then.
We're finally lucky! It really writes the string. Can you stay here a little bit? I want to test if gupdate.gcd can be extended by writing past it.
And then I will probably finish the dumper within 30 minutes.
Bookmarks