View Full Version : New firmware for liteon soon
cunny
17th November, 2009, 11:36 PM
Just come accross this post and thought would shave. It seems that c4eva has found out how m$ are detecting drives.
pastebin - c4eva CONFIRMS F/W IS DETECTABLE - post number 1674784 (http://pastebin.ca/1674784)
Firmware was due for tomo 18/11/09 but could be delayed due to ban wave breakthrough.
Thats again only going off what i have just read.
Bulld0g
17th November, 2009, 11:40 PM
Just come accross this post and thought would shave.
Its the info that counts m8. I don't mind if you come in with a full beard, no real need to shave :roflmao:
Sorry couldn't resist that one lol
chroma
18th November, 2009, 12:22 AM
Something smells heavily like horseshit.
I dont know anyone who would withold information regarding how boxes get banned, if i knew for certain id post instantly to let other people know asap.
He doesnt appear to have done this, and still flat out deny's his original firmware was detectable, instead blaming it on bad burns and abgx...
Somethings not quite right.
johnboy1974
18th November, 2009, 12:16 PM
whether the firmware was detectable or not we all owe these guys a huge thanks. if ms have now found ways to detect it then im sure these guys will get around it. if you have found your xbox banned from live and need to buy a new one then just think of the money you have saved these past 2-3 years and you are still quids in.
micpuk
18th November, 2009, 12:17 PM
Something smells heavily like horseshit.
I dont know anyone who would withold information regarding how boxes get banned, if i knew for certain id post instantly to let other people know asap.
He doesnt appear to have done this, and still flat out deny's his original firmware was detectable, instead blaming it on bad burns and abgx...
Somethings not quite right.
If he posts how though then it's freely available for MS to see and release a patch for it straight away which then again puts him back to square one and us back to the same situation.
If he doesn't then they have to download and de-code the firmware themselves and see what he's does; thus buying us time?
on_the_jazz
18th November, 2009, 05:05 PM
If he posts how though then it's freely available for MS to see and release a patch for it straight away which then again puts him back to square one and us back to the same situation.
If he doesn't then they have to download and de-code the firmware themselves and see what he's does; thus buying us time?
I'm pretty sure microsoft already know how they are detecting firmware :D
cgscott
18th November, 2009, 05:22 PM
If he posts how though then it's freely available for MS to see and release a patch for it straight away which then again puts him back to square one and us back to the same situation.
If he doesn't then they have to download and de-code the firmware themselves and see what he's does; thus buying us time?
If its man made man can break it.
Although this may take some time for microsoft to do as he is writing the code for it.
This means he is the only one who knows how its done.
Which means someone will have to hack it again and devise a way to read it.
chroma
18th November, 2009, 05:49 PM
If he posts how though then it's freely available for MS to see and release a patch for it straight away which then again puts him back to square one and us back to the same situation.
If he doesn't then they have to download and de-code the firmware themselves and see what he's does; thus buying us time?
Microsoft got their startup from essentialy reverse engineering other peoples products, its their bread and butter. As far back as approaching IBM with a ficticious operating system to the release of Windows 1.0. the only original code from microsoft that i can find was the BASIC interpreter on the Altaire.
As soon as an exploit is released within a few hours its already stripped to bits and largely understood, especialy with something as trivial and straightforward as low level firmware.
Im not suggesting he posts the source (i can obtain this easily enough in the same way as microsoft does)
By stonewalling the release of detection methods hes buying up no more than a few hours of time, 12 at most.
The time taken to patch isnt in the actual coding its in the testing and deployment phases. posting the detection methods wouldnt cut down either of these timescales.
The only reasons i can see for witholding information from the wider community is that its either speculative guesswork or wildly inaccurate fiction.
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.