Hacking Hardware Picofly - a HWFLY switch modchip

[abal1000x]

wdym by pull up? also werent you talking about resistors near the emmc, not the cmd?

What i mean by 'pull up' is the cmd line normal is high voltage, data low voltage.
View attachment 434628
Resistor under the triangle is the cmd line pullup resistor its should be 4k7 (cmiiw).

From the datasheet of the emmc
View attachment 434629

 

[naldo29]

What i mean by 'pull up' is the cmd line normal is high voltage, data low voltage.
View attachment 434628
Resistor under the triangle is the cmd line pullup resistor its should be 4k7 (cmiiw).

From the datasheet of the emmc
View attachment 434629

yeah. i checked rn. It measured 4k7 sad

 

[superxoi]

its 100% something hardware related. Just tried restoring my console by following level 1 and level 2 of sthetix guide and even wiping the entire nand and replacing it with a new one resorted with the same exact issue. Could there be something in the hardware side that could cause this? becuase it would be the only explanation onto why both emunand and sysnad both stopped working on the same time and why rebuilding my nand didnt work either and just produced the same issue

From 17.0 + you have to launch the console in syscfw first after doing unbrick (sthetix method). Did you try it? If you have tried it but no result then it definitely hardware related. To check this you can run android to test. If the console can use android mean that your emmc issue , if not then you can be sure that it is hardware related. The "nintendo" then shut off causes by myriad reason you have to check it your self. The last time i fixed one was the dram getting very hot when booting. Some mosfet can cause it too but sadly you have to check yourself there is no way to be sure which one is causing it.

 

[naldo29]

From 17.0 + you have to launch the console in syscfw first after doing unbrick (sthetix method). Did you try it? If you have tried it but no result then it definitely hardware related. To check this you can run android to test. If the console can use android mean that your emmc issue , if not then you can be sure that it is hardware related. The "nintendo" then shut off causes by myriad reason you have to check it your self. The last time i fixed one was the dram getting very hot when booting. Some mosfet can cause it too but sadly you have to check yourself there is no way to be sure which one is causing it.

thank you, this info has been extremely helpful.

 

[Hassal]

its 100% something hardware related. Just tried restoring my console by following level 1 and level 2 of sthetix guide and even wiping the entire nand and replacing it with a new one resorted with the same exact issue. Could there be something in the hardware side that could cause this? becuase it would be the only explanation onto why both emunand and sysnad both stopped working on the same time and why rebuilding my nand didnt work either and just produced the same issue

My friend I don't think its a hardware issue. If that was the case you would never reach this stage of the boot process.

Take it step by step.
If there's a problem in your emuNAND it can be fixed since the least requirement is your prodinfo in order to restore it. Fixing your sysNAND can be a different story depending on what kind of errors you're facing.

Which firmware were you using? Missing keys can prevent you from booting.
I remember when 17.0 first came out I forget to include the newer keys which lead to the boot screen to get stuck.

I think both your systems stopped was sheer coincidence and by that I mean you didn't know the condition of your sysNAND just BEFORE the emuNAND problem.

 

[Eds05]

Hello guys,

Sorry Im out of the topic but I throw a bottle here in case

Im looking for a cnc milling machine or a fiber laser to do PCB reverse engineering and Im sure here I can find some specialists !

The goal is too delayer a PCB. I would like to have as a project to RE the next switch when it will be released or participate at least to the documentation (make a BOM etc…) On the actual switch we have 10 layers.

I already have equipments as microscope, tools, multimeters, oscilloscope, power supply, infrared camera etc… And I would like now a cnc or a fiber laser to go farther.

 

[Danook28]

My friend I don't think its a hardware issue. If that was the case you would never reach this stage of the boot process.

Take it step by step.
If there's a problem in your emuNAND it can be fixed since the least requirement is your prodinfo in order to restore it. Fixing your sysNAND can be a different story depending on what kind of errors you're facing.

Which firmware were you using? Missing keys can prevent you from booting.
I remember when 17.0 first came out I forget to include the newer keys which lead to the boot screen to get stuck.

I think both your systems stopped was sheer coincidence and by that I mean you didn't know the condition of your sysNAND just BEFORE the emuNAND problem.

Boot1 boot0 prod kyes and new mmc and donor nand donor prod kyes... Level 1 unbrike well help you...

 

[Hassal]

Boot1 boot0 prod kyes and new mmc and donor nand donor prod kyes... Level 1 unbrike well help you...

Well you should direct that to him not me. I was advising him how to restore his emuNAND.

 

[thesjaakspoiler]

