Yeah, I think it might be that it is formatted as 64gb fat32 and windows wouldn't usually even format fat32 over 32gb, the switch picks it up and so does my Samsung Galaxy, but I wanted to format it as exFAT. Maybe there is an android app for that.
Yeah, I think it might be that it is formatted as 64gb fat32 and windows wouldn't usually even format fat32 over 32gb, the switch picks it up and so does my Samsung Galaxy, but I wanted to format it as exFAT. Maybe there is an android app for that.
Like it has been said before... you are getting a black screen because auto rcm is in effect..
Auto rcm is automatically applied when you use choidujour... this is to prevent you booting into normal bootloader and burning fuses..
Each system version 2.0-4.1.0-5.1.0 have different fuses counts ,, 2-4-5-6 etc
If for instance you update to 5.1.0 with no fuse method,auto rcm weill prevent you loading the stock bootloader, and will require you run a alternative..
hekate / cfw etc... When you load with hekate or another fuse bypass loader. you dont burn fuses.
for instance if you update from 4.1.0 say with 4 fuses as a example with the no fuse guide to say 5.1.0. means you stay on 4 fuses burned..
Now If you remove auto rcm and say try to boot into your 5.1.0 you will burn a fuse,
so say for example you now have 5 fuses burned. thats fine if you wish to stay on 5.1.0....
the issue is when you want to downgrade or go back to the system version you was on example 4.1.0
Because you booted into 5.1.0 without bypassing fuse check with autorcm and Alternative bootloader not used you burn fuse/s if you now try to load any other system version that requires less fuses burnt example 4.1.0. the console i think kernel, will panic to that the fuse count does not match the system version and will freeze/crash/ simply not load...
So If you wish to update system version and be able to downgrade system version use auto rcm..
If you do not care about returning to earlier system versions then you do not have to use auto rcm...
As for these posts /comments
I think you stand alone here.. and i do not agree...
Granted autorcm is shall we say a little dangerous in regard to it bricks your boot file.. but can be restored with ease.. Id say your posts are dangerous and are upon a danger to yourself with what you have been posting.
Remember kiddies boys and girls / make a full backup before you play with your toys..
Backup here >>https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/
Auto rcm is automatically applied when you use choidujour... this is to prevent you booting into normal bootloader and burning fuses..
Each system version 2.0-4.1.0-5.1.0 have different fuses counts ,, 2-4-5-6 etc
If for instance you update to 5.1.0 with no fuse method,auto rcm weill prevent you loading the stock bootloader, and will require you run a alternative..
hekate / cfw etc... When you load with hekate or another fuse bypass loader. you dont burn fuses.
for instance if you update from 4.1.0 say with 4 fuses as a example with the no fuse guide to say 5.1.0. means you stay on 4 fuses burned..
Now If you remove auto rcm and say try to boot into your 5.1.0 you will burn a fuse,
so say for example you now have 5 fuses burned. thats fine if you wish to stay on 5.1.0....
the issue is when you want to downgrade or go back to the system version you was on example 4.1.0
Because you booted into 5.1.0 without bypassing fuse check with autorcm and Alternative bootloader not used you burn fuse/s if you now try to load any other system version that requires less fuses burnt example 4.1.0. the console i think kernel, will panic to that the fuse count does not match the system version and will freeze/crash/ simply not load...
So If you wish to update system version and be able to downgrade system version use auto rcm..
If you do not care about returning to earlier system versions then you do not have to use auto rcm...
As for these posts /comments
I think you stand alone here.. and i do not agree...
Granted autorcm is shall we say a little dangerous in regard to it bricks your boot file.. but can be restored with ease.. Id say your posts are dangerous and are upon a danger to yourself with what you have been posting.
Remember kiddies boys and girls / make a full backup before you play with your toys..
Backup here >>https://gbatemp.net/threads/backup-...-your-biskeys-tseckeys-keys-txt-guide.513386/
- Joined
- Jun 24, 2007
- Messages
- 12,005
- Trophies
- 3
- Location
- In the Murderbox!
- Website
- www.twitch.tv
- XP
- 16,136
- Country
your windows system can detect a whole range of formats.. and fat32 it should def detect..
Please try another method of reading on pc. different usb slot/card reader etc.. or even another pc to see if it is detected. i feel its strange its detected on phone and switch but not pc...
All tho if sd card is corrupt you may have issues... You say your switch gave you card errors after you update to 5.1.0 did you install the exfat option ? Try to backup sd card in another machine or by some method, or if you dont really care for the contents reformat the sd card if is detected as storage device even if it does not display partition.
Last edited by Canna,
Thanks, Yes I did choose to install 5.1.0 with exfat support, the card at the time of updating was fat32 and upon first 5.1.0 boot I recieved a memory card error.
I tried 2 different card readers and 3 usb slots on my Windows 10 machine and no dice, easeUS doesn't detect it either.
I will see if it's detected elsewhere from the pc but its strange how my phone and switch have no issue with it.
if you do not care about the contents use your phone and or switch to refomrat the card.. i feel the issue is with pc somewere wether its the pins or connections in adapter the usb reader or some sort of bug with windows. if the reader is detected in device manager and it shows a drive letter, then the reader is ok but the sd card is not making contact with the reader , or is corrupt in someway.. if ease us cant detect it then its not windows or software...
like i said format it in your phone or switch then plug into pc should be detected if not its the reader like i said. hope this helps .. try another sd card with same reader maybe first ,,
you restarted your pc right ?
i find its those damn micro sd to sd card adaptors sometimes..
Last edited by Canna,
Agree with @Canna. Also I have found with win10 if it detects a problem with a removable drive (for instance it wasn’t ejected properly) win10 will give you one chance to scan and repair it. If you miss that dialog you are hosed on that machine and must use another machine to scan and repair the drive. I am sure there are low level utilities or methods to get around the problem but to the average user the drive seems to be dead.
must definitely be a win10 issue then cuz i'm on win 7 and never had any issues with sd card readers.
I run into it occasionally with thumb drives if I pull them out of my old WDTV without ejecting. Fortunately I have a second box to quickly fix it and never had that problem with win7. Thanks Windowz.
I dont know what the issue was, I formatted the micro sd with the phone and placed the files back on, switch had no issues reading it but again pc was a no go.
As recommended I formatted from the Switch and bingo, drive shows in windows again.
Thanks to everybody who contributed, I have flashed or hacked just about everything worth hacking in my time but jumped in feet first here due to being too busy mostly, I needed to show the console/scene a little more respect.
Thanks again.
As recommended I formatted from the Switch and bingo, drive shows in windows again.
Thanks to everybody who contributed, I have flashed or hacked just about everything worth hacking in my time but jumped in feet first here due to being too busy mostly, I needed to show the console/scene a little more respect.
Thanks again.
>He doesn't have a modchip installed so he doesn't have to worry about fuses anymore
*sips tea* Ah, your fuses burned and you won't have that shitty warmboot exploit? That sucks... :v)
Similar threads
- Solved
- No one is chatting at the moment.
