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

[Stingray]

how to unlock region free for DVD?

I saw in the previous screenshots that you managed to do it.

[Coopervid]

Hi Matt,

I appreciate your work. Believe me. But this forum is highly influenced by "burning disc believers".

Burning discs is outdated. You should store on HDD and save your drive for reading. Burning will shorten the lifetime of the laser.

Pioneer was just doing a marketing job over the last years. You can tell by flashing XD05 to XD06 worked. Then as well to XD08. Now think about it. XD08 is most likely a XD05 with most likely some value engineering between it. Making the drives less cost.

I have seen here in the forum that the best burns were with a 206. All newer were just "good enough" following the value engineering.

Then let's address the Pioneer utility that gives you options older drives didn't have. Again marketing. All the burning options turned out to be worse than the standard.

PureRead 3 / 4. Forget about it. If you want to rip audio use EAC ( Exact Audio Copy) and there are even better (older) drives to do that.

Silent audio mode. Who plays audio CDs from a computer? Most likely the fan is noisier than the drive. Audio freaks use standalone players which do a much better job.

Saving on disc. Yes, HDDs have become more expensive but only BdR25 can compete in that price range. BDR50 have an issue at the layer break most of the time. Uncompetitive and only programs like the new fork of TSMUXer can prevent issues at the layer break with "layer guard".

Believe me. I'm a great believer in "better safe than sorry". This forum has a lot of freaks who are computer savvy. Many other users are not. Therefore my warnings. Otherwise: Excellent job!

[mattjackson]

Napisany przez Stingray

how to unlock region free for DVD?

I saw in the previous screenshots that you managed to do it.

Ill have it in a coming version. Yes I did it to mine just need to wire it up in app. Im making sure the basics are proven and seems we have a few happy people now which is great. Coming versions will keep building onto what I have

[misiozol]

Napisany przez Coopervid

Hi Matt,

I appreciate your work. Believe me. But this forum is highly influenced by "burning disc believers".

Burning discs is outdated. You should store on HDD and save your drive for reading. Burning will shorten the lifetime of the laser.

Pioneer was just doing a marketing job over the last years. You can tell by flashing XD05 to XD06 worked. Then as well to XD08. Now think about it. XD08 is most likely a XD05 with most likely some value engineering between it. Making the drives less cost.

I have seen here in the forum that the best burns were with a 206. All newer were just "good enough" following the value engineering.

Then let's address the Pioneer utility that gives you options older drives didn't have. Again marketing. All the burning options turned out to be worse than the standard.

PureRead 3 / 4. Forget about it. If you want to rip audio use EAC ( Exact Audio Copy) and there are even better (older) drives to do that.

Silent audio mode. Who plays audio CDs from a computer? Most likely the fan is noisier than the drive. Audio freaks use standalone players which do a much better job.

Saving on disc. Yes, HDDs have become more expensive but only BdR25 can compete in that price range. BDR50 have an issue at the layer break most of the time. Uncompetitive and only programs like the new fork of TSMUXer can prevent issues at the layer break with "layer guard".

Believe me. I'm a great believer in "better safe than sorry". This forum has a lot of freaks who are computer savvy. Many other users are not. Therefore my warnings. Otherwise: Excellent job!

You concerns have been noted, now please leave them be

[skyrider]

Napisany przez 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

What firmware did you flash onto your BDR-207? From what I can see on the website, the BDR-207 is crossflashable to the BDW-PR1EPDVPP100. But the BDW-PR1EPDVPP100 is crossflashable to the BDR-211M SAT8800. Does that mean it's possible to flash BDR-211 firmware onto a BDR-207?

[Stingray]

Napisany przez skyrider

Does that mean it's possible to flash BDR-211 firmware onto a BDR-207?

I think NO. just 08<->09<->11

[mattjackson]

0.12.0 is coming out later today, no change for pioneer. Should just have better MediaTek support for backing up and flashing. Im feeling Pioneer is quite stable and just looking to get MediaTek equally so.

Im looking at the cross flash "family" logic as I have 1-2 that don't seem to fit so digging into those.

[mattjackson]

So 2 known (correct me if there are more) matching hardware families that seem to be not flashable at this time:

S05XLB to 206/S06
207M to PR1ML


They match on hardware family but the issue seems to be that kernels are encoded differently. So the kernel on the drive expects the incoming kernel to be in format A but its actually in format B so it messes up.


I can already decode and re-encode these formats at will so I am going to try first looking at what format the kernel on the drive wants, then re-encoding the incoming to that format.


This should allow these to then be flashed. Again, as always, at your own risk <blah blah blah>


Ill keep you posted

[mattjackson]

0.12.1 due tomorrow should fix cross flashing pioneer firmware within the same hardware family.

S05XLB to 206/S06 and 207M to PR1ML should then work in Recover mode. I put it there for now until testing proves its solid to be moved to flash mode. Just as a safety gate but its not that crazy whats being done so after some testing it will just be part of flash and happen auto behind the scenes like any other flash.

[Stingray]

