Post by: bluewoodz on September 12, 2004, 02:20:00 PM
Loaded it in my V1.6 xbox with xenium ice.
Retail kernel wouldnt launch at all.
So i took my Original eeprom and mixed it s data with the other EEPROm and wrote it.
Now i can only load Xenium OS
and i hit restore and it still doenst work.
I cant even unlock my HD from Xenium os
says failed.
Please help
thanks
Post by: Artifex on September 12, 2004, 02:48:00 PM
Did you unlock the hdd before doing so?
What do you mean by "mixed it's data with the original eeprom"?
It's likely you've put yourself in a pretty bad situation, but you need to provide some details as to the specific steps you took in order to determine what that situation is, and how to go about fixing (if you even can at this point).
--Arti
Post by: bluewoodz on September 12, 2004, 02:53:00 PM
Post by: bluewoodz on September 12, 2004, 04:43:00 PM
Uhm i got the eeprom that screwed up my XBOX on my pc.
Dont think i can restore the eeprom i backed up on xenium cause it wont unlock the HD.
Post by: bluewoodz on September 12, 2004, 05:13:00 PM
Im running out of ideas.
Post by: Gumba on September 12, 2004, 05:41:00 PM
| QUOTE (bluewoodz @ Sep 13 2004, 01:16 AM) |
| i tried making a CDRW boot for EVOX , with eepromer on it and the original eeprom, but it wont load when i goto launch evoX. Get error code 16. Im running out of ideas. |
Look, see
http://arisme.free.fr/Xbox/Reflash/
Post by: bluewoodz on September 12, 2004, 05:48:00 PM
Post by: Artifex on September 12, 2004, 06:36:00 PM
If so... then it's time go go shopping for a new drive, and mourn the loss of savegames.
--Arti
Post by: bluewoodz on September 12, 2004, 06:43:00 PM
| QUOTE (Artifex @ Sep 13 2004, 02:39 AM) |
| Well, bluewoodz failed to provide any details on his situation, but it sounds like he didnt unlock his hdd before he blew away his original eeprom. This means his hdd is locked with a key which has now gone off to that great big bit bucket in the sky, with his original eeprom.... leaving him with an unlockable hdd. If so... then it's time go go shopping for a new drive, and mourn the loss of savegames. --Arti |
well thats not a very helpful post ARTIFEX posted... lol
I think ARTIFEX failed to read the post thoroughly...lol
cause its not the drive thats the problem... its the eeprom.. lol
and again it is fixable... lol
thanks to the help of GUMBAs post.
Lol
u get all types here huh... peeps who are kool and helpful and others who are well.. whatever
Post by: bluewoodz on September 12, 2004, 07:23:00 PM
And launched the .bin file.
It starts up for a second then shutdown.
It keeps do that strating up and shutting down.
any more help would be great.
thanks
Post by: Artifex on September 12, 2004, 08:51:00 PM
| QUOTE (bluewoodz @ Sep 13 2004, 02:46 AM) |
| well thats not a very helpful post old ARTIFEX posted... lol I think ARTIFEX failed to read the post thoroughly...lol cause its not the drive thats the problem... its the eeprom.. lol and again it is fixable... lol thanks to the help of GUMBAs post. Lol u get all types here huh... peeps who are kool and helpful and others who are well.. whatever |
Yes, you're right, you know oh so much more then me, i'm just a random n00b.
Oh why didn't I see how much of an idiot I am?
Nevermind the fact that I coded XeniumOS, know the xbox architechture and firmware backwards and forwards, and have a well established reputation and history for being one of the most prominent developers of groundbreaking and legal software for the xbox.
You don't need my lowly assistance, you've got The Great Cromwell to solve all of your problems.
You just go right on ahead and keep laughing.
--Artifex
------------------------
EDIT:
P.S.
I'm usually not one to go for flamings and snide comments, but I just couldn't resist here.
------------------------
Post by: Artifex on September 12, 2004, 08:56:00 PM
| QUOTE (bluewoodz @ Sep 13 2004, 03:26 AM) |
| well i went to the link did what it said to do. And put it on CDRW. Then put it in ADDITEMS. And launched the .bin file. It starts up for a second then shutdown. It keeps do that strating up and shutting down. any more help would be great. thanks |
You spoke too soon, eh?
--Artifex
Post by: bluewoodz on September 12, 2004, 09:06:00 PM
| QUOTE (Artifex @ Sep 13 2004, 04:59 AM) |
| You spoke too soon, eh? --Artifex |
dude whats ur deal?
im working on it right now...
Post by: bluewoodz on September 12, 2004, 09:25:00 PM
| QUOTE (CrayZEE @ Sep 13 2004, 05:27 AM) |
LOL  |
lol
wazzzzzzzzzzzuuuuuuuuupppppppp
Post by: Frezz on September 12, 2004, 10:07:00 PM
Frezz
Post by: bluewoodz on September 12, 2004, 10:16:00 PM
Post by: Palmore on September 12, 2004, 10:24:00 PM
Post by: bluewoodz on September 12, 2004, 10:36:00 PM
| QUOTE (Palmore @ Sep 13 2004, 06:27 AM) |
| I'm assuming you still don't know who Artifex is... lol He's part of Team Xodus, the guys that made the mod chip you have, and as he said, he wrote the code from the Xenium OS.. That's not a guy to badger, or take lightly... He was trying to help, but I see you didn't figure that out, maybe that's how you got in this situation... As he was saying, if your Hard drive was LOCKED, and you over wrote your EEPROM.. You see, that stores the unlock key for your harddrive. If the hard drive was LOCKED, and you put a new EEPROM in, then it CAN'T unlock the hard drive.. In other words your drive is toast, and you must buy a new one before you get any further... Think before you act and speek, you have ppl trying to help you, and you just wanna talk trash. |
MAybe cause i'm pissed off... lol
Cause i got screwed , and screwed again!
Anyways i'm over that.
i just really wanna solve the problem..
and no i didnt know he made the chip! until he posted it.
what if i down grade the Xenium os to 1.1 and then use the cromwell bin with the patch to eeprom.bin?
(cause when i do it now it just hangs and keeps rebooting an shutting down)
Or would putting slayerevox on a CDRW and trying to boot EVO X work?
Anyways if i pissed anyone off acted like an ARSE!!! i do apologize.
When things go miserably wrong and comments are taken the wrong way i lose my kool ... well i dont have to explain human nature to ya!
Where is the eeprom located at physically?
Is it on the motherboard ... i mean if i put in my OG harddrive will it boot?
man i hope TEAM XODUS doesnt show up at my door and kick my ARSE!!
Post by: Gumba on September 13, 2004, 04:15:00 AM
Post by: bluewoodz on September 13, 2004, 07:45:00 AM
| QUOTE (Gumba @ Sep 13 2004, 12:18 PM) |
| If you locked the HD with XOS2, I think it sets the master password to "TEAMASSEMBLY" and you can use that fact to unlock it without knowing the user password |
Whats the fact?
I think i have one ooption left now> throw it in the trash..
I'm bout to give up.
Post by: bluewoodz on September 13, 2004, 09:13:00 AM
| QUOTE (pablo15 @ Sep 13 2004, 05:11 PM) |
| Dude, That frezz guy is right.. your a TOOL BOX. MORON! |
Dude thanks for using ur first post ever on XBOX-scene on my thread!!
If ur gonna say something dont hide behind a new name... and dont post little girlie comments... be a man... take off ur skirt!
shit like i'm the only person to fuck up an xbox... get real..
damn wankers..
ive been doing alot of reading at it seems this is the only modchip that the linuxpatched eeprom doesnt load , but hangs up.
Anyone know why it hangs up?
Post by: bluewoodz on September 13, 2004, 10:11:00 AM
I guarantee! cause if i cant im just gonna buy a regular xbox anyways.
Post by: cybrpunk on September 13, 2004, 12:45:00 PM
Do you still have your original eeprom? If you do, you should be able to reflash your xbox with the original eeprom. This is a flashable chip on the motherboard which contains various info such as your region (NTSC/PAL), DVD Region settings, video settings ... as well as the key to unlock your hard disk. Without the original eeprom you are kinda screwed here, so I hope you have a backup of it.
If you DO have a backup of the original eeprom... and not the one that you modified... then all you need to do is follow the instructions HERE ... something you've already seen I know.
The cromwell image there is a valid, 256KB BIOS file that should flash to any modchip. I suspect you probably made a mistake when injecting the eeprom image into the cromwell BIOS, hence why it wouldn't add to your launch list.
Forgive my skepticism, but you've made a good number of mistakes either by not reading or by rushing yourself. Take the time to research a little better and re-trace your steps. Calm down and take your time. I'm willing to bet that the reason you couldn't add the .BIN file as a launch item is due to you not following directions properly.
We're trying to help (some of us are). Artifex would've probably solved this for you had you not insulted him. Take a breath and realize that we're not obligated to help. Any help that you do get is due to the kindness of the community and the wealth of information shared here. I learned what I know by reading and listening to these same people and am giving it back now... as many others do on a daily basis. That's the way it works.
Post by: Artifex on September 13, 2004, 01:07:00 PM
| QUOTE (cybrpunk @ Sep 13 2004, 08:48 PM) |
| If you DO have a backup of the original eeprom... and not the one that you modified... then all you need to do is follow the instructions HERE ... something you've already seen I know. |
That cromwell image was built before proper 1.6 support, it seems. Someone should re-apply the patches to current cvs and rebuild.
| QUOTE |
Forgive my skepticism, but you've made a good number of mistakes either by not reading or by rushing yourself. Take the time to research a little better and re-trace your steps. Calm down and take your time. I'm willing to bet that the reason you couldn't add the .BIN file as a launch item is due to you not following directions properly. We're trying to help (some of us are). Artifex would've probably solved this for you had you not insulted him. Take a breath and realize that we're not obligated to help. Any help that you do get is due to the kindness of the community and the wealth of information shared here. I learned what I know by reading and listening to these same people and am giving it back now... as many others do on a daily basis. That's the way it works. |
AMEN!!!!!!
--Artifex
Post by: Artifex on September 13, 2004, 01:09:00 PM
| QUOTE (kong @ Sep 13 2004, 08:53 PM) |
| HEY TOOLBOX!!! THERE IS NO WAY TO RECOVER WHAT YOUR DUMBASS DID!! FREZ IS RIGHT!!! I IWSH I WAS AS SMART AS BLUEWOODZ TOO!!! AND MAYBE IF YOU HADN'T PISSED OF ARTIFEX, ARTIFEX WOULD TELL YOU THE TRUTH THAT THIS XBOX IS DEAD!!! THERE IS NO FIX FOR YOUR PROBLEM WITH A XENIUM CHIP!!! IF YOU HAD A SIMPLER CHIP YOU COULD DO THE CROMWELLPATCH WITH THE EEPROM ORIGINAL. BUT THIS CHIP IS MORE ADVANCED, WITH MORE ADVANCED PROBLEMS THAN SIMPLE LINUX! cheers |
Bluewoodz/Kong....
Multiple accounts are not allowed for any reason, especially when only held for the explicit purpose of flaming and confrontation. Keep this up, and you'll find yourself banned.
--Artifex
Post by: bluewoodz on September 13, 2004, 01:28:00 PM
Dude just please help me get my xbox back working.
Thats all i am trying to do. Just sqeeuze enough info out of ur head to get me back in business please.
Thats all i want.
I got bent over buying a bad eerpom that was sold as what it wasnt ( v1.6 eeprom, flashed my v 1.6 xbox, in avalaunch using eepromer, locked HD in eepromer, then launched retail kernel from xenium os, and bam, my box got toasted.)
I obviously dont know what im doing to fix the problem.
I've been try to fix it for the past 26 hours.