Print

[run088]

QUOTE(ldotsfan @ May 23 2008, 09:19 PM)

Isn't error 13 a ms dash error? Turn on chip , load slayer's and rebuild C with retail dash should fix it. With chip off, any homebrew dvd disc isn't supposed to work. Unless you also try original game disc and it didn't work also?

The bios on the tsop are not original look to be 4981 if I had to guess.Error 13 should be a dashboard error and reading on the error in the pin section it says it has something to do with the kernal and the eeprom being uncompatible.But the fact remains I can not boot from disk I got 5035 on one bank of the modchip as well as the old xecutioner bios on the tsop neither will boot both will sit there at the x for alittle while and then go to the error 13.
Bit atleast I am moving in the right direction.This xbox has came along way from being a 3boot frag box to a flash green flashing red to the present error13.
The only reason I have ever seen an xbox that should be booting from disk and not is when it had problems with the pic16 chip or a bad dvd drive and I know its not the dvd drive I have hooked up 2 that I know to be good with no success.And by the description of the error having something to do with the eeprom its making me think its not the pic16 but the eeprom.The hdds that I hook to it have already been modded and work on other xboxes which also makes me wonder about this error 13

[Bomb Bloke]

QUOTE(Movax @ May 24 2008, 02:23 AM)

Sounds Familiar.  

Ooops.

In my experience, error 13 means the system can read the HDD ok but it can't find an XBE it wants to boot. I can't think of anything EEPROM related that should give that or any other (with the exception of error 6, though you'd know if the drives were locked or not).

Ah! Here's a thought: The 5035 reads most of it's settings from an INI file stored on E:. Create a custom one using X2ool, throw in some settings to change the way the flubber sequence appears (change some colors or something). See if the console pays any attention to those. If it doesn't, then perhaps the system is really having trouble reading the drive?

[run088]

This is more than your run of the mill error13 because I am running hacked bios on the chip and tsop I can run this xbox with an unlocked hdd.I have rebuilt c 10 times and even added a dashboard file in e for the fun of it and no cigar.It wont boot  from a disk and I know its not the dvd drive.I can mostly likely fix this issue by replacing the pic16 chip I have found in the past it is the cause for xboxes that will not read from disk and receive no dirty disk error.But Im still going to get the error13 more than likely so I dont think I will be able to gain any advantages by doing that just yet until I can find the issue with the error 13.
Unless someone knows for certain that the pic16 chip somehow has to do with the the error13 like weather it has functions it performs to help the xbox where the error13 is concerned.
What I am trying to say is how is this line out of the pin section for error 13 relative to the motherboard and the motherboards components in the way it works if I dont think the problem is on the hdd end of things but the components on the mobo itself....


13 - kernel - Dashboard launch fail (due to missing/bad key, or anything else that would prevent it from running) and the dashboard didn't specify why it failed.
Details]

This is an error thats most common when you have changed something on your xbox harddisk drive for whatever reason you had, but did not do it properly.

The thing you should understand is that error 13 is only because something is wrong with the files on your xbox harddisk.

