Leaderboard

This is NOT for updating your JTAG/RGH dashboard/kernel, this is for installing Avatar/Kinect data ONLY. To change the dashboard/kernel version of your JTAG/RGH console, you build a new image with J-Runner or similar. Before you proceed, ensure you have an internal hard drive connected with enough space for the update (I think somewhere around 128MB is required). Also, ensure that you have DashLaunch installed and configured. So, you have a JTAG or RGH system, but no Avatars or Kinect? This small tutorial will help you install them (ensure your Kinect hardware is connected before you begin or you will be prompted to update again once you connect it!). Step 1 Download the USB system update from here (remember to check that the system update you download matches your JTAG/RGH kernel version - go to System Settings>Console Settings>System Info and read where it says Dashboard: 2.0.XXXXX.0, where X = your current dashboard/kernel version). Step 2 Extract the $systemupdate folder from the archive with 7-Zip or similar and rename it to $$ystemUpdate. Step 3 Transfer the $$ystemUpdate folder (the one you renamed in Step 2) to the root of a FAT32-formatted USB stick (I recommend 512MB+). Step 4 Connect your USB stick to your console, power it on and accept the update when prompted. There are different messages shown based on what the system update is going to apply. If you see this: Do NOT accept the update because this is telling you that the system is going to attempt a complete update which alters bootloaders and it will also burn eFUSEs. If you see this: It is fine to proceed with the update. This is the system telling you that additional components are missing. The console will reboot once the update has installed successfully and you should now see Avatars and have Kinect installed (don't forget to configure it!). If the console doesn't do anything, ensure that: The update folder is named correctly.The system update you are applying matches the JTAG/RGH dashboard/kernel version your console is currently running (see Step 1).You inserted the USB stick before booting the console (FSD can block the system update).If, after all this is attempted, the console still won't update, go into FSD and then into the File Manager, look for a SysExt: folder and delete what you can (don't forget to enable File Manager Advanced Mode in General Settings first). Reboot the console and you'll be told that there are corrupted files - reboot the console to resolve this. Do this with the USB stick connected and your console should prompt you to accept the update. I find that if I boot the console to NXE/Metro (hold RB after powering the console on) and THEN insert the USB stick, the update prompt shows up.

When LiNK was first out, there were some users who found out quite unhappily pfSense and LiNK don't work together. There were oddball ways to get around scrapping your pfSense in favor of a generic router, but all were kind of crappy. Either way, the issue is LiNK is using encrypted packets and pfSense doesn't handle this well right out of the box. Without getting into the nitty gritty of why this occurs, I'll just sum it up. LiNK sends a packet out, pfSense gets this packet and messes with the header of the packet so it can route it through other ports and use different IP's etc (correct me if I'm wrong). There is a really simple solution to this that I suppose was undiscovered to the few who have tried making it work. It is a feature in pfSense called 'Static Port'. So the solution is simple. You must enable static port for the outbound NAT rule for the xbox. This forces pfSense to route the traffic through the ports LiNK wants it to. 1. Set a static IP for your xbox (either on the xbox itself, or through the DHCP server) 2. Create a port forward rule under NAT for the xbox IP and specify the two ports you have set in LiNK settings on the console (ie 3071/3072) 3. Create an outbound NAT rule (manual NAT must be used) on your WAN interface using the xbox ip as the source (ie 192.168.1.100/32). At the bottom of the rule tick the box that says 'use static port'. 4. Test! There is a possibility you need to reset your firewall states and try again. Mods feel free to move/edit this. Just wanted to share my findings and couldn't find a better place to do so. NOTE: Tested with pfSense 2.0.3. Confirmed by toggling static port on and off with all the same rules. UPnP 'could' work but I was unable to get it working properly myself. Tutorial assumes you already know how to use pfSense and are following other tutorials for port forwarding/setting up link. This is really just to clarify the outbound nat rule importance.

Solved , If anyone got same issue , Delete the Fsd3 u use at the moment , Download the fsd 3 offline package here , Zip it up, FTP over to xbox , Fix the settings etc ( as u like it ) And its solved ( hopefully ) Helped me

It might be better if you posted the answer in case another member has the same problem