LITEON DG-16D4S - SLIM 2.0.13146.0 to 2.0.13604.0 with cfw failed

[jamie321]

I have a 4 gig slim that has 9504 osig.

i tried FOOLISHLY to update with cfw from 2.0.13146.0 (dash that reflashed drive fw to 0272 but didnt spi lock) to latest dash.

update failed and gave error

335A 3524 B600 0401 C000 0001
contact xbox support.

The drive (winbond) was spi locked during attempted update.
I have killed the pcb :facepalm: kamakazee style.

so my question is if i buy a team x pcb (if i can find one) flash it with ofw 0272 will the update be a sucess.

The console now switches on says applying update then error cant update your console

335A 3524 B600 0401 C000 0001

I know i shouldnt of tried to update with cfw (i was being stupid and now I am the noob).

I know its probably flagged the console for a ban.

If anyone has a definate answer i would be gratefull
If not then it can go in the box labled another idiotic failiure by jamie321.

 

[demon2011]

Get a tx-unlocked pcb and flash it to stock 0272 then reflash to 2.0 job done, should work.

 

[jamie321]

Get a tx-unlocked pcb and flash it to stock 0272 then reflash to 2.0 job done, should work.

if someone could confirm, this will 100% work as £50 is quite a bit of cash. thanks

 

[tingedace]

Yes, 110%

 

[MightyShots]

if someone could confirm, this will 100% work as £50 is quite a bit of cash. thanks

This will depend on how your tied to update, thats how i understand it. If the update failed via xbl update then you can use a usb, if it failed using the backed up game then just insert the original to complete it. However if you want CFW back the the best option is the TX replacement PCB, as long as you have the key still

 

[frazzeld]

if you had have flashed to stock prior to the attempted update your drive would have locked on 0272 after the update anyway

Buy a TX and sell the winbond

 

[jamie321]

bought tx unlocked replacemant, flashed fw as stock 0272. update still fails, tested tx board in another slim and works fine...... any help

 

[RickSizz]

Try this..it can't hurt.. flash the tx pcb to stock 9504 using your key, leave all spi unlocked (switch and in jf) and attempt to update. If it fails again, lock the drive in jf but leave switch on pcb unlocked. if that fails then lock it all and attempt to update it again. Remember the 9504 to 0272 locks the drive and changed fw ver so the update is going to want to flash first, then lock it down. Good luck.

 

[jamie321]

Try this..it can't hurt.. flash the tx pcb to stock 9504 using your key, leave all spi unlocked (switch and in jf) and attempt to update. If it fails again, lock the drive in jf but leave switch on pcb unlocked. if that fails then lock it all and attempt to update it again. Remember the 9504 to 0272 locks the drive and changed fw ver so the update is going to want to flash first, then lock it down. Good luck.

this wont spi lock the drive permanently?
so leave the switch on wp1 or wp 0, only got the pcb today? is wp1 unlocked.
soz for sounding idiotic

 

[diaboliq20]

Try this..it can't hurt.. flash the tx pcb to stock 9504 using your key, leave all spi unlocked (switch and in jf) and attempt to update. If it fails again, lock the drive in jf but leave switch on pcb unlocked. if that fails then lock it all and attempt to update it again. Remember the 9504 to 0272 locks the drive and changed fw ver so the update is going to want to flash first, then lock it down. Good luck.

this wont spi lock the drive permanently?
so leave the switch on wp1 or wp 0, only got the pcb today? is wp1 unlocked.
soz for sounding idiotic

RickSizz is worng - the 13599 update will attempt to lock the SPI on the PCB - this will fail EVERY time with a TX PCB as the update cannot complete the task - your original PCB needs to take the fall here, and get it's SPI locked, then flash your TX PCB to the latest fw, and lock the SPI - then move WP switch to 0 and you're good to go

unfortunately your orig PCB is dead by the look of it is it?

 

[jamie321]

RickSizz is worng - the 13599 update will attempt to lock the SPI on the PCB - this will fail EVERY time with a TX PCB as the update cannot complete the task - your original PCB needs to take the fall here, and get it's SPI locked, then flash your TX PCB to the latest fw, and lock the SPI - then move WP switch to 0 and you're good to go

