Noob Needs Help Hdd Upgrade!

[DaveB]

Ah, the last question is a moot point - there is no switch on the damn chip. Guess I'm screwed!

Edited March 31, 2019 by DaveB

[TEK Nemesis]

1 hour ago, DaveB said:

should I flick the switch before I power it up

I'm sure the textbook answer is to have the XBox unplugged when doing any work inside it however I have been known to flick switches with it plugged in and powered on.  So, don't do as I do, do as I say.  LOL.  "Unplug it.  Move the switch.  Power on and access the chip's menu." 

EDIT:  I see that there's no switch on your chip.  Apply the rule above for the future though.

Edited March 31, 2019 by TEK Nemesis
Not applicable -> no switch on chip

[DaveB]

I did a google image search - that 1 inch piece of red wire on the chip, isn't it supposed to be longer and attached to the motherboard?!

[TEK Nemesis]

17 hours ago, DaveB said:

I get the error "Bios is not properly sized!"

The site below made a reference to this error message and stated that if you get the message "Bios not properly sized" then "more than likely its not the size of the BIOS it's how you burnt the CDRW".  Now, if you didn't use a CDRW, then relate the statement to something else.  For example, there may be a problem with how you are burning the media (i.e. DVD-R) or maybe when you FTP'd the file, it didn't copy correctly.  The link below says to rename your BIOS file to BIOS.BIN (though that might just be for clarity).  Read over the guide at the link below.  It seems quite thorough.

http://consoleforum.info/viewtopic.php?t=5

[DaveB]

Is that red wire a problem, though? I dunno if the file ftp'd properly or not, but I did burn the cd according to the instructions in the user manual. I'll read over that guide next, thanx for the link.

Just in case I'm making another stupid mistake, in the 'xeniumOsv2.31.' I downloaded, in the folder burning a cd, there's 2 iso image files  - "xos_2.3.1_Recovery_Restore_Factory_Defaults" that's 410,980kb. And another "xos_2.3.1_Recovery", also 410,980kb in size. I renamed the image file "BIOS" before burning it. Was that correct, or did I misunderstand?

Edited March 31, 2019 by DaveB

[TEK Nemesis]

2 minutes ago, DaveB said:

Is that red wire a problem, though?

I'm sure that's the D0 wire on the "D0" pad on the Xenium chip.  You definitely need it.  From here, it's a software solution that you're after.

[Ging3rguy]

Have you tried putting the bios you want to flash on to your E partition and then flashing it using the xenium flash menu?

[DaveB]

yea, the xenium os will only browse to C drive or cd/dvd drive, not E. I tried it in C drive, still same problem "bios incorrect size" etc. I'm more concerned with the red "DO" wire now though! The xbox seemed to be functioning ok with that red wire as it is (snipped off and not attached to the motherboard), but TEK Nemesis, I "DEFINITELY NEED IT" TO BE ATTACHED TO THE MOTHERBOARD? Do I need to fix that first, and how?

Could that be what's screwing up the flashing process?! Should it have even been functioning like that?!!!

 

Edited March 31, 2019 by DaveB

[DaveB]

OMG,  really really sorry, disregard the stuff about the "DO" wire, it IS attached by a very fine wire that I didn't notice lol I really need to get my eyes tested!

So, there's no switch, back to square one then. Did I burn the cd correctly? If so, then I'm out of options, I guess? If not, where did I go wrong?

