Not that I know of, but I haven't even looked into the scene in over half a year. SI is actually the founder of the site, but he hasn't been around in years. Xantium from X-S is running the server this runs on, but he didn't respond when I tried to contact him ages ago about the forum being down.

No idea what happened. I don't have server-side access, I didn't even realize it was back until someone sent me a PM on here.

Wow, what a useful first post in a thread that is over a year old.
And for your helpful post, I will stick my boot all the way up your ass. Yay.

That's a generic capacitor, any electronics shop on- or offline will have that.

No. The NAND Flasher uses the 360 southbridge to actually interface with the chip (nand is not SPI normally).

You're f***ed on this one. You overwrote the security data that identifies it as a "real" 360 HDD. The only way to use it at all anymore is to RGH your console, but then you can forget about ever going on live.

It makes no difference, a modification can be detected as soon as you connect.

No.

You can't install an update to files that are not there. You NEED the BC files from an original HDD, any original HDD, and copy them to partition 2.

This topic has been moved to Junkyard/Sewer/Dumpster/Landfill.

http://www.xboxhacker.org/index.php?topic=18032.0

Asking the same question in several places will not get you an answer faster, but will get me annoyed.

You apparently didn't read very much. You have to install a glitch chip to load xell, there is no other way. If you don't want to mod the console, you are out of luck, end of story.

You wiped the security sector. The security sector is signed and contains drive specific data. Unless it happens to be a WD HD, you have no way to save it.

Not to mention that loading times go to hell due to the wrong file order on the disk. Plus, most games exceed the space of a dvd-5 these days.

Usually there's variations in the logic boards that will prevent it from working at all or at least well with the "wrong" drive.

If you had put the 320 GB HDD in with the hdss from the 20GB, it would have shown up only as a 20 GB drive. Since you don't have the security data needed, the 20GB will not work in a 360 again. That data is unique and encrypted.

Access time is a big factor. Console requests data, FSD catches the request, sends it to the server, server checks the request, searches for the data, finds the data, sends it to FSD, FSD forwards it to console.. that stuff takes a while.

Use -w. The dump already has the correct ECC data, so no need to recalculate.

Oh look, a scriptkiddie. Baby, actually.
"I got your IP, ph33r m3".
You better watch out that your father doesn't catch you posting crap on his internet account, or he will take the belt to you again.

No. The LDV would not match.