Free, Open Source, Windows/Linux/Mac Pioneer Flashing App

[mattjackson]

Appreciate it, good open source team work right there

[cashkey1]

Drive Information
OS device name: \Device\CdRom5
Current profile: BD-ROM
Manufacturer: PIONEER
Product: BD-RW BDR-UD02
Revision: 1.00
Serial number: LJDL050094WL
Firmware date: 2012-08-23
Bus encryption flags: 1B
Highest AACS version: 68


LibreDrive Information
Status: Enabled
Drive platform: RS8410
Firmware name: PIONEER BDR-US02
Firmware type: Original (unpatched)
Firmware version: 1.00/ID19
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

this was my original ud02 readout before i flashed it..

[cashkey1]

and this is the link of my post in this same forum for help with my drives i had during those days.

Pioneer BDR-TD05 and Pioneer BDR-UD02

[mattjackson]

it gives me a date to look for so it will help

[cashkey1]

Yippee!!!

[cashkey1]

attached below is the link to the ud02 posting in MakeMKV Forum made by redrok84

https://forum.makemkv.com/forum/view...206400#p206400

[Stingray]

Thank you very much I made backups for around 10 pioneers now USB is working.

1 more issue - PR1MD2MCM was not possible to backup.
RESULT: error: INQUIRY identity is incomplete. details for this drive:

[Flowery]

I have to thank you for the tool! I got ahold of a flasher, that would take my BDR-212M on 1.05 to a BDR-212U on 1.05, which wasn't exactly what I wanted.

I've tried out a few releases of freemkv-flash for the past few days. On v0.10.5 I could crossflash/downgrade my drive to a BDR-212M on 1.03 FW! After which I crossflashed it through BDRFlash to an S12J-X on 1.01.


I read in your Pioneer FW documentation, that after downgrading, the kernel isn't 100% stock, because the newer downgrade check bit had to be flipped, to not get rejected by the drive, correct? So if I then crossflash it to another drive, while already being on a pre 12/22 FW, will the firmware be 100% stock?


It's awesome to see an open source flasher as well as an open FW archive.
Keep up the good work!

[mattjackson]

Glad its working for so many!

I can work on making the firmware always OEM, its my preference too I just wanted to make sure the basics worked. The change it just 1 byte so its not drastic and not actually doing any harm, but I think I know how post flash it can be truly 100% OEM.

Curious why people use this tool to downgrade, but not cross flash (you seem to revert to using BDRFlash for that). You should have been able to go from 212M on 1.05 directly to S12J-X on 1.01. If there are issues let me know, but idea is 1 tool 1 flash and less of a dance around versions.


RESULT: error: INQUIRY identity is incomplete. details for this drive:
I will look into this!

Also any backups people make, I would love to review and publish on my website for others to then utilize as a flash destination. Backups contain 0 personal info, they should be 100% OEM flashes that get generated (where possible).

[Flowery]

I got ahold of a flasher that could only take the 212M to a 212U, which I wasn't looking for, like I said.

Out of curiosity i tried the v0.10.5 build, to see, if it could get my drive back to 212M. For the first few flashes I used the "force" option (because I was thinking of BDRFlash's behavior). Afterwards i tried it without and couldn't believe, that it was working. I only used BDRFlash, because I didn't want to test my luck haha.

Also, when a flash failed, I had to re-flash with an official one, because freemkv-flash was telling me, that the tray was ejected or that a disc is inside. Is that because of kernel mode?

I only read about the byte change after the fact. But yeah, 100% OEM is nice to have. If you need any more testing done, I can try to go to 212M on 1.05 to S12J-X in one go.

[Stingray]

I tested crossflashing for my old 207 it works , thank you. And now I want to update X13JBK SAT 9400 1.04 ID15.
I see that a lot of versions of S13|X13 could be used. But please confirm that is possible to crossflash it into S13JX SAT9201 ID72 1.05. Bdrflash can't do it. thank you

[mattjackson]

I hear you, when it comes to flashing stick to what you feel comfortable.

I can look into the drive tray check, I added that to be safe (Ive heard the drive should be empty) but during a failed flash maybe it prevents fixing it. It should be removed if you specify force for sure so Ill make that change there.

Any idea why a flash failed in first place? Thats something Id like to not have, no failures.

And Ill take any and all testing anyone is willing and comfortable to do


I won't confirm anything can or cant be done - I can just say that the cross flashes listed on website look as safe as possible based on the data. I actually look at ~5 different components of each drive and match them up, and only suggest a cross flash if all 5 match. Its saying that firmware x runs on this EXACT hardware and the cross flash also runs on that same EXACT hardware. Lasers, servos, a few things I look at. But could I be wrong? 100%

[Flowery]

I did all the flashing yesterday. I think there was an error about failing at a specific number of bytes. Afterwards, the drive was in kernel mode, and I had to reflash with an official pioneer flasher.

I could try to replicate the procedure of yesterday and send you the exact error.

[mattjackson]

Yea I am trying to be as cautious as possible, so I could be being too strong in some areas and actually causing failures. It shouldn't have left it in kernel mode so I will look at at least cleaning up the drive. I doubt I flashed anything and failed, I bet i opened it, then detected a failure and left it in an odd state. I should be cleaner there.

[mattjackson]

https://github.com/MattJackson/pione...d/src/image.rs

For anyone interested in how I generate the unique hardware fingerprint per flash, this is then what I compare and only if 2 flashes have same fingerprint do I suggest it.

Joys of open source, you get to read the code