Hacking Updated OFW to 7.0.1, now SXOS emunand no longer boots.

jereb · Mar 31, 2019

I updated my OFW to 7.0.1 today for online and now I simply can't get emunand to start. After the SXOS splash screen I get a black screen that lasts indefinitely. OFW works fine, and booting into CFW sysnand works fine. I made sure that I was on SXOS 2.6.1, then redownloaded it and added it to the SD card again to be extra sure that the file was correct. I've tried re-adding all my emunand files back to the SD card from a backup, formatting the SD card to FAT32 to see if that would work, checking the SD card itself with h2testw to make sure it's behaving correcltly, and even creating an entirely new emunand on another SD card. Nothing has worked so far.

I'm not sure what else to even try, other than restoring my old nand backup which seems like a hassle and might not even be necessary. Anyone know what's up?

Kafluke · Mar 31, 2019

Well for starters you no longer have a clean nand for online play. You booted CFW on your sysnand. Ban is highly likely. Secondly you should read this before you try any downgrading.

https://gbatemp.net/threads/psa-stop-downgrading-unless-you-know-what-youre-doing.531861/

As far as the black screen it seems like you may have some SD corruption. You may need to reformat your SD entirely and start over.

jereb · Mar 31, 2019

Kafluke said:
As far as the black screen it seems like you may have some SD corruption. You may need to reformat your SD entirely and start over.

jereb said:
I've tried... ...formatting the SD card to FAT32 to see if that would work, checking the SD card itself with h2testw to make sure it's behaving correcltly, and even creating an entirely new emunand on another SD card.

jereb · Apr 11, 2019

Does anyone else have ideas on what to try, or should I just wait and hope that TX is working on a fix? Looking around it seems like this black screen is a common issue with this update, but none of the things that have gotten it working for other people have worked for me.

luan43 · Apr 11, 2019

are you using the beta boot.dat? Fixed my black screen.

jereb · Apr 11, 2019

luan43 said:
are you using the beta boot.dat? Fixed my black screen.

Yeah, the 2.6.1 beta.

JJTapia19 · Apr 11, 2019

Try this.

JJTapia19 said:
After the sx boot screen wait a couple of seconds on the black screen and try pressing the power button once. Many users reported this workaround on their forums.if nothing works re create with emunand the files on sd option. Then update to 7.0.1 with exfat.

paulzheng · Apr 11, 2019

jereb said:
I updated my OFW to 7.0.1 today for online and now I simply can't get emunand to start. After the SXOS splash screen I get a black screen that lasts indefinitely. OFW works fine, and booting into CFW sysnand works fine. I made sure that I was on SXOS 2.6.1, then redownloaded it and added it to the SD card again to be extra sure that the file was correct. I've tried re-adding all my emunand files back to the SD card from a backup, formatting the SD card to FAT32 to see if that would work, checking the SD card itself with h2testw to make sure it's behaving correcltly, and even creating an entirely new emunand on another SD card. Nothing has worked so far.

I'm not sure what else to even try, other than restoring my old nand backup which seems like a hassle and might not even be necessary. Anyone know what's up?

it's a common issue with sxos's emunand. you have to holding power button 20secs until shutdown. press vol+ and rehack it again.
don't unplug dongle quickly.

RicardoGuedes32 · Apr 11, 2019

jereb said:
I updated my OFW to 7.0.1 today for online and now I simply can't get emunand to start. After the SXOS splash screen I get a black screen that lasts indefinitely. OFW works fine, and booting into CFW sysnand works fine. I made sure that I was on SXOS 2.6.1, then redownloaded it and added it to the SD card again to be extra sure that the file was correct. I've tried re-adding all my emunand files back to the SD card from a backup, formatting the SD card to FAT32 to see if that would work, checking the SD card itself with h2testw to make sure it's behaving correcltly, and even creating an entirely new emunand on another SD card. Nothing has worked so far.

I have exact same issue. I come from 5.1 OFW and the emunand worked nice on there then I had to update because I want to play new games that will come like FF12 and DQXI.
I'm 2 days trying fix this and tried several fix in posts like you did and nothing worked! I'm thinking in continue without emunand, someone can say if I can keep my system without an emunand? I'm really tired.

MasterJ360 · Apr 11, 2019

My guess is that the problem is burnt fuses. The emunand was on a lower firmware/with less fuses burned, however updating the system to 7.X through Nintendo causes more burnt fuses resulting a mismatch count towards emunand. Your may have to recreate Emunand on 7.X firmware to use it again. Only reason my emunand was still accessible is b/c I updated it with ChoiDujourNX 6.2 to 7.0.1 including my sysnand without burning fuses. FW6.2 is 8 burnt fuses FW7.0.1 is 9 burnt fuses. Since I dislike Auto RCM i updated to 7.0.1 just to dump its keys and downgraded both emunand/sysnand back to 6.2

stick267 · Apr 11, 2019

