I don't understand what you are trying to do. Patched fw_all.bin is already present as boot.bin. And if you use this boot.bin in gupdate.gcd it won't flash anything.
19th May 2013, 06:17 PM
jinxxxxxx
Sorry I am a little new to this and a little confused. I need to go back and reread a few things. Again thank you for your time.
19th May 2013, 06:20 PM
kunix
You won't read about running fw_all.bin by using it as boot.bin in gupdate.gcd anywhere except this thread.
Even the purpose of boot.bin isn't properly described anywhere.
19th May 2013, 06:35 PM
jinxxxxxx
I have read this thread at least three times and will read it again if needed. I apologize for the trouble but I do want to understand this. My purpose for understanding this is
to be able to mod the firmware myself.
So are you saying I need to mod boot.bin to see if the mods will work or am I totally lost and over my head on this ?
19th May 2013, 07:41 PM
kunix
jinxxxxxx
No, you can test your fw_all.bin mods yourself. For example, like here:
1) Patch fw_al.bin as you want
2) Save it by clicking File->Produce File->Create EXE file...
3) Optionally pack this fw_all.bin with gfwpack utility (for more details read [Only registered and activated users can see links. Click Here To Register...]).
You could use the following command line:
Code:
gfwpack pack -verify fw_all.bin
4) Run RGN_Tool and drag fw_all.bin onto RGN_Tool's window. Make sure it prints "Section: 0800", it's uber-important.
Save the resulting GCD file and you're done.
Also there are two caveats:
1) If you don't pack fw_all.bin in step 3 then it would probably be too large (normal boot.bin is only 72 KB), and it won't be able to run as boot.bin.
2) RGN_Tool doesn't allow manually specifying the "Section: xxxx" option, instead it detects this option automatically.
And if you don't pack fw_all.bin then RGN_Tool would print "Section: BD02", which is not what you need.
Aslo I tried to make a quick and dirty nag screen patch. Can you please test it? Hopefully it would remove the nag screen. [Only registered and activated users can see links. Click Here To Register...]
19th May 2013, 08:44 PM
jinxxxxxx
Ran the new gudate but no luck. Nag screen was blank with a x in the uper left corner. waited and the nag timed out to the audio screen. Loaded the maps bak in
and the Nag screen was back to normal and timed out to audio screen.
19th May 2013, 08:52 PM
kunix
Ok, so quick&dirty solution didn't help...
19th May 2013, 08:58 PM
jinxxxxxx
No but thank you if you have anything else you want to try I will be happy to try it for you.
And thanks for the info post 272 it cleared up a lot.
19th May 2013, 09:19 PM
Neil
@kunix
More than just clearing up any misunderstandings or misconceptions, i suspect that the info in post #248 is revolutionary [it is to me but i'm a fw pre-schooler at best]. Is this something you have done before, using fw_all.bin as boot.bin for safe testing and is it likely to be a universal tool or at least widely useful for other units?
19th May 2013, 09:32 PM
kunix
I was using fw_all.bin instead of boot.bin for quick and safe testing for a long time. For example, I was flashing RGN files with fw_all.bin used as boot.bin.
The same ideas works with GCD files.
And also this trick only works if the base addresses of fw_all.bin and boot.bin are equal. It's true for almost all nuvi devices (I can't remember any exception), but it's not true for some devices, like eTrex-10/20/30, GPSmap 60CSx, and many others.
And it's only useful if you are not sure that the device have a reliable pre-boot mode implemented in the bootloader. For example, it's useful for GVN53.