Great! We need to update your injector as well.
If you inject using Hekate you can use the same Hakate.x.x.x.bin file you just downloaded in the zip file in Tegra on your PC
If you inject using Hekate you can use the same Hakate.x.x.x.bin file you just downloaded in the zip file in Tegra on your PC
It booted to the Hekate v5.9.0 menu which it never got there before when i injected payload it would just boot cfw and get me to the homescreen for the switch
But anyway..
I picked launch
chose CFW - emuMMC
then this happened
Panic Occured while running Atmosphere.
Title: ID: 0100000000000BD00
Error: std::abort (oxFFE)
Report saved to /atmopshere/fatal_errors/report_019a6549f.bin
Press power to continue
You just over wrote your original /atmosphere….you didn’t move it to /atmosphere.bk
I can tell because Mission Control is barfing on the new FW.
It’s OK
Do this quick test…
Move(or rename) /atmosphere/contents to /atmosphere/contents.bk temporarily and reboot.
I saved the originals folders on my PC Atmosphere and Bootloader that I copied from the SD card before downloading all the new stuff you instructed
Im uncertain of what you mean by BK?
I just deleted the contaminated atmosphere & bootloader folder on the SD should I just drag the new atmosphere and bootloader folders that you asked me to download earlier? onto the sd?
.bk is just a random set of letters I add to a directory so it is out of the way.
Gives the new /atmosphere files contained in the zip a clean place to lay down.
You could have renamed it to /atmosphere.MyCoolFilesThatIDontWantToOverWrite but it takes a lot longer to type than /atmosphere.bk.
We’re beyond that now…let’s keep moving forward. Almost there. Just move/rename /atmosphere/contents to /atmosphere/contents.bk and reboot.
E: if you already deleted them, that’s fine…just copy over the files from the zips. You will need to create a new /bootloader/hekate_ipl.ini file as the new ones from the zip won’t have one.
Also recreate your /atmosphere/hosts/ files as the new zip won’t have that either…
awesome its fixed and working again thanks!
1. Can i try and update the scarlet version again by matching local data? or will i get back into the same problem i had earlier?
2. what do I do with my old files/folder (atmosphere & bootloader)
3. how can i boot up my switch automatically to the homescreen skipping the hekate menu like before?
Sure, you are at latest and greatest…nothing can touch you now. :-)
Your /atmosphere/contents directory has some sys-modules and stuff that you might want. You will probably have to upgrade them in order to make them work with your new firmware. They are small…keep them around for a while and if you notice something weird, you can reference them to find out what you need to upgrade to get it to work.
E: here’s the Mission Control update that would fix the error (0100000000000BD00) we got earlier:
https://github.com/ndeadly/MissionControl
Your hekate_ipl.ini has some settings in it. You can read about the autoboot setting here:
https://github.com/CTCaer/hekate#hekate-global-configuration-keysvalues-when-entry-is-config
Here’s what I would probably do, but you should read about the options just the same.
[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=65
autohosoff=2
autonogc=1
updater2p=1
bootprotect=0
[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp
[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp
autoboot=1
autoboot_list=0
bootwait=1
backlight=65
autohosoff=2
autonogc=1
updater2p=1
bootprotect=0
[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp
[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp
Last edited by binkinator,
Muppet here. Recently bought this unpatched switch from a pawn shop store on ebay, at least I'm pretty sure it is. Can someone put my mind at ease? It was a good deal so I didn't study the picture as long as I should have before buying (and I was stoned). Pretty sure the first 6 numbers of the serial after the XAW1 are 005621.
Attachments
hmm now i realized my sysnand (ofw) have about 20.8GB free on MicroSD Card while 19.6 Fortnite +4.1GB Game installed, total 44.5GB
System Memory still 25.8GB
I thought we must use seperate MicroSD card if want to install content on switch(ofw)
System Memory still 25.8GB
I thought we must use seperate MicroSD card if want to install content on switch(ofw)
When I checked with a Online Web:
That's all the information we could know through the serial number.Your console is not patched. Hooray!
No necessary to do that. I am using emuNAND and sysNAND on the same card (256gb) and everthing seems good.
so microsd share partition between cfw and ofw or it create each partition for cfw/ofw right ?
ofw can't see other than it partition, cfw can see all, when enabled MTP too
They share the same ex-data partition (which is indicated microSD Card under Data Management) but they never use data in that partition of each other.
When you create EmuNAND with partition option, you will create a new partition in microSD and this partition isn't accessible in any machine (window, mac,...) without specific software (after created EmuNAND partition, whenever you plug microSD into a window machine, there is always a pop up to ask you format a "disk" that window can't read). This partition is System Memory under Data Management in CFW.
Sum up, there would be 3 region partition and there place:
- System Memory of OFW - eMMC in Switch machine
- System Memory of CFW (partition EmuNAND) - a New Partition when you create with hekate/...
- microSD Card of "OFW & CFW" - remaining capacity of your microSD after Create partition for your CFW - this partition is "share" capacity between OFW and CFW but their data won't be used by another.
Apparently, when you plug microSD in PC, you can access one partition (which I call microSD Card - "shared ex-data partition" under Data Management). In there, it contains both OFW (Nintendo folder) and CFW (the rest) contents. As I said above, they can see all, but their data will be not used by another.
Hope that will help you to clear the mist in your mind.
Last edited by marhalloweenvt,
"When you update your system firmware version and boot the stock operating system, your Nintendo Switch burns a microscopic fuse to prevent your Switch from being able to downgrade. Essentially, if a stock firmware tries to boot but too many fuses are burnt for that specific firmware version, the system will simply power off, preventing you from booting."
=> So, the answer is a big NO
and is there a way i can mod a v2/redbox switch on 12.0 firmware ,, so this ''switch.homebrew.guide/usingcfw/manualchoiupgrade" will essentially brick the system ?
Have a look at HWFLY modchip, this can help u in modding your machine.
I thought V4 was just the generation of the modchip. I bought one of these for my V2 Mariko and it works great.
I wish they would have used different nomenclature….like version A, version B, version B.2, etc
Less confusing!
I wish they would have used different nomenclature….like version A, version B, version B.2, etc
Less confusing!
- No one is chatting at the moment.
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
-
