-
Hi folks the maximus xtractor 360 toolbox for liteon and hitachi mode B is out and work like a charme .
(IMG:http://www.maximusgames.net/images/360xtractorreader.jpg)
Maximus xtractor official page for download the soft
CODE
---------------------------------------------------------------------
Maximus - 360 Xtractor Reader Beta 0.3
---------------------------------------------------------------------
Intherim Release, this functionallity will be added to Fw Toolbox soon
WHAT IS IT ?
----------
Graphical tool to allow read keys from Lite On / Benq Drives
It supports USB key dumping if using with an 360 Xtractor Tool
Also contains bonus feature as NO-SLAX ModeB command
Can work with 360 xtractor tool or other (homemade max323) adapters,
even rival tools are welcome
MAIN FEATURES:
---------
- Key reading on Liteon Benq Drives
- key.bin/identify.bin/inquiry.bin file generation
- Allow ORIGINAL / CLONE detection for 360 Xtractor Tool (R.I.P. D.France)
- BONUS FEATURE: Send ModeB command to All Hitachi Drives (even 78/79) NO SLAX REQUIRED
INSTALLATION:
---------------
- Unzip contents on the folder you like, make sure the folder has write permissions
since some small temp files could be generated by application on that folder
HOW TO USE:
------------------
- This application rely on Legacy Mode or IDE-SATA adapter to be able to send/receive
data from the drive, Legacy Mode it could or could not be supported by your PC Bios
once enabled the OS will see sata channels as if where regular IDE channels
- Once you setup Legacy Mode or IDE-SATA adapter you should choose the IDE Port
(Primary Master/Primary Slave or Secundary Master/Secundary Slave) according to the
sata channel you have attached the Drive, you could simply click on "SEND IDENTIFY ATAPI"
button so if you get the Drive response then its the proper channel
- Liteon Drives should be powered on with tray half opened, I would recommend follow this great
tutorial from devils360 http://www.devilsps3.centelia.net/360/?p=7
you also should choose the com port that is used to comunicate with the drive
- To Read liteon Keys just click on "Key Read" Button, keys will be displayed
- To Save Files just click on "Get Key And Files" and files will be generated and you
will be asked for location of the files
- To Put a Hitachi drive in ModeB just click on ModeB button, make sure the attached drive is
a Hitachi, this command will be rejected for other brand of drives, this feature is useful
on Hitachi 78/79 to avoid SLAX booting.
- Dont use this tool to mess with Other (Windows Visible) drives or dvd roms, sending eject/load
commands to windows controlled drives could work but if you disturb windows control over them
horrible things could happen. My advice is keep a channel for the "non-visible" drives it could
be Primary or the Master, and leave the other for Windows controlled drives
SUPPORT/DONATIONS
-----------------
- NO NEEDED, IF YOU WANT HELP US IN ANY WAY, BUY GENUINE 360 XTRACTOR TOOLS AT
http//www.maximusgames.net/360xtractor.php
For those bashers around there: We give software tools for FREE, our hardware is OPTIONAL
If you dont like our hardware simply DONT BUY IT and stop posting bullshit.
THANKS TO
-------------------------------------------------------------------
C4E, geremia, and all others on xboxhacker.net
This post has been edited by Yoshihiro: Sep 23 2008, 11:35 PM
-
nice tool would be nice now if we can get a tool that can make the samsung be reconized in windows without using a 0800 disc
-
- BONUS FEATURE: Send ModeB command to All Hitachi Drives (even 78/79) NO SLAX REQUIRED
THATS HOT! (IMG:style_emoticons/default/pop.gif)
but even after mode B is done do we need to restart the computer after mod b or should the drive auto detect because if thats what it says ITS AMAZING!
This post has been edited by mafiafan123: Sep 24 2008, 03:50 AM
-
mafiafan> No rebooting required. Did a V79 today completely without rebooting. Credit goes to podger for the code though.
Oh, and great tool. Was waiting for a solution that didn't require me to manually copy the key. (IMG:style_emoticons/default/smile.gif)
This post has been edited by Ree1981: Sep 24 2008, 05:55 AM
-
yea no reboot is required but ree is right credit goes to podger if it was not for him we still would probly be using slax and that rebooting stuff gets boring lol
-
That's right. This software is nothing but a shell to hide Podger's work...
-
QUOTE(Ree1981 @ Sep 24 2008, 06:53 AM)

mafiafan> No rebooting required. Did a V79 today completely without rebooting. Credit goes to podger for the code though.
Oh, and great tool. Was waiting for a solution that didn't require me to manually copy the key. (IMG:
style_emoticons/default/smile.gif)
Hi the orginal code for the mode b not come from the podger the code is here before teh xtrem firmware the code come from kev the code is opensource i know this one since too many time
here the proof : Kev DVD hitachi 360 hacking site
/*
* Puts a Hitachi-LG Xbox 360 DVD drive into modeB.
* In modeB, the drive responds to standard ATAPI
* commands that it otherwise wouldn't (for example:
* Read(12), Inquiry, Mode Sense(10)). ModeB also
* changes, among other things, the behaviour of the
* drive's eject input and tray_status output.
*
* author: Kevin East (SeventhSon)
* email: [email protected]
* web: http://www.kev.nu/360/
* date: 2nd March 2006
* platform: Windows
*
*/
source for linux and windows .
Cya guys
-
Then perhaps he should give credit to Seventhson for all of his work relating to Hitachi drives....
-
QUOTE(caster420 @ Sep 24 2008, 05:14 PM)

