Jump to content
ITzTravelInTime

TINU: The bootable macOS installer creation tool - Mac app

314 posts in this topic

Recommended Posts

great work my friend very easy to use

i was wondering if it is possible some how that within TINU that we can chose the file system to install (HFS+ or APFS)

because with sierra and up and if you have SSD it will install with APFS file system.

and for me i like to use the HFS+ file system or if there is a way to do that

thanks

Share this post


Link to post
Share on other sites
Advertisement
3 minutes ago, newsman1 said:

great work my friend very easy to use

i was wondering if it is possible some how that within TINU that we can chose the file system to install (HFS+ or APFS)

because with sierra and up and if you have SSD it will install with APFS file system.

and for me i like to use the HFS+ file system or if there is a way to do that

thanks

you cannot choose which file system will install the bootable usb drive you create, because tinu uses just the command line method to create usb drive and that method does not allows to chosse if eneble or not the automatic apfs convert in the usb installer, but you have several ways to do avoid that, first of all there is an option in tinu 2 which is enabled by default which creates a copy of tinu inside the usb installer, and after you have booted into the installer you can open tinu using the terminal with the following command: "/Volumes/Image Volume/TINU.app/Contents/TINU" . when tinu is opened you can use it to install mac os and inside the advanced options you find also an option to disable the automatic apfs upgrade, the other method is to use the unsolid kext, which is a kext that lets macOS to belive that you are not installing on an ssd, so it will not upgrade to apfs.

For all of you guys remember that if you open tinu from the booted installer you can use it to install macOS without apfs upgrade

Share this post


Link to post
Share on other sites

so just put this kext at EFI/CLOVER/kexts/Other. on the Install macOS High Sierra USB 

when I want to do a fresh install it will see my SSD drive as reg hard drive and it will install HFS+ file system 

Share this post


Link to post
Share on other sites

but after the installation is done and high Sierra is up and running is it still see my SSD drive as Reg Hard drive or it will recognized as SSD drive.

and do I need to put the UnSolid.kext in the EFI/CLOVER/kexts/Other. in the SSD drive.

Thanks,

Share this post


Link to post
Share on other sites

The kext is only used for the install process... 

You don't have to use it on the EFI-Partition of the SSD afterwards...

The SSD will be shown as SSD.

Share this post


Link to post
Share on other sites
4 hours ago, al6042 said:

There is also the option to use the Unsolid.kext to prevent the APFS filesystem on SSDs.

This kext was created by @Brumbaer and works like a charm.

i have also suggested the unsolid kext in my post and it's probably the most simplay way to avoid the apfs conversion on a hackintosh

Share this post


Link to post
Share on other sites

Hey ItzTravelInTime! I've just found now that TINU require 8Gb USB and no less, even if 7Gb, in my case i create two partitions one for the installer (macOS) and the second for apps and files required after the installation. Now if i have 8Gb USB Stick I create partition 1 with 6,50 Gb and partition 2 with 1,20 Gb. But TINU doesn't see the partition, can you do something please?

Edited by ammoune78

Share this post


Link to post
Share on other sites

I've found another issue, TINU create USB installer but when i boot from it doesn't see the "boot from Install macOS High Sierra", i just tried it two times but same result!

Edited by ammoune78

Share this post


Link to post
Share on other sites
23 hours ago, al6042 said:

The kext is only used for the install process... 

You don't have to use it on the EFI-Partition of the SSD afterwards...

The SSD will be shown as SSD.

Thank you very much my freind that's answer all my qustions

:thumbsup_anim::thumbsup_anim::thumbsup_anim:

Share this post


Link to post
Share on other sites

I think it's not related to TINU because same thing with install media command from terminal!

So is there a trick for this 10.13.4 Installer to be detected by clover Boot Menu or i'm doing something wrong :(:whistle:

Share this post


Link to post
Share on other sites
3 hours ago, ammoune78 said:

Hey ItzTravelInTime! I've just found now that TINU require 8Gb USB and no less, even if 7Gb, in my case i create two partitions one for the installer (macOS) and the second for apps and files required after the installation. Now if i have 8Gb USB Stick I create partition 1 with 6,50 Gb and partition 2 with 1,20 Gb. But TINU doesn't see the partition, can you do something please?

tinu does detects only partitions which can be used with an install media, so at least 8 gb, if it's not shown it's because it's not usable with tinu

 

28 minutes ago, ammoune78 said:

I think it's not related to TINU because same thing with install media command from terminal!

So is there a trick for this 10.13.4 Installer to be detected by clover Boot Menu or i'm doing something wrong :(:whistle:

tinu uses the command line method, probably it can be solved via a future clover update which will support this new frmat of installers, but at the time being you can solve this issue by creating a .IABootFiles folder and you have to put inside of it all the files inside the system folders in the usb key, so you should end up with something like this which should solve the issues at least in my case it did.

Schermata 2018-04-04 alle 20.38.51.png

Share this post


Link to post
Share on other sites

Reagrding what is happening with macOS 10.13.4 and the usb installers not detected, i have added a new advamced setting to tinu, which is enabled by default if you want to create a bootable usb installer of macOS 10.13.4 and does the procedure i described in the previous post, it creares an .IABootFiles folder and the it copyes all the system files from the usb installer inside the .IABootFiles Folder, a temporary solution which helps until the clover team adds support for 10.13.4 installers, when this support will be added to the latest clover, i will no longer make it enabled by default when such support is added, now this feature is in testing, i will let you know how is it going

Edited by ITzTravelInTime

Share this post


Link to post
Share on other sites

so, after some thuble shooting the new advanced option works, maybe i can consider tinu as the first mac os installer creation tool which has the 10.13.4 support in it

And i have also fixed a bug hich was introduced in the pre-release 2 of tinu 2.0 which i have discovered only now

Edited by ITzTravelInTime

Share this post


Link to post
Share on other sites
41 minutes ago, ITzTravelInTime said:

so, after some thuble shooting the new advanced option works, maybe i can consider tinu as the first mac os installer creation tool which has the 10.13.4 support in it

And i have also fixed a bug hich was introduced in the pre-release 2 of tinu 2.0 which i have discovered only now

Where I can find new pre-release of Tinu 2.0. Thanks

Share this post


Link to post
Share on other sites
Just now, Matgen84 said:

Where I can find new pre-release of Tinu 2.0. Thanks

look at the orevious posts, i have created one with links to download the app and the source code, but a new one is coming shortly

Share this post


Link to post
Share on other sites

As far as I know, the removal of the file ".IAPhysicalMedia" should be sufficient.

The following lines from the Clover Sourcecode (loader.c) should explain it:

// Use standard location for boot.efi, unless the file /.IAPhysicalMedia is present
// That file indentifies a 2nd-stage Install Media, so when present, skip standard path to avoid entry duplication

 if (StriCmp(CustomPath, MACOSX_LOADER_PATH) == 0 && FileExists(Volume->RootDir, L"\\.IAPhysicalMedia")) {
DBG("skipped standard OSX path because volume is 2nd stage Install Media\n");
continue;
}

Share this post


Link to post
Share on other sites
43 minutes ago, al6042 said:

As far as I know, the removal of the file ".IAPhysicalMedia" should be sufficient.

The following lines from the Clover Sourcecode (loader.c) should explain it:

 

 


 if (StriCmp(CustomPath, MACOSX_LOADER_PATH) == 0 && FileExists(Volume->RootDir, L"\\.IAPhysicalMedia")) {
DBG("skipped standard OSX path because volume is 2nd stage Install Media\n");
continue;
}

 

ok, i will test this, but i will also keep the option to create the .IABootFiles folder but i will make it disabled by default and i will make another option to remove .IAPhysicalMedia that will be enabled by default, i do this to also leave more freedom to the users to choose a way to fix, but clover team should allow the usb drive to be detected if there is the .IAPhisicalMedia file and not the .IABootFiles folder, to let the "vanilla" usb installer to be detected, or am i wrong?

Share this post


Link to post
Share on other sites

