Some God Games Restart 360, but atlease 1 works. Options

[DARKFiB3R]

I'm thinking it's something to do with your hdd wiring, as it only started when you opened up the box to start soldering again.

Did you remove the sata power as well as the data cable? Andy bridged joints/solder splash?

I know cloudy with a chance of meatballs works and nothing else does so that's strange, but maybe it doesn't try to access the hdd like the others do? I dunno, just taking a shot in the dark here.

What about xbla games, same deal?

[UnrealEureca]

I'm thinking it's something to do with your hdd wiring, as it only started when you opened up the box to start soldering again.

Did you remove the sata power as well as the data cable? Andy bridged joints/solder splash?

I know cloudy with a chance of meatballs works and nothing else does so that's strange, but maybe it doesn't try to access the hdd like the others do? I dunno, just taking a shot in the dark here.

What about xbla games, same deal?

Yeah some load and some tell me it can't read the disk. Some make it all the way into a game, but then fail at loading and tell me it can't read the data or parts are missing. BTW I also tried loading games from a USB drive and had the same results.

I really think its a problem my my NAND and I'm not talking about the dump, but the physical NAND. What I tried doing today is getting my original NAND from when the 360 was at 4XXX and flashed back on. I then removed all the jtag wires to make sure it booted and the light just turns on and it never displays anything.

if I put the hacked NAND back on it boots back up, but won't play games. If I dump the NAND now I always get Bad Block found @ 0x3a5 status 250. I did not have any read errors before this incident.

I search for that area in my old NAND and there is data there so I think when I try to flash it back on that date is obviously not written which results in it not booting. I also think that when I try to play a game on the hacked nand that boots it probably tries to access something that was originally in that portion of the NAND and thats why it reboots.

I would really appreciate some assistans on how to remap my NAND so that it avoids that 0x3a5 portion. I'm thinking I can do that to my original NAND then update from there and hopefully the 360 knows to avoid that piece as I update because its bad. That or fix the current hacked NAND by figuring out what data is missing and inserting into a different section.

This post has been edited by UnrealEureca: Aug 11 2010, 02:43 AM

[UnrealEureca]

Yeah some load and some tell me it can't read the disk. Some make it all the way into a game, but then fail at loading and tell me it can't read the data or parts are missing. BTW I also tried loading games from a USB drive and had the same results.

I really think its a problem my my NAND and I'm not talking about the dump, but the physical NAND. What I tried doing today is getting my original NAND from when the 360 was at 4XXX and flashed back on. I then removed all the jtag wires to make sure it booted and the light just turns on and it never displays anything.

if I put the hacked NAND back on it boots back up, but won't play games. If I dump the NAND now I always get Bad Block found @ 0x3a5 status 250. I did not have any read errors before this incident.

I search for that area in my old NAND and there is data there so I think when I try to flash it back on that date is obviously not written which results in it not booting. I also think that when I try to play a game on the hacked nand that boots it probably tries to access something that was originally in that portion of the NAND and thats why it reboots.

I would really appreciate some assistans on how to remap my NAND so that it avoids that 0x3a5 portion. I'm thinking I can do that to my original NAND then update from there and hopefully the 360 knows to avoid that piece as I update because its bad. That or fix the current hacked NAND by figuring out what data is missing and inserting into a different section.

Another thing that can confirm what I'm thinking is if there is a way to extract the contents of the NAND then I can extract my NAND from right before this happened and compare each file to each other. From there I can determine what file is causing the problem and hopefully there is a way to rebuild my NAND while avoiding that bad block.

[UnrealEureca]

Alright I was able to extract my NAND before and after the incident and they are identical so there is something else causing this box to give me dirty disk errors and rebooting.

My last shot at it will probably be reflow then after that there must be a component on the board thats bad, if I only knew what it may be. Could be ram chip and hopefully the reflow will fix that, but usually when ram is bad you won't have it fail at the same spot every time so its probably another component.