Print

[BCfosheezy]

QUOTE (Sottilde @ Sep 21 2003, 08:23 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

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.

[Sottilde]

Dude, I don't think you have any idea what he's trying to do.  If he unlocks his stock HD and locks it with a key he can USE, he can boot from it.  Once he can boot from that, he can either unlock - lock his 120 gigger using ConfigMagic or his computer.  I quite obviously know you can't boot an unlocked drive with an unmodded box.

The point is to get his Xbox running - whether it be with the 8gig or the 120 gig.

[BCfosheezy]

ok... and I understand that. YOu're right that definitely would work too. (btw he already got it fixed by chipping it) The only problem with that is, he'd have to know what key his eeprom is locked with in order to have that work. He changed it to something. He HAD to have changed his eeprom value or his stock hd would still boot. ok so now with your theory you would think, well just lock a hd with the same key that he wrote to the eeprom. The only problem is, the 120 gig is locked with that key and it doesn't boot. He can't do it your way. I DO understand what the problem is but from what he previously said... it can't be done that way.

[Sottilde]

Course you know it's possible the guy botched locking the 120 gig... or it was unlocked.

[MrSelfDestruct]

well...it seems we have quite a lively debate here

[exiled350]

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.

[BCfosheezy]

First of all I'd like to start out with this reply by saying that your hypothesis on what would have to be done to have a unique hdd password stored in the eeprom is not true. It would not be that difficult but good try at making it seem that way. Also, you had a great idea on how the hdds get locked. That may be close to correct but what you said about liveinfo is false. It will not unlock a locked hdd unless you have... what??? the eeprom contents because that's where the password is stored. It says nothing about serial numbers. Give that idea up. As a matter of fact here's a excerpt from teamassembly that gets you started in the direction you need to go.
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.

[exiled350]

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 Xbox’s unique serial number, configuration, revision level and the information obtained from the currently installed hard drive itself.

Whats up now?

[BCfosheezy]

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 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 Xbox’s unique serial number, configuration, revision level and the information obtained from the currently installed hard drive itself. 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.

I guess you meant the value that is clearly labeled hdd key... not: hdd value used in conjunction with serial numbers to calculate a hdd key.

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.

[exiled350]

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 Xbox’s 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.

[BCfosheezy]

HAHA well if you knew who I was you wouldn't try to bitch slap me. Also, you didn't prove anyone wrong and I told his friend what to do to fix it and it worked so sit on that and spin. You didn't show me that it's not true. If you would have read you'd see I have sufficient evidence to back myself up. Also, you're acting like that ancient article by Opjose is grail. You're probably wrong on all counts and I'd like to meet you just to fuck your whole world up... but I'm a bigger man than that now. I don't have to take your dignity.

[exiled350]

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.) 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. I guess you meant the value that is clearly labeled hdd key... not: hdd value used in conjunction with serial numbers to calculate a hdd key. 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.

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.

[RiceCake]

Well whatever then, heh, I guess it works for you...

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...