|
|
#31 |
|
Member
![]() Join Date: Oct 2010
Posts: 469
Likes: 91
Liked 145 Times in 104 Posts
Mentioned: 94 Post(s)
Tagged: 0 Thread(s)
|
in the generated txt file the target id is at offset 0x000000FA
but as i can see it now, it only generates eid0 (decrypted?), or am i wrong? Last edited by haxxxen; 10-17-2012 at 04:28 AM. |
|
|
|
|
|
#32 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,034
Likes: 1,034
Liked 580 Times in 471 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
no it seems to generate all EID's, atleast after eid0 offsets
eid0 offsets: cexdump: block 2F070-2F8CF req.idps.txt offset: F0-11AF then after that part u'll get eid2 req.idps.txt offset: 11B0 (cexdump offset 2FB90) but not the full eid2 section like in cexdump offset 2FB90-3029F it hurts my eyes but this way all eid's are converted, a real convert?! nice share, must be that missing step only from that dex2cex kit thx |
|
|
|
|
|
#33 |
|
Member
![]() Join Date: Oct 2010
Posts: 469
Likes: 91
Liked 145 Times in 104 Posts
Mentioned: 94 Post(s)
Tagged: 0 Thread(s)
|
hm, you are right. the 2nd target id is also at place...
the offsets i see in my request_idps.txt: eEID0? 0x000000FA eEID5? 0x0000131A but maybe within the blocks there are also target ids? edit what is the difference anyways if eEID5 target id is converted? isn't it about bdrom drive? @Abkarino have you converted eEID5, too? if so, please share your experience about it. does it make the bdrom or other hardware behave different? Last edited by haxxxen; 10-17-2012 at 06:10 AM. |
|
|
|
|
|
#34 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,034
Likes: 1,034
Liked 580 Times in 471 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
checked the full file, it's like this:
decrypted: full eid0 cexdump offset: 2f070-2f8cf // re.idps.txt offset: f0-11af small part from eid2 cexdump full eid2 offset/block: 2fb90-3029f / only offset 2fb90-2fc0f // req.idps.txt offset 11b0-12af full eid4 cexdump offset: 303a0-303cf // req.idps.txt offset 12b0-130e full eid5 cexdump offset 303d0-30dcf // req.idps.txt offset 1310- last offset 2710 Last edited by haz367; 10-17-2012 at 06:31 AM. |
|
|
|
|
|
#35 |
|
Member
![]() |
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. |
|
|
|
|
Likes: (3) |
|
|
#36 | |
![]() ![]() Join Date: Mar 2012
Posts: 8,947
Likes: 6,265
Liked 3,836 Times in 2,492 Posts
Mentioned: 950 Post(s)
Tagged: 0 Thread(s)
|
![]() **does this mean what I think it does????
__________________
|
|
|
|
|
|
|
#39 |
![]() ![]() Join Date: Mar 2012
Posts: 8,947
Likes: 6,265
Liked 3,836 Times in 2,492 Posts
Mentioned: 950 Post(s)
Tagged: 0 Thread(s)
|
@Abkarino
I'm sure someone will see this and upload the relevant files
![]() Quite possibly, TBH im not adverse to converting (I made my files based off http://tny.cz/4d179a08 this method ages ago) I'm just waiting until I have to (I also dont have spare USB HDD's laying about)
__________________
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|