Kernel/dash Versions For Reference, Since Live Automatically Updates Options

[enixn]

so i remember reading somewhere that the xex of the emulation profile update was kinda like a zip file, which if true means that it extracts the content somewhere first before moving it around on the hdd...would they first be extracted to the hdd?....or can the files exist in the ram and from there be copied directly to the hdd into their specific location?...but then everything read to ram is encrypted i think, and so on and so forth...

[lordvader129]

so i remember reading somewhere that the xex of the emulation profile update was kinda like a zip file, which if true means that it extracts the content somewhere first before moving it around on the hdd...would they first be extracted to the hdd?....or can the files exist in the ram and from there be copied directly to the hdd into their specific location?...but then everything read to ram is encrypted i think, and so on and so forth...

the files would be exrtracted stright to the HD

[enixn]

aha, so i guess M$ did it after all....A disc was created with a loose media check that references external files:
http://forums.xbox-scene.com/index.php?showtopic=474350 , So now, back to my original post, anyone think its still possible?...hehe

[cregan]

My 360 just flashed its kernel and dashboard for a secong time. My xbox was (D:2.0.2241.0 - K:2.0.2241.0) but now it updated to (D:2.0.2255.0 - K:2.0.2255.0) but my BK is still (2.0.1888.0). This doesn't mean that the backup isn't reprogramable but it does mean that the 360 doesn't automatically update it's back up to the current kernel when the current kernel is being updated. This is what i expected. My question is that does anybody know a way to get the 360 to reflash its backup? My computer has 2 network ports and i want to try using it as a server between my 360 and the internet (xbox live). If I could get the xbox to update through my computer i could get more info on how its done. The only problem is that i never know when my 360's gonna update and if i did get it i only get one shot at trying to read any info.

[lordvader129]

My 360 just flashed its kernel and dashboard for a secong time. My xbox was (D:2.0.2241.0 - K:2.0.2241.0) but now it updated to (D:2.0.2255.0 - K:2.0.2255.0) but my BK is still (2.0.1888.0). This doesn't mean that the backup isn't reprogramable but it does mean that the 360 doesn't automatically update it's back up to the current kernel when the current kernel is being updated. This is what i expected. My question is that does anybody know a way to get the 360 to reflash its backup? My computer has 2 network ports and i want to try using it as a server between my 360 and the internet (xbox live). If I could get the xbox to update through my computer i could get more info on how its done. The only problem is that i never know when my 360's gonna update and if i did get it i only get one shot at trying to read any info.

what you need a second 360, or a friend with one, once yours updates bring him over and let his update

would actually be interesting to see how an update from 1888 to 2255 goes


personally i dont believe backup kernel would be left writable, the idea behind it would be if your 360 gets a bad flash this will let it reprogram itself, by putting the backup in jeopardy of a bad flash you pretty much nullify its entire purpose

[bowser22]

Maybe if you run your internet connection thorugh your pc with 2 nic's,like your main connection on nic 1 and have that shared to nic 2 for your 360 then use a program like packetzyer to capture the packet then dissasemble it then learn how it works and write your own flash then turn your pc into a live server and make it update
sounds farfetched

c ya

[littlestevie360]

Im under the impression that the Bootstap and the Kernal are burned into the CPU (ie: not reprogrammable)
and that the Kernal update is infact a patch that is written to the TSOP. Thus BK standing for Base Kernal not Backup Kernal.

This is my opinion on the matter and in theory works perfect, its n00b pr00f


Littlestevie360

[LightningStruckMyXbox]

Im under the impression that the Bootstap and the Kernal are burned into the CPU (ie: not reprogrammable)
and that the Kernal update is infact a patch that is written to the TSOP. Thus BK standing for Base Kernal not Backup Kernal.

This is my opinion on the matter and in theory works perfect, its n00b pr00f
Littlestevie360

Unless the BK revision changes after a dash update

[littlestevie360]

Unless the BK revision changes after a dash update

which to date hasnt happened

[ethan craft]

[u][/u]

My current kernel and dash have been upgraded to: 2.0.2241.0

(D:2.0.2241.0 - K:2.0.2241.0)
BK:2.0.1888.0

I'm guessing that BK = Backed up Kernel since I think if we're flashing from Live that there would be a backup kept.
Also, when I opened my console it said revision 1888 so I'm quite sure that's the version it shipped with. Everyone please post your results and if you've connected to live or not and if you can remember, how many updates you've received. I've received two if I remember correctly.

Edit: To view this information simply go to your dashboard. Then go to the system tab. Next go to console settings. Then go into system info. You'll notice information similar to what I posted above in the lower left.

I also applied a thin layer of Arctic Silver 5 to my cpu and gpu. I'd recommend the same since the gpu uses an aluminum pad.