I just create a new Install Stick with TinU (Public) and then try to just rename the file and/or the folder to verify.

Share this post


Link to post
Share on other sites
Just now, al6042 said:

I just create a new Install Stick with TinU (Public) and then try to just rename the file and/or the folder to verify.

i tried moving the .IAPhisicalMedia file to another location in a usb installer created with TINU and it's detected by clover and correctly booted, so i can say that removing or moving it works, maybe i will remove it in the code i am going to write for the app

Share this post


Link to post
Share on other sites

Just finished my test, but didn't had to rename or move the hidden file at all.

The unmodified install stick was found by the original MBP which I currently use on holiday.

Adding Clover in Version 4423, without changing the hidden file, showed the Installer in the Clover bootmenu also.

That means, that you shouldn't have to do anything, since the newest Clover sources seems to tackle the already known issue.

HS10.13.4-Installer1.png

Share this post


Link to post
Share on other sites
16 minutes ago, al6042 said:

Just finished my test, but didn't had to rename or move the hidden file at all.

The unmodified install stick was found by the original MBP which I currently use on holiday.

Adding Clover in Version 4423, without changing the hidden file, showed the Installer in the Clover bootmenu also.

That means, that you shouldn't have to do anything, since the newest Clover sources seems to tackle the already known issue.

HS10.13.4-Installer1.png

