Thread: IMPORTANT! If you want HELP in case of a bricked Garmin device, please follow this

The JEFF.BIN is located in JOURNAL folder, in the SD, and appears after every attempt of recovery.

<SD label GARMIN>\JOURNAL\JEFF.BIN

Has 32,768 byte lenght (or 2^15, if you prefer).

Is an hidden file, dated 01/01/1601 and all the byte are set to 0 (zero).

[Only registered and activated users can see links. ]

Maybe it is what remains of the mechanism of jourmaling after the attempt (and the failure) of the restoration ???

After a bit of searching I've found some references to JEFF.BIN file, always regarding Drive Series devices. There will be another file of same name in the internal memory of the device, also in a hidden folder named JOURNAL but it's likely got some readable bytes. Anyway, I don't think it's got anything to do with the problem this device is having, more likely JEFF.BIN is maybe some java-related performance enhancing file specific to Drive series but there may be other recent devices which also have it. It seems it's likely always created on the SD card by Ldr.bin's initiation and it's size is consistently exactly 32 KB (32,768 bytes) albeit all zeros. The original file on the device is also 32KB and mostly just zeros with minimal readable data referencing other files on the device.

So for your Drive 40 attempting SD flash, Ldr.bin is being initiated but is unable to go too far and txt commands aren't being executed. When there's no files named Last_ID.bin and Update.log created in the card then the flash has failed. It seems that because this device has lost it's UID and HWID and has likely flash damage across multiple regions that it's not a candidate for recovery. Maybe it could be JTAG'ed by Garmin to reprogram the flash chip however they only offer a 'one for one' replacement service at a prohibitive price. Sorry but it might be only a candidate for parts now because it's very likely this is a hardware failure.

Originally Posted by Butters

After a bit of searching I've found some references to JEFF.BIN file, always regarding Drive Series devices. [...]

Thanks for informations. And thanks for your help: is very appreciate

Originally Posted by Butters

So for your Drive 40 attempting SD flash, Ldr.bin is being initiated but is unable to go too far and txt commands aren't being executed. When there's no files named Last_ID.bin and Update.log created in the card then the flash has failed. It seems that because this device has lost it's UID and HWID and has likely flash damage across multiple regions that it's not a candidate for recovery. Maybe it could be JTAG'ed by Garmin to reprogram the flash chip however they only offer a 'one for one' replacement service at a prohibitive price. Sorry but it might be only a candidate for parts now because it's very likely this is a hardware failure.

Is not a tragedy: is only a piece of plastic and of silicium.
But is very interesting try to understand how works this kind of dibolic devices.
Today, Garmin support propose me to repair for a cost equal to the 70% of the cost of a new device (new and better). Note that I wrote the word 'support' with the 's' in lower case...
No matter: for 20$, I bought an used Drive 40, with screen damaged: it may possible that, from 2 broken devices I obtain a working Drive (if I'm lucky)

Question 1: they are utility and documentation about jtag programming of Garmin device?
Question 2: is possible to connect a serial TTL i/f on the PCB to see something that is not a stupid message different from "SYSTEM SOFTWARE MISSING"?

Originally Posted by bartolfax

......
No matter: for 20$, I bought an used Drive 40, with screen damaged: it may possible that, from 2 broken devices I obtain a working Drive (if I'm lucky)

That's a good score. As far as I know there is only one screen type for Drive 40 so a screen swap to the $20 device should be fine. Assuming that it's otherwise undamaged of course. It's surprising how many devices with smashed or cracked screen also are 'bricked'. Ppl seem to either crack them using too much force trying to access preboot or abuse them in anger because they can't get them to boot up.

Question 1: they are utility and documentation about jtag programming of Garmin device?

Not that I'm aware of. Garmin would never distribute that information. There's been attempts by advanced users but nothing was ever published about successful results if there were any.

Question 2: is possible to connect a serial TTL i/f on the PCB to see something that is not a stupid message different from "SYSTEM SOFTWARE MISSING"?

Sorry, that's way above my pay-grade. Maybe someone can do it but ppl do sometimes keep their secrets close.

I need help reprogramming a protected Garmin Software. The instructions were on the forum, but I have no access to it anymroe.

Can someone please help??? PM me pleaseeeeeeeeeeeee!

Hi everyone,

I tried to update APAC firmware to Garmin 935 (ROW), now it stuck at logo can't boot (when click back show "Clear User Data") and updater.exe not recognize

Could you please show me show to unbricked?
Thank you
[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]


[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

1) Etrex 20, WebUpdater says that it is uptodate, ID 3875015106
2) I disabled the UK Openstreetmap and enabled Worldwide AutoRoute DEM. Switched off and now it will not restart.
3) I switch on, it goes through all the normal start up procedures but when it reaches "loading profiles" or "Loading complete press any key to continue" it switches off.
4) Yes eg no problem reloading the last software update.
5) I have downloaded the UK Openstreetmap that I had disabled but no change.
I reloaded the last update and again no change.
6) Yes
7) That is the number in 1)
8) No
9) Yes
10) No

I hope you can help.

Thank you in advance.

Peter

Originally Posted by PeterHallowe

1) Etrex 20, WebUpdater says that it is uptodate, ID ......

That's not your device's HWID, it's the UID (Unit ID). You should edit your post to remove it as it's not something you should disclose publicly.

2) I disabled the UK Openstreetmap and enabled Worldwide AutoRoute DEM. Switched off and now it will not restart.

"Worldwide AutoRoute DEM" is an automotive device basemap. I don't think it's an OEM map for eTrex. As it seems from your answer to "5" that you still have Mass Storage Mode available you might solve your problem by simply removing that map.