Print

[Dark Mod]

QUOTE(moh.sakhaii @ Apr 9 2011, 11:51 AM)

Damn, if they do this, we are screwed for good      

screwed is an understatement...more like raped without lube

[moh.sakhaii]

QUOTE(Dark Mod @ Apr 9 2011, 07:27 PM)

screwed is an understatement...more like raped without lube

Yeah, that would do some justice (IMG:style_emoticons/default/sad.gif)

[Ranger72]

it just makes thing more difficult but it is not the end by any means of the imagination. Give the people in the know time and I am sure things will happen.

[alanewake]

Thanks Ranger72...I didn't mean that I don't believe you..no...but thanks a lot for this screen...

[dave11674]

im sure there will be some kinda patch program to patch in your modified firmware into the firmware update to this new beta dashboard
so when it does flash the drie its with "your" modified firmware

just a thought
would be nice

dave

[mikey63366]

I hope they get work around to get our keys if we updated to beta dash.  I was looking foward to flashing my drive, but now I'm holding off since everyone reporting cant get there key after updating to beta dash.  

[juggahax0r]

I'm pretty sure they are updating it with a file called oddupd.xex in the sys update file , I haven't looked in any other system updates so i don't know if that is a standard file or not , their are 3 of them oddupd1 , 2 ,3 respectably. Xextool reports it as a DLL , I think i saw a reference to it in the install_extender.xex i'll have to take another look.

 Seems like they are updating them to conform to their new disc standard. Whatever it is they are doing , it doesn't appear to be related to stopping mass piracy or unflashing your modded drives , just updating the drives FW to conform.

 In another thread we are discussing this same issue , apparently if you have a modified FW on your drive the system update will fail , and if you flash back to stock then run the update it will work and flash your drive and you can then dump it and flash it again.  It also appears to fail if you have no drive in at all , or a drive with the wrong key.

@Ranger - if you are unable to dump the FW after it's been updated through the system update then apparently whatever hole was open to get the fw without a hardware hack has been closed , or just another software method will need to be found.  It seems the old 360s can just be reflashed so this must be related to the new slim drives.

[arana]

well guys since its confirmed that after beta update you can reflash FATS back to whatever you had before, that gives me some relief, since drives are still reflashable it would be a matter of time (and i believe not much) before c4eva and team either fix the lt+ fw, modify the rootkit to report the right version (in case of slims), or just create another fw, they have already released 1 slim version so i believe they have the most of the work already done.

anyone knows if previous 9054 slims are also reflashable after update?

I have only read of people flashing back to lt+ with fats, not a single one i have read about doing it with slim, but if 0225 was more difficult to write to, my bet is 0272 would be even harder. i am sure they are already working on this, and i am also sure they wont release nothing before the official dash launch to prevent from MS doing it even harder for the final.

btw did you check the FW was not 0272 before updateing? and does this apply to fats? i would like to know what version the FAT reports after update, if they had OFW and what they report if they had CFW

This post has been edited by arana: Apr 10 2011, 04:43 AM

[juggahax0r]

QUOTE(arana @ Apr 9 2011, 11:37 PM)

well guys since its confirmed that after beta update you can reflash FATS back to whatever you had before, that gives me some relief, since drives are still reflashable it would be a matter of time (and i believe not much) before c4eva and team either fix the lt+ fw, modify the rootkit to report the right version (in case of slims), or just create another fw, they have already released 1 slim version so i believe they have the most of the work already done.

anyone knows if previous 9054 slims are also reflashable after update?

I have only read of people flashing back to lt+ with fats, not a single one i have read about doing it with slim, but if 0225 was more difficult to write to, my bet is 0272 would be even harder. i am sure they are already working on this, and i am also sure they wont release nothing before the official dash launch to prevent from MS doing it even harder for the final.

btw did you check the FW was not 0272 before updateing? and does this apply to fats? i would like to know what version the FAT reports after update, if they had OFW and what they report if they had CFW

