After ROPing my 3ds. I tried to launch my flash card again, but it came up with the 'DS cannot read software', Then I tried to use Pokemon Black and it came up with the same screen. Anyone know how to fix this?
Isn't the cause of your problem pretty obvious to you? DS Profile is currently set up to trigger a glitch and launch the ROP chain - if you plan on using DS Mode again, you need to remove the profile exploit.After ROPing my 3ds (...)
Don't post if you don't know what you're talking about. That's not how it works. The exploit is automatically removed upon launching DS mode, and as he said, he's unable to do that which means he's also unable to remove the exploit by conventional means.Isn't the cause of your problem pretty obvious to you? DS Profile is currently set up to trigger a glitch and launch the ROP chain - if you plan on using DS Mode again, you need to remove the profile exploit.
Is there any other way, or am I stuck with that option onlyoverwrite the NVRAM (format the 3DS)
Which part of what I've said is incorrect to you? The source of his problem is exactly what I said it is, whether the exploit is corrupt or not, and the solution is exactly what I've said it is - removing it.Don't post if you don't know what you're talking about. That's not how it works. The exploit is automatically removed upon launching DS mode, and as he said, he's unable to do that which means he's also unable to remove the exploit by conventional means.
you can hardware mod the 3DS wifi card and access the NVRAM from there.Is there any other way, or am I stuck with that option only
So that a no for a (strictly) software only guy with no moneyyou can hardware mod the 3DS wifi card and access the NVRAM from there.
Just a quick question to you, since you're more well-versed in the matter - can you R/W from/to NVRAM in 3DS Mode at all? Just wondering, really.you can hardware mod the 3DS wifi card and access the NVRAM from there.
Sorry fox, I'm very newWhich part of what I've said is incorrect to you? The source of his problem is exactly what I said it is, whether the exploit is corrupt or not, and the solution is exactly what I've said it is - removing it.
I wasn't talking to you, I was talking to "TheRealJdRudeForNoReason" - I'm just trying to help you.Sorry fox, I'm very new
I do know the ROP failed, I was just looking for advice on (non-formating) ways to fix it
you can with the "cfg:nor" service but not everyone has access to that service or directly when you are in kernel mode.Just a quick question to you, since you're more well-versed in the matter - can you R/W from/to NVRAM in 3DS Mode at all? Just wondering, really.
Thank you. Perhaps once we figure these things out a little bit better, making a 3DS-side exploit tool would be a good idea - a simple uninstaller or profile editor would be nice.you can with the "cfg:nor" service but not everyone has access to that service or directly when you are in kernel mode.
well most homebrew exploit don't have access to "cfg:nor"Thank you. Perhaps once we figure these things out a little bit better, making a 3DS-side exploit tool would be a good idea - a simple uninstaller or profile editor would be nice.
Which is why it's an idea for the distant future.well most homebrew exploit don't have access to "cfg:nor"
Glad to see that your issue is resolved, more or less.Okay, It worked but I can't use any of my NES games. Atleast there was a few good Nes emulators for the DS
the only exploit that has access to it is the GW exploit but the GW exploit is fixedWhich is why it's an idea for the distant future.
Nothing lost,Glad to see that your issue is resolved, more or less.