Xbox 1.2 Corrupted Tsop
Posted 09 March 2012 - 08:18 PM
Posted 13 March 2012 - 02:55 PM
Posted 13 March 2012 - 08:36 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".
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.
Posted 13 March 2012 - 10:54 PM
Posted 14 March 2012 - 04:18 PM
Posted 24 March 2012 - 01:12 PM
Posted 24 March 2012 - 01:30 PM
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.
Posted 31 March 2012 - 01:30 PM
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.
Posted 31 March 2012 - 07:46 PM
That almost certainly means that the soldering still isn't right. What is the error message when you try to flash?
Posted 31 March 2012 - 08:11 PM
Posted 31 March 2012 - 08:42 PM
I can give you a photo of TSOP and screen from HEXEN with info that it's Xbox 1.2
Posted 01 April 2012 - 01:42 PM
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.
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.
Posted 01 April 2012 - 05:44 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users