Post by: pHrEaQuAzOiD on September 18, 2004, 02:34:00 PM
First off, I guess I'm greedy, but I would Like to Modify both the flubber and the logo color on my bios. I've done both with and evox m7_ef bios with no problems whatsoever...I'm not able to use an X2-4981.06 bios because it wont read my F: drive( I had a previous TSOP flash), but the 4983.67 works great and I have no complaints! My problem is that I cant seem to colormod that bios...is it locked? Is there any way around this? Now I would be content with the Evox M7_ef bios, except for the fact that I cant change the boot logo under the X(the ms)... so is there any way to colormod the X2-4983.67 bios using XBtool?
My other question is as I stated earlier, I had a TSOP flash done, and then my eeprom went bad. I now have an X2 2.3b Pro chip, got everything in order with the eeprom(video discrepancy), and now all is well......but I can't restore the original bios to the TSOP. I'm using Evox to do it, I have a 1.4 version box and I'm using the 5101 original bios. It just keeps saying not a valid bios file...I've used ALOT of different original bios files trying it (bad idea), and have a locked HD, but it wont read ANY of them..Does anyone have any ideas? Please? Thanks in advance.......
Edited for wording
Post by: pHrEaQuAzOiD on September 18, 2004, 04:03:00 PM
Post by: pHrEaQuAzOiD on September 18, 2004, 06:11:00 PM
Post by: pHrEaQuAzOiD on September 18, 2004, 08:22:00 PM
1) Is there any way for me to edit the X2 4983.67 bios using XBtool or is it just un-editable??
and.......
2) Does anyone have any suggestions as to why I'm not able to flash my TSOP using Evox and the original 5101 bios (1.4 box), accquired from the usual places? Am I doing something wrong??
Any help would be greatly appreciated
Post by: heinrich on September 18, 2004, 09:27:00 PM
2) you need to boot from the tsop to flash the tsop. and why you are flashing with evox and not raincoat. and what on earth does your drive being locked or unlocked have to do with flashing. the exact error message and what chip you are trying to flash might help, as well.
Post by: pHrEaQuAzOiD on September 18, 2004, 11:59:00 PM
Well I'm not a total nooB but I still have a lot to learn....I'm acually not sure what raincoat is(dumb as that sounds).....I was using evox to flash the tsop because just the dash that I use. I was however performing the flash with the chip OFF, so that it wouldn't write to my chip. The chip that I have is an Xecuter 2.3b pro and the error message is something along the lines of "not a valid bios". When I run the m$ dash from evox my kernel is 5101, and that is the bios that I've been trying to use(I was also reading a good deal in the forums and one of the mods confirmed 1.4 box=5101, correct if wrong please). Also, since I can't edit the X2 4983.67 bios, is there any way to get the 4981.06 bios to detect my F drive without formating it, or am I just stuck with a colorful M7_ef with crappy m$ logo(he he). Thanks again
Post by: pHrEaQuAzOiD on September 19, 2004, 12:55:00 AM
Post by: pHrEaQuAzOiD on September 19, 2004, 12:59:00 AM
EDIT-scratch that, I found it.
Post by: pHrEaQuAzOiD on September 19, 2004, 01:10:00 AM
Post by: pHrEaQuAzOiD on September 19, 2004, 08:50:00 AM
Post by: pHrEaQuAzOiD on September 19, 2004, 09:36:00 AM
That tut won't open, it's corrupted....I've been reading some more about this, but I don't have agent under fire! I also can't telnet to my xbox. And which version raincoat do I use?....I'm very confused.
Post by: atomiX on September 19, 2004, 10:53:00 AM
and like heinrich said, you need to boot from the tsop if you want to flash it. once the xbox boots from a chip, it can't "see" the tsop anymore so it can't be flashed.