Results 1 to 10 of 24
-
16th January 2020, 02:08 AM #1
nuvi 3790
hi
i have problem with nuvi 3790, after loading logo Garmin, apear SYSTEM SOFTWARE MISSING , can you for HWID 1101, software version 510 prepare Sd patch. Please .petrivulcan Reviewed by petrivulcan on . nuvi 3790 hi i have problem with nuvi 3790, after loading logo Garmin, apear SYSTEM SOFTWARE MISSING , can you for HWID 1101, software version 510 prepare Sd patch. Please . Rating: 5
-
16th January 2020, 07:11 PM #2
-
The Following 1 Users Say Thank You to FireFox58 For This Useful Post:
- [ Click To Expand ]
-
petrivulcan (17th January 2020)
-
17th January 2020, 03:58 PM #3
thank you for help, but still dead. i open one file create by updater (update .log)
Parsing "del,0:/.System/gupdate.gcd"
Error
Parsing "rrgn,154,2:/BUK_154.bin"
Error
Parsing "xrgn,14,2:/Garmin/Updater/1101/14.bin"
Error
Parsing "xrgn,127,2:/Garmin/Updater/1101/127.bin"
Error
Parsing "reboot"
nüvi blade Series Software Version 5.10, UID: 0, HWID: 4294967295
-
5th March 2020, 03:46 PM #4
I missed seeing this thread until now and maybe the OP has given up on the device. "System Software Missing" message can have two senses. At it's most benign it means that the device is missing the main system software as region 14 is empty, or that the region is corrupt or incomplete from an earlier flashing (rgn14 is flashable with fw_all.bin aka 14.bin in an otherwise healthy device, usually done as an RGN file). In such cases the device will always default to preboot mode and maintain it constantly while powered on so just re-loading the original fw as an RGN file via Updater.exe will easily restore the device. At it's most serious, the message indicates that the internal flash memory has some damage which prevents the device loading fw to boot normally. In that latter case preboot is usually not available and the device is usually not economically repairable. The failure of flashing from SD is not welcome news but doesn't mean that preboot isn't available in the first case, in the second case (flash damage) neither preboot or SD flash will be available. Try this: . Extract it to find a safely named RGN file for HWID1101 and Updater.exe. Drag the RGN onto Updater.exe, connect the nuvi to a rear USB2 port of a PC and flash if the window next to "USB Device" on Updater's GUI is populated with the device details. If no details appear and Windows Device Manager does not show it listed as "GARMIN Device" then preboot isn't reached.
PS: I think nonvol may be in region 41 not 154 in nuvi 37xx series. Also fw doesn't need to be patched using IMGPatcher (aka Universal Firmware Patcher) to use unlocked maps.
-
7th June 2023, 04:16 AM #5
i cant download this file. please help me what the decryption key for download
Last edited by mamik19; 7th June 2023 at 05:02 AM.
-
7th June 2023, 06:43 AM #6
I think there's a problem with that hyperlink, try this direct one:
IMPORTANT: Ensure that yours is a US/EU firmware device which has HWID of 1101. I note your location is Indonesia and i recall that there were several versions of 37x0 sold in Asian markets with different HWIDs therefore different firmware.
-
The Following 1 Users Say Thank You to B1ng0 For This Useful Post:
- [ Click To Expand ]
-
mamik19 (7th June 2023)
-
7th June 2023, 08:42 AM #7
thanks for the fast reply. But how can i found the version on this stuck device. i think my mine is Asian market/Taiwan device.
-
7th June 2023, 10:52 AM #8
To read the HWID of a bricked device you must use the G7ToWin. It's old but works to read 'bricked' devices in preboot mode. Do an internet search for this: "Use program G7ToWin to retrieve your HWID" but if you can't find it PM me because it's against the rules to post links to concurrent forums.
-
The Following 1 Users Say Thank You to B1ng0 For This Useful Post:
- [ Click To Expand ]
-
mamik19 (7th June 2023)
-
7th June 2023, 03:24 PM #9
Big thanks for your advice. Sorry for my bad english.
Unfortunately my device stuck on the logo, and every i connected to the laptop (win10) just apear sound like "connected device" after 2-4 second apear sound "ejected device".
With that problem i can't connect to laptop, for just flash my device.
-
8th June 2023, 06:08 AM #10
You must know the basics before attempting to cure this device which is hopefully only 'soft-bricked' due to corrupt data in a file essential to a successful boot-cycle. So let's take it slow and do it "step-by-step" because it'd be too confusing if you're given the entire process at once.
Access to preboot mode is essential for curing. Most Garmin automotive devices access preboot by holding the lower left corner of the screen, making the process relatively simple. Unfortunately US/EU 3xxx series devices are more difficult because the preboot hold position is much harder to accurately access when the screen is blank. I believe that all Asian 37x0 models are the same as the US/EU 3xxx devices in that regard, but if the following procedure doesn't work then try holding the lower left corner instead.
Now for some general tips: It's better to use a USB2 port rather than a USB3 port if possible. It's also ideal to use a Windows desktop PC rear USB2 port but if you only have access to a laptop then the procedure should still work properly if you use a USB2 port directly connected. Avoid using a hub, connect only directly. Be sure to use a "known-good" micro-USB cable.
Before you turn off the device, note the position as below on the screen (just above the G) because that's where you'll need to hold to access preboot mode. I usually thoroughly clean the screen then leave a clear thumb-print to mark the spot before turning off, otherwise it's difficult to find it accurately when the screen's blank.
You must force the device completely off by holding the power button down until the screen goes blank. Check that the position you've thumb-printed is still clearly visible on the screen.
- Go to Windows' Device Manager on the computer and leave it open and visible
- Plug the USB cable into the computer's port
- Pick up the device in your left hand and hold the screen firmly with your thumb as shown above, fingers behind the device
- Watch Device Manager's alphabetical list of devices and plug the microUSB into the device's socket which will power it on - keep your thumb firmly on the screen!
- You should see "GARMIN USB Device" appear in the list and hear the Windows connection sound. If that happens the device is in preboot, so keeping the firm pressure on the screen, please time how long it stays in that mode before it disconnects from Windows. It may be as short as 10 seconds and it's helpful to know how long we have to work to establish a flash later.
Once you can confirm that your device will access preboot, we will then go through the procedure to find the HWID which can be done either using G7ToWin or via a previous files backup of the device if you have one (let me know if you do please). If you don't understand anything above just ask, i'll be happy to explain until you do. Good luck, if preboot is available to it we can fix it eventually.
PS: Your English is fine!Last edited by B1ng0; 8th June 2023 at 06:32 AM.
-
The Following 1 Users Say Thank You to B1ng0 For This Useful Post:
- [ Click To Expand ]
-
mamik19 (8th June 2023)
tomtom xl
Hi Does anyone know how I can reset my TomTom...