Homebrew [KTM Release] Tomorrow

  • Thread starter Thread starter LuksaXD
  • Start date Start date
  • Views Views 89,385
  • Replies Replies 589
  • Likes Likes 3
So... what's the status on N3DS users who keep soft-bricking? Is KTM confirmed to fix this? Are we shit outta luck unless we format the 3DS? Is there some solution that I'm not aware of?

at this point all we can do is hope KTM works (doubtful) or hope gateway comes out with their own downgrader that works for those of us getting softbricks (we'll be waiting a while.)
 
at this point all we can do is hope KTM works (doubtful) or hope gateway comes out with their own downgrader that works for those of us getting softbricks (we'll be waiting a while.)
i dont think the soft-bricks are the problem ... me personally am not using sysupdater for the chanche of a hard-brick.. the n3ds isnt a month old and dont want a rock.

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

The situation of KTM right now from my point of view: no source = no proofs of improvement = bullshit.

PS: My apologies if anyone feels offended.
then you sir are blind.. https://github.com/JustPingo/KernelTimeMachine/commits/master
 
Guys heres a tip to save yourself a n3DS. Dont use SysUpdator on n3DS simple. Be patient and wait for KTM. SysUpdator basically doesnt even work on n3DS its that high of a brick rate/unsuccessful rate yet it almost always works on o3DS (Never saw anyone say it didnt work etc from just regular app issues just simple mistakes THEY made like downloading n3DS update files rather then o3DS etc).

KTM should work perfect on n3DS just be patient :)

Uh, sysupdater worked perfectly fine on both the N3DS systems I used it on. 1st try for both, which I know is fairly rare, but saying it basically doesn't work is completely incorrect. KTM still uses memchunkhax2, by the way, so no it won't work any better on N3DS until the bugs can be ironed out of mch2.
 
i dont think the soft-bricks are the problem ... me personally am not using sysupdater for the chanche of a hard-brick.. the n3ds isnt a month old and dont want a rock.

hardly anyone is getting hard-bricked right now - and that's pretty much due to user error. there are, however, many people who are doing everything right and still getting softbricked after downgrading.
 
hardly anyone is getting hard-bricked right now - and that's pretty much due to user error. there are, however, many people who are doing everything right and still getting softbricked after downgrading.
As far as we know. There could be people getting hard-bricked but not reporting anything.
 
The situation of KTM right now from my point of view: no source = no proofs of improvement = bullshit.

PS: My apologies if anyone feels offended.

to say that you should have programming knowledge and having read the repo and have identified any flaw in the code many of those who read this thread think that equals sysupdater but have no idea what they are talking
 
hardly anyone is getting hard-bricked right now - and that's pretty much due to user error. there are, however, many people who are doing everything right and still getting softbricked after downgrading.
Yep 10th try and softbrick everything is ok and no dice :(
 
It's some sad shit how people still think these programs won't brick your 3DS. No coding on this planet is perfect. Any of these programs even ones that are known to work can still brick your 3DS till this day. This a fact, and there is no such thing as a 100% success rate on any of these programs. Just because many people have reported "Oh, look. It worked." Does not lower the chances of YOUR 3DS getting bricked. You can get bricked with KTM, and SysUpdater. And, even if they say it will never fail (100% success rate(?)), There is always a chance that it will brick your console. Always.
 
  • Like
Reactions: The_Jesus_2.0
ahem
"this version should be almost brick-proof" note the almost ?
KTM will never, ever be 100% brick-proof. It all has to do with memchunkhax2. If anybody tells you otherwise they are lying and you are naive for believing them.

And are you really going to take the word of JustPingo and Mrrraou over the guy who helped fix sysupdater?
 
  • Like
Reactions: DKB
KTM will never, ever be 100% brick-proof. It all has to do with memchunkhax2. If anybody tells you otherwise they are lying and you are naive for believing them.
i had thought that memchunkhax2 was to get the privileges... and sysupdater downgrades one way.. ktm will downgrade in another way..
dunno.. i just wait..tomorrow is the day he said will be released...if he does and is good i use it if not well .. i may take a chance with sysupdater before 10.4 time will tell.
 
KTM will never, ever be 100% brick-proof. It all has to do with memchunkhax2. If anybody tells you otherwise they are lying and you are naive for believing them.

And are you really going to take the word of JustPingo and Mrrraou over the guy who helped fix sysupdater?

This x1000000.
It's not the app, it's the exploit. You want to wait for KTM? Go for it. However, the chance to brick will still be there.. SysUpdater is just fine for what it is.
 
i had thought that memchunkhax2 was to get the privileges... and sysupdater downgrades one way.. ktm will downgrade in another way..
dunno.. i just wait..tomorrow is the day he said will be released...if he does and is good i use it if not well .. i may take a chance with sysupdater before 10.4 time will tell.

The issue right now is time. If you wait too long to downgrade, and get screwed by something going wrong, then you'll have to update to the latest firmware with nintendo's official servers. Because, if you use a application to do it, things will might only get worse. When 10.4 comes out, all of this is going to change.
 

Site & Scene News

Popular threads in this forum