Hacking Hardware Picofly - a HWFLY switch modchip

[abal1000x]

what is the risk? software or hardware? Where can i find 2.75? On rehius github?
View attachment 398262

"what is the risk? software of hardware?"
This is my opinion might be wrong. In hardware-wise theres should be no problem. But in software-wise, if you use the vanilla rp2040, then you might take the usb out from the board. So you could only update using toolbox.bin. If something error, and the glitch wont work, then to revert back you need to uninstall the rp2040 from the mainboard and put the usb port back.

"On rehius github?"
Yes it is.

 

[Crung]

"what is the risk? software of hardware?"
This is my opinion might be wrong. In hardware-wise theres should be no problem. But in software-wise, if you use the vanilla rp2040, then you might take the usb out from the board. So you could only update using toolbox.bin. If something error, and the glitch wont work, then to revert back you need to uninstall the rp2040 from the mainboard and put the usb port back.

"On rehius github?"
Yes it is.

where can i find your version?

 

[abal1000x]

where can i find your version?

The source code is in here:
https://github.com/abal1000x/usk
branch 'abal_version'
But theres no 'releases', i just too lazy to set it up.

I attach the last build (v200.75), yesterday i update the installation on my brother oled with this firmware.


I also build and attach the v2.76 rehius code, which still not yet on the 'releases'.

 

[Crung]

The source code is in here:
https://github.com/abal1000x/usk
branch 'abal_version'
But theres no 'releases', i just too lazy to set it up.

I attach the last build (v200.75), yesterday i update the installation on my brother oled with this firmware.


I also build and attach the v2.76 rehius code, which still not yet on the 'releases'.

Thanks! One more question before i am going to attempt this. In guide i see i need to put the firmware with ".bin" ending. The picofly firmware has ".uf" ending.
Does this mean that the ".uf" has to be compressed into ".bin" (in case i downloaded ".uf")?
Also is 2.76 safe for usage? Is it confirmed?

 

[abal1000x]

