Thread: GarminCure3 tool - the new way to create cure firmwares for Garmin devices

Guys, if GarminCure3-ed firmware still doesn't enter the mass storage mode, you should try erasing NV.
I thought that people like catymag, lolypop000 and Neil (and many others) do know this.

We go to this step to erase NVM when all other step's don't work

But in Redrock3 case erase NVM is only option for nuvi to maybe work again.

lolypop000
Are you sure?
On [Only registered and activated users can see links. ] NV backing up (before erasing I suppose) was finally suggested only on the 3rd page (!!!), after so many trials and errors.
And it's not going to work most probably, because fw_all.bin would crash before loading ldr.bin and calling the bootloader.
Guys, you don't learn anything...

In this thread, we still don't know if he flash with cure or not and if he flash original in the end.
User ask if he will have after cure all data on nuvi, so if we tell him tu erase NVM, he will lost all, but we try to repair his nuvi with no data lost.

I think that in page 5 we will know if he loaded cure or not

@kunix
That's method of last resort to erase 41 and we all do know it. In the other thread:

(i) amos1 has no existing NV backup.
(ii)He's not particularly interested in saving his unit [we are]. He's stated that he only wants the data off it. I suggested he attempt 41 backup to see if the unit writes to sd for potential data recovery primarily, erase 41 secondarily in amos1's case.
(iii) If Redrock3 has an existing 41 backup, sure, just erase it now. If he hasn't and is prepared to lose registration and unlock codes then fine, skip the 'trial & error' and do it now.

Surely just better to try getting to the bottom of this problem than go straight to erase 41 though? Or do you know for sure it's hopeless in this case?

It's such a mess, I would have solved both problems quickly and aggressively, using the most powerful methods. I can make and restore NV backups anyway.
But you're doing something too subtle for me to understand. Okay, let it be...

Now I just want to note that you've used a wrong method for running ldr.bin. You should always use [Only registered and activated users can see links. ] when fw_all.bin doesn't boot completely.
Well, I'm sorry for being narrative, but in case of amos1 finding out if ldr.bin was really executed would be really problematic. So let's just execute it directly with updater.exe!

Originally Posted by kunix

I can make and restore NV backups anyway.

How?
If you erase region41 how you can restore it back or write something inside?