Likes: 
Reply With QuotePerfect! Its now working with CURE and mounting the drive. Any thoughts on which file might be the problem one? Or do you suggest wiping it and starting over?
Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 31 to 40 of 43
Thread: Nuvi 265WT bricked
-
4th June 2014, 03:12 PM #31Navigation software Moderator
- Join Date
- Sep 2011
- Location
- Belarus
- Posts
- 908
- Rep Power
- 439
I promise that flashing GarminCure3-ed firmware without boot.bin (fw_all.bin only) won't make your device feel worse.
Please, try it.
-
4th June 2014, 04:06 PM #32Member
- Join Date
- May 2014
- Location
- US
- Age
- 60
- Posts
- 19
- Rep Power
- 0
-
4th June 2014, 04:15 PM #33Navigation software Moderator
- Join Date
- Sep 2011
- Location
- Belarus
- Posts
- 908
- Rep Power
- 439
Well, this was unexpected
I thought that your flash chip is broken and it can't flash other firmwares except the one that was flashed before it broke (some flash blocks are "frozen" with some bytes forever; writing differing bytes causes an error). I've seen this before. And your situation looks very similar. So I was going to confirm that.
But now it looks like something different. boot.bin can't flash firmwares, but bootloader can do it. Wow.
Now you can try following the GarminCure3 tutorial and format the drive with RMPREPUSB. But make a backup first.
-
4th June 2014, 08:07 PM #34Member
- Join Date
- May 2014
- Location
- US
- Age
- 60
- Posts
- 19
- Rep Power
- 0
That's roughly what I was thinking you were going to say. That it couldn't fit the firmware into the space it had.
Not sure why this was different, but it was. I just finished backing up, reformatting and then reinstalling everything with the Garmin Express tool. So I'm live again thanks to all the help from here!
-
4th June 2014, 09:01 PM #35Navigation software Moderator
- Join Date
- Sep 2011
- Location
- Belarus
- Posts
- 908
- Rep Power
- 439
So does it boot normally now? Don't celebrate too early.
-
4th June 2014, 09:03 PM #36Member
- Join Date
- May 2014
- Location
- US
- Age
- 60
- Posts
- 19
- Rep Power
- 0
Yes. Just like new!
-
4th June 2014, 09:09 PM #37Navigation software Moderator
- Join Date
- Sep 2011
- Location
- Belarus
- Posts
- 908
- Rep Power
- 439
Well, congratulations then
Your case was remarkable for me. I've learned something new and I will use this info for curing in the future.Last edited by kunix; 4th June 2014 at 09:12 PM.
-
4th June 2014, 09:57 PM #38Garmin/GPS Systems GMod.
- Join Date
- Aug 2011
- Location
- Oz.
- Posts
- 6,115
- Rep Power
- 1616
A most pleasing albeit unexpected result. Well done kunix for the insight, and pgardella for following his advices so trustingly and precisely. Another trick worth trying before 'end-game'....
In summary kunix, is this understanding correct?: His unit couldn't flash fw_all.bin using the boot.bin in full firmware, but following successfully flashing boot.bin solely a copy of bootloader was properly retained, which in turn was found to flash fw_all.bin alone.
Thread marked as Solved. WOW indeed.'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
[Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].
-
5th June 2014, 12:45 AM #39Important User
- Join Date
- Nov 2007
- Location
- light side
- Posts
- 15,420
- Rep Power
- 5073
@kunix
Wondering how many nuvis have you helped to unbrick with your advices and your cure.
We are pretty proud to have you here posting,
as usual, many thanks.
You have to navigate to get to the good.
Galaxy S5 Kitkat 4.4.2 / Nuvi1200->1250 / Nuvi3790T->34xx / Nuvi 2200 / Nuvi 66 / Oregon 600
-
5th June 2014, 06:24 AM #40Navigation software Moderator
- Join Date
- Sep 2011
- Location
- Belarus
- Posts
- 908
- Rep Power
- 439
I think bootloader was correct all the time and the issue was caused by the difference in flash writing algorithms in boot.bin (ramloader) and bootloader. And somewhat degraded flash chip, of course.
Originally Posted by Neil
So, boot.bin's flash writing algo was failing somewhere.
But bootloader's algo did the job.
Bookmarks