[doc81]

N00B-time: Hi DEXter, what does this button do?? hahahaha sorry i could not resist asking that.

Seriously, what does this tool do above other tools? Do you install it over cfw 3.55 to play 3.60+ games, What what whaaaaaaaaaaaatttt!!?????
Do you have to have a non jailbroken 4.11 ofw ps3?? or a slim ps3 or do you have to update to 4.21??

i read the pages but no good info, i am lost in HEX numbers and algorithems, so please explain it in N00B language!!! don't flame me for asking this, because alot of people are wandering this so, i do not ask for my self.

Please make a N00Breadme.txt on tools like this.

Furthermore Good job in getting SEX to DEXters labratory heheheheheh (CEX=> DEX thing hahaha)

Peace out man.


PS: new cfw should be called "ps3 dexters-lab.pup"

[ALDONUM1]

Riiiigggghhhht.

[lintz]

Originally Posted by doc81 N00B-time: Hi DEXter, what does this button do?? hahahaha sorry i could not resist asking that. Seriously, what does this tool do above other tools? Do you install it over cfw 3.55 to play 3.60+ games, What what whaaaaaaaaaaaatttt!!????? Do you have to have a non jailbroken 4.11 ofw ps3?? or a slim ps3 or do you have to update to 4.21?? i read the pages but no good info, i am lost in HEX numbers and algorithems, so please explain it in N00B language!!! don't flame me for asking this, because alot of people are wandering this so, i do not ask for my self. Please make a N00Breadme.txt on tools like this. Furthermore Good job in getting SEX to DEXters labratory heheheheheh (CEX=> DEX thing hahaha) Peace out man. PS: new cfw should be called "ps3 dexters-lab.pup"

Okey I'll try to answer it for you. This tool dumps 'some' of the needed files for the cex -> dex converting that before Linux was needed on the PS3 to do. It's not all the files that's needed but it removes the need of Installing Linux to the PS3.

Not sure if you know what the whole CEX->DEX thing is about so I'll try to explain that to.
CEX= Normal retail console bought in any store close to you.
DEX= Developers console that are sold to game developers, they aren't locked to signed codes and can there by run any code/programs you throw at them.

There is a way to play 3.60+ games on the DEX consoles but it's still in a early stage and it involves using the standard BD-Disk emulation that exists in the DEX console and it have limitation to how many games you can store in it if I don't remember wrong its a max of 4(each game have to be store on a external mass media in a partition each).

In other word Multiman or what every backupmanager you use normaly don't work on a DEX console with fw higher then 3.55, the reason for that is the need of Peak & Poke with don't exist for fw's higher then 3.55 atm.

PS the whole converting process is still long so at least I will wait till it's more simple and a better way then the BD-disk emulator works for games.

[DEFAULTDNB]

Does syscall 36 still exist in higher firmwares? if so: why not utilize this instead of peek poke?

Click here to see full text

I’ve often been asked what Custom Firmware (CFW) should a person install and why. In this article, I’ll do a comparison between the five widespread custom firmware. By the end of this, you should know, which custom firmware is best.

Geohot Custom Firmware – Geohot’s CFW has the ability to load signed homebrew. Since lv2 is not patched, no backup managers work because of this. If you want games to play, you will have to convert them into a PKG using tools.


Unpatched lv2 (No Backup Managers, game must be converted to a PKG)
Loads Signed Homebrew


wutangrza Custom Firmware - wutangrza’s CFW based on flukes1′s instructions to add peek and poke to lv2. Just like geohot’s, it loads signed homebrew and has the extra progress of peek and poke in lv2. It’s still not able to make use of Backup Managers in a stock setup, however, later, the kmeaw patch can be applied to do that.

Only Signed Homebrew
No Backup Managers on Stock CFW (However possible using kmeaw’s patch)
Added Peek and Poke to lv2


Waninkoko Custom Firmware – Waninkoko’s CFW patched lv2, however, it did this without even checking lv1 first. This method was highly unstable and led to a lot of random bricks. The CFW did bring Peek and Poke to lv2 as well as SysCall 36 which allowed Backup Managers to work.

Launch Signed Homebrew
Working Backup Managers
Peek, Poke and SysCall 36
Highly Unstable (Causes Random Bricks)


kmeaw CFW – Just about a day after wutangrza, kmeaw came up with his CFW. kmeaw’s CFW implemented PL3. kmeaw also released a patch for wutangrza’s CFW which brought PL3 to it.

Launch Signed Homebrew
Working Backup Managers
Peek, Poke and SysCall 36
Seems stable.


Rebug CFW – Rebug Custom Firmware is the latest custom firmware out there. It aims to add debug console features to regular retail consoles. While not all debug features work, it has bought some.

Launch Signed Homebrew
Working Managers
Peek, Poke and SysCall 36
Some Debug features
Pre-installed BDEmu
Supports TB Dongle through a PKG Patch


