nuvi 610 has white screen after flashed with wrong firmware

Disappointing but not at all that unexpected either now on checking further. I've been able to source a nuvi 310 to dump it's region 14. It's just not quite big enough to fit the fw_all.bin from 6xx, short by only 135,168 Bytes (132kB or a lousy 0.12 - 0.13 MB) in the words of Maxwell Smart "missed it by that much". More bad news. Mostly all fw_all.bin files can be compressed but unfortunately 6xx is one of only a couple of Garmin's firmware that can't be compressed successfully. Some more explanatory background info, when you flashed the full fw 3xx to your 610 the region layout was resized, a bit like a re-partitioning a drive, so the space available in region 14 became 10,223,616 bytes (~9.75 MB) whereas the 6xx layout is somewhat larger.

[Only registered and activated users can see links. Click Here To Register...]

Now, it's logical to think "Why not just flash the full 6xx firmware with SD bin files and re-size back in the process?". So i should explain a little about why flashing the full 6xx firmware might not work using SD. The Ldr.bin (boot.bin) initiates flashing of the main system software (firmware). You presently have 'foreign' 3xx Boot BLK and X-loader in the 6xx device's regions 5 and 43. They were flashed there via an RGN in preboot using 3xx's boot.bin which is initially stored in region 12, a virtual rather than physical region. We are now intending to overwrite those regions with the correct data at the very same time that they are being used too by Ldr.bin to write new data to region 14 at the same time it's attempting to change the region layout resize back to a 6xx device from the present [foreign] 3xx layout. Can you see the possible complication? It's this: Writing to a region while it's being used can be potentially deadly and give you a paperweight.

Still wish to try? I can now only give you one option: Attempt to write the full 6xx firmware to re-set the region layout sizes and change it's HWID back to 0596 (Fingers crossed it doesn't die on the spot). If you want to precede post again and I'll make another SD kit. It seems you have little to lose though by going ahead.

PS: Your dumped nonvol region 41.bin file will be empty, 0 Bytes. That's why it shows an error for it too in update.log file.

Thank You for all You are doing to help me.
I will try that method.
I want to proceed.

Ok thanks for that. I've made the kit, same instructions as previously for use:

Spoiler:

[Only registered and activated users can see links. Click Here To Register...]

Good luck. Anything could happen or not happen. The device might refuse to flash; try to flash but fail; flash but die; or be flashed and fixed. :fingers-crossed:

Regardless the outcome, I really admire your efforts Butters. That's the spirit which have died years ago on many other forums.. ;)
Sorry za offtopic..

Haha! Thanks, but nothing is off-topic for me when i'm getting a compliment (to tell the truth I find this stuff fascinating so I'm getting as much or more out of it as the OP ;) ). It's certainly true what you've said about Garmin forums generally. Let's keep the spirit going here .... as you do too janch. I know you help out a lot in other sections here. Cheers.

I have tried this method.
The flasning was not succesful, but after this pre boot mode is available again.

When I try to flash propper SW for Nuvi 610 with updater, the flashing process starts, but after some time it gives an error.
It is stil Nuvi 310 , SW V 5.20 in Webupdater.

When I turn on the device it starts loading, but after some time the display is white again.

Is there any solution for this situation?

Getting preboot back increases the options now so there still might be a solution. Try to flash the lowest available version of 6xx firmware named OUT.RGN. V2.30 V2.60 is the lowest I can find:

Code:

---

http://gawisp.com/perry/nuvi/nuvi610_260.exe

---

To find the GCD, extract [don't run] the EXE and look in Nuvi folder for Garmin folder containing GUPDATE.GCD then convert with RGN_Tool to out.rgn. If you fail let me know the error message Updater displays.

When I tried to flash this FW, the device could enter Pre Boot mode propperly, but the flashing process could not be finished.
After enetering the Pre Boot mode and starting Flashing the device disconets and the flashing process could not be finished.
I have tried about 50 times.
Ther was always an error message that the device is not connected with updater or error message:

IOU_UTILITIES.CPP-203-2.8

After a couple of tries there was a message on the display "SYSTEM SOFTWARE MISSING", but the updater still could recognize the device and I tried to flash it again, but unsuccessfuly.
After that there was an error message :
The Garmin device is unable to program the requested memory region.
This could bee due to an incompatibility between this application and the Garmin device.
If this error continues to occur, please contact Garmin tehnical support.

Webupdater stil can recognize the device as Nuvi 310, SW V 5.20 .
When I turn on the device the display is white again and I can not enter Pre Boot mode.

Now the device also can not enter mass storage mode.
I also tried previous SD Card flashing methods, but It did not work.

Is there any solution for this situation?

Quote:

---

Originally Posted by alexandarser [Only registered and activated users can see links. Click Here To Register...]

......
Now the device also can not enter mass storage mode.

---

Damn!

Quote:

---

I also tried previous SD Card flashing methods, but It did not work.

---

When last_id.log file is created after the card is used to flash, it won't allow another flash attempt unless that LOG file is removed. Regardless, the device wouldn't flash with the full 6xx firmware previously in preboot which I think might be due to Updater.exe detecting fw/hw incompatibility of some kind. However if you get preboot back we can maybe try some other things.

Quote:

---

Is there any solution for this situation?

---

Certainly running out of options and not having preboot shortens the chances very much further I'm sorry.

If you're desperate enough we can try to delete rgn14 which usually will force it to default into preboot mode. I'm not sure if that will happen with this damaged device but if you're prepared to try look behind the spoiler:

Spoiler:

[Only registered and activated users can see links. Click Here To Register...]

I'm sure you know the procedure and terms regarding risk by now. Good luck.