Thread: Oregon 650 flashed with Oregon 750 firmware is BRICKED

@andna
Losing both the Unit ID and HWID (both showing as '0') are very bad signs, as is the fact it's being alternately reported in Updater GUI as Oregon 750t and Oregon 600.

Comparing usual 6x0 fw with the rgn file you flashed, not only did you leave the HWID of 2512 internally which is for 750 but also safe-named the file for 6x0's HWID of 1651 (i.e. 165101000520.rgn) so Updater.exe then flashed the device without further prompt. As the boot.bin for 2512 is around twice the size of that of 1651 and fw_all.bin is also considerably larger, it's highly unlikely the relevant regions of the 650 are large enough to accommodate the 750's firmware BINs. Additionally it seems you've also flashed the 750's logo to region 16 (hex 10):

[Only registered and activated users can see links. ]

The resultant mayhem in your device's fw regions has rendered it inoperable and likely unrecoverable. Despite your statement that it seems to update successfully, it certainly does seem it's not actually accepting a flash via Updater.exe at all as that program directly flashes regions. I'm even a little surprised that in its present state that it still has preboot available to be honest.

Probably it's too damaged to do so, but does it read from and write to an inserted media card? Try backing up it's NV memory: [Only registered and activated users can see links. ]. You might have to experiment by using HWID folder with either of the Oregons' HWIDs, as well as 0. Also it's hard to know which ramloader to use for Ldr.bin, either Oregon boot.bin could be applicable depending on which was flashed successfully in your previous attempts although.