Hacking o3ds emunand on n3ds

[Deleted User]

back when we had to downgrade for cfw you had to remove the sdcard on the n3ds inorder to boot
but when I put o3ds firmware on one of my emunands it blackscreens so I remove the sdcard amd it fails to read the nand
is there a way around this or do I just have to use my o3ds for o3ds firmware?

 

[dpad_5678]

You can't use a NAND backup from any other system at ALL. They're encrypted with console unique keys.

 

[Deleted User]

You can't use a NAND backup from any other system at ALL. They're encrypted with console unique keys.

im not a fucking idiot
im using the same ctrtransfer file I used for my o3ds and n3ds
edit: there's also extremely time consuming ways around the keys for nand backups

 

[dpad_5678]

im not a fucking idiot
im using the same ctrtransfer file I used for my o3ds and n3ds

Don't be a prick if you want help, huh? A little punctuation and a pinch of correct grammar would be great as well.

You made it sound like you were trying to restore an Old 3DS's NAND backup to a New 3DS

And no, you can't use a Old 3DS CTRTransfer file a a New 3DS, and vice versa.

 

[Deleted User]

Don't be a prick if you want help, huh? A little punctuation and a pinch of correct grammar would be great as well.

You made it sound like you were trying to restore an Old 3DS's NAND backup to a New 3DS

And no, you can't use a Old 3DS CTRTransfer file a a New 3DS, and vice versa.

when a9lh was still a thing you had to downgrade both o3ds and n3ds with a o3ds 2.1 ctrtransfer
also screw punctuation I only use it when its really needed our autocorrect does it

 

[The Real Jdbye]

back when we had to downgrade for cfw you had to remove the sdcard on the n3ds inorder to boot
but when I put o3ds firmware on one of my emunands it blackscreens so I remove the sdcard amd it fails to read the nand
is there a way around this or do I just have to use my o3ds for o3ds firmware?

Newer o3DS firmware is unable to boot on n3DS at all. Firmwares up to 6.x (maybe 7.x and 8.x as well, not sure) could theoretically work, but might require some CFW patches. There's just no interest in getting o3DS firmware working on n3DS. Due to hardware differences, it doesn't work correctly anyway. If you've ever downgraded a n3DS to 2.1 you probably know what I'm talking about (colorful flickery upper screen)
The only good reason to run o3DS firmware on a n3DS is to system transfer from n3DS->o3DS, and I suspect that there's a reason why that hasn't been successfully done yet.

 

[Deleted User]

Newer o3DS firmware is unable to boot on n3DS at all. Firmwares up to 6.x (maybe 7.x and 8.x as well, not sure) could theoretically work, but might require some CFW patches. There's just no interest in getting o3DS firmware working on n3DS. Due to hardware differences, it doesn't work correctly anyway. If you've ever downgraded a n3DS to 2.1 you probably know what I'm talking about (colorful flickery upper screen)
The only good reason to run o3DS firmware on a n3DS is to system transfer from n3DS->o3DS, and I suspect that there's a reason why that hasn't been successfully done yet.

I've never had the color flickering except on my friends 3ds
I want to install o3ds firmware on my emunand so I can safely do the brick that happens when you close the system

 

[The Real Jdbye]

I've never had the color flickering except on my friends 3ds
I want to install o3ds firmware on my emunand so I can safely do the brick that happens when you close the system

You can't safely do that brick. It's a hardware brick, it's got nothing to do with your NAND.
Most people say it's a MCU brick which is unfixable, I've heard one guy claim it's not and that it is fixable but I've never heard a single person claim they actually fixed it, so for all intents and purposes it's a hard brick and can't be fixed without replacing parts.
If it was that simple, you could fix it with ntrboot.

 

[proflayton123]

I've never had the color flickering except on my friends 3ds
I want to install o3ds firmware on my emunand so I can safely do the brick that happens when you close the system

And why would you even want to "safely" brick?..

 

[dpad_5678]