Then perhaps he should give credit to Seventhson for all of his work relating to Hitachi drives....
Hey it's already done in Maximus Firmware toolbox for hitachi the first real thing of this tool it's the benq key dumping the mode b it's added for the beta testing dont worry about the thanks of Seventhson .
THANKS TO
-------------------------------------------------------------------
C4E, Seventhson, garyopa, geremia, birdy, Loser, modfreakz, uberfry,
Tecno Devices and all others on xboxhacker.net .
-
QUOTE(Yoshihiro @ Sep 24 2008, 10:25 AM)

Hey it's already done in Maximus Firmware toolbox for hitachi the first real thing of this tool it's the benq key dumping the mode b it's added for the beta testing dont worry about the thanks of Seventhson .
THANKS TO
-------------------------------------------------------------------
C4E, Seventhson, garyopa, geremia, birdy, Loser, modfreakz, uberfry,
Tecno Devices and all others on xboxhacker.net .
No, we WILL worry about people giving credit where credit is due. Beta or not is no excuse. If its been 'opensource' information, then why has he not implemented it before? Kinda a lame excuse to wait all this time, and then oh-so coincidentally right after podger releases it.
The fact is, seventhson told podger about it, and gave him the 'ok' to make it public, and then maximus is now using it. That is the REAL story.
I do not understand the point of this release. Why did he not just implement it into fwtb? This is just a clone of dvdkey32 and mode_b.
-
About as open as N.O.C.H.E.C.K firmware being hidden from 4.0
The guy has done everything to avoid thanking podger, even for his time / research and insights.
Let alone his 79Unlock (IMG:style_emoticons/default/wink.gif)
I praised the passkey, it done what we all wanted to do - but sometimes, poeples actions deserve condeming
IF max played ball, we could have had so much more, sooner
9 weeks it took podger to code 79unlock on his own, nocheck was implemented after podger released it, but was 'common knowledge' before then as well.
Credit where its due!
This post has been edited by OggyUK: Sep 24 2008, 05:26 PM
-
QUOTE(Iriez @ Sep 24 2008, 06:02 PM)

