Print

[ZprivateZ]

How much easier then dosflash do you need besides someone doing it for you lol, far fewer people were having problems before iprep, im not saying its a bad program but people should have an understanding of what there doing before recommending/using an automated program then less people would make expensive paperweights.

[caster420]

QUOTE(ZprivateZ @ Apr 12 2008, 11:22 AM)

How much easier then dosflash do you need besides someone doing it for you lol, far fewer people were having problems before iprep, im not saying its a bad program but people should have an understanding of what there doing before recommending/using an automated program then less people would make expensive paperweights.

I disagree.  So, you're going to dump with dosflash.  What next?  How are you going to prepare the firmware?  Please dont tell me 360 Firmware Toolbox.  Once you get to dos with iPrep it is simply a batch file and i dont see the difference between typing the commands out and having them run for you.

If you want to ensure it for yourself, then learn how to create your own hacked firmware by hexediting.  Then you have no one to blame.  However, these applications were created to get away from that because of all of the confusion, and yes, because there were still drives being bricked.  

IMO, if people can't be bothered to read and understand the tutorial (which clearly explains everything), then what makes you think they're going to 'understand' what they're doing by typing the commands out them self?  No matter what you do, there is always going to be people who fuck up the process. There were before Xtreme Boot Maker/Iprep came out, and there will continue to be.  These are people that shouldn't be modifying their drives, PERIOD!  We have tried to make the process as idiot proof as possible.  I mean, how hard can it be to ensure that firmtool runs and that is doesnt display any error messages?

Caster.

This post has been edited by caster420: Apr 12 2008, 05:31 PM

[ZprivateZ]

lol 360 Firmware Toolbox isnt needed for benq drives so why would you prepare the firmware with it, but this is a conversation that could go on forever with the why whynots so lets just say we agree to disagree.

Now i will agree with that you cant fix user error

This post has been edited by ZprivateZ: Apr 12 2008, 05:34 PM

[caster420]

QUOTE(ZprivateZ @ Apr 12 2008, 01:17 PM)

lol 360 Firmware Toolbox isnt needed for benq drives so why would you prepare the firmware with it

Exactly.  So the process you go through, by typing out the commands, is the same as the batch files do.  So, if you didnt read a warning from firmtool when you made your firmware, you'd be just as likely to brick your drive doing it manually as someone using iprep.

Caster.

[OggyUK]

If you're not using Toolbox, You're using FirmTool.

Well, that or hexediting, but I seriously doubt you would, especially when you could use toolbox.

@Caster - Im sure it was you that made FirmTool, Id personally like to thank you as you are obviously viewing this, and cheers for the help on IRC ( I doubt you remember!)

Also, how did you edit your post 10 mins after? Im sure there is a 5 min max limit???

This post has been edited by OggyUK: Apr 12 2008, 05:50 PM

[caster420]

QUOTE(OggyUK @ Apr 12 2008, 01:31 PM)

If you're not using Toolbox, You're using FirmTool.

Well, that or hexediting, but I seriously doubt you would, especially when you could use toolbox.

That being said, DO NOT USE 360 FIRMWARE TOOLBOX FOR BENQ'S/SAMSUNG'S!!!  The checks are lacking and it doesnt prepare your firmware properly (benq anyways).  I have had many firmwares that are a bad dump that work with 360 firmware toolbox and not firmtool.

Caster.

Edit:  You're welcome for firmtool.  As far as editing goes, i have no idea.  I dont have any 'special' powers, so idk. lol.

This post has been edited by caster420: Apr 12 2008, 05:51 PM

[OggyUK]

Im not sure if you remember my thread about my PC hanging when Reading MS28's and BenQ's a few months back?

Thats sorted anyhows, but I had no issues using Toolbox with those drives whatsoever?

Or is it a small byte difference thats not stopping the 360's functionality?

[caster420]

QUOTE(OggyUK @ Apr 12 2008, 01:41 PM)

IThats sorted anyhows, but I had no issues using Toolbox with those drives whatsoever?

