Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,256,986
  • Replies Replies 48,066
  • Likes Likes 66
Hi People, i messed up updating my newly modded Gen 2 switch and could do with assistance. (I think that’s the issue anyway).

My OFW is on 21.1.0 but my CFW is on 19.0.1 (I downgraded). I cant boot in CFW (EMUMMC) I just get the Atmosphere error screen stating error 2002-0001 (0x202). Program 0100000000000025.

At first i had error

2162-0002​

but then followed this: https://gbatemp.net/threads/does-an...error-when-booting-into-emummc-please.678242/.
...and now the error ends with 0001.

Is it the mis-matching FW causing the issue or something else?

Thanks!
 
Last edited by That_Guy_Who,
Hi guys. I'm on FW 18.X and want to update. The guide I used to follow is no longer available. I don't remember every detail so I'd like to use a current guide (what I used to do was updating Atmosphere/Hekate/FW/Sigpatches/homebrews (don't use many of them though).

Do you know where I could find such a guide? Thanks!
 
Hi guys. I'm on FW 18.X and want to update. The guide I used to follow is no longer available. I don't remember every detail so I'd like to use a current guide (what I used to do was updating Atmosphere/Hekate/FW/Sigpatches/homebrews (don't use many of them though).

Do you know where I could find such a guide? Thanks!
@harticho use this
 
  • Like
Reactions: harticho
QUESTION ABOUT available with older HOS Firmware but newest ATMOSPHERE.


Hi everybody,

I can't find any information about this anywhere because it is really hard to formulate it in short and the patch notes of Atmopshere also don't mention anything about the conditions.

As I would like to be always up to date with switchcrafts patches and better stability I also have to upgrade atmosphere.
But I don't see any reason to update my HOS and I am still on 19.0.1. (Metroid Prime 4 is running perfectly fine with update and I generally can do everything.)

Because Nintendo is reserving more and more memory for their bullshit the devs of atmosphere say that they have less and less memory use and allow mods or homebrew (OVL?) to use since 20.0.0 and then again less with 21.0.0.

Now my question:
If I stay on HOS 19.0.1 (with AMS 1.9.5) but only upgrade onto the newest AMS 1.10.0, do I also "lose" that part of the memory capacity or does Atmopshere consider older Firmware to have more than the newest supportes HOS?

I hope I could formulate it as understandable as possible.


My additional question:
Because I don't know what this affects specifically: Should I care at all or when do I have to expect crashes if any homebrew or mod needs too much RAM?


Thank you in advance!

Kind regards!
Happy new year btw!
 
QUESTION ABOUT available with older HOS Firmware but newest ATMOSPHERE.


Hi everybody,

I can't find any information about this anywhere because it is really hard to formulate it in short and the patch notes of Atmopshere also don't mention anything about the conditions.

As I would like to be always up to date with switchcrafts patches and better stability I also have to upgrade atmosphere.
But I don't see any reason to update my HOS and I am still on 19.0.1. (Metroid Prime 4 is running perfectly fine with update and I generally can do everything.)

Because Nintendo is reserving more and more memory for their bullshit the devs of atmosphere say that they have less and less memory use and allow mods or homebrew (OVL?) to use since 20.0.0 and then again less with 21.0.0.

Now my question:
If I stay on HOS 19.0.1 (with AMS 1.9.5) but only upgrade onto the newest AMS 1.10.0, do I also "lose" that part of the memory capacity or does Atmopshere consider older Firmware to have more than the newest supportes HOS?

I hope I could formulate it as understandable as possible.


My additional question:
Because I don't know what this affects specifically: Should I care at all or when do I have to expect crashes if any homebrew or mod needs too much RAM?


Thank you in advance!

Kind regards!
Happy new year btw!

You don't really benefit anything for being on lower firmware and using newer atmosphere build.
 
You don't really benefit anything for being on lower firmware and using newer atmosphere build.

That might be the case but the programs I use do get updated and gave me the advantages of their improvements so I just upgrade to higher atmosphere versions automatically and also because they require it.
Do you have any information about my question about the memory?
 
That might be the case but the programs I use do get updated and gave me the advantages of their improvements so I just upgrade to higher atmosphere versions automatically and also because they require it.
Do you have any information about my question about the memory?

Newer firmware have less memory, 18.1.0 has 40MB, 19.x.x has 24MB and 20.x.x/21.x.x has 14MB. Some people are patching games and staying on lower firmware.

As for your other questions, Homebrew used this reserved space for its TLS slots, which means any homebrew software using TLS slots will experience memory corruption when running under Atmosphere 1.10.0.

To help make this transition easier, hbmenu now shows a warning when selecting homebrew compiled with an older, incompatible ABI version.
 
  • Like
Reactions: Thundereus
Newer firmware have less memory, 18.1.0 has 40MB, 19.x.x has 24MB and 20.x.x/21.x.x has 14MB. Some people are patching games and staying on lower firmware.

As for your other questions, Homebrew used this reserved space for its TLS slots, which means any homebrew software using TLS slots will experience memory corruption when running under Atmosphere 1.10.0.

