Jump to content

Welcome to our site

Take a moment to join us. You can sign in with Facebook with a couple of clicks. No need for a lengthy registration. We also have Tapatalk support so you can use this forum on your phone the same way you use facebook. It will keep you notified.

Recommended Posts

Hi there, I'm having some strange issues formatting SATA HDDs on a 1,6 Xbox with and Aladding xt +2 modchip. I have upgraded to a 1TB SATA drive with the SATA/IDE adaptor and the 80 wire cable. I just did this on a Xbox 1.0 and it worked just fine, but when I try on the 1.6 Xbox even though I try to write the partition at 927.7 GB it never shows up correctly after the reboot, the F drive is only 120GB and after many tries still cannot access the full amount of memory.. Tried a bunch of times, wondered if something was wrong with the drive (it was used but was working perfectly before I upgraded my computer to an SSD) so I went out and bought a brand new 2TB Seagate drive and I'm still having a ton of weirdness. When I try to make both partitions 927.7GB it still shows very strangely after a reboot. It shows (again) that the F drive is only 120GB but is showing the G drive at like over 1700 GBs. To my knowledge the largest size these partitions (with 64KB clusters) can be is 1024GB and anything over that will not work correctly. I kept messing with it and I can't get the two equal sized partitions no matter what. I have tried loading some games on and it seems to work (games load), and the memory seems to display correctly (minus the size of the game copied) after I copy a game. Should I bother worrying about this? The GBs do after all add up to pretty much 2TB... It just seems so strange because I was really pretty sure you can't have partitions over 1TB.. Also since I had no issues before on the 1.0 version I was thinking it could just be the Xbox somehow...? That seems wrong too though...

Any clarification or suggestions would be super appreciated, thanks a bunch.

Share this post


Link to post
Share on other sites

i had the same issue 

 just need to flash the bios using the latest hexen disc 

 

and that will fix your issue, if you plan to keep the 2tb in there flash your chip with the bios for the F and G drive if you only want the 1tb use the bios for just the F drive

Share this post


Link to post
Share on other sites

Does XBPartitioner v1.3 display an error message that LBA48 support is not found?

At the top of XBPartitioner's main screen, what version of LBA48 patch is displayed?

 

 

Edited by KaosEngineer

Share this post


Link to post
Share on other sites

Nope, no errors at all. Also, to the previous comment - I may try that if nothing else works - but I did reflash the modchip with a new (or new=ish) bios that is for a 1.6 version right after installing it. Thanks for the replies tho:)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


Board Life Status


Board startup date: April 23, 2017 12:45:48
  • Similar Content

    • By booyaa5
      Does anyone have any original xbox controller that is pad hacked. I want to build arcade cabinet.
    • By PaulRevere
      I'm  a noob and I need a little help please. I have softmodded my Xbox with Unleash X and now I want to hard mod it. I have burned Hexen 2018 disc image file to a disc and now I am trying to figure out how to get Xbox Bios Checker either v4 or V5 onto a disc. I burn the files to the DVD R disc but the Xbox won't recognize it.  What Files do I need to burn onto the disc? Should there be a disc image file? What am I doing wrong? Do I have to hardmod it first for this to work? I'm sorry but I have looked at so many videos and searched so many forums that now I'm lost in the forest. Please break out the crayons on this one to show me how to do this. Thank you.
    • By Daver80
      Into quite a bit of a mystery here. Sold a fellow a modded Xbox and he traded in an old busted Xbox to save a few bucks so now I'm trying to fix it. When turned on the Xbox turns off pretty quickly but then restarts immediately, then the same again, turns off and then back on a third time and then stays on and shows flashing orange and red lights (the odd time it will flash red and green just to deepen the mystery). Googling the problem results in many ppl saying it's an 'av pack' issue if the av cable is not the problem but the restarting thing tells me it's more likely a PSU issue or a bios/mod-gone-wrong problem. Pulled everything apart completely, thought I found the problem with a burnt contact point near the plugin. Re-flowed all 4 points just to be sure and no difference at all. Kept googling and found a few encouraging leads including this url Please login or register to see this link. and tried jumping that wire from the lpc pin 5. No f*ckin' joy. Also just a side note - the lpc vias are all plugged with solder (see pic) indicating that a modchip was removed at some point. Also I checked the solder points for the Xbox 1.0 TSOP and it looks like they've been done also - but the guy said he never modded that one. Thing is, the further into this I get the more convinced I am that this unit is fixable. Most people will just say eff it and chuck it or whatever but I really like to save old things if at all possible. I have included a pic of the wire I jumped (yellow wire) from the lpc pin 5 as the url tutorial suggested. The same pic also shows a mysterious blue wire that was here before I opened it. Asked the dude about the blue wire and he said no idea, never modded that one. In some of my Googling I found a post saying something about a D0 wire or DO wire described as a 'modchip enable wire', maybe this could be it? Any ideas about how to move forward or what the blue wire is for would be great, my thanks go out to anyone who has any ideas that might help,

×

Important Information

By using this site, you agree to our Terms of Use.