Print

[NLA]

I'm having a very unusual problem after JTAG'ing, and this seems to be a recurring problem that has happened since I first flashed Xell and Xellous to NAND. After I'm done flashing, I can boot up the 360 just fine, it'll launch whatever I flashed to it no questions asked. BUT after a few subsequent bootups, it won't bootup anymore.

It turns on, but its just the power light, nothing shows up on screen. I remember flashing xell, turning it on, booted up fine, then it didn't boot after a few more shutdowns/restarts. So I flashed Xellous.. turned on, booted up, then after a few boots wouldn't boot anymore. And now I have XBR on it, and it booted up once just fine, and now it just hits the green light and stops.

What could the problem be? My soldering looks good and it definitely worked a few times, and it always seems the reflashing the NAND lets me boot up once or twice just fine again.

[NLA]

BUMP for great justice

[Ranger72]

Is it a big block Jasper? If so are you installing anything onto the onboard MU after it has been jtaged?

[NLA]

It is a big block: 512MB. I haven't added anything, no. There is the one obligatory profile stored on the internal memory unit that the 360 forces you to make when you first turn it on, but I haven't been accessing it in any way and I've been signed out of it since I first made it.. All I've done is flashed XBR, then turned on console, changed date/time/region/video settings/told 360 to block LIVE connections, and turned off. Thats it.

[Haruno]

Try this
http://www.xboxhacke...p?topic=14039.0
deleting the partition might help you out.

[NLA]

Ok, I just reflashed Xellous, then updated to XBR w/ Xellous set to load w/ eject key, and I went through the same procedure that I have for at least three reflashes: change keyboard layout/locale, change time/region/date, set the 360 to block LIVE access (and be forced to make and save a passcode). Every time I did this before, after I would turn the unit off, maybe even unplug for a while, plug back in and reboot, DEAD. I'd have to reflash Xellous and start over again.

The difference is that THIS TIME I deleted the avatar the 360 forced me to make when I first turned on and set up the console, and everything else in the MU before reflashing Xellous and upgrading to XBR. As of right now, I have changed all the time/date/place/LIVE settings, unplugged, waited 30 secs and replugged, and it seems to be going swimmingly. I was hoping to find out that changing just one of those settings would cause the NAND crash, so I did them one by one.. but it seems everything is good so far. If it NAND crashes again, I'll reflash and delete the MU. Will post here if this occurs.

-

On a side note, is it normal to [predictably] cause a single-lower-right RRoD E71 error with just a flash drive inserted? I tested with it in, with it out, time and time again, and I always made it E71 whenever it was inserted before bootup.

[Jtag]

QUOTE(NLA @ Feb 5 2010, 07:30 PM)

It is a big block: 512MB. I haven't added anything, no. There is the one obligatory profile stored on the internal memory unit that the 360 forces you to make when you first turn it on, but I haven't been accessing it in any way and I've been signed out of it since I first made it.. All I've done is flashed XBR, then turned on console, changed date/time/region/video settings/told 360 to block LIVE connections, and turned off. Thats it.

Aww man only if i new this before. well i just crashed mine when i put 3 orange box save into the MU. can i pay someone to fix this. i dont have the necessary equipment