Hacking Hardware Picofly - a HWFLY switch modchip

[rehius]

Nobody can help

but I created 2.78 for you

 

[superfiege]

but I created 2.78 for you

Hey thank you very much @rehius !!!!
Do you think it was a timing-problem?
I saw you restructured error-handling and a slower glitching, is that right?
I will try it if i run into the problem again.

 

[rehius]

Do you think it was a timing-problem?

There were no retries for various eMMC failures, now it's 4 attempts no matter what. Should be enough for your case

 

[superfiege]

There were no retries for various eMMC failures, now it's 4 attempts no matter what. Should be enough for your case

This sounds very very promising!!! Thank you! I have a friend with an oled with this issue. Will give you feedback when he updated!

 

[Jkop]

but I created 2.78 for you

Thank you rehius! Unfortunately it didnt work. I actually have 2 consoles a SK Hynix and a Samsung both with different chips that are doing that. I do change to Instinct V6 and it works fine

 

[rull_bull]

Thank you rehius! Unfortunately it didnt work. I actually have 2 consoles a SK Hynix and a Samsung both with different chips that are doing that. I do change to Instinct V6 and it works fine

Aliexpress chip? Have you checked the values on the resistors on the chip? Changed them so you have 100/100/47ohm?

 

[jkyoho]

Thank you rehius! Unfortunately it didnt work. I actually have 2 consoles a SK Hynix and a Samsung both with different chips that are doing that. I do change to Instinct V6 and it works fine

picture of your chips didnt work?

 

[rehius]

Thank you rehius! Unfortunately it didnt work. I actually have 2 consoles a SK Hynix and a Samsung both with different chips that are doing that. I do change to Instinct V6 and it works fine

do you have the same **= error? okay, we can try to increase the waiting timeout, try 2.79

 

[Jkop]

Aliexpress chip? Have you checked the values on the resistors on the chip? Changed them so you have 100/100/47ohm?

Yes these are the chips I used. Kamikazed dat0. The left I used with samsung emmc and right with SK hynix. I would have to check the ohms but I think the 2.79 firmware from rehius fixed it. Will keep you updated

Post automatically merged: Sep 3, 2024

picture of your chips didnt work?

I just updatd to 2.79 from rehius and it works. If I get errors I will try to record it it will be a long video because only 1 of 15 boots goes into OFW

Post automatically merged: Sep 3, 2024

do you have the same **= error? okay, we can try to increase the waiting timeout, try 2.79

Yes I did get the **= on 2.78. But I think the 2.79 has fixed it I am sitting here testing it and turning it off and on and no problems will keep you updated

Thank You!!!!!!

 

[Stonehearth]

Aliexpress chip? Have you checked the values on the resistors on the chip? Changed them so you have 100/100/47ohm?

Issue: 1 of 150 units modded (1 unit is an OLED and 1 unit is a common Switch) doesn't turn on OFW from Hekate (stuck in the middle between the first and the second logo, sometimes stuck on the second logo too, some times black screen after second logo...)

Recommendation from the forum: As well said by all of you there're differents brand of CPU and RAM that require Change/swap resistance.


Evidences: I'm curious about that, because i'm getting those measured values (YELLOW) and what I see you recommend using HWFLY OR WHATEVER (not a dev board) = in green.

The following image is pico-corefly for a Normal Switch.

Are those values in GREEN the good ones my lords?
Will this green values work for every CPU/RAM combination?
Will this green values work too for a OLED?

This can be solved just updating the firmware RP2040 with the last Rehius version 2.79 ????

Thanks in advance

 

[jkyoho]

Issue: 1 of 150 units modded (1 unit is an OLED and 1 unit is a common Switch) doesn't turn on OFW from Hekate (stuck in the middle between the first and the second logo, sometimes stuck on the second logo too, some times black screen after second logo...)

Recommendation from the forum: As well said by all of you there're differents brand of CPU and RAM that require Change/swap resistance.


Evidences: I'm curious about that, because i'm getting those measured values (YELLOW) and what I see you recommend using HWFLY OR WHATEVER (not a dev board) = in green.

The following image is pico-corefly for a Normal Switch.

