The image is the same as used in ali.
Furthermore, the store has not been open long.
It is very likely that you will receive 3 anchor type trash instead of the 4 anchor type in the image.
No. If you can glitch use emmchacgen to rebuild. If you can get to hekate. you should still be able to dump keys.
Emmchacgen to rebuild the switch firmware
Yes all my installs have continuity from drain to source, I assume there is either leakage through the cpu or through the mosfet, either way every install is working fine
Last edited by CodyRoseman,
- Joined
- Jul 12, 2010
- Messages
- 162
- Trophies
- 1
- Age
- 36
- Location
- Bananna Land.
- Website
- www.nerdfy.com.br
- XP
- 835
- Country
I realized I bought 30 pcs of these damn crappy dat0 cables. Currently I have the Black screen and error *=* No eMMC block 0 read (eMMC init failure?). My diode reading for dat0 is 687, hynx chip.
Is it possible that the short caused by these cables could kill the EMMC? Is there anything I can do to test my Switch and verify the extent of the damage?
Last edited by Mr Skinner,
Hmmmm your not alone with the exact same problem as me and like 4-5 switch lites. Something is being reproduced here but I have no idea what it could be! Weird thing is, I've not seen this problem with HWFLY lite installs but lots of pico installs with this problem. What is going on? Is the Pico drawing to much power from the lite that is more power starved than the other switch versions or something!?I have same problem with my lite after install i get "no sd card" then when i insert sd card then black screen then when i boot to ofw using +&- button it's blue screen
That does sound like the most logical variable here. Hwfly lite 3.3v is sourced from the cap that is directly above the sd card reader. All other data lines are the same as Pico install. So.....that improper line we use could be the cause of bsod etc and seems like the odd variable out. Apart from the circuitry of the hwfly modchip but I doubt that's super cutting edge ahead of us.
Edit - That point gives 0.8v voltage drop. What does the pico 3.3v value give?
Edit - Nonetheless it's from a different part of the board. Different voltage rail. I wonder if this is it. But first thing is to restore out the bsod. Unless, trying this line with the pico would fix it. Isn't this all just so fun!
Reference:
Last edited by Takezo-San,
From the datasheet
The dat0 neighbour is same datn, not the vss or vdd which is dangerous to short circuited.
Logically short circuited the data line is not that dangerous (wont burn the ic), but it might corrupt the data when there is write to the nand via those data lines. And corrupt the loaded data (in ram) when the cpu read from the nand. In which i suspect the cause of purple or blue screen.
The diode mode should be 600 - 607. I don't know whether diode mode is different between multimeter. But i think it should be the same. Shift it to right is okay, pin A2 is NC (Not connected). Thats why i shift it to right rather go to left (A4) which is the Dat1.
If i am gonna revise the design of the flex, i will put 3 point (A2, A3, A4), in there with 0.5 mm apart (according to the datasheet). So we could detect whether its short circuited with the neighbour point or not, before connecting the power.
Post automatically merged:
Both point comes in the same line.
You could track the traces yourself in here https://balika011.hu/switch/lite/
I finally got the rp2040-tiny.
It has a 0201 smd resistor of 47 ohms,
The revision is 1.1.
The inference that they got the resistor values wrong was correct lol.
It has a 0201 smd resistor of 47 ohms,
The revision is 1.1.
The inference that they got the resistor values wrong was correct lol.
All I knows is, thats the only point difference in the hwfly install and the pico install.
hwfly is totally different, they put lot of component on their hardware. Yes its add the cost, but its also more stable and secure. You might add a diode zener in the 3.3v or LDO in there, or capacitor to smooth it up, or something similar, and it will increase the cost.All I knows is, thats the only point difference in the hwfly install and the pico install.
I am actually want to hear from people in here whose bought the rp2040 version of the hwfly, whether they face similar problem or not. I believe its only hardware issue. Maybe adding some cap, ldo or zener might solve the problem.
Last edited by abal1000x,
That seems a good idea on paper, but unless there is even tension keeping the flex against the solder, and some independent give on each point to compensate for variances, as soon as you have more than 1 point, the edge connection will become unreliable (seesaw).
This is what in my mind, which i thought its more secured.
Also the left and right part might be extended like usual to secured it even more.
Hello here I am with a Oled that has the same Problem after a hwfly install (no I did not install the hwfly) someone else did , so this has nothing to do with the picofly this is a issue that occurs during installation
Hi, can you share a link to this particular datasheet?
Hey guys, does anybody has desoldered EMMC BGA153 and crappy OLED DAT0 cable?
Can we just flip over this EMMC chip and put this cable above to see if DAT0 on cable shorts neighbour DAT1? Is that make sense?
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
@
Xdqwerty:
@Purple_Heart, then I will be actually older than him for a bit (ik thats not how ages work btw) -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
