Jump to content
OGXbox.com

Search the Community

Showing results for tags 'fault'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Rules
    • Why Can't I Download?
  • Subscribed Members Only
    • Subscribed Members Only
  • Off Topic
    • New Member Introductions
    • Rumble Pit
    • Suggestion Box.
  • General Xbox Discussion
    • General Xbox Discussion
  • Original Xbox Modding Forum
    • Hardware Mods
    • Modchips
    • TSOP Flashing
    • Softmods
    • Repair
  • Xbox Case Modding
    • Case Mods
    • Lighting & Electrical Mods
  • Tutorials
    • Official Tutorials
    • Tutorial Submission
  • Software
    • Bios
    • Dashboards
    • Installation Disks
    • Applications
    • Games
    • Emulators
    • Homebrew
  • Xbox Collecting
    • Xbox Collection Showcase
  • Rare and Uncommon
    • Rare and Uncommon Xbox Hardware
    • Rare and Uncommon Xbox Software
  • Vendors
    • N64 Freak's Products
    • Barnito's Products
  • Development
    • Rocky5's Projects
  • Online Play
    • Game Night
  • Classifieds
    • Wanted
    • For Sale
  • Moderator Section
    • Moderator Back Room

Product Groups

  • Vendor Forum
  • Membership Subscriptions
  • Forum Ads

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 3 results

  1. I'm posting this here as I am at the end of my rope with trying to diagnose this issue. I have 23 original Xbox's and this fault ONLY happens on hard modded systems that have the Samsung DVD drive (both the SDG-605B and SDG-605F). I will give a little information first on the type of hard mods I performed to each of the systems(they are all identical). modchip: Xblast Jafar/Aladdin ide wire: 40 pin 80 wire 24" long ide to sata: startech adapter(set to master) hdd: 3tb wd red pro or 4tb hgst ultrastar RAM: stock 64mb(1.6 models and 2 1.4s) or 128mb upgrade(all other models) console capacitors: all replaced on both the motherboard and PSU with Panasonic FM(mouser) or Nichicon (console5 kit) DVD drive caps: all replaced on Samsung drives only BIOS: Cerbios 2.3.1 UDMA5 (tried UDMA2 did not help) Xbox motherboard revision: I have all revisions from 1.0 to 1.6b The issue I am having is that XBMC4Gamers gives the DVD "Busy" signal when I try to boot a game(game is brand new, no scratches), and the stock 5960 dashboard will just give a disc read error. The error can be fixed by simply rebooting the console into xblast OS then loading cerbios from there. Once the console boots again the game reads fine first try and works without stutters(the lasers are fine). The issue will happen again if the xbox is turned off then unplugged and allowed to sit a bit. If I turn it on again using the power button (instead of using disc button to boot to xblast first) the issue will happen again until I go back into xblast and reboot the bios. Also, the game will boot if I have the disc in the drive when first turning on the console. It only doesn't work when trying to insert it after reaching the dashboard (stock or xbmc). This issue only happens on the samsung drives. I have many thomson, philips and even 1 hitachi drive and the issue does not happen there. On first boot with these drives, the games always load first try without having to reboot the console. I can rotate these samsung drives between consoles and the issue follows them to whichever console I put them into. I am convinced that this is not a hardware issue because of this but some problem with either the BIOS or xbmc4gamers. I really hope someone can help me here as I have no idea what the issue can be and troubleshooting this had led me nowhere so far.
  2. Is there an OG XBOX fault tree / repair guide out there somewhere? I know its hard or near impossible to record or prep every possible scenario, but Going through this XBOX repair of mine I've found a lot of threads, youtube videos, and suggestions from you amazing folks, but nothing comprehensive on the repair side except an electrician who does some otherworldly stuff trying to determine the fault with a power supply. I know about the XBOX repair guide, but that doesn't have a fault tree like I envision. Not saying a fault tree doesn't exist, just that I haven't come across one. Since I'm trying to track down the Gremlin in my own XBOX and currently the Gremlin is winning, I thought through the process I would document what was done, and add in what could have been done so that it can be a resource for others, especially those new to the community, should -they suffer the same fate. Again if one exists I don't want to re-create the wheel. My XBOX knowledge is banal, so I would be relying on this community to keep me on the correct path, but I'd be willing to organize the thing if you all think it would be a worthwhile endeavor. For example, first thing would be power on Y/N. If No, swap power cords. -> No change ->check fuse functionality-> check plug solder joints. I'll attach a pic of a concept I quickly jotted down probably about a 10% complete, haven't thought it through too much or put any time into it since I don't know if its even needed -- and definitely not saying its the right way or the steps are even in order, but its a concept. On the left side is a descriptive fault check pathway, on the right is the traditional fault tree. Let me know if you think something like this would be value added.
  3. I repaired a black Controller S just replacing the worn joysticks with alternatives which have worked well. The controller had joystick centering issues which those replacements pretty much eliminated. The controller has been used quite a lot over the two months since the repairs without any problems and then last night (BTW still very hot ambient temperatures 85+F) the controller started acting up. At first I thought it was a game glitch or a corrupt game save file but after being returned to the pause menu multiple times or just freezing with no controller response it started to tell me to reattach the controller to port 1. A replacement Controller S worked fine as far as I tested it so I do not think it is a controller port problem. I've had a similar thing with a used MS XB360 wired controller which was faulty. It would work fine then suddenly report the same thing or getting no signal despite the fact it was a wired controller. My suspicion was the cable had been run over by a vacuum cleaner or something similar as there was clear physical damage and exposed wires I'd wrapped in insulating tape. But I guess it was also stretched to the point one or more of the wires was part broken. However with this OG Xbox and Controller S its unlikely to be anything like that. The cable is always used with plenty of slack and has never knowingly been stretched or damaged. There's no evidence of that at all - the cable looks good. So what could cause this behaviour with a Controller S? Any ideas?

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.