-
Content Count
360 -
Joined
-
Last visited
-
Days Won
17
Posts posted by BL4K3Y
-
-
I don't understand why people are in such a rush to update their JTAG/RGH kernel.
For what it's worth, kernel version 16747 and DashLaunch 3.12 are still perfectly fine.
-
Every FIFA game is XBOX Live only.
You can not play XBL-only games over system link.
-
nooooo gutted. lost 180 GB of games dating over the last year.
That's no big deal.
You can simply install/transfer them again from their original games discs .
- 1
-
Excuse me, but just to see if I understand you perfectly:
I just put the new 2TB hard disk (without any format or partitions, totally raw) inside the 360 and I can then configure it totally from the NXE? And then I can put all the games, FSD, etc and transfer my profile, saved games, etc to it? I ask because the FAT32 formated 320GB USB HDD I am using right now to hold my games cannot be read by NXE but it can be perfectly seen by FSD3. NXE just tells me that I have to configure the drive and that it will erase everything on it.
Thanks a lot.
Yes - format/configure your 2TB hard drive and you're all set.
A FAT32 hard drive can't be accessed in NXE/Metro unless it has been formatted/configured first.
-
plug n play thanks to the jtag
Almost .
It needs formatting/configuring, but apart from that, there is nothing you need to do.
-
You can use XZP Tool to extract and re-package skin files.
-
The HDD signature check is removed in JTAG/RGH images which means you can use any size hard drive you like.
A 5400RPM drive is perfectly fine as read/write times are fine and the HDD will run quiet.
I have a 2.5" 500GB Seagate hard drive in my RGH console.
- 3
-
Build an image with "noremap" enabled and write it to the console with RawFlash.
If this fails, you will need a hardware flasher (you can buy one or you can make your own).
-
Your console looks like a Jasper (look at the Southbridge chip).
Use XeBuild's Update Mode (UPDSERV) and the build type will be detected for you.
-
Not HDD1, not HDDX, rather HDDSYSEX
Good point, but as far as I know, it won't transfer the data to any other device (IntMU/USB).
-
so i should accept the liv update? or download it from the web and install?
You don't ever accept an official system update when you are using a JTAG/RGH console.
You need to apply the correct update to match your console's current kernel version.
For example, if your JTAG/RGH console is on 16747, you can apply the 16747 update to install Avatar/Kinect data.
It is also worth mentioning that XeBuild's Update Mode will send the data to your console's internal hard drive (HDD1) if the correct $SystemUpdate folder is present.
- 1
-
Is it an internal hard drive or an external USB hard drive?
-
You need to point the Default line in Launch.ini to FSD's Default.xex.
You can do this manually or set the path using the DashLaunch Installer.
For example: Default = Hdd:\FSD\Default.xex.
- 1
-
How do I do that from nxe? I'm sorry if it sounds like a stupid question but I'm new at this.
Replace the files in your FSD folder with clean FSD3 rev775 files.
-
XeBuild's update mode makes updating your console's kernel version a piece of cake!
It updates your console using LAN, so not only is it easier than ever, it is also a quick process.
The only thing you need to do is enable/launch UPDSERV on your console, execute one command and XeBuild will do the rest.
-
hi guys thanks for your replies , yeah theres no memory unit so this is a 16MB
thats the end of this chapter , progressing further into RGH
Pay attention to what Swizzy said about there being an "old" Flash Config for 16MB Jasper boards.
If you see Flash Config 0x01198010, you must use the "jaspersb" image type when building your image.
I believe his GUI will select the correct radio button when you load your NAND image as the source .
- 1
-
I was lost my original nand so I need to make retail nand I have some doubt for making retail nand,,,i was extract my glitch nand nw I have kv.bin,smc.bin,smc config.bin, ldv,cpu key I was downloaded clear doner nand for smc.bin my question is which file was need from doner nand, smc.bin is enough or else smc_confi.bin also need for making retail nand
To build a retail NAND image from files, you need the console's CPU key, the original KV, the SMC Config (original if possible) and a clean/stock SMC.
You also need FCRT from a slim console or it will refuse to boot any games, even if you build and write a valid retail NAND image.
You also need to make sure the CB and LDV match what CPU fuses say or the console will show RROD error code 0022.
- 1
-
Is the "clicking" sound coming from the HDD?
-
Which version of XeLL has the NAND got on it at the moment?
Build a new image for your console (JTAG/Glitch), rename it to updflash.bin and put it on the root of a FAT32-formatted USB stick.
Boot your console to XeLL with the USB stick connected and tell us what happens.
For future reference, DO NOT modify/delete ANY files from the Flash:\ partition unless you know what you are doing.
In fact, disable the Advanced File Manager view in FSD and then you won't be tempted to mess with any files there .
- 1
-
connected to Trinity with updsvr version 2 (peek version 2)sending flash data to console...file sent OK, awaiting result...success!Completed in 18sloading avatar data...***** WARNING: could not find manifest data for sysex!***** WARNING: avatar data skipped, unable to load data!sending reboot command...OK16747_g2_trinity.bin image built, info:---------------------------------------------------------------Kernel : 2.0.16747.0Console : TrinityNAND size : 16MiBBuild : Glitch (v2)Xell : power on console with console eject buttonSerial : 052226412505ConsoleId : 060153589030MoboSerial: 794893E204271255Mfg Date : 06/14/2011CPU Key : 2A35D492FF26486CE4C3345ACDC30EA91BL Key : DD88AD0C9ED669E7B56794FB68563EFADVD Key : 0A61137DCC8B3DB140F345B51E16BBD8CF LDV : 2KV type : type2 (hashed - Good! Signature is valid.)---------------------------------------------------------------xeBuild Finished. Have a nice day.---------------------------------------------------------------Did you put the 16747 $SystemUpdate folder in the XeBuild\16747 folder?
-
Why don't you use XeBuild's Update Mode (UPDSERV) to update your console to 16747 and let it transfer the system update data to your console?
Read this great tutorial (thanks JPizzle!) and remember to replace 16537 files with 16747.
-
Put the DashLaunch v3.12 installer on a USB stick and launch it with XeXMenu or FSD.
Your first USB device will be seen as USB0 and the second as USB1.
-
Removing a path in FSD will only remove it's entry from the database - your games will still be present on the HDD.
When you use the function to copy a game disc to your console's hard drive, you can play the game without the disc in the drive (that function basically extracts the contents of the disc to the hard drive).
You shouldn't confuse that with mandatory game installs because those are different.
-
16747 is the new version...
Yeah, I just found out myself .
make a shortcut in nxe
in Aurora support
Posted
Give QuickBoot a try.
It will create an NXE shortcut to a XEX file.