(adsbygoogle = window.adsbygoogle || []).push({}); Hey NGU, could use some of your brainpower right about now :/ To start things off, I have tried everything I could find on YouTube, NGU, other ps3 hacking websites, and to no luck, I can't get past this damn error. I've Rebuilt my data base, Checked file systems, changed my IDPS/CID to multiple different ones, and when I changed it to my original CID, It gives me the OG Error of it being banned or suspended, so this leads me to believe I'm being a dumbass somewhere along the lines. I've *tried Spoofing my LV2 memory IDPS to 0x82 (CEX), I've tried manually changing the CID in webMAN, I've check my NP Environment, every damn thing I could think of and nothing seems to work. I recently changed around some settings in Debug Settings as well as Rebug Toolbox but I'm pretty sure they're all set to what I had them as before. If someone could reply with a picture or such with their Debug Settings/Toolbox settings for me to double check that'd be greatly appreciated. As to what I have changed recently before it fucked up, I was trying to get ProDG's TMAPI to work properly, and in the midst I changed the settings in Toolbox and Debug Settings, I have my mind set that it HAS to be something to do with that. Anyways, thanks in advance to whoever can help.*

Firmware: Rebug 4.81 DEX
COBRA Version: 7.3
PSN ID: Unbanned
CID: Unbanned (As concluded by my unprofessional opinion, Could be wrong.

Rebug Toolbox Current Settings Starting From Selector Tab:

-System Mode: REBUG
-XMB Operation Mode: Debug
-Debug Menu Type: Dex
-Toggle XMB CFW Settings: Disabled
-Toggle Host Information on XMB [DEX]: Enabled
-Toggle COBRA Mode: Enabled
-Toggle Ps2 Emulator: Cobra
-Toggle webMAN: Enabled.

LV1 Patches:

LV1 Peek/Poke Support: Enabled
LV2 Memory Protection: Disabled
HTAB Mapping With Write Protection: Disabled
Access to all INDI Info Manager Services: Disabled
Update Manager EEPROM Write Access: Disabled
Dispatch Manager Access: Disabled
Allow ENCDED IOCTL Command 0x85: Disabled
System Manager Ability Mask of GameOS: Disabled
Extract all PKG Types: Disabled
Full Access for Repo Nodes in Any LPAR: Disabled
LV1 Full Access to MFC_SR1 SPE Register: Disabled
LV1 Access to set Data Break Points: Disabled
LV1 Access to GPU GART Memory: Disabled.
Storage Manager ENCDEC Keys Access: Disabled
Skip all ACL Checks: Enabled
Initial GuestOS Loader: Disabled

DEX/CEX:

Swap LV2 Kernel: N/A*
Rewrite Target ID in Flash: N/A

Utilities:

Toggle QA Flag: Enabled
Toggle Recovery Mode: Disabled
Load LV2 Kernel: *No
Button Assignment: Cross is Accept but who cares
Backup/Restore xRegistry: No
Resize VFLASH/NAND Regions: N/A
Install Petitboot: N/A
Set GameOS Boot Flag: N/A
Create Packages Folder: N/A
Export Hypervisor LV1 Memory: What do you know it's N/A
Export GameOS: LV2 Memory
Export Flash to File: Can you guess?
Dump eid root key: C'mon you know you want to
Change Active PS3I I've already tried changing this to EID5. No luck :/

DEBUG SETTINGS ON XMB:

[Circle] Button Behavior: Back
NP Environment: np
Game Type (Debugger): Disc Boot Game
Game Output Resolution: 480 (4:3)
Game Output Sound: Maximum Number of Channels Set On [Sound Something]
BGM Player: On
GameContentUtil Boot Path: For Development
GameContentUtil Dir Name: N/A
GameContentUtil Boot Path (/app_home/PS3_GAME/)
Region Settings: North America
Fake Region: Off
HDCP: on
Display System Storage Free Space: Off
Fake Free Space: Off
Fake Limit Size: Off
Fake System Storage Access Speed: Off
Fake Save Data Owner: Off
Format System Cache: N/A
Release Check Mode: Dev Mode
Exception Handler: Off
NP Debug: Off
NPDRM Debug: Off
NPDRM Clock Debug: Off
In-Game Commerce Debug: Off
Service I N/A
MsgDialogUtiil Display Errorcode: Off
Format BD Emulator HD N/A
Disable ExitGame Timeout: Off
Core Dump: Off
Crash Report: On
PowerOnReset: Off
Boot Mode: System Software Mode
Blu-Ray Disc Access: BD Drive
Transfer Rate Pacing for BD Emulator: Equiv. to BD Drive
Network Settings for Debug: Dual Settings
Connection Status List for Debug: N/A
Connection Settings for Debug Dual Settings: N/A
Pad Auto Detect: On
Initialize Boot Parameters: No
Update Server URL: N/A
Video Upload Debug: On
Wake On LAN: Off
PlayStation Store Ad Clock: Off
Dummy XMB (in game) Debug: Off
Dummy BGM Player Debug: Off
TPPS Proxy: Do Not Use
Game Update Impose Test: Off
Network Emulation Setting: Off
Network Emulation Status: N/A
MediatedServices: Mediator URL: N/A
MediatedServices: Provider Data: N/A
MediatedServices: Notifications: N/A
WLAN Device: On
NAT Traversal Information: N/A
Adhoc SSID Prefix: PSP
Disc Auto Start at System Startup: Off
3D Video Output: Automatic
Fake NP SNS Throttle: Off (60 sec)
Fake Plus: Off
Application Type: PS3
Improper Shutdown Warning: On
SF Force: Off
Playstation manifest URL: Off
Closed Captions: Off
Closed Captions Settings: N/A

Inputs from other NGU Users in the comments:

Changing CID Through CCAPI: Did Not Work
Updating to 4.81: Did Not Work

**Sony has patched Fake, Generated, or Invalid CID's. Leading to the error 8002A224. Find Thread Here: You must login or register to view this content.

What should I do? I bought all of my CID's from so called "trusted sellers" and they all give me this error. I'm at a lost at this point

May have to get a broken PS3 and dump a cid

Raga quindi è un problema di cid falsi? Fatemi capire...

You must login or register to view this content.

Yes. 8002A224 = invalid cid error

You either have an invalid CID or you can try to change your active PS3id to CEX/DEX in rebug toolbox..

Yep, im using a real CID . . .

Are you COMPLETELY sure. A lot of people are selling fake cids to scam people.

MANY people used this exploit to their advantage and called them "real", and scammed people out the ass. Go into CCAPI, Connect, and reset your IDPS, that'll give you your stock console ID. That is a true CID and you can tell by it either letting you log in, or sayings its banned. That's the only way to see if its a real CID I believe

Damn it, all that work for a lame CID. Maybe we dont have to wait, what, another decade to find a new exploit? lol. Thanks for your help, regardless man.

It's just that it wasn't your typical "found" exploit, if you know what I mean.. This was a mistake on sony's part for only a month, or few months now, and they have just fixed it...
Chances are we will never see that again until sony gives up on ps3...