Print

[Bocasean]

I'm sorry to comment on such a buried thread, but I've been successfully softmodding and cloning new hard drives to the Xbox for 2 years now, and up until recently I've never had any problems.  I'm hoping that someone can steer me in the right direction.

I use Chimp (thanks to Idotsfan for creating it!) and I exclusively use WD 80g hard drives.  I've successfully cloned over 85 Xboxs using the same method, but for the past 2 months I've been having issues.

Chimp loads, I am able to swap the cables, the master/slave tabs are set as they've always been, etc.  Once I'm in the menu, I check to make sure that the 80g drive is recognized with the "Scan physical IDE devices" option, then I clone the C partition and the E partition as I've always done.

I then lock the drive from motherboard and shutdown the system.

This is what I have always done and, usually, it works without problem.  I will disconnect the splitter, set the newly-cloned 80g drive to Master, and hook it up as the old drive once was.  At this point, I turn the Xbox on a again, and as it's booting, I always eject the Chimp disc while the flubber is still showing on screen, having the disc drive closed before the flubber finishes.  

At this point, when everything is working normally and successfully, the UnleashX symbol pops up on screen and, shortly thereafter, the UnleashX menu loads.  The new hard drive is a success.

Sadly, for the past 2 months, I've gone through 6 different Xboxs and at least 10 hard drives and, whenever I turn the Xbox on with the new 80g drive installed, it goes to the "Chinese Screen" as I call it.  It's the error screen that says to Call Customer Service in many different languages.  In essence, this hard drive is toast and I just wasted money.  Throughout the past couple years, this has happened sporadically, but I've simply chalked it up to a bad hard drive in the lot and moved on.  Sometimes, an Xbox will burn through 3 or 4 hard drives and I'll give up on it.  This has only happened 6 or 7 times in the 80-plus that I've cloned.  Lately, though, this has happened with every Xbox and hard drive that I've tried.

What can I do?  Why does it sometimes work and sometimes not?  Do I need to do more in Chimp after I have installed the new drive?  Is it a hard drive problem or an Xbox problem with certain models?  

I'm at a loss.

[Infamous Ob]

Damn. This program is sick! I just ran it on my v1.3 just to see how it worked and everything. Man, it's thorough and very user friendly. I definitely look forward to upgrading my HDD with it.

[ldotsfan]

I've started on a remake of chimp26 on a newer 2.6 kernel: 2.6.18 Here's a preview of the main menu:



1. It now works on xbox 1.6 on-screen (instead of telnet) although there is an ugly blinking cursor which is a slight nuisance  

2. More menu options: displaying hdd security status, backup of eeprom, reboot, shutdown.

3. Ability to use master passwords: TEAMASSEMBLY or XBOXSCENE on the slave hdd on DVD IDE connection.  

4. Shares the same code base as LPartx hence have a configurable network setting and formatting of extended partitions and drop to shell option. It now uses Gentoox Loader for xbox 1.6 support instead of xbeboot.

5. Experimental(Read:dangerous) support for FATX (16K,32K,64K clusters) partition mounting.

Should be ready for a beta release soon.

[unclebree]

Wow, what a coincidence. I came here today with a question about this very subject.

I'm trying to telnet into my v1.6 box, and of course I'm having all the usual problems that apparently everyone else has.

I set up my box the way I "think" I'm supposed to -- set to STATIC, port to 23, HTTP Proxy, etc

I'm able to ping to it, and I'm even able to telnet into it before I use chimp, but when I run chimp and try to access it I get the usual "unable to open..."java script:emoticon(':grr:',%20'smid_11')

Now I see some hope on the horizon!

I'll patiently wait with my fingers crossed and check back (every 10 minutes!) to see how you're coming along with this.

I'm sure glad there a so many people out there smarter than me!java script:emoticon(':jester:',%20'smid_13')

Thanks [/u]BIG TIME ldotsfan!!

[Heimdall]

Original chimp doesn't care what IP address you statically set your box to - it ALWAYS uses 192.168.0.3 - that's why you can't connect to it........

Give your PC a static address in the same range (192.168.0.x) and it will work.

By the look of it this new version will allow you to change that.

[unclebree]

I did set the IP to STATIC and set it to 192.168.0.5 (The guide said anything higher than .0.4).  I then tried to telnet to it using 192.168.0.3 (numerous times), and I just couldn't get into it. (Not even pinging to it.) But, when I would let it get it's own IP (192.168.254.2), I could ping to it and even telnet into it, just not when Chimp was running.

I sure hope this new version will get rid of that.

Best of luck to you on finishing it, not just for me but for what I'm sure are many others!

[Heimdall]

