By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Wlakiz on 26 April 2010
Edit Thread
slowmo said:
Wlakiz said:
slowmo said:
 

I'll answer the bolded, the rest has zero to do with retail law and is a terrible analogy. 

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.

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.

3.  Lets say your 360 has a E71 error which is a firmware fault on occasions, CFW allows you to fix that too.

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.

5.  The Pandora hack on PSP's can recover some bricked PSP's that failed normal software updates.

I'll not continue much further but I think I've just proved my point you know very little on the subject of CFW and hacking.  Perhaps you should follow your own advice and start reading yourself before attempting to "educate" others.

 

1. So... the issue is that the DVD board is broken and to replace it you need a signed DVD drive? How does the CFW help you even get the CPU key to sign the DVD? The answer: it doesn't. CFW won't say: OH PLEASE INSERT NEW DVD DRIVE AND I WILL SIGN IT FOR YOU!!111 Instead, it will circumvent the signing requirement. Which means you can never use the stock FW ever again.

2. Or you can dump the firmware and reflash it with a stock firmware... no CFW is required

3. there is a E71 error and reflashing to stock firmware will fix it.. (assuming FW is the problem) :-p

4. Again, if you use CFW, to circumvent the signing process, then you can never use stock fw ever again. If hackers stop supporting CFW, updating back to original will brick your console.

5. Pandora hack is not a hack.. it is modifying your own battery to activate debug mode. Nothing to do with CFW.

You didn't prove that CFW can fix hardware faults, you just showed that they can be used to replace parts on your own- something that M$ would do for you without CFW. CFW can't fix produciton defects and there are more chance bricking through installing CFW  than installing OFW.

1.  Look up JTAG hack, research Xell, come back and apologise because you don't know anything about it and are wrong.

2.  No 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.

3.  No reflashing with a update HDD doesn't always fix the issue and neither does a reheat, you obviously haven't fixed that many 360's, I've done thousands.

4.  No you're wrong AGAIN, you could lock a HDD then revert back to stock firmware.

5.  It is a hack

I did just prove it can be used to fix faults, you're in denial because I've just shown your knowledge to be at best severely limited.  You got owned just admit it and walk away, being in denial doesn't make you any more credible.

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.