Hacking I need help to solve Extended RAM games black screen on old 3ds

[The Catboy]

my sysnand is 11.2 sir

Try following the first part of the troubleshooting guide and see what happens
https://github.com/AuroraWright/Luma3DS/wiki/FAQ-and-troubleshooting

 

[Josephimmanuel]

Try following the first part of the troubleshooting guide and see what happens
https://github.com/AuroraWright/Luma3DS/wiki/FAQ-and-troubleshooting

i've done that yesterday and got bricked.

 

[The Catboy]

i've done that yesterday and got bricked.

What about the second part?
Did you apply any patches previously to your NAND?

 

[Josephimmanuel]

What about the second part?
Did you apply any patches previously to your NAND?

Havent sir.

 

[The Catboy]

Havent sir.

I am actually a girl, but I respect your respect.
Still, so it looks like you are having issues with all of the high memory mode, since Pokemon isn't working either.
So here's the advice to help figure that out

@Josephimmanuel You should try to restore a CTRNand image, you may have a frankenfirm.

 

[Josephimmanuel]

I am actually a girl, but I respect your respect.
Still, so it looks like you are having issues with all of the high memory mode, since Pokemon isn't working either.
So here's the advice to help figure that out

im sorry. i didnt notice it. my bad. It takes too much time, and even it's not give any progress. other solutions? thanks b4

 

[The Catboy]

im sorry. i didnt notice it. my bad. It takes too much time, and even it's not give any progress. other solutions? thanks b4

It's cool~
And it looks like a frankenfirm, the fact that you bricked when applying those patches is what's worrisome. This method takes longer, but it flashes a clean 9.2 FIRM to your 3DS and will remove any defective packages. Then upgrading will bring you back up to date.

 

[Josephimmanuel]

It's cool~
And it looks like a frankenfirm, the fact that you bricked when applying those patches is what's worrisome. This method takes longer, but it flashes a clean 9.2 FIRM to your 3DS and will remove any defective packages. Then upgrading will bring you back up to date.

do i have to use the decrypted cia file?

 

[The Catboy]

do i have to use the decrypted cia file?

Use whatever is on that guide. All the files on the guide are tested, scanned, ect. They are safe, clean, and the best to use.

 

[Josephimmanuel]

Use whatever is on that guide. All the files on the guide are tested, scanned, ect. They are safe, clean, and the best to use.

alright, thnks! will try it later

 

[dudemo]

@Crystal the Glaceon is correct. Somehow you managed to get a frankenfirm. How is irrelevant. You need to follow the CTR NAND guide here: https://plailect.github.io/Guide/9.2.0-ctrtransfer

This will bring you back to a stock 9.2.0 firmware and will allow you to update to 11.2 and play extended memory games. It isnt that hard or long. And the end result is a perfectly working o3DS.

 

[BARNWEY]

@Crystal the Glaceon is correct. Somehow you managed to get a frankenfirm. How is irrelevant. You need to follow the CTR NAND guide here: https://plailect.github.io/Guide/9.2.0-ctrtransfer

This will bring you back to a stock 9.2.0 firmware and will allow you to update to 11.2 and play extended memory games. It isnt that hard or long. And the end result is a perfectly working o3DS.

Wow! I just got on GBAtemp, and it seems you guys already may have solved his issue! Even though I'm sorry to hear about the brick @Josephimmanuel, it's a good thing you have a9lh! Anyways, I'm almost absolutely certain that you have a frankenfirm. However, if that is not the case I would highly recommend updating your Luma payload. I read the patches for Luma 6.6 (released this morning), and apparently people have been having issues with games that require a reboot to run (GBA, DS, DSi, High Mem.) So after you finish restoring, if what everyone else says on here doesn't work, I would probably update Luma.

 

[Josephimmanuel]

It worked! Just format your system and before doing that, download JK save managwr to backup your save. And thanks to @JPnintendo! And thanks to all people here! I love GBAtemp!

 

[BARNWEY]

It worked! Just format your system and before doing that, download JK save managwr to backup your save. And thanks to @JPnintendo! And thanks to all people here! I love GBAtemp!

Congragulations! Glad you can play, have fun with your Island Challenge!!!
P.S. FrankenFirms are the worst, am I right? XD

 

[Josephimmanuel]

Congragulations! Glad you can play, have fun with your Island Challenge!!!
P.S. FrankenFirms are the worst, am I right? XD

thanks mate!!!!

 

[BARNWEY]

thanks mate!!!!

No prob
P.S. Once you feel like you got the hang of a9lh and CFW, you may want to try out 3dsafe. It's like Luma's built in password function, but more secure (it stores the pin on the nand, not the sd.) It will also allow you to boot CFW from the NAND, it works a lot like a9lh v3 (even though it's a fork of v2.)

 

[pikpol]

@Crystal the Glaceon is correct. Somehow you managed to get a frankenfirm. How is irrelevant. You need to follow the CTR NAND guide here: https://plailect.github.io/Guide/9.2.0-ctrtransfer

This will bring you back to a stock 9.2.0 firmware and will allow you to update to 11.2 and play extended memory games. It isnt that hard or long. And the end result is a perfectly working o3DS.

It's cool~
And it looks like a frankenfirm, the fact that you bricked when applying those patches is what's worrisome. This method takes longer, but it flashes a clean 9.2 FIRM to your 3DS and will remove any defective packages. Then upgrading will bring you back up to date.

A CTR transfer didn't work for me though. Everything works except extended ram games. I tried retail Sun, downloaded Moon and retail SSB. None of those worked. I have all the latest stuff. Deleted any boot managers I got. Tried with custom path for luma and without. I don't know what to do... It worked before as I played Pokemon Moon on this system before I installed it(and copied the save over) on an other 3DS.

 

[DestinySky]

You must have a region changed console.
Just restore factory setting and it will work again.