Jump to content
Sign in to follow this  
Followers 0
jsione

Erricsson H5321gw high sierra

3 posts in this topic

Recommended Posts

Hello everyone.

I'm trying to get . work my H5321gw WWAN card on High Sierra.

I have a patched kext (in attachment) and unclear info from logs:

 

 

Mon Apr  2 13:30:18 2018 : Initializing device: AT&FE0Q0V1
Mon Apr  2 13:30:18 2018 : Initializing PDP context: AT+CGDCONT=1,"IP","otk.msk"
Mon Apr  2 13:30:18 2018 : Dialing: ATD*99***1#
Mon Apr  2 13:30:18 2018 : Waiting for connection
Mon Apr  2 13:30:19 2018 : Connection established
Mon Apr  2 13:30:22 2018 : Serial connection established.
Mon Apr  2 13:30:22 2018 : Using interface ppp0
Mon Apr  2 13:30:22 2018 : Connect: ppp0 <--> /dev/cu.wwan
Mon Apr  2 13:30:56 2018 : LCP: timeout sending Config-Requests
Mon Apr  2 13:30:56 2018 : Connection terminated.
Mon Apr  2 13:31:06 2018 : Serial link disconnected.
Mon Apr  2 13:50:48 2018 : publish_entry SCDSet() failed: Success!
Mon Apr  2 13:50:48 2018 : publish_entry SCDSet() failed: Success!
Mon Apr  2 13:50:49 2018 : Apple Base Script.ccl Version 3.3
Mon Apr  2 13:50:49 2018 : Initializing device: AT&FE0Q0V1
Mon Apr  2 13:50:49 2018 : Initializing PDP context: AT+CGDCONT=1,"IP","otk.msk"
Mon Apr  2 13:50:49 2018 : Dialing: ATD*99***1#
Mon Apr  2 13:50:49 2018 : Waiting for connection
Mon Apr  2 13:50:50 2018 : Connection established
Mon Apr  2 13:50:54 2018 : Serial connection established.
Mon Apr  2 13:50:54 2018 : Using interface ppp0
Mon Apr  2 13:50:54 2018 : Connect: ppp0 <--> /dev/cu.usbmodem
Mon Apr  2 13:51:28 2018 : LCP: timeout sending Config-Requests
Mon Apr  2 13:51:28 2018 : Connection terminated.
Mon Apr  2 13:51:37 2018 : Serial link disconnected.

 

Please help me to resolve  my problem.

Laptop specs: ThinkPad x230 2325-78G

CellPhoneHelper.kext.zip

Share this post


Link to post
Share on other sites
Advertisement

Rather than patch the CellPhoneHelper directly, I recommend you insert the patch into FakeSMC's Info.plist. That brings the following advantages:

  • it keeps the vanilla CellPhoneHelper kext untouched in /S/L/E
  • it keeps the patch sustainable to OS X/macOS updates (not necessarily to OS X/macOS upgrades since Apple has a tendency to modify USB kext names and Info.plist syntax with each new release)

Which vanilla profile did you base your patch on? Sony Ericsson W350?

Who's your cell service provider and, assuming you do have a suitably detected and installed WWAN module under OS X/macOS, how did you setup your connection (APN details)?

Edited by Hervé

Share this post


Link to post
Share on other sites

Yes, I've used SE W350 profile. 

My cell carier is  MegaFon (Russia) and quasi-MVNO utcorp.ru. So my APN is "otk.msk".

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By 22eme_arkane
      Hi everyone !
       
       I build a new os on High Sierra and i have problem with my Skarkoon RAID 5 - 5 bay, is unmounting, work fine in windows but not in Mac Os.
      I use a card eSata in chipset Marvell 88SE9215, and i have the kext 3-party eSata  but nothings change.
      I try with the AppleAHCIPort.kext v328, nothings change.
       
      Any solution ?
       
      Thanks a lot !
       
      Config : GA-Z68X-UB3-B3 // BIOS UEFI, Version: U1f //
    • By bummercheese
      I have what's been said to be a natively supported wifi card, but for the life of me I cannot get it working properly with High Sierra. It is detected in DPCIManager but the wifi symbol at the top is hollowed and I can't turn it on.
       
      Here's some basic info about my hackintosh. It's running an i7 9700k with an MSI Z390-A PRO, a GTX 1070, and it's SMBIOS is running as an iMac 18.1

      Someone else has posted here about this with an ac66, which I think is very similar and uses the same device number 43A0. But he didn't get his problem solved in the end. And I have looked up this problem in a million different ways, I haven't found a solution that works from any yet.
       
      I've tried a large amount of different kext patches, kexts (fakepciid, airportbrcmfixup, etc), changing fake ID, modifying kext info.plist files, and every combination of those, none have gotten it to properly work.
       
      I have gotten it to work in one way but it's so unstable that it's unusable. Using the IO80211family.kext from yosemite works, but then it will randomly freeze about 10-15 minutes in, and then it'll not boot 9/10 times, and when it will it'll freeze on the login or right after. It gives errors about out of date kext, only way get back in is by reinstalling. So I figure this method is unusable.
       
      I'm just stumped on why a supposed confirmed working out of box card doesn't just just work, even with every amount of tweaking and adding kexts. I'm in my 4th day of almost nonstop testing and researching on how to fix this, and I'm too stubborn and determined to just buy a different card. Any suggestions would be greatly appreciated. 
    • By gannok
      Hello and thanks for taking the time to read this, I can't seem to get past this screen, I've tried booting in verbose and safe mode to help diagnose the issue, but it keeps looking like the system is rejecting my CPU? am I forgetting something to do in the bootloader menu of clover on the drive? Kernel extensions? or the plist files? I've tried a lot of things. help would be much appreciated.

      Don't have access to download the Mojave installer and try that, but I assume it would be similar to this.

      I have included my EFI boot loader, and the error in hopes that it may help

      System build here

      Z370 Aorus Ultra Gaming Wifi
      i3-8100
      32GB ballistix ddr4
      RX560 4GB

      EFI.zip
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.13 installation on MBR partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.13 Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.13 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. This patched MBR OSInstaller method works with both MBR and GPT partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.13 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?

      How to make 10.13 installer for MBR (MBR-Automatic-Method)?
      Just use 13MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, new for 10.13+.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
       


       
×