Venix Downgrade GUI v1.2 BETA - Improved Validation

Published on 04-13-2012 08:13 PM

12 Comments

A developer here by at PSX-Scene by the name of OverX, has just informed me that he has released an updated version of Venix Downgrade GUI, 1.2 Beta.

Apparently the whole warning behind the last release was a misunderstanding, as they only stated the tool would validate the patching process, and nothing more. Instead of taking the open criticism lying down, the developers have returned with a better product, which now includes more validation process, such as NAND and NOR headers.

The following has been roughly translated using Google:

After the analysis made unfair by the member in our program "RUT Dark Ronin" the ps3devwiki ("unjust" because the program that had not been created to achieve the purposes for which has been criticized), but still accept their criticism and unfounded decided to do exactly what he asks: validation of all headers of a "NAND" and "NOR" and their sizes.

"RUT Dark Ronin" claimed that my program apply patch without checking these areas, which is actually true, since it is a program whose sole purpose was precisely this: apply patch!

But as professionals we are democratic and we are always researching and developing programs to increasingly meet the needs of our students, we decided to accept the unfair criticism made by him and turn it into constructive, so we improved our program and now in its new version, in addition to patch, it also creates a complete verification of almost all the headers of a NOR / NAND, something that no other program is currently, or had to be done manually.

Updates:

Checking the header and size of files:
IFI
asecure_loader
eEID
CISD
CCSD
trvk_prg0
trvk_prg1
trvk_pkg0
trvk_pkg1
cvtrm
metldr
ROS0
ROS1
CELL_EXT
Checks if the metldr is compatible with downgrade.
Validation editable via xml
Search patch for external NOR and NAND.

How to use:

Make reading your NAND or NOR with E3 or Progskeet.
Open your backup with v1.2 Downgrade Venix
Rewrite.

Failures:
If by chance the program detects a fault, we will use the Flow Rebuild to solve.

Let's download the Flowrebuild here
We will open your NOR defective.
Now select the "Byte reverse and extract a NOR dump file."
Open your NOR and execute the function.
The program will create a new NOR with the extension. REV.
Remove the extension and apply the patch to v1.2 Downgrade Venix

Download Patch

Source: Cursos Games

Share
- Share this post on
- Digg
- Del.icio.us
- Technorati
- Twitter

kite21, BahumatLord, nameless32 and 1 others like this.

Categories:

_{Tags :

downgrade,

downgrade gui,

hacker,

hwapx,

overx,

venix,

venix downgrade,

venix downgrade gui,

venix downgrade gui 1.2,

venix downgrade gui beta}

12 Comments

nameless32 - 04-13-2012, 09:09 PM
- Reply
Boa OverX Detona

BahumatLord - 04-13-2012, 10:02 PM
- Reply
@OverX - Very nice update. Glad you didn't give up

OverX - 04-13-2012, 10:23 PM
- Reply
Originally Posted by BahumatLord

@OverX - Very nice update. Glad you didn't give up

never friend, I will make several other versions, next project we will work with donor, dump is build

RUT Dark Ronin - 04-14-2012, 02:44 AM
- Reply
Man, so much for that approach... RUT Dark Ronin here, there, everywhere... Once again, I wasn't unfair, damn it. Your previous statement was completely clear - "Checks for ANY mistakes inside dump". So please stop pushing things on me like a eight years sore boy - it just make no sence for me, standing to help you out.

BahumatLord - 04-14-2012, 03:01 AM
- Reply
Originally Posted by RUT Dark Ronin

Man, so much for that approach... RUT Dark Ronin here, there, everywhere... Once again, I wasn't unfair, damn it. Your previous statement was completely clear - "Checks for ANY mistakes inside dump". So please stop pushing things on me like a eight years sore boy - it just make no sence for me, standing to help you out.

I think there's a translation issue. don't take it personal

