TheNumberOne wrote that rebooter/freeb00t says that its 12611 but it has a 12625 files that by passes the checks.

but the other rebooter i got says this..

Click to View Content

__ ____ ___ ___ _____
/ _|_ __ ___ ___| __ ) / _ \ / _ \_ _|
| |_| '__/ _ \/ _ \ _ \| | | | | | || |
| _| | | __/ __/ |_) | |_| | |_| || |
|_| |_| \___|\___|____/ \___/ \___/ |_|
[v0.05 - coded by YOUYUBE.COM/GavinGaming]



I. Introduction
================

freeBOOT is a rebooter for the Microsoft Xbox 360. This version of freeBOOT
allows you to reboot into kernel 2.0.12625 on all Xenon, Zephyr, Falcon, and
Jasper consoles, which are vulnerable to the JTAG hack.

This version of freeBOOT no longer requires a second flash memory and will
thus work with all currently existing solutions.



II. Bug Fixes
=============

none



III. New Features
=================

- updated to kernel 2.0.12625

- now supports all consoles and flashing solutions (ikari)

- removed memory protections (cOz)

Code can be executed and modified anywhere in the range from 0x80000000
to 0x9FFFFFFF. This can be used to create game trainers and will allow
for porting of emulators, which rely on dynamic compilation.

- encrypted DevKit XEXes are now working (cOz)

- includes dash launch patch (cOz)

- keyvault and console signature checks have been disabled (Bliep4Ever)

- LIVE/PIRS/GOD content fully working (cOz)

- internal security breach reports deactivated (Redline99)

- easier image generation process (ikari)

- ibuild can now also generate single flash XeLL and original images (ikari)



IV. Instructions
================

In contrast to previous freeBOOT releases, the image generation process has
been made a lot easier. As prerequisites you will need an image of your
console updated to kernel 2.0.7371 and an archive "12625.zip" available
at the usual places.

1. Extract your original image

Extract your original 7371 image with the following command:

> ibuild.exe x -d temp\ -p <cpu key> -b <1bl key> .\7371.bin

2. Extract "12625.zip" archive

Extract the contents of the "12625.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. For Cygnos360, a
patched SMC can be created with their software. There's also a
collection of patched SMCs available at the usual places. Make sure
to pick the right one for your console.

For other solutions, a patched SMC can be extracted from previously
released XeLL images.

5. 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".



VII. Credits
============

Thanks a lot to [cOz] and Bliep4Ever for providing most of the new
patches in this release. Without their support, this would not have been
possible.



-----
ikari, 2010/04/13
Also To Get Online KV Unbanned!!!!!!

Thanx to Dreamer!








INSTRUCTIONS
Flash KV.
After that your fine to go online




Any Complaints - egdarkdreamer

Icy-Tank wrote To the best of my knowledge and understanding of the online "method" , that is not the correct files. There is no simple "JTAG TOOL" or "Rebooter Builder" that creates the online method for you.

As always, each individual freeBOOT needs to be encrypted for that particular NAND all while being created with the proper smc for the wiring method that you are using. I am certain that the originators know what simple coding to perform on all of the JTAG consoles, as it would really only need to be created and encrypted with the CPU key, edited, and flashed.

In short, to answer your question...No, I would not believe that it is, nor trust flashing that to my console until I was able to dissect the entire "image" that is builds and then compare it to others that I have.

I also want to reiterate what iPatobo said (Thank you by the way) that I am never going to blatantly flame someone for asking a question. By doing this, all he is doing if anything is trying to weed out fakes and potentially trying to avoid bricking his JTAG. The sale of, begging for the release of, or scam attempts of the "online method" are what get insta-flame from me.

I don't want to see ANYONE have their JTAG bricked because some **** decided it would be funny to create a image that bricks the consoles or worse...scamming people out of their money and giving them the big F U.

Hope this helps ya...

TTG_ModMenu is gay wrote failll