-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
euicc_init failed on 5ber standard edition #175
Comments
I have a similar issue with the
I have tested it on the same machine via. Windows and it shows the same behavior. |
@JohnDoe-JohnDoe ; @Root-Core
This is the first thing I'd try to see if the issue is related to card or driver or LPAC. |
Decided to give this a try with my 5ber Ultra. `++APDUSender : Begin++ TrasmitAPDU : SUCCESS TrasmitAPDU : SUCCESS TrasmitAPDU : SUCCESS TrasmitAPDU : SUCCESS TrasmitAPDU : SUCCESS Not sure what any of this means. Hope it doesn't damage my card. 😋 |
Well, the issue is definitely the card. Quick search suggests to try
If it returns 019000 you can go forward, otherwise please post the response code.
It shouldn't, but of course sending any apdu command is a 'do at your own risk' thing. These commands do not modify file system of your eUICC so I wouldn't worry if I were you. Hope that helps. I am not a smart card mega expert as well. |
@rdtmaster
Tried the new commands you posted with 5ber Ultra.
|
Also got the same error code 87 with 9esim with 00 70 00 00 00 01 |
I used gscriptor, but never worked with it before.. so I hope that helps:
|
My bad, I made a mistake when pasting the command. Of course I meant
(there was an unwanted |
@rdtmaster Thanks. Got 019000 this time.
|
@harshd3shpande You might try to select another aid just to see if it exists:
(Ecasd), but even if you can you will not be able to do much other than view card EID. |
This is what I thought.. but unfortunally I do not have access to such a device. |
@iebb over at NekokoLPA checked in this change meant to support 5ber. Although I haven't had much luck with their app either even with the latest version with the 5ber toggle turned on. |
@harshd3shpande @JohnDoe-JohnDoe @Root-Core
Like I said, 5ber uses custom AID
If you don't have trouble compiling lpac from source, I'd find Or before doing that run APDU command:
To see if the AID is right. |
I have just changed the AID in the source code, compiled LPAC and could download an eSim profile to a 5ber standard card that was not working previously successfully. Thanks @rdtmaster for the hint. |
That's good news. |
@JohnDoe-JohnDoe I forked the repo. You can download the binaries from here. https://github.com/harshd3shpande/lpac/actions/runs/12528635582 Also download EasyLPAC from here https://github.com/creamlike1024/EasyLPAC/releases/tag/0.7.6.5 Replace the lpac.exe file included in EasyLPAC with the one from my fork. |
That's great thanks. |
Had you actually installed an eSIM on the card? Check on 5ber app to see if it shows any profiles on it. If it's a brand new 5ber card, then there shouldn't be any profiles on it. |
Was the same with my card as well, it also showed 5ber as the provider name when installing it in a device. But there were no profiles on the card. |
Thanks. |
…up#157) - Added env variable "CUSTOM_AID" for user defined AIDs - Added support for 5ber by iterating over multiple pre-defined AIDs
I implemented support for 5ber Standard via #181 please give some feedback, if it works out for you. |
I'm trying to use EasyLPAC (windows 11) with a 5ber "standard" eSim card.
I am using this card reader http://www.aliexpress.com/item/1005006885571475.html
I get a popup
Lpac error
Function:euicc_init
Data:
Please check log for details
When I look at the log:
C:\temp\EasyLPAC-windows-x86_64-with-lpac\lpac.exe version
{"type":"lpa","payload":{"code":0,"message":"success","data":"v2.1.0"}}
C:\temp\EasyLPAC-windows-x86_64-with-lpac\lpac.exe driver apdu list
{"type":"driver","payload":{"env":"DRIVER_IFID","data":[{"env":"0","name":"Generic Smart Card Reader Interface 0"}]}}
C:\temp\EasyLPAC-windows-x86_64-with-lpac\lpac.exe profile list
{"type":"lpa","payload":{"code":-1,"message":"euicc_init","data":""}}
I messaged EasyLPAC and was told it is an LPAC issue.
What am I doing wrong??
Thanks.
The text was updated successfully, but these errors were encountered: