Homebrew RIP [KTM]

[Rinnegatamante]

julian made 2 versions which he stated in this post:
http://gbatemp.net/threads/safesysu...e-your-brick-story.412245/page-2#post-6028179

Probably he miswrote: https://github.com/Myriachan/libkhax/pull/12

 

[Mrrraou]

no. people have more bricks using safesysupdater than just using julian's libkhax sysupdater.
http://gbatemp.net/threads/safesysupdater-vs-sysupdater-share-your-brick-story.412245/

I used it too. And I risked a brick, yeah. Ended with franken firmware, fixed it with OOT3D. I thought it was doing its job fine. Sorry about this.

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

Probably he miswrote: https://github.com/Myriachan/libkhax/pull/12

IIRC he ported mch2 to libkhax, but not sure about this. But I know he used libkhax. That's why the application start is different from TuxSH's build (TuxSH used sulib)

 

[Joom]

Remote downgrade? You mean via Skype or phone instructions? With a person who is kinda clueless about what she is doing? No, too tedious.

You could at least do the file transfers and whatnot via something like TeamViewer. The actual operations on the 3DS are cake, even for someone doing it for the first time.

 

[kje123]

Holy mother of necrobump. 0-0

As for downgrading, I used Safesysupdater, and it worked the first try. Just make sure you're using the right firmware CIA's, lest you'll end up with a really nice paperweight.

 

[gnmmarechal]

Holy mother of necrobump. 0-0

As for downgrading, I used Safesysupdater, and it worked the first try. Just make sure you're using the right firmware CIA's, lest you'll end up with a really nice paperweight.

pretty sure safesys checks if the cia's are the correct ones for the system when it checks the hashes.

 

[kje123]

pretty sure safesys checks if the cia's are the correct ones for the system when it checks the hashes.

You can never be too safe.

 

[Mrrraou]

pretty sure safesys checks if the cia's are the correct ones for the system when it checks the hashes.

It does.

 

[gnmmarechal]

You can never be too safe.

true that.

 

[Kristjan Kütaru]

You can never be too safe.

And this is the reason why I don't do "Downgrade via a Skype call" with a person who does not know the difference between RAM and HDD.

 

[Joom]

And this is the reason why I don't do "Downgrade via a Skype call" with a person who does not know the difference between RAM and HDD.

I didn't suggest a Skype call, did I?

Holy mother of necrobump. 0-0

I've seen worse. So have you, apparently

 

[Kristjan Kütaru]

I didn't suggest a Skype call, did I?

Yeah, but i cannot do the real downgrade via Teamviewer, only the firmware download and SD manipulation part. I have 0 control over the process after that. So the program that handles downgrading on the 3DS side should be really foolproof and i dont feel that systemupdater (when i used it i mean, maybe times have changed, but from the discussion i dont feel it.) was exactly that. If a person does not know what she is doing things will be dangerous. But hell, this discussion does not lead us anywhere, lets send this thread back to the graveyard it apparently belongs.

 

[Santaros]

Yeah, but i cannot do the real downgrade via Teamviewer, only the firmware download and SD manipulation part. I have 0 control over the process after that. So the program that handles downgrading on the 3DS side should be really foolproof and i dont feel that systemupdater (when i used it i mean, maybe times have changed, but from the discussion i dont feel it.) was exactly that. If a person does not know what she is doing things will be dangerous. But hell, this discussion does not lead us anywhere, lets send this thread back to the graveyard it apparently belongs.

Sysupdater is inherently unstable, but that's a side effect of the exploit that is being used. There really isn't anything that can be done about other than using another exploit, of which there really aren't any.

 

[Kristjan Kütaru]

Sysupdater is inherently unstable, but that's a side effect of the exploit that is being used. There really isn't anything that can be done about other than using another exploit, of which there really aren't any.

You misunderstood what i meant. Foolproof !=stable