Pioneer XD08 UMB-S Not Working

[CoffeeDrinker]

Hi, so my current UHD drive is a Pioneer XD08 UMB-S. I thought this drive would work, as I've seen people talk about using this drive on the forums before. I tried using it out of the box (it was new, unopened, but purchased through a vendor on ebay) with adding no updates. The problem is, what I thought was an older, pre-2022 drive, turned out to be a December 2022 one.
When I try to read the disc, I get
ILLEGAL REQUEST:CANNOT WRITE MEDIUM - INCOMPATIBLE FORMAT' occurred while issuing SCSI command
repeatedly.

Here's the specs

Manufacturer: PIONEER
Product: BD-RW BDR-XD08U
Revision: 1.02
Serial number:
Firmware date: 2022-12-27
Bus encryption flags: 1B
Highest AACS version: 68

LibreDrive Information
Status: Possible, not yet enabled
Drive platform: Pioneer RS9331
Firmware version: ID05

I am currently using Max OS Sonoma.

Is this problem fixable? Or am I stuck with a drive that won't work for ripping UHD for now? Ripping regular blu-ray discs works just fine. Same with playing DVDs and CDs on playback.
EDIT: I've been viewing forums and it looks like supporting later firmware is in the works, but everyone is kinda in the dark about how long it's going to be before there's a possible update? What would that look like under the scenario when it does become supported through LibreDrive? Is that as simple as--updating MakeMKV, or will it require more than that on my end? (is that still an open question too?)
Thank you for your patience, I am fairly new to this and am not much of a tech person.

[bmcampjr]

I have the same drive and have the same problems. I have found another;

When I pull the result from MakeMVK and HandBrake into Vegas 21.0 I found that all the Channels of a 7.1 disk were exacting the same. This means that channel 1 is being copied to all the other channels instead of being independently copied. This needs to be looked into.

[MrPenguin]

Manufacturer: PIONEER
Product: BD-RW BDR-XD08U
Revision: 1.02
Serial number:
Firmware date: 2022-12-27

The Pioneer firmware needs to pre-date December 2022 for the drive to be LibreDrive-compatible. In effect, that means firmware revision 1.01 whereas your drive has revision 1.02.

On the bright side, you only need LibreDrive if you plan to rip UHD disks. There are sufficient keys and certificates available online to handle non-UHD disks up to and including MKBv81 without LibreDrive.

[CoffeeDrinker]

Yeah I use it for regular blu-rays all the time. Is there any chance that Mike will release a version of MakeMKV that addresses this firmware update? (I got this out of the box and did not update)

[MartyMcNuts]

Yeah I use it for regular blu-rays all the time. Is there any chance that Mike will release a version of MakeMKV that addresses this firmware update? (I got this out of the box and did not update)

It's not that simple. Pioneer have done something to stop us from using them. This issue has been worked on for the past year and a half with no luck as of yet. It may or may not ever happen.

[CoffeeDrinker]

So in layman's terms, could you explain why this is possibly an unsolvable issue? That almost makes it sound like Mike may have given up on the issue? I certainly hope not.

[Coopervid]

So in layman's terms, could you explain why this is possibly an unsolvable issue? That almost makes it sound like Mike may have given up on the issue? I certainly hope not.

The new firmware is encrypted and not easy to decrypt. Pioneer did a good job.

[hikarutilmitt]

I' actually having a problem with the same drive model, except in my case it refuses to read normal BDs, not just UHD. I'm not too concerned about not reading UHDs but I'd really like to be able to use this for BDs because I want to replace an aging drive that's starting to show signs of wear.

Arch Linux
Using the GUI version of MakeMKV or makemkvcon doesn't really matter, it just gets "stuck" on loading the disc information. I've tried using the normal libaacs package with a KEYS.cfg file and bd_info works fine there. Using the makemkv-libaacs package doesn't help and actually makes bd_info fail, as well.

I can actually take my other drive over to this machine, plug it in, and nothing changes with it, but this new drive it doesn't want to work. The old drive is a normal BD, not UHD drive.

EDIT:
So... I went and just plugged the drive into my NAS, where the old drive is, and it started ripping like nothing was ever wrong. My guess is maybe the power draw was more than the USB3 ports on either of the desktops could provide and it wasn't spinning up fully or there's some small, weird difference in the configuration I use there compared to my test runs on my usual desktop and the one in my office. I have a USB3.2 port on the machine that provides full power and used a C-to-C cable to connect it and was off to the races. I guess this proves the USB-C port on front of my desktop is just another hub connection

The only thing that makes me wonder about that aspect is that the drive would still read and let me browse files normally as a data drive, even if a tad bit slow.

EDIT2:
Got a bug up my rear about figuring out what the problem was. The other thing I remembered was that my NAS uses the LTS kernel (6.6.x) versus what I usually use (latest Zen, in this case 6.11.2) and I tried it on one of the non-working desktops. No dice.

Sooooo I checked the makemkv version and the NAS is running 1.17.7, but the one I am (was) running on my other 2 machines is 1.17.8. I grabbed the cached 1.17.7 package, downgraded, and suddenly the drive is loading discs just fine. So I guess I found a bug. It also dumped the firmware file and the program wanted me to send it to the support address, but I'm going to assume they already have it.


TL;DR
Have to use 1.17.7 for now until whatever problem is causing 1.17.8 to not load discs is resolved. If there are any logs for this I can send I'd be more than happy to send them along.

[CoffeeDrinker]

So in layman's terms, could you explain why this is possibly an unsolvable issue? That almost makes it sound like Mike may have given up on the issue? I certainly hope not.

The new firmware is encrypted and not easy to decrypt. Pioneer did a good job.

That is really unfortunate. I hope he can solve it.