Swizzy

What does it get stuck on more precisely? You may want to try to reset the settings and such followed by re-downloading all covers & tu's...

Then i'm afraid your data is lost...if you can read the remaining memory space (has to be done using a hardware flasher) someone migh eventually write an app to read that data... maybe i will when i get bored enough... Yeah, it's not a reliable place to store things with a hacked machine... these kinds of problems ocassionally happen (write error causing corruption in the memory unit) it mostly happens on Corona 4GB and Jasper 256MB/512MB, i think trinities are quite "safe" as they have an external module instead of built into the same device that you have the rest of your NAND on (the bootloaders etc.)

There was probably a write error to the Memory device causing the memory unit region to be mangled... (not readable anymore)

If you have a corona; not sure... and that's why you don't use the internal memory You could try to write back an old dump from your console and pray that you can read the internal memory again... otherwise there is no tool to read the contents of the internal memory

Well, you don't need the simpleflasher.cmd file, that's purely for automation with autoGG... + to flash you need to add a crc32 aswell (matching the file you want to write)

"Compatibility pack" that's what you want to be searching for, or just download all possible DLC for the game? ;D

Yeah, read and write using Simple 360 NAND Flasher... it has to be done that way because of the MMC, nobody has reversed how the dashboard communicates with the MMC yet, therefor we cannot access that from XeLL... the only other option at this time is to use hardware (which for the record is a pita by itself) Yes, when you build a new freeboot image (using xeBuild GUI, JRunner or AutoGG) you always get an updated XeLL with it aswell (all of these apps use xebuild in the background...

No, corona is the LATEST motherboard version, MMC coronas are any 4GB slim with a corona motherboard...

that'd be "xebuild" not "xebuild GUI"

not if you have a 4GB corona (MMC corona) howewer the 16mb model (NAND corona) works just fine altought you get no video output on any corona with older versions of xell (v0.992 was the first one that had corona video support)

what do you mean? If you mean why old versions of XeLL don't have MMC reads it's because of the way it was coded (it uses raw access which only have NAND support), the new one uses virtual access (however, this don't work when launched from xelllaunch)

Try Simple 360 NAND Flasher, Flash360 don't have corona support... and old XeLL don't have Corona MMC (4GB) read support etheir...

One of the many problems with having our own LIVE clone service is that many, i repeat MANY games have their own servers in the background running the actual game server... in order for ALL games to work on such a service we'd have to spend decades figuring out exactly everything about every game, and for what? LiNK is quite enough for online play, there's MANY users there already... Another problem with making a cloned LIVE service is that it's constantly changing, if we make it work today tomorrow it won't... you don't notice most of these changes, but... they're there...

When you have a JTAG/RGH you just format it as-is, it'll use the entire disc... the thing you did before was add security sectors which is used by the original dashboard to verify that it's indeed a Microsoft branded harddrive (and what size it should have) one of the patches done with JTAG/RGH is to disable that check which means it can use ANY harddrive with ANY size... (the limit is the filesystem)

yes... if you run the updsrv on the box and use the new xebuild modes... read more about it here: http://www.realmodscene.com/index.php?/topic/2205-xebuild-108-update-tutorial/ or in the readme...

You need to format it in the xbox once you've installed the new harddrive

Dunno why, but my memory says i have used my 3TB drive without a problem... but it depends on the sector size used, 4K sectors = 16TiB maximum apparently, but yeah... normally it's 2TB maximum xD i also don't know where i got 4TB maximum from... maybe my mind mixed up TB and GB and put it in the wrong context(?) http://en.wikipedia.org/wiki/File_allocation_table

One more thing; you can use any HDD up to 4TB (the limit of FAT32) i have used my 3TB WD with my 360 without a problem

Tried this?: http://xboxpirate.eu/forums/topic/4082-splinter-cell-blacklist-how-to-setup/#entry40609

NAND corruption ussually gives E79, E71 or random freezes, this error is likely to be something like 0023... phatties can sometimes have problems with the eject button, it may be clicking (making sounds) but not react... i've had that happen... the same naturally goes for the sync button which is also used to get the error code... On a side note; corrupt SMC will likely cause very random issues and have errors relating to the southbridge... etheir way, corrupt smc is likely caused by a bad write due to bad soldering/connections...

Just run the installer, however... DL 3.08, 3.09 and 3.10 are all the same (the difference is in the installer)

The no-power from console rule isn't true, it however is recommended that you use a "big" one, meaning one that draws power from your wall socket as this means that it'll generally have better performance (less lagg for games) Most USB harddrives are delivered with NTFS, so you have to format it yourself, windows won't do it, but if you're using windows use this tool to format (it's the recommended one across all scenes and so on): http://www.ridgecrop.demon.co.uk/guiformat.exe

how? : launch.ini or dashlaunch installer

yeah, what this does is allow EVERYTHING to get to this ip xD

It's because of UDP and TCP...