Current issue for 2.61 is we can't boot to OFW, whether using hekate->reboot->ofw or by vol+ vol_.People click the "important posts" and stop using old fw you might find on YouTube links.
But still can boot OFW via "warmboot error fix".
Current issue for 2.61 is we can't boot to OFW, whether using hekate->reboot->ofw or by vol+ vol_.People click the "important posts" and stop using old fw you might find on YouTube links.
In the same spirit, I vectorized your graphic. The attached is a scalable vector that can be used to make icons, large graphics, and other things without losing fidelity of the shape. Just download and remove the .pdf extension to use in your favorite photo editors.CHECK THE AIO Thread there are pinouts for everything
https://gbatemp.net/threads/picofly-aio-thread.628951/
images Mosfet
Post automatically merged:
Have Fun Guys
i know its not the best , but for now the best i could do
View attachment 364155
Or if people linked the GitHub that has the firmware on itPeople click the "important posts" and stop using old fw you might find on YouTube links.
The github should really have archive for older. I hope the owner fixes thatOr if people linked the GitHub that has the firmware on it
Latest firmware here
ChangeLog:
v2.0 + Active MMC communication
v2.1 + Toshiba support
v2.2 + Fix Toshiba boot fail
v2.3 + SanDisk support
v2.4 + Faster Toshiba boot
v2.5 + fix OFW boot
v2.6 + software update, xiao & itsy support
v2.61 + Instinct-NX sdloader, bug fixes
v2.62 + Make 16.0.1 happy
must be RED after USB write. if you see green, set "RGB mode" jumper
WHITE = eMMC write
BLUE = glitch
PURPLE = eMMC boot failure, check CMD / CLK
PINK = NS eMMC init fails, inoperative eMMC ?
YELLOW = eMMC write failure, check D0 / unsupported eMMC
CYAN = no reaction to glitch, check mosfet wire
GREEN = success
Q: What is supported?
A: Erista (v1), Mariko (v2, Lite, OLED)
Q: eMMC types support?
A: Tested on Hynix, Samsung, Toshiba, SanDisk
Q: rp2040 boards support
A: WaveShare 2040-zero/one, xiao-rp2040, adafruit itsybitsy (Pi Pico is not supported for now)
Q: GREEN, but instant reset
A: Clean flux near the RST point
Q: Do I really need 47 Ohm resistors?
A: You can skip them, however in this case you will have to use emuMMC due to the line interference, sysNAND would not boot (sysNAND data can be damaged).
Q: Does the firmware has learning? How to reset statistics
A: Short pin 0 to either 1 or GND during start for chip reset. The statistics is collected each boot. The more you start it - the better it boots.
Q: open source?
A: no
Q: why you made it?
A: to prove it possible!
Q: run Atmosphere?
A: no piracy
v2.5 firmware had a bug with BOOT0 corruption. To recover it:
- boot "Full Stock" using hekate
- update to the latest official firmware over Wi-Fi
- boot "Full Stock" using hekate
- perform a full system reset
- show firmware information
- update firmware from SD card (place update.bin into the root folder)
- rollback to the backup firmware slot
- reset learning statistics
- dump / write sdloader
if you have an rp2040-zero from waveshare/ali then it has a neopixel. It is used for diagnosing proper firmware flashes as well as console glitching. If you plug it in, and flash the uf2 firmware to it and immediately see a red light after flashing (this is not the same as flashing, then unplugging and replugging), then no rgb jumper needs to be made. If on the other hand, you get one quick green flashing light, then you need to bridge the jumper pads indicated to swap the LED colors for proper diagnoses capability.
I think its fix the 'ofw boot' issue. Now its gone.what changed in the latest version?
v2.62 + Make 16.0.1 happywhat changed in the latest version?
can you send link of 2.5 update.binput 2.5 on pico, boot it and then upgrade to 2.6
can you send me the link update.bin 2.5have u tried backflashing the 2.5 yet
I wanted to know whatv2.62 + Make 16.0.1 happy
improved support for 16.0.1?)
check pmcan you send link of 2.5 update.bin
Post automatically merged:
can you send me the link update.bin 2.5
nopeHello there, with the last UF2 version, do we still have to do the unlock thing with Hekate ?
Have you tried the reset statistic, maybe the statistic corrupted, for the oled?erista patched updated to 2.62: fixed ofw boot everything works,. Thanks!!!
Oled updated to 2.62: Blue led then red led then ofw, can´t lauch hekate anymore
i´ve updated directly and now cant boot hekate so can´t clear stadistics.check pm
Post automatically merged:
nope
Post automatically merged:
Have you tried the reset statistic, maybe the statistic corrupted, for the oled?
update has a protection, it completes only on a successful boot. so just power it on again to launch the previous firmware.Oled updated to 2.62: Blue led then red led then ofw, can´t lauch hekate anymore
My Switch (v2 Mariko) regular version is same state after the update.erista patched updated to 2.62: fixed ofw boot everything works,. Thanks!!!
Oled updated to 2.62: Blue led then red led then ofw, can´t lauch hekate anymore
please try reboot from OFW. I rolled back that change in 2.63Blue led then red led then ofw, can´t lauch hekate anymore
Is it an Oled?@Modzvilleusa i removed my chip and im still getting purple screen a death