I don't remember, maybe in another forum... I'm still shocked that I can't use my console till a new version of CFW will be released...Where the hell did you hear this...
Where exactly does it say that you cannot use your console without a new CFW version?I don't remember, maybe in another forum... I'm still shocked that I can't use my console till a new version of CFW will be released...
Anyway, when it will be patched, I will still have my data saved games?
Unfortunately I updated to the 6.2 version...Where exactly does it say that you cannot use your console without a new CFW version?
Use it on 6.1 with CFW, or use it on 6.2 in OFW, playing all your legally purchased games. No biggy
Ok thanks I didn't know that I have not touched firmware 6.2 in anything as yet and the user did not explain that part to me, it makes sense now with emunand.
I don't think that's correct since having 6.2.0 prevents emunand from booting...
I thought exactly the same as you did but apparently not. I cannot test this procedure out because I don't want to update ofw to 6.2 yet for reasons of my own but as I can see it, it seems even though you update your ofw/sysnand to firmware 6.2.0 when you use the sx dongle it will still boot into sxos main menu because the rcm exploit can not be stopped so it continues to go into the sxos menu and also boots directly into your 6.0/6.1 sd emunand supposedly being the priority boot but it wont boot into cfw because that is still on firmware 6.2.0 so basically you need too setup sd emunand on 6.0/6.1 before you update ofw/sysnand to 6.2. This is only what I have been told for information and how I can see it running but I don't know 100% myself and I can't test it either.So Reecey if you're correct I can use my old 6.1.0 emunand on 6.2.0 sysnand and still have sleep mode and everything work? I don't think that's correct since having 6.2.0 prevents emunand from booting... And if it did boot it'd still not work with sleep mode.
Where did you get that information? I don't think that's correct. AFAIK when using emunand the TX bootloader bypasses the sysnand completely to boot directly into the emunand; whatever is installed on the sysnand should have zero impact on the ability to boot into emunand.
I thought exactly the same as you did but apparently not. I cannot test this procedure out because I don't want to update ofw to 6.2 yet for reasons of my own but as I can see it, it seems even though you update your ofw/sysnand to firmware 6.2.0 when you use the sx dongle it will still boot into sxos main menu because the rcm exploit can not be stopped so it continues to go into the sxos menu and also boots directly into your 6.0/6.1 sd emunand supposedly being the priority boot but it wont boot into cfw because that is still on firmware 6.2.0 so basically you need too setup sd emunand on 6.0/6.1 before you update ofw/sysnand to 6.2. This is only what I have been told for information and how I can see it running but I don't know 100% myself and I can't test it either.
Edit: I thought it was reported to TX that sxos did not work at all even booting but others say it does boot into the menu and you can boot emunand of it a bit confusing.
For one I've been unable to boot anything on my 6.2.0 switch and for two Team Xecuter and He Hexytz said that CFW doesn't work on 6.2.0. You can't boot any CFW at all.
No I can't boot into 6.0.1 emunand at all. I can only boot into the SX Menu on 6.2.0 sysnand. I can't do anything else whatsoever.
My bad - I thought you meant that sysnand on 6.2 was preventing you from booting in pre-6.2 emunand; I understand what you meant now. But technically as long as your emunand is < 6.2 you should be able to run CFW on it, even if your sysnand is on 6.2.
Please keep us updated!Tonight, when I get back from the movies. I said in another thread yesterday I'd be updating to SD emunand when SX OS 2.3 is out of beta, or when a new firmware hits the scene. Ironically the latter took less than 24 hours to happen. Time to put my money where my mouth is.
Sleep mode doesn’t work because of the warm boot fuse checksMy hacked switch, that I thought was banned, managed to get updated to 6.2.0, kids just pushing random things when they popup and I didn't have 90dns or anything setup anymore. It was a 1.0.0 launch console, only had 1 fuse burnt. Oh well.
6.2.0 doesn't work with anything (atmosphere, reinx, hekate, sx os beta). I tried everything before I went the nuclear route. I restored my 1.0.0 nand with autorcm enabled from hekate. Everything seemed to work. I noticed I couldn't consistently boot from hekate to cfw. So Updated to 5.1.0, same thing. Then I noticed sleep mode didn't work. Updated all of my sdcard files, same thing. Updated to 6.1.0, same crap.
I'm wondering if something else got updated that doesn't get downgraded with ChoiDujourNX.
Sleep mode doesn’t work because of the warm boot fuse checks
Also... YOU UPDATED A 1.0
That's not an unban. Normal/soft bans don't prevent system updates so even if you're banned, you can still update the system firmware. Your friend still cannot play online, access the eShop, or download game updates because these are still restricted by standard bans. Only a CDN ban would prevent system updates.I saw reports in TX foruns that Nintendo was lifting update bans so people would accidentaly update to 6.2 as they want you to.
I was skeptical at first, but i talked with a friend with a banned console to check it out and he confirmed that they did unban him, he tried to update the console and it was possible (ofc he aborted and stuff).
So becarefull even with a banned console, put airplane mode on guys.
That's not an unban. Normal/soft bans don't prevent system updates so even if you're banned, you can still update the system firmware. Your friend still cannot play online, access the eShop, or download game updates because these are still restricted by standard bans. Only a CDN ban would prevent system updates.