Print

[techmob]

just to add, it does actually erase first but the actual flash message i get is


bank 0 - OK!

bank 1 - OK!

bank 2 - OK!

bank 3 - OK!

254582 write errors occured



one thing to add, is this drive was soldered when that was the only way to dump the firmware with the first hack, so not sure if thats a cause of this prob?

the firmware i have tried to flash is the firmware from my other Benq drive, but i noticed that my old drive the one with the write errors, the original rom-version for that is Benq-VAD6038-62430C



while the original one that comes with the xbox360 is  Benq-VAD6038-64930C



could that be a problem?

[Plug]

QUOTE(techmob @ May 3 2008, 02:32 AM)

just to add, it does actually erase first but the actual flash message i get is
bank 0 - OK!

bank 1 - OK!

bank 2 - OK!

bank 3 - OK!

254582 write errors occured
one thing to add, is this drive was soldered when that was the only way to dump the firmware with the first hack, so not sure if thats a cause of this prob?

the firmware i have tried to flash is the firmware from my other Benq drive, but i noticed that my old drive the one with the write errors, the original rom-version for that is Benq-VAD6038-62430C
while the original one that comes with the xbox360 is  Benq-VAD6038-64930C
could that be a problem?

Simple fix.

The reason your getting errors is becuse for some reason the first time around when the power went out
the drive wasnt fully erazed properly..

i would suggest you manualy enter the eraze command into dosflash v1.3 beta
1.4 beta of dosflash will give you a version mismatch when trying to eraze

the command you want to do is

dosflash e 7c00 1 a0 1 4 d8 0

replace the 7c00 with your internal port on your sata chipset that the drive is plugged into
you can get this from within windows or useing iprep then look into rben.bat to get your correct port then replace the 7c00 with that.

then once erazed you dont have to reboot your pc in dos just shut down your xbox360 and start it back up

then use the flash command

dosflash w 7c00 1 a0 1 4 c:\hacked.bin

remember to replace the 7c00 with your port number and remember to give the correct location where your hacked firmware is with your key added to it.

goodluck

and if this fails you can also try the badflash recovery method wich i know works 100%

[techmob]

thanks for that, it is encouraging that it can be fixed but i am having trouble understanding what you have said

this is the only the second time i have flashed a BenQ, first time was successful thankfully

but really really appreciate the heads up, will look into that asap

does it have to be spoofed at all?

drive 1 = Benq-VAD6038-62430C
drive 2 = Benq-VAD6038-64930C

just opened rBen and on line 25 i have a reference

Tools\dosflash w 8C00 1 a0 1 4 BACKUPS\%1\%2\BenQ-OFW.bin 0

so i imagine the port used will be 8C00 ?

QUOTE(Plug @ May 3 2008, 09:38 AM)

Simple fix.

The reason your getting errors is becuse for some reason the first time around when the power went out
the drive wasnt fully erazed properly..

i would suggest you manualy enter the eraze command into dosflash v1.3 beta
1.4 beta of dosflash will give you a version mismatch when trying to eraze

the command you want to do is

dosflash e 7c00 1 a0 1 4 d8 0

replace the 7c00 with your internal port on your sata chipset that the drive is plugged into
you can get this from within windows or useing iprep then look into rben.bat to get your correct port then replace the 7c00 with that.

then once erazed you dont have to reboot your pc in dos just shut down your xbox360 and start it back up

then use the flash command

dosflash w 7c00 1 a0 1 4 c:\hacked.bin

remember to replace the 7c00 with your port number and remember to give the correct location where your hacked firmware is with your key added to it.

goodluck

and if this fails you can also try the badflash recovery method wich i know works 100%

[OggyUK]

At the dos prompt from your boot device....

As you normally would for a BenQ drive.

C:/>

type cd tools

press return

you'll be at

C:/Tools>

type dosflash e 8c00 1 a0 1 4 d8 0

press return

follow the boot on/off proceedure to erase the drive.

Once erased, power down 360

WAIT 10 SECONDS FOR IT TO FULLY SHUT DOWN

One the 360 fans have stopped you know it has powered down.

then:

At C:/Tools>

type cd..

Press return

C:/>

fben xxxxxxx xxxxx (x's = the serial you used)

Should be fine



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

The reason you lost power was because you resent the mtk vendor command as the 360 was powering down after erasing, the 360 takes a little longer to power down once the firmware is erased.

[techmob]

i have tried the dosflash erase command and it erases ok!

but when i do the write command fBen etc it wants to erase again, which says erase ok !

but writing still gives me errors

let me just clear a few things up incase it is my stupidy we are overlooking here!

the original drive that came with the xbox is Benq-VAD6038-64930C, this was dumped and flashed with ixtreme 1.41 - all went well

the replacement drive i have is Benq-VAD6038-62430C (which isn't originally from this system)- i do  have the firmware for this drive (but it was dumped via a switch, i have also tried spoofing the original firmware to match the other original drive),  i also have the drive key needed from the other working drive

i have tried flashing the ixteme firmware created for the original drive into the replacement drive, thats how i am doing it

i know i have to spoof it now, but i can't even get it to write correctly

[techmob]

i can't get this to work lads  

i get
status 0x73
Erase OK!


but writing still gives errors..

how do you do a badflash recovery? is that lifting the chip out to reprogram?

[podger]

Are you certain you are using dosflash 1.3 and not 1.4

The bad flash recovery is what you are doing with power on/off with the via card...

If this is not working it's time to go old school and put the switch back on the board, like you did originally, this will absolutely put the driv ein bad flash mode as it remove power from the spi and make it appear like it's not there...


If you have the orig.bin from the drive, try putting that back first and alleast getting the drive to boot.... and then mod from scratch, at least this way you will have all the spoof/serial number/keys and wisely love lan etc... just for completeness

[podger]

Time to try the switch, while you are at it you try a different sata card, just in case you have an issue with the via card..

[podger]

I can't really see if the cuts have been reconnected properly or not, if they haven't then that would certainly cause you issues.... Have a look at the tutorial below, the image on page 3 is the interesting part for un-doing the damage...

http://caster420.360...038/vad6038.pdf

[podger]

I really don't think so... The traces that are cut remove power from the SPI and make the board think it not there, as a result the board goes into recovery mode which allows you to read and flash it....

From the image you took it looks like one of the tracks is re-connected bu the other isn't...

Just go ahead and reconnect the 2 traces as per the bottom image in page 3.... re-assemble the drive and give it another go soft flashing...

[techmob]

ok maybe everything isnt ok


the traces were joined and the drive flashed ok, and i do not get e65 anymore but the drive will not open..

it just wont eject?