Try it again, and when you've set your PC IP address to 192.168.0.5, subnet mask 255.255.255.0, open a command window on your PC and type ipconfig, hit return, and see what it says.

[unclebree]

Okay, I tired that and same thing. I opened my connections and set it to assign IP 192.168.0.5 and subnet 255.255.255.0 (actually the subnet did that automatically when I set the IP.)

Then I opened the command prompt, typed ipconfig, and it threw out some stuff about media disconnected (I'm assuming this is my DirecTV, which was set up on media share), and showed the new IP and subnet.

I then turned on the Xbox and telnet(ed?) to it and saw in the command prompt "FTP ready to UnleashX," or something to that nature. So, I closed the command prompt and started Chimp on the Xbox -- got my usual green screen -- and opened the command prompt again and typed telnet 192.168.0.3, and got the usual "could not open port...."

I know this isn't supposed to be this difficult, and there's probably some little something that I'm just not getting right, but I'll be damned if I can figure it out.

Thanks for trying to help though. I guess I'll just have to wait on this new update to Chimp and hope like hell it gets me past the telnet part at least. (Then I'll probably just get stuck at a new hurdle, but at least it'll be a new problem and not the same one over and over.)

[Bomb Bloke]

You say that when you let your PC "get it's own IP", it automatically came up with the address 192.168.254.2 - this would imply that there's a DHCP server somewhere in your network, which I'd assume is a router (like a DSL/cable combo-router box for eg).  Is your PC wired to the console through this router box?

[unclebree]

Yes, there's a wireless router, but when I couldn't telnet into the Xbox I disconnected it and used a wired ethernet port instead, but still wasn't able to telnet in when Chimp was running. However, I could telnet to the box when it was at it's dashboard.

[xman954]

change DHCP on you router to 192.168.0.X instead of 192.168.252.X
start DHCP at .50

restore if wanted when done




This post has been edited by xman954: Jun 30 2010, 05:53 AM

[unclebree]

What about when I disconnect the router and use an ethernet port instead? 'Cause when I do, I'm able to ping, and even telnet into the box, just not when Chimp is running.

I wouldn't think the settings on the router should matter if I'm not even using it. I went into the router to change the settings, but once I got in, I was afraid I'd screw something up and mess up my whole home network.

I think I'll just have to wait and hope ldotsfan comes up with this new update. I guess I can "try" and be patient. (Heck, after being married to the same woman for more than 25 years you'd think patience would come natural to me!)

Thanks for ideas, though.

[ldotsfan]

QUOTE(unclebree @ Jun 30 2010, 11:27 PM)

I think I'll just have to wait and hope ldotsfan comes up with this new update. I guess I can "try" and be patient.

I'm still working on it:
1. The cloning function. Untested.
2. DHCP. Not working. Not needed for xbox 1.6 since you can now use the tool on-screen with the controller but a good-to-have feature. Static IP works though.

I can release something though if you are keen to test the cloning which may be broken.

 

[unclebree]

Thanks ldotsfan, but I think I'd be better off waiting 'til you have a more stable version.

Right now if something were to go wrong I wouldn't know if it was me or the program. (More than likely, it'd be me!)

Actually, right now I'm waiting on a SATA to IDE converter so that maybe I can use XBOXHDM on the drive.

(Does anyone know if this'll work?)

Oh well, at least with this converter coming in the mail and with ldotsfan update to Chimp, it looks like my options might be improving.

I've already burned the ISO, but the only way I could hook up the new HDD was to use the IDE cable connected to the DVD drive, which I'm sure you all know doesn't work. (And now I know it too -- lol.)

In the meantime, Ill wait and let you cross all your i's and dot all your t's and maybe get this thing up and running. Like I said earlier, I'm sure there are a LOT of people that'll be happy as a pig in  -- stuff -- when you get this running smooth.

[ldotsfan]

QUOTE(ldotsfan @ Jul 1 2010, 11:39 AM)

I'm still working on it:
1. The cloning function. Untested.
2. DHCP. Not working. Not needed for xbox 1.6 since you can now use the tool on-screen with the controller but a good-to-have feature. Static IP works though.

1. Fixed DHCP with a kernel recompile.
2. Cloning is working for C and E partitions. Figured out a method to parse the partition table from shell script. This will pave the way to extended partition cloning. Have used Pipe Viewer instead to display progress status. For real world statistics, I reached 15MB/s which works out to under 10 minutes for a stock 8Gb hdd on a 1.6 . Uncertain if other hdds have the same/better/worst performance.  
The new version has ETA, throughput and percentage completed display. Example:

CODE

51.7GB 0:28:52 [30.6MB/s] [====>                              ] 17% ETA 2:17:35

3. Will need to tidy things up and remaster initrd. Will also need to test that the cloned hdd actually boots  .