HOME Menu limits to displaying 300 icons. Like I said, it could've been accomplished with A9LH but it was never implemented. B9S doesn't change this or make it any more possible.there is no actual title limit
HOME Menu limits to displaying 300 icons. Like I said, it could've been accomplished with A9LH but it was never implemented. B9S doesn't change this or make it any more possible.there is no actual title limit
thats not a limit, the homemenu just runs out of ram, you can install 7662 titles and launch them through FBIHOME Menu limits to displaying 300 icons. Like I said, it could've been accomplished with A9LH but it was never implemented. B9S doesn't change this or make it any more possible.
Pretty sure it does.HOME Menu limits to displaying 300 icons. Like I said, it could've been accomplished with A9LH but it was never implemented. B9S doesn't change this or make it any more possible.
It doesn'tPretty sure it does.
Did you even read my postthats not a limit, the homemenu just runs out of ram, you can install 7662 titles and launch them through FBI
Well it's still not really limited thats the point, if the homemenu would be able to access more ram it could show moreDid you even read my post
>displaying icons
Anything can LOAD them, HOME Menu just limits to 300 displayed icons...
you can edit the homemenu easily here are some tuts out there, theres also linux for 3ds, but as brahma payloadThe Home Menu is still the Home Menu. Neither A9LH or B9S has any effect on it. If there was a fix for the 300 title issue with the Home Menu, it'd also be possible with all other entrypoints, including menuhax (on EmuNAND in that case, of course).
He does have A9LH. Hes on 11.2 A9LHoh so the one who asked has a9lh? looked to me like a noob with something like menuhax or mset or whatever
I don't think so because your console ID its stored on the server in a black list, or you can buy another 3ds to use their seedGuys small question... Would this be exploitable in a way or another to fully bypass the ban problem? (Yes, Big N high-kicked me because of Pokemon and that fuckin damn missclick on the menu, now I can ofc play online using the public seed but it would be nice if we could let's say install another nand backup or mod it, or whatever you can think about to access eshop again)
Anyway, I'll wait, I'm already running on a9lh and I don't see the point of upgrading right now.
If you installed sighax, then go aheadI have finish to update at sighax Can I update safely now ? I don't get trouble with somes app/games ?
once again sighax is the exploit used to install b9s / sign the firms.If you installed sighax, then go ahead
You are supposed to delete it from SYSNAND CTRNAND, IF it exists on there. It would only be loaded if you start your 3DS without the SD card though.sorry if this has been asked before, but will we now need to keep the boot firm always in the root of the SD in order to have the 3ds boot luma cfw?
i finished installing b9s , i deleted the boot9strap folder and it boots fine with luma cfw.
and i guess we need to only keep the boot firm after finishing the installation correct?
the only thing that was weird to me was were these steps >
- Navigate to [1:] SYSNAND CTRNAND
- Press (Y) to paste a copy of boot.firm
- Select “Copy path(s)”
- Press (A) to unlock SysNAND (lvl1) writing, then input the key combo given
- Press (X) on arm9loaderhax.bin to delete it <<< this one in particular, does this tell me to delete the arm9loaderhax from sysNAND lvl1? or the root of my mSD ? because i only had it in the root of my mSD and i deleted it from there for that step.
You are supposed to delete it from SYSNAND CTRNAND, IF it exists on there. It would only be loaded if you start your 3DS without the SD card though.
You can delete it from your SD card anyway though, which you did
edit: snipsorry if this has been asked before, but will we now need to keep the boot firm always in the root of the SD in order to have the 3ds boot luma cfw?
i finished installing b9s , i deleted the boot9strap folder and it boots fine with luma cfw.
and i guess we need to only keep the boot firm after finishing the installation correct?
the only thing that was weird to me was were these steps >
- Navigate to [1:] SYSNAND CTRNAND
- Press (Y) to paste a copy of boot.firm
- Select “Copy path(s)”
- Press (A) to unlock SysNAND (lvl1) writing, then input the key combo given
- Press (X) on arm9loaderhax.bin to delete it <<< this one in particular, does this tell me to delete the arm9loaderhax from sysNAND lvl1? or the root of my mSD ? because i only had it in the root of my mSD and i deleted it from there for that step.
That's because you never copied the file to the root of your sysNAND's ctrnand and you didn't have to do that. As I said, the reason for copying the .bin/ .firm is that Luma works without the SDthere was no arm9loaderhax in the root of my sysNAND's ctrnand.
It would only be there if you put it there to begin with.there was no arm9loaderhax in the root of my sysNAND's ctrnand.
sorry but how exactly do we know if we have b9s /sighax installed successfully?
if my 3ds boot with the boot firm of luma, then it means it is installed fine?
okki, got it sankyuThat's because you never copied the file to the root of your sysNAND's ctrnand and you didn't have to do that. As I said, the reason for copying the .bin/ .firm is that Luma works without the SD