Thanks my friend. I've tried but doesn't work. Now It stock on Nintendo Switch Logo. After that tried changing the wi-fi/BT module but no luck too.
I don't know what to do for now.
If have any sugestion.
I got this NSW Just for study.
I don't know what to do for now.
If have any sugestion.
I got this NSW Just for study.
- Joined
- Sep 2, 2020
- Messages
- 1,280
- Trophies
- 0
- Age
- 39
- Location
- TORONTO
- Website
- form.jotform.com
- XP
- 2,210
- Country
only unpatched v1 need a Jig to go into RCM if AutoRCM is off. All the rest modded/chip-mod model will always cold boot to payload from SDcard unless the modchip failed or soldering issue,
You mean stuck on logo? Is it joycon logo or it show nintendo letter then shutted off. If it was joycon logo, your switch has full partitions on emmc already. Try to replace the wifi ic if it was the case.
If it was nintendo letters then shutted off , it meant your console only has boot0,boot1 and lacks some partitions on the emmc(assuming it was the emmc as you above mentioned).
If you are not sure then up a picture of which stage your console is on then.
Post automatically merged:
The switch can boot sucessfully without the m92t ic so no need to check.
Its on joycon logo. already changed wifi IC.
This console have the emmc burned and APU.
Then I change the APU and EMMC from anothers bad consoles.
You don't need to. Just turn it on and it will boot into Hekate or Atmosphere.
Your Switch Lite doesn't have the vulnerability to use RCM to boot with a custom firmware.
That is why you need the picofly to boot.
If you need to copy some files over, the latest Atmosphere has an option to act as a usb stick.
Then you can copy homebrew app over by just connecting it to a PC/Mac.
If it was joycon logo that meant your emmc is good with full partitions already. You have good cpu and emmc. Change another wifi ic and make sure it a good one.
Shorts and missing resistors nearby M92T36 can occur to stuck on joycon logo without errors
Thanks for helping, I fixed it. It was something ridiculous… the vcc wire on the pico was broken … I didn’t see it under the kapton tape
This one is fully working now
Thanks for help.
I remake the reball of APU again. And ir Works.
Probably the soldar of the wi-fi Point doesnt good.
Attachments
I had a picofly installed by somebody over a year ago. I think they used the wrong resistors for my eMMC. I have a Toshita one. I can make and restore backups in Hekate perfectly fine. As well as boot into OFW for a decent amount of time (to keep it up to date with emu eMMC). But putting the console to sleep on sys eMMC is a near instacrash (usually under a minute). I've tried formatting too. Didn't help. But, oh well. Like I've said, I've had it for over a year and nothing bad has happened. I just can't use the internal eMMC.
Picofly = glitch cpu boot process, forget about all you read about RCM because your lite dont have RCM bug (only for unpatched switch v1 switches)
So start over and read (skip every part that is about RCM because that information is useless to you)
Not a question. More-so just me saying that even if your syseMMC isnt completely usable, as long as you're fine with only using emueMMC, you're likely still good. Like I said, I had mine modded at the beginning of last year and it works fine still. No corruption or anything.
Having this issue iwth my oled. I did kamikaze, it went great. Got it to boot up and setup emmunand properly and started using it then out of no where while entering dbi my console shut off and it gets stuck at the nintendo logo, i checked my cpu flex cable and one of the capacitors seemed a bit loose so i fixed that but the same issue is still persisting. It boots up to hakete, but no matter where i boot into, sysnand emunand or OFW it gets stuck in the nintnedo logo. Any advice into what to check? thanks!
Getting stuck on the logo can only mean one thing, there's a problem in your system partition. Though I'm not sure how you managed to cripple both since its usually one and not the other since they are separate entities.
You probably made a mirror of your sysNAND when its on the brick going bust.
Hello @psycho-neon. Have chips manufactured with component assembly. I put three, all three flashed correctly. The first chip rarely does not turn on with the console, the second went well and the third directly does not turn on with the console. Have they given you any problems? I'm thinking about throwing them away and sticking with my Rp2040s, which never fail me.
Never had issues with mine 100s of them. They all boot fine. Had my second batch of 100s coming in a few days as well.
You can try removing the cap above the oscillator.
Similar threads
-
Xdqwerty
what are you looking at? -
K3Nv2
-
Psionic Roshambo
-
-
-
@
Xdqwerty:
@Psionic Roshambo, checked the core list and there is no n64 core for that fork/version of retroarch+1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
