Print

[ZeroP]

My old firmware, which I did not flash myself, was iXtreme 1.5 on a BenQ drive. I don't remember which version my 360 is. It's either a Falcon or a Zephyr; whichever one doesn't have an HDMI port.

Anyway, I was using JungleFlasher. I had hooked it up to my onboard SATA, turned my PC on and used the half-open tray method to get it into vendor mode. I actually had to use the Intro / Device ID and power-off/power-on method to really get it to work.

So, I followed the directions in the user's guide, clicked read, saved to file, and then write and all that (I didn't click erase first, something I may live to regret), but the output window kept saying, 'verify failed', or something like that. I looked it up and everyone seemed to get through it OK, even though it said that, so I proceeded to click Outro / ATA Reset. This is where it started acting weird.

My whole PC froze up for about 3 minutes, then it came back and then froze again. I let it run for about 15 minutes and decided it was enough. Unfortunately, it didn't work and, now, I get an E65 error every time I bootup my 360.

To make matters worse, every time I turn my 360 on while connected to my PC, it causes it to freeze again with the same behavior. So, I can't even get back to using JF anymore.

I've tried updating my BIOS and, also, my VIA RAID drivers but with no luck. I've also tried using different SATA ports. I can't uninstall my VIA drivers (which I don't think is the problem, exactly, because I flashed my old 360 with this same computer) because my primary HD is SATA.

And, if my 360 is on BEFORE my PC, it won't get past the RAID scanning screen.

So. What are my options, here? I've saved my old firmware and keys and all that like the guide said. I've googled this problem but only some are exactly the same as mine. The ones that are the same, have no answers.

[TheDemonIII]

try using dosflash or iprep (in dos) to avoid the freezing. you need a compatible scsi chipset like nforce or via, which you may or may not have.

PS: i wouldnt be worried. benq drives really cant get messed up from a bad flash so long as you keep your original firmware. first thing u wanna do is get that thing erased, then write the new fw

PPS: to check if you have any scsi ports type "msinfo32" (without quotes) into run. go to components->storage->scsi. if any ports show up there, they are scsi and will work in dos

This post has been edited by TheDemonIII: Jun 25 2009, 09:31 PM

[ZeroP]

Well, that's certainly good news. Thanks for the info.

I've tried Dosflash... in DOS. Using a custom bootable disc, Hiren's BootCD and, finally, the ISO image + iPrep that was covered in the xbox PDF guide.

No matter which method I use I still can't get Dosflash to work. It always hangs on one drive and returns the error, '0xE000 SATA Pri Master ATAPI no identify possible'.

So, I looked up the error and it seems I can use l-o-eras to try and erase the FW drive but I can never get FF72 - always FF80. Right now, I'm going to stop for the night and resume tomorrow. Do you think turning the unit on and off or unplugging the power from the drive and plugging it back in will help towards FF72?

I'm willing to try anything, now.

This post has been edited by ZeroP: Jun 26 2009, 06:30 AM

[ZeroP]

Oh my God, I got it to work..

Put the iPrep files on my IDE hard drive, disconnected all other SATA drives and switched the SATA port that the 360 was connected to on my motherboard.

Dosflash saw it, erased it, and flashed it again perfectly. I was sooo happy when I clicked the eject button and it came open (IMG:style_emoticons/default/biggrin.gif)

Anyway, maybe people can use this info... Thanks, again, for your help! (IMG:style_emoticons/default/biggrin.gif)

[TheDemonIII]

glad to see it worked. dosflash (because its in dos) is often picky about which ports it likes to see. at least now u know in case anything happens again