More on LIVE Bans, HDD Crippling, Possible Ban Causes


Recommended Posts

Kushan (our Kushan?) wrote a nice little article summarizing all kinda info we have about the current (still ongoing) Console Live Ban Wave:

- What does this mean for you and what can you do about it?

Firstly, and most obviously, you cannot connect to Xbox Live on this console any more. This means no more game updates (aka title updates), XBLA games, marketplace content, netflix/sky player and so on. There is no way around this, all online capabilities are now disabled PERMANENTLY.

In all likelihood, your gamertag has NOT BEEN BANNED. When your gamertag gets banned, Microsoft sends you an email detailing why, if you have not recieved this email then your profile should be ok, to a certain extent.

Hard Drive installs are now disabled on the banned console. This means any disk-based games you have will no longer play off of the hard drive. If you attempt to play a game, it will tell you that it was installed on a different 360 and needs to be deleted/installed again. When you delete the game and attempt to install it, you are given a message telling you that it is not supported. There is no way to fix this, that functionality is simply gone from the banned 360.

The hard drive itself is left untouched - you can place it in another 360, even an unbanned one, and it will still work just fine. You do NOT need to reformat it to regain any kind of functionality. Any installed games will need to be reinstalled for the console you want to play them on. This is normal behaviour and happens when swapping HDDs on unbanned/legit 360's.

Windows Media Centre functionality is disabled. It is still possible to stream video/music content via the video library.

Your Gamertag may be corrupted. This does not mean your gamertag has been banned, you can recover it using any live-capable 360, however ANY ACHIVEMENTS YOU HAVE EARNED SINCE BEING BANNED WILL BE LOST. Your gamertag will be corrupted EVERY SINGLE TIME it is used on a banned console. This means you cannot use your banned console to play backups offline just to get achievements - it wont work, the second you put your profile back on a good 360, it will be corrupted and all progress lost. There is no way around this.

The same applies to game saves - if you access a game save on a banned 360, it too will be corrupted when accessed on a legit/unbanned 360! YOU HAVE BEEN WARNED! There is no way around this, either.

Your XBLA games and DLC will still be valid, however to play them on a different 360 you will need to be signed into Xbox Live. This is normal behaviour on unbanned/legit 360's as well. They may be corrupted and have to be re-downloaded if you attempt to access them on a banned 360. You can transfer all of your downloaded content to a new 360 here: http://www.xbox.com/en-US/support/systemus...ion/default.htm however note that you can only do it once every 12 months.

So, in summary:

Your Banned 360:

* Cannot go on Xbox Live

* Cannot install games to the HDD

* Cannot use Windows Media Centre extender

* Cannot be used to get achievements from backups without corrupting your profile

You cannot do anything about this, short of buying a new 360.

There may be more functionality disabled than mentioned here, things are still being discovered.

- So what caused my ban?

There are MANY theories as to what is causing so many consoles to get banned this time, however as of yet there is nothing concrete, just a lot of circumstantial evidence and speculation. Please do not add to this, a full investigation is under-way.

c4eva, the main guy behind <snipped>, had this to say:

<+c4eva> fw itself not detectable

<+c4eva> suspect they are going hard on warez releases and incorrect use of abgx!

He also added the following:

<+c4eva> just to let you know that im looking into the current ban wave. I am currently running several brand new xboxs on live! These xboxs are in various configs. All are running ixtreme 1.61

<+c4eva> One is running original discs, another is running on xbl (no discs) , another is running a backup from my region!

<+c4eva> until tests are completed, no eta on liteon fw!

When we know more, YOU'LL no more, so please do not ask for updates!

A full transcript is available here - http://pastebin.ca/1660777

Remember, if you really want to blame someone, blame the person that decided to modify your 360 in the first place - most likey, that would be you ;

Interesting...

I hope this isn't breaching any rules...

Edited by t0mbi

They also seem to be banning people who 'play it safe', and use retail copies + abgx etc.

I myself think it may have something to do with forza 3 or bad abgx data, although thats just me, and as microsoft do it in waves its harder to find out the reason.

They also seem to be banning people who 'play it safe', and use retail copies + abgx etc.

I myself think it may have something to do with forza 3 or bad abgx data, although thats just me, and as microsoft do it in waves its harder to find out the reason.

Security through obfuscation is the way they certainly do it, if you have a google you will probably find infinite theories within the last week posted onto the internet as to who/why/when/what the criteria is. It makes me laugh.

I am actually not understanding this whole banning thing....I thought everyone used to say "If you play it safe you can't get banned." What happened to that?

Nothing happened, really. Just people being impatient. A new firmware will be eventually released to sort the issues, but people just can't wait anymore, have to play bad releases of games that have not been released and brag about it on the internets. That's what gets them banned.

Last thread got closed (made by AB).

Nothing wrong with my topic and it's simple message, it was the tard packs who couldn't keep their hands out of the "HAI GUYZ I PIRATE N GET MY STUFFZ FROM THIS SITE" jar who got it closed.

Nothing wrong with my topic and it's simple message, it was the tard packs who couldn't keep their hands out of the "HAI GUYZ I PIRATE N GET MY STUFFZ FROM THIS SITE" jar who got it closed.

ohhh those buggers always spoiling the informative fun :(

Looks like ABGX is at fault as nearly every 3rd game isn't stealth (according to their tests).

There's a new firmware in the works also. Apparently the new one will be indistinguishable from the original and there won't be any more bans. But they've said that before :p

Looks like ABGX is at fault as nearly every 3rd game isn't stealth (according to their tests).

There's a new firmware in the works also. Apparently the new one will be indistinguishable from the original and there won't be any more bans. But they've said that before :p

That's a load of rubbish. What he's saying is they ripped 40 games and 1 in every 3 wasn't in the database. That means nothing, it just means nobody has added that particular pressing to the DB. This is a misunderstanding of how the whole thing works.

Not what I read. Was plain as day the script I seen...

"we tested 40+ NTSC games. at least every 3rd didnt verify. so the db = defn has problems."

Yes, from a guy who doesn't actually work with the stealth team. Furthermore, you're right, it IS plain as day - "every 3rd didn't verify". Do you know what that means? 1 in every 3 was never added to the database. Is that a problem? Not really, because ALL games have more than one pressing. Different disc manufacturers give a different pressing and even different times of pressing (some are pressed over a few days, or some "reprints" are done) will require a different rip to be COMPLETELY verified.

But that doesn't matter because as long as one rip of a certain game version is in there, that's all that matters.

Or let me put it this way - if abgx was at fault, why would they be completely rewriting the firmware?

Oh and people have got banned having used only their own personal backups. No abgx invovled there.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • One Year In
      hhgygy earned a badge
      One Year In
    • One Month Later
      AMV earned a badge
      One Month Later
    • Week One Done
      AMV earned a badge
      Week One Done
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!