Jump to content


Photo

Duox 2 Reboot Loop


  • Please log in to reply
7 replies to this topic

#1 aladdin64

aladdin64

    X-S Member

  • Members
  • Pip
  • 130 posts

Posted 16 December 2005 - 12:53 AM

Hello.

Anyone knows what could be about? It just shows the Xecuter 2 text under the blue logo and then reboots. Happens when you try a boot DVD as well. Tried different HDs and different DVD-players. Still the same thing. Sounds like a "Clock Loop" but thats not possible with a modchip and a boot DVD is it?

Anyone got ideas or have experienced this before?

Regards

Aladdin

#2 redbaronnl

redbaronnl

    X-S Enthusiast

  • Members
  • 7 posts

Posted 03 February 2010 - 08:27 PM

awfull bump, but this is what happens to me aswell actually, i have even rebuilt the HD with xboxHDM and the problem persists

Edited by redbaronnl, 03 February 2010 - 08:28 PM.


#3 justtaint

justtaint

    X-S Genius

  • Members
  • PipPipPipPip
  • 944 posts
  • Location:Chicago
  • Xbox Version:v1.6
  • 360 version:v1 (xenon)

Posted 06 February 2010 - 08:40 AM

What does it do with the modchip disabled?

#4 redbaronnl

redbaronnl

    X-S Enthusiast

  • Members
  • 7 posts

Posted 07 February 2010 - 04:46 PM

with the modchip disabled it boots wit the normal green X, however an error pops up, but this is probably because my harddrive is unlocked ( so i do need the chip)

#5 litspliff

litspliff

    X-S X-perience

  • Members
  • PipPip
  • 395 posts
  • Location:nebraska
  • Interests:electronics, music, your sister.
  • Xbox Version:v1.0
  • 360 version:none

Posted 12 February 2010 - 12:19 PM

2 possibilities i can think of....
  • bad flash (wrong .bin(ary) image size, or corrupt .bin(ary) image.
  • shtty install
i'm leaning towards bad flash from a bad download, or a 512KB image squeezed down to 256KB. checksums are your friend. get a second opinion on that bios image (get it somewhere else that you can do a checksum).

Edited by litspliff, 12 February 2010 - 12:21 PM.


#6 redbaronnl

redbaronnl

    X-S Enthusiast

  • Members
  • 7 posts

Posted 13 February 2010 - 12:07 AM

I strongly doubt it has anything to do with the chip, since this has remained untouched since it was first time installed. It has worked fine for a very long time, with a 120gb harddrive.

At some point the drive was taken out, wiped and used in a windows pc, the xbox has been lying safely in a box until recently. I tried putting the same harddrive back ( formatted it, even made it RAW using some software, and when all that failed i tried this xboxHDM thingy)

So far no good.


My guess would be then that these installs would be corrupted, but i also seriously doubt this one because i have downloaded several versions of slayers, severeal times, downloaded xboxhdm twice, put at least 4 kinds of different software in the C folders ( varying from original xbox dash to evox to avalaunch)

So far no succes

#7 FallsInc

FallsInc

    X-S Hacker

  • Moderator
  • PipPipPipPipPipPip
  • 2,280 posts
  • Gender:Male
  • Location:Ohio
  • Xbox Version:none
  • 360 version:none

Posted 14 March 2010 - 03:57 AM

did you format the drive again with fatx? based on what you have said, the xbox is booting to a hard drive with no partitions.

#8 litspliff

litspliff

    X-S X-perience

  • Members
  • PipPip
  • 395 posts
  • Location:nebraska
  • Interests:electronics, music, your sister.
  • Xbox Version:v1.0
  • 360 version:none

Posted 18 April 2010 - 09:40 AM

not likely a HD issue. if it was, xecuter would spit a service code out.
when you have a chip, you can put any HD in it, even unpartitioned and unlocked or locked to a different xbox.
you should still be getting an error code.

i still think it's a bad bios image or faulty chip or faulty install.

what happens using the other bios bank on the chip?

Edited by litspliff, 18 April 2010 - 09:41 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users