Thread: Garmin 265w boot loop, logo, white screen, 3+ years later

It seems I can write to region 14 but in a crazy way. I first upload boot.bin only rgn from sw 4.6, I see white screen, after this it goes in pre-boot automatically, I keep holding top left corner until it reboots in few seconds and goes back into second pre-boot caused by me pressing the screen, at this time updated.exe uploads fine any sw (4.6, 6.4, 7.2, 76) fw_all.bin only rgn, it doesn't not reboot when finishes writing, takes around 3 minutes to finish. It will now allow to upload boot.bin only rgn. So it seems one or the other depending when it went into pre-boot. I used rrgn,14 and hex editor to verify contents, and it matches exactly to fw.all.bin with padded FFs in the end. This is the ONLY way uploader sends fw_all.bin. It seems 4.60 boot is fine with it.

How and when does boot.bin region 5 gets updated? I am guessing either rgn 5 is bad or corrupt or 3 years ago I flashed wrong hardware boot.bin. Maybe its write protecting reg 14 now.

So maybe dangerous boot.bin rgn5 needs to be fixed?

After playing some more I, FFed fw_all.bin from address 0x100 to the end and uploaded it, now Garmin acts differently, it goes in pre-boot automatically and stuck at SOFTWARE LOADING...

It shows Logo, SYSTEM SOFTWARE MISSING...LOADER LOADING...SOFTWARE LOADING...LOADER...SOFTWARE LOADING... stuck here
Video


How should region 5 layout match boot.bin? I compared it to sw 6.40 boot.bin inside gupdade.gcd found on internal drive and they don't match like rgn 14 = fw_all.bin?

EDIT. I put gupdate.gcd on sd:/garmin/ and now the unit stays at SOFTWARE LOADING... 4 seconds, white screen flash, reboot, then repeats. So it does see gupdate.gcd on SD and causes a reboot.

EDIT2: Tried to xrgn,48,1:/48.bin and ergn, 48 both error. I wonder if we can use updater.exe to write to region 48?