92w ago - Following up on my previous post, below is a video demonstration for those interested dubbed PS Vita Crash CMA Debug Time via Xcode Execution.
I just released a fast small video to show the crash and freeze of the PlayStation Vita system using Xcode Execution. I also explain how to check every information coming from the CMA to PS Vita (debugger).
Below is a pastebin with tutorial and the video that show you something interesting.. As I promise and I do what I said
The tutorial to Debug CMA PS Vita Under MacOS and Xcode: http://pastebin.com/40FrAJXg
CMA Debugging PS Vita Under Xcode Execution Tutorial
You need a Dev account Apple to have Xcode that you can use your MacOSX under a Development Environment
1- Launch Xcode (Spotlight -> Xcode)
2- Create a Empty Project (MacOSX)
3- Enter whatever name on the Product Name (For Example PSV)
4- A new window appear, change command-line builds use Debug than release
5- Click on BreakPoints
6- On the top menu of the Xcode, choose Product and make a new scheme and name your new scheme psv for example, press ok
7- A new windows appear that you can edit your scheme on the left menu you can see RUN click on it and edit the run configutation build configuration -> Debug Executable (you need to choose the CMA.APP) for that, just click on None to Other and here you choose the CMA.APP Debugger, you can choose ever LLDB or GDB (choose by default GDB) Launch = Auto
8- Choose Diagnostics and here active every option Memory Management (malloc, Guard Malloc, Objective-C) Logging (Memory/execptions/Dyld) Debugger (Legacy->Stop on debugger and debugstr) Click OK (don't forget to active breakpoints before click Ok) click OK
9- Plug-in your PS Vita and Click on RUN (if you are connected in Wifi you just connect fast and disconnect)
Xcode/IO Framework, etc it's the best way to exploit the PS Vita under MacOSX and as you would see, the Sony have a strong access to your kernel system that i really don't appreciate and can control everything
The PS Vita use also NFS -> Network File System and Open Remote System File that ping pong between the PS Vita and Sony Server.
Hope that would help some smart dev And here the video that show you a example of what you can do
Some PS Vita user ask me the PS Vita Windows Driver that i made it's available on the older thread PS Vita 1.50 Firmware but I reuploaded the driver that you don't need to search
Griever2Kx It's hope to you, if you want to use your PS Vita use it and update don't worry about the update right now, anyway FW 1.06 is a firmware with too much bug that give you some problem it's unstable and some app/game will not run correctly with this Firmware. It's more easy with 1.06 but also more unstable.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
I'm happy that you discover the first step of an exploit, and I would love to see homebrews coming to Vita. If you say that Sony can't fix the USB Debug, stop your teasing and unveil the USB debug trick and everyone will have the chance to help you (as a developer, I will probably the first one).
It can't work 3.55 Firmware don't include the necessary driver to recognize the PS Vita, etc...
4.11 with a flasher will change anything because anyway you can't install PS Vita app that is not properly sign with your unique ID PS Vita Account, etc..
When you install a PS Vita App with the PS3, the PS3 go under a special mode that you don't have anymore access to the PS3 XMB, you control everything with the CMA Lite task background of the PS3 and the CMA from the PS Vita, it's more the PS Vita control the transfer than the PS3, the PS3 only call the PS Vita system to install PS Vita APP, kernel call to the PS3 system that lets you to control PS3/PS Vita transfer file.
If you talk about unit13, it's not a problem of a fail it's just the 3D engine need more optimisation, fix some memory access for decompressing textures, shaders,
About the USB Debug mode they can't fix, i was starting to making a pastebin with more explain about the PS Vita/Debug why it can't be fixed and why it's useful. i'm sure that have already many dev who know how to exploit it (the PS Vita = A smartphone)
I didn't check all but it seems that Netflix have also a similar problem (probably because the App was release a little bit too fast without checking everythings)
I'm pretty sure he was saying about the update of the PS Vita that for sure don't need that much security that already have, about the stuff of the SEN Store and Vita Game Card is different the Vita Card (memory card) it's a Micro m2 + Encryption (not sure if is the best but that go to far for me) nothing else than that but the Encryption is generated by the PS Vita system and save your Unique ID in cache that when you install a game or app you can only launch that with your system.
Actually is not the PS3 decrypt the PS Vita App, it's the PS Vita system when is connected to the PS3 system the PS3 system = Host
Now about the dump the keys, it's not my job i try to offer more than that, like i said dualboot/bootstrap and also a alternative app that you can use under Linux/MacOS to exploit the PS Vita more easily i'm not here yet but i have the more important to exploit it.
Take a look to my last pastebin that i hope will let you understand more http://pastebin.com/hU1M9eWH
PS Vita ARM Debug Explain.
Probably some dev already know that but it's good to explain why we can go under Debug mode on the PS Vita that don't change that much than a Smartphone with ARM Architecture.
ARM CPU include a Debug mode and Monitor Mode (related to the Embedded)
As you probably know the Debug mode of the ARM, let you have a full control of the CPU, System Execution, Software, etc...
The Monitor Mode (related to the Interface) let you control some part of the system software in real-time (RTOS)
About the debug mode that use a breakpoint exception (remember USB is a external signal) that let you to use the external signal (hw,data breakpoint, enter debug and act debug state) the CMA use Monitor Mode to let you control the transfer file to your computer or PS Vita but with some limitation on the software and hardware access restricted
The instruction is stocked in a sequential memory of the PS Vita system, that if you use a breakpoint -> you read/write the memory
Take a look to this excellent pdf of ARM Cortex-A9 (CPU of the PS Vita) http://infocenter.arm.com/help/topic/com.arm.doc.ddi0407g/DDI0407G_cortex_a9_mpcore_r3p0_trm.pdf
Reason why i was talking about the CMA, the debug execution and the IOCTL call
Add this to all my last pastbin log execution (CMA, etc)
Also another one http://infocenter.arm.com/help/topic/com.arm.doc.dui0440b/DUI0440B_realview_platform_baseboard_for_cortexa9_ug.pdf
So you mean that's the USB Debug Mode can't be fixed through a FW-Update. That's cool. And I heard that some other App's have a fail algo too. You know what i mean Please don't mention it, because Sony reacts really quick these days.
Does i have the same possibilities with an App who has an fail algo too since the Facebook app went offline ?
And he says that the PS3 can decrypt the new packages on firmware 4.00 which contains the new PS VITA PKG AES key for the PS3 PS VITA content exchange feature. This means we can decrypt and get the content of the PS VITA PKG files via a 4.00 PS3. Sadly there's no solution to re-encrypt it again, yet. But maybe we will find a way to do it. Or there will be a Way if the Jailbreak from Waninkoko appears out of the wild. We will see.
''the unique key of your PS Vita are save in a special cache on your Windows for example and as you can see if you check the key of CMA on your windows reg, you can find that the CMA work in read-only mode that you can't modify and only Sony can modified this (this is pretty illegal, it works like a spyware/malware that let Sony control your computer) anyway this can be fixed, check your reg''