You are viewing our Forum Archives. To view or take place in current topics click here.
Troubleshooting | Updating To 16756 | Common Errors
Posted:
Troubleshooting | Updating To 16756 | Common ErrorsPosted:
Status: Offline
Joined: Apr 05, 201113Year Member
Posts: 361
Reputation Power: 17
Status: Offline
Joined: Apr 05, 201113Year Member
Posts: 361
Reputation Power: 17
[ Register or Signin to view external links. ]
[ Register or Signin to view external links. ]
[ Register or Signin to view external links. ]
Requirements:
- JTAG/RGH
- USB Flash Drive (at least 1GB)
- CPU Key
- Your NAND
- Flash 360
- XeBuild
- Xex Menu
- Dashlaunch 3.12 (Optional)
*Before continuing, You will need to download Flash360, Xebuild, and Xexmenu
(If you have everything listed above, please skip to step 5.)
- USB Flash Drive (at least 1GB)
- CPU Key
- Your NAND
- Flash 360
- XeBuild
- Xex Menu
- Dashlaunch 3.12 (Optional)
*Before continuing, You will need to download Flash360, Xebuild, and Xexmenu
(If you have everything listed above, please skip to step 5.)
Step 1:
Step 2:
Installing XexMenu:
*Note: To use this method, You will need to download Horizon first*
- Download Xexmenu 1.2 and extract it to your desktop. (Xexmenu 1.1 works also.)
- Open the extracted folder and continue opening the folders until you see C0DE99990F586558 (Should be the last file)
- Open Horizon, insert your Fat32 configured USB into your computer.
- Open Horizon, go to device explorer.
- Open USB in device explorer, Right click demos, Select "Inject file"
- Navigate to the file C0DE99990F586558 and inject file to your USB
- Wait until finished, then unplug USB
- Plug USB into your JTAG/RGH
- Navigate to system settings, storage, and select your USB
- Navigate to Demos folder on your usb and you will see XexMenu, Move XexMenu to HDD
- XexMenu is now located in your Games folder.
*Note: To use this method, You will need to download Horizon first*
- Download Xexmenu 1.2 and extract it to your desktop. (Xexmenu 1.1 works also.)
- Open the extracted folder and continue opening the folders until you see C0DE99990F586558 (Should be the last file)
- Open Horizon, insert your Fat32 configured USB into your computer.
- Open Horizon, go to device explorer.
- Open USB in device explorer, Right click demos, Select "Inject file"
- Navigate to the file C0DE99990F586558 and inject file to your USB
- Wait until finished, then unplug USB
- Plug USB into your JTAG/RGH
- Navigate to system settings, storage, and select your USB
- Navigate to Demos folder on your usb and you will see XexMenu, Move XexMenu to HDD
- XexMenu is now located in your Games folder.
Step 3:
Installing Flash360:
- Download Flash360 and extract it to your Desktop.
- Plug USB into computer and Place Flash360 and MEDIA on the root of your USB
- Unplug USB from computer.
- Plug into JTAG/RGH and power console on.
- Launch XexMenu and navigate to HDD
- Press Y, then click create, and name the folder Flash360
- Then Navigate from your HDD to your USB
- Locate Flash360 and MEDIA files on the USB
- Copy both files into the Flash360 folder you created on your HDD
- You are now ready to dump your Nand.
- Download Flash360 and extract it to your Desktop.
- Plug USB into computer and Place Flash360 and MEDIA on the root of your USB
- Unplug USB from computer.
- Plug into JTAG/RGH and power console on.
- Launch XexMenu and navigate to HDD
- Press Y, then click create, and name the folder Flash360
- Then Navigate from your HDD to your USB
- Locate Flash360 and MEDIA files on the USB
- Copy both files into the Flash360 folder you created on your HDD
- You are now ready to dump your Nand.
Step 4:
Extracting your NAND:
- Plug USB into your JTAG/RGH
- Launch XexMenu, navigate to Flash360 and launch Flash360.xex
- Press X to backup your Nand, Then press A to start.
- Once done press the back button and exit Flash360.
- Your NAND should be in the Flash360 folder you just created in step 3.
- If done correctly, you should have a file named "flashdmp.bin"
- Hover over flashdmp.bin, Press Y then copy the file.
- Navigate back over to USB, Press Y and paste your flashdmp.bin file.
- Unplug USB from JTAG/RGH and plug into your computer.
- Copy your flashdmp.bin file to the desktop.
- Now you're ready for Step 5.
*Most people, including myself recommend making a backup of your Nand and CPU/DVD Key in case you ever happen to have a bad flash*
- Plug USB into your JTAG/RGH
- Launch XexMenu, navigate to Flash360 and launch Flash360.xex
- Press X to backup your Nand, Then press A to start.
- Once done press the back button and exit Flash360.
- Your NAND should be in the Flash360 folder you just created in step 3.
- If done correctly, you should have a file named "flashdmp.bin"
- Hover over flashdmp.bin, Press Y then copy the file.
- Navigate back over to USB, Press Y and paste your flashdmp.bin file.
- Unplug USB from JTAG/RGH and plug into your computer.
- Copy your flashdmp.bin file to the desktop.
- Now you're ready for Step 5.
*Most people, including myself recommend making a backup of your Nand and CPU/DVD Key in case you ever happen to have a bad flash*
Step 5:
Updating to 16756:
**Note** Remove ALL plugins from Dashlaunch before updating!
This will reduce the chance of you having a bad flash, dashlaunch freezing, getting stuck on xbox boot logo, etc.
- Open xeBuild GUI 2.0
[ Register or Signin to view external links. ]
- Click Open(1), Locate where you saved your "flashdmp.bin" and open it.
- Click Save(2) and save it to the root of your USB as Updflash
- Navigate to the CPUKey textbox(3) and enter in Your CPU key. (If you don't have your CPU key, refer back to Step 1)
- Navigate to the Kernel Version Textbox(4) and select 2.0.16756.0
- Navigate to the top of the page and remember the output path(2).
- For this Tut, I saved it to the root of the USB as Updflash
(This is where your Updflash.bin file will be)
- Click "Generate hacked image"(5), then click yes when prompted to close the program.
- Locate your Updflash.bin file that you just created and copy it to the root of your USB
- Ignore(6) right now.
- Now you're ready to flash your Nand
Flashing using Xell:
Flashing using Flash360:
**Note** Remove ALL plugins from Dashlaunch before updating!
This will reduce the chance of you having a bad flash, dashlaunch freezing, getting stuck on xbox boot logo, etc.
- Open xeBuild GUI 2.0
[ Register or Signin to view external links. ]
- Click Open(1), Locate where you saved your "flashdmp.bin" and open it.
- Click Save(2) and save it to the root of your USB as Updflash
- Navigate to the CPUKey textbox(3) and enter in Your CPU key. (If you don't have your CPU key, refer back to Step 1)
- Navigate to the Kernel Version Textbox(4) and select 2.0.16756.0
- Navigate to the top of the page and remember the output path(2).
- For this Tut, I saved it to the root of the USB as Updflash
(This is where your Updflash.bin file will be)
- Click "Generate hacked image"(5), then click yes when prompted to close the program.
- Locate your Updflash.bin file that you just created and copy it to the root of your USB
- Ignore(6) right now.
- Now you're ready to flash your Nand
Flashing using Xell:
- Plug USB into JTAG/RGH with the console off.
- Press the Eject button on your JTAG/RGH to power on.
- Xell will boot up and within a few seconds you should see "rawflash v4 started"
- Wait until you see "Image written, shut down now!", then shut down the console using the power button on your JTAG/RGH.
- Although this is not required, most people suggest removing the power brick for 30 seconds after powering down the console.
- This will power cycle your console
- Press the Eject button on your JTAG/RGH to power on.
- Xell will boot up and within a few seconds you should see "rawflash v4 started"
- Wait until you see "Image written, shut down now!", then shut down the console using the power button on your JTAG/RGH.
- Although this is not required, most people suggest removing the power brick for 30 seconds after powering down the console.
- This will power cycle your console
Flashing using Flash360:
- Plug USB into JTAG/RGH with the console off.
- Power console on, run XexMenu, Navigate to your USB and locate your Updflash.bin
- Copy your Updflash.bin to your Flash360 folder you created on the HDD
- Launch Flash360.xex
- To Update, Press A, A, Start, A
- Once finished, press back, then shut down the console using the power button on your JTAG/RGH.
- Although this is not required, most people suggest removing the power brick for 30 seconds after powering down the console.
- This will power cycle your console
- Power console on, run XexMenu, Navigate to your USB and locate your Updflash.bin
- Copy your Updflash.bin to your Flash360 folder you created on the HDD
- Launch Flash360.xex
- To Update, Press A, A, Start, A
- Once finished, press back, then shut down the console using the power button on your JTAG/RGH.
- Although this is not required, most people suggest removing the power brick for 30 seconds after powering down the console.
- This will power cycle your console
Step 6:
Power on JTAG/RGH:
- Navigate to your Dashboard
- Go to Settings > System > Console Settings
- Scroll down to System Info, Your current dashboard should now be 2.0.16756.0
Congratulations you have now successfully updated to 16756!
- Navigate to your Dashboard
- Go to Settings > System > Console Settings
- Scroll down to System Info, Your current dashboard should now be 2.0.16756.0
Congratulations you have now successfully updated to 16756!
Fixing black screen, Xbox stuck on boot logo, Bad flash, Etc:
Common Errors:
- Black screen
- Stuck on boot logo
- Powers on then off
- Dashlaunch freezes
- With your console off press Eject
- If you can boot into Xell, follow the steps below
- On your computer, locate your Flashdmp.bin file
- Rename it Updflash.bin
- Put onto the root of your USB
- Plug USB into JTAG/RGH with the console off.
- Press the Eject button on your JTAG/RGH to power on.
- Xell will boot up and within a few seconds you should see "rawflash v4 started"
- Wait until you see "Image written, shut down now!", then shut down the console using the power button on your JTAG/RGH.
- Although this is not required, most people suggest removing the power brick for 30 seconds after powering down the console.
- This will power cycle your console
- How to avoid these errors/problems
- Black screen
- Stuck on boot logo
- Powers on then off
- Dashlaunch freezes
- With your console off press Eject
- If you can boot into Xell, follow the steps below
- On your computer, locate your Flashdmp.bin file
- Rename it Updflash.bin
- Put onto the root of your USB
- Plug USB into JTAG/RGH with the console off.
- Press the Eject button on your JTAG/RGH to power on.
- Xell will boot up and within a few seconds you should see "rawflash v4 started"
- Wait until you see "Image written, shut down now!", then shut down the console using the power button on your JTAG/RGH.
- Although this is not required, most people suggest removing the power brick for 30 seconds after powering down the console.
- This will power cycle your console
- How to avoid these errors/problems
- Remove ALL plugins from Dashlaunch before updating!
- Make sure you enter in your CPU key correctly
- Make sure you select the correct Kernel version
- Make sure you have your most recent flashdmp.bin file
- Recently I have seen a lot of topics about getting a black screen after updating.
- One of the reasons you are getting a black screen is an issue with the FCRT.bin checks
- To avoid this when updating, tick the "Disable FCRT.bin check" box (6)
[ Register or Signin to view external links. ]
- Make sure you enter in your CPU key correctly
- Make sure you select the correct Kernel version
- Make sure you have your most recent flashdmp.bin file
- Recently I have seen a lot of topics about getting a black screen after updating.
- One of the reasons you are getting a black screen is an issue with the FCRT.bin checks
- To avoid this when updating, tick the "Disable FCRT.bin check" box (6)
[ Register or Signin to view external links. ]
Credits:
*Swizzy - For obvious reasons
*Droseum20 - For previous work and releasing the Updated XeBuild GUI Download
*Hub - For explaining the FCRT.bin checks
Please feel free to leave any feedback that you might have including:
- Positive or negative feedback
- Problems you're experiencing
- Anything that you think I should add to the tutorial.
- Problems you're experiencing
- Anything that you think I should add to the tutorial.
Last edited by ATF ; edited 4 times in total
The following 5 users thanked ATF for this useful post:
Rodent (06-20-2014), oMew (06-09-2014), Reqzay (06-08-2014), nice_gamer (06-08-2014), Dekku (06-08-2014)
#2. Posted:
Status: Offline
Joined: Oct 08, 201112Year Member
Posts: 484
Reputation Power: 18
I did it by lap top with j runner and it booted by itself do I still need to do the last step because it says 16756 as updated
- 0useful
- 0not useful
#3. Posted:
Status: Offline
Joined: Mar 28, 201113Year Member
Posts: 1,897
Reputation Power: 103
You only need number 6 under step 5 if:
1. Your NAND doesn't have fcrt.bin (I think most if all phats don't have it and slims made up until 2011 (some in 2010 have it) don't have it. You can check for frct by extracting your NAND with jrunner, and will tell you if it's missing.
AND
2. When you press check kv, it says true for fcrt.bin required.
FCRT.bin is associated with a consoles drive (correct me if I am wrong), and I know for certain that consoles with the drive DG 4s 9504, don't have fcrt.bin in the NAND.
Also good tutorial by the way.
1. Your NAND doesn't have fcrt.bin (I think most if all phats don't have it and slims made up until 2011 (some in 2010 have it) don't have it. You can check for frct by extracting your NAND with jrunner, and will tell you if it's missing.
AND
2. When you press check kv, it says true for fcrt.bin required.
FCRT.bin is associated with a consoles drive (correct me if I am wrong), and I know for certain that consoles with the drive DG 4s 9504, don't have fcrt.bin in the NAND.
Also good tutorial by the way.
- 1useful
- 0not useful
#4. Posted:
Status: Offline
Joined: Dec 29, 201211Year Member
Posts: 735
Reputation Power: 29
Status: Offline
Joined: Dec 29, 201211Year Member
Posts: 735
Reputation Power: 29
When i try flashing in Xell it just stops on Fat Mount what am i doing wrong?
- 0useful
- 0not useful
#5. Posted:
Status: Offline
Joined: Apr 05, 201113Year Member
Posts: 361
Reputation Power: 17
Status: Offline
Joined: Apr 05, 201113Year Member
Posts: 361
Reputation Power: 17
SpiralUK wrote When i try flashing in Xell it just stops on Fat Mount what am i doing wrong?
Is your USB FAT32 formatted?
By any chance are you using a Hitachi drive?
- 0useful
- 0not useful
#6. Posted:
Status: Offline
Joined: Feb 19, 201113Year Member
Posts: 1,166
Reputation Power: 59
Status: Offline
Joined: Feb 19, 201113Year Member
Posts: 1,166
Reputation Power: 59
SpiralUK wrote When i try flashing in Xell it just stops on Fat Mount what am i doing wrong?
Had the same problem. Just plug out your dvd drive and boot xell. This worked for me!
Btw.. Great tutorial! Looks like it took alot time to do it!
- 1useful
- 0not useful
#7. Posted:
Status: Offline
Joined: Apr 05, 201113Year Member
Posts: 361
Reputation Power: 17
Status: Offline
Joined: Apr 05, 201113Year Member
Posts: 361
Reputation Power: 17
Stealthed wroteSpiralUK wrote When i try flashing in Xell it just stops on Fat Mount what am i doing wrong?
Had the same problem. Just plug out your dvd drive and boot xell. This worked for me!
Btw.. Great tutorial! Looks like it took alot time to do it!
Thanks Stealthed, I tried to make it very simple.
Unfortunately this doesn't work with some Hitachi drives.
Instead of opening up your console to disable the drive you could try using 360 Flash Dump Tool.
You're going to need a USB, your most recent Flashdmp.bin file, and 360 Flash Dump Tool.
Unfortunately this doesn't work with some Hitachi drives.
Instead of opening up your console to disable the drive you could try using 360 Flash Dump Tool.
You're going to need a USB, your most recent Flashdmp.bin file, and 360 Flash Dump Tool.
- Plug USB into computer
- Format your USB to FAT32
- Open 360 Flash Tool and click the "Keys" menu.
- "Keys" menu will open, enter the CPU key that goes with your Nand.
- Click on the "Open File" button. (located in the top left of Flash tool)
- Load your most recent Flashdmp.bin file, click open.
- Copy down your Region, DVD KEY, and OSIG from the bottom right hand corner
- Click Patch, You should notice a popup, Tink the box next to Patch Keyvault.
- Select the correct Region, type in your DVD KEY, and change the OSIG to "None Drive Info / Unspoofed"
- You will be prompted to save the file. Save it to your USB as updflash.bin
- Unplug USB
- Plug USB into JTAG/RGH with the console off.
- Press the Eject button on your JTAG/RGH to power on.
- If your drive doesn't open, you did it correctly.
- Xell will boot up
Note: I have not tested this as I don't own a Hitachi drive.
This is just my theory for an alternative method without having to open up your console.
If anyone can confirm this as working, please let me know and I will add it to my Tutorial.
- Format your USB to FAT32
- Open 360 Flash Tool and click the "Keys" menu.
- "Keys" menu will open, enter the CPU key that goes with your Nand.
- Click on the "Open File" button. (located in the top left of Flash tool)
- Load your most recent Flashdmp.bin file, click open.
- Copy down your Region, DVD KEY, and OSIG from the bottom right hand corner
- Click Patch, You should notice a popup, Tink the box next to Patch Keyvault.
- Select the correct Region, type in your DVD KEY, and change the OSIG to "None Drive Info / Unspoofed"
- You will be prompted to save the file. Save it to your USB as updflash.bin
- Unplug USB
- Plug USB into JTAG/RGH with the console off.
- Press the Eject button on your JTAG/RGH to power on.
- If your drive doesn't open, you did it correctly.
- Xell will boot up
Note: I have not tested this as I don't own a Hitachi drive.
This is just my theory for an alternative method without having to open up your console.
If anyone can confirm this as working, please let me know and I will add it to my Tutorial.
- 1useful
- 0not useful
#8. Posted:
Status: Offline
Joined: Jul 30, 201211Year Member
Posts: 2,396
Reputation Power: 123
Status: Offline
Joined: Jul 30, 201211Year Member
Posts: 2,396
Reputation Power: 123
Nice tut, this helped out my good friend when he updated his dash, I didn't get the black screen so I had no idea how to help him
- 1useful
- 0not useful
#9. Posted:
Status: Offline
Joined: Apr 05, 201113Year Member
Posts: 361
Reputation Power: 17
Status: Offline
Joined: Apr 05, 201113Year Member
Posts: 361
Reputation Power: 17
SRT wrote Nice tut, this helped out my good friend when he updated his dash, I didn't get the black screen so I had no idea how to help him
Thanks for the feedback
300 views and only 7 replies
- 0useful
- 0not useful
#10. Posted:
Status: Offline
Joined: Jun 07, 20149Year Member
Posts: 62
Reputation Power: 2
Status: Offline
Joined: Jun 07, 20149Year Member
Posts: 62
Reputation Power: 2
If you used jrunner u most likely will come across this problem
- 1useful
- 0not useful
You are viewing our Forum Archives. To view or take place in current topics click here.