In reply to your post "Rob Ocelot", yes I was always aware of the flash protection dip switch, and yes I am the only one who uses my XBOX. Yes you are right, accidents DO happen, although, the ONLY way I could accidentally overwrite the bios, is by EVOX, and you'd have to go though three menus to do it, not to mention that the flashing process is indicated by a bar at the bottom of the screen, so I think I would have noticed something like that. And no, flash protection is not unreasonable, but in my situation, I do not have any children, or other adults that use my XBOX. I live alone, so suffice to say I don't have to worry about someone who is not familliar, yet curious enough to explore my XBOX.
As far as the details of my job, I think they are beyond the scope of this forum, and the reason I deemed necessary to mention my profession, is to give a sense to you, and anyone else who challenges me, that I pretty much know my XBOX, and I pretty much know what I'm doing IMO. I don't think you, or anyone else has the right to come here and tell me that I make wild claims, or use my ten minutes to inspect my XBOX, as opposed to posting in this forum. I did not come here to be challenged, or to challenge anyone, I came here to contribute to a solution of the problems we are having, by mentioning my experiences. And AGAIN I'll say, I never refuted other members theories, and I never said what I believe is fact. So please do me a favour and stop quoting bits and pieces of my posts. If you want to quote something, why don't you quote the parts where I say, that I will keep looking nto the events of my findings, or what about the part that I will admit if I've taken a wrong path, and apologize to this forum. Maybe it will be you who will find your posts in the trash bin, or maybe it will be both of us, so I propose a truce, in the spirit of being constructive. What do you say? Are we agreed?
I do not have another chip laying around to see if the problem persists, although that would answer a lot of questions. But there ARE other ways to find out if in fact the chip is at fault. What I DO know, is that the problems started shortly AFTER HALO2, the dash update, and connecting to XBL for the first time, two years AFTER modding the XBOX, so I strongly believe therein lies the problem, as I've NEVER had any problems with my XBOX before. Like you said it may be merely a coincidence, but I find it very unlikely. I WILL restore old backups of C:/ and E:/ partitions, and maybe X Y Z to be sure. I'll report back to this thread on what I find.
I know that initially, it would not make sense to think that M$ would be targeting mod chips that are left on write enable. But it could very well be a trade-off from getting banned. Maybe those of us who were lucky, or unlucky(take it as you may) enough to leave the chip to "write enable" are given a "chance" so-to-speak, Basically, if you inadvertely allow your chip to be erased, by a piece of embedded "sleeper" software in the "new and improved" xboxdash.xbe, that is patiently waiting for you to power on your chip, or remotely, then you won't get banned from XBL. As far as M$ is concered, the perverbial thorn in their side is the mod chip itself, and the hacked bios it contains. That is the root of their problem. Bigger HDD's new partitions, various homebrew apps, are all useless without the chip and/or the bios. So as in most solution scenarios, the logical path is to eliminate the problem at it's source- in this case the chip, and it's instructions, which tells the XBOX what it can and cannot do, within the limitations of it's hardware infrastructure of course. Again considering the scrutiny that I've recieved from you in the past, I will mention that it is my OWN theory, considering that I have not been banned. The Marriage theory? Very likely, and I won't refute that. There have been many articles on the internet about M$'s plans to crack down on modders, and cheaters, and they can scan HDD's, or whatever else have you. But I don't really believe M$ would disclose any hints, or precise information, on how exactly they are dealing with the problem, or the methods they have chosen to tackle it. I think that they would purposely want to put us on the wrong track. Yes, it is odd that no one else has come foward with similar incidences, although there was one post somebody else wrote(can't remember the make of the chip) stating that his LEDS were acting strange, inticative of his chip going into different modes- enable and disable- without his intervention. He said that he noticed the LEDS on the eject button went from Green, to yellow to red, and that his chip indicates those colors, to let the user know which mode his chip is in, as to not accidentally log onto XBL, with the chip on. So there IS one similar instance reported, after all. I will try to find it, and post the link here. I hope the members, moderators, administrators, and yourself, will find my reply satisfactory, in regards to my conduct.
Cheers.
Author
Topic: Has M$ Disabled My Mod Chip?!?! (Read 143 times)