I had lightning. We must be different elements.I just ran it and smoke started bellowing out of my ass.
I had lightning. We must be different elements.I just ran it and smoke started bellowing out of my ass.
You sure you didn't attempt "asshax"?I just ran it and smoke started bellowing out of my ass.
OHHHHYou sure you didn't attempt "asshax"?
the hash isn't the same
I'm going to the future guys. Peace.
Well, this could be a tool that was completed before 33c3... it's very unstable, so derrek and other ppl tried to find another way to do this (?)I don't know about this theory. I am talking about the method that was used in the presentation in 33C3... Which this tool is claimed to be based on.
We're not sure yet, it could bei'm confused, is this a joke or not?
Why wouldn't they of made it say press B to Exit Main menu. That what is in the beginning
I'm going to the future guys. Peace.
the hash isn't the same
https://twitter.com/derrekr6/status/744693728292540416
--------------------- MERGED ---------------------------
What Derek posted was a SHA1 hash not the key
Well, this could be a tool that was completed before 33c3... it's very unstable, so derrek and other ppl tried to find another way to do this (?)
Anyone have the boot1.bin to test the key?
Thanks. I won't be able to dump my NAND today. Hoping someone else could work with @EclipseSin to test if the key he got is legit.Dump your SLC, boot1 is at 0x200-0xE200
where is that if i'm looking at hexfile ? how does that equatDump your SLC, boot1 is at 0x200-0xE200
All?Editing and redumping your SLC with changed boot1.
What possibly could go wrong?
Probably.All?
Oh so that's what you meant.Testing the key means trying to decrypt it...
You can't change boot1 anyway, even with the key, because it is signed.
And what does it mean where is it? It starts at offset 0x200, and its length (at least for me) is 0xe000 bytes...
good thing i didn't ran it.This turned all my icons into reggie