Jump to content
RealModScene

BL4K3Y

Members
  • Content Count

    360
  • Joined

  • Last visited

  • Days Won

    17

Posts posted by BL4K3Y


  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.


  2. 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.

    • Like 1

  3. 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.


  4. 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 :).

    • Like 1

  5. 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.

    • Like 1

  6. 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 :).

    • Like 1

  7.  

     
    connected to Trinity with updsvr version 2 (peek version 2)
    sending flash data to console...
    file sent OK, awaiting result...success!
    Completed in 18s
    loading avatar data...
    ***** WARNING: could not find manifest data for sysex!
    ***** WARNING: avatar data skipped, unable to load data!
    sending reboot command...OK
    16747_g2_trinity.bin image built, info:
    ---------------------------------------------------------------
    Kernel    : 2.0.16747.0
    Console   : Trinity
    NAND size : 16MiB
    Build     : Glitch (v2)
    Xell      : power on console with console eject button
    Serial    : 052226412505
    ConsoleId : 060153589030
    MoboSerial: 794893E204271255
    Mfg Date  : 06/14/2011
    CPU Key   : 2A35D492FF26486CE4C3345ACDC30EA9
    1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
    DVD Key   : 0A61137DCC8B3DB140F345B51E16BBD8
    CF LDV    : 2
    KV 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?


  8. 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.

×
×
  • Create New...