Hacking Moved Emunand from NAND to SD... Now it boots to a black screen

Keylogger

Well-Known Member
Member
Joined
May 3, 2006
Messages
2,639
Trophies
1
Age
34
Website
Visit site
XP
6,634
Country
France
atkzdZx.png

Here you go ^^
could you screenshot that in an hex editor please? :P
 
  • Like
Reactions: thaikhoa

johnsnow

Active Member
Newcomer
Joined
Oct 7, 2018
Messages
44
Trophies
0
Age
48
XP
145
Country
Australia
What I need to edit please?

https://ibb.co/eXEFPf
eXEFPf

0x180000 is probably not good starting point, as this is for FW 1.0. Are you running FW 1.0?
You are probably around FW 5.0 ?

Table is here: https://switchbrew.org/wiki/Cryptosystem
Look at Table of used keyblobs. 5.0.0-5.1.0 uses keyblob_nr 5.

So goto 0x180800 [= 0x180000 + (keyblob_nr - 1) * 0x200]
Copy 0x180800..0x1808AF and overwrite at 0x450

Save boot0.bin

Now try boot emunand.

If you are FW 6.0 try keyblob_nr = 6
 
  • Like
Reactions: DJravingMonkey

rsn8887

Well-Known Member
Member
Joined
Oct 8, 2015
Messages
956
Trophies
1
Age
46
Website
www.patreon.com
XP
3,619
Country
United States
Same problem, no success here. I have never used Emunand before. I just created it with SX Pro 2.3 on SD Card.

Emunand was created successfully but just boots to black screen. I renamed „Nintendo“ to „Emutendo“ but it shouldn’t matter for the boot process.

If I disable Emunand everything boots fine.

What I tried:
- straightforward create emunand on SD and boot into it -> boots to black screen
- copy boot0.bin from a former sxos nand backup (from sxos/backup to sxos/emunand/boot0.bin) -> still boots to black screen)
- copy and rename BOOT0 from a hekate nand backup to sxos/emunand/boot0.bin -> still black screen

I am using 6.1.0, and SX OS 2.3 Beta.
 
Last edited by rsn8887,

DJravingMonkey

Well-Known Member
OP
Newcomer
Joined
Oct 11, 2009
Messages
45
Trophies
0
Age
39
XP
478
Country
Germany
Same problem, no success here. I have never used Emunand before. I just created it with SX Pro 2.3 on SD Card.

Emunand was created successfully but just boots to black screen. I renamed „Nintendo“ to „Emutendo“ but it shouldn’t matter for the boot process.

If I disable Emunand everything boots fine.

What I tried:
- straightforward create emunand on SD and boot into it -> boots to black screen
- copy boot0.bin from a former sxos nand backup (from sxos/backup to sxos/emunand/boot0.bin) -> still boots to black screen)
- copy and rename BOOT0 from a hekate nand backup to sxos/emunand/boot0.bin -> still black screen

I am using 6.1.0, and SX OS 2.3 Beta.
Exactly the same here... My sysnand is on 6.1 and everything is fine. My emunand was on 6.0 maybe this is the problem? Does sxos mess up the bootloaders and now uses a 6.1 version for a 6.0 emunand perhaps?
 

Hernie

Well-Known Member
Member
Joined
May 11, 2018
Messages
121
Trophies
0
Age
46
XP
848
Country
United States
I had that black screen bullshit, too. I did what @javilobo8 said he did. After creating emunand, I then made a nand backup. I put the Sdcard into my computer deleted the sxos\emunand folder. Then renamed the sxos\backup folder to sxos\emunand. I made a folder called "emutendo" and copied all the contents of the "Nintendo" folder into "emutendo".

Fired it up and it worked like a charm. I then ran choidujourNX and updated to 6.1.0.
 
  • Like
Reactions: Keylogger

Keylogger

Well-Known Member
Member
Joined
May 3, 2006
Messages
2,639
Trophies
1
Age
34
Website
Visit site
XP
6,634
Country
France
I have 6.1 NAND and 6.0 emunand with lot of saves on my emunand.
If I create a new 6.1 emunand to SD card and rename my emunand's nintendo folder to emutendo, will I keep my saves?

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

Same problem, no success here. I have never used Emunand before. I just created it with SX Pro 2.3 on SD Card.

Emunand was created successfully but just boots to black screen. I renamed „Nintendo“ to „Emutendo“ but it shouldn’t matter for the boot process.

If I disable Emunand everything boots fine.

What I tried:
- straightforward create emunand on SD and boot into it -> boots to black screen
- copy boot0.bin from a former sxos nand backup (from sxos/backup to sxos/emunand/boot0.bin) -> still boots to black screen)
- copy and rename BOOT0 from a hekate nand backup to sxos/emunand/boot0.bin -> still black screen

I am using 6.1.0, and SX OS 2.3 Beta.
Did you fixed your problem?
 

jaysea

Well-Known Member
Member
Joined
Aug 17, 2009
Messages
279
Trophies
1
Age
46
XP
1,189
Country
Netherlands
I just made a new backup of my boot0/boot1 and replace them to :\sxos\emunand folder but it didn't work
Creatie a boot0 and boot1 backup with hekate and rename them boot0.bin and boot1.bin.
It seems that sx os 2.3 is not making correct boot0 and boot1 backups (in emunand aswell as backup option)
 

rsn8887

Well-Known Member
Member
Joined
Oct 8, 2015
Messages
956
Trophies
1
Age
46
Website
www.patreon.com
XP
3,619
Country
United States
I tried that too and it didn’t work for me either. Windiff reveals that boot0.bin and boot1.bin created by SX during Emunand setup are bit by bit identical to boot0 and boot1 from Hekate backup.
 

jaysea

Well-Known Member
Member
Joined
Aug 17, 2009
Messages
279
Trophies
1
Age
46
XP
1,189
Country
Netherlands
I tried that too and it didn’t work for me either. Windiff reveals that boot0.bin and boot1.bin created by SX during Emunand setup are bit by bit identical to boot0 and boot1 from Hekate backup.
In my case this cannot be true since that was the only thing I have changed to make the emunand work.
 

jaysea

Well-Known Member
Member
Joined
Aug 17, 2009
Messages
279
Trophies
1
Age
46
XP
1,189
Country
Netherlands
I

Ive Try the same - with sx os boot dump not work ....With hekate boot0/1 the Same :/
I don’t know if it matters, but I renamed the BOOT0 to boot0.bin from uppercase to lowercase. Furthermore I do not have autorcm enabled on any of the boot bin files
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    AncientBoi @ AncientBoi: 🫂 +1