Hacking Hardware Picofly - a HWFLY switch modchip

Danook28 · Jun 5, 2023

Mr Skinner said:
View attachment 375961

These capacitors follow the same rule?

Sp1 capacitor and sp2 capacitor value left 11.1 ohm or 10.1 ohm. And from right is 0.1 ohm. The sp1 is from right is 11.1 ohm or 10.1 ohm and from left is 0.1 ohm. Use multimater. The value can up 12.1 ohm to 16. 1 to 18.1 ohm. I read value from v1 and v2 and oled.
And after add Flex Cable. (Is same) .
Diode mod beep from left and right and the it is beeping from both side (console working)

sergiochendry · Jun 5, 2023

abal1000x said:
Theres no solution so far.
Someone saying succeed solve it by restore the nand content from backup.

My current analysis is the nand data corrupted, because of improper CMD/CLK/D0 used.
The problem is how to restore it, since its usually before even goes to hekate to backup the nand.

Try use ums-loader, does it work? Try to backup the emmc using pc, does it work?

how can i try ums loader without hekate?

abal1000x · Jun 5, 2023

sergiochendry said:
how can i try ums loader without hekate?

picofly will run sdcard://payload.bin after glitch.

You could put any payload in there, hekate just one of it.

sergiochendry · Jun 5, 2023

abal1000x said:
picofly will run sdcard://payload.bin after glitch.

You could put any payload in there, hekate just one of it.

oh you mean like memloader.bin?

abal1000x · Jun 5, 2023

sergiochendry said:
oh you mean like memloader.bin?

rename ums-loader.bin into payload.bin in root sdcard

sergiochendry · Jun 5, 2023

abal1000x said:
rename ums-loader.bin into payload.bin in root sdcard

still same
black screen
is there any solution?

abal1000x · Jun 5, 2023

sergiochendry said:
still same
black screen
is there any solution?

The glitch ok, payload.bin in microsd, but still blackscreen?

sergiochendry · Jun 5, 2023

abal1000x said:
The glitch ok, payload.bin in microsd, but still blackscreen?

yes, glitch ok
i already place payload.bin in micro sd
download from here
https://github.com/lulle2007200/ums-loader
rename to payload.bin
still blackscreen

abal1000x · Jun 5, 2023

sergiochendry said:
yes, glitch ok
i already place payload.bin in micro sd
download from here
https://github.com/lulle2007200/ums-loader
rename to payload.bin
still blackscreen

Logically its not a corrupted nand content.

I think its more probable the ram is malfunction.
Since ums-load use only iram.

You might check the connection between the ram and the cpu maybe theres some resistor burned.
Or you could check the supplied voltage to the ram, maybe the voltage is not being supplied.
If the voltage in problem, you might track it, which ic supplied the voltage. Maybe some resistor burned.

Post automatically merged: Jun 5, 2023

sergiochendry said:
yes, glitch ok
i already place payload.bin in micro sd
download from here
https://github.com/lulle2007200/ums-loader
rename to payload.bin
still blackscreen

Before the glitch happened, theres a write to emmc, and read from emmc.
So we could assume the nand is okay hardware perspective.

I assume the next step is, the cpu will fetch the machine code from the emmc to the ram, then run it.
The bootloader (BCT) in the emmc is modified, and it will run the payload.bin (which is loaded to the ram).

So the most probable scenario is theres problem on ram.

sergiochendry · Jun 5, 2023

abal1000x said:
Logically its not a corrupted nand content.

I think its more probable the ram is malfunction.
Since ums-load use only iram.

You might check the connection between the ram and the cpu maybe theres some resistor burned.
Or you could check the supplied voltage to the ram, maybe the voltage is not being supplied.
If the voltage in problem, you might track it, which ic supplied the voltage. Maybe some resistor burned.

Post automatically merged: Jun 5, 2023

Before the glitch happened, theres a write to emmc, and read from emmc.
So we could assume the nand is okay hardware perspective.

I assume the next step is, the cpu will fetch the machine code from the emmc to the ram, then run it.
The bootloader (BCT) in the emmc is modified, and it will run the payload.bin (which is loaded to the ram).

So the most probable scenario is theres problem on ram.

Btw i remember
I ripped of some resistor while try to open cpu shield using my nail
I solder back again
the left resistor
Is that resistor burned?

abal1000x · Jun 5, 2023

sergiochendry said:
Btw i remember
I ripped of some resistor while try to open cpu shield using my nail
I solder back again
the left resistor
Is that resistor burned?

Seems not.

Tracing using https://balika011.hu/switch/oled/ That resistor seems goes to supply voltage to the emmc.
Since the glitch worked, i think its okay.

