TUTORIAL: como reparar tsop tras infectus ;-)

xboxes escribió:Gracias por la info... muy interesante

kikofras_cs escribió:Os explico ke me pasó ami cn mi consola.

Me compré el infectus en divineo, con la esperanza de meterme linux, y hacerme el mod del doble kernel cn las x D.

Bueno, hice la instalacion bien , dumpeé bien,antes de nada kite la r6t3 y pude actualizar y downgradear la 360 2 veces.

Aqui viene cuando la matan.

Al kerer volver a mi kernel inicial (2858) no me borraba bien la memoria, el chekeo fallaba y antes de morir me salió el error E79 y las 3 luces rojas. Primero fue el E79 y despues los 3 RLOD.

Hice el fix ke comentas, ke deberias decir de donde lo has sacado(http://www.infectus.biz, foro) y dar credito a sus autores... pero bueno eso es cosa tuya y de tus principios.

Y la historia acaba enviando la consola al SAT aver si la cuelo, fecha de fabricacion 2005, de octubre, la placa es del 2005, y con el lector cambiado, porke venia cn samsung y abri el lector, asi ke tuve ke cambiarlo por el hitachi nuevo.

estoy a la espera ke me la devuelvan nueva o la misma,

pero ya os digo... el infectus es un console-killer


enga;)

kikofras_cs escribió:Y la historia acaba enviando la consola al SAT aver si la cuelo, fecha de fabricacion 2005, de octubre, la placa es del 2005, y con el lector cambiado, porke venia cn samsung y abri el lector, asi ke tuve ke cambiarlo por el hitachi nuevo.

estoy a la espera ke me la devuelvan nueva o la misma,

pero ya os digo... el infectus es un console-killer


enga;)

Flash78 escribió:
Yo aun conservo a la fallecida, estos dias lo probaré a ver que resultados obtengo.

Un saludo

Flash78 escribió:
Yo aun conservo a la fallecida, estos dias lo probaré a ver que resultados obtengo.

Un saludo

DAVER_7 escribió:Me puede decir alguien que es el infectus??? Estoy perdido en este tema.

Gracias

Salu2

Here's a way to reflash the 360 after a bad flash without having to use an extra 5/3.3V power supply. Make sure you leave the power supply unplugged and don't connect the 5V line on the 360 MB at all. Never plug in the power supply while it's wired up like this! You can fry the chip and/or MB that way!
This does NOT fix the doubled byte error while flashing, just the "unable to detect flash type" after a bad flash.

We gladly thank our user ARAKON for this tutorial.
If you need to get your 360 back working after a bad flash, you can finally do it.
When the 360 flash is bad (= system will not even turn on anymore), the system pulls up D1, 3 5 and 7 (3.3V).
This prevents the infectus from detecting the chip and from reading/writing to it anymore.
In order to fix that, the flash and chip will have to be supplied with external power, so the motherboard doesn't interfere with the flash read and write.
Infectus should look into that and ensure that the required powers are available from the chip itself when connected by USB, so people don't need an extra external power supply.
The 5V and GND points on the infectus have to be connected to a 5V supply and GND (GND on both the chip AND the 360 MB).. DISCONNECT 5V from the 360 MB!! (Infectus could take the 5V from USB).



Connect the circled 3.3V point in the attached picture to a 3.3V supply. (Infectus could provide 3.3V on one of the points). DO NOT CONNECT THE 360 POWER SUPPLY!

Turn on your power supply, then plug in the USB connector. The infectus will detect the flash as usual and you can write a valid firmware back to it. Be aware that you will have to repeat this procedure every time you have a bad flash. After you have a valid firmware on there, remove the 3.3V, 5V and GND wires and install like in the normal diagram.

Again, thanks to ARAKON for this useful tutorial.

hitman43 escribió:Ok, it is so simple but nobody saw it.
I think that the most of us has installed the infectus with the installdiagramm v1.3.
On this diagramm the V point isn´t displayed.
So i think also that nobody has installed the V point because the installdiagramm v1.3 is wrong!!
So i tested the whole day a lot of combinations with an beta programmer to locate the problem.
Every test failed. After earsing,checking,flashing,updating the actel,dumping the new flash and so going i have all the time the same result.
The dump was corruped and the 360 didn´t do anything.
After this i checked my installation again,everything was correct but i thought that i have saw some other points on older diagramms.
So i checked an older diagramm and saw the differents between the v1.3 and v1.1-1.2 revision of the installdiagramm.
The V Point was missing!!!!
My 360 doesn´t do anything without the V point and of course my dumps has a lot of corupted bytes in it.
After installing the V point the dump was fine and the 360 works perfect again!

So please use this diagramm and test writing to NAND again with installed V point:

http://dwl.modcontrol.com/XBOX360/ANLEITUNGEN/INFECTUS_INSTALLDIAGRAMM_360NAND.jpg

I will test it also with an newer loader (v24+).

Infectus escribió:V point is not used in the last actel firmware. Before we set this pin to give a little power in the flash. After some test we see that it don't work well. So we decide to not use this pin. In the actel project it's not used.

If it really work, we don't know why.

hitman, what about the new programmer with downgrade/upgrade?

hitman43 escribió:I make yesterday a complete fresh installation and i try to use the installation without V wire.
The result is the same,the nand is dead after flashing.

Mithrandir0x escribió:Disculpa si te ofende mi ignorancia, pero ¿qué es la Tsop?