Hacking GWemuNAND > Homebrew Browserhax Error

Osmosis

Accidents Happen. Don't be one of them.
OP
Member
Joined
Dec 20, 2014
Messages
823
Trophies
0
XP
367
Country
United States
Was using Luma 5.2 and when the guide instructs to hold SELECT for Luma3DS menu there's no "SysNAND is Updated" selection.

Then, when I save and reboot and hold "START" nothing happens. Double checked all copied files on SD and all of hourglass is there. Even renamed the Hourglass9.bin to start_Hourglass9.bin.
 

ihaveahax

Well-Known Member
Member
Joined
Apr 20, 2015
Messages
6,005
Trophies
2
XP
7,289
Country
United States
Was using Luma 5.2 and when the guide instructs to hold SELECT for Luma3DS menu there's no "SysNAND is Updated" selection.

Then, when I save and reboot and hold "START" nothing happens. Double checked all copied files on SD and all of hourglass is there. Even renamed the Hourglass9.bin to start_Hourglass9.bin.
why are you using 5.2? Plailect's guide is based on the latest version, which has "SysNAND is updated". also not really necessary unless you are using firmware.bin.

also if your sysnand is still 2.1, it won't boot. need to get into Hourglass9 or Decrypt9 somehow. does D9 work?
 

ihaveahax

Well-Known Member
Member
Joined
Apr 20, 2015
Messages
6,005
Trophies
2
XP
7,289
Country
United States
I have no idea who started this rumor but you can stop using 5.2 now since you're already at arm9loaderhax. try it with 5.5 with no firmware.bin and see if it works(after you restore sysnand keeping a9lh).
 

Osmosis

Accidents Happen. Don't be one of them.
OP
Member
Joined
Dec 20, 2014
Messages
823
Trophies
0
XP
367
Country
United States
Rodger. Will do...

::huggies::

Yup, that worked...

SysNAND Restore: SUCCESS!!

Hrm... after restoring sysNAND with the emuNAND_orirginal.bin (as the guide says to) it just black screens on reboot.

Put Luma 5.2 back on and put the firmware.bin in folder again?
 
Last edited by Osmosis,

Just3DS

Well-Known Member
Member
Joined
Jan 31, 2015
Messages
440
Trophies
0
XP
227
Country
Rodger. Will do...

::huggies::

Yup, that worked...

SysNAND Restore: SUCCESS!!

Hrm... after restoring sysNAND with the emuNAND_orirginal.bin (as the guide says to) it just black screens on reboot.

Put Luma 5.2 back on and put the firmware.bin in folder again?
You may also need to remove/rename "Nintendo 3DS" folder and put the one that was backed up along with original emuNAND. If you don't have it then just delete/rename "Nintendo 3DS" folder.
 

Osmosis

Accidents Happen. Don't be one of them.
OP
Member
Joined
Dec 20, 2014
Messages
823
Trophies
0
XP
367
Country
United States
Putting firmware.bin back into Luma folder booted it up.

I am now done with the Plailect Guide.

Think I might call it quits for tonight. At this point my System Settings is reading "Sys 11.0.0-33U"

So my sysNAND is now my emuNAND? But at this point, how do I get it to autoboot into GWemuNAND so I can use RedCart and such?

Already formatted 128GB mSD to FAT32 and copied all files, booted up and works.

So now for the fun part... GWemuNAND and installing everything.
 
Last edited by Osmosis,
General chit-chat
Help Users
  • No one is chatting at the moment.
    K3N1 @ K3N1: https://youtube.com/shorts/PArWUK0WyDQ?feature=share