Thanks both for the feedback, revising the survey now :3
I also figured the survey was a good source to condense down the information to find out the most common factors
edit: Okay, so reviewing the information, so far
5 lites, 4 blue screen, 1 black (black screen since resolved)
3 oled, 2 black screen, 1 purple screen (hwfly chip)
2 v2 redbox, 2 black screen
Last edited by Adran_Marit,
Because I never really figured out what the issue was. I went from double mosfet to flex to single mosfet. Even the single mosfet was giving problems. It was covered of course. But it’s been acting fine so I gave it back to the customer. I’m still unsure. I just did a v2 with a single mosfet, took an hour, and it’s running perfect so idk.well why dont u let us know what the issue was so other people who have a same issue they maybe find the solution
Before adding resistors, it should still boot into OFW or am I wrong?
In Emummc instead, once the console goes into standby, it is not possible to wake it up.
My theory is that shorting the 15 CPU wire corrupted or damaged the mmc.
Now will I try resistors first or mmc unbrick first?
Yes, to narrow it down into any instalation issue then you must clean all and try to restore ofw full funcionality first. After that you can redo carefully for this time.
Sometime there is some unit thats need more attention and special treatment.
I believe nintendo itself have some kind of defect threshold and they incorporated it on the hos system, because manufacturing can have variations.
And if you mod it maybe that variations creates some special treatment for the mod to be stable.
Thats just a theory though.
Hi guys, quick question about an OLED RP2040-zero install. Everything seems to be fine, diode mode test gives good values, but on boot I get =* (no dat0) and it goes directly to OFW. dat0 shows continuity to the RP2040 with good values though...
The supplier I used sent a janky OATO flex for the emmc and when installed, it is offset to the right and the contact point seems to have a really bad shape but does seem to contact the correct pin. Could it be a bad dat0 contact, or is there a possibility for another issue? I have the 4 anchor point dat0 on it's way but if there's anything else to check before swapping the adaptors I'm open for ideas.
The supplier I used sent a janky OATO flex for the emmc and when installed, it is offset to the right and the contact point seems to have a really bad shape but does seem to contact the correct pin. Could it be a bad dat0 contact, or is there a possibility for another issue? I have the 4 anchor point dat0 on it's way but if there's anything else to check before swapping the adaptors I'm open for ideas.
Attachments
Last edited by Uberfish,
=* means the pico doesn't read the voltage in the range 1.6-2.0v
So i am sure there is disconnection somewhere on the dat0 line.
Maybe the 47ohms resistor burned?
Voltage from emmc? I checked the resistors, all read 48 still with no shorts. dat0 line shows a strong connection. No wiggle at all on the adaptor. Also, it stopped giving =* when I just checked and now gives =** (emmc initi failure).
Attachments
If you know embedded, this code simply check the voltage. The =* error is simply the rp2040 read the gpio pin on dat0 voltage and is not around 1.8 +- 0.2V.
=** is different error. The d0 voltage check are passed means it connected. This could be lot of scenario. I am not focused now, afraid giving wrong analyze.
If you said is true, when you check the error change from =* to =** then the connection on your d0 line is unstablle. Please make sure its okay first (before connecting power or turn it on). Because one mistake in there could corrupt your emmc, which lead to blue screen or black screen which will be very difficult to analyze and solved.
Just cheap analyze (i am not thourough in here), initialization error means that that rp2040 couldn't read emmc initialization activity in CMD line which supposed to be happening after a Reset. It could be the CMD line is unstable, or CLK line is unstable.
Hm, CMD and CLK are the two I have the most confidence in. Honestly, I think the 'OATO' adaptor is just bad and others have recommended avoiding it, the claw contact looks bad, and there's a high chance it's just not making good enough contact, which could result in the voltage error. So far, the board still boots into OFW so the emmc is still good.
I'll wait for the good DAT0 adaptor to arrive in a day or so and give that one a try and see how it turns out first. I don't want to have to remove the mask I put on the CLK point.
It could be a short on dat0, in my experience if the adapter makes a short under emmc it still gives the correct diode value. I would cut the left side of the dat0 adapter (like abal1000x did earlier) or just wait for the good one.
Just check the photo and you will see why this is possible
Attachments
Yeah the old one isn't viable now, one of the ground 'legs' tore when I tried to desolder it to make the change
The newer 4 anchor point one is hitting my mailbox any day now so I'll just use that. Thanks!
For the records, my black screen first is due rst to 3v3 and dat4 to gnd shorts, after clean black screen with no logo but hekate boot showing 0% battery and I can backup emmc fine so the next is check the fuel gauge and pmics, for missing 1.35v or fuel gauge replace or reflow
Last edited by seraser2,
installed a picofly in a oled switch but it refuses to boot into hekate/no sd screen.
flashes blue and then 3x3 times yellow and stops blinking = black screen. when clk is removed the switch bootes into ofw. red that blinking yellow means dat0 issue. but i have .7v on dat 0 in diode mode. its not the first time i installed modchips. had many sxcore/hwfly installations on oled switch. any ideas?
flashes blue and then 3x3 times yellow and stops blinking = black screen. when clk is removed the switch bootes into ofw. red that blinking yellow means dat0 issue. but i have .7v on dat 0 in diode mode. its not the first time i installed modchips. had many sxcore/hwfly installations on oled switch. any ideas?
=*** eMMC init failure
Need to check CMD or CLK.
The Dat0 also possible cause if got short circuit with Dat1, but since you said experience on SXCore then i assume the Dat0 is correct.
The pico will read emmc activity after reset via CMD line, there should be Initialization, then CMD1 request then CMD1 response. In your case the initialization is not even detected.
Similar threads
