xboxscene.org forums

Pages: 1 ... 3 4 [5] 6 7 ... 13

Author Topic: E66 Fix For Swapped Mobos/dvd Roms  (Read 404 times)

segaboys

  • Archived User
  • Newbie
  • *
  • Posts: 20
E66 Fix For Swapped Mobos/dvd Roms
« Reply #60 on: November 06, 2006, 12:57:00 PM »
well done myfranco!!!!

Last question before you go back to playing,

What would the steps be if I wanted flash my Hitachi V40 to fake itself as a Samsung, thats the Drive my Motherboard is married to.

I now have a Hitachi and no Samsung
Logged

myfranco

  • Archived User
  • Sr. Member
  • *
  • Posts: 359
E66 Fix For Swapped Mobos/dvd Roms
« Reply #61 on: November 06, 2006, 12:27:00 PM »
QUOTE(segaboys @ Nov 6 2006, 09:28 PM) View Post

well done myfranco!!!!

Last question before you go back to playing,

What would the steps be if I wanted flash my Hitachi V40 to fake itself as a Samsung, thats the Drive my Motherboard is married to.

I now have a Hitachi and no Samsung


Honestly i don't know what to do for samsung since i tried to fake v47 for v59 hitachi.However,in the previous posts there were some explanations.I'll have a look for samsung,try if it fits than i try to help you ok?
Logged

segaboys

  • Archived User
  • Newbie
  • *
  • Posts: 20
E66 Fix For Swapped Mobos/dvd Roms
« Reply #62 on: November 06, 2006, 01:09:00 PM »
If I changed the descriptions as below and create a fake-sam-e.bin

Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)

Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)

Would the following command update the description in the firmware?

46flash.exe H fake-sam.bin 90002000 1000 <---- Flash the first changed sector
46flash.exe H fake-sam.bin 9003D000 1000 <---- Flash the second changed sector

And in theory would I be able to change it back?

Thanks

Logged

myfranco

  • Archived User
  • Sr. Member
  • *
  • Posts: 359
E66 Fix For Swapped Mobos/dvd Roms
« Reply #63 on: November 06, 2006, 02:33:00 PM »
QUOTE
If I changed the descriptions as below and create a fake-sam-e.bin

Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)

Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)


Segaboys i believe you should change those info in the hitachi firmware than you should encrypt it.Finally you can flash with 46flash.exe

But the first part is a bit complicated
Logged

SCSI

  • Archived User
  • Newbie
  • *
  • Posts: 21
E66 Fix For Swapped Mobos/dvd Roms
« Reply #64 on: November 06, 2006, 02:44:00 PM »
This is great news. Thanks myfranco, langnao, and gary. Will do the same on my older 47DJ and keep my newer Hitachi as a backup.

This post has been edited by SCSI: Nov 6 2006, 10:46 PM
Logged

spydermixx

  • Archived User
  • Newbie
  • *
  • Posts: 15
E66 Fix For Swapped Mobos/dvd Roms
« Reply #65 on: November 06, 2006, 03:06:00 PM »
well done myfranco, glad to see you got it working! now all we need is a certifiable fix for the samsung->hitachi owners and we're all golden!!
Logged

segaboys

  • Archived User
  • Newbie
  • *
  • Posts: 20
E66 Fix For Swapped Mobos/dvd Roms
« Reply #66 on: November 06, 2006, 03:29:00 PM »
Samsung ----> Hitachi

Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)

Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)


DOES not work.... must be something extra cos the above fits in sweetly...

When I open the firmware in firmware tools it still comes up as a Hitachi firmware....

Windows detects my Hitachi as a Samsung Drive now....

Also just noticed, if you remove the SATA cable then XBOX boots up to dash (missed that one)
Plug in SATA while on and you get Error 66

Plan to roll back and try again....

Logged

langnao

  • Archived User
  • Full Member
  • *
  • Posts: 160
E66 Fix For Swapped Mobos/dvd Roms
« Reply #67 on: November 06, 2006, 04:05:00 PM »
QUOTE(myfranco @ Nov 7 2006, 01:57 AM) *

