Post by: MrSelfDestruct on September 20, 2003, 12:56:00 PM
He was installing the xbox today, and he ran into a problem. I had him write a me a small desription of what he was doing, and why it didnt work.
| QUOTE |
| I got an error 6 when loading with the 120 hdd in ur box. I put it on my box, ran config magic, and wrote down the unique hdd key. I ran ur box with original hdd, ran config magic, and did on the fly eeprom editing and changed the unique hdd key to the one i wrote down. Tried booting with 120 gig hdd and got error 6, tried botting with original hdd and got error 6. |
He tells me that the only way to get around the problem is to buy a modchip, or to flash the TSOP (but he said he had never done that before, and it requires soldering, so I dont think thats the best idea). Is this true? I thought it was possible to get a bigger HDD without a modchip. So...is there any way to get around this problem without having to buy a chip?
Post by: MrSelfDestruct on September 20, 2003, 03:04:00 PM
Maybe this is posted in the wrong forum
Post by: BCfosheezy on September 20, 2003, 04:54:00 PM
Post by: MrSelfDestruct on September 20, 2003, 05:00:00 PM
I mean, I didnt take my box to a proffesional or anything, so I wasnt totally expecting everything to work out PERFECT the first time, but damn.
So how SHOULD it have been done? what did he do wrong, just so I can tell him, so he doesnt do it in the future. any help would be greatly appreciated
Post by: regulater7 on September 20, 2003, 07:14:00 PM
Post by: MrSelfDestruct on September 20, 2003, 10:24:00 PM
| QUOTE (regulater7 @ Sep 21 2003, 04:14 AM) |
| fucking, just flash the tsop with 007 trick, its a free mod chip.. if u have the game... or rent it.. 5$ modchip. |
so are you saying I DONT have to buy a modchip after all?
If not, then please explain exactly how I can fix the problem I have (error 06)
Post by: RiceCake on September 21, 2003, 12:02:00 AM
Well he changed your HDD key to his HDD key, and because the 120Gb isn't locked, and the original has a different key, its fucked!
Your only hope now is to mod it or to lock your original/120Gb with his key (With the 120Gb you'd need to use HDD Driver or similar to copy over the dashboard).
I got an error 6 when loading with the
120 hdd in ur box.
Its not locked, DUH...
I put it on my box, ran config
magic, and wrote down the unique hdd key.
Thats his EEPROM HDD key, pfft!
I ran ur box with original hdd, ran config magic, and did on
the fly eeprom editing and changed the unique hdd key
to the one i wrote down.
He changed your EEPROM to his EEPROM, big mistake, should do it to the (Ahem) hard drives not the EEPROM...
Tried booting with 120 gig
hdd and got error 6, tried botting with original hdd
and got error 6.
Well the 120Gb's not locked, and the original now has a mismatched key, doofus...
Post by: BCfosheezy on September 21, 2003, 07:01:00 AM
You only have 1 option now. You MUST put a chip in to fix this as it is the only way to load a hacked bios. (a hacked bios does not look for hd passwords unless the drive is already locked.)
The guy that was talking about doing the 007 mod to flash your tsop is a moronical bastard because you have to be able to boot and go to 007 to be able to do that. You can't even boot so to suggest that was ignorant.
Future advice:
Yeah those exploits are cool but they are not for noobs. Just put a chip in from now on or have someone flash your tsop because this way you do not have to "sign" every piece of software you want to run. It is much easier to have a hacked bios load from the start rather than to do it the way you tried.
Post by: MrSelfDestruct on September 21, 2003, 07:05:00 AM
| QUOTE |
| The guy that was talking about doing the 007 mod to flash your tsop is a moronical bastard because you have to be able to boot and go to 007 to be able to do that. You can't even boot so to suggest that was ignorant. |
Yea, I didnt think that would be possible.
Ok, well thanks for all the help guys, I really appreciate it. So you say my only option is to get a modchip (and I bet that is the case)
Rice cake said
| QUOTE |
| Your only hope now is to mod it or to lock your original/120Gb with his key (With the 120Gb you'd need to use HDD Driver or similar to copy over the dashboard). |
Is what he said right? IS there infact another option other than buying a chip?
Post by: exiled350 on September 21, 2003, 07:17:00 AM
| QUOTE (BCfosheezy @ Sep 21 2003, 04:01 PM) |
| This means that in order to upgrade your hdd, your new hd has to be locked with the same password as the one you're trying to replace. (that password is stored on the mobo on the eeprom) He tried to change the eeprom password to the one on your 120 gig. |
i dont belive that is true. i think the way it works is the eeprom is used to calc a password on the fly using several things inc the hdd serial and xbox serial. you have to use liveinfo with your eeprom that should have been extracted before you started. then liveinfo calculated the password to lock the new hdd with. theroeticaly if you have the eeprom from the broken box you could get the key back from the orig hdd and relock it with the right password.
Post by: MrSelfDestruct on September 21, 2003, 07:25:00 AM
| QUOTE (exiled350 @ Sep 21 2003, 04:17 PM) |
| theroeticaly if you have the eeprom from the broken box you could get the key back from the orig hdd and relock it with the right password. |
Really.....
So that would fix the 120 gig HDD to work with the xbox, without a modchip, right?
Post by: exiled350 on September 21, 2003, 08:21:00 AM
Post by: MrSelfDestruct on September 21, 2003, 08:32:00 AM
Before he took out my original HDD, he went into evox, and hit the backup:) button. He then took those files and put them on a CD-R.
So....could you please be so kind as to explain exactly how to fix this problem with that backed up CD-R. I would REALLY appreciate it
Post by: exiled350 on September 21, 2003, 08:45:00 AM
Post by: MrSelfDestruct on September 21, 2003, 08:52:00 AM
But yes....the original HDD was working no probelm before he did anything. Thanks for all the help. Ill let you guys know how it turns out
Post by: BCfosheezy on September 21, 2003, 09:10:00 AM
| QUOTE (exiled350 @ Sep 21 2003, 10:17 AM) | ||
i dont belive that is true. i think the way it works is the eeprom is used to calc a password on the fly using several things inc the hdd serial and xbox serial. you have to use liveinfo with your eeprom that should have been extracted before you started. then liveinfo calculated the password to lock the new hdd with. theroeticaly if you have the eeprom from the broken box you could get the key back from the orig hdd and relock it with the right password. |
no it doesn't calculate anything on the fly. They are all set values. Sorry junior.
The hd password stays static. If the eeprom password changed according to those other variables then the xbox would not be able to unlock it upon boot genius. I realize that the you gave examples of 2 serial numbers, which in theory should not change. You may be right that the password WAS generated once by those 2 serials but it is not constantly changed. It is not ON-THE-FLY. That was bs. what I said was true and if it were not then u wouldn't have all these people who locked their hd but killed their mobo with wasted drives now.
Post by: BCfosheezy on September 21, 2003, 09:14:00 AM
| QUOTE (exiled350 @ Sep 21 2003, 11:45 AM) |
| good. the orignal hdd is unlocked right? and it was working correctly b4 he started to mess with it? follow this guide and that will get you back on track. you can also use live info with your eeprom to get the orignal hdd key to relock it so it works again incase of an emergency. |
no, from what he said it HAS to still be locked. He's using the phoenix bios loader, which has to be loaded AFTER the original bios loads. As we all SHOULD know, the original bios HAS to unlock the hd in order to boot. It will not boot if the drive is unlocked. He changed the hd unlock password in the eeprom and now it won't unlock the original drive. That is the whole problem. He cannot change values in the eeprom back to the original ones without being able to boot the xbox.... which he cannot do with an original bios. THE ONLY WAY HE'S GOING TO BE ABLE TO FIX THIS IS TO SOLDER IN A MODCHIP.
Post by: MrSelfDestruct on September 21, 2003, 09:29:00 AM
| QUOTE (BCfosheezy @ Sep 21 2003, 06:14 PM) |
| no, from what he said it HAS to still be locked. He's using the phoenix bios loader, which has to be loaded AFTER the original bios loads. As we all SHOULD know, the original bios HAS to unlock the hd in order to boot. It will not boot if the drive is unlocked. He changed the hd unlock password in the eeprom and now it won't unlock the original drive. That is the whole problem. He cannot change values in the eeprom back to the original ones without being able to boot the xbox.... which he cannot do with an original bios. THE ONLY WAY HE'S GOING TO BE ABLE TO FIX THIS IS TO SOLDER IN A MODCHIP. |
yes,
I think your right BC. Well....I was going to be paying him $80 for the job (installing CC light, custom jewel, and HDD....but since he didnt install the HDD correctly and now I have to buy a chip, Ill probrably just end up paying him $40 for the install, and the other $40 I was going to give him will go towards that mod chip.
Well thanks for all the help guys. I REALLY, REALLY appreciate it.
Post by: exiled350 on September 21, 2003, 09:58:00 AM
| QUOTE (BCfosheezy @ Sep 21 2003, 06:10 PM) | ||||
no it doesn't calculate anything on the fly. They are all set values. Sorry junior. The hd password stays static. If the eeprom password changed according to those other variables then the xbox would not be able to unlock it upon boot genius. I realize that the you gave examples of 2 serial numbers, which in theory should not change. You may be right that the password WAS generated once by those 2 serials but it is not constantly changed. It is not ON-THE-FLY. That was bs. what I said was true and if it were not then u wouldn't have all these people who locked their hd but killed their mobo with wasted drives now. |
well if that is true then why the fuck is the password on my 40gb diferent than the one on the orignal 8gb? and i never said the the password was "changed" on-the-fly i said that it is calculated using static values in the eeprom including the hdd serial # at boot time. if you take the orignal hdd that is unlocked and put it in a computer and run liveinfo with the eeprom that was taken from that box it will give you the password to lock that drive with. once that is done then the box can unlock the hdd because it has the password that hdd wants. if the drive is locked with a incorrect password then there is no easy way of getting it back.
Post by: RiceCake on September 21, 2003, 03:21:00 PM
Your 120Gb obviosly isn't locked, I didn't see anywhere where he did. So, first prepare the hard drive somehow (I think there's a PC utility) and then take his hard drive EEPROM key and use it to sign your 120Gb. He changed your hard drive key (In EEPROM) to his (He's a moron cause he thought you could on-the-fly edit the hard drive key, but the data he saw was actually the EEPROM...).
It should work, in concept unless he fucked something else up...
I still can't believe he was stupid enough to use an On-The-Fly Edit EEPROM with an EEPROM utility and thought it had something to do with the hard drive...
He thought if you put in the hard drive the key it showed was the key the hard drive currently was locked with...
Edit: Oh just noticed - yes if you do get back the key from your original hard drive and relock it with the one he put on your Xbox, it should work.
Post by: Sottilde on September 21, 2003, 04:31:00 PM
Follow my tutorial posted on this board. You CAN fix it without a modchip or TSOP flash (not that you could, anyhow). The tutorial is at http://forums.xbox-s...T&f=41&t=105803 if you need guidance to lock/unlock the drives.
Error 6 is a 'cannot load dash' error, not 'hacked bios'.
Here's what you do.
You have that backup on a cd-r, no? Use the key in hddkey.txt (without colons or 0's) to unlock the original HD (using hdunlock.exe, in dos). Also use hddisabl with the same key. You can also unlock the 120 gigger using your friend's key. Grab his backup folder, use liveinfo - click 'load eeprom' and point it to eeprom.bin off HIS BACKUP. It should give you a 40-character key in the bottom half of the screen. You can use this to unlock the 120 gigger. If that doesn't work, try the key in hddkey.txt (from HIS backup folder). He may have been dumb and used that. Remember to use hddisabl after you unlock.
If you can get either of them unlocked, you are good to go. You can lock both drives with hdlock.exe . Use the key in YOUR hddkey.txt to lock the original HD - use the key given to you from liveinfo when loading YOUR eeprom.bin to lock the 120 gigger.
Good luck with it, PM me if you have further troubles.
Sottilde
Post by: BCfosheezy on September 21, 2003, 04:48:00 PM
| QUOTE (exiled350 @ Sep 21 2003, 12:58 PM) | ||||||
well if that is true then why the fuck is the password on my 40gb diferent than the one on the orignal 8gb? and i never said the the password was "changed" on-the-fly i said that it is calculated using static values in the eeprom including the hdd serial # at boot time. if you take the orignal hdd that is unlocked and put it in a computer and run liveinfo with the eeprom that was taken from that box it will give you the password to lock that drive with. once that is done then the box can unlock the hdd because it has the password that hdd wants. if the drive is locked with a incorrect password then there is no easy way of getting it back. |
Pop your 8 gig back in and it will unlock it allowing u to boot. This means that your eeprom didn't change. It doesn't calculate on the fly... otherwise there'd never be a problem of people flashing the wrong thing to their eeprom... it'd just DO IT ON THE FLY LOL. That doesn't happen. It's a static value and that's that.
Post by: BCfosheezy on September 21, 2003, 04:50:00 PM
| QUOTE (Sottilde @ Sep 21 2003, 07:31 PM) |
| You guys are all quite wrong, in my opinion. First of all, ConfigMagic COULDN'T HAVE changed the EEPROM. The Jumpers to flash the TSOP weren't soldered, so you can't change the EEPROM. If you could, what would be the point of soldering it? Follow my tutorial posted on this board. You CAN fix it without a modchip or TSOP flash (not that you could, anyhow). The tutorial is at http://forums.xbox-s...T&f=41&t=105803 if you need guidance to lock/unlock the drives. Error 6 is a 'cannot load dash' error, not 'hacked bios'. Here's what you do. You have that backup on a cd-r, no? Use the key in hddkey.txt (without colons or 0's) to unlock the original HD (using hdunlock.exe, in dos). Also use hddisabl with the same key. You can also unlock the 120 gigger using your friend's key. Grab his backup folder, use liveinfo - click 'load eeprom' and point it to eeprom.bin off HIS BACKUP. It should give you a 40-character key in the bottom half of the screen. You can use this to unlock the 120 gigger. If that doesn't work, try the key in hddkey.txt (from HIS backup folder). He may have been dumb and used that. Remember to use hddisabl after you unlock. If you can get either of them unlocked, you are good to go. You can lock both drives with hdlock.exe . Use the key in YOUR hddkey.txt to lock the original HD - use the key given to you from liveinfo when loading YOUR eeprom.bin to lock the 120 gigger. Good luck with it, PM me if you have further troubles. Sottilde |
HAHAHAHAHAHAHAHA
you're an outright idiot. You do NOT have to solder anything to flash your eeprom. YOu have to solder to flash your TSOP. They are two completely different things. I can't believe your stupid ass made a tutorial. HAHAHAHAHAHAHA
Post by: BCfosheezy on September 21, 2003, 04:52:00 PM
| QUOTE (RiceCake @ Sep 21 2003, 06:21 PM) |
| Here's what you do: Your 120Gb obviosly isn't locked, I didn't see anywhere where he did. So, first prepare the hard drive somehow (I think there's a PC utility) and then take his hard drive EEPROM key and use it to sign your 120Gb. He changed your hard drive key (In EEPROM) to his (He's a moron cause he thought you could on-the-fly edit the hard drive key, but the data he saw was actually the EEPROM...). It should work, in concept unless he fucked something else up... I still can't believe he was stupid enough to use an On-The-Fly Edit EEPROM with an EEPROM utility and thought it had something to do with the hard drive... He thought if you put in the hard drive the key it showed was the key the hard drive currently was locked with... Edit: Oh just noticed - yes if you do get back the key from your original hard drive and relock it with the one he put on your Xbox, it should work. |
this guy doesn't know wtf he is talking about.
Post by: Sottilde on September 21, 2003, 05:01:00 PM
Post by: MrSelfDestruct on September 21, 2003, 05:10:00 PM
I showed this thread to the guy who was doing my installs, and he was REALLY cool about it. He actually took the modchip out of his xbox, and put it in mine.
He said that the HDD is now installed, and working fine. Ill probrably be picking it up on wednesday. Thanks for all the help guys.
Post by: BCfosheezy on September 21, 2003, 05:13:00 PM
| QUOTE (Sottilde @ Sep 21 2003, 08:01 PM) |
| Okay, so it might be possible I'm wrong about that. Still, just repeat what I said, but rather with your friend's hddkey.txt . Yeah, you're right. Luckily, you know what EEPROM it was set to. There's still hope - use your friend's EEPROM to get yourself up and running. Better yet, you could just steal his drive |
ok dude.... he can't use that txt file because he can't boot his xbox to run configmagic to set it to that..... what part about that don't you understand? it DOES NOT BOOT anymore. Then only way/s it will are if he used a drive that was locked with the key he programmed the eeprom with. The only problem with that is: he used a key he thought he got from the 120 gig.... only it wasn't locked so he couldn't have. So unless he can figure that one out himself that idea is out of the picture.
The only other way is to boot a bios that does not check for the hddkey unless the drive is locked and needs unlocked. This way you can boot unlocked drives. He can't flash the tsop so his only other way is........ MODCHIP. Why is this so hard for you guys to understand?
Post by: Sottilde on September 21, 2003, 05:23:00 PM
| QUOTE |
| ok dude.... he can't use that txt file because he can't boot his xbox to run configmagic to set it to that..... what part about that don't you understand? it DOES NOT BOOT anymore. Then only way/s it will are if he used a drive that was locked with the key he programmed the eeprom with. The only problem with that is: he used a key he thought he got from the 120 gig.... only it wasn't locked so he couldn't have. So unless he can figure that one out himself that idea is out of the picture. The only other way is to boot a bios that does not check for the hddkey unless the drive is locked and needs unlocked. This way you can boot unlocked drives. He can't flash the tsop so his only other way is........ MODCHIP. Why is this so hard for you guys to understand? |
Wow, dude, are you english, or retarded?
Remember the days BEFORE configmagic? When we had to do stuff ourselves? That's where you go grab hddunlock. Oh, but if you had read my previous posts, you would've known that. Ha.
You can unlock the drive through your computer... Think about it.
Sottilde
Post by: exiled350 on September 21, 2003, 06:13:00 PM
| QUOTE (BCfosheezy @ Sep 22 2003, 01:48 AM) | ||||||||
Pop your 8 gig back in and it will unlock it allowing u to boot. This means that your eeprom didn't change. It doesn't calculate on the fly... otherwise there'd never be a problem of people flashing the wrong thing to their eeprom... it'd just DO IT ON THE FLY LOL. That doesn't happen. It's a static value and that's that. |
no fucking shit the eeprom doesnt change, no one said that it did. you probaly dont even know what eeprom stands for do you? even if you were stupid the rom part should tip you off that it cant change without work. point is i have two hard drives with diffrent keys, both work. something at boot time takes the info in the eeprom and info from the hdd and generates a key, that key is what the hdd is locked with. therefore with liveinfo and the eeprom dump you can generate the correct key for the hard drive and lock it. end of story.
Post by: BCfosheezy on September 21, 2003, 06:29:00 PM
| QUOTE (exiled350 @ Sep 21 2003, 09:13 PM) | ||||||||||
no fucking shit the eeprom doesnt change, no one said that it did. you probaly dont even know what eeprom stands for do you? even if you were stupid the rom part should tip you off that it cant change without work. point is i have two hard drives with diffrent keys, both work. something at boot time takes the info in the eeprom and info from the hdd and generates a key, that key is what the hdd is locked with. therefore with liveinfo and the eeprom dump you can generate the correct key for the hard drive and lock it. end of story. |
Calm down junior. First of all since we agree that electronically erasable programmable read only memory doesn't change.
then we should note that it sends 1 key out at boot. It is programmed with 1 key to unlock the hard drive. So, each hard drive has to be locked with the same key that the eeprom has in order to be unlocked. That only makes sense. I don't appreciate the fact that you cursed at me. I also don't care that you have 2 hds with different keys and they both unlock.... if I saw your set up I could explain why. I have not provided any false information here. I wouldn't take a joke this far. Don't question me any more on this stuff. I won't provide false information unless it's a joke... and this is not a joke. I don't give help unless I'm sure about it... unlike yourself.
Post by: BCfosheezy on September 21, 2003, 06:33:00 PM
| QUOTE (Sottilde @ Sep 21 2003, 08:23 PM) | ||
Wow, dude, are you english, or retarded? Remember the days BEFORE configmagic? When we had to do stuff ourselves? That's where you go grab hddunlock. Oh, but if you had read my previous posts, you would've known that. Ha. You can unlock the drive through your computer... Think about it. Sottilde |
HAHAHA nice try at a putdown. Anyways, what good is unlocking his stock hd going to do anyways? (It's the only drive that could possibly be locked so I guess that's what your stupid ass is talking about.) He doesn't have his tsop flashed nor a modchip so he can't boot an unlocked hard drive. As a matter of fact I think you might be somewhat retarded.
Post by: Sottilde on September 21, 2003, 06:45:00 PM
The point is to get his Xbox running - whether it be with the 8gig or the 120 gig.
Post by: BCfosheezy on September 21, 2003, 07:02:00 PM
Post by: Sottilde on September 21, 2003, 07:12:00 PM
Post by: MrSelfDestruct on September 21, 2003, 07:29:00 PM
Post by: exiled350 on September 22, 2003, 08:57:00 AM
| QUOTE (BCfosheezy @ Sep 22 2003, 03:29 AM) |
| Calm down junior. First of all since we agree that electronically erasable programmable read only memory doesn't change. then we should note that it sends 1 key out at boot. It is programmed with 1 key to unlock the hard drive. So, each hard drive has to be locked with the same key that the eeprom has in order to be unlocked. That only makes sense. I don't appreciate the fact that you cursed at me. I also don't care that you have 2 hds with different keys and they both unlock.... if I saw your set up I could explain why. I have not provided any false information here. I wouldn't take a joke this far. Don't question me any more on this stuff. I won't provide false information unless it's a joke... and this is not a joke. I don't give help unless I'm sure about it... unlike yourself. |
so basicaly what you are saying, is that the eeprom has only one key and that key is the only key for that xbox. in keeping with this, ms would have to pay a whole lot of people to sit around and generate keys for the hdds, then generate the eeprom image with this key, flash the eeprom, and finaly makesure that the correct hdd makes it in to that box. this seems like an awful waste of time and money. wouldnt it make more sense to create an alogrithm that takes, say, the s/n of the xbox and the s/n of the hdd plus some other factors, and generates a key? now if this was true the box could come along the line with the eeprom already flashed, then they could pull up the image (via barcode on bottom) and lock a hdd from a pile (using the afformentioned alogritm and eeprom image) and set it in the box. this process could be completly automated and elimante any chance for the wrong hdd to end up in the wrong box. with fair confidence i can say that team assembly's liveinfo replacates this alogrithm allowing you to generate the same key that would have been used at the factoy if your hdd had been in that pile, therefor allowing a forigen hdd to work as if it were stock.
Post by: BCfosheezy on September 22, 2003, 10:26:00 AM
News: UNLOCKING XBOX HDD - Source Code Released !!!!!
This is the FULL source code that will unlock any locked XBOX hdd!!! (Provided the eeprom contains the correct HDDKEY that this drive was locked with of course..)
here is a link to that page just so you can see.
Don't you think that it would just read the serial number and calculate the password if that were possible??? or did UNDEAD from teamassembly just feel like making it difficult?? no that would defeat the purpose of his program.
(I've been reading about LiveInfo and it does detect the serial and model #'s from a hd locked with configmagic. It does not say anything about MS locked hds. They do not use the same method of calculating the password to lock with.)
Don't post again until you prove yourself. You are clearly wrong about what you say so I don't expect you'll be posting again.
Post by: exiled350 on September 22, 2003, 10:48:00 AM
| QUOTE |
| The OEM bios generates the unlock key on the fly. That is it generates a unique key or password which is dependant upon several things. This password is generated by looking at your Xboxs unique serial number, configuration, revision level and the information obtained from the currently installed hard drive itself. |
Whats up now?
Post by: BCfosheezy on September 22, 2003, 12:57:00 PM
| QUOTE (exiled350 @ Sep 22 2003, 01:48 PM) | ||
| aperaently you didnt even read what i said just like the other posts. i never said that liveinfo unlocks or locks or anything of the sort. i ran it and it with my eeprom and 2 diffrent hdds and it gave me 2 diffrent keys, i locked both hdds with their respective keys that it gave me. both hdds work in the xbox, the eeprom was never changed. explain to me how the eeprom could have a key for a hdd that it had never seen before now. *edit* look here http://www.xbox-scen...es/lock-hdd.php
Whats up now? |
I've read every one of your posts very carefully. Sometimes 2 and 3 times because they don't make much sense normally.
Apparently it is you that has not been reading MY posts because that is exactly what I just got done saying. I really don't know why you are still arguing with me about this. I solved the guy's problem. He fixed his box with my advice and is probably playing it right now but you still want to argue about how liveinfo does this and the eeprom does this and then completely change what you say after I prove you wrong.....
I want to clarify a few things tho because I challenge you on them and you never respond. 1. I want to know what you think is going to happen if you take 1 xbox hd that has been locked and then put it in another xbox.
2. I want you to break down exactly what you're disagreeing with me on because you tried to tell me that the eeprom does on the fly calculations (I guess you just worded that wrong because I know you don't think that an eeprom can calulate anything.)
| QUOTE |
| i think the way it works is the eeprom is used to calc a password on the fly using several things inc the hdd serial and xbox serial. |
Also I got a kick out of this:
| QUOTE |
| you have to use liveinfo with your eeprom that should have been extracted before you started. then liveinfo calculated the password to lock the new hdd with. theroeticaly if you have the eeprom from the broken box you could get the key back from the orig hdd and relock it with the right password. |
He knows what the eeprom said because he changed the hdd key to the value in his 120 gig. It didn't boot.
Anyways I now understand exactly what you're saying. I don't believe it but I understand. I won't argue anymore because honestly that's not the way I was told but it makes sense.
Post by: exiled350 on September 22, 2003, 01:19:00 PM
| QUOTE |
| This means that in order to upgrade your hdd, your new hd has to be locked with the same password as the one you're trying to replace. (that password is stored on the mobo on the eeprom) |
#2
| QUOTE |
| no it doesn't calculate anything on the fly. They are all set values. Sorry junior. The hd password stays static. If the eeprom password changed according to those other variables then the xbox would not be able to unlock it upon boot genius. |
#3
| QUOTE |
| the eeprom contents because that's where the password is stored. |
#4
| QUOTE |
| It is programmed with 1 key to unlock the hard drive. So, each hard drive has to be locked with the same key that the eeprom has in order to be unlocked. |
so that is 4 documented places that you said that the hdkey is stored in the eeprom and it is static. according to an article on this site
| QUOTE |
| The OEM bios generates the unlock key on the fly. That is it generates a unique key or password which is dependant upon several things. This password is generated by looking at your Xboxs unique serial number, configuration, revision level and the information obtained from the currently installed hard drive itself. |
which is exactly what ive been saying this whole time. but apperantly you have some sort of superiority complex and cant see your way out of your own ass. so it is you who should stop posting and maybe save what ever dignaty you have left.
Post by: BCfosheezy on September 22, 2003, 02:31:00 PM
Post by: exiled350 on September 22, 2003, 05:54:00 PM
| QUOTE (BCfosheezy @ Sep 22 2003, 09:57 PM) | ||||
| I want to clarify a few things tho because I challenge you on them and you never respond. 1. I want to know what you think is going to happen if you take 1 xbox hd that has been locked and then put it in another xbox. 2. I want you to break down exactly what you're disagreeing with me on because you tried to tell me that the eeprom does on the fly calculations (I guess you just worded that wrong because I know you don't think that an eeprom can calulate anything.)
Also I got a kick out of this:
He knows what the eeprom said because he changed the hdd key to the value in his 120 gig. It didn't boot. Anyways I now understand exactly what you're saying. I don't believe it but I understand. I won't argue anymore because honestly that's not the way I was told but it makes sense. |
ill clarify it just for you and ill even spell it out slowly so you can understand.
1. the xbox cant unlock the forigen hdd because the key is calculated using diffrent values.
2. the eeprom cant caluclate shit, i never said it could. i said that certian values contained in the eeprom were used in conjunction with other factors (hd serial #) by the kernel/bios at boot time to generate the key to unlock the hdd.
take an eeprom and find me where it is clearly labled hdkey and it is a fixed value. if the guy that was orignaly having this problem did the swap correctly then it would have worked. i did it according to BaD_HeX's guide and it worked perfect. if you want proof of how it all works dl the source libs from team-assembly, you can see how the key is generated for your self. i am through with this thread and will no longer post to it.
Post by: RiceCake on September 25, 2003, 03:09:00 PM
As for this whole HD key thing - sorry, I gotta 'read-up' on it myself. I didn't know it caused some sort of generation or whatever. I was trying to do the right thing but kinda got fucked up. Judging by how this guy originally tried his install he hot-swapped the drive into his XBox and thus getting the right (Generated) key through ConfigMagic.
I'm probably wrong though.
Paece out then...