No SD logo

[FAKEdemicBioPYSCHONANOWAR]

Trying to boot hekate and im getting "

no sd logo"

I first formatted the sd with guiformat to fat32 with default cluster. Then it still gave me the error. So I then reput my sd files on it. Then hekate booted somehow.
Then I did the emunand part with partition based emunand. and I rebooted then again..."NO SD" logo...

What is going on to behave this way?

 

[Stryd]

Trying to boot hekate and im getting "View attachment 294147no sd logo"

I first formatted the sd with guiformat to fat32 with default cluster. Then it still gave me the error. So I then reput my sd files on it. Then hekate booted somehow.
Then I did the emunand part with partition based emunand. and I rebooted then again..."NO SD" logo...

What is going on to behave this way?

You should check if your SD card is being recognized properly.

Try to plug it into your pc and use H2Testw to check if it's working as intended.

 

[FAKEdemicBioPYSCHONANOWAR]

My seller is saying there might not be support
https://github.com/Spacecraft-NX/sdloader/pull/2/commits
Eventhough he has also tried 1TB sandisk without problem he says...
32 GB SD boots each time without fail and the 1TB sandisk that is giving me trouble in my oled, boots without fail in my erista switch.
the 1TB i got to boot once succesfully out of 10 times or so on this mariko oled.
He also claims hekate has a bug, and you HAVE to set 1x12 GB for size 2x29 wont work

Kinda at a loss here......

 

[Stryd]

My seller is saying there might not be support
https://github.com/Spacecraft-NX/sdloader/pull/2/commits
Eventhough he has also tried 1TB sandisk without problem he says...
32 GB SD boots each time without fail and the 1TB sandisk that is giving me trouble in my oled, boots without fail in my erista switch.
the 1TB i got to boot once succesfully out of 10 times or so on this mariko oled.
He also claims hekate has a bug, and you HAVE to set 1x12 GB for size 2x29 wont work

Kinda at a loss here......

When i created emuNAND on OLED i made it as low as 4gb, so i don't think the emuNAND size is the problem here.
I have a 128 gb microSD at the moment, and all works fine.

Not really sure at this point, but if it works for him, should be working for you as well

 

[laramie]

My seller is saying there might not be support
https://github.com/Spacecraft-NX/sdloader/pull/2/commits
Eventhough he has also tried 1TB sandisk without problem he says...
32 GB SD boots each time without fail and the 1TB sandisk that is giving me trouble in my oled, boots without fail in my erista switch.
the 1TB i got to boot once succesfully out of 10 times or so on this mariko oled.
He also claims hekate has a bug, and you HAVE to set 1x12 GB for size 2x29 wont work

Kinda at a loss here......

Maybe check the sd card reader and make sure it's on all the way and maybe clean the sd card reader

 

[FAKEdemicBioPYSCHONANOWAR]

Maybe check the sd card reader and make sure it's on all the way and maybe clean the sd card reader

SD card is reading 100% fine in my other switch and in PC also.
And other sd card is reading fine in my switch that experiences the issue...
Clean the SD card reader from that switch? it's squeeky clean.. brand new..

 

[laramie]

SD card is reading 100% fine in my other switch and in PC also.
And other sd card is reading fine in my switch that experiences the issue...
Clean the SD card reader from that switch? it's squeeky clean.. brand new..

Maybe see if the reader is seated all the way? It may be a new switch but if someone didn't put a clean sd card in it, it might not read......

 

[FAKEdemicBioPYSCHONANOWAR]

Maybe see if the reader is seated all the way? It may be a new switch but if someone didn't put a clean sd card in it, it might not read......

I bought the 1TB sandisk seperately and I reseated it about 10 times now with only succeeding to boot once... I thought it was connection at first too, but now im not too sure since I always make sure it is properly seated as far as I can tell...

But it booted ONCE, so that tells me it should be possible?!!
I suspect a firmware issue with spacecraft somehow.

 

[laramie]

I bought the 1TB sandisk seperately and I reseated it about 10 times now with only succeeding to boot once... I thought it was connection at first too, but now im not too sure since I always make sure it is properly seated as far as I can tell...

But it booted ONCE, so that tells me it should be possible?!!
I suspect a firmware issue with spacecraft somehow.

Nah, it's either a borked sd card or the reader is borked/dirty/not seated to the motherboard. I don't think it's the sd card since it booted once.

 

[FAKEdemicBioPYSCHONANOWAR]

Nah, it's either a borked sd card or the reader is borked/dirty/not seated to the motherboard. I don't think it's the sd card since it booted once.

But if it's the sd card reader, then why does my samsung 32 GB boot EACH time correctly on it lawl....
and if it's a borked sd card, then why does the 1TB san disk boot EACH time correctly on my other switch....

