Print

[OggyUK]

There's 4 via's to probe | The IC leg, I hardly think they would take this long to develop "epoxy over one via"

The fact its a new f/w revision completely suggests that the manner in which it operates or its structure, is different.

[fitsman]

The new liteon drive can't flash like the oldone if i manually add the serials(Lazer, pcb & cover) codes that it missing from dumping 4 files anyone can get with connectivity kit 3.

If there is anyone to know how i can flashed the new liteon drive.

[OggyUK]

QUOTE(fitsman @ Jun 10 2009, 05:49 PM)

The new liteon drive can't flash like the oldone if i manually add the serials(Lazer, pcb & cover) codes that it missing from dumping 4 files anyone can get with connectivity kit 3.

If there is anyone to know how i can flashed the new liteon drive.

That, is not this.

You just have data missing at 0x1ff00.

The drive will function fine without this data.

[MickRick]

Probably due to using the first Jungleflasher release. Try updating to the latest version.

[Reaper527]

QUOTE(BoNg420 @ Jun 10 2009, 10:43 AM)

Well they made this deal with liteon and moved on from Benq.

i don't think they "moved on" from benq, i think liteon actually acquired benq.

you are right though, ms is constantly trying to stop firmware mods, and its a never ending game of cat and mouse.

---edit---

http://www.emsnow.com/newsarchives/archive...ls.cfm?ID=12622

yeah, liteon and benq's optical division are one in the same.

This post has been edited by Reaper527: Jun 10 2009, 06:44 PM

[OggyUK]

QUOTE(MickRick @ Jun 10 2009, 06:41 PM)

Probably due to using the first Jungleflasher release. Try updating to the latest version.

JF has always dumped this data, and if the data isnt there to be dumped ... then ... it .. isnt .. present! Updating JF will not change this as its simply not there.

Many a refurb has come back without this data.

Wandering off topic anyway.

[carniver]

QUOTE(BoNg420 @ Jun 10 2009, 07:43 AM)

Think about it, they have tried so much in an effort to stop firmware modding, hitachi 78/79, epoxy on chips, new benq drive, new liteon drive.  All have failed to prevent it.  So what is their next trick up their sleeve?

I think they're heading to the right direction with the liteon. Make the process as painful and costy as possible, the hackers cannot afford this by themselves for very long. One day when the hackers have to set up PayPal accounts to collect donations, then they can get a court order to have paypal reveal the names of all the hackers.

For now they can remove the function to dump the key from their firmware?

This post has been edited by carniver: Jun 10 2009, 06:56 PM

[MickRick]

QUOTE(OggyUK @ Jun 10 2009, 06:51 PM)

JF has always dumped this data, and if the data isnt there to be dumped ... then ... it .. isnt .. present! Updating JF will not change this as its simply not there.

Many a refurb has come back without this data.

Wandering off topic anyway.

I think you'll find that it hasn't. The first release had a bug that failed to read this data and drives had to have the data entered manually with a hex editor.

[Ldngeez]

QUOTE(MickRick @ Jun 10 2009, 07:09 PM)

I think you'll find that it hasn't. The first release had a bug that failed to read this data and drives had to have the data entered manually with a hex editor.

I think you will find Oggy is  correct, the problem was never a "bug" in JungleFlasher.
It was actually a poorly written Guide giving incorrect instructions.(Team-Xecuters Guide)


This post has been edited by Ldngeez: Jun 10 2009, 07:23 PM

[MickRick]

Really? What was the poorly written information that caused JF to fail to save the info to the extracted files?

[OggyUK]

Taken from JF v043b readme (this is what T-X depict in their tutorial)

QUOTE

 3. Moved, build from dump files to DVDKey32 Tab and added warning.
     i. this function was for legacy support only, but some used it in main path
     ii. this is for creating a dummy from old dump files
     iii. dummy.bin from JF, Dosflash 1.7 or DVDkey 0.7 should always be used where possible.
     iv. only dummy.bin created in this way will include drive serial data

Feel free to dump a stock LiteOn, using JF v026, use the FirmwareTool32 \ Advanced \ Serial tabs and you'll see full 0x1ff00 data present.

Then, open the same dummy.bin in JF v0162 and you wont see the warning

If it was present on the drive to start with of course

[xboxmoddude]

QUOTE(Bazdoctor @ Jun 10 2009, 05:15 PM)

Buying some certain people out maybe. The xbox comes to mind.

Why not just mould the entire drive PCB into epoxy?

[run187]

QUOTE(vb_encryption_vb @ Jun 10 2009, 04:18 PM)

I've had the same issue, I think it's the latest version of jungleflasher though being stubborn, that's when I noticed it being a lil pissy from time to time. But power cycling the drive and hitting the device intro seems to work.

yeah jf can be pain sometimes i had problems flashing a new revesion tired my friends older one worked first time ,power ctvling and reboot of pc fixed other probem (after i tired every sata port possiblle every usb and every wire combo known to mam on the newer revesion )..

[-PK-]

Considering what they did with the hitachi 78/79, this drive's fw doesn't appear to be much of an issue.

QUOTE(xboxmoddude @ Jun 10 2009, 08:36 PM)

Why not just mould the entire drive PCB into epoxy?

Or forget the pcb all together.  Wire all of the components together in to a messy ball and submerge in epoxy.  Each drive would have its own unique ball of wires making things impractical for both parties.  (IMG:style_emoticons/default/tongue.gif)

[Djpj]

QUOTE(-PK- @ Jun 10 2009, 10:12 PM)

Or forget the pcb all together.  Wire all of the components together in to a messy ball and submerge in epoxy.  Each drive would have its own unique ball of wires making things impractical for both parties.