TEK Nemesis

Welcome!!!

@Rocky5 A quick hack of the file gives some pretty good results but I can't back out of the Synopsis screen. I just want the Back button to act like the B button in this case. Any ideas? remote.xml

OK. Thank you.

Now it will be easier for future upgrades to that XBox because you've got the "latest" version of the Xenium OS and you have a BIOS on the modchip to support many terabytes of drive space.

Glad it works now! So, XBpartitioner 1.3 worked well?

evox.m8plus.137.bin would be an example of an M8+ that has been modified to support larger HDD.

I thought the evoxm8+ would have come with LBA48 support. There should definitely be something on the Hexen 2018 disc though. EDIT: Yes, you will need to look for an M8+ that has been patched for LBA48.

Hey @Rocky5. Great job on the skin. I really like it a lot! Quick question. I just recently did the XERC 2 IR mod with the internal MS USB dongle. The install was a success and I can see in UnleashX everything working perfectly. However, none of the navigation buttons seem to work with the XBMC4Gamers, even when I enable the MCE/Universal remote, nothing. Is it just me or...? Thank you!

I'd do this, in this order: 1. Flash with LBA48 BIOS to enable F, maybe with something cool like "x2.5035.137.(Force480p).bin". (I like forcing 480p.) It looks like your chip can handle all the main BIOS file sizes so just stay away from the ones that say they are only for the XBox v.1.6. (Others to try are "M8plus.(Force480p)prepatched.bin", "iND-BiOS.5004.67.bin", "x2.5035.137iND-BiOS.5004.67.bin". 2. Once flash is done, use your Hexen 2018 disk to reformat your HDD from square one. 3. Run XBpartitioner.

search for "Xenium OS 2 user manual". First hit.

Again, don't look at the negative. You have two successful stories now. One, that you were able to flash the BIOS and two, that you have successfully upgraded the Xenium OS.

Did you remove the DVD from the drive and reboot?

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.

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.

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

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.

You keep trying. You mess things up. You learn more. You try something different. You wake up in the morning at 2am with an idea. You try one more thing and then you have a breakthrough. You finally did it and you feel great. You try your luck at something else. It gets messed up. You do some more research and you see how people carry out similar things. You try your hand. Mess it up. Buy a $5 modchip on eBay. Buy some solder, flux, wire. Buy an old junky XBox on eBay. Start tinkering. Bammo! Something worked! You did it! Then you go back to that other XBox and you mess around again and boom! All of a sudden it starts working too! You feel great and want to learn and tackle more. You come back here to share your success and are overwhelmed by the responses to your story. You see someone new on this board asking for help and now you too have the experience to assist. This is what it's all about. No one is perfect and not everyone got it the first time but we persevered and one day we had success.

I'm at the point where I need to see pictures. LOL! I think there's a switch on the chip. I'd open the box up and switch it to the opposite position and then see what happens.

Did you place the XeniumOS 2.3.1 recovery.bin file to the root of the E drive and then this happened? If not, what led to this?

Pay specific attention to this statement: "Place the XeniumOS 2.3.1 recovery.bin file to the root of the E drive like @KaosEngineer suggested."

OK. So, I'd stick the future BIOS' there but I'd do as @KaosEngineer recommended first.

Learning is about trial and error sometimes. Did you place the XeniumOS 2.3.1 recovery.bin file to the root of the E drive like @KaosEngineer suggested?

Stick it on your C drive. I'd do a factory reset so that you return to known state.

Me too please.

How do you know that it is a Xenium modchip?