Are those values in GREEN the good ones my lords?
Will this green values work for every CPU/RAM combination?
Will this green values work too for a OLED?

This can be solved just updating the firmware RP2040 with the last Rehius version 2.79 ????

Thanks in advance


View attachment 456051

I believe the 1st 47 ohm from top is RST not CLK.
So you should remove/replace rst 47 ohm with 0 ohm or blob of solder
https://gbatemp.net/threads/error-code-2002-3540.635990/post-10295047

 

[rull_bull]

Issue: 1 of 150 units modded (1 unit is an OLED and 1 unit is a common Switch) doesn't turn on OFW from Hekate (stuck in the middle between the first and the second logo, sometimes stuck on the second logo too, some times black screen after second logo...)

Recommendation from the forum: As well said by all of you there're differents brand of CPU and RAM that require Change/swap resistance.


Evidences: I'm curious about that, because i'm getting those measured values (YELLOW) and what I see you recommend using HWFLY OR WHATEVER (not a dev board) = in green.

The following image is pico-corefly for a Normal Switch.

Are those values in GREEN the good ones my lords?
Will this green values work for every CPU/RAM combination?
Will this green values work too for a OLED?

This can be solved just updating the firmware RP2040 with the last Rehius version 2.79 ????

Thanks in advance


View attachment 456051

No, the recommended values are
100ohm on dat0
100ohm on cmd
47ohm on clk

And like the guy above said, you have mixed up clk and rst placement on your picture. It’s the other way around.

Just exchange them on the chip with the correct resistors , really easy.

 

[Stonehearth]

No, the recommended values are
100ohm on dat0
100ohm on cmd
47ohm on clk

And like the guy above said, you have mixed up clk and rst placement on your picture. It’s the other way around.

Just exchange them on the chip with the correct resistors , really easy.

Ok, so wrapping up, for NS V1/V2, OLED or Lite the common working values for all CPU/RAM/NAND combinations is A or B, or it dpends if it's V1/V2 o OLED, or just when try when Read values not working?

 

[rull_bull]

Ok, so wrapping up, for NS V1/V2, OLED or Lite the common working values for all CPU/RAM/NAND combinations is A or B, or it dpends if it's V1/V2 o OLED, or just when try when Read values not working?

B is the recommended values and the one to use, tried and tested since the beginning by the people here and as the picofly guide will tell you.

And i dont know why you keep on insisting with other values?

 

[Jkop]

Yes these are the chips I used. Kamikazed dat0. The left I used with samsung emmc and right with SK hynix. I would have to check the ohms but I think the 2.79 firmware from rehius fixed it. Will keep you updated

Post automatically merged: Sep 3, 2024

I just updatd to 2.79 from rehius and it works. If I get errors I will try to record it it will be a long video because only 1 of 15 boots goes into OFW

Post automatically merged: Sep 3, 2024

Yes I did get the **= on 2.78. But I think the 2.79 has fixed it I am sitting here testing it and turning it off and on and no problems will keep you updated

Thank You!

do you have the same **= error? okay, we can try to increase the waiting timeout, try 2.79

2.79 is also a no go. It was working great for a while. It gives a *=* code now. Video below error start around 38 seconds but every other video boot works fine

 

[rehius]

2.79 is also a no go. It was working great for a while. It gives a *=* code now. Video below error start around 38 seconds but every other video boot works fine

well, since I don't have such console, we can only try messing with attempts and timeouts
(try 2.80)

 

[Threex]

well, since I don't have such console, we can only try messing with attempts and timeouts
(try 2.80)

2.80 ver. only for oled? Work with Switch v2?

 

[rehius]

2.80 ver. only for oled? Work with Switch v2?

All firmwares should work on the whole range of NS models. I personally test on my Switch Lite

 

[Nephiel]

Yes these are the chips I used. Kamikazed dat0. The left I used with samsung emmc and right with SK hynix. I would have to check the ohms but I think the 2.79 firmware from rehius fixed it. Will keep you updated

What are the values of these resistors?

 

[rehius]

What are the values of these resistors?

BTW: such resistor placement may cause a black screen, OFW boot issues, etc. So I suggest to avoid this kind of PCB design. Resistors must be far from the rp2040 MCU on the edge of the PCB close to the solder points.