Separate names with a comma.
Discussion in '3DS - Tutorials' started by Temptress Cerise, Jun 21, 2016.
ok i think i understand everything and thank you very much
i just tried to downgrade in reinand and then this shows up what to do?
EDIT: it seems that the system settings shows rei 11.2 for me. so maybe it worked nontheless? strange is: after formating i started system nand. changed color to black (theme). then went into emunand, and it was black. now after downgrade my emunand is still black theme and sysnand is white again? are they not linked anymore? how can i check if nands are linked?
EDIT: seems like sysnand doesnt save my theme color anymore, after power off and on again ..
EDIT: gw emunand does not load anymore. i think something screwed up bigtime . loading the old sd card, everything seems to work as before. theme colors will save. gw emunand works..
Looks like one of the CIAs may have got corrupted or something. You could clone SysNAND to EmuNAND and try again (I'd recopy the CIAs over). Or just backup the EmuNAND on the old card, then copy it to the new one and restore it.
well i just started from scratch again, new sd card format emunand, clean sd. then i went into the systemmenue, and as before, the colors will always revert to white. changing, power off and power on will reset the theme color? what am i doing wrong? or is this normal?
EDIT: its the strangest thing. if i change theme color in emunand, it will stay after reboot. but sysnand always keeps reverting. this is making me insane...
and i got the same cia error while downgrading again as before, even though i redownloaded it fresh from nus. something is not working right ...
i will retest what happenes, if i transfer the sd card to the new one and not format emunand. i want to check if its working normally untill this point.
EDIT: its the same problem. when i just copy all the files from the old to the new sd card, and start the 3ds up. the theme is the white one and all changes do nothing. everything is saved, icon order, display brightness etc. only the theme reverts. i can also save the current black theme with arranged icons, and after reboot it will have the white one and i can load the black one again from the saved theme. but the standard just wont stay..any idea on what is going on? and also for the emunand im at a loss. i dont know exactly how to inject the bin into the emunand. my godmode launcher thin h as no setting for backup/inject nands. only the script for backup of your all in one file...
EDIT: the strangest thing, when i boot reinand without having emunand formated, it boots into reisysnand and there the old black theme is and changing the color will be saved upon reboot. whats happening? why is the luma sysnand acting up? should i reconfigure luma or something? if so, how can i do that?
so i guess i have the solution to the problem. it seems the 3ds really has problems with 256gb cards. i have 3 original sandisk cards, all of which work properly. 2x 128gb and 1x 256gb. my original 128gb works well, i used it for the last week. i tried just copying over the content to the other 128gb card and everything works fine. as soon as i use the 256gb card, the home theme gets reset for some unknown reason. downgrading i didnt try with the other 128gb but i bet it would work and doesnt work with the 256gb. so i guess this is it huh?
Yeah, it sounds like that's what it must be. Well, the manual only says it takes SDHC. It doesn't really say anything about SDXC. We're lucky 128 works I guess. Though I guess it's possible GW messed up formatting the card. You could try with GM9 and see if that solves it.
To restore a NAND image manually, you can select the file, NAND image options, Mount image to drive, and then copy nand_minsize.bin (select it and hit Y) to the E: drive (go to the E: drive and hit Y again). Restore scripts were included in GodMode 1.4.2 (written by yours truly) and when I get R6 ready, it will include them. It's getting close. I just changed all B9S installers. They now let you pick between B9S and GM9 for your firm (and for that matter, any other .firm you want to add to the "boot9strap" folder, as long as it will verify, and you include an .sha file to check it). So, technically they're Sighax installers now. I'm going to add GM9 as a chainloader option and it will be ready for release I think (unless they manage to fix that display bug, but I'm about to give up on that).
i dont think it will make a big difference, since the problem with the home theme arises even if i dont format emunand and only copy the files over. everything seemed to work (except the emunand downgrade which showed an error while showing it is 11.2 in the menue). but i dont want to realise after some time that other problems are also present so i will stick to the 128gb card i guess..
hej, so i read a bit on the inet and all, and i tried something. formatting the sd with 64kbit cluster size instead of the recommended 32 solves the theme problem. but only if i dont format emunand with the gw menu, after that its the same old story, even if i format the partition in windows with 64kbit again. i guess that settles it and i cut the strings of gw...
I've red your Tutorial. Gw runs very well.
I'm trying to upload luma from 7.0 to 8.0,but it gives me an error.
Is it cause i'm on A9LH?
Also, my fw is 188.8.131.52E NEW 3DSXL. How can i upload it to 11.20?
That would be it. Luma 8.x only runs on Sighax. If you want to upgrade from A9LH, my InScripted AIO (that iso site, CFW Discussion section, I can't upload it here, because it would no longer be an AIO) has an extremely easy to use "A9LH to Sighax" installer. It also has a pre-made configuration for B9S that includes Gateway (it's hotkeyed to B by default, but I include GM9 scripts to change the hotkeys, so, you can make it whatever you want). Just copy the contents of the "N3DS" folder within the "B9S Configurations" folder over, then copy the contents of the "A9LH to B9S" folder within the "Installers" folder over, and place the card in your system. It will boot to GM9. Just hit home, more, scripts, select the "0 - Install Scripts" option. I would pick option 3. B9S tends to be all most people need, but having the "Switch Firms" script will allow you to checkout GM9 if you want to (though if you would rather not mess with it, just pick option 1).
Since you are on A9LH, you can safely update to 11.2 (this will remain true if you upgrade to Sighax). Just use the latest 3DNUS to grab 11.2 (type in 11.2.0-35E, and make sure the right hardware model is checked). Copy the CIAs to a folder named "updates" on the SD card, and use SysUpdater to update. I would heavily advise backing your card up, formatting EmuNAND, and restoring at some point. I realize it's time-consuming, but it really is the best way to go. Gateway makes you enter an extra key combo without an EmuNAND. Besides, if you do that, you can update SysNAND to 11.6 for use with Luma, and still be able to use Gateway on 11.2 via the EmuNAND (which it will load automatically if it finds one).
Thank you. I will try!!
I can only get this to boot gw enand by disabling autoboot of emunand in luma options and holding down when powering on the console. How do I get this to autoboot into gw enand?
When autoboot emunand is enabled in the luma options, the L trigger and down has to held to boot into gw enand.
Any kind of auto boot enand in luma setting always boots the console into luma enand.
EmuNAND is not proprietary. It contains zero patches. All CFWs (including Gateway mode) that support EmuNAND boot the same ones. CFWs do all of their patching in memory. There is no such thing as Luma EmuNAND or GW EmuNAND. There is just EmuNAND. Luma's chainloader is always going to boot into Luma by default (one of the primary reasons I don't use it). You have to use a real chainloader like BootCTR9 or CBM9 to get a choice of what CFW (or other app) boots by default. If you need an example of this, look up my InScripted AIO (that iso site, "CFW Discussion" section). Just copy the configuration over from "B9S Configurations" that matches your hardware. It boots Luma by default, Gateway on B, and GM9 is on left (among other things, a full list is included in the "ReadMe.txt" file). However, if you go into GM9, hit home, and select the Scripts menu, under "Default Payloads & Hotkeys" you will see an option to change the default payload. You can make it Gateway (or anything else).
If you do that, you no longer need Gateway on B. So you might want to reassign that hotkey. Luma's already hotkeyed to A as well, so unless you have a use for the "persistence" feature, you could make B something else (A overrides it, so that you can get back to your default NAND, so, I'd recommend leaving Luma on A, because without the override, you would have to power down just to leave your non-default NAND). There's individual scripts under the "Change A Hotkey" option, or you can use the "Change All Hotkeys" script (you can just hit B for any hotkey you don't want to change). The only keys you can't change are select (so you can get to Luma's configuration menu), L (so you can access the non-default NAND in Luma), and R (that's to reset to the default hotkeys in case, say, you mess up and forget to assign one to GodMode9 -- I've tried to make it difficult to paint yourself into a corner).
Thanks that worked a treat!