Am I screwed? I think I am.
Downgraded through OOTHAX and PlaiSysUpdater, following Plailect's A9LH guide.
Downgraded through OOTHAX and PlaiSysUpdater, following Plailect's A9LH guide.
1. Try booting with your SD card out, and then reinserting it after booting.
- Power off your 3DS by holding down the power button.
- Take out the SD card.
- Power on the 3DS.
- When the home menu appears, reinsert your SD card.
No luck there either. Probably a softbrick, and I'd be fine with that if anything actually worked on 11.0.It may sound stupid but ... try booting with your SD out ..?
Sounds like a softbrick
Don't update yet , maybe there's a solutionNo luck there either. Probably a softbrick, and I'd be fine with that if anything actually worked on 11.0.
Or sys-recover and update to 11 and wait for downgrading to be fixed. It's possible.Try taking the ss out. Of that doesn't work try entering recovery. If that doesn't work you'll need a hardmod and NAND backup
I'm updating now through recovery. A shame too, given that this is a friend's 3DS and I told him I would A9LH it.Don't update yet , maybe there's a solution
Can you even access recovery at all ?
I kinda feel bad for you and your friend ;w;I'm updating now through recovery. A shame too, given that this is a friend's 3DS and I told him I would A9LH it.
You can't downgrade on 11.0throws 3DS at wall
I'll have to try again later on, but for now, it's about worthless. Quite odd how it (soft)bricked an o3DS using completely safe and reliable tools but when I downgraded my n3DS with (at the time) newer unreliable tools it worked perfectly.
You can't downgrade on 11.0
for now, it's about worthless.
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.
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.
Yes, yes I know, but it's just horrible luck that that "small" chance happened to me with that seems to be the most reliable downgrader.Taken from Plailect's guide.
Nope, neither the o3DS (which I bricked) or the n3DS (which is working fine) was formatted.Did you format the console "before" downgrading? I just want to know since I'm currently doing a9lh right now.
You were lucky off, you got a frankenfirmware. At least it booted.I got a similar problem times ago.
I downgrade my new 3ds 9.9
With a tutorial for 10.6 - 10.7.
Durint process i got "An error has occured"
I shut down console and its boot with 9.2
But Gateway refuse works and i couldn't setup cfw and emunand. So i decide try again
I repeat processo without touch anything. I meaning i didnt update to 10.7. While 9.2 frankfirmware i tried again and works.
Complete downgrade. And o setup emunand after that a9lh.
So anyone knows what happens? Why its give error fisrt attemp but works second.
And its happens twice with mine and a friend new 3ds.
Well the funny part it's boot like was downgraded, but doesnt let setup cfwYou were lucky off, you got a frankenfirmware. At least it booted.