Hacking So basically.. I'm screwed?

[mikey420]

Why do people always recommend outdated apps... Safesysupdater is not recommended. See above post.

 

[Aerocool]

yes use plaisysupdater instead!

 

[Tobias97]

Yeah, SafeSysUpdater has had some reports of freezing mid-process. And well, you don't want that to happen.

 

[Sonic Angel Knight]

Isn't one app supposed to verify the right downgrade files before using another to perform actual downgrade?

 

[Aerocool]

Isn't one app supposed to verify the right downgrade files before using another to perform actual downgrade?

no, both check if the files are good and perform the downgrade.

 

[ScarletDreamz]

i had 0 freezes / errors after downgrading more then 20 consoles.

But again you can do whatever you want lol.

In case you want the SafeSys : https://gbatemp.net/attachments/safesysupdater-3dsx-1-0-zip.41859/

 

[Sonic Angel Knight]

i had 0 freezes / errors after downgrading more then 20 consoles.

But again you can do whatever you want lol.

In case you want the SafeSys : https://gbatemp.net/attachments/safesysupdater-3dsx-1-0-zip.41859/

20?

Umm wow okay. thats a lot

 

[placebooooo]

Hi there,

I just bought a New 3DS on firmware 9.6 with the goal to downgrade to 9.2.

So I installed The Homebrew-Launcher through Browserhax and it worked. Now I wanted to downgrade to 9.2 - but now I'm stuck at the black error screen "please power of your system and so on..". It happended shortly after I started downgrading.

Now I'm screwed.. am I ? There is no way to get around a system update to 11.0, right?

Just wanted to know. Thanks.

I just bought a new 3ds xl as well and just installed arm9 on it a few days ago. Honestly, my plan was that if anything went wrong, like with your case, I would update the system, return it, and buy a new one.

 

[Bimmel]

Thats perfect!
Like I said in my post before, you just have an partial downgrade.
This happened to me everytime I downgraded a 3DS but it was easily fixable!
Just get the homebrew launcher running, install menuhax and start the downgrade process again!

Wow. First, thank all of you for your answers!

So I tried again what Don said and started the process again. This time it worked, but was very.. fast. It rebooted without any problem - the whole thing did take 20 seconds. Is this suspicious?
I reinstalled menuhax and looked at the Firmware version.. and it shows 9.2.0-20E - time to celebrate at this point for not screwing it up?

I take a break with this until someone says I'm good to go. Got a little frightened here to be honest.

The console boots normally again, with the SD-Card in it.

 

[Sonic Angel Knight]

Good job, next time follow the guide and consult the troubleshooting FAQ , and don't panic if you don't understand something. Just try again.

 

[Bimmel]

Good job, next time follow the guide and consult the troubleshooting FAQ , and don't panic if you don't understand something. Just try again.

Still shaking here.

The part I've read sounded so sure that I was about to give up.. damn, that was a close one. But it was exactly like it was written there. Did I misunderstood or something?

 

[Sonic Angel Knight]

can you be more specific what your talking about?
https://github.com/Plailect/Guide/wiki/Troubleshooting

 

[Bimmel]

can you be more specific what your talking about?

Of course.

I meant this

All variations of sysUpdater, not just PlaiSysUpdater, has a very small chance of causing a "soft brick" once the downgrade is complete and the device reboots. This will cause the system to boot directly to the Nintendo error screen instructing users to power off the device.

The reason for this is unknown, but can be prevented by performing a system format before downgrading. It seems to happen very often on systems with ambassador status or who have DSiWare installed.

Once this error happens, it can only be fixed by using safe mode (A + R + L + Up on the D-Pad) to update to the latest system version.

As of the time this is written, the latest version (11.0.0) has completely blocked all software downgrading, and if someone encounters this error they will be locked out of any further downgrading unless they use a hardmod exploit.

It happened exactly like that. I started PlaiSysUpdater, the System did try a reboot as far as I could see, and the Nintendo error screen was there. So I thought it was over.

 

[Sonic Angel Knight]

can you be more specific what your talking about?
https://github.com/Plailect/Guide/wiki/Troubleshooting

It say small chance, and once again, if you run into problems, follow the troubleshooting guide for help.

I'm sure even if the small chances, the stuff in the guide it instruct to use was tested for stability and mostly for precautions to avoid brick, so consider that next time.

 

[Bimmel]

It say small chance, and once again, if you run into problems, follow the troubleshooting guide for help.

I'm sure even if the small chances, the stuff in the guide it instruct to use was tested for stability and mostly for precautions to avoid brick, so consider that next time.

Will do that. I'll report back if the rest goes well. Thanks for now!

 

[Sonic Angel Knight]

Will do that. I'll report back if the rest goes well. Thanks for now!

If you ever have to do any of this again, for whatever reason like buying a new system, PLEASE book mark this page.
https://github.com/Plailect/Guide/wiki

Look at the right side, click faq before doing anything, click on anything that interest you in whatever it is you want. Click troubleshoot if you need advice. If you need second opinion or help on anything that isn't covered in the guide, just ask like you did today.

 

[Kirtai]

This time it worked, but was very.. fast. It rebooted without any problem - the whole thing did take 20 seconds. Is this suspicious?

I've had several N3DS' that crashed on the very last file (NFIRM) of the downgrade. In that case, rerunning the downgrade only has to install one file and is very fast.

 

[Ricken]

I've had several N3DS' that crashed on the very last file (NFIRM) of the downgrade. In that case, rerunning the downgrade only has to install one file and is very fast.

Isn't NFIRM 2nd to last?

 

[Kirtai]

Isn't NFIRM 2nd to last?

Could be, I just remember that in each case it only needed to write the NFIRM during the second downgrade.

 

[solress]

Could be, I just remember that in each case it only needed to write the NFIRM during the second downgrade.

that's true, for the complete downgrade to have taken place it only needs to adjust the native firm, and it's done.