2 red lights means your overheating..... check your heatsinks and thermal paste.........3 bad blocks wouldn't cause your overheating issue
you manually did something wrong .......

never question the simple $#!t....

you just reset your defaults (system back of the dash)...then when you reboot it brings you to ...picking a language and suck...

i'd jump on this .......but in your topic you just said I need help without the  ??
use the nm...lol
so without the drive the 360? does that error? and with it in...it lags
you might be able to catch the info on that drive if you back down to the early years when us old peeps used Hitachi's(software)for command line flashing at boot up...(see i said command line not DOS...

I wish i had my socket for the Willem...but china is closed till the 25th...dammit (some new year $#!t for them)

ya and next time pic up that error $#!t with a link...
your soldering looks....ok if using xp set printer polling to disabled...and normal mode(spp)...and tick on legendary mode...

all that solder job don't look to bad.....just messy flux...
I take it you have the diode for lpt connection on pin 11 on the db25..along with the resistors?

I noticed a corrupt nand(SMC destroyed) can cause a no-boot(poweron) or a (mega)error(s) like up above your spam post......

don't use a lota flux.........this causes solder problems to....

Don't you have Egypt bay out there?

and i own 10 consoles 4 jatagable 6 not and 15 motherboards(all bought and no trade ins)............not to mention all the 360's i get in and
 can keep for later if there total warped boards......and you talk about $300 bucks...pfft....earn your hobby...lol

payed 20-100per unit/system..l.....bragin..damm right i am ...
because i am a bragin-Reballing-Mofo ...
and you guys whine when i spoon feed noobs...lmfao so i gota post something....

you might be able to change the LDV values to stop the e80(resistor pulled error)

man,,,these freaking people come with bashed up nands ...like they went out drinking with there nand and got into a fight....and the nand lost....jesus....only good part of this nand is, he had a valid copy of the KV from 360flashtool (encrypted/decrypted)

how he corrupted his nand after that,is either uploading it and caught some $#!t in a transfer or just playing around.....
it kinda looks like he was spoofing a Hitachi drive to a liteon and messed something all up...lol

lmfao...erm ya, it did kinda get robbed.......
don't beat me down admins,he did it not me......

well the most you can do it rebuild your current kernel with bincrpt.....back down to 1888 and then you can work your way up from there...not good for games or anything..though...asking for updates....

but you can talk any dash from 7371 for the xbr(jtag) you don't need a 4532 to compile a homemade dash
unless your making your own as you stated......but it's as of no use for running stuff.....
anyways good luck on your project
P.S SMC Hack on there is old...lol

i sent you xbr_3 for Xenon all you have to do is flash the nand to the box....(don't mess with it)
you can't get it any easier then this for help...so now your back on your own....
good luck...
P.S already over helped .....

first, flash back the orig nand to see if the 3Rod goes away....

3b? no 3b for falcon
XBR_3a for falcon...and you don't need to erase the nand...jst reflash XBR_3a along with your kv and config.....unplug from the back of the 360 for 25 secs...and then power on either to xell(eject button) or front power button(dashboard)...

check your pm.....and try this nand...make sure you make a copy...to
lazy......

just remember anything you buy, run it first before you just go doing homebrew this way you can resolve some of the future errors you come across.

if you can't re-ball yourself,shoot me a pm.......

here is your nand readout...this is with the CPU KEY and 1BL key un-ticked...it crashes the flashtool360 if there ticked...
as you see by the nand pic...in the files section, it's corrupted(don't know if it was from the dl or what)...you need to get another read your 360's nand...
you only read your nand once?

dude pull your cpu key down...you don't need to be handing it out...

your nand dump is also corrupted....

i guess this was a last min posting spot as some posted replys to your last reply of November 19, 2009...
and it's now feb....lol
i was having fun and watching peeps post for "i guess a jot down reason only" warpjavier .....so no don't close it yet...lol
s
after all it only takes 1 poster to update an old post...then most goto answer it because of it showing new in the section...
---cough----Mr. krestean ...lol

i also run a lot of scsi  10,000 rpm drives of all makes......
and still have ones from the early 80's...
but sticking with wd on the small stuff ...
every manufacturer has or had it's problems with certain models

bottom line ...
yep.....
i am glad they make bigger sticks....to back up stuff from the start and as you go along...


always ran Seagates(past ones),wd's and maxtors from win 3.1 upto win7...but all under 500gb drives...

you need to make sense of this?
there are key if the CPU must lay out

ahhhhh...well i guess he knows it's a corrupted kv ,but can't find the problem...
and Russia rapid share........that's like 23-33kb's...lol

also ...why are you using XBR2
search for a fix....or enjoy your scrap.....
nm i think you don't even have a clue wtf your doing...

why are you even doing that flash the nand with the XBR it dont call for updates....1888 aint going to do anything for you..........