RUT Dark Ronin - 04-14-2012, 03:05 AM
- Reply
And man, what's the point of bytereversing a bad dump, you seriously think it might help recover lost or messed data? Please, don't lead plain users on the wrong road! Bytereversing is critical when you catch the flash contents without reversing selected, and want to patch it properly...
Once again, read the damn wiki, lying there for good sake!
As I see through your idea, things should be following:
1 - check dump size and halt if it fails (HIF).
2 - inspect DEADBEEF 0FACE0FF header, IFI header, check if reversed. If not - automatically bytereverse. HIF.
3 - count the percentage of 00's and FF's dump containing, crosscheckin a range posted over at devwiki -+ 1%, and HIF.
4 - look out for doubles!!! In a few cases, all the headers can be discovered twice in single dump (bad wiring it seems). HIF.
5 - check bootldr, metldr, asecure, cSID eEID and all other stuff. Halt if one of checks fails.
6 - check out bootldr offset accordingly to SKU models. If offset matching downgradeable ones - patch. Otherwise - halt, because of no reason for patching, since console will be RLOD'ed.
Hope this helps you. And stop mention my name in that manner, OK?

ieder-zijn-meis - 04-14-2012, 04:18 AM
- Reply
You got good solid points there RUT Dark Ronin

In the mean time, the BETA does not seem to be doing its job:

wrongly detected:
* bad A0 wire -> Validation Failed00 byte count
* bad A1 wire -> Validation Failed00 byte count
* bad A2 wire -> Validation Failed00 byte count
* bad A3 wire -> Validation Failed00 byte count
* bad A4 wire -> Validation Failed00 byte count
* bad A5 wire -> Validation Failed00 byte count
* bad A6 wire -> Validation Failed00 byte count
* bad A7 wire -> Validation Failed00 byte count
* bad A8 wire -> Validation Failed00 byte count
* bad A9 wire -> Validation Failed00 byte count
* bad A10 wire -> Validation Failed00 byte count
* bad A11 wire -> Validation Failed00 byte count
* bad A12 wire -> Validation Failed00 byte count
* bad A13 wire -> Validation Failed00 byte count
* bad A14 wire -> Validation Failed00 byte count
* bad A15 wire -> Validation Failed00 byte count
* bad A16 wire -> Validation Failed00 byte count
* bad A17 wire -> Validation Failed00 byte count
* bad A18 wire -> Validation Failedff byte count
* bad A19 wire -> Validation Failed00 byte count
* bad A20 wire -> Validation Failed00 byte count
* bad A21 wire -> Validation Failed00 byte count
* bad A22 wire -> Validation Failedff byte count
* bad bootldr -> Validation Failed00 byte count
* bad bootldr -> Validation Failed00 byte count
* bad cCSD unreferenced area -> Validation Failed00 byte count
* bad cISD unreferenced area -> Validation Failed00 byte count
* bad EID unreferenced area -> Validation Failed00 byte count
* bad header -> Validation Failed00 byte count
* bad header asecure loader -> Validation Failed00 byte count
* bad header cISD -> Validation Failed00 byte count
* bad header cvtrm -> Validation Failed00 byte count
* bad header eEID -> Validation Failed00 byte count
* bad IFI -> Validation Failed00 byte count
* bad header trvk -> Validation Failed00 byte count
* bad metldr -> Validation Failed00 byte count
* bad/missing bootldr -> Validation Failedff byte count
* bad/missing cCSD -> Validation Failed00 byte count
* bad/missing cISD0 -> Validation Failed00 byte count
* bad/missing cISD1 -> Validation Failed00 byte count
* bad/missing cISD2 -> Validation Failed00 byte count
* bad/missing EID0 -> Validation Failed00 byte count
* bad/missing EID1 -> Validation Failed00 byte count
* bad/missing EID2 -> Validation Failed00 byte count
* bad/missing EID3 -> Validation Failed00 byte count
* bad/missing EID4 -> Validation Failed00 byte count
* bad/missing EID5 -> Validation Failed00 byte count
* bad/missing metldr -> Validation Failed00 byte count
* bad/missing PerConsoleNonce -> Validation Failed00 byte count
* bad patterned non 00's -> Validation Failed00 byte count
* bad patterned non FF's -> Validation Failed00 byte count
* bad region -> Validation Failed00 byte count
* bad filelength -> application hangs
* known good reference dumps (184) -> Validation Failed00 byte count

Conclusion : USELESS, 100% valid files will be failing 00/ff check. Improper files will be failing 00/ff check too, and no detection of the root of the cause. Nothing was patched and gives the user a permanent false sense of having bad dumps without leads of what to solve.

Originally Posted by OverX

never friend, I will make several other versions, next project we will work with donor, dump is build

