Separate names with a comma.
Discussion in 'Wii U - Hacking & Backup Loaders' started by DarkWolfRaiju, Jul 17, 2017 at 1:55 AM.
Ahh, okay. I don't intend to ever play Brain Age.
the speed of loadiine won't matter with something as small as a ds game. I'm talking about games with tens of thousands of files. the DS games r merely roms in a file named rom.zip, so they're compressed roms. they're most likely a single file inside of there.
— Posts automatically merged - Please don't double post! —
btw, u can speed up games in loadiine if they have .cpk or .psarc (perhaps others). Star Fox Zero and Super Mario 3D Land both have .cpk. it's not the size of the game but the number files that is the issue usually with loadiine. both .cpk and .psarc r compressed file formats with thousands+ files sometimes. they both have a folder layout, so u can mimic it with other files to speed up load times. however, as I mentioned, the rom(s).zip file is one file. I remember this from the wupserver installs of haxchi. who knows if Nintendo downloaded the games from warez sites then slapped their name on them. haxchi is basically replacing that rom(s).zip file with something else that's exploitable. the emulators r all NIntendo though; the roms on the other hand - who knows.
Interesting. So, to clarify, it's fairly simple to actually get them on the WiiU, then?
Here's the gist of it.
That guide led to many people not understanding what they had in the beginning. They followed a step by step holding their hands through every step and not explaining each step. This in turn led to users bricking because they never understood the process.
In the beginning it wasn't updated regularly. It left out many steps and instructed users to use one CFW to boot a 2nd CFW to launch and use an outdated corrupt prone 3rd CFW (CBHC to Mocha to Rednand)
It wasnt until extreme pressure from bricked users that the author updated his guide to reflect safer and more proven methods.
We had to deal with almost daily thread creation from frustrated users that followed that guide and didn't understand the hacks that they were using.
Since that time the guide has been updated to reflect more current hacks but it took a while to be updated and almost all of the info had been copied and pasted from here. Why not stick close to the sources?
Almost every Wii U guide on the web is generated from info that first originated in gbatemp. The authors of the hacks themselves (fix94 and dimok) always released their hacks here 1st.
My question is, why would you trust any other guide that doesn't originate from the temp?
Thanks for commenting. Yeah, I have your guide bookmarked for when I pick up my Wii U. Curious if GameStop still sells them in-store, otherwise, I have to rely on Amazon's "Warehouse Deals" to ship me a working system, and hope it has the cables, and Gamepad.
I never wrote a haxchi or hacking guide for the wii u. what I have is this: http://www.psx-place.com/threads/pinkys-wii-u-tutorials.11377/ pinky is me in the psx world. I made godreborn before that though, but pinky is due to my love of pink floyd. one tutorial that u might not find here on temp, despite it being very important, is deleting a fake ticket, but that's only if u've installed a bunch of things, then want to switch to cbhc. with haxchi, the title should fail to install, but only if using from a coldboot; if using from cfw, it won't and result in a false positive. fake tickets can circumvent legit (bought) ones.
I just felt more comfortable with a guide made by the same person who got me through modding my 3ds, though any guides, be it 3ds.guide/wiiu.guide or the ones you guys are recomending, I don't trust any of ya till I get thorough proof that the guide I choose has worked for the most people, the only reason I choose wiiu.guide over thoughs is I get overwhelmingly more people sugesting it compared to this community, the more people who have tested it with success, the more dependable to me
I don't know about any other guide maker (check out my ps3 and 360 guides which r on temp and under the pinky name), but I always go through the steps again while writing the guide to prevent mistakes.
I know that the 3ds guide is the go to standard but that has nothing to do with the Wii U guide. I wouldn't ask a mechanic to operate on my child just because people trust his work as a mechanic.
Since day one that guide has been frowned upon here. I can't control what other sites recommend or how "hundreds" have had success with it. We don't get the "hundreds" coming here for help. We get those that brick because they followed a guide that STILL doesn't have a nand backup step (huge red flag) and they brick because they can't even tell you what kind of hack they are using.
Again, the authors of the very hacks themselves released those hacks here for a reason. Fix94 didn't introduce HaxChi on wiiu.guide. Dimok didn't supercharge the Wii U scene with HBL on wiiu.guide. all other guides and sites are just copies of info that originated here first.
just going go with quick bullet points this time
-the mechanic on a child thing, I get your point but I would feel more like a veterinarian to a pediatrician would be a tad more apt, though a person can have skill in multiple fields
-I do understand that originally, well, it was pretty shitty but it has had a turn around
-and I just poked around and when it gets to the homebrew channel section it does recommend you do a nand back giving a link to that section on how to do it(the site is split into separate chunks for each section of the tutorial)
-I also noticed, it does show at the beginning of each section a little explanation of what the hack does that your working with in the current section
-of course they don't debut there exploits and stuff wiiu.guide , it's exactly that, a guide, ya don't exactly release something in a guide, even folks in the 3ds side don't release their exploits on 3ds.guide so that point doesn't really make sense, gbatemp(I see as a game system hacking forum primarily) has multiple purposes and goes hand in hand with all of these guides for support, alongside the Nintendo Homebrew discord
You do know that the nand backup mention was only recently added based on pissed off users. It went weeks suggesting users install CBHC when there were nand backup tools available. How can you trust an author that doesn't stay on top of recent findings and hacks?
Hey I know how good 3ds.guide is. I've used it lots. When wiiu.guide came out many parts of that same guide were copied and pasted from 3ds.guide with only slight changes. They are not even close in what types of exploits are available. That's when I got my first bad taste for wiiu.guide. It only got worse from there when user after user flocked here for help after following it.
It's not half bad now but we've had to "push rope" to get them to update it properly and/or get users to stop following it blindly just cause 3ds.guide was so good. Writing a great guide does not mean that everything you type up from that point forward is "the gold standard".
RedNAND is not a CFW though.
That belief dates back to the old "fw.img"-based CFW which is no longer in use.
That's what I was saying @Kafluke.
If someone only updates their guide weeks and weeks after a lot of the community has already bricked their consoles with no way to restore their consoles, how can you trust a guide like that?
That makes me think that the person does not care one bit about his guide, so why should anyone else?
And wiiu.guide isn't just a guide, it's a website, wiiu.guide is the domain name. So Kafluke's statement is vaild, and very true. There is a reason why all the latest WiiU modding info gets released on GBATemp first. Because Gbatemp is the number one place to go for all WiiU modding and hacking. And that's not an opinion, thats a fact.
wishing there was a change log, how could the same person be on the point with updating there guide the day of or after an exploit releasing on one of their guides and show such apathy towards another, that's the only thing that isn't clicking for me
First off. It's not "my" guide. There are many contributors. It's a community guide since anyone that shows interest in helping to keep it updated is given access to the OP. One of the things that we work hard on here is to work on things as a group. I'm always soliciting input and making changes based on feedback. I had originally kept an up to date changelog on the AIO for months. When I gathered up all the recent info that was available at the time the OP was really just a wall of text. More a placeholder for the info. Many of us worked on it from there fixing typo's, adding sections and cleaning it up. Honestly I'm glad you mentioned a changelog because I think that's a section that got lost in the shuffle. I will most certainly add it right away.
I really have no beef with wiiu.guide right now. It's been a battle for months but having gone through the guide recently it's up to speed now. I just worry that something is going to change and the authors won't reflect it for some time afterwards causing issues for users once again. They're lucky that the homebrew scene has slowed down considerably making easier for them to keep up.
wo, I wasn't saying about your guide, I wasn't criticizing you, sorry, I didn't intend it to come off that way, I was reffering to the one by plailect and flim flam, and over in the Nintendo Homebrew discord we do talk quite a bit about the guide and what to do to improve it, I suppose there isn't really much to say about it, besides, wtf am I still doing here, I do plan on getting a wii u, but still don't have one, I ended up shifting the money I was about to put into it into the switch :/
Let's take a moment and look at the OP and see how far the topic has digressed lol
ya...kinda sidetracked, hehe *sigh* sorry about that
RedNAND is an emulated copy of the sysNAND. Since it is not official it would technically be a custom firmware. It doesn't matter how its loaded or where it runs. Once you're in it you are no longer using the office built in sysNAND so it's a custom firmware. Semantics really
Also, he doesn't have a Wii U. Directly referring to Plaitect