You are viewing our Forum Archives. To view or take place in current topics click here.
How to flash a kv to the NAND correctly
Posted:
How to flash a kv to the NAND correctlyPosted:
Status: Offline
Joined: Mar 28, 201113Year Member
Posts: 1,897
Reputation Power: 103
NOTE: I posted this on another forum, so this is actually my own work. Also some people will be aware that you don't need Xebuild to flash kvs to the nand, but i like to use it anyway. In addition I will adding pictures and possibly a video tutorial soon, however i am too busy to add that at the moment..
I prefer to flash my kvs to the NAND as it stops any idiot stealing them with a tool/plugin. Recently i have seen people having issues with flashing kvs to the nand, so i am going to make a tutorial.
How to flash a kv to the NAND tutorial:
1. Dump your original nand using flash 360 on the console. To do this, download these files, and put them on a USB stick, which you then insert into the console.
[ Register or Signin to view external links. ]
Load the xex file with xexmenu or freestyle dash, and follow the on screen instructions to dump your nand.
2. Move the flashdmp.bin on your USB stick to your desktop, and copy to a folder named backup on the desktop aswell.
3. Download 360 flash tool and open it.
[ Register or Signin to view external links. ]
4. Upon first opening it will you give a screen regarding CPUkeys. Firstly tick XEX 1 at the top, then tick CPUkey. Then enter your cpukey for your console (can be found by booting console into xell with eject button). Then click add cpukey, and the key will move into the multiple cpukeys box. Then click ok.
5. Click ... under open file, and select the flashdmp.bin on the desktop.
6. Copy your DVDkey, OSIG and region on the right, into a notepad.
7. Click import on the bottom left. Then tick key vault. Next click ... to the right of the key vault box, and select your new, unbanned kv.bin (or kv_dec.bin). (Make sure the KV is the right type for your console (e.g type 1 or 2), and matches your console version (e.g. slim or phat) - if it is not a phat/slim, then use the kv converter on this forum). Then click ok.
8. Now save the updated nand to a folder called updatednand on the desktop and call the file flashdmp.bin
9. Close 360 Flash tool. Download and open jrunner. This has more drives available than 360 flash tool, so is better for patching the kv.
[ Register or Signin to view external links. ]
10. On Jrunner, click load source on the left. Select flashdmp.bin in the folder updatednand. Then type your cpukey in the cpukey box (can be found in xell).
11. Click advanced > Patch Nand, then tick patch key vault. Now from the notepad created earlier, change the region, dvdkey and osig, so that they match what is in the notepad. You may not need to change the osig or region, if they already match. Also leave the serial and console id alone. Then click ok.
12. Now navigate to the jrunner folder, and go to the output folder. Your updated nand will be here. In the updatednand folder on your desktop, delete flashdmp.bin, then move the file in the output folder of jrunner into the updatednand folder.
13. Many people think they are ready to flash the kv now, but they are wrong. One more thing needs to be checked and it is best to rebuild the nand with xebuild. Download and open Xebuild:
[ Register or Signin to view external links. ]
14. Click open near the top, and select the nand file in the updatednand folder. Now click save, and make a new folder on the desktop called FINALNAND, and select this as the directory to save to.
15. Enter your CPUkey in the CPUKey box (can be found in xell). Then click check KV in the bottom right. If Requires FCRT.bin is true, then tick Disable FCRT.bin check under special patches. If this is not done, then your console does not boot or boots with a black screen. If Requires FCRT.bin is false, then you don't need to do anything.
16. Check that the kernel version is 2.0.16756.0 on the left. Now click generate hacked image, and wait for it to complete.
17. Once completed a file called updflash.bin will be created in the folder called FINALNAND on your desktop. Put the file updflash.bin on the root of a USB stick, and insert the USB stick into your console.
18. Power on your console with the eject button to boot into xell. Wait for it to find the USB with the updflash.bin on it. Once found, it will wait around 30 to 60 seconds before flashing it. It will tell you when it is complete.
19. When it says 'image written', turn of the console by the power button. Then unplug the console from the power supply for 30 to 60 seconds (to allow the chip to cool and SMC data to reset).
20. After 30 to 60 seconds is up, plug the console back in and boot normally, and your console should boot as it normally does - with the new kv.
I have flashed many kvs to the nand, and had boot problems and black screens on several occasions. I managed to fix these problems, to come up with the method above. Ever since, I have used the method above, I have had no boot issues or black screens. The method above is my own work and is not copy and pasted from elsewhere.
If you have any questions or issues, i am more than willing to help.
Thanks.
Last edited by Hub ; edited 1 time in total
I prefer to flash my kvs to the NAND as it stops any idiot stealing them with a tool/plugin. Recently i have seen people having issues with flashing kvs to the nand, so i am going to make a tutorial.
How to flash a kv to the NAND tutorial:
1. Dump your original nand using flash 360 on the console. To do this, download these files, and put them on a USB stick, which you then insert into the console.
[ Register or Signin to view external links. ]
Load the xex file with xexmenu or freestyle dash, and follow the on screen instructions to dump your nand.
2. Move the flashdmp.bin on your USB stick to your desktop, and copy to a folder named backup on the desktop aswell.
3. Download 360 flash tool and open it.
[ Register or Signin to view external links. ]
4. Upon first opening it will you give a screen regarding CPUkeys. Firstly tick XEX 1 at the top, then tick CPUkey. Then enter your cpukey for your console (can be found by booting console into xell with eject button). Then click add cpukey, and the key will move into the multiple cpukeys box. Then click ok.
5. Click ... under open file, and select the flashdmp.bin on the desktop.
6. Copy your DVDkey, OSIG and region on the right, into a notepad.
7. Click import on the bottom left. Then tick key vault. Next click ... to the right of the key vault box, and select your new, unbanned kv.bin (or kv_dec.bin). (Make sure the KV is the right type for your console (e.g type 1 or 2), and matches your console version (e.g. slim or phat) - if it is not a phat/slim, then use the kv converter on this forum). Then click ok.
8. Now save the updated nand to a folder called updatednand on the desktop and call the file flashdmp.bin
9. Close 360 Flash tool. Download and open jrunner. This has more drives available than 360 flash tool, so is better for patching the kv.
[ Register or Signin to view external links. ]
10. On Jrunner, click load source on the left. Select flashdmp.bin in the folder updatednand. Then type your cpukey in the cpukey box (can be found in xell).
11. Click advanced > Patch Nand, then tick patch key vault. Now from the notepad created earlier, change the region, dvdkey and osig, so that they match what is in the notepad. You may not need to change the osig or region, if they already match. Also leave the serial and console id alone. Then click ok.
12. Now navigate to the jrunner folder, and go to the output folder. Your updated nand will be here. In the updatednand folder on your desktop, delete flashdmp.bin, then move the file in the output folder of jrunner into the updatednand folder.
13. Many people think they are ready to flash the kv now, but they are wrong. One more thing needs to be checked and it is best to rebuild the nand with xebuild. Download and open Xebuild:
[ Register or Signin to view external links. ]
14. Click open near the top, and select the nand file in the updatednand folder. Now click save, and make a new folder on the desktop called FINALNAND, and select this as the directory to save to.
15. Enter your CPUkey in the CPUKey box (can be found in xell). Then click check KV in the bottom right. If Requires FCRT.bin is true, then tick Disable FCRT.bin check under special patches. If this is not done, then your console does not boot or boots with a black screen. If Requires FCRT.bin is false, then you don't need to do anything.
16. Check that the kernel version is 2.0.16756.0 on the left. Now click generate hacked image, and wait for it to complete.
17. Once completed a file called updflash.bin will be created in the folder called FINALNAND on your desktop. Put the file updflash.bin on the root of a USB stick, and insert the USB stick into your console.
18. Power on your console with the eject button to boot into xell. Wait for it to find the USB with the updflash.bin on it. Once found, it will wait around 30 to 60 seconds before flashing it. It will tell you when it is complete.
19. When it says 'image written', turn of the console by the power button. Then unplug the console from the power supply for 30 to 60 seconds (to allow the chip to cool and SMC data to reset).
20. After 30 to 60 seconds is up, plug the console back in and boot normally, and your console should boot as it normally does - with the new kv.
I have flashed many kvs to the nand, and had boot problems and black screens on several occasions. I managed to fix these problems, to come up with the method above. Ever since, I have used the method above, I have had no boot issues or black screens. The method above is my own work and is not copy and pasted from elsewhere.
If you have any questions or issues, i am more than willing to help.
Thanks.
Last edited by Hub ; edited 1 time in total
The following 3 users thanked Hub for this useful post:
#2. Posted:
Status: Offline
Joined: Jul 19, 201113Year Member
Posts: 2,037
Reputation Power: 1150
Status: Offline
Joined: Jul 19, 201113Year Member
Posts: 2,037
Reputation Power: 1150
Great Tut, thanks man
- 1useful
- 0not useful
#3. Posted:
Status: Offline
Joined: Oct 08, 201113Year Member
Posts: 484
Reputation Power: 18
Can u help me with xblse thanks
- 0useful
- 1not useful
#4. Posted:
Status: Offline
Joined: Mar 28, 201113Year Member
Posts: 1,897
Reputation Power: 103
varr13 wrote Can u help me with xblse thanks
Sure, what do you need help with?
- 0useful
- 0not useful
#5. Posted:
Status: Offline
Joined: Oct 08, 201113Year Member
Posts: 484
Reputation Power: 18
The xblse menu won't pop up I put them in the right place I belive
- 0useful
- 0not useful
#6. Posted:
Status: Offline
Joined: Oct 08, 201113Year Member
Posts: 484
Reputation Power: 18
#7. Posted:
Status: Offline
Joined: Mar 28, 201113Year Member
Posts: 1,897
Reputation Power: 103
varr13 wrote The xblse menu won't pop up I put them in the right place I belive
Verify you have done all these steps:
1. Put XBDM.xex and XBLstealth.xex on your internal hdd (move from usb to hdd with xexmenu)
2. Put XBDM.xex as plugin 1 in dashlaunch. Get the latest XBLStealth.xex and put this a plugin 2. Do not have any other plugins for now.
3. Press rb on the controller and press x on hdd1.
4. Exit dashlaunch and reboot console.
5. You should get a message from XBLSE saying it is rebooting to finalize, let it do so.
6. Once rebooted, connect your RGH/JTAG to internet by ethernet or wifi.
7. Reboot console again, and this time the menu should come up.
If it doesn't come up, then it could be:
a) Your internet connection is poor, try resetting your router
b) Your kv is banned, get a new one
c) Unlikely, but your nand has issues, so reflash it
- 1useful
- 0not useful
#8. Posted:
Status: Offline
Joined: Jan 31, 201212Year Member
Posts: 1,770
Reputation Power: 81
Overall this is complex. Some people might mess up when doing this if their a beginner but for people that have experience it's kinda big and easy to understand.
- 1useful
- 0not useful
#9. Posted:
Status: Offline
Joined: Oct 08, 201113Year Member
Posts: 484
Reputation Power: 18
My dash launch freezes when I press a plugin how to fix
- 0useful
- 0not useful
#10. 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
varr13 wrote My dash launch freezes when I press a plugin how to fix
Give it some time, about 20-30 seconds.
- 0useful
- 0not useful
You are viewing our Forum Archives. To view or take place in current topics click here.