Hacking Gamesd.skprx vs Storage Manager

  • Thread starter Thread starter godreborn
  • Start date Start date
  • Views Views 11,114
  • Replies Replies 28
Yamt lite is outdated, lastest official version is recommended, and as i said it is not like gamesd, it is a different patch.

Also, yamt adds NO delay.
StorageManager is the one with a big delay, everything else is faster.
Not really outdated if you look at the progress of the OG one. Lite just cut out the troubled bits and called it a day. Storage Manager is the same speed once booted into so idk where you get its faster everywhere else.
 
Yamt is not the most stable thing also the old uninstaller has an error.
New 3.1 fixes that and a few more things.

If you don t want troubles or possible bugs it is a good choice to update.

Noone is speaking about the speed when booted because it makes no sense...

The delay is a boot delay, when the plugin starts because it adds a few seconds to your boot time.
 
Yamt is not the most stable thing also the old uninstaller has an error.
New 3.1 fixes that and a few more things.

If you don t want troubles or possible bugs it is a good choice to update.

Noone is speaking about the speed when booted because it makes no sense...

The delay is a boot delay, when the plugin starts because it adds a few seconds to your boot time.
Yamt lite ive had no issues with so idk how you can say its unstable. you said Storage manager is faster everywhere else. I said its no faster then YAMT.
 
I've installed yamt lite and 0syscall6. however, I encountered a bug to where it only looks for boot plugins' config in ur0. it's in vs0 on 3.65 enso. I moved it over, patched it, then moved it back using vita rw. everything works, so I'm backing up my stuff right now. if you don't move it back, it won't work.

edit: I also have the sd2vita in a version 5. and, 0syscall6 is working too.
 
Last edited by godreborn,
  • Like
Reactions: Raylight
I've installed yamt lite and 0syscall6. however, I encountered a bug to where it only looks for boot plugins' config in ur0. it's in vs0 on 3.65 enso. I moved it over, patched it, then moved it back using vita rw. everything works, so I'm backing up my stuff right now. if you don't move it back, it won't work.

edit: I also have the sd2vita in a version 5. and, 0syscall6 is working too.
I have 3.65 Enso and my plugins and stuff are in ur0:, not sure why yours were in vs0.
 

the only reason for that that I can think of is that I installed enso in a different manner. it was an older version, and they were probably stuck in vs0 due to not having write privileges. you have to use vita rw instead. if you mess with those files without knowing what you're doing, you could brick. I think boot_plugins.txt says that at the top of the file. everything works fine, and I've heavily modded the vita in the past, and I've never even suffered a soft brick.
 
the only reason for that that I can think of is that I installed enso in a different manner. it was an older version, and they were probably stuck in vs0 due to not having write privileges. you have to use vita rw instead. if you mess with those files without knowing what you're doing, you could brick. I think boot_plugins.txt says that at the top of the file. everything works fine, and I've heavily modded the vita in the past, and I've never even suffered a soft brick.
This is correct. You installed 3.65 Enso via the update365 tool which takes a 3.60 Vita and updates it to 3.65 while also applying Enso at the same time. This installed all the plugins and stuff into vs0. I used to have mine that way too, but after native 3.65 Enso came out I restored my Vita and reinstalled Enso so that all my content was now in ur0 which has solved a lot of headaches exactly like this one for me.
 

Site & Scene News

Popular threads in this forum