so in other words everbody should be watching for a patch like lv2.pkg or a update on a backup manger.
i'm like this idea because as long as we all stay off psn less likly to block us from playing backups of the new games they will be more focused on locking up their new firmwares than blocking copying discs.
Last edited by ddamyank; 02-18-2012 at 06:16 PMReason: Automerged Doublepost
I would like to clarify some things . First of all, this stuff (payloads) come from my few hours in working to reverse tb dongle. I have remarked that the dongle brick automatically if there are syscalls peek / poke (I bricked my dongle but i got a new one yesterday).
Yesterday, i created a cfw with peek/poke syscalls and some extra modification to bypass and prevent from suicide . It work fine ! Currently, these payloads lead to understand how Tb and Cobra work.
The important payload part lies in lv2 (memory) when TrueBlue is enabled. I am trying to reverse this part (but don't expect from me a cfw with cobra and true blue implemention).
Great work ,and you have a modified peek and poke working too , that is great. Glad to see someone with skills doing some real work on reversing these dongles. Keep it up and keep us posted! Shame about your dongles untimely suicide.
You probably talk about the lv1_wrapper of the Cobra/TB2 (hv call/kernel mode) under lv2 check the lv1 execution that will help you a lot, the Cobra/TB2 need to use this direction under 3.55 firmware, it can't patch on the fly the lv2 just like that.
i was wonder which syscall did you use for brick your dongle ? i know that cobra/tb2 rom chip (battery that destroy if you make electric things or try a some stuff on it) include a decryption table.
the decryption table is the most important part of the dongle, that allow you to have a useless dongle nice