http://forums.xbox-s...p;#entry4792002

 This thread has some people doing some tests also on the update. Most of these are fats no slims.

[-Gadget-]

QUOTE(juggahax0r @ Apr 10 2011, 04:37 AM)

I'm pretty sure they are updating it with a file called oddupd.xex in the sys update file , I haven't looked in any other system updates so i don't know if that is a standard file or not , their are 3 of them oddupd1 , 2 ,3 respectably. Xextool reports it as a DLL , I think i saw a reference to it in the install_extender.xex i'll have to take another look.

 Seems like they are updating them to conform to their new disc standard. Whatever it is they are doing , it doesn't appear to be related to stopping mass piracy or unflashing your modded drives , just updating the drives FW to conform.
<snip>

its a shame that early tests looks like its not possible to fix those consoles thats lost there key, but hopefully maybe in the future we can alter the sytem update files (with out breaking the signing) to get it to flash a drive with a wrong key (IMG:style_emoticons/default/smile.gif) (maybe having the key of all FFF's, all 000's could work ?)

This post has been edited by -Gadget-: Apr 10 2011, 12:16 PM

[boflc]

QUOTE(-Gadget- @ Apr 10 2011, 06:16 AM)

maybe in the future we can alter the sytem update files (with out breaking the signing)

not going to happen, unless you end up jeff-goldblum'ing the mothership in independence day.

[juggahax0r]

QUOTE(boflc @ Apr 10 2011, 10:50 AM)

not going to happen, unless you end up jeff-goldblum'ing the mothership in independence day.

 Sounds like a plan to me.

[xfxgames]

Now for the logic guys! the secret may be easier than you think, why? we have a dashboard or Update 2.0.13141.0 Beta 2.0.13142.0 Beta Update the logic it stores the firmware file to update it can do so if dashboad take this and analyze this file may have an opening to and to update any console via USB drive and modify to update the firmware xxxx.xxxx ...... , which is understood at all get the firmware from microsoft and put the hacked firmware, when the dashboard is modified to install the firmware from microsoft it takes the firmware that was patched on the console and play it, it can be easier than this despair all that's happening. I think the most viable solution at this time. no cricket, only to get the dashboard to change the directory where this firmware, and put the hacked firmware ... if you delete all data from there it will put all that exists can be sure to update it and the stick and gets away with this agony, the dashboard can Flesher by usb! why not a hacked firmware on dashboad clear that for each console should create a program for patching the dashboard with the firmware. this can be a breeze for C4eva ..

[Ranger72]

QUOTE(xfxgames @ Apr 10 2011, 08:56 PM)

Now for the logic guys! the secret may be easier than you think, why? we have a dashboard or Update 2.0.13141.0 Beta 2.0.13142.0 Beta Update the logic it stores the firmware file to update it can do so if dashboad take this and analyze this file may have an opening to and to update any console via USB drive and modify to update the firmware xxxx.xxxx ...... , which is understood at all get the firmware from microsoft and put the hacked firmware, when the dashboard is modified to install the firmware from microsoft it takes the firmware that was patched on the console and play it, it can be easier than this despair all that's happening. I think the most viable solution at this time. no cricket, only to get the dashboard to change the directory where this firmware, and put the hacked firmware ... if you delete all data from there it will put all that exists can be sure to update it and the stick and gets away with this agony, the dashboard can Flesher by usb! why not a hacked firmware on dashboad clear that for each console should create a program for patching the dashboard with the firmware. this can be a breeze for C4eva ..

Only thing you are forgetting is that if you alter just one bit of code in any of the dashboard update files it breaks the signature rendering the complete dashboard update file useless.

[xfxgames]

could have a way to update the firmware does not have to open the console, why? become routine! all the time will have to open the console to change the firmware, get the original and put the hacked total discomfort. everyone. I think the solution would be to flash the drive by the usb console would become easier and faster. with the information we have everything on the Internet become easier and faster,  sort by flashing stick.


This post has been edited by xfxgames: Apr 11 2011, 04:11 AM