Jump to content


Photo

Error #6 After Locking With Correct Eeprom


  • Please log in to reply
11 replies to this topic

#1 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 21 June 2012 - 07:14 PM

Hi,

I did softmod my XBox using the hotswap technique, i used this tutorial as i had the same kernel and dashboard versions:
http://daleswanson.org/stuff/xbox.htm

It worked, so i tried the next step: use a larger HDD
So i put ConfigMagic on the drive via FTP, ran it and choose "Unlock drive" and "Create Backup Files"

I had the EEPROM on the E drive then, named EEPROMBackup.bin

But the problem now is that i did "Unlock drive", which i shouldn't.
When the XBox started i had an error #5

So i re-branded my XBOXHDM CD, with the EEPROM in it.
I managed to lock it, but then i had an error #6

I suppose ConfigMagic made the correct EEPROM? And i don't have any other XBox.
I heard about a virtual EEPROM, but mine does show the correct XBox serial number in LiveInfo?
Does the virtual EEPROM have the correct serial too maybe?

Can you help me?




I tried this too:
Used atapwd to unlock using "XBOXSCENE" and then reboot in option #3 to launch unlockhd and lockhd.
The commands succeed but say nothing about any success.

Also i saw something previously stating "XBOXSCENE", when i locked/unlocked the first time i think.

#2 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 21 June 2012 - 07:25 PM

If you are getting error 6 then you definitely haven't locked it with the correct eeprom.

Did you rename your eeprom file eeprom.bin in lower case before building the xboxhdm iso?
Did you select option 3, then type lockhd -a?

#3 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 21 June 2012 - 07:55 PM

Thanks for the reply.
I renamed it, put it in the linux folder and burnt it.
And yes, i used the third option and did "unlockhd -a" followed by "lockhd -a"

I saw that ConfigMagic comes with an eeprom.bin which is empty, maybe when i used "Lock" in the program, it did lock using the dummy eeprom.
Is that possible? (It's the only explanation i can see)

Edited by kwixbit, 21 June 2012 - 07:57 PM.


#4 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 21 June 2012 - 09:13 PM

I just saw i named it EEPROM.bin
Can that be the problem? As it had to be lowercase?

#5 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 21 June 2012 - 09:24 PM

Yes, it has to be lower case.

#6 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 21 June 2012 - 09:35 PM

The unlockx command show the password on top, so i suppose it's not related to the case of my eeprom file.

Edited by kwixbit, 21 June 2012 - 10:17 PM.


#7 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 21 June 2012 - 10:00 PM

I just did this:
Unlock using master password with atapwd
Unlock using unlockx

The comand said it unlocked the drive (which doesn't when not unlocking with atapwd)

However i still have the error #6 and unlockx says "Not lockable"

Edited by kwixbit, 21 June 2012 - 10:08 PM.


#8 shambles1980

shambles1980

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,092 posts
  • Location:wales uk
  • Xbox Version:v1.2
  • 360 version:v4.0 (jasper)

Posted 21 June 2012 - 11:05 PM

You need to Unlock And dissble with atapwd..
Unlock will only temporerealy unlock it. Dissable or remove lock "i dont remember what its called off the top of my head" has to be used after unlock with master password..

so unlock using master password,
then
Dissable using master password..

when the hard disk is unlocked use explorer360 to find all eeprom.bin files you can find on the hard disk.
Then you can either tell us where exactly you found them on the drive..
OR you can make a disk for each one and try and try again till you dont get eror 6..



#9 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 21 June 2012 - 11:44 PM

QUOTE(shambles1980 @ Jun 22 2012, 12:05 AM) View Post

You need to Unlock And dissble with atapwd..
Unlock will only temporerealy unlock it. Dissable or remove lock "i dont remember what its called off the top of my head" has to be used after unlock with master password..

so unlock using master password,
then
Dissable using master password..

when the hard disk is unlocked use explorer360 to find all eeprom.bin files you can find on the hard disk.
Then you can either tell us where exactly you found them on the drive..
OR you can make a disk for each one and try and try again till you dont get eror 6..


Thanks, i was able to browse again using x360explore.
So i searched for .bin files and found some on partition 4 (you can see the location on the image):
http://imagebin.org/217394

Only EEPROMBackup.bin gives a valid file, which does match my XBox serial number.
However when opened in LiveInfo the HDD section is not available, only the EEPROM section.

At the same location of EEPROMBackup.bin i can find a txt and cfg file with the same name.

Edited by kwixbit, 21 June 2012 - 11:46 PM.


#10 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 22 June 2012 - 05:25 PM

Well it seems my stock HDD stopped working...
Luckily i have a 80GB Seagate which seems to be compatible, which i tried to use in the XBox too by using the same method, which gave an error #6 also.

So, maybe i do it wrong, or the EEPROM is really incorrect.
How can i check if the EEPROM is the correct one?

Edited by kwixbit, 22 June 2012 - 05:25 PM.


#11 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 23 June 2012 - 01:15 PM

Anybody can help me?
Is there a way to verify the validity of an EEPROM, other than the serial?
Because i'm pretty sure it's the correct one.

#12 kwixbit

kwixbit

    X-S Enthusiast

  • Members
  • 11 posts

Posted 23 June 2012 - 07:01 PM

I managed to fix it by generating a HDD key (in option 1) and using the generated key with unlockx (in option 4). This time it worked.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users