Article: WARNING! Venix Downgrade GUI May Cause PS3 Bricks

[tthousand]

You can view the page at http://psx-scene.com/forums/content....-and-Validator

[ieder-zijn-meis]

I think before you news bad programs, you first should test them (or look at tests that other people did, like with that bad E3 Nor checker) :

Talkowngrading with Hardware flasher - PS3 Development Wiki

Warning
This tool is known and proven to give false positives on bad dumps that lead to permabricks.

Use this method: Validating flash dumps to make sure the dumps are in crisp condition.

You cannot recover from bad flash without proper dumps (e.g. bricking the console beyond repair).
note: there are 12½ million bits to permabrick a console

Some portuguese dude (somehow venix name reminds me of a fake bricker CFW and highly hyped and never released manager long time ago) apparently never found ps3devwiki guides or used flowrebuilder/winskeet autopatcher or hexeditor with autopatch scripts.

Time for some tests, like I did with E3 Nor dump checker.

Quick bulletproof test

does not test:
* bad region - not detected, user not warned -> result = result = brick file
* bad A9 wire - not detected, patch file created -> result = result = brick file
* bad A10 wire - not detected, patch file created -> result = result = brick file
* bad A11 wire - not detected, patch file created -> result = result = brick file
* bad A12 wire - not detected, patch file created -> result = result = brick file
* bad A13 wire - not detected, patch file created -> result = result = brick file
* bad A14 wire - not detected, patch file created -> result = result = brick file
* bad A15 wire - not detected, patch file created -> result = result = brick file
* bad A16 wire - not detected, patch file created -> result = result = brick file
* bad A17 wire - not detected, patch file created -> result = result = brick file
* bad A18 wire - not detected, patch file created -> result = result = brick file
* bad A19 wire - not detected, patch file created -> result = result = brick file
* bad A20 wire - not detected, patch file created -> result = result = brick file
* bad A21 wire - not detected, patch file created -> result = result = brick file
* bad A22 wire - not detected, patch file created -> result = result = brick file
* bad boardID - not detected, patch file created -> result = result = brick file
* bad bootldr - not detected, patch file created -> result = result = brick file
* bad cCSD unreferenced area - not detected, patch file created -> result = result = brick file
* bad cISD unreferenced area - not detected, patch file created -> result = result = brick file
* bad EID unreferenced area - not detected, patch file created -> result = result = brick file
* bad header - not detected, patch file created -> result = result = brick file
* bad header asecure loader - not detected, patch file created -> result = result = brick file
* bad header cISD - not detected, patch file created -> result = result = brick file
* bad header cvtrm - not detected, patch file created -> result = result = brick file
* bad header eEID - not detected, patch file created -> result = result = brick file
* bad header metldr - not detected, patch file created -> result = result = brick file
* bad metldr - not detected, patch file created -> result = result = brick file
* bad/missing bootldr - not detected, patch file created -> result = result = brick file
* bad/missing cCSD - not detected, patch file created -> result = result = brick file
* bad/missing cISD0 - not detected, patch file created -> result = result = brick file
* bad/missing cISD1 - not detected, patch file created -> result = result = brick file
* bad/missing cISD2 - not detected, patch file created -> result = result = brick file
* bad/missing EID0 - not detected, patch file created -> result = result = brick file
* bad/missing EID1 - not detected, patch file created -> result = result = brick file
* bad/missing EID2 - not detected, patch file created -> result = result = brick file
* bad/missing EID3 - not detected, patch file created -> result = result = brick file
* bad/missing EID4 - not detected, patch file created -> result = result = brick file
* bad/missing EID5 - not detected, patch file created -> result = result = brick file
* bad/missing metldr - not detected, patch file created -> result = result = brick file
* bad/missing PerConsoleNonce - not detected, patch file created -> result = result = brick file
* bad patterned non 00's - not detected, patch file created -> result = result = brick file
* bad patterned non FF's - not detected, patch file created -> result = result = brick file
* bad region - not detected, patch file created -> result = result = brick file

