Softmodding 1.6b stalls at xboxhd

[Gavin19]

Ok, I followed the softmod instructions for the 1.6b so that I could get my x3 flashed with the 3.03 bios. Everything was fine until I booted into the linux iso and came to type 'xboxhd'. Even though the drive was unlocked it gave an error about not being able to find an xbox hard drive on /dev/hda, even though that is exactly where it is. Even stranger is that if I reboot it locks the drive, but after some seek errors it loads anyway. But this time when I type 'xboxhd' it recognises the drive perfectly on /dev/hda but because it is locked most of the features are disabled.
Why the hell won't it recognise the drive first time, ie when it is unlocked?

I intended on using a 200gig Maxtor but was waiting to flash first then change hdds, but I went ahead and tried to use it. It worked ok, seemingly, as I was able to format and build an xbox hdd from scratch. But the guide is a bit vague for me at this point. What exactly do I do with this fully prepared drive? I tried swapping it straight back into the xbox but it was showing error7 and wouldn't do anything. I rebooted with it in and got another error?

I don't care which drive I use to flash the bios, I just need to get one to actually do the job for me. Any ideas please? I really need this 100% for Saturday. Thanks.

 

[Martin C]

I'd seriously leave the idea on softmodding.

When you boot FlashBIOS from the chip, exactly what happens on your Xbox / Screen ?

Martin

 

[Gavin19]

I have no idea which bank the bios is supposed to be on. No matter which combination of banks I use it always just gives me a blank screen. What happens on the xbox is that I can hear the dvd-rom drive (empty) seek a few times, the main led on the front flashes green. Then it stops flashing after 10 secs or so and the LED shows amber.If I hold power/eject it ends up at a blank screen too. But if I just disable the chip it boots normally.

What is it likely to be?

 

[Martin C]

It a FlashBIOS version issue. You need 3.0.3 on your chip. The best advice is to contact your supplier and see if they don't mind reflashing it for you.

Martin

 

[sveetsnelda]

He already knows it's a flashbios problem. Thats why he is trying to softmod his box (to flash 3.0.3 to the chip). There is no way he is going to be able to get his chip to a supplier and back in 2 days.

Gavin, the reason you are getting the HD error on the newly prepared drive is because the new drive isn't locked properly. When softmodding, the new drive you create has to be locked using your unique HDD key. A non-modded xbox will not boot an unlocked drive.

As for the seagate drive not showing as dev/hda, when are you swapping the drive? I'm assuming you did it after the bios posted? I've had this problem before, but I don't remember the circumstances/how I fixed it.

 

[Gavin19]

Well, more progress made. After trying both my pcs I got a chance last night to use a friends and it recognised the xbox drive as being at /dev/hda and it went OK. Then I put the xbox drive back in place, booted with x3 off the pins and Evox started!! I was over the moon. Well, for a while anyway.. Now I'm stuck at the bios stage. When I go to flash the bios it doesn't show any to choose from. I checked the c:/fonts/bios folder and both 3.03 and the x3 bios are there, but it can't/won't recognise them. To come so close yet still so far is beyond annoying. However on a lighter note, due to the successful softmod I was able to install my old Spectrum and Mame games! Well at least xmas hasn't been completely ruined

So any ideas as to why it shows no choice of bios? I even renamed 3.03 to BIOS.BIN because I had heard that it had to be named so, but still nothing. Maybe is there any other apps that I could run from within Evox that could help? If I could just get this flashed it would be heaven.

Thanks a million for the guide sveet too. Nice job :idea:

 

[Martin C]

You don't have to rename the file to BIOS.BIN if you're reading it from evox. As long as it's a BIN extension it should be ok. Did you remember to update the evox.ini with the ROM data?

Martin

 

[XboxSysMods]

Can I use Kinect with my banned 360?

I'm sorry for what is probably a simple question. I have an Elite with a BenQ drive. I had it modded 2 days after I bought it and 1 week later I was banned. I'm not complaining about that, but I'd like to ask a question:

I am interested in getting the Kinect. I understand that the dashboard can be manually updated so does this mean I am able to use it? I'm not sure what firmware I have (I'll check if it's necessary... and if I can figure out how), but I know that I need to insert the special disk for wave 4 games.

I'd also like to be able to play the Kinect games. Is any extra modification/ flashing required?

Thanks a ton in advance!

 

[webbo73]

Re: Can I use Kinect with my banned 360?

I think you should be fine, i have a banned console with the new dash, updated via usb and kinect works fine. It was banned last year so...
As long as you don't play AP2.5 games.