Well in the meantime you can always check your shoulder buttons. Through observation around here it's almost always the "L" or "R" button that gets stuck and causes issues.
what would it need to be changed in it's source exactly? I'm a little bit confusedIs there someone on here who can do a simple source edit and compile GM9? Help out @yudhafd, if you can pls .
I assume you can just remove the permission check from the Lvl 0 Sysnand from the PERM_BASE.....what would it need to be changed in it's source exactly? I'm a little bit confused
but it isn't defining that the normal user at GM9 bootup gets Level 0 SysNAND access?(For me it seems that way..)I assume you can just remove the permission check from the Lvl 0 Sysnand from the PERM_BASE.....
I dunno, Lol. I was just guessing since he pointed to that line specifically. I don't know what you could change it to...but it isn't defining that the normal user at GM9 bootup gets Level 0 SysNAND access?(For me it seems that way..)
I changed:I dunno, Lol. I was just guessing since he pointed to that line specifically. I don't know what you could change it to...
#define PERM_BASE (PERM_SDCARD | PERM_IMAGE | PERM_RAMDRIVE | PERM_EMU_LVL0 | PERM_SYS_LVL0)
#define PERM_BASE (PERM_SDCARD | PERM_IMAGE | PERM_RAMDRIVE | PERM_EMU_LVL0 | PERM_SYS_LVL1)
It works just fine just so you know. As in, it doesn't require permission.Well, here's my first try. I have no way to test it so..
Thanks a lot.I have another few hours until I get home
if nobody has helped you by the time im home and done with my homework (could be upto 8 hours from now) ill edit and compile for you
i was gona (and still going to because it would actually be very useful) change thisI changed:
Code:#define PERM_BASE (PERM_SDCARD | PERM_IMAGE | PERM_RAMDRIVE | PERM_EMU_LVL0 | PERM_SYS_LVL0)
to
Code:#define PERM_BASE (PERM_SDCARD | PERM_IMAGE | PERM_RAMDRIVE | PERM_EMU_LVL0 | PERM_SYS_LVL1)
#define PERM_BASE (PERM_SDCARD | PERM_IMAGE | PERM_RAMDRIVE | PERM_EMU_LVL0 | PERM_SYS_LVL0)
#define PERM_BASE (PERM_SDCARD | PERM_IMAGE | PERM_RAMDRIVE | PERM_EMU_LVL0 | PERM_SYS_LVL0 | PERM_ALL)
I did plan to put PERM_ALL instead of PERM_SYS_LVL1, but since PERM_ALL gives full access to everything, a noob could do something that could break his system and then put the blame on us...i was gona (and still going to because it would actually be very useful) change this
to thisCode:#define PERM_BASE (PERM_SDCARD | PERM_IMAGE | PERM_RAMDRIVE | PERM_EMU_LVL0 | PERM_SYS_LVL0)
but that works tooCode:#define PERM_BASE (PERM_SDCARD | PERM_IMAGE | PERM_RAMDRIVE | PERM_EMU_LVL0 | PERM_SYS_LVL0 | PERM_ALL)
yeah thats why im not releaseing my build and i only built it for a9lh incase it does get released by accidentI did plan to put PERM_ALL instead of PERM_SYS_LVL1, but since PERM_ALL gives full access to everything, a noob could do something that could break his system and then put the blame on us...
they have a warning for that when you open the sysnand so you cant claim accidentI understand noobs might get over zealous but a write lock isn't exactly bullet proof glass lol. If they really want to delete things, they can. People use FBI and delete system titles all the time because "I didn't know what it was" lol so maybe that should implement some button combo as well so no one can claim accident.
Sent from my SAMSUNG-SM-N910A using Tapatalk
I know, but the fact is they still do. Just like you have to accept an update from Nintendo but it happens on "accident" quite often. I was being facetious.they have a warning for that when you open the sysnand so you cant claim accident
but yeah file management sucks in fbi