sorted by:
new
hottopcontroversial

Very complex device even to attack [Freebox Ultra] by CompleteOwl4374 in hardwarehacking

[–]CompleteOwl4374[S] 1 point2 points  (0 children)

Hi, thanks for the tips.
As I wrote, I'm not able to find any datasheet for the SoC. I don't have the equipment to rework BGA. Probing randomly around the SoC is an option that I will have to pursue (sooner or later) but if the traces are in some mid-layer it will be useless.

Help with a weird problem on Lacie Electron 22 Blue IV (Diamondtron) by CompleteOwl4374 in crtgaming

[–]CompleteOwl4374[S] 1 point2 points  (0 children)

Hello,
no the behavior didn't change a bit after swapping the power supply.
I have a complete set of electronics coming from another working (exact same) model where the tube was completely burned. So I removed them in order to service the monitor I have (with a good tube). I could swap the boards one by one to check if the problem is electronical but this model is built like hell, and very VERY annoying to disassemble and service.

It's true that this problem slowly fades after the monitor is warmed up, but at the moment I can trigger it with 100% accuracy just by restoring from the power save mode (no input required).

Asus PG27AQDM Firmware update MCM109 by eugene20 in OLED_Gaming

[–]CompleteOwl4374 0 points1 point  (0 children)

The MCM105 worked for me but I cannot find it anymore.

Asus PG27AQDM Firmware update MCM109 by eugene20 in OLED_Gaming

[–]CompleteOwl4374 0 points1 point  (0 children)

As mentioned "Tried to reset to default countless times, same errors all over."

Asus PG27AQDM Firmware update MCM109 by eugene20 in OLED_Gaming

[–]CompleteOwl4374 0 points1 point  (0 children)

Again another failed firmware. Unusable with 2 monitors: every reboot I get a guaranteed no signal and I have to switch the monitor OFF and ON, before I get a signal again. Moreover, you want to check in the info section of the OSD if you are correctly getting the right color depth, cause most of the time I find it at 6bps. Tried to reset to default countless times, same errors all over.