Picofly AIO Thread

zorusgb · May 27, 2023

QuiTim said:
I would go for short wires, single mosfet but soldered on 2 caps and fw2.74 (better glitch times)
If it works, great. If it does not, then you have eliminated all possible alternatives and you either go with i2c (i would) or "try" 2 mosfets.
Have you considered using a bigger mosfet both in capacity and/or size?
Edit: I would also add more solder to those points in pico and you should also solder to both points in the pcb for a better connection (bridge the points)

I intentionally used only one of the available data pads. I thought, if I accidentally rip the pad (a lot of people did) I'll have a backup to fall on without needing to resort to trace repairs. Now that I know the connections are decent I can mask the wires to the board and call it a day. I need to replace the MOSFET anyway (don't ask why

), so might as well try the double setup. Good thing I ordered 5. Unfortunately, I only have the 8342's; at the time I ordered them there wasn't much information on alternatives.

SirHill · May 27, 2023

Hello guys,

I tried to install the Picofly on my V2 switch. I'm quite in trouble now...

I followed the very good V5 guide, so I installed my picozero. And it worked (green led + success screen) !

BUT (there is a but), when I tried to clean up the set up and I accidentally torn the 2 CMD pads... So I tried to repair my mistake : I succeed in soldering the CMD via to the inductor at the left (CMD side of the inductor) to repair the broken path. I installed the CMD wire to the picofly at the same place (see picture).

Now, the fact is that it's not working : I got a purple or pink Led (purple I guess because the problem was on the CMD line). I already removed my USB C connector, so I can't have the last version...

I tried to remove the picofly (to boot on OFW), and nothing's working : black screen

Does anyone has an idea ? My switch is good for the trash...

Thanks for your help

cicci084 · May 27, 2023

SirHill said:
Hello guys,

I tried to install the Picofly on my V2 switch. I'm quite in trouble now...

I followed the very good V5 guide, so I installed my picozero. And it worked (green led + success screen) !

BUT (there is a but), when I tried to clean up the set up and I accidentally torn the 2 CMD pads... So I tried to repair my mistake : I succeed in soldering the CMD via to the inductor at the left (CMD side of the inductor) to repair the broken path. I installed the CMD wire to the picofly at the same place (see picture).

View attachment 374276

Now, the fact is that it's not working : I got a purple or pink Led (purple I guess because the problem was on the CMD line). I already removed my USB C connector, so I can't have the last version...

I tried to remove the picofly (to boot on OFW), and nothing's working : black screen

Does anyone has an idea ? My switch is good for the trash...

Thanks for your help

In first page you can find this schematics.

It's easy to repair

cgtchy0412 · May 28, 2023

I tried to remove the picofly (to boot on OFW), and nothing's working : black screen

Does anyone has an idea ? My switch is good for the trash...

Thanks for your help

You need to fix that cmd point you broke, you will know its fixed when your switch can boot normally.

naldo29 · May 28, 2023

Seems to work but it is SO SO SLOW its kindof speratic, sometimes fast, sometimes slow, but when its slow its like 20s-30s on to glitch successfully, no errors though, although 1 time it said success but it did nothing. Do you think it needs more resistors? Its a Shynix emmumc.

floxcap · May 28, 2023

So.. I recently installed on a lite and encountered the BSOD.
I've been checking everything (install seems okay) and currently looking at doing a mmc dump (via H/W interface).

What I've found so far is:

Glitching works perfectly and is fast (~ 1 second).
Booting without a SD card gets the "no card" screen.
Booting with Hekate as payload.bin just gets a black screen.
vol + - from the "no card" screen just gets a blue screen.

I was starting to give up hope - thinking it may be a hardware problem (SD reader issue or power issue) - when I found this:
Payload to mount SD and/or EMMC via USB

Using the above as the payload.bin on the SD card works perfectly - It runs and I can navigate etc.
Though I haven't yet managed to get it to mount the mmc.

So - this clearly indicates that the BSOD is not an SD card reader issue - at least not for me.

Just have to figure out what I can't get in to Hekate.

abal1000x · May 28, 2023

floxcap said:
So.. I recently installed on a lite and encountered the BSOD.
I've been checking everything (install seems okay) and currently looking at doing a mmc dump (via H/W interface).

What I've found so far is:

Glitching works perfectly and is fast (~ 1 second).

Booting without a SD card gets the "no card" screen.

Booting with Hekate as payload.bin just gets a black screen.

vol + - from the "no card" screen just gets a blue screen.

I was starting to give up hope - thinking it may be a hardware problem (SD reader issue or power issue) - when I found this:
Payload to mount SD and/or EMMC via USB

