Samsung CERT File Edit or Generate as per Our IMEI

[Stunman112]

Originally Posted by Stunman112

Got a good idea on it but doesn't really matter. Id love full access without 3rd partying.

Sent from my SM-N920P using Tapatalk

"Its not about what you know, rather WHO you know"

Sent from my SM-N920P using Tapatalk

[does12]

sry to take u all back here, but that something alot of ppl are interested in, so am i.
i have some high end computer power.


i've seen a few services that creating certs for ppl.

so it seems that they are generating a new cert on the local pc of the cos.tum.er?

https://www.imeigurus.com/imei-repai...mei-repair-fix

Originally Posted by concepttheman

There are like 5 people in the US that has access. You may think you know but might be wrong.

this number as grown?

i do want to create my own cert.

and own imei number, in other its called vanity, u can create a vanity address within couple of days or weeks depending on ur hardware and address u required.
since i have an high end computing power i belive i can create my own certs but i need the algorithim \ program for it.

Originally Posted by Brka

There is no any secret, it's simple cryptography,
cert files are signed with PRIVATE keys, which only FACTORY HAVE.

You or anyone else don't have them, and CAN NOT create cert files without it.

Phone hardware check cert via public key decrypting, and if matches,
security is ok, imei ok, network ok, all ok.

b.r.
Alex

the thing is, we are not trying to crack a private key but creating a new pub and maybe private that could be use with the phones.

(if its not possible then how come seller like imeiguru and certcurt are selling and creating certs?)


this guy DARKMED ELECTRONICS is selling a tool that create certs.
how much would u trust him?

[concepttheman]

2048 RSA
Could take months and thats for 1 key ID. Lol

[Brka]

@does12

Nobody of mentioned people is generating certs.
All certs are from factory.

All "high-end" PC / mining farm / whatever is still not enough
for fast enough FACTORIZATION (not cracking) of ONE single RSA key.

That darkmed guy is probably scammer. (99% chance).

b.r.
Alex

[does12]

Originally Posted by Brka

@does12

Nobody of mentioned people is generating certs.
All certs are from factory.

All "high-end" PC / mining farm / whatever is still not enough
for fast enough FACTORIZATION (not cracking) of ONE single RSA key.

That darkmed guy is probably scammer. (99% chance).

b.r.
Alex

creating a pubkey and privkey takes seconds-minutes on a standart pc.
its the same factor as creating a cert of openvpn.

its 2048 bits.
cracking it however will take ages.
so how come imeiguru and curt cert can create imeis?
and can recover ur own imei ?

[Brka]

Originally Posted by does12

creating a pubkey and privkey takes seconds-minutes on a standart pc.
its the same factor as creating a cert of openvpn.

its 2048 bits.
cracking it however will take ages.
so how come imeiguru and curt cert can create imeis?
and can recover ur own imei ?

None of them have privkey, nor anyone can get it.