.The error it gives is because of the incompatibility between the (older) dashboard (4920) that older slayer cd installs and the new dashboard/kernel versions found in some new xbox's and found in xbox's that have been connected to xbox live (when you go on xbox-live, it'll upgrade your dashboard file to i believe it is now 5659.03. This dasboard is incompatible with the dash that (old) slayer cd installs (for example 2.5 or lower) for you.

(In detail, in the eeprom chip there is a kernel which is incompatible with the dashboard (4920) that slayer installs.)

It looks as if  I need to find out more about this kernel in the eeprom if our guide is correct.How its signal starts and comes into the eeprom  and which leg of the eeprom it comes into it in as well as the lines going out of the eeprom until that signal gets to the hdd or where ever it ends.

[Movax]

QUOTE(run088 @ May 24 2008, 07:27 AM)

(In detail, in the eeprom chip there is a kernel which is incompatible with the dashboard (4920) that slayer installs.)

I should add, this part of the explanation you quoted is incorrect in it's use of 'eeprom' here. They are referring to the TSOP.

[run088]

I know the eeprom was part of the problem because when I finally got it flashed it will now boot from any bios it just throws the error 13 on everything thats not linux.
I have fixed a half dozen xboxes with a pic16 swap before because it controls so many functions.I replaced one in a coma box that would not boot as well as several that would not boot from disk or give a dirty disk error.I know this chip does alot of things. I never have read to many post about it on our site but Ive learned alot from sickmods site about it from sickdimension and pablot.As far as trying different IDE cables and dvd cables and hdds I swapped every piece you can think of atleast 5 times.
Im certain there is more to this I just need to know the info I was asking about to get to the bottom of the problem.

[Bomb Bloke]

QUOTE(Bomb Bloke @ May 24 2008, 11:25 PM)

Ah! Here's a thought: The 5035 reads most of it's settings from an INI file stored on E:. Create a custom one using X2ool, throw in some settings to change the way the flubber sequence appears (change some colors or something). See if the console pays any attention to those. If it doesn't, then perhaps the system is really having trouble reading the drive?

[run088]

I was going to try your idea next bloke but I think I found the culprit.As I said from the start of this thread this was someones former parts board that I bought years ago that I had laying around and decided to give it a go.I had thought I caught all the missing pieces over the hours I went over the board but I found a group around the cpu that I must have missed.First I need to reinstall these pieces and see if that does the trick and if it doesnt its on to your idea Bloke.

[run088]

Fooling around with flashbios Ive discovered that the xbox is "unable to read the first sector,returned 1" this is what it says when I try to lock any hdd with flashbios.Can anyone point me in the right direction to what controls how the xbox reads the hdd sectors.

[Movax]

QUOTE(run088 @ May 24 2008, 11:48 AM)

Can anyone point me in the right direction to what controls how the xbox reads the hdd sectors.

Yes, the southbridge MCP-X chip. Good luck troubleshooting that. I think your xbox is a goner.

[HD10291]

I stopped reading about have way through all the posts:

Did you try different IDE cables? Both male, and replace the female on the board?

It doesn't boot from CD, and won't read the Hard drive. It can only mean that you have bad access through the IDE hardware.

[run088]

Ive replaced a handful of components around that part alone I first need to go and double check around that area for shorts or maybe more components missing.Do you have any more info on it or the lines that run in and out of this chip that are responsible for this function?Or an idea where I can find this information? Ive replaced already over a dozen of the smallest components on this motherboard it could be on one of my repairs or possibly a component I damaged on the reinstall.It would be easier to test If I knew a little more information on what I should be looking for.

[HD10291]

Idk much about chips, besides potatoe, but maybe you should just give up? NAW! I would never give up.

If you had shorts, I'm sure the console wouldn't even boot, and it would frag at best. Try to desolder your female pin header, and solder an IDE cable directly into the board.

Here's an Idea, check for trace corrosion, or any broken trace at that matter.

If you're concerned about the eeprom, just flash it with a working Xbox's eeprom, and lock your drive to that eeprom. Also, you have no way to flash your modchip? I would say change the bios, and restore the factory Xbox's TSOP bios. Then you can rule that out as being the problem.

[run088]

QUOTE(HD10291 @ May 24 2008, 06:32 PM)

I stopped reading about have way through all the posts:

Did you try different IDE cables? Both male, and replace the female on the board?

It doesn't boot from CD, and won't read the Hard drive. It can only mean that you have bad access through the IDE hardware.

This brings me back to a possible bad pic16 chip.Just as you say here about if it will not read the dvd it will not read the hdd.Well I am for certain that the pic16 is responsible in this way for the dvd drive in some situations.I have fixed several xboxes that would boot normally but would not read a disk or even threw a dirty disk error the dvd drive would spin but it would never take action.I stumbled on this find on the first mod I ever attempted years ago when I shorted out a samsung 616t drive on the install.After I did that the xbox would not boot from disk."I did find one back door to this and I have no idea why it worked but if I used a real old xbmc and used the orbs skin it would force it to load from the video settings but this was the only way it would play disk"So tracing the board I found with help that the short fried this function in the pic16 and once I replaced the pic16 chip the xbox booted disk from then on with no problem.I have fixed atleast 3 xboxes that had issues with reading the dvd drive but all of them still had the ability to read the hdd.I fixed another with a pic16 replacement that was a coma xbox it would do nothing no matter what I tried.all the traces leading to the pic16 were a ok.
If someone can verify if  the pic16 chip has any functions it preforms that have a bearing on the xboxes ability to read the hdd this would be helpful for me I know the pic16 has a bearing on the dvd but am unsure about the hdd.

[run088]

QUOTE(HD10291 @ May 24 2008, 06:42 PM)

Idk much about chips, besides potatoe, but maybe you should just give up? NAW! I would never give up.

If you had shorts, I'm sure the console wouldn't even boot, and it would frag at best. Try to desolder your female pin header, and solder an IDE cable directly into the board.

Here's an Idea, check for trace corrosion, or any broken trace at that matter.

If you're concerned about the eeprom, just flash it with a working Xbox's eeprom, and lock your drive to that eeprom. Also, you have no way to flash your modchip? I would say change the bios, and restore the factory Xbox's TSOP bios. Then you can rule that out as being the problem.

Well the board was cleaned before I started I did that as well as replace anything I saw missing and believe it or not I have found and replaced missing pieces after I have been stuck on the error13.It was booting to this error even though it was missing 3 caps around the cpu.1 broken #330 chip under the mcpx as well as a few others this was amazing to me.
As far as the eeprom I finally got one on there with flashbios unathorized.I can now boot any bios it just goes to error 13 now.I can verify that 5035 will boot past an eeprom error but no other bios I could find would this was the only bios that would not flash green once flashing red no picture epprom error before I got an epprom image on the eeprom.
Bios are not the issue all the bios will load on the chip or the tsop but the xbox is having trouble with reading the dvd and the hdd.Cromwell sees the drives but sometimes gets the sizes incorrect.It sees the dvd drive and knows weather its there or not.Cromwell will lock the drive but is unable to unlock it.Everything turns on and you can hear them all run as they should but nothing is getting accessed.
The error 13 is also listed as the dashboard failed to launch and didnt specify why on this error it can usually be corrected by files on the hdd and you should still have the ability to boot from disk but I cant boot from disk but that doesnt matter because my drives are unlocked and Ive repaired the files with no success the same drives tested boot normally when connected to any other xbox.

[run088]

Its not the pic16 chip I changed it and the result is the same error13.Any other ideas?