Concerning the Nintedont Maintenance and sysUpdater (people who haven't sucesfully downgraded)?

yep, updating will be down.

 

This may be a once in a lifetime opportunity to downgrade so keep trying until it works. I just downgraded today and fortunately it worked my second time. I was using a mac and got the extra .[name whatever].cia and deleted it with ftbrony and it worked like a charm (first time was a partial downgrade.) And I did this just using the sysupdater, I didn't format my sdcard or started fresh. Just. Keep. Trying.

 

The "once in a lifetime" part is the ability to recover from softbrick, right? Cause everything else that I know of can still be done even if they take the servers down and you're on 10.3.

 

what should I do im getting my 2ds tomorrow in the mail but won't be home untill 3pm. Should I just come home and use sysupdater and hope everything works out?

 

Either that or wait for KTM, which will be released sometime after the maintenance window and 10.4 release.

 

If you're getting a 2DS, it will be below 9.3 as long as it isn't the Yokai Watch bundle. You don't need to downgrade for that.

 

Yeah, uh, Pingo doesn't have the best track record with that. Besides, all it would've done was to do some hash checks for file integrity. You can do that yourself. If I hadn't downgraded already I'd do it now so softlocks let you have another chance.

 

So if we are on 10.3 and DONT downgrade we will still be able to downgrade even after the update as long as we have a way to get to menuhax correct? Assuming we stay on 10.3.

 

I'm also really hoping for a solution to the softbrick problem. I really don't want to format and lose almost 5 years of data that can't be backed up.

 

We should be fine as long as we can still access homebrew, right? I plan on downgrading my sister's 3DS sometime this week and she's on 10.1(I believe). Is there something Nintendo implemented that requires we use their service for any of the downgrade/CFW installation process?

 

The main fear would be that if you soft-bricked your 3ds and updated through recovery mode, you would get 10.4 instead of 10.3, which may not be vulnerable (I'm new here, don't know for sure)

The failure rate for downgrading is relatively high, which is why some people are trying to do it while the exploitable 10.3 is still available

 

I see, I hadn't considered getting a brick. My O3DS downgrade went smoothly. Fingers crossed, I hope my sister's O3DS will downgrade without any issues as well.

Thanks for clearing it up.

PS- I hear different entrypoints are better?
I used Ninjhax, in case anyone's wondering.

 

Hm. They say IronHax works well, I think different entrypoints have more levels of access to points of the hax, allowing for a higher success rate. Personally, first time I used menuhax and the downgrade failed. Second try, I used Browserhax and it worked smoothly. (30 games installed baby yeah)

 

Formatting is the solution to the soft-bricking, guys. Worked instantly after formatting. There might be another fix, but it sure ain't gonna come in a day. The problem isn't the downgrader, or the cia files, or anything. It's the console. Either wait an eternity for someone to maybe figure it out and fix it, or just rip the bandaid off and backup what you can.

 

It also checks after a CIA install whether the CIA actually installed or not and retries the install up to 5 times, something sysupdater doesn't do yet AFAIK. Sysupdater will just give up on a failure.

 

Everyone knew this was coming, especially after the 32c3 conference. What everyone is interested in is what Nintendo's response is, more or less what exploits they've closed/fix.

 

What's the rush? Just because 10.4 might come out doesn't mean you can't downgrade, just don't update from 10.3. Once you're using EmuNAND, chances are you can update that to 10.4 just fine.

 

The rush is that there's certain select people, seemingly at random, that get constant soft-bricks when trying to downgrade. And soft-brick=have to update to latest FW.