Using the above as the payload.bin on the SD card works perfectly - It runs and I can navigate etc.
Though I haven't yet managed to get it to mount the mmc.

So - this clearly indicates that the BSOD is not an SD card reader issue - at least not for me.

Just have to figure out what I can't get in to Hekate.

Maybe that's the clue. You can't mount the mmc. Might be the data broken?
Have you tried to restore the backup nand?

floxcap · May 28, 2023

abal1000x said:
Maybe that's the clue. You can't mount the mmc. Might be the data broken?
Have you tried to restore the backup nand?

Don't have a backup - as I never got in to Hekate.
I suspect you're right though - it seems as though the mmc can be access in 1 bit mode - but full init seems to be failing (looking at the ums-loader code).

It can't be completely broken - as I understand it - after the glitch - the core loader (picofly payload) boots from mmc and looks for a payload.bin on the sdcard - that's all working correctly.

abal1000x · May 28, 2023

floxcap said:
Don't have a backup - as I never got in to Hekate.
I suspect you're right though - it seems as though the mmc can be access in 1 bit mode - but full init seems to be failing (looking at the ums-loader code).

It can't be completely broken - as I understand it - after the glitch - the core loader (picofly payload) boots from mmc and looks for a payload.bin on the sdcard - that's all working correctly.

i think picofly only use 1 bit mode (only dat0) to write the loader to the mmc.

Maybe you short circuit the dat0 with dat1 or maybe with other datn:

The green is dat0 the blue is dat1.
The bottom is dat4. You might check the continuity about dat0 point.

Post automatically merged: May 28, 2023

floxcap said:
Don't have a backup - as I never got in to Hekate.
I suspect you're right though - it seems as though the mmc can be access in 1 bit mode - but full init seems to be failing (looking at the ums-loader code).

It can't be completely broken - as I understand it - after the glitch - the core loader (picofly payload) boots from mmc and looks for a payload.bin on the sdcard - that's all working correctly.

The whole dat maybe some short circuit with something else.

floxcap · May 28, 2023

abal1000x said:
i think picofly only use 1 bit mode (only dat0) to write the loader to the mmc.

Maybe you short circuit the dat0 with dat1 or maybe with other datn:
View attachment 374345
The green is dat0 the blue is dat1.
The bottom is dat4. You might check the continuity about dat0 point.

Post automatically merged: May 28, 2023

View attachment 374349
The whole dat maybe some short circuit with something else.

Again - I think you might be right... going to de-solder and check.

Don't suppose you know which pads are dat 1-7?? (Would be great for the hardware reader I'm building).

Thank you for the tips abal1000x!

The interesting part (at least to me) is the ums-loader - perhaps that'll help some of the others that are also getting BSOD.

abal1000x · May 28, 2023

floxcap said:
Again - I think you might be right... going to de-solder and check.

Don't suppose you know which pads are dat 1-7?? (Would be great for the hardware reader I'm building).

Thank you for the tips abal1000x!

The interesting part (at least to me) is the ums-loader - perhaps that'll help some of the others that are also getting BSOD.

In the picture i already add each pad number.

Use the datasheet

And track the trace using https://balika011.hu/switch/lite/

cgtchy0412 · May 28, 2023

@floxcap
If you comfortable soldering 1 hair thick point you can try this dat0 point, its easier to not short at least for me.
I already move to this point as dat0 solder point onwards on Lite as it is harder to messed up..

FreeLander · May 28, 2023

floxcap said:
So.. I recently installed on a lite and encountered the BSOD.
I've been checking everything (install seems okay) and currently looking at doing a mmc dump (via H/W interface).

What I've found so far is:

Glitching works perfectly and is fast (~ 1 second).

Booting without a SD card gets the "no card" screen.

Booting with Hekate as payload.bin just gets a black screen.

vol + - from the "no card" screen just gets a blue screen.

I was starting to give up hope - thinking it may be a hardware problem (SD reader issue or power issue) - when I found this:
Payload to mount SD and/or EMMC via USB

Using the above as the payload.bin on the SD card works perfectly - It runs and I can navigate etc.
Though I haven't yet managed to get it to mount the mmc.

So - this clearly indicates that the BSOD is not an SD card reader issue - at least not for me.

Just have to figure out what I can't get in to Hekate.

Hello. I encountered this three times. Exactly the same. However, now it’s only getting blue screen even after removing the modchip and wire. Has it stopped showing the no sd card and turned to blue screen only in your case?

floxcap · May 28, 2023

