can I downgrade (or "sidegrade") my firmware on DVR-A04?

[harry349]

I've seen a number of posts about utilities to downgrade firmware on the A03. I've got an A04, and while I'm not currently having a major problem, I flashed with a hacked 1.33 that allows the 2x burning on all media types. I wanted to simply go back to the official 1.33 release, but even this will not work.

If I could downgrade somehow, I could then apply the official 1.33 release. Any ideas? Thanks.

[harry349]

One additional note.

I know some places state that the firmware upgrades from Pioneer are not downgradable, but when I attempt to go from 1.33 (hacked) to 1.33 official, or when I try to downgrade, I get the following message:

"FW is already latest.
If you want to update the current firmware,
then you need to update this utility software.
Update program is terminated by occuring an error."

This makes me wonder if anyone knows how to "update this utility software" or has found any other way to downgrade.

Thanks again.

[coby]

...are you having some sort of "non-major" problems with your hacked 1.33? I ask because it's tempting to try it!

[Platin]

Harry: That message about having to use an updated version should not get your hopes up. I think what it means is simply to wait for Pioneer to release the next firmware and updated UPGDVD.EXE. There is no simple way of downgrading firmware 1.3x right now, but there could possibly be one in the near future, because there are people trying to hack the UPGDVD.EXE.

Coby: Gradius the firmware patcher says in another forum that Pioneer has messed up with v1.33 and that you should hold on upgrading to v1.33 whether it's official v1.33 or the patched v1.33. I don't know any more details, sorry. I myself use the official v1.33 and it works just as Pioneer says it will.

[harry349]

Hope Gradius is right, a "screwed up" 1.33 would hopefully mean a faster release of a 1.34 and hence my ability to *upgrade* back to an official firmware.

[rufusrex]

Where is the offical 1.33? When I go to the Pioneer webpage and click on their "mandatory upgrade" link it takes me to the 1.32 firmware.

[harry349]

Seems they post these things first on their main page in Japan, and then the updates trickle down to their US and other areas.

Check www.doom9.org, and the news on the main page from 10/13. This links to an English page with the files on their Japan-based web page.

[alexnoe]

Maybe you can try the same trick for A04 which I've used for A03:

Use an older firmware file, rename it to 1.34, and modify refinq.dat to make it appear being a newer one (I hope that the loaders are the same :p ).

[ArieBK]

i tryed it but it's not working any other idea ?

[alexnoe]

Please post the old refinq.dat and your modified one. I want to see if you've changed it appropriately.

[ArieBK]

filename : Refinq.dat

R4100103.134 // 0: Firmware Filename
PIONEER DVD-R104 // 1: Enter Key
PIONEER // 2: Vendor Name
DVD-RW DVR-104 // 3: Product ID
1.34 // 4: Rivision Level
02/10/28 // 5: ROM Release date
N // 6: N: Normal only, A: Kernel+Normal
H8_3062A // 7: CPU type (H8_3062A or H8_3062R)
ATPIO1.34 // 8: OEM Mark
BIN // 9: Firmware File Format (BIN or HEX)
100000 // 10: Firmware File Binary Size
1004 // 11: Drive Model & Generatoion (10xx --> DVD-RW)
0 // 12: Show the caution


i rename the R4100103.133 to R4100103.134


i even try to change the R4100103.134 header to this

******** Copyright(c) 2000 Pioneer Corporation ********
This is microcode file.
ID : PIONEER DVD-RW DVR-104
Revision Level : 1.34
Hardware Version : ATA 0003
Kernel Version : GENERAL
Destination : GENERAL
File Type : Normal
Generated Date : 02/10/28
Kernel Version2 : 0001

[alexnoe]

I didn't change anything in the file.

The date in the file (02/10/28) must be changed to a few days later than the actually installed file (maybe 02/10/30)

[ArieBK]

nop .... :(

no good ... same problem as b4

/// DVD-ROM/DVD-RW Firmware Update Utility Ver1.16E

Start updating the device No.1.
Current Revision>> PIONEER DVD-RW DVR-104 1.33 02/09/30
FW is already latest.
If you want to update the current firmware,
then you need to update this utility software.
Update program is terminated by occuring an error.


any other ideas ?

[alexnoe]

Seems as if they have built in a lock mechanism to prevent the current flash utility being used for downgrading :-(
They are really annoying. I'm out of ideas now :angry:

[ArieBK]

to do that ...
and not with the hardware hack... :(

if any one know ... i'll be more then glad :)

[herbsman]

I've seen a number of posts about utilities to downgrade firmware on the A03. I've got an A04, and while I'm not currently having a major problem, I flashed with a hacked 1.33 that allows the 2x burning on all media types


You do mean burn at X2 on media supporting X2 burn speed surely..?
I forget which firmware I got for my Pioneer 104 now but everything works as it should. If I put X2 blank media in , the drop down box in Nero automatically goes to burn at X2 although if for some strange reason you wanted to burn at X1 then that option is still open to you. But are you under the impression that with firmware action your going to be able to burn at X2 on a X1 blank media type?




Peace out :D

[alexnoe]

The hacked firmware allows 2x writing on media which is not certified for 2x. This works on Ritek G03, but most other 1x media will give coasters / badly readable discs.

[herbsman]

ahh , this is the 1st I've heard of this !!
mind you when you can buy - for example - FWS X2 for £0.89 that work perfectly (tried & tested) then why mess with firmware ?:D
LOL Each to their own I suppose


Off to find out more on this Sanyo releasing a a CD-R with 120mins audio capability... Ciao

[alexnoe]

I guess that these discs are using a mixture of BCD and hex as q-subchannel timestamps (98, 99, A0, A1...), as you now get when overburning a 99min CD to 100+. Definitely incompatible with normal drives and needs special support via firmware.

[herbsman]

I've got loads of 700+ MB movie rips and not currently able to burn them to disc but ... soon come! :D

firmware shouldn't be a problem , here's hoping anyway