Please don't, as you can see on Flash, only trvk, ros are per firmware. The rest is perconsole, encrypted and bound to specific hardware, peruser or otherwise never exchangeable and unique.

Source: Talkowngrading with Hardware flasher - PS3 Development Wiki

OverX - 04-14-2012, 10:50 AM
- Reply
Originally Posted by RUT Dark Ronin

And man, what's the point of bytereversing a bad dump, you seriously think it might help recover lost or messed data? Please, don't lead plain users on the wrong road! Bytereversing is critical when you catch the flash contents without reversing selected, and want to patch it properly...
Once again, read the damn wiki, lying there for good sake!
As I see through your idea, things should be following:
1 - check dump size and halt if it fails (HIF).
2 - inspect DEADBEEF 0FACE0FF header, IFI header, check if reversed. If not - automatically bytereverse. HIF.
3 - count the percentage of 00's and FF's dump containing, crosscheckin a range posted over at devwiki -+ 1%, and HIF.
4 - look out for doubles!!! In a few cases, all the headers can be discovered twice in single dump (bad wiring it seems). HIF.
5 - check bootldr, metldr, asecure, cSID eEID and all other stuff. Halt if one of checks fails.
6 - check out bootldr offset accordingly to SKU models. If offset matching downgradeable ones - patch. Otherwise - halt, because of no reason for patching, since console will be RLOD'ed.
Hope this helps you. And stop mention my name in that manner, OK?

Does not retrieve any data, only checks, bytereversing recommend to use flowrebuild.
All of these checks are being made and only look at the xml, first version only checked the header IFI
Nothing else! so it was unfair!

OverX - 04-14-2012, 10:57 AM
- Reply
Originally Posted by ieder-zijn-meis

...

@ieder-zijn-meis You must be some clown wanting to appear, put this analysis because the previous version? to confuse people?
if you can not program and can not help, not harm!

I put all validation required that page in my program Validating flash dumps - PS3 Development Wiki

recommended process:

Dump > check with venix > flowrebuilder > flash!

RUT Dark Ronin - 04-14-2012, 12:19 PM
- Reply
Ahhh, screw this! I was trying to be polite and show some tolerance, but this is getting heavy! Author, quit pissing me off! Fair-Unfair - what a f****ng childish moves you're making here? You're trying to make something and make it better - I'll give you that, but with all above tactics "Bad unfair Dark Ronin, blah-blah-blah" you'll get no respect from more skilled dev's, knowing that your programm is pretty plain. Stop act like a child, I'm warning you for your own sake. Be a man, in the end!

OverX - 04-14-2012, 12:58 PM
- Reply
Originally Posted by RUT Dark Ronin

Ahhh, screw this! I was trying to be polite and show some tolerance, but this is getting heavy! Author, quit pissing me off! Fair-Unfair - what a f****ng childish moves you're making here? You're trying to make something and make it better - I'll give you that, but with all above tactics "Bad unfair Dark Ronin, blah-blah-blah" you'll get no respect from more skilled dev's, knowing that your programm is pretty plain. Stop act like a child, I'm warning you for your own sake. Be a man, in the end!

simple yes, but not useless! done in a day, if your help and sully the name of the people, I dispense!

ieder-zijn-meis - 04-14-2012, 02:08 PM
- Reply
Originally Posted by OverX

@ieder-zijn-meis You must be some clown wanting to appear, put this analysis because the previous version? to confuse people?
if you can not program and can not help, not harm!

I put all validation required that page in my program Validating flash dumps - PS3 Development Wiki

If you take endusers serious: Please solve previous errors in current BETA ! Clearly the detection routine is failing as the long test with 237 samples proved in all 100% of the cases.

In short: get that head out of your arse, it is getting smelly. People are trying to help you with feedback on your "tool" so you can repair and prevent the damages.

With a program that fails 100% this should not even had left alpha stadium and spread to the wild to endanger the public.

Originally Posted by OverX

recommended process:

Dump > check with venix > flowrebuilder > flash!

Wrong: recommended proces: fix the flaws as betatesters are reporting back to you.

I hope you:
- take coding serious
- take testers serious
- listen to endusers feedback and tips
- use the fielddata of thousands of flash
- use the meticulous testing and documenting of ps3devwiki as postitive criticism

Until the program doesn't even do 1 iota of what it claims then not a single user besides yourself should even waste time on it.