Print

[krizalid]

Has anyone tried this on the Xbox installed games on HDD (the one's you rip from game disc)??

I wonder if playing games from HDD without the need of disc is possible yet?

This post has been edited by krizalid: Dec 4 2009, 09:26 PM

[signal-to-noise-ratio]

QUOTE(Martinchris23 @ Dec 4 2009, 08:47 AM)

Removal of R6T3 does NOT prevent the CB from being updated. It's this which causes the XeLL to stop functioning.

But this would http://www.xbox-scen...ZpuCOUujZej.php

Prevent HDD Crippling - NAND write protect diagram

Run the nand write protected unless updating xell seems would be the way to go.

That and removing rt63 after xell is installed to protect efuses.

[evlspcmk]

quick question, im on 7371 xenon if i update to the hacked 8955 kernel will the xbox be able to play all the latest games? or should i buy another xbox and leave this one for homebrew?

[ccfman2004]

QUOTE(evlspcmk @ Dec 4 2009, 10:27 PM)

quick question, im on 7371 xenon if i update to the hacked 8955 kernel will the xbox be able to play all the latest games? or should i buy another xbox and leave this one for homebrew?

That is the whole point of having the hacked 8955.  The xbox you do the hack on will never see LIVE ever again.

[torne]

QUOTE(modslave @ Dec 4 2009, 05:14 PM)

So on a recovered banned console it would be advisable only to do the Nand protect, to enable dash upgrade when needed without screwing secdata.
But for exploitable consoles you should do both the Nand AND remove R6T3?
(Of coarse using a toggle switch so nand is not protected all the time)

No, you should *not* write protect the NAND on a box that is connected to Live and gets updated! This is dangerous misinformation I'm afraid. If you leave R6T3 in place but write protect the NAND, then you risk bricking the console: CB updates first blow an efuse, and *then* reflash the NAND, so it will disable your current CB version and then fail to install the new one, leaving you with a box that doesn't boot at all and must be manually recovered by rebuilding a new NAND image for it (this seems to be *very difficult* for current kernels).

There is no sensible way to protect an xbox that keeps connecting to live and updating from being crippled. The best you can do is to take a backup of the NAND to use to uncripple it, and then after each update back up the NAND again. If you get banned, you can use the most recent backup to uncripple the xbox without any messing around with having to find an old copy of secdata.bin, as long as your backup is the same version of the kernel/dash as the one currently on the box.

If you have an exploitable console there is no real need to write protect the NAND, but you can if you want. Removing R6T3 is sufficient to stop updates, because the first thing the update does is try to blow the CB lockdown efuse and if that fails it will stop with an error. Even if something *does* write to the NAND you always have the ability to reflash it from a backup.

[Morning Call]

anyone else having issues with the game being corrupted after transfering to the console?

the game shows for a split second under the games tab then dissapears.

This post has been edited by Morning Call: Dec 5 2009, 01:22 AM

[Surazal]

QUOTE(Morning Call @ Dec 4 2009, 07:21 PM)

anyone else having issues with the game being corrupted after transfering to the console?

the game shows for a split second under the games tab then dissapears.

Do you have an exploitable 360 running either freeboot or xbrebooter?

If you answered no, then you have found the problem.  This does not bypass the security on the 360.  The signature and security checks must be bypassed for this to work and that is only done by running a modified kernel such as the ones found in freeboot or xbreboot.

[No_Name]

QUOTE(Surazal @ Dec 4 2009, 04:27 PM)

Do you have an exploitable 360 running either freeboot or xbrebooter?

If you answered no, then you have found the problem.  This does not bypass the security on the 360.  The signature and security checks must be bypassed for this to work and that is only done by running a modified kernel such as the ones found in freeboot or xbreboot.

Actually to be able to use those you need to already made the modifications to be able to run XELL using the JTAG hack.
Thats step 1 everything else comes after that.

[tbb033]

QUOTE(condorstrike @ Dec 4 2009, 12:19 AM)

it's on!!!!!!

Like Donkey Kong! No, wait, that's Nintendo....


It's on, like uh... that guy from Halo! Yeah, that's the ticket.  (IMG:style_emoticons/default/jester.gif)


This is cool news, anyway.

[rawdog805]

darn so this wont work on my 8955 console huh??

[jester]

QUOTE(rawdog805 @ Dec 4 2009, 09:31 PM)

darn so this wont work on my 8955 console huh??

.. No.

[Jebuzz]

So, theoretically, couldnt you download arcade game demos then mod the xbox and now you have all those games for free and in full?

[jester]

QUOTE(Jebuzz @ Dec 5 2009, 01:55 AM)

So, theoretically, couldnt you download arcade game demos then mod the xbox and now you have all those games for free and in full?

Yeah.

[Vejita]

QUOTE(Jebuzz @ Dec 5 2009, 06:55 AM)

So, theoretically, couldnt you download arcade game demos then mod the xbox and now you have all those games for free and in full?

Yes, theoretically, scene groups may start releasing Xbox Arcade games en masse, much like the rampant piracy of PSN minis on PSP and WiiWare games on Wii.

'tis sad

[uberd0gg]

QUOTE(Jebuzz @ Dec 5 2009, 06:55 AM)

So, theoretically, couldnt you download arcade game demos then mod the xbox and now you have all those games for free and in full?

If you mean download via xbox Live first then mod that same console, no, because as soon as you go online to download the demos you would be prompted to update (thereby ruining your ability to JTAG the xbox).

But you could download the demos to an updated xbox, hack them, then put them on your modded console's HDD.