MrKronic

Hmm, I have missed that :| Should've been a bit thorough. Either way, enabling DMZ still had no effect. I had a suspicion that this might have been an ISP level issue because the connection I am using is basically a shared connection, with a singular external IP maintained by the ISP which is heavily bottlenecked (Only ISP in the area so no other option). That is the only thing I could think of. However my System Link option still appears greyed out in all multiplayer games, which you mentioned might again be another ISP level issue. If that is the case, how was it able to connect and play in Live before it was modded?

So what could be done to solve this? Or is it really an ISP level problem like I mentioned earlier?

Hello again. I've been trying to set up SystemLink on my RGHed Corona in Aurora, but I've been having issues with the data and broadcast ports being unreachable. HEre's the info: Problem: I can't get a "pass" on Data port and Broadcast Port ------------------------------------------------------------------------------------------------------------- Description: I would like to play online with my RGH Xbox via System Link, but can't get a "pass" on the port tests. ------------------------------------------------------------------------------------------------------------- Setup: - XBOX 360, Corona, Glitch2, Aurora 0.5b, Dashlaunch 3.16, Kernel 2.0.17489.0 - Router: Netgear WNR2000v5 ------------------------------------------------------------------------------------------------------------- Network Settings in NXE: - Manual Settings - Static IP: 192.168.1.188 (DHCP reserved IP for XBOX on MAC) - Subnet Mask: 255.255.255.0 - Default Gateway: 192.168.1.1 ------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------------------------- LiNK Settings (FSDPlugin): Enable LiNK ✔ Enable UPnP ✔ Data Port: 3072 Broadcast Port: 3071 Status: FSD Plugin is Loaded || ConnectX Plugin is not Loaded... ------------------------------------------------------------------------------------------------------------- Router Settings: UPnP enabled ✔ List of UPnP enabled Ports: Protocol Port Host IP-Address to Port TCP 3071 RGHXBOX 192.168.1.188 3071 TCP 3072 RGHXBOX 192.168.1.188 3072 UDP 3071 RGHXBOX 192.168.1.188 3071 UDP 3072 RGHXBOX 192.168.1.188 3072 Additional Router Info: There is no DMZ Option available There is no NAT Settings Option available (see above: Exposed Host) There is no Firewall Rules option available ------------------------------------------------------------------------------------------------------------- Result of Test in Aurora: UPnP Status: UPnP enabled Router Found Data Port Status: Port: 3072 TCP: Fail UDP: Fail Broadcast Port Status: Port 3071 TCP: Fail UDP: Fail JQE360 Authentication Status: Auth [username]: Pass DevLink Disabled: Pass: DevLink is disabled Ping Patch Enabled: Pass: Ping Patch enabled ------------------------------------------------------------------------------------------------------------- Additional Info: I have already tried setting the Router to non DHCP which had the same result. Changing the ports in the Router and in Aurora had the same result. Based on what I have read so far, there may be no open ports in my external ip, but owing to the fact that I was able to connect to Live on the same console before RGH, I doubt that could be it.

Tried that route already.Boots to Xell fine, but the issue pops up right after I flash the updflash file and powercycle console.I presume if it was hardware, even Xell wouldn't have worked. Also I'm posting an image of Xell if it helps

That might be, but something must be up with the NAND image that's causing this. Just reflashed a fresh updflash.bin, console's back to where it started

UPDATE: Console is booting after flashing back to stock!!!! So hardware issue is out. This time around, I've noticed that the updflash.bin image that is being created by Jrunner always has an older CB version (13121) for some reason even after using the recommended settings. If I'm correct, then that must be what's causing this problem. Should not have used that s#@* in the first place Anyway, how do I go about building an updflash.bin image in xebuild gui with an altered SMC setting?

Just rechecked all the wires for continuity like you said. They're all clean and none of them appears to be crushed or damaged. Besides, as far as I'm concerned, the only screw that actually intersects with the wire's pathway is a large one that goes at the center. I kept it blank since I knew there was a wire at that point. I'll try flashing the stock nand to see if it boots then. Here are the NAND images. Hope they help.

R2C8 looks fine to me. And regarding wire patches, I checked 'em out to make sure they don't move. As for flux, I used solder paste instead which I use for all PCB jobs. Never had a problem with it at all. Unfortunately this is the best I can do with a soldering tip that's larger than the points itself. I made the wires short so that they don't get to move around much. Anywho I moved the wire loop away from the X-Clamp now, if its fine. Not messing around with the joints anymore because I sealed them up with glue (they were perfectly soldered though) To clarify,I did test out the console right after flashing the image through Xell. The console booted up fine then. At that moment the motherboard was fitted into the metal case with the DVD drive and wireless module installed (besides the fans and ROL board of course). The problem began right after I fitted all of the remaining componets and the screws and put the console back togethter. By all accounts, it probably isn't a NAND problem. Is there any possibility that this could be an issue with the SOuthbridge? If yes, how do I check to be sure? Or could it be the ROL or the PSU?

Way ahead of you. That was one of the first things I checked for as soon as I took it out of the casing. Even so, if there was a bridge somewhere, wouldnt the problem present itself earlier? The only thing I remember doing right before putting everything back together was to desolder the NAND-X cable. The motherboard was in the metal shell at that moment, but again, I made sure there wasn't any debris or cross connections afterwards. Any resistor or points I can check for continuity to find faults?

Well, I didn't use any of the screw holes, I used one of the JTAG holes. But I am absolutely sure that the wire is intact, unless there is some other factor in play. Since this is a Corona, I presume there isn't a HANA, so it might be somewhere around the Southbridge. I've brushed up the points a bit more to see if any of them was the problem, but to no avail. Here are the pics. I hope they clarify things though.

Not yet actually. Otherwise the console was working fine before I reinstalled the hard drive and cables and the other innards. The only thing that crosses my mind would be the NAND points; I desoldered the JRP cables with the motherboard inside the casing, but I cleaned it up properly though.

So yea, got a new problem. I put everything back together in the metal shell after flashing xebuild image rechecking, but this time the console doesn't power on at all. It just makes a beep whenever I switch on the mains, but otherwise it doesn't respond at all :/ The CR4 seems to be getting power though. The only thing I could think of that might be causing this is a short somewhere. I'm not sure, but could it have something to do with removing the JRP cables from the NAND points with the board in the casing (no qsb so I soldered it to the points)? Any other insights into what might be causing this?

Couldn't get hold of a repair guy, so I went ahead and did it myself. Anyways, I managed to get the console booting again Will it be safe to seal up the joints with hot glue so that they don't get a chance to move? And if yes, will it be a problem if it covers up some of the surrounding components and solder points? And i'm not entirely sure whether the glue sticks i have is E6000

Ah, sorry for the confusion. So basically the console is destined to be stuck in an RROD loop in stock dash unless the FT3T10 point is reconnected topside. Any suitable links you can provide for repair points for all CPU_RST points. Would need to explain it to the repair guy before I get anything done. Also, can you suggest a safe way to secure the wire connecting the points permanently?

But I didn't use the CPU_RST point under the X-Clamp. Like I mentioned in the OP, I have no access to the X-clamp underside, as I can't get my hands on thermal paste. The only point that has been damaged was the FT3T10 point. I am using R4P5 now instead.