Maximus-Garyopa XTRM-HITACHI v2.2 FwStealth

[vviruss]

helpe me!!!
My drive was flashed whit Birdy_Hitachi-LG_friendly_Flasher_v2.2_with_Xtreme_v1.3_and_2.0 mediacheck2_FIXED I restored it whit Maximus-Garyopa XTRM-HITACHI v2.2 FwStealth and now the drive works whith original FW but when i put it in mode B windows wont detect it.

[DarkDudae]

helpe me!!!
My drive was flashed whit Birdy_Hitachi-LG_friendly_Flasher_v2.2_with_Xtreme_v1.3_and_2.0 mediacheck2_FIXED I restored it whit Maximus-Garyopa XTRM-HITACHI v2.2 FwStealth and now the drive works whith original FW but when i put it in mode B windows wont detect it.

If you make a "restore", you get a 100% original firmware = No mode B.

You should have reflashed before turning off your computer and/or your console.

Greetings

[arch]

Today i decided to flash my drive with firmware v2.2. It was already flashed once by someone with FW V2.1.
First i ran Restore.bat from the V2.2 files. It ended up with 100% ok.
Then i flashed it with FLASH22S.BAT L 0697. In the Readme file it says that after the flash you end up with a folder (0697_
with 5 files:

---- key.bin   ---- DRIVE KEY /// DRIVE KEY
---- was.bin   ---- Your drive before FLASH
---- gdrXX.bin ---- The untouch original fw
---- XX_22.bin ---- The patched Xtreme22 fw
---- now.bin   ---- Your drive after FLASH!

The flash was 100% complete but i only have 4 files, the gdrXX.bin is missing. Is this o.k.?

I still have the folder of the first time flash and in that folder i got indeed 5 files.

[mcmanic]

worked fine on my just brough virgin 59 drive xbox360,

quick question though, does the 59b have it written as such on the dvd-drive?, or does it show up as as 59b on a 59 drive when you look at the rom version after extracting the firmware from the drive?

[buzzar]

Excellent, silky smooth, regards to Gary & Max

[McScruff]

1st post , thanks for this release

i have a 47 drive, i flashed a while back with the other release but it didnt detect my media (non pioneer) so i flashed with birdys media fixed one (as i wanted to test my backups with my non pioneer burner), then this came out so i restored with birdys then reflashed with this and its perfect

[rgoeke]

finaly it happens

1.restored to original
2.reboot
3.slax again modeb
4.windows, and flash22s.bat
after finaly done, 100% ... reboot, pluged back to 369;P.

now the disc tray won't open.
somewhile got error 64. and the d3 led goes flashing red.

when i press eject button and power button, the debug led/ in the middle flashes (like in modeb on first time).

i tried if i have a second chance, to do a bad flash recovery,
but now my 46dh doesnt recognized by dos & windows anymore, if the status (debug led) is flashing,
the system hangs and after 2 minutes, it' boots to winxp.

if than or else ... bricked ?

any chance to get it back to life ?

i read, have to iron the sst out, but my idea was than ... when i have to iron that sst out, it is easier to iron a nme
modchip in... will that work ?

[Xenn0X]

when using the restore.bat. it will reflash an orginal firmware of the correct drive with the original key from the original firmware?
so you get a non xtreme hacked drive right? or is it more advisable to use the original backup firmware file to revert it to original and then reflash it to 2.2?

[Wuthoqquan]

when using the restore.bat. it will reflash an orginal firmware of the correct drive with the original key from the original firmware?
so you get a non xtreme hacked drive right? or is it more advisable to use the original backup firmware file to revert it to original and then reflash it to 2.2?

Good point!!! Why not using the original RESTORE.BAT command from the distribution previously used to flash one's own drive? For example, in my case, I still have GaryOPA 2.1... and if upgrading to this "new" 2.2 version I would certainly use the restore.bat from 2.1 release, not the one included with this latest distribution.

[nSkuL]

yes, I have that doubt too... in case of having a drive flashed with gary-opa_2.1, is it better to restore with 2.1 restore.bat or this 2.2 restore.bat??

thanks.

[arch]

yes, I have that doubt too... in case of having a drive flashed with gary-opa_2.1, is it better to restore with 2.1 restore.bat or this 2.2 restore.bat??

thanks.

I used the restore.bat from 2.2 while my drive was flashed with 2.1.
My xbox works fine here.

[PaiNofDK]

hallo i are new in this.. where can i get this Maximus-Garyopa XTRM-HITACHI v2.2 FwStealth fil?

[stonersmurf]

hallo i are new in this.. where can i get this Maximus-Garyopa XTRM-HITACHI v2.2 FwStealth fil?

Not here, do not ask for firmware files or you will be banned!!

[Xenn0X]

just flashed a 59dj (june 2006) drive from a friend and works fine!

will reflash my 2.1 to 2.2 later. or maybe will wait till version with full stealth inc media stealth:)

