top of page

Group

Public·8 members

Download Ccapi 2.60 On Pc


The Ccapi.dll file is 0.01 MB. The download links have been checked and there are no problems. You can download it without a problem. Currently, it has been downloaded 6868 times and it has received 5.0 out of 5 stars from our users.




download ccapi 2.60 on pc



If you have come across one of these errors, you can download the Ccapi.dll file by clicking on the "Download" button on the top-left of this page. We explained to you how to use the file you'll download in the above sections of this writing. You can see the suggestions we gave on how to solve your problem by scrolling up on the page.


Changelog2.80(rev7) Added 4.86 CEX support(rev6) Added 4.85 CEX support(rev5) Added 4.84 DEX support(rev5) Added 4.84 CEX support(rev4) Added 4.83 CEX support(rev3) Added 4.82 DEX support(rev2) Reduced memory useAdded ps3 TOOL support (with DEX/CEX kernel only)Added console finder into consolemanagerAdded vsh menuAdded 4.82 CEX support2.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 supportAdded other platform supportOptimized network bitrate2.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 supportAdded 4.60/4.65 supportAdded Cobra supportAdded SetBootPsid/SetBootIdps/SetPsid2.50Added 4.53/4.55 supportAdded a console list2.00Reduced memory useDLL (C++ / C#) released to build programs for ccapi1.00Original version


Port:6333Communication: HTTPPort:1979 PS3 Communication: TCP/UDPstatic int connect_to_CAPPI(void)struct sockaddr_in sin;int s;sin.sin_family = AF_INET;sin.sin_addr.s_addr = 0x7F000001; //127.0.0.1 (localhost)sin.sin_port = htons(6333);s = socket(AF_INET, SOCK_STREAM, 0);if (s return -1;if (connect(s, (struct sockaddr *)&sin, sizeof(sin)) return -1;return s;void DoNotify(char *szFormat,int id = 0) char _notify_buffer[512];snprintf(_notify_buffer, 512, "/ccapi/notify?id=%i&msg=%s",id,szFormat);send_CCAPI_request(_notify_buffer);void ShutDownPS3() char _notify_buffer[512];snprintf(_notify_buffer, 512, "/ccapi/shutdown?mode=1");send_CCAPI_request(_notify_buffer);void RestartPS3() char _notify_buffer[512];snprintf(_notify_buffer, 512, "/ccapi/shutdown?mode=2");send_CCAPI_request(_notify_buffer);void Buzzer(int snd = 1)char _notify_buffer[512];snprintf(_notify_buffer, 512, "/ccapi/ringbuzzer?type=%i",snd);send_CCAPI_request(_notify_buffer);Source : CCAPI && Webman Http requests for sprx - Jo-Milkhttps//pastebin.com/RqnvPZ0j


At this location is where you will find the ccapi sycall switch case 0x8000000000691840 In reference the the offset above it is for lv2 4.84 dex with ccapi 2.80 rev5. The offset changes on each console boot but it should be relatively easy to find by searching for one of the syscall commands like 0x977. The method used to block TMAPI and CCAPI is by returning 0 in GetProcessList function in the kernel.


In relation to CCAPI VSH plugin since Milk found where "ccapi syscall" was located at we decided to hook into it using HookFunctionStart. So I went and bought a FMT mod menu "Fury" and decided to inject it while having the hook active. That way I was able to log all the parameters for each ccapi syscall command that the Fury menu used.


After a dozen dumps we got an error saying "An error occurred while starting menu: 70000006" which I believe means we got blacklisted because I ended up buying the same menu with a different account which allowed me to inject the menu again. To this day my first account I used to inject the menus is unable to use fury. While researching CCAPI I wanted to know how ccapi injected and started the mod menu. So the process goes as followed 1) ccapi plugin calls CCAPIEnableSysCall 2) downloads the files from FMT servers 3) CCAPIAllocatePage is called with file size4) CCAPIWriteProcessMemory is called to write the downloaded file into the allocated page memory address. Each write memory has the size of 0x6000 until the menu is fully written into memory.5) CCAPICreateProcessThread is called to start the mod menu thread aka payloadOnce I knew how ccapi injected the menus I wanted to see if I could do it using my own syscalls. So I created syscall 207 in kernel to invoke the following functions create_process_thread, get_process_module_info, set_process_memory, get_process_memory, process_page_allocate. After that I was using FMT menus using my own syscalls and that inspired adding these functions into COBRA 8.1. A note about set_process_memory before COBRA 8.1 the method used to write memory was essentially a memcpy (copy_to_process) which meant when writing into protected memory (eg: RX) would result in a crash in the game OS. I went and took a look into old ccapi versions 2.50 then searched for syscall 201 and saw that it used process_write_memory which means the memory address maps lpar then memcpy's causing it to bypass the write protection.


When install CCAPI you get a config file. In 2.60 the file was located in /dev_flash/sys/internal/config.cfg but since 2.70 the path has been changed to /dev_flash2/config.cfg and appears to be encrypted,


Since ccapi 2.80 rev6 and above enstone has completely gotten rid of the custom instruction 0xEF455314. In kernel there have been massive changes, he now deletes the initializing of hooks and function setup including the opd sections of the code which is much harder to reverse engineer. In the CCAPI VSH plugin he did some similar things like applying anti debugging techniques.


Moving forward what can we do reverse engineer the new updates of ccapi example ccapi rev6 and above? I was thinking just like the cobra payload ccapi must have a similar payload located somewhere in the ps3 file system and knowing enstone it will likely be encrypted so if we find we will need to decrypt the payload then having ccapi easier to reverse engineer. To get the payload file we could hook into cellFsOpen in kernel and see which files are being read and hopefully find the payload.


ReplaceSyscallInstruction((uint32_t)sys_ccapi_call); // enable ccapi syscallReplaceSyscallInstruction((uint32_t)sys_ccapi_call); // write process paramsReplaceSyscallInstruction((uint32_t)sys_ccapi_call); // read process paramsReplaceSyscallInstruction((uint32_t)sys_ccapi_call); // create thread params


Ahora en nuestro PC ejecutamos la aplicación CCAPI-setupV2.60.exe para instalarlo, una vez finalizado el proceso de instalación, vamos a vincular nuestra PS3 con el PC para ello haremos lo siguiente; con la PS3 encendida y desde el PC abrimos el programa Control Console CCAPI.exe, pulsamos donde pone FILE/ADD NEW CONSOLE, en esta ventana deberemos escribir el nombre de nuestro sistema PS3 y la dirección IP de la misma y le damos "ok".


Hola tengo un problema, yo instale el CCAPI 2.80.2 y queria descargar una tool para Aw lo que pasa es que cuando trato de conectar el ccapi me pide que instale la versión 2.60 pero el problema es que tengo la 2.80 no se que hacer ayuda!!!!!!!!!!!!


  • About

    Welcome to the group! You can connect with other members, ge...

    Group Page: Groups_SingleGroup
    bottom of page