Hacking Question Error "FFFFFFFF" when using Lockpick and printing TSEC keys

cloudfe · May 2, 2019

I'm using Atmosphere 0.8.9, on OFW 6.2.0, and FAT32 (with SX OS on the side).
I'll update the OFW to 8.0.1 as soon as SX OS comes out of beta.
No Emunand.

When trying to print the TSEC keys, I get " Found pkg1 ('20181107105733'). TSEC key: ERROR FFFFFFFF ".
When trying to use Lockpick, I get " ERROR FFFFFFFF dumping TSEC ".

It has been suggested in another thread this could be related to a boot0 issue, but I don't know what to think.

Additional info:
- my SD card should be ok (a Sandisk that never gave me a problem in the past nor the present), with plenty of free space;
- I always use the latest version of softwares (taken either from SDsetup or GitHub itself), including Hekate and Lockpick;
- Atmosphere seems to work fine for the rest, and also SX OS;
- I do have a Nand backup, but I hope it won't be needed.

I hope someone will be able to help, thank you

notimp · May 2, 2019

Try this:
https://gbatemp.net/threads/hekate-4-8-printing-keys-question.532815/

Maybe try launching the hekate payload a different way (sounds odd to me)(different payload launcher) - suggested in the thread.

Downgrading hekate sounds odd to me as well. (Try second). But hey - if it helped some folks...

edit: Make sure to use CTCers Hekate, I'm pretty positive, that there are a few other versions floating around as well..

https://github.com/CTCaer/hekate/releases This one is the 'main' one.

cloudfe · May 2, 2019

notimp said:
Try this:
https://gbatemp.net/threads/hekate-4-8-printing-keys-question.532815/

Maybe try launching the hekate payload a different way (sounds odd to me)(different payload launcher) - suggested in the thread.

Downgrading hekate sounds odd to me as well. (Try second). But hey - if it helped some folks...

edit: Make sure to use CTCers Hekate, I'm pretty positive, that there are a few other versions floating around as well..
https://github.com/CTCaer/hekate/releases This one is the 'main' one.

Do you think this problem may be related to the OFW version? I keep seeing 6.x.x when looking for solutions on this.

Hayato213 · May 2, 2019

You using lockpick or lockpick-RCM?

chippy · May 2, 2019

The issue is that your chain loading the lockpick payload throu sx os payload. Just push the lockpick payload not the sx os one as only the first payload gets access to tsec bug/flaw/issue
Its listed in the lockpick thread as someone yesterday or the day before hassle the same issue and was fixed by passing the payload NOT chain loading

cloudfe · May 2, 2019

Hayato213 said:
You using lockpick or lockpick-RCM?

I'm pretty sure it's Lockpick (it was the one with the lockpick icon).

While checking on GitHub, I see that for Lockpick-RCM there is a version with my exact firmware in the description. Could this be related to my issue?

Hayato213 · May 2, 2019

cloudfe said:
I'm pretty sure it's Lockpick (it was the one with the lockpick icon).

While checking on GitHub, I see that for Lockpick-RCM there is a version with my exact firmware in the description. Could this be related to my issue?

You have to load Lockpick-RCM from RCM directly to get your keys not through SX OS chainloading if you are doing that as suggested above.

cloudfe · May 2, 2019

Hayato213 said:
You have to load Lockpick-RCM from RCM directly to get your keys not through SX OS chainloading if you are doing that as suggested above.

N00b question: when you say "chainloading", you mean the SX OS dongle? Does this mean I should use TegraRcmGUI to load the Lockpick-RCM payload?

Hayato213 · May 2, 2019

cloudfe said:
N00b question: when you say "chainloading", you mean the SX OS dongle? Does this mean I should use TegraRcmGUI to load the Lockpick-RCM payload?

You can either load it from Hekate or load it directly not through sx os.

KnightMars · May 2, 2019

Make sure you're using the latest Hekate & Lockpick

cloudfe · May 2, 2019

Hayato213 said:
You can either load it from Hekate or load it directly not through sx os.

I can try that for Lockpick. But what about the TSEC error? I've always used Hekate (latest version) for that, and it gives me the same error (at least it looks the same - FFFFFFFFF) that Lockpick gives.

Also, if/when I'll update to 8.0.1, should I still be using Lockpick-RCM? Or the "normal" one should be ok?

Hayato213 · May 2, 2019

cloudfe said:
I can try that for Lockpick. But what about the TSEC error? I've always used Hekate (latest version) for that, and it gives me the same error (at least it looks the same - FFFFFFFFF) that Lockpick gives.

Also, if/when I'll update to 8.0.1, should I still be using Lockpick-RCM? Or the "normal" one should be ok?

Try loading lockpick-RCM.bin

cloudfe · May 2, 2019

Hayato213 said:
Try loading lockpick-RCM.bin

Sorry, this suggestion is referred to what part of the question?

Hayato213 · May 2, 2019

cloudfe said:
Sorry, this suggestion is referred to what part of the question?

Lockpick-RCM is only used to get the keys, Hekate is a bootloader, that you can use to Load Lockpick-RCM.bin.

cloudfe · May 2, 2019

Hayato213 said:
Lockpick-RCM is only used to get the keys, Hekate is a bootloader, that you can use to Load Lockpick-RCM.bin.

Yes, this I understand.
What I was asking is:
1) should I keep using the RCM version even after updating to 8.0.1?
2) what about the TSEC error (which looks remarkably similar to the Lockpick error)? I've always used Hekate for that, and so the SX OS chainloading should not be part of the faulty equation.

Hayato213 · May 2, 2019

cloudfe said:
Yes, this I understand.
What I was asking is:
1) should I keep using the RCM version even after updating to 8.0.1?
2) what about the TSEC error (which looks remarkably similar to the Lockpick error)? I've always used Hekate for that, and so the SX OS chainloading should not be part of the faulty equation.

Not sure about the second question, my SX OS one is using key from my other switch that is on 8.0.1 which used lockpick_RCM to get the keys, never ran into a TSEC error.

cloudfe · May 2, 2019

Hayato213 said:
Not sure about the second question, my SX OS one is using key from my other switch that is on 8.0.1 which used lockpick_RCM to get the keys, never ran into a TSEC error.

Then I'm not sure I understand the difference between the original Lockpick and RCM. Github's description mentions problems for the original with 7.0.0 and higher. Is then the original to be considered "outdated"?

Hayato213 · May 2, 2019

cloudfe said:
Then I'm not sure I understand the difference between the original Lockpick and RCM. Github's description mentions problems for the original with 7.0.0 and higher. Is then the original to be considered "outdated"?

Lockpick_RCM is for 7.0.0 and higher firmware.

Chocola · May 3, 2019

The firmware 7.x and newer need sept for tsec things, this is the reason because you need run lockpick from RCM and the hombrew app isn't work.

Trust on @Hayato213, he is fine.

Hacking Question Error "FFFFFFFF" when using Lockpick and printing TSEC keys

Well-Known Member

Well-Known Member

Well-Known Member

Newcomer

Well-Known Member

Well-Known Member

Newcomer

Well-Known Member

Newcomer

Well-Known Member

Well-Known Member

Newcomer

Well-Known Member

Newcomer

Well-Known Member

Newcomer

Well-Known Member

Newcomer

GBAtemp Meowgular

Similar threads

Popular threads in this forum