We haven't yet seen "picofly" cause a brick, so this is definitely a unique situation so far- and may be something we need to keep an eye on if others' consoles have this problem in the future.
- Joined
- Jan 11, 2015
- Messages
- 754
- Trophies
- 0
- Age
- 36
- Location
- Makati
- Website
- leerz25.sitesled.com
- XP
- 2,189
- Country
yes, that's why i have brought it to attention, i have modded plenty of switches from eristas to latest oled aula, so i pretty much know what i'm doing installation hardware and software wise,
i don't mean to fear monger, i'm not making false information so do not worry about reliability if i somehow made a booboo accidentally contaminated my data and mixing up the backups, i'm pretty positive picofly caused the softbrick.
nonetheless, any other tester should do their diligence in saving their switch guinea pigs data, esp the anon uf2 files are flying out of nowhere.
additional info, the nosd screen seem to be from a recent build of hwflynx
This is an interesting idea. It would be ideal to check this after reading the EMMC dump.
First make the original dump, then install rp2040 and make comparisons.
Then write the original dump back and put the hwfly and do the comparison again.
So we can find out what is being patched. I checked this on my erista model and the patched boot0 matched the pieces of code from firmware.bin, which I took from the github repository.
To do this, you need to reball emmc + programmer)
First make the original dump, then install rp2040 and make comparisons.
Then write the original dump back and put the hwfly and do the comparison again.
So we can find out what is being patched. I checked this on my erista model and the patched boot0 matched the pieces of code from firmware.bin, which I took from the github repository.
To do this, you need to reball emmc + programmer)
The payload is a modified version of HWFLY's with some additional code to overwrite the keyslots before chainloading a secondary payload.
That's really quite unnecessary. These comparisons could be done on a V2 console so its eMMC could be connected to an adapter without risking damage from doing repeated and unneeded BGA soldering. OR, it could be done but just using an RP2040 to dump the contents of boot0 over UART. We really don't need to do that though, we know exactly which blocks are modified, what those blocks are used for normally, and what the chips are using them for. It's a total replacement of the primary boot control table for one that will load our payload from a spare section of the b0 partition. This payload could be anything, as long as it is signed using the key stored in the BCT. BCT just tells the boot processor what it should do.
"you cannot bypass the chip by pressing the volume buttons. How would that even work? You see my video above showing how it normally works with a mod chip? The coding in the payload if u hit both volumes on the "no SD screen" it will boot stock. bypassing\disabling the chip.... I want to know have u tried with the pico....
If you're getting the "no SD" screen then yes, you can boot stock using the volume buttons.
Post automatically merged:
At least considering the raw sdloader binary data, the sdloader is custom-made.
Newest ubuntu fw:
HWFLY-NX sdloader:
Last edited by Piorjade,
This is incorrect. It can boot Hekate. It cannot boot Atmosphere CFW. Through Hekate you can also boot Android and L4T Ubuntu. You can also boot stock Horizon.
fixed v2.5yes, I understand this from reading all the 78 pages
i wish mena/phenom could dropby this thread also
also forewarning, anyone attempting to try this.
backup your nand first, boot0,boot1 from a normal chip (hwfly or sx)
I did some stuff earlier and switch won't boot hos even with the pico is not connected
1. first install success, can get to hekate, get boot hos by pressing reboot to ofw
2. dumped boot0, boot1 with picofly
3. restored a mariko (lite) boot0, boot1 i had from a donor
4. picofly took a few seconds longer to glitch and call hekate
5. tried to reboot to ofw (normally it would start ofw) but now it is = BLUESCREEN
6. restored boot0, boot1 that i dumped from pico, no more bluescreen BUT
7. switch will boot hekate fine, but will blackscreen when restart to ofw, or even if the chip /picofly is removed
will put back a hwfly chip and restore boot0, boot1 from there maybe it will be fixed
i'm calling it softbrick for now, boots hekate, but no longer boots ofw even if the chip is removed.
so again, warning to all, do not trust the boot0/boot1 dump or any other dump made from picofly , will install a hwfly chip tomorrow (it's 11PM here +PST)
Did this firmware clean keyslots and block tsec after initialization? As I remeber SX OS's original sdloader does so
It can be "no piracy" like "I will not add support of Atmosphere launching" and like "I will block Atmosphere launching". Not the same.
I think it's pretty clear that the sole reason why he used a custom sdloader / bct was to block Atmosphere.
But I'm relieved, it seems like he isn't just another HWFLY competitor trying to make money
Also keeps Ninty Ninjas at bay. This way, if someone were to “figure it out“, that’s on them.
I’m alright with it as is. I have two unpatched Switches so I’m not in any need for Atmosphere on it. I have plenty of legit games to play and now we can boot into Android/L4T Ubuntu on it.
Might get a Switch Lite just for a dedicated handheld. You can get one pretty cheap on eBay. A dedicated Lakka handheld device does sound enticing. Plus both of my unpatched Switches are banned, so this helps me not be banned on that one too for doing or forgetting to to something dumb.
Might get a Switch Lite just for a dedicated handheld. You can get one pretty cheap on eBay. A dedicated Lakka handheld device does sound enticing. Plus both of my unpatched Switches are banned, so this helps me not be banned on that one too for doing or forgetting to to something dumb.
Thank you to everyone and all ur hard work. There are a few insider memes in the video, so over look somethings. Now I can play raid shadow legends on my OLED!
Last edited by Magnus Hydra,
Similar threads
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
BigOnYa:
Anybody here have a Xbox series S and a series X, is the performance difference noticeable? Not worried about 4k. I have a series X but not a series S and was curious. (Reason- I was thinking of buying a series S for a second tv, for when grandkids come over, to keep them off my X) -
-
-
-
-
-
-
-
-