partly test (if user flashes that, it will permabrick):
* bad A0 wire - detected, 00 filled file created -> result = result = brick file
* bad A1 wire - detected, 00 filled file created -> result = result = brick file
* bad A2 wire - detected, 00 filled file created -> result = result = brick file
* bad A3 wire - detected, 00 filled file created -> result = result = brick file
* bad A4 wire - detected, 00 filled file created -> result = result = brick file
* bad A5 wire - detected, 00 filled file created -> result = result = brick file
* bad A6 wire - detected, 00 filled file created -> result = result = brick file
* bad A7 wire - detected, 00 filled file created -> result = result = brick file
* bad A8 wire - detected, 00 filled file created -> result = result = brick file
* bad header IFI - detected, patch file created -> result = result = brick file

does test:
* circulair reference - errors out: "The process cannot access the file '\nor-validationtest\venix.bin' because it is being used by another process." -> result = OK

Conclusion : USELESS, brickdumps will still show as 'valid' and corrupt patch files will be generated, not preventing the user from permabricking.

Recommendation: Validate flash dumps first and use Flowrebuilder or Winskeet with autopatcher instead.

[futuretime23]

i think you might want to close this thread and take it away from the front page ASAP.(to tthousand)

[RUT Dark Ronin]

I think that way too. For all of guys messing with flashers - the best solution ever is to watch your dumps closely and study wiki in a first place. No any programm will ever ensure you're not the one next to permabrick, so just use common sense. Patching a valid dump is ain't no big deal either, so - useless.
If you want to get the job done nicely - do it yourself. At least, you'll gain some vital experience. So, please, move this tool away somewhere - it's risky.

[KillerDAN]

Venix is crap... junk Just stuff taken from others and put together to seem a nice shiny thing.

[OverX]

Currently the program only checks the header of NOR, But I'm studying the structure of NOR and NAND to do a full scan. So who wants to help will be grateful.

I'm new in this area and still do not know much, But I know how to program I will strive to do better, I do not remember having published a single manager, and much less CFW if people use my name to play boring, what can I do!

Because instead be trying to sully my name is not helping me!

[tthousand]

Afraid that is just the state of the current scene OverX, flooded with trolling and bashing. It is easy to see why devs stay away from forums, and instead are hosting their own blogs/sites.

Well, I for one am always glad to have a new developer here at PSX-Scene. If you need anything, just send me a Visitor Message, or hit me on twitter (link)

[BahumatLord]

@OverX - don't sweat the small stuff. Bugs are just a part of the game. It's really not a bad idea what you tried to do here and I'm sure you can get it right. Don't let negative people stop you from improving on it.

My messages are open if you need something

[OverX]

@OverX - don't sweat the small stuff. Bugs are just a part of the game. It's really not a bad idea what you tried to do here and I'm sure you can get it right. Don't let negative people stop you from improving on it.

My messages are open if you need something

Thanks for the support friend, I'm writing a script to perform a full check, hope who see my efforts and stop criticizing me for something I never did.

I studied and made a script for this validation, I wonder if the way I'm doing will work well?

[XML] Validation - Pastebin.com

if suggest some other improvements?

thank you

[RUT Dark Ronin]

Whoa, excuse me, am I to bash someone? Where did that conclusion came from?
To actuall dev behind this tool - we're all looking forward to your great work, keep it steady. Seriously though, while this programm in it's early stage of development, IMO you shouldn't post it everywhere, cause it's truly risky one, messing with the data you won't be able to recover no matter what. Just a few dosen of newb's permabricks and flaming afterward - does that ring a bell? Throw this away for testing purposes for guys, dealing with flashers at pro and wait for them to comment - that's how this supposed to work. So, as we all can proclaim, this tool is in early stage of testing & development, but not finished kick-off aparently, and you're the one should mention it in a first place.
We're here not to rant on someone's work to make things around easier. We standing to help out both of sides - dev and end-users. If this tool contains any dangerous bugs or mislinks - we'll report it not to harsh you, but to help everyone understand what they're dealing with. So don't be mad on us, fellows with flashers. Anyway, we're all appreciate your quest to make something usefull, so don't give up. Cheers)