Wlakiz said:
Yes, I do owe you an apology, honestly, I did not look much into the Xbox 'homebrew' scene. I made a poor assumption, that Xbox's CPU key was as secured as the PS3 or PSP which prevents digital signing of code. In any case, I relooked into Xbox's exploits, and would like to question some of the claims that you made: "2. Lets say your 360 comes up with the xmas tree lights fault, this could be recovered potentially in the same manner by dumping the firmware and injecting your keyvault into a CFW which would allow you to then reflash back to stock if you wish. -> if you dump stock firmware then reflash you will fix nothing as you need to extract the key vault, decrypt it then fix the issue and reinject into stock firmware." "Xmas lights fault", which specific fault are you talking about? RROD? What are you doing in the CFW step to fix the issue before reflashing back to stock? "3. Lets say your 360 has a E71 error which is a firmware fault on occasions, CFW allows you to fix that too." Again, I am interested how does CFW fix this. According to http://forums.xbox-scene.com/index.php?showtopic=484726 (this site deals with modded xboxs) and their comment for E71 is : "E71: Dashboard Error - Error within Xam.xex: possibly a dashboard update error, Check below in the "Console Reset Codes" for instructions. If that does not work there is no other solution and the console must be sent back to MS for repair." "4. On the original Xbox if your HDD died the console was a brick for all intensive purposes. Guess what CFW would allow you to install another drive and lock it to the Xbox thus allowing it to function again." "1. Lets say for instance your 360 DVD drive board dies and you do not posess the drive key for it. You can do the JTAG hack or one of the earlier fixes if it is exploitable to retrieve the CPU key on that console and hence decrypt the key vault giving you the DVD key so you can put it into a new drive and it will work fine." Both above methods are detectable by M$ which would result a CPU key ban, which is might as well making your xbox a deadweight. "5. The Pandora hack on PSP's can recover some bricked PSP's that failed normal software updates. -> It is a hack" I guess accessing a built-in debug mode for reflashing is considered a hack these days. I personally consider it an exploitable feature on the PSP but that is my own definition.
|
2. The xmas tree light fault is a alternating red and green fault code which isn't standard and is generally related to a keyvault error for example incorrect region coding. By alternating red and green I mean the top two LED's in the quadrant will flash green and the bottom two will flash red, they will then switch so the top is red and the bottom green and flash in that order. It is not a RROD and doesn't return any secondary codes. I don't blame you for not having heard of it as its quite rare in most unmodded consoles but becoming more regular in hacked boxes where people screw up modifying the key vault.
3. E71 is indeed a dashboard error, I don't know why but on occasions I'm guessing bad blocks develop in the nand that were not present at manufacturing and so aren't flagged as they should be. If the bad block happens to fall in a essential dashboard file (which are obviously stored in the nand or an arcade couldn't work) then updating by normal means probably doesn't pickup the bad block and keeps writing data to it. If you manually read the nand using a spi flasher then you can identify where bad blocks occur and rebuild a new firmware image with the bad blocks remapped to other areas of the image so they will not be damaged when you write back to the nand. I would also add that E71 isn't always a software fault and a GPU reheat can resolve some of them, although they generally end up as RROD with a secondary 30022 code eventually.
4. If the xbox was online before you apply the softmod then it would be banned due to the marriage theory when reverted to stock. If it hadn't been online though and you swapped the HDD, you could quite happily game on it until they discontinued Live recently as they were unable to detect when you reverted to original firmware and whether the HDD was the original or not. You may actually be able to clone the identity of one HDD's serial number onto another to get past the marriage theory but I never needed to goto such lenghs personally. This would make the first half of my post redundant. Most people didn't clone though because they wanted to install bigger HDD's which wouldn't work with a cloned firmware installed.
1. No you're still wrong I'm afraid. You dump your original firmware using a flasher. You build a image, you write it back. You apply the JTAG hack. You get your CPU key. You use a flashtool combined with your CPU key and original nand dump to extract your dvd key. You use one of the DVD firmware flashing programs to write back a stock firmware image with your DVD key. You then write back your original firmware dump and remove the JTAG hack. The console is now back in its original factory state and is not detectable as having been modded. I know this for a fact because I have done it.
5. Semantics, either way we both see its merits for fixing faults surely. For instance it allows you to replace the wifi board in a PSP that wouldn't be possible otherwise.
