GENERAL 9504 pre dash lock

[Preddy]

Just wondering if it would be possible to read the key then put a tx replacement board in and update the console with the tx board?

thanks

 

[diaboliq20]

nope - read the key - update and lock the drive.,...then put the TX board in

EDIT - just to expand on the above....
If u update to 13599 witht the TX board in...the update will attempt to lock the drive, and it wont be able to......failed update.

If u update with the original PCB in the update will lock the SPI and finish the update...then flash your TX board as an 0272 with the latest CFW then lock it and put it in your drive.

 

[Netkar]

you can see all here http://team-xecuter.com/forums/showthread.php?t=70447

 

[nosherfj]

hot swapping every update?
or
what if you got a sputnik switch installed then it's ok to update with stock pcb?

 

[diaboliq20]

hot swapping every update?
or
what if you got a sputnik switch installed then it's ok to update with stock pcb?

Didn't we have this conversation the other day? lol :rolleyes2:

I really don't think there will be any hot swapping needed after the 13599 update

 

[Netkar]

update is for xgd3, I think for now no other updates.. hope..

 

[nosherfj]

we did have same convo lol
iam still un clear.
EDIT - just to expand on the above....
If u update to 13599 witht the TX board in...the update will attempt to lock the drive, and it wont be able to......failed update.
i see it like this-
all updates after 13146 flash the drive if it's on old fw.
all updates after 13599 look at the spi status on 9504/0272 drives this includes in the FUTURE.
so....
if this is the case and you have a tx pcb installed, your have to "hot swap" before updating your 9504/0272 console to dash 13599 or FUTURE dash's as the update will check the spi of the tx pcb and it has a different spi configuration to a stock 9504/0272 pcb lock spi.

this is why it's advised NOT to update with a tx pcb as per the op

help??? lol

 

[diaboliq20]

I see it like this - and I may be wrong (I usually am lol)

update to 13599 locks the SPI.
m$ carry out realtime checks on the status of the SPI i.e. locked or unlocked, as will future updates.
As they are not actually changing the SPI status, the TX PCB is safe for the forseeable post 13599 dash updates.

You watch - a mod will swoop in here and kick my butt now for talking rubbish lol

 

[Netkar]

in the topic that I tell previusly we have already talked about it

 

[nosherfj]

the tx pcb can't be safe as it failed the 1st time otherwise you could just update to 13599 with a tx pcb

 

[diaboliq20]

the point I'm making is the 13599 update locks the SPI on the original PCB right?
if the TX PCB is in for the 13599 update, the update cannot lock the SPI of the TX PCB as it is hardware rather than software locked.....hence the failed update.

Future updates will not attempt to lock the SPI again (because m$ think they have already locke it)....only "have a look" to see if it is locked, so the update shouldn't fail

same principle as the 0225s

 

[sp4rkst4rt3r]

I see it like this - and I may be wrong (I usually am lol)

update to 13599 locks the SPI.
m$ carry out realtime checks on the status of the SPI i.e. locked or unlocked, as will future updates.
As they are not actually changing the SPI status, the TX PCB is safe for the forseeable post 13599 dash updates.

Just to add to previous post for clarity:-

M$ may very well check the SPi status on future dash updates but they could also check what FW is on the drive.

So it will still be necessary to flash back to OFW and lock the SPi before attempting any dash update

 

[nosherfj]

aha so they know your updating from dash 13599 and so won't check?

it was my belief the checks were not performed on 0225 for the reason you give but for ever more will be performed on 9504 as they want to make sure all 9504's out there are locked.

i'd feel jittery updating a 9504 with a tx pcb still iam sorry not convinced lol

 

[diaboliq20]

I'm pretty sure the update will first check the SPI status - then lock if needed no?
otherwise if they attempt to lock and already locked drive m$ would fail their own update...

EDIT - thanks for the clarity their sp4rkst4rt3r - a very good piece of advice guys

 

[nosherfj]

I'm pretty sure the update will first check the SPI status - then lock if needed no?
otherwise if they attempt to lock and already locked drive m$ would fail their own update...
so why not update to 13599 with a tx pcb?

 

[diaboliq20]

because pre 13599 the drive isn't locked....this is the first update with the lock in....so it will, I assume, just automatically attempt to lock the SPI this update....just seems logical

 

[sp4rkst4rt3r]

so why not update to 13599 with a tx pcb?
[/COLOR]

Maybe because from 13146 dash to 13599 dash M$ would expect to find a UN-Locked SPi and if you allow M$ to lock the TX PCB it would foook it up

Edit:- SNAP!!!!.....damn keyboard racers...lols

 

[Netkar]

Maybe because from 13146 dash to 13599 dash M$ would expect to find a UN-Locked SPi and if you allow M$ to lock the TX PCB it would foook it up

Edit:- SNAP!!!!.....damn keyboard racers...lols

Is possible wrong but I know that with tx board fail update and flag console but don't fook the tx pcb..

 

[sp4rkst4rt3r]

Maybe because from 13146 dash to 13599 dash M$ would expect to find a UN-Locked SPi and if you allow M$ to lock the TX PCB it would foook it up

Edit:- SNAP!!!!.....damn keyboard racers...lols

Is possible wrong but I know that with tx board fail update and flag console but don't fook the tx pcb..

I have highlighted the important word just for you :facepalm:

 

[nosherfj]

but future updates have to at least check the spi status of 9504/0272 pcbs
so if it fails with a tx pcb 13599 it's gonna fail again for future updates.
or
are the spi status locked the same for tx pcb and stock pcb?
if so
why did it fail for 13599 with a tx pcb?
think I'll have to start my own thread on this sometime lol
and tx pcbs are software locked and hardware locked.