OK I'VE DONE IT !!!!

Story : Hitachi v59 got bricked with Birdy Flasher then we bought a Hitachi v47 , flashed and injected the key.It worked fine.After the fall update 360 was giving E66 Error since it was married with a hitachi v59 but there was v47 at that moment.

Solution :

1 - Flashed back to original Firmware (used restore.bat command in Garyopa 2.3 )

2 - Flashed with Garyopa 2.3 (thank you to Garyopa)

3 - Unstealthed the firmware with the encrypted original.bin :
47flash H orig-e.bin 90033000 1000 --->this is the very first original firmware.

4 - Hexedited original.bin and changed v47 information to v59 to make Xbox 360 return with the correct code:

saved the bin file as fake59 then encrypted with Firmware Toolbox 1.2

5 - Again with Garyopa's X-LG folder:
47flash.exe H fake59.bin 90002000 1000 <---- Flash the first changed sector
     47flash.exe H fake59.bin 9003D000 1000 <---- Flash the second changed sector
(Where H is the drive letter)

Turned 360 off.Plugged all the cable and played Splinter Cell Double Agent  (IMG:style_emoticons/default/biggrin.gif)
I want to thank to Garyopa and Langnao for their great contribution.

I believe this solution be a sticky topic since all these people who swapped hitachi to hitachi or hitachi to samsung or vice versa would need it in case they get E66 error


Glad it works out for u .... Thanks to all, garyopa, averian for contributing.

Just one question, u don't plan to stealth back the firmware?

Something happened similar to me. Was helping my brother to flash to 2.3 and the process hang after completing the 9 steps at 'Checking flashed version'. Pack up the box and forgetten to manually run the last 2 steps of stealth the firmware. Too lazy to open up again and probably waiting for the next release. Everything fine just unstealth that's all ... (IMG:style_emoticons/default/smile.gif)

QUOTE(segaboys @ Nov 7 2006, 06:00 AM) *

Samsung ----> Hitachi

Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)

Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)
DOES not work.... must be something extra cos the above fits in sweetly...

When I open the firmware in firmware tools it still comes up as a Hitachi firmware....

Windows detects my Hitachi as a Samsung Drive now....

Also just noticed, if you remove the SATA cable then XBOX boots up to dash (missed that one)
Plug in SATA while on and you get Error 66

Plan to roll back and try again....


Maybe try a MS28 as in your original drive could be a MS28 thus setting to MS25 will still fail ? ...
Logged

myfranco

  • Archived User
  • Sr. Member
  • *
  • Posts: 359
E66 Fix For Swapped Mobos/dvd Roms
« Reply #68 on: November 06, 2006, 03:33:00 PM »
@segaboy what about the second part of the fimware

QUOTE
3D49E (2 bytes) forewards version becomes "59"
3D4A8 (8 bytes) ver. build date becomes "06/01/24"
3D51C (2 bytes) backwards version becomes "95" taken from Garyopa


I hope it fits well in there too.

@Langnao you're right , i haven't done it on purpose.That machine would never be on live so i just left it unstealthed.I was afraid of breaking something  smile.gif
Logged

segaboys

  • Archived User
  • Newbie
  • *
  • Posts: 20
E66 Fix For Swapped Mobos/dvd Roms
« Reply #69 on: November 06, 2006, 03:46:00 PM »
QUOTE(myfranco @ Nov 6 2006, 10:40 PM) View Post

@segaboy what about the second part of the fimware
I hope it fits well in there too.

@Langnao you're right , i haven't done it on purpose.That machine would never be on live so i just left it unstealthed.I was afraid of breaking something  smile.gif


Yes I saw that, I have just rolled back....
I started replacing in the second section but they dont seem to match in size... also I cant encrypt the firmware anymore with the extra changes so something must be wrong...

Will keep messing

Does the Firmware toolkit do specific firmware checks so I can't encrypt a faked Samsung/Hitachi firmware

I am a bit of a Noob and would like to know the follwing...

When you flashing specific lines on the hitachi firmware, how do you know which section?
Eg. 46flash H orig-e.bin 90033000 1000
how do you calculate 90033000 1000

