(adsbygoogle = window.adsbygoogle || []).push({}); That’s from graf_chokolo’s HV documentation, but do note, it /is/ possible to generate a “working” token for QA token, using another part of the system, but it is what you would call a “false-token”. It does not unlock anything fancy, only the repository node in Lv-1. Token requires a seed and it is formed from that seed and the EID0 of your console I think. QA Flag requires the QA Token to work. FSELF flag controls whether FSELFs can run as “root” or have modified control flags, sort of like the way PSGroove does things with 3.41. Debug Support is currently unexplored territory, but it has to do with debug permissions.

Recover Flag allows backup (ros1) Core OS in NOR/NAND, to be run instead of ros0 , I’ve never seen this flag set. Update Status determines whether you are in updater mode, and whether to run ps3swu.self from /dev_hdd0. Device Type controls whether you are in Service mode or not, value 0xFF is retail, and 0*********00 is Factory/Service mode. HDD Copy Mode is pretty much self explanatory.

0x600C - Write EEPROM

Writting to EEPROM of Update Manager is also possible through DM
Tested this service successfully with QA flag

I have got access to this service through DM and PSGroove and tested it
The service expects one additional unknown parameter of size 4 bytes, it has to be 0x00000001 or else the service fails

Here is the return value:

00 00 00 01 00 00 00 00 00 03 00 20 00 00 00 00 00 00 00 00 00 00 00 01
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01
from hypervisor reverse engineering so basiclly u need dongle or knowledge of dm mode ??

Thanks even though i had r read it already.

no prob just seeing if this help any one here on ngu

Where did you get this info from?

hypervisor bible

Lawlz
10 char