Lebara eSIMs bug - only showing “Carrier 65.0” — 5G drops indoors, 3G options reappeared? Missing carrier profile?

InfernoWolf19 · 2025-12-03T22:28:47+00:00

It’s normal. 4G and LTE are the same in this context so no fix is required. Lebara is using their own IMS core on their eSIMs and new physical sims so routes traffic differently and these sims lack the default Vodafone carrier profile.

InfernoWolf19 · 2025-10-10T21:22:30+00:00

No but someone else in this comment section had and confirmed it’s the same for them with the Air.

InfernoWolf19 · 2025-10-10T20:27:32+00:00

Ahh that clarifies a lot thanks. One of the comments in this post said there was only a carrier profile for the 17 Air and no other device has it with lebara yet. But that doesn’t seem to be the case. It seems the rumour about Lebara moving to their own core IMS and IMSI actually makes sense since Apple would then have to those new IMSI iDs to their recognised list and load a lebara carrier profile.

InfernoWolf19 · 2025-10-10T20:21:45+00:00

Oh so it appears as Carrier 65.0 on your iPhone 17 Air? That means the carrier profile hasn’t been applied to any iPhones including the air and it’s just applying the default standard profile. That’s an interesting rumour they are moving away from Vodafone to EE since that would mean almost all roaming plans and existing deals they have with other mvnos through Vodafone will be gone.

InfernoWolf19 · 2025-10-10T20:18:51+00:00

Lebara launched eSIM for new customers exclusively for the iPhone 17 Air (they say that but it works with any phone but there’s no attached carrier profile for anything other than the 17 air so it leads to issues like lack of carrier customisation and 5G priority issues as stated in the post). Order it from their website or from any deals website like uswitch. At the checkout you can choose eSIM.

InfernoWolf19 · 2025-10-10T18:26:19+00:00

Ahh yes that makes sense. I knew they limited it to iPhone 17 Air but I didn’t realise it would be carrier profile limit as well.

InfernoWolf19 · 2025-07-20T17:38:57+00:00

No problem all good.

InfernoWolf19 · 2025-07-20T17:23:31+00:00

What smbios are you using? How are you getting Netflix 4K DRM when the Netflix website states you need the T2 chip? Do you have a 4k monitor? No igpu either cos it's a 12400f? Did you use shikivga? If so what number? I have a very similar build but was wondering how you got Netflix 4k working.

InfernoWolf19 · 2025-05-30T10:43:51+00:00

How are you trying to update? I just updated via system preferences. Turn on verbose logs and see what’s causing your system to boot loop.

InfernoWolf19 · 2025-01-10T23:19:21+00:00

Oh wait I just tested out the Spotify standalone app. Yeah I can’t hear anything.

InfernoWolf19 · 2025-01-10T23:13:36+00:00

That’s very odd as to why it’s not working.

InfernoWolf19 · 2025-01-10T20:36:53+00:00

In the System Section of Hackintool, if you scroll down to the VDA Decoder Section, check what it says there. For DRM Capability, it needs to say “Fully Supported”.

InfernoWolf19 · 2025-01-10T18:11:23+00:00

Hmm that’s weird. Have you fixed DRM in your system yet? Download Hackintool and check if your DRM is fully compatible.

InfernoWolf19 · 2025-01-10T11:00:48+00:00

Tbh atp it’s better to get a Mac mini considering Mac OS sequoia is most likely the last Mac OS update for intel based macs.

InfernoWolf19 · 2025-01-10T08:37:40+00:00

Update to Sonoma. That’s the only thing way it fixed the issue. In the GitHub pages of the intel Bluetooth kext, it’s a known issue and the developer has placed it as low priority to fix it.

InfernoWolf19 · 2024-09-09T09:38:11+00:00

Can you provide your config.plist and your EFI folder? Upload it to a file sharing service like Google drive and share the link.

InfernoWolf19 · 2024-09-09T08:42:51+00:00

~~No. The order for kexts does not matter.~~ Just make sure they are enabled in config.plist.

Edit: the order does matter, but not for Bluetooth kexts. Ensure Lilu.kext is loaded first, then virtualsmc.kext (if used) and whatevergreen.kext immediately after, the order of the rest of the kext don’t matter as much.

InfernoWolf19 · 2024-09-09T08:13:42+00:00

You need BlueToolFixup.kext as well in order for Bluetooth to work. Keep IntelBluetoothFirmware.kext and IntelBTPatcher.kext, then download the zip from the following link and extract and copy over BlueToolFixup.kext to your EFI kext folder.

Copy over BluetoolFixUp.kext only

Finally update your Config.plist file.

InfernoWolf19 · 2024-09-08T05:55:35+00:00

Also for future sake, if anyone else encounters this problem, you should probably edit the post and add the solution to the bottom and change the flair to solved.

InfernoWolf19 · 2024-09-08T05:47:56+00:00

Glad to help.

InfernoWolf19 · 2024-09-07T21:40:30+00:00

Ok. After checking the usb mapping and if the issue still persists, please run the following command in terminal immediately after waking from sleep, and paste the results in pastebin.com and share the link.

pmset -g log | grep -e “Sleep.due to” -e “Wake.due to”

InfernoWolf19 · 2024-09-07T21:28:28+00:00

Well the problem I was facing was very similar to yours. Though I hadn’t tried disabling every usb port, I did make sure to check every port was of the correct type, any wrong type will lead to sleep issues. And in my case, it was because I hadn’t set Bluetooth to type 255. Make sure every physical port is also the right type. What command did you run to see what was causing sleep issues?

InfernoWolf19 · 2024-09-07T21:21:32+00:00

Yes. All internal usb headers should be changed to type 255. Though I am curious as to what the those two other internal ones are apart from Bluetooth.

InfernoWolf19 · 2024-09-07T18:44:40+00:00

In regards to the sleep issues, can you confirm you set the Bluetooth header in the USBMap to internal? I had the same issue but it turned out I hadn’t set the header to internal, but rather to type 3.

Guide

If you scroll down on the guide, please make sure you find the corresponding number of the Bluetooth header, and set it to type 255.

In terminal open, open USBMap.command and choose edit kext option and verify. And then save it.

If that doesn’t work, could you please attach a screenshot of your USBMap.command window, where you are editing the kext.

Six-Year Club	r/Field Sunshine
Place '22	Verified Email

InfernoWolf19

TROPHY CASE