your setup is bad then you will never get a full clean flash

E71 is indivating that your dash files are corrupt

now you have linux running use lflash to flash the image in linux using onboard SPI

do some reading up on it we're not going to spoon feed you the to do list

forgive me for my incorrect terminology

when i say dos, i meant an ms-dos command prompt, not native dos (apologies)

yes you can flash through JF one sector at a time, but i have had at least 10 hitachi's brick flashing through JF on a via chipset, when using the same chipset works perfectly the old way through a ms-dos command prompt, or even with fwtoolbox

dont get mw wrong oggy im not bashing JF i love it and use it every single day but it has a definate bug with via chipsets and hitachi's

it took me ages to discover my onboard sata works perfectly with hitachis in JF no crashes no bricks so now i use it to do the hitachi but i would prefer to spread that fact and save some1 else the frustration i encountered.

to change key in a command prompt the old school way

xxflash <drive letter> <fw.bin> 90004000 1000

where

xxflash is the flashing app found on xbins rev xx to match your drive revidsion eg 47flash, 59flash
<drive letter> is drive assigned by windows
<fw.bin> is your encrypted 59fw with correct key inserted

covered in the tutorial i wrote some years ago found here

http://forums.xbox-scene.com/index.php?showtopic=552675

my opinion is no the updates are performed in an environment of virtual efuses

on the 5 boxes i have done i have not removed them no issues so far.

and im sure that when a new dash comes out we will be reprogramming the NAND rather than applying an official type update so again the fuses will not come into play

only trying to offer a simpler option that has less chance of being worked loose screwed inside the casing rather than protruding on front of ROL board

some of us are used to the older ways of flashing the hitachis

even if it is outdated, it still works and doesnt crash and f*** your drive up like JF

obviously your see through case is fouling the disc magnet look at it and figure out which way it needs t go up or down and bend it slightly

is it a replacement case cover for dvd drive or the clear spindle that is meant for hitachi/samsung?

your first post says no bad blocks but seems there are bad blocks after all did you not see that?

you will have to remap these also these are the cause of your E71 (corrupted NAND files)

act as if the last block wasnt there as it will be remapped to the last free block before it

0x155 to 0x3FE

0x313 to 0X3FD

so make a new XBR.bin insert KV and config then do

nandpro XBR.bin: -r16 0x155.bin 0x155 1
nandpro XBR.bin: -r16 0x313.bin 0x313 1

nandpro XBR.bin: -w16 0x155.bin 0x3FE 1
nandpro XBR.bin: -w16 0x313.bin 0x3FD 1

then erase your nand

nandpro lpt: -e16

then write XBR

nandpro lpt: -w16 XBR.bin

why in gods name would you want to put an xbox into that pos?

looks terrible and would look $#!t in my tv stand lol

no disrespect but its a console only a mother would love!!

i have that issue also

change ports and it will go away

or hit the square with 3 dots beside the port to refresh the port, then change port and back and it will go away

just a bug in JF nothing to do with the LT switch

AFAIK hitachi drives are all the same board layout the ribbons will all be the same anyways

anyways as long as you get a close rev it should fit fine 47 to 59 is defo ok

to put key into new drive i would do the following

assembe drive with new board

use JF to put drive into modeb

dump the drive using JF to get native FW call it new.bin

open your orig fw in fwtoolbox and save key into notepad

close then open your new.bin in fw toolbox

copy correct key from notepad into clipboard then paste into fwtoolbox and hit save key

then chosse the option to patch key and spoof as original hitachi 47

stick it in xbox and pat yourself (and me lol) on the back

good luck!!

ps i have the manual way to do it quickly in dos if you want, but its sending commands that may confuse you the other way is easier for beginners

no and next time read up a bit b4 posting stupid $#!t.

too many reasons to go into why its a no

you'll have to figure that one out yourself i cant be arsed.

why did you wire the diode to the ROL board instead of the undwerside of mobo? seems wierd to me and its obviously the cause of your issues

all of the falcons i do i keep ALL of the JTAG wiring on the underside of the board its much neater and easier to route to and you dont have to pass through the board

if you have your kv then you can write a bit b4 it errors try to get linux running and flash within linux then there will be no issues

my theory is that the nand image is encypted as a whole, you cant change bits in and out without breaking the overall encrytion even though its all done in the same CPU key i know

try extracting/injecting with bincrypt i had an issue with 360flashtool before that it did not produce a correct KV.bin to use with a con resigner and i had to use an older version to get a correct kv.bin

offset issues im told.

this would explain the xmas lights issue also.

flacon nands are a nightmare!

dumps all match?

confident writes go 100%?

try this

erase nand

write XELL

dump it and verify it

wont take long to do will tell you if your setup is sound

you using compostie/vga not HDMI?

heres another cryptic clue

falcon mobo need a diff media update also 'out there'

ready........GO!

the errors that occur during reading writing are random and dependant on alot of factors it can occur during the dumping of any section of the NAND

you have a dump that has all of the important files intact to run without any major problem, errors could be in free space or a rarely used file (secdata.bin etc)

if i was you id build an XBR image, inject kv and config blocks then use nandpro to move the last bad block


command

nandpro XBR.bin: -r16 0x3FF.bin 0x3FF 1                     read bad block
nandpro XBR.bin: -w16 0x3FF.bin 0x3FE 1                    write bad block to 0x3FE

then write to NAND using flash360 if your XBR boots or lflash if you can get linux running

0x3FF is the very last block and is usually a remapping block for other bad blocks the remaps start backwards from here so in theory as long as you remap it, it should be fine

more as i think of it unless your nand develops a bad block and the block is moved automaticaly during a flash update, you should have no problem, in fact remapping 0x3FF to 0x3FE will prevent that problem in the future

degraded no coz you prob didnt hex the date to 2005

360flashtool what version you using?

reconstructing a NAND is a bad idea

how many times does it have to be said?

do not flash the damn xbox until you have 2 100% matching dumps!!!

if you have overwritten your original NAND you could have issues if you want to return to stock dash falcon NAND images are awful to make ive not succeded in my tries.

if you have your kv and config block you should be ok

try to get linux running and flash from there if your lpt setup is crap.

also if you have flashed over lpt id suggest putting a copy of your XBR image on usb and run flash360 and flash the NAND again to make sure its 100% correct

if your lucky the kv and config blocks are ok and you can get it running XBR

good luck