Print

[Bubbafish]

Thanks for your great work, Frosty.  I tried it on my virgin BenQ and it worked great.  I did, however, run into the issue where, after successfully reading the original firmware off my drive, the program hung.  This happened even though my C: drive is IDE (I read earlier in the thread that the hanging problem usually only happens with SATA C:. Oh well).  I did notice, however, that an orig.bin *did* actually get written to my C: drive, and was about 60kb.  

Anyways, I am a risk-taker, so I decided to try again, and on the second time run through, I answered "no" to the NTFS4DOS prompt, and just proceeded without having the program save my original firmware.  Everything completed and all seems well. Whew.

So now my only question is:  is my 60kb orig.bin that got written the first run through valid?  I thought orig.bin's were normally 256kb.  Maybe I don't really need to care all that much, since everything is working, but I'm just curious.  Also, I *did* jot down my drive key when it was displayed on screen at the end.  Figured that might be handy one day.

[FrostyTheSnowman]

QUOTE(Bubbafish @ Mar 15 2009, 12:12 AM)

Thanks for your great work, Frosty.  I tried it on my virgin BenQ and it worked great.  I did, however, run into the issue where, after successfully reading the original firmware off my drive, the program hung.  This happened even though my C: drive is IDE (I read earlier in the thread that the hanging problem usually only happens with SATA C:. Oh well).  I did notice, however, that an orig.bin *did* actually get written to my C: drive, and was about 60kb.  

Anyways, I am a risk-taker, so I decided to try again, and on the second time run through, I answered "no" to the NTFS4DOS prompt, and just proceeded without having the program save my original firmware.  Everything completed and all seems well. Whew.

So now my only question is:  is my 60kb orig.bin that got written the first run through valid?  I thought orig.bin's were normally 256kb.  Maybe I don't really need to care all that much, since everything is working, but I'm just curious.  Also, I *did* jot down my drive key when it was displayed on screen at the end.  Figured that might be handy one day.

The 60kb orig.bin file is not valid, you definitely do not want to use it.

I'm glad you got it working though, and yes, your drive key is very important to hold on to, indeed it may even be worth more than your orig.bin file anyway as having your key means that you can repair your drive or replace your drive any time you like as long as you know that key.

[bdm214]

where do i downlaod this?
is it on xbins?

[DuggyUK]

QUOTE(blackg1000 @ Mar 14 2009, 11:56 AM)

Cos the guy who made the disc recommends it.

if the 360 wasn't 100% reliable in powering the drive, how do you think it does it when you play your games?  

[solecon360]

QUOTE(DuggyUK @ Mar 15 2009, 07:50 PM)

if the 360 wasn't 100% reliable in powering the drive, how do you think it does it when you play your games?  

Also used 360 Modification Disc v1.51, worked fine powered by xbox.
It was useful to know to disconnect every HD, after disconnecting it worked ok without freeze.

[FrostyTheSnowman]

QUOTE(DuggyUK @ Mar 15 2009, 12:50 PM)

if the 360 wasn't 100% reliable in powering the drive, how do you think it does it when you play your games?  

It's not that the power source in the 360 is not reliable, the power in the 360 is perfectly reliable.

The problem is that the 360 does not instantly power off when you hit the power button... it stays on for another 10-15 seconds if the dvd drive is not connected (which affects timing), and also that when the drive is connected to the 360 the 360 is sending it signals over the power connector which can have an effect on the drive's ability to go into 'vendor mode' (being able to dump and flash).

So it's not that the 360's DVD power source is unreliable, it's that it throws a bunch more variables into the mix while flashing, which is not a good thing. Kudos to those who got it working with the 360's DVD power source though!

[tankuk]

Hi Frosty,

Im having an isue flashing my samsung drive, I have had a read through the previous post but cant find anything, it is possible I might have missed it.

I managed to find the drive and get upto the section where it says you need to restart press enter.

I press enter and a 2nd set of instructions come up telling to press enter and leave power to the drive.

Thing is when I press enter here it just hangs with a _ flashing in the top corner.

I left it for a while and it didnt do anything, it does spin up the CD in the pc but then nothing else happens.

I have disconnected all HDD's in case that information helps.

Have you any ideas?

Thanks

[snart]

Frosty- any word on that update to replace NTFS4DOS?

Thanks.

-snart

[FrostyTheSnowman]

QUOTE(snart @ Mar 15 2009, 10:06 PM)

Frosty- any word on that update to replace NTFS4DOS?

Thanks.

-snart

I have the necessary software to replace NTFS4DOS, except I am having trouble implementing it into my disc, as my disc currently uses the 'El Torito BIOS-Level Floppy Disc Emulation' as the basis for the disc, which is unfortunately limited to a maximum of 2.88MB of space as the 'floppy drive', and the solution I have available takes up over 4MB of space alone, and when combined with the firmware, scripts, tools, and OS it comes to a combined size of 6.50MB, which is WAY too big for floppy emulation...

I know that there is the 'El Torito BIOS-Level HDD Emulation' which basically turns your bootable CD into an emulated HDD, which WOULD work, but I can't seem to get this feature to work for the life of me... (can't seem to successfully create a bootable MS-DOS HDD image for a bootable CD...)

If anyone out there has any knowledge on HDD Emulation from a bootable CD, please PM me and we can combine forces to improve the '360 Modification Disc'. (don't worry, all credits for your assistance will be included in the disc)

[Bubbafish]

Frosty, have you looked at this?

http://support.microsoft.com/kb/167685

[blackg1000]

Hi, I'm hoping someone can help. I'm flashing a Lite-on and having a wee bit trouble at the dumping stage. It is saying 'DVD-KEY invalid' and is asking if the dump was succesful. How do I know if it is successful? When I select no it takes me back to the page for the hardware instructions and I seem to be going round in circles.

I'm using a CK3 to get the tray open and follow the instructions to the letter but I can't get it to read the key.

Could it be that my serial port is wrong? I can only select one or two but I haven't tried two yet. This is a serious noob question but how do I know which port the serial is on?

Secondly, does simply switching on the CK3 count for powering on the drive when it prompts me to 'connect the power cable' at the hardware instructions page or do I have to have the CK3 on and connect the cable when prompted? I  believe the tray is halfway as it looks similar to what I would do using Jungleflasher but again could this cause the error I'm getting.

Also, when asked to connect the serial, does this mean to the CK3? Obviously it can't go anywhere else but it's because the prompt says 'connect serial cable to the drive'.

I've used this disc to do a BENQ and it was flawless but I'm having a bit of trouble with the Liteon and I really hope someone can shed a bit of light.

Many Thanks,

[snart]

QUOTE(FrostyTheSnowman @ Mar 16 2009, 07:46 AM)

I have the necessary software to replace NTFS4DOS, except I am having trouble implementing it into my disc, as my disc currently uses the 'El Torito BIOS-Level Floppy Disc Emulation' as the basis for the disc, which is unfortunately limited to a maximum of 2.88MB of space as the 'floppy drive', and the solution I have available takes up over 4MB of space alone, and when combined with the firmware, scripts, tools, and OS it comes to a combined size of 6.50MB, which is WAY too big for floppy emulation...

I know that there is the 'El Torito BIOS-Level HDD Emulation' which basically turns your bootable CD into an emulated HDD, which WOULD work, but I can't seem to get this feature to work for the life of me... (can't seem to successfully create a bootable MS-DOS HDD image for a bootable CD...)

If anyone out there has any knowledge on HDD Emulation from a bootable CD, please PM me and we can combine forces to improve the '360 Modification Disc'. (don't worry, all credits for your assistance will be included in the disc)

Well, good luck, and keep up the good work!

-snart

[DuggyUK]

QUOTE(FrostyTheSnowman @ Mar 16 2009, 07:46 AM)

I have the necessary software to replace NTFS4DOS, except I am having trouble implementing it into my disc, as my disc currently uses the 'El Torito BIOS-Level Floppy Disc Emulation' as the basis for the disc, which is unfortunately limited to a maximum of 2.88MB of space as the 'floppy drive', and the solution I have available takes up over 4MB of space alone, and when combined with the firmware, scripts, tools, and OS it comes to a combined size of 6.50MB, which is WAY too big for floppy emulation...

I know that there is the 'El Torito BIOS-Level HDD Emulation' which basically turns your bootable CD into an emulated HDD, which WOULD work, but I can't seem to get this feature to work for the life of me... (can't seem to successfully create a bootable MS-DOS HDD image for a bootable CD...)

If anyone out there has any knowledge on HDD Emulation from a bootable CD, please PM me and we can combine forces to improve the '360 Modification Disc'. (don't worry, all credits for your assistance will be included in the disc)

You probably want to use "no emulation" actually from reading around. Seems straight forward enough to do too?, do you visit IRC ever?

[DuggyUK]

QUOTE(DuggyUK @ Mar 16 2009, 09:55 PM)

You probably want to use "no emulation" actually from reading around. Seems straight forward enough to do too?, do you visit IRC ever?

looks like you need to just follow these steps http://forum.imgburn...?showtopic=2600

[FrostyTheSnowman]

QUOTE(DuggyUK @ Mar 16 2009, 05:53 PM)

looks like you need to just follow these steps http://forum.imgburn...?showtopic=2600

Thanks, this should indeed do the trick.

Expect an updated release within a few days.