Post by: appleguru on May 11, 2005, 01:49:00 PM
Post by: Rabid1 on May 11, 2005, 01:56:00 PM
When I do my install I update the chip to 2.3.0 before I do anything. I don't know if you have upgraded the chips to 2.3.0 or not but it might be worth a try. I have not tried leaving the chip at 2.0 but I have a couple extra's maybe I will try this weekend.
Post by: shift2255 on May 11, 2005, 02:37:00 PM
Post by: StewPidasso on May 12, 2005, 01:58:00 PM
Post by: DJLink on May 13, 2005, 06:37:00 PM
Yes I've got the latest OS version v2.3 on almost all the xenuim modified Xboxs. The only ones without 2.3 are a few that I've either never been in town to update and/or that also have not had a problem b/c they are rarely unplugged.
Yes I use instaboot on all the xbox's
No I just press the power button unless I want to enter into xenuims OS.
Any suggestions are welcome. So thank you for taking a stab at it. But I've tried almost every thing lodgical solution and I give very strict instructions about the Xenuims operation to anyone that I have provide a mod for. They are all set to instaboot. No-one has ever changed a setting on the xenium without calling me first, and I've only had a few people even have the need to change a setting.
Second,
I'm glad I am not totally alone, thank you Chiablo that is scenerio 3 that i talk about and that really sucks!
Why this does not happen to most people:
Most people do not have their xenuim modified Xboxs unplugged for 1-2 days on very frequent bases. Most people probably leave their Xboxs at home and plugged in; if thats the case you will never see this problem.
The main reason this happens so frequently to me and the Xboxs in my circle are b/c they are unpluggedl all the time. I've never had one problem with any xenuim modified Xboxs that are constantly plugged in.
I travel at least once every two weeks and bring my Xbox for something to do while in hotel rooms on business. I have 4 personal Xboxs at my house. 2 are xenuim mods and 1 is an x3 and the other is a tsop. I started bringing my tsop with me, b/c I'm tired of this problem happening. I mainly use my x3 for HD upgrades and I like to have the switch on the outside to I don't like to travel with it, but I do leave it unplugged for months sometimes and have never had a problem.
Yes, I pack the Xbox properly and treat it like a baby and so do all my friends and family that travel with theirs.
If simply leave 4 xenuim Xboxs unplugged for 1-2 days, I usually have at least one but usually 2 of the 4 Xboxs have to auto-recover.
I've been a big fan of xeniums ever since they came out; my main home box has xenuim in it. I even like it more than the x3, which I typically only use as an upgrade Xbox.
Team xodus please help me!
I'm not trying to flame the xenuim, I really like everything about them, the price, the ease of installation and flashing is far superior to any other chip in my opinion.
But this problem is really annoying and is a big deal if you travel and a really big deal if its not my Xbox that has the problem but a friend or family member that cannot quickly fix it like me and has to ship it me for me to open the thing up when nothing is wrong with the installation, every single box shipped back to me has had the chip with full power, I just had to recover the OS, and 8 times that has required me opening up the Xbox and flipping your recovery switch b/c the chip would not ato-recover. I have OS 2.3 on a recovery disc and have also tried that on the ones that would not auto-recover before opening them up fliping the switch and it would not work. After opening them up and fliping the switch, it has recovered everytime from the recovery.bin I have on the e-drive.
The problem has to OS related. That's only logical reason for this..
Post by: Rabid1 on May 14, 2005, 10:02:00 AM
Post by: DJLink on May 14, 2005, 05:03:00 PM
Post by: TvLover on May 15, 2005, 12:36:00 PM
I also think that this is an odd thing to happen because the Xenium chip is supposed to override the Xbox bios on bootup. Not using the clock at all.
Just my 2 cents.
Post by: turbinesurgeon on May 16, 2005, 01:32:00 PM
Post by: DJLink on May 22, 2005, 08:33:00 PM
I downgraded the Xenium OS from 2.3.0 to 2.2.1 on 5 different Xbox's I had at my house last Sunday. 2 are my personal ones and 3 I'm modifying for family/friends
Anyway,
Here are the details of each of the 5 Xboxs:
Box #1: v1.3 Xbox, original Xenium chip (not ice), that I bought when they first came out. Pin header install
Box #2: V1.4 Xbox, Xenium ice solder-less
Box #3: V1.0 Xbox, Xenium ice solder less
Box #4: v1.4 Xbox, Xenium ice solders-less
Box #5: v1.0 Xbox, Original Xenuim, pin header install.
Unfortunately 3 of the 5 Xbox's fraged and required recovering, to be specific box 1,3,4.
Please note****All three recovered very easily using scenario 2 (you have to hold down the eject button until it goes into recovery) which I mention above.*****
Just in case anyone asks..... All the chips had power and were definitely installed correctly, I watched the LED's etc and you really know the install is proper b/c they recovered just by holding the eject button
The other two Xenuim boxes instabooted the bios flashed to the Xenuim with no problems.
*One other note for Team Xodus if you can replicate this problem is that box 1 and 2 which are my personal Xboxs, both have had OS 2.3.0 installed for a while, the last time they fraged after being unplugged for a few days, the Xenuims with 2.3.0 recovered using scenario #1(which is the best case for newbs) that I mention up above, where it frags on start up but automatically recovers after cycling the Xbox on and off once, without having to hold the eject button. Scenario 1 does not always happen with 2.3.0. Scenario 2 and 3 has happened as well, but before 2.3.0 I never had scenario 1 happen.
Also if someone can please explain the quote from TyLover
QUOTE
I also think that this is an odd thing to happen because the Xenium chip is supposed to override the Xbox bios on bootup. Not using the clock at all.
I really think TyLover makes a great point.
I would really like to know how the clock has anything to do with the Xenuim not loading the bios and having to frequently recover after being uplugged. It does not make any lodgical sense to me. The two xbox's that did not need to recover, loaded the bios just fine and did not have the clock set, but they worked anyway, the bios loaded up UnleashX and UX sets the clock to a default time to aviod problems with game save etc. If someone can explain the lodgic in the clock being a problem I would really appreciate it! Thanks in advance to whomever can expain this for me.
Also, thank you all again for your help, suggestions, and sharing your experiences. Does anybody have any other suggestions? I would really like to solve this problem and as you can see I'm more than willing to test any ideas.
DJLink
Post by: aliupdx on May 23, 2005, 12:18:00 AM
I took the Xbox apart, pulled the Xenium out of the solderless adapter and then booted to MSDash fine. Then I shut it down and re-plugged in the Xenium and turned it back on and everything works.
I didn't do any OS recovery tricks, so the OS must be fine on the chip.
Maybe this will help give someone an idea of what's going on?
I didn't set the clock on the Xbox, just booting to the MSDash seemed sufficient to get everything into a good state for the Xenium chip.
Maybe someone else can try this trick and verify that it works for more than just me.
Post by: ajb on May 23, 2005, 06:58:00 AM
To recover, I always boot with the eject button and wait for the upgrade to HALT since there is not CD or image on the hard drive. Then I power down and boot normal.
I had this problem with XOS 2.0.1 so I upgraded to 2.3 -> Same problem.
I have been reading and researching this since I got the chip and can find no explination. I am told by some it's the clock not being set which causes the XOS to panic. I don't know that I believe this since it does boot sometimes without the clock being set (in which case I have Avaluanch auto set the clock or I set it myself in the MS dash).
I have my Xenium setup to always boot to the XOS. I don't use quick boot.
I don't plan to keep my XBOX unplugged for extended periods of time much longer though. I am waiting for my replacement power cord to arrive. Once it does I will no longer unplug it every night.
However I would still really like some answers as to why this happens. I agree with DJLink; how can the clock cause this problem? If that was the case it would happen every time (not just 2 or 3 times out of 5).
Post by: teargas1 on May 26, 2005, 05:45:00 PM
Statistics:
-11 of 12 installs currently run O.S. 2.30. My first install is still using O.S. 2.20 and has never had a problem (Installed Dec 04).
-Of the three that had problems, two were version 1.0, one was version 1.6.
-The 1.6 had chip unplugged while checking solder connections, but did not recover when chip was plugged back in. XBOX was booted to retail bios between first frag incident and reinstallation of chip.
-If I remember right, 2 of the 3 had reported changing some of the Xenium settings prior to the frag episode. I did not think to ask the 3rd person.
-All three were install using pinheader method, and all three had the external LED installed.
-All of the 3 that had problems were purchased in the same batch. Five chips were purchased at the same time. The other 2 chips are running under the same conditions and work fine.
-Holding the eject button was never tried to get the chips into recovery mode, as I just read about that in this thread today.
Hope this adds some data to the troubleshooting. My only problem with the unplugged theory, is that the 'BOX I fixed last night was booted to retail after removing the Xenium, then chip was plugged back in and it still fragged. Also, most of the installs were done on boxes that operate under the same conditions, and only a third have shown this problem.
Post by: MonsterTy on May 26, 2005, 07:44:00 PM
Post by: Player_X on May 27, 2005, 01:45:00 PM
1.0 Xbox (maybe a MS refurb model)
Xenuim ice chip with os 2.30
Stock HD
Chip installed on 4/27/05
Im having a similar problem but only when I leave it plugged in. I notice this when I have my Xbox in my bedroom it happens, 75% of the time it will need to recovered, 50% by it self the other 50% by using the eject button.
When its in the front room it will work correctly about 95% the other 5% is when I just unplugged it from my bedroom it will need to recover.
The interesting part is that if I leave it the Xbox unplugged it will boot fine every time.
So whats the only thing different about my front room where it works great and in my bedroom where it works like crap you ask. Is the power cored in my bedroom is the one sent to my by MS from the power cord recall. The cord in the front room is a replacement I purchased 3 years ago when the original got lost after a halo event I went to.
I honestly dont believe the power cored is the problem, and Im 100% sure the chip is installed correctly.
So Im left saying wtf is going on here?
Post by: teargas1 on June 06, 2005, 12:10:00 PM
Post by: aliupdx on June 06, 2005, 09:53:00 PM
So I have a similar setup to Player X. When the Xbox is in my bedroom, it is connected via that Replacement Power cord sent by MSFT. When I take the Xbox downstairs to my front room to take it apart/test/etc, I plug it in using one of the power cords for the newer Xbox's.
The Xbox was stuck in a scenario 3 in the bedroom, so I went to take it downstairs to take apart, but I plugged it in to test one last time and I got it unstuck like a scenario 2.
I'm going to have to test this a whole bunch more times, but there may be something to the Power cord theory. Either that, or bedrooms are kryptonite compared to front rooms.
Next time I'm stuck in a scenario 3 in the bedroom, I'll try using a different power cord to see if it fixes it again.
DJLink, any correlation with the power cord you're using?
Post by: Artifex on June 07, 2005, 04:52:00 PM
The RTC is powered by a large aerogel capacitor which acts like a small battery. When the xbox is unplugged, this capacitor keeps the RTC logic powered for a short period of time, ranging anywhere from 1 hour to 24 hours, depending on various factors. Once the capacitor has drained (the "battery" has died) the RTC logic loses power, and thus it's non-volatile contents are lost. This includes the current date, time, and "clock mode." When the RTC regains power (by plugging it back in, the capacitor is recharged) it is in a corrupted state, which XeniumOS can not properly process.
Setting the clock in the MS dashboard will fully reconfigure the RTC's data, thus making it again processable by XOS. Booting into the recovery firmware causes the RTC to become partially reconfigured (as a side effect of something compleatly unrelated, actually) and XeniumOS can process it enough to at least boot. (although the internal time/date structures will contain junk data, and you should still go into the ms dash as soon as possible and set the clock, to avoid improper timestamps on files and whatnot.)
We are continuing to investigate this long-standing issue, and will produce a fix when we have one.
--Arti
Post by: XBox2107 on June 09, 2005, 12:41:00 PM
i removed the chip and let my lil bro play halo 2 so da xbox could get used 2 runnin through its own system, almost finishing a level it turned off and it powers on for less then a sec and goes off, no lights light up even with da chip...im sure the power supply is fine
Post by: mitchafi on July 01, 2005, 05:23:00 PM
Post by: DJLink on July 01, 2005, 10:18:00 PM
QUOTE(Artifex @ Jun 8 2005, 01:03 AM)
This is a bug caused by problems with the RTC (Real Time Clock) "emulation" in the mcpx. The Xbox's RTC does not behave 100% like a standard RTC, and we have not yet been able to determine why the differences have been causing these issues.
-
Title: When Xbox Is Unpluged For Period Of Time Xenuim
Post by: teargas1 on July 02, 2005, 08:06:00 PM
-
So the question I have is, why does this only affect some consoles and not others? The ones I have problems with can be left unplugged for an hour and exhibit the problem. Others that don't have the problem can stay unplugged for several weeks or longer. Why would some capacitors stay charged longer than other under the same operating conditions?
-
Title: When Xbox Is Unpluged For Period Of Time Xenuim
Post by: DJLink on July 30, 2005, 04:44:00 PM
-
Post by: teargas1 on July 02, 2005, 08:06:00 PM
Post by: DJLink on July 30, 2005, 04:44:00 PM
QUOTE(teargas1 @ Jul 3 2005, 04:17 AM)
So the question I have is, why does this only affect some consoles and not others?
-
Title: When Xbox Is Unpluged For Period Of Time Xenuim
Post by: DJLink on December 24, 2005, 05:44:00 AM
-
THIS IS HUGE IF THE BELOW QUOTE TESTS OUT!
Artifex, does this mean that you really have a fix!!!!!!
If that is the case then I couldn't be happier! Your announcement was indeed HUGE. For the "small" percentage of us plagged by this problem this was a HUGE issue and we have been paciently waiting for a fix.
I have only one request. Please rls the updated OS for public, ASAP(before x-mass), or at least rls to a select few affected users TO TEST that this issue really affects the most, like me,
It would help so much to have before x-mass or on x-mass, b/c I'm currenlty on vacation for x-mass in my home town and majority of my family that have xenuim mod xbox's that have this problem are all within driving distance, so I could update the OS on at least 10-15 xbox's without having to incur the shipping $$$ for sending the xbox's back and forth, which I have previously had to incur several times before b/c of this issue.
thanks in advance for your help!
DJLink
Post by: DJLink on December 24, 2005, 05:44:00 AM
QUOTE
A HUGE announcement will be made in a few hours
THIS IS HUGE IF THE BELOW QUOTE TESTS OUT!
QUOTE
XeniumOS 2.3.1 Gold Edition:
- Fixed RTC access problems. System clock is now read correctly, and overridden to a default time if not set
- Fixed RTC access problems. System clock is now read correctly, and overridden to a default time if not set
Artifex, does this mean that you really have a fix!!!!!!
If that is the case then I couldn't be happier! Your announcement was indeed HUGE. For the "small" percentage of us plagged by this problem this was a HUGE issue and we have been paciently waiting for a fix.
I have only one request. Please rls the updated OS for public, ASAP(before x-mass), or at least rls to a select few affected users TO TEST that this issue really affects the most, like me
, It would help so much to have before x-mass or on x-mass, b/c I'm currenlty on vacation for x-mass in my home town and majority of my family that have xenuim mod xbox's that have this problem are all within driving distance, so I could update the OS on at least 10-15 xbox's without having to incur the shipping $$$ for sending the xbox's back and forth, which I have previously had to incur several times before b/c of this issue.
thanks in advance for your help!
DJLink