search

estkme-group / lpac

C-based eUICC LPA
GNU Affero General Public License v3.0
292 stars 67 forks source link

built in Microsoft UICC ISO Reader not recognized #62

Closed itenosgh closed 5 months ago

itenosgh commented 7 months ago

I have an ASUS Laptop with built in WWAN card that contains a SIM tray and an eSIM. The Laptop also has a built in card reader from Alcorlink. If I insert my 5ber card into the card reader EasyLPAC is able to read the profile correctly but is not able to download any new profile. If I insert it instead into my SIM tray the profile cannot be read giving the error code: SCardConnect() failed: 8010000F {"type":"lpa","payload":{"code":-1,"message":"es10x_init","data":""}}

This same error code happens also if I want to read the profile of my built in eSIM (without 5ber card in the SIM tray)

Using the SIM tray Windows 11 is able to install new profiles on my 5ber card instead.

As LPAC gives valuable information about the remaining space on the eSIM I like to use that instead but the constant fiddling of getting the nanoSIM into the full size card and out again is more cumbersome then just inserting it into the SIM tray.

Any idea how to make LPAC recognize my built in Microsoft UICC ISO Reader?

damonto commented 7 months ago

To read your card from the WWAN SIM tray, you need to set LPAC_APDU=at and AT_DEVICE=comX environments. Please ensure that your modem supports these commands: AT+CCHO, AT+CGLA, and AT+CCHC

itenosgh commented 7 months ago

Thank you for your quick reply. I tried to issue your commands but I receive the following errors:

PS C:\Users\ExpertBook\Downloads\EasyLPAC-windows-x86_64-with-lpac (2)> LPAC_APDU=at LPAC_APDU=at : The term 'LPAC_APDU=at' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

PS C:\Users\ExpertBook\Downloads\EasyLPAC-windows-x86_64-with-lpac (2)> AT_DEVICE=comX AT_DEVICE=comX : The term 'AT_DEVICE=comX' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

PS C:\Users\ExpertBook\Downloads\EasyLPAC-windows-x86_64-with-lpac (2)> at The AT command has been deprecated. Please use schtasks.exe instead.

The request is not supported.

What am I doing wrong?

On Sun, Mar 31, 2024 at 9:09 AM Damon To @.***> wrote:

To read your card from the WWAN SIM tray, you need to set LPAC_APDU=at and AT_DEVICE=comX. Please ensure that your modem supports these commands: AT+CCHO, AT+CGLA, and AT+CCHC

— Reply to this email directly, view it on GitHub https://github.com/estkme-group/lpac/issues/62#issuecomment-2028529454, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHO4WZ5NNUBLAQN3WYDZH73Y25V6ZAVCNFSM6AAAAABFQAD3ZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGUZDSNBVGQ . You are receiving this because you authored the thread.Message ID: @.***>

estkme commented 7 months ago

Your situation is a bit complicated.

For your first issue: 5ber card can't download new profile by lpac

There are several possibilities.

  1. Your card reader doesn't fully support interactive with eUICC. That was reported before by two user(not in github issues)
  2. Your card reader does support operating eUICC, but the driver on Windows is broken. That was also reported before, after switch to Linux solved this.
  3. There is a bug in our project "estkme-group/lpac". That could be possible, but since lpac have been widely tested, which I think it is not quite possible.
  4. 5ber OTA itself firmware to block lpac. Since before there actually many 5ber user use lpac to bypass "5ber standard" download limitations, that's confirmed we compatible 5ber before. But I don't think this could be possible.

...And for the second issue: Your card in built-in LTE module doesn't work with lpac.

In one word: Yes, that is predictable.

  1. lpac only support operating eUICC through LTE modules by AT command interface or gbinder on Linux based OS.
  2. On windows platform we never tested AT interfaces.
  3. Mostly your LTE module use MBIM interface to interact with eUICC which lpac is lacking support with it.
  4. Most of primary contributors of lpac are Linux users so we don't make many support/test on windows. But contributions are welcome.

PS: EasyLPAC only support SmartCard Reader, that is a limition in its code. You need use lpac for future debug.

damonto commented 7 months ago

Thank you for your quick reply. I tried to issue your commands but I receive the following errors: PS C:\Users\ExpertBook\Downloads\EasyLPAC-windows-x86_64-with-lpac (2)> LPAC_APDU=at LPAC_APDU=at : The term 'LPAC_APDU=at' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + LPAC_APDU=at + ~~~~ + CategoryInfo : ObjectNotFound: (LPAC_APDU=at:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException PS C:\Users\ExpertBook\Downloads\EasyLPAC-windows-x86_64-with-lpac (2)> AT_DEVICE=comX AT_DEVICE=comX : The term 'AT_DEVICE=comX' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + AT_DEVICE=comX + ~~~~~~ + CategoryInfo : ObjectNotFound: (AT_DEVICE=comX:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException PS C:\Users\ExpertBook\Downloads\EasyLPAC-windows-x86_64-with-lpac (2)> at The AT command has been deprecated. Please use schtasks.exe instead. The request is not supported. What am I doing wrong? … On Sun, Mar 31, 2024 at 9:09 AM Damon To @.> wrote: To read your card from the WWAN SIM tray, you need to set LPAC_APDU=at and AT_DEVICE=comX. Please ensure that your modem supports these commands: AT+CCHO, AT+CGLA, and AT+CCHC — Reply to this email directly, view it on GitHub <#62 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHO4WZ5NNUBLAQN3WYDZH73Y25V6ZAVCNFSM6AAAAABFQAD3ZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGUZDSNBVGQ . You are receiving this because you authored the thread.Message ID: @.>

I have confirmed that LPAC does not yet support using a modem to communicate with eUICC on Windows

itenosgh commented 7 months ago

OK, thank you, let's hope you will be able to implement this soon. If you need help with testing let me now

itenosgh commented 6 months ago

Hi, as you confirmed that LPAC doesn't support a modem under Windows I installed the Windows Subsystem for Linux on my Laptop. Being a complete noob to Linux it took some time to learn how to manage it. First difficulty was to get the gtk3dialog dependencies installed but that's finally done. Now when I execute EasyLPAC it gives me the following errors and I have no idea how to proceed. Could you please explain step by step for a total Linux noob?

mario@ASUS-EXPERTBOOK:/mnt/c/Users/ExpertBook/Downloads/EasyLPAC-linux-x86_64-with-lpac$ ./EasyLPAC 2024/04/20 16:26:37 Fyne error: Unable to connect to session D-Bus 2024/04/20 16:26:37 Cause: dial unix /run/user/1000/bus: connect: no such file or directory 2024/04/20 16:26:37 At: /home/runner/go/pkg/mod/fyne.io/fyne/v2@v2.4.4/app/app_xdg.go:40 2024/04/20 16:26:37 Fyne error: Unable to connect to session D-Bus 2024/04/20 16:26:37 Cause: dial unix /run/user/1000/bus: connect: no such file or directory 2024/04/20 16:26:37 At: /home/runner/go/pkg/mod/fyne.io/fyne/v2@v2.4.4/app/app_xdg.go:177

Further while in EasyLPAC for Windows I can at least choose my adapter under the Linux version I can't at all

image

estkme commented 5 months ago

I will close this issue for now.

We lack the hardware mentioned in this issue and the development team cannot debug it.

The conversation can still continue, feel free to subscribe/unsubscribe it.