I have tried two pc's. When the gps worked I was able to use both of my computers to connect to it.
Printable View
I have tried two pc's. When the gps worked I was able to use both of my computers to connect to it.
I'm suspecting a damaged flash chip. But maybe lolypop000 or kunix can help. Let's see if it can get far enough into the boot to dump regions to a microSD card. It cannot do that with the cure fw loaded, so you will have to flash the original 6.20 fw back to it in preboot. You have that in Loly's repair pack.
Then extract this onto a clean microSD:
Ensure the unit is fully off by holding on/off button for ~6 seconds. Place card in the unit and turn it back on. If the flash is successful you'll see 'Loader' on the screen and it will try to reboot. Remove the card and see if a file has been created in the root named 41_backup.bin. If it's there, don't upload it yet just advise the outcome.
will I lose the saved data by trying any of this? I would like to recover the mileage only don't care about the rest.
When you use pack from Neil all data will be on your nuvi.
When you flash in pre boot with folder for repair, process finish or you have some error?
Flash take about 30-40 second so you have time to flesh before nuvi restart after 1 min 18 sec.
I never get an error code, so I will proceed tonight, thanks
Try with tutorial from post #18 and let us know if your nuvi work after this.
No way you can lose data by trying to write to the card. The question is whether your data is still there or was already lost when it bricked. If we find that the unit can write to the card we can maybe help you recover any existing internal files also.Quote:
Originally Posted by amos1 [Only registered and activated users can see links. Click Here To Register...]
I was able to try what Neil said in post 22 with no results but I need to try it again this weekend.
If the conventional method of copying to card doesn't work [because the unit's not booting far enough], there is another method using a modified boot bin flashed via updater.exe as an rgn file to execute the txt file. It's a little more complicated that the method in Post #22 as it requires a hex editor to replace a specific string in the boot.bin file. The patching and flashing methods are described in Post #33 here: [Only registered and activated users can see links. Click Here To Register...]. Try that if the sd pack in 22 above doesn't work.
PS: I've intentially bricked a 1390 by loading a TTS3 voice to it as the only vpm file. Result endless boot loop and unable to read from or write to microSD by usual method of using ldr.bin with update.txt file in 0972 folder. Removed ldr.bin, patched it, saved it as an .rgn and flashed it to the nuvi with the card inserted. Result, backup_41.bin on card and success shown in update log:
Changed update.txt to 'copy,0:/.System/Voice/English_Australian_Karen.vpm,1:/Backup/English_Australian_Karen.vpm' flashed the boot rgn again and my miscreant Voice, the incompatible 1390-bricking TTS3 file, was in the Backup folder on the card. So you maybe can at least backup your files too, even if you can't save the nuvi.Code:nüvi 13xx Series Software Version 6.20, UID: xxxxxxxxxx, HWID: xxxxxxxxxx
------------------------------------------------------------------------------
Parsing "rrgn,41,1:/41_backup.bin"
Success
Parsing "reboot"
Another flash to delete the voice file [del,0:/Voice/English_Australian_Karen.vpm] then the nuvi was accessible to rename my original voices file folder Poice back to to Voice and it boots up and works fine. Flashed the full original v6.20 fw again. You may have to delete the nuvi's entire directory unless you know what may have bricked it, i.e. a map or other file which was recently loaded.
PPS: Full credit to kunix for this, as i'd actually forgotten about it.
I tried again still no go, I will try the method from Neil in post 29, its not looking good for recovery...
thanks