You failed somewhere, redNAND have sigpatches and don't even check if the .tmd/.tik is right...
So the .h3/.app are fucked up, the file you provided while packing are fucked too then
You failed somewhere, redNAND have sigpatches and don't even check if the .tmd/.tik is right...
So the .h3/.app are fucked up, the file you provided while packing are fucked too then
Right, as why i said it's 100% safe.
But at the same time, even though you can just format the SD card, maybe the first line of protection other people should take is to know what they are doing. Eliminating the need to do that.
This. Priiloader/Bootmii alldey
read full point, was refering to the fact any changes you make incorrectly will result in brick on sysNAND but not redNAND
I dont know what happens then. I get error code 0xFFFBF442. Verify title.tik and WUP files ar correct & complete.
NUS packer made installation files should work on iosu cfw (yes calling it that now cause Nexocube is triggered lol) as it has sig patches but for some reason it thosen't and I have no information on why it thosent but apparently it should on REDNAND
From my latest findings:
0xFFFFFFFFFFFBF442 (-265150)
ES_ERR_VERIFICATION
Causes:
Wrong title.tmd
Sysnand is enough for most. Nobody really needs brick protection as long as they install games.
I have been corrupting files and stuff then installing to see if the brick. The either don't install or partially install.
Rednand is good if you need added protection.
Most users don't
Ninty has a 1% chance of throwing out a new update so no issue
I have been corrupting files and stuff then installing to see if the brick. The either don't install or partially install.
Rednand is good if you need added protection.
Most users don't
Ninty has a 1% chance of throwing out a new update so no issue
@KevinX8, hey, add "sysNAND will never support coldboothax to iosuhax sysNAND." to the sysNAND cons.
--------------------- MERGED ---------------------------
--------------------- MERGED ---------------------------
*bricks*
um where did you get this info from? this thosent even make sense considering the way rednand and iosu cfw are launched are in the exact same way
The current coldboothax requires replacing sysNAND's default title, therefore when you load iosuhax for sysNANd it'll automatically load homebrew in a bootloop.
Can one of you coders point me to what I need to change to stop iosuhax making the screen red during boot?
https://github.com/FIX94/iosuhax
https://github.com/FIX94/iosuhax
oh yeah lol I saw someone do youtube vid of that and it happened to him, like I said coldboot hax is no good until we get boot0 cfw
Why do you put lines after you type.
Like this? But seriously, it's safer and a better solution, you're all basically using PastaCFW.
--------------------- MERGED ---------------------------
And, uh no? It's perfectly fine and works with redNAND, just doesn't work with sysNAND?
Thats the magic word.
The current coldboothax is shit.
Once Salt Releases a proper cfw you won't be able to update to it because they stated it might not work with the current rednand. Not only that but you can't boot sysnand and edit system.xml. Now I don't know about you but I hate being stuck with something outdated
Last edited by xtheman,
OK let me chime in here as well.
*** Do not attempt ColdBoot ***
If you try that shit you are going to brick.
Let me explain real quick like.
Stage:1 Hardware checks software in mlc, hardware loads software AKA System OS.
Stage:2 OS checks sigs and whatnot for OS related security, I.E. Games and titles.
Stage:3 We boot isouhax through OS, in a vulerability within OS.
Stage:4 You want to patch files checked in OS by hardware?
Stage:5 You decide to make these changes then wonder why the fuck you bricked, because you can't tell hardware the files in OS are legit.
Stage:6 You post here whining about shit and we laugh at you.
Stage:7 After reading this, you decide not to *** Brick your WiiU ***
*** Do not attempt ColdBoot ***
If you try that shit you are going to brick.
Let me explain real quick like.
Stage:1 Hardware checks software in mlc, hardware loads software AKA System OS.
Stage:2 OS checks sigs and whatnot for OS related security, I.E. Games and titles.
Stage:3 We boot isouhax through OS, in a vulerability within OS.
Stage:4 You want to patch files checked in OS by hardware?
Stage:5 You decide to make these changes then wonder why the fuck you bricked, because you can't tell hardware the files in OS are legit.
Stage:6 You post here whining about shit and we laugh at you.
Stage:7 After reading this, you decide not to *** Brick your WiiU ***
It is until a better solution comes out. You know once coldboothax is installed you can't uninstall it. So when a better hax comes out your wii u will be booting into a not as good back.
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
@
SylverReZ:
You can make a post on the DS forum about your findings, and they'll do their best to respond. They have a GBAtemp account here, you know. -
@
Materia_tofu:
oh ye i made a post i did forget they had an account i prob shouldve tagged them in the post+1
tbh -
-
-
-
-
@
BakerMan:
Update on my brother: He's home now, tired and hungry, obviously, but other than that, seems to be doing fine.+2 -
-
-
@
BakerMan:
Well, from what I've heard from my parents, he had a seizure last night, perhaps an epileptic episode, fucking died, had a near death experience, my dad called the paramedics, they showed up, took him to the hospital, and he woke up covered in tubes, and started complaining.
-
-
-
-
-
-
