Some people are trying it on xboxhacker , i will check again and see if they made any progress. The problem is going to be the efuses among other things. It burns the efuse before it does the update , so if you have the resistor removed when you do the update if you just tried doing it even on a normal 360 with it removed it will fail and reboot , boot to dash with no error but an unchanged dash version , normally you would get an e80 error because it burned the fuses afterwards leaving you unable to boot with unburned fuses.
The hack still uses the same SMC code it did with the KingKong hack or at least very similar , i'm sure it is different between the MoBo revisions , and until XBR/freeboot their wasn't a whole lot of work being done on retail 360s. Xbr is a patched version of 8955 , and all the SMC patching is done as the system boots when you hit the power button or the eject button for xell , that is why it takes longer to boot , it patches it then reboots after POST and it keeps the system alive , and running an exploitable CB on the new dash. The major issue besides the efuses is the CB the new kernels are made not to run with an old CB. If you open an Xbr image in Flashtool you will see the CX section , it shows the explotiable CB on mine it is a Zephyr so that is a 4558 and the patch 0 is the exploitable 4532 dash from the kinkKong shader hack , and that one is the same on all images. However the dash you are actually running is the 8955. I guess the major issue is changing the virtual efuses too match what the kernel expects , so they have to find which value has changed and update the virtual fuses to match.
I am by no means an "expert" but i have done a lot of this stuff in the last few months and read a lot , i am not a coder but i am learning , i am more of a hardware guy than software , but that is my basic understanding of it their are a lot more details though. Check out xboxhacker see if they made progress i know i am going too.
This post has been edited by juggahax0r: Apr 11 2010, 06:33 AM