Print

[mtl_m2]

Hi,

I tried to restore original FW to my drive, since I have never connected my modded 360 to LIVE (=not banned) and I thought to take a gold membership for one month to try it out.

So here is what I did:

Modded my Hitachi drive with "Birdy Hitachi friendly Flasher with Xtreme 2.0" about a year ago. Worked fine..

Today I tried to restore my drive to its original condition with "C4EVA iXtreme1.4" restore.bat
After:
 "Restoring 11/11 Sector 90005000 (Stealth Data and Code)"
  Checking Restored Firmware...
  Done"  restore.bat closes.

I hook the drive to my 360, download new updates.
Originals work OK, and just for the hell of it I insert a backup (my only backup btw.) and it boots and starts the game.

I hook the drive back to computer, read the firmware with 360FwTb.exe and I compare it to backup of my  original firmware I took before first MOD. and it is 1:1 same.

What am I missing here? Why my 360 still boots backups?  (IMG:style_emoticons/default/uhh.gif)

Please advice



MTL_M2

[PieOPah]

Did you buy your XBox brand new or second hand? Possible that you have bought a premodded box?? Has it been sent back anywhere for repair? It is possible that it has been 'replaced' instead of fixed!

[cypher21]

QUOTE(PieOPah @ Jan 21 2008, 09:31 AM)

Did you buy your XBox brand new or second hand? Possible that you have bought a premodded box?? Has it been sent back anywhere for repair? It is possible that it has been 'replaced' instead of fixed!

did you even read his post? He said he flashed it, and then restored. But it still boots backups after restoring.

@TS: Do you still have the dumped original firmware? If so, try restoring it with Toolbox. I've got better experience with restoring with toolbox then with the batchfiles. It seems that your drive is not restored completely

This post has been edited by cypher21: Jan 21 2008, 11:40 AM

[Hercules Man]

QUOTE(cypher21 @ Jan 21 2008, 12:40 PM)

did you even read his post? He said he flashed it, and then restored. But it still boots backups after restoring.

@TS: Do you still have the dumped original firmware? If so, try restoring it with Toolbox. I've got better experience with restoring with toolbox then with the batchfiles. It seems that your drive is not restored completely

did you even think about the possibility that his original firmware that he restored might be a modded firmware. simple solution really is load in your "so called original firmware" into toolbox and see what toolbox says.



H MAn

[rb8720]

Your easiest solution is to download virgin firmware for your drive and revision, Insert your dvd key and reflash the drive.  That way you know that it have original firmware on it. I ahve had to do a couple this was cause I cuoldn't get restore.bat to work.

[cypher21]

QUOTE(Hercules Man @ Jan 21 2008, 05:19 PM)

did you even think about the possibility that his original firmware that he restored might be a modded firmware. simple solution really is load in your "so called original firmware" into toolbox and see what toolbox says.
H MAn

i'm not replying to start flaming, but restoring a hitachi does NOT require original firmware, and after reading his opening post you could have figured out he used the BATCH files to restore his firmware, and did not flash his original firmware back

[Hercules Man]

If he dumps the current firmware and toolbox says it is stock firmware, and it is still booting backups, then something is messed up with his restore somwhere ?


H MAn

[podger]

The hitachi restore batch files only write a small number of sectors the 64 sectors on the 256kb flash

The restore.bat with 1.4 will restore sectores that 1.4 modifies. As it's a much newer version there are probably more sectors modified by the 1.4... Also, it's by a different author, so there could well be different sectors modified by Birdy, than by the current 1.4....

go with cypher21 advice and open you orig.bat form last year in Tool box. Click

Tools > Direct Drive Flash ( GDR Only ) > Differential Flash (Patch)

click > Read and Detect Differences

I'm sure you'll find that several of them are still different....

This post has been edited by podger: Jan 21 2008, 07:02 PM

[PieOPah]

QUOTE(cypher21 @ Jan 21 2008, 07:33 PM)

i'm not replying to start flaming, but restoring a hitachi does NOT require original firmware, and after reading his opening post you could have figured out he used the BATCH files to restore his firmware, and did not flash his original firmware back

I am completely new to this whole flashing scene so please excuse my ignorance... I was merely thinking that if he had bought a second hand machine then it was possibly already flashed meaning that the 'original' backup may already be a flashed version!!!

I was not aware that the hitachi doesn't need original firmware to restore it!

[mtl_m2]

