The Dreaded "no Bios Update Found... Halting!" Options

[nabziF]

I have an Xbox 1.6, which I've installed a Spiderchip 1.1 (although its boot screen says 1.0b...hm) into and I'm trying to flash the bios. Since my previously burned movies work on the Xbox, I figured I'd stick with known-compatible media and burn a boot DVD instead of a boot CD (I'm using Verbatim DVD-R). I've decided to go with the metoo-m8plus-v1.4.1. So I downloaded that, selected the file Metoo-M8plus_16-06.bin, renamed bios.bin, created a 1.4GB dummy file named aaa.aaa, burned as ISO (it automatically changed the file names to uppercase since I disabled Joliet), and burned at 1X (since that's the top speed of my DVD burner. Pity me). So anyway, I've tried booting several (10+) times, and I always get "No bios update found... Halting!"

The only things I can see that could be causing a wrinkle in the process is that I'm burning using Toast 6 on Mac OS X, and I'm using the Metoo-M8plus_16 bios. However from what I've read, neither of these facts should prevent this from working. Any suggestions would be greatly appreciated. Thank you!

[HackDaBox]

read here
http://www.xbox-scene.com/articles/macosx.php

and download my Spiderchip V1.6 BIOS cd
main website is here ...

www.hackdabox.com

This post has been edited by Chancer: Aug 1 2005, 04:33 PM

[nabziF]

Thank you for the quick response!

I notice your bios ISO file has the standard M8plus 1.6...however I would like the LBA48 and Xbox Live disable features from the metoo release; and according to several on http://forums.xbox-scene.com/index.php?showtopic=314524&st=0 they were able to flash the metoo bios to their chip...

[HackDaBox]

LBA 48 is allways enabled for one large F drive with my filez !

flash it with my file first then it's easy for you to reflash later with something else !

[nabziF]

Thanks, your ISO worked. I have no clue why the ones I was making didn't work; everything looked pretty much the same (except my dummy files were named aaa.aaa, I wonder if that has something to do with it...)

[Chancer]

A flash disc is not converted to Xiso. It should be burned as a regular data file. Hacks files are images of the complete disc for ease of burning

[otherguy]

when the files are sorted alphabeticaly on the disk the bios.bin file must be the first in the list.
Naming the dummy file aaa.aaa most likely was your problem. If you try making a flash disk in the future i suggest you name the dummy file dummy.bin or zzz.zzz or something to that effect.

[Chancer]

when the files are sorted alphabeticaly on the disk the bios.bin file must be the first in the list.
Naming the dummy file aaa.aaa most likely was your problem.

It doesn't make any difference at all. The Flashbios will not read the dummy wherever its burned on the disc. It merely pads out the burn. The disc is checked for the correct file over the entire written area.

[otherguy]

are you sure?
is this a change made recently?

I do recall what i mentioned to be an issue in the past. I suppose i could be wrong, since i never intentionally burn my dummy files to go against my logic...

Either way the bios disc wasn't burned correctly.

[Chancer]

yep the dummy file on my old flash disc (used on many) is called abc.dat

[top]

hi ,im having the same thing happening to me..I have a 1.6 with a x3ce and a x3cp
Im tring to flash with x3.3108v16plus.bin
and im using a 100k dummy bin
any help thanks

[nabziF]

A flash disc is not converted to Xiso. It should be burned as a regular data file. Hacks files are images of the complete disc for ease of burning

A premade ISO flash disc image from HackDaBox (nothing to do with Xiso) was what I had to ultimately resort to. But what I was trying to do initially was to create my own bios flash disc using the metoo bios; it didn't work . I renamed the bios file bios.bin, added a dummy file, and burned as ISO according to various tutorials on x-s, and yet the chip simply would not find the bios file...however it obviously recognized the disc itself, because the boot screen would show the disc name. For future reference, any suggestions on what I may have been doing wrong? Perhaps the metoo just isn't compatible with Spiderchip 1.1? (specifically, metoo-m8plus-1.6)

when the files are sorted alphabeticaly on the disk the bios.bin file must be the first in the list.
Naming the dummy file aaa.aaa most likely was your problem. If you try making a flash disk in the future i suggest you name the dummy file dummy.bin or zzz.zzz or something to that effect.

This seems backwards of what would make sense. If I understand correctly, most burning apps by default burn ISOs alphabetically starting in the center. I also checked the burn order, and the dummy file was listed first (which according to my application's help file, the files at the top are burned first, innermost). Please correct me if I am wrong, but to my knowledge the purpose of a dummy file is to increase the bitrate at which the relevant data is accessed at a given rotational speed (by pushing that relevant data (bios.bin) further out toward the edge of the disc); thus it makes sense to me that the dummy file should be first in the order of files burned. This is why I named it so that it would alphabetically precede bios.bin.

It doesn't make any difference at all. The Flashbios will not read the dummy wherever its burned on the disc. It merely pads out the burn. The disc is checked for the correct file over the entire written area.

Er...so what is the point of a dummy file (see response to otherguy's quote)?

[ChuckBales]

xbox's have a hard time reading the cd with just a <1MB file (the bios) on it, so the dummy file is added for some fluff.

This post has been edited by ChuckBales: Aug 2 2005, 07:01 AM

[Chancer]

The dummy file is so the laser simply doesn't skip a 512k file.Its simply increases the size of the burned area, it has nothing to do with putting the bios in a certain place.
The reason your disc did not work is simple you burned it using the wrong method. The disc is burned as a plain and simple data disc (try it if you don't believe) the standard on nero that this conforms to is classed as an ISO9660., thats where the iso bit comes from.
You are making the assumption that the bios file would be skipped if it was burned in the centre of the disc. How can the size of the file increase the bit rate at which the data is accessed. This would suggest the larger the files the quicker the access time and its incorrect the access time is determined by the seek time of the drive itself.
Media is ruled out as it returned the disc name. the bios compatibility theory is gone because it would not stop it flashing.
next time you do a flash disc just try for me select data disc in nero and burn it as is, (the rest of the stuff BIOS.BIN etc is spot on). It wirks everytime as long as your media is compatible with the drive.

[top]

if you had a choice would you burn to a cd-r or cd-rw or dvd...
i cant get the cd-rw to read...getting ready to try the dvd