Post: ControlConsoleAPI 2.80 REV4 (CCAPI)
Options
11-11-2013, 05:34 PM
#1
FM|T Enstone
Bounty hunter
Current version : 2.80 REV4
Hello everyone,
CCAPI is a software that establishes a connection between your ps3 and your computer. You can control your ps3 from your pc. Some CCAPI functions:
Debug non-fself & fself in real time
Real time memory edit on CEX/DEX
Wire(less) connection
Module loading
Modify idps and psid
Edit console Leds
Ring console buzzer
Get ps3 temperature
...
Compatible firmwares:
CFW 4.21, 4.30, 4.40, 4.41, 4.46, 4.50, 4.53, 4.55, 4.60, 4.65, 4.70, 4.75 CEX or DEX + 4.66, 4.76 CEX or DEX
Cobra/Non-Cobra, 4.78 CEX or DEX, 4.80 CEX or DEX, 4.81 CEX or DEX, 4.82 CEX or DEX, 4.83 CEX
VSH module loading:
- create a directory in your /dev_usb000/ called plugins
and put all your sprx plugins into, it should be
/dev_usb000/plugins/prx_name1.sprx
/dev_usb000/plugins/prx_name2.sprx
....
All of the sprx that are present in this folder, will be loaded at ps3 boot.
Important: If some games refuse to work, just don't use plugins (delete plugins folder from /dev_usb000)
How to install CCAPI?
Just download and run the ccapi pkg on your ps3.
It will tell you to reboot, and it's done. You only need to do this once.
How to uninstall CCAPI?
Just run again the pkg.
Console Manager:
Add consoles (name/ip) usable in all ccapi tools
Virus scan:
You must login or register to view this content.
ChangeLog
- 2.80
(rev4) Added 4.83 CEX support
(rev3) Added 4.82 DEX support
(rev2) Reduced memory use
Added ps3 TOOL support (with DEX/CEX kernel only)
Added console finder into consolemanager
Added vsh menu
Added 4.82 CEX support
- 2.70
(rev6) Added 4.81 DEX support
(rev5) Added 4.81 CEX support
(rev4) Added 4.80 DEX support
(rev4) Added 4.80 CEX support
(rev3) Added 4.78 DEX support
(rev2) Added 4.78 CEX support
(rev2) Added 4.76 DEX support
Added other platform support
Optimized network bitrate
- 2.60
(rev7) Added 4.76 CEX support
(rev6) Added 4.75 DEX support
(rev5) Added 4.75 CEX support
(rev4) Added 4.70 DEX support
(rev3) Added 4.70 CEX support
(rev2) Added 4.66 CEX support
Added 4.60/4.65 support
Added Cobra support
Added SetBootPsid/SetBootIdps/SetPsid
- 2.50
Added 4.53/4.55 support
Added a console list
- 2.00
Reduced memory use
DLL (C++ / C#) released to build programs for ccapi
- 1.00
Original version
The following 871 users say thank you to FM|T Enstone for this useful post:
^TPP^, _HURT_, _L0st_my_Gh0st_, -Google-, Nath, -Numb, -SuperMan, !MixerxHD!, ..jigsaw, .MrRedDoT, {H} | Exception, {OM}1337{OM}, Jiggy, /SneakerStreet/, ❇❥⛺Cerberus⛺❤❇, マated, بومبو, Smooth, ＶＡＰ３Ｒ, Dynamite, One, Okami, ⓙω мσ∂z, ▶DaOriginal209◀, Nana, ☓-Dani-☓, Kappa, DIRTY SMASHER, ⚔Spanners⚔, #Dragoss, #Rage, 045Connection, 077407, 0xX0R, 0zersub, 192.168.1.1, 6jarjar6, A_Gen_Fiasco, abankmino, aburezk, AcidicSins, Adel500, AdnanM801, AdxmModz, ady05113, Ahmed.AK, Aitan7, AKONIT92, alboyiscool, Albus, alchybear, AlecKeaneDUB, aleeeex, alenbih, Alex_xbr, AlexNGU, Alexon, AleXta, Alf.Red, ALI ALHILFI, aliast, allant, AllMw2MoDz, alvieth, Amanda, Andr3wM, AndresKid, AndrewKills, angelo27093, animalovich, annern, Ansity., anxify, Aphelion09, Appreciate, arash_ashkan, Armyspy, Arrow_Modz, Asian, Ass Burgers, ateazy12, audi787b, mason, AutoModder, azooz121, Azus, B o n e, b3tl1ng, BadChoicesZ, bAdReQuEsT, BAGZY13B, BaileyisDope, bam509, bandphan, Bane., barelynotlegal and 771 other users.
11-09-2014, 02:12 AM
#786
emski022
Banned
Too be honest, I think something is wrong all together witH 2.60. It's causing all sorts of problems with tools that DO support it. Tools are saying it's not installed when it is e.t.c weird.
Originally posted by hunter926
Searches are taking about 20 times longer with the 2.60 update. took me 300 seconds (5 minutes) to search a small range 0x00010000-0x03320000.
I have a wired connection so there should be no reason it should take so long. Any ideas?
I have a wired connection so there should be no reason it should take so long. Any ideas?
11-10-2014, 12:33 AM
#790
iTCGz
Haxor!
Wouldn't advise any one using 2.60 becasue My hard drive got mess up using 2.60 becasue everytime i tried to connect a tool it froze then after a few time, it got to a point where everytime i turn my ps3 on it gave me a restore page and couldnt cancel it so i had to change hard drives. please fix this or get it stable
11-10-2014, 05:02 PM
#792
FM|T Enstone
Bounty hunter
Originally posted by FarSideX
Any chance of getting normal API updates? What I mean is an API should be backwards comparable. Especially when it is used with an external device. Your could easily export the same function interface as older versions and connect to the newer PS3 code. This is what API's are supposed to do, it would allow it to work with older tools without having to update the older tools.
For example in 2.00 you exported the functions under 2 names each, in 2.50 you dropped some of the names. If you had not done that then past programs that were written for the CCAPI.dll 2.00 would have continued to work with the new 2.60 dll unchanged.
As for using PS3lib for backwards compatibility support, it has its own issues such as performance due to it being an API written in managed code for an existing unmanaged API and does not pass exceptions in places that it should.
As it is right now I am still using 2.00 rather than rewriting my tools every time there is an update to the API, I can not think of any other API that this is necessary as they are true API's and not completely different interfaces each update.
For example in 2.00 you exported the functions under 2 names each, in 2.50 you dropped some of the names. If you had not done that then past programs that were written for the CCAPI.dll 2.00 would have continued to work with the new 2.60 dll unchanged.
As for using PS3lib for backwards compatibility support, it has its own issues such as performance due to it being an API written in managed code for an existing unmanaged API and does not pass exceptions in places that it should.
As it is right now I am still using 2.00 rather than rewriting my tools every time there is an update to the API, I can not think of any other API that this is necessary as they are true API's and not completely different interfaces each update.
You can use older software built for CCAPI directly (in less than 1 minute) as long as you followed IMCSx 's tutorial correctly.
By doing this:
How to convert a 1.00/2.00/2.50 tool -> 2.60 tool
1) Put the PS3Lib.dll v4.4 in the same folder than the software (you can find it in CcApi_package_2.60/PC/PS3Lib/
2) Use the installer to install CCAPI 2.60 on your PC
3) Install the CCAPI 2.60 pkg on your PS3
If you didn't use PS3Lib.dll, then no you can't, PS3Lib.dll was useful as a compabitility layer between software and CCAPI, that way I can modify CCAPI how I want, add functions, etc and all software are still compatible.
I sugget you to read the tutorial on how to make a CCAPI software.
Also saying that using PS3Lib as performance issue is not true, i think you're forgetting that you are using network functions with CCAPI, that take much much much longer than a c# code vs a compiled code.
Originally posted by HaXoR
Cobra compatibility is the only thing that is beneficial with this update. Enstone could at least implement this cross-platform and open source this instead of being a unproductive money-whore. I'm not hating, just pointing out facts.
Now preventing any further implementation of any Unofficial version of PS3Lib... Enstone and iMCSx are obviously hurt that I made one.
Also I did tell Enstone about getting PS3IP through Network using Macaddress OUI Fingerprinting... but he was too lazy to do so, as he said "It already does what it's supposed to", proving he doesn't care too much about the user's convenience.
I added: "GetLVL2/SetLVL2 Memory" back into PS3Lib Unofficial (4.4.8.5) as he removed it from 2.50 I implemented it back in. Then afterwords I implemented what he wouldn't which was PS3 connect via Mac Fingerprint. Still no one has yet to realize this.
Now preventing any further implementation of any Unofficial version of PS3Lib... Enstone and iMCSx are obviously hurt that I made one.
Also I did tell Enstone about getting PS3IP through Network using Macaddress OUI Fingerprinting... but he was too lazy to do so, as he said "It already does what it's supposed to", proving he doesn't care too much about the user's convenience.
I added: "GetLVL2/SetLVL2 Memory" back into PS3Lib Unofficial (4.4.8.5) as he removed it from 2.50 I implemented it back in. Then afterwords I implemented what he wouldn't which was PS3 connect via Mac Fingerprint. Still no one has yet to realize this.
Why would I have to make it open source ? I developped it, and what if I want to continue to work on it alone ?
What rights do you have on this ? none. I think I made a decent job by developping CCAPI, it helped a lot to make RTE more user friendly. I also think that you forgot in what kind of community we are, the RTEing community (not the real PS3 dev scene) that take a source that replace all credits and put their own.
Maybe you support only open source then good for you, but I am not the only devlopper to act like that, on ps3 (deank) and on any other platforms.
You re-added, GetLV2Memory but the only use of YOUR GetLV2Memory is what ? Reading the console id from any console. Do you really think this has an interest ? Apart from helping to steal other people's console id.If developpers need this function then they are free to use ccapi 2.00, but i won't help you to read console id from memory. This adds safety for CCAPI users.
If you have decent ideas, i will add them for sure, but i didn't see many interesting things from you.
Originally posted by hunter926
Searches are taking about 20 times longer with the 2.60 update. took me 300 seconds (5 minutes) to search a small range 0x00010000-0x03320000.
I have a wired connection so there should be no reason it should take so long. Any ideas?
I have a wired connection so there should be no reason it should take so long. Any ideas?
Yes, the main buffer have been reduced but why ?
Simple, people ask for more features, that take more memory.
But on the contrary small buffers will be transfered much faster. This should help to make mod menus but won't help software that make huge memory scans. Anyway, RTEing shouldn' be used to scan memory like this, this is really a bad idea. If you want to scan memory do it on the console directly.
People wants multithreading support for ccapi, more memory, they want multi application support, more memory, they wants multi pc support, more memory. They also want cobra, ok less memory for CCAPI available, they also want webman, ok less memory for CCAPI available, they also want plugins, ok less memory for CCAPI available. At the end CCAPI, must work on so many firmwares (around 20), with almost no memory... I'm not a god, ps3 has not enough memory for all of this... Give me 10MB ram i will do it, but no there is only a couple 100kB for it...
The following 8 users say thank you to FM|T Enstone for this useful post:
11-10-2014, 05:48 PM
#793
tryme
Do a barrel roll!
Originally posted by FM
You can use older software built for CCAPI directly (in less than 1 minute) as long as you followed IMCSx 's tutorial correctly.
By doing this:
How to convert a 1.00/2.00/2.50 tool -> 2.60 tool
1) Put the PS3Lib.dll v4.4 in the same folder than the software (you can find it in CcApi_package_2.60/PC/PS3Lib/
2) Use the installer to install CCAPI 2.60 on your PC
3) Install the CCAPI 2.60 pkg on your PS3
If you didn't use PS3Lib.dll, then no you can't, PS3Lib.dll was useful as a compabitility layer between software and CCAPI, that way I can modify CCAPI how I want, add functions, etc and all software are still compatible.
I sugget you to read the tutorial on how to make a CCAPI software.
Also saying that using PS3Lib as performance issue is not true, i think you're forgetting that you are using network functions with CCAPI, that take much much much longer than a c# code vs a compiled code.
Why would I have to make it open source ? I developped it, and what if I want to continue to work on it alone ?
What rights do you have on this ? none. I think I made a decent job by developping CCAPI, it helped a lot to make RTE more user friendly. I also think that you forgot in what kind of community we are, the RTEing community (not the real PS3 dev scene) that take a source that replace all credits and put their own.
Maybe you support only open source then good for you, but I am not the only devlopper to act like that, on ps3 (deank) and on any other platforms.
You re-added, GetLV2Memory but the only use of YOUR GetLV2Memory is what ? Reading the console id from any console. Do you really think this has an interest ? Apart from helping to steal other people's console id.If developpers need this function then they are free to use ccapi 2.00, but i won't help you to read console id from memory. This adds safety for CCAPI users.
If you have decent ideas, i will add them for sure, but i didn't see many interesting things from you.
Yes, the main buffer have been reduced but why ?
Simple, people ask for more features, that take more memory.
But on the contrary small buffers will be transfered much faster. This should help to make mod menus but won't help software that make huge memory scans. Anyway, RTEing shouldn' be used to scan memory like this, this is really a bad idea. If you want to scan memory do it on the console directly.
People wants multithreading support for ccapi, more memory, they want multi application support, more memory, they wants multi pc support, more memory. They also want cobra, ok less memory for CCAPI available, they also want webman, ok less memory for CCAPI available, they also want plugins, ok less memory for CCAPI available. At the end CCAPI, must work on so many firmwares (around 20), with almost no memory... I'm not a god, ps3 has not enough memory for all of this... Give me 10MB ram i will do it, but no there is only a couple 100kB for it...
By doing this:
How to convert a 1.00/2.00/2.50 tool -> 2.60 tool
1) Put the PS3Lib.dll v4.4 in the same folder than the software (you can find it in CcApi_package_2.60/PC/PS3Lib/
2) Use the installer to install CCAPI 2.60 on your PC
3) Install the CCAPI 2.60 pkg on your PS3
If you didn't use PS3Lib.dll, then no you can't, PS3Lib.dll was useful as a compabitility layer between software and CCAPI, that way I can modify CCAPI how I want, add functions, etc and all software are still compatible.
I sugget you to read the tutorial on how to make a CCAPI software.
Also saying that using PS3Lib as performance issue is not true, i think you're forgetting that you are using network functions with CCAPI, that take much much much longer than a c# code vs a compiled code.
Why would I have to make it open source ? I developped it, and what if I want to continue to work on it alone ?
What rights do you have on this ? none. I think I made a decent job by developping CCAPI, it helped a lot to make RTE more user friendly. I also think that you forgot in what kind of community we are, the RTEing community (not the real PS3 dev scene) that take a source that replace all credits and put their own.
Maybe you support only open source then good for you, but I am not the only devlopper to act like that, on ps3 (deank) and on any other platforms.
You re-added, GetLV2Memory but the only use of YOUR GetLV2Memory is what ? Reading the console id from any console. Do you really think this has an interest ? Apart from helping to steal other people's console id.If developpers need this function then they are free to use ccapi 2.00, but i won't help you to read console id from memory. This adds safety for CCAPI users.
If you have decent ideas, i will add them for sure, but i didn't see many interesting things from you.
Yes, the main buffer have been reduced but why ?
Simple, people ask for more features, that take more memory.
But on the contrary small buffers will be transfered much faster. This should help to make mod menus but won't help software that make huge memory scans. Anyway, RTEing shouldn' be used to scan memory like this, this is really a bad idea. If you want to scan memory do it on the console directly.
People wants multithreading support for ccapi, more memory, they want multi application support, more memory, they wants multi pc support, more memory. They also want cobra, ok less memory for CCAPI available, they also want webman, ok less memory for CCAPI available, they also want plugins, ok less memory for CCAPI available. At the end CCAPI, must work on so many firmwares (around 20), with almost no memory... I'm not a god, ps3 has not enough memory for all of this... Give me 10MB ram i will do it, but no there is only a couple 100kB for it...
i just have one request, can you only explain to me (even if only pm) how to make notify work with ccapi 2.0 or 2.5? vsh exports only make ccapi crash for me using in a prx
and maybe you can consider letting user choose from where to load plugins?
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