There you have it. A simple comparison between the five different Custom Firmwares. My advice; use either kmeaw CFW or Rebug CFW. Make sure to avoid Waninkoko’s as there’s a high chance it’ll randomly brick you. Also, if you plan on switching CFW's, I suggest you uninstall the current CFW by installing the Original Firmware version you need for the new CFW.

Old info, I know, but is it still relevant?

[greyestest]

Originally Posted by lintz Okey I'll try to answer it for you. This tool dumps 'some' of the needed files for the cex -> dex converting that before Linux was needed on the PS3 to do. It's not all the files that's needed but it removes the need of Installing Linux to the PS3.

Does it? AFAIK Linux is still needed to run metldrpwn to decypher metldr.

[doc81]

@lintz 2 words:
Thank You!!!

Thats all :-).

[mirkie]

Originally Posted by DEFAULTDNB Does syscall 36 still exist in higher firmwares? if so: why not utilize this instead of peek poke? Click here to see full text I’ve often been asked what Custom Firmware (CFW) should a person install and why. In this article, I’ll do a comparison between the five widespread custom firmware. By the end of this, you should know, which custom firmware is best. Geohot Custom Firmware – Geohot’s CFW has the ability to load signed homebrew. Since lv2 is not patched, no backup managers work because of this. If you want games to play, you will have to convert them into a PKG using tools. Unpatched lv2 (No Backup Managers, game must be converted to a PKG) Loads Signed Homebrew wutangrza Custom Firmware - wutangrza’s CFW based on flukes1′s instructions to add peek and poke to lv2. Just like geohot’s, it loads signed homebrew and has the extra progress of peek and poke in lv2. It’s still not able to make use of Backup Managers in a stock setup, however, later, the kmeaw patch can be applied to do that. Only Signed Homebrew No Backup Managers on Stock CFW (However possible using kmeaw’s patch) Added Peek and Poke to lv2 Waninkoko Custom Firmware – Waninkoko’s CFW patched lv2, however, it did this without even checking lv1 first. This method was highly unstable and led to a lot of random bricks. The CFW did bring Peek and Poke to lv2 as well as SysCall 36 which allowed Backup Managers to work. Launch Signed Homebrew Working Backup Managers Peek, Poke and SysCall 36 Highly Unstable (Causes Random Bricks) kmeaw CFW – Just about a day after wutangrza, kmeaw came up with his CFW. kmeaw’s CFW implemented PL3. kmeaw also released a patch for wutangrza’s CFW which brought PL3 to it. Launch Signed Homebrew Working Backup Managers Peek, Poke and SysCall 36 Seems stable. Rebug CFW – Rebug Custom Firmware is the latest custom firmware out there. It aims to add debug console features to regular retail consoles. While not all debug features work, it has bought some. Launch Signed Homebrew Working Managers Peek, Poke and SysCall 36 Some Debug features Pre-installed BDEmu Supports TB Dongle through a PKG Patch There you have it. A simple comparison between the five different Custom Firmwares. My advice; use either kmeaw CFW or Rebug CFW. Make sure to avoid Waninkoko’s as there’s a high chance it’ll randomly brick you. Also, if you plan on switching CFW's, I suggest you uninstall the current CFW by installing the Original Firmware version you need for the new CFW. Old info, I know, but is it still relevant?

For syscalls you need peek and poke.

[DEFAULTDNB]

Originally Posted by mirkie For syscalls you need peek and poke.

I could not for the life of me remember if it was "as well as" or "instead of" peek/poke cheers @mirkie

[mirkie]

Originally Posted by DEFAULTDNB I could not for the life of me remember if it was "as well as" or "instead of" peek/poke cheers @mirkie

Haha i am sorry. My english is not perfect.

[deank]

Originally Posted by lintz Okey I'll try to answer it for you. This tool dumps 'some' of the needed files for the cex -> dex converting that before Linux was needed on the PS3 to do. It's not all the files that's needed but it removes the need of Installing Linux to the PS3. Not sure if you know what the whole CEX->DEX thing is about so I'll try to explain that to. In other word Multiman or what every backupmanager you use normaly don't work on a DEX console with fw higher then 3.55, the reason for that is the need of Peak & Poke with don't exist for fw's higher then 3.55 atm.

It seems you're the one that is unaware of the stuff you talk about. And - NO - you are wrong, this tool does nothing and can't give you the keys/decrypted/re-encrypted EID section. It is just children-at-play-proof-of-nothing-tool-to-make-headlines-and-grab-attention.

Originally Posted by DEFAULTDNB Does syscall 36 still exist in higher firmwares? if so: why not utilize this instead of peek poke?

Yes, syscall36 is just a SYSTEM CALL FUNCTION and is available in each firmware. It is a blank/empty one, so if you rewrite it with something useful you'll get what you coded.

Originally Posted by greyestest Does it? AFAIK Linux is still needed to run metldrpwn to decypher metldr.

Correct!

Originally Posted by mirkie For syscalls you need peek and poke.

Peek/Poke are (replaced) syscalls. You don't need peek&poke to call "system-calls". Educate yourself before stating something as a fact.