Where is Chimp on UnleashX?

Hey all, so I'm gearing up to upgrade my XBox's HDD. I have all the tools to open the machine, and a compatible IDE HD is on its way. I have FTP'd the necessary files (Chimp, linuxboot.cfg, and so on) to the requisite folders as the how-to's explain.

How I am puzzled by one thing. All the guides I have read say I should FTP the Chimp folder, unrenamed, to the root of the E drive, and then when I am in the process of upgrading, I should go to the 'Applications' folder on UnleashX and launch chimp.

But I have looked, and Chimp can't be found. But there is a file called LPARTX, which when launched becomes Gentoox. What the hell are these?

How do I get Chimp to launch?

 

It doesn't go on the ROOT of E:\, it goes into E:\Apps or F:\Apps.

 

I tried that, too, and it still wouldn't show up.

 

Yeah, just confirming Chimp still won't appear when I have it in the 'Applications' folder. I did not rename the Chimp folder, either.

I have three choices in the Apps folder on UnleashX:

LPartX
NKPatcher Settings
XBMC

Can anyone help??

 

LPARTX that boots to Gentoo is the launcher for Chimp once it opens you should be given a set of options and just hit the one that says fatx and it should launch chimp it may ask you to press enter if your not using a keyboard just hit A

 

Ahhhhh I see! That wasn't made clear. Ta!

 

Help everyone, this isn't working for me.

I launch LPARTX and go to FATX option (having swapped the cable from the DVD to the new HDD) but it hangs when trying to launch Linux. It looks like two little red exclamation marks appear.

I also note that when trying to put Xromwell on the E Drive, my FTP program, GFTP (On Ubuntu), cannot send over 'md5sums', saying '450 cannot access file'. Can someone help?!

 

Folks,

I am utterly lost with this. I've been working on it all night, and I'm at my wits end. I've moved to Filezilla but it won't even see the XBox's filesystem. It says 'failed to retrieve directory listing'. What the hell am I supposed to do?!

 

Try my tutorial, maybe you are missing something..
check the jumper settings

https://www.youtube.com/watch?v=3WdstTRnINk&list=UUps0V_MhxlnIvX6RsPZBlxw

 

Yeah, your tutorial is pretty much entirely different from everything else I've seen. I have a softmodded XBox - no modchips inside. I'd prefer to keep it that way, as I barely have an idea which end to hold a soldering iron.

I've been following both parts of this tutorial: https://www.youtube.com/watch?v=726sttXBFpM

But it's this Xromwell thing that won't transfer properly that I suspect is the problem. Help, anyone?!

 

Anyone at all?

 

Nobody?! Am I the only person who has encountered this error? Surely someone can help!

 

Use the version of chimp in the link above, maybe it's as simple as that..

a run down:

burn the the iso to a dvd, or extract and FTP but just using a dvd is much easier..
copy Lpartx folder to e:\Apps copy the configuration file to e:\

close out of file explorer and sit on the unleash dash for 5 minutes

disconnect dvd ide and plug into drive set to SLAVE

open file explorer e:/Apps/LpartX and run the .xbe

load Chimp

a black log log screen will appear, it will promt you to press enter to continue, press A


SCAN HDD and check if both disks show up

do a full disk copy to SLAVE a stock 8gb drive will take about 20minutes to copy

when it's done you will be back at chimp main menu

LOCK SLAVE DRIVE FROM MOTHERBOARD

Shutdown

 

Thanks. Booting from the DVD worked to get the hdd tools up, but now it's not detecting my second HD. It's a Hitachi Deskstar 500GB IDE, but no matter what setting I put the jumpers on - slave, cable select, force detect device 1 - it just insists it's still connected to the Philips DVD drive (even though the IDE ribbon is in the second drive).

The second drive is definitely receiving power. There's, like, four different ways of configuring the jumpers for slave, too, which is confusing.

I'm sorry to be nagging about this, but I just want this to work. I have checked the HDD compatability list for this brand of drive and it seemed to be a safe bet.

 

Guys, is there any way to salvage this? I am looking at XBOXHDM as an alternative, but it requires a desktop PC (I have a laptop) and Windows (I have Ubuntu). Also XBOXHDM looks way complicated.

Is there anyone who can help? Or do you know anyone who can? This silence is maddening.

 

You aren't providing enough details on what you tried for anybody to help. If chimp didn't detect the target drive, it simply means you swapped in the IDE cable too late. Did you follow LeHaM's instructions?

 

your deathstar drive (The current working drive in the xbox) needs to be set to either MASTER OR CABLE SELECT.

both hdd need to be connected to power before boot (use a Y splitter) connecting the SLAVE (new) drive whilst the xbox is on will cause a drop and either reset the console or mess up the ide controller and make it sort of freeze (this happened to me), making it not see the new disk even when refreshed..

If you are using an external supply it needs to be ground tied to the xbox (alligator clip between the xbox shielding and external PSU ground)

if you dont the above will happen when you hotswap the hdd's...


dont forget to scan new drives when you load chimp

hope this helps

 

Shouldn't it already be in that state if I haven't touched the original HDD yet? I don't want to have to fiddle with its housing until it's ready to be completely removed.

Makes sense. I've been making sure the HDD is connected via my Y-splitter at all times.

Yeah, I've been doing that.

The problem is I'm now using the DVD drive to load Chimp so I am unsure when to do the swap. Can it be done as soon as Gentoox is loaded, or must be be after loading chimp but before the next step?

Thanks folks.

 

Hey everyone,

Good news, last night I followed LeHam's tutorial once again. Despite doing everything the same as the last time, this time it mysteriously decided to behave! It booted to Gentoox no trouble, and actually detected the HDD. Seems to have locked fine, as well. I can't fully test until Thursday, but things are looking up!

Thanks for your help, and sorry for getting a bit distressed at times

 

If it didn't work, once you turn off the system and turn it on again. It would error (if locking failed).