if you are having problems installing something this simple chances are you will have problems installing a demon. if you find a demon slim then a bit of a suggestion, I like to call them "solderfalls" because on a quick solder board your solder should look like a waterfall flowing over the edge of each point, anyways your "solderfalls" need to be almost flawless and the demon has to be lined up with precision. Demons are only recommend for pro installers even though there are lots of people who manage to get them working like me (and some other people whose names I won't mention) without even being close to a pro installer. best bet is to try and see if you can get what you've got working before moving on to the demon. save the demon for when you have actually finished a rgh xbox and you have the experience to do the demon.
TRINITY PRE-CR4, How's my soldering?+Tuning advice
- Thread starter Orangeprofessor
- Start date
I've done rgh'd an xbox before. I got it to boot xell and everything but it died shortly after
The support thread is on here as well.ok did you ever recheck those points? Have you even tried your jrp again today to see if your flash config: was still acting up?
You can also do a wire install with the demon just to read and write to the nand and then remove it afterward.
You can also do a wire install with the demon just to read and write to the nand and then remove it afterward.
Last edited:
If you spi was bad you would have had to do something to make it that way, but it was working in the first place so it should be still good unless you did something like short out the nand points. Im betting there is something you are missing that is causing the bad flash config: have you tried a continuity test from the quick solder points to the port on your JRP where the wires plug in to it? I would test from the actual pins that solder the port onto the JRP, to the qsb points that way you know it is getting a good connection. If one of them is getting a sketchy connection then it will cause the bad flash config
Last edited:
The slots on the nand headers seem to thick for my test leads.
EDIT: all of the nand asb points to the jr prog have continuity
Last edited:
like shorting any of the nand points to ground with power to the console or shorting them to each other. but almost all of your nand points tested good, just need to recheck a couple of them and see what they read at. j2c1.1 and j2c1.3 should be roughly a half a volt but it took me a minute when testing mine because the readings were up and down all over the place and I had to get my probes just right. you had J2C1.3 and J2C1.4 backwards when typing it in.
J2C1.1 = 23mV
J2C1.2 = 3.2V
J2C1.3 = 1.8v
J2C1.4 = 41 Ohms
J2C3.5 = 3.3v
J2C3.6 = nothing (qsb connection is bad. resoldering now)
Last edited:
They are all still pretty close I cant be sure about 1.1 and 1.3 but I think you have a short or a bridge or loose connection somewhere. Try looking over the console with a magnifying glass and clean it up really good with some qtips and isopropyl alcohol and also look for any remnants of tiny capacitors or resistors that have been snagged and broken off of the board. you can tell if any pads ever had a component soldered to it before and if you find any missing then I can get you the specs on the right component. also check around the hana chip near STBY_CLK r3b15 resistor should read 33ohms Ive read it can cause bad flash problems.
I got:Flash Config: 0xFFFFFFFFIoTimedOut
IoTimedOut:No more bytes!
FFFFFFFF
Reading Nand to C:\Users\XCGPUC-A02\Desktop\J-Runner v3 (5) Core Pack\output\nanddump1.bin
Cancelled
Are we getting somewhere?
EDIT: Back to flash config: 0x00000000
IoTimedOut:No more bytes!
FFFFFFFF
Reading Nand to C:\Users\XCGPUC-A02\Desktop\J-Runner v3 (5) Core Pack\output\nanddump1.bin
Cancelled
Are we getting somewhere?
EDIT: Back to flash config: 0x00000000
Last edited:
yep I would say so. It is definitely a loose connection or a bridge and make sure you are running as an administrator.
Check continuity between all the points on the j2c1 header to make sure they are not bridging and also test each point with the other side of the board to make sure they are making a good connection.
Check continuity between all the points on the j2c1 header to make sure they are not bridging and also test each point with the other side of the board to make sure they are making a good connection.
After I reflowed that point I got 0xFFFFFFFFIoTimedOut. then it went back to 0x00000000
this is why i cut the plugs off and make nice solid legs wrapped in heatshrink and soldered on to the nand wires and I read nands with a direct connection to the board with the wires. those qsb's can be really tricky, even if it looks perfect it can always have a problem, or some little tiny piece of wire stuck under the qsb that causes all sorts of errors.
if the continuity tests all come back good, grab the 3 plugs and push them all down a little and try to read the nand while holding them there, then try again with the plug on the jrp side