Homebrew [KTM Release] Tomorrow

[Urbanshadow]

It would but it's not worth risking the NAND again.
The execution rate isn't so great right now but there are way to make it better.

Thanks for the quick response. We should wait then for a proper cleaner? (Im one of those users seeking a pristine 9.2)

 

[BothyBhoy]

could you maybe elaborate on ways to make it better?. do you mean all the careful stuff you gotta ensure you do?.

 

[JustPingo]

Thanks for the quick response. We should wait then for a proper cleaner? (Im one of those users seeking a pristine 9.2)

I'll make one.

 

[Nyannurs]

wat

did i word it wrong or what
just basing my points on his own post

 

[Urbanshadow]

I'll make one.

Thank you so much for that, then. I'll wait for it. Perhaps an update to KTM with this option could be more than enough?

Just a question: What would prefer an emunand in 10.3 when booting: the real unused titles on a downgraded sysnand or the SD 10.3 titles?

 

[Deleted-236924]

i'm not even going to start on how retarded you are. don't you realize that this long post you wrote are all fairly good decisions taken by @JustPingo? "he didnt take advantage of snshax because sysupdater was due to an earlier release" why would he keep working on KTM using snshax when sysupdater already does?????????????

Lol ok you've just lost any credibility you ever had in my book.
You resort to calling me retarded = I'm done with you, cya

 

[Insidious611]

I realize I'm newish here, but a post calling itself "[KTM Release] Tomorrow" with absolutely no actual hard data backing it seems a tad deceptive to me.

 

[RhythmCat]

I realize I'm newish here, but a post calling itself "[KTM Release] Tomorrow" with absolutely no actual hard data backing it seems a tad deceptive to me.

There is a source to compile on github.

 

[Urbanshadow]

I realize I'm newish here, but a post calling itself "[KTM Release] Tomorrow" with absolutely no actual hard data backing it seems a tad deceptive to me.

It's ok. Just go chill around the forums a bit until you feel more comfortable and come back here when there's hard data backing it for you. There are plenty of threads worth a read.

 

[Nyannurs]

Lol ok you've just lost any credibility you ever had in my book.
You resort to calling me retarded = I'm done with you, cya

i really couldnt care less buddy

 

[Ripper00420]

This is still an open thread....??? Well its the tomorrow after tomorrows tomorrow I guess...lmao!!!! Someone please stop the damned madness over source that can be compiled that's not finished and rumors.

 

[Juiss]

did i word it wrong or what
just basing my points on his own post

It sounds like you're implying sysUpdater uses SNShax

 

[Nyannurs]

It sounds like you're implying sysUpdater uses SNShax

i believed it used it, since i saw some people downgrade new 3dss with it. just now i realized that n3ds can use mch2 as well, seems like im the retard now lol
@Ammako sorry for calling you retarded lmao, im the stupid 1 here, i take it all back

 

[HeyItsJono]

There is a source to compile on github.

Available source != actual release, lol. The source was probably available for a while before this thread was made too.

I realize I'm newish here, but a post calling itself "[KTM Release] Tomorrow" with absolutely no actual hard data backing it seems a tad deceptive to me.

I believe the thread was made because JustPingo tweeted out saying it would be released, but he then decided to push the release back once or twice for stability's sake. Honestly, AFAIK there's no real benefit to using KTM over the latest SysUpdater as long as you verify the hash of your update package when using SysUpdater. Does that sound about right @JustPingo? I was also wondering, there have been reported cases of psuedo-hardbricks with the latest SysUpdater (see this thread), is this a risk with KTM? Curious as to whether the issue is related to the downgrade process itself or some fault in the way SysUpdater is written.

 

[Insidious611]

Yeah, I've already downgraded two seperate O3DS style machines (one 2DS and one 3DS) using SysUpdater, with absolutely 0 issues.

 

[JustPingo]

Available source != actual release, lol. The source was probably available for a while before this thread was made too.

I believe the thread was made because JustPingo tweeted out saying it would be released, but he then decided to push the release back once or twice for stability's sake. Honestly, AFAIK there's no real benefit to using KTM over the latest SysUpdater as long as you verify the hash of your update package when using SysUpdater. Does that sound about right @JustPingo? I was also wondering, there have been reported cases of psuedo-hardbricks with the latest SysUpdater (see this thread), is this a risk with KTM? Curious as to whether the issue is related to the downgrade process itself or some fault in the way SysUpdater is written.

Well, as a first guess I'd say that it have less chances to happen with KTM because this looks like an OS call error, and KTM will always try again multiple times. But you know, that's just a guess.

 

[Mr_sephiroth]

so KTM will be made then SoonTM ?

 

[Tyler Martin]

so KTM will be made then SoonTM ?

i wish it would come out today

 

[Lycan911]

K™ will come out SOON™

 

[HeyItsJono]

Well, as a first guess I'd say that it have less chances to happen with KTM because this looks like an OS call error, and KTM will always try again multiple times. But you know, that's just a guess.

That's certainly reassuring. Just so I can understand it a bit better, what do you mean by OS call error? What I'm gathering here is that if SysUpdater screws up installing a .cia it skips over it whereas KTM will try again to lessen the chance of this happening? Also what tipped you off as to the fact that it was a OS call error? TuxSH seemed not to know the cause of the issue in the thread, he only referred to it as a rare code corruption, but it seems to be the cause of a few permanent bricking cases so it's not rare enough imo.