022-2402 (3DS/2DS)
Support code detected, press to expand information
1 messages · Page 1 of 1 (latest)
Support code detected, press to expand information
Open friends list, and see if you get an error there
If the above steps don't work, then yes, make it on the website
Note that some settings will be inaccurate and cannot be changed without a modded Wii U
No, it shouldn't do any harm
In the second step nnid, do we try to do the log in process with our pretendo accounts?
In the 2nd step, just exit out and go to step 3
Hey @neon fable I just can’t get it to connect. Did all the steps, I even did the language one where you change it to Spanish, French, and even Portuguese. Do you think I’m better off doing a hard reset?
Do you get an error in the friends list app?
002-0101
Support code detected, press to expand information
Unless the servers have been busy for a whole week. I’m stuck
It's unknown what causes this error, and currently a fix isn't known either unfortunately
Would a system reset be best?
Don't
it won't help
@hidden mist another case
It's the same person as last time I think
Either way he is interested in looking at this specific error code
So every time I see the error until he responds I will ping him
@solemn gust Ok thanks all! One more question, my system boot is 11.5.0-38. Do I need to update my 3ds system? I heard rumor while back that Nintendo did a patch to ban modded 3ds systems. Could that be the issue why I can’t connect?
That rumor was never true
You can update it just fine
Yes
I can’t update it now…
Switch to Nintendo Network to update
Did both after Nintendo wouldn’t.
Error code please
No code just quote “an error has occurred. Unable to update. The system will now be restarted”
Do you know if a SOAP transfer is needed here?
no wait nvm
confused with another user
Is your 3DS region changed?
I bought it from Asia. But it looks like it was transferred to the u.s. region. wouldn’t Luna3ds remove region restrictions tho?
Modded 3DS consoles are region free, but here i am talking about the firmware region
11.5 is a common version for CTRNAND transfers so, lets do something
What's the second letter of your serial?
Ohh I see. 11.5.0-38U
That's the version, not the serial
Look at the back of the console
Would a picture help or is that against rules
Yeah, a picture would be fine, although we only need the letters
In fact, I wouldn't actually give oht the full serial
just tell the second letter
From that we can know the original region of your console
Also i noticed you help people in NH, is a SOAP transfer needed for system updates or no?
The serial is inside the lib of the console, but dont send the full serial, just tell me the second letter of your serial
Also nice console
They did a good job refurbish quite impressed myself
It should be after the first N
If it's NJ, Japanese
NE should be Europe
NW should be an USA console
you might want a case on it too
Well crazy but. I don’t see one, im gonna unscrew it and see if it’s under the console
Dont unscrew
You can also see the serial on gm9
the serial number is here btw
just tell the first two letters
Yeah that’s where I opened but it looked like the seller ripped it off
okay there is another way
Godsmode opened create essential files?
open godmode9
press home
go to more...
and you should find system info or smth
And tell the first two letters of the serial
Japan
I largely help with Pretendo related issues there, and a bit with other things
I asked someone else there, and they said a SOAP transfer isn't needed to update
Region is Japan
Very nice ^^ do you find others helping with Pretendo questions too?
And, have you ever found someone with a banned error code?
You guys are great help btw
Usually just 0121 (not a ban)
NH doesn't help with unbans at all anyways, but some might think it's a ban
well i think for pretendo you can tell them to join this server and appeal it
Shouldnt be against the rules correct?
np, well i think you have to ask to discord.gg/nintendohomebrew for the update thing
@pale star 👋
@pale star can you check this file in godmode9?
SYSNAND CTRNAND -> rw -> sys -> SecureInfo_B (or it might be SecureInfo_A)
press A on that, show in hexeditor
towards the bottom, is there a serial number?
if so, send the 2 letters at the start (not the full SN)
Sorry I have to take a picture there too much letters and numbers for me to understand programming. Also I did see secureinfo_A (picture below) and C. But no B
gotcha.
that's the issue then
@solemn gust
what the???
Is SecureInfo_C the same?
Did a side by side check and c has a lonely star figure on the right
Fixable? Or better to just buy another?
Noticed just now
@pale star hey, hope you don't mind me asking; where did you get this console from? and do you have a file called essential.exefs?
(don't send the file here if you do, just tell me if you have it)
I got it from AliExpress. Shipped from china. Where would I find that?
can you show me what's in [S:] SYSNAND VIRTUAL?
This stuff be found in godmode?
yes
try this: select essential.exefs -> Mount as EXEFS image
in it, you should see files like frndseed, hwcal0, hwcal1, movable, nand_cid, nand_hdr, otp, and secinfo
Yup
@solemn gust would it be fine if this was taken over to Nintendo Homebrew? this might be a new trend that we want to investigate
Sure
this is actually the second console we've seen come in this state, also shipped from aliexpress
Are you a helper there?
yes, i'm part of crc, you could ask any of the staff there
Damn, I should’ve bought it from fb marketplace then..
oh nice ^^ well we promote this server so i am fine with it
Also would be cool posting the fix here
well we need to know what to do first
https://github.com/Preloading/Restore-LFCS_B/releases/tag/v1.2 Preloading made a script for the LFCS
and if you want a helper from NH, hi, that would be me, i'm also glad to say "what the hell this warrants further study"
so i assume a similar one might help
in any case... a private smallhelp channel will be made
Lol
Yes thank y’all for the support
(Hi, I'm also a helper)
What sub channel should I mention this to
last person who had it, we just grabbed the serial from 2:/sys/log/inspect.log (which was fortunate to even exist...) and made a simple secureinfo file with it
important note is that the user was simply trying to system transfer. dunno if something else was altered and/or if this will work with pretendo
I actually wonder how this issue actually happens
hold on just a moment
it's a deliberate erasing of SecureInfo_*
well it's more like why, since this is (hopefully) something that they have to do themselves
it's not filesystem corruption or anything
Necessary to use Pretendo, how fantastic, well good luck guys sorting this one out
necessary to use any online services
true
actually the only thing ctrcheck complained about is secureinfo. hopefully it's the exact same case for this console
Also, i think it's like the 5th or more user posting this error code on this server
that's not great
well... i think this is only the 4th case of an identity stripped console from a chinese seller i've seen so far ¯_(ツ)_/¯
fourth?
if you guys search 002-0101 you can find more
Support code detected, press to expand information
We had another one 2 weeks ago but we didnt know how to fix it, but shutterbug2000 wanted to investigate
Well today he found out it was because of that file
i don't think the original SecureInfo_* file can be restored
Also... have you guys ever found 002-0150?
Support code detected, press to expand information
that signature is simply gone without the rsa private key
#1289399563664359495 #1289611146239672492 #582166023902330880 message
and of course, this is 4th
Rip
So this console cant use Pretendo?
a quick search suggests 002-0150 is due to lfcs?
Support code detected, press to expand information
Yep
someone made a script
we are using this for supporting people with that error code
that's cool
Have you guys ever got people with this error code in NH
i think so, i just did a quick search for it
nice
not very often though
also since you guys don't assist with unbanning, 002-0121 is not a ban error code
Support code detected, press to expand information
no idea if everyone there realised yet
unlike lfcs, i don't think this file will be recoverable
but if you find people with error codes: 002-0102, 022-2802, 022-2812, 022-2814, 115-5007, 598-0010, 598-0011 they are all bans from Pretendo
Support code detected, press to expand information
that's not good at all
(wait wdym unlike lfcs)
This helped a lot of people
i'm curious about the 0.1% that it doesn't help
yea, you can look at the methods it uses
Also the fact Luma3DS backups the file helps a lot
That's also another huge factor why it works
The fix here ofc it's checking the SD card for Luma3DS files and settings
and if it doesnt work yet reinstalling Nimbus fixes the issue
hmm
Another common error code you might see on NH is 015-5015, which basically requires to link your PNID (can also happen you log out and you have to do it again)
Another tricky error is 022-5432, maybe more technical details why this actually happens can improve the advice, I think it happens when your NNID is loaded to PN, usually I tell people to open Nintendo Network and to open the eShop to reload the NNID on NN, then switch back to Pretendo and it should work after linking the PNID
The NNID in PN glitch usually happens after updating Luma3DS and not re-enabling the options (therefore no patches to make Pretendo work) or just disabling them on your own
I have seen cases of this happening randomly, but idk why outside of removing your SD card
I think that's it for now in case assistance with Pretendo error codes are needed there
A dev is asking me if you tried this https://github.com/joel16/3DS-Recovery-Tool/releases/tag/v1.40 -
@rustic sierra @sullen ore
i kinda forgot that existed, how exactly does it rebuild said data?
@humble mesa
- Dump original LocalFriendCodeSeed from data. (This is different from copying the seed from nand)
- Dump original SecureInfo from data. (This is different from copying the SecureInfo from nand)
- Restore LocalFriendCodeSeed and SecureInfo from memory.
Restore LocalFriendCodeSeed and SecureInfo from backup.
- Verify LocalFriendCodeSeed and SecureInfo.
- Wipe temporary titles, expired titles, TWL titles, pending titles, demo launch infos, config, parental controls and CTRNAND.
- Format (delete) SMDC root and NAND ext savedata.```
The readme says this
i wonder what "from memory" means
In the app it's restore original
i read the readme, but i'm still confused
this confuses me too
Apparently the 3ds bootrom has copies of si_a and lfcs_b?
I guess we're finding out
that would be the first i've heard of that
+1
On 3dbrew it's deleterestoresecureinfo or something
Basically, deletes the one on nand and replaces it with the one loaded from the bootrom
there's nothing to lose
@mellow egret 👋
idk what you're able to do with this, but on our side, all that we need is a serial number
the error comes from the outright lack of one (i was able to replicate it on my console by nulling the SN)
the secureinfo file being correct isn't a strict requirement
that's good to know
means the only real "loss" is the inability to remove custom firmware (which we don't recommend anyway)
actually wonder how many people ignored this advice and bricked the console
anyone who follows our guide wouldn't
right
idk if they're removing the stickers from the console too (if they're blanking secureinfo likely)
but if not that'd be a way to recover
it makes extra sure that the console would actually function on stock
the serial label is also gone
rip.
but, the serial number can be recovered from twln/sys/log/inspect.log
ah
yeah that'd work
btw just for fun i tried using secureinfo from n2dsxl to my 2ds, soft bricked it lol (i restored my file ofc so i am good)
hoping to replicate that error code, but i failed
i wonder if there's some other modification going on then?
just to make sure I’m looking at the right thing, this? https://www.3dbrew.org/wiki/CfgI:DeleteCreateNANDSecureInfo
cant we just ask luigo if its helpful, they reimplemented cfg
i sent a message
https://github.com/luigoalma/3ds_cfg/blob/db950e6f7ee6d344c444c73be0a056b9007062c8/source/cfg_service_nonnor.c#L362
"this call just saves what's in memory"
@subtle rune
so "restoresecureinfo" is misleading and the thing won't help, alright
@solemn gust too
@humble mesa (they told me about the tool)
i already saw
so that console is done for then if I understood correctly
unfortunate
That's why I never recommend people buying pre-modded consoles in the first place
not entirely, we can build a dummy secureinfo that contains the serial number and region byte
well pretendo doens't care about the secureinfo signature (supposedly?)
and inspect.log is intact
and hopefully the localfriendcodeseed is intact
so going off of that it should work out pretty fine (if you don't plan to remove cfw)
well from what shutterbug2000 said, as long as the serial number is in SecureInfo_*, Pretendo will accept it
yeah
we never see the signature there (afaik?)
i mean, Nintendo Network doesn't seem to care 👀
Ofc we care if you try to unban your console, which wont work here
that usually involves lfcs, not secureinfo
but it uses the lfcs for it
LFCS_* does 100% need a valid signature however, so if that's toasted then yeah the console ain't going online anymore
whats the serial, i can make a secureinfo rq
we've already done that
oh nevermind then
i tampered with the hash on my secureinfo_b just because i wanted to see what would happen if i tried anyways, but the app just crashes lol
cant even compile it if i want to because (for some reason) my msys2 instance cant find citro2d
Small clarification (also hi! fancy seeing you here, love your work btw!)
While it's true we do very basic SN checks on the server (we can't even validate if a SN is legitimate or not because, unlike the Wii U, the 3DS does not send the SN check digit), if this console has been online with our servers before then the serial number in SecureInfo_* must be the same serial number
We identify 3DS consoles in NASC using the fcdcert, and if we have not seen this console before we register it on our end using the data given at the time of that request, including the SN. On all subsequent requests as a sanity check (and as a way to combat trivial LFCS sharing, which was an issue in NN) we compare the SN being sent with the one already stored on our end, and reject requests if they don't match. Other than that the only thing the SN is used for on our end is identifying the 3DS model by just checking the first character
So, technically speaking, if this console has never been seen on our servers before you could, actually, just set this to whatever so long as it looks like a SN (people used to change their SNs on NN to bogus ones all the time as a ban bypass in the past, so we have no idea if any SN that hits us is ever legit. Doesn't really matter anyway since the SN is only really used for sanity checks). However if this console had connected to our servers in the past then you'd need to restore the original SN
Luckily, if the console has connected to us before then we have the SN. So long as the LFCS is still intact and legit we can look up the console details on our end
@slate anchor and I have been working on some updates to Nimbus to fix other parts the console (like updating the users PID HMAC, which normally can't be changed) by requesting new data from the server, so I wonder if this is something worth also looking into fixing through the same update? If the server has already seen this console then send back the serial and patch it? Doing so would sort of defeat the whole "we also sanity check to block trivial LFCS sharing", since now people who share a LFCS can just get the "correct" serial and bypass that block, but if this trend is getting worse like you said then it may be worth risking trivial LFCS sharing again to try and help fix this issue
thanks, i think that's interesting
the serial number is at least not lost, that's stored in twlnand, so we've already creatd a sig-less SecureInfo_A for them to use
Ah okay, my bad. I must have missed that (there's a lot of messages here and I kinda skimmed)
it's in twln/sys/log/inspect.log
since it's not in ctrnand, even a botched ctrtransfer (which these consoles could have?) wouldn't modify it at all
I see that there's a worry that this is being intentionally done by people trying to scrub these consoles of their identifiable information? If that's the case is there a worry that the people doing so would also eventually find this log file and scrub that to?
I'm wondering if it might be worth trying to automate this process of using the serial from the log file to fix the broken SecureInfo_*, but if there's a concern that this is being done intentionally I wonder if it might not be worth showing them where the info is also at?
I don't know yet if it was a deliberate attempt to scrub identifying information, for one thing we've only looked at secinfo and not LFCS or anything else
I would've thought this particular one was a region-changed console but... no, the SN starts with NW, which is for USA New 2DS XL
Yeah they told me the serial was a NJ
that person
wait, where did you see NJ?
wait....
this?
something's not adding up here...
Yea i assumed it was a region change but.... still didnt add up because people with region changed consoles are using Pretendo just fine
maybe product.log? that also has some info (such as the original factory firmware)
Even with no SOAP transfers
Also.... they were trying to update the console
but it failed
i'm pretty sure some of these were region-changed and had a "soap transfer"
They are suck on 11.5
I am assuming NH will already not recommend Aliexpress now
pretty sure anything might be attempted to reduce this issue ig
I don't know if we ever recommended aliexpress anyway
Also about the error codes, are you going to update the bot to refer to Pretendo?
also.... we might use unused banned error codes that exist
102-2822 this one for example
Support code detected, press to expand information
ok when are we removing the word piracy from the filter
we already had experiences with consoles sold from certain weird sellers that come with some so-called "stealth luma" version and also a bunch of games
(this message timed me out becaue i said a bad word apparently)
you got sniped by the strict block piracy filter
in any case, i would like to check product.log on that console now too...
we will remove it since it's just promoting to bypass it
Good idea
we can make a list then, 002-0150 is one of the custom ones
Support code detected, press to expand information
And also 002-0151 but no one got it yet
Support code detected, press to expand information
is there any sort of format for pretendo error codes? to separate them from nintendo network
This is LFCS_B anyways, dont see any cases that affects another file iirc
598
598-0010
Support code detected, press to expand information
there are usually dedicated prefixes to codes specific to pretendo
Support code detected, press to expand information
Martini is outdated anyways
All I know is that 0150 and 0151 are custom 3DS ones, and then the last section on this page
https://wiki.erdbeerbaerlp.de/pretendo:errors
We actually relicensed our error codes repo specifically for stuff like this (the NH bot was a driving factor in the decision tbh), it used to be much more restrictive but now it’s more lenient (though there’s an argument to be made tbh that the license wouldn’t have covered the error codes themselves, only the wrapper lib we ship with them, and since your bot is written in Python you wouldn’t need that wrapper anyway cuz it’s written in JS)
Also the ban error codes
i have not really touched kurisu's code in a long while
We are currently using 022-2812 for console bans
Support code detected, press to expand information
and 102-2812
Support code detected, press to expand information
Any 281X means it's a permanent console ban
2814 is used mistakely for PNID bans, we will change it to 2802
when does bandwidth (haha funny pun please laugh /s) get an update to check ban reasons on a linked pnid
2802 will be used for PNID bans globally
28x3, 28x4, 28x5 ofc depend from that Wii U error database
282X are temp PNID bans and 283X are temp console bans, they exist but never used by Nintendo, meant to be temporary bans
In most cases we don’t have a ton of control over the error codes. In cases like Miiverse we do since the app lets us display fully custom error codes, in which case we use T9 style prefixes. But in other cases we just use error codes Nintendo didn’t officially use and do our best lol
I figured that was the case
002-0121 definitely needs to be updated since most of the time it's just someone's patches not applying correctly (due to incorrect settings)
104-2210 should be an issue with boss shared data
Do people still think 0121 is a ban on NH?
i'm not sure, i've been a little too busy today to go looking
this is what our bot currently states
022-2402 has various causes with various fixes
When none of the files are broken, somehow it's fixed by going into NNID settings on NN, and then changing the language to Spanish and going back to Pretendo
which i think is more or less similar to your 002-0121, but that doesn't specify that it could be a ban
Support code detected, press to expand information
some day we'll have an error code redirector/server side api to fetch error codes from
some day
002-0110 is outdated (on Pretendo it's used if the game is unsupported or tester only, while on NN almost everything is gone)
Maybe it's worth having a Nintendo Network button for archival purposes
if some of these error codes have alternative fixes because custom servers
0110 means discontinued but can happen in different situations
@mellow egret
this is a joke ban i did
well i brought up the error codes thing with the most active kurisu developers
I should make a list then
apparently they talked about it before but the license was a possible issue, but if we're not using the JS wrapper then it's probably fine
i figured
about why GodMode9 may have reported "Japan"
unfortunately the bottom cover of the New 2DS XL does not seem to be significantly different per-region
i dug out my japanese one to check the bottom
if its actually japanese it would usually say ll instead of xl
For Wii U, replace 022 with 102 and 015 with 115
Custom modules:
377
598
678
377-0001 happens when you open eshop on wii u on pretendo
is this all in the error-codes repo?
Not all of them iirc
At least under Bandwidth
i cannot see that on the shell of the New 2DS XL/LL
whats the language the bottom shell is in?
mostly english
however, i know for a fact that this was sold as a used (but fully stock) New 2DS LL
i region-changed it myself
022-2613: this can happen if you attempt to make a pnid but affected by the nnid bug on pn when you dont have a nnid
Support code detected, press to expand information
Therefore incorrect credentials
wouldn't it be a good idea to put these into the repo?
We should make some PR to update the fixes ngl
whats the second letter on the serial number
starts with NJE
022-2571 if you make pnid the same as nnid
Support code detected, press to expand information
That's a JP serial
correct
also matches inspect.log and SecureInfo_B
but the bottom shell text looks the same as this NA model
i'm guessing nintendo cheaped out by not producing different New 2DS XL/LL shells for different regions
I own 4 New 2DS XLs europe
i mean, a lot of japan does speak some english anyways afaik, so im not entirely surprised they saved the hassle and just put an english shell
well, it's also that it does not say "New Nintendo 2DS LL/XL"
every other 3DS model does
no, probably not
i don't think they'd care that much
this is kinda scratched up, it was a used unit
the sticker looks intact
what sticker
Let me take a pic of my pokeball unit
oh lol
i thought you said they took it off
might be mixing something up though
i doubt that whoever sold this to me would have gone through that effort
i mean, i have no hard proof, it just seems super unlikely
about licenses: since the repo is AGPL-3 and Kurisu is Apache-2.0, i wonder how this would impact using error-codes as a submodule
I don't know if that means Kurisu would need to become compatible with AGPL-3.0, despite not using any of the JS code
mine does not have the Nintendo logo like that, and it doesn't look like it got scratched off or anything
The dev branch was changed to be LGPL because AGPL is too restrictive in this case. LGPL is better suited for your needs, the fact that you guys use Apache was why we changed to a less restrictive license
oh I did not see the dev branch.... 🙃
i have to make some PR to the error codes
yes, you probably should
It’s a relatively recent change, I’d have merged to master sooner but there’s some pending PRs I had intended to merge first. But they’re growing kinda stale tbh so I might just merge to master before merging those
Btw speaking of bandwidth
Do we need to get some commands like the one on NH?
for support
Tho most of the times are just error codes
Error Code: 002-0102 // NH SecureInfo_A thread
Error Code: 002-0101 // NH SecureInfo_A thread
Changed the title
Accidentally typed the ban code
Fwiw, this is something that'll break consoles restored with Lazarus3DS when the console is missing a SI_A (those use a CW0000000 fomat serial, maintaining console revision but zero'd serial), though it's unlikely that those will ever have a working LFCS but not a working SI_A.
in this particular case, LFCS looks fine (we got essential.exefs), but i don't know if it's the original or shared from another console
i wonder why nintendo didn't use otp for device auth, that can't be easily replaced
iirc they did start using it later?
well, in place of everything using lfcs
Yeah, they started using CTCert later (Ref: https://github.com/LumaTeam/Luma3DS/pull/1422)
If Pretendo bans could be handled by CTCert, that'd allow Laz'd consoles to be able to connect even with shared LFCS/SI_A
I’m gonna be so real with you I have no idea what Lazarus3DS even is so idk if that’s even something we should worry about
as far as I know, it's a tool that is supposed to "resurrect" any 3DS
even if all the console-unique files are gone, it can make it bootable again
It's unfortunately had to be used a number of times.
of course, without things like the original LFCS, Nintendo Network will never be happy about it
Well, that's the thing. It has a "valid" donor LFCS that was never actually banned?
I fully expected it to get banned because it was a random public one, but it hasn't as of yet so I don't see that changing.
The 3DS never sends the device certificate to NASC under normal circumstances. It’s been suggested internally that we update our patches to add it to NASC requests but it’s been shot down for a couple of reasons
NASC, the standard 3DS authentication server, only ever gets the signed LFCS
When the 3DS contacts the SOAP server or NNAS though it does send the device certificate, like the WiiU does (in fact it sends it in every request, when the WiiU only sends it in 1)
hmm
We do use the device certificate for bans on NNAS since we have access to it. The issue is NASC, which only gets the signed LFCS, so we use that for console bans in NASC
maybe pretendo can start issuing its own LFCS files in exchange for device otps
(i don't know if this is a good or bad idea)
It'd need Luma patches to make it a "good" idea, basically a clone of the SI_C patches
yes, i figured
with a luma patch it could start loading from like LocalFriendCodeSeed_C
That way stock would still boot due to the broken sig on LFCS_C
We didn’t even consider that ngl
it'd probably be neat
by the way, last night i worked on a tool to restore the overwritten secureinfo files, which i think is the main issue affecting these consoles
but this tool IS NOT READY, in fact i'm already aware of a way in which it's deficient
it basically reads the SN from inspect.log and puts it into a sig-less SecureInfo_A/B, along with the region byte (which is taken from SecureInfo_C if it exists)
Could you instead put text in the sig area essentially saying "this was restored by <link> on <date>"?
Just for future reference
I mean, Restored by https://github.com/ihaveamac/restore-overwritten-secureinfo on 2024-12-25 is only 85 bytes
also, it does an extremely basic check to prevent any random user from running this tool, which is checking if SecureInfo_A/B's serial starts with a null byte
i'll probably adjust this to check for a specific set of letters, so it avoid garbage "passing"
it took me like four hours to make it, and most of this time was spent on the interface
Since it's userland homebrew, why not just verify the sig?
because i don't know how to do that 👀
You'd have to do it in software using something like OpenSSL since sig patches would screw up the PXI sig commands.
i’ve never used openssl in C
I've had an overcomplicated idea for a patch thing that might make the idea viable
(Custom sysmodule to interface with assembly patches)
(I've also had this idea for upwards of 6-8 months now so who knows if its gonna happen lol)
are OTPs signed?
yes i'm pretty sure they are
i don't remember how exactly i did it but i remember verifying the CTCert signature using a public key
ah
yeah we could maybe use that somehow
and i'm pretty sure you can get the CTCert information in userland
the public key is somewhere in the bootrom
@mellow egret is CTCert what gets sent to the NNID endpoints?
(idk if you'll know that or not)
hm
i'm gonna guess that it's what's sent to the NNID server
if so, then we already have the pubkey
if you've never checked out cleaninty, you should
https://github.com/luigoalma/cleaninty/blob/d533a6264809d9fad64f4bb9ef6bf3754b38653f/src/cleaninty/ctr/constants.py#L204-L366 and forgive my messy constants extraction
but middle of that is recovering the public EC X and Y of the public key
both dev and retail
that signs the CTCert
cool stuff here
@shrewd sigil
hallo i was called
your expertise in regards to nintendo soap operations would probably be useful
in terms of using CTCert to identify consoles
this was the original idea
assuming something like a patch to load LocalFriendCodeSeed_C happens, it could work
CTCert on actual soap operations is only used on IAS registration and ticket download, going off what i recall right now
my 3ds_cfg is code ready to support that quickly
it's cfg that loads it?
i wonder if you could have it load the file from elsewhere 👀
would be, the exact same patch type
@hidden mist
secinfo and lfcs follow the same code base
only difference in some things but loading and saving is the same
cool
in any case, i looked at one of my old projects and i see i used AMNet to sign some data, then i could use a public key to verify it
but you'd be better at explaining this than me
https://github.com/luigoalma/3ds_cfg/blob/db950e6f7ee6d344c444c73be0a056b9007062c8/source/storage/secinfo.cpp#L104
i got code ready to load secinfo C if it exists in my implement with templates
https://github.com/luigoalma/3ds_cfg/blob/db950e6f7ee6d344c444c73be0a056b9007062c8/source/storage/lfcs.cpp#L102
i didnt apply that for lfcs but would be the same
regardless both follow the same logic code for read and save on actual cfg
patching actual cfg you'd just, swap _A and _B on paths to do _C if you want secinfo same type of patch with luma
also it's about 2am, gn
(yes, CTCert is the device certificate, which is sent to NNAS)
Support code detected, press to expand information