[WarriorSan]

Today i decided to flash my drive with firmware v2.2. It was already flashed once by someone with FW V2.1.
First i ran Restore.bat from the V2.2 files. It ended up with 100% ok.
Then i flashed it with FLASH22S.BAT L 0697. In the Readme file it says that after the flash you end up with a folder (0697_
with 5 files:

---- key.bin   ---- DRIVE KEY /// DRIVE KEY
---- was.bin   ---- Your drive before FLASH
---- gdrXX.bin ---- The untouch original fw
---- XX_22.bin ---- The patched Xtreme22 fw
---- now.bin   ---- Your drive after FLASH!

The flash was 100% complete but i only have 4 files, the gdrXX.bin is missing. Is this o.k.?

I still have the folder of the first time flash and in that folder i got indeed 5 files.

@ GaryOPA / Maximus,

I'm also missing gdrXX.bin using Maximus-Garyopa_XTRM-HITACHI_v2_2_Stealth 8in1 with Revised bats but I got extra bin file called 47_22S.bin. Also 100% flash and working fine but ending up with these files:

---- key.bin   ----
---- was.bin   ----
---- XX_22.bin ----
---- XX_22S.bin ---- (Firmware with maximus stealth patch?)
---- now.bin   ----

Where is gdrXX.bin? THNX

[garyopa]

@ GaryOPA / Maximus,

I'm also missing gdrXX.bin using Maximus-Garyopa_XTRM-HITACHI_v2_2_Stealth 8in1 with Revised bats but I got extra bin file called 47_22S.bin. Also 100% flash and working fine but ending up with these files:

---- key.bin   ----
---- was.bin   ----
---- XX_22.bin ----
---- XX_22S.bin ---- (Firmware with maximus stealth patch?)
---- now.bin   ----

Where is gdrXX.bin? THNX

Not to worry, the only file you need to kept is the was.bin file, the rest don't matter, and the readme is just out of date in the naming of the files.

[zillionare]

Super great work Garyopa. gonna let the dust settle for a while longer before I do this one.

Gonna get some feedbacks first. then after I flash one I'll post back results. did the 2.0 that was bad and about shot myself for going first. 2.1 fixed it right up.

Congrats on this release!

Peace
zil

[klipseracer]

finaly it happens

1.restored to original
2.reboot
3.slax again modeb
4.windows, and flash22s.bat
after finaly done, 100% ... reboot, pluged back to 369;P.

now the disc tray won't open.
somewhile got error 64. and the d3 led goes flashing red.

when i press eject button and power button, the debug led/ in the middle flashes (like in modeb on first time).

i tried if i have a second chance, to do a bad flash recovery,
but now my 46dh doesnt recognized by dos & windows anymore, if the status (debug led) is flashing,
the system hangs and after 2 minutes, it' boots to winxp.

if than or else ... bricked ?

any chance to get it back to life ?

i read, have to iron the sst out, but my idea was than ... when i have to iron that sst out, it is easier to iron a nme
modchip in... will that work ?

I had a similar problem when i flashed form 1.3 to 2.1

I flashed it, 100/pass turned everything off, and my dvd tray stayed open. so i manually shut it, turned on the xbox blinking power led and no tray response.  i ended up having to open up my dvd tray, manually open the drive, pull the power plug on the back, wouldn't recognize by windows, but for some reason it closed likke 5 minutes after that when attempting to get the drive recognized. This is something that needs to be fixed IMO. I have a 47DJ and there are a few bugs that need to be wrinkled out still. I will not be flashing any more drives until this is all resolved. Keep up the good work. I'll help if anyone is interested in my problem.

[SCSI]

Great release. Working great. Now I wait for media steath.. 

[WarriorSan]

@ GaryOPA / Maximus,

I'm also missing gdrXX.bin using Maximus-Garyopa_XTRM-HITACHI_v2_2_Stealth 8in1 with Revised bats but I got extra bin file called 47_22S.bin. Also 100% flash and working fine but ending up with these files:

---- key.bin   ----
---- was.bin   ----
---- XX_22.bin ----
---- XX_22S.bin ---- (Firmware with maximus stealth patch?)
---- now.bin   ----

Where is gdrXX.bin? THNX

Not to worry, the only file you need to kept is the was.bin file, the rest don't matter, and the readme is just out of date in the naming of the files.

Thanks for the answer. Also I was using the 1.3 version before with media detection v2 from Geremia. And 1 game I burned on a Platinum disc because I run out of verbatims which played perfect. Now after using this firmware with the same media detection v2 it won't play the game anymore [verbatims still run fine]. How come?