Topic: Resurecting A Dead Xecuter 2.2 Lite (Read 84 times)

kevbox · « **on:** October 28, 2003, 09:36:00 AM »

I flashed (well,,, atempted) my xecuter 2.2 chip through evox with the M7 bios. Everything was going well until the Xbox switched off,,,,,and then,,,,,,,Red/Green arghhh!!!! Now I cant even boot up off the evox disc! or use the normal MS dashboard cos I get the Error 05 code which says my machine needs a service!!

I flashed the thing with bank one selected but they both have appeared to have been wiped.

So do any of you clever people out there know what I can do to get my chip working again?

and

How can I restore the original MS Dashboard?

Cheers Guys

Specification

Xbox v1.3
120 GB HD
Xecuter 2.2 Lite

themadman123 · « **Reply #1 on:** October 28, 2003, 07:46:00 PM »

dude, I'm having the same EXACT problem, I wish I could help you out, but I can't. If there is anyone else out there reading this thread, PLEASE HELP if you can. Thanks, hope everything works out for you man.

kevbox · « **Reply #2 on:** October 29, 2003, 10:25:00 AM »

excellent! i like the way you are thinking, fortunately i thought the only way i could get it going again was to get another chip, so i did, still waiting for it to arrive (damn royal mail!). i suppose i can get the life back in to my badly flashed one by what u are saying so i could sell the new one on (or even return it). one question though, y do you think it erased banks 1 & 2 when i had bank 1 selected?, I'll let you know how it goes.

cheers

pdottz · « **Reply #3 on:** October 29, 2003, 03:02:00 PM »

he's right, hot swap or programmer is the way to go here.
and whats even better is if you have a locked dirve and your bios boots to the evoxdash.xbe instead od xboxdash.xbe (like mine.) that way incase this ever happens again you still have your original ms bios and it goes to dash while you work out what to do.
Another thing. when I first got my chip 2.2lite I didn't know you could flash multiple bioses on it. the site says not to. So I did a 1meg bin of just x2 4977. then yesterday I deciced I would try multiples just incase somethign ever went bad. So I used x2bm and loaded x2 4977 in 2 slots. 256/256 for bank 1 and cromwell on bank2 as 256/256. I switched my chip to ON (even though for me it doesnt matter since I got a bad chip stays on whether i want it to or not) then put it to unprotect and switched it to boot on BANK 2. x2 bios loads then evox and I flash my chip hoping for the worse. BUt it worked. now I have cromwell on bank 2 and x2 4977 on bank 1.
I know that evox will flash a 256 bin into all four slots. But Im going to try a 512 of the m7 using flashbios in cromwell. If this works then Ill never have to worry about a bad flash cause I could always fall back on cromwell.
sorry for the rant. just wanted to put some info out there incase you needed it.

kevbox · « **Reply #4 on:** October 31, 2003, 09:02:00 AM »

right guy's i've hit a problem,,,,,,

i've put the new xecuter 2.2 lite in my xbox to do the swap. but i get the cromwell screen where it says "Please insert the BIOS update disk". so i've burned about 7 coasters with xecuter_Flash_BIOS227 (cromwell) but it keeps chucking the discs back out. any ideas what i should be putting in there and what should the bios file be called? e.g. BIOS.BIN BIOSUPD1.BIN etc etc.

cheers guys

kevbox · « **Reply #5 on:** October 31, 2003, 11:02:00 AM »

it's a new chip and it's a v1.3 box with a Phillips drive and a 120GB HD. I'm having better luck with my HP CD-RW's as opposed to Datarite Red x4's. Although I've burned it a couple of times and althoug it recognises the disk (it displays the disk label) nothing seems to be happening afterwards. When I'm burning should i put the dummy file first i.e. name it 0dummy or just leave the bios.bin come first?

kevbox · « **Reply #6 on:** October 31, 2003, 11:10:00 AM »

Oh, and I'm getting "No Bios Update found...Halting!"

damn thing!

kevbox · « **Reply #7 on:** November 01, 2003, 04:47:00 AM »

Right guys, my xbox is driving me crazy, i really need an answer. When I boot up with the brand new xecuter2.2lite I get the FlashBIOS (Cromwell) screen that says "Please insert BIOS update disc" If burned so many now, nothing seems to be happening, I've put my 1MB bios.bin along with dummy file (300MB) onto a CD-RW which the Phillips drive is recognising great. When it loads i get "CD-ROM Label: UNTITLED_CD" so it is recognising the disc right? but nothing happens after that. what files is it asking me for? how do i get it kickstarted so i can be back into evox?

Please help.

d7onr8 · « **Reply #8 on:** November 01, 2003, 09:30:00 AM »

Look here too: http://forums.xbox-s...94&hl=flashbios

kevbox · « **Reply #9 on:** November 02, 2003, 06:37:00 AM »

Cheers guys for all your replies. Very helpful. I think I've narrowed it down to the media I'm using. As I have a Phillips drive, I've found numerous amount of people who have the same drive and same problem. But as it recognises the label, shouldn't this not be a media problem?

What do u think?

kevbox · « **Reply #10 on:** November 05, 2003, 09:44:00 AM »

please please please someone say something that'll guarantee it'll work, plllleeeaaassseeeee. :-(

I've tried all different types of media, even the memorex CD-RW's which people are recommending. I still can't get past the first screen where cromwell asks for a CD with the bios update from when i first put the x2.2lite in!

Every time I try, cromwell recognises the CD and display's its label e.g. CD-ROM Label: UNTITLED_CD, but nothing happens after that, I've even let it run on over night incase i felt the need to flash the chip 4am!

What else is there to do? I've burned the disks at UDF's Iso's xIso's etc. etc. with 1MB bios' like cromwell and even the new M7 bios. I've named them bios.bin BIOS.BIN biosupd1.bin BIOSUPD1.BIN etc. etc. etc.!!! I've put 100MB, 200MB, 500MB, 650MB dummy files on the disk, placed the bio file above and below the dummy file.

Please please please tell me what haven't I done to get it right???

Thanks Guys/Gals

kevbox · « **Reply #11 on:** November 06, 2003, 09:16:00 AM »

Just a thought, but would the fact I got a 120GB unlocked HD have anything to do with it?

spyg00se · « **Reply #12 on:** November 06, 2003, 02:42:00 PM »

i am using my original HD, but i am having the same problem on my 1.0 box with a Thomson drive and an X2.2 lite+ modchip.

firefucker · « **Reply #13 on:** November 06, 2003, 02:51:00 PM »

)
OK. Last try: I soldered the 2 bridges and did the TSOP flash, flashed the X2 and finally flashed the M$-Bios to X2. worked perfectly and took only a few minutes cause the xbox was already open

lol.
Stats: modded 3 times a xbox with x2 pro: 2 times flashed via LPT and once via TSOP
Next time I will do it again with TSOP flashing cause its the only way works ALWAYS!

Author Topic: Resurecting A Dead Xecuter 2.2 Lite (Read 84 times)