SOLVED: Nuvi 1350 T wrecked after 2013.10 upload using Garmin Map update v.3.1.12...known issue..
|
16 years
|
Resolved...
3 hour for first failed upload.
70 min with CS. 50 minutes of "on hold". 10 minutes of actual discussion on phone. 10 minutes of yada yada yada script reader's script reading.
I restarted the process. I returned to my computer later in the day and it now works.
Lost all personal data though.
I'm not really fond of Lifetime Updater software and usually opt for the manual one-time option as needed.
I updated my 1350T (LMT package) many times successfully in the past. This time, it stopped working after flashing with 2013.10 using v.3.1.12 Map Update...
Error: "unable to authenticate". Map list blank.
Called tech support the second they opened in the morning. 20 minutes of hold with extremely aggravating automated message suggestive of how stupid they think users are.
Script reading drone describes per-the-manual step to get to gmapprom.unl "start" then there is this thing called "my computer".. once there you should see your device...
Script reader guy asks me to read out each letter. I tell him its 125 chars long. He said it should only be 25 or so.
He says he'll put me to "software support" since its out of his hand and it'll be a "few minutes". Overpromise..under deliver.
a few Garmin minutes later (20 real minutes later) Richard from software support picks up.
and I
I was then told this is known to occur with v.3.1.12 of Map Update. He emailed me a copy of Map Update 3.0.11 and said that one should go fine. After I got it I realized I happened to have the same one on hand. It's the same one I used in March when I uploaded 2012.40 into my nuvi successfully.
It had to re-download everything, but my device works fine now. After the first failed attempt with 3.1.12, I lost all my personal data.
Thanks.
This is the first I have heard of this issue with Map Update 3.1.12. Thanks for the heads up so other forum members can avoid this problem. Did the Garmin tech say if this just affected certain nuvi models/firmware versions? Or is it a global issue with the 3.1.12 software that affects all models?
Alan - Android Auto, DriveLuxe 51LMT-S, DriveLuxe 50LMTHD, Nuvi 3597LMTHD, Oregon 550T, Nuvi 855, Nuvi 755T, Lowrance Endura Sierra, Bosch Nyon
Someone else had an issue with "not able to authenticate"
It was determined to be their modem was dropping out. After getting a new modem and re-downloading the map, everything was cool. As I recall he was 2 digits short on his code.
Just an FYI:
Nuvi 2460LMT.
Falcon9 wrote: ...I call
...I call tech support. First guy was not able to figure it out. He had me check the file gmapprom.unl
He asked me to read out the contents. When I told him its like 125 characters long, he said it should only be 25 or so...
Every time you update your GPS with new map there is a new 25 characters long unlock code added to your gmapprom.unl. For example if you update your unit 5 times your unlock file will have 125 characters long code. Considering that there are no spaces between codes it looks like it's all one code, but it isn't.
Unlock Codes
...I call tech support. First guy was not able to figure it out. He had me check the file gmapprom.unl
He asked me to read out the contents. When I told him its like 125 characters long, he said it should only be 25 or so...
Every time you update your GPS with new map there is a new 25 characters long unlock code added to your gmapprom.unl. For example if you update your unit 5 times your unlock file will have 125 characters long code. Considering that there are no spaces between codes it looks like it's all one code, but it isn't.
Garmin support should have known better suggesting it should only be 25 characters.
I believe the gmapprom.unl stores the unlock codes for each map uddate for the reason that should you decide to revert back to an old map it would still recognize the map as unlocked. Only having the most recent with the 25 characters, then copying an old map back will give you the message "map locked".
Nuvi 2460LMT 2 Units
NOW FIXED
...I call tech support. First guy was not able to figure it out. He had me check the file gmapprom.unl
He asked me to read out the contents. When I told him its like 125 characters long, he said it should only be 25 or so...
Every time you update your GPS with new map there is a new 25 characters long unlock code added to your gmapprom.unl. For example if you update your unit 5 times your unlock file will have 125 characters long code. Considering that there are no spaces between codes it looks like it's all one code, but it isn't.
After I did it ALL OVER again with 3.0.11, my nuvi works.
In the process of messing with the unl file following the first rep's claim that it should be 25 characters, I lost ALL of my personal data like favorites.
Yes, you're right. It was 125 bytes at first. The key did not transfer for some reason. It's 150 bytes after reflashing it the second time around.
The 3.0.11 has the entry option for "enter key manually" the 3.1.12 does not.
nuvi 1350 LMT and garmin lifetime updater
I have received update alerts in the past from my Garmin Lifetime Updater, but did no receive one for 2013.10 and maps 3.1.12. Am I lucky or has this issue been resolved. Are there users out there that had no problems? Also does any know why the Lifetime updater did not alert me? Is the unl file discussed above only needed for additionally purchased maps, or should it be on my pc for the free updates. I can not find it.
Same problem
I also have the same problem.
ChefDon
No problems here.
No problems here.
Standard suggestion number 1
BACK UP YOUR PERSONAL DATA REGULARLY.
And it isn't only about the updater (I always use the webupdater for fimware and dashboard for maps for my units). What would you do if your unit was stolen or had an electronic fault.
Currently have: SP3, GPSMAP 276c, Nuvi 760T, Nuvi 3790LMT, Zumo 660T
Modem was problem
It was determined to be their modem was dropping out. After getting a new modem and re-downloading the map, everything was cool. As I recall he was 2 digits short on his code.
Just an FYI:
Well, it looked like it was 2 digits short, but it wasn't. It was a "font" thing, as different letters have different widths. It "Looked" shorter than the other codes listed at Garmin, but it had the 25 characters required.
The modem was definitely the problem.
Anyway, see:
http://www.poi-factory.com/node/36600
Metricman DriveSmart 76 Williamsburg, VA
1350 update went smoothly
I decided to do the update and it went perfectly.