More actions
m (Text replacement - "GameBrew!" to "GameBrew") |
No edit summary |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
|title=Vita Homebrew Apps (System Tools) - GameBrew | |title=Vita Homebrew Apps (System Tools) - GameBrew | ||
|title_mode=append | |title_mode=append | ||
|image= | |image=psvita2.png | ||
|image_alt=VitaRW | |image_alt=VitaRW | ||
}} | }} | ||
{{Infobox Vita Homebrews | {{Infobox Vita Homebrews | ||
|title=VitaRW | |title=VitaRW | ||
|image= | |image=psvita2.png | ||
|description= | |description=Enable RW access to read-only partitions (e.g. vs0, os0). Do not use it. | ||
|author= | |author=Major_Tom | ||
|lastupdated=2016/09/13 | |lastupdated=2016/09/13 | ||
|type=System Tools | |type=System Tools | ||
| Line 18: | Line 18: | ||
|source=https://github.com/tomtomdu80/VitaRW | |source=https://github.com/tomtomdu80/VitaRW | ||
}} | }} | ||
VitaRW | VitaRW is a tool that gives you Read/Write access to the Vita protected partitions (e.g. vs0, sa0, os0, etc). | ||
'''Note from developer:''' | |||
==Partitions mounted in RW== | This is a PoC, and should be used by devs who like the risk. Used improperly, this tool could let you badly damage your PS Vita, beyond repair. If you mess up with the wrong files, you'll end up with a permanent brick and your PS Vita will become an expensive paperweight. | ||
==User guide== | |||
===Partitions mounted in RW=== | |||
0x200= os0 0x300= vs0 0x400= vd0 0x500= tm0 0x700= ud0 0x800= sa0 0x900= gro0 0xC00= pd0 | 0x200= os0 0x300= vs0 0x400= vd0 0x500= tm0 0x700= ud0 0x800= sa0 0x900= gro0 0xC00= pd0 | ||
==What is VitaRW | ===What is VitaRW=== | ||
If you read the paragraph above, read it again. Then read this: this release is for developers/tinkerers who are aware of the risks. Most people should be patiently waiting for actual tools that have been vetted and beta tested. | If you read the paragraph above, read it again. Then read this: this release is for developers/tinkerers who are aware of the risks. Most people should be patiently waiting for actual tools that have been vetted and beta tested. | ||
With that out of the way, what does VitaRW let you do, technically? | With that out of the way, what does VitaRW let you do, technically? | ||
Here's what we know about some of these partitions (from [https://playstationdev.wiki/psvitadevwiki/index.php/Files_on_the_PS_Vita Vitadevwiki]): | |||
*os0 found on the NAND is where the | *os0 found on the NAND is where the "main" OS (aka CoreOS) files are including all the kernel libraries and the most important user libraries. There's always two copies of this for redundancy and updating will only update the inactive partition and the active flag is swapped. | ||
*sa0 found on the NAND is the | *sa0 found on the NAND is the "bulky" data like fonts and handwriting information. Why is it a separate partition? Because it makes update files smaller. Your "systemdata" PUP provides the update for this partition. | ||
*vs0 found on the NAND is the rest of the OS including all the system apps, the main shell, and the remaining user libraries | *vs0 found on the NAND is the rest of the OS including all the system apps, the main shell, and the remaining user libraries. | ||
*Hopefully this gives you an idea of how dangerous it could be to change these files on your console. With that being said, according to Major_Tom, SMOKE has started modifying some files in vs0 and did not run into any big issue. Then again, proceed at your own risk. | *Hopefully this gives you an idea of how dangerous it could be to change these files on your console. With that being said, according to Major_Tom, SMOKE has started modifying some files in vs0 and did not run into any big issue. Then again, proceed at your own risk. | ||
==Hall of Fame== | ===Hall of Fame=== | ||
Try not to end up here. | Try not to end up here. | ||
<pre> | <pre> | ||
| Line 46: | Line 47: | ||
<Moolie> yep | <Moolie> yep | ||
<Lupo511> what happened? | <Lupo511> what happened? | ||
<Moolie> I | <Moolie> I **** up os0 | ||
<Lupo511> yeah, I mean what did actually happen | <Lupo511> yeah, I mean what did actually happen | ||
<Moolie> well I deleted some stuff in a folder | <Moolie> well I deleted some stuff in a folder | ||
| Line 54: | Line 55: | ||
</pre> | </pre> | ||
== External links == | ==External links== | ||
* Wololo - https://wololo.net/2016/08/19/release-vitarw-gives-us-write-access-vitas-protected-partitions-wheres-downgrader/ | * Wololo - https://wololo.net/2016/08/19/release-vitarw-gives-us-write-access-vitas-protected-partitions-wheres-downgrader/ | ||
* | * GitHub - https://github.com/tomtomdu80/VitaRW | ||
* VitaDB - https://vitadb.rinnegatamante.it/#/info/151 | * VitaDB - https://vitadb.rinnegatamante.it/#/info/151 | ||
Latest revision as of 13:35, 6 July 2024
| VitaRW | |
|---|---|
 | |
| General | |
| Author | Major_Tom |
| Type | System Tools |
| Version | #04d791c |
| License | Mixed |
| Last Updated | 2016/09/13 |
| Links | |
| Download | |
| Website | |
| Source | |
VitaRW is a tool that gives you Read/Write access to the Vita protected partitions (e.g. vs0, sa0, os0, etc).
Note from developer:
This is a PoC, and should be used by devs who like the risk. Used improperly, this tool could let you badly damage your PS Vita, beyond repair. If you mess up with the wrong files, you'll end up with a permanent brick and your PS Vita will become an expensive paperweight.
User guide
Partitions mounted in RW
0x200= os0 0x300= vs0 0x400= vd0 0x500= tm0 0x700= ud0 0x800= sa0 0x900= gro0 0xC00= pd0
What is VitaRW
If you read the paragraph above, read it again. Then read this: this release is for developers/tinkerers who are aware of the risks. Most people should be patiently waiting for actual tools that have been vetted and beta tested.
With that out of the way, what does VitaRW let you do, technically?
Here's what we know about some of these partitions (from Vitadevwiki):
- os0 found on the NAND is where the "main" OS (aka CoreOS) files are including all the kernel libraries and the most important user libraries. There's always two copies of this for redundancy and updating will only update the inactive partition and the active flag is swapped.
- sa0 found on the NAND is the "bulky" data like fonts and handwriting information. Why is it a separate partition? Because it makes update files smaller. Your "systemdata" PUP provides the update for this partition.
- vs0 found on the NAND is the rest of the OS including all the system apps, the main shell, and the remaining user libraries.
- Hopefully this gives you an idea of how dangerous it could be to change these files on your console. With that being said, according to Major_Tom, SMOKE has started modifying some files in vs0 and did not run into any big issue. Then again, proceed at your own risk.
Hall of Fame
Try not to end up here.
<Moolie> well I found what a brick looks like xdxd <Lupo511> did it brick? <Moolie> yep <Lupo511> what happened? <Moolie> I **** up os0 <Lupo511> yeah, I mean what did actually happen <Moolie> well I deleted some stuff in a folder <Moolie> then now its stuck on ps sign [...] <Moolie> xyz: I deleted everything in os0:sm/