Editing Talk:ReDRM / Piracy dongles

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
== another clone? -> FAKE! ==
== another clone? -> FAKE! ==
<div style="float:right">[[File:Infinitydongle.jpg|210px|thumb|right|Infinity dongle]]</div>
http://www.jb-infinity.com/infinity_usb/
http://www.jb-infinity.com/infinity_usb/
[[:File:Infinitydongle.jpg]]


This clone turned to be '''fake''' and Matrix team was not involved.<br />
This clone turned to be '''fake''' and Matrix team was not involved.<br />
Line 472: Line 473:
Fake proof:
Fake proof:
# Though the 2.3 payload upon execution does relocate itself to 0x80000000007f0000 then continue execution, the USB descriptor is still present, at minimum those 0x20 bytes would need to be removed, or accounted for during the initial execute.  multiMan has no facility for this.
# Though the 2.3 payload upon execution does relocate itself to 0x80000000007f0000 then continue execution, the USB descriptor is still present, at minimum those 0x20 bytes would need to be removed, or accounted for during the initial execute.  multiMan has no facility for this.
# The initial EBOOT.BIN.elf does contain the 2MB flash contents for the dongle, BUT that would need to be carefully extracted (and has been, it too is available on the psdevwiki), again multiMan has no facility for this.
# The initial EBOOT.BIN.elf does contain the 2MB flash contents for the dongle, BUT that would need to be carefully extracted (and has been, it too is available on the ps3devwiki), again multiMan has no facility for this.
# The creating of the folder and copying the files into it was just to make this fake seem more real with additional steps.  multiMan has no code to ever look inside that directory.
# The creating of the folder and copying the files into it was just to make this fake seem more real with additional steps.  multiMan has no code to ever look inside that directory.
# The fact of the matter is that the source code for multiMan was available, and there is NO provisioning in multiMan for "additional" payloads of any kind, the values possible in the .ini file are hard-coded.  It is well documented what payloads work with multiMan, and multiMan will only work with those payloads.
# The fact of the matter is that the source code for multiMan was available, and there is NO provisioning in multiMan for "additional" payloads of any kind, the values possible in the .ini file are hard-coded.  It is well documented what payloads work with multiMan, and multiMan will only work with those payloads.
Please note that all contributions to PS3 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS3 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)

Templates used on this page: