|
New JungleFlasher v0.0.43b released - Old dump methods flawed! Possible Fix.
|
|
|
Donaldo
Senior Member
|
25. January 2009 @ 03:56 |
Link to this message
|
0.0.43_Beta first clean up
1. Added more messages ahead of lite-On-Erase to encourage users to have their DVDkey before erase
2. Fixed issues around Device Intro/ID for Lite-On, to account for delay in Lite-On controller
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
4. Added a check box on DVDKey32 tab to scan for "ScsiAdapter" IO ports
i. have filtered this to remove device that contain "SCSI" and "Promise"
ii. although port may be compatible with DVDkey32 they may not suppoer MTKFlash
5. Comport, enumeration has been improved,
i. now works in vista
6. Added multiple Key extractions with a comparison.
i. key will be dumped 6 times and compared for consistancy
ii. again the only way to be 100% key is correct is to spoof another drive with your key and test.
7. Added option in registry to disable enumerate
i. can diable com port, io port and windows drive enumeration
ii. this is debug functions to located potential issues
iii. some phanton drive for Nero and remote drives caused derive enum to fail....
8. fixed issue with spoofing Lite-On encrypted f/w from a previously spoofed f/w
i. key was always copied correctly
ii. spoofing was based on source type rather than what it was spoofed as
iii. this will mean you can put back a lite-on where it was replaced
iv. Serail data will very likely not be present in non-dummy f/w
9. Spoofing a Lite-On iXtreme will only copy serail info that is available
i. any serial info not present in source will mean ix1.5 serila will remain intact...
ii. this will occur when key, inquiry, identify are used as source and not a full dummy.bin
10. loading files in Vista issue resolved.... previously only opend from program working directory.
11. Intro and device ID after Lite-On-Erased fixed for working with Winbond Spi flashes
12. New Benq-Un-Lock keys add, extra 13 keys now support 62430 with Keys in B000 and C000
13. Improved Manual spoofing...
i. can manually edit keys
ii. can load key from 16 byte bin file ( key.bin)
iii. can manually enter barcode for Lite-On Spoof
iv. can load barcode from 96 byte bin file (inquiry.bin)
14. Drag and drop of firmware files to Source and Target tabs...
15. Mutual Exclusion to avoid multiple instance of JF being opened
16. Add Explorer Context menu support for bin.
i. user can right click .bin file and select "JF Source" or "JF Target"...
ii. this will start JF, if JF is not already running...
iii. if JF is running, Mutex will stop a new instance from being started, but will message the
existing instance with the action and the close..
|
|
Advertisement
|
|
|
|
|
Donaldo
Senior Member
|
25. January 2009 @ 04:15 |
Link to this message
|
Originally posted by Donaldo:
iv. only dummy.bin created in this way will include drive serial data
does anyone know what they mean by that ?? what data isn't properly included when you use just key.bin, inquiry.bin and identify.bin
cause that's what i did when i flashed my liteon drive. those were the only files i had i didn't even have the orig.bin from the drive. now they have a big warning message that comes up when you do it::
|
|
drybrdl
Junior Member
|
25. January 2009 @ 16:28 |
Link to this message
|
|
looks like theres supposed to be a drive serial aswell, i flashed my liteon already, does that mean the serial is lost?
|
|
aj123
Member
|
25. January 2009 @ 19:09 |
Link to this message
|
|
so are we supose to use the key,inquiry, and identify or the dummy one?
edit: where can i get new version from?
This message has been edited since posting. Last time this message was edited on 25. January 2009 @ 19:10
|
|
Donaldo
Senior Member
|
25. January 2009 @ 20:00 |
Link to this message
|
Originally posted by drybrdl:
looks like theres supposed to be a drive serial aswell, i flashed my liteon already, does that mean the serial is lost?
ya i think so ... it's quite ridiculous if ya ask me ... cause i don't remember it mentioned anywhere before... that there was unique information on the drive that wasn't covered by the key.bin, inquiry.bin, and identify.bin
assuming they mean the firmware had a serial # implanted in it... and god knows what else that they haven't mentioned. i can see the serial # being useful if ya send the xbox to microsoft for repair... which i don't plan on doing. i'm just wondering how this affects live and bannings...
|
|
Donaldo
Senior Member
|
25. January 2009 @ 20:03 |
Link to this message
|
Originally posted by aj123:
so are we supose to use the key,inquiry, and identify or the dummy one?
well from what they seem to indicate now ... none of those are what you want.
you need the "orig.bin" file which is a complete firmware dump from your xbox 360 drive. before it was ever flashed ....
|
|
aj123
Member
|
25. January 2009 @ 20:49 |
Link to this message
|
Originally posted by Donaldo:
Originally posted by aj123:
so are we supose to use the key,inquiry, and identify or the dummy one?
well from what they seem to indicate now ... none of those are what you want.
you need the "orig.bin" file which is a complete firmware dump from your xbox 360 drive. before it was ever flashed ....
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
seems to me that it wants us to use the dummy.bin file
|
|
Donaldo
Senior Member
|
26. January 2009 @ 01:06 |
Link to this message
|
Originally posted by aj123:
seems to me that it wants us to use the dummy.bin file
ya i see what you mean... i think they are referring to a dummy.bin that's created when you dump the original firmware from the drive.
cause i have a dummy.bin that was created using jungle flasher .26 using the "Load from dump files" option. It creates a dummy.bin in that directory based off those files...
when i try to load that dummy.bin into the latest version of JF here is the big warning it gives me ::
|
|
drybrdl
Junior Member
|
26. January 2009 @ 07:24 |
Link to this message
|
i asked the this question in Jungleflasher IRC room
"i flashed my liteone drive with jungleflasher .26 it works ok but ive checked the dummy file and the serial info is missing, will this cause any problems in the future".
This was my reply from admin
"potentially could be detected easier on XBL than one with it"
so im guessing its only a problem if u use XBL
|
|
aj123
Member
|
26. January 2009 @ 16:41 |
Link to this message
|
so how do u extract the firmware with the serial info in it?
|
AfterDawn Addict
|
26. January 2009 @ 17:09 |
Link to this message
|
|
Just used .43 today to flash another members LO.
You do just use the dummy it creates when it asks you to load the "orig.bin". All went smooth except writing and verifing was very slow. I found that a little odd.
Did you guys bother clicking the link to the quide provided when JF.43 first starts up?
|
|
drybrdl
Junior Member
|
26. January 2009 @ 17:28 |
Link to this message
|
Originally posted by bhetrick:
Just used .43 today to flash another members LO.
You do just use the dummy it creates when it asks you to load the "orig.bin". All went smooth except writing and verifing was very slow. I found that a little odd.
Did you guys bother clicking the link to the quide provided when JF.43 first starts up?
we are actually discussing the fact that dumps from jf .26 are missing the serial so clicking the link to the guide really doesnt help us
|
|
aj123
Member
|
26. January 2009 @ 18:40 |
Link to this message
|
|
so with .43, we are supose to use the "get key,create dummy.bin, open as source" button now?
|
AfterDawn Addict
|
26. January 2009 @ 18:48 |
Link to this message
|
Quote:
so with .43, we are supose to use the "get key,create dummy.bin, open as source" button now?
What's it say in the guide?
This message has been edited since posting. Last time this message was edited on 26. January 2009 @ 18:49
|
|
aj123
Member
|
26. January 2009 @ 21:32 |
Link to this message
|
Originally posted by bhetrick:
Quote:
so with .43, we are supose to use the "get key,create dummy.bin, open as source" button now?
What's it say in the guide?
no guide came up when i opened jf
|
|
Donaldo
Senior Member
|
26. January 2009 @ 21:38 |
Link to this message
|
Originally posted by aj123:
no guide came up when i opened jf
lol no guide comes up on mine either... instead it crashes with an error message and i have to hit "continue".
anyways i think this whole thing is a real mess... why wasn't it disclosed before that key.bin, inquiry.bin, and identify.bin are not adequate for flashing a drive?
and to find that out now... after i have already flashed my drive... making it impossible to recover any "serial" data...
thanks drybrdl for finding out that it could cause trouble on XBL... that is exactly what i was worried about ... =/
|
AfterDawn Addict
|
26. January 2009 @ 21:54 |
Link to this message
|
Word is it may just be a coding error (with the new jf itself) when the new jf tries to read the old jf lite on dump. It's still the same info.
If it were actually missing important serial info, don't you guys think that it would have been mentioned in the .43 news release. I'm pretty sure the people behind Jungleflasher wouldn't find out something as important as that, and then not say anything about it. There would have been news about it all over the different sites... just like the new iXtreme (which was suppose to help with stealth) back when Halo 3 came out.
This message has been edited since posting. Last time this message was edited on 26. January 2009 @ 22:03
|
AfterDawn Addict
2 product reviews
|
26. January 2009 @ 23:51 |
Link to this message
|
|
I don't think any info is actually missing. This is straight from DVDKey32 v0.8.1 "ver 0.8.1 -- Since the relaese of ix1.5, and the fact that orignal drives are now being erased, the
potential for lost keys has risen. It's been shown that the serial interface is prone
to minor errors. As parity is not used on the link these errors are impossible to trap.
DVDKey32 will now do multiple extractions of the DVDkey for comparision.
Hopefully, extracting the key multiple times should account for any glitches."
Looks like people using "serial" cables might have got a messed up key that looked good. That might be why JF .43 prompts you re-dump the key, inquiry, and identify. Or could just be an issue with the new program. I'm guessing all the info in the original dump is legit and shouldn't have a problem with xbl. I haven't heard anybody with a lite-on getting banned but I guess a ban wave hasn't rolled through.
This message has been edited since posting. Last time this message was edited on 26. January 2009 @ 23:52
|
|
aj123
Member
|
27. January 2009 @ 01:02 |
Link to this message
|
|
yup bhetrick that msg doesnt pop up for me, but i think the problem is just that i have my via drivers reinstalled since i only uninstall it when flashing and then that msg pops up, so im not worried about that.
but, i agree with u and think that important serial info probably hasnt really been lost and i don't think it increases the chances of getting banned.
|
AfterDawn Addict
2 product reviews
|
27. January 2009 @ 14:47 |
Link to this message
|
|
Here is the dump difference between JF .26 and JF .43 under the serial tab.
JF.26 -
0000: 44 36 30 38 43 47 38 33 - 35 39 31 30 30 30 34 53 D608CG835910004S
0010: 31 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 1 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
JF .43 -
0000: 44 36 30 38 43 47 38 34 - 32 38 30 38 30 30 57 4E D608CG84280800WN
0010: 30 20 20 20 FF FF FF FF - 38 4A 30 38 30 38 39 32 0 ....8J080892
0020: 31 37 47 32 31 34 58 58 - 41 30 FF FF 53 34 50 38 17G214XXA0..S4P8
0030: 41 31 35 30 30 30 30 30 - 31 33 38 38 31 32 00 00 A1500000138812..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
These are 2 Different Lite-ON drives using exact same dump process I have done. There might be some info missing if someone had used JF .26. Anybody have any additional info about this? If anybody has done Lite-ONs and used JF .26 and JF .43, can you please post the difference between the versions.
This message has been edited since posting. Last time this message was edited on 27. January 2009 @ 14:58
|
|
Donaldo
Senior Member
|
27. January 2009 @ 14:55 |
Link to this message
|
Originally posted by aj123:
and i don't think it increases the chances of getting banned.
did you read the post by drybrdl where he asked the admin in the jungle flasher IRC room if it will affect XBL ??
and the guy responded that it can increase the chance for detection ??
do you think the people who wrote the software are lying ??
|
AfterDawn Addict
|
27. January 2009 @ 17:32 |
Link to this message
|
I flashed a Lite On yesterday. These logs are for the same drive. I dumped with JF.26 first. Here's the log:
Quote:
JungleFlasher 0.0.26 Beta
Session Started Mon Jan 26 13:17:05 2009
Found 10 I/O Ports.
Found 2 Com Ports.
Found 5 windows drives.
Found 1 CD/DVD drives.
Sending DVDKey request to I/O port 0x09F0 and COM1
................................
Serial Data OK! Key looks good
Your Key is: A17Bxxxxxxxx0E42
Key data saved to C:\Documents and Settings\Shome Urboobis\Desktop\keith\Key.bin
Sending Inquiry to I/O port 0x09F0
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S
0020: 37 34 38 35 30 43 41 30 - 41 31 44 36 30 38 43 47 74850CA0A1D608CG
0030: 38 33 39 38 31 31 30 30 - 48 4B 31 20 20 20 00 00 83981100HK1 ..
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
Inquiry String saved to C:\Documents and Settings\Shome Urboobis\Desktop\keith\Inquiry.bin
Sending Inquiry to I/O port 0x09F0
0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 44 36 30 38 - 43 47 38 33 39 38 31 31 ....D608CG839811
0020: 30 30 48 4B 31 20 20 20 - 00 00 00 00 00 00 34 37 00HK1 ......47
0030: 35 38 43 30 20 20 4C 50 - 53 44 20 20 20 20 47 44 58C0 LPSD GD
0040: 31 2D 44 36 53 32 20 20 - 20 20 20 20 20 20 20 20 1-D6S2
0050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00 ..
0060: 00 00 00 0B 00 00 00 04 - 00 02 06 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0080: 03 00 78 00 78 00 E3 00 - 78 00 00 00 00 00 00 00 ..x.x...x.......
0090: 00 00 00 00 00 00 00 00 - 02 02 00 00 68 00 00 00 ............h...
00A0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00B0: 20 20 00 00 ..
Identify String saved to C:\Documents and Settings\Shome Urboobis\Desktop\keith\Identify.bin
Sending Serial data request to I/O port 0x09F0
0000: 44 36 30 38 43 47 38 33 - 39 38 31 31 30 30 48 4B D608CG83981100HK
0010: 31 20 20 20 FF FF FF FF - 38 49 31 32 30 30 36 39 1 ....8I120069
0020: 31 37 42 38 31 34 58 58 - 41 30 FF FF 53 34 50 38 17B814XXA0..S4P8
0030: 39 31 39 30 30 30 30 30 - 30 33 36 31 37 32 00 00 91900000036172..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
I then did the dump again and then flashed with Jungleflasher .43 and here's it's log:
Quote:
JungleFlasher 0.0.43 Beta
Session Started Mon Jan 26 13:41:12 2009
Found 10 I/O Ports.
Found 2 Com Ports.
Found 5 windows drives.
Found 1 CD/DVD drives.
Sending DVDKey request to I/O port 0x09F0 and COM1
................ Serial Data looks ok, key returned: A17Bxxxxxx0E42
................ Serial Data looks ok, key returned: A17Bxxxxxx0E42
................ Serial Data looks ok, key returned: A17Bxxxxxx0E42
................ Serial Data looks ok, key returned: A17Bxxxxxx0E42
................ Serial Data looks ok, key returned: A17Bxxxxxx0E42
................ Serial Data looks ok, key returned: A17Bxxxxxx0E42
Extracted drive key matched 6 times.
Key data saved to C:\Documents and Settings\Shome Urboobis\Desktop\keith\jf43\Key.bin
Sending Inquiry to I/O port 0x09F0
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S
0020: 37 34 38 35 30 43 41 30 - 41 31 44 36 30 38 43 47 74850CA0A1D608CG
0030: 38 33 39 38 31 31 30 30 - 48 4B 31 20 20 20 00 00 83981100HK1 ..
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
Inquiry String saved to C:\Documents and Settings\Shome Urboobis\Desktop\keith\jf43\Inquiry.bin
Sending Inquiry to I/O port 0x09F0
0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 44 36 30 38 - 43 47 38 33 39 38 31 31 ....D608CG839811
0020: 30 30 48 4B 31 20 20 20 - 00 00 00 00 00 00 34 37 00HK1 ......47
0030: 35 38 43 30 20 20 4C 50 - 53 44 20 20 20 20 47 44 58C0 LPSD GD
0040: 31 2D 44 36 53 32 20 20 - 20 20 20 20 20 20 20 20 1-D6S2
0050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00 ..
0060: 00 00 00 0B 00 00 00 04 - 00 02 06 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0080: 03 00 78 00 78 00 E3 00 - 78 00 00 00 00 00 00 00 ..x.x...x.......
0090: 00 00 00 00 00 00 00 00 - 02 02 00 00 68 00 00 00 ............h...
00A0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00B0: 20 20 00 00 ..
Identify String saved to C:\Documents and Settings\Shome Urboobis\Desktop\keith\jf43\Identify.bin
Sending Serial data request to I/O port 0x09F0
0000: 44 36 30 38 43 47 38 33 - 39 38 31 31 30 30 48 4B D608CG83981100HK
0010: 31 20 20 20 FF FF FF FF - 38 49 31 32 30 30 36 39 1 ....8I120069
0020: 31 37 42 38 31 34 58 58 - 41 30 FF FF 53 34 50 38 17B814XXA0..S4P8
0030: 39 31 39 30 30 30 30 30 - 30 33 36 31 37 32 00 00 91900000036172..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Dummy bin file saved to C:\Documents and Settings\Shome Urboobis\Desktop\keith\jf43\dummy.bin
Loading DVDkey source file
Inquiry string found
Identify string found
DVD key found @ 0xA030 key is A17Bxxxxxx0E42
Firmware is a Lite-On or Benq Dummy OSIG: PLDS DG-16D2S 7485
Firmware type is: DVDKey32 extract
Lite-On-Erase NOT sent
Loading target file C:\Documents and Settings\Shome Urboobis\Desktop\ixtreme15\ixtreme15\ixtreme_1.5\ix15-liteon.bin
Target File MD5 hash is: d8aaa30797c7680109b395bc3a380d5f
Genuine Lite-On iXtreme 1.5 Final
Inquiry area found
Current DVD key is 55AA55AA55AA55AA55AA55AA55AA55AA
Firmware is a Lite-On encrypted iXtreme OSIG: PLDS DG-16D2S 7485
Firmware type is: iXtreme v1.5 12X
Loading Source File C:\Documents and Settings\Shome Urboobis\Desktop\keith\jf43\dummy.bin
Inquiry string found
Identify string found
DVD key found @ 0xA030 key is A17Bxxxxxx0E42
Firmware is a Lite-On or Benq Dummy OSIG: PLDS DG-16D2S 7485
Firmware type is: DVDKey32 extract
DVD Key copied to target
Inquiry string copied from Source to Target
Identify string copied from Source to Target
Serial strings copied from Source to Target
Target f/w saved as: C:\Documents and Settings\Shome Urboobis\Desktop\keith\jf43\Lite_CFW.bin
Sending Lite-On-Erase request to port 0x09F0
Drive returned Status 0xD0
...................
Serial flash found with Status 0x72
Sending Vendor Outro to port 0x09F0
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
Getting Status from port 0x09F0
SPi flash found with Status 0x72
Sending Chip Erase to Port 0x09F0
Writing target buffer to flash
Writing Bank 0: ................
Writing Bank 1: ................
Writing Bank 2: ................
Writing Bank 3: ................
Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Write verified OK !
Sending Vendor Outro to port 0x09F0
So unless I've missed something (I'm getting old and my eyes are messing with me), Jungleflasher .26 and Jungleflasher .43 read the same serial data. But I get that "serial data missing" message when I open the .26 dummy with .43.
So, like I said unless I've missed something, it appears that JF.43 just has a problem reading JF.26 data.
No one is saying the admin from the irc forum is lying. I'm sure it's true that if serial data is actually missing, then MS may be able to detect it.
But the question is... is there data truly missing or is it just a coding problem with JF.43 not reading the JF.26 dummy correctly?
This message has been edited since posting. Last time this message was edited on 27. January 2009 @ 18:17
|
AfterDawn Addict
2 product reviews
|
27. January 2009 @ 17:58 |
Link to this message
|
|
Hmmm... information in my first Lite-ON looks like it is missing compared to my second and yours bhetrick. I hope this doesn't cause a problem down the road with xbl. At this time MS is only doing challenge responses with the disc correct?
|
AfterDawn Addict
|
27. January 2009 @ 18:15 |
Link to this message
|
|
Yeah, it's hard to say. It does look like info is missing from yours. But with it being 2 different drives you can't be 100% positive whether it's missing or not. So it's a tough call whether to trust that drive and xbl.
|
|
Advertisement
|
|
|
AfterDawn Addict
2 product reviews
|
27. January 2009 @ 18:20 |
Link to this message
|
Originally posted by bhetrick:
Yeah, it's hard to say. It does look like info is missing from yours. But with it being 2 different drives you can't be 100% positive whether it's missing or not. So it's a tough call whether to trust that drive and xbl.
Since the Lite-ON has been erased, would there be a possibility on getting that serial data or am I just re-dumping the original info that im missing that I flashed... Just a thought but I have a feeling I can't get any new info
|