The fact is, seventhson told podger about it, and gave him the 'ok' to make it public, and then maximus is now using it. That is the REAL story.
I do not understand the point of this release. Why did he not just implement it into fwtb? This is just a clone of dvdkey32 and mode_b.
Sorry if you believe that maximus never use anything without ask to real dev ever you can use the last toolbox for help you to flashing your drive and patch your hitachi firmware or spoof it .so no need to throw stones to him thanks
It's only My Opinion
-
Anyone actually test the product?
I can't get it to work with my XCK v2 / RS232 kit. Wish I could just enter my port number instead of dealing with the master/slave thing.
-
What is the no check firmware in the new firmware toolbox?
-
It was in 4.0
-
New version out : Beta 05
---------------------------------------------------------------------
Maximus - 360 Xtractor Reader Beta 0.5
---------------------------------------------------------------------
Intherim Release, this functionallity will be added to Fw Toolbox soon
New on B.5
- FIXED : Bug showing wrong key when it contains a "00" on it
- ADDED : SPOOF File Generation Option (it patches both, inquiry and
identify routines).
*Note: If you plan to flash the resultant firmware with Firmware Toolbox
(if the destination drive is a hitachi), take note Firmware Toolbox
will not open properly the resultant file since Toolbox does not
yet full spoof, we are working on a new release to fix that.
Samsung generated files can be flashed with mtkflash as usual.
(IMG:http://img338.imageshack.us/img338/7515/xtractor360toolro3.th.jpg)(IMG:http://img338.imageshack.us/images/thpix.gif)
Download here : Xtractor Reader Beta 05.rar
This post has been edited by Yoshihiro: Today, 08:58 PM
-
do i need to use the maximus xtractor tool for this to work?
because when i hooked this up to my via sata card it didn't work
-
QUOTE(OggyUK @ Sep 24 2008, 03:48 PM)

It was in 4.0
yes but what does it do
-
AKA - The anti Passkey patch, as it was named when it was first publically released.
The info was always there, and 'others' knew about it but it was never made public until Podger.
Leaving a v79 flashable after first hack, no unlock/passkey required.
Removes the one bit protection the passkey initially overcame.
-
QUOTE(farntheplaya @ Sep 25 2008, 04:42 AM)

do i need to use the maximus xtractor tool for this to work?
because when i hooked this up to my via sata card it didn't work
Hi Yes you can use it without 360 Xtractor if wont work you can contact the maximus team .
QUOTE(OggyUK @ Sep 25 2008, 09:00 AM)

AKA - The anti Passkey patch, as it was named when it was first publically released.
The info was always there, and 'others' knew about it but it was never made public until Podger.
Leaving a v79 flashable after first hack, no unlock/passkey required.
Removes the one bit protection the passkey initially overcame.
hi oggy you know how work the 79 Flash R/W Enabler ?
you need to enable it in hitachi drive RAM so you need to write the good byte to good offset i can say that can be done without the data track . but need some work 
PS: where you have read maximus can do it since longtime to firmware toolbox you cant compare a modchip hack and a sata ram hack on xbox 360 drive .
-
I have never compared a hardware mod to a software one (only praised them both for doing what they were intended for)
Also, I said the nocheck firmware was in toolbox 4.0 not the soft unlock.
Either, your English is letting you down, or you want to believe Im saying something Im not.
The anti passkey patch (or nocheck firmware) removes the one bit protection after intial passkey install (well, it did upon release) - the passkey was always needed for this, of course until 79unlock.
I know maximus knew about this before, it was disabled in F/W TB 4.0 but not released until 4.7
-
QUOTE(OggyUK @ Oct 8 2008, 11:00 PM)

So, this tool, is infact a waste of time (as of 0.8b) unless, you have a motherboard that supports SATA as Native IDE....9/10 will use DVDKey 1.2 / 32 anyway.. rendering this almost worthless????
And only now, 0.8b does it actually do more than toolbox done in the first place, therefore, shouldnt have been released until it surpassed toolbox, as that was its intended purpose????
Why rush these things out? The overpriced tool isnt even on sale yet and we have had how many unreliable beta's?
What happened to closed doors beta testing??? Not letting people who could spoof it with no Identify/Inquriy and know no different because they assume its been beta tested before public release...Yes its beta, but completely untested beta?
You are shitting me?
Not a waste of time buddy, this tool did the identify.bin before other tools did it, also you can use cheap IDE-SATA adapter to do the trick, you will suprised how many people are taking that way instead of configuring their pcs or getting the sata addresses.
The intended purpose is to provide our own tool with our own support and the hability to do our own customization when we need it.
And m8, the issues we have found on the application since first release are not critical, just the one pointed by podger (and he refused to give us details on first instance), but fortunatelly we fixed it before the product reach stores so I think the beta was tested enough before launch.
-
QUOTE(carranzafp @ Oct 9 2008, 02:16 AM)

Not a waste of time buddy, this tool did the identify.bin before other tools did it, also you can use cheap IDE-SATA adapter to do the trick, you will suprised how many people are taking that way instead of configuring their pcs or getting the sata addresses.
The intended purpose is to provide our own tool with our own support and the hability to do our own customization when we need it.
And m8, the issues we have found on the application since first release are not critical, just the one pointed by podger (and he refused to give us details on first instance), but fortunatelly we fixed it before the product reach stores so I think the beta was tested enough before launch.
How ironic, the guy who done the main bulk of your beta testing and highlighted the flaws, was the same guy who smashed your passkey out of the water.
You state it was the first tool to support Identify.bin handling/insertion....Wasnt the sole aspect of this 'part' of the tool to actually insert it properly?? It clearly wasnt tested internally as isnt that what you 'should' have been checking??? I mean, the first tool to insert it and it wasnt even doing it properly. Where do I sign?
6USD for a IDE->SATA converter?? How much are the RS3232 Interfaces, and USB ->Serial converters these days? Alot cheaper than 'the xtracter' +PATA->SATA converters thats for sure- Lets buy a tool that supports it all, but I still need a converter to get it to work....Go figure.
Oh wait it supports modeb, not sure if it does for v78/v79's - You dont even need to reboot for modeb anymore thanks to that guy again, your main beta tester, podger.... So thats a pretty null selling point
As of 0.7 it was only ever as good (or not as godd??? stealth?) as Toolbox, which, I must thank you for, fantastic tool.....Why didny you just incorporate it into this?
Or did you need a selling point for your Xtracter?
-
*** Important ***
As Maximus didn't say it I will.
If you spoofed your BenQ with version 0.7 and below you need to spoof again with 0.8 and re-flash it....If you want to keep the best possible prtotection against bannings
Let me first start by saying, the intention here is not to start a pissing contest with Maximus...
A serious flaw was spotted by Podger in version 0.7, to call this a bug is and understatement to say the least...
The flaw was posted on IRC 3 days ago in private channels where people who often speak for Maximus hang out, Maximus has to be out of his mind if he thinks anyone not to mention serious hackers/developers are going to contact him via e-mail, especially not at c*rranz*[email protected].... FFS, does he not know Hotmail is owned and maintained by M$....
The test was as basic as it gets, and yet 2 weeks after release, no-one in Maximus' team had performed it...
Identity.bin returned from lite-on was as follows..
CODE
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 31 36 38 30 39 .....D608xxxxxxxx
0020: 30 30 32 51 30 20 20 20 - 00 00 00 00 00 00 34 37 002Q0 .......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
Notice PLDS is obfuscated because of the big to little endian conversion of the 16 bit data port, this is normal, this data should then be patched into the donor BenQ firmare in such a way that the BenQ responds in an identical fashion to the target Lite-On....
*** This is the whole concept of spoofing ***
However, Maximus's "Untested" tool (0.7b and below) the Identity.bin returned from the Benq was as follows...
CODE
0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 .................
0010: 00 00 00 00 36 44 38 30 - 47 43 31 38 38 36 39 30 .....6D80xxxxxxxx
0020: 30 30 51 32 20 30 20 20 - 00 00 00 00 00 00 37 34 00Q2 0 .......74
0030: 38 35 30 43 20 20 50 4C - 44 53 20 20 20 20 44 47 850C PLDS DG
0040: 2D 31 36 44 32 53 20 20 - 20 20 20 20 20 20 20 20 -16D2S
Notice it's not swapped any more??? Making the identify a complete magnet to any Ban Hammer....
With a flaw like this, Max can't possibly stand over this body work... Releasing this to the public in this condition is nothing short of wreckless....
This post has been edited by OggyUK: Oct 9 2008, 04:43 PM
-
Wow. This is good to know. This new tool is an over priced POS as I suspected.
So not only does it offer nothing new, it is also gonna ban your 360 unless you update it. Sad.
Thanks Podger, Oggy, Seventh son, Germania ( forget spelling), C4eva, and anyone else who is bringing reliable software to the masses instead of trying to make a quick buck.
Has anybody checked FWTB for shoddy workmanship?
This post has been edited by calloused labia: Oct 9 2008, 05:27 PM
-
OOhhh indeed unreliable / overpriced / guess it aint gonna get that ronseal stamp off approval then. IE: Does exactly what it says on the tin. Well maybe it does but by the sounds of it no more than is already out there.
Well also given the fact it was a preorder item on 29th Sept any issues should have been well and truely ironed out before release, i for one assumed beta was a term used for testing a product, so were looking at testing this tool at a price and maybe even a higher price with a ban then report back stating this and that aint working??.
(IMG:style_emoticons/default/ph34r.gif)
This post has been edited by sparky2k1: Oct 9 2008, 10:53 PM
-
QUOTE(calloused labia @ Oct 9 2008, 12:26 PM)

Has anybody checked FWTB for shoddy workmanship?
Well, the exact issue that Oggy is discussing above (identify string) is not changed by 360FWTB when it performs any spoofing, unless max has fixed it in the most current revision. I have done this for a long time in both samtool and firmtool. When you attempt to open a firmware where the identify is spoofed, it incorrectly detects the firmware type and loads incorrect information. I assume that when he says above, "this tool did the identify.bin before other tools did it" he is purely referring to this application only. Why not implement it in your other applications as well?
In addition to that, he does not copy the BENQ serial when creating/patching hacked benq firmware from an original benq source. This is used to unlock the drive and should be checked/copied in my opinion. This is the primary reason it was not recommended to use 360FWTB with BenQ firmware when it was released until he fixed it.
Regards,
Caster.
-
Posted in another topic but it relates to what i said above...
(1) Firmware created with firmtool
(IMG:http://caster420.360mods.net/ftsamsungspoof.jpg)
2) Firmtool created firmware opened with 360 Firmware Toolbox
(IMG:http://caster420.360mods.net/360fwtbftspoofed.jpg)
3) 360 Firmware Toolbox v4.7 spoofing the same type of firmware...
(IMG:http://caster420.360mods.net/360fwtbspoof.jpg)
4) Hex comparison of two generated firmware...
(IMG:http://caster420.360mods.net/comparison.jpg)
Regards,
Caster.
-
QUOTE(OggyUK @ Oct 9 2008, 04:25 PM)

*** Important ***
A serious flaw was spotted by Podger in version 0.7, to call this a bug is and understatement to say the least...
The flaw was posted on IRC 3 days ago in private channels where people who often speak for Maximus hang out, Maximus has to be out of his mind if he thinks anyone not to mention serious hackers/developers are going to contact him via e-mail, especially not at c*rranz*
[email protected].... FFS, does he not know Hotmail is owned and maintained by M$....
Come on, you think M$ will delete my email just for giving me details of the bug ? lol, he can also could pass the info to the ones that speaks with me instead of refusing
QUOTE(OggyUK @ Oct 9 2008, 04:25 PM)

Identity.bin returned from lite-on was as follows..
bla bla bla
*** This is the whole concept of spoofing ***
However, Maximus's "Untested" tool (0.7b and below) the Identity.bin returned from the Benq was as follows...
With a flaw like this, Max can't possibly stand over this body work... Releasing this to the public in this condition is nothing short of wreckless....
Yes M8, and figure what... if you only spoof inquiry like it was done on previous tutorials BEFORE this tool you are on same BANNER RISK (I would love to see somebody refuses this point)
Also, the bug just affected BENQ target drives, samsung and hitachis were OK, and OHH figure also this.... If you PATCH the ATA STRING mannually on hex editor (pasting the data on the identify.bin file over the target BENQ firmware) you will be on same situation as the bug !!! so... yes, I agree, thanks for pointing it... but the only reason to find the bug was because the tool was the first to attempt to patch it, before that you were on BANNER SITUATION (even with first dvdkey32 not giving even the identify.bin at all).
And no, I dont care who did the finding on the bug, if he just gave me the detail I will be giving thanks as I always do, but he preffered use that information for his own purposes, At least I didnt leave the bug affected intentionally.
QUOTE(calloused labia @ Oct 9 2008, 05:26 PM)

So not only does it offer nothing new, it is also gonna ban your 360 unless you update it. Sad.
Thanks Podger, Oggy, Seventh son, Germania ( forget spelling), C4eva, and anyone else who is bringing reliable software to the masses instead of trying to make a quick buck.
Has anybody checked FWTB for shoddy workmanship?
QUOTE(sparky2k1 @ Oct 9 2008, 10:41 PM)

Well also given the fact it was a preorder item on 29th Sept any issues should have been well and truely ironed out before release, i for one assumed beta was a term used for testing a product, so were looking at testing this tool at a price and maybe even a higher price with a ban then report back stating this and that aint working??.
(IMG:
style_emoticons/default/ph34r.gif)
Yes m8 go spoof benq manually or with previous tutorials who only patched INQUIRY and you will be surprised you will be on same situation. And I think my software is also downloadable for free? isn't?
If you could really understand 100% the problem you will see you need update your spoofing not just because "max had a bug" its because previous spoofings (done manually or spoofing only the inquiry) are also on same situation. Nobody knows if ever will be used for banning but like you like to dramatize it I need to point it.
QUOTE(caster420 @ Oct 9 2008, 11:05 PM)

In addition to that, he does not copy the BENQ serial when creating/patching hacked benq firmware from an original benq source. This is used to unlock the drive and should be checked/copied in my opinion. This is the primary reason it was not recommended to use 360FWTB with BenQ firmware when it was released until he fixed it.
Yes M8, I do know both situations and are fixed on next release, its fair to say works fine 99% times on the keys, and about the benq serial is same situation as before, fortunatelly I added on Toolbox 4.8 the "ASK" for inquiry.bin instead of patching with hardcoded values, that reliefs a bit while I have time to finish next release
This post has been edited by carranzafp: Oct 10 2008, 08:27 PM
-
QUOTE(OggyUK @ Oct 9 2008, 07:11 AM)

Lets buy a tool that supports it all, but I still need a converter to get it to work....Go figure.
Oh wait it supports modeb, not sure if it does for v78/v79's - You dont even need to reboot for modeb anymore thanks to that guy again, your main beta tester, podger.... So thats a pretty null selling point
As of 0.7 it was only ever as good (or not as godd??? stealth?) as Toolbox, which, I must thank you for, fantastic tool.....Why didny you just incorporate it into this?
Or did you need a selling point for your Xtracter?
No need to buy ide-sata if your PC has legacy, also (and Podger knows this) If my xtractor reader application can work writing to standard IDE ports nothing is stoping me to write to any SATA port there is no BIG DEAL with that, just matter of changing hex address. Its just limited (at this moment) to these well know addresses. The hard job is done with the ata/atapi layer, after that just point to another address and away you go.
M8, you dont needed to reboot also with Xtractor Reader application using the button MODEB, and I just must say I incorporate this function since b.01, was my initals tests, and NO !! I dont was the first to publish it, and also was not Podger, sorry if you are disappointed, the first was Seventhson, he released a ModeB application for windows . Didnt you know it? well you know it now
QUOTE(OggyUK @ Oct 9 2008, 04:25 PM)

*** Important ***
Let me first start by saying, the intention here is not to start a pissing contest with Maximus...
Of course not... lol
This post has been edited by carranzafp: Oct 10 2008, 08:45 PM
-
I had some time to do some more testing today.... I have my own stuff to write and test so I do this purely for the good of the scene.....
I tested Benq and Sammy and all was good IMHO with version 0.8.. as you know there was small bug in 0.7 with Benq firmware...
I promised to take a look at hitachi spoofing, figured this would be Maximus's strongest area, no hurry, right! Had a look this evening... My target was to make my 79 ( the one I did all my testing on for 79Unlock, key location is 4E10...). My task to make it appear to be my Lite-On...
So DVDkey32'd my Lite-On as I don't have an Intel chipset or a spare IDE slot for a PATA-SATA adapter as my PC like so many others has a Hard drive on my primary IDE bus and a Burner and Kreon on the other...
Luckily, enough I have a Via 6421, I find it useful from time to time... for STUFF..
Lauched Maximus 0.8b, clicked "Perpare Spoofed Firmware"... picked up the 3 files and generated firmware...
Didn't open in FWTB... hardly a surprise... Max did say it wouldn't, but
Maximus: do you even know why???
I Opened the .bin file in Hexedit to have a little look.....
OMG, what a disaster...
small bit of background on hitachi
QUOTE
let me explain a small bit here.... when a Hitachi boots, it reads the checksum at 0x3E7FC... if its 0x00000000 (master checksum) it boots to normal code...
if it's not 0x0000000 it calculates the sum for range between 0x6000 and 0x3E800 in 32 bits and result should be zero.. the stored checksum at 0x3E7FC makes this happen
if the result is zero the drive boots to normal code.
if it's not is goes to Recovery code, this is in theory to allow you the fix up the drive...
this area also has an Inquiry and Identify string, but to all intents and purposes is unused, It can however be useful to say identify a spoofed drives original type...... see below
setting the master checksum is handy for modding as you can then effectively ignore it.
SO... heres what I found
The "Perpare Spoofed Firmware" left normal code untouched, so drive appears exactly as it did before the spoof...
Instead it patches the Recovery area.... As, I pointed out earlier this area could be useful for spotting the type of drive....
But guess what it now says Lite-On and FWTB can't identify that... ( maximus: no need to thank me for that, spotting it is thanks enough )
Now that's not all......
So guess where the "Perpare Spoofed Firmware" put my key, 4e10 you say.... NO!, 4f00, ... FFS Maximus... WTF is that about....
Did you even look at the code before you released... I mean did you even try it once...
As FWTB couldn't read the file, I sure most of you have not used this for Hitachi's so the damage is negligible
I manually spoofed my firmware and FWTB read it just fine and flashed the 2 sectors 4000 for the key and 3c000 for the identity/inquiry data without incident
ran DVDkey32 ( no key) and both strings were fine....
Oh and Maximus BTW....
If this was a pissing contest, I'd have let you go ahead and release FWTB 4.9 .... just to compound your mess....
-
QUOTE(Iriez @ Sep 24 2008, 05:02 PM)

No, we WILL worry about people giving credit where credit is due. Beta or not is no excuse. If its been 'opensource' information, then why has he not implemented it before? Kinda a lame excuse to wait all this time, and then oh-so coincidentally right after podger releases it.
The fact is, seventhson told podger about it, and gave him the 'ok' to make it public, and then maximus is now using it. That is the REAL story.
I do not understand the point of this release. Why did he not just implement it into fwtb? This is just a clone of dvdkey32 and mode_b.
Hi Iriez just looking back on previous msgs,
I dont use Seventhson code on this tool (I dont know if podger use it but not my case), seventhson code dont have its own atapi layer. Let me know if you are meaning that everytime we say "modeb" we must add the "thanks to seventhson" because I think its pretty obvious, he discovered and documented the command. Repeat I dont used seventhson code just invoked his documented command like slax does. I thanked geremia and c4e for sharing me the key dumping information on the liteon/benq that is the important thing on the tool.
I could show you code listings on what was first, podger or maximus on modeb (strangly he posted 2 days after I told geremia I already have it coded on beta .01, the Modeb was the feature that I used to test my atapi layer from begginning) but honestly I dont care what people thinks m8, the first to release a MODEB application for windows was Seventhson, its on its website. End of history.
Honestly m8 you disappoint me with your comments, I thinked had your support but apparentlly I was totally wrong with you.
-
QUOTE(podger @ Oct 11 2008, 01:16 AM)

Instead it patches the Recovery area.... As, I pointed out earlier this area could be useful for spotting the type of drive....
But guess what it now says Lite-On and FWTB can't identify that... ( maximus: no need to thank me for that, spotting it is thanks enough )
So guess where the "Perpare Spoofed Firmware" put my key, 4e10 you say.... NO!, 4f00, ... FFS Maximus... WTF is that about....
As FWTB couldn't read the file, I sure most of you have not used this for Hitachi's so the damage is negligible
Yes podger I see the problem and yes since nobody has used for hitachi is because of whats not been reported yet. I am working on a fix at this moment.
Sincerelly m8, whats the problem you have with me? I mean its not about this software at all I really feel you want to chop my head, maybe I did something to hurt you on the past? sincerelly dont remember. I just starting to know about you for bashing me on every comment you post.
-
Maximus: Well ignore my last post and go after Iriez instead, why don't ya.......
Firstly: I first posted on Mode-B from window 6 months also...651006. Seventhson's exe proved hard to use for ports other than 1F0, 170, because of the necessity to know the ATA command block base register address, often undocumented...
At this time all I posted was a way to find the ATA command block base register and as a result use the tool. all credit to SeventhSon at that time.
Secondly: SuperMario descovered the E7 H I T 30 90 90 D0 01 and for the record Seventhson has never claimed to have found the documented command. He offers full credit on his site to Supermario...update_02_03_06
Thirdly: Seventhson has an exceptionly well written ATAPI layer driver.. requires you to know the ctrl port as is and uses the geek's hideout port IO driver.... hmmmmm, I wonder....
My second post on XBH on Mode-B came about as a result of work I did on DVDKey32 to remove the requirement to know ATA command block base register address, as again this made the tool hard to use, thanks to Seventhson and Uberfry.
With the requirement gone I recoded the Mode_b.exe ( with the express written permission of Seventhson BTW ), and I tested it and got others to test it for a few days. This made the tool easier to use and quite useful for people stuck with a spoofed unmodded 78/79.....Oh yeah that post was 3 days before I released it so I guess your 2 day head start is shot to shit...
I further improved the tool by adding a loop that continually sends the command until the drive acknowledges. So executing the comand with the drive off then powering it, the drive effectively powers up in mode B and doesn't lock up the controller card and the system.... You may come up against that issue if you ever decide to support ports other than 170 1F0...
-
QUOTE(carranzafp @ Oct 10 2008, 07:31 PM)

Hi Iriez just looking back on previous msgs,
I dont use Seventhson code on this tool (I dont know if podger use it but not my case), seventhson code dont have its own atapi layer. Let me know if you are meaning that everytime we say "modeb" we must add the "thanks to seventhson" because I think its pretty obvious, he discovered and documented the command. Repeat I dont used seventhson code just invoked his documented command like slax does. I thanked geremia and c4e for sharing me the key dumping information on the liteon/benq that is the important thing on the tool.
I could show you code listings on what was first, podger or maximus on modeb (strangly he posted 2 days after I told geremia I already have it coded on beta .01, the Modeb was the feature that I used to test my atapi layer from begginning) but honestly I dont care what people thinks m8, the first to release a MODEB application for windows was Seventhson, its on its website. End of history.
Honestly m8 you disappoint me with your comments, I thinked had your support but apparentlly I was totally wrong with you.
Keep in mind that I work with, and represent, most of the developers in the entire scene. So when I see a software release that looks like it is using methods founded by other developers, and no thanks are given, Im going to call you out on it. It doesnt matter if i support you or if i do not support you. Its good to know that you took the 'concept' and expanded on it to make it your own, but keep in mind that the original concept was documented and created by Seventhson. You said so yourself that you just 'invoked his documented command', which means that you've used his work.
Just give thanks where thanks are due, and no one will be pissy about it. Yes, everytime you use it, you should give thanks. Its people like Seventhson that make possible today the work you do. You *should* be grateful enough to recognize and respect that on every release.
-
Podger:
I dont refused your previous comment (I responded already) was just matter of the timming on the posts.
and no point on going to dates on who did what all as i can say is that I have not ever heard about you doing modeb tool when I did mine,
Here is a small transcript of Geremia chat I would not post it if not was true chat
12/09/08 05:40:57 p.m. [email protected] SAYS: well, you could also do an hitachi soft modeb
12/09/08 05:41:44 p.m. [email protected] SAYS: with full control over sata at lower level, you can
12/09/08 05:42:00 p.m. [email protected] SAYS: yes
12/09/08 05:42:06 p.m. [email protected] SAYS: Indeed I did it
12/09/08 05:42:10 p.m. [email protected] SAYS: it works
Going to explain history in detail about supermario and seventhson is pointless for the the topic, of course thanks to them, they were foundation of all this, we are just catfight girls compared to them
There is one single thing I discover myself over their work, and worked fine, I was lucky for figure it out, but they were foundation.
Iriez:
I added Seventhson on the readme included on new fix, not inttentionally leaved out, for me was pretty obvious
-
QUOTE(carranzafp @ Oct 10 2008, 08:13 PM)

And I think my software is also downloadable for free? isn't?
Yes the SW may very well be free for download, but reading back on the flaws so far, I beleive this "free" SW should have been fully tested before use on the "Purchased Tool" that the SW is for.
Not much point having a car without having the petrol to run it. (IMG:style_emoticons/default/wink.gif)
Granted the SW may work with other tools but I get the impression it was written specifically for the tool being sold.