Vita Guides: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
== How to check if a DevKit has been activated before & when == | == How to check if a DevKit has been activated before & when == | ||
<code>psp2ctrl.exe get-setting kernel:/bootparam</code> | |||
will return something like | |||
<code>45 03 C7 63 01 13 04 00 45 03 C7 63 00 00 00 00 01 00 00 80 00 00 00 01 00 00 04 00 18 00 00 38 <binary>:System.Byte[]</code> | |||
where "45 03 C7 63" is the date (here 17/01/2023) | |||
== How to check if there is a QAF token installed == | == How to check if there is a QAF token installed == | ||
In any case dumping NVS is the savest way to tell for sure if and which kind of token is installed! | In any case dumping NVS is the savest way to tell for sure if and which kind of token is installed! | ||
=== CEX (Retails) === | === CEX (Retails) === | ||
Dumping NVS or using Apps to check and display the token name. (eg: PSVident or QAFUtility [PCSI90043]) | Dumping NVS or using Apps to check and display the token name. (eg: PSVident or QAFUtility [PCSI90043]) | ||
=== DEX (TestKits) === | === DEX (TestKits) === | ||
When the Kit is activated for a very long time there most likely is an active QA Token installed. | When the Kit is activated for a very long time there most likely is an active QA Token installed. | ||
=== TOOL (DevKits) === | === TOOL (DevKits) === | ||
| Line 52: | Line 58: | ||
== How to dump a DevKit == | == How to dump a DevKit == | ||
=== with Activation via Neighborhood === | |||
0) Re-Activate <br> | |||
1) rename "devdump_xxxxxx.skprx" to "bootstrap.skprx" and put into local file serving directory (host0)<br> | |||
2) enable devmode (via for example <code>psp2ctrl set-setting integer bootparam:/development_mode 1</code>)<br> | |||
3) run "ngs_exploit_XXX.self"<br> | |||
<br> | |||
NGS Exploit files: https://www.mediafire.com/folder/7h2n6rqu5rqks/NGS<br> | |||
Devdumpers: https://github.com/SKGleba/VitaTools/tree/main/devdumper/build<br> | |||
=== without activation === | |||
use Henkaku / Henlo | |||
== How to dump a MemoryCard == | |||
=== via DevKit === | |||
=== via Vita === | |||
== How to fix a Devkit stuck in PSTV mode == | |||
Lorem Ipsum | Lorem Ipsum | ||
== How to | == How to downgrade a PDEL below 1.69 == | ||
Lorem Ipsum | |||
== How to replace a CP Battery == | |||
They all use a.. | |||
=== PDEL / new DEM === | |||
Lorem Ipsum | |||
=== DEM-3000G/H === | |||
Lorem Ipsum | Lorem Ipsum | ||
Revision as of 11:18, 28 June 2023
How to check if a DevKit's Firmware is Internal/External
Activate and try run a game cartridge. If there is an error it is most likely internal. To confirm it needs to be dumped and the modules checked.
How to check if a DevKit has been activated before & when
psp2ctrl.exe get-setting kernel:/bootparam
will return something like
45 03 C7 63 01 13 04 00 45 03 C7 63 00 00 00 00 01 00 00 80 00 00 00 01 00 00 04 00 18 00 00 38 <binary>:System.Byte[]
where "45 03 C7 63" is the date (here 17/01/2023)
How to check if there is a QAF token installed
In any case dumping NVS is the savest way to tell for sure if and which kind of token is installed!
CEX (Retails)
Dumping NVS or using Apps to check and display the token name. (eg: PSVident or QAFUtility [PCSI90043])
DEX (TestKits)
When the Kit is activated for a very long time there most likely is an active QA Token installed.
TOOL (DevKits)
When the Kit is activated for a very long time there most likely is an active QA Token installed. For DevKits you can often tell from the Console Output alone as it will have additional debug output. It is however possible that there is an inactive token still installed while the firmware was reverted to external for example. In that case only dumping NVS can tell.
What kind of QAF Tokens are there and what do they do
| Name | Flags | Notes |
|---|---|---|
| QAF_QATEAM_E | 01 00 00 00 00 00 0D 04 64 00 00 00 04 00 00 03 | for "QualityAssurance Team" units (early) |
| QAF_QATEAM_MINI_E | 01 00 00 00 00 00 0D 04 64 00 00 00 04 00 00 03 | for "QualityAssurance Team" units |
| QAF_QATEAM_FULL_E | 11 00 00 00 00 00 0F 04 64 00 00 00 04 00 00 03 | for "QualityAssurance Team" units |
| QAF_SYS_DEV_I | 33 00 00 00 00 00 07 05 73 01 00 01 06 03 03 01 | for DevKits used for "System Development" |
| QAF_MGVIDEO_DEV_I | 33 00 00 00 00 00 07 05 73 01 00 11 06 02 03 01 | for DevKits used for "MagicGate Video Development" |
| QAF_MGVIDEO_ADV_I | 33 00 00 00 00 00 07 05 73 01 00 11 06 03 03 01 | for DevKits used for "MagicGate Video Development" |
The "_E" / or "_I" suffix indicates the Firmware the token is for. (External / Internal)
How to re-activate a DevKit
Lorem Ipsum
How to re-activate a TestKit
Lorem Ipsum
How to dump a DevKit
with Activation via Neighborhood
0) Re-Activate
1) rename "devdump_xxxxxx.skprx" to "bootstrap.skprx" and put into local file serving directory (host0)
2) enable devmode (via for example psp2ctrl set-setting integer bootparam:/development_mode 1)
3) run "ngs_exploit_XXX.self"
NGS Exploit files: https://www.mediafire.com/folder/7h2n6rqu5rqks/NGS
Devdumpers: https://github.com/SKGleba/VitaTools/tree/main/devdumper/build
without activation
use Henkaku / Henlo
How to dump a MemoryCard
via DevKit
via Vita
How to fix a Devkit stuck in PSTV mode
Lorem Ipsum
How to downgrade a PDEL below 1.69
Lorem Ipsum
How to replace a CP Battery
They all use a..
PDEL / new DEM
Lorem Ipsum
DEM-3000G/H
Lorem Ipsum