No, because you'd be breaking the signature.
If we could modify kernels/updates, we wouldn't need to use an exploit to run them.

Why would MS remove a security feature they added before? Especially considering the Slim is not much different hardware-wise, there's no reason to use a completely different kernel and bootloader.

Yes, I have a comment about that wiring. But I can't write that in public.

Make sure you have no USB device plugged in that contains a default.xex.

Some years back, people went nuts with a knife and carved random people up.
Now, we have the dremel.

Again, make sure the default.xex is not on the stick, otherwise that's exactly what you get.

That's cause you have to use it as an update, not run the default.xex. You put just the $Systemupdate folder on an USB stick, pop it in, then turn on the console.

Edit again: Seems SI implemented those ads. They show up on my XP machine too.

I have. The avatars install fine (of course assuming you have the 12611 freeboot version installed already).

I just disabled noscript in firefox, and I have no ads anywhere on this site.

I extracted the smc from an original dump using ibuild here and it worked fine.

If it comes up with the "put this game into an xbox360 console", you didn't insert your key properly.

You probably connected the wrong pins, or additional spots. Clean up the soldering and try again. If it boots up without the solder in place, you had messed up somewhere.

Avatar update works fine. You probably wrote the default.xex to your USB stick too.. ONLY copy the $Systemupdate folder. The default.xex is for updating from CD.

It's not just about "fitting" the pieces into the nand, but the memory addresses are also different. So even if you get the freeboot "pieces" to fit into the nand without overwriting anything important, it would patch the wrong addresses and crash.

Did you just bridge the connection with a switch? Or did you also use the resistor?

I believe the xell slot is no longer in the same position as with XBR, so updating with flash360 messed it up. You'll have to reflash the nand.

Then you are out of luck. The avatar files are not in a visible area, and I doubt you could use the kinect dash avatars, considering they were completely redone. Just get the official update.

For one, modchips can't do anything more or less than the firmware mods themselves can do. Second, there's not even a way to use a modchip on a Liteon drive, as all the data lines for the firmware storage are internal to the controller.

A jtag console doesn't do any drive checks, since it doesn't use the drive (usually).
You can't build a proper iso from files, since there's no way to create the padding.