UniBeast 7 Troubleshooting Notes

Discussion in 'UniBeast' started by MacMan, Sep 27, 2016.

Thread Status:
Not open for further replies.
  1. MacMan

    MacMan Administrator Staff Member

    Joined:
    Feb 2, 2010
    Messages:
    7,811
    Mobo:
    GA-Z77X-UP5 TH
    CPU:
    Core i7-3770K
    Graphics:
    GTX 670
    Mac:
    MacBook Pro
    Classic Mac:
    Power Mac, PowerBook
    Mobile Phone:
    iOS
    Sep 27, 2016 at 7:13 PM #1
    MacMan

    MacMan Administrator Staff Member

    Joined:
    Feb 2, 2010
    Messages:
    7,811
    Mobo:
    GA-Z77X-UP5 TH
    CPU:
    Core i7-3770K
    Graphics:
    GTX 670
    Mac:
    MacBook Pro
    Classic Mac:
    Power Mac, PowerBook
    Mobile Phone:
    iOS
    Before posting an issue or question with UniBeast please read the following:

    1. UniBeast does NOT install anything on your hard drive, it CREATES a bootable USB stick.

    2. UniBeast only works on English language systems and is not supported using any other language.

    3. UniBeast is not supported when running within a VM. Use your native OS X installation instead.

    4. UniBeast does not support running from or copying to Case-sensitive file systems.

    5. UniBeast will only run on Intel 64-bit systems.

    6. UniBeast will detect and only works with valid purchased Sierra install applications in /Applications.

    7. UniBeast will erase the destination disk as part of the creation process. Make sure you have backed up any files on the destination before running.

    8. It typically takes between 15-30 minutes to complete copying and creating the USB. The time is all based on system and USB type and speed.

    9. A UniBeast created 10.12 drive uses approximately 7.42 GB on the destination drive. You can verify this by doing a “Get Info” in the Finder for the USB stick. Note not all 8 GB USB sticks are made alike, make sure your drive has at least 7.6 GB free.

    10. UniBeast is a signed installer. Make sure "System Preferences - > Security & Privacy -> General -> Allow applications downloaded from" is checked for "Mac App Store and identified developers" or "Anywhere".

    11. When running UniBeast on Lion (OS X 10.7), you must be running OS X 10.7.5 with the OS X Lion 10.7.5 Supplemental Updateinstalled. Otherwise you will see "The operation couldn’t be completed. CSSMERR_TP_NOT_TRUSTED" in the install.log.

    12. When running on Snow Leopard (OS X 10.6) you must be running OS X 10.6.8 with the Apple Software Installer Update 1.0installed. Otherwise you will see "The operation couldn’t be completed. CSSMERR_TP_NOT_TRUSTED" in the install.log.

    13. Most UniBeast failures are due to it not finding your valid purchased copy of Install macOS Sierra.app in /Applications, or the application is incomplete or corrupted.

    Your copy of the install application can get corrupted if you copy it off to another folder and/or volume. It could also get corrupted if you have multiple copies of the application and then update it from the Mac App Store. When you update the application the Mac App Store download function is smart and can detect if the original is no longer in /Applications and update it in the new location or it will only update part of it in the new location and create the rest in /Applications, thus creating a spilt update.

    To fix this issue you need to delete all copies of "Install OS X xxxxxxx.app" from all mounted volumes and empty the Trash. Then download it again to ensure that you are downloading a clean complete copy from the Mac App Store.

    14. UniBeast will log to ~/Library/Logs/UniBeast.log which is accessible via the Console application

    Any failures or errors will be logged during the appropriate phase.

    15. Clover installation logs are written to /var/log/install.log which is accessible via the Console application

    Any Clover installation failure logs are written there.

    16. UniBeast will only write to an external drive with a partition of 32 GB or less. Larger drives will need to be partitioned.

    17. Failure to write errors are either a bad destination drive or host system USB issues.

    18. If you choose UEFI Boot Mode install, the USB stick MUST be formatted as GPT.

    19. If you choose Legacy Boot Mode install, the USB stick can be formatted as MBR or GPT. If it's MBR then Clover will be installed to the root of the destination drive. If it's GPT Clover will be installed on the EFI partition.

    20. If none of these solve your problem then follow the instructions in http://www.tonymacx86.com/unibeast/85364-unibeast-failure-reporting.html
     
    Last edited: Dec 18, 2016
Thread Status:
Not open for further replies.

Share This Page