FreeLander said:
Hello. I encountered this three times. Exactly the same. However, now it’s only getting blue screen even after removing the modchip and wire. Has it stopped showing the no sd card and turned to blue screen only in your case?

As I understand it (someone please correct me if I'm wrong) - The picofly writes to emmc (Normal BCT & SafeMode BCT & an unused section) - so it can't just be removed.... because the BCT (Boot Configuration Table) has been modified to point to the custom payload (not referring to payload.bin).

Mine still gets the no sd card if there is no sd card.... and I've managed to confirm that the glitch and boot sequence is working by using "ums-loader" as my payload.bin.

Just can't get in to Hekate.

rehius · May 28, 2023

FreeLander said:
Hello. I encountered this three times. Exactly the same. However, now it’s only getting blue screen even after removing the modchip and wire. Has it stopped showing the no sd card and turned to blue screen only in your case?

It could be you have cheap soldering iron that has high voltage on its tip. I know several cases where the very soldering killed devices

abal1000x · May 28, 2023

rehius said:
It could be you have cheap soldering iron that has high voltage on its tip. I know several cases where the very soldering killed devices

This is very possible scenario.
Just remembered decade ago i used cheap solder and its shock me everytime my feet touch the gnd.

Hellflame · May 28, 2023

Sorry it's bit out of topic in this pico thread, can i use the same method of using mosfets this hwfly v2 chip? Anyone has the schematic showing the cpu point? needed it badly as i do not have the flex cable. Im using it on erista switch

FreeLander · May 28, 2023

rehius said:
It could be you have cheap soldering iron that has high voltage on its tip. I know several cases where the very soldering killed devices

I like this. True, my soldering iron is Quico, pretty cheap off Aliexpress, but the iron tip is a genuine T12. I work on 330c.

I'm going to buy a Hakko. This work is delicate and requires a genuine setup.

Thank you Rehius <3

Post automatically merged: May 28, 2023

floxcap said:
As I understand it (someone please correct me if I'm wrong) - The picofly writes to emmc (Normal BCT & SafeMode BCT & an unused section) - so it can't just be removed.... because the BCT (Boot Configuration Table) has been modified to point to the custom payload (not referring to payload.bin).

Mine still gets the no sd card if there is no sd card.... and I've managed to confirm that the glitch and boot sequence is working by using "ums-loader" as my payload.bin.

Just can't get in to Hekate.

I see. Alright, I'm going to resolder everything VERY carefully and insert an SD card with the payload you suggested. Hoping for the best. Thank you all as always.

LogicalMadness · May 28, 2023

Adran_Marit said:
The number of consoles I've killed over the years while chipping is too damn high, when I first started out I killed a ps1. Since then I've killed 2 ps2 slims, succeeded several rgh3 slims, killed my lite but did an oled successfully.

I hope you still have those dead soldiers and keep trying to revive them over the years

Post automatically merged: May 28, 2023

floxcap said:
As I understand it (someone please correct me if I'm wrong) - The picofly writes to emmc (Normal BCT & SafeMode BCT & an unused section) - so it can't just be removed.... because the BCT (Boot Configuration Table) has been modified to point to the custom payload (not referring to payload.bin).

Mine still gets the no sd card if there is no sd card.... and I've managed to confirm that the glitch and boot sequence is working by using "ums-loader" as my payload.bin.

Just can't get in to Hekate.

Possible scenario?:
'Bad' SD card(cheap\fake\old\dead) or reader (dirty\broken), corrupts the 1st glitch, creates BSOD.

Have you tried a different card? What model card are you using? Inspect the card reader?

MegaDeKay · May 28, 2023

FreeLander said:
I like this. True, my soldering iron is Quico, pretty cheap off Aliexpress, but the iron tip is a genuine T12. I work on 330c.

I'm going to buy a Hakko. This work is delicate and requires a genuine setup.

Thank you Rehius <3

Post automatically merged: May 28, 2023

I see. Alright, I'm going to resolder everything VERY carefully and insert an SD card with the payload you suggested. Hoping for the best. Thank you all as always.

A good tip won't help you if the iron itself is putting a high voltage out of the main body of the iron. The tip will conduct that voltage to whatever you are working on. We had to throw away a lot of our old irons at work some time ago because they were not ESD safe.

I suppose the other possibility is that you've made the same mistake on all the units with the problem? Like getting mixed up and soldering to DAT1 instead of DAT0? Triple check all the connections you've made to the pictures in the guide to make sure they are all to the correct points.

Picofly AIO Thread

Well-Known Member

New Member

Well-Known Member

Attachments

Well-Known Member

Well-Known Member

Attachments

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

Well-Known Member

Member

Attachments

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum