Homebrew RELEASE ChoiDujourNX - a system firmware installer homebrew for the Nintendo Switch

[SirhanSquared]

Hi, quick question, tried searching but couldn't find an answer.
I have a legit (checked with h2test) samsung 256gb evo select. Whenever I try to update via choidujour, after the file package is checked, it always says I am missing 1 nca file. It doesn't matter which stock OS version I am using and the folder contains the correct number of nca files (which were from Xbins). Using a 64gb samsung microsd however works with the same files. How can I fix the missing 1 nca file error?

The reason this is important it be installed with the 256 gb card is I'm trying to run SX OS 2.3 beta and emunand from the micro SD card. Prior to this, emunand was in the sysnand and the maximum size partition allowed was 25gb and I was hoping to run emunand off the SD to preserve all of the faster switch internal storage for installs.

Thanks!

 

[movietime]

Sorry it this has already been answered in this long thread. I'm trying to find a way to upgrade my OFW to 6.0.1 (from 4.x) using this tool. Is there an option to do this? Whenever I run it, it tries to upgrade the CFW instead of OFW. Any help will be highly appreciated.
I'm running CFW using SX OS.

Thx

 

[Draxzelex]

Sorry it this has already been answered in this long thread. I'm trying to find a way to upgrade my OFW to 6.0.1 (from 4.x) using this tool. Is there an option to do this? Whenever I run it, it tries to upgrade the CFW instead of OFW. Any help will be highly appreciated.
I'm running CFW using SX OS.

Thx

CFW and OFW use the same Switch firmware.

 

[movietime]

Thx Draxzelex. I do see system software ver 4.1 when I boot using OFW option in SX OS and when I boot under CFW, it says the ver is 6.0.1. I also see EmuNAND enabled within SX OS.
When I try to connect to eshop when booting into OFW, it says I have to update my software and I don't want to take any chance to upgrade to 6.2 which is not supported by SX OS currently.
So looking forward for a way to upgrade OFW to 6.0.1 so that I can download eshop games.
Thanks for your continuous guidance.

 

[Draxzelex]

Thx Draxzelex. I do see system software ver 4.1 when I boot using OFW option in SX OS and when I boot under CFW, it says the ver is 6.0.1. I also see EmuNAND enabled within SX OS.
When I try to connect to eshop when booting into OFW, it says I have to update my software and I don't want to take any chance to upgrade to 6.2 which is not supported by SX OS currently.
So looking forward for a way to upgrade OFW to 6.0.1 so that I can download eshop games.
Thanks for your continuous guidance.

To update OFW, you will have to use homebrew, or if you're willing to use RCM and memloader, you can use the homebrew-less ChoiDujour.

 

[movietime]

Thanks a lot Draxzelex. I have been searching the options you provided but couldn't find a single video or instructions on how to upgrade OFW offline All the links I have found only talk about CFW upgrade to the desired version but nothing for CFW.

 

[Draxzelex]

Thanks a lot Draxzelex. I have been searching the options you provided but couldn't find a single video or instructions on how to upgrade OFW offline All the links I have found only talk about CFW upgrade to the desired version but nothing for CFW.

You cannot update to a specific firmware in OFW without hacking/homebrew hence why all of the videos show how to do it with CFW. Your only choices are ChoiDujourNX or ChoiDujour.

 

[DocKlokMan]

You cannot update to a specific firmware in OFW without hacking/homebrew hence why all of the videos show how to do it with CFW. Your only choices are ChoiDujourNX or ChoiDujour.

You can, it just requires a game cart with that update on it.

 

[Draxzelex]

You can, it just requires a game cart with that update on it.

Crap you're right. Although I guess it slipped my mind since I would assume OP wants a free option. Not to mention there is a lack of carts with firmware 6.X...

 

[notimp]

Now whats wrong with calling

- OFW patches a "CFW" because more people would know what to make of the term

- using an emunand (not a real emunand) feature that you dont understand what it does exactly

- asking essentially "how do I update my firmware, or my emunand - I don't know" on SX OS (not a OS), on a forum that doesnt so much care about SX OS in the first place.

Hey this guy now has two firmwares on his nand, probably wants to update both of them, doesnt know which one is emunand (not a real emunand). Go.

Why he has two firmwares on his nand (normal and emunand), nobody knows at this point. Even he wants both of them to be on 6.1.0. And is weary of going oniine with both of them (probably rightfully so).

 

[notimp]

The trolling around here is rampant. People around here from time to time pretend to know things and be helpful even though they are just childish trolls.

This is what mikefor20 did in this thread.

Never mentioned, that after updating his firmware - he is stuck in a bootloop, until four or five posts into the exchange. At this point still never mentioned how he got out of it (?) to try stuff again. Or that he did so.

Proclaiming all the while, that ChoixdujourNX "dont work" which had everyone (ok, at least me) stuck with the impression, that he couldnt boot into the homebrew.

Blindly went into a thing thats supposed to fix ChoixdujourNX not starting up, while proclaiming, that "he did that already" - netting him a different result ("now I get this error message"), still not indicating at any point - that prior to this he could start ChoixdujourNX and now he cant.

After the lingering realization sets in, that this guy might have issues booting the firmware he just installed (which is entirely unrelated to ChoixdujourNX) - verbally berated people (ok, me) for telling him - how to get back to the state he was in - because that tip in the opening posting - is depreciated by now - and caused an issue rather than fixing one (Will do so every time with newer CFWs - so someon should fix this).

In the mean time said sorry tree times, even dropping me a PN with "I appologize!" in the header -

claming he had understood, why not all trolling has to be negative.

Then _finally_ doing what he was told - by the troll - and actually posting an error report that stated, that he was tuck in a bootloop.

