Hacking Is now safe downgrade a N3DS?

[tivu100]

Can anyone give the link to download the last sysUpdater? The github just gives me 404 error not found.

Don't get it from the github. The safest downgrade sysupdater is the one you find on the same line of the firmware package pn that common place

 

[Halvorsen]

Well that's just a ludicrous opinion to have. I've never said that bricks would be impossible, user error will always exist, I just said that the current state of downgrading can become more stable and minimize the risk of bricks caused by the program's behalf.

Neither did I say it is the best, most perfect build to ever exist.
However it is close.

 

[Dedede]

-snip-

 

[Halvorsen]

But you said it's safety cannot be improved, right here:



The definition of something that is perfect is something that can't be improved.

No. It cannot become safer by a substantial margin, that still stands.

 

[Dedede]

-snip-

 

[ombus]

cant it be done that if some cia fails it rety again ?

 

[thatbooisaspy]

.

 

[Dedede]

-snip-

 

[Halvorsen]

You've gone from saying "sysUpdater can never be improved" to "sysUpdater can never be improved by a substantial margin".

I agree that the current downgrade process doesn't need much improving, but that doesn't mean it can't be improved and that it's the safest it will ever be.

I didn't think I had to be literal. I thought the substantial margin part was implied, as you know, anything can be improved.

 

[Dedede]

-snip-

 

[Halvorsen]

So, IT CAN BE IMPROVED, as I originally stated. I'm glad that you've now found sense. Conversation over.

Can't find something I never lost.
Either way I didn't know you were that desperate to insult someone by an obvious fact that it probably at most would only be improved by at most a few percent. Still basically the same failure rate. If something is at 99.9% success and you complained it wasn't perfect enough, (i.e. right now) you'd be crazy.

 

[Dedede]

-snip-

 

[Halvorsen]

I'm not trying to insult you. If I have I do honestly apologise. All I've ever said is that the current downgrade applications have the potential for improvement, now that you've stopped refuting that statement, let's be glad that we both agree.

I would definetaly argue that the O3DS success rate is lower than 99.9%, but seeing as nobody knows for sure, and user-errors cannot be accuretaly identified, there's no point trying to put a number on it. I would say with near-certainty however that the success rate is much lower than 99.9% on the N3DS.

Check out this post I wrote about the steps I took to attempt to downgrade mine (https://gbatemp.net/threads/full-report-on-my-downgrade-attempt-9-9-0-26e-new-3ds.408248/). As can be read in the steps, I did everything as carefully and properly as possible, and yet the end result was a brick. Unless I just happened to land in the 0.1% error rate, then I'd say the current downgrade tools could certainly use some improvement to safety.



If I got a brick after one attempt, that makes my own personal success rate 0%. Call me crazy if you will, but I do in fact complain that the current state of things isn't perfect enough.

Okay. You're fine.
And if you get a success rate of 0% then get it the next time (latest update) it's not that bad. And yeah. I was mainly talking about the old 3DS anyway. I helped two people install it and they both were successful, and reading these forums backed it up.

 

[Deleted User]

So you're saying you agree that downgrading won't get any safer than the current methods, yet you also imply that bricks can occur even when there is no fault on the user's behalf?

Doesn't the fact that the program can brick even when the process is done correctly suggest that the downgrade process can become more reliable in the future?

My point is that anything that modifies your system can cause a brick, regardless of the safety measures taken. It can be a 0.1% chance, it can be a 50% chance - if you don't understand what is going on, you make things worse for yourself as you may skip part of an important process or something. If you know what you are doing, go for it, but if you console bricks please, come back with useful information about the steps you took, the intended result, and whether you think that your console is hard bricked or not. If you know it is hard bricked, then don't bother posting because we can't magically fix your potato of a system at this point.

I simply am playing to the lowest denominator because I can't assume that a newbie won't hop on this thread looking for answers, so I simply am stating the generic bold warning. Everybody starts somewhere, and if you are confident enough you can do what you'd like.

(Also, if you have to ask what the brick rate is for this, you haven't used the search function or Google that much, or you don't know how to search well because there are a million duplicate threads on here and Reddit.)

EDIT:

If I got a brick after one attempt, that makes my own personal success rate 0%. Call me crazy if you will, but I do in fact complain that the current state of things isn't perfect enough.

If you hold this attitude, then you aren't blaming yourself for mistakes you made. That 0.01% failure rate is people who didn't read the instructions. They turned off their device while flashing system files, threw their 3DS off the roof for good luck, or otherwise did something they shouldn't have for some reason. If you read the instructions, you will most likely be safe at this point.

 

[Dedede]

-snip-

 

[Deleted User]

I'm sorry if I'm missing something but I genuinely have no clue what this reply is all about. Not only did you not answer the questions posed, but you went off on a weird, unrelated rant about how I should have detailed what I did, and how I should blame myself for my bricked console because of my mistakes, despite the fact that I've already detailed what I did and don't have a bricked console.

You are missing something, and that is that you were not the audience for my reply, your quote just happened to fit with what I had to say. I understand you already know, and feel that your thread is actually extraordinarily useful. I have even linked to it externally elsewhere as a list of correct steps to take and why having a backup is important. I apologize if it came across as me saying that you were incompetent, as that was not my intention at all. Also, you misinterpreted the sentence "I simply am playing to the lowest denominator because I can't assume that a newbie won't hop on this thread looking for answers, so I simply am stating the generic bold warning" - I literally meant that newbies should NOT touch any of this with a ten foot pole if they don't know what they are doing.

Overall, what I meant was that when I write anything on a forum, I assume that I am writing for more than the person I reply to - in this case, I wanted to point out that bricking is possible even with the safest methods, and that someone who was not as prepared as you (or who was lazier and didn't do the required preparations in terms of making backups) would end up in a position where they were SOL. Many people skim and make assumptions, so repeating the obvious can sometimes lead fewer people to messing up.

In the quip about not being perfect (in response to "If I got a brick after one attempt, that makes my own personal success rate 0%. Call me crazy if you will, but I do in fact complain that the current state of things isn't perfect enough"), I was pointing out that if you interpret this literally in the context written, then you will never actually stop complaining as you can't reach 100% certainty of never bricking.

TL;DR - My post wasn't directed at you at all.

(PS - I don't know if you edited your post at a later time or if my work network blocked the link or something, but the link to your other thread wasn't on your post when I replied to it.)

 

[Jil.10]

So now is better wait tomorrow for KTM release?

 

[Phil5004]

I just found this on YT...
So I think it's save with this method