This means that if you have an older firmware version, the glitch may not work. Because it uses a different hacking method.
Why could old set-top boxes of a certain version be flashed, but not with a new firmware version? Because!
Its wired up the same way a hwfly/sx is wired up except I've ran manual wires instead of the flex... I've attached a photo for reference but this is purely setup for testing at the minute
Attachments
he had created account just before posting, thats probably somebody else from this threat.
Boot encryption key missingnot sure it'll work but try running lockpick_rcm
Post automatically merged:
@Adran_Marit any ideas? you seem to be pretty knowledgeable about this stuff
So we are getting rcm, hekate boots, but it is failing to boot HOS. The bek is either missing or the wrong key for FW.
Possibly try lockpick RCM first via hekate, if not then the bek might be hard coded in the picofly code? (this is just speculation)
Yeah I'm tech minded but not smart enough to do this XD, but once someone gets it going I can translate down for end users
Post automatically merged:
What pin on the flex is it wired to? I might have to break out my lite after work and do some testing
lockpick rcm doesnt load at all.Boot encryption key missing
So we are getting rcm, hekate boots, but it is failing to boot HOS. The bek is either missing or the wrong key for FW.
Possibly try lockpick RCM first via hekate, if not then the bek might be hard coded in the picofly code? (this is just speculation)
Yeah I'm tech minded but not smart enough to do this XD, but once someone gets it going I can translate down for end users
Post automatically merged:
What pin on the flex is it wired to? I might have to break out my lite after work and do some testing
and its wired to both sp1 and sp2, its bridged on the flex.
the original photo on page 1 is setup the same way hence why i did it this way aswell.
let me see what happens give me a minute
Post automatically merged:
doesn't load HOS either bud, same problem
yours does load lockpick....which then black screens and doesnt do anything
Post automatically merged:
dont know if this is useful for anyone here, but i managed to dump the sdloader using hwfly toolbox....it wouldnt let me dump the firmware obvs.
Last edited by Tafty,
if it wont load stock hekate and stock atmosphere then it isnt going to load any of these.
i tested it anyway and same thing missing BEK. we wont magically get it working with a payload at this point.
Then how do we usually get the BEK? Is it something HWFLY / SX Core do too before booting the payload?
Or is it that this firmware somehow writes an old payload to BOOT0?
What happened if you restore a boot0 image from a Hwfly and try too boot Atmosphere?
wont let you fails, and trying to overwrite the sdloader loader with the hwfly one DOES work, but after reboot the switch fails to to glitch.
Similar threads
- No one is chatting at the moment.
