Hi, Again, sorry for the amount of threads I've made recently. The reason I was trying to open my sidecar was to replace the hdd, since it was giving me E68. I have now tried it with multiple hard drives and it still spits out an E68. It only gives an E68 when the hard drive is plugged into the 360's hard drive port. The sidecar itself runs fine when it's unplugged. I have tried using a retail hard drive in the xdk, to rule out the problem being with the xdk's hdd port, the retail hdd works fine. I also know the retail hdds work fine in other consoles. Any ideas on what the issue may be and any way to resolve it? Thanks all.
Wait, so does a Retail standard-ass 20GB harddrive work on the XDK, like if you remove the sidecar from the console completely and just use a HDD that M$ supply's, Does that give any results? but if its connected to the sidecar then connected to the console it E68's ?
XDK with retail hdd no sidecar - Works XDK with sidecar and HDD - Doesnt work XDK with sidecar, HDD not plugged in to the sidecar board or the actual connection to the xbox hdd port - Works
That is very odd 0.o PERHAPS Something is shorting out the sidecar? i'm not 100% sure of all the internal guts of the sidecar. Perhaps the connectors are stripped/damaged? i suggest doing a check up on them, Post results if any
I would assume it is an issue with the SATA port on the Sidecar based off the results you have gotten. Then again, I have never touched an XDK.
E68 can also indicate there's a problem with the circuitry between the sidecar, the hard drive, and the connection to the xbox. The console can't tell whether the hard drive itself is broken or merely the path to the hard drive is broken.
I had a sidecar do this years back. It ended up being some capacitor blown in the top daughter board which was causing connectivity issues with the hdd inside.
My guess is that the forward link between the controller and the drive is damaged in some way. When the drive isn't connected, the reverse link is down and hence the controller doesn't even attempt to send commands to the drive because it's not present. When a drive is plugged in, the reverse link comes up since the drive is sending the correct framing patterns - and at this point the controller discovers it can't communicate with it because of the problems on the forward link and throws an error.
Like XS, I had a sidecar that did this but I never looked into it too much. It's a faulty board or wire, probably anything that has to do with bad HDD communication. -Doom
Bad caps or faulty wires/contacts are the most common issues. Start from here. Same here and one sidecar had cracked top PCB (I wonder if they were playing football with it...).
I've had a few so far with e68. Tested all hdd's alone and they work just fine, but plugged into top board = e68. If you want, you can connect the HDD wire directly to the HDD and run the wires around it and the hdd will work. It's just kinda hard to route all the wires for correct lengths within that small space!
Ok mate, yeah I was thinking that. Whats the best method to remove the hard drive conector from the bottom board? It seems to be held in with some sort of glue? Dont want to end up scratching any traces trying to pull it off. Cheers
I used a hair dryer on low to make glue pliable and it'll lift off with some slight resistance. I have done what Shawn suggested before. It works and can allow the sidecar to be powered on to give the lit green led effect.
Managed to do it earlier mate, I like plied them off with some scissors with care. Going to do some Tetris with it to fit everything back in now haha
Put it all back together and it works Managed to get the two back screws in to the HDD so it won't wiggle about either.
