|
5 - kernel - HDD not locked (The retail xbox bioses require the hd to be locked)
When you upgrade your hard disk drive for one that is larger, you most of the times use a new hard drive that you bought in the shop. Now, when you put this hdd in your xbox and you try to boot up with your chip off. It gives you error 5. Why you ask? Well i will try to explain it simple.
The original (also called "Retail") hard drive is locked by MS. Why did they lock the harddrive?
Well if it wasn't it wouldve been more than easy (in the start of xbox hacking)
for hackers to change content on it. Thats why MS locks it. It is just a security measure.
This locking proces uses information thats on the motherboard. The "Lock" on a xbox hard drive contains information that is based on the harddrive itself and the motherboard it came with.
One thing that makes this clear: You can not change a retail harddrive with another one from an other not modded xbox. With every xbox there is only ONE i repeat ONE compatible harddisk drive. That is, if they are locked.
If you don't mod your xbox (tsop or modchips) you can not change harddrives. Not even from another xbox. However when your xbox IS modified you can change your harddisk for almost every other harddisk (thats UNLOCKED). This means that even when your xbox is modified, you can not just put another (retail) XBOX harddisk in your xbox. However some smart people made programs that can lock or unlock your xbox harddisk on the fly.
So when does the error occur? The only time this error should occur is when you boot up your xbox in original mode AND you have a harddisk in your xbox that is not yet locked. So now you ask what do i have to do to make your xbox work again?
Well the answer is pretty easy. Boot up your xbox with the chip on. Preferably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"
When it is "Done" just turn off your xbox. Disable your chip and try to boot in original mode. Now there should be no more error 5.
|
