Print

[bigsexyc420]

So I have been reading and researching this mod for a good week before I decided to make the plunge.

Using an Elite with the 7357 Dash.  

Added the LPT mod with Cat5 extender.
Also soldered on the Jtag hack before doing any kind of flashing or reading.

Made sure all my points were on good and neat. Used the least amount of cable possible for connection to PC (32 cm).  
Used nandpro20b to read my nand 2 times, then used totalcommander to compare, and got identical dumps.

So with one of them I proceeded to install XBreboot, heres where the issues started happening.
First dump of XBreboot installed fine, no errors occured at all after the writing process.  Unpluged the lpt cable, to test it on the TV, the 360 booted up nothing on the screen.  Tried turning it off for a bit, (ate some lunch) then came back to turn it on again.  This time, nothing on the screen only to to see that this time around I got the red rings (1,3 and 4) flashing.

I did some more research, and read that it could be due to a bad flash.  So back to the PC, transferred a nan again only this time sans the config file.   Tried it again on the TV after, only to see that the xbox does not even turn on at all now.

So doing some more research, i heard to check my soldering points yet again.  nothing out of the ordinary.
So I figure, ok 3rd times a charm.  Re-injected the nand with the KV and the config, and wrote it all over again.  This time, towards the end of the process of the writing, I had noticed the red rings started flashing (1,3, and 4).  But according to nandPro20b this was not having an effect on the writing of the NAND as it was writing like normal.
So despite the red lights flashing, I let it finish.  Tried to boot it up again, only to see that I still get no power.
Which is weird because the lights turned on during the NAND writing.

So, after all the trial and error and extensive research, I have nothing left to do but post and ask questions.
Any ideas on whats going on?

Also I had a question on one of the points of solder for the Jtag Hack, one diagram has one of the points leading to the back of the motherboard.

While the other has the same point going to the front, near the power button.
 


do i need both of those points?
Any ideas on why I get no power when trying to turn it on after Flashing the XBreboot?
If it reads fine and it can write with no errors, am I correct to assume that my connections are good?

Sorry for the long post.

[ZprivateZ]

What version board? falcon, jasper? Did you check the cb to make sure the box was exploitable even though it had an exploitable dash? Have you tried flashing back the original nand to see if it boots back up?

[bigsexyc420]

Falcon, with 5766 CB.

I havent tried to boot the original nand.  
If it boots up, what was the issue?  If it doesn't what's the issue?

Also any difference in those soldering points I posted above?

Thanks for the reply.

[TBAYJ]

ive had my personal falcon turn on while flashing wierdest thing ..this is how i flash mine and others error proof

i was you i would send the nandpro erase command first
nandpro lpt: -e16 0 400 first

then write the free60 version of xell via lpt (in usual place) free60/older named falcon_hack_1(has to be this one )
and grab the xell lous update while there (XeLLous_v1.0 or) in xell-lous on xbinz  

take a raw xbr3 for falcon inject your kv into it (nandpro xbr.bin -w16 kv.bin 1 1) leave your config out

save a copy of new xbr  rename it to upflash.bin make sure not updflash.bin.bin , put upflash.bin in root of thumb drive in a folder for now

rename the xell-lous update to updxell.bin( you want the one named xell-1f) in xelllous folder   again make sure not updxell.bin.bin
 
rename falcon_hack_1 to free60.bin and place in nandpro folder

then run nandpro lpt: - w16 free60.bin 0       take 2 -5 mins
unplug 360 1 min

with the updxell in root of thumb drive put in front usb  turn on 360 power button should boot into xell and say update found when its finished unplug 360 1 min

 and put usb thumb drive in pc put updxell a folder in root of usb take the updflash.bin file the xbr you created with your kv in nandpro and renamed it to updflash.bin and put in root of usb plugin 360 turn on with eject buton with drive connected

should say updflash.bin found press power if you dont want to update let it run takes 5 mins tops

after unplug 360 1 min turn on with power and test

this may seem like a lot but u can flash a 360 in 10 mins or less this way and it writes the nand from usb which is error proof

if updxell or updflash is not found when booting xell or xell lous it could be name updflash.bin.bin correct either file

[bigsexyc420]

TBAYJ:
Thanks for the info, gonna try that after work tonight.
During that whole process, should the Jtag wires remain on the console?

crackwhore:
I've tried all three different types of video connections (hdmi, component, composite) with black screen as the result.

Thanks for all the help and information, I will keep updates on this thread for future reference.

[bigsexyc420]

Just got home, removed the Jtag wires, re-wrote the original NAND back on to the 360.  Still doesn't boot up.

Looked around for random solder splash or anything out of the ordinary. Nothing.

Gonna test to see if I remove the LPT port cables.

any thoughts  

is my 360 dead?

Edit:  Just rebooted with LPT cables off, now its booting with red rings.  Still no sign of video at all to see the error codes.  The only clues here are that I get the 1,3, and 4 red lights.  And that when the LPT cables were attached, it could read and write fine with no errors.

double checked with degraded and flash.

[bigsexyc420]

So after some thorough inspection of my soldering points and mobo parts.  I notice that my heat sinks do some jiggling when moved.  So in attempt to fix this, hoping that the issue is with the heatsinks, I am going to try the xclamp fix tonight to see if that solves the issue.

As an update, I was able to flash the original nand back and get the 360 to power back on but with the red rings.


Any thoughts on what the cause would have been earlier when the 360 wouldnt boot up at all?  Is that mainly caused by incorrect Jtag wiring?

[smiley2billion]

It could be a bad flash.

If the orig nand file didn't flash back properly then it will give you the 3 red rings in some cases.  Also, if it got a bad flash from free60 it could cause it not to power up too.  

I'd read back the nand and check it against your known good nand you got when you first read it.  I've had this happen to me before and it turned out to be a bad flash.

Also, I've used the "chunk" method or reading/writing smaller segments and checking them individually and it seems to work better, or at least save some time if you get a bad read on one of them and don't have to read back the entire NAND.

See this thread for reading and writing in chunks:  http://www.xboxhacke...p?topic=12585.0