Homebrew Nearly Bricked and had to update

[Biovirulent]

Okay, so it seems there is no way to use homebrew at the moment. Freakyforms is unavailable from the e-shop.

Anyhow, I was downgrading to 9.2.0 for CFW and everything was going well until it said an error has occured. It had kept saying this until I booted in safe mode.
The problem is, everything on screen said was "GOOD" and then it said "DONE" as if it finished correctly.
I chose the right region, console model... What could have happened? And why? I am now without homebrew because of this. I'm just glad it didn't brick.

 

[solress]

did you boot without SD? It's usually just that

 

[MsMidnight]

Okay, so it seems there is no way to use homebrew at the moment. Freakyforms is unavailable from the e-shop.

Anyhow, I was downgrading to 9.2.0 for CFW and everything was going well until it said an error has occured. It had kept saying this until I booted in safe mode.
The problem is, everything on screen said was "GOOD" and then it said "DONE" as if it finished correctly.
I chose the right region, console model... What could have happened? And why? I am now without homebrew because of this. I'm just glad it didn't brick.

did you try taking out the sd card

 

[Biovirulent]

did you boot without SD? It's usually just that

Yes, I did. A few times actually.

 

[solress]

Yes, I did. A few times actually.

It might have been a soft-brick. Did you format your system before downgrading?

 

[Biovirulent]

It might have been a soft-brick. Did you format your system before downgrading?

Formatting would mean losing all data, and in the tutorial it didn't say anything about it. So no, I didn't.

 

[solress]

Formatting would mean losing all data, and in the tutorial it didn't say anything about it. So no, I didn't.

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 beforedowngrading. 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.

 

[NinjaSushi]

Formatting would mean losing all data, and in the tutorial it didn't say anything about it. So no, I didn't.

yeah. That'd be the problem. What guide did you follow

 

[Biovirulent]

Ahh.. I see. Thank you for pointing this out. I must have skipped over reading this. Thank you for helping.

So it seems this could have been prevented, I just wish it would have said this during the tutorial in the steps and troubleshooting rather than somewhere else.

 

[proflayton123]

Ahh.. I see. Thank you for pointing this out. I must have skipped over reading this. Thank you for helping.

So it seems this could have been prevented, I just wish it would have said this during the tutorial in the steps and troubleshooting rather than somewhere else.

Did you then boot into safe mode and update to latest firm? :c

 

[solress]

Ahh.. I see. Thank you for pointing this out. I must have skipped over reading this. Thank you for helping.

So it seems this could have been prevented, I just wish it would have said this during the tutorial in the steps and troubleshooting rather than somewhere else.

Plailect's explaination is that it's not necessary for everyone, and it can't be prevented after downgrading. It's in the intro to the part which tells you more and important things.

 

[Biovirulent]

Did you then boot into safe mode and update to latest firm? :c

Yes. I had no other choice.

 

[proflayton123]

Yes. I had no other choice.

Ah, I guess you learnt a new lesson..

Always read it over, check it twice, maybe even a third time. These things happen due to user error :c

 

[Biovirulent]

Ah, I guess you learnt a new lesson..

Always read it over, check it twice, maybe even a third time. These things happen due to user error :c

Yep. A little too late now. I'm just impatient haha.

 

[gnmmarechal]

It was a softbrick. You should've formatted prior to downgrading. It avoids this.

 

[bi388]

You can still use homebrew, cubic ninja and maybe oot and smash bros can run homebrew

 

[Quantumcat]

You can still downgrade with a hard mod, but you'd also need to get a copy of FreakyForms. Best thing to do is send it to someone for a hardmod + downgrade (or full a9lh install to save yourself any future grief).

 

[Biovirulent]

You can still use homebrew, cubic ninja and maybe oot and smash bros can run homebrew

Don't have cubic ninja, and neither it or oot3d are updated. They are also secondary hax.
I don't think I can set up smashbroshax.

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

You can still downgrade with a hard mod, but you'd also need to get a copy of FreakyForms. Best thing to do is send it to someone for a hardmod + downgrade (or full a9lh install to save yourself any future grief).

Freakyforms goes for $40+ usd in physical. Not worth just some waiting for me.

 

[bi388]

Don't have cubic ninja, and neither it or oot3d are updated. They are also secondary hax.
I don't think I can set up smashbroshax.

No cubic ninja is 100% primary and I'm pretty sure it's updated to work on latest firmware and oot can be primary if you get a powersave

 

[Biovirulent]

No cubic ninja is 100% primary and I'm pretty sure it's updated to work on latest firmware and oot can be primary if you get a powersave

No powersave, sadly. Oh well. Not sure if I trust any sites selling hardware for the 3ds with my debit card information.