Jump to content
Sign in to follow this  
Magicaldave

Injecting Ind-5003.67 Bios Does Nothing

Recommended Posts

So I was trying to inject the .cfg into a 5003.67 box. (Duh) This seemed to work but I noticed the .cfg loading delay was still in place. I figured this was because I had left a .cfg sitting on C:\

But I deleted the .cfg file, and afterward the default IND intro played and the system sat on the IND-BIOS X Screen indefinitely. What gives? There were no errors when injecting in Windows. It just doesn't seem to have done anything except prevent an error screen from presenting. 

Share this post


Link to post
Share on other sites
Just now, Kekule said:

injecting the CFG does not work!   if you had tried it with 5004 you would have bricked your TSOP

I noticed! I did manage to reflash to an older version of EvoX but this presents the exact same issue on multiple unlocked Hd’s. I’m hoping I can fix by installing my modchip which is equipped with the latest EvoX, then reflash IND and forget about injecting. 

Share this post


Link to post
Share on other sites
13 minutes ago, Magicaldave said:

I noticed! I did manage to reflash to an older version of EvoX but this presents the exact same issue on multiple unlocked Hd’s. I’m hoping I can fix by installing my modchip which is equipped with the latest EvoX, then reflash IND and forget about injecting. 

Yes, the chip will work

Share this post


Link to post
Share on other sites
42 minutes ago, Kekule said:

Yes, the chip will work

This particular console is a 1.1 with an st chip inside. Hopefully I can just pull whatever is in the other bank(s) to resolve. 

Share this post


Link to post
Share on other sites

After injecting the configuration file into the BIOS, did you reflash the TSOP?

There's a new file created to flash not the original dot bin file:

iND-BiOS.5003.67.bin

but

iND-BiOS.5003.67-Patched.bin

Share this post


Link to post
Share on other sites

What app did you use to reflash the BIOS?

What version is your Xbox? Update: I thought you'd said it before - v1.1 Xbox.

Which brand and part number is the TSOP flash device on the motherboard? Update: STMicroelectronics TSOP flash - 1MB in size.

Share this post


Link to post
Share on other sites
4 minutes ago, KaosEngineer said:

What app did you use to reflash the BIOS?

What version is your Xbox? Update: I thought you'd said it before - v1.1 Xbox.

Which brand and part number is the TSOP flash device on the motherboard? Update: STMicroelectronics TSOP flash - 1MB in size.

Good guess! Lol. It is an ST chip and I flashed with EvolutionX’s dash tool. 

Share this post


Link to post
Share on other sites

Was the Evox BIOS file - M8plus.bin?

I don't understand why it would hang at the big X logo screen.  It reads no configuration file to boot up.

Does the word Microsoft appear below the big X?

And, during the startup animation, you see the EvoX purple shield in the upper left-hand corner of the screen ?

Share this post


Link to post
Share on other sites
38 minutes ago, KaosEngineer said:

Was the Evox BIOS file - M8plus.bin?

I don't understand why it would hang at the big X logo screen.  It reads no configuration file to boot up.

Does the word Microsoft appear below the big X?

And, you see the EvoX purple shield in the upper left-hand corner of the screen?

The MICROSOFT logo does indeed appear. 

 

It was NOT M8Plus.Bin. I flashed EvoXM7, apparently. This is the BIOS file that was packed with EvolutionX dash 3935. There is no big pink logo in the top left as would be expected. 

 

Even without a CFG file I’d expect IND to give an error but maybe it was just my revised version breaking. 

 

You know what? I can’t check right now but I think the hanging behavior may be caused by the fact that both drives are trying to run Rocky5 softmod on top of the modded BIOS. So I need to grab one, boot a HeXen CD and clean the thing. 

Edited by Magicaldave
Noob mistake

Share this post


Link to post
Share on other sites

Just a warning for anyone who is thinking about attempting to inject their config without a modchip. 

 

Don’t do it. You will send yourself directly down a rabbit hole to hell. 

Share this post


Link to post
Share on other sites
3 hours ago, Ging3rguy said:

Also a good idea to test it on a chip with multiple bios banks to make it easier to fix.

You know, I did this on a 1.1 so I wasn’t too worried about that. I figured I could just employ the 3-wire trick if things got real bad. 

I spent WAY too much time trying to do this and once I had recovered, I tried again and I’m not sure what exactly I flashed, but whatever it was it nuked my TSOP completely. Attempts to hotswap my chip failed multiple times and I ended up either busting my LPC or my modchip as I improvised a pin header from pins I ripped out of an old IDE dvd drive. Not sure as I spent 2 whole days on it and have a life outside Xbox modding to get back to, but hopefully I just need to rework a couple pins on the LPC.

 

So my attempts to make improvements to a friend’s console have now turned into my buddy getting a better console and I got jack while I figure this out :P

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Similar Content

    • By FerociousOG
      Unable to flash BIOS. Error reading bios file (see pic). To me it sounds like I have a bad DVD burn? Just wanted to confirm. I did burn at the slowest write speed. Will re-burn again.
      -v1.1 mobo
      -XeXEn 2018
      -Using Verbatium DVD+R media
      -Attempting to flash iND-BIOS.5004 (F and G) to use 2TB SATA HDD.

      Thanks in advance.
       
    • By Radio_Gra
      Hello, I am new here so apologies if I'm posting this on the wrong forum.  I am currently running a v1.6 Xbox with Rocky5's Softmod (v1.1.7) and XBMC4Gamers and am met with a black screen when booting the game 007: Everything or Nothing from my HDD while using component cables.  My legitimate NTSC copy of the game was ripped to my HDD via dvd2xbox (with ACL processing enabled) and I have enabled Force Progressive video mode via the NKPatcher settings (followed by a reboot).  I have attempted to boot the game while the following resolutions have been enabled on my console:
      480p (y) 720 (y) 1080i (n) 480p (y) 720 (y) 1080i (y) However, neither of these configurations seems to result in the game displaying properly.
      If anyone has any troubleshooting ideas, I would be greatly appreciative.  Thank you.
    • By Paw
      Hi guys i just found my old xbox in the basement and by the look of things it looks like its hardmoded with a Xecuter chip and there is even a 120gb drive installed and all is working without any issues. My main question is if anyone here could help me identify what kind of Xecuter chip this is, because my plan is that i would like to replace the 120gb drive with a 1tb but im getting a LBA48 warning when i try to partition the new disk and its asking me to ugrade the current bios with a new one that supports LBA48.
      Current INFO:
      Bios: Xecuter2 4976.02
      Kernel 1.00.5838.01
      Xbox v1.1
      What would be the best course of action, how should i approach the reflashing, what bios should i pick so that the new 1tb drive works as intended and ofcause what should i think about when i approach all this?
       
       
      Please login or register to see this attachment.
      Please login or register to see this attachment.
      Please login or register to see this attachment.

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.