question is to use this update after having to go back to the old one when updating OFW
Hi everyone...i recently installed picofly on my switch lite...ibstalled the mosfets...tested and got no sd screen...closed the console and when power on got a yellow/orange light just after blue and loads ofw...can anyone explain where is the problem? (Sorry for my english)
How did you do that? What gauge wire were you using?
I've been a little rough with my lite flex cable, and that hasn't happened yet. I've creased the hell out of it. I'm a little concerned that might be the cause of my glitch consistency.
Attachments
yes always make a backup.
Both emmc raw, boot0/1 and keys
2.66 had the fix to skip hekate after ofw update to allow efuse burn but will skip hekate on 1st boot with a new install
2.67 still has the fix but won't skip to ofw on 1st boot with a new install..
It's still not working. Tried 2.66, 2.67 but no lock. Updated to 2.67 via toolbox, removed sd card.
Restarted to the "no sd card" screen, presses Vol+- to boot OFW but it blackscreens.
I also get slow emmc errors when backing up emmc. Maybe thats the problem?
Any other ideas?
Last edited by Jonas225,
Do you have the 3 resistors on the picofly?
This happens because of interference on eMMC lines. After the logo NS switches to the high speed mode. You can test eMMC benchmark in hekate - in perfect conditions you should get around 200-350 MB/s.
To fix that ensure you have resistors on D0, CMD, CLK, the wires are well soldered, short and aligned the same way
Post automatically merged:
Same here. Show us pictures of your soldering, looks like it is flawed in some way
Hello! Guys I have a weird problem here. From the beginning: brand new switch oled, successfully updated to 16.0.2 before picofly install. Dat0 was soldered with enameled wire via reballing Hynix emmc. I’ve soldered all other wires to it’s places (but not to rp2040) and booted stock FINE, just to test everything works - and it worked 
. Flashed 2.66 to rp2040, soldered all wires and booted to raspberry fly boot logo just fine. Assembled back whole console and saw that 2.67 is out. Tried to update, but fw remains the same 2.66 . Then I tried to boot stock and got instant purple screen. According to my knowledge it should be a CMD 4.7k resistor, but it was fine, and replacement to working one did not solved the issue. I decided to reball emmc once again and at the same time check continuity from switch board on pad under emmc ic to the point connected to 4.7k resistor and it was OK. After placing back emmc nothing changed. Hekate boots fine and I decided to check emmc info. Here what I got. Seems like corrupted info in user partition . Emmc benchmark passes ok, reading speeds are fine and health of emmc ic is 100%.
So my question what have happened?. I’ve allready made about 15 oleds with rp2040 from initial 2.5 to 2.66 firmwares and it was always fine. It is definitely not the soldering issue, cause I’ve double checked everything and it boots hekate just fine. May a rp2040 ruin user partition on emmc? Data corruption on reballing process is also unlikely, because boot0/1 partitions are alive and I’ve made boot and raw backups just fine (no errors).
And the second question is how to restore this switch back to working order? Seems that I need to generate user partition, or may be there is an option to restore it, may be info is alive, only partition table is broken?
. Flashed 2.66 to rp2040, soldered all wires and booted to raspberry fly boot logo just fine. Assembled back whole console and saw that 2.67 is out. Tried to update, but fw remains the same 2.66 . Then I tried to boot stock and got instant purple screen. According to my knowledge it should be a CMD 4.7k resistor, but it was fine, and replacement to working one did not solved the issue. I decided to reball emmc once again and at the same time check continuity from switch board on pad under emmc ic to the point connected to 4.7k resistor and it was OK. After placing back emmc nothing changed. Hekate boots fine and I decided to check emmc info. Here what I got. Seems like corrupted info in user partition . Emmc benchmark passes ok, reading speeds are fine and health of emmc ic is 100%. So my question what have happened?
. I’ve allready made about 15 oleds with rp2040 from initial 2.5 to 2.66 firmwares and it was always fine. It is definitely not the soldering issue, cause I’ve double checked everything and it boots hekate just fine. May a rp2040 ruin user partition on emmc? Data corruption on reballing process is also unlikely, because boot0/1 partitions are alive and I’ve made boot and raw backups just fine (no errors).And the second question is how to restore this switch back to working order? Seems that I need to generate user partition, or may be there is an option to restore it, may be info is alive, only partition table is broken?
Attachments
Last edited by achm3t,
Does anyone have any ideas what I am maybe overlooking. I have Waveshare 2040-One I flashed with latest firmware 2.67. I have set “RGB mode” jumped. When I power on the Switch Lite I get a blue then cyan. I have changed mosfet twice.
Attachments
Hello! Guys I have a weird problem here. From the beginning: brand new switch oled, successfully updated to 16.0.2 before picofly install. Dat0 was soldered with enameled wire via reballing Hynix emmc. I’ve soldered all other wires to it’s places (but not to rp2040) and booted stock FINE, just to test everything works - and it worked
So my question what have happened?
And the second question is how to restore this switch back to working order? Seems that I need to generate user partition, or may be there is an option to restore it, may be info is alive, only partition table is broken?
sk hynix emmc's are more brittle than others and need a slower temperature rise when removing and reattaching to pcb. what's your heating method and temperature?
Post automatically merged:
This might not be the issue here, but putting the mosfet on top of the substrate like this means it is taller than the apu core, which means the shield and cooler will rest on top of the mosfet rather than the apu. not ideal
Similar threads
-
Xdqwerty
what are you looking at? -
OmDRetro
-
BakerMan
I rather enjoy a life of taking it easy. I haven't reached that life yet though. -
a_username_that_isnt_cool
-
@
NinStar:
because I already got burned out with breath of the wild, which for the most part is essentially the same game, and then again with master mode, which doesn't work as a new game plus (that always felt bizarre to me) -
-
-
-
-
-
-
-
-
-
-
-
@
a_username_that_isnt_cool:
i just got a stream deck (mobile cause i'm broke) and i've been messing around with the soundboard. and i found out that my vine boom sound was delayed because of it.
-
-
-
-
-
@
BakerMan:
@Xdqwerty the joke is that the cat grill friend is a friend that is also a cat that works a grill
-
-
@
OmDRetro:
The cat grill friend is likely to be an experienced griller, but once you piss it off it might be grilling you next?+1
-
-
-
-
@
OmDRetro:
@Xdqwerty HM...+1
If the cat girl leaves, my kokoro dies a little.
If I piss off the cat grill friend, I get no food and he's likely to grill me.
There's just no winning here
-
