To quote: Hi Guys! Today I would like to introduce you the new step in the Progskeet evolution: the “QT” Flasher... The actual public version is a bit “buggy” and difficult to use, and it works well only on Windows XP, as Windows 7 and other OS have compatibility problems with it (some are just crappy things that you can fix with some tricks, while other makes the Flasher crash).
During the last times, the Flasher developer which constantly works on it to improve the stability and the features, has gave a big push to the Flasher, making the choice of using a powerful and multi-platform framework such as QT!
QT is a framework which can allow the developer to write a program and make it work the same way on the 3 main platforms : Windows, Linux and Mac OS X without worrying about write tons of lines to make it work on the currently running platform: QT will do the dirty work for you.
Because of this, @uf6667, helped by two other good coders named Ago and bmx, started to port the original Flasher to QT... and as always we (DiGiTaLAnGeL) and some others have the privilege to beta-test this new and awesome version of the Flasher.
Let’s start with some hightlights: at the moment, the version we have is the Windows one, which then will be called WinSkeet40000, followed by Linuxkeet (Linux) and iSkeet(MAC OS X). This is the GUI of the QT Flasher:
The interface is full of new things... and for now we can use these features:
The “evil” progskeet.log is gone, and the event log is now embedded in the flasher itself, in realtime!
You can manually read,write and now erase too.
You can use presets and create new ones, matching your NOR/NAND flash -now there are some presets for the PS3 flashes and XBOX360 NAND-.
You can change the write method, between buffered write (the default one) or use the “single word” or “double word” mode (you can use it when something goes wrong or your tasks fails).
Now the flasher is splitted in tabs: “Common”, “NOR”, “NAND” and “Patcher” making it more easier and faster to use.
The byteswap function is still here, working flawlessly on both writing and reading.
You can use the “patcher” tab:useful to apply patch to your dump on the fly.
There is an option to change to refresh-cycle of the flash (for slower/faster flashes).
Progskeet Flasher is being translated! For now there are english,french and german languages -italian and all the others are coming-
The “verify” task is now done at the end of the read->erase->write process.
The patcher is the very sexy thing of the QT version, apart from the rocksolid framework: It works selecting the .bin to patch and with a textfile, containing a syntax like this:
Filename is relative to the patch.txt file, and the offset and length parameters are written in HEX format (without the leading “0x” ).
Finally, from IRC:
[Ago] everyone who wants to translate can download that file and edit
[Ago] just change language="it_IT" to whatever you need
[Ago] and remove the type="unfinished"
[Ago] or use the linguist
[eussNL] Done : Dutch translation - ProgSkeet_nl_NL.ts
[DiGiAnGeL] Done : Italian translation - ProgSkeet_it_IT.ts
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
To quote, roughly translated: Hello, I've been working on this project about two months now since I've gotten to work as public so that everyone can use, this tutorial is for consoles with 256MB NAND flash does not mean it does not work in 16MB in itself is changed almost the same in those with normal flash, but because even I have my fat 16mb 80GB I have not been able to neither prove nor verified.
Nougat (the phrase I owe to some forero around here that I really liked the expression):
With INFECTUS flash0.bin and we get our nand flash1.bin as in the tutorial to repair bad lukin nands do the same process until we get our dump flashfinal.bin 256MB nand we open this with a simple hex editor and look for this part editor:
"00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0"
You will see that just under a very similar line, I find this data in the offset 000C0020 may vary according to the nand and the party starts here
EVEN replace that line with the file if you use the hxd 1patchcos.bin get in the first 0 of the line -> right click and paste, writing before you have to have an open 1patchcos.bin hxd in hex and copy its contents to can paste.. then we find the second file to patch at hxd we dump on our part:
Then we take the option we use reescramble flowrebuilder this dump so we rebuild our flash0.ECC.bin and flash1.ECC.bin and flash the result, when you finish you will notice that the PS3 now has a nice on but black screen, it cojemos our factory jig to put it into service mode and put it in factory, then the typical cojemos lv2diag of yore and the pup you please.
(NOTE: the first pup that metais will stay in the console as the minimum version that you can downgrade then, if you want to lose 3.55 to 3.41 then you will have to put the pup up to 3.41 before 3.55 or 3.55 will remain in that if cost will not rewrite the dump again to downgrade to lower the pup that you put the first time.)
Then you put your factory lv2diag to leave the service and you're
Note: this applies to repair the brick Waninkoko NAND not plates even sem-001 (tested) (and step downgrade )
All channel # irc-hispano darkps3 for supporting me for so long
To donate the INFECTUS austaquio32 to achieve to continue with my project
To Nodial2ne paid for the help locating files in the nand
To robs1 for helping throughout the process with ideas to make this possible
And everyone who was patient and not by private haunts me
er_poty: I do post, post it comes to creating private fights and telling him to send me get to the bottom of the shoes PDNKED
pd: I have 4 years unemployed, who selflessly want to donate something please contact me via private (sorry but I have 2 children and the PS3 does not give me to eat me or them ) either that or give me a job lene!
PS3's compatible with this method (thanks pdnked)
CECH = 256MB
CECHB = 256MB
CECHC = 256MB
CECH = 256MB
CECHG = 256MB