It's strange why does your program find 1939 here?
MT1959UWDN =1939
MT1959HWDN = 1959

[mattjackson]

Thats a good question Let me dig in

0.12.2 due today, found a regression in 0.12.1 the second i released it. typical. not harmful just not as useful.

[Stingray]

Napisany przez mattjackson

0.12.2

thank you. but err log the same:

...[ 3.870s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, 70, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.875s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=f47a8ec3e9aff2318d896942282ad4fe37d6391c829 14f54a5da8a37de1300c6 count_known=true status_ok=true
[ 3.875s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=5
[ 3.875s] SCSI request: device=\\.\CdRom2 cdb=[3c, 06, 00, 1f, 80, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 attempt=1 strict=false timeout_ms=30000
[ 3.875s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, 80, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.879s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=5e4c78746fd3d4d452e997c199cf05e64bfbf388823 f989c4c4aa4d19cb8f1e1 count_known=true status_ok=true
[ 3.879s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=3
[ 3.879s] SCSI request: device=\\.\CdRom2 cdb=[3c, 06, 00, 1f, 90, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 attempt=1 strict=false timeout_ms=30000
[ 3.879s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, 90, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.882s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=9e5a57f5f6567951bfc6c8165d41e20b1bc665943a6 9406a744530bfe1701a14 count_known=true status_ok=true
[ 3.882s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=3
[ 3.882s] SCSI request: device=\\.\CdRom2 cdb=[3c, 06, 00, 1f, a0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 attempt=1 strict=false timeout_ms=30000
[ 3.882s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, a0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.886s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=ab102825e15b21c975d0eebcadd0a0b4b1608646c85 354b02c03333e9aca3e3d count_known=true status_ok=true
[ 3.886s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=3
[ 3.886s] Progress { label: "reading drive memory", done: 2076672, total: 2097152 }
[ 3.886s] SCSI request: device=\\.\CdRom2 cdb=[3c, 06, 00, 1f, b0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 attempt=1 strict=false timeout_ms=30000
[ 3.886s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, b0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.889s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=7554b71897ef574e3ff3f5124f2d38a48baa1671d21 7d54bfc9d60785b53ec11 count_known=true status_ok=true
[ 3.889s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=3
[ 3.889s] SCSI request: device=\\.\CdRom2 cdb=[3c, 06, 00, 1f, c0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 attempt=1 strict=false timeout_ms=30000
[ 3.889s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, c0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.893s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=8a153d497e50c8a4f4f96df3175279db1d266b08c9e d7668df9e9fbe996bb970 count_known=true status_ok=true
[ 3.893s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=3
[ 3.893s] SCSI request: device=\\.\CdRom2 cdb=[3c, 06, 00, 1f, d0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 attempt=1 strict=false timeout_ms=30000
[ 3.893s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, d0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.898s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=a1456cb0d372e6ffbb24f889bc42cea052a76e00a03 98c2bf845275d60f23d8d count_known=true status_ok=true
[ 3.898s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=5
[ 3.898s] SCSI request: device=\\.\CdRom2 cdb=[3c, 06, 00, 1f, e0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 attempt=1 strict=false timeout_ms=30000
[ 3.898s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, e0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.904s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=f47a8ec3e9aff2318d896942282ad4fe37d6391c829 14f54a5da8a37de1300c6 count_known=true status_ok=true
[ 3.904s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=5
[ 3.904s] SCSI request: device=\\.\CdRom2 cdb=[3c, 06, 00, 1f, f0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 attempt=1 strict=false timeout_ms=30000
[ 3.904s] SCSI execute: device="\\\\.\\CdRom2" cdb=[3c, 06, 00, 1f, f0, 00, 00, 10, 00, 00] direction=FromDevice requested=4096 timeout_ms=30000
[ 3.909s] SCSI incoming data: reported=Some(4096) buffer_bytes=4096 inspected_bytes=4096 sha256=f47a8ec3e9aff2318d896942282ad4fe37d6391c829 14f54a5da8a37de1300c6 count_known=true status_ok=true
[ 3.909s] SCSI result: status=0x00 transferred=4096 sense=[00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00] elapsed_ms=5
[ 3.909s] Progress { label: "reading drive memory", done: 2097152, total: 2097152 }
[ 3.910s] RESULT: error: backup needs every firmware byte, but read 65536 of 2097152; unreadable ranges [
(
0x0,
0x1f0000,
),
]. `dump` saves what the drive returned

[Oinker]

Is 1.V9 available anywhere? And is it recommended? It it downgradable to e.g. 1.V1 (encryption?)?

[DavyCrockett]

Some LG drives have the mt1959 chip physically inside in them but report as mt1939. Trust the report in makemkv that says 1939 and do not flash!!!

[Stingray]

Napisany przez Oinker

Is 1.V9 available anywhere? And is it recommended? It it downgradable to e.g. 1.V1 (encryption?)?

as far as I remember I found this FW on this forum here Vinpower WH16NS58 1.V8 does not support disc quality check??!!!! Please help!. I do not know about it downgradable or not.