I've got an alert set on my local selling app (OfferUp) for "broken OLED".Wish I see less switch send in due to self mod failed![]()
Never see any Switchs, but one day I'll swoop on a broken OLED to fix XD
I've got an alert set on my local selling app (OfferUp) for "broken OLED".Wish I see less switch send in due to self mod failed![]()

My local marketplace sucks, wish to see your swoop happen here as wellI've got an alert set on my local selling app (OfferUp) for "broken OLED".
Never see any Switchs, but one day I'll swoop on a broken OLED to fix XD

you dont have rgb led on the RPi pico. So good to go after uf2 flashedHello. Raspberry Pi PICO user here. Getting green color after flashing. I was going to ask how to set RGB mode on RRPICO but I remembered the LED light will be removed anyways. Is this correct, or am I missing something? The only thing I did so far was soldering the detection pins. Waiting for confirmation if I need anything else before I begin. Thanks!
Thanks. I needed to hear that. 2.65v flashed. Off I go.you dont have rgb led on the RPi pico. So good to go after uf2 flashed
I use the new mos tube and Pr2040, and it works fine. However, the temperature of the CPU is still high, and the resistance at both ends of the cap is reduced to 2 ohms after startup.If the soldering is correct, and you get 0 Ohm (test on the lowest range of your multimeter), the trasistor is defective (Drain and Source are shorted). If you remove the wires from the MOSFET, what's the resistance on the Capacitors?
Where is the switch damaged or is there a solution to this problem?I use the new mos tube and Pr2040, and it works fine. However, the temperature of the CPU is still high, and the resistance at both ends of the cap is reduced to 2 ohms after startup.
https://rentry.org/MarikoEmuNAND
Have you tried 'Warmboot Error Fix' to boot to ofw?
your picofly version?Just to show how much I believe the statement that picofly works on ALL firmware versions, I updated to 16.0.2 on OFW, booted to Hekate, dumped keys (there's one new Dev.key one called "secure_boot_key" btw), then dumped OFW with tegraexplorer and updated CFW with daybreak. CFW emuNAND still boots just fine.
i already try on my pico v2.5 all cfw and ofw working fineCurrently still running 2.64 like the definitive guide says, but I'm sure 2.65 would be equally fine.
2.5, or 2.65?i already try on my pico v2.5 all cfw and ofw working fine
Interesting, as long as it's stable I suppose no need to upgrade!2.5 my dear
thank you for your adviceIf the usb still there, use 2.65 is better. fw2.5 cannot update.
Update mechanism (without usb) only exist on >=2.61
but It glitched successful without sd card or empty sd cardMaybe the RST line need cleans. I remember @rehius saying that RST line is sensitive.
And i see in the pio glitch, it kind of make the cpu in reset state, before glitching.
Post automatically merged:
I think the fuse is inside the tegra, in the range of nanometer, can't be seen.
They should work, yes, just bigger than 0805Nobody answered my question![]()