Oregon 650 flashed with Oregon 750 firmware is BRICKED

**andna** · 9th June 2022, 06:40 AM

Dear Butters, yes, I want to try. Please help me. Can you additionally see the firmware from post # 318? This is a modification firmware that was made for the Oregon 750 firmware after replacing the nvram and dumping the dump merged from 650 (there was no dump from 750). And then they successfully flashed it with the original firmware for 750. I bricked my 650 with this firmware. Maybe you can find some answers in it? Thank you.

**Butters** · 9th June 2022, 07:43 AM

I now also need the original firmware V5.20 for O750 from which that RGN file linked in Post #318 was made. Please post a link to that and additionally answer the following:

My initial examination of "165001000520.rgn" indicates that it's got the same boot.bin as latest V6.00 for O750 and despite it's file naming "1650..." it's actually got internal HWID of 2512... so what do you mean by saying it's "a modification firmware"? If it's only been named differently that's not a real 'modification'.
Also, you're referring to the ramloader (boot.bin) as "nvram" is that correct? Additionally, are you suggesting that it's a hybrid firmware, i.e. a blend of O6x0 & O750? Because on cursory examination it seems not to be that which is particularly why i need the original fw file.
What did you dump from O650?
Finally, you mentioned at some point that it's a 'cure' fw, correct? If so how was it made, by use of a Hex Editor or with kunix's GarginCure3.exe?

Best we clear all this up before attempting anything further.

**andna** · 9th June 2022, 08:46 AM

Dear Butters, I can't answer some of the questions as I didn't do it. Found information not one of the forums. I know that it was a hardware repair of Oregon 750. We changed nand flash and flashed full dump from 650 using programmer. Then they flashed the firmware from post 318 using updater.exe. Link with firmware Oregon 750:

Spoiler: download

**Butters** · 9th June 2022, 12:09 PM

So "Патченая" means "Patched" in Russian correct? You described it as "recovery firmware" which i took to mean cure firmware. So how was this firmware 'patched' please, was Universal Firmware Patcher used, or JNX Patcher, or both .... or what?

**andna** · 9th June 2022, 12:40 PM

On this file hosting service for each firmware are the original and patched (firmware that allows you to view maps in jnx format). I didn't use them. To create a cure firmware, I used the firmware from post 318. You asked about the original firmware 5.20 for the Oregon 750, so I dropped the link.

**Butters** · 9th June 2022, 01:09 PM

Now i understand fully. Someone else likely used the original (not the JNX patched) firmware for O750 to make the cure (recovery) RGN named 165101000520.rgn which you downloaded and it's badly bricked the O650.

It'll be maybe a day before i have time to make the modified ramloader and flash kit. Standby and check back in about 12-24 hours, i'll add it here as an edit when done.

EDIT: Look behind the spoiler for the download link and instruction for use. Read the warning there and only proceed on that basis:

Spoiler:

Good luck.

**andna** · 10th June 2022, 07:16 AM

Butters, After flashing, updater.exe wrote "The update was successful". Garmin logo and Loader on the screen. It's been about 30 minutes now. Is that how it should be? Is it a long process?

I changed the name of the folder on the sd card from "2512" to "1651" and flashed it again. After the firmware on the SD card, a 16.bin file appeared.
Text from updater log:

Oregon 600 Software Version 5.60, UID: 4294967295, HWID: 4294967295
-------------------------------------------------- ----------------------------
Parsing "del,0:/.System/gupdate.gcd"
error
Parsing "rrgn,16,1:/16.bin"
success
Parsing "rrgn,154,1:/154.bin"
error
Parsing "ergn,14"
success
Parsing "xrgn,14,1:/Garmin/14.bin"
success
Parsing "reboot"
success

After a reboot, it is again defined as O750.

**Butters** · 10th June 2022, 08:23 AM

That's too long of course and likely it was stuck on something again trying to reboot ... and now i see you removed the card and re-tried with 1651 folder name and surprisingly it's dumped the logo (16.bin), reportedly erased region 14 and re-flashed it with the O650's 14.bin (fw_all).

Not deleting gupdate.gcd isn't unexpected of course but it hasn't dumped region 154, when we previously were successful in dumping 154 when using 2512 folder! I suspect the modded boot.bin flashed as RGN to overwrite region 12 successfully and perhaps it's also re-mapped the region layout of O650, changed HWID to 1651, although maybe only partially, and that's why it was able to read the 1651 folder subsequently.

So some progress, seems it's now at least partly reconverted to O650 despite still identifying as O750.

Maybe the non-vol region for O650 is 41 and 154 doesn't exist in O650's region layout. Try to dump it using the usual SD card method with "rrgn,41,1/41.bin" and use O650's V5.60 boot.bin as Ldr.bin in 1651 folder. Also please report how it's now performing after you force it off and back on.

Please also upload the 16.bin so i can check it.

(I'll request of staff that this entire exchange of ours be moved to it's own thread because of the unusual problems with this device.)

Done. Very interesting thread.

**Butters** · 10th June 2022, 11:57 PM

@andna
IMPORTANT! Some devices like O600 need to see an Update.log file in the HWID folder or Update.txt is ignored, O750 doesn't need that but maybe because the device has been partly recovered to O650 it now does. It can even be an empty file made with Notepad, but it just might need to be present.

**andna** · 11th June 2022, 05:57 AM

I used O650's V5.60 boot.bin as Ldr.bin. Nothing happened when the folder was called 1651. After changing to 2512 for 5 hours, the screen was SOFTWARE LOADING... But nothing happened, the UPDATER LOG did not change.
Link to 16.bin:

Spoiler: Link

Thread: Oregon 650 flashed with Oregon 750 firmware is BRICKED

Thread Tools

Display

Advertissements

Bookmarks

Bookmarks

Posting Permissions