Topic: 4552 Update? (Read 105 times)

tmh88 · « **on:** March 24, 2007, 07:45:00 PM »

Hey guys, I used to visit this site when I was really into modding, and lately I haven't been on. Anyway I'm trying to learn more about the 360 and I'm confused about the 4552 kernel and the issues dealing with upgraded firmware. What exactly is so bad about this kernel, and what can happen if you have upgraded firmware and you update? I did some research and read something about efuses(i know how they work so no need for an explanation of them), but I don't know why they're related to this update. I searched and couldn't find any posts that answered this so I'd appreciate it if someone could explain the situation.

I'd like to upgrade my dvd firmware, but I'm almost positive my box is already upgraded to the 4552. I read that COD3 and GOW upgrade automatically. anyway umm yea, thanks

Havok · « **Reply #1 on:** March 24, 2007, 11:19:00 PM »

The 4552 Kernel is required if you go on LIVE or play any NEW games..

MS fixed a security hole that allows the running of homebrew code.

The 4552 update blows efuses so that the kernel can not be downgraded and homebrew can no longer be run.

None of the MS updates have anything to do with the firmware modifications..

This post has been edited by Havok: Mar 25 2007, 06:20 AM

tmh88 · « **Reply #2 on:** March 25, 2007, 10:34:00 PM »

That really sucks, but at the same time its cool that they have the ability/technology to do that.

But from what I read about efuses, they are not permanently "blown". They can be reversed, so this means that technically its possible to "un-blow" the efuse if someone is smart enough to figure this out.

This is what wikipedia says about it. "This process does not physically destroy the eFUSE, so it is reversable and repeatable."

This post has been edited by tmh88: Mar 26 2007, 05:36 AM

Havok · « **Reply #3 on:** March 26, 2007, 10:16:00 AM »

You can't unblow an efuse.

Wikipedia is probably wrong or mistaking in the fact that you can probably undo the affects of an efuse by blowing additional ones.

Now you can remove a resistor and prevent the efuse from being blown. But the upgraded Kernel is still very hard to downgrade. You would need to desolder the flashrom and reprogram it using an external programmer.

caster420 · « **Reply #4 on:** March 26, 2007, 12:08:00 PM »

QUOTE(Havok @ Mar 26 2007, 11:47 AM)

You can't unblow an efuse.

Yes, in theory you can. However, we cannot do so with the 360. Here is a quote from networkBoy...

QUOTE

To "unblow" an e-fuse requires a charge pump and voltage path. These are OTP. There is no erase path to unblow them. Sorry.
-nB

Caster.

Havok · « **Reply #5 on:** March 26, 2007, 09:18:00 PM »

Thanks caster...

I tend to take the hard line on knowledge sometimes to not confuse people.. but yes you are correct...

Pepsi_Man0077 · « **Reply #6 on:** April 07, 2007, 01:33:00 PM »

So yeah, i am kind of pissed. My kernal Autoupdated.... i have the 4552 kernal. But i would really like to see it be ran in the future even with this efuse. Does it look like that is ever going to be possible? Could i remove that resistor? and then if i tried to downgrade, the efuse couldnt blow? I really want to run linux on my xbox 360 in the near future, can anyone help?

The Prankster · « **Reply #7 on:** April 16, 2007, 09:00:00 PM »

The eFuse won't blow when you downgrade, only when you upgrade to 4552, I do believe that the eFuse allowed for the downgrading of kernels if a bad flash occured to the 16 mb NAND Flash and would fallback to the previous kernel. (If that's slightly incorrect do correct me.) If you updated to the 4552, you're out of luck, just like thousands of other xbox 360 owners including me, I don't really care though, never cared for linux, bought my 360 for games. And I have two 360's anyway.

The Prankster · « **Reply #8 on:** April 27, 2007, 09:25:00 AM »

Just wanted to also post some more info, wasn't satisfied with my last post. You already blew your efuse, no reversement here, out of luck, and also... YOU updated it. It did not 'autoupdate' as you claim, remember the little popup from the guide, that tells you there is an update? You did your part, and accepted willingly. If you knew your stuff, you wouldn't have started updating your 360 at all, because OBVIOUSLY this is how M$ fixes their bugs and hacks you bimbo. Don't blame M$, hopefully a cure to the hypervisor is possible in 4552 and the spring update coming soon too, you never know, M$ could have us on this one. Once again said in another post, but it IS possible to create a hack proof system, the odds are on our side though. (IMG:style_emoticons/default/cool.gif)

This post has been edited by The Prankster: Apr 27 2007, 04:28 PM

Author Topic: 4552 Update? (Read 105 times)