QUOTE(podger @ Jan 21 2008, 07:49 PM)

The hitachi restore batch files only write a small number of sectors the 64 sectors on the 256kb flash

The restore.bat with 1.4 will restore sectores that 1.4 modifies. As it's a much newer version there are probably more sectors modified by the 1.4... Also, it's by a different author, so there could well be different sectors modified by Birdy, than by the current 1.4....

go with cypher21 advice and open you orig.bat form last year in Tool box. Click

Tools > Direct Drive Flash ( GDR Only ) > Differential Flash (Patch)

click > Read and Detect Differences

I'm sure you'll find that several of them are still different....

Hi!

Thanks to everyone for replys!

I bought the machine as brand new. So the firmware was originaly untouched.
I made the FW-backup with Birdy's flasher.

I did try "Differential Flash" with FW toolbox... I open 47.bin (virgin that comes with FW toolbox)
 change DVD key and start Differential Flash, after " Read and Detect Differences" it asks if I want to keep the keys allready on drive. I don't know why it asks that, I just changed the key. I click yes and it says that there are no differences between opened file and drive firmware.

BUT

I compared the virgin-fw with my original backup with hex-editor, DVD-key is offcourse dirrefent but there are allso difference between 0x4F81 - 0x4F87, does this address have something to do with keys?
I'm asking because Fw-toolbox indicates that only difference between virgin-FW & my drive is the key..


MTL



This post has been edited by mtl_m2: Jan 23 2008, 06:43 PM

[caster420]

QUOTE(mtl_m2 @ Jan 23 2008, 12:37 PM)

there are allso difference between 0x4F81 - 0x4F87, does this address have something to do with keys?

 

0x4F80 to 0x4F93 is the Hitachi 'Player' key, 20 bytes in length.  It is unique drive to drive (kinda like a BenQ serial) but doesnt appear to be reported or be of any importance to the console.  Obviously some bytes are similar to the original you're comparing with, just not all of the bytes.

 

Caster.

[mtl_m2]

QUOTE(caster420 @ Jan 23 2008, 08:06 PM)

0x4F80 to 0x4F93 is the Hitachi 'Player' key, 20 bytes in length.  It is unique drive to drive (kinda like a BenQ serial) but doesnt appear to be reported or be of any importance to the console.  Obviously some bytes are similar to the original you're comparing with, just not all of the bytes.

 

Caster.

Ok, so now I have compared a virgin-FW file to the firmware on my DVD-drive and they are 1:1 same. (Except keys) and it still boots game backups. Now I'm really confused.  (IMG:style_emoticons/default/blink.gif)


Now I tried to flash my drive with iXtreme1.4, I used flashix.bat, after doing some stuff it says
"PASS: Hitachi FW FLASHIX is 100 complete!", but now I read a direct drive dump with FW-toolbox and I compare it to the original FW-file, it's still original. Can't get my drive flashed anymore, it seems that I can read the flash chip but I cannot write it for some reason...

MTL

[notrain]

are you using a direct sata connection from the DVD Drive to the PC or are you using a SATA to USB Adapter?
Just hook it up directly via SATA and use the original Firmware that comes with toolbox + your key and flash that onto the drive, should solve your issues.

[pricemeista33]

Well all I can say to this here incident is that you're done dude.  If that drive is a Hit59dj, then you did not restore the drive at all.  I had this similar prob and the flash reported everything ok when it wasn't.  This will cause your drive to go into a loop process and never come out of restore mode.  Therefore you will experience a bricked drive if continuing to try and reflash.  The green center led will just blink rapidly and your drive will do nothing at all.  You will not be able to eject, no spin ups, no sound from the drive.  It will still show up in the bios but will not be detected in windows no longer.

So if I were you, I'd leave it be and just rock on with that unless you have a method to completely erase the controller chip on the drive's PCB WITHOUT REMOVING IT.

Mismatch keys will definitely brick and confuse your drive!  You state that you have a 1:1 replica of the F/W, BUT THE KEYS ARE DIFFERENT:O  Not a 1:1 then huh?

[caster420]

QUOTE(pricemeista33 @ Jan 23 2008, 02:53 PM)

You state that you have a 1:1 replica of the F/W, BUT THE KEYS ARE DIFFERENT:O  Not a 1:1 then huh?

He's comparing what is dumped from the drive to the originals provided with 360FWTB.  Of course the keys are different.

Caster.