Xbox 360 XDK flash/XDK kernal question

.

 

No. XDK do not require any development files on the HDD/sidecar. What files are in "filesystems" on a retail console running an XDK kernel are on the official XDK's nand. Filesystems is on a RGH/Jtag running RGLoader's HDD because the retail NAND is too small by comparison.

Flash refers to the retail dashboard. XDK refers to the Launcher version. Both are updated by a recovery via ISO or remote.

You're running the most recent leaked XDK firmware, you do not need to worry about updating anytime soon.

 

woo! surgeon to the rescue thanks for the info mate! id assume this is gonna be the last XDK launcher revision huh? :/ or at least very near to the last?

 

I'm sure it wont be the last recovery but more than likely tapering off to the end as the Xbox 360's flame slowly burns out. You CAN upgrade and downgrade as you feel fit as long as it's not dramatic. For example going from 21256.3 to 1888.0 and back. There is not much of a reason to downgrade, but just know it's possible and safe if it's done gradually with official recoveries both iso/disc or remote based.

 

That's awesome! i do like the look of those beta launchers! is there anyway to flash the XDK launcher revision with perhaps a .xex and a file that gets read of a usb? if so id flash down as soon as i can find some launcher files haha xD just for shits and giggles.. a console running 16547, yet with a beta launcher.. hehe

i wouldn't if it wasn't safe like you said to just go down all in one go, if so. id purchase some many versions of earlier revisions so i can step it down date by date to be safe

 

You won't be able to separate the flash and the launcher files, it'll corrupt the nand causing E71. Sorry, no 16547 running the beta launcher. I have tinkered with using a bladed dashboard.xex with a modern revision and it crashes the kit. All recoveries must be done with either ISO/disc or remote otherwise it can spell trouble that might not be able to be turned around for the kit.

 

.

 

Do dev kits not have efuses, then? I was always under the impression that they did. Also, can a Beta 2 downgrade to the beta dash?

 

They have fuses just the systemcall for using them is never called in the dev updates, nor is there a requirement for certain kernels to run. All 360 cpus have fuses

 

Hmm, interesting!

 

So by this, you mean a Jasper could run a 1888? Whats the general rule of thumb for stepping up and down?

Also don't the efuses have something to do with like a limited number of flashes, or is that bullshit, or a high enough number?

Cheers!

*Actually, just remembered I have a while slim XDK with a 2013 manufacture date, and I tried flashing 20353 and it said not compatible?

 

I have taken my jasper as low as 7776 and never had any issues. Although I probably wouldn't want to try lower haha.

I can only assume that slims would be limited due to their later release? Although I seem to remember being able to run under 20500 on my slim.
I could be wrong though as I never really went all out with testing recoveries.

 

I have dropped xenon, zephyr, falcon and jasper xdk down to 1888.0 Beta. No issues as long as it is gradually done. I dropped a trinity straight from 21250.7 to 1888.0 by accident, put in wrong disc, in order to get rid of xbdmrecovery.xex so I could use a remote recovery again and it caused serious nand corruption in which the FS Table was totally missing. It took me having to buy another trinity and a nand-x with a ton of patience and 2 months of work to get it back up in running without a copy of the original nand. Upgrade, downgrade just don't do what I did the one and only time.

 

That makes more sense taking down to a lower one and then further. Going straight from to the other seems to be just bad news...

 

.

 

I dont remember the XDK working with the wireless adapter, assuming you are using a non-slim.

 

no way/patch around that? :/

 

Wireless both slim and phat with adapter is used for Partnernet access only and not for the Launcher to use Neighborhood. It won't work. AFAIK there is no patch, but I could be wrong. But straight "out of the box", no.

 

ah shame :/ well at least now i know! thanks

 

I could make a patch for it easily enough, but the feature was removed for a reason. WiFi simply isn't consistent/ strong enough for file transfers and will generally lead to corruption using the protocol in Neighborhood. If you ever need help rebuilding a NAND, recovering a brick, or anything else technical, I have gained plenty of experience with it and can probably help you with anything you need.