Or it could be burnt cmd resistor. Try to boot into ofw and see if it does, otherwise what @QuiTim is the problem
Well it makes more sense if the resistor is burnt, usually we get "slow emmc" when resistance is low, that's why we started using 100ohm instead of 47ohm which was used originally and if yours is damaged you might be getting 0ohms.
Both rp2040 and rp2040-tiny work great (tiny fits better and no need to remove anything from the board).
Check that one first, but it could be something else as psycho-neon suggested.
Get 47 ohm readings on the other resistors. Only dat0(C point) resitor which is no reading. Does not look burnt so my guess it was like this from factory.
Ordering a few 0402 100 ohms resistor.
Can I just disconnect rp2040 chip to boot to ofw or do I need to desolder anything?
You can press VOL+ and - at the same time at the NO SDCARD screen.
I'm gonna try to install the RP2040-Tiny instead of the Aliexpress one. Does the RP2040 Tiny not need resistors installed? No 47 Ohm resistors?
well, as you can see in the picture you posted, the dat0 clk and cmd points do have 47ohm resistors. It's a good idea to either replace them with 100ohm ones for dat0 and cmd, OR add additional 47 ohm ones on these two points.
Hi guys! I've already opened a post about it but then i find this post so i ask here:
I managed to install the chip on the console, immediately afterward I backed up the raw eMMC, boot0, boot1 and the keys. I could successfully boot into both ofw and cfw. The next day, however, I noticed that sometimes it wouldn't boot into Hekate but directly into ofw, and the error was D0. So, I disassembled and correctly positioned the D0 (I have the adapter with two pads that hold it in place) and made sure it was secure. I always checked all the values with the multimeter, and they were in the correct range of 500-800. Hekate now starts correctly, but sometimes the cloned chip gives an error * = * or **= and boots into ofw then i've the logo and then black screen. I have to hold it down for 20 seconds, and then Hekate starts normally again. The problem is that I can no longer enter OFW or syscfw; every time it shows the startup screen and immediately goes black. So, I always have to hold it down for 20 seconds and go back to Hekate. I doubted that I damaged the eMMC, but removing the flat cables from the chip and starting ofw starts normally. Could the problem be the chip or something else? If it's the chip, do you know where I can buy a new one? Could I solve it by positioning the D0 adapter better? I don't mind too much being able to access OFW because the idea is to use it for Moonlight on Android, but I still want to resolve it. Thanks in advance to everyone for the help.
I managed to install the chip on the console, immediately afterward I backed up the raw eMMC, boot0, boot1 and the keys. I could successfully boot into both ofw and cfw. The next day, however, I noticed that sometimes it wouldn't boot into Hekate but directly into ofw, and the error was D0. So, I disassembled and correctly positioned the D0 (I have the adapter with two pads that hold it in place) and made sure it was secure. I always checked all the values with the multimeter, and they were in the correct range of 500-800. Hekate now starts correctly, but sometimes the cloned chip gives an error * = * or **= and boots into ofw then i've the logo and then black screen. I have to hold it down for 20 seconds, and then Hekate starts normally again. The problem is that I can no longer enter OFW or syscfw; every time it shows the startup screen and immediately goes black. So, I always have to hold it down for 20 seconds and go back to Hekate. I doubted that I damaged the eMMC, but removing the flat cables from the chip and starting ofw starts normally. Could the problem be the chip or something else? If it's the chip, do you know where I can buy a new one? Could I solve it by positioning the D0 adapter better? I don't mind too much being able to access OFW because the idea is to use it for Moonlight on Android, but I still want to resolve it. Thanks in advance to everyone for the help.
Replaced dat0 resistor to 133 ohm.
Tested to boot into OFW but get purple screen, I guess I should replace 47 ohm CMD resistor aswell then.
Hard to replace resistors on this chip they are so tiny and sit so close to each other
As I expected. The value is 4.7k ohm just for your info, not 47ohm resistor. Do not be confused about the resistor at the chip.Replaced dat0 resistor to 133 ohm.
Tested to boot into OFW but get purple screen, I guess I should replace 47 ohm CMD resistor aswell then.
Hard to replace resistors on this chip they are so tiny and sit so close to each other
What you have to replace is the resistor on the switch board itself. Point A resistor.
Because it is busted or you burnt it when you are connecting the point A and thus giving you purple screen error. That's the real reason for the purple screen and not the chip. If you have a hot air gun, you can try and reflow it, most of the time the solder connecting the resistor gets disconnected when you solder the wire.Ah ok, it's a 0201 size?
It gets tinier and tinier
May I ask the reason why it needs to be replaced?
What is the supposed stock value? I meassured it inline and get 1.1M Ohm
If you will not fix it, then your switch wont work unfortunately even without the mod chip.
You can use 0402 or 0603 and wire it manually if you have difficulty with 0201.
Thx,
tried reflowing the resistor with hot air but still 1.1M ohm.
WIll have to find some 0201 4.7k ohm resistors somewhere.
I guess 0201 is not so bad but this one sits in an awkward spot.
EDIT: removed resistor from board and meassured I guess it's burnt. No reading from it.
Last edited by etnicor,
The cause is not known, but I assure you that (it has happened to me 2 times in my career) it is not due to damage to the resistor, at least in my case. In an emergency I even used a laboratory resistor, just remove the old resistor.Ah ok, it's a 0201 size?
It gets tinier and tinier
May I ask the reason why it needs to be replaced?
What is the supposed stock value? I meassured it inline and get 1.1M Ohm
MM I actually soldered one side of the resistor to a lab board to be able to measure it better, if I measured it on the underside I got a 4.8k reading sometimes but not when putting probes on the sides or top. So my guess is that I perhaps burnt the metal.
Ordered a smd sample book with 0201 resistors from amazon, will get it on Wednesday. Just hoping it has 4,7k resistors, didn't say which values it contained.
EDIT:
Had an old laptop motherboard which I found a 0201 4.7k resistor on wIll trie to solder it tomorrow.
However I purposely tried to burn multiple 0201 resistors on laptop MB, i was unsuccessful in all attempts, so wonder how I managed on the switch MB(doesn't seem that I am alone though). Crappy resistors on switch MB?
Also as a sidenote if you buy modchip kit from alie check your resistors, I had bought a v1/v2 aswell which is unused so I checked resistors and this one had a broken 47 ohm resistor. Would suggest go with rp2040-tiny as recommended...
Last edited by etnicor,
I've placed an order with JLCPCB with your files, will update when I've gotten a chance to install one! The only change I made to the settings was board thickness 1mm (same as rp2040-tiny), default is 1.6mm which seemed unnecessary. Just a note, the pads are still present as components in the gerber file and the jlcpcb ordering system complains about it not existing in the bom file. not a big issue though, you can just ignore it and hit continue
Great! I've ordered them as well. 100pcs (panelized 5x4) since I have plenty of rp2040 chip with me.
Expecting them to come after 2days. Thickness of the board I have set was 0.6mm (same as the prototype)
This was the initial version of the board, with my V2 switch. All works good and clean installs. both oled and v2 works perfectly.
Similar threads
-
realtimesave
-
Xdqwerty
what are you looking at? -
BigOnYa
-
K3Nv2
-
Psionic Roshambo
-
-
-
-
-
-
@
BigOnYa:
I was gonna sell one of RGH3 x360 today to neighbors kid, and refused to buy it cause I RGH modded it, they wanted a stock model, like wtf, better take your ass to gamestop. Dumbass.
-
-
@
SylverReZ:
@BigOnYa, The worst part when buying 360's at GameStop, is that they bolt the heatsinks down. -
@
realtimesave:
@BigOnYa yeah my sister wants a ps3 but I don't think she wants a modded one so I showed her where I got mine for 60 bucks.. they are still out there
-
-
-
-
@
realtimesave:
I bought one of the jaspers used at gamestop. it was still brand new, just was in a refurb box
-
-
-
-
-
@
BigOnYa:
I would Not trust anything from gamestop, ive read people buying stuff new under warranty, then something happens and they return to get fixed under they warranty to only get a used 2nd hand unit back, that bs
-
-
@
SylverReZ:
@realtimesave, I haven't modded a Xbox 360 before, looks easy to mod, but difficult to take apart lol. I've done OG Xboxes before.
-
-
@
realtimesave:
they aren't that hard to take apart. I can pop them apart with a jeweler's screwdriver any more
-
-
-
@
realtimesave:
@Xdqwerty that's ok tho if you ever needed another model they are only like 60-80 dollars on offerup. pretty cheap+1
@
realtimesave:
@Xdqwerty that's ok tho if you ever needed another model they are only like 60-80 dollars on...
+1