MasterJ360 said:
My guess is that the problem is burnt fuses. The emunand was on a lower firmware/with less fuses burned, however updating the system to 7.X through Nintendo causes more burnt fuses resulting a mismatch count towards emunand. Your may have to recreate Emunand on 7.X firmware to use it again. Only reason my emunand was still accessible is b/c I updated it with ChoiDujourNX 6.2 to 7.0.1 including my sysnand without burning fuses. FW6.2 is 8 burnt fuses FW7.0.1 is 9 burnt fuses. Since I dislike Auto RCM i updated to 7.0.1 just to dump its keys and downgraded both emunand/sysnand back to 6.2

Fuses don't matter to emunand as far as I know.

JJTapia19 · Apr 11, 2019

RicardoGuedes32 said:
I have exact same issue. I come from 5.1 OFW and the emunand worked nice on there then I had to update because I want to play new games that will come like FF12 and DQXI.
I'm 2 days trying fix this and tried several fix in posts like you did and nothing worked! I'm thinking in continue without emunand, someone can say if I can keep my system without an emunand? I'm really tired.

Try what I posted above. It has really worked to a lot of people.

MasterJ360 · Apr 11, 2019

stick267 said:
Fuses don't matter to emunand as far as I know.

Its bizarre to update a sysnand and the emunand just magically stops working thats why I can't think of another reason aside from mismatch fuses. Having said that the right way of doing things is to update emunand with choidujournx to the latest firm. The sd card is not the problem since hes able to boot into cfw sysnand.

RicardoGuedes32 · Apr 11, 2019

MasterJ360 said:
Its bizarre to update a sysnand and the emunand just magically stops working thats why I can't think of another reason aside from mismatch fuses. Having said that the right way of doing things is to update emunand with choidujournx to the latest firm. The sd card is not the problem since hes able to boot into cfw sysnand.

Well, the first thing I did was what several tutorials says: to update the emunand with Choidujournx but the result was the same, black screen!
When I run out of solutions, tested my sd in everyway, then I updated the sysnand! Now my only solution is continue without the emunand!

MasterJ360 · Apr 11, 2019

RicardoGuedes32 said:
Well, the first thing I did was what several tutorials says: to update the emunand with Choidujournx but the result was the same, black screen!
When I run out of solutions, tested my sd in everyway, then I updated the sysnand! Now my only solution is continue without the emunand!

black screen from Choidujournx is Auto RCM you need to use TegraRcmGUI app from your PC with a cfw plugin in order to boot into cfw mode.

JJTapia19 · Apr 11, 2019

It's a problem with the latest sx os beta 2.6.1 and emunand hidden partition on 7.0.x. I posted a workaround here: After the sx boot screen wait a couple of seconds on the black screen and try pressing the power button once. Many users reported this workaround on their forums.if nothing works re create with emunand the files on sd option. Then update to 7.0.1 with exfat.

MrKinopio · Apr 11, 2019

I had the same problem. I use my PC for the payload and usually boot into RCM by plugging in the USB cable. But then I get a blackscreen when trying to boot emuNAND. It works just fine by simply entering RCM without the cable plugged in. Hope this might help

jereb · Apr 11, 2019

JJTapia19 said:
It's a problem with the latest sx os beta 2.6.1 and emunand hidden partition on 7.0.x. I posted a workaround here: After the sx boot screen wait a couple of seconds on the black screen and try pressing the power button once. Many users reported this workaround on their forums.if nothing works re create with emunand the files on sd option. Then update to 7.0.1 with exfat.

I just now tried pressing the power button after the black screen starts, unfortunately it didn't do anything. And I have already tried recreating the emunand with files on SD. Even with a brand new emunand on a FAT32-formatted SD card it won't start.

JJTapia19 · Apr 11, 2019

jereb said:
I just now tried pressing the power button after the black screen starts, unfortunately it didn't do anything. And I have already tried recreating the emunand with files on SD. Even with a brand new emunand on a FAT32-formatted SD card it won't start.

Sad to hear it didn't worked. With the files on sd emunand could you try booting it a couple of times? I personally had low boot rate like 1 out of 5. If it runs a clean fat32 format should fix the boot rate issue.

jereb · Apr 12, 2019

JJTapia19 said:
Sad to hear it didn't worked. With the files on sd emunand could you try booting it a couple of times? I personally had low boot rate like 1 out of 5. If it runs a clean fat32 format should fix the boot rate issue.

I tried it like 6 times earlier and still couldn't get it to boot.

Hacking Updated OFW to 7.0.1, now SXOS emunand no longer boots.

Active Member

Well-Known Member

Active Member

Active Member

Well-Known Member

Active Member

I fight for my friends.

Well-Known Member

New Member

Well-Known Member

Well-Known Member

I fight for my friends.

Well-Known Member

New Member

Well-Known Member

I fight for my friends.

New Member

Active Member

I fight for my friends.

Active Member

Similar threads

Popular threads in this forum