| QUOTE (Psilocybe @ Jun 4 2004, 06:51 PM) |
| you need a real dev or debug kit, not a retail with a debug bios (unless you do a ram upgrade and make it a debug box) |
the RAM has nothing to do with it, the "Hack-devkit Bios" is signed with the debug key, and only boots on dev & debug kits.
ram upgrade and debug bios therefore creating a debug kit (along with the xdk launcher and such also)
it will still not boot a *true* debug bios - ones which bootloader is signed with the "debug rc4 key", that is the reason this bios will not boot on a retail system, nothing at all to do with the RAM or dash on the hard drive. There is a seperate MCPX revision for those systems..
| QUOTE (Psilocybe @ Jun 5 2004, 10:25 AM) |
| ram upgrade and debug bios therefore creating a debug kit (along with the xdk launcher and such also) |
Dev Kit...
Ram Upgrade... Yes
Debug Bios.. Yes
RC4Key... Debug
Retail Kit converted to Debug....
Ram Upgrade..Not needed
Debug Bios... Needed
RC4Key... RETAIL
So why can you normally not load a debug bios on a retail box, cause its signed with the dev key, not retail.
Same applies for a retail bios on a dev box.
Solution for running modded bios on dev box, resign the bios with the dev key !
Ram, xdk, xshell, none of that matters if it will boot or not. Its the key. Literally the key is the key.
Oh, Also....
This is nothing new what yoshi has done.
With the proper tools one can re-key a bios to boot on the debug as BFM.
alright sorry for my misunderstandings
though i did think that the rc4 debug key was known or available (mcpx11.exe maybe?)
anyway sorry
Yes the key is known, and available.
Just a little bit hard to find, unless you know where to look.
keys aren't hard to find anymore, people arent uptight as they once were when they were first being found by those on xboxhacker.net
they are all over now