Go to Datel's website and download their XPORT360 software. It comes with a driver for the memory card and an browser program.

Even the XBR authors mentioned that it was put together quick to make people without cygnus be able to use a rebooter on their boxes and is in no way an permanent solution. Why would you panic about other people creating odd rumors just because they're doing things wrong and are not satisfied with freeboot ?
Freeboot is harder to setup but it surely works better.

DON'T USE THE INTERNAL MEMORY UNIT

Edit:
http://www.xboxhacker.org/index.php?topic=14039.0  <- read this for more details.

Just set the temps for 060ｰC;060ｰC;065ｰC  -  080ｰC;080ｰC;082ｰC. It might be a bit loud, but it's not so loud as it was keeping 100% fans all the time and make sure it will never get past 65C.

Another advantage is that the fans keep the temperature constant, causing less mechanical damage due to temperature fluctuations when the GPU processing load changes too frequently.

Just don't mind the noise and the system will last much longer than it would even with the fans at 100% all the time because then at 100% the temperature would still float from 45C to 60C all the time.

To keep an axis on the center, the controller expect that the voltage on the middle pin of the axis potentiometer be exactly 50% of the main power voltage. I just put 2 resistors of the same value on each hole:


[GND]----|1k|----[Middle]----|1k|----[+3.3v]

Does it throw that "Update failed" error right away when you try to update ?  Is there any possibility that the unit has JTAG and is flashed with XBR ?

An older console with R6T3 removed does that if you try to update. The updater tries to write the CB only after it blew the fuse. If it can't blow the fuse it toss a error screen with an "Try again later" message.

Do you realize that errors like "0020" E08 and "0022" E10 are quite generic ?
Basically E08 (0020) means the GPU did not start up and reply to the Southbridge that it started. Could be everything from hardware fault to badly corrupted/erased boot blocks.

E10 (0022) means the thing started to boot but stopped somewhere in the middle, before it could start the screen. Basically the two error codes can be anything related with the GPU/CPU/Flash. 

You had blocks with messed up ECC when you re-flashed FreeBOOT. Erasing then re-flashing would be enough. But you flashed back the original for testing, which is a good idea if you have time to spare.

I  think it bricked the first time due to MU corruption. And I suggest you to read the thread about how to disable (delete the partition) the internal MU.

For fighting games is the best thing one can get. If you see the official SF4 pad from Capcom it's based on Saturn's pad (button placement, etc)

The point here was reuse the circuit I made that allows me to use the pad with Arcade boards.

Sorry about necro-posting but I finished this project and forgot to post the results:



Picture contains:

Play&Charge cable
XBOX360 wireless controller with all mechanical components removed (resistors added to set triggers and analog buttons as not activated/centered)
SEGA Saturn to JAMMA controller adapter board (demultiplexes the Saturn controller and latches the button signals so no hacking is done to the Saturn controller)
1994 SEGA Saturn Japanese BEIGE controller.

Turns out that I reverse engineered the battery to use with this idea but I gave up of using it because I used the Saturn controller and TTL chips I am obligated to draw 5V from the XBOX360 USB port through the Play&Charge cable.

It works pretty good with SF4/SSF4 with just 2 button changed.

I don't think there's issues with Freeboot. I've done so many consoles with 0.32 and not a single one failed of software issues yet (some did of hardware issues though).
Freeboot is closer to a unpatched retail console than XBR so it has much less issues. Still anyone with Jasper consoles with internal MU should refrain from using it as these units STILL corrupt with Freeboot and 9199 dash.

Jasper 256 was working fine with freeboot now it doesnt boot (no vid/audio)

http://www.xboxhacker.org/index.php?topic=14039.0  <- read this please.

If this issue happens for you, you will get absolutely no video, no 3RED, no green lights, just an solid green on the power led.

For LT and RT, it depends on the type of controller you have. The matrix controller has the  LT/RT controller voltage lower when the keys are pressed.
For the non matrix controller(I am talking about wireless ones, I don't have an wired to check for you) the voltage raises when the key is pressed.

So we get something like this:



But then if you leave the trigger mechanism in place, you just need to solder the wires.

Also if you feel like you want to remove the analogs (to perhaps fix another controller you're keeping normal) you can if you do this circuit 4 times:

Use 360 Flash Tool to edit the fan speed with, for example your original dump.  After you save the edited image, re-open it on flash tool and extract the config block. Edit it so it's in the 16KB format ibuild want it to be (cut off the first 16KB) or use this nandpro command to dump the config block for ibuild:  (I am assuming it's an 16 MB dump)


I no longer use 100% speed all the time. Currently I am using an target temperature of 60C (Celsius, as we need to be scientific here, ok ?) and the box keep the fans at 70% most of the time (If I pop in that Gears of War1 or 2 disc it does 100% after a while so I believe it's going good).

Also I changed the "danger" temps from 100/100/117 to 080/080/087 so if it gets that hot it will just shut down and show the 2 lights.

Ah and regarding the changing of KV, the only consoles that one can edit the KV is the old Xenons, so that's why changing the KV works for some people but not for everybody.

lol if you keep doing that you're going to ruin it. 

Probably it has an outdated version of the xbox rebooter(XBR), which causes that bug on certain games.

You need to STUDY how the hack works before doing anything with your console or else you will end with an useless piece of scrap in the end.

More like "it doesn't matter where they are, the SMC knows where to find them". 

The original phrase did sound a bit confusing as make people think the nand itself which "remaps" blocks, which is not true. The Southbridge CPU (SMC) that does this "remapping" work.

People should just stop messing with the damn keyvault....   

A GREAT hint of what is going sour is check the XCODE with XVAL or 360 flash tool 0.94 decrypt x-code function.

Anyway STOP editing the keyvault. THAT DOES NOT WORK PERIOD. 

Anyway, the official SONY unbrick card uses their Magic Gate protection crap, so the dump only works on the exact same card it came from.
I don't know if the XBOX360 has locking mechanisms in the kernel to bind the files with an certain device.

I know that they can do it, but I think it's up to the code on the game or app XEX file to do the checking.
On Sony stuff, these checks are made by the system and the file is only booted if the DRM is accepted as valid.

And the OP mentions that copying the files made another card work like the first.  One thing I say, even if the files are useless, it could show us how to use the booting mechanism from memory units and maybe make "emulator cartridges" for JTAGs with the idea lol

for reference, if you're curious about the design, it's called "flip chip". Put that on Google and have fun reading.

ok people FAIL to understand what is happening, I'll waste a little more english to explain what's going on.

On old consoles (Xenon pre 2007 units) there were nothing like KK exploit. So MS felt that CPU encryption and HMAC was enough to keep the device certificates secure.
KK exploit happened and people started to look how things were laid down internally on the XBOX360 software.
After that people figured out how to decrypt the keyvault and which part made what. This was when people started to play around with region changing.

As it's aways in defensive, MS added a new protection which hashes the *DECRYPTED* keyvault with the CPU key, making it impossible to be modified and useless on anything but the CPU it is "married" with. First consoles with this were the then brand new Zephyr units.

We didn't knew about that because then Zephyrs and Falcons were unhackable (no KK exploit were possible on them). XELL and finally the rebooter comes.

People hit the new keyvault protection.  Pointless threads pop here and there. 

Do you understand why you can't change the region now ? They're hashed the decrypted contents of the keyvalt so it's checked multiple times now. If hash fails the unit throws you "christmas lights" on the ring of light and log an "keyvault policy violation" event. That's what makes the profiles corrupt as the console now behaves like an banned console.