Then got angry about the circumstance, that I had him cycle through most likely scenarios first, and even had him revise a step (in detail - so he'd do nothing wrong), he claimed "he'd already done" - and told everyone, that people in here are juste useless trolls, pretending to know things.

While all the while - at least I was clear, that we are trying stuff out here - in order of likelyhood, and that the problem description was bad.

After the word "bootloop" was uttered (not a bootloop either) - in comes another person to help with a "reinitialization might be required".

Why that should have fixed things - we still dont know at this point (updating from a lower firmware to a higher firmware - usually never requires reinitialization), but hey - now it worked.

Also - I wouldnt have ruled out "factory reset" - if I had any inkling, that you were stuck in a bootloop. I hadn't at that point. From my perspective - you couldnt get an app to start because it was crashing. My crystal ball to read minds with still was a bit foggy at that point ("Switch logo? "When you boot into some nsps there is a switch logo." And this guy is using an nsp launcher to launch hbmenu, which is non standard....)

But eff this troll pretending to know things, and not fixing my stuff -

Troll even said - after the crystal ball started working better "if this is what you are experiencing - what I told you will not help" but no...

People around here from time to time pretend to know things and be helpful even though they are just childish trolls.

I must have pretended again... Oh well.

Here is your moral of the story. Get to know your stuff. Give issue descriptions people can actually work with. Dont expect to establish a service "chat" first. Where you then can pretend being angry at the person you havent told jack.

Thats the actual sitrep.

And just for a second try to imagine me realizing, that the guy saying he did a thing before, just did the thing for the first time, and because the thing - even though it was suggested to fix "app not booting" in the first posting, actually might cause new errors on new CFW installations - (because it uses an old naming scheme). (I fixed that mistake only using theorycrafting at this point. - All we got from Mr creative story telling at this point was "It doesnt work after switchlogo".)

Also - funny that we couldnt guide him to a fix straight away - because none of us had this issue before - nor does the way of fixing it make much sense in this instance - but hey "it worked". Let me make a note of that... In me troll-binder.

 

[mikefor20]

This is what mikefor20 did in this thread.

Never mentioned, that after updating his firmware - he is stuck in a bootloop, until four or five posts into the exchange. At this point still never mentioned how he got out of it (?) to try stuff again. Or that he did so.

Proclaiming all the while, that ChoixdujourNX "dont work" which had everyone (ok, at least me) stuck with the impression, that he couldnt boot into the homebrew.

Blindly went into a thing thats supposed to fix ChoixdujourNX not starting up, while proclaiming, that "he did that already" - netting him a different result ("now I get this error message"), still not indicating at any point - that prior to this he could start ChoixdujourNX and now he cant.

After the lingering realization sets in, that this guy might have issues booting the firmware he just installed (which is entirely unrelated to ChoixdujourNX) - verbally berated people (ok, me) for telling him - how to get back to the state he was in - because that tip in the opening posting - is depreciated by now - and caused an issue rather than fixing one (Will do so every time with newer CFWs - so someon should fix this).

In the mean time said sorry tree times, even dropping me a PN with "I appologize!" in the header -

claming he had understood, why not all trolling has to be negative.

Then _finally_ doing what he was told - by the troll - and actually posting an error report that stated, that he was tuck in a bootloop.

Then got angry about the circumstance, that I had him cycle through most likely scenarios first, and even had him revise a step (in detail - so he'd do nothing wrong), he claimed "he'd already done" - and told everyone, that people in here are juste useless trolls, pretending to know things.

While all the while - at least I was clear, that we are trying stuff out here - in order of likelyhood, and that the problem description was bad.

After the word "bootloop" was uttered (not a bootloop either) - in comes another person to help with a "reinitialization might be required".

Why that should have fixed things - we still dont know at this point (updating from a lower firmware to a higher firmware - usually never requires reinitialization), but hey - now it worked.

Also - I wouldnt have ruled out "factory reset" - if I had any inkling, that you were stuck in a bootloop. I hadn't at that point. From my perspective - you couldnt get an app to start because it was crashing. My crystal ball to read minds with still was a bit foggy at that point ("Switch logo? "When you boot into some nsps there is a switch logo." And this guy is using an nsp launcher to launch hbmenu, which is non standard....)

But eff this troll pretending to know things, and not fixing my stuff -

Troll even said - after the crystal ball started working better "if this is what you are experiencing - what I told you will not help" but no...

I must have pretended again... Oh well.

Here is your moral of the story. Get to know your stuff. Give issue descriptions people can actually work with. Dont expect to establish a service "chat" first. Where you then can pretend being angry at the person you havent told jack.

Thats the actual sitrep.

And just for a second try to imagine me realizing, that the guy saying he did a thing before, just did the thing for the first time, and because the thing - even though it was suggested to fix "app not booting" in the first posting, actually might cause new errors on new CFW installations - (because it uses an old naming scheme). (I fixed that mistake only using theorycrafting at this point. - All we got from Mr creative story telling at this point was "It doesnt work after switchlogo".)

Also - funny that we couldnt guide him to a fix straight away - because none of us had this issue before - nor does the way of fixing it make much sense in this instance - but hey "it worked". Let me make a note of that... In me troll-binder.

This is so full of crap it's amazing. My initial post said I was stuck at the switch logo. Told you about the Switch's history(because I believe it matters.)

Hello all! Rajkosto San!
Thank you for all your work. I am trying to update with ChoiDuJour and there is some really wrong. I am on 3.0.1 and I really want to update to 5.1 or higher so I can play a few new titles. Every attempt with ChoiDujourNX resulting a being stuck on the Switch logo, I tried getting the update files from several sources. Formatting the SD in ExFat and FAT32. Tried 3 different SD cards. Tried running Choi under SXOS, ReiNX, Atmosphere and of course RajNX. I am out of ideas except initialize the system. Any ideas? Plus if I initialize the system ill lose my User profile. I want my saves to work. Should I go online and download the profile after initialization? will error logs and such still be present after initialization? Also I noticed on your pastebin there is a BackupUser.Js and RestoreUser.JS.. Could there be a solution? Thank you for your help.

This says everything you need to know. I was out of ideas. Wanted to initialize to eliminate the possibility of something weird , possibly from EARLY HB. It's not a SXOS question. I simply mentioned that I tried all possible OS, including SXOS. Just to eliminate people telling me "Try this CFW" I had never played with maintenance mode so I didn;t know

You would do a factory reset, wont you?

Do you know what FAQ means? Like the FAQ listed in the first posting?



Also, its heartwarming to hear your entire story for why you want to use choixdujournx - but this still isnt a propper error report:

100% Troll. A jerk in every way. This post reads "Hey Dumbass, didn't you read the FAQ? Well I either didn't read or comprehend yours. You would try something different after you tried everything else wouldn't you?" Trolling without helping is still trolling.

Then please provide a proper issue description.

We trolls cant mindread, if you did read stuff or not. (You have to provide us with that information.) So we start with the most likely scenario.

Second most likely scenario interpreting your issue description as "program just crashes upon launch" - as with all instances where everyone says something works - but one guy says it doesnt, is that you have a corrupt file system.

Also - of course, I wont support you on the issue any further. Im no masochist.

(What the mill... doesnt know is that not all trolling is bad. But everyone in his agegroup tells him it is, so he starts to character assassinate people actually trying to help him.)

Then this says Notip(or tip-less is you prefer) can't or didn't read your post. You quote something I didn't say. I never said a "program crashes at launch" When you put something in quotes, it's supposed to be a quote not your interpretation. And full of assumptions. Then you get all butt hurt. As fools do. I tried to calm you down because the only thing worst than a stupid troll is an angry stupid troll and I am not in pre-school. I came here to ask information not fight. There is no good trolling. My age group? Stifle it kid. I said it was stuck at the switch logo.

I am using that build, I can read. Troll

--------------------- MERGED ---------------------------

it copied that version over again in case and now when i click the album I get error 2347-0003 under kosmos.atmo

Informing you that I tried your idea, just in case. I'll entertain the idea.. Even though I had already did it. Why not? I tried it again. Dame result. I am out of ideas and nobody told me about the "initialize without losing your saves/user data" option. So I was looking for a way..

To give anyone wanting to pick up for this consumer a hand - the switch logo isnt supposed to show up at any point in the process - so he is doing some real user error level stuff wrong.

He said, that he already did, whats stated in the faq - when did it "again", then his error profile changed.

Also - kosmos.atmo isnt a thing - and if we start supporting "easy setup bundles" instead of proper installations, we can just hang ourselves beforehand, that saves everyone some time.

I actually might suggest - giving this user some space - to create his own safespace - on the road to finding out, that listing specific error codes, usually doesnt help either. Let him figure this one out. (To prevent the biggest casualties: Factory reset is not a solution.)

WOW, You obvously never used ChoiDujourNX before. Immediately after install it reboots. Then you see the Nintendo Lolgo, then the Switch logo! It's DEFINATELY part of the process. I did wat's in the post before as well. I think the FAQ is depreciated. Kosmos didn't need it. And it caused an error. Kosmos is the new SD files. So it is an iteration of Atmosphere. Read.

I apologize for my attitude I was just following suit. You must admit, you are kind of abrasive...

The "Heartwarming story"was about telling you details.

seems it wants a nro, it's there. ill figure this out yet

Same bootloop

It said to extract to root but didn't say to install the nsp... maybe I should.

This translates to "Calm down little girl, you mock my "Heartwarming" post but obviously didn't understand it. Then a thought outloud about installing the NSP.

Dont install the nsp - this is actually the only nsp you never will install.

edit:

The choixdujournx "app" is an .nro - you will launch it through hbmenu (https://github.com/switchbrew/nx-hbmenu/releases/tag/v3.0.0). (When this tutorial was written accessing hbmenu usually was done through gallery - and not through a menu shortcut, or anything of that sort)

The nx-hbloader (https://github.com/rajkosto/nx-hbloader/releases) linked in the faq, actually also shouldnt be needed with current atmosphere setups... So maybe remove those files from your sdcard again - on second thought. (That one is on me - I'll get into more details on it later).

The intended launch process is as follows:

Firmware (f.e. atmosphere) gets booted up, loads a loader nsp (currently called hbl.nsp (the one in the faq package is called loader.nsp, which makes me weary of recommending using that package - seems "old")), which is the only nsp that you should never install, it gets executed in place. This loader nsp then is responsible for loading hbmenu - when you click on gallery. (hbmenu.nro has to be in root as well.)

This loader nsp also has to provide hbmenu and then choixdujournx with some debug syscalls, which not all of them did in the past, but actually most current ones (Kosmos) should do. If the current one in Kosmos actually does, I dont know - you'd have to ask the package provider. (It should though.)

At no point do you actually actively launch a nsp by clicking on an nsp icon - try to stick to opening hbmenu via the gallery button just to rule out other possible issues ("after the switch logo shows up?"). No switch logo should show up at any point.

So here is what you do.

1. Reboot the system - try if using the hb loader from the faq actually solved your issue (you have to reboot after copying it on the sdcard - or it might not work, if you already did that (= if f.e. you did take out the sdcard which makes you reboot the system), you can skip this step.

2. Remove the files from the hb loader package in the faq from your sdcard again. Reboot the system - try to launch choixdujournx again - this time through the gallery (>hbmenu then choixdujournx). This should work.


If it doesnt.

3. Doublecheck the Kosmos package installation. Maybe copy all the files and folders over again (Dont use MacOS to rule out other potential issues).

If that doesnt work, ask in the Kosmos thread, if anyone has the same issues as you do with Choixdujournx.



Here are known working versions of hbloader ( https://github.com/switchbrew/nx-hbloader/releases/ ) and hbmenu ( https://github.com/switchbrew/nx-hbmenu/releases/tag/v3.0.0 ) that work with current atmosphere (including the sigpatches, if that matters). But - how the hbloader is named (hbl.nsp or loader.nsp), and how it gets the debug permissions, depends on the actual CFW you are using.

So this is where you trust your "package provider" (Kosmos) or do some legwork on your own.

As you see - this isnt the easiest issue to troubleshoot.

And all the while - every issue here could be caused by a corrupt filesystem, and the files on the sdcard being actually faulty - but this time, lets not assume that straight away.

No need to assume any of that if you READ. Once again the "Heartwarming" post says I tries several CFWs, Several SD Cards, Several sources for the update files and even tried both file system architectures. That pretty much renders evrything you said useless and already tried.

Also - if your excellent issue description of "resulting being stuck on the switch logo" actually means, that you successfully launched choixdujournx and flashed a firmware - and are now stuck booting it - which you recovered from HOW?

Then everything I just posted was useless and wrong.

Because at this point this has nothing to do with choixdujournx anymore - but with "my CFW wont boot" - but for that to be the case you really must have skipped heaven and earth in your error description.

Of course none of what you posted immediately makes sense, and you refuse to actually post an error description that isnt a grammatically wrong fragment of a sentence, that actually isnt very descriptive.

("I've tried everything." "Sure. Now whats the issue" "I stuck at the logo." "What, where? Trying to do what?" "I've tried everything, should I factory reset or use javascript applets?")

Wow, it seems you actually read something. YES the switch logo appears at the end of the process. Your intellect is astounding. Have you seen your grammar? lol this isn't high school. Well, maybe for you little boy(girl?) And it has everything to do with ChoiDujourNX installation causing a boot loop. And the question about the Java applets was for Rajkosko. He wrote them. They are on his PasteBin. And He's not an idiot.

The trolling around here is rampant. People around here from time to time pretend to know things and be helpful even though they are just childish trolls.

My original "heartwarming story", as you called it, has all the information you say I omitted.

, I read fine. And my "story" states that I ran Choi, its obviously not a problem getting in to HBL. I'll entertain your theory as I am out of guesses and why not..

I did provide a description. It seems you make an effort for a second. It looked that way at least so I stroked your ego a bit to try to get you to be civil. What a waste of time. And trolling is bad. You call out people for BS. Confusing the issue and pissing people off without any real knowledge to back it up. You didn't even read my posts.



Here's were you really let your troll self show. The Switch logo show AT BOOT, Like I said. Just because your comprehension is sub par does not mean I am wrong. There is no error code in a boot loop. Troll, I mean try again. The only error code happened after I put the HBL with svc mode title files you liked to. That was the only error.. and you caused it. You didn;t need to interperate my statement. I speak english, and Kosmos , is SDfiles, SD files IS Atmosphere setup. I said Kosmos/Atmosphere to let you know it was up to date. If you knew your stuff and read my "story" you would know that.



I already ruled all this out too IF you read my Heartwarming story. I understand how to run homebrew. I am not new to this. I am not asking how to run Choi. I just want to update WITHOUT A BOOTLOOP.

1. plenty of reboots, the HBL from the FAQ was tried early on in my process. I may have installed the damn nsp though. Not sure was weeks ago.
2. I have launched Choi through Atmo, Kosmos, ReiNX, RajNX and SXOS all with the same result. Like I said in my Heartwarming story.
3. I tried re-downloding EVERY file,4 SD cards, Fat32 and ExFAT and several sources for the update files. Like I said in my Heartwarming Story. Did you even read this stuff?

Why would I ask in the Kosmos thread? EVERY CFW GETS THE SAME RESULT. IT'S NOT KOSMOS SPECIFIC. READ




Once again, yes NoTip, everything you post is useless. It has everything to do with Choi or something lingering on my system from prior fuckery. Or maybe something I am not seeing. Before I came here I already tried all your solutions. They are all obvious. Same boot loop. Next thing is make sure my system isn't causing it. Some ghost in the machine. So I was wondering how to stay offline, do a system initialization and not lose my save games. I know how to read so I am aware initialization will delete my user profile, which my saves are linked to, rendering my saves useless. Rajkosto, who wrote ChoiDuJour in case you didn't comprehend that post either, wrote a JavaScript to Backup/Restore user. It's in his PasteBin. I was asking if I could use that to backup my profile, initialize the system, and the restore user without going online. That's when you stepped in . confused the issue, and took me on a wild goose chase. I happily followed because I am running out of ideas.

I hope that the mods don't cut this to hell. I hope they at least leave the information in there so I can find a solution,. Hopefully Rajkosto will read this. He might have an idea. This issue may occur again to someone else. and this may be useful in the future. I promise a full write up of any solution I find.

So just one more time in case so mods have something good to leave behind. I am attempting to update from 3.0.1 to 5.1 or higher so I can play new titles. My Switch is a launch switch. The update history is as follows. I updated from 1.0 to 3.0 using CDN to download the Zelda DLC 1. Haven't been online since. I update to 3.0.1 using the SMO cart, to 3.0.2 using Xenoblade 2 cart. Back down to 3.0 with Hekake as it was my "Cleanest" backup after my first Choi boot loop.. then back up to 3.0.1 with SMO again. I sold Xenoblade 2. fuse count is 4 burnt fuses.(3.0.1-3.0.2)

I do not wish to go online until/IF a proven unbanable solution exists. I am trying to use ChoiDuJourNX to update offline. I have tried running Choi under all current CFWs (Rei ,Raj ,Atmo/Kosmos and SXOS) All go through the process and get stuck on a bootloop switch logo at boot. I have tried 4 different SD cards now. it's not the card. Tried ExFAT and FAT32, and tried Windows disc manager, panasonic Sd formatter and gpart to format. It's not the file system architecture. Tried 4 sources for the update files. Tried to install 6.0, 5.1 and 4.1 Not the files. I tried to boot after install, on all firmware listed, with all CFW as well. Same boot loop. To fix the loop I have restored a backup made and restored with SXOS and tried my backup made and restored with Hekate. All restore fine. Then I try again and get another loop. I am wondering if it's something in my console so I want to initialize. But I want to be able to restore my User profile without going online.

I think a few months ago I installed the NSP in the FAQ (nx-hbloader with debug svcs enabled)..oops. Also, it may be pertinent to mention I can't get HDD loading to work right on SXOS but I think it's a power issue. I am waiting on a y-cable, that's another issue.

Anyone know how to backup and restore user profiles? Any other ideas to get updated? I might go get a used Octopath to update then return it... I am hoping for something a little easier..

This one is self explanatory. It shoots down your garbage and asks the adults in the thread for an answer.

Tank you for your constructive reply. I havent used the ChoiPC version. Maybe that's a shot. I am backing up my saves now and I will initialize soon.(fingers crossed) I may go pick us a used octopath traveler, use it to update to 5.1 and then return it but I will initialize first,

Anyone now if initialization, for sure, kills the store error reports and stuff? If It does I could go online and update I suppose. But first wait for 6.2 compatible CFW..



I FIXED IT!! Here's what I did for anyone else.

1. Backup saves with Checkpoint
2. Backup SD
3. Put Kosmos and a fresh Download of 5.1 on my 4 GB SD
4. Boot in to hekate and remove AutoRCM.(I was on 3.0.1 and so were my fuses so meh. Not sure if necessary but I couldn't get in to maintenance mode without disabling AutoRCM for some reason.
5. Boot in to Maintenance mode
6. choose to initialize without deleting saves and profile.(maybe backing up saves was pointless?)
   
7. boot in to hekate--.HBL-->ChoiDuJour->install 5.1

This time it worked. Something in my Switch was fucking it all up. Only thing is IF I had deleted the user profile I think my old error logs go with it... Maybe I will

This post thanks the human being who responded and tells you my results. It works. It was something in my system from a long time ago. Probably some old homebrew. The next "post" I will insert replies in to because iit;s just too much. Responses in Bold Italics.

This is what mikefor20 did in this thread.

Never mentioned, that after updating his firmware - he is stuck in a bootloop, until four or five posts into the exchange. At this point still never mentioned how he got out of it (?) to try stuff again. Or that he did so.

I said stuck on switch logo in the first post. Any non-troll who has done this before knows that's a boot-loop.

Proclaiming all the while, that ChoixdujourNX "dont work" which had everyone (ok, at least me) stuck with the impression, that he couldnt boot into the homebrew.

Never said Choi don't work. Funny you use quotes on that. And you are the only fool who assumed all the details. I said I ran Choi, Several times. Read troll.

Blindly went into a thing thats supposed to fix ChoixdujourNX not starting up, while proclaiming, that "he did that already" - netting him a different result ("now I get this error message"), still not indicating at any point - that prior to this he could start ChoixdujourNX and now he cant.

I never said Choi didn't work. I said there was a freeze on the Swith logo. I already clarified this to be a boot-loop. Same thing.

After the lingering realization sets in, that this guy might have issues booting the firmware he just installed (which is entirely unrelated to ChoixdujourNX) - verbally berated people (ok, me) for telling him - how to get back to the state he was in - because that tip in the opening posting - is depreciated by now - and caused an issue rather than fixing one (Will do so every time with newer CFWs - so someon should fix this).

Your demeanor is what got you "berated" You are inflamatory. And kind of a Pud. I bet you are a fat virgin with back tits.

In the mean time said sorry tree times, even dropping me a PN with "I appologize!" in the header -

claming he had understood, why not all trolling has to be negative.

I said sorry for my attitude, yes. You pushed some buttons and I thought "Maybe I over reacted." Like an adult, I apologized. I never said trolling is good. I just didn't want an angry troll derailing yet another thread. You are the worst! A cancer. So self absorbed. Trolling IS negative.

Then _finally_ doing what he was told - by the troll - and actually posting an error report that stated, that he was tuck in a bootloop.

I humored you, and YOU caused the error. It had nothing to do with the original problem. More Troll shit.

Then got angry about the circumstance, that I had him cycle through most likely scenarios first, and even had him revise a step (in detail - so he'd do nothing wrong), he claimed "he'd already done" - and told everyone, that people in here are juste useless trolls, pretending to know things.

While all the while - at least I was clear, that we are trying stuff out here - in order of likelyhood, and that the problem description was bad.

If you read my posts, you would know what was tried. Read Troll

After the word "bootloop" was uttered (not a bootloop either) - in comes another person to help with a "reinitialization might be required".

Why that should have fixed things - we still dont know at this point (updating from a lower firmware to a higher firmware - usually never requires reinitialization), but hey - now it worked.

It was probably something in there that was messing it up. What IDK And I DON"T CARE. I had told yuou plenty of times what's up. YUou are just trolling. I posted what worked for me. Like a good Temper. To help someone in the future and to spread knowledge. You just antogonize and suck, Like all Trolls.

Also - I wouldnt have ruled out "factory reset" - if I had any inkling, that you were stuck in a bootloop. I hadn't at that point. From my perspective - you couldnt get an app to start because it was crashing. My crystal ball to read minds with still was a bit foggy at that point ("Switch logo? "When you boot into some nsps there is a switch logo." And this guy is using an nsp launcher to launch hbmenu, which is non standard....)

Inkling?? READ. And the reset DID help.

But eff this troll pretending to know things, and not fixing my stuff -

NOW YOU FINALLY ADMIT IT!!


Troll even said - after the crystal ball started working better "if this is what you are experiencing - what I told you will not help" but no...

I must have pretended again... Oh well.

Well you pretend to read the post you troll so why not? NO CRYSTAL BALL REQUIRED.

Here is your moral of the story. Get to know your stuff. Give issue descriptions people can actually work with. Dont expect to establish a service "chat" first. Where you then can pretend being angry at the person you havent told jack.

Thats the actual sitrep.

Moral of the story is to expect a dumb dick child troll to derail every thread. They can't read and they defiantly make shit up. Go away troll.

And just for a second try to imagine me realizing, that the guy saying he did a thing before, just did the thing for the first time, and because the thing - even though it was suggested to fix "app not booting" in the first posting, actually might cause new errors on new CFW installations - (because it uses an old naming scheme). (I fixed that mistake only using theorycrafting at this point. - All we got from Mr creative story telling at this point was "It doesnt work after switchlogo".)

WOW, There's that stellar grammar again. I tried the solution in the FAQ long ago with SDFiles.. Had this problem for 2 weeks. I then did it again in case some combination of CFW.UPDATEFILE/CHOI BUILD or whatever cause the failure before, It's called the ghost in that machine. And I was out of ideas.

Also - funny that we couldnt guide him to a fix straight away - because none of us had this issue before - nor does the way of fixing it make much sense in this instance - but hey "it worked". Let me make a note of that... In me troll-binder.

Write it down, take a picture, I DGAF. Just leave you illiterate,Asperger riddled troll. just go,..

That was a long one. Maybe Qcat is right and I should just ignore the morons. Oh well. Half of this stuff will most likely get deleted. Any typos are because I am on my phone and don't have the time to proofread at the moment. ill look at it later. Thanks to anyone constructive!! Piss off Tipless .

 

[Tere Valentin]

Can Anyone help me with my problem? I am not sure if it's related to ChoiDujourNX.
I just got a new 200gb micro sd for my games and I wish to make it my primary sd card, but the console won't boot up normally so I can format it for the console. It only boots up to my 64sd card that I been using for months now.
I been using ChoiDujourNX since the release of World of FinalFantasy Maxima. Is ChoiDujourNX the cause of this?
I use SX pro, if that helps.

 

[Devrim]

Does someone have the hashes for the firmwares?

 

[WiiUBricker]

So I'm on 6.1.0 and want to install the exFAT driver. What game ships with the 6.1.0 firmware?

 

[Draxzelex]

So I'm on 6.1.0 and want to install the exFAT driver. What game ships with the 6.1.0 firmware?

You don't need a game if you pay attention to any coughing.

 

[Cyan]

xbin coughing? you need to understand what it is, how it works, how to use it, etc.
personally, I don't know what it is, even less what it means. is it like saying "dcc"? yeah, great hints really.

edit: looks like it's a homebrew release news website. not what I thought.

 

[spotanjo3]

There is an instruction for how to update it without burn the fuse but what about the downgrade ? There are several youtube but I am not sure since I don't trusted them.

 

[Draxzelex]

There is an instruction for how to update it without burn the fuse but what about the downgrade ? There are several youtube but I am not sure since I don't trusted them.

Its the same process for updating/downgrading. Just place whatever firmware files you want to install with ChoiDujourNX. It doesn't matter what your current firmware is.

 

[stupiddimbulb]

I'd like to update from 5.1 to 6.1, but I can't find an xci of that firmware anywhere. Closest I came are the zip files at consolehax but I have no idea how to convert those to xci files. Can anyone help?