Jump to content
InsanelyMac Forum

sebkulu

Members
  • Content count

    24
  • Joined

  • Last visited

About sebkulu

  • Rank
    InsanelyMac Protégé
  • Birthday 06/06/1979

Profile Information

  • Gender
    Male
  • Location
    France
  1. Wouldn't that be the purpose of Kernel flag in org.chameleon.boot.plist? Kernel=<file> The filename of your kernel you wish to boot. This can be different from mach_kernel, but be sure to create a symlink that points to the new kernel you're booting with a name of mach_kernel to allow all software to be compatible. Note that this is necessary for you to boot a differently named kernel, because osx naively tries to load the symlink itself as the kernel and not the file that the symlink points to if you don't tell the bootloader! [Default mach_kernel]
  2. 10.9 Ivy Bridge-E, Atom & Lapic Fix Kernel

    Oh, and by the way, I'm also NOT currently using NullCPUPM, without any problems at all... with Ivy Bridge-E CPU! (i7 4930K) Ok, I don't get CPU Power Management to fully work, I only get multiplier 34... so using NullCPUPM has the one advantage of being able to lower CPU multiplier to 12, BUT, when Mac Pro 6,1 will be released anytime soon, that should be a whole different story
  3. Thanks mate ;-) Nope, you can keep them as long as they're as useful to you to correct Chameleon SMBios Injector ;-) You can also share them with the Dev Team as long as they're useful ;-)
  4. Ok, so, supposed that Bungo already downloaded the files, I can now delete them ;-) Ok, next time I'll hide sensitive informations.
  5. I'm starting to think I shouldn't have ^^ Also, by sharing this with the community with the intention of helping, I really hope no one thinks about doing something wrong with my personal information ;-) Anyway, here are also SMC keys attached: SMC-keys.txt
  6. Ok, so short answer is : "I don't care" Here you are, see attached MacBook Pro 11,2 (file deleted)
  7. Oh? As simple as that? I should have looked at that possibility first Before I do so, should I hide my Original Mac Serial Number in .spx file or should I not care because IT IS an original Mac? ^^
  8. So I double-checked, and you're right, the MLB is only a 17 digits string ! Just replaced value in my post I also noted that something is quite not right at the very end of the file stating : "Invalid entry length (0). DMI Table is broken! Stop." But I extracted everything with DarwinDumper 2.8.6... So I don't know why that message... Anyway, how do I do to dump System Profiler? For IOReg, I think I have a valid dumper, but not for System Profiler, and DarwinDumper only produces TXT files to be used within the generated HTML GUI... I have to disagree with you on the fact MLB isn't useful... A long discussion about that has been done in January/february 2013 around iMessage connection problems, and it seemed that only FileNVRAM containing a 17 digits MLB could do the job. I'll give you another example: I'm currently having the "Call Apple Support" popup when trying to log into iMessage, BUT if I change my MLB "on the fly" (meaning with NVRam commands without any reboot), and try to reconnect to iMessage, it WORKS! I mean, first time I try to reconnect, Message App seems to be searching (in vain) the iMessage server, which is never found, so I have to cancel. The second time though, it CONNECTS! Sure, I CAN'T send or receive any messages, but Message App says I'm connected, and I'm able to see my personal informations, and to modify them!!! So, for sure, MLB IS quite involved in some Apple processes.
  9. Hi there, Here is my SMBios dump from MBP 11,2: # dmidecode 2.11b Handle 0x0000, DMI type 4, 35 bytes 0000: 04 23 00 00 04 03 c6 02 61 06 04 00 ff fb eb bf 0010: 01 8a 19 00 d0 07 d0 07 41 2d 02 00 03 00 04 00 0020: 03 05 00 Processor Information Socket Designation: U3E1 Type: Central Processor Family: Core i7 Manufacturer: Intel(R) Corporation ID: 61 06 04 00 FF FB EB BF Signature: Type 0, Family 6, Model 70, Stepping 1 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz Voltage: 1.0 V External Clock: 25 MHz Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: <OUT OF SPEC> L1 Cache Handle: 0x0002 L2 Cache Handle: 0x0003 L3 Cache Handle: 0x0004 Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Part Number: Not Specified Handle 0x0001, DMI type 7, 19 bytes 0000: 07 13 01 00 00 80 01 80 00 80 00 40 00 40 00 00 0010: 05 04 07 Cache Information Socket Designation: Not Specified Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 128 kB Maximum Size: 128 kB Supported SRAM Types: Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Data Associativity: 8-way Set-associative Handle 0x0002, DMI type 7, 19 bytes 0000: 07 13 02 00 00 80 01 80 00 80 00 40 00 40 00 00 0010: 05 03 07 Cache Information Socket Designation: Not Specified Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 128 kB Maximum Size: 128 kB Supported SRAM Types: Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Instruction Associativity: 8-way Set-associative Handle 0x0003, DMI type 7, 19 bytes 0000: 07 13 03 00 00 81 01 00 04 00 04 40 00 40 00 00 0010: 05 05 07 Cache Information Socket Designation: Not Specified Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: Internal Installed Size: 1024 kB Maximum Size: 1024 kB Supported SRAM Types: Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 8-way Set-associative Handle 0x0004, DMI type 7, 19 bytes 0000: 07 13 04 00 00 82 01 00 18 00 18 40 00 40 00 00 0010: 05 05 09 Cache Information Socket Designation: Not Specified Configuration: Enabled, Not Socketed, Level 3 Operational Mode: Write Back Location: Internal Installed Size: 6144 kB Maximum Size: 6144 kB Supported SRAM Types: Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 12-way Set-associative Handle 0x0005, DMI type 7, 19 bytes 0000: 07 13 05 00 00 83 01 00 00 00 00 40 00 40 00 00 0010: 05 05 08 Cache Information Socket Designation: Not Specified Configuration: Enabled, Not Socketed, Level 4 Operational Mode: Write Back Location: Internal Installed Size: 0 kB Maximum Size: 0 kB Supported SRAM Types: Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 16-way Set-associative Handle 0x0006, DMI type 16, 15 bytes 0000: 10 0f 06 00 03 03 03 00 00 80 00 fe ff 02 00 Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 8 GB Error Information Handle: Not Provided Number Of Devices: 2 Handle 0x0007, DMI type 130, 186 bytes 0000: 82 ba 07 00 08 00 00 00 b0 00 92 12 0b 03 04 21 0010: 02 01 03 52 01 08 0a 00 fe 00 69 78 69 30 69 11 0020: 18 81 20 08 3c 3c 00 f0 83 01 00 00 00 00 00 00 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040: 00 00 00 00 00 00 2f 11 61 01 00 00 00 00 00 00 0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 0080: ad 01 00 00 00 00 00 00 bc 8d 48 4d 54 34 35 31 0090: 53 36 41 46 52 38 41 2d 50 42 20 20 4e 41 80 ad 00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0: 00 00 00 00 00 00 00 00 00 00 Apple specific SPD 000082ba070008000000b00092120b030421 00100201035201080a00fe00697869306911 0020188120083c3c00f08301000000000000 003000000000000000000000000000000000 00400000000000002f116101000000000000 005000000000000000000000000000000000 006000000000000000000000000000000000 007000000000000000000000000000000080 0080ad01000000000000bc8d484d54343531 0090533641465238412d504220204e4180ad 00a000000000000000000000000000000000 00b0000000000000000000000000111b0800 00c00600ffff0000000000100d0001021880 00d00040060304050644494d4d300042414e 00e04b203000307838304144003078303030 00f0303030303000556e6b6e6f776e003078 Handle 0x0008, DMI type 17, 27 bytes 0000: 11 1b 08 00 06 00 ff ff 00 00 00 00 00 10 0d 00 0010: 01 02 18 80 00 40 06 03 04 05 06 Memory Device Array Handle: 0x0006 Error Information Handle: No Error Total Width: Unknown Data Width: Unknown Size: 4096 MB Form Factor: SODIMM Set: None Locator: DIMM0 Bank Locator: BANK 0 Type: DDR3 Type Detail: Synchronous Speed: 1600 MHz (0.6 ns) Manufacturer: 0x80AD Serial Number: 0x00000000 Asset Tag: Unknown Part Number: 0x484D54343531533641465238412D50422020 Handle 0x0009, DMI type 130, 186 bytes 0000: 82 ba 09 00 0a 00 00 00 b0 00 92 12 0b 03 04 21 0010: 02 01 03 52 01 08 0a 00 fe 00 69 78 69 30 69 11 0020: 18 81 20 08 3c 3c 00 f0 83 01 00 00 00 00 00 00 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040: 00 00 00 00 00 00 2f 11 61 01 00 00 00 00 00 00 0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 0080: ad 01 00 00 00 00 00 00 bc 8d 48 4d 54 34 35 31 0090: 53 36 41 46 52 38 41 2d 50 42 20 20 4e 41 80 ad 00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0: 00 00 00 00 00 00 00 00 00 00 Apple specific SPD 000082ba09000a000000b00092120b030421 00100201035201080a00fe00697869306911 0020188120083c3c00f08301000000000000 003000000000000000000000000000000000 00400000000000002f116101000000000000 005000000000000000000000000000000000 006000000000000000000000000000000000 007000000000000000000000000000000080 0080ad01000000000000bc8d484d54343531 0090533641465238412d504220204e4180ad 00a000000000000000000000000000000000 00b0000000000000000000000000111b0a00 00c00600ffff0000000000100d0001021880 00d00040060304050644494d4d300042414e 00e04b203100307838304144003078303030 00f0303030303000556e6b6e6f776e003078 Handle 0x000A, DMI type 17, 27 bytes 0000: 11 1b 0a 00 06 00 ff ff 00 00 00 00 00 10 0d 00 0010: 01 02 18 80 00 40 06 03 04 05 06 Memory Device Array Handle: 0x0006 Error Information Handle: No Error Total Width: Unknown Data Width: Unknown Size: 4096 MB Form Factor: SODIMM Set: None Locator: DIMM0 Bank Locator: BANK 1 Type: DDR3 Type Detail: Synchronous Speed: 1600 MHz (0.6 ns) Manufacturer: 0x80AD Serial Number: 0x00000000 Asset Tag: Unknown Part Number: 0x484D54343531533641465238412D50422020 Handle 0x000B, DMI type 19, 15 bytes 0000: 13 0f 0b 00 00 00 00 00 ff ff 7f 00 06 00 00 Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x001FFFFFFFF Range Size: 8 GB Physical Array Handle: 0x0006 Partition Width: 0 Handle 0x000C, DMI type 0, 24 bytes 0000: 00 18 0c 00 01 02 00 00 03 7f 80 98 01 00 00 00 0010: 00 00 c1 02 00 01 ff ff BIOS Information Vendor: Apple Inc. Version: MBP112.88Z.0138.B00.1310031144 Release Date: 10/03/2013 ROM Size: 8192 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported ACPI is supported IEEE 1394 boot is supported Smart battery is supported Function key-initiated network boot is supported BIOS Revision: 0.1 Handle 0x000D, DMI type 1, 27 bytes 0000: 01 1b 0d 00 01 02 03 04 fa fc 4c f5 48 b4 4b 50 0010: a8 d5 8f 53 e0 76 60 16 06 05 06 System Information Manufacturer: Apple Inc. Product Name: MacBookPro11,2 Version: 1.0 Serial Number: **private** (12 digits) UUID: **private** Wake-up Type: Power Switch SKU Number: System SKU# Family: Mac Handle 0x000E, DMI type 2, 16 bytes 0000: 02 10 0e 00 01 02 03 04 05 09 06 0f 00 0a 00 00 0010: Base Board Information Manufacturer: Apple Inc. Product Name: Mac-3CBD00234E554E41 Version: MacBookPro11,2 Serial Number: **private** (17 digits) Asset Tag: Base Board Asset Tag# Features: Board is a hosting board Board is replaceable Location In Chassis: Part Component Chassis Handle: 0x000F Type: Motherboard Contained Object Handles: 0 Handle 0x000F, DMI type 3, 21 bytes 0000: 03 15 0f 00 01 0a 02 03 00 03 03 01 01 00 00 00 0010: 00 00 00 00 00 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-3CBD00234E554E41 Serial Number: **private** (12 digits) Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0010, DMI type 8, 9 bytes 0000: 08 09 10 00 01 00 02 12 10 Port Connector Information Internal Reference Designator: None Internal Connector Type: None External Reference Designator: USB0 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0011, DMI type 8, 9 bytes 0000: 08 09 11 00 01 00 02 12 10 Port Connector Information Internal Reference Designator: None Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0012, DMI type 8, 9 bytes 0000: 08 09 12 00 01 ff 02 00 ff Port Connector Information Internal Reference Designator: None Internal Connector Type: Other External Reference Designator: Mini DisplayPort External Connector Type: None Port Type: Other Handle 0x0013, DMI type 8, 9 bytes 0000: 08 09 13 00 01 ff 02 00 ff Port Connector Information Internal Reference Designator: None Internal Connector Type: Other External Reference Designator: Mini DisplayPort External Connector Type: None Port Type: Other Handle 0x0014, DMI type 8, 9 bytes 0000: 08 09 14 00 01 ff 02 00 ff Port Connector Information Internal Reference Designator: None Internal Connector Type: Other External Reference Designator: HDMI External Connector Type: None Port Type: Other Handle 0x0015, DMI type 8, 9 bytes 0000: 08 09 15 00 01 ff 02 00 ff Port Connector Information Internal Reference Designator: None Internal Connector Type: Other External Reference Designator: Microphone External Connector Type: None Port Type: Other Handle 0x0016, DMI type 8, 9 bytes 0000: 08 09 16 00 01 ff 02 00 ff Port Connector Information Internal Reference Designator: None Internal Connector Type: Other External Reference Designator: Speaker External Connector Type: None Port Type: Other Handle 0x0017, DMI type 8, 9 bytes 0000: 08 09 17 00 01 00 02 ff ff Port Connector Information Internal Reference Designator: None Internal Connector Type: None External Reference Designator: MagSafe DC Power External Connector Type: Other Port Type: Other Handle 0x0018, DMI type 8, 9 bytes 0000: 08 09 18 00 01 00 02 1f 1d Port Connector Information Internal Reference Designator: None Internal Connector Type: None External Reference Designator: Audio Line Out External Connector Type: Mini Jack (headphones) Port Type: Audio Port Handle 0x0019, DMI type 8, 9 bytes 0000: 08 09 19 00 01 00 02 12 10 Port Connector Information Internal Reference Designator: None Internal Connector Type: None External Reference Designator: SD Card Reader External Connector Type: Access Bus (USB) Port Type: USB Handle 0x001A, DMI type 9, 13 bytes 0000: 09 0d 1a 00 01 a5 08 03 03 00 00 04 06 System Slot Information Designation: AirPort Type: x1 PCI Express Current Usage: Available Length: Short ID: 0 Characteristics: 3.3 V is provided Hot-plug devices are supported SMBus signal is supported Handle 0x001B, DMI type 9, 13 bytes 0000: 09 0d 1b 00 01 06 05 03 04 02 00 04 07 System Slot Information Designation: Thunderbolt Slot 1 Type: 32-bit PCI Current Usage: Available Length: Long ID: 2 Characteristics: 3.3 V is provided PME signal is supported Hot-plug devices are supported SMBus signal is supported Handle 0x001C, DMI type 9, 13 bytes 0000: 09 0d 1c 00 01 06 05 03 04 03 00 04 07 System Slot Information Designation: Thunderbolt Slot 2 Type: 32-bit PCI Current Usage: Available Length: Long ID: 3 Characteristics: 3.3 V is provided PME signal is supported Hot-plug devices are supported SMBus signal is supported Handle 0x001D, DMI type 9, 13 bytes 0000: 09 0d 1d 00 01 06 05 03 04 04 00 04 07 System Slot Information Designation: Thunderbolt Slot 3 Type: 32-bit PCI Current Usage: Available Length: Long ID: 4 Characteristics: 3.3 V is provided PME signal is supported Hot-plug devices are supported SMBus signal is supported Handle 0x001E, DMI type 9, 13 bytes 0000: 09 0d 1e 00 01 06 05 03 04 05 00 04 07 System Slot Information Designation: Thunderbolt Slot 4 Type: 32-bit PCI Current Usage: Available Length: Long ID: 5 Characteristics: 3.3 V is provided PME signal is supported Hot-plug devices are supported SMBus signal is supported Handle 0x001F, DMI type 10, 6 bytes 0000: 0a 06 1f 00 83 01 On Board Device Information Type: Video Status: Enabled Description: nVidia Video Adapter Handle 0x0020, DMI type 10, 6 bytes 0000: 0a 06 20 00 87 01 On Board Device Information Type: Sound Status: Enabled Description: Azalia Audio Codec Handle 0x0021, DMI type 10, 6 bytes 0000: 0a 06 21 00 81 01 On Board Device Information Type: Other Status: Enabled Description: SATA Handle 0x0022, DMI type 11, 5 bytes 0000: 0b 05 22 00 03 OEM Strings String 1: Apple ROM Version. BIOS ID: MBP112. Built by: root@s String 2: aumon. Date: Thu Oct 3 11:43:05 PDT 2013. Revision: String 3: 138.0.0~1 (B&I). Buildcave ID: 1487. ROM Version: 0138_B Handle 0x0023, DMI type 12, 5 bytes 0000: 0c 05 23 00 00 System Configuration Options Handle 0x0024, DMI type 13, 22 bytes 0000: 0d 16 24 00 01 00 00 00 00 00 00 00 00 00 00 00 0010: 00 00 00 00 00 00 BIOS Language Information Installable Languages: 1 <BAD INDEX> Currently Installed Language: Not Specified Handle 0x0025, DMI type 32, 20 bytes 0000: 20 14 25 00 00 00 00 00 00 00 00 00 00 00 00 00 0010: 00 00 00 00 System Boot Information Status: No errors detected Handle 0x0026, DMI type 131, 6 bytes 0000: 83 06 26 00 05 07 Apple specific Processor Type cpu=0705 Handle 0x0027, DMI type 128, 88 bytes 0000: 80 58 27 00 04 00 00 00 37 f5 03 e0 37 ff 03 e0 0010: 02 00 00 03 00 00 00 00 00 00 99 ff ff ff b2 ff 0020: 00 00 b3 ff ff ff b5 ff 00 00 b6 ff ff ff dd ff 0030: 00 00 e1 ff ff ff e3 ff 00 00 00 00 00 00 00 00 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0050: 00 00 00 00 00 00 00 00 Apple specific FirmwareVolume FirmwareFeatures: e003f537 FirmwareFeaturesMask: e003ff37 Region Type:02 Start:ff990000 End:ffb2ffff Region Type:00 Start:ffb30000 End:ffb5ffff Region Type:00 Start:ffb60000 End:ffddffff Region Type:03 Start:ffe10000 End:ffe3ffff Handle 0x0028, DMI type 133, 12 bytes 0000: 85 0c 28 00 02 00 00 00 00 00 00 00 OEM-specific Type Header and Data: 85 0C 28 00 02 00 00 00 00 00 00 00 Handle 0x0029, DMI type 221, 26 bytes 0000: dd 1a 29 00 03 01 00 01 06 01 00 00 02 00 00 00 0010: 00 0f 00 03 00 01 03 00 01 00 OEM-specific Type Header and Data: DD 1A 29 00 03 01 00 01 06 01 00 00 02 00 00 00 00 0F 00 03 00 01 03 00 01 00 Strings: Reference Code - CPU uCode Version TXT ACM version Invalid entry length (0). DMI table is broken! Stop.
  10. Ok... I'll try it again... I already tried modifying a bunch of things 'til now... But who knows, I'll give it a shot. If it helps, I can post a SMBios dump from my real MacBook Pro.
  11. I have 7.0.3 on both my iPad mini and iPhone 5. I have a valid credit card bound tu my account. I have (I think) all the necessary values into NVRam and SMBios (MLB, REAL Mac Serial, Custom UUID...) Indeed my iMessage, at some point, has been able to re-connect although I couldn't for at least 3-4 weeks (before having installed iOS 7.0.3, and before having installed Mavericks...) Then I installed Mavericks over my 10.8.5 installation (to keep everything) and BOOM, no more iMessage with the BLOODY "Call Apple Support" error message AGAIN... I thought maybe it was because Apple was using now more values to check if the device is allowed to use iMessage service, but it seems that's not the case, or at least, not for everyone...? I mean, why the heck can someone else log into Message with his AppleID on MY build while I CANNOT? (i.e. my wife can, and it works...) And, of course, I can log into iMessage on my MacBook Pro/Air... So, definitely, there IS something missing with SMBios injector... Just my two cents...
  12. And how the hell can we get rid of that damn error? Isn't there any way?
  13. Hi guys BTW, does the new 2267 Beta 2 allow to bypass the "Call Apple Support" error message in iMessage login? Thanks
  14. FileNVRAM 1.1.3 Released

    It seems I'm actually a bit wrong in what I'm saying. My reasoning is invalid. Actually problem lies in boot loader, so problem lies in Chameleon not in FileNVRam.dylib. What's happening here, is that Chameleon CAN read/write NVRam correctly, BUT fails at populating SMBios (real SMBios Used by MacOS, not SMBios.plist which is read by Chameleon to populate real SMBios fields), which causes the updates via App Store AND iMessge connection error to arise. When I say "fail", it doesn't fail, it just does not write ALL necessary fields to SMBios to be seamlessly used by AppStore updates and iMessage. That's what I understood from the Chameleon Topic, and what they're saying about 2267 Beta. And what also points to that direction, is that Clover does NOT have all the trouble to get your updates properly done and your iMessage to work... But I just don't like Clover, and would much rather stay on Chameleon ^^ So I'll wait ^^ What I don't understand, is WHY THE HECK can others login into iMessage with my build, and I don't... There MUST also be some kind of server side validation, which could have been reinforced for some users reaching some iMessage connection attempts number... Don't really know, but how could that be only client sided? What I mean by "reinforced validation", is that Apple would consider reading others(more) SMBios fields for specific users, and when they don't match a real Mac, the connection is refused. Just a theory though, nothing rock solid here... Anyway, let's just wait for the new Chameleon rev! ^^
  15. Dual Boot Bluetooth Pairing Solved

    So, to answer to myself Now I'm damn sure it's a select mode issue only I deleted the keyboard in OS X, then re-added it. I need to explain a little further why I did this. Basically, when you pair your Keyboard in Windows, and install the device with HID Driver, and you get back to OS X, I noticed my link keys in /private/var/root/Library/Preferences/blued.plist had become 00000000 00000000 00000000 000000000 I think it does mean that you're paired in HID only mode allowing less secure connection between BT device and BT Dongle. So, when you delete the keyboard in OS X then re-add it, the connection is then done in HCI mode (because OS X have the right DRIVERS for the Keyboard), and set up in a secure way (you do that by typing a passcode on the keyboard) Then, again, to ensure BT Dongle memory erasing, I unplugged it (while in OS X), then re-plugged it, checked my devices were pairing all right with it, and finally rebooted. And guess what? I have my HID Proxy mode back I think Windows has set BT Dongle in HCI Mode only because of the lack of drivers for the keyboard (or at least its inability to pair in a secure way in HCI), so as long as your BT Dongle is powered, you can't get your HID Proxy Mode back... That being said, this is not enough, you MUST have paired your keyboard at least once in HCI mode with a valid link key, which I think is stored by the BT Dongle (that could be why HID Proxy Mode works only AFTER you have paired your keyboard at least ONCE) So that is why I also deleted the keyboard in OS X, and then re-added it, to establish a secure connection and make the BT Dongle store the damn Link Key Now, what I need to ensure, is that it won't happen again! So, what I can try, is first uncheck "HID Driver" for keyboard bluetooth device in Windows and try to pair it in HCI mode. If so, I then will have the opportunity to enter the OS X converted link key into Windows Register. If not, I have no clue what to try next ^^ PS: I hope I'm clear enough in my explanations
×