Hello guys,

Sorry Im out of the topic but I throw a bottle here in case

Im looking for a cnc milling machine or a fiber laser to do PCB reverse engineering and Im sure here I can find some specialists !

The goal is too delayer a PCB. I would like to have as a project to RE the next switch when it will be released or participate at least to the documentation (make a BOM etc…) On the actual switch we have 10 layers.

A CNC milling machine that is precise enough to remove 1 layer will cost you a fortune.
A copper layer on a PCB is around 0.03 mm in height.

Fine grid sandpaper is much more affordable and much more reliable.
That is how most people delayer PCBs :
https://bitbuilt.net/forums/index.php?threads/nintendo-switch.3998/

 

[Eds05]

A CNC milling machine that is precise enough to remove 1 layer will cost you a fortune.
A copper layer on a PCB is around 0.03 mm in height.

Fine grid sandpaper is much more affordable and much more reliable.
That is how most people delayer PCBs :
https://bitbuilt.net/forums/index.php?threads/nintendo-switch.3998/

Good to know ! Thank you Im gonna read it.

 

[Modificatorul]

Thank you Doc for rev 2.0c, works great.
@psycho-neon

​

 

[nuage83]

I found a solution for OLED switches with Dat0 adapter which are capricious and refuse to start.


I tap lightly on the place indicated in the photo, this is obviously enough to put the adapter back on the chip and the console then starts on Atmosphere.

Could this pose a real risk for the console?

 

[QuiTim]

I found a solution for OLED switches with Dat0 adapter which are capricious and refuse to start.


I tap lightly on the place indicated in the photo, this is obviously enough to put the adapter back on the chip and the console then starts on Atmosphere.

Could this pose a real risk for the console?

Did this a couple of times on the first Oled I moded (for a friend) but after a while it did not work anymore so I changed the dat0 adapter and still works to this day (while taking a beating constantly from his 2 kids).

Now, after some experience with these consoles, I think this is not a wise thing to do since depending on how loose the adapter is and which side is leaning toward to under emmc it might lead to corruption of nand or maybe some other “mysterious” issues that we faced here while using dat0 adapters.

Better to redo the work (or better yet do a reball or kamikaze) than to rely on a “lucky slap”

 

[Danook28]

Did this a couple of times on the first Oled I moded (for a friend) but after a while it did not work anymore so I changed the dat0 adapter and still works to this day (while taking a beating constantly from his 2 kids).

Now, after some experience with these consoles, I think this is not a wise thing to do since depending on how loose the adapter is and which side is leaning toward to under emmc it might lead to corruption of nand or maybe some other “mysterious” issues that we faced here while using dat0 adapters.

Better to redo the work (or better yet do a reball or kamikaze) than to rely on a “lucky slap”

Joycon buzzing play cult of lamb and 3 to 4 days the adapter move littel bit and the cfw not working so i open console and fix adapter with new one add bit more iron under the point that conect to dat0 iron ball and to gnd legs and now cfw working...

 

[QuiTim]

Joycon buzzing play cult of lamb and 3 to 4 days the adapter move littel bit and the cfw not working so i open console and fix adapter with new one add bit more iron under the point that conect to dat0 iron ball and to gnd legs and now cfw working...

Wow, i never really thought about it but i think you are right, the joycon vibration could actually play a big role on displacing dat0. After all, Nikola Tesla almost knocked down an entire building using a small vibrating machine.

 

[abal1000x]

Thank you ,Doc, for rev 2.0c, works great.
@psycho-neon

​

View attachment 435143

lol flux capacitor, docs from go back to the future

Post automatically merged: May 4, 2024

I found a solution for OLED switches with Dat0 adapter which are capricious and refuse to start.


I tap lightly on the place indicated in the photo, this is obviously enough to put the adapter back on the chip and the console then starts on Atmosphere.

Could this pose a real risk for the console?

common issue on flex dat0 adapter

 

[RatchetRussian]

Thank you ,Doc, for rev 2.0c, works great.
@psycho-neon

​

View attachment 435143

Does it fit under the metal shield on the lite or do you need to cut the shield?

 

[Modificatorul]

Does it fit under the metal shield on the lite or do you need to cut the shield?

Yes,with 0.6 mm pcb ,0.5mm 3m tape and kapton on top, but in that position the shield create same pressure on rp ic and flash .

 

[Tembokbesi]

Hi. It is normal? Im using intinct nx v6

 

[abal1000x]

Hi. It is normal? Im using intinct nx v6
View attachment 435732View attachment 435731

normal