i have been at the end of my theather with this mod i did the hex edit with the values from my sata card which is via 6421 and i tried everything to get the drive recognised and some mentioned that the drive has to be in 0800 mode for it to be recoginsed is this true and if so how do i go about doing it? do i burn the 0800.iso in the xtreme 3.3 and just put that in the 360?
thanks

the 0800 refers to a seperate firmware used to get the sammy recognised within windows so that you can extract the secuirty sectors.

are you sure your asking the correct question ?

well my problem is when i boot my pc with the 360 drive connected after the main bois screen with the ram and primary hard drive and dvd-rom it hangs on the sata bios says searching for devices, so i unplug the sata wire and boot with the disc and when i get into dos mode i reconnect the sata wire and trpe the command A:\Mtkflash r backup.bin and then it comes up

A:\mtkflash r backup.bin
Mtkflash by Joseph Lin, MTK 1998 (ver1.83c)

Port: 170, Master/Slave : a0

and thats all that comes up. so i dont know what to do i edited Mtk flash with hex editor and put on the floppy and i cant get new drivers for my sata card as i bought the card off ebay and it didnt come in a box or with any sort of manufactars stamp on it here is a link to a pic of the card maby some will recognise it http://cgi.ebay.com/ws/eBayISAPI.dll?ViewI...ADME:L:RTQ:US:1

the picture shows a sata card with a VIA chipset, these are generaly tought to work ok with MKTflash.

as your using a sata card (as opposed to onboard) you might try using the /sata command.

A:\mtkflash r /sata backup.bin

i think i got the drive recognised , when i extract the firmware and opened my backup file with hex edit and i dont have a 4000-4200 range i extracted twice with 2 differant floppies and i get differant ranges like first was 4010 and no 4000 and second the closest to 4000 was 4018, the floppies i used warnt new maby this is the problem i the 2 times i extracted i got differant results can you explain this?

It seems you've missed a step in the tutorials. Read it over again and again. Follow it to the letter.


Yes, to get the drive recognised by windows you gotta burn the 0800.iso(AKA activate.iso, AKA Enable0800.iso) onto a DVD+R DL. Pop that disc in the 360 and leave it on, then boot up your computer.

To get it recognised in MTKFLASH, you leave the drive in it's normal state and edit mtkflash to your specific sata chipset.

So in other words, you do NOT enable 0800 to extract/flash your FW with MTKFLASH. Read the tutorials over again before you brick your drive.

Ahh no wonder I couldn't get the 0800.iso to work--I burned it onto a CD-R and not DVD+R DL. You've tried this and confirmed that it works?

Yes, I have.

I can't see why you'd have to use a DVD+R DL disc to burn the 0800.iso because there's no layer break information in the iso file. Wouldn't a regular DVD+R disc suffice?

No, because the firmware is looking for that byte in a certain spot. It happens to be about 7 gigs away from the last sector of the disc.

Did you use Nero to burn the 0800.iso onto a DVD+R DL or another program? If so, were there any special settings you use? Thanks for the heads up!

you should just be able to use clone cd to burn it, just to safe and not make a coaster i suggest you set the bitset to dvd-rom aswell.

How can you use clone CD to burn this .iso file without a .DVD file to tell it where the layer break is? This is the enable0800.iso we're referring to.

Yeah...and your point is?

CloneCD can burn a lot more than just .dvd files. In fact it doesn't actually "burn" the .dvd file at all when your burning 360 backups.

Just Write Image to File and select the ISO. Not too hard.

I did as you suggested and it worked. Thanks!

I'm having some trouble getting my Samsung in 0800 mode as well.

360 Hardware: TS-H943 ms25 H/W:005 Ver.A flashed to 3.3
Computer HW: Asus K8N-E using Nforce 3 SATA in IDE mode
Software: Used Alcohol 120% and CloneCD to burn two seperate Enable0800.iso on Memorex DVD+R DL disks.

