Homebrew [Release] 3DSBank - "Nintendo 3DS" folder selector

  • Thread starter Thread starter RocketRobz
  • Start date Start date
  • Views Views 160,657
  • Replies Replies 370
  • Likes Likes 75
Hi! I've come to greets&thanks for this amazing tool!

But... I have, also, a little suggestion to do about an "add-on" for it, or something like...

First things first: I'v noticed that, when a new folder is made, it comes completely 'naked'! There'r totally no installed apps...
That's OK! It's the app proposal... But, how to install new apps, noob-friendly?!? Even "vital" jailbroken apps (as FBI, nShop, Universal Updater, Checkpoint etc) ARE NOT on this new folder! Then, it's mandatory to "reinstall" those apps manually at this new folder (atleast FBI, the most basic app to manage other apps w/o messing on storage using other device like a PC or something else) - wich is very noob-unfriendly (and, let's put this way, "less elegant")!
(By myself, initially, I'v made a "basically setuped backup" containing those essential apps only - no games yet - and each new folder created I manage to paste this backup inside the new folder. Functional, but if there is a new relevant app to be duplicated over the folders - like Ghost eShop, as example, wich one I'v meet only after starting to work with 3dsBank - I need to re-download it n/or messing with File Managers again.)

I guess you'v got the point... Even if got, lemme explain my ideas.
One of the solutions I'v tough is to have, inside the 3dsBank own interface, an 'app manager' whose only function is to (check if already exists and, if not) copy apps from other banks to the newly being created one (probably working from the original folder/recently made enviroment created from jailbreak ).
Other solution is a 3rd party app itself to do the above mentioned.
A very simpler solution is to assemble and host a pre-made autoextractable package (somewhat alike my above mentioned backup) to people download and apply each new folder.

I can imagine some other solutions yet, maybe a bit more complexes not only to implement but even to use after. So, letta restraint on these ones...


And so? Can be?



Thanks in advance!
There would need to be a way for 3DSBank to recognize the apps inside the banked folders, before trying to transfer some apps over from one folder to a different one.
 
I thought about that... Due this I'v mentioned the 3rd party app: since installed at the starter folder (the initial jailbroken setup folder, even before installing 3dsBank), it may can replicate the other installed apps to the desired folders. The advantage on this approach is avoiding to (hard) update the 3dsBank itself - you can just insert a simple message alert about the other app, or mention it on the 3dsBank database entry(es) to do people seek ahead for the complementary app by themselves! ;)
 
Is there any possibility to add a feature to boot into this app and pick a folder when turning the system on? No idea how any of this works, I just thought it'd be cool.
 
Is there any possibility to add a feature to boot into this app and pick a folder when turning the system on? No idea how any of this works, I just thought it'd be cool.
You can have Luma autoboot into it by putting in the title ID (which you should see in FBI) in the Luma config file, and then turning on the autoboot feature in the Luma config menu.
 
Just came back here to say that I experienced the issue where 3DSBank froze yet again when I selected a slot, although this time this particular micro SD card did not die. I eventually had to turn the 3DS off after it froze, to which it made a brand new home menu (as expected), but trying to select other slots in 3DSBank would not successfully change the home menu. Worrying that my card failed like last time, I backed up all of my data before doing anything else, only to find out that after I backed up my data, when I changed the slot number (in the config file of 3DSBank) to one of my existing home menus and renamed the corresponding slot folder to "Nintendo 3DS" and put it on my root, I was able to interact with my data normally on my 3DS. 3DSBank also started to work from there, and switching to different slots was seamless as it was before.

Based on this, I think it's safer to say that this whole 3DSBank freezing thing is either a hardware failure that happens pretty much .1% of the time, or a bug with 3DSBank that too happens .1% of the time.
 
I have a question, is there a bug where the theme of the main 3ds menu will change to the default theme or change to the theme of another 3ds menu?
 
extdata, I think.
If I recall correctly, the actual themes themselves are stored as DLC for the home menu, with the configuration data for the home menu (current theme settings, icon layout, etc) being stored as extdata.
 
  • Like
Reactions: RocketRobz

Site & Scene News

Popular threads in this forum