Completely at a loss here...

 

[laramie]

But if it's the sd card reader, then why does my samsung 32 GB boot EACH time correctly on it lawl....
and if it's a borked sd card, then why does the 1TB san disk boot EACH time correctly on my other switch....

Completely at a loss here...

If that's the case then it's 100% a dirty/broken reader. ez

 

[kylum]

@Mena has already stated that there is a known issue with compatibility with some SD cards. This may be the problem you are experiencing. There is a firmware in this thread here that can potentially help with your issue but Mena stated that it also causes slower glitching so…. It’s being worked on so maybe we will see an another update in the near future. Use the card that works until then or try a different branded or tier of card.

 

[FAKEdemicBioPYSCHONANOWAR]

If that's the case then it's 100% a dirty/broken reader. ez

If I use my 32 GB to boot into hekate, remove it. put 1TB in. then run the microcard sd info i do get all the info, then run benchmark and it is reading and writing. which would suggest the reader is fine......

 

[laramie]

If I use my 32 GB to boot into hekate, remove it. put 1TB in. then run the microcard sd info i do get all the info, then run benchmark and it is reading and writing. which would suggest the reader is fine......

what @kylum said, also booting from one sd card then swapping is in fact reseating the sd card so my thoughts are the same, either a weird bug like @kylum said or reader. Literally from a realistic standpoint it's one of two things, hardware or software and the only difference between your test is the console's reader. So if it's working on one but not the other you follow the points of failure back. First software, then sd card, then sd card reader, cable, and finally the motherboard.

 

[FAKEdemicBioPYSCHONANOWAR]

what @kylum said, also booting from one sd card then swapping is in fact reseating the sd card so my thoughts are the same, either a weird bug like @kylum said or reader. Literally from a realistic standpoint it's one of two things, hardware or software and the only difference between your test is the console's reader. So if it's working on one but not the other you follow the points of failure back. First software, then sd card, then sd card reader, cable, and finally the motherboard.

looooooooooooooooooooooooooool.... omfg ifI put the 32 GB sd first boot into hekate and then remove it, and THEN put the 1TB i can choose CFW and bootup the switch I see HOS home menu now.... I mean... if I keep the switch charged... this ain't super bad but..... Im doubting the overal stability of this way......

So i have a workaround way now of booting into my switch but......

 

[kylum]

looooooooooooooooooooooooooool.... omfg ifI put the 32 GB sd first boot into hekate and then remove it, and THEN put the 1TB i can choose CFW and bootup the switch I see HOS home menu now.... I mean... if I keep the switch charged... this ain't super bad but..... Im doubting the overal stability of this way......

So i have a workaround way now of booting into my switch but......

I’m about 80% sure it’s related to the modchip firmware. Your workaround proves that it is! Hopefully, we will see another fix from @Mena soon! The downside is you will have to find a way to initially flash the OLED chip with a programmer first as HWFLY screwed us on the USB. But at least it’s fixable on the OLED thanks to Mena.

 

[FAKEdemicBioPYSCHONANOWAR]

I’m about 80% sure it’s related to the modchip firmware. Your workaround proves that it is! Hopefully, we will see another fix from @Mena soon! The downside is you will have to find a way to initially flash the OLED chip with a programmer first as HWFLY screwed us on the USB. But at least it’s fixable on the OLED thanks to Mena.

"there is a firmware in this thread here that can potentially help with your issue but Mena stated that it also causes slower glitching so"
I don't see any firmware in that thread? Also what do you mean with slower glitching?
So is using this workaround safe... in the meantime or should I stop using it or even send my SD card back...?

 

[kylum]

"there is a firmware in this thread here that can potentially help with your issue but Mena stated that it also causes slower glitching so"
I don't see any firmware in that thread? Also what do you mean with slower glitching?
So is using this workaround safe... in the meantime or should I stop using it or even send my SD card back...?

It’s at the bottom of the OP. The first post. Not sure about the slow glitching, just letting you know what was stated. I would believe your work around would be ok, other than prematurely wearing out the SD slot. If you can leave your switch in sleep and docked when not in use vs powering it down you should be good.

 

[kylum]

WTF… quit with porn already!! Modz!!!!

 

[FAKEdemicBioPYSCHONANOWAR]

It’s at the bottom of the OP. The first post. Not sure about the slow glitching, just letting you know what was stated. I would believe your work around would be ok, other than prematurely wearing out the SD slot. If you can leave your switch in sleep and docked when not in use vs powering it down you should be good.

This "firmware_oled_chip_only.bin" is where you need to flash your modchip with? Or place in root of sd?