donixa 0 Posted April 26, 2020 Since corona pandemic situation in 2020, I reopened my old xbox 360, last time I played it many years ago, was quit because of fatal crash intercepted, before that happen, I did use cheat save mod, I forget whats is name, deleted the program already, it was working for sometime, not long, then I began had that fatal crash intercepted, then stop playing, but I suspect that was not problem, since I have the this FCI even when trying to reload the game, got same FCI while game is loading for the first time, Now I have experience same problem, tried to adjust and configure Usb0:\Content\0000000000000 with scan depth 7 (after researching and concluded may be this one was missing), after power off a while, the game was successfully load and play the game abit longer, but then fatal crash intercepted, I use Freestyle rev 735, I have read somewhere here, just use Aurora, they say its better, my quick reaction is what to do with old game saves, is it save, My question: Any recommended quick easy solutions? What is my alternative solutions and its how to? many thanks, happy work (game) from home Quote Share this post Link to post Share on other sites
donixa 0 Posted April 26, 2020 someone said that Diablo 3 Reaper of Soul UEE needs to be played minimum at kernel version 16537 and up, in other similar info, games from 2014 release also require particular updated kernel version, my version is attached shows 2.0.16203.0, is this the main culprit? Where should I go next from here? Quote Share this post Link to post Share on other sites
Neocazen 27 Posted April 26, 2020 1 hour ago, donixa said: someone said that Diablo 3 Reaper of Soul UEE needs to be played minimum at kernel version 16537 and up, in other similar info, games from 2014 release also require particular updated kernel version, my version is attached shows 2.0.16203.0, is this the main culprit? Where should I go next from here? A Freestyle is famous for faltalcrash and may be a possible cause of your problem. I suggest installing Aurora and leave as main, in parallel at least, for eventual diagnosis. Your Kernel is pretty old too, but we'll leave it to a second option for testing. Quote Share this post Link to post Share on other sites
donixa 0 Posted April 26, 2020 I have XBOX 360 S with manufacture date: 24 Feb 2012 with rounded power port like below, so I guess definitely corona version, it says 12v 9,6a, Just to make sure it says corona, I have to install dash launch, what version can i install the dash launch? Can I upgrade directly to latest kernel? Do we have link for that in this forum, thanks for replying, Quote Share this post Link to post Share on other sites
felida 1653 Posted April 26, 2020 6 hours ago, donixa said: I have XBOX 360 S with manufacture date: 24 Feb 2012 with rounded power port like below, so I guess definitely corona version, it says 12v 9,6a, Just to make sure it says corona, I have to install dash launch, what version can i install the dash launch? Can I upgrade directly to latest kernel? Do we have link for that in this forum, thanks for replying, All 9.6 are corona.. lol.. you could have a 4g nand or a regular 16mb nand depending.. You can use swizzys simple nand flasher to dump your current nand, then use one of multiple programs to update your nand.. then flash it with nand flasher.. there are guides on this site if you search.. Quote Share this post Link to post Share on other sites
donixa 0 Posted April 27, 2020 Thanks for replying, someone posted swizzys tools and showed very noob friendly tutorial to update kernel, the poster was appreciated as being the most clear, concised, and precise steps, he mentioned: Before Starting, Remove your Current Launch.ini. If you don't you may be stuck on the Xbox Logo after Boot. Is this correct? does it mean I boot the xbox 360, goto file manager look for it at root level in any partitions, delete/move it, and start using the Simple 360 NAND Flasher, or delete/move it, then reboot, after that use Simple 360 NAND Flasher? Sorry this looks dumb, Quote Share this post Link to post Share on other sites
felida 1653 Posted April 27, 2020 45 minutes ago, donixa said: Thanks for replying, someone posted swizzys tools and showed very noob friendly tutorial to update kernel, the poster was appreciated as being the most clear, concised, and precise steps, he mentioned: Before Starting, Remove your Current Launch.ini. If you don't you may be stuck on the Xbox Logo after Boot. Is this correct? does it mean I boot the xbox 360, goto file manager look for it at root level in any partitions, delete/move it, and start using the Simple 360 NAND Flasher, or delete/move it, then reboot, after that use Simple 360 NAND Flasher? Sorry this looks dumb, you dont need to remove the launch.ini.. that seems like to be remove the rgloader.ini.. or xbdm.ini.. launch.ini wont mess with anything.. Quote Share this post Link to post Share on other sites
donixa 0 Posted April 27, 2020 Am I looking good with below? thanks for replying, ================================== Swizzy's xeBuild GUI version 2.098 Log Started: Tuesday 28/04/2020 2:37:46 ================================== *** Some console information *** CB Version: 0 ERROR: Unable to decrypt KV using specified CPUKey! This means the log will NOT contain information from your keyvault, it can be caused by etheir badkey or badblock/corrupt keyvault Using xell-reloaded for Glitch hack Including dashlaunch... Done! Including custom dashlaunch settings (launch.ini)... Done! Copying nand to data directory, this may take a while... Done! Checking if SMC is Glitch or Retail... Dumping current SMC... Done! Checking SMC... SMC is Glitch patched! it will be used the way it is... Parameters sent to xeBuild: -noenter -t glitch2 -c corona4g -d data -f 17559 -b DD88AD0C9ED669E7B56794FB68563EFA -p 5EE4BD8621861BFD86F46EA80C114E2D output.bin Building nand using xeBuild (this may take a while): --------------------------------------------------------------- xeBuild v1.21.810 --------------------------------------------------------------- base path changed to D:\Program Sources\XBOX 360\xeBuild_GUI_2.098 (17559)\files ---- { Image Build Mode } ---- building glitch2 image done! fsroot found ok! --------------------------------------------------------------- output.bin image built, info: --------------------------------------------------------------- Kernel : 2.0.17559.0 Console : Corona NAND size : 48MiB MMC (system only) Build : Glitch (v2) Xell : power on console with console eject button Serial : [myserialnumber] ConsoleId : [myconsoleid] MoboSerial: [mymbserial] Mfg Date : 02/24/2012 CPU Key : [mycpukey] 1BL Key : [my1blkey] DVD Key : [mydvdkey] CF LDV : 1 KV type : type2 (hashed - unchecked, master key not available) --------------------------------------------------------------- xeBuild Finished. Have a nice day. --------------------------------------------------------------- Moving output to your destination directory... Done! Cleaning data and temporary directories... Done! ****** The app has now finished! ****** Quote Share this post Link to post Share on other sites
felida 1653 Posted April 28, 2020 6 hours ago, donixa said: Am I looking good with below? thanks for replying, ================================== Swizzy's xeBuild GUI version 2.098 Log Started: Tuesday 28/04/2020 2:37:46 ================================== *** Some console information *** CB Version: 0 ERROR: Unable to decrypt KV using specified CPUKey! This means the log will NOT contain information from your keyvault, it can be caused by etheir badkey or badblock/corrupt keyvault Using xell-reloaded for Glitch hack Including dashlaunch... Done! Including custom dashlaunch settings (launch.ini)... Done! Copying nand to data directory, this may take a while... Done! Checking if SMC is Glitch or Retail... Dumping current SMC... Done! Checking SMC... SMC is Glitch patched! it will be used the way it is... Parameters sent to xeBuild: -noenter -t glitch2 -c corona4g -d data -f 17559 -b DD88AD0C9ED669E7B56794FB68563EFA -p 5EE4BD8621861BFD86F46EA80C114E2D output.bin Building nand using xeBuild (this may take a while): --------------------------------------------------------------- xeBuild v1.21.810 --------------------------------------------------------------- base path changed to D:\Program Sources\XBOX 360\xeBuild_GUI_2.098 (17559)\files ---- { Image Build Mode } ---- building glitch2 image done! fsroot found ok! --------------------------------------------------------------- output.bin image built, info: --------------------------------------------------------------- Kernel : 2.0.17559.0 Console : Corona NAND size : 48MiB MMC (system only) Build : Glitch (v2) Xell : power on console with console eject button Serial : [myserialnumber] ConsoleId : [myconsoleid] MoboSerial: [mymbserial] Mfg Date : 02/24/2012 CPU Key : [mycpukey] 1BL Key : [my1blkey] DVD Key : [mydvdkey] CF LDV : 1 KV type : type2 (hashed - unchecked, master key not available) --------------------------------------------------------------- xeBuild Finished. Have a nice day. --------------------------------------------------------------- Moving output to your destination directory... Done! Cleaning data and temporary directories... Done! ****** The app has now finished! ****** No.. it says your cpu key is bad.. lol Quote Share this post Link to post Share on other sites
donixa 0 Posted April 28, 2020 I did the kernel update anyway, and was patched, so I guess that means OK? What is the reason to have ERROR: Unable to decrypt KV using specified CPUKey! I use XEbuild 2.098, the tab main shows ERROR in serial number field and so on, but the output shows all correct values like serial number, so thats why I apply patch anyway, it was patched and able to play D3 ROS, Oh anyway I just realized in 2017 we have latest expansion pack downloadable, diablo 3 rise of the necromancer, can I use it in xbox 360? Thanks, Quote Share this post Link to post Share on other sites