Is there a cmd I can use to dump the firmware I just modified, to check that I have patched it correctly?
Figured that one out :-)  memdump ... checked for full command in the bat file.

Thanks again for all the help.
Logged

garyopa

  • Archived User
  • Sr. Member
  • *
  • Posts: 410
E66 Fix For Swapped Mobos/dvd Roms
« Reply #70 on: November 06, 2006, 04:01:00 PM »
QUOTE(segaboys @ Nov 6 2006, 05:53 PM) View Post

Yes I saw that, I have just rolled back....
I started replacing in the second section but they dont seem to match in size... also I cant encrypt the firmware anymore with the extra changes so something must be wrong...

Does the Firmware toolkit do specific firmware checks so I can't encrypt a faked Samsung/Hitachi firmware


Use the old command prompt "firmcrypt" named "firm.exe" in our package to "encrypt" the faked firmwares.
Logged

myfranco

  • Archived User
  • Sr. Member
  • *
  • Posts: 359
E66 Fix For Swapped Mobos/dvd Roms
« Reply #71 on: November 06, 2006, 04:45:00 PM »
Well you have hitachi now and you can use Garyopa's FW.What you need to do is:

To encrypt the firmware , put your bin file in X-LG(garyopa's flashing folder).Say your bin file is segaboy.bin:

Firm.exe e segaboy.bin encrypted.bin

"e" is for encrypting.

To decrypt:
Firm.exe d segaboy.bin encrypted.bin    (Shorter filenames is better)

To know which sector to flash ,there must be 8 digits.Say we flash 2030, you type

"9002030"  but if it's more than 4 digits where you need to flash(like 3d000) you type
"9003d000"   in any case that 9000 thingy must be totally 8 digits.Keep in mind it must be always encrytped.


To dump original.bin or let's say whatever you flashed
memdump %1 12200 8 8000 firmware.bin     where %1 is the drive letter of hitachi.


In your situation , i believe you flashed one part but not the second part.Open an untouched hitachi bin file(verifying it's your version for hitachi) , encrypt it then flash the first part to its original state.After that you can modify another hitachi fw and you can flash those sectors you need to.
I have no idea what to do for the second part but i'll have a look and help you as much as i can.
Logged

segaboys

  • Archived User
  • Newbie
  • *
  • Posts: 20
E66 Fix For Swapped Mobos/dvd Roms
« Reply #72 on: November 06, 2006, 04:56:00 PM »
grr.gif  GAMEOVER

Replacing it in both places bricks the drive!!!!!!!!!


USB Connectivity kit will not find drive


Error 66   has changed to Error 65


Verified firmware before I rebooted to make sure changes were made....

Can't say I learnt anything new :-(

Logged

garyopa

  • Archived User
  • Sr. Member
  • *
  • Posts: 410
E66 Fix For Swapped Mobos/dvd Roms
« Reply #73 on: November 06, 2006, 05:37:00 PM »
QUOTE(segaboys @ Nov 6 2006, 07:03 PM) View Post

Replacing it in both places bricks the drive!!!!!!!!!
USB Connectivity kit will not find drive
Error 66   has changed to Error 65
Verified firmware before I rebooted to make sure changes were made....

Can't say I learnt anything new :-(


Hmm, you are sure you replaced the strings right and encrypted the firmware,
and flashed the two correct sectors?

Also the strings must match in both halves or the drive itself will be not bootup
correctly.

Also was this on a "Xtreme" version of firmware or your "Original" firmware,
in both cases you must also make sure the "checksum" is set to all ZERO's,
or the drive will boot-up into RECOVER mode and will not operate correctly.
Logged

langnao

  • Archived User
  • Full Member
  • *
  • Posts: 160
E66 Fix For Swapped Mobos/dvd Roms
« Reply #74 on: November 06, 2006, 06:17:00 PM »
Actually the second part is found at:
0x3D480 - 0x3D49F
0x3D51A - 0x3D539
Logged
Pages: 1 ... 3 4 [5] 6 7 ... 13
« previous next »