Yes, that's fully confirmed at the moment. If anything was sent to the server that fully proved that a device was playing it before release date (Going online, SpotPass, etc), it's fully banned, and you're in the status we are in.
- Status
ok just asking before i reinstall everything on a new 3ds thats all, lmao dont want to be stuck with two bans if it is an antitheft system
This may be the best development ever! You never disappoint!I was going to start work on reverse-engineering the Wii networking and then starting work on the 3DS Device-Certs, but then I found something.
There was a file on Dolphin's NAND called device.cert.
Man, this looks familiar!
I tried this for the lelz. I thought it wouldn't work, but it's worth a try. I converted it to Base64, got the DeviceID, set the platform to Wii U, and..
it worked.
The most unexpected thing to happen happened.
This means 2 things:
1. This was solved a while ago. A LONG while ago, like 5 years ago. If Dolphin can generate device certs, we can, especially if it's using an old cert from 2006 and was achieved a long time ago. This further supports that generating movable.seds is very possible.
2. There is hope! Making a method from this wouldn't be impossible.
But, we haven't made anything like a quick patch for this in NTR yet. I mean, I discovered this 2 minutes ago, but just wanted to report this.
That's (mostly) all.
With the ability to generate signed certs like this, are there any more ways for Nintendo to fix it, or is this game over for Nintendo's banning efforts?
The only real way would be to use the CTCert database, but I don't think they'll do it, and here's why.This may be the best development ever! You never disappoint!
With the ability to generate signed certs like this, are there any more ways for Nintendo to fix it, or is this game over for Nintendo's banning efforts?
They can't just put all CTCerts in there. They're constantly being created from production. What if someone buys a Wii U, gets home and finds out that Nintendo hadn't put their CTCert in the database and they have to wait 24 hours?
And that's another thing. They cannot really combine the 3DS/WiiU/DSi/Wii database into one, it's impossible.
So, this has a very very rare chance of actually being patched now, aside from something like adding a header via a software update, but that brings another problem to the table for Nintendo: people not being able to connect because they have an old firmware, and people who can't update.
A few.
YES.
It's probably a matter of days until we have a full method for this.
For now, this is a concept/a huge glimmer of hope.
I wonder if we can generate DSi certs.
So if I understand this part correctly, you mean that adding a header requirement would render users unable to do a System Update over the internet? If that is the case, then it is definitely game over for Nintendo!
I realized that device.cert files can't actually be generated
I feel worse that I jumped to this conclusion that they can and spread it pretty quickly.
I am so sorry
But, that was from a Wii and not a Wii U.
The point is
that Wii certificates do work. Obviously, Nintendo wouldn't have an OpenSSL vulnerability exploited.
I'm assuming DSi certs work too, but we're not at that point in DSi hax yet.
But, this is still hope, because if you have a Wii, that means you can unban yourself, and pretty much everyone on the planet has a Wii.
Since this works with setting the platform ID to a Wii U, this means that there is a possibility that the cert is shared between the Wii U's regular mode and the vWii mode.
So
Since the Wii has no online services except for the Wii Shop Channel (let's face it, nobody uses it, and if you do care, you have a Wii U), once we get a method up to change DeviceID and Device-Cert, you can dump your Wii NAND in BootMii, extract it, get the Device-Cert and actually use it.
This doesn't really mean that all hope is lost, it just means I̶ ̶r̶e̶a̶l̶l̶y̶ ̶n̶e̶e̶d̶ ̶t̶o̶ ̶s̶t̶o̶p̶ ̶j̶u̶m̶p̶i̶n̶g̶ ̶t̶o̶ ̶c̶o̶n̶c̶l̶u̶s̶i̶o̶n̶s̶ ̶o̶r̶ ̶e̶l̶s̶e̶ ̶t̶h̶e̶ ̶a̶b̶o̶v̶e̶ ̶w̶i̶l̶l̶ ̶h̶a̶p̶p̶e̶n̶.̶.̶ that it's just going to be a bit harder. MOST PROBABLY everyone here has a Wii, and dumping the device cert isn't much of a hassle or a risk.
Oh, and if you want to help me and PF2M in our Miiverse hax magic, you know who to contact.
In all seriousness, the worst that can happen is your Wii Shop Channel not working, if we even do get it banned, well, unless you dump it from a vWii, then your entire Wii U will be banned if we ban it if you give us your cert.. yeah.
But they are interchangable, that is right. Nintendo isn't always stupid, they're just trying.
And you know what? They fuckin' deserve it for even thinking console bans were a good idea!
But anyway, if @Joom can actually modify DeviceID in ITCM and have it work, that would be great.
I can't find the signature at the bottom in ITCM, whereas I can find everything else in ITCM.
I feel worse that I jumped to this conclusion that they can and spread it pretty quickly.
I am so sorry
But, that was from a Wii and not a Wii U.
The point is
that Wii certificates do work. Obviously, Nintendo wouldn't have an OpenSSL vulnerability exploited.
I'm assuming DSi certs work too, but we're not at that point in DSi hax yet.
But, this is still hope, because if you have a Wii, that means you can unban yourself, and pretty much everyone on the planet has a Wii.
Since this works with setting the platform ID to a Wii U, this means that there is a possibility that the cert is shared between the Wii U's regular mode and the vWii mode.
So
Since the Wii has no online services except for the Wii Shop Channel (let's face it, nobody uses it, and if you do care, you have a Wii U), once we get a method up to change DeviceID and Device-Cert, you can dump your Wii NAND in BootMii, extract it, get the Device-Cert and actually use it.
This doesn't really mean that all hope is lost, it just means I̶ ̶r̶e̶a̶l̶l̶y̶ ̶n̶e̶e̶d̶ ̶t̶o̶ ̶s̶t̶o̶p̶ ̶j̶u̶m̶p̶i̶n̶g̶ ̶t̶o̶ ̶c̶o̶n̶c̶l̶u̶s̶i̶o̶n̶s̶ ̶o̶r̶ ̶e̶l̶s̶e̶ ̶t̶h̶e̶ ̶a̶b̶o̶v̶e̶ ̶w̶i̶l̶l̶ ̶h̶a̶p̶p̶e̶n̶.̶.̶ that it's just going to be a bit harder. MOST PROBABLY everyone here has a Wii, and dumping the device cert isn't much of a hassle or a risk.
Oh, and if you want to help me and PF2M in our Miiverse hax magic, you know who to contact.
In all seriousness, the worst that can happen is your Wii Shop Channel not working, if we even do get it banned, well, unless you dump it from a vWii, then your entire Wii U will be banned if we ban it if you give us your cert.. yeah.
Um.. yeah, really sorry for this.We have been able to generate properly signed 3DS certs in Dolphin for years and did not even know it! Stupid Nintendo, making certs interchangable between their platforms!
But they are interchangable, that is right. Nintendo isn't always stupid, they're just trying.
And you know what? They fuckin' deserve it for even thinking console bans were a good idea!
But anyway, if @Joom can actually modify DeviceID in ITCM and have it work, that would be great.
I can't find the signature at the bottom in ITCM, whereas I can find everything else in ITCM.
Last edited by Deleted member 355359,
, Reason: fffff
Follow this guide exactly.
https://dolphin-emu.org/docs/guides/nand-usage-guide/
Afterwards when you have a usable NAND in a folder, the device cert is in sys, and the file is device.cert.
There's no current (easy) method to replacing this, so just hold it for now once you have it.
Don't extract it from a vWii.
I think maybe iff @Joom could give you some enlightenment you'll be able to make it work. Why shouldn't dump it from vWii? or wiiu?
keep up the good work guys
vWii has a pretty good chance of sharing the same device cert with the other half of the Wii U. On a normal Wii, this is independent, and getting banned on this will only restrict you from the Wii Shop Channel, though if you get banned on your vWii DeviceID, it's not only over for your vWii, but your Wii U too. The original Wii never had Nintendo Network.
I'm using the arm9loaderhax that was provided, but I keep getting 002-2802 errors
did the arm9loaderhax devices Id get banned? Or is it just me
Ah ok. I see where 1234 is in HXD, its right after Nintendo-API
so im assuming thats where the device id is?
edit: around 0000f1d0
Last edited by craftsygaming,
Well, you can modify it, but Nintendo's patched this completely. Wait for something new to be released.
- Status
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
@
BigOnYa:
@SylverReZ I've never used a disposable, seems like a waste. kinda cool idea tho. It would be nice to have vape built in to a cell phone even. "The iVape"+1 -
-
-
-
-
-
@
K3Nv2:
I was hoping I could add a custom ROM to this fire HD 10 tablet but guess no one's made twrp available -
-
-
-
-
-
-
-
-
-
-
-
-
