Hacking 10.3 New 3ds downgrade to 9.2

[Subhaan2703]

How can I ensure that the downgrade to 9.2 goes smoothly? I've heard that downgrading new 3ds' can cause a softmod leaving me on 11.0. What can I do to ensure this doesn't happen and what is the optimum fw to downgrade from?

 

[Kingy]

10.3 is best for the kernel exploit you will be using. I recommend formatting your 3ds and then downgrading as that lowers the chances of bricking. You still have a chance to brick, but just hope that doesn't happen. Good luck!

Also: Use PlaiSysUpdater as it checks your downgrade files.

 

[Subhaan2703]

10.3 is best for the kernel exploit you will be using. I recommend formatting your 3ds and then downgrading as that lowers the chances of bricking. You still have a chance to brick, but just hope that doesn't happen. Good luck!

Also: Use PlaiSysUpdater as it checks your downgrade files.

Is plaisysupdater what the plailect guide uses?

 

[Kingy]

Is plaisysupdater what the plailect guide uses?

yes. It is.

 

[Subhaan2703]

yes. It is.

Okay awesome ty!

 

[Kingy]

Okay awesome ty!

Good luck!

 

[Subhaan2703]

Good luck!

Quick question before I do it, I just got the console today and it was used but reset. All I have done is set it up and installed menuhax but no games, nnid or anything else. Would you still reset it to make sure or just go ahead with the downgrade?

 

[Kingy]

Quick question before I do it, I just got the console today and it was used but reset. All I have done is set it up and installed menuhax but no games, nnid or anything else. Would you still reset it to make sure or just go ahead with the downgrade?

You can just go for it. Again, good luck!

 

[Deleted member 381889]

Hope everything goes smoothly for you!

 

[Subhaan2703]

You can just go for it. Again, good luck!

Hope everything goes smoothly for you!

Just did it and all seemed to have went smoothly, just had to manually reboot after 10s. Currently backing up sysnand.bin and will probably do the full install tomorrow as i don't have a charger atm. Ty for your help

 

[YourHero]

FYI, if you downgrade and it turns back on to a black screen, try ejecting the SD card. For me the ext data became corrupted after my downgrade from 9.6>9.2. Removing the SD card and deleting the EXT data fixed it for me. I don't remember reading about that on Plai guide, so I thought I'd mention it. As far as bricking goes, I think it's just a slight softbrick fixable by doing recovery mode update to max version, which leaves you with a 3DS you cannot downgrade BUT working.

 

[Subhaan2703]

FYI, if you downgrade and it turns back on to a black screen, try ejecting the SD card. For me the ext data became corrupted after my downgrade from 9.6>9.2. Removing the SD card and deleting the EXT data fixed it for me. I don't remember reading about that on Plai guide, so I thought I'd mention it. As far as bricking goes, I think it's just a slight softbrick fixable by doing recovery mode update to max version, which leaves you with a 3DS you cannot downgrade BUT working.

Have a bit of a problem, can't seem to launch luma as i just get a black screen. Tried deleting config.bin with no prevail. Shall i redo the complete Rednand setup or can that cause a brick. Or shall i restore rednand from the sysnand.bin file I made earlier (Though this is 1.98gb and the guide says 1.88gb). Any help is much appreciated!!

 

[Deleted member 381889]

Have a bit of a problem, can't seem to launch luma as i just get a black screen. Tried deleting config.bin with no prevail. Shall i redo the complete Rednand setup or can that cause a brick. Or shall i restore rednand from the sysnand.bin file I made earlier (Though this is 1.98gb and the guide says 1.88gb). Any help is much appreciated!!

Try redownloading luma, if the RedNand was bad, you'd still see the config. If that doesn't work, check for a frankenfirmware.

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

Wait, was the RedNand working before?

 

[Subhaan2703]

Try redownloading luma, if the RedNand was bad, you'd still see the config. If that doesn't work, check for a frankenfirmware.

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

Wait, was the RedNand working before?

I haven't been able to launch it at all yet, just got to the step when you first open luma and it didn't work, what would you recommend i do?

 

[Deleted member 381889]

I haven't been able to launch it at all yet, just got to the step when you first open luma and it didn't work, what would you recommend i do?

Did you try redownoloading luma?

 

[Subhaan2703]

Did you try redownoloading luma?

Just used luma 5.2 and i think it worked but it doesn't say EMU it says VER even though i selected show ... in system settings. What shall i do now?

Edit: I think it worked currently updating rednand, hopefully it works!!

 

[Subhaan2703]

Just used luma 5.2 and i think it worked but it doesn't say EMU it says VER even though i selected show ... in system settings. What shall i do now?

Edit: I think it worked currently updating rednand, hopefully it works!!

Yup worked my way to the finish of part 3. Will hopefully finish the guide once I get a charger tomorrow. Hopefully I don't brick like my last time!! Thanks for your help

 

[YourHero]

Have a bit of a problem, can't seem to launch luma as i just get a black screen. Tried deleting config.bin with no prevail. Shall i redo the complete Rednand setup or can that cause a brick. Or shall i restore rednand from the sysnand.bin file I made earlier (Though this is 1.98gb and the guide says 1.88gb). Any help is much appreciated!!

On the website for luma is a firmware.bin. Drop it in the luma folder.

 

[Thelvyn]

FYI, if you downgrade and it turns back on to a black screen, try ejecting the SD card. For me the ext data became corrupted after my downgrade from 9.6>9.2. Removing the SD card and deleting the EXT data fixed it for me. I don't remember reading about that on Plai guide, so I thought I'd mention it. As far as bricking goes, I think it's just a slight softbrick fixable by doing recovery mode update to max version, which leaves you with a 3DS you cannot downgrade BUT working.

This happened to me too - your advice really helped thanks - though to be safe I treated it as a partial fail and restarted the downgrade which worked fine.