[Abkarino]

Originally Posted by haxxxen @Abkarino do you have to change the target id manually? you haven't mentioned it and i still want to know what is the difference with a eEID5 converted?

I never changed any thing my self.
Just put the generated file into a temp folder and ObjectiveSuite did the magic.
btw: for eEID5 i never checked cause it was too late when i tested this.
After successfully conversion i just tested if debug menu and settings work , installed Rogero 3.55 DEX CFW , tested it then i turned my console off to have a sleep

[DEFAULTDNB]

Does this method mean CEX2DEX converting now has a significantly lower brick possibility than ever before?

[haxxxen]

thanks for answering
so this tool is only intentionally for cex/dex -> dex/cex conversions? really nice. maybe i test it on my other rsod cechl. but i am not very tempted at the moment and i still want to know where the difference is with eEID5. without it, you don't have to do a remarry afterwards when using the "usual" method

edit
Abkarino, have you checked the target ids in a dump after using objective suites? just to be sure it makes really all by itself?

[zecoxao]

Originally Posted by Abkarino Sure here it is: 1 - Dump you NAND/NOR flash using a memDump tool or Hardware flasher if you have a higher firmware. 2 - Drag this dump into Request IDPS generator tool to generate the request_idps.txt file. 3 - Set your PC IP Address to: 192.168.0.100 and sub net mask to 255.255.255.0. 4 - Enter a FSM using any dongle/software method you like. 5 - Connect your PS3 to your PC directly using Ethernet cable. 6 - Find the old leaked CEX2DEX conversion tools that contains ObjectiveSuite-SetIDPS. 7 - copy all files from conversion folder into flash drive and put it in the right USB slot in your PS3. 8 - in your PC start copy the generated request_idps.txt into the TEMP folder inside the ObjectiveSuite-SetIDPS folder. 9 - Start ObjectiveSuite.exe then power up your PS3. 10 - Wait for about 1 min and you will see a "PASS" message in ObjectiveSuite. 11 - Now turn off your console. 12 - Flash any 3.55 CFW DEX. 13 - While in FSM remarry your BD Drive using 3.30 DEX PUP + 3.55 Remarry tools from Wiki. 14 - Exit from FSM and now you have a fully functional DEX machine. Sorry i'm @ work now, and i'll try to write a full tutorial about it when i back to home.

Cool. you have done it. wow. Have you atleast got the time to check minimal version on the recovery menu? By all means go there and see for yourself. Also, check qa flag.

Seriously people...

[haxxxen]

me also think this cannot change target to dex automatically, as this objective suites was for id changing on 2 consoles, if you look on the manuals

edit
but i know for sure, you can install a dex firmware on cex without any conversion in fsm and qa flagged it will not brick after leaving fsm...

[diesel701]

It's not my upload, but this is what you need for this process: http://www.mediafire.com/?9ev09tlqr1trd9b

[ryant001]

Originally Posted by haxxxen @Abkarino do you have to change the target id manually? you haven't mentioned it and i still want to know what is the difference with a eEID5 converted?

Originally Posted by haxxxen me also think this cannot change target to dex automatically, as this objective suites was for id changing on 2 consoles, if you look on the manuals edit but i know for sure, you can install a dex firmware on cex without any conversion in fsm and qa flagged it will not brick after leaving fsm...

The target id is automatically set to dex when request_idps.txt is generated so you don't need to set it manually.

1 - Dump you NAND/NOR flash using a memDump tool or Hardware flasher if you have a higher firmware.

Now the million dollars question, do the objective suites still work on ofw>3.55?

[haxxxen]

strange, it wasn't with me. my text files do say the actual target. i have used the cex and dex dumps to verify

edit
it says on my dex dump in request_idps.txt on eEID0 offset "82" on on eEID5 offset "85", so no changings automatically...

i am sure you have to do it manually !!!

[diesel701]

Originally Posted by ryant001 The target id is automatically set to dex when request_idps.txt is generated so you don't need to set it manually. Now the million dollars question, do the objective suites still work on ofw>3.55?

I don't think this is right. We must ask to Rnd to know this.
I've created a request_idps from a dump through the program and the Target_ID seems Retail (0x84), so I think is ObjectSuite to make the conversion... (if what Abkarino said is right)
If not, I think we must change the Target_ID manually.

[ryant001]

Originally Posted by haxxxen strange, it wasn't with me. my text files do say the actual target. i have used the cex and dex dumps to verify

Originally Posted by diesel701 I don't think this is right. We must ask to Rnd to know this. I've created a request_idps from a dump through the program and the Target_ID seems Retail (0x84).

request_idps.txt should contain all the data already calculated and ready for the conversion or at least the one that you could get from sony's servers was like that.
If the target id is still cex then it's most likely that the objective suites changes it to dex during the conversion.