Hacking Upgraded O3DS but can't run any CFW

[yelever74]

So, it seems my upgrade is messed up some how as I can now but into emunand using luma but trying to but into luma sysnand I get a black screen. Also have to have to firmware.bin in the luma directory.

 

[EmperorOfCanada]

So, it seems my upgrade is messed up some how as I can now but into emunand using luma but trying to but into luma sysnand I get a black screen. Also have to have to firmware.bin in the luma directory.

any chance you can post a pic of your luma settings? also, you are using menuhax? how do you have that set up currently?

 

[yelever74]

Menuhax is setup to to press L. I can boot emunand but can't cfw sysnand. Tried pasta and minipasta aswell.

 

[Zan']

Menuhax is setup to to press L. I can boot emunand but can't cfw sysnand. Tried pasta and minipasta aswell.

Do you even have A9LH installed?
Because from what I've read it surely doesn't look like it.

 

[masenko]

i see from your pic you're using luma dev version, try the regular version

 

[EmperorOfCanada]

Do you even have A9LH installed?
Because from what I've read it surely doesn't look like it.

... also Dev luma?.

@yelever74 Are you trying to get on A9LH or do you already have? (Im assuming you dont)

Remove all LUMA folders and files from your SD card, redownload LUMA NON-DEV version, then then it loads for the first time, select ONLY "show current nand in system settings"

 

[yelever74]

OK no dev version and redownlaoded to make sure. It boots emunand fine but not cfw sysnand still whcih kinda sucks as wanting to install gba games to work on emunand. I still need the firmware.bin in the luma folder to boot into emunand though.

 

[HenryLeonheart]

@yelever74 Do you have A9LH installed or not? Because you can't load CFW SysNAND without it being installed. Follow Plailect's guide here: https://github.com/Plailect/Guide/wiki
If your emunand is working correctly, make sure everything is just as Part 3 says and then start from Part 4.

 

[TheLegendofMario]

Try the upgrade again, and try RedNand please try my advice I know what I'm talking about

 

[yelever74]

The upgrade won't work as I can't access cfw sysnand

 

[Zan']

The upgrade won't work as I can't access cfw sysnand

For me pretty much none of this makes sense.
You said something about using menuhax.
You say you boot into emuNAND via menuhax, which would require sysNAND to be working because otherwise menuhax wouldn't load at all.

EmuNAND booting but SysNAND not booting would imply you installed A9LH.
In that case you can't use Menuhax.
You would launch EmuNAND via A9LH or launch updated SysNAND via A9LH.

 

[yelever74]

Normal sysnand boots but not cfw sysnand like pastcfw or minipasta. Not installed A9lh. To install anything on sysnand an entry point would be such as pastacfw or minipasta which just gives me a black screen from hbl.

 

[TheLegendofMario]

EDIT didn't see post above, using crappy android phone.y

--------------------- MERGED ---------------------------

Did you makke a sysnand Backup before updating?

 

[yelever74]

I think so but if I did it's on friend's laptop.

 

[TheLegendofMario]

I assume that you used a homebrew updater instead of official, am I correct? if so which one?

 

[The Real Jdbye]

@yelever74 Do you have A9LH installed or not? Because you can't load CFW SysNAND without it being installed. Follow Plailect's guide here: https://github.com/Plailect/Guide/wiki
If your emunand is working correctly, make sure everything is just as Part 3 says and then start from Part 4.

You don't need A9LH to use sysNAND CFW... You just can't update sysNAND to 9.3+ without A9LH.

 

[Eruandou]

I had the same exact problem. It was caused by leftover files that gateway's downgrade left. Hope you came with a solution. In case you haven't, here what worked for me:

-Download GODMODE9 and run it from homebrew launcher.
-In GODMODE9 select "EMUNAND CTRNAND" and go to the following route:"title/00040138/00000002/content".

- Here you'll find some files (.tmd and .app) and a "cmd" folder. There should only be 1 .tmd and 1.app. Delete the cmd and app with the lowest values ( ex. you have 00000001.tmd and 000000002.tmd, delete the 000000001.tmd file), thus leaving ONLY one .app and one .tmd (with the highest values).
-Once you have one of each, enter the CMD subfolder. There'll be more than 1 .cmd files. Delete of all them EXCEPT the one with the highest value (follow the same logic from the step before this one)

After you have One .tmp, one .app, and, in the cmd subfolder, one .cmd file (always highest value, can't stress this enough) you should be safe to press start and reboot.
Everything should boot normally after that.