Jump to content
taikentsuken

Series 9] Probleme de boot sur le HDD apres installation

5 posts in this topic

Recommended Posts

Bonjour tout le monde,

 

Je me suis acheté un Samsung Series 9 sur lequel j'ai commencé à installer Mountain Lion avec #######.

 

Tout s'est bien déroulé à l'exception que même après avoir installé CHAMELEON 2.1 rv2048, le pc ne boot pas sur le HDD même si il est configuré en First Boot dans le BIOS.

 

J'ai eu beau essayé d'installer le fix boot0 en copiant le boot1h mais rien à faire, lorsque je démarre le pc j'ai droit à un écran noir qui clignote.

 

Mountain Lion marche très bien lorsque je boot sur la clé ######## en choisissant la partition HDD.

 

Merci de m'aider :)

 

Tai.

 

PS : Est ce qu'il y a bien les drivers pour ce laptopt ?

 

Config :

Laptop : Samsung Series 9 NP900X3A

USB : OCZ 8Go usb2.0

Share this post


Link to post
Share on other sites
Advertisement

Merci pour les règles du forum, par contre j'ai bien essayé de l'installer direct à partir de la clé usb (chameleon) mais rien à faire j'ai toujours droit à un black screen.

 

Que puis je faire ?

Share this post


Link to post
Share on other sites

Essaie un truc, si ton hdd est vide, sinon sauvegarde tes données sur un autre hdd. Tu démarres l'installation, tu vas dans utilitaire de disque -> tu sélectionne ton hdd -> tu clique sur formater, options et sur tableau de partition GUID, tu choisis le nombre de partitions que tu veux, et tu clique sur appliquer.

ATTENTION ! La totalitée de ton disque va être effacée, et tu ne pourra plus récupérer tes fichiers si tu n'as pas sauvegardé....

Ensuite, installe avec le moins de Kexts possibles (il vaut mieux les installer après, et si ça marche :P )

Enfin, dès que l'installation est finie, redémarre et essaie de booter, et dis nous si ça marche toujours pas...

Share this post


Link to post
Share on other sites

Bonjour

taikentsuken,

 

J'ai exactement la même chose...

 

J'ai également un Samsung ( RV520) et l'installation se fait sans trop de problème mais lors du reboot, écran noir "clignotant" !

Apparemment, de ce que j'ai déjà pu lire partout grâce a google, ça arrive a tous les portable Samsung... pourquoi ? je n'ai pas encore trouvé de soluce! je suppose que c'est la carte mère!?

 

quelqu'un aurait déja réussi l'install de mac sur un samsung?

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Ciumann
      Salve ragazzi!
      Dopo molti tentativi sono riuscito a fare hackintosh con High Sierra. Ogni sistema operativo ha il suo Hard Disk.
       
      Scheda madre: AsRock B85M (UEFI)
      Processore: Intel i5 4460
      Scheda Video: Palit GTX 960 4 GB
      Ram: 2 schede HyperX Fury 4 GB ognuna.

      Ora ho un po' di cose da risolvere.

      Innanzitutto vorrei scegliere all'avvio del PC quale dei sistemi operativi far partire. Ho fatto la procedura con "moltebestie" (in ogni tipo di opzione nel quick start) ma all'avvio devo sempre inserire la pennetta per poter scegliere Sierra.
       
      Secondo problema è che mi mancano i vari driver, scheda video... E, cosa strana, ho notato che nelle informazioni di sistema mi da che ho 4 GB di Ram invece che 8.


      Ringrazio in anticipo!

    • By tbianco
      Ho comprato da poco un Acer Aspire 5750G e girando su internet ho trovato la cartella efi che garantiva quasi tutto funzionante perfino il wifi (https://github.com/zipippino/HighSierraAspire5750G).
      Allora felicissimo installo macOS e a parte incappare in errori stupidi, riesco a fare tutto, ma quando sono riuscito ad installare clover Legacy e sostituendo la roba con la 'mia' efi clover si avvia ma macOS no, semplicemente non carica (si nota anche pk la spia dell'hdd che dice se è in attivitá è spenta.
      Qualcuno può aiutarmi?
    • By JLMOX
      I think, at this point converting to hfs+ is out of the question, Apple has been pushing the apfs file policy very aggressively, so does anybody solved the missing "Boot macOS from Mojave " (this last word may be different). I have installed the latest clover in HDD and USB, but I can only see 3 Mac Os related tabs but not the one for actually loading the Mojabe mac OS. I updated high sierra to Mojave and everything went fine. My laptop (Dell E6530) booted up normally, Mojave system loaded up, I finished the setup and spent sometime exploring. I updated clover to the latest version and turned of machine. When I restarted, I noticed Clover did not have an option for booting into the system like High sierra had it. I tried adding the apfs.efi or the ApfsDriverLoader-64.efi driver to the clover efi folder in the HDD and also tried with a USB clover installation and the result is the same: No boot option for the Mojave OS. I used the recovery option and I was able to explore the partion where the system is located but that´s as far as I could go. Does anybody has an idea of what happened?

    • By Mattbatt
      First post, thank you all for any help offered. I am coming from a certain commercialized hackintosh community - after seeing such amazing vanilla installs and reading of the talent here, I decided to have a go at not using such software methods. And I immediately got myself into a predicament 
       
      BACKSTORY
      I successfully upgraded from Mavericks to Mojave 10.14.2 but decided to start over and do a clean install because my Vega Frontier was not playing OOB even with Lilu & whatevergreen - and there was a lot of 'code junk' Clover barfed at boot from this 'commercialized software'.
       
      SUCCESS
      I created Mojave USB installer from scratch using the latest Clover, it worked fine, got me to the Mojave install screen.
       
      PROBLEM
      For reasons unknown to me, I decided for one last ditch effort to see if I could get my already installed Mojave playing nicer - instead of starting over clean. So I installed the latest Clover on my Mojave SSD, (it had a Clover version YEARS ago when I last installed Mavericks) and I replaced the EFI file with the kexts and config of my USB EFI file because I figured, since the USB installer launched, it was all good to go.
       
      Now nothing boots after BIOS. Not my Mavericks drive, Mojave SSD, nor my USB Mojave Installer. They all hang right where Clover usually launches. I look at my USB lights and nothing flashes...
       
      The only drive I can use is Windows 8.1 (my testing environment) and not from Clover. That's just booting windows up without any HD's plugged in.
       
      Is there a way to rescue my predicament? I don't have another Mac computer and CloverConfig only runs on Mac. Is there a way to fix the USB from Windows? Thanks!
       
      Specs: Gigabyte GA-X58A-UD5 rev. 2.0, FC BIOS, i7-980x, Vega64 Frontier Edition, Nvidia GTX480, 24 GB 1333 RAM, SSD + various hardrives
    • By shmn
      Hey guys, my hack gets stuck at the attached screen, saying the 'VirtualSMC EFI module is broken' and it's waiting on some boot media. It does boot once in a while, but I cannot reproduce what makes it work, removing all USB devices doesn't help for instance. I know this seems to be a common issue, but the solutions I found didn't help.
      Please find attached the screenshot and my Clover folder. Any support much appreciated! (:

      CLOVER.zip
×