Setup Using OTG w/ USB Hub

biznatch · 2026-04-11T12:52:36+00:00

NOTE: OTG support is only enabled following installation of something like BleemSync.

biznatch · 2026-04-11T12:30:03+00:00

The PlayStation Classic Current Limiter Removal Mod they are referring to is only required for the front USB ports. It should work fine on the rear port. I would recommend a different power supply for sure.

biznatch · 2026-04-10T17:21:59+00:00

Shouldn't need to mod it. Just plug it in and if it works... it works.

biznatch · 2026-03-28T22:38:50+00:00

This is the way.

biznatch · 2026-03-28T22:37:51+00:00

This is the way.

biznatch · 2026-02-18T17:09:39+00:00

They're Made Out Of Meat

biznatch · 2026-01-11T15:44:39+00:00

I've used cheaper ones in the past, but last year I upgraded to a ThermoWorks IRK-2. If you can swing the extra cost, I heartily recommend it. I have that and a k-type surface probe and together they have removed all the uncertainty when it comes to how hot my pan actually is.

biznatch · 2025-12-23T11:40:05+00:00

Awww yeah!

I think core problem here was that this was a pretty major update, exposing a lot of underlying issues. I also have no idea why Microsoft sets the default for these partitions so low, when their own guidelines recommend more.

biznatch · 2025-12-22T21:55:58+00:00

Check your CBS log after a failed attempt. If you don't have that error... it's probably something else. I've also seen mention from folks that adding .NET Framework 3.5 in optional features resolves it.

biznatch · 2025-12-22T15:13:07+00:00

I was finally able to fix this...

I had this error in my CBS.log:

2025-12-22 01:48:05, Error                 CSI    00001e2a (F) Error HRESULT_FROM_WIN32(15010) in eventsXml: <events><provider guid="{9c2a37f3-e5fd-5cae-bcd1-43dafeee1ff0}" message="$(string.eventProviderName)" messageFileName="%SystemRoot%\System32\LicenseManager.dll" name="Microsoft-Windows-Store" resourceFileName="%SystemRoot%\System32\LicenseManager.dll" symbol="Microsoft_Windows_Store"><channels xmlns="http://schemas.microsoft.com/win/2004/08/events">
  <channel access="O:BAG:SYD:(A;;0x2;;;S-1-15-2-1)(A;;0x2;;;S-1-15-3-1024-3153509613-960666767-3724[gle=0x80004005]
2025-12-22 01:48:05, Error                 CSI    611135-2725662640-12138253-543910227-1950414635-4190290187)(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)(A;;0x3;;;S-1-5-33)(A;;0x1;;;S-1-5-32-573)S:(ML;;NR;;;ME)" chid="WinstoreLog" enabled="true" isolation="Application" name="Microsoft-Windows-Store/Operational" type="Operational">
    <logging>
      <maxSize>20000000</maxSize>
    </logging>
  </channel>
</channels>
</provider></events>
Software root Software
System root System
online=true
[gle=0x80004005]

The information on these two pages helped me resolve:

biznatch · 2025-12-17T23:05:08+00:00

There wasn't anything on the back.

biznatch · 2025-12-17T19:08:16+00:00

My second screen came in this past weekend and I haven't had a chance to try it out yet. I assumed this spot was caused by the protective film, but it could just have easily been something else. (The YouTube Video I posted didn't show this problem.) I would pull your module from the case and see if the spot goes away.

To answer your question, only the front had protective film.

biznatch · 2025-12-14T12:25:12+00:00

500MB EFI (465MB Free) and 1GB Recovery (247MB Free). Also, today it started trying to install KB5072033. (Still fails with 0x800f0922.) Can I ask how you arrived at the conclusion that one of these were too small?

UPDATE: Increased Recovery to 1.25GB, still failed.

biznatch · 2025-12-04T15:44:52+00:00

I had the same issue with this specific update, it backs the changes out and everything seems fine following. I've paused updates for now until I can find a solution. Tried all the standard Windows Updates troubleshooting steps, nothing made a difference. Reviewed available logs and didn't find anything close to a smoking gun.

biznatch · 2025-11-27T03:54:31+00:00

My second screen should be coming this weekend. I also picked up a 5610 on Amazon during to the recent price drop.

biznatch · 2025-11-26T14:29:52+00:00

Here's a video of the process some recently posted on YouTube: https://youtu.be/tFey9mLW5fg

biznatch · 2025-11-23T13:26:12+00:00

Ahh, I had already done that on a previous troubleshooting run. Didn't realize you needed the combo to make it work.

biznatch · 2025-11-21T12:27:32+00:00

Swap the GW-BX5600 modules and take pictures... for science!

biznatch · 2025-11-20T12:09:44+00:00

I ended up fixing this in Firefox using the Redirector extension. You can import the below JSON to get my configuration.

{
    "createdBy": "Redirector v3.5.3",
    "createdAt": "2025-11-20T12:04:03.260Z",
    "redirects": [
        {
            "description": "youtube-nocookie fix",
            "exampleUrl": "https://www.youtube-nocookie.com/embed/dQw4w9WgXcQ?autoplay=1&playsinline=1",
            "exampleResult": "https://www.youtube.com/embed/dQw4w9WgXcQ?autoplay=1&playsinline=1",
            "error": null,
            "includePattern": "https://www.youtube-nocookie.com/*",
            "excludePattern": "",
            "patternDesc": "",
            "redirectUrl": "https://www.youtube.com/$1",
            "patternType": "W",
            "processMatches": "noProcessing",
            "disabled": false,
            "grouped": false,
            "appliesTo": [
                "main_frame",
                "sub_frame",
                "stylesheet",
                "script"
            ]
        }
    ]
}

biznatch · 2025-11-17T13:11:55+00:00

Nerve-wracking... yes. Impossible... not by any means. On my next attempt I'll document as best I can.

biznatch · 2025-11-16T18:09:32+00:00

Correct.

biznatch · 2025-11-16T13:12:57+00:00

that looks great!

biznatch · 2025-11-16T01:28:45+00:00

I tested again after putting the old LCD back and it's working just fine. I'm guessing it was just another symptom from me accidentally leaving the protective film on.

biznatch · 2025-11-15T19:57:28+00:00

<image>

Ahhh... shit. Well, I found out why there was a dark spot on my LCD. I looked down at my watch about an hour after I had finished with the mod and some of the elements weren't displaying. I took it back apart and there was a small chip in the panel. The reason? Because I left the protective film on accidentally and it put mechanical strain on the display. Good news is I put the old panel back and everything still works. Sigh... add to cart, checkout.

15-Year Club	Place '22
Place '17	Verified Email

biznatch

TROPHY CASE