unfortunately your orig PCB is dead by the look of it is it?

dead as dead can be (strange though the orig pcb was spi locked during failed update, as i had to kamakazee it to unlock (all went wrong after trying that), so i need an orig unlocked 9504 drive or a unlocked m$ 9504/0272 pcb. lmco.
suppose its worth £ something.com to someone

hang on if the drive was spi locked? then why is the update trying to spi lock a tx pcb that is locked...???

 

[diaboliq20]

ok - I'm confused now lol
so - you had the original PCB in (I assume with cfw on it) you then did the update to 13599 which failed yet locked the SPI??????

 

[RickSizz]

RickSizz is worng - the 13599 update will attempt to lock the SPI on the PCB - this will fail EVERY time with a TX PCB as the update cannot complete the task - your original PCB needs to take the fall here, and get it's SPI locked, then flash your TX PCB to the latest fw, and lock the SPI - then move WP switch to 0 and you're good to go

unfortunately your orig PCB is dead by the look of it is it?

See diaboliq20 I understand my method is incorrect, fully. My post was just an attempt to give him other options because he doesn't seem to have a working stock pcb to take the fall. But thanks for pointing that out.

 

[diaboliq20]

See diaboliq20 I understand my method is incorrect, fully. My post was just an attempt to give him other options because he doesn't seem to have a working stock pcb to take the fall. But thanks for pointing that out.

I'm going boggle eyed today - you'll have to excuse me

 

[jamie321]

ok - I'm confused now lol
so - you had the original PCB in (I assume with cfw on it) you then did the update to 13599 which failed yet locked the SPI??????

i had orig pcb with lt2.0 (flashed to it) tried to update from 2.0.13146.0 with 0272 drive not spi locked to 2.0.13604.0 latest dash.

it did the first bit of the update, restarted console and said applying update.... cant update your xbox error bla bla bla (see page 1) so i assumed cfw was to blame...
i removed drive and hooked up to jf in an attempt to restore ofw but drive was spi locked. i killed pcb kamakazee.
so i think console knows drive is spi locked.

hey never mind, its my own fault for bolloxing about with cfw upon update of dash....

but if anyone knows of a fix im all ears as dumbo said

 

[diaboliq20]

Are u doing the update with any memory attached.... I.e. Hdd etc?

 

[jamie321]

Are u doing the update with any memory attached.... I.e. Hdd etc?

Yep, its 4gig, ive also tried with 250gig hdd.
it tries to apply the update then fails, ive tried switching on and pressing sync but still no joy.
maybe this ones goin on ebay...
but i will explain in listing everything ive tried

jsinger on jungleflasher #efnet said i MUST HAVE A LITEON SLIM MS PCB. period


p.s. could i not rgh it with coolrunner and a donar nand? assumming i could write xell to it and get cpu key, i could use donar nand for freebootythingy, im prob talkin bs, just a thought

 

[tonyg243]

When I purchased my slim,and opened it it was a winbond 0401.I then bought a spare dvd drive without a pcb and put a tx unlocked pcb in there.The golden rule we have all seen on here is "Flash back to stock before accepting a dashboard update".This obviously will involve having to open up your slim.Therefore I have my original drive for updating and then my cfw drive for playing my back-ups.Some may say that seems a bit o.t.t, of course you can always swap out your pcbs,update then swap them back.My solution saves having to dismantle dvd drives everytime there is an update.Also this way you dont have to keep flashing back to stock when your original will always be stock.

 

[page360]

Go to Ebay and buy original 9504 PCB without dash update (unlocked)

 

[jsinger47]

Yep, its 4gig, ive also tried with 250gig hdd.
it tries to apply the update then fails, ive tried switching on and pressing sync but still no joy.
maybe this ones goin on ebay...
but i will explain in listing everything ive tried

jsinger on jungleflasher #efnet said i MUST HAVE A LITEON SLIM MS PCB. period


p.s. could i not rgh it with coolrunner and a donar nand? assumming i could write xell to it and get cpu key, i could use donar nand for freebootythingy, im prob talkin bs, just a thought

Yea I did say that Haha. Tx pcbs fail for the 13146 update for 9504 0272. Find yourself an unlocked PCB.