Homebrew LocalFriendCodeSeed_B problem

[JhonSmith]

So i just tried to unban my 3DS with a localseed and this hapend.
Ican´t turn on my console now.

 

[Dracari]

So i just tried to unban my 3DS with a localseed and this hapend.
Ican´t turn on my console now.

Probably poor timing but GM9 doesnt have the impact to Corrupt your mSD/SD, you could also have a fake card, test it with H2WTest your 3DS isnt bricked (well it maybe If what was copied , had already by that point Corrupted.) if you have a Spare SD/mSD, put a simple copy of luma on there as teh only boot.firm and see if it boots. if it does your fine

if your SD did corrupt and have no chance to recover (likely the FAT Table is corrupt and not the actual content,) and you have no backup, then you learned a hard lesson to make Regular backups.

 

[Giodude]

Not sure how to recover the sd card, but the console should boot if you put boot.firm on the ctrnand.

 

[JhonSmith]

Not sure how to recover the sd card, but the console should boot if you put boot.firm on the ctrnand.

Not the case...

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

I canñt acces to recovery menu without the sd

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

Now my sd look like these

 

[Dracari]

Not the case...

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

I canñt acces to recovery menu without the sd

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

Now my sd look like these

well i'd still try atleast to copy off your nand backup, but form looks of thinsg it was indeed corrupted or something began to overwrite it, copy what you can and do an SD Test with H2WTest this will tell you if you got a fake or faulty card.

