One more question. Since I'm on the previous Atmosphere firmware should I have the corresponding payload.bin?Or will the attached one from Ctcaer work?
It will workOne more question. Since I'm on the previous Atmosphere firmware should I have the corresponding payload.bin?Or will the attached one from Ctcaer work?
You rename the fix to payload.bin and put it in the root of your sd, if you use a mod chip. Also rename it update.bin and replace it in the bootloader folder, especially if you use a dongle.One more question. Since I'm on the previous Atmosphere firmware should I have the corresponding payload.bin?Or will the attached one from Ctcaer work?
Are you sure? I've seen many topics here suggesting using the corresponding Hekate file to the Atmosphere version.It will work
CTCaer somehow fixed performance issues.
CTCaer somehow fixed performance issues
documentation of what?CTCaer posted an updated version of Hekate for those having the error.Can you please link to documentation of that? And what about file based being more prone to corruption?
and what about fusee.bin's location? I see it in the payloads folder together with hekate from cctaer.No, you do not need hekate in the payloads folder. Not unless you also launch some other custom thing besides hekate (and then it doesn't need to be named payload.bin anyway). Generally those are payloads you would launch from NYX which loads from hekate to begin with. Like picklock/lockpick, and other such things.
documentation of what?CTCaer posted an updated version of Hekate for those having the error.
search here:https://github.com/CTCaer/hekate.What? I wasn't asking about the error. I very clearly quoted your comment about performance issues being fixed, so I was obviously asking if you could link to documentation that states performance issues were fixed. You also didn't address the concern about if file based being more prone to corruption was fixed or not.
search here:https://github.com/CTCaer/hekate.
Also, about file-based or partition-based emunand all I know is the same as you that partition-based is more trustworthy
I did it directly from Hekate's tools. The emunand partition is visible to windows, but not readable. When you insert an sd card with an emunand partition, it will ask you to reformat it. DO NOT do that unless you want your emunand partition completely wiped.With which tool did you make the partition for the emunand?Can you see it on windows with the sd card inserted?
So they have legit 1.5TB micro sd cards now i thought 1TB is the biggest cards?I did it directly from Hekate's tools. The emunand partition is visible to windows, but not readable. When you insert an sd card with an emunand partition, it will ask you to reformat it. DO NOT do that unless you want your emunand partition completely wiped.
In the end, I ended up switching to a file based partition and reinstalling all my games. I backed up my saves and transferred them using JKSV. It took a while, but everything is much easier to manage and backup now.
They do:So they have legit 1.5TB micro sd cards now i thought 1TB is the biggest cards?
Anyway, your laziness in "looking" doesn't change facts, of which "lesser chance of corruption", isn't one. Less chance of you deleting or overwriting your emummc files, sure, but no more or less chance of corruption. exfat does that on its own compared to fat32, but that's a different story. Disadvantage is always having threads such as this, where people have a hard time migrating. And this difficulty also causes people to not make backups when/as often as they should.anyway, I did look and didn't see anything specifically stating that CTCaer fixed performance issues. I also wouldn't say there are zero advantages to partition based as urherenow stated. A lesser chance of corruption is certainly a pretty big advantage.
Yes, you can place fusee.bin there, but just remember to update that copy whenever you update Atmosphere. Using fusee.bin more or less takes hekate and its config files out of the picture. It honestly doesn't matter where you put it, as you would either be pointing a payload launcher to it, or adding an entry (pointing to its location) into hekate_ipl.ini anyway.and what about fusee.bin's location? I see it in the payloads folder together with hekate from cctaer.
BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH BLAH
You being a smart ass doesn't change the facts either. Lazy? I looked, moron. How is looking being lazy? You didn't mention ANYTHING about it only effecting resized nands. LMAO! Move your goal posts much? It also doesn't mater what is the cause of corruption, if there is a higher chance of corruption for file based, then there is a higher chance of corruption period. You seem to be about one of the only people pushing that file based is better. Just because some people can't follow directions properly and need to come and create topics for hep, doesn't mean file based is better. It only means it's easier for people who cant follow directions properly. Gtf off your high ass horse with your "laziness blah blah blah" bullshit.
I asked a simple question. if you can't answer without being a smart ass, don't answer at all. Talk to me like that and I'll talk to you like that back. That's how it works, lil guy. Now gtfo.
To be honest you need better stuffs to do, because all you do is bicker with people here.
Says the person trying to bicker with someone. I wasn't the one who came in first with snide and rude remarks and bullshit. I asked a simple question because I genuinely wanted to look at the documentation of performance being improved... which in the end turned out to only pertain to performance regarding a resized emunand. urherenow was full of shit and then tried making me look like the stupid one with rude comments. I simply talked to them the way they talked to me to begin with. Get the order of events correct before you chime in with your shit. Why are you even getting involved? It shows that you want to stir the pot and cause trouble. Go away, fucking troll.
Because you are not helping the thread, you started bickering with uherenow, and beside he isn't the only person you bicker with before, because you bickered with me before, so can't you see, you have a problem.
Can you please link to documentation of that? And what about file based being more prone to corruption?