Print

[Millenia1x]

im bout to try it with my hitachi spoofed as benq next week when i get home

This post has been edited by Millenia1x: May 31 2011, 12:35 AM

[iRaz]

Im now having a problem that whenever I power on my ck3 windows crashes.
If i disable 621 drivers it works but JF can not see my drive.
Anyone know a fix for this ?

[-Gadget-]

like i said in my last post, window will now not like the drive and wont see it or just crash ..
it because th efirmware is currupt
either do/try what nkxtc said
or try what i said, which was using dosflash in REAL dos .....

[Millenia1x]

using a benq spoofed as a hitachi this does not work,
 flash the benq back to stock firmware,
copy the hitachi key to the benq,
update,

it only says play dvd

[krizalid]

So, to understand this more clear.

I can just unspoof the drive and have the correct key and it will update just fine?


Example:


Console with a LiteOn spoofed as hitachi79 on 12625,


replace LiteOn with Samsung MS28 using correct key, no spoofing; update to 13146 = good!


Than put back the LiteOn back and be ok with it except for live since Firmware is inferior to what dash expects.



What about unspoofing the LiteOn and leaving the LiteOn with the correct key and update?


This is great to hear!! Cheers.

[danthaman673]

QUOTE(krizalid @ Jun 4 2011, 06:17 PM)

So, to understand this more clear.

I can just unspoof the drive and have the correct key and it will update just fine?
Example:


Console with a LiteOn spoofed as hitachi79 on 12625,
replace LiteOn with Samsung MS28 using correct key, no spoofing; update to 13146 = good!
Than put back the LiteOn back and be ok with it except for live since Firmware is inferior to what dash expects.
What about unspoofing the LiteOn and leaving the LiteOn with the correct key and update?
This is great to hear!! Cheers.

Un-spoof with ORIGINAL Firmware! and it should be fine (From what I hear anywayz. I haven't had need to try yet myself) as for future updates beyond this one, it may come back to haunt, but I doubt it's likely...



Hope this helps/Dan

[zetecblack]

QUOTE(Millenia1x @ Jun 4 2011, 01:01 AM)

using a benq spoofed as a hitachi this does not work,
 flash the benq back to stock firmware,
copy the hitachi key to the benq,
update,

it only says play dvd

If its spoofed as hitachi you sould be able to just update and it wont touch the drive.

[blackopsftw]

Just tried this, has a BenQ spoofed as a Liteon, so went back to BenQ OFQ, updated dashboard and there we have it, a newly updated BenQ F/W.

Flashed back to ix-lt1.1, all good.

[hus13]

Ok let me get this straight:

I have a Benq spoofed as Liteon.

Lets say Liteon Key is 12345 (LITEON_12345) And the Spoofed Key is the same (obviously) [BENQ_12345(SPOOFED)]

The Benq Original Key is ABCDE
The Spoofed key is 12345 [BENQ_12345(SPOOFED) as Liteon]

So I flash OFW with the Original Benq Key i.e. ABCDE [BENQ_ABCDE_OFW] and update the console?

The console will be unable to play anything since the drive is a mismatch - correct?

Once updated, I flash LT v1.1 (or LT V2.0, once released) Benq without spoofing the key
back to 12345 (Liteon). [BENQ_ABCDE(UPDATED TO New OFW) + LT V1.X OR 2.0] and place it in
my console and all should work?

Will ABCDE become the New Key 'married' to the console?

My new CFW Key+Drive will look like this:

BENQ_ABCDE_LT+V1.x rather than BENQ_12345_LT+V1.x right?

And this in theory according to the first post should work on the console and play all but AP2.5 games if I were to use LTv1.1. Personally I'll wait until 1.9 or 2.0 but I wanted to know if I had grasped this correctly.

Thanks.

[-Gadget-]

spoofing and keys are totally different subjects..
the Key is set and is never changed
its the 'osig' string thats changed to fool the console in thinking its got a diferent drive ...

But when the firmware is spoofed into a difent model, it obvoiusly tried to flash that firmware to the drive which is the wrong firmware for the hardware
which is why it fails ...

but it seems that the 360 READS the drive osig string and flashes the firmware according to what it READS and not to what it as SET in its KV 'osig' string.

Mick ..

[TingedAce]

So it seems that upgrading while using the wrong hardware with the corresponding wrong OFW for that hardware, along with the correct key for the console results in a console that can boot originals.

This must mean that either
1. The 13146 dash doesn't care about matching OSIG with KV
2. The KV is updated to the different drive model

I'd be really surprised if it were the 2nd one, but surely doesn't take much to find out. If it is then it's a brilliant trick for anyone who never wants to be troubled with reburning ap2.5 discs ever again. i.e. put in a sammy with OFW, upgrade, put your liteon (or whatever) back with CFW and off you go.