I have a Xbox360 Slim 0033. Turn on and quickly red light. I tried something bad and what is found in the attached photo. The motherboard is shorted in C7F2 (red circle). The capacitor off the board is working normally. I removed the resistor R7F1 and found this image under it (yellow arrow). Could anyone help me?

Anyone know the track of the temperature sensor in Slim?


Portuguese:

Tenho um console xbox 360 Slim com 0033. Ligo ele e rapidamente dá luz vermelha. EU procurei alguma coisa ruim na placa e achei o que está na imagem anexa ao tópico. A placa tem um curto no GND e + desse capacitor, mas fora o capacitor está perfeito. Eu removi o R7F1 e encontrei a placa tipo queimada (seta amarela). Alguém tem alguma idéia?

Alguém sabe qual a trilha do sensor de temperatura do Slim?

the original NAND it starts normally? If possible take picture of the CPU_PLL point was to see how the soldering. Where is the wire going CPU_RESET?

If I had seen before I would measure it for you.

 

Thank you Blackaddr ! Increased my understanding of RGH. I will not lose much time with the Slims.

Congratulations! Thank God!

Oops. Friend RGH was not done it. I grabbed a customer and do not know what happened there. I immediately thought it was the mosfets, but I tested so far was good. I decided to stop and ask for help. There is no tension in the plate (only 0.26v).

Yes. Works perfectly in all consoles.

Before creating the topic I searched for information, but none was complete.

I took a client not a jasper no sign of life. There is no standby voltage (1.8V, 3.3V and 5V). The only measurement that meeting the board is 0.26V. Even direct pins PSU only get this voltage. I thought it was the mosfets/regulators U5B1, U5B2, U1F2, ,Q6F1 and Q6F2. I tested the mosfets, but they were good. The regulators have not tested. Without them, the board has no voltage 5v (same thing). Could anyone help me? A mosfet/regulator burned prevent the verification of the source (power good)? I tested the electrolytic capacitors near the cooler (C8B1, C7B3, C6B3, C5B7, C5B4, C5B2), but all are good. I also tested C9C1, C9C4, C9E3 and C9D2 (all good). The source it stays lit with orange led.

English:
If I understand you're talking about the RF board. Make sure the capacitor C57 (top connector faceplate) is not short. Games are probably is it.

Português:
Se eu entendi vc está falando da placa RF. Verifique se o capacitor C5 (em cima do conector do faceplate) não está em curto. Provalvemente é ele.

I expressed myself wrong. The idea would be to write a NAND a Trinity (9504/0225/0401/1071) in Corona. This with the KV Corona injected into the NAND Trinity.

@nknave:

Thanks for the reply. A Brazilian users reported getting some kind of hack in Corona. I asked because I thought it had something to do. Now we realize that it is "clone" the Coronas (like they did in the old JTAG). Thank you.

If you can answer I'm thankful!

The CPUKEY is a physical key or is contained within the Nand (software)?

If I switch to NAND cpukey also changed?

Thanks to those who spend time answering me.

Here I finished the whole process and the red light remained the same in the original dash. Not synchronizing the controls. Disconnect the matrix glitche, there were only taken before the VCC, and slim worked normal. The GND was connected with the CPU_RESET (A). In your case, Watk, it may happen that one of the glitch points have been connected in GND.

3.3v (pin 8 from top to bottom).
After the updated you use nandpro.

"Follow instructions for USB install.
Make the following connections from the LPC2148 to the Xilinx device
 Jtag conenctor:

ArmLpc  Jtag            Olimex          Maximus

3.3v    VCC             EXT2.24         M1
GND     GND             EXT2.25         N3
P0.17   TCK             EXT1.18         A2
P0.18   TDO             EXT1.19         B3
P0.19   TDI             EXT1.20         C1
P0.20   TMS             EXT1.21         C2

Xilinx CPLD flashing typical command line:

Flash a .xsvf file, created by Impact, to cpld:
   Nandpro xsvf: filename.xsvf

General XSVF notes:
LPT is not supported for this feature. 
Requires additional connections from LPC2148 to the Xilinx jtag connector.
The Xilinx Impact tool is used to create .xsvf files. The Xilinx Impact software
 records/redirects cpld operations into a binary file (.xsvf) that can be
 processed by Nandpro. IE: Nandpro does not flash .jed files, but .jed files
 may be directly converted to .xsvf by Impact.
 See the Xilinx Impact tool for more information."

source: readme.txt nandpro v3.

I believe I will get the upgrade Nandflasher using this scheme:



is it correct?

The price for the Brazilian x360glitch is good. I bought and waiting to arrive. I hope you do not have the same problem that we have some matrix Glitcher slims (report of users).

I agree with you Mordock. The drilling with a thin tool increase the margin of error. Here I use a 2 mm drill until you start to see the wires and then I finished the job. So I feel safer.