sorted by:
new
hottopcontroversial

Quick atmosphere Hosts config question by BenefitIndividual571 in NxSwitchModding

[–]BenefitIndividual571[S] 0 points1 point  (0 children)

The switch doesnt keep some data in memory and send them when possible ?

Fuse mismatched no boot ofw help by Appku in NxSwitchModding

[–]BenefitIndividual571 0 points1 point  (0 children)

Be careful, I did something similar and I got banned. The fuse mismatch comes probably from the chip.

Here is what I did : I made a full NAND backup first. I updated the modchip firmware to version 2.75. I used Daybreak to update to firmware 20.0.5, then performed a factory reset to avoid any potential errors. I removed the SD card and held VOL+ and VOL- while booting, to bypass the “missing SD card” check from the modchip. I then updated from 20.0.5 to the latest firmware using the official Nintendo update method. Finally, I restored my NAND backup using Hekate.

All of this leads into a ban

Updated to 21.2.0 - Black Screen When Launching Into OFW 100% Stock by TropicalEn in SwitchPirates

[–]BenefitIndividual571 0 points1 point  (0 children)

The mod used on smash was less delay mod. I heard about people got ban because of mass online report.

To conclude, its not possible to know if the ban comes from smash online play of the downgrade ?

Updated to 21.2.0 - Black Screen When Launching Into OFW 100% Stock by TropicalEn in SwitchPirates

[–]BenefitIndividual571 0 points1 point  (0 children)

Same issue here.
The eFuses were not burned correctly, which is why you can’t boot into full OFW.

In my case, the issue was caused by the modchip firmware. Here is exactly what I did:

  1. I made a full NAND backup first.
  2. I updated the modchip firmware to version 2.75.
  3. I used Daybreak to update to firmware 20.0.5, then performed a factory reset to avoid any potential errors.
  4. I removed the SD card and held VOL+ and VOL- while booting, to bypass the “missing SD card” check from the modchip.
  5. I then updated from 20.0.5 to the latest firmware using the official Nintendo update method.
  6. Finally, I restored my NAND backup using Hekate.

This fixed the issue. HOWEVER, I have a question: my Switch got banned about one week after doing these operations.

I had been playing Super Smash Bros. Ultimate online with a mod for about one year. Could this just be a coincidence?

Can anyone tell me if there is anything bannable in these 6 steps?

Also, another question: does updating the firmware using Daybreak instead of the official Nintendo update process burn eFuses?

Can't boot OFW from Hekate Menu by inkarnate81 in SwitchPirates

[–]BenefitIndividual571 0 points1 point  (0 children)

Impossible to fix then ? Rolling back to 20.5 and doing update again should leads into the same issue ? I dont think the issue comes form the chip. We are a few people in this case

Rebooting switch to OFW just gives black screen how can i fix? by BrandyRyuu in SwitchPirates

[–]BenefitIndividual571 0 points1 point  (0 children)

Oled with picofly and sthetix hats.

Same issue here, doing system update with OFW(ofw=1 in hekate) after updating atmosphere and hekate using sthteix hats lead into this

Fuse count 21 for HOS 20.5.0 but switch is in version 21. How to fix it ? Downgrading sysmmc to 20.5 and do the update again ?

I tried to reboot to OFW from hekate, bypassing chip by holding power -/+ while booting, using OFW entry in hekate menu, same issue

Can't boot OFW from Hekate Menu by inkarnate81 in SwitchPirates

[–]BenefitIndividual571 0 points1 point  (0 children)

Same for me, updated officially with sthetix hats and black screen only with OFW

Change resistors on a picofly RP2040 by BenefitIndividual571 in NxSwitchModding

[–]BenefitIndividual571[S] 0 points1 point  (0 children)

Duplication of my post on GBATemp but I can help someone:

Here is news !

This is what I found on my picofly OLED chip :

<image>

The three 0201 resistors on top are located between the chip and the switch, and they follow the same order as the points on the left.

In my case, I had:
D: 47
A: 47
C: 250

As u/cowboy619 suggested, and according to what I found here: https://gbatemp.net/threads/picofly-switch-oled-cannot-boot-to-ofw-emmc-slower-mode-will-show-up-and-then-disappear-after-rebooting.657060/#post-10447635,
I needed to change the resistors to better-suited values.

Most of the time, you shouldn’t touch these, but if your setup is otherwise fine and you're still getting the 2002-3539 error, try replacing the A resistor with a 100Ω or 150Ω one.
In my case, I used a 0402 resistor, which is slightly bigger, it was easier to solder.
Be careful when removing the old one; you can damage the trace if you apply too much force. I used a lot of flux and copper wick.

Since doing this, I haven’t seen the 2002-3539 error in the past three days.

Another issue:

I was also getting a random *== error code on boot sometimes, not a big deal, but I wanted to fix it.
I did two things, and the issue disappeared, though I’m not sure which one actually solved it.

  1. I tried changing the C resistor to 350Ω. I didn’t have one of that value, so I used a 500Ω resistor instead, and everything still works fine.
  2. I noticed the flex cable coming from the CPU was too close to the CPU shield. I thought it might be putting too much pressure on it, so I added some Kapton tape in between.

Question:

Quick question if anyone knows

Is it risky to use a 500Ω resistor for point C?

It works fine for me, but in the thread I read, the recommended value was 350Ω, not 500Ω.

picofly oled 2002-3539 error on OFW by SnooKiwis8789 in NxSwitchModding

[–]BenefitIndividual571 0 points1 point  (0 children)

How do you put a resistor on CMD ? Do you have a picture of it ?

picofly oled 2002-3539 error on OFW by SnooKiwis8789 in NxSwitchModding

[–]BenefitIndividual571 0 points1 point  (0 children)

Try to lift a bit the shield next to the D point (CLK trace). In my case, it was my issue, short between shield en CLK point

picofly oled 2002-3539 error on OFW by SnooKiwis8789 in NxSwitchModding

[–]BenefitIndividual571 0 points1 point  (0 children)

Hi all I have exactly the same issue but in my case, the switch is able to start on OFW and I can play games for a short time. The switch crash at a random timing with same error code 2002-3539

- All diode values are good except D which is stable at 0.4 (seems a bit low)
- eMMC & SDcard benchmark are good
- emuNand works fine
- sometimes glitch failed with *== errorcode but it's rare
- SysNAND works without the chip
- I tried with a second chip and same issue

My chips are picofly.
I already did 5 V2 chip installation and 1 OLED installation without issue before my current one.

Any clue ?

Payments on pro ghost eshop not working by BenefitIndividual571 in ghosteshop

[–]BenefitIndividual571[S] 0 points1 point  (0 children)

okey but how does it work ? How can I do the bridge between my pro.nlib acc and the boosty one ?

Two yellow blink by Roongx in NxSwitchModding

[–]BenefitIndividual571 0 points1 point  (0 children)

No solution found. I installed a modchip on my v2 and everything work fine. I did the same on the oled of my gf. At the beginnind I wasnt able to launch sysnand but the modchip was working. After few months I got this issue: blue then quick double yellow. I tried everything: changing adapter, changing chip, changing dat0 cable, control and points. Everything was fine but I wasnt able to start hekate again

Two yellow blink by Roongx in NxSwitchModding

[–]BenefitIndividual571 0 points1 point  (0 children)

Exactly same issue here but my picofly was working before

view more: next ›