ok, but i will kepp the 2 options in tinu beause i have already created them, but i will leave them disabled by default and i will just tell to folks using tinu to just upgrade their clover version, thank you very much for your help

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 BiggestDrugo
      Hi, I have an MSI 945gcm5 v2 and was wondering if it's possible to run Hackintosh High Sierra on this board? It will run Lion, but my guess is that the chipset and various other factors will prevent an upgrade to High Sierra. Any thoughts?
    • By plasticduck35
      I have a hackintosh running 10.13.5 (High Serria) that works except it doesn't shutdown properly and it doesn't seem to be going to sleep. 
       
      Here are some diagnostics that I gathered 
       
      Davids-MacBook-Air-2:~ davidozersky$ sudo pmset -g Password: System-wide power settings: Currently in use: hibernatemode 0 womp 0 networkoversleep 0 sleep 5 (sleep prevented by diskmanagementd, UserEventAgent, mds, diskarbitrationd, coreaudiod, mds_stores, Disk Utility) Sleep On Power Button 1 ttyskeepawake 1 hibernatefile /var/vm/sleepimage disksleep 10 displaysleep 5  
      And I've attached files from a RunMe utility app I've found online. 
       
       
      Any ideas? 
       
      Thank you, 
      David
      runmereport.ioreg
    • By AudioGod
      I have put together this simple little guide for anybody wanting to use a Patched DSDT EFI with the same configuration as me.
      This is also a thread to discuss everything Z390 Pro and try and help where we can and maybe make things a little better for you. 
       
      A huge massive thank you to @glasgood @MaLd0n @larabee These three guys have helped me and talked me so much and are as helpful as you could ever get, Without them I wouldn't have a perfect working build like I do or be putting up this Guide & Discussion Thread sharing the hard work and countless hours that we have all put in to this.   
       
       
      This EFI and Patched DSDT have been created to work with a Gigabyte Aorus Z390 Pro, 9900k with a Vega 56 but has also been tested and verified fully working with the following Hardware
       
      CPU's
      8700k, 9600k, 9700k, 9900k
       
      GPU's
      RX 560, 570, 580, 590, Vega 56, Vega 64, Radion VII
      (If you have success with any different CPU or GPU's then please do let me know)
       
       
       @glasgood Has kindly put together a new simple Catalina install guide so Just Follow He's Guide For a Perfect Install.
       
       
      HARDWARE USED
      • Intel I9 9900k 
      • Gigabyte AORUS Z390 PRO
      • Sapphire Nitro+ SE Vega56 ( connected to monitor with DisplayPort )
      • Corsair Vengeance Pro RGB 16GB @3200mhz (2 x 8GB)
      • Corsair RM850x 80 Plus Gold Power Supply Unit
      • Coolermaster MASTERLIQUID ML360R RGB CPU Cooler
      • Samsung 970 EVO 1TB NVMe SSD macOS Mojave
      • Samsung 860 EVO 1TB SSD (2.5) Windows 10 Pro
      • ABWB BCM943602CS 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E)   
      • Lian Li PC-O11DW Dynamic ATX Case
       

       

       
       
      WORKING
      • Sound 
      • Ethernet Port
      • WiFi
      • SSD Trim
      • USB 3.0 & 2.0 (All ports Open Natively)
      • AirDrop
      • iCloud
      • Hardware Acceleration
      • iMessages
      • Facetime
      • Sleep & Wake
      • Sleep and Shutdown via the Power Button
      • Handoff
      • Netflix on Safari browser
      • Continuity
       
       
      CLOVER  FOLDER
      Use this folder with fully patched DSDT
      Z390 Pro DSDT EFI.zip   (Updated 21 July 2019)
       
       
      ADDITIONAL DSDT's  (A big thanks to @MaLd0n for compiling these extra DSDT's)
      If your using a Vega 56/64 or Radion VII then use this DSDT (already installed in my EFI)
      DSDT.VEGA.VII.zip
      If your using a RX Series or Nvidia GPU then use this DSDT
      DSDT.RXxxx.NVIDIA.zip
       
       
      To Create Your Own Patched DSDT Message @MaLd0n using the link bellow
      https://olarila.com/forum/viewtopic.php?f=19&t=1131 
      (If you want a perfect setup then getting your own patched DSDT made would be the best thing to do, Mine will work perfectly fine but different hardware no matter how small a change it is can tend to have some sort of effect on the DSDT and your setup)
       
       
      If Your Not Using File Vault Then Please Disable Hibernate
      disablehibernate.command
       
       
      ADDITONAL DOWNLOADS
      Clover
      Clover Configurator
      Kext Updater
       
       
      OPTIONAL DOWNLOADS
      AirportBrcmFixup.kext    (If your Wifi Card isn't working after installing my EFI then add the AirportBrcmFixup.kext to your clover kext folder and reboot)
      FakeSMC    (Can be used instead of VirtualSMC)
      Hackintool
      IORegistryExplorer
      Native Display Brightness with MonitorControl
       
       
      BIOS SETTINGS (Bios Revision F10)
       
      • Enter BIOS → Press F12 → Enter Setup
      • Save & Exit → Load Optimized Defaults
       
      • BIOS → Windows 8/10 Features → Other OS
      • BIOS → CSM Support → Enabled  (Can be set to disabled depending on what GPU you use)
       
      • MIT → Advanced Memory Settings  → Extreme Memory Profile (X.M.P) → Enabled  
       
      • Peripherals → Initial Display Output → PCIe 1 Slot
      • Peripherals → Trusted Computing → Security Device Support →  Disable
      • Peripherals → Intel(R)Bios Guard → Intel BIOS Guard Support →  Disable
      • Peripherals → USB Configuration → Legacy USB Support →  Enabled
      • Peripherals → USB Configuration → XHCI Hand-off →  Enabled
      • Peripherals → Network Stack Configuration → Network Stack →  Disabled
      • Peripherals → SATA And RST Configuration → SATA Mode Selection →  AHCI
       
      • Chipset → Vt-d → Enabled  (can be enabled or disabled, your choice)
      • Chipset → Internal Graphics → Disabled
      • Chipset → Audio Controller → Enabled
      • Chipset → Above 4G Decoding → Disabled 
       
      • Power → Platform Power Management → Enabled
      • Power → ErP → Enabled  (can be enabled or disabled, your choice)
      • Power → RC6 (Render Standby) → Disabled
       
      • Save & Exit → Save & Exit Setup
       
       
      SCREENSHOTS
       

       

       

       

       

       

       

       

       

       

       

       

    • By Ethan Jarvis
      Hello,
       
      Here I am looking for the answer of new Mac OS Catalina features and what type of Mac will support this new Os??
×