[diesel701]

So we need a dump from a real Debug unit and study the differences in the request_idps between Retail and Debug.

I think that there is not a real method from Sony to change a Retail to a Debug or viceversa, becouse the Debug firmware is mounted only on DECH console and Retail one only on CECH.

[Dogertyboy]

Originally Posted by haxxxen this "only" indicates, it could work with 3.56+

so it turns out it is "only" indicates .. but do not actually work?
************* [ - Post Merged - ] *************

Well, for example I saw there the keys to СEX in 2 places may just need to change one byte to 82 and all?

[haxxxen]

and i still would like to have an answer about the full conversion and its difference to our "partially" converted dex. but then again, it makes it a hybrid, doesn't it???

[haz367]

nvm..pls del post

[DebugBrain]

Originally Posted by TheWhiteTyger sorry you had to do things the hard way to find out the worth of this program. If only someone would have contributed more info earlier.

2 days ago:

Originally Posted by DebugBrain Warning! This application does not convert anything, if you go to check the data contained in the generated file "request-idps.txt you will notice that they are all data contained in the CEX dump of your PS3.

Using the program with dump DEX (obtained through cex2dex) you get the request-idps.txt to convert ps3 through objective suite.

[butnut]

Originally Posted by DebugBrain 2 days ago: Using the program with dump DEX (obtained through cex2dex) you get the request-idps.txt to convert ps3 through objective suite.

There were way to many people in this thread claiming way to many different things about what this generator+OJ Suites could do.

Since it was considered possible that OJ Suites may contain the cex-dex conversion algorithms and it seemed that no one had any real facts about what this could truly do, I chose to find out for myself.

[haz367]

nvm..its not my thing, to difficult....

[JonahUK]

@haz367

The info is on the wiki for offsets and size of each EID region:

http://ps3devwiki.com/wiki/Flash#eEID
************* [ - Post Merged - ] *************

Originally Posted by haz367 thx, but i think the offsets/size are for the full EID sections, if u notice for the convert with EID0, it only required a piece of it, cut out that block and convert using keyseed etc.. and put back, now we have eid2/4/5 and guessing...it isn't full EID5 block used? like eid0 need some tips i guess otherwise to much hex...gonna take a look anyway..i'm bored

We only changed 2 bytes of the IDPS and associated values so that's why only a snippet was used.
Looking a full block rather than a snippet could lead you to something else and a better understanding of the values contained I suppose.

[Abcdf]

Originally Posted by diesel701 So we need a dump from a real Debug unit and study the differences in the request_idps between Retail and Debug. I think that there is not a real method from Sony to change a Retail to a Debug or viceversa, becouse the Debug firmware is mounted only on DECH console and Retail one only on CECH.

not worth a converted request_idps? in this zip by Scorpion2k7 http://psx-scene.com/forums/attachme..._idps_info.zip are a converted request_idps.txt

sorry for my pour english

[Abkarino]

I think that we need to study ObjectiveSuite and SIG files more to understand how we could customize it very well.
May be we lead us to do some thing usefull.
Also there is another Objectivesuite leak that contains another 3 SIG files that where released here in the past.
I'll try to study it and customize it may be we can find any thing that help us to fully convert our consoles or maybe we could hack higher fw consoles if we could convert it to DEX without having its eEID root key.