Thanks! One more question before i am going to attempt this. In guide i see i need to put the firmware with ".bin" ending. The picofly firmware has ".uf" ending.
Does this mean that the ".uf" has to be compressed into ".bin" (in case i downloaded ".uf"?

No its 2 different file.

Theres 2 method to update the rp2040 firmware, choose one of it:

v2.76.uf2 => This is installed by putting the rp2040 into boot mode (press and hold the boot button and plug the usb to the pc, then release the button). There will be new storage shows on the explorer, then drag-n-drop that file to the drive shown.

update.bin => This is copy-pasted into the microsd root, then goes to the toolbox and do update.

 

[Crung]

Update failed X_X Now it boots to OFW. Guess its time to solder usb port X_X

Post automatically merged: Oct 9, 2023

Nevermind. For some reason first boot was to OFW. Now it works.

 

[abal1000x]

Update failed X_X Now it boots to OFW. Guess its time to solder usb port X_X

Its suck.
When i modify the code, its happened all the time.

Now for development, i've use the rp2040-tiny.
Its way easier to upload the firmware.

 

[Crung]

Its suck.
When i modify the code, its happened all the time.

Now for development, i've use the rp2040-tiny.
Its way easier to upload the firmware.

Im confused now. Did it work or not (how can i check my current picofly firmware)?
First boot was straight to OFW.
Now the chip works,it glitches.

Post automatically merged: Oct 9, 2023

So this did not fix my problem. I still have error in OFW. Im doing a emmc sthetix LVL 1 repair, and i got this error. What does this mean?

 

[abal1000x]

Im confused now. Did it work or not (how can i check my current picofly firmware)?
First boot was straight to OFW.
Now the chip works,it glitches.

Post automatically merged: Oct 9, 2023

So this did not fix my problem. I still have error in OFW. Im doing a emmc sthetix LVL 1 repair, and i got this error. What does this mean?
View attachment 398273

"how can i check my current picofly firmware?"
Using the toolbox, after successfull glitch.

I've no idea for level 1 sthetix. Hopefully other might give a clue on it.

 

[Crung]

"how can i check my current picofly firmware?"
Using the toolbox, after successfull glitch.

I've no idea for level 1 sthetix. Hopefully other might give a clue on it.

Ok so. I checked picofly version and i was still on 2.73. I tryed several times more to update, and it finnaly worked.
After attempting to do a new NAND write from scratch with prodinfo, OFW was stuck on logo . So i did a NAND restore to my old NAND save (the one that i was getting 3539 error on ).
Now when trying to start OFW i get this screen

Well.

 

[abal1000x]

Ok so. I checked picofly version and i was still on 2.73. I tryed several times more to update, and it finnaly worked.
After attempting to do a new NAND write from scratch with prodinfo, OFW was stuck on logo . So i did a NAND restore to my old NAND save (the one that i was getting 3539 error on ).
Now when trying to start OFW i get this screen
View attachment 398276
Well.
View attachment 398280

Do you use flex cable to the emmc dat0?

 

[Hassal]

Im confused now. Did it work or not (how can i check my current picofly firmware)?
First boot was straight to OFW.
Now the chip works,it glitches.

Post automatically merged: Oct 9, 2023

So this did not fix my problem. I still have error in OFW. Im doing a emmc sthetix LVL 1 repair, and i got this error. What does this mean?
View attachment 398273

It means your eMMC went bad.

 

[LuigiGad]

The source code is in here:
https://github.com/abal1000x/usk
branch 'abal_version'
But theres no 'releases', i just too lazy to set it up.

I attach the last build (v200.75), yesterday i update the installation on my brother oled with this firmware.


I also build and attach the v2.76 rehius code, which still not yet on the 'releases'.

Just put it on my switch lite (2.76 via toolbox). Seems slightly faster in the glitch

 

[Vigintiduo]

Can anyone tell me where in the hell are the SDA and SCL points on this V1 unit lol? It doesn't look like the image in the guide at all

 

[rehius]

on this V1 unit

for v2 only, not tested on v1 (not required)

 

[JPelayo]

yep, solder to the middle pins of the flex

What about using a that same ribbon on a hwfly chip. Will it work or need to solder directly to the chip? Thanks

 

[thesjaakspoiler]

As a soldering newbie, I'm very scared to try and do this job myself!

Go practice on a bunch of (unrelated) boards because you need both the skills and to figure out if you even have the right equipment for the job.
Things are really tiny and it's rather easy to mess up.
If you go working on your switch straight away, you'll probably ruin it.

 

[Crung]

Do you use flex cable to the emmc dat0?

its a v2. no flex. i have vanilla rp2040

 

[abal1000x]

its a v2. no flex. i have vanilla rp2040

Ah yes, you're right, its v2.
My minds focus are splitted to other things.

 

[Crung]

The emmc is totally bricked now I was doing a emmc restore from an older state, and i got error+ slow emmc warning when flashing. Now i am unable to glitch. I get *=* No eMMC block 0 read (eMMC init failure?) or =** eMMC init failure during glitch process (if i take the emmc out and put it back,battery unplugged dont worry).
I dont really feel bad about bricking it (that is a lie ) since i already tought about it as a dead nintendo.This nintendo gave me so many problems. I wonder if i should declare it as for parts and be done with it and move on with my life, or if i should make a final attempt and buy this product in order to try to rewrite the emmc (i have a nand restore wich i suspect is not good, BUT I HAVE THE PRODKEYS)

Post automatically merged: Oct 10, 2023

A wow that is very stupid.
If i keep pressure with my finger on the emmc connector, i am able to glitch :| I think i have a damaged plastic connector or connector pins. Super glue time . Im JOKING. Agh i really hope i wont have to change board connector X_X

So hear me out. I have another theory. Once the console was getting hot, even in CFW the screen would freeze. What was happening i think, was the emmc was getting disconnected since it doesnt have a perfect connection. That might not matter since i was basically booting from SD card, but it might have had some effect on the processor (the connecting and disconnecting of the emmc) resulting in it to stall and freeze ?

I had some flux into the connector.After cleaning it with cotton and alcohool (very carefully) it wont even glitch when i am putting pressure on the connector XD its like... evolving BUT BACKWARDS XD

Changed my connector because it looked like sht. Still no luck.