That is why you can't dump your keys.Therefore, I have not yet flashed unlock.uf2
That is why you can't dump your keys.Therefore, I have not yet flashed unlock.uf2
It's normal that hekate shows sbk as FFF... on mariko.View attachment 362519
I have successfully dumped the key after flashing the unlock.uf2 file !!
But, the secure boot key value remains unchanged at ffff. Could you please explain to me if installing Piko would overwrite the secure boot key to ffff regardless of whether the unlock.uf2 file is flashed or not? Also, are there any potential negative effects of this? I would appreciate your guidance.
tyhe just did not write unlock.uf2 properly
sometimes people drop two .uf2 files, this does not work, it is needed to write them separately
does it dump clean or dirty?That is why you can't dump your keys.
Pics of the internal cuts please, I was thinking of doing this same thing.
Oof was the Switch dusty? I noticed the cotton tops or was it just the thermal paste being like black?Bollox, sorry, just seen this, this is all I have
It's ready to go. But OLED is the hardest/most annoying to mod since you need an ankor or reballing of the eMMC. The Firmware doesn't matter since it's the bootloader that is being abused to inject custom code.Hey im really sorry if this is the wrong place to ask but i have an OLED switch that ofc cant be hacked with fusee gelee. Is this mod chip ready to go or should i wait a bit longer. Also is this chip independant of firmware version (im guessing that it is but its a good idea to check).
Ahh alr, ty for the help. Btw is there like a github for the firmware and what parts do you need for the mod.It's ready to go. But OLED is the hardest/most annoying to mod since you need an ankor or reballing of the eMMC. The Firmware doesn't matter since it's the bootloader that is being abused to inject custom code.
V2.6 that is being developed seem to be a big upgrade so if you don't have to mod it right now, wait a bit.
If this is your first soldering job. It isn't for you.Ahh alr, ty for the help. Btw is there like a github for the firmware and what parts do you need for the mod.
Ty and yeah after seeing everything here im defo gonna actually learn how to solder before doing this.If this is your first soldering job. It isn't for you.
Here is a summary page that try to collect all info and make it easier to find - https://gbatemp.net/threads/picofly-aio-thread.628951/
Hey i just had a look at this thread and saw that it was recomended to get it done by a professional, would this mean sending my switch somewhere or would a high street repair place be able to do it.If this is your first soldering job. It isn't for you.
Here is a summary page that try to collect all info and make it easier to find - https://gbatemp.net/threads/picofly-aio-thread.628951/
Are there any other soldering points besides the emmc chip on patched erista and big mariko switches? I've seen it somewhere, but I don't remember where.Use points not on emmc as its safer (The points on diagram has 2 points and they are already connected so a bridge is fine)
Use toshiba fix then use unlock all on pc first
47ohm some boot ofw some dont but you get slow mode so use it for sure
Are there any other soldering points besides the emmc chip on patched erista and big mariko switches? I've seen it somewhere, but I don't remember where.
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
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
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: GREEN, but instant reset
A: Check your soldering, clean flux. If does not help = add 20K-30K to RST
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.
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
By using the Atmosphere unlock tool you agree to use it for homebrew only.
Way 1 (USB): flash the unlock.uf2 into chip by USB
Way 2 (no USB): run picofly_tb from Hekate, need unlock.bin on the SD carddo not use, bugged.
Boot into Full Stock and perform a full system reset.
Has any information come out about the scheme of the welding points for the Rp2040 Pi Pico? (the version that is a little larger than the zero) in the Pi pico version some names change and I would like to know their equivalence. Thank youLatest 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
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
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: GREEN, but instant reset
A: Check your soldering, clean flux. If does not help = add 20K-30K to RST
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.
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
By using the Atmosphere unlock tool you agree to use it for homebrew only.
Way 1 (USB): flash the unlock.uf2 into chip by USB
Way 2 (no USB): run picofly_tb from Hekate, need unlock.bin on the SD carddo not use, bugged.
Boot into Full Stock and perform a full system reset.
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
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
YELLOW = eMMC write failure, check D0 / unsupported eMMC
CYAN = no reaction to glitch, check mosfet wire
GREEN = success
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
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
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: GREEN, but instant reset
A: Check your soldering, clean flux. If does not help = add 20K-30K to RST
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.
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
By using the Atmosphere unlock tool you agree to use it for homebrew only.
Way 1 (USB): flash the unlock.uf2 into chip by USB
Way 2 (no USB): run picofly_tb from Hekate, need unlock.bin on the SD carddo not use, bugged.
Boot into Full Stock and perform a full system reset.
Has any information come out about the scheme of the welding points for the Rp2040 Pi Pico? (the version that is a little larger than the zero) in the Pi pico version some names change and I would like to know their equivalence. Thank youLatest 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
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
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: GREEN, but instant reset
A: Check your soldering, clean flux. If does not help = add 20K-30K to RST
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.
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
By using the Atmosphere unlock tool you agree to use it for homebrew only.
Way 1 (USB): flash the unlock.uf2 into chip by USB
Way 2 (no USB): run picofly_tb from Hekate, need unlock.bin on the SD carddo not use, bugged.
Boot into Full Stock and perform a full system reset.
for pico u need to wait for the 2.6 fw release i think it added the pico to it not sure thoughHas any information come out about the scheme of the welding points for the Rp2040 Pi Pico? (the version that is a little larger than the zero) in the Pi pico version some names change and I would like to know their equivalence. Thank you
well maybo not so@everyonesweird, it's been partially answered before
- multi-board support (RPi, xiao, zero, one) within the single fw
- OFW support fixes
- brick-proof firmware update through hekate
- sdloader power fixes, should also improve glitch
- maybe some glitch algo improvements
xiao, zero, one
Yes, just cleaning up thermal paste on other switch jobs.Oof was the Switch dusty? I noticed the cotton tops or was it just the thermal paste being like black?
Pico is on the 2.6 support listfor pico u need to wait for the 2.6 fw release i think it added the pico to it not sure though
no one knows when it will be released u have to wait till its done hes doing this in his free time for free so just be patiant and wait :-)
Post automatically merged:
well maybo not so
the pico is to big anyways just try to ur hand one of these chips
@everyonesweird, it's been partially answered before
- multi-board support (RPi, xiao, zero, one) within the single fw
- OFW support fixes
- brick-proof firmware update through hekate
- sdloader power fixes, should also improve glitch
- maybe some glitch algo improvements
Post automatically merged:
they are the same mosfets. third letter means its origin (manufacture)
i thought so wasnt sure thats why i edited :-) dont wane spreead false rumors XdPico is on the 2.6 support list