there is some unknown your not telling us , you say the only thing you did was put a LFCS_B on the SD and booted GodMode9 to copy. before this did you Add anything else to this SD? did you downloading anything else to it before hand, did you make a backup before overwriting? how long have you had teh sd card? do you know how old teh build of GM9 your using? (despite i dont think any of the B9S era versions have yet to have a Critical flaw/bug such as corrupting an SD Card)
other can help you out once we have this info as you likely hit just poor timing, RNGesus just spat in yer eye on poor timing for the card to give out. you have a fake and a Backup was the last thing to push it over teh edge of its Real capacity and the sd got overridden. (given i haveto get scoot scootin in about 30 mins for a doctor appointment an di have limited data i might not be able to respond for any help till later in day. Doc just Loves taking his sweet arse time[i've seriously had a 9AM appointment before and not get home till almost 7 at night.)

 

[Majickhat55]

I've seen this happen more than once and it's always a faulty/corrupted SD card like @Dracari said it just seems like bad timing. Correlation doesn't equal causation. What happens is the console fails to read the card (likely because of bad sectors) and writes gibberish to the partition to complete the process. This can happen in the case of the aforementioned or when say, you remove the SD card while it's being written to, failing to eject it properly or using a bad adapter.

 

[JhonSmith]

A. No, i don´t change anything before the lfcs_b.
B. I have a Nand Backup.
C. I have the card since september of 2016.
D. i belive since boostrap9 came.

 

[Dracari]

A. No, i don´t change anything before the lfcs_b.
B. I have a Nand Backup.
C. I have the card since september of 2016.
D. i belive since boostrap9 came.

OK that at least means you have a valid backup that wont Brick you should you need to restore, has the SD been in heavy Use (alot of Writing(freeshop, FTPserv, SD Management) did you get it online from something like eBay/Amazon (a 3rd party seller not a verified by Amazon as it can happen but rarely from them) have you used it frequently to copy data on/off to via a USB SD Adapter (regardless if this a microSD or full SD form-factor plays no role in when flash memory just cant take it and bites the dust)

if you got your SD from an online source not direct from the manufacture,(or thru amazon but a non "Fulfilled by Amazon") proper local store that isn't some drugstore/"Ma 'n Pa" store higher chances you got a Fake SD and it started to overwrite itself. this makes me think more so w/ the second screenshot as not everything was restored (you can count your "Nintendo 3DS" Folder as a total write-off as there's no way to be certain even if restored digital signatures are intact or files themselves are not corrupt. (sorry but more than likely your saves are Toast.)

GM9/your 3DS isn't at full fault. as @Majickhat55 stated that at the time of reading it couldn't read anything properly due to a Corrupted (in this case of Fat32) FAT Table or full on partition/FS and it has-to to complete the process write garbage back. this garbage write w/ a corrupted fs/partition can even endup writing this gibberish as the FAT (think of it like a big File index but thats over simplifying things and a discussion for another time) causing what you see in the first Screenshot.. If it had written the garbage to the partition Table you'd just get back in windows "This drive needs to be formatted" (as to windows any unknown/unsupported Filesystem/partition scheme gets seen as a unformatted (unknown File system) or uninitialized Disk (unknown partition scheme) and the 3DS in all aspects wouldn't be recognized as i believe the 3DS only supports Fat32.

please check your SD with this: https://3ds.guide/h2testw-(windows).html this wont be the 100% sure fire answer to your problem as it could just be bad timing (incorrect handling of the SD, mishandling/manhandling it. and random Corruption) if you sadly have a Fake SD there's nothing that can be done save for just buying a new one. if you do Test the SD immediately when you get it home, and if proven fake (again proper retail stores have a verrrrry minute chance of also getting fake sd cards in stock.) (Walmart is scummy like this and does it a bit often than people give them credit for.) take it back for a refund and just buy directly from Sandisk or such. at the end of the day w/ a new card make regular backups if your SD 's Data, so if this happens again, your not caught with your pants down and so much progress Lost.

 

[JhonSmith]

OK that at least means you have a valid backup that wont Brick you should you need to restore, has the SD been in heavy Use (alot of Writing(freeshop, FTPserv, SD Management) did you get it online from something like eBay/Amazon (a 3rd party seller not a verified by Amazon as it can happen but rarely from them) have you used it frequently to copy data on/off to via a USB SD Adapter (regardless if this a microSD or full SD form-factor plays no role in when flash memory just cant take it and bites the dust)

if you got your SD from an online source not direct from the manufacture,(or thru amazon but a non "Fulfilled by Amazon") proper local store that isn't some drugstore/"Ma 'n Pa" store higher chances you got a Fake SD and it started to overwrite itself. this makes me think more so w/ the second screenshot as not everything was restored (you can count your "Nintendo 3DS" Folder as a total write-off as there's no way to be certain even if restored digital signatures are intact or files themselves are not corrupt. (sorry but more than likely your saves are Toast.)

GM9/your 3DS isn't at full fault. as @Majickhat55 stated that at the time of reading it couldn't read anything properly due to a Corrupted (in this case of Fat32) FAT Table or full on partition/FS and it has-to to complete the process write garbage back. this garbage write w/ a corrupted fs/partition can even endup writing this gibberish as the FAT (think of it like a big File index but thats over simplifying things and a discussion for another time) causing what you see in the first Screenshot.. If it had written the garbage to the partition Table you'd just get back in windows "This drive needs to be formatted" (as to windows any unknown/unsupported Filesystem/partition scheme gets seen as a unformatted (unknown File system) or uninitialized Disk (unknown partition scheme) and the 3DS in all aspects wouldn't be recognized as i believe the 3DS only supports Fat32.

please check your SD with this: https://3ds.guide/h2testw-(windows).html this wont be the 100% sure fire answer to your problem as it could just be bad timing (incorrect handling of the SD, mishandling/manhandling it. and random Corruption) if you sadly have a Fake SD there's nothing that can be done save for just buying a new one. if you do Test the SD immediately when you get it home, and if proven fake (again proper retail stores have a verrrrry minute chance of also getting fake sd cards in stock.) (Walmart is scummy like this and does it a bit often than people give them credit for.) take it back for a refund and just buy directly from Sandisk or such. at the end of the day w/ a new card make regular backups if your SD 's Data, so if this happens again, your not caught with your pants down and so much progress Lost.

I don´t any problem if have to buy another SD CARD... Butm actually i can´t put the recovery menu or the L+R+UP+START recover...

 

[Dracari]

I don´t any problem if have to buy another SD CARD... Butm actually i can´t put the recovery menu or the L+R+UP+START recover...

you wont not w/o a usable SD w/ a boot.firm in the SD Root. but if however your going to ignore steps given to find the problem at fault. you might have a hard time w/ others giving you help if you dont have an SD Reader for your PC just say so. but beatin around teh bush isnt going to help thinsg any faster,. so as is heres your problem

Your files are Bunk , should not be trusted, your saves are more than likely gone you can copy your "Nintendo 3DS" Folder if you wish but i cannot nor can anyone tell you w/ 100% certainty that everything will be fine. your 3DS is not bricked

that's the tl;dr truth of your situation. wither you do have a SD Reader for your computer or not, or continue to refuse to test for a fake card or not is upto you. i only told you what you should do to save yourself more headaches.

 

[JhonSmith]

you wont not w/o a usable SD w/ a boot.firm in the SD Root. but if however your going to ignore steps given to find the problem at fault. you might have a hard time w/ others giving you help if you dont have an SD Reader for your PC just say so. but beatin around teh bush isnt going to help thinsg any faster,. so as is heres your problem

Your files are Bunk , should not be trusted, your saves are more than likely gone you can copy your "Nintendo 3DS" Folder if you wish but i cannot nor can anyone tell you w/ 100% certainty that everything will be fine. your 3DS is not bricked

that's the tl;dr truth of your situation. wither you do have a SD Reader for your computer or not, or continue to refuse to test for a fake card or not is upto you. i only told you what you should do to save yourself more headaches.

Ok i gonna try all you recomend. Thanks for your time... if i find something im going to post hear.