To flash, I used a non-modified MTKFLASH on a floppy to extract the original DVD BIOS and saved off to several locations (just in case). Ran the included SAM360 that came with the 3.3 firmware to make the modified BIOS and reflashed back to the drive. Tested the modified BIOS with original 360 disk (Project Gotham) and played it through to make sure no errors popped up during play.

What I'm doing to get into 0800 mode: Turn on 360 with SATA connected. PC is off. Insert Enable0800 DVD. The drive seems to "grind" searching for something. (This happens on both my burned copies.) Not sure if this is normal. The XBOX 360 green light stays steady green. Turn on PC and boot into XP. Drive letter for the 360 never shows up, although BIOS before Windows XP boot up does recognize it along with the full ID.

I've tried several variations as I've seen suggested. Hotswap SATA cables after booting, waiting 5, 10... 30 seconds with the 0800 DVD, inserting it and keeping it in during XP boot, etc. Haven't found anything that gets the drive letter recognized in windows.

Troubleshooting suggestions? Should I reflash back to the original BIOS and retry modifying the BIOS? Is there possibly something wrong with my 0800 DVD? Should it "grind" like that when inserted? What should happen when the drive is in 0800 mode? What should I look for? (The guides aren't really clear on this point.)

TIA

Forgot to mention that my PC DVD burner is a LG 4166B with 1.2 BIOS and booktype set to DVD-ROM mode when burning. Not sure if that factors in, but there's the info if you need it.

Update: reflashed and I'm trying to make sure that I have a proper Enable0800.iso made. This time around I used ImgBurn to make the image. I think that it could be the problem. I've noticed that in the past it seemed to hang around 50% when burning. I checked my log this time and pulled this out:

I 02:12:41 Source File: D:\Temp\xtreme33\Enable0800.iso
I 02:12:41 Source File Sectors: 129,824 (MODE1/2048)
I 02:12:41 Source File Size: 265,879,552 bytes
I 02:12:41 Source File Volume Identifier: XBOX360
I 02:12:41 Source File Implementation Identifier: Daikin U.S. Comtec Lab
I 02:12:41 Source File File System(s): ISO9660, UDF (1.02)
I 02:12:41 Destination Device: [0:3:0] HL-DT-ST DVDRRW GSA-4166B 1.02 (E:) (ATA)
I 02:12:41 Destination Media Type: DVD+R DL (Disc ID: RITEK-D01-01) (Speeds: 4x)
I 02:12:41 Destination Media Sectors: 4,173,824
I 02:12:41 Write Mode: DVD
I 02:12:41 Write Type: DAO
I 02:12:41 Write Speed: 2.4x
I 02:12:41 Link Size: Auto
I 02:12:41 Test Mode: No
I 02:12:41 BURN-Proof: Enabled
I 02:12:41 Optimal L0 Data Zone Capacity: 64,912
I 02:12:41 Optimal L0 Data Zone Method: ECC Block Boundary
I 02:12:41 Filling Buffer...
I 02:12:42 Writing LeadIn...
I 02:13:18 Writing Image...
I 02:13:18 Writing Layer 0... (LBA: 0 - 64911)
I 02:14:53 Writing Layer 1... (LBA: 64912 - 129823)
W 02:33:47 Failed to Write Sectors 65552 - 65583 - No Seek Complete


Crapola. I've got another HP DL drive that I'm going to try and burn with (just finished in fact) and I'm going to see if that's the issue. Already I noticed that the other writer wrote the entire image to Layer 0. I'll be pissed off if my LG isn't working as it should. I really don't want to get another burner if I have to.

Second Update: Damn it. It was the 0800 disk on my LG. The one I burned off of my HP laptop works just fine. In fact, I'm backing up a game right now using the same hardware. I'll try burning it when I'm done with the LG and see what happens. What's another coaster at this point? I'll be fine (mentally) if I can still do backups with the LG. But if I get another coaster.... man, that will totally suck.