I promise that flashing GarminCure3-ed firmware without boot.bin (fw_all.bin only) won't make your device feel worse.
Please, try it.
Printable View
I promise that flashing GarminCure3-ed firmware without boot.bin (fw_all.bin only) won't make your device feel worse.
Please, try it.
Perfect! 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?
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.
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!
So does it boot normally now? Don't celebrate too early.
Yes. Just like new!
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.
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.
@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. :)
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.Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
So, boot.bin's flash writing algo was failing somewhere.
But bootloader's algo did the job.