XBRv3a on Falcon, lots of strange errors, diodes, soldering or something else?

[Snigel]

Update: I think I found something, it behaves worse using VGA output than HDMI.

Seriously i dont think it are your diodes. Maybe they get damaged by the rebooting, tho.

Neither do I anymore. The error keep coming back even though I changed type of diodes.

Anyway, did you try to run the console while it is not in the metal case ?
This sounds more like a "half" short somewhere.

I actually tried running it without the case right now, removed the board with the leds and power button too. It booted up by itself just like 30 seconds after I plugged it in. Looked at the soldering points again, couldn't find anything weird.

Did you watch the Power Supply's LED while it reboots ? Maybe its a current problem from the PSU.

I didn't have any troubles with this before the JTAG, so I doubt it's the PSU. It shows orange when it's in standby and green when it's on. So when it loops between on and off the power supply switches colors accordingly.

Maybe measure the 5V 12V voltages if they are constant.

I doubt it because what I see is a normal shut down, just like somebody pressed the button, dimming the screen taking a little while. Not the instant power failure kind of shut down.

If you google for xbox keeps rebooting you will see this or a similar issues on stock consoles without jtag.

I googled some, but I couldn't find any real good answers. Most threads were filled with spam and no real answers to anything.

Update: Currently I have a wired controller, the power+led board and the fans connected. No harddrive or DVD. It is without its case. New problem, I can't shut it down. Pressing the power button does nothing. Using the controller results in a reboot.

Did a resolder of the cord connecting to the connector of the power+led board. Machine turning itself off again, and goes for a rebooting loop.

Lastly I tried soldering directly to the power+led board. That worked in perhaps five minutes of standby before it turned itself on and started the infinite loop of on/off.

[Snigel]

Update: Found out that there was a soldering point for DB1F1 on the back side of the motherboard. Soldered it there and haven't had any problems so far, been two days now.

I want to add that I had resoldered DB1F1 several times before and that it might not be 100% that this works since the errors seem to come totally at random.

[farntheplaya]

im having VERY similar issues

console boots sometimes sometimes it doesnt.

i willl try to repeat your finding see if it helps

thanks

[akijikan]

Wow I hadn't seen anyone else describe this behavior before stumbling across this thread today.  I had experienced all kinds of weird stuff on my falcon.

Turning self on
Powering on without center light on (and sometimes no lights on)
Losing controller sync
One time I was playing a game for about two hours and suddenly the ring of light started flashing ORANGE (like when you use xell to boot gentoo) and then the ring of light went off completely and my controller was no longer connected to the 360.

I thought maybe the wire to the RF/Power board was touching the point next to it as well as the intended connection, but I cleaned that up and it didn't fix the problems.

Eventually I cleaned and resoldered the connection at DB1F1 and that fixed the problems.  It seems to me, and by your experience at well the problem is caused by unreliable or dirty connections to DB1F1. 

I know many have found it difficult to solder at DB1F1 and have seen some JTAG jobs where the solder just lays on top of the point rather than actually contacting it.

[Snigel]

The soldering point at the bottom of the motherboard was much better for me. Still haven't any problems since I changed.

Kind of confused though, the guy who helped me with solderings has soldered via points before, and soldered thousands of machines since the SNES time. I just don't see him failing three times on the same soldering point.

[Snigel]

Since the last post I've had no problems what so ever with the xbox. My cousin even played 15 hours straight the other day without any hiccups.

Today I connected my controller to the xbox for charging (if it does matter the battery was totally empty). I started the xbox from the controller. First it didn't give any picture at all but the fans was running. I shut it down and pressed the power button on the xbox. Now I got an error message on the screen, stupid me I didn't look for the error number but just shut down.
I tried disconnecting the controller and start it up again, now it started up fine but all the settings was reset.
This could be some of those problems I had earlier, since I almost always used a wireless controller with the charging cable connected.

My question is now, is this an known issue which I have missed? If not, has someone else noticed this problem?

[MastaG]

I'm experiencing the exact same behaviour on one of my zephyrs.
When I turn it on it'll take much longer before it boots compared to my falcon console (also xbr).
I'll hear the fans speeding up and down a few times and after 6 or 7 seconds I'll get the booting animation.
Like it has trouble attempting the jtag hack.
The console doesn't have any bad blocks and I redid the soldering many times, tried it with the point on the bottom of the board and also the point on the rf-pcb, no difference.
Usually when I turn it on for the second time, I'll get some Exx error (I think it's E79).
This will cause my settings to be reset and the next succesfull boot will take me to the setup screen.
Very annoying :p

[Snigel]

Well, my current problem is only when the wireless (charging) controller was connected and used to start the xbox. Not otherwise.

[Gazcoigne]

i have a flacon with XBR on it and it never ever errors, or does anything wierd and it is played every single day for a few hours at a time.

i used the DB1F1 point, and have actually removed it and redid it again as i was trying to get orig nand rebuilt, then gave up and kept XBR on it and bought it off the guy i was fixing it for.

all these errors etc are most likely due to bad wiring, or else corrupted writes to the nand.

i make a point of flashing the XBR image again through flash360 after i do it with lpt to make sure the nand is 100% with no errors.

[Pacote-san]

Done 20 or so x360 so far and i got a falcon with the exact same problem... i only got it to boot xell twice, other time always E79.... will take if off the metal case tomorrow and try to use solder db1f1 on the bottom pad

[Pacote-san]

Yeah tried without sucess.... strange this is the only falcon that i got that i just cant get xbr to work...

and checked CB and its exploitable...

[ZerOneX]

Try to use BAT46 instead 1N4148, it worked fine for me.

I couldn´t find BAT41, so I tried BAT46.

[littlestevie360]

Try to use BAT46 instead 1N4148, it worked fine for me.

I couldn´t find BAT41, so I tried BAT46.

i use BAT46 myself and they work fine,
as for the difference between BAT41 and BAT46 according to jaycar they are almost identical

[BoXXDr]

On falcon these alternate points have given me the best results. This is the shortest possible route i can find. It's really not very hard to do either.

I would like someone to confirm if this works on Jasper too?

I am going to have to order some BAT41 too. It sounds like they are probably the most suitable for this.

[rusudanion]

hy i have the same problem with one jasper.he make me the same.i thisk the problem its wireless rf pannel.somthing its briken there.

[rusudanion]

make an prove.on the consolle without the rf pannel.with an remote control or usb wire control.
please answer

[arcane]

I would like someone to confirm if this works on Jasper too?

I have verified that this works on a Jasper console.  Very neat installation!

[maximilian0017]

Maby everyone with troubles could post the type of Southbridge they have?
Flashconfig 23010 means the new "Panda?!" Southbridge, standard Flashconfig is the old one.
If i read it right the new southbridge has a different way to number its bad blocks and this could explain some problems.

And please try to place the diodes on the underside of the board(if you are sure you can solder it without damage!).

Does anyone know if a serial debug would shed some info on the problem?, i can serially debug but i have no consoles with troubles....(Anyone in Holland having these kind of problems?)