when a9lh was still a thing you had to downgrade both o3ds and n3ds with a o3ds 2.1 ctrtransfer
also screw punctuation I only use it when its really needed our autocorrect does it

Yes and there were tweaks with the CFW and CTRTransfer to allow that 2.1.0 to work on N3DS consoles.

Nowadays, that's obsolete, not to mention there's no REASON to run O3DS FW on N3DS.

And "screw punctuation"? How about the fact that your initial question and following responses are almost unreadable?

 

[Deleted User]

And why would you even want to "safely" brick?..

trying to find out what actually causes the brick

 

[Majickhat55]

trying to find out what actually causes the brick

No offense (I don't know your skill set) but if the devs/programmers around here have already done that and no one has found a solution, why try? If you are REALLY that curious than I would like to inform you that the "MCU" brick is tantamount of a hardware brick, which as stated requires a replacement.
Why the hell would you want to brick yourself on purpose when not one person has successfully recovered from one? I'd also like to mention that if you visit 3D Brew you will see that the MCU SoC buses (there are two) control a hell of a lot more than just the LED lights which was the big deal with closing the lid on a N3DS in 2.1... The MCU also controls the volume slider, the camera, the LCD screens, the Home button and a lot more.

I have seen at least two "perm" bricks that were related to the MCU and a broken camera ribbon cable. Of course he didn't assume it was hardware since the screen would init from the bootrom, but not the homemenu but after BOTH of them opened the chassis and repaired the cable it worked fine.

I don't see how you plan to fix a system module that is stuck in a circle of reading bad data, failing, and attempting to read it again on a loop. You would need to stop it to even get into the console. I mean honestly you may be able to disable the LED light altogether from the motherboard and fix it that way, but no one has tried since I'm pretty sure that would require damaging the MCU SoC (I'm not sure if there is a tiny cable from the MCU to the LED). If you do that, you're breaking more than you're fixing and you're going to end up with a crap system anyway.

Makes you wonder why everyone says they can't even be fixed with a hardmod; that implies you can't fix it without breaking other necessary components for the console to run; or that it's impossible TO fix.

 

[Deleted User]

No offense (I don't know your skill set) but if the devs/programmers around here have already done that and no one has found a solution, why try? If you are REALLY that curious than I would like to inform you that the "MCU" brick is tantamount of a hardware brick, which as stated requires a replacement.
Why the hell would you want to brick yourself on purpose when not one person has successfully recovered from one? I'd also like to mention that if you visit 3D Brew you will see that the MCU SoC buses (there are two) control a hell of a lot more than just the LED lights which was the big deal with closing the lid on a N3DS in 2.1... The MCU also controls the volume slider, the camera, the LCD screens, the Home button and a lot more.

I have seen at least two "perm" bricks that were related to the MCU and a broken camera ribbon cable. Of course he didn't assume it was hardware since the screen would init from the bootrom, but not the homemenu but after BOTH of them opened the chassis and repaired the cable it worked fine.

I don't see how you plan to fix a system module that is stuck in a circle of reading bad data, failing, and attempting to read it again on a loop. You would need to stop it to even get into the console. I mean honestly you may be able to disable the LED light altogether from the motherboard and fix it that way, but no one has tried since I'm pretty sure that would require damaging the MCU SoC (I'm not sure if there is a tiny cable from the MCU to the LED). If you do that, you're breaking more than you're fixing and you're going to end up with a crap system anyway.

Makes you wonder why everyone says they can't even be fixed with a hardmod; that implies you can't fix it without breaking other necessary components for the console to run; or that it's impossible TO fix.

idc
if its a mcu brick then ill spend forever on it
atleast ill have something to do

 

[Majickhat55]

More power to you, it's your stuff after all. I still don't get why you would want to try something that's been tried already many times expecting a different result; experiments change a variable, they don't just rinse and repeat. So I would at least do some research and ask around what hardmodders have tried in regards to fixing the brick. Else you're just wasting your time. Good luck!! I'm interested in what you discover.