I know you should always revert to stock FW before updating your dash and then re-flash, but I was just wondering what would happen if you left CFW on the drive and used J-runner to write a retail 15574 to the nand. Would this still cause some kind of ban flag? Not really thinking of trying this , just curious if it would work.
Can you write retail 15574 to nand with LT+ 3.0 still on
- Thread starter MySongRanHills
- Start date
Martin C
VIP Member
Anything you build with J-Runner is done outwith the normal MS update route. The question is why are you asking? What dashboard are you currently on?
My xbox is fine. Like I said I don't intend to do this. I have a CK3 mini and a VIA6421. I was just curious and trying to learn. At the same time I was thinking if you did a DemoN install for someone and flashed their drive, when a dash update is pushed out instead of them having to figure out how to take apart their xbox and re-flash their drive back to stock, they could just wait till J-runner gets support for newest dash and build a retail dash and flash that to stock nand. Again assuming it wouldn't flag your console even though you aren't using a microsoft update(which I assumed it wouldn't I wouldn't ask).
Martin C
VIP Member
Martin C
VIP Member
I should have added, there may be instance where this doesn't work. We don't know what MS have in store for bootloaders for example.
Wait I think you might have lost me. Let me see if I follow. Are you referring to an update like 2.0.14717.0 where they changed everything to splt CB? Writing that dash to your nand with out going through the microsoft update would cause something not good I'd assume, since the console would still have a single CB and the dash would expect to find split? So if in the future they change it again it would cause problems? Thanks you, you have been helpful.
Martin C
VIP Member