Print

[holyniht]

i was thinking of a the least troubesome way to revert the drive back for a firmware upgrade without modifying the script. To have my drive read back as a hitachi, couldnt i just flash my original bin @ the following locations :
47flash e orig.bin 90002000 1000

47flash e orig.bin 9003D000 1000

Would i have to unstealth my drive 1st , flash, restealth, then restore?
or i could i just flash orig, then do garyopa restore, upgrade firm, then flash step 3 bin back @ those locations?

[langnao]

Unstealth, encrypt your original bin and flash to change your drive model back to default. Then stealth and proceed to whatever you wanna do. Just remember, any flashing to the drive, the respective firmware has to be encrypted first ...

For me, I would prefer to modify the respective scripts, easier ...

[holyniht]

i would like to edit the script aswell, but what exactly do i edit, thats what i dont know

[langnao]

QUOTE(holyniht @ Dec 6 2006, 11:37 AM)

i would like to edit the script aswell, but what exactly do i edit, thats what i dont know

Wait for garyopa new firmware and we will see. Basically, edit to remove the checking of drive model and just direct to the flashing portion for your drive keeping the rest of the script e.g error checking routines untouched ...

[myfranco]

There are still ppl with E66 errors.Carrying the topic to the first page.

[Dark_Neo]

I have a new motherboard that had a 59 drive, but mines a 46, of course with the fall update I got an E66, tried changing the model number values (and injected the key) but now I'm getting an E65. I'm going to restart my computer soon and dump the firmware again (if possible) to see what's wrong. I followed the directions in this thread perfectly as far as I know. Is there anything you can suggest to do/try?

I noticed when comparing the modded firmware (which is just the drives original firmware with the key + values changes) to the firmware from the motherboards original drive the second drive details bit is not at the same offset, is this normal?

[myfranco]

It seems that something went wrong.I assume you slipped over a couple of bytes and you changed the wrong bytes.E65 means your drive is in recovery mode now and needs to be reprogrammed.

[langnao]

The byte location of the drive model should be the same. If not, something is wrong. Are u using a hex editor that padded additional bytes as mentioned in one of the postings?

Anyway, do a dump of the present firmware and check what is wrong. May be able to fix ...

[Dark_Neo]

I'm using UltraEdit to hex edit the files, and I've never had any problems with it before. I can't dump the firmware, it's not being detected by Slax any more to get it into modeb, any suggestions on that? I have 2 original firmware files, one before I started any sort of modding, and the second before I tried getting the drive working with the new motherboard (after a restore) there's quite a few differences between those files. Also a compare between the second original and the modded one shows only the changes that should have been made.

Here's the diff (don't think there would be a problem posting this, it's only arbitary bytes):

CODE

Different between:
First file: "v59-faked-with-key.bin"
Second file: "original-new-key.bin"

------------------------------------------------------------------------

00002030 | 39 35                   | 00002030 | 36 34                   |
------------------------------------------------------------------------
000020D0 |             35 39       | 000020D0 |             34 36       |
000020D8 |                      36 | 000020D8 |                      35 |
000020E0 |       31       34       | 000020E0 |       37       37       |
------------------------------------------------------------------------
0003D498 |                   35 39 | 0003D498 |                   34 36 |
------------------------------------------------------------------------
0003D4A8 |    36       31       34 | 0003D4A8 |    35       37       37 |
------------------------------------------------------------------------
0003D518 |             39 35       | 0003D518 |             36 34       |
------------------------------------------------------------------------

Oh and in the original v46 firmware the second HL-DT-STDVD-ROM starts at 0x0003D484 but in the v59 firmware from the motherboards original drive it starts at 0x0003D4A0.

[Dark_Neo]

No-one have any ideas of what went wrong? Maybe a checksum problem?

[myfranco]

Have you un-stealthed the fw before proceeding ? that tutorial i wrote was tested a couple of times and nothing happened.However,i witnessed that some ppl slipped over a couple of bytes and i corrected them.
You better send it to someone who can reprogramme since there is nothing left for that hitachi.
Can you tell us what you have done after you flashed the hacked firmware?

[rca1]

1st time poster long time reader. Anyways I got a good one for you. I have a 360 v59 drive bricked. Got the replacment v32 drive with v40 fw and e66 with fall update. I sent the drive back and got it fixed to look like a v78. I got the drive installed and e66 still. Do you think the drive has to say v59 and no other type of FW revision?

[majik655]

QUOTE(rca1 @ Dec 12 2006, 04:28 PM)

1st time poster long time reader. Anyways I got a good one for you. I have a 360 v59 drive bricked. Got the replacment v32 drive with v40 fw and e66 with fall update. I sent the drive back and got it fixed to look like a v78. I got the drive installed and e66 still. Do you think the drive has to say v59 and no other type of FW revision?

yeah it must say 59   as that is what your original firmware was.  anything else there will not be original.

[langnao]

QUOTE(Dark_Neo @ Dec 12 2006, 06:35 AM)

I'm using UltraEdit to hex edit the files, and I've never had any problems with it before. I can't dump the firmware, it's not being detected by Slax any more to get it into modeb, any suggestions on that? I have 2 original firmware files, one before I started any sort of modding, and the second before I tried getting the drive working with the new motherboard (after a restore) there's quite a few differences between those files. Also a compare between the second original and the modded one shows only the changes that should have been made.

Here's the diff (don't think there would be a problem posting this, it's only arbitary bytes):

CODE

Different between:
First file: "v59-faked-with-key.bin"
Second file: "original-new-key.bin"

------------------------------------------------------------------------

00002030 | 39 35                   | 00002030 | 36 34                   |
------------------------------------------------------------------------
000020D0 |             35 39       | 000020D0 |             34 36       |
000020D8 |                      36 | 000020D8 |                      35 |
000020E0 |       31       34       | 000020E0 |       37       37       |
------------------------------------------------------------------------
0003D498 |                   35 39 | 0003D498 |                   34 36 |
------------------------------------------------------------------------
0003D4A8 |    36       31       34 | 0003D4A8 |    35       37       37 |
------------------------------------------------------------------------
0003D518 |             39 35       | 0003D518 |             36 34       |
------------------------------------------------------------------------

Oh and in the original v46 firmware the second HL-DT-STDVD-ROM starts at 0x0003D484 but in the v59 firmware from the motherboards original drive it starts at 0x0003D4A0.

Based on your earlier post, is it correct to say that your original drive is 59 and now you wanna replace it with 46? Or vice versa?

Yes, the second portion of drive model for 59 is at 0x003D4A0. Thus if you wanna change, you should follow it at this address. What you had shown above is correct for changing a 46 to 'look' like a 59 (modifying the 46 firmware)

Before you implemented the change, was the firmware flashed with xtreme 2.3? You need to do this else you will have problem with the checksum.

[rca1]

Thanks for confirming what I was thinking majik655. Now I have to send the drive back again.