sergiochendry · Jun 5, 2023

abal1000x said:
Seems not.

Tracing using https://balika011.hu/switch/oled/ That resistor seems goes to supply voltage to the emmc.
Since the glitch worked, i think its okay.

i remember after i add more resistor 47+47
black screen happen
before that, picofly logo show but cannot enter ofw
you think add more resistor can make ram failed
just wonder

Adran_Marit · Jun 5, 2023

lightninjay said:
If it doesn't exist, then it will never be any issue (I copied the LED code data directly from Rehius' post, so if he still includes it, then so will I)

this tbh

abal1000x · Jun 5, 2023

sergiochendry said:
i remember after i add more resistor 47+47
black screen happen
before that, picofly logo show but cannot enter ofw
you think add more resistor can make ram failed
just wonder

It should not.

I think i misunderstand something.
I assume when you say the glitched work, the picofly logo shows.
So how you know the glitch already work?

Post automatically merged: Jun 5, 2023

Adran_Marit said:
this tbh

I read the code, and theres no detection on clk part or throwing the pulse light code.
Yet it exist on the 'Led Indication' part.
I have ask the man, but he still not yet replied. I am too shy to ask him again.

bilalhassan341 · Jun 5, 2023

Finally Saved my Blue Screen switch. First I Reflow the Apu the blue screen gone and then black screen comes. Checked the whole board shorts and everything and didn't find any shorts. Then, I tried to install the picofly and switch showed the No SD Logo. Put the hekate into sd card. Restore the the boot 0 and 1 using Sthetix guide for level 1 unbricking. Switch boots to home page after reboot to OFW.

sergiochendry · Jun 5, 2023

sergiochendry said:
Hello, i bought new switch oled and get toshiba nand
when i press the power on
Picofly logo show normaly, when i press volume -+ to get OFW, just show blackscreen
I unplug battery and plug in back, i got error ** (RST)
I change RST cable and now got =**
Picofly logo show again and cannot get into OFW
Just blakscreen again

So i add more resistor cause i think toshiba need more resistor (47+47)
And now got =***

this is my first post about my switch oled problem
after i remove pico
i got nintendo logo and switch logo, but never get into menu
restart switch and get black screen
i realize my dat0 adapter suck so i change the good one
and i got succes led light

abal1000x said:
It should not.

I think i misunderstand something.
I assume when you say the glitched work, the picofly logo shows.
So how you know the glitch already work?

i know glitch work by see led light

fox87 · Jun 5, 2023

Danook28 said:
1.0 uf 6.3 v ( 0201)

What Software is that @Danook28 ?

abal1000x · Jun 5, 2023

sergiochendry said:
this is my first post about my switch oled problem
after i remove pico
i got nintendo logo and switch logo, but never get into menu
restart switch and get black screen
i realize my dat0 adapter suck so i change the good one
and i got succes led light

i know glitch work by see led light

So if we analyze the flows like this:

"when i press the power on
Picofly logo show normaly, when i press volume -+ to get OFW, just show blackscreen"
At this point i suspect the partition corrupted, need to rebuild.

"I unplug battery and plug in back, i got error ** (RST)"
The RST line is not stable.

"I change RST cable and now got =**"
RST line stable, Emmc init worked, but failed in the glitch stage.
I suspect the Dat0 is 'lightly' touch the Dat1, so the emmc its not stable.

"Picofly logo show again and cannot get into OFW
Just blakscreen again"
When the glitch work, the initial problem occured, which is partition corrupted.

"So i add more resistor cause i think toshiba need more resistor (47+47)
And now got =***"
At this point, the initialization of emmc is not even detected, after reset, before glitch.
Could be problem with combination of CLK, CMD, or Dat0.

"this is my first post about my switch oled problem
after i remove pico
i got nintendo logo and switch logo, but never get into menu"
The emmc hardware still okay, but the same problem still not fixed, which is the nand partition corrupted.

"i realize my dat0 adapter suck so i change the good one
and i got succes led light"
If the glitched worked, the picofly should shows.

In current firmware.
The success light pulse should be * (1 short light). (Repeat 3 times as usual).
There is no information about this on Led Indication, i read it from the code.

If the ram still okay, then without the pico, the nintendo logo still shows up, then blackscreen. Means the partition still corrupted. But if the ram failed, i think there will be no nintendo logo shows up.

bilalhassan341 · Jun 5, 2023

What is the other point of D0 on switch lite?

abal1000x · Jun 5, 2023

bilalhassan341 said:
What is the other point of D0 on switch lite?

Hacking Hardware Picofly - a HWFLY switch modchip

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Attachments

Well-Known Member

Well-Known Member

Walküre's Hacker

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum