Welcome to our community

Be apart of something great, join today!

opened up 360

Did you make sure you updated iprep with the latest definitions file? Also you are talking about iprep AND bootmaker??? you only need to use iprep to prepare everything you need m8 ;)

did you download the super tutorial from the link I posted for you on the first page of this thread?

It gives precise instructions with pics detailing exactly what you need to do both in terms of setting everything up with iprep and then completing your tasks of dumping your original firmware and then flashing your drive.
 
Last edited:
ive tryed all ways mate and still no go ..my pc will not boot into doss with the cd i made with iprep..even puled the hard driveide's out and still it will not...its not nowt to do with me being in ntfs and not fat 32....? my floppy comes up as fat not as ntfs wen i format it...

dont no then im lost now lol ...

me pc trys to boot of the floppy but gets half way and then comes up saying remove disks and other media and press any key 2 restart

? cld some1 flash the drive for me if i was to send it them and pay to flash it.

wouldent mined only i have everythink hear lol

not gd..could somone fash it if 4 us if i pay them
 
how you tying to boot it? your not just putting the disk in and rebooting are you? you have gone into bios and set it to boot from floppy or usb ect...


sure ive seen this before but i just cant put my finger on it at this min in time, ive seen it infact ive had it,


you got any other floppys laying about, might be the floppy,



easiest way is iprep and usb flash drive but theres no reason not to do it with floppy as long as its not old and battered, infact my first 2 floppys wouldnt work (too old)...worked first time with a new floppy but now i use the usb.



edit, just read the above and something isnt right, you have not updated iprep yet you,ve made a floppy? im sure iprep wouldnt let me load the firmware till i updated so how have you managed it?

you need to post the files your using and the tut your using as im pretty sure your not doing it right hence the no boot, something just dont seem right to me.
 
Last edited by a moderator:
sorry mate how do i update iprep with latest deinishions

?

mate I'm becoming increasingly confused lol...that tutorial from the link I posted for you on the first page of this thread tells you exactly what to do click for click and even has screenshots detailing the clicks... the reason I'm saying I'm confused is because if you are using that exact tutorial then it answers in detail with screenshots almost every question that you have asked since your first post of this thread... I'm wondering if you are perhaps using a completely different tutorial???
 
how you tying to boot it? your not just putting the disk in and rebooting are you? you have gone into bios and set it to boot from floppy or usb ect....

I didn't want ask the obvious but ofcourse this is very possible and an easy thing to overlook when youre feeling the pressure of it all and things are getting on top.
 
I didn't want ask the obvious but ofcourse this is very possible and an easy thing to overlook when youre feeling the pressure of it all and things are getting on top.


its always best to ask, you never know. im sure we had a guy the other week asking how to get some sat channels or why he wasnt getting sat channels turned out he was using a fixed sky dish, this was after loads of replys telling him about patches and boxes ect...then it turned out after all that it was down to his dish which he failed to mention.


always start right from the beginning then you know your telling them the right info.
 
lol no mate im ok with sat got a patched 1500 tms so im pritty much up on that lol ...

anyways mate back to this 360 YES mate i did update iprep befor i made the floppy..just tryed it again and it says no updates at this time...anyway im useing a pritty new sony floppy well its as good as new...i could try another one but i carnt see that being the problem as it formats in windows ok and all....

im lost as to why the floppy go's half way then stops on me..
 
its always best to ask, you never know. im sure we had a guy the other week asking how to get some sat channels or why he wasnt getting sat channels turned out he was using a fixed sky dish, this was after loads of replys telling him about patches and boxes ect...then it turned out after all that it was down to his dish which he failed to mention.


always start right from the beginning then you know your telling them the right info.

A very fair and valid point...

I do rather get the impression that the tutorial partycan is using somehow differs to textbooks super tutorial because the super tutorial at no point even mentions bootmaker when reading through the ms28 bad flash method or preparing iprep.
 
trust me m8 its better it stops before you start than half way through flashing ;)

good....well im useing the xbox 360 for noobs tut from hear lol

i dont think im making the floppy right me as it should work lol

? whats this dosflash program ive got ..could i try that

sorry mate... yes we have set comp up to boot off the floppy in bios wen we have bin trying......i bet if i was to put a windows boot up floppy in it would go in doss then
 
Last edited:
good....well im useing the xbox 360 for noobs tut from hear lol

i dont think im making the floppy right me as it should work lol

download the one from the link I posted on the first page of this thread as textbook constantly updates the tut... atleast that way we know we're reading from the same page so to speak lol.

iprep should be straight forward to sort out following that tut to the letter which should give you a floppy ready to go... ofcourse it could be one of so many other things that is holding you up its just hard to pin down.
 
hi mate
i had probs with iprep
but i use ms dosflash 32 very easy to use.heres the read me:


DosFlash and DosFlash32 V1.3 Beta
-----------------------------------
- BenQ optimization in unlocking the flash chip, it should now be possible to read/write/erase
the flash without any soldering or wire tricks, the drive is polled for the correct mtk
unlocking status after power on, this only works on VIA cards and NForce boards
- DosFlash32 is now available in two versions, the "EnableDrives" version enables the drives in
device manager after flashing, this could give BSOD on some systems
- better support of Intel chipsets, drives can now be flashed if the controller is not set to
native mode in the BIOS
- the following controller list includes vendor and device IDs that are hardcoded to identify
the controller type (IDE or SATA), this is needed if the BIOS uses IDE ports like 0x01F0 or
0x0170 as SATA and not as IDE channels
- the following chipset support is added
- VIA cards
- all VIA cards with a 6420 chipset
- IDE Controllers
- NVIDIA nForce 2 IDE Controller
- NVIDIA nForce 4 IDE Controller
- Intel ICH9
- Intel ICH (i810,i815,i840)
- Intel ICH0
- Intel ICH2M
- Intel ICH2 (i810E2,i845,850,860)
- Intel C-ICH (i810E2)
- Intel ICH3M
- Intel ICH3 (E7500/1)
- Intel ICH4 (i845GV,i845E,i852,i855)
- Intel ICH5
- Intel ESB (855GME/875P + 6300ESB)
- Intel ICH6 (and 6) (i915)
- Intel ICH7/7-R (i945, i975)
- Intel PIIX3 for the 430HX etc
- Intel PIIX4
- Intel PIIX4 for the 430TX/440BX/MX chipset
- Intel PIIX
- SATA Controllers
- NVIDIA nForce 4 SATA Controller
- NVIDIA nForce 2 SATA Controller
- NVIDIA nForce 3 SATA Controller
- NVIDIA nForce MCP04 SATA Controller
- NVIDIA nForce MCP51 SATA Controller
- NVIDIA nForce MCP55 SATA Controller
- NVIDIA nForce MCP61 SATA Controller
- Intel 82801EB (ICH5)
- Intel 6300ESB (ICH5)
- Intel 82801FB/FW (ICH6/ICH6W)
- Intel 82801FR/FRW (ICH6R/ICH6RW)
- Intel 82801FBM ICH6M
- Intel Enterprise Southbridge 2 (631xESB/632xESB)
- Intel 82801GB/GR/GH (ICH7, identical to ICH6)
- Intel 2801GBM/GHM (ICH7M, identical to ICH6M)
- Intel SATA Controller IDE (ICH8)
- Intel Mobile SATA Controller IDE (ICH8M)
- Intel SATA Controller IDE (ICH9)
- Intel SATA Controller IDE (ICH9M)


The following only applies to a software flash on a locked flash. The methods have been tested
with the BenQ and the Sammy. The VCC trick will work on any motherboard, but you need to do
some soldering and cut traces.


Flashing the BenQ with a VIA card and DosFlash16
--------------------------------------------------
- connect a 2nd power supply unit to the BenQ, don't turn it on yet
- cold reboot or reset the computer
- boot from a Dos disk
- at the prompt type:
DosFlash r 7000 1 a0 1 4 A:\orig.bin and press return
- use the port your VIA card uses, 7000 is only an example
- keep in mind that the same VIA card may change the base address on another system
- DosFlash16 will ask you if you wanna resend the mtk vendor intro cmd, press Yes
- after you pressed Yes the changing drive status is shown on the screen
- turn on the BenQ and wait 2 or more seconds
- turn off the BenQ and wait 2 or more seconds
- turn on the BenQ, you should get a good drive status and flashing should start
- this worked only one time after the computer is powered on or resetted for me
- writing and erasing works the same way, for writing the flash type at the prompt:
DosFlash w 7000 1 a0 1 4 A:\ixtreme.bin
- for erasing type:
DosFlash e 7000 1 a0 1 4 D8 (D8 is the sector erase opcode for the BenQ flash, if you need
to erase another drive lookup the value in the datasheet or in DosFlash.typ
- in my tests the VIA did not work with any motherboard, it seems some Intel boards can kill
the VIA trick


Flashing the BenQ on a NForce board and DosFlash16
----------------------------------------------------
- power the BenQ up before, at the same time or after the computer, it doesn't really matter
- use DosFlash auto or manual mode, both will do the trick
- if DosFlash will ask you to resend the mtk vendor intro press Yes
- turn off and on the drive, wait 2 seconds in between
- the drive status will be displayed and should be good, if not power the drive off and on
once more
- you can now continue as usual using DosFlash
- erasing and writing the flash has worked for me on NForce4 motherboards
- if you use auto mode and the ports are scanned there is the possibility that you'll get the
resend question for other drives like a NEC, this is because the NEC has no MTK chip and
returns a bad status, if you know the NEC is at that port you should press No and press Yes
only if the port of the BenQ is shown
- this is so much easier than using the VIA, but at least the VIA should give more people a
cheap alternative to flash their drives and I bet most will already own this card


Flashing the BenQ with a VIA card or NForce board and DosFlash32
------------------------------------------------------------------
- connect a 2nd power supply unit to the BenQ, don't turn it on yet
- cold reboot or reset the computer
- turn the BenQ on when you are in Windows XP
- start DosFlash32
- DosFlash32 will ask you if you wanna resend the mtk vendor intro cmd, press Yes
- turn off the drive, wait 2 or more seconds, turn on the drive
- the flash should be recognized by DosFlash32 and you can use it as usual
- after closing DosFlash32 you can start it and use the power off/on trick again
- reading/writing/erasing were tested and worked for me without a prob


Many thanks to jumba for the great idea of BenQ polling!
Thanks to Jumba, Redline99, TeamModfreakz and Tiros for testing and support!


************************************************************************************************


DosFlash and DosFlash32 V1.2 Beta
-----------------------------------
- bug fix for BenQ recognition
- manufacturer and device id are sometimes 0x00 for a correct installed switch
- this issue is fixed with an additional ATAPI device reset before the mtk vendor intro is sent

Thanks to Redline99 who fixed my buggy code by adding one line! :)


************************************************************************************************


DosFlash and DosFlash32 V1.1 Beta
-----------------------------------
- DosFlash.typ modified for better BenQ support
- DosFlash16 Flash Manufacturer and Device ID screen output restructured
- flash chips are first erased before writing starts
- DosFlash32 no reenable of DVD-ROMs in device manager after flashing, this means you can't see the drive
and maybe have to activate it manually again in device manager, this could give better compatibility and
hopefully no more blue screens

Many thanks to Jumba, Redline99, TeamModfreakz and Tiros for inspiration and help!


************************************************************************************************


DosFlash and DosFlash32 V1.0 Beta
-----------------------------------
DosFlash can be used to read/write/erase the flash chips of most CD/DVD-ROM drives
that have a mediatek chipset installed. DosFlash is for DOS flashing, DosFlash32
for Windows flashing.


Features:
-----------
- flashes IDE and SATA drives
- supports parallel and serial flash chips
- flash drives in Windows with direct port access
- no vendor cdb flashing commands are used
- tested with the following drives:
- TS-H943A MS25, MS28
- SH-D162C
- SH-D163A
- and some other drives like Liteon, Hitachi, ...
- NEC drives are not supported, cause they have no mediatek chipset installed


DosFlash
----------
DosFlash supports two flashing modes, Auto and Manual. If you type DOSFLASH at a DOS prompt it
will start in Auto mode. All drives and the corresponding flash chips are detected automatically.
If you can't get a flash chip recognized due to a bad flash or other problems you should use the
Manual mode. In Manual mode you can enter all the parameters used for flashing by hand. The
following help screen is displayed if you start DosFlash with a wrong number of parameters:


DOSFLASH by Kai Schtrom, 08/05/2007 (Ver 1.0 Beta)
DOSFLASH [R|W|E] [PORT] [PORT TYPE] [DRIVE POS] [FLASH TYPE]
[FLASH SIZE] [FLASH SECTOR ERASE OPCODE] [FILE NAME]
R: Read FLASH
W: Write FLASH
E: Erase FLASH
PORT: Port to send command to
PORT TYPE: 0 for IDE, 1 for SATA
DRIVE POS: A0 for Master, B0 for Slave
FLASH TYPE: 0 for parallel flash, 1 for serial flash
FLASH SIZE: size of flash chip in number of banks
FLASH SECTOR ERASE OPCODE: individual sector erase opcode command byte
this is only needed for erasing a serial flash
FILE NAME: name of the file to read/write from/to flash
All numbers are intepreted as hex values!

Example Usage:
"DOSFLASH R 01F0 0 A0 1 4 C:\flash.bin"
=> Read serial flash with a size of 4 bank (262144 bytes) from Master Device
on IDE port 0x01F0
"DOSFLASH E C000 1 A0 1 4 D8"
=> Erase serial flash with opcode 0xD8 and a size of 4 banks (262144 bytes)
from Master Device on SATA port 0xC000


Explanation of the Parameters:
--------------------------------

[R|W|E]
---------
- this will set the mode of flashing, it is recommended to first try read on any
drive, if the read will fail, it is highly unlikely that a write or erase will
succeed

[PORT]
--------
- the port to which the drive is connected, a port number should always be entered
in hexadecimal and have 4 hex digits, valid ports are: 01F0, 0170, C000, C800
- this option can be used if your PCI adapter card or on board IDE/SATA ports are
not identified by the auto mode

[PORT TYPE]
-------------
- the port type tells DosFlash what type of port is installed on the before entered
port address
- valid values are 0 for IDE and 1 for SATA
- make sure you never mix the wrong port with the wrong port type, this could give
strange results or in the worst case a bricked drive

[DRIVE POS]
-------------
- old style IDE channels have the possibility to connect two drives at one IDE
channel, the first drive is called the master, the second drives is called the
slave
- you can select which drive should be flashed on the channel, A0 selects Master,
B0 selects Slave
- on SATA ports this value is always A0, cause you can only connect one drive to
a SATA port, so for SATA you will always type A0 here
- it is not recommended to flash IDE drives with another drive connected to the
same IDE channel, this could be risky if something in the Master/Slave selection
fails

[FLASH TYPE]
--------------
- there are two types of flash chips out for CD/DVD-ROM drives atm
- the older type is parallel flash, which is also supported by mtkflash for example
- the newer type is serial flash, which is supported by flashers like XSF
- the problem here is that no tool is out that can flash serial flash chips on
SATA ports

[FLASH SIZE]
--------------
- this is specifies the flash chip size in banks
- one bank is always 65.536 bytes in size
- if you know your drive has a flash chip of 262.144 bytes in size you need to enter 4

[FLASH SECTOR ERASE OPCODE]
-----------------------------
- the opcode used in the flash chips datasheet for erasing
- for serial chips this command can be different from the standard and needs to be
entered for flash erase
- for parallel flash chips you can enter a dummy cmd byte, the integrated command
should work on all parallel flash chips without a prob

[FILE NAME]
-------------
- name of the file that should be used for flashing
- for reading operations this should be the output file
- for writing operations this should be the input file


Hints and Warnings
--------------------
- read, write erase TS-H943A MS28 after the firmware stealth has been disabled with Enable0800 disc
- this only works one time, after the first mtk vendor specific intro cmd is send
- if the mtk vendor specific outro cmd is send the chip goes back to stealth mode and you need
again the Enable0800.iso to disable it
- therefor the mtk vendor specific intro is send at program start to all present devices and the
mtk outro is sent at program end
- if you have a chip manufacturer id of 0x02 and a chip device id of 0x02 for the TS-H943A
the flash chip is in stealth mode and won't give access to any reading, writing, erasing
- always have a look at the DataSum generated, this is exactly the DataSum of mtkflash
- the DataSum is calculated as the sum of all bytes of the firmware in a short integer
- to make 100% sure that the flash is written right compare that DataSum to a known one
- this tool has not been tested on all drives out there, the typ list is simply copied from well
known programs like mtkflash and XSF
- always try a flash read on a not yet tested drive before doing anything else
- if the read doesn't succeed it is highly unlikely that a write or erase will
- some LiteOn drives seem to have probs to write the firmware correct, this prob seems to be
related to windows register flashing, cause even an assembler app can't do this error free
- if you get errors on LiteOn drives, write the flash two times in a row
- for direct port I/O in windows the givoio.sys driver is used, this driver is loaded at DosFlash32
start and unloaded at program end, be warned, this driver can possibly make your system unstable,
it's intention is to let privileged assembler instruction like in and out pass, even in windows,
if this driver is not used you will not be able to get direct access to port registers
- DosFlash was tested on MS-DOS 6.22 and later, you can easily copy it on a MS-DOS boot disk created
in Windows XP and start DosFlash directly from the disk
- don't forget to also copy the DosFlash.typ file, it has all the informations about flash chips
for auto mode flashing
- DosFlash32 was tested without a prob on Windows XP SP2, you'll need also the typ file for the
win version
- DosFlash32 will deactivate all CD-ROMs in device manager at startup, this is better for flashing,
cause Windows seems to poll the drives all the time and this could result in a bad fw file or
a program hang, the drives are activated again at program end
- you should make sure that the flash is not in an erased state at program end, cause device manager
don't like drives that do not respond to the inquiry command
- deactivating all CD-ROMs could take a few seconds, so please be patient at program start
- DosFlash and DosFlash32 will try to scan for the VIA 6421L Raid Controller card, based on vendor
id 1106 and device id 3249, it doesn't matter if the card driver is installed or not


goodluck
 
hello..you lost me now lol wity that lot ha........


not good this ....

i no what my problem is... its my pc ive just put a windowns floppy disc in and set agAin in bios to boot frm floppy to get into doss prompt and guess what it dont so some how my pc has stoped booting into doss and the bios is set to boot from floppy first

? anyone
 
Last edited:
the only thing ive done diff to my pc is last week is ive changed in windows from fat 32 to ntfs so i could do a game as it was to big 6 gig ......

? would that be the problem as i carnt get into doss no more not even with a windows boot up floppy ..just tryd it

? anyone
 
changing to ntfs wont stop a floppy booting into dos just means you wont be able to access the drives, but your A:> prompt will be ok, have you got boot from floppy selected in the bios
 
Last edited:
this could turn into " l have now had it and l am kicking my xbox around the room " thread lol .. lve had more luck with a-drives than usb sticks
 
Back
Top