How to update from Kernel 2.0.16203.0 to 17502

[xboxmsian 0]

Hi all,

I am newbie. I recently registered as member. I have JTAG XBOX 360 Console 4GB manufactured 2012.

Where can i find the tutorial how to update this kernel to latest one?

I am unable to play Lego Jurassic World. It kept saying Please download games again.

Can I straight away follow this post without any stages upgrade?

http://www.realmodscene.com/index.php?/topic/6843-xebuild-117-xebuild-gui-2098-17502-kernel-support-added/

 

 

 

 

 

 

 

 

[Swizzy 2084]

You can follow the tutorial linked to from my signature below regardless of what the previous kernel version is... only caveat is that the method for grabbing the cpukey is more limited the further back in kernel versions you go...

Sent from my SM-G903F

[xboxmsian 0]

Do I need to update the XexMenu 1.2? Currently, I am using XexMenu 1.1?

[Atifkazia 222]

Do I need to update the XexMenu 1.2? Currently, I am using XexMenu 1.1?

Not really needed but you can still do it..but whats the use of xexmenu when you have better file manager/browser within aurora or fsd..

You can also update it later..

[xboxmsian 0]

I`ve successfully updated to XexMenu1.2.

I ran Simple_360_NAND_Flasher_v1.2. No issue found. Then I ran xeBuild GUI 2.0 on PC and loaded flashdmp.bin. Then I got error in the screenshot.

[Swizzy 2084]

Well, you have a 4GB corona most likely, the dump is 48mb correct? Then you need to follow the specific instructions for 4g corona

Sent from my SM-G903F

[xboxmsian 0]

Thanks for your help. the dump size is 48MB. Where can i find the specific instrustioncs for 4g corona?

Shall I ignore the error "unable to determine dump size"?

Shall I refer this topic Specific information for Corona with 4GB Internal memory?

How do I get the CPUKey using xeBuild?

[Swizzy 2084]

Shall I refer this topic Specific information for Corona with 4GB Internal memory? 

How do I get the CPUKey using xeBuild?

Yes, read the tutorial, it explains different methods of getting the cpukey

[xboxmsian 0]

I have successfully generated updflash.bin. Anything I need take pre-cautious actions? I have backup the original nand. if something wrong happened, How do I rollback the original nand?

 

done! fsroot found ok!

---------------------------------------------------------------

output.bin image built, info:

---------------------------------------------------------------

Kernel    : 2.0.17502.0

Console   : Corona

NAND size : 48MiB MMC (system only)

......

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!

[xboxmsian 0]

While entering CPUKey, I got the below error but then i`ve successully generated updflash.bin .will any issue happen if update my xbox with the file? How do i rollback the changes if the flash is not working?

[Swizzy 2084]

While entering CPUKey, I got the below error but then i`ve successully generated updflash.bin .will any issue happen if update my xbox with the file? How do i rollback the changes if the flash is not working?

That error is normal as xeBuild GUI doesn't understand mmc dumps (48mb dumps)

Saving the current nand somewhere safe along with the cpukey is really all you need, there shouldn't be any issues with it, as long as the output file is also 48mb, if it's smaller it won't work (and you won't be allowed to flash it either)

If something goes wrong (it no longer starts) you will need to reflash the console using hardware

Sent from my SM-G903F

[xboxmsian 0]

In xeBuild_GUI.log I found an error like "ERROR: Unable to get CB version!ERROR: Unable to decrypt KV using specified CPUKey!"

==================================

 Swizzy's xeBuild GUI version 2.098

 Log Started: Sunday 6/19/2016 7:54:20 AM

==================================

 

 *** Some console information ***

ERROR: Unable to get CB version!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:

 

<--erased-->

 

Building nand using xeBuild (this may take a while):

 

---------------------------------------------------------------

     xeBuild v1.17.785

---------------------------------------------------------------

base path changed to C:\xbox_hack\xeBuild_GUI_2.098\files

---- { Image Build Mode } ----

building glitch2 image

 

done! fsroot found ok!

---------------------------------------------------------------

output.bin image built, info:

---------------------------------------------------------------

Kernel    : 2.0.17502.0

Console   : Corona

NAND size : 48MiB MMC (system only)

Build     : Glitch (v2)

Xell      : power on console with console eject button

Serial    : <--erased-->

ConsoleId : <--erased-->

MoboSerial: <--erased-->

Mfg Date  : <--erased-->

CPU Key   : <--erased-->

1BL Key   : <--erased-->

DVD Key   : <--erased-->

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! ******

 

Shall I need regenerate the updflash.bin file again with the setup in the screenshot?

 

Under Misc,I ticked "Use Custom xeBuild Settings" and "Open Parameter/......"

 

Under Special Patches, I ticked "Disable FCRT .bin check"

[Swizzy 2084]

In xeBuild_GUI.log I found an error like "ERROR: Unable to get CB version!ERROR: Unable to decrypt KV using specified CPUKey!"

==================================

 Swizzy's xeBuild GUI version 2.098

 Log Started: Sunday 6/19/2016 7:54:20 AM

==================================

 

 *** Some console information ***

ERROR: Unable to get CB version!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:

 

<--erased-->

 

Building nand using xeBuild (this may take a while):

 

---------------------------------------------------------------

     xeBuild v1.17.785

---------------------------------------------------------------

base path changed to C:\xbox_hack\xeBuild_GUI_2.098\files

---- { Image Build Mode } ----

building glitch2 image

 

done! fsroot found ok!

---------------------------------------------------------------

output.bin image built, info:

---------------------------------------------------------------

Kernel    : 2.0.17502.0

Console   : Corona

NAND size : 48MiB MMC (system only)

Build     : Glitch (v2)

Xell      : power on console with console eject button

Serial    : <--erased-->

ConsoleId : <--erased-->

MoboSerial: <--erased-->

Mfg Date  : <--erased-->

CPU Key   : <--erased-->

1BL Key   : <--erased-->

DVD Key   : <--erased-->

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! ******

 

Shall I need regenerate the updflash.bin file again with the setup in the screenshot?

 

Under Misc,I ticked "Use Custom xeBuild Settings" and "Open Parameter/......"

 

Under Special Patches, I ticked "Disable FCRT .bin check"

it's normal that you get those errors, it's like i said because xeBuild GUI can't understand MMC dumps...

it should be all good with that, the updflash.bin file is the same size as your flashdmp.bin correct?

[xboxmsian 0]

The file size is still same even though i ticked the following options.

Under Misc,I ticked "Use Custom xeBuild Settings" and "Open Parameter/......"

Under Special Patches, I ticked "Disable FCRT .bin check"

Shall i tick them up before generate the flash file?

Or should i dont tick them up?

Thanks in advance.

[Swizzy 2084]

The file size is still same even though i ticked the following options.

Under Misc,I ticked "Use Custom xeBuild Settings" and "Open Parameter/......"

Under Special Patches, I ticked "Disable FCRT .bin check"

Shall i tick them up before generate the flash file?

Or should i dont tick them up?

Thanks in advance.

What is the filesize? And did you really read ALL instructions?

Sent from my SM-G903F