Jump to content
RealModScene

Search the Community

Showing results for tags 'cpu key'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Site News
    • Scene News
  • Phoenix
    • Aurora releases
    • Aurora support
    • Aurora Localization
    • Skins, Coverflow Layouts, Scripts and Trainers
    • Skin development and LUA scripting
    • Unity Support
    • Requests and Suggestions
  • FreeStyle Dashboard / F3
    • News
    • FreeStyle Dashboard Releases
    • Support
    • Skins
    • Skin Dev
  • Xbox
    • Tutorials
    • Homebrew
    • LibXenon
    • Games
    • Software
    • Other topics
  • PlayStation
    • Tutorials
    • Homebrew
    • Games
    • Software
    • Other Topics
  • Matchmaking
    • North America
    • Central & South America
    • Europe
    • Asia
    • Africa
    • Australia
    • Modded Lobbies
  • MarketPlace
    • Buy
    • Sell
  • Miscellaneous
    • Feedback
    • Other Topics
    • LiNK News

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. Hello all, I've got an old XBOX360 slim 250 GB with Kinect, manufactured in 2010. It was JTAged at the time (probably RGH?). DashLaunch V3.19 (592) shows Trinity, Glitch 2, Kernel 2.0.14699.0. Few days ago I started to prepare it for my Kids to have some fun. I have XexMenu 1.2 installed, no FSB or Aurora. I tried to install AURORA 0.7b1, but I can't, from what I read on the forums, could be because the Kernel is too old. I tried to update Kernel with xeBuild_GUI_2.098_17559, but I am stuck by not having a CPU Key. Also DVD Key is missing in System Info of a DashLaunch. Tried to get it somehow through XBOX360 Neighbourhood with usage of Xbdm.xex, but I just cant retreive the XBOX's IP to make it connect with my laptop. Was trying to obtain CPU Key by Eject button boot, but it doesn't show me Xell, just boots up normaly. If anyone could please point me in the right direction on how to obtain my CPU Key the easiest or any other way, please help. Spending hours searching the forums and I am about to give up. Tnx
  2. So I have a Falcon that had been sitting in a box for a good while that is a failed Rgh 1.2 attempt from when I first was diving into console modding. Long story short, I didn't know what I was doing at that point and managed to mistakenly flash a nand dump that belonged to a different console. This wouldn't be a huge issue but I no longer have any of the nand dumps from back then thanks to my lovely wife deciding to wipe the desktops hdd without giving me any heads up. Fast forward to today, I've removed the 1.2 wiring and glitch chip, and done RGH 3 wiring. Console would boot xell, but the cpu key in xell was rejected in jrunner as the wrong cpu key. Is there any hope of this console booting a hacked dash? I've built a donor nand image in jrunner, but the console will not boot xell or a hacked dash after flashing this nand image. I thought that the cpu key given in xell would be the correct one, even though I mistakenly wrote the wrong nand image to the console forever ago? If not, is there any possible way of recovering the cpu key at this point, or am I totally up a creek? I do have a dump of the nand that would boot xell so I can at least fall back to that point, if it helps at all. Thanks in advance to anyone who is willing to lend some advice.
  3. Hello Have a Trinity 4GB. I updated yesterday from kernel 15574 to 16747 using xeBuild_GUI_2.093. Everything appears to be running fine except for XeLL. XeLL 0.991 was running ok and showing me all the normal info, including my 2 keys. XeLL 0.993 does not show any of the keys. It appears to hang after SATA device at ea001200 My ATAPI DVD is identified by XeLL as HL-DT-STDVD-ROM DL10N I think I have read something about a bug on this version of XeLL and Hitachi drives. Is this the reason to this happening? No USB device has been connected to the console at boot.
×
×
  • Create New...