Hey Guys!

I've noticed that many people are begining to get screwed over by the circulation of KeyVaults with no sync. After seeing many have difficulty with this problem and a few asking for my help with their situation, I've decided to post a solution to the problem, as seek to find.

I know I'm new on the site and all but I have personal experience with this issue and have a fool proof fix.

meganfox_ttg is here to help!

What's an Un-Sync KV?

An Un-Sync KV is a KeyVault with no sync involved. This basically means that once you flash this KV to your nand, your controller won't sync to your box. This has caused many people huge problems as people don't know how to do anything with their nand without Flash 360. Some non-experienced modders will even assume their JTAG is broken after they flash a KV with no sync and end up selling their JTAG for next to nothing because they think it's broken. The people who are smart enough to think for a minute or two sometimes guess that it might be bad flash, then are stumped because they can't get to XeXMenu nor use Flash 360 to flash a good NAND to their console. I'm going to lay out an easy-to-follow TuT on how to fix this problem with good old fashioned, Xellous!

As many of you have probably forgotten as the uasge and popularity of Flash 360 has risen, updflash NAND can be easily flashed through Xellous and auto-detected aswell. You can probably guess the fix to this problem at this point.

Step 1: Identifying Bad Flash

Don't mistake this fix as a solution to ALL bad flash types. This fix only works with a no sync KV bad flash, and where the only true problem with the console is the controller attachment. If your console simply won't turn on or has some other error message, don't expect an easy flash in Xellous to be the solution to your nightmare.

Step 2: Identify if you have Currently Installed Xell or Xellous (they are NOT the same!)

I'm not going to define each aspect of Xell and Xellous so you can determine which one is installed on your console. Here is the one hint I will give you. If you boot Xellous if will run through a reboot and at the end it will show something like this:

CPU Key: ************************
DVD Key: ************************

If you have any trouble identifying your Xell or Xellous, contact me on AIM or PM me and I'd be happy to help you out.

Step 3: Getting a Good Flash Prepared

If your a prepared guy or even if your lazy you will probably have either a back-up KV or a banned KV lying around your desktop somewhere that you forgot to delete. If so, then its your lucky day, you don't have to go searching for an old KV download link or a banned KV from somebody... it's just a waste of time. Anyway, get the banned or back-up keyvault and import into your flashdmp.bin NAND file extracted from your console as if you usually when flashing a KV. Then patch the keyvault and save as updflash.bin like normal. Put that updflash on the ROOT of your USB drive, and your set to go!

Step 4: Flashing with Xellous

Next, your going to plug the USB drive, with updflash NAND on the ROOT of it, into your console. Then boot up Xellous by clicking the eject button on the DVD drive. Watch as your blue television screen does the work for you! It will begin reading the updflash on your USB drive about 20 seconds into the boot, after giving you a 15 second countdown warning for you not to update, ignore it. Reading the NAND off of the USB takes about 2 minutes. Then, if done correctly, it should automatically start flashing the NAND to your console. Once completed it will tell you to shut down Xellous and reboot your console.

Step 5: Ta-Da!

You have successfully reflashed with Xellous and your JTAG is set to go! Your broken JTAG nightmare is over.

*Sorry I couldn't include pictures to help guide you guys. I wrote this up real quick, and I'm too tired tonight. I might be able to add pictures into the post tommorrow or whenever I get spare time*

- I put a lot of work into this TuT so if it helps, hit the +rep please!