Recommended Posts
-
Similar Content
-
By farrdeamer
OK... Long story - have a older Xbox (pre 1.6, mf 2002) which years and years ago I installed an Xecutor 2 and unlocked the drive, installed new dash etc.
Unfortunately after removing the clock cap, I played one game and the HDD developed a hard fault. Bought a new SATA drive for it (and adapter), found Hexen 2018 and used it to remake the OS. Booted fine, but couldn't see the larger drive (0bytes shown free).
Ah! thought I, maybe I need to flash the XEcutor 2 with a new BIOS to let it see a larger drive.
Out comes the Hexen disc again, and I used option 3 (flash), chose an 1.1-1.5 BIOS 256k and pressed to update.
After completing, it shut down... and won't startup!
I guess I wrote an incompatible BIOS (or it wrote it to the machine).
Any ideas how I can breathe life back into the machine?
Tried booting - after it tries to boot 3 times I get red/green flashing.
Tried unplugging the XEcutor from the board, I get a red ring of death (red flashing).
Tried unplugging the drive and plugging other drives in (it was unlocked).
I believe there is a copy of the flash on the HDD (but I can't read it!).
During my initial recovery, I have a copy of XBINS site, so I have all the tools on there (just that it is nearly 20 years since I used any of the tools and setup an XBOX!)....
Thanks for any help...
-
By bulkchart32
Please login or register to see this link. please click that link so that u can see a video of what i'm talking about. you'll notice that there are vertical static(static as in fuzzy static on a tv not, static as in "unchanging") lines on the screen when there is a dark scene. the video doesn't show it too well but they are even easier to see in person. that is the opening sequence of xmen legends. i have this problem on 2 of my stock xbox v1.0's and on my modded v1.4(i also have the diagonal lines on it). the lines do not appear on my v1.6's. i've tried it on 2 stock and one modded 1.6 and none of the 3 have the problem. i am connected thru the official hd xbox thing(with the component cable outputs). i'm wondering if it is an issue with certain capacitors that cause this? if so, does anyone know which specific ones cause it? the reason i ask is because it would be a pain to fully recap each board of the xbox when they are functioning perfectly in all other areas so i'd rather just replace the specific ones instead of recapping the whole board. btw, none of the cap are bulging or show obvious wear. i know that the 1.4's are very prone to the diagonal lines because of bad caps but i don't which ones are the problem.
-
By OGXbox Admin
I know people get really tired of hearing this debate, but I'd like to make my position as clear as possible once and for all.
First and foremost:
The reason the LPC exists on the Xbox motherboard is because the TSOP is soldered to the board blank, and programmed via the lpc port later in the manufacturing process. When the TSOP is blank, the xbox then looks to the LPC for a bios image to boot. This is because a pre-programmed rom is more expensive than a blank eeprom (TSOP in this case). It also allowed Microsoft to more easily update the bios image in new Xboxes for whatever reason.
So we know that they would have to retool the LPC programming device if they disconnected some LPC points. This new tool would need to be incredibly fine because the point it needs to make contact with is no longer a nice big pad.
Since nobody can find a 1.5, this retooling would have been for just a handful of motherboards. So they would have gone through this expense of retooling for such a tiny amount of boards it wouldn't have made any sense.
Next, what exactly did the alleged 1.5 board prevent? It ONLY would slow down mod chip installation. I say slow down because any knucklehead with a DMM could figure out how to get it working again. It does absolutely nothing to stop soft modding or TSOP flashing. Why would Microsoft go to such an expense to stop only one method of modding the Xbox? I don't doubt that people have found LPC points that show no continuity. This could be because of the very programmer I mentioned at the beginning of this post. It could be due to trace rot. It could be due to operator error in measuring the components. Whatever the reason for a person measuring this situation, I don't believe it was a particular version of motherboards that Microsoft intended to put out.
We saw with the 1.6, where it DID come with a pre-programmed rom (so no TSOP) on the board that they could finally disconnect the LPC. That's why we have to rebuild it there. It is perfectly consistent. It stops TSOP mods. It stops modchips for noobs. It required a new bios that supported the new video encoder. I think they believed they could use updates on game disks and Xbox Live to patch the softmods. So they thought they had all the bases covered with 1.6.
I got my information from the Xbox-Linux Project. They published an article on Xbox Security which I preserved on this site.
"Now other people found out that, if the flash chip is completely missing, the Xbox wants to read from a (non-existant) ROM chip connected to the (serial) LPC bus. This is of course because of the manufac- turing process: As it has been explained before, the flash chip gets programmed in-system, the first time they are turned on, using an external LPC ROM chip. Modchip makers soon developed chips that only needed 9 wires and connected to the LPC bus. It was enough to ground the data line D0 to make the Xbox think that flash memory is empty.
Lots of these “cheapermods” appeared, as they only consisted of a single serial flash memory chip. They could be installed within minutes, especially after some companies started shipping chips that used pogo pins, so that no soldering was required.
Some groups wrote applications like boot menus that made it possible to copy games to hard disk and run them from there. Patched Xbox kernels ap- peared that supported bigger hard disks. Making the Xbox run copies from DVD-R or hard disk as well as homebrew applications written with the official Xbox SDK was now easy."
Please login or register to see this link.
It's under the "Modchips" heading.
-
Board Life Status
Board startup date: April 23, 2017 12:45:48
Important Information
By using this site, you agree to our Terms of Use.