Hacking PSA: The upcoming kernel exploit works on ALL firmware versions!
- Thread starter FusionGamer
- Start date
- Views 35,107
- Replies 128
- Likes 3
There isn't, it's just DNS is the second easiest thing if you can't use router to block.
I've looked all over these forums. I'm on firmware 1.99 and don't want to update so I lose the exploits. I want to play MK8 and Smash Bros but those will update off a disc right? Can I change one bit of information between the processor and crystal looking thingy to unlock the region? If I scratch my MK8 disc would it let me play without updating? I bet I can find a way to use amiibo without the 5.3.2 update. Would you do it?
You're making exploits for 5.3.2 because it makes the mat sense but I want to he sure, should I update to 5.3.2? Should I be an idiot and stay on 2.99 to try and have you waste time making an exploit for my old version because I'm ignorant? Just asking as I can't find answers. Credit me if my changing of one bit idea works.
Seriously, block with a mac address on your router. Then unblock with one click to go back online. Thanks for sharing updates and handling the ignorance, lol. Somebody might cr6, "I blocked it all and played MK8 online...I was updated to 5.4!!!"
Wow. It's a perfectly valid question, albeit one that may have already been answered somewhere. It would be interesting to see how mouthy and aggressive people are if they weren't hiding behind their keyboards and computer screens.
In extremely oversimplified terms, the IOSU controls the security of the hardware thus would need to be exploited in order to use 'backup' games as well as any kind of access to the system software. I believe the kernel exploit should still suffice to grant hardware access to homebrew applications, however.
In extremely oversimplified terms, the IOSU controls the security of the hardware thus would need to be exploited in order to use 'backup' games as well as any kind of access to the system software. I believe the kernel exploit should still suffice to grant hardware access to homebrew applications, however.
Seen as you are from the UK I will take pitty and help you
1. You can update to the latest FW 5.3.2 on your WiiU at this time and the homebrew hack will work through the browser.
2. Yes I presume you wanted to know, you will eventually be able to play backups.
3. An emunand will be in place eventually so you can do all sorts of cool stuff.
4. Just be patient and let these guys do the work, it will happen very soon I would imagine.
I hope this helps you
Edit: If I'm not right about something, I'm sure some of the guys that are in the know will correct me and help. I wish them all the best!
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 45
- Location
- Engine room, learning
- XP
- 15,649
- Country
I'm wondering how will be working the NNID link with any future emuNAND.
I know emuNAND doesn't exist yet and talking about its feature or behavior is probably useless. Don't take this post the wrong way.
I currently have no NNID on the console.
If I update to 5.3.2, don't create NNID, then Nintendo release v6.0, will I be able to create a NNID without updating to 6.0?
If I need 6.0 to create NNID, I suppose I need to create it now on 5.3.2 before an update is available as NNID is managed at the console boot screen and boot screen will probably never be part of emuNAND as the exploit entry point is an application not the boot process like bootmii on wii.
if NNID creation doesn't require latest version, then it's fine and I can create an account just before creating EmuNAND 5.3.2.
I guess we will not be able to create NNID while emuNAND is already created or inside EmuNAND as account data will not match from the boot account and the emuNAND account info.
Unless emuNAND will have its own account management and will not use the console's boot accounts.
I was only thinking out loud.
putting text to my thoughts wondering if I should create NNID now or later.
I guess linking at least one NNID account now to be safe is better.
I know emuNAND doesn't exist yet and talking about its feature or behavior is probably useless. Don't take this post the wrong way.
I currently have no NNID on the console.
If I update to 5.3.2, don't create NNID, then Nintendo release v6.0, will I be able to create a NNID without updating to 6.0?
If I need 6.0 to create NNID, I suppose I need to create it now on 5.3.2 before an update is available as NNID is managed at the console boot screen and boot screen will probably never be part of emuNAND as the exploit entry point is an application not the boot process like bootmii on wii.
if NNID creation doesn't require latest version, then it's fine and I can create an account just before creating EmuNAND 5.3.2.
I guess we will not be able to create NNID while emuNAND is already created or inside EmuNAND as account data will not match from the boot account and the emuNAND account info.
Unless emuNAND will have its own account management and will not use the console's boot accounts.
I was only thinking out loud.
putting text to my thoughts wondering if I should create NNID now or later.
I guess linking at least one NNID account now to be safe is better.
personally i would make a NNID know so then when a copy is made you will have that access. just a personal opinion though
Cyan: Considering you can just load Nintendo Network's libraries (they're readily available), if you know what you're doing, it's possible to send a command to their servers to register one, along with deleting and freeing from a console
- Joined
- Apr 22, 2007
- Messages
- 1,567
- Trophies
- 0
- Location
- The Netherlands
- Website
- www.hyrule.net
- XP
- 737
- Country
So... I am tempted to prepare for an exploit now.
Should I update today in a few hours from FW 2.1.0E to the latest EUR fw? (As in, is the latest FW still exploitable today)
Should I update today in a few hours from FW 2.1.0E to the latest EUR fw? (As in, is the latest FW still exploitable today)
would blocking these url's just block the wii U end or botht he 3ds end too? prolly a stupid question but better safe than sorry.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 45
- Location
- Engine room, learning
- XP
- 15,649
- Country
It will block Wii, WiiU and 3DS.
Servers might differ from user to user.
Here is what I noticed:
nus.cdn.shop.wii.com : seems to be used by Wii and WiiU, based on wiimpersonator log
nus.cdn.wup.shop.nintendo.net : the server I'm connected to when updated my WiiU
nus.c.shop.nintendowifi.net :
nus.cdn.c.shop.nintendowifi.net : the server I'm connected to when updating my 3DS
nus.wup.shop.nintendo.net : Main URL to check if servers are available. Blocking this URL alone should block all eshop access (eshop and updates)
ccs.wup.shop.nintendo.net : blocking this URL is also blocking updates
Blocking only nus.cdn subdomain without blocking the others has strange result.
the console downloads all the update files, but is probably storing the HTTP answer inside ("403 forbidden"). after download it tries to install and fail. On next boot it deletes the files.
It might allow access to eshop without allow updating. though, it seems like it's updating so it might be frightening or not recommended to download fake file content.
Similar threads
-
- Portal
- No one is chatting at the moment.
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
-
-
