Hacking SWITCH NOOB PARADISE - Ask questions here

[saito1234]

No XCI mounting for Atmosphere. Should be able to use tinfoil fine.

Sorry I meant installing from .xci, and not mounting it.
Whenever I mount an xci in SX OS from my Pendrive and I want to put Switch into sleep mode, it wakes up and quits the game ,so I think its bugged or something. So either ways I dont really use this feature even in SX OS.

I tried installing an .xci and it worked perfectly with Tinleaf so I am very satisfied. I don't see much point to use SX OS any more.

 

[Adran_Marit]

i have a problem...i updated to 11.0.1 with daybreak..now if i wanna start ams i get following error:


ERROR Fatal Error: [NXBOOT] Couldnt parse boot0: I/O error!

what to do?......sxos dont boot either but stock fw boots (i have ams 0.16.1 and sxos 3.10)

Are you using the latest fusee-primary? As that was updated in 0.16.0

If using just Atmosphere payload, is there a way to select weather to boot into EmuNAND or SYSNand? or is Hekate needed to do this??

It's easier with Hekate, but you can edit one of the atmosphere ini files

 

[jonnyh585]

https://switchbrew.org/wiki/Fuses#Anti-downgrade

Hekate Fuse count?

I am on 1.0 techically yes, launch switch that i have carefully maintained but downgraded now i can boot hekate but when i go to launch os from its menu 6.x doesnt work

 

[Hayato213]

I am on 1.0 techically yes, launch switch that i have carefully maintained but downgraded now i can boot hekate but when i go to launch os from its menu 6.x doesnt work

"i wanted to downgrade to use devmenu to remove an patch game update requirement for a game, and i felt like i had done this before

i downgraded via choidujour, then hit "Shutdown"

all my previous set up was correct, sx os, auto rcm, exfat32, etc

went from 10.1 to 6.1, not my switch wont boot

help how do i fix this, i tried using an older boot.dat and no luck "

Based on what you said in the last post, 10.1.0 expect 13 fuse burn, so if you restore to 6.1.0 it is 7 fuse, where it refuse to boot as too many fuse were burnt. Depends on your fuse count.

 

[Purple_Heart]

Are you using the latest fusee-primary? As that was updated in 0.16.0



It's easier with Hekate, but you can edit one of the atmosphere ini files

i was using ams 0.16.1 with latest fusee primary....it worked when i was in 11.0...but that error occured when i updated to 11.0.1 (stock fw works)...i used daybreak to update

 

[jonnyh585]

"i wanted to downgrade to use devmenu to remove an patch game update requirement for a game, and i felt like i had done this before

i downgraded via choidujour, then hit "Shutdown"

all my previous set up was correct, sx os, auto rcm, exfat32, etc

went from 10.1 to 6.1, not my switch wont boot

help how do i fix this, i tried using an older boot.dat and no luck "

Based on what you said in the last post, 10.1.0 expect 13 fuse burn, so if you restore to 6.1.0 it is 7 fuse, where it refuse to boot as too many fuse were burnt. Depends on your fuse count.

i have carefully updated with choi since 1.0 and never had an issue, should only have 1 fuse burnt

in any case, is there a way to restore firmware to 10.1 in this state?

 

[almmiron]

I have a pure neverhacked 3ds.

Have this question concerning save edition of pokemon games.

If i'm willing to NOT lose my nnid, its a bad idea to create pokemon with save edition homebrew/software and then connect to the internet and send them to official pokebank?

Let's assume it is 'safe'.

There's some method for hacking that I should use/avoid? Emunand is a thing or not in 3ds nowadays?

Edit, I posted here because of nnid I use on switch is the same.

 

[Purple_Heart]

I have a pure neverhacked 3ds.

Have this question concerning save edition of pokemon games.

If i'm willing to NOT lose my nnid, its a bad idea to create pokemon with save edition homebrew/software and then connect to the internet and send them to official pokebank?

Let's assume it is 'safe'.

There's some method for hacking that I should use/avoid? Emunand is a thing or not in 3ds nowadays?

emunand was and is a thing but not neccessary anymore...you wont get a ban unless you cheat online. but for uploading hacked mons online i am not sure i did and never got banned...but dont trade em online or fight online thats a ban then

 

[Adran_Marit]

i was using ams 0.16.1 with latest fusee primary....it worked when i was in 11.0...but that error occured when i updated to 11.0.1 (stock fw works)...i used daybreak to update

Got a backup you can restore?

I have a pure neverhacked 3ds.

Have this question concerning save edition of pokemon games.

If i'm willing to NOT lose my nnid, its a bad idea to create pokemon with save edition homebrew/software and then connect to the internet and send them to official pokebank?

Let's assume it is 'safe'.

There's some method for hacking that I should use/avoid? Emunand is a thing or not in 3ds nowadays?

Edit, I posted here because of nnid I use on switch is the same.

make sure they flag as legit

 

[Hayato213]

i have carefully updated with choi since 1.0 and never had an issue, should only have 1 fuse burnt

in any case, is there a way to restore firmware to 10.1 in this state?

If you have a 10.1 NAND backup then restore that. Check Hekate and see what is your fuse count ?

 

[jonnyh585]

If you have a 10.1 NAND backup then restore that.

not sure i have a backup and if i do its from 1.0, im telling you i havent burned fused and i have downgraded and upgraded firmware before, if i can book hekate why is it black screen when i launch?

 

[Hayato213]

not sure i have a backup and if i do its from 1.0, im telling you i havent burned fused and i have downgraded and upgraded firmware before, if i can book hekate why is it black screen when i launch?

Hekate doesn't touch Horizon OS, so that is seperate, the problem is you downgrade from firmware that have a lot higher fuse count to something that is much lower, that why the system start to panic, refusing to boot, you are not suppose to go around downgrading firmware, that is not how it work. You can get away from downgrading to like firmware one fuse down, not one that is like 6 or 7 fuse down.

 

[jonnyh585]

Hekate doesn't touch Horizon OS, so that is seperate, the problem is you downgrade from firmware that have a lot higher fuse count to something that is much lower, that why the system start to panic, refusing to boot, you are not suppose to go around downgrading firmware, that is not how it work. You can get away from downgrading to like firmware one fuse down, not one that is like 6 or 7 fuse down.

ok thank you i appreciate the help, i was thinking my hekate was too new to boot on 6/x and needed an older version, i remember using it when it was just black and white text

if i dont have a backup, how can i launch choi and "upgrade" back to 10.1?

 

[Hayato213]

ok thank you i appreciate the help, i was thinking my hekate was too new to boot on 6/x and needed an older version, i remember using it when it was just black and white text

if i dont have a backup, how can i launch choi and "upgrade" back to 10.1?

You might have to rebuild the NAND using choidujour 6.2 or lower firmware and see if it boot.

https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

If 6.2 doesn't work, try 5.1.

 

[jonnyh585]

You might have to rebuild the NAND using choidujour 6.2 or lower firmware and see if it boot.

https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

If 6.2 doesn't work, try 5.1.

ok is that an option in hekate? i can launch payloads and sx os boots fine im still in RCM but i dont have a way to launch choi on the switch cuz nothing boots

 

[Purple_Heart]

Got a backup you can restore?

make sure they flag as legit

i have a nand backup of 10.2 but burned fuses

 

[Hayato213]

i have a nand backup of 10.2 but burned fuses

Think you can restore to 10.2.0 and then update to 11.0.0 fine.

 

[Purple_Heart]

ok then ill do that

 

[Hayato213]

ok then ill do that

but make a copy of 11.0.1 NAND backup as pre-caution.

 

[Purple_Heart]

yes i am doing that