How to use an unsupported (i.e. Indonesian) Voice on US 1490

**Neil** · 4th October 2013, 06:12 AM

Although any firmware modification carries some risk it is unlikely that using RGNVoiceEditor caused the problem [even though there is a warning to that effect in both the other thread and turboccc's wikispaces page]. It is likely that the swapping back and forth from US to ID to US is the reason for it bricking. Different firmwares sometimes write info to other parts of the memory and when you then use another fw there can be a few bytes of info in the wrong place for the new fw. This can cause the unit to brick, and sometimes brick rather badly. This may be the reason that your unit bricked in the first place and it's possibly bricked again now.

Have you tried to force it on by holding the on button down for ~10 seconds while it's on charge?

You say '....., but worked when connected to usb'. Do you mean your PC can see it when connected by usb?

As much information as possible is needed.

**dasilvarsa** · 4th October 2013, 06:22 AM

Does the Nuvi enter pre-boot mode ?

**Neil** · 4th October 2013, 06:54 AM

In post #10 he said 'updater can not recognize my device', but he hasn't said how he tried.

@novier
Try to enter preboot by having updater.exe open on your Desktop with a dot beside 'USB Device' with the rgn US fw loaded. Have a usb lead plugged into a rear port of the PC, hold the top left hand corner of the screen and then plug the mini-usb into the nuvi to see if its recognised that way. If it is flash it.

noviar · 4th October 2013, 07:26 AM

once, device can not turn on using car lighter, I tried many times to turn it on while the car lighter connected to the device, then I connected the device to USB, and it turned it on.

now, after I flash the device with 610.rgn the device seemed working well, there is no indonesian voice issue any more, but couple minutes later the device totally dead.

updater.exe can not recognize my device because my device won't turn on. the device can not enter preboot mode, and I have tried to push the power button too, nothing happen. I am planning to dissamble the device to disconnect the battery then connect it again.

noviar · 4th October 2013, 04:20 PM

thanks to all of you guys, after I reassemble and disconnect the battery, the device works well.

**Neil** · 4th October 2013, 10:46 PM

Nice! I had a 255W that was brought back from the dead like that. I'd swapped firmware too many times [converted US > SG > US then to 465T > 255W US] and it died. My previous experience and all i had read said that it would only be good for parts, but when left for a day without the battery it turned on. I had to cure it, loaded 465T fw again and my son has been using it daily for business for the last year or so.

Always worth the trouble to disassemble a 'dead' unit to try, especially if you're going to tear it down for parts anyway .... cheers.

NOTE: Thread renamed to reflect the actual problem faced and marked as Solved.

**chokie** · 28th October 2014, 07:06 AM

I have the same problem my Garmin 1350 from Malsing how to use Indonesian,Damayanti_TTS and JCV Indonesia??

I uppgrade firmware to 6.20 it's not worked it's say "incompatible audio version" and the JCV it's not worked in my 1350

please help thanks

**Neil** · 28th October 2014, 08:38 AM

Do you mean you've converted your SG/MY 1350 to US FW V6.20, or do you have an original US unit you've upgraded to V6.20? US/EU firmware cannot use ANY Asian JCV file, even if the file's patched, Asian fw can use another Asian region's JCV if patched. See: [Only registered and activated users can see links. ]. Read also Post #29 for compatibility.

If it's an original US device, you can load modded fw to use the ID voice. See this thread, Post #22: [Only registered and activated users can see links. ]. But as said, can't see any Asian JCV with a US fw device. If it's SG/MY device it can use the ID voice and see patched ID jcv files.