BGAMods
VIP Member
xb1 games on jtag 360
- Thread starter Hackerjac
- Start date
Hello
I have the EXACT same problem with the xbox logo displaying, but then freezes and game doesn't load. I didn't jtag my 360 so unable to connect to PC and therefore unable to use Jtag Tool 1.74. The only option I have to flash (as far as I know) is to flash via flash360.
Using freeBoot Toolbox Maker v2.4, I create my image. This app doesn't have the option to choice between mem edit or xbox1 emu, but I've recently read that it incorporates both (although not sure about that somehow).
Flashed, tried to load a xbox games, but now have the problem where by the 360 shuts itself off.
Please help. How can I create a suitable freeboot image with mem edit, ready for me to flash via flash360 please?
I have the EXACT same problem with the xbox logo displaying, but then freezes and game doesn't load. I didn't jtag my 360 so unable to connect to PC and therefore unable to use Jtag Tool 1.74. The only option I have to flash (as far as I know) is to flash via flash360.
Using freeBoot Toolbox Maker v2.4, I create my image. This app doesn't have the option to choice between mem edit or xbox1 emu, but I've recently read that it incorporates both (although not sure about that somehow).
Flashed, tried to load a xbox games, but now have the problem where by the 360 shuts itself off.
Please help. How can I create a suitable freeboot image with mem edit, ready for me to flash via flash360 please?
If your Xbox360 isn't connected to your PC, you can still use Jtag Tool. Just create the freeboot file from within Jtag Tool using your original NAND dump and CPU Key. After that, just skip the "writing freeboot to your NAND through Jtag Tool" step, and instead install the created freeboot file using Flash360.
Its just as easy as that...
I did try that but jtag tool gives error message....
"Unhandled exception has occurred in your application.
Could not find file 'bin\XB1\jasper 256.bin"
I can confirm I have my CPU key and original nand (66MB). Where am I going wrong please?
"Unhandled exception has occurred in your application.
Could not find file 'bin\XB1\jasper 256.bin"
I can confirm I have my CPU key and original nand (66MB). Where am I going wrong please?
You didn't mention it before that you had 256MB NAND. Currently, the Jtag Tool has a bug in it due to which it gives this error while making the freeboot file for 256/512MB NANDs.
The next version of Jtag Tool is on its way and should be released soon. YOu can then try to make the freeboot file for your Xbox360. Alternatively, you can manually create the freeboot file yourself. There are many tutorials on how to create freeboot manually if you opt for doing it yourself. Just search for them.
Ok thank you. Can you point me in the right direction for the manual creation please? I've searched but can only find tuts on freeboot tool maker etc.
Here, just copied it from big_ted's tutorial.
========================
!!HERE for freeboot!!
Making the freeboot dash.
we now have a full dump, cpu key info, key vault. we are now ready to make the new updated dash.
first off open up 360 dump flash tool, put in your cpu key from the text file or the one you have written down, open up you dump and now the text on the right will now give you cpu key dvd key serial etc. If it is there click the bad block box and note the bad blocks in the dump (this is not visible if there are no bad blocks)
TNOw to make the free style dash we need
dump.bin
9199.zip
freeboot 0.032
First extract free boot to freeboot directory inside this should be 3 folders (bin data temp,ibuild) and readme, you will need to find and put a copy of libeay32.dll in there too, put a copy of you dump.bin in there too. you'll need to google for the 1bl key.
1. Extract your original image
Extract your original 7371 [recommended but not necessary] image with the following command:
ibuild.exe x -d temp\ -p [cpu key] -b [1bl key] dump.bin (dont include the square brakets)
2. Extract "9199.zip" archive
Extract the contents of the "9199.zip" archive into the "data"
directory.
3. Copy these files from "temp" to "data" directory
- crl.bin
- crl.bin.meta
- extended.bin
- extended.bin.meta
- kv.bin
- odd.bin
- odd.bin.meta
- secdata.bin
- secdata.bin.meta
- smc_config.bin
4. Patch SMC
Put a patched "smc.bin" in the "data" directory. The easy way to grab this is to grab a copy of xbr for your console rev, open it in flash tool and extract the xbr, you need the smc enc.bin (encrypted) not smcenc.bin rename it to smc.bin and put it in the data folder.
If you are using one of the new smc by blackaddr (bug fix new ports) (here http://www.xboxhacker.org/index.php?topic=15254.0) now is a good time to put it in your build, as it is encrypted with the rest of your build.
5. Choose your patches in the "bin" directory there are 2 directories:
"patches [full mem editing]" and "patches [xb1 compatibility]".
If you want xbox1 emu use "patches [xb1 compatibility]",
if you want to be able to have full memory access use the other.
6. Create the freeBOOT image
Finally, create your freeBOOT image with this command:
ibuild.exe c freeBOOT -c [console] -d data\ -p [cpu key]
-b [1bl key] bin\image.bin bin\fuses.bin
Replace [console] with either "xenon", "zephyr", "falcon", "jasper",
"jasper256" or "jasper512" [without quotes] and square brackets
example
ibuild.exe c freeBOOT -c Xenon -d data\ -p 123456789012345678 -b 1234123412341234 bin\image.bin bin\fuses.bin
You will now be gifted with two new files in the bin folder
one called image.bin and one called fuses.bin, the fuses is the details of keys etc we already have this to be able to get this far so ignore it.
we need to flash the image.bin to the console.
========================
Just follow the above steps until you create the freeboot file i.e. image.bin.
After that just rename it, and use the Flash360 to write it to your NAND, and there you have your freeboot installed just like you want it to be
I know the tutorial is a little rough, but I think it will suffice in your case.
Last edited:
Opps. Just came back to advise I had found a vid tut. Thanks anyways and all done now and xbox 1 games working!
However, xexmenu now hard resets 360 without a USB plugged in? I have already deleted the 'unknown xbox game' save which caused xexmenu to not boot (black screen) before, but this hard reset is new to me and not heard of this problem before? Any ideas?
However, xexmenu now hard resets 360 without a USB plugged in? I have already deleted the 'unknown xbox game' save which caused xexmenu to not boot (black screen) before, but this hard reset is new to me and not heard of this problem before? Any ideas?
Great you got it working.Opps. Just came back to advise I had found a vid tut. Thanks anyways and all done now and xbox 1 games working!
However, xexmenu now hard resets 360 without a USB plugged in? I have already deleted the 'unknown xbox game' save which caused xexmenu to not boot (black screen) before, but this hard reset is new to me and not heard of this problem before? Any ideas?
Sorry, can't help you with the hard reset problem. It never happened with me, so I can't advice you in this matter.
I also have this problem! When i put my HDD with modified Xbox 1 emulator files into an NON-Jtagged xbox, xbox 1 games do work. In mine, the Jtagged console, they don't. So i think it has something to do with the Nand flash?
Like it has been mentioned in this thread, for playing Xbox1 games you need to patch freeboot with Xbox1 compatibility patch, then flash it to your NAND. After that, your Xbox360 will play Xbox1 games.
Since many users here have used Jtag Tool to make and flash freeboot, it was found that the Jtag Tool has a bug. Read this post about the bug: http://www.team-xecuter.com/forums/showpost.php?p=277821&postcount=26
So, after you create the new freeboot file, flash it to your NAND. After that your Xbox1 games should work fine as long as the emulator files are present on the HDD.
Full Memory Access means that you get full privileged access to Xbox360 RAM and then can use it for applying Mods etc.
Last edited:
I'm getting this error on Jtag Tool 1.74 - Could not find file 'bin\XB1\jasper512.bin'
Everything else went to plan but this jasper 512.bin doesn't seem to be in the program folders,it's only got one named jasper.bin.
Can someone please help or point me in the right direction.
I've searched and read that much info my head is spinning ?
The Jasper 512mb has been out for ages,so surely this isn't a fault with Jtag tool 1.74?
All help greatfully accepted and appreciated.
Everything else went to plan but this jasper 512.bin doesn't seem to be in the program folders,it's only got one named jasper.bin.
Can someone please help or point me in the right direction.
I've searched and read that much info my head is spinning ?
The Jasper 512mb has been out for ages,so surely this isn't a fault with Jtag tool 1.74?
All help greatfully accepted and appreciated.
This is a bug which is present in the current version of Jtag Tool and will probably be fixed in the next version.
So, what you should do is to use Freeboot Toolbox instead to make the freeboot image for your console, then use Jtag Tool to write it to your NAND.
Here's a link for download Freeboot Toolbox: http://www.bestpig.fr/files/freeBOOT_ToolBox_Maker24.exe
Thanks for that info,I was dreading the thought of having to use DOS programs .
I'm glad it was a fault with the program and not something I was doing wrong.
There is so much old and useless information on a lot of the sites,it's good to be able to ask a question here and get a fast reply,my hat goes off to you.
This is my first Jtag and drive flash ,should I just keep a copy of my CPU key and my DVD key in case it's needed in the future,or is there something else I need to keep?
I selected XB1 compatibility instead of Mem Editing in Jtag Tool,was this the right choice to make?
Thanks again champ.
.I'm glad it was a fault with the program and not something I was doing wrong.
There is so much old and useless information on a lot of the sites,it's good to be able to ask a question here and get a fast reply,my hat goes off to you.
This is my first Jtag and drive flash ,should I just keep a copy of my CPU key and my DVD key in case it's needed in the future,or is there something else I need to keep?
I selected XB1 compatibility instead of Mem Editing in Jtag Tool,was this the right choice to make?
Thanks again champ.
BGAMods
VIP Member
what i personally do is keep a copy of everything that is dumped off the 360. i also keep a notepad file with my cpu and dvd key. its better to have and not need than need and not have.
Yes, you should always keep a copy of CPU and DVD Keys. You should send yourself an email with these attached so you never lose these.Thanks for that info,I was dreading the thought of having to use DOS programs
I'm glad it was a fault with the program and not something I was doing wrong.
There is so much old and useless information on a lot of the sites,it's good to be able to ask a question here and get a fast reply,my hat goes off to you.
This is my first Jtag and drive flash ,should I just keep a copy of my CPU key and my DVD key in case it's needed in the future,or is there something else I need to keep?
I selected XB1 compatibility instead of Mem Editing in Jtag Tool,was this the right choice to make?
Thanks again champ.
Alongwith this, you should also keep a backup of your original NAND dump, so that if anything goes wrong with your JTAG, you could use it to get your Xbox360 back to normal.
Cheers for the info, I had the same problem. I can now get xbox1 games to load.
Ive only tried a few so far. Has anyone ever got Forza Motorsport 1 to load? Ive tried it from both Disk & HDD & no go! I cudnt get it to load on my normal (non jtag) system either.
If anyone has got it to work, please let me know, as I'd love to try it out.
Cheers