Toolbox will work most of the time but it doesnt check 'fully' (imo) for the key.  I have seen firmwares that are a bad dump but still had the basic requirements for 360 firmware toolbox.  The data was disjointed and the keysection partially fit the criteria but not fully.  So, a key was found, firmware was created with it, and the user bricked his/her drive.  This is the same with both samsung and benq drives.  Also, if you use 360fwtb to create benq firmware, it does not copy your benq 'serial' number to the hacked firmware.  It will simply remain blanked out on the firmware that you flash to your drive.  At this time, it isnt and issue and who knows if it will.  When i was writing firmtool, that was one of the requirements by c4e for firmware creation.  Thats why it has never been recommended to use 360fwtb with benq firmware.  If you go back to the original iXtreme benq threads, you'll see this noted many times.

Personally, i've had bad experiences with it as well.  Its a great app for 'checking' firmware, visually verifying, and for flashing v78/79 drives but besides that it shouldnt be used unless absolutely necessary.  I am not just saying this because i wrote an application that does similar things.  Maximus has been informed (a long time ago) about these issues and they've never been addressed.

Caster.

[st3venhal1]

Ok, thanks for the posts. When i went through the process it would have been that simple, however i could never get firmtool to run. Even in windows. I checked and it was in my partitioned drive with IPREP, but whenever i clicked on the application in windows it would show a .cmd box and immediatly close. How to i get firmtool to run automatically, and just in windows in general?

[caster420]

QUOTE(st3venhal1 @ Apr 12 2008, 01:58 PM)

Ok, thanks for the posts. When i went through the process it would have been that simple, however i could never get firmtool to run. Even in windows. I checked and it was in my partitioned drive with IPREP, but whenever i clicked on the application in windows it would show a .cmd box and immediatly close. How to i get firmtool to run automatically, and just in windows in general?

Hold on a second.  I re-read your original post.  You state, 'IPREP created a cdr bootup disc'.  You tried flashing from a cdr boot disc?  Please tell me that you didnt attempt that and that it is a typo.  Or are you booting from the NTFS4DOS cd and IPREP prepared a NTFS partition for you?  If so, how big is your partition?

As far as firmtool goes, if you're trying to run it from the 'Make iXtreme firmware' command and it doesnt run, its likely embedded in too many directories.  Since it is a dos based application, the variable for the directory string is only so many characters and doesnt like it when you have it in /Documents and Settings/Users/Whatever/Desktop/BenQ iXtreme v1.41/12x/...  Move the folder to c:\ and it should run.  You can also open a command prompt window, goto the directory, and type firmtool.  It will tell you the requirements.

Caster.

This post has been edited by caster420: Apr 12 2008, 06:20 PM

[st3venhal1]

No, i didnt try flashing from my CDR, i used the NFST method. my partition was somewhere below 50 mb i think . How big should it be? and what do you think my chances of having a bad key are? i am not at home so i cant check...

[caster420]

QUOTE(st3venhal1 @ Apr 12 2008, 02:36 PM)

No, i didnt try flashing from my CDR, i used the NFST method. my partition was somewhere below 50 mb i think . How big should it be? and what do you think my chances of having a bad key are? i am not at home so i cant check...

Nope, thats good.  The size only matters if you were trying to use a large partition, which usually causes issues.  As far as your 'bad' key question, i can't say.  Either the firmware you dumped is good or it isnt.  Check your PM's and email me your original firmware.  I'll take a look for you.

Caster.

[xbox360sexual]

QUOTE(OggyUK @ Apr 12 2008, 12:34 AM)

Well, if you done that many drives, youd know to read what firmtool shows when copying the  key over, you dont actually need toolbox as it displayes the key there and then for you

I don't use automated tools, I just said that

[OggyUK]

So you hex edit?

Name me an istance where firtool has done its job and fucked up without user error?

This post has been edited by OggyUK: Apr 12 2008, 11:26 PM

[xbox360sexual]

My mistake, I should have said automated DOS tools, but you get my point