In the 'hdd' folder of "xOs2.3.1_Recovery" and "Recovery Restore Factory Default",  both the bin files are each 1,207kb. To flash from hard drive, I rename the bin file "BIOS", then ftp it to C drive (since the xenium OS won't browse to E drive), then that should work when I use 'flash' option, yea...?

 

 

Edited March 31, 2019 by DaveB

[Ging3rguy]

I think your getting confused between the xenium software and a bios, i think you are trying to load the xenium software as a bios, I gave you the bios sizes in an earlier post. 

[DaveB]

Yea I am confused! I was advised to use the files contained in "XOS2.3.1". There are only 4 files in this download - 2 iso files for cd, and 2 .bin files for hdd. If none of these are the right files to update the bios with, I have no idea what to do!

[Ging3rguy]

yes they are for the firmware, go to https://drive.google.com/drive/folders/1cjyjBbca9SXrSdevbAkP2r1GdW49GSE5 (thanks to xbmcmodsforxbox) download a bios (evox m8) load it to your c partition and see if you can flash it using the xenium flash menu.

[DaveB]

Ok, I think I see the prob here - the 'Recovery' files are supposed to be used in the the "Recovery" option on the xenium menu screen? But when I choose that, I get a screen that says "Safety mode  loading...." which then changes to "loading...HALT". This is because the switch needs to be flicked. But the switch is missing from the chip. So, there's nothing else I can do to make the xbox use thewhole drive then, right?

[DaveB]

Thanks for the link, but there's lots of different files for 256k evo 8, I dunno which is the correct one to download and use!

"Evox m8 bin"?

 

Edited March 31, 2019 by DaveB

[DaveB]

Thanx for the link, I managed to flash the bios ok this time. But, when I reboot the xbox, the only difference is that I get "EVO X" logo in the top left of screen. Xb partitioner 1.3 still gives the LBA48 missing" error. I still can't upgrade the chip cos Recovery mode still does the "Safe Mode loading...HALT" crap then freezes, just as before. So, I can only surmise that the Recovery mode needs the switch to be flicked, and since there is no switch to flick, I've hit a brick wall!

Edited March 31, 2019 by DaveB

[DaveB]

[Ging3rguy]

Which evox M8 did you use? try the M8+

[Ging3rguy]

Found this over on Xbox-HQ. This is for updating the firmware.

Using Flash Fxp you are going to transfer the file you downloaded (recovery.bin) to your "E" folder. Once transferred you will boot to the xenium os and from the menu select "Recovery Mode" once selected it will automatically find the file and update itself, also it will turn it self off. There has been reports of xbox's freezing up and people waiting up to 10min or so before shutting them off, I would give it at least 5min if it happens to freeze, mine did not freeze and it only took about 2 min. tops. When your machine turns off simply turn it back on and you should be updated with v1.1, if not simply try again. One thing you will want to do is turn the instant boot feature on. "Configuration" > "Settings Menu" > "InstantBoot" just press "A" and it will change it to ON. I would turn "Quick Start" off in my experience when leaving Quick Start on and instantboot on the xbox fragged.

[DaveB]

I used EvoxM8.bin (256k), I'll give give M8+ a try. Should I put the firmware "Recovery"  file in a folder on E, or in the root? Does it matter?

Edited March 31, 2019 by DaveB

[Ging3rguy]

Put the recovery file in the root otherwise I don't think it will find it.

[DaveB]

Ok, I already went ahead and put it in the root of E, tried 'recovery mode', it's been frozen on the 'safe mode loading...HALT' screen again for 10 minutes now, nothing happening...

[Ging3rguy]

Give it a bit longer and then try it again, but as you are now able to update your bios do you need to update the firmware?

[DaveB]

Yea, I still get the 'LBA48 missing, you need to update" when I use xb partitioner. I tried the 'recovery mode' again with the cd, this time I didn't get the 'loading...HALT" on screen, and instead of the led turning to red, it's flashing orange. Not getting my hopes up, but at least something's happening this time. Gonna wait a while and see what happens...

[DaveB]

Still waiting, it still says "Loading....". Not looking too good, it should've been done by now if it was gonna work, surely? Been 20 minutes now...

[TEK Nemesis]

1 hour ago, DaveB said:

Thanx for the link, I managed to flash the bios ok this time.

Woah, woah, woah!  This is the breakthrough you needed!  Congrats.  Whatever you did here, you were on the right track.  So, remember what size the BIOS file was and try again with a different BIOS of the same file size that supports LBA48.  I would halt all other attempts with upgrading the Xenium firmware/OS.