Jump to content


Photo

Xbox 1.2 Corrupted Tsop


  • Please log in to reply
31 replies to this topic

#16 MrMajst3r

MrMajst3r

    X-S Senior Member

  • Members
  • PipPip
  • 191 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 09 March 2012 - 08:18 PM

I tried today about fifty times to boot Xbox with tsop_d6 on DuoX2. Only once I got blue logo and Evox loaded. But I wasn't able to flash TSOP, i got message "flash not writeable".

#17 Movax

Movax

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,520 posts
  • Xbox Version:v1.4
  • 360 version:none

Posted 09 March 2012 - 09:43 PM

Sounds like bad soldering.

#18 MrMajst3r

MrMajst3r

    X-S Senior Member

  • Members
  • PipPip
  • 191 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 13 March 2012 - 02:55 PM

I have 1.1 motherboard with dual-bios. Can I desolder the tsop and solder it on 1.2 mobo? Is there points A19 for dual-bios too?

#19 AZImmortal

AZImmortal

    X-S Genius

  • Members
  • PipPipPipPip
  • 842 posts
  • Xbox Version:v1.0
  • 360 version:v4.0 (jasper)

Posted 13 March 2012 - 08:36 PM

QUOTE(MrMajst3r @ Mar 9 2012, 12:18 PM) View Post

I tried today about fifty times to boot Xbox with tsop_d6 on DuoX2. Only once I got blue logo and Evox loaded. But I wasn't able to flash TSOP, i got message "flash not writeable".

You're sure that your TSOP write points are properly bridged? Regarding transplanting your TSOP, the 1.1 TSOP is 1mb and the 1.2 TSOP is 256kb, so the answer is pretty clearly no, but honestly, even if you could do it, that's a lot of trouble when you can just buy a cheap modchip and have a perfectly fine working console.

#20 MrMajst3r

MrMajst3r

    X-S Senior Member

  • Members
  • PipPip
  • 191 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 13 March 2012 - 09:17 PM

Bridges are good. I tested it with a multimeter following by this http://img.photobuck...OP/points12.jpg

#21 AZImmortal

AZImmortal

    X-S Genius

  • Members
  • PipPipPipPip
  • 842 posts
  • Xbox Version:v1.0
  • 360 version:v4.0 (jasper)

Posted 13 March 2012 - 10:54 PM

Assuming your bridges are indeed good, then make sure that your evox.ini contains your flash ID. You can get a comprehensive list of flash IDs from the evox.ini in HeXEn.

#22 MrMajst3r

MrMajst3r

    X-S Senior Member

  • Members
  • PipPip
  • 191 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 14 March 2012 - 04:18 PM

I think flasher isn't a problem. Rather this metod is not working in every case of corrupted TSOP. Maybe i will try with 1/2 gen modchip or eventually i put in console LPC modchip.

#23 MrMajst3r

MrMajst3r

    X-S Senior Member

  • Members
  • PipPip
  • 191 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 24 March 2012 - 01:12 PM

Hi again. And again the same question. Can I use this modchip to repair a TSOP?
IPB Image

#24 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 24 March 2012 - 01:30 PM

No. That's a standard LPC chip. You need a 29 wire chip, one that sits (logically) on top of the TSOP, not one that connects via the LPC.

The TSOP_D6 BIOS method works on 1.2 Xboxes. Testing with a multimeter doesn't guarantee that your TSOP bridge soldering is good. Remove the solder, clean the pads (scrape very gently with a craft knife), and use lots of flux when you resolder.

#25 MrMajst3r

MrMajst3r

    X-S Senior Member

  • Members
  • PipPip
  • 191 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 31 March 2012 - 01:30 PM

Hi Heimdall.

I resolder the bridges, checked it with a multimeter via lines on picture.
I boot console from tsop_d6 and run your great installer (HEXEN).

I tried to flash with Evox, but I still get "flash not writeable".

I can resolder it again, but, there is any chance that is a problem with soldering?
Maybe the TSOP is broken?

Is there any sens to try with 1gen modchip?

I remember, that when I want to flash it first time (when it works), I made bridges, and in EvolutionX in most of bioses I get "bad bios file" or something like this. Only on some kind of Evox M8 or M7 it flashed TSOP, and now it is corrupt...

Oh, I remember also that EvolutionX seen TSOP as Winbound, but it is Hynix.


#26 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 31 March 2012 - 07:46 PM

QUOTE(MrMajst3r @ Mar 31 2012, 01:30 PM) View Post
Oh, I remember also that EvolutionX seen TSOP as Winbound, but it is Hynix.

That almost certainly means that the soldering still isn't right. What is the error message when you try to flash?



#27 shambles1980

shambles1980

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,092 posts
  • Location:wales uk
  • Xbox Version:v1.2
  • 360 version:v4.0 (jasper)

Posted 31 March 2012 - 08:11 PM

i never saw a hynix tsop chip on a 1.2 before.. (live and learn i guess lol)

#28 MrMajst3r

MrMajst3r

    X-S Senior Member

  • Members
  • PipPip
  • 191 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 31 March 2012 - 08:42 PM

EvolutionX saw Hynix as Winbound at the first time, when I broke TSOP... Now, it says "flash not writeable".

I can give you a photo of TSOP and screen from HEXEN with info that it's Xbox 1.2 smile.gif


#29 Heimdall

Heimdall

    X-S Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 5,749 posts
  • Location:UK
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 01 April 2012 - 01:42 PM

QUOTE(MrMajst3r @ Mar 31 2012, 08:42 PM) View Post

EvolutionX saw Hynix as Winbound at the first time

It's Winbond, not Winbound, and I can guarantee you that whatever it said on the screen the chip hasn't changed. It was reading from an incorrect Evox config file, one that was written by an idiot about 10 years ago, that incorrectly put the text about Winbond against the error code 0x0900. 0x0900 means chip not writeable, and in HeXEn I fixed the text so it now tells you something that is correct and useful.

QUOTE(MrMajst3r @ Mar 31 2012, 08:42 PM) View Post
I can give you a photo of TSOP and screen from HEXEN with info that it's Xbox 1.2 smile.gif


HeXEn uses UnleashX, so the identification of the Xbox as a 1.2 is only as good as the UnleashX detection routines. I've never known them be wrong, but the only guaranteed way to identify the Xbox version is to use one of the walkthroughs where you look at the video chip, the PSU etc.

#30 MrMajst3r

MrMajst3r

    X-S Senior Member

  • Members
  • PipPip
  • 191 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 01 April 2012 - 05:44 PM

I read again all the topic about fixing TSOP with DuoX2 and tsop_d6.bin and there were another people who can't flash the TSOP with blue and white X logo. I think I will try with 29-wire chip, but for a few weeks, when I will have more time. I have a few more questions about it, I will add new topic before I start smile.gif Thanks for your help.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users