Homebrew [KTM Release] Tomorrow

[DKB]

Yeah, like the fact I can't update my emuNAND to 9.5 (N3DS). x)

Personally I updated mine to 9.5, but I'm dying for GW or someone to make emunand 10.3..or even..10.4..oh boy.

 

[Ruby Gloom]

I think that's okay, if if means we get KTM sooner than it doesn't matter to me

Let's just wait until he/she is done. The better implemented the code is, the better.

 

[toto9992]

Personally I updated mine to 9.5, but I'm dying for GW or someone to make emunand 10.3..or even..10.4..oh boy.

Yeah, that would be even better ! *.*

 

[dpad_5678]

so basically you are releasing it today right ?

OMFG Be Fucking Patient.

 

[cvskid]

Yeah, like the fact I can't update my emuNAND to 9.5 (N3DS). x)

For now you can use game updates and dlc in .cia format instead of using the eshop and use firmware spoofed games.

 

[toto9992]

For now you can use game updates and dlc in .cia format instead of using the eshop and use firmware spoofed games.

Yeah, and that's awesome, but I would love to be able to use my official cartridges on certains games that need firm 9.9 and above. ^^

 

[dpad_5678]

Yeah, and that's awesome, but I would love to be able to use my official cartridges on certains games hat need firm 9.9 and above. ^^

 

[Tyler Martin]

OMFG Be Fucking Patient.

dont be rude MY GOD

 

[Alpuy]

It is really easy to make a downgrader that does not brick, delete and copy the safe cia, if it fails, retry with the safe cia if it succeeds, continue with the rest of the cias. That way if something fails, there is either the safe cia correct or the other cias correct.
Is that what you do? @JustPingo

An idea that I have is that you can make an app that only changes the safe cia. So the user has to execute that first successfully. Once its executed successfully the user executes another app that installs the rest of the cias. That way there is no risk of brick. What do you think?

Edit: its the same as copying the safe cia first with the condition that it does not continue if it fails

 

[Cloud9Skywalker]

@JustPingo,

Two Questions.

1. Once this is released will you be making a dedicated thread with a tutorial or guide to help with the process?
2. (This isn't really directed towards you.) What is the deal with n3ds users only being able to access Emunand Firmware 9.5? I feel like it's such a drag not being able to have complete access to Internet based features and having to find a workaround for this issue. I mean, really?​

 

[Juiss]

@JustPingo,

Two Questions.

1. Once this is released will you be making a dedicated thread with a tutorial or guide to help with the process?
2. (This isn't really directed towards you.) What is the deal with n3ds users only being able to access Emunand Firmware 9.5? I feel like it's such a drag not being able to have complete access to Internet based features and having to find a workaround for this issue. I mean, really?​

https://gbatemp.net/threads/aes-key-scrambler.406951/

 

[Cloud9Skywalker]

https://gbatemp.net/threads/aes-key-scrambler.406951/

When I clicked that linked and attempted to understand what was being discussed in that thread even with the basic knowledge I have for technology lol. It hurt my head a bit . I'll attempt to take a second look at it again and read word for word soon when my brain refreshes lol. Thank-you though!

 

[EpicLPer]

When I clicked that linked and attempted to understand what was being discussed in that thread even with the basic knowledge I have for technology lol. It hurt my head a bit . I'll attempt to take a second look at it again and read word for word soon when my brain refreshes lol. Thank-you though!

For dummies: There's a hardware component in the 3DS's which prevents us from having all the fun we want to have.

 

[HeyItsJono]

When I clicked that linked and attempted to understand what was being discussed in that thread even with the basic knowledge I have for technology lol. It hurt my head a bit . I'll attempt to take a second look at it again and read word for word soon when my brain refreshes lol. Thank-you though!

N3DS has an extra layer of security built in which prevents updating past 9.5. Keys are needed for v9.6+ and but we only know them for 9.5 and below was the gist I was getting from that thread. It's not the devs' fault we're stuck on 9.5, it's just really difficult to crack the extra security that is preventing us from upgrading. I also hear that even if they do find the new keys for 9.6+, Nintendo can just push new keys in an update and we'll be stuck below that firmware all over again. So basically they need a better way to beat it than just finding the keys, I believe. I'm no expert tho.

 

[Nyannurs]

Don't get me wrong, I don't have anything against him. But a lot of people myself included kinda stopped caring after the first few times.
Like I said, the first time was understandable, they tried. It just turned out what they were trying wouldn't work.
But then he was gonna be working on SNShax and would be making KTM to take advantage of SNShax so that N3DS users on 9.3-10.1 could downgrade earlier than the others without having to wait for memchunkhax2. Then he stopped because it turned out he had to write ROP and decided to can it because the people working on memchunkhax2 would have sysupdater ready soon enough anyway.
A lot of people were waiting for KTM regardless (and a lot still are), but at this point it just gets delayed because no-one can or is willing to beta-test it, or people have already downgraded using memchunkhax2 + sysupdater.

I mean, can't really blame it on him if there's no-one for beta-testing, but everyone with a hardmod would just have already downgraded to 9.2 with sysupdater long ago and most likely don't really care about KTM anymore. And a lot of people just gave up and lost faith because he had never delivered on anything so far.

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?????????????

 

[Juiss]

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?????????????

wat

 

[Quantumcat]

No more "realse" "tomorow"? Sad

 

[Mr_sephiroth]

No more "realse" "tomorow"? Sad

this thread has the best title
because it says tomorrow and then tomorrow and so on, he had already thought about the delay

 

[Urbanshadow]

@JustPingo How's the execution rate during your tests? Has improved over sysUpdater? Some people had trouble running it from some entrypoints.
It will be safe to launch on 9.2 or lower devices to update/downgrade to 9.2? If so, is an arm9 release expected for 4.X systems? Would KTM be able to "clean" sysUpdater downgrades?

 

[JustPingo]

@JustPingo How's the execution rate during your tests? Has improved over sysUpdater? Some people had trouble running it from some entrypoints.
It will be safe to launch on 9.2 or lower devices to update/downgrade to 9.2? Would it "clean" sysUpdater downgrades?

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.