Hacking Firmware status

[Jonna]

Yeah im staying on 2.x, would be funny if TX's solderless mod was for 1.x - 2.x and 3.x on wards required a solder job... Lets just sit ad wait

This is actually the primary possibility I thought it was going to be, before price fluctuation or anything else.

 

[SpaceMonkeh]

Yeah im staying on 2.x, would be funny if TX's solderless mod was for 1.x - 2.x and 3.x on wards required a solder job... Lets just sit ad wait

Hope that's not the case for future people that get it. I came in late to the whole 3ds scene and it was a pain for me.

 

[Kafluke]

+1 for a sticky

 

[Deleted User]

neat.

 

[Tempest228]

Basically

1.0.0 now

2.x-3.x soon

4.x soon™

 

[kitzuki]

I believe SciresM still states lower is better but no differences between 2.x -3.0 other than Fuses currently

 

[longlivebrazilusbloader]

I knew it. @SciresM never tested TZhax on 3.01-3.02.

He only tested it on 3.0 and then jumped the gun by saying it worked on all 3.x firmwares. The fact that 3.01-3.02 are receiving content later than 3.0 despite supposedly having the same level of access is proof of that. It also explains why he was reluctant to respond to the people asking about >3.0

In the meantime, he'll be attempting to get TZ level access on 3.01-3.02 in order to transform his premature statement into a reality. I wonder what he'll say if he fails

 

[SciresM]

I knew it. @SciresM never tested TZhax on 3.01-3.02.

He only tested it on 3.0 and then jumped the gun by saying it worked on all 3.x firmwares. The fact that 3.01-3.02 are receiving content later than 3.0 despite supposedly having the same level of access is proof of that. It also explains why he was reluctant to respond to the people asking about >3.0

In the meantime, he'll be attempting to get TZ level access on 3.01-3.02 in order to transform his premature statement into a reality. I wonder what he'll say if he fails

Actually, the opposite is true -- I tested on 3.0.2, but didn't test on 3.0.0 -- I verified the bug was still there on 3.0.0 via code RE.

3.0.1/3.0.2 will get stuff later publically because they don't have the sm bug, and thus require more privilege escalation to use deja vu -- and I may not want to burn said privilege escalation immediately.

 

[Tempest228]

And I may not want to burn said privilege escalation immediately.

Oh boy.

 

[SciresM]

Oh boy.

I can't predict the future -- I'm sure I'll release bugs before they're patched but I'll need to think -- there's a balancing act between blowing everything I've got to get access up through a given firmware and then locking out all future firmwares for all time

 

[longlivebrazilusbloader]

Actually, the opposite is true -- I tested on 3.0.2, but didn't test on 3.0.0 -- I verified the bug was still there on 3.0.0 via code RE.

3.0.1/3.0.2 will get stuff later publically because they don't have the sm bug, and thus require more privilege escalation to use deja vu -- and I may not want to burn said privilege escalation immediately.

If I was wrong, I apologize. I appreciate the clarification about >3.0

 

[Tempest228]

I can't predict the future -- I'm sure I'll release bugs before they're patched but I'll need to think -- there's a balancing act between blowing everything I've got to get access up through a given firmware and then locking out all future firmwares for all time

As I've said before, I look forward to whatever you can cook up for 4.x. I'm guessing hackerone also has a play in there, but minimal as we have no idea what they disclose.

 

[DarkenedMatter]

I knew it. @SciresM never tested TZhax on 3.01-3.02.

He only tested it on 3.0 and then jumped the gun by saying it worked on all 3.x firmwares. The fact that 3.01-3.02 are receiving content later than 3.0 despite supposedly having the same level of access is proof of that. It also explains why he was reluctant to respond to the people asking about >3.0

In the meantime, he'll be attempting to get TZ level access on 3.01-3.02 in order to transform his premature statement into a reality. I wonder what he'll say if he fails

Let's see what you say when you realize he roasted your ass.

 

[Frezgle]

I'm ok with Soon™ for 4.x, I guess d:
(Although it's gonna be pretty hard for me to stay there if Kirby requires something newer, rip.)

 

[Tempest228]

I'm ok with Soon™ for 4.x, I guess d:
(Although it's gonna be pretty hard for me to stay there if Kirby requires something newer, rip.)

The closer we get to release without a new firmware update, the more likely it'll be 4.1, so you should be good.

 

[Thirty3Three]

According to SciresM of the ReSwitched team:

I thought 1.0.0 - 3.0.0 were all the same...? With the same privalges, how is 1.0.0 better? Just with release time?

 

[longlivebrazilusbloader]

Let's see what you say when you realize he roasted your ass.

Are you blind? Or did it take you 20 minutes to write one sentence?

BTW @SciresM gave me every reason to doubt him. He made it seem like he didn't have a 3.02 console for testing exploits, and he didn't give any clarification on 3.01-3.02 until I called him out. I should've done that from the beginning, since he wasn't willing to answer direct questions about it.

 

[the_randomizer]

Interesting, so much for 4.x.x not being hackable.

 

[TheCyberQuake]

Well with access to every game I currently want, and no currently announced titles I'm interested in, I'll be able to hold out on 4.1 until something comes for it.

 

[loler55]

Actually, the opposite is true -- I tested on 3.0.2, but didn't test on 3.0.0 -- I verified the bug was still there on 3.0.0 via code RE.

3.0.1/3.0.2 will get stuff later publically because they don't have the sm bug, and thus require more privilege escalation to use deja vu -- and I may not want to burn said privilege escalation immediately.

Later mean we can wait a few months or more? I hate it to be on 3.01 now and that only for oddesey