Help with setting up Demon

[Martin C]

Will most likely be your soldering, why does everyone always get touchy when someone says your soldering is bad lol.

I'd remove the Demon, clean up the motherboard, clean up the demon and then start again.

Because most people think they can solder really well until they're given something that requires a higher level of skill. Watch any of the talent shows on TV (x-Factor etc) and people who think they can sing go ballistic when they're told they can't. Same thing.

 

[rpmccormick]

Yes, but my soldering is not bad. I've soldered 400-pin CPU's. I've even soldered ball-joints with a heat-gun. My job for 10 years was designing circuit boards, and debugging prototypes with an O-scope. I'm not trying to get touchy or brag or anything like that, I just want the people helping me here to know that I do know what I am doing.

I have re-heated up every solder joint, re-checked neighbor shorts, re-checked each of the 14 test-points for continuity with a pin on the stock NAND on the opposite side of the xbox, and then checked every testpoint for a short to GND or Power (Red wire). I have also just checked that each testpoint hits the DemoN NAND, and they all do except for CE (which makes since each NAND would have a separate Chip-Enable) Everything is wired fine.

I guess I can get an O-scope later and make sure that each pin on the stock NAND (except for CE) is toggling with good rise/fall time while reading the DemoN NAND back. Anyone have any other debugging advise?

 

[Martin C]

Talk me through exactly how you're checking the QSB points are ok.

You're testing continuity from the test points adjacent to the QSBs with the console's NAND, yes? Something's amiss here - just need to work out what. A pic of your RB soldering is still needed.

 

[rpmccormick]

Yes, I am testing from each TP (near each QSB-pad) to the console NAND on the opposite side of the board. All TPs (including RB) are connected, and none of them are shorting their neighbors, GND, or power.

Pics attached.

 

[rdubbs007]

Yes, but my soldering is not bad.

the soldering on this job is atrocious

 

[Martin C]

the soldering on this job is atrocious

There's no telling some people.

I digress...

Desolder that green wire from the board. You're hitting two via pads it's that bad. Trim the excess wire and make sure you're only hitting the via connected to R1P7.

 

[rpmccormick]

Is this a troll or something... the soldering is GREAT! The pictures are a bit blurry, and maybe you are thinking that the green-wire looks like it has a giant solder blob, but in actuality that blob makes a triangle connecting the green-wire to both the 0402 resister as well as the via.

The soldering is about the best possible that anyone could do using the stock-tip on a cheap Weller WLC100. I like my solder to bubble on pads, fully enclose the wire, and connect to multiple small points if there is not a good large point. You can tug on my wires and be assured they are a solid connection. There are no shorts. Please stop telling me how bad it is when... you are wrong... it is good... really... I do know what I am talking about.

---------- Post added at 11:31 ---------- Previous post was at 11:29 ----------

I'm not hitting 2 via pads. I'm hitting the one via pad that connects to that resister, as well as the side of the resistor itself. There are no shorts, I promise you. I will un/re solder it anyway though just to make sure.

 

[Martin C]

ok it's not a bridge, it's the reflection of the flux itself.

You're getting a good ID (73AD) so it's possible it's the USB cable itself.

 

[rpmccormick]

Now it's just on the via and clean. You guys like?

Board still has same errors trying to read XBox NAND.

 

[rpmccormick]

How do I know I'm getting a good ID (73AD). What is that an ID for, the NAND? And you are saying it reads that from the NAND chip, so at least most of the important pins are good?

I don't think it is the cable since I can read and write the DemoN NAND fine.

 

[rpmccormick]

I tried a different USB cable, same issue.

 

[sick360mods]

Look at your soldering and this one. Do you see how I don't have residue flux everywhere. That's what it should look like

Sent from my PC36100 using Tapatalk 2

 

[Martin C]

hold on - when you are trying to dump the NAND, you're making sure the LED on the USB port is OFF, right?

 

[rpmccormick]

So get this... I tried it again, and it read all 01's for the first NAND read. I let it do the second read and prob a single test-point WE with a multimeter set to DCV while it is reading. I see the line toggling, and when it is done it says the files don't match, so I look at the second file and the end of it has data (the beginning is all 01's).

So I tried it again immediately and it works perfect now (in both J-Runner and Demon). Very, very strange.


So now that I have my NAND, I still need to know how to boot XELL so I can get my CPU key. When I click Create ECC I get this:

* unpacking flash image, ....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
 * we found the following parts: 
SMC: 1.10
CB_A: 4569
CB_B: 4569
CD (image): 4569
CD (decrypted): 9452
 * checking required versions...
Failed to create ecc image

---------- Post added at 13:31 ---------- Previous post was at 13:28 ----------

More than anything I just want the lost DVD key.... Is there a way to just get J-Runner to populate the DVD-Key box in the KV Info tab (or do I need the CPU key first)?

 

[LoneWolf913]

So get this... I tried it again, and it read all 01's for the first NAND read. I let it do the second read and prob a single test-point WE with a multimeter set to DCV while it is reading. I see the line toggling, and when it is done it says the files don't match, so I look at the second file and the end of it has data (the beginning is all 01's).

So I tried it again immediately and it works perfect now (in both J-Runner and Demon). Very, very strange.


So now that I have my NAND, I still need to know how to boot XELL so I can get my CPU key. When I click Create ECC I get this:

* unpacking flash image, ....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
 * we found the following parts: 
SMC: 1.10
CB_A: 4569
CB_B: 4569
CD (image): 4569
CD (decrypted): 9452
 * checking required versions...
Failed to create ecc image

---------- Post added at 13:31 ---------- Previous post was at 13:28 ----------

More than anything I just want the lost DVD key.... Is there a way to just get J-Runner to populate the DVD-Key box in the KV Info tab (or do I need the CPU key first)?

You do know 4569 is a dashboard of 15574 which is unglitchable without a CPU key or prior split-CB nand dump, right? So no, you're SOL until the method to glitch 15574 is released.

 

[Martin C]

FFS - you telling me you didn't even read the stickys and guides before you started? It's there in my RGH roadmap for noobies.

EDIT: and ALL this for a DVD key.

So you said 'you gotta learn sometime'. You're right, you do. You've just learned the hard way, which is what happens when you don't read the stickys before you start.

 

[XL3THAL VIP3RX]

So get this... I tried it again, and it read all 01's for the first NAND read. I let it do the second read and prob a single test-point WE with a multimeter set to DCV while it is reading. I see the line toggling, and when it is done it says the files don't match, so I look at the second file and the end of it has data (the beginning is all 01's).

So I tried it again immediately and it works perfect now (in both J-Runner and Demon). Very, very strange.


So now that I have my NAND, I still need to know how to boot XELL so I can get my CPU key. When I click Create ECC I get this:

* unpacking flash image, ....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
 * we found the following parts: 
SMC: 1.10
CB_A: 4569
CB_B: 4569
CD (image): 4569
CD (decrypted): 9452
 * checking required versions...
Failed to create ecc image

sounds like the read wasnt so perfect,if i was you before you balls something up,is to read with the nand-x so you have the nand saved.
cos as you stated,ya dnt know how the RGH process works,so the wise thing to do would have been to install the coolrunner and get it glitchin before you attempted the demon install

the saying don't RUN before ya can WALK springs to mind

are you even on the correct dash as it sounds like you havnt read the TUTs

 

[Ticallion]

I guess experts are beyond tutorials and noob guides huh?

And why would you go straight to DemoN for a dvd key? Coolrunner would have done just nicely ..?

 

[XL3THAL VIP3RX]

FFS - you telling me you didn't even read the stickys and guides before you started? It's there in my RGH roadmap for noobies.

EDIT: and ALL this for a DVD key.

So you said 'you gotta learn sometime'. You're right, you do. You've just learned the hard way, which is what happens when you don't read the stickys before you start.

got there before me lol
internets toss in mablethorpe lol in a caravan:rolleyes2:

 

[Martin C]

Thread closed to avoid wasting any further bandwidth.