Initialising the screen prior to payload execution in order to see ARM9 binaries' outputs.What is screeninit?
Initialising the screen prior to payload execution in order to see ARM9 binaries' outputs.What is screeninit?
I liked it as well, not because it's my idea or anything. But no dev ever wants to make changes because "it'd make things confusing" or "it sounds dumb". So I'm done.I actually like /homebrew/ path. Mostly because I find it cleans up the root of my SD card a bit more.
Multiple releases means more shit to maintain, and I have real life responsibilities as well. Making it check a million paths is only slightly better, because that will increase payload size. I'll just go with SD root, but keep the bin file boot.bin. I've got a few ideas to check if possible to handle screeninit and a few other things better. Stay tuned.Maybe it could try different paths? i.e. try path 1, if there's no file there then try path 2, if there's no file there try path 3 etc. until it either locates a payload or falls back on the built in miniCFW. Overcomplicating things with multiple releases isn't much of a solution.
Pouty pout, I liked the feature.I liked it as well, not because it's my idea or anything. But no dev ever wants to make changes because "it'd make things confusing" or "it sounds dumb". So I'm done.
Convince devs to switch to it, and I'll keep it.Pouty pout, I liked the feature.
No need to do that, in meanwhile you can make a directory for all ShadowNand stuff, probably "sd:shadownand/boot.bin" and "sd:shadownand/safe_mode.bin".Convince devs to switch to it, and I'll keep it.
I am still trying to convince people to stop using RXTools. But I can add this to my mission as well!Convince devs to switch to it, and I'll keep it.
+1 for this. I don't want shadownand to be scattered with other stuffs as well. I like how when I want to look for shadownand files, I'll only look in a single folder.No need to do that, in meanwhile you can make a directory for all ShadowNand stuff, probably "sd:shadownand/boot.bin" and "sd:shadownand/safe_mode.bin".
ShadowNAND uses two files anyway: boot.bin, and safe_mode.bin. When I add extra files to be read, they will be at sd:/ShadowNAND+1 for this. I don't want shadownand to be scattered with other stuffs as well. I like how when I want to look for shadownand files, I'll only look in a single folder.
ShadowNAND uses two files anyway: boot.bin, and safe_mode.bin. When I add extra files to be read, they will be at sd:/ShadowNAND
safe_mode.bin will be booted if you hold dpad_down while booting. I use it for saving my ass if I fuck up something in stage2, and for boot manager.What's the function of safe_mode.bin?
Do u have a modded home menu/font/power off menu?Im having problems updating my sysnand in both my 3ds and n3ds both on latest luma3ds and shadownand v0.85 intalled to v11.1, is anyone having the same issues? it says "unknonwn error"
yep, seems to be an issue with anyone who has custom HOME. I think I won't update to 11.1 for now cuz I don't want to have to modify Home again and cuz NTR doesn't yet work natively.It was modded back in 10,3 times, but i updated to v11 without any issues. Anyway, i reinstalled original home menu on both consoles and updated to v11.1 without any issues
Yes. This IS A9LH. If I am not wrong, you install it the same way you'd install A9LH from SafeA9LHInstaller via payload.So if I already have A9LH installed can I still install this? I am currently on luma.
Oh so do i have to restore my pre-A9LH nand backup and re do it? ewYes. This IS A9LH. If I am not wrong, you install it the same way you'd install A9LH from SafeA9LHInstaller via payload.
Sent from my Motorola DynaTAC 8000x using Tapatalk
Oh so do i have to restore my pre-A9LH nand backup and re do it? ew
No, just as with "regular" A9LH, you just install it.Oh so do i have to restore my pre-A9LH nand backup and re do it? ew
Yes. This IS A9LH. If I am not wrong, you install it the same way you'd install A9LH from SafeA9LHInstaller via payload.
Sent from my Motorola DynaTAC 8000x using Tapatalk