Best way of soldering DB1F1
- Thread starter kerman80
- Start date
i understand Nand Pro 2.0e is the appropiate tool for reading/writing the nand. But once I got the CPUKey, should I inject it with Nand Pro too, to create freeBOOT image, or with freeBOOT ToolBox v2.4
Please, notice im just talking about creating freeBOOT image once I got CPUKey, not reading/writing/updating NAND.
Do they both work fine on w7 x64 systems?
Please, notice im just talking about creating freeBOOT image once I got CPUKey, not reading/writing/updating NAND.
Do they both work fine on w7 x64 systems?
Last edited:
Where do you want to inject the CPU Key to? Once you have the CPU Key, what you have to do is to create a freeboot image either manually or by using a program such as Jtag Tool or freeBOOT ToolBox. Then write the freeboot image to the NAND using NandPro.
Sorry, I thought CPUKey had to be injected to create freeBOOT image, the same way Keyvault and configblocks to CBR.
Also, I was told previously (or at least I misunderstanded) no freeBOOT ToolBox would be needed in the whole process in order to install freeBOOT, as long as I used Nand Pro.
Also, I was told previously (or at least I misunderstanded) no freeBOOT ToolBox would be needed in the whole process in order to install freeBOOT, as long as I used Nand Pro.
Last edited:
I think the person who told you this, meant Command Prompt instead of NandPro, because NandPro needs to be used through Command Prompt and the process of making a freeboot image manually also involves the use of Command Prompt.
Isnt there a gui for the nandpro, so you can create freeBOOT image with CPUKey with no need of command prompt?
Yes there is. Although I have never tried it personally, but it should work fine. Its called Easy freeBOOT. More info here: http://www.xbox-scene.com/xbox1data/sep/EkZEypEluZtumtFiNY.php
So, the conclusions are,
1- With CPUKey I can create manually freeBOOt image with the use of Nand Pro, which uses Command Prompt.
2- If I go with the traditional JTAG installation (no solders at the bootom of the MB), theres no need to patch anything with SMC, right?
1- With CPUKey I can create manually freeBOOt image with the use of Nand Pro, which uses Command Prompt.
2- If I go with the traditional JTAG installation (no solders at the bootom of the MB), theres no need to patch anything with SMC, right?
When you create a freeBOOT image manually, it will always require an SMC file which is either patched with default SMC points for JTAG or patched with non-default SMC points for JTAG.
You can get a SMC with default JTAG points by extracting the SMC out of XeLL or XBR. Then you can use it while making freeBOOT. Or you can edit the default SMC file first and then use the modified SMC file while making the freeBOOT image.
Thanks for your clear explanation. Everything about freeBOOT and SMC has been absolutely cleared out for me.
But just out of curiosity, is it correct to state, that is possible to create the freeBOOT -using the proper SMC file and CPUKey of course- with the Nand Pro (through command prompt)?
But just out of curiosity, is it correct to state, that is possible to create the freeBOOT -using the proper SMC file and CPUKey of course- with the Nand Pro (through command prompt)?
Last edited:
Making a freeBOOT image has actually nothing to do with NandPro. A freeBOOT image is made using a a program named "ibuild" which is included with the freeBOOT package you get from Xbins.
The only thing common between NandPro and ibuild is that Command Prompt is needed to use them both. Nothing else.
The basic function NandPro is to read/write the Xbox360 NAND. Additionally, you can use it read/write bad bad blocks etc. That's all. It shouldn't be complicated with the process of making a freeBOOT image as it literally has nothing to do with it.
I hope this clears everything out for you
Well, maybe NandPro theres nothing to do with creating freeBOOT image, but is not all about read/write NAND, since it can do other things, like injecting keyvault and configblocks to create XBR image. I.e,
nandpro xbr_8955.bin: -w16 rawkv.bin 1 1
nandpro xbr_8955.bin: -w16 rawconfig.bin 3de 2
Again, OK theres nothing to do with freeBOOT image, thats cleared out. But not just read/write NAND. The point of NandPro being able to use as a tool for injecting that values for creating XBR image, just lead me to think it may be useful too for freeBOOT image.
Thanks again
Last edited:
When I mentioned in my previous post that NandPro can be used to read/write bad blocks etc, I actually included the injecting kv bit into the "etc"Well, maybe NandPro theres nothing to do with creating freeBOOT image, but is not all about read/write NAND, since it can do other things, like injecting keyvault and configblocks to create XBR image. I.e,
nandpro xbr_8955.bin: -w16 rawkv.bin 1 1
nandpro xbr_8955.bin: -w16 rawconfig.bin 3de 2
Again, OK theres nothing to do with freeBOOT image, thats cleared out. But not just read/write NAND. The point of NandPro being able to use as a tool for injecting that values for creating XBR image, just lead me to think it may be useful too for freeBOOT image.
Thanks again
.Anyways, how's the freeBOOT image coming?