Minecraft_Mod_DEV wrote FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!FAKE AND GAY!

I'm sorry but what exactly is fake and gay?

just buy stealth lol or wait untill "if" he ever releases it when xbox one is out

BlueYetiMicrophone wrote just buy stealth lol or wait untill "if" he ever releases it when xbox one is out

instead of buying day of stealth buy that much worth of lottery tickets then buy lifetime or pay for someone to get you online with your winnings simple

LOL the op is banned funnny

ImJtagModz wrote Lets Just all agree that you are all wrong and XBLS, Nickas, Jester, Dwack are right ;)

with out a doubt they usually are ,i do wonder why it is always the same people responding to questions about XBLS though? this seemingly unknowable XBLS.

If someone ever will make a new sort of XBLS just contact me. I will provide a free server that I bought for 8.000$.

vokal wrote

ImJtagModz wrote Lets Just all agree that you are all wrong and XBLS, Nickas, Jester, Dwack are right ;)

with out a doubt they usually are ,i do wonder why it is always the same people responding to questions about XBLS though? this seemingly unknowable XBLS.

Those would be people with a history of pulling it off on previous dashes, but when the new protection came along in dash 16202 they were not interested and/or did not release anything to my knowledge. I went by a completely unknown alias before creating the framework of XBLS, so it's not going to get you far to guess randomly.

TroPPicZ wrote

nickcas wrote

TroPPicZ wrote

XBLS_ wrote Fuselines are read directly from the HV, more than once, with checks against spoofing/patching.

Doesn't stop somebody from hooking HvxGetVersions to return a different CPU key.

Spoofing the cpu key in HV memory does not spoof the fuselines, so no.

Obviously not, but the way his xex reads the CPU key is by calling HvxGetVersions and reading 0x20 in the hv. Well it used to at least... maybe my xex is out of date.

I haven't looked at his xex in a while, but it sounds like they (or they used to) patched hvxGetVersions to peek hv memory, which really isn't the best way to peek/poke.

vokal wrote

ImJtagModz wrote Lets Just all agree that you are all wrong and XBLS, Nickas, Jester, Dwack are right ;)

with out a doubt they usually are ,i do wonder why it is always the same people responding to questions about XBLS though? this seemingly unknowable XBLS.

I'm just interested in LIVE stuff, and know a bit about it to answer these questions. No affiliation/interest in XBLS and his business.

nickcas wrote

TroPPicZ wrote

nickcas wrote

TroPPicZ wrote

XBLS_ wrote Fuselines are read directly from the HV, more than once, with checks against spoofing/patching.

Doesn't stop somebody from hooking HvxGetVersions to return a different CPU key.

Spoofing the cpu key in HV memory does not spoof the fuselines, so no.

Obviously not, but the way his xex reads the CPU key is by calling HvxGetVersions and reading 0x20 in the hv. Well it used to at least... maybe my xex is out of date.

I haven't looked at his xex in a while, but it sounds like they (or they used to) patched hvxGetVersions to peek hv memory, which really isn't the best way to peek/poke.

vokal wrote

ImJtagModz wrote Lets Just all agree that you are all wrong and XBLS, Nickas, Jester, Dwack are right ;)

with out a doubt they usually are ,i do wonder why it is always the same people responding to questions about XBLS though? this seemingly unknowable XBLS.

I'm just interested in LIVE stuff, and know a bit about it to answer these questions. No affiliation/interest in XBLS and his business.

They use the XeBuild system call(HvxGetVersion). It's available to every console running XeBuild.

Modes:
0/1 return 1
2/3 deal with TLB_RPN
4 is used to launch a payload
5 is peek/poke

SSJ4_Dwack wrote

nickcas wrote

TroPPicZ wrote

nickcas wrote

TroPPicZ wrote

XBLS_ wrote Fuselines are read directly from the HV, more than once, with checks against spoofing/patching.

Doesn't stop somebody from hooking HvxGetVersions to return a different CPU key.

Spoofing the cpu key in HV memory does not spoof the fuselines, so no.

Obviously not, but the way his xex reads the CPU key is by calling HvxGetVersions and reading 0x20 in the hv. Well it used to at least... maybe my xex is out of date.

I haven't looked at his xex in a while, but it sounds like they (or they used to) patched hvxGetVersions to peek hv memory, which really isn't the best way to peek/poke.

vokal wrote

ImJtagModz wrote Lets Just all agree that you are all wrong and XBLS, Nickas, Jester, Dwack are right ;)

with out a doubt they usually are ,i do wonder why it is always the same people responding to questions about XBLS though? this seemingly unknowable XBLS.

I'm just interested in LIVE stuff, and know a bit about it to answer these questions. No affiliation/interest in XBLS and his business.

They use the XeBuild system call(HvxGetVersion). It's available to every console running XeBuild.

Modes:
0/1 return 1
2/3 deal with TLB_RPN
4 is used to launch a payload
5 is peek/poke

Tehee i remember when you sent me the thing to Get CPUKey using that. it came in quite handy ;)