First off I want to say special thanks to aerosoul94, we discovered this few months ago, we did alot of mods, and now this is the time for release!
Ok, so now I'll explain how to edit memory of PS3 games in real time.
Tools needed :
A PS3 with a DEX firmware
ProDG Target Manager and ProDG Debugger (they got leaked just google it)
make_fself.exe
The ELF file of the game you want to mod
/!\ - Your PS3 must be wired, it will not work if you're using WiFi - /!\
Ok first, start ProDG Target Manager and go on "Search For Targets" then press the refresh button to start scanning, if all is ok your PS3 should be detected, just right click on it and move it to "Debugging Station" group then double click on it, it will add your PS3 into your targets list.
Now in your targets list, right click on your PS3 then choose "Connect", once your PS3 is connected you can start ProDG Debugger (if it's asking you to select a target then just select your PS3).
You will see a window called "Memory", that's in this window that you will edit the memory of the game you want.
Ok now you need to make a fself (with make_fself.exe) of the ELF you want to edit memory, just go into cmd then put make_fself x.elf EBOOT.BIN where x is your ELF (it will create the EBOOT), once you have your file just put it in your PS3 in the right game folder.
In ProDG Debugger you should see a process appear in the "Processes" window, right click on it then choose "Attach Process" then "Continue without symbols" now your process is attached and you can view memory, but when you attach it, ProDG pauses the process, you have to continue it, just go in ProDG Target Manager, expand the list of your PS3, go to "Kernel Explorer", highlight the process then press the "Continue" icon (you can also continue it with ProDG Debugger).
Now you're done and you can edit memory of your game, by the way there are other options in ProDG Debugger, you can add breakpoints, show disassembly, etc. Also don't forget to refresh memory or just enable "Auto Update" option.
Yeah of course it can be dangerous,Ive been using real dex and fake dex firmware on both of my consoles and you will notice the difference between speed,heat.This is why i dont recommend messing round with kernal on fake dex
---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------
Originally posted by DEREKTROTTER
very nice releases
but DEX uses way too much system resources and puts strain on the ps3. Much more likely to YLoD/ overheat, just dobt overuse it.
Exactly what i said earlier to everyone.I can see alot of people moaning about ylod on fake dexs its not the same as real dex!! but all the kids got to live and learn.
---------- Post added at 02:41 PM ---------- Previous post was at 02:39 PM ----------
Originally posted by Soldier
How does one obtain a "make_fself.exe?" I have "makeself.exe" but that's it.
Look at Failoverflow tools or geohot tools MFW has it is well!!
The following user thanked ELITE xxmcvapourxx for this useful post:
Exactly what i said earlier to everyone.I can see alot of people moaning about ylod on fake dexs its not the same as real dex!! but all the kids got to live and learn.
I'm using a DEX firmware on a retail console, and I never had those problems, you just need to connect your console with the Target Manager then debug your ELF with the debugger, but if you enable some options and you don't know what you're doing, maybe you can crash your console.
I'm using a DEX firmware on a retail console, and I never had those problems, you just need to connect your console with the Target Manager then debug your ELF with the debugger, but if you enable some options and you don't know what you're doing, maybe you can crash your console.
I believe he means a fake DEX firmware like the one included in the 4.21.1 REX firmware instead of the standard DEX conversion with a flasher.
---------- Post added at 10:15 AM ---------- Previous post was at 10:05 AM ----------
Originally posted by xxmcvapourxx
Yeah of course it can be dangerous,Ive been using real dex and fake dex firmware on both of my consoles and you will notice the difference between speed,heat.This is why i dont recommend messing round with kernal on fake dex
---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------
Exactly what i said earlier to everyone.I can see alot of people moaning about ylod on fake dexs its not the same as real dex!! but all the kids got to live and learn.
---------- Post added at 02:41 PM ---------- Previous post was at 02:39 PM ----------
Look at Failoverflow tools or geohot tools MFW has it is well!!
I only have "makeself.c" in my tools, isn't that linux.
First off I want to say special thanks to aerosoul94, we discovered this few months ago, we did alot of mods, and now this is the time for release!
Ok, so now I'll explain how to edit memory of PS3 games in real time.
Tools needed :
A PS3 with a DEX firmware
ProDG Target Manager and ProDG Debugger (they got leaked just google it)
make_fself.exe
The ELF file of the game you want to mod
/!\ - Your PS3 must be wired, it will not work if you're using WiFi - /!\
Ok first, start ProDG Target Manager and go on "Search For Targets" then press the refresh button to start scanning, if all is ok your PS3 should be detected, just right click on it and move it to "Debugging Station" group then double click on it, it will add your PS3 into your targets list.
Now in your targets list, right click on your PS3 then choose "Connect", once your PS3 is connected you can start ProDG Debugger (if it's asking you to select a target then just select your PS3).
You will see a window called "Memory", that's in this window that you will edit the memory of the game you want.
Ok now you need to make a fself (with make_fself.exe) of the ELF you want to edit memory, just go into cmd then put make_fself x.elf EBOOT.BIN where x is your ELF (it will create the EBOOT), once you have your file just put it in your PS3 in the right game folder.
In ProDG Debugger you should see a process appear in the "Processes" window, right click on it then choose "Attach Process" then "Continue without symbols" now your process is attached and you can view memory, but when you attach it, ProDG pauses the process, you have to continue it, just go in ProDG Target Manager, expand the list of your PS3, go to "Kernel Explorer", highlight the process then press the "Continue" icon (you can also continue it with ProDG Debugger).
Now you're done and you can edit memory of your game, by the way there are other options in ProDG Debugger, you can add breakpoints, show disassembly, etc. Also don't forget to refresh memory or just enable "Auto Update" option.
I'm using a DEX firmware on a retail console, and I never had those problems, you just need to connect your console with the Target Manager then debug your ELF with the debugger, but if you enable some options and you don't know what you're doing, maybe you can crash your console.
Let me explain:
On retail console dex converts it has eid ,on real dex full eid converted,dex retail has not got all the options of what a real dex like debug menu, and bdemu so on!! retail use's so much because it loads more modules your ps3 will begin to get hotter and hotter hense you hear your fans speed up faster, core_os has more in retail then dex,dex has only 4 files lv2,lv0,lv1,emer_init,Now if you take alook at core_os retail you have about 10-12 files now if you convert that into dex your retail is using so much power to the ppc,spu and ram all at one go!! dex has its 4 files which does not use so much power into it now what you done there will soon or later will cause you 5 beeps and boom ylod or red light if you use it to much!! Hope this clear's it up much!!
---------- Post added at 03:53 PM ---------- Previous post was at 03:48 PM ----------
Originally posted by Soldier
I believe he means a fake DEX firmware like the one included in the 4.21.1 REX firmware instead of the standard DEX conversion with a flasher.
---------- Post added at 10:15 AM ---------- Previous post was at 10:05 AM ----------
I only have "makeself.c" in my tools, isn't that linux.[/QUOTE
Yes also see if you can find sdk 3.70 or 4.00 ;-p that might help you!!!
The following user thanked ELITE xxmcvapourxx for this useful post:
First off I want to say special thanks to aerosoul94, we discovered this few months ago, we did alot of mods, and now this is the time for release!
Ok, so now I'll explain how to edit memory of PS3 games in real time.
Tools needed :
A PS3 with a DEX firmware
ProDG Target Manager and ProDG Debugger (they got leaked just google it)
make_fself.exe
The ELF file of the game you want to mod
/!\ - Your PS3 must be wired, it will not work if you're using WiFi - /!\
Ok first, start ProDG Target Manager and go on "Search For Targets" then press the refresh button to start scanning, if all is ok your PS3 should be detected, just right click on it and move it to "Debugging Station" group then double click on it, it will add your PS3 into your targets list.
Now in your targets list, right click on your PS3 then choose "Connect", once your PS3 is connected you can start ProDG Debugger (if it's asking you to select a target then just select your PS3).
You will see a window called "Memory", that's in this window that you will edit the memory of the game you want.
Ok now you need to make a fself (with make_fself.exe) of the ELF you want to edit memory, just go into cmd then put make_fself x.elf EBOOT.BIN where x is your ELF (it will create the EBOOT), once you have your file just put it in your PS3 in the right game folder.
In ProDG Debugger you should see a process appear in the "Processes" window, right click on it then choose "Attach Process" then "Continue without symbols" now your process is attached and you can view memory, but when you attach it, ProDG pauses the process, you have to continue it, just go in ProDG Target Manager, expand the list of your PS3, go to "Kernel Explorer", highlight the process then press the "Continue" icon (you can also continue it with ProDG Debugger).
Now you're done and you can edit memory of your game, by the way there are other options in ProDG Debugger, you can add breakpoints, show disassembly, etc. Also don't forget to refresh memory or just enable "Auto Update" option.
also works with an infectus2 modchip piggyback straight to the ram. live memory debugging. > myself and prokilla used this expliot. with help/clues from theunkn0wn before jailbreak and cfw's not used it on ps3 for a while. went to xbox. same pricipals > memory debugging via neighbourhood :-)