Jump to content

Search the Community: Showing results for tags 'iCloud'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 27 results

  1. baloobb

    problema accesso iMessage iCloud

    Ciao a tutti dopo aver fatto partire l 'installazione di mavericks ho riscontrato subito un problema al primo riavvio schermo nero e sul monitore appariva nessun segnale; reinstallo tutto da capo installo chimera2,2 come bootloader e nella cartella extra si metto il file orgchamaleonboot.plist che avevo modificato in precedenza sulla chiave usb per far partire l istallazione ho aggiunto nella stringa del kernel flags questo codice <key>Kernel Flags</key> <string>darkwake=0 PCIRootUID=0</string> fin qui tutto funziona il mio hack si spente e accende senza problema anche se ad ogni avvio devo cliccare invio al momento del boot, non so bene il perché! ora si presenta un altro problema l'accesso ad iCloud App Store e iMessage ho provato sia a usare champlist , a modificare file sbios.list vedendo se concedevano numero di serie e tipo di mac, ed ho provato anche cancellando la scheda di rete e installare un altro file ma niente! Qualcuno ha delle indicazioni , credo di avere qualche casino all'interno della cartella extra in quanto una volta installato chimera mi compariva solo la cartella modules tutto il resto dei file li ho inseriti io prendendoli dall'usb usata per l installazione. scheda madre : Asus p5qd turbo grazie dell'aiuto!
  2. Hello All, I've reached a dead end getting my file server up and running. I've installed 10.8.1, and can boot into the OS no problem using a patched kernel from here, as well as FakeSMC.kext, NullCPUPowerManagement.kext, and lnx2mac's RTL81XXX driver. HOWEVER, I try to install MacMan's Jmicron SATA and ATA drivers, and they do not load! These are listed as working with 10.8, so I'm confused. I have also installed ApplePCIIDE.kext, IOAHCIBlockStorageInjector.kext, and tried booting with PCIROOT=1. I have a Mac Mini 3,1 system definition and serial from Chameleon Wizard. I think I also have an IOATAFamily that's been patched in there too, but maybe not... Currently, the IDE controller is registered as connected to the PCI bus, but the kext is not loaded. However, MacMan's kext should be the right one, this is the "GSATA" Gigabyte chip, JmicronXXX363. What can I do to get the kexts to load? Should I make a DSDT for this system (even though it doesn't seem to need it)? Would a different system definition help? Please help! I am soooo close to getting this system up! Thanks! PS: I can't get iCloud to work, either. It has a "communication error"...
  3. Hello Everyone, Here's My Story. I am Using Hackintosh Sine Leopard It worked Flawless till Mavericks. I installed Yosemite Zone Niresh Distro Yesterday. Sine then I am trying to figure out iCloud Fix. Here is what I tried till. Reinstalled OS like 20 times. EFIstudio Method. (This method is to make Ethernet as en0 I already got en0 in System Config.) IMessage Fix V2 (Nireh Hack). Changed SMBIOS to everything. But non of them worked. Details :- Sys Config :- Model Name: iMac Model Identifier: iMac11,1 Processor Name: Intel Core 2 Duo Processor Speed: 1.2 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 2 MB Memory: 2 GB Bus Speed: 800 MHz Boot ROM Version: Niresh12495.com SMC Version (system): 1.30f3 Serial Number (system): W8053TYI5RU Hardware UUID: D5194B8D-670A-583D-AE52-1874D81675E0 ALX Ethernet Driver: Name: Qualcomm Atheros AR8131 Gigabit Ethernet Type: Ethernet Controller Bus: PCI Vendor ID: 0x1969 Device ID: 0x1063 Subsystem Vendor ID: 0x1458 Subsystem ID: 0xe000 Revision ID: 0x00c0 Link Width: x1 BSD name: en0 Kext name: ALXEthernet.kext Location: /System/Library/Extensions/ALXEthernet.kext Version: 1.0.2 NetworkPreferences.plist <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Interfaces</key> <array> <dict> <key>Active</key> <true/> <key>BSD Name</key> <string>en0</string> <key>IOBuiltin</key> <true/> <key>IOInterfaceNamePrefix</key> <string>en</string> <key>IOInterfaceType</key> <integer>6</integer> <key>IOInterfaceUnit</key> <integer>0</integer> <key>IOMACAddress</key> <data> HG9lkk7/ </data> <key>IOPathMatch</key> <string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEX1@1C,1/IOPP/ethernet@0/ALXEthernet/en0</string> <key>SCNetworkInterfaceInfo</key> <dict> <key>UserDefinedName</key> <string>Ethernet</string> </dict> <key>SCNetworkInterfaceType</key> <string>Ethernet</string> </dict> </array> <key>Model</key> <string>iMac11,1</string> </dict> </plist> org.chameleon.Boot <dict> <key>CSTUsingSystemIO</key> <string>y</string> <key>DropSSDT</key> <string>y</string> <key>EnableC2State</key> <string>y</string> <key>EnableC3State</key> <string>y</string> <key>EnableC4State</key> <string>y</string> <key>EthernetBuiltIn</key> <string>Yes</string> <key>GenerateCStates</key> <string>y</string> <key>GeneratePStates</key> <string>y</string> <key>Graphics Mode</key> <string>1024x768x32</string> <key>GraphicsEnabler</key> <string>y</string> <key>Kernel Flags</key> <string>debug=8 ahcidisk=1 dart=0</string> </dict> </plist> smbios.plist <dict> <key>SMbiosversion</key> <string>Niresh12495.com</string> <key>SMboardproduct</key> <string>Mac-F2268DAE</string> <key>SMfamily</key> <string>iMac</string> <key>SMproductname</key> <string>iMac11,1</string> <key>SMserial</key> <string>W8053TYI5RU</string> </dict> </plist> PLEASE HELP ME THANK YOU.
  4. iCloud via Safari works. iCloud via Internet Accounts will not sign in. Console: error=Error Domain=AOSErrorDomain Code=1000 "The operation couldn’t be completed. (AOSErrorDomain error 1000.)" UserInfo=0x7fa1ebc19170 {HttpStatusCode=500, DialogInfo={ "AlternateButtonLabel.skipped" = ""; "AlternateButtonLink.skipped" = ""; Body = "Try signing in again."; DefaultButtonLabel = OK; "DefaultButtonLink.skipped" = ""; DialogType = GenericDialog; ErrorID = "GENERIC_SERVER_ERROR"; Header = "Unable to sign in because of a problem communicating with iCloud."; "HelpLink.skipped" = ""; description = "Generic server error when setup is down"; localizedError = "GENERIC_SERVER_ERROR"; protocolVersion = 2; }}, httpStatusCode=500, responseHeaders= { "Cache-Control" = "no-cache, no-store, private"; "Content-Encoding" = gzip; "Content-Length" = 434; "Content-Type" = "application/xml; charset=UTF-8"; Date = "Fri, 15 Nov 2013 16:41:57 GMT"; "X-Apple-Request-UUID" = "146ef630-3f70-4756-8f2a-6d7fe7eb7bd3"; "X-Responding-Instance" = "setupservice:10600401:st11p06me-setupsvc004:8001:1U35:114660"; }, responseBody= <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>protocolVersion</key> <string>2</string> <key>DefaultButtonLabel</key> <string>OK</string> <key>Body</key> <string>Try signing in again.</string> <key>ErrorID</key> <string>GENERIC_SERVER_ERROR</string> <key>DialogType</key> <string>GenericDialog</string> <key>AlternateButtonLink.skipped</key> <string></string> <key>AlternateButtonLabel.skipped</key> <string></string> <key>localizedError</key> <string>GENERIC_SERVER_ERROR</string> <key>DefaultButtonLink.skipped</key> <string></string> <key>Header</key> <string>Unable to sign in because of a problem communicating with iCloud.</string> <key>description</key> <string>Generic server error when setup is down</string> <key>HelpLink.skipped</key> <string></string> </dict> </plist>
  5. Hi Everybody, This is my first post so hope its ok, anyway. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- WillWills' Hackintosh Guide ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- What You Need: USB stick A computer that you are able to use, preferably with OS X installed Internet connection How to fix Hackintosh locked via iCloud website Step 1. Backup Data (Optional) So, first we need to backup our data, to do this, we need access to our system that we are locked out of, this is a temporary fix and may or may not work for you but here is how you do it: Boot Into Your Bootloader Boot Using The Boot Flags -s and -v When You Get To Bash, type "nvram -c" without quotation marks Now Type "exit" Without Quotation Marks And You Should Be Able To Access Your Old Files Step 2. The Fix This is the easy part, all you need to do is download the latest version of your BIOS and flash it (make sure it erases and resets everything) now you will either have access to your hard drive or you will have to do a clean install of OS X ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Thank You For Reading ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  6. Ciao a tutti, Chiedo un consiglio per un curioso problema che mi si presenta su un sistema come da titolo. Ho usato MyHack 3.x per l'installazione e tutto va alla perfezione. Uso i driver Lnx4Mac per Lan Realteck e Voodoo per l'audio Via. Arrivo all'aggiornamento ML 10.8.4 regolare e rete, audio e grafica vanno perfettamente. Ora vorrei collegare il mio account iCloud. Uso il sistema qui descritto. Funziona sempre, ma questa volta, al primo riavvio prima di re inserire la rete nuova, la grafica si spegne. Parte Cameleon, il sistema si avvia ma non si accende la grafica. Se non tocco org.chameleon.Boot.plist tutto regolare, appena lo modifico per aggiungere i parametri della scheda di rete come da tutorial, il sistema si avvia ma la grafica non si avvia. Ho provato tutte le combinazioni di -x, -f, -F PCIRoot o GraphicsEnable=Yes No Maybe che di solito funzionano con le Nvidia ma nulla. Appena ripristino il sistema tutto riparte. Come posso accedere per eventualmente ripristinare una versione precedente dei file modificati? Grazie
  7. Hello fellow hackintoshers. I'm having a problem with both FaceTime and iCloud not letting me log in. I'm on 10.7.2 and I CAN log into the app store and iTunes but FaceTime give the "Server encountered and error during registration" message and iCloud give the "This is an Apple ID but not an iCloud ID" message. It's a dell laptop that is 100% functional except for these problems and I've tried every possible solutions that has been posted already but nothing worked. What I've Tried... My ethernet is built-in. I've checked my hosts file. I've changed my smbios. I've tried changing the date & time preferences to automatically configure. I've tried different versions of chameleon and chimera including 755. I've tried deleting my network preferences.plist. I've tried ethernet builtin=yes with efi string. I've tried editing my dsdt. My Ethernet Card Realtek RTL8168B: Name: ethernet Type: Ethernet Controller Bus: PCI Slot: Built-in Vendor ID: 0x10ec Device ID: 0x8168 Subsystem Vendor ID: 0x1028 Subsystem ID: 0x0275 Revision ID: 0x0002 Link Width: x1 BSD name: en0 Kext name: RealtekRTL81xx.kext Location: /System/Library/Extensions/RealtekRTL81xx.kext Version: 0.0.90 I must be missing something and I'm hoping that someone else has had this problem and found a working solution. Please help me if you can. Thanks.
  8. Hey guys, This is my first topic on this forum, but I've been familiar with the mackintosh community for 3 years, and am not afraid to get my hands dirty. With that said, to the problem. I am having trouble signing into iMessage. And believe me I don't like posting stupid, duplicate topics without a reason to do so. I've read every damn topic on the net I could find, tried it, and all of those failed. It always tells me, "Your Apple ID "[My Mail ID]" can't be used to set up iMessage at this time". But, my father bought an iPhone 5s a couple of weeks ago, and I used it for a week. My iMessage was signed in on the phone. And around that time, I upgraded to Mavericks. I gave my father the iPhone back 3 days ago, and that's when it started giving me this stupid message. So, after browsing a bit, I heard about NVRam and Clover, and saw that my PC didn't have a UUID. So, I got the necessary tools and applied a UUID to my machine. Yet it didn't work. Also tried a full restore, booting from Chameleon, Chimera, and Clover. Nothing works. The only thing that works is signing into my father's iPhone. And again, logging out of that gives me the message. Yes, I've checked for nvram.[uuid].plist, and everything but the IOPower variables are valid. MLB and ROM are in place. Find MyMac works. I've also created a recovery partition. I would also have tried gdb-ing iMessage, but I'm terrible at that. I, currently, am on 10.9.1(It didn't work on 10.9 also). Also, I didn't use Messages when I used 10.8. Any suggestions would be warmly welcome.
  9. I have my system completely setup with Clover 3259, Yosemite 10.10.5 and completed the entirety of the iMessage guide. My injected ROM values are correct and do not change. My hardware specs: • Asus Maximus VI Gene • Intel 4670K, not overclocked • Asus GTX 670 2GB • Apple BCM94360CD iCloud works no problem and all my data syncs to my iPhone 6. Perfect! iMessage allows me to sign in and it recognizes my phone number. However, I'm not able to send messages and all contacts appear in red. If I turn on Text Message Forwarding, it's still not perfect. Contacts only appear in green and any message people send to me do not receive on my computer, just my iPhone. Handoff works fine if I transfer from my iPhone to my computer, but not the other way around. For instance, if I start an email on my computer, the icons for Handoff don't even show up on my iPhone. I've verified that all my devices appear under my iCloud/AppleID account on the website. There are no duplicate devices listed anywhere. The WiFi/BT card appears to work perfectly, never dropping signal to the internet. Bluetooth connectivity works perfectly with my PlayStation 4 controller. Things I've already tried to fix this behaviour: • Removing the plist and cache files from my ~/Library folders • Completely signing out and back in to my iCloud and iMessage accounts on my iPhone and computer • Turning Handoff, Text Message Forwarding, and Bluetooth Sharing off and on again I'm beginning to think that this is an iMessage server authentication issue than anything else, strictly affecting my computer. But I'd rather not call Apple about it until I've exhausted my other options.
  10. So I'm running Yosemite on an HP Sandy Bridge laptop with MacBook 8,2 system definition, and I just picked up the same year(2011) Sandy Bridge MacBook Pro 8,2 that is ridiculously close to the end of it's life. I don't plan on using iMessage or FaceTime if I even use the MBP at all (it's screen is cracked, missing keys, aluminum falling apart, it's had a rough life). So I've taken the SMBIOS variables using iMessage_debug V2, but I'm not sure on what the best way to apply these is and I've seen a lot of conflicting information in the many forums I've checked out. I've seen people imply that MLB and ROM are the only really important variables here, and that if you're taking these values from a real mac that these ones are the only ones you should take while separately generating a serial number, smUUID etc from Clover Configurator or uuidgen. I've also seen people recommend to simply make sure the output of iMessage_debug exactly replicates your hack and real Mac (in the case where the system definition matches the Mac that you're getting the variables from). I've seen people say that you shouldn't take any variables, ever, at all, even from a retired Mac that you already own. A good chunk of the material I've found on this subject is over 5 years old, which is why I think I'm finding a lot of conflicting information. In addition to that most guides etc are written from the standpoint of someone that does not have another mac to take the variables from, and if they do mention scenarios like this it's so briefly touched that I'm still left unsure. Does anyone more experienced have any personal recommendations for someone specifically in my case, where I own a Mac that matches the system definition I'm using for my hack?
  11. Good morning everyone, I been trying to get my iCloud to work with little success. I tried all the fixes out there: EFI studio, Ethernet Built in, NVRAM module, etc. I also tried installing mountain lion but the same problem persists. When I do try to login to iCloud I get "Unable to sign in because of a problem communicating with iCloud" message. I am able to login into the APP STORE (I downloaded apps) and iTunes without any issues. When I do attempt to login into iMessage I input my credentials and it actually goes through, but two seconds after it logs me in iMessage goes "inactive" requiring me to input my password again. When I do input it again, it gives me trouble activating iMessage. I am currently running 10.9 with just Audio, R9 270 Kext, and RealtekRTL81xx.kext version 0.0.90. I made sure to update Chameleon and I can confirm my Ethernet is "en0" in system info I am using Chameleon pre made SMBIOS MacPro 3,1 and I randomized the Week of Manufacture and Unique Number Besides the fact iCloud/iMessage is not working I have a fully functional system. If I missed anything please do no hesitate to ask.
  12. friscos

    Limite account raggiunto

    iCloud Limite account raggiunto Ma che significa? io ho fatto quell'acconto mesi fa e non l'ho mai usato. E poi ammazza che pezzenti non si può neanche scaricare dei programmini idioti gratuiti da Apple store che vogliono conoscere il N° della tua carta, roba da matti
  13. So I have a working apple ID for my appstore account and I was running into the issue other people reported about this account is valid, but not an iCloud account. I made some changes without intending to fix this (using DSDT now, updated my voodooHDA and removed appleHDA) and when I try to log into iCloud it says this device is no longer eligible to create a new apple ID. Is this related to my serial number, or is it something that is local to my machine? If it is the serial number, how do I go about generating a new one? Any help would be greatly appreciated! Dave
  14. Hello, I've a complete Lion 10.7.3 with iCloud, AppStore and Messages.4 Now I'm trying the installation and the configuration of Mountain Lion. It works perfectly but I'm having serious problem with the Ethernet. I've copied Extra folder by Lion to Mountain Lion, AttansicL1Ethernet in Extra folder and in S/L/E. Wireless works but Ethernet isn't recognized..and AppStore don't works What I've to do? If I replace IO80211Family.kext and IONetworkFamily.kext with version for 10.7.3 also WI-FI seems not installed. My motherboard is P5Q-E.. Can You help me? Sorry for my bad English
  15. I've installed Yosemite with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url], actually i'm using Chameleon. The problem is the next: I can't sign in with my iCloud account to sync my Notes, Messages, Calendar and things like that. I already tested a LOT of proceeds written on the internet, but no one worked. Note: I'm using a wireless adapter because here in my room do not have ethernet cable, and also hackintosh don't detect my ethernet card. I have FileNVRAM on the modules folder. org.chameleon.Boot <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>EthernetBuiltIn</key> <string>Yes</string> <key>IGPEnabler</key> <string>Yes</string> <key>Kernel Flags</key> <string>kext-dev-mode=1</string> <key>Legacy Logo</key> <string>Yes</string> <key>Timeout</key> <string>2</string> <key>UseKernelCache</key> <string>Yes</string> <key>GraphicsEnabler</key> <string>Yes</string> <key>DropSSDT</key> <string>Yes</string> <key>SMboardserial</key> <string>CK148614DB6F940D2</string> <key>SMsystemuuid</key> <string>a8dd17a0-cf10-4323-9841-29a9f08c1d49</string> <key>SMchassisserial</key> <string>CK129U13DB67</string> <key>SMserial</key> <string>CK129U13DB67</string> </dict> </plist> NetworkInterfaces <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Interfaces</key> <array> <dict> <key>Active</key> <true/> <key>BSD Name</key> <string>en0</string> <key>IOBuiltin</key> <false/> <key>IOInterfaceNamePrefix</key> <string>en</string> <key>IOInterfaceType</key> <integer>6</integer> <key>IOInterfaceUnit</key> <integer>0</integer> <key>IOMACAddress</key> <data> 6E4GG+gE </data> <key>IOPathMatch</key> <string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/EUSB@1D,7/AppleUSBEHCI/802.11n WLAN Adapter@fd800000/IOUSBInterface@0/RTL8192CU/en0</string> <key>SCNetworkInterfaceInfo</key> <dict> <key>USB Product Name</key> <string>802.11n WLAN Adapter</string> <key>UserDefinedName</key> <string>802.11n WLAN Adapter</string> <key>idProduct</key> <integer>33142</integer> <key>idVendor</key> <integer>3034</integer> </dict> <key>SCNetworkInterfaceType</key> <string>Ethernet</string> </dict> <dict> <key>Active</key> <true/> <key>BSD Name</key> <string>en1</string> <key>IOBuiltin</key> <false/> <key>IOInterfaceNamePrefix</key> <string>en</string> <key>IOInterfaceType</key> <integer>6</integer> <key>IOInterfaceUnit</key> <integer>1</integer> <key>IOMACAddress</key> <data> ABWDB81d </data> <key>IOPathMatch</key> <string>IOService:/IOResources/IOUserEthernetResource/IOUserEthernetResourceUserClient/IOUserEthernetController/en1</string> <key>SCNetworkInterfaceInfo</key> <dict> <key>UserDefinedName</key> <string>Bluetooth PAN</string> </dict> <key>SCNetworkInterfaceType</key> <string>Ethernet</string> </dict> </array> <key>Model</key> <string>iMac14,2</string> </dict> </plist>
  16. Joshie100


    Version 3.2


    A nice app I found that can be used to generate fake serial numbers in smbios required to get iCloud working. - App not made by me, their website is down so I am uploading it here.
  17. Olá, tenho hackintosh ha um ano, mas nunca enfrentei um problema tão sem solução quanto este (até agora). Desde que instalei o OSX 10.8 (Mountain Lion) há duas semanas, não consigo fazer o iCloud funcionar. Sempre aparece a mensagem "Este ID Apple é válido, mas não é uma conta iCloud". Antes do Mountain Lion eu utilizava o Lion 10.7.2, e o meu iCloud funcionava perfeitamente. Também testei todas as versões Developer Preview do Mountain Lion, e em todas elas o iCloud funcionou normalmente. Também tenho um iPod touch, e garanto que minha conta funciona normalmente. Já instalei a última versão do Chameleon, editei o org.chameleon.plist, inseri EthernetBuiltIn=Yes, gerei o serial do SMBios.plist várias e várias vezes, refiz minha conexão com a internet (não uso wifi, uso Ethernet mesmo, e ele já está como En0), cheguei até a reinstalar o sistema operacional, baixando de outra fonte... e nada de resolver o problema. Para completar, resolvi testar se o problema era apenas com o meu ID Apple, então inseri um e-mail fictício, como "joao@maria.ipod", e ele repetiu a frase. "Este ID Apple é válido, mas não é uma conta iCloud". Enfim, se alguém já passou por isso e conseguiu resolver o problema, por favor, me ajude. Grato. PS: Também já testei o Chimera 1.11.0. Sem êxito.
  18. rgray99c

    iCloud problem :/

    Hey guys, ive finally got a working instal on my pc. Im now down to literally my last problem, which is the whole iCloud and facetime problem. Ive tried using champlist to change my smbios to the closest match, but i think the problem is that my cpu (i3 - 530) was never used in any macs, and the closest match on the drop down list was an imac with an i3 540 cpu. Is this the problem, if sao how do i fix it, or is there something else i havent done. The install method was iatkos l2 dvd. cheers for the help guys. also as a side note i cant sign into the app store as my "device or computer" cannot be verified :/
  19. Dontview

    iCloud Issue

    Hello, finally I managed to setup my AMD Mavericks. I am using an USB Wifi Adapter (en1) for internet connection. Also I am able to login into the AppStore and iMessage. Just iCloud has some "communication Issue". I tried to delete: Library/Preferences/SystemConfiguration COM.APPLE.NETWORK.IDENTIFICATION.PLIST Library/Preferences/SystemConfiguration TNETWORKINTERFACE.PLIST My onboard Ethernet was recognized as eth0. I installed some .kext and used EthernetBuildIn Yes. Although I don't use a cable connection. Of course I used Chameleon Wizard to create a SMBios. I would really appreciate having iCloud for sharing passwords over my Systems... Any suggestions?
  20. **FOR THOSE WHO'VE TRIED EVERYTHING TO LOGIN TO ICLOUD/MESSAGES AND CAN'T. USE THIS KEXT** http://cl.ly/3T2m2U2n332O ^ PlatformUUID.kext -------------------------------------- I tried every solution and combination to fix the issue. I could log into the Mac App Store and iTunes Store, however I couldn't login to iCloud or Messages account. I kept getting a message saying "This is an Apple ID but not a valid iCloud account." For some reason my Hardware UUID was causing a conflict and using the built-in UUID changer in Chameleon's boot.plist wasn't able to change my UUID either. This kext will force the UUID to change. Be sure to install it to S/L/E and not E/E. BEFORE: AFTER: Godspeed. PS - Thanks to Superhai for making this kext! -stell
  21. Good morning everyone, I been trying to get my iCloud to work with little success. I tried all the fixes out there: EFI studio, Ethernet Built in, NVRAM module, etc. I also tried installing mountain lion but the same problem persists. When I do try to login to iCloud I get "Unable to sign in because of a problem communicating with iCloud" message. I am able to login into the APP STORE (I downloaded apps) and iTunes without any issues. When I do attempt to login into iMessage I input my credentials and it actually goes through, but two seconds after it logs me in iMessage goes "inactive" requiring me to input my password again. When I do input it again, it gives me trouble activating iMessage. I am currently running 10.9 with just Audio, R9 270 Kext, and RealtekRTL81xx.kext version 0.0.90. I made sure to update Chameleon and I can confirm my Ethernet is "en0" in system info I am using Chameleon pre made SMBIOS MacPro 3,1 and I randomized the Week of Manufacture and Unique Number Besides the fact iCloud/iMessage is not working I have a fully functional system. If I missed anything please do no hesitate to ask.
  22. Fixing Login Errors For Apps That Connect To Apple's Servers These steps should fix 98% of login errors, but some specific exceptions still exist and are omitted to avoid unnecessary confusion. Since this is a FAQ and not a full manual on all things Ethernet, it's not feasible to detail every method mentioned here, but hopefully at least it will let you know where to go next. So always start here!: To sign into any of the Apple services/apps that require authentication through Apple run servers, there are a few conditions that must be met when first logging in. For apps such as iCloud, once logged in the first time you will stay logged in even after reboots and configuration changes until manually logged out, at which point to log back in the same conditions will again apply. 1) Must have a working ethernet adapter that can at least show up as a possible network connection. It must also work, but you might be able to get away with mostly working if your lucky. You'll need a kext that supports your NIC to proceed. 2) It must also show as "Built In". Three possible ways of doing this which are all different ways of achieving the same result. Easy way, add following to Chameleon's org.chameleon.Boot.plist in /Extra folder: <key>EthernetBuiltIn</key> <string>Yes</string> Medium way, add EFI string to Chameleon's org.chameleon.Boot.plist in /Extra folder using tool such as "EFI Studio" Hard way, edit DSDT to have NIC device, i.e. LAN0 show as internal 3) It needs to be listed as en0. i.e. The first, or primary, network device recognized by OSX Issue here will usually be that your wifi got enabled first and thus became en0, making your ethernet en1. To correct the issue: First if your wifi device or whatever is currently listed as en0 can be removed/unplugged from your PC by removing 3 screws or less, and you own a screwdriver, remove/unplug it. Next go to System Preferences > Network (as seen above in #1) and click the minus button to remove all the listed network devices, then reboot. Upon reboot return to System Preferences > Network and hit the plus button, add only your ethernet, open System Information (as pictured directly above) and verify Ethernet is now en0, if it is you can add your other devices now too. If ethernet is still showing as en1, you should then repeat the above steps, but this time just prior to reboot navigate to /Library/Preferences/SystemConfiguration/ and delete Networkinterfaces.plist and reboot. Extreeme cases only: If failure is still an option, and overkill seems necessary, it's possible to manually edit this plist. Again repeat initial steps, then copy plist to your desktop so it will be writable and open it with a text editor, cut an paste your ethernet so it appears first in the list, change every occurrence in it's section of en1 to en0, and vice versa for your prior en0 device, changing all it's en0 occurrences' to en1. Also verify here that ethernet shows: <key>IOBuiltin</key> <true/> and not <key>IOBuiltin</key> <false/> Once your satisfied with your edits (in simpler terms, your basically just swapping the two interfaces in the plist), launch Terminal from Applications/Utilities, enable root user by typing sudo -s and hitting enter, then entering your password when requested. Next enter the following, hitting return after each line: cp -R ~/Desktop/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/ chown root:wheel /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist chmod 644 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist reboot 4) You need to have a SMBIOS which includes a valid serial number for the Mac model listed. For this, just use Chameleon Wizard to generate one for you and save to /Extra folder. WHEN ALL ELSE FAILS, BUT IS ALSO RIGHT, AKA-LAST RESORT: If you've met all the above requirements and ethernet works perfectly to browse the webs, but still can't log into these services, although it shouldn't need to be done manually, you may need to.... First Open IORegistryExplorer (found in Xcode tools) Copy to Text Edit then get your ethernet MAC address Add results to org.chameleon.Boot.plist and after reboot you should see something like this And hopefully that will be it. Again, this won't cover every last possibility, but should be more than a good start.
  23. THE BEGINNING As you folks can see in my signature, i'm an AMD hackintosher. That means that, some time in the past, i have the clever idea to invest some money on a cheap piece of hardware that nonetheless gave me lots of computational happiness, with (most of the times) little or no less performance compared to my friends' much pricier intel rigs, especially in day-to-day tasks. That means, unfortunately, that my times of hackintoshing have been giving me equal doses of fun and frustration, and all fun comes exclusively from OSX. Everyone who frequently reads OSX86 forums know by now that AMD machines are at the bottom of the chain food in the mackintosh world. OSX running on AMD could be already a dead subject, if there wasn't very skilled people working very hard (Q: Wanna know what "hard" means? Write an on-the-fly sse3 emulator!) for it to be possible. However, even with the talent and industriousness of those pro-AMD good people, well... sometimes the road comes to a dead end and that was kind of the case: the seventh iteration of OSX, Lion, added a new CPU instruction to the recipe, the ssse3 (believe, my friends, it is not just sse3 with one more "s"). This, by itself, put every AMD CPU but the newest ones, called Bulldozers or FX-Series, out of the party. Or that could have been the case, if we AMD user weren't so stubborn. Slowly, heterodox solutions popped here and there to make Lion roar on AMD machines. Better saying, almost like that: running strictly 32-bit, even on the Bulldozer machines, without support to many cool features like iCloud (Oops, i say it!) or even the stock Finder, this Lion err... Meows. So that was the situation. While Intel users lived in the safe and confortable Palaces of Vanilla, we're from AMD side were left behind in the Wild Land of Doing It Ourselves. INTO THE WILD The famed and almost universally accepted theories of Charles Darwin, the Theory of Evolution of The Species and of natural selection proposes that, in the nature, only the fit survive and procreate. No, maybe that's what people usually think that Darwin stated, but anyway: the fact that we AMD hackintoshers have almost no support to make our machines work with the beloved OSX, except for a few good souls and great minds that develops cool things to support our hardware, this fact made us to either give up or read a lot and learn a lot: an authentic process of selection similar to the one that suposedly made the bacteria turn to plants, then to plants, than to, than to. There are people at the Intel side of the mountain that cannot tell the user library from the system one, and lots of them had built their machines using that uni and multi pets. That is neither bias, nor intends to be an insult out of pure envy (but i concede that the envy exists indeed, at least inside me): the AMD users that were lazy, incompatible with computers or just wanted something to work effortlessly so they could work hard on anything else, these now are either using Windows again, changed to Intel or (the more intelligent choice) bought a Mac. Indeed, a couple of months after the first useful AMD kernel for OSX Lion came out, a guy whose nickname is RAWX86 developed a kernel which made possible (for Bulldozer CPUs only, that's it) run Lion flawlessly, with 64-bit app support and all the small things. All the small things except the cloud-related ones. As always with AMD, with success comes frustration. INTERLUDE Besides my AMD desktop computer, i own a small and cheap Asus netbook, as you can also see in my signature. Like AMD, its Intel Atom CPU is not natively compatible with OSX and, even being supported for a while during the early Snow Leopard times, it's not any longer, and cannot run the vanilla kernel. However, Intel is Intel and, when coupled with OSX, the happy ending can sometimes be troublesome to achieve, but is as certain as the success of a new Apple device: the patches work somewhat better, since the CPU supports the same instructions of all modern Intel processors, and has a very closely related architectural design. Therefore, my little Asus can run versions of OSX as new as the last one, Mountain Lion 10.8.1. But not without its measure of woes: it was a real pain to get iCloud, FaceTime and other cloud features to work. Indeed, it ain't easy for anyone that runs a hackintosh and some indispensable steps must be accomplished for these features to be used: 1) You ought have a built-in ethernet working properly. I'm not saying just using the famed Chamaelon boot flag "EthernetBuiltIn=Yes". This, buddy, is not enough: you have to effectively configure your hardware so your LAN card is properly recognized by the OS, with a corrected kext loaded to it and assigned to the network interface assigned to en0. Do your homework! That, alone, solve all App Store and iTunes Store issues, even for AMD hacks. 2) You must get a valid serial number, so the Apple servers think they're talking with a real Mac. Do you really thought the Cupertino Colossus wouldn't have its beautiful paradisiac garden just without any fences? But you can dodge them using a very cool app called Chamaleon Wizard - google is your friend! - to generate a file called smbios with a (hopefully) valid serial number. This, along the first step, should be enough for everyone to have the full array of Apple cloud features. But is not. It was not enough for me and my little Atom CPU (speed-wise, it should be called Animal Traction, but does not matter, i love it, specially because it was very pocket-friendly). It was not enough for my AMD computer also, but let's left it aside for a while. I, frustrated and a little amused by the difficulty (remember that talk of natural selection) resorted to various additional, some of them quite unorthodox, like trying various versions of symbioses and an obscure method i found at a thread in Tonymac's, of getting a supposedly valid UUID (take a look: http://www.famkruith...et/uuid/uuidgen). Not needed to say, nothing worked. THE REAL CAGE OF THE LION Most people that posts in OSX86 forums know meklort, right? Should exchange some words with him: the guy is a genius. He, alone, solved the iCloud issue for almost every Atom OSX computer. At least in Mountain Lion: i don't know if he's done something about it for Lion. Theoretically, it should work. He addressed the problem with a single and very reasonable insight: why apple should give all of the amazing features of OSX out with the open-source XNU kernel? Nah, it could be that way. Something will be missing, precisely that something that, among other things, makes iCloud and related goodies tick. So he came out with his own patched kernel for 10.8: https://dl.dropbox.com/u/863180/kern...ocache.patched (if you have 10.8.1, try this one: mach_kernel_Atom 10.8.1(dev).zip). The patches weren't apllied to the source of the open-source XNU; instead, they were binary patches. And, pure magic, all started to shine: iCloud, FaceTime, iMessages, GameCenter. Pure joy. Of course they wouldn't have worked, the kernels, without following the steps mentioned before. Again, you have to do your homework! Would his method work on AMD machines? Of course, meklort told me: once someone writes correctly the patches for AMD CPUs, they could with all certainty be applied as binary patches and should work. I guess it's not an easy task, tough - i, certainly, don't have the skill to do it, and no one showed up with something like that even until now. But i was not prepared to give up yet! MY WORKAROUND TO GET ICLOUD TO WORK ON MY AMD MACHINE Are you still reading? Good! You're a pure breed AMD hackintosher, not some uni/multipuppy lazy guy (okay, call me envious, and no offense at all to the puppies owners, they're great tools to get the work done). Why did i talk so much about my atom experiences? Because from them, i learned enough to establish a realistic assessment of the facts, which are the following: - On contrary of what most people think, these iCloud, FaceTime etc issues are indeed somewhat kernel related. Recently, i decided to reformat the disk of my netbook, erasing all partitions and letting only OSX installed. The problem was OSX wasn't in the first partition, so i decided to reinstall and restore my system from a time machine back up. I when i finished, i tried to do a call using FaceTime and, surprise!, it didn't let me log in. I forgot to put meklort's kernel back. When i did it, reboot and all went back to normal; - I have to follow closely and carefully the basic steps of getting Apple's web-based services working; kernel tricks wouldn't suffice to achieve success; - The critical moment for iCloud to work is not the log in, is the first log in. Is not without reason that Apple instructs you to set up iCloud, not just "sign up and sign in" like the way of the App Store. In that critical moment, something in your system files are optimized and changed, so Apple can offer you a better and more customized service. At this very moment, your computer is also checked if it's a genuine Apple-branded computer, not some fake thing. The evidence (circumstantial, i confess) is that my netbook is always "signed in" iCloud, even when it's offline (of course, in this case no data is exchanged, but it stays logged in anyway, because it's not really a log in). Once we make through the first set up, i thought, we shouldn't bother anymore with kernels, serials and everything. But how to set up for the very first time, if our patched kernel is refused altogether? That was the way i achieved that, and i can bet that will work for everyone. You'll have to use your friend's Mac/Intel hack/Atom hack with working iCloud, and will need a working network between it and your own computer. I assume you already followed the basic steps for Apple's web services and features: 1) On the Mac/Intel hack/Atom hack, create a new user account; 2) Set up iCloud for this user account; 3) Log both this computer and your computer at the same network; 4) Start the migration assistant (/Applications/ Utilities/ Migration Assistant) in your computer. When prompted to chose which kind of migration, chose "from a Mac"; 5) Since both computers are in the same network, you should see the other computer, select it; 6) Start the migration assistant in the Mac/Intel hack/Atom hack. When prompted to chose which kind of migration, chose "to a Mac"; 7) Select your computer from the Mac/Intel hack/Atom hack; 8) A passcode will appear on your computer; check the Mac/Intel hack/Atom hack, will appear there too. If they match, hit continue; 9) When prompted to chose which files to migrate from the Mac/Intel hack/Atom hack, select under "users" the user you just created to set iCloud, and select "settings"; 10) When it ends, congratulations: you have iCloud working on your AMD hackintosh, like i do. Reboot it, and don't forget to erase the user account you created in your friend's computer. Attention! The method works for iCloud, but not for FaceTime! Apparently, FaceTime does make a live login every time, and every time the kernel is checked. Why am i saying that? First of all, it doesn't work in my AMD. Second, remember when i formatted my Atom netbook and forgot to change the kernel? FaceTime (and Messages also) would not connect. But my iCloud account, previously set up, was working flawlessly. If someone gets a workaround for it, post here.
  24. Difficoltà tecnica: 9/10 (Il terminale è vostro amico) Attivare l’opzione "Trova il mio Mac" Questa guida si occupa di come attivare l’opzione "Trova il mio Mac" presente in iCloud, anche per i nostri cloni Mac. Le metodologie di attivazione basilari di AppStore(Lion e Snow Leopard) e iCloud (Lion), con problematiche quali; account, configurazione di rete, impostazioni di rete e del giusto seriale, non verranno trattate qui. Ogni eventuale domanda relativa a tale argomento non verrà presa in considerazione e i post incriminati verranno cancellati senza nessun preavviso da parte dei moderatori. Le informazioni sulla configurazione e attivazione di iCloud sono perfettamente spiegate in questa guida : [Trucco] come arginare verifica di apple store (snow e Lion) In questa guida verrà trattato come abilitare la funzione "Find My Mac" (In italiano: Trova il mio Mac), tramite la realizzazione e impostazione della partizione di ripristino "Recovery HD" presente nei veri Mac. Iniziamo. Dalla versione 10.7.2 di OS X Lion alla Apple hanno introdotto il servizio iCloud, accessibile dal pannello di controllo. Accediamo ad esso inserendo il nostro AppleID e password. Non tratteremo come attivare iCloud dato che l‘argomento è ampiamente trattato su tutto il forum con soluzioni di ogni genere, Detto questo normalmente sui nostri Hack vi sarete accorti che la funzione "Trova il mio Mac" è disabilitata (riquadro GIALLO). Situazione confermata anche entrati nel "cuore" dell‘applicazione (sempre riquadro GIALLO). Notare la dicitura: Partizione di ripristino richiesta Come si procederà: FASE 1) Creiamo il "contenitore" della partizione di ripristino. FASE 2) Creazione della partizione "Recovery HD". .: FASE 1) Creiamo il "contenitore" della partizione di ripristino :. In questa prima parte “creeremo” il necessario atto a "emulare" lo stesso contenuto richiesto nella partizione speciale "Recovery HD". Abbiamo bisogno dei file contenuti all’interno dell’applicativo di installazione di OS X Lion. Questo può essere o il "Installa Mac OS X Lion.app" oppure il .dmg "OS X Lion 10.7.x.dmg" (La x stà a indicare l’eventuale numero di versione della versione in formato .dmg da voi posseduta). Nel nostro desktop creiamo una nuova cartella chiamata com.apple.recovery.boot Ora apriamo il terminale e digitiamo: defaults write com.apple.Finder AppleShowAllFiles YES;killall Finder Questo attiverà la visualizzazione dei file nascosti. Abbiamo bisogno di copiare determinati file che sono localizzati in posizioni differenti a seconda della "distribuzione" che possedete, con distribuzione mi riferisco o al formato applicativo .app (Che probabilmente avete comprato dall’ AppStore e vi siete ritrovati nella cartella Applicazioni) oppure in formato .dmg (Immagine disco). I file di cui abbiamo bisogno e che devono essere recuperati( o dall’applicativo o dall’immagine disco): .disk_label BaseSystem.dmg boot.efi com.apple.Boot.plist kernelcache PlatformSupport.plist SystemVersion.plist Vediamo come recuperarli. Nel caso voi possediate l’applicativo .app dobbiamo montare il file InstallESD.dmg che si troverà in /Applications/Install\ Mac\ OS\ X\ Lion.app/Contents/SharedSupport/InstallESD.dmg Copiate i seguenti file (ATTENZIONE ALLA POSIZIONE LOGICA) all’interno della cartella com.apple.recovery.boot. /Volumes/Mac OS X Install ESD/.disk_label /Volumes/Mac OS X Install ESD/BaseSystem.dmg /Volumes/Mac OS X Install ESD/boot.efi /Volumes/Mac OS X Install ESD/kernelcache /Volumes/Mac OS X Install ESD/System/Library/CoreServices/PlatformSupport.plist /Volumes/Mac OS X Install ESD/System/Library/CoreServices/SystemVersion.plist Finita l’operazione di copia potete smontare l’immagine Mac OS X Install ESD Nel caso voi possediate l’immagine disco .dmg) dovete semplicemente montare l’immagine...) Copiate i seguenti file (ATTENZIONE ALLA POSIZIONE LOGICA) all’interno della cartella com.apple.recovery.boot. /Volumes/OS X Lion Install Disk/.disk_label /Volumes/OS X Lion Install Disk/BaseSystem.dmg /Volumes/OS X Lion Install Disk/boot.efi /Volumes/OS X Lion Install Disk/kernelcache /Volumes/OS X Lion Install Disk/System/Library/CoreServices/PlatformSupport.plist /Volumes/OS X Lion Install Disk/System/Library/CoreServices/SystemVersion.plist Finita l’operazione di copia potete smontare l’immagine OS X Lion Install Disk Successivamente da terminale digitiamo: defaults write com.apple.Finder AppleShowAllFiles NO;killall Finder Questo ripristinerà la visione normale di file e cartelle. .: FASE 1) COMPLETATA :. .: FASE 2) Creazione della partizione "Recovery HD" :. Apriamo il terminale ed entriamo in super user mode. su - ErmaC:~$ su - Password: ErmaC:~# Visualizziamo tutti i dischi. diskutil list ErmaC:~# diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *128.0 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD 127.7 GB disk0s2 Otteniamo maggiori informazioni sul nostro disco. Nel mio caso disk0s1. Il vostro avrà ovviamente un output diverso. diskutil info /dev/diskXsX ErmaC~:# diskutil info /dev/disk0s2 Device Identifier: disk0s2 Device Node: /dev/disk0s2 Part of Whole: disk0 Device / Media Name: Macintosh HD Volume Name: Macintosh HD Escaped with Unicode: Macintosh%FF%FE%20HD Mounted: Yes Mount Point: / Escaped with Unicode: / File System Personality: Journaled HFS+ Type (Bundle): hfs Name (User Visible): Mac OS Extended (Journaled) Journal: Journal size 16384 KB at offset 0x3ba000 Owners: Enabled Partition Type: Apple_HFS OS Can Be Installed: Yes Media Type: Generic Protocol: SATA SMART Status: Verified Volume UUID: 5C784582-B984-3B4A-85FE-245E9056CD5F Total Size: 127.7 GB (127691702272 Bytes) (exactly 249397856 512-Byte-Blocks) Volume Free Space: 28.2 GB (28211933184 Bytes) (exactly 55101432 512-Byte-Blocks) Device Block Size: 512 Bytes Read-Only Media: No Read-Only Volume: No Ejectable: No Whole: No Internal: Yes Solid State: Yes Ora abbiamo due possibilità per creare una partizione aggiuntiva: La prima sarebbe quella di usare Utility Disco, e partizionare il Disco (Opzione non usata), l’altra è continuare ad utlizzare il terminale ed effettuare le operazioni da esso.(Opzione che verrà esposta). Ridimensioniamo la nostra partizione principale. Il procedimento si basa su estrarre dal quantitativo totale della partizione una quantità di circa 650Mb (Per sicurezza ridurremo la dimensione di 700Mb). Dall’ultimo log., rivediamo questo dato importante: (Il valore si riferisce al mio caso voi avrete un valore differente). Total Size: 127.7 GB (127691702272 Bytes) (exactly 249397856 512-Byte-Blocks) - La formula per calcolare lo spazio è la seguente: Dim-Totale (meno) Dim-Da-Estrarre dove Dim-Totale = 127691702272 Byte e Dim-Da-Estrarre = 700MB ossia (700*1024*1024) cioè 734003200 Byte - Nel mio caso otterrò: 127691702272-(700*1024*1024)= 127691702272-734003200=126957699072Byte Bene torniamo al terminale: diskutil resizeVolume /dev/diskXsX 126957699072B jhfs+ "Recovery HD" 734003200B ErmaC:~# diskutil resizeVolume /dev/disk0s2 126957699072B jhfs+ "Recovery HD" 734003200B Started partitioning on disk0s2 Macintosh HD Verifying the disk Checking file system Performing live verification Checking Journaled HFS Plus volume Checking extents overflow file Checking catalog file Checking multi-linked files Checking catalog hierarchy Checking extended attributes file Checking volume bitmap Checking volume information The volume Macintosh HD appears to be OK Resizing Waiting for the disks to reappear Formatting disk0s3 as Mac OS Extended (Journaled) with name Recovery HD Initialized /dev/rdisk0s3 as a 621 MB HFS Plus volume with a 8192k journal Mounting disk Finished partitioning on disk0s2 Macintosh HD /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *128.0 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD 127.0 GB disk0s2 3: Apple_HFS Recovery HD 651.1 MB disk0s3 Ora copiamo tutta la cartella com.apple.recovery.boot (che abbiamo realizzato nella prima fase di questa guida) all’interno della nuova partizione creata. Possiamo tranquillamente usare il finder, con un semplice copia e incolla, oppure trascinare la cartella all’interno del disco. Fatto ciò ritorniamo al terminale e correggiamo la dimensione della partizione "Recovery HD" da 700Mb a 650Mb. diskutil resizeVolume /dev/diskXsX 650002432B ErmaC:~# diskutil resizeVolume disk0s3 650002432B Started partitioning on disk0s3 Recovery HD Verifying the disk Checking file system Checking Journaled HFS Plus volume Checking extents overflow file Checking catalog file Checking multi-linked files Checking catalog hierarchy Checking extended attributes file Checking volume bitmap Checking volume information The volume Recovery HD appears to be OK Resizing Finished partitioning on disk0s3 Recovery HD /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *128.0 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD 127.0 GB disk0s2 3: Apple_HFS Recovery HD 650.0 MB disk0s3 Smontiamo la partizione di ripristino: diskutil unmount /dev/diskXsX ErmaC:~ root# diskutil unmount /dev/disk0s3 Volume Recovery HD on disk0s3 unmounted ErmaC:~ root# Ora viene la parte più rischiosa di tutta la procedura SISTEMARE IL TIPO DI PARTIZIONE asr adjust --target /dev/diskXsX -settype "Apple_Boot" ErmaC:~# asr adjust --target /dev/disk0s3 -settype "Apple_Boot" Fsck /dev/disk0s3 ....10....20....30....40....50....60....70....80....90....100 Adjust completed successfully Ricontrolliamo diskutil list ErmaC:~ root# diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *128.0 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD 127.0 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 .: FASE 2) COMPLETATA :. Ci siamo! Riavviamo il nostro hack e apriamo nuovamente iCloud. Finalmente l'opzione "Find My Mac" è attiva. Premiamo il pulsante "Successivo" Finito! Ora possiamo usare iCloud in tutte le sue "finezze" Fabio Guida alternativa semplificata (In Inglese): [How To] Enable "Find My Mac" with a FAKE Recovery HD Ringraziamenti: Google it! - How to create a Mac OS X Lion recovery partition by Dmitry Dulepov Google it! - Mac recovery partition: revised by Dmitry Dulepov
  25. So after I was able to fix the iMessenger problem, I still get stuck in iCloud. iCloud is sync my data but for some reason it don't allow me to change things or even add other apps to use it in Yosemite Video showing what happen after add my password: 1) add a wrong pw to make sure is validating the pw 2) I put the right pw and don't do nothing