BL4K3Y
-
Content Count
360 -
Joined
-
Last visited
-
Days Won
17
Everything posted by BL4K3Y
-
Crazy? Try sensible . If you plan on taking the console back to it's retail state in the future, use a donor KV. This is a safer option and you don't need to worry about getting the original key vault banned.
-
Have you tried another hard drive? Dump the NAND image from the console using the client mode "-i" switch and check for bad blocks. You can find your console's NAND image in the "mydata" folder.
-
I think he's talking about using XeBuild mode to manually create an image and then use XeLL or an application like Swizzy's Simple 360 NAND Flasher to write the image to your console's NAND. What is the issue with UPDSERV? As long as your console is in the same IP range as your computer, the update mode should work fine.
-
The option to include DashLaunch patches is enabled by default in the latest J-Runner build. Make sure liveblock is true and livestrong is false in launch.ini to stop the console from connecting to XBL. If you want to play XBLIG, you need to enable fakelive.
-
Do you see an IP address in FSD? I'm using Windows 7 x64 as well and this works fine. You can force XeBuild to use an IP address you specify by using the "-ip <IP goes here>" switch on the command line.
-
A 3.5" hard drive requires 12v to power it. There are several 12v power sources on the XBOX 360 motherboard.
-
They should put a new NAND image on there for you (16537) and update DashLaunch patches. I'd be pretty angry if I had paid somebody for a JTAG/RGH modification and they didn't use the latest updates. I did three RGH installs for a friend using the 16203 dashboard files and a week later, 16537 files were released, so I told my customers how to use UPDSERV to update the dashboard using LAN.
-
You can connect your console to a router (recommended) or to a PC. The console must be in the same IP range as your computer.
-
This new version of XeBuild takes care of everything including reading the NAND, creating a new image, writing it back to the console and even installing system update data (for Avatars and Kinect)! All you need to do is connect your console to your network and enter one simple command on the command line .
-
Use DashLaunch to set paths and enable/disable settings. Once you are happy with the changes, press RB until you see the menu which lists the hard drive (HDD1) and then press X to save launch.ini to your hard drive (it will overwrite what is already there). If you set the Default path correctly, you should be greeted with F3 each time you boot the console.
-
Read this tutorial. It explains how to update the kernel version on your JTAG/RGH console.
-
You don't need to remove DashLaunch. There is no AUD_CLAMP JTAG wiring for Xenon consoles. If you follow the tutorial correctly, your console will be updated to the latest dashboard version. DashLaunch doesn't require network or internet access to function.
-
Have you extracted disc 1 and put the Content folder in HDD1? Disc 1 is the installation disc and disc 2 is the game.
-
The kernel version on that console is old. Build a 16537 JTAG image (use the updserv method - the tutorial is here) and then install DashLaunch v3.09.
-
I don't think NXE2GOD is required anymore. FSD will deal with games installed with Metro/NXE on it's own now .
-
It won't reduce it to 32GB. It will reserve 32GB on the drive for XBOX 360 storage and the remaining space should still be accessible in Windows.
-
Did you put the $SystemUpdate folder in the XeBuild16537 folder?
-
Being a Villa fan has to be better than being a scouse fan lmao. Just kidding - welcome to the forum !
-
I convert multiple disc games together using ISO2GOD and it places them in the same folder. All you need to do from there is move the entry for the other disc(s) to "No Section" and FSD will deal with the disc swap when it is required.
-
System update data will only be installed to HDD1 (an internal HDD) as far as I know. You can also follow this tutorial to manually install Avatars and Kinect data.
-
You are correct. He can either build a new image (recommended) or manually put bootanim.xex in the Flash: partition.
-
Are you 100% sure that you are running the 16537 system update? Is there a storage device attached to the console?
-
I have set the temperature thresholds on my slim with DashLaunch - they are set to 70/70/70, but the room temperature is quite cool most days. Setting those thresholds in DashLaunch means that the console will try and maintain those temperatures automatically and the fan speed will be altered when it is required. An alternative to doing this is to set the temperature thresholds with XeBuild before building your image.
-
I can not see the new F3 775 bar by pressing the guide!!!
BL4K3Y replied to Marcio Fontes's topic in Support
Post a screen shot showing what you mean (click the left analog stick in FSD). -
The latest version of XeBuild and UPDSERV automatically installs system update data to HDD1, so this tutorial is pretty much redundant now.