Yes, it takes seconds when you have it,
or it takes some short time to generate online,
with VALID level of Samsung GSPN access,
and that is what those guys have.
(And other guys which sells cert's).

b.r.
Alex

[Fast Unlocking]

Originally Posted by does12

creating a pubkey and privkey takes seconds-minutes on a standart pc.
its the same factor as creating a cert of openvpn.

its 2048 bits.
cracking it however will take ages.
so how come imeiguru and curt cert can create imeis?
and can recover ur own imei ?

because they simply have admin samsung access and have the admin tools to create it, nothing else

[does12]

Originally Posted by Brka

None of them have privkey, nor anyone can get it.

Yes, it takes seconds when you have it,
or it takes some short time to generate online,
with VALID level of Samsung GSPN access,
and that is what those guys have.
(And other guys which sells cert's).

b.r.
Alex

GSPN is equal to GSX ?

then why they claiming to create certs?

btw cpid can be writing with z3x? because imeigur claim that even if u have a cert u cannot flash it with octo or z3x because its cpid

[boubousat]

Originally Posted by does12

GSPN is equal to GSX ?

then why they claiming to create certs?

btw cpid can be writing with z3x? because imeigur claim that even if u have a cert u cannot flash it with octo or z3x because its cpid

you think they have !!!

[does12]

Originally Posted by boubousat

you think they have !!!

i dont think anything, i just mention what they claim to have.

[Stunman112]

Imeigurus made a cert for me as an example/proof a while back ago and they had their own application which is no longer on the market but they did it. It took 2 days I think and was totally custom (I gave key ID and custom imei)

Did they pay Sam for it? I don't know, I do know it was not an instant thing and basically is still mystery. Here is pic of custom imei STILL working today. Whatever they did do I give them props

-BR-

.:112:.

[does12]

thats still does not answer how its being done.

i am pretty sure samsung big as they are wont give or sale anything.

a cert have to be made some how.

first of all, whats required to create a cert.

SN?
device id?
baseband?
key id?

[genhack23]

Private key is the only solutions, If this company can do it is only for the samsung access, any imei can be put inside. The only ways is change the device pub key inside cpu and i think is burn inside (Like apple device) so no one can do it and no one can "Generate any other cert"... The only ways is study Arm and reverse the Boot of samsung device make a some sort Boot 0 days and disable any sort of signin.
@Victor The validifcation of the cert is inside the firmware like apple in the soc firmware. No one study the samsung Bootloader? I dont find any reserch about...

[gencom]

hello i recovered cert combination with file imei 0000000. how i does? combination file generating devices own cert posssible?

note: changed imei

[SherrySoft]

Hi folks,

I have got something interesting if anyone can go further with the data I have mentioned that would be great.

8a:fd:12:4e:96:b0:eb:70:7f:9e:39:f7:66:42:b1:
                    ab:ac:52:da:76:40:57:7b:2a:bd:e8:6e:03:b2:0b:
                    80:85:88:9d:0c:c7:c2:77:b0:9a:9a:57:f4:b8:fa:
                    13:5c:68:93:3a:67:a4:97:d0:1b:99:b7:86:32:4b:
                    60:d8:ce:ef:d0:0c:7f:95:9f:6f:87:4f:87:8a:8e:
                    5f:08:7c:aa:5b:fc:5a:be:a1:91:9f:55:7d:4e:b0:
                    0b:69:cc:b0:94:a8:a7:87:f2:d3:4a:50:dc:5f:72:
                    b0:16:75:1e:cb:b4:18:62:9a:b0:a7:39:aa:9b:9f:
                    66:d8:8d:a6:6c:96:15:e3:e6:f2:f8:f1:83:62:6c:
                    bb:55:e9:61:93:a3:3d:f5:b1:57:8b:4f:23:b0:9b:
                    e5:94:6a:2f:df:8c:df:95:51:29:60:a1:0b:29:e4:
                    5c:55:58:b7:a8:fc:99:ee:25:4d:4c:0e:b3:d3:4c:
                    8f:84:e8:29:0f:fd:10:54:02:85:c8:f9:e5:c3:8b:
                    cf:e7:0f
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Certificate Sign, CRL Sign
            X509v3 Policy Mappings: 
                2.16.756.1.83.2.1:2.16.756.1.83.2.1
            X509v3 Basic Constraints: critical
                CA:TRUE, pathlen:7
            X509v3 Subject Key Identifier: 
                4D:26:20:22:89:4B:D3:D5:A4:0A:A1:6F:DE:E2:12:81:C5:F1:3C:2E
            X509v3 Authority Key Identifier: 
                keyid:4D:26:20:22:89:4B:D3:D5:A4:0A:A1:6F:DE:E2:12:81:C5:F1:3C:2E

    Signature Algorithm: sha256WithRSAEncryption
         32:0a:b2:a4:1b:cb:7d:be:82:57:89:b9:6a:7f:f3:f4:c1:2e:
         11:7d:b8:19:3e:79:b7:a8:a8:72:37:66:9b:1a:ed:ac:13:3b:
         0e:bf:62:f0:9c:df:9e:7b:a1:53:48:0e:41:7a:ca:20:a7:17:
         1b:b6:78:ec:40:91:f3:42:ad:10:c3:5c:ef:ff:60:59:7f:cd:
         85:a3:8b:3d:48:1c:25:02:3c:67:7d:f5:32:e9:2f:30:e5:7d:
         a5:7a:38:d0:f3:66:2a:66:1e:8d:33:83:8a:6f:7c:6e:a8:5a:
         75:9a:b8:d7:da:58:48:44:47:a8:4c:fa:4c:49:0a:4a:c2:12:
         37:a8:40:0c:c3:c8:e1:d0:57:0d:97:32:95:c7:3a:9f:97:d3:
         57:f8:0b:de:e5:72:f3:a3:db:ff:b5:d8:59:b2:73:dd:4d:2a:
         71:b2:ba:49:f5:cb:1c:d5:f5:79:c8:99:b3:fc:c1:4c:74:e3:
         b4:bd:29:37:15:04:28:1e:de:45:46:70:ec:af:ba:78:0e:8a:
         2a:ce:00:79:dc:c0:5f:19:67:2c:6b:4b:ef:68:68:0b:43:e3:
         ac:c1:62:09:ef:a6:dd:65:61:a0:af:84:55:48:91:52:1c:c6:
         25:91:2a:d0:c1:22:23:61:59:af:45:11:85:1d:01:24:34:8f:
         cf:b3:ff:17:72:20:13:c2:80:aa:21:2c:71:39:0e:d0:8f:5c:
         c1:d3:d1:8e:22:72:46:4c:1d:96:ae:4f:71:b1:e1:05:29:96:
         59:f4:bb:9e:75:3d:cf:0d:37:0d:62:db:26:8c:63:a9:23:df:
         67:06:3c:7c:3a:da:34:42:e1:66:b4:46:04:de:c6:96:98:0f:
         4b:48:7a:24:32:75:91:9f:ac:f7:68:e9:2a:b9:55:65:ce:5d:
         61:d3:27:70:d8:37:fe:9f:b9:af:a0:2e:56:b7:a3:65:51:ed:
         3b:ab:14:bf:4c:51:03:e8:5f:8a:05:9b:ee:8a:6e:9c:ef:bf:
         68:fa:c8:da:0b:e3:42:c9:d0:17:14:9c:b7:4a:e0:af:93:27:
         21:55:26:b5:64:2f:8d:f1:ff:a6:40:05:85:05:5c:ca:07:19:
         5c:0b:13:28:4c:58:7f:c2:a5:ef:45:da:60:d3:ae:65:61:9d:
         53:83:74:c2:ae:f2:5c:c2:16:ed:92:3e:84:3e:73:60:88:bc:
         76:f4:2c:cf:d0:7d:7d:d3:b8:5e:d1:91:12:10:e9:cd:dd:ca:
         25:e3:d5:ed:99:2f:be:75:81:4b:24:f9:45:46:94:c9:29:21:
         53:9c:26:45:aa:13:17:e4:e7:cd:78:e2:39:c1:2b:12:9e:a6:
         9e:1b:c5:e6:0e:d9:31:d9
SHA1 Fingerprint=77:47:4F:C6:30:E4:0F:4C:47:64:3F:84:BA:B8:C6:95:4A:8A:41:EC
-----BEGIN CERTIFICATE-----
MIIEPjCCAyagAwIBAgIESlOMKDANBgkqhkiG9w0BAQsFADCBvjELMAkGA1UEBhMC
VVMxFjAUBgNVBAoTDUVudHJ1c3QsIEluYy4xKDAmBgNVBAsTH1NlZSB3d3cuZW50
cnVzdC5uZXQvbGVnYWwtdGVybXMxOTA3BgNVBAsTMChjKSAyMDA5IEVudHJ1c3Qs
IEluYy4gLSBmb3IgYXV0aG9yaXplZCB1c2Ugb25seTEyMDAGA1UEAxMpRW50cnVz
dCBSb290IENlcnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzIwHhcNMDkwNzA3MTcy
NTU0WhcNMzAxMjA3MTc1NTU0WjCBvjELMAkGA1UEBhMCVVMxFjAUBgNVBAoTDUVu
dHJ1c3QsIEluYy4xKDAmBgNVBAsTH1NlZSB3d3cuZW50cnVzdC5uZXQvbGVnYWwt
dGVybXMxOTA3BgNVBAsTMChjKSAyMDA5IEVudHJ1c3QsIEluYy4gLSBmb3IgYXV0
aG9yaXplZCB1c2Ugb25seTEyMDAGA1UEAxMpRW50cnVzdCBSb290IENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC6hLZy254Ma+KZ6TABp3bqMriVQRrJ2mFOWHLP/vaCeb9zYQYKpSfYs1/T
RU4cctZOMvJyig/3gxnQaoCAAEUesMfnmr8SVycco2gvCoe9amsOXmXzHHfV1IWN
cCG0szLni6LVhjkCsbjSR87kyUnEO6fe+1R9V77w6G7CebI6C1XiUJgWMhNcL3hW
wcKUs/Ja5CeanyTXxuzQmyWC48zCxEXFjJd6BmsqEZ+pCm5IO2/b1BEZQvePB7/1
U1+cPvQXLOZprE4yTGJ36rfo5bs0vBmLrpxR57d+tVOxMyLlbc9wPBr64ptntoP0
jaWvYkxN4FisZDQSA/i2jZRjJKRxAgMBAAGjQjBAMA4GA1UdDwEB/wQEAwIBBjAP
BgNVHRMBAf8EBTADAQH/MB0GA1UdDgQWBBRqciZ60B7vfec7aVHUbI2fkBJmqzAN
BgkqhkiG9w0BAQsFAAOCAQEAeZ8dlsa2eT8ijYfThwMEYGprmi5ZiXMRrEPR9RP/
jTkrwPK9T3CMqS/qF8QLVJ7UG5aYMzyorWKiAHarWWluBh1+xLlEjZivEtRh2woZ
Rkfz6/djwUAFQKXSt/S1mja/qYh2iARVBCuch38aNzx+LaUa2NSJXsq9rD1s2G2v
1fN2D807iDginWyTmsQ9v4IbZT+mD12q/OWyFcq1rca8PdCE6OoGcrBNOTJ4vz4R
nAuknZoh8/CbCzB428Hch0P+vGOaysXCHMnHjf87ElgI5rY97HosTvuDls4MPGmH
VHOkc8KT/1EQrBVUAdj8BbGJoX90g5pJ19xOe4pIb4tF9g==
-----END CERTIFICATE-----
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 1246989352 (0x4a538c28)
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=US, O=Entrust, Inc., OU=See  entrust net /legal-terms, OU=(c) 

2009 Entrust, Inc. - for authorized use only, CN=Entrust Root Certification 

Authority - G2
        Validity
            Not Before: Jul  7 17:25:54 2009 GMT
            Not After : Dec  7 17:55:54 2030 GMT
        Subject: C=US, O=Entrust, Inc., OU=See entrust net /legal-terms, OU=(c) 

2009 Entrust, Inc. - for authorized use only, CN=Entrust Root Certification 

Authority - G2
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:ba:84:b6:72:db:9e:0c:6b:e2:99:e9:30:01:a7:
                    76:ea:32:b8:95:41:1a:c9:da:61:4e:58:72:cf:fe:
                    f6:82:79:bf:73:61:06:0a:a5:27:d8:b3:5f:d3:45:
                    4e:1c:72:d6:4e:32:f2:72:8a:0f:f7:83:19:d0:6a:
                    80:80:00:45:1e:b0:c7:e7:9a:bf:12:57:27:1c:a3:
                    68:2f:0a:87:bd:6a:6b:0e:5e:65:f3:1c:77:d5:d4:
                    85:8d:70:21:b4:b3:32:e7:8b:a2:d5:86:39:02:b1:
                    b8:d2:47:ce:e4:c9:49:c4:3b:a7:de:fb:54:7d:57:
                    be:f0:e8:6e:c2:79:b2:3a:0b:55:e2:50:98:16:32:
                    13:5c:2f:78:56:c1:c2:94:b3:f2:5a:e4:27:9a:9f:
                    24:d7:c6:ec:d0:9b:25:82:e3:cc:c2:c4:45:c5:8c:
                    97:7a:06:6b:2a:11:9f:a9:0a:6e:48:3b:6f:db:d4:
                    11:19:42:f7:8f:07:bf:f5:53:5f:9c:3e:f4:17:2c:
                    e6:69:ac:4e:32:4c:62:77:ea:b7:e8:e5:bb:34:bc:
                    19:8b:ae:9c:51:e7:b7:7e:b5:53:b1:33:22:e5:6d:
                    cf:70:3c:1a:fa:e2:9b:67:b6:83:f4:8d:a5:af:62:
                    4c:4d:e0:58:ac:64:34:12:03:f8:b6:8d:94:63:24:
                    a4:71
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Certificate Sign, CRL Sign
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Key Identifier: 
                6A:72:26:7A:D0:1E:EF:7D:E7:3B:69:51:D4:6C:8D:9F:90:12:66:AB
    Signature Algorithm: sha256WithRSAEncryption
         79:9f:1d:96:c6:b6:79:3f:22:8d:87:d3:87:03:04:60:6a:6b:
         9a:2e:59:89:73:11:ac:43:d1:f5:13:ff:8d:39:2b:c0:f2:bd:
         4f:70:8c:a9:2f:ea:17:c4:0b:54:9e:d4:1b:96:98:33:3c:a8:
         ad:62:a2:00:76:ab:59:69:6e:06:1d:7e:c4:b9:44:8d:98:af:
         12:d4:61:db:0a:19:46:47:f3:eb:f7:63:c1:40:05:40:a5:d2:
         b7:f4:b5:9a:36:bf:a9:88:76:88:04:55:04:2b:9c:87:7f:1a:
         37:3c:7e:2d:a5:1a:d8:d4:89:5e:ca:bd:ac:3d:6c:d8:6d:af:
         d5:f3:76:0f:cd:3b:88:38:22:9d:6c:93:9a:c4:3d:bf:82:1b:
         65:3f:a6:0f:5d:aa:fc:e5:b2:15:ca:b5:ad:c6:bc:3d:d0:84:
         e8:ea:06:72:b0:4d:39:32:78:bf:3e:11:9c:0b:a4:9d:9a:21:
         f3:f0:9b:0b:30:78:db:c1:dc:87:43:fe:bc:63:9a:ca:c5:c2:
         1c:c9:c7:8d:ff:3b:12:58:08:e6:b6:3d:ec:7a:2c:4e:fb:83:
         96:ce:0c:3c:69:87:54:73:a4:73:c2:93:ff:51:10:ac:15:54:
         01:d8:fc:05:b1:89:a1:7f:74:83:9a:49:d7:dc:4e:7b:8a:48:
         6f:8b:45:f6
SHA1 Fingerprint=8C:F4:27:FD:79:0C:3A:D1:66:06:8D:E8:1E:57:EF:BB:93:22:72:D4