To help make this transition easier, hbmenu now shows a warning when selecting homebrew compiled with an older, incompatible ABI version.
Thank you very much for your reply!

So this means no matter if I stay on an older Firmware the newer Atmosphere will still use less memory?
Does this only affect homebrew software launched from the hbmenu or does it also affect mods for games and overlays?

Do you think this is a problem that could show for me in every-day use, even if the homebrew I use is patched for this lower available ram capacity?
I wonder if any future mods that I want to use with my games will be possible and if any future updates of some overlays and homebrew programs might break or lose functionality. (e.g. losing the ability to use the status monitor while having mods running or not being able to access the Uberhand/Ultrahand menu when in a game.)
 
Thank you very much for your reply!

So this means no matter if I stay on an older Firmware the newer Atmosphere will still use less memory?
Does this only affect homebrew software launched from the hbmenu or does it also affect mods for games and overlays?

Do you think this is a problem that could show for me in every-day use, even if the homebrew I use is patched for this lower available ram capacity?
I wonder if any future mods that I want to use with my games will be possible and if any future updates of some overlays and homebrew programs might break or lose functionality. (e.g. losing the ability to use the status monitor while having mods running or not being able to access the Uberhand/Ultrahand menu when in a game.)

No, the available amount of memory for homebrew goes down as the firmware number goes up, so depends on what firmware you are on, some people prefer to stay on like 19.1.0 and patch their games. Certain case like using like mission control and salty NX together and attempt to run Pokémon games, would cause the game not able to load on 20.x.x due to lower amount of memory.
 
  • Like
Reactions: Thundereus

Error:2002-4686 010000000000001F​

After shutdown the switch with Ultrahand plugin, and turn it on today when I boot to the CFW.

I checked the content folder, there is no one name 010000000000001F, and I tried to delete all file in the [content] folder, and the overlay items, still not able to boot to the CFW.

Any guys have this issue? How can I solve it?
 

Attachments

  • IMG_9251.jpg
    IMG_9251.jpg
    1.1 MB · Views: 30
Hi friends,
I found lately a package3 for the 21.1.0 firmware which appears to have been modified by kefir to support tinfoil 20 in FW 21.1.0.
I tried desperatly to modify or extract the splash with no success, with the methods i found on internet (insert_splash_screen.py + extract_splash_screen.py). I believe he inserted an additional code for his own boot but as my coding knowledge is 0 i was wondering if someone would like to try ?
I add here his package3 for 21.1.0 supporting Tinfoil.
 

Attachments

Hi People, i messed up updating my newly modded Gen 2 switch and could do with assistance. (I think that’s the issue anyway).

My OFW is on 21.1.0 but my CFW is on 19.0.1 (I downgraded). I cant boot in CFW (EMUMMC) I just get the Atmosphere error screen stating error 2002-0001 (0x202). Program 0100000000000025.

At first i had error

2162-0002​

but then followed this: https://gbatemp.net/threads/does-an...error-when-booting-into-emummc-please.678242/.
...and now the error ends with 0001.

Is it the mis-matching FW causing the issue or something else?

Thanks!

hey, I'm in a similar situation.

updated hekate.
updated atmosphere.
updated sigpatches.
update firmware to 21.1.0 using daybreak on emuNAND and some homebrew were not working.
downgradeded firmware to 20.5.0 using daybreak on emuNAND and now whenever I try to boot my emuCFW I get this same error.

Any chance someone could help 2 folks at the same since we have the exact same problem?

--------------------------------------------------------------------------------------

EDIT: found a fix

https://github.com/sthetix/DowngradeFixer

put the downgradefixer bin in bootloader/payloads
in hekate boot into downgradeFixer, fix emuMMC, reboot into hekate, boot into emuCFW.
 
Last edited by veggav,
Is there just general issues with FW 21.1.0 and newest HATS Pack?

My memory card started acted funky (before updating) so I formatted it to start from scratch, then applied the newest HATS Pack, as well as updating my switch. Followed the normal procedure, partioning the SD and setting up the emMMC as always and never had any issues like this. Now i'm getting crashes in CFW (emuMMC) and OFW, can't play any games.
 
I'm trying to understand something here.

If using emuMMC this is equivalent to a copy of the system nand, right?

So, when installing games you get the option to install on NAND (if you are on emuNAND so the emuMMC) or SD CARD.

If installing to sd card and rebuild emu nand.
Why the games not present?
When installing to sd card where are the games?
 
I'm trying to understand something here.

If using emuMMC this is equivalent to a copy of the system nand, right?

So, when installing games you get the option to install on NAND (if you are on emuNAND so the emuMMC) or SD CARD.

If installing to sd card and rebuild emu nand.
Why the games not present?
When installing to sd card where are the games?

The internal storage for Emunand is on the SD card. If you are installing on an emunand, then the game would be on the SD, not on the physical internal NAND.
 

Error:2002-4686 010000000000001F​

After shutdown the switch with Ultrahand plugin, and turn it on today when I boot to the CFW.

I checked the content folder, there is no one name 010000000000001F, and I tried to delete all file in the [content] folder, and the overlay items, still not able to boot to the CFW.

Any guys have this issue? How can I solve it?
Anyone can help me please? :(
 

Error:2002-4686 010000000000001F​

After shutdown the switch with Ultrahand plugin, and turn it on today when I boot to the CFW.

I checked the content folder, there is no one name 010000000000001F, and I tried to delete all file in the [content] folder, and the overlay items, still not able to boot to the CFW.

Any guys have this issue? How can I solve it?
I'm no professional and don't know what the error code means but when your system worked before I would suggest to rule out a hardware problem.
My ideas/suggestions in order of effort to fix the problem.


1. Go into Hekate - Tools - Archive RCM Touch Pkg1/2 and tap to "Fix Archive Bit".

2. You could also try letting windows checkdisk do a scan for errors on the sdcard but I doubt the filesystem to be the problem.


---------

3. Basically try to boot into a fresh installation of your homebrew setup.:

Make a backup of all folders, except "Nintendo" (As it is very big and you DON'T need to delete it for my suggestion.) Then delete everything else (Atmosphere related, NOT the "Nintendo" folder) and copy a fresh Atmosphere and software you need (Ultrahand, SaltyNX etc.).

Basically try to boot into a fresh installation of your homebrew setup. If it works copy your "config" folder from your backup onto the SD card and test if it boots then. If it doesn't the problem must be inside the config files, otherwise continue by copying the backed up "switch" folder onto the sd card and check if it works then. Slowly copy one part of the folder structure from your backup back to the sdcard and see when it crashes again.

When you find the problem, just copy everything else, except that folder or file that causes the crash and just reconfigure the lost settings manually.

Again: Don't delete your "Nintendo" folder. Only what comes with atmosphere. And backup everything before.

-----------

4. If all of this doesn't help and it still crashes try to boot into original HOS without atmosphere.

If it still crashes it might be a Dat0 problem. (At least this was the problem with my switch when it suddenly crashed after working well for weeks.)
Post automatically merged:

Hi guys , sorry to ask but i have an issue that i tried to solve to no avail ( switch oled )

I currently have battery desync,
At first my battery has issue which is if i charge not full example (87-99%) the ui it suddenly will change to 100% automatically but it still run and turned off normally at 0%

Then i thought this must be the mismatched and after searching find the battery desync nx

I try to follow the guide there :
Open emummc - charge it to 100% - Open app - reset call - use it till low battery show up

In first step it cause new problem suddenly it shut down at 52% - i keep positive and think its part of process i charge it in hekate with the screen turn off. Btw when its on its already on 52% again. I charge it with saturation (6 hours )

On second cycle it turn off again in 51%

I think there is something wrong here.. is there any step that i misread

Thank you
Hi,
From my experience this can be really messy and annoying so it might take some attempts... But some nuances might help, because the fuel gauge is a bitch and needs time to calibrate when the battery is empty and full.

1. Reset fuel gauge with app. Leave app with "B" and close homebrew.

2. Connect charger and charge the console.

3. Important: When the battery is seemingly full (Ui showing 100%) open Ultrahand - StatusMonitor - Other - battery/charger and check what Raw Charge says. Let the console charge until Raw charge is 100% or the Current Flow drops to +-0mA. (Sometimes it shows some mA flowing but as long as it is just in the single digits it is just margin of error.)

4. When Raw charge and UI say 100% and there is no current being pushed in, let the console sit for 30 more minutes in sleep mode. Give the fuel gauge time to calibrate and save the values.

5. Disconnect the charger and let the console discharge in home menu. Don't use the console, don't use anything that raises the power draw and just turn the screen brightness to minimum.

6. Let the console dischararge and turn off by itself.

7. Wait for around 1 hour after it turned off (Let the fuel gauge save the "empty" status of the battery.) before doing anything.

8. Then connect the charger and boot again. Check if the percentage is around 1% - 5%.



If it is still very high (over 50%), check what the Raw Charge from Status Monitor says. If raw charge also says over 50% then something could be wrong with your hardware. What does the voltage say? Empty should be around 3,400V to 3,500V.

I don't know for sure if it will work but if it still turns off at around 50%, force it to turn on all the time until you get 0%. Drain that bastard with force until the hardware completely shuts down.
When it does so let it sit for an hour. Then charge it fully and don't boot into the system until it is full. (Except it boots automatically, then just let it is do it's job without touching. Just put it into sleep mode if you disabled auto sleep.) Then follow steps 3-8 again and see if it finally drops to 0% when discharging fully. (Or around 5% when it automatically shuts off.)



Additional info when checking the Raw charge:
The battery is full when the voltage is around 4,200V or at least between 4,165V and 4,250V, depending on your individual battery cells.
As mentioned above: The battery is fully charged when the voltage stays stable for a certain amount of time and when current isn't flowing constantly anymore (+XXmA).
 
Last edited by Thundereus,

Site & Scene News