Quote Originally Posted by neyd View Post
I got all files from the other GPS but since there was no gupdate file I decided to update that one too, to possibly get that file, now I have two bricked GPS's
Ouch! One bricking is unfortunate. Two seems downright cruel. GarminExpress hasn't been a problem bricking devices for some time now, I think we need to look at your procedures very closely.

I do however have the Partnumber, 006-B1722 but I can not find any firmware for that.
Where and when did you buy these devices, new or secondhand? I suppose they're both out of warranty or you wouldn't be looking for help here. The reason I'm asking where you bought them is that the HWID of 1722 is common to Asian firmware versions of nuvi 25x7. I thought that Western versions of 25x7 only have either HWID of 1582 or 2077 (C4 chip version) although there was a device named 'nuvi 2567' sold in Europe with Eastern European maps loaded as OEM. I'd have assumed it was a regional version of the 25x7 with either of those Western HWIDs. Maybe not. Here's the bad news if it has HWID 1722, it seems there hasn't been any specific firmware updates for that EU 2567 and it wasn't sold for very long either it would appear:
Code:
Please Login or Register to see the links
I did try to connect through Updater, using some QuickCure.rgn file I got somewhere, just to see if I could connect, If I use the setting Serial, then I get to Initializing but then Garmin not responding (tried all Baud rates), Nuvi is visible as the USB drive below but when selecting that Iget instantly Garmin not responding.
Like all modern devices it connects via USB only, not serial. Make sure you have [Only registered and activated users can see links. ] loaded, without that your PC cannot connect it in pre-boot mode for USB. Pre-boot is also tricky to hold in some recent devices as it only lasts for a matter of seconds if a flash isn't started very quickly. Once a flash is initiated and correctly established the pre-boot mode will be maintained until the flash completes.

I have also tried to get GPS ID using G7ToWin but then I get Serial Port Timeout
Same reason as above maybe, make sure you've set it up properly as per initial post here: [Only registered and activated users can see links. ]. However, first things first. From here on, we must 100% confirm the HWID. Was the 'Partnumber 006-B1722' you quoted got from the GarminDevice.xml of either device, if so which one and when? Did you keep a backup of either device before you did the attempted updates with Garmin Express? Try to connect the devices again to G7ToWin and follow the tut in the first post of that thread exactly.
  • Start G7To Win before you try to get the device into pre-boot, select USB for COM Port in Configuration and then connect the device as follows.
  • Ensure device is fully OFF. You may need to force it off by holding the power button down for between 10 and 30 seconds if it won't turn off normally.
  • Plug a USB cable into a rear port of the PC. Don't use a hub or a front port.
  • Hold the top left corner of the screen firmly (use your left thumb is easiest I find), you'll need to keep steady and continuous pressure so don't ease off until this is finished.
  • Plug the USB cable into the device, that will power it up.
  • Very quickly in G7ToWin's GPS menu click on 'Get GPS ID' (have the GPS dropdown already open with cursor positioned over 'Get GPS ID' ready to select).
  • If it shows any 'USB Error' popup window immediately click OK

There's in fact two reasons for doing the above (1) obviously, to confirm the HWID is 1722 and (2) very importantly, to check that the devices can access pre-boot. Without pre-boot there's no way to load any cure firmware.

I have no firmware and no connection, I have a trash bin -should I use that or do I still have a chance?
I have a bigger trash bin, you can chuck 'em my way. So, no firmware specific to it it would seem and (as yet) no connection but you still have your sense of humor so let's battle on. If a device can power on as far as the logo splash screen, then generally it can be cured.

Thank you for any help.
Don't thank me yet, what I'm likely to end up proposing could end up with at least one of your devices dead as a dodo, coz we may need to make a franken-firmware to attempt a cure. Let's hope that you can get QuickCure going when we sort out pre-boot and USB connection.