Jump to content

TINU: The bootable macOS installer creation tool - Mac app


ITzTravelInTime
390 posts in this topic

Recommended Posts

1 minute ago, Matgen84 said:

 

I rebuild the app with new source. Works fine now finally.

 

 

Yes, i have finally figured out the issue, when i am done testing i will release an updated build of the app.

Link to comment
Share on other sites

I have made a new release that fixes the bug that @Matgen84 had, and also makes a few small changes.

 

Here is the change log:

  • Fixed a crash that occurs when the SIP status isn't fully disabled or fully enabled.
  • New lower SIP Requirements (Now the app just requires the CSR_ALLOW_UNRESTRICTED_FS flag to be disabled to operate without forcing the diagnostics mode).
  • Updated links in the menu bar.

And here is the download link: https://github.com/ITzTravelInTime/TINU/releases/tag/3.0_RC_(101)

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

1238656384_ScreenShot2021-10-01at19_53_27.thumb.png.0f19c225097bcec5b6b6011f82888aa5.png1277537415_ScreenShot2021-10-01at20_12_24.thumb.png.77df526fa7a5207e6388f0e60e5228a8.png

Spoiler

1238656384_ScreenShot2021-10-01at19_53_27.thumb.png.0f19c225097bcec5b6b6011f82888aa5.png1277537415_ScreenShot2021-10-01at20_12_24.thumb.png.77df526fa7a5207e6388f0e60e5228a8.png

Hi I can successfully build a USB installer on Monterey Beta 8 with the previous version of TINU app, but the newest version quits after formatting the Drive. I don't know if you can gather any info from the attached to see what the problem maybe - Thanks.

Link to comment
Share on other sites

1 hour ago, eSaF said:

Hi I can successfully build a USB installer on Monterey Beta 8 with the previous version of TINU app, but the newest version quits after formatting the Drive. I don't know if you can gather any info from the attached to see what the problem maybe - Thanks.

 

Hi, perhaps this was a knows problem since it's a crash of the NSProcess api, it's also a  problem that i might actually have already fixed in the latest source code, i will send you via private messange a build of tinu made from the last source code, check if it fixes this problem. You can also get xcode 13 and a copy of the source code and try to build the app and test it.

 

If it fixes the issue i will post a new updated build.

  • Thanks 1
Link to comment
Share on other sites

  • 4 weeks later...

New stable relese guys, version 3.0 here is the changelog:

- New algorythm for the detection of usable drives and partitions, unusable/unsupported drives and partitions will now be displayed and flagged as unusable/unsupported instead of being hidden (Doesn't apply APFS Volumes yet).
- Installer apps for OS X Lion and Mountain Lion will now be detected and flagges as unsupported.
- Added downloads for the OS X Lion, Mountain Lion and Yosemite installer apps in the dedicated installer app download window.
- License and legal overhaul. Amoung other things now you will be no longer prompted to agree to the license every time you want to make a usb installer (the license is still readable using the `About TINU` window).  
- Various UI-related fixes and corrections.
- Various bug and crash fixes.
- Tested to work on macOS Monterey.

 

And here are the downloads, as always: https://github.com/ITzTravelInTime/TINU/releases

  • Like 3
  • Thanks 2
Link to comment
Share on other sites

New release guys, version 3.0.1, here is the change log:

  • Improves some messages and alerts, so some things are now explained better and with more details (this following some user feedback).
  • Now you can use the mouse scroll wheel to scroll horizontally when needed (another requested thing).
  • Improved UI outlines thanks to screen pixel size detection.
  • Improved the size requirements for drives and installer apps.
  • Bug fixes.

 

As always you can get it from the releases page here: https://github.com/ITzTravelInTime/TINU/releases

Edited by ITzTravelInTime
  • Like 1
Link to comment
Share on other sites

So i am working on a new feature that will extend what TINU can do, here is a teaser (sorry for the Italian text, it's what i use for testing usually):

 

101414994_Schermata2021-11-01alle17_58_09.thumb.png.3e00963c640fa63dc6d429b281134298.png

 

Edited by ITzTravelInTime
  • Like 2
Link to comment
Share on other sites

  • 10 months later...

Hi  @ITzTravelInTime,

I decided to create new bootable stick and choose your TINU to do this.Took the latest version from GitHub 3.0.1.

All are understandable, works without gitches. For my wonder it found all my InstallMacOS.app and created menu with them.

After finish I mounted the EFI partition and found it empty. No problem! I took my Clover-5149.pkg and installed Clover on this partition.

The stick is bootable, Clover started and I see "Install macOS..." in the menu.

 

Thank you for the very convenient software!

  • Like 5
Link to comment
Share on other sites

8 hours ago, Slice said:

Hi  @ITzTravelInTime,

I decided to create new bootable stick and choose your TINU to do this.Took the latest version from GitHub 3.0.1.

All are understandable, works without gitches. For my wonder it found all my InstallMacOS.app and created menu with them.

After finish I mounted the EFI partition and found it empty. No problem! I took my Clover-5149.pkg and installed Clover on this partition.

The stick is bootable, Clover started and I see "Install macOS..." in the menu.

 

Thank you for the very convenient software!

 

Oh thank you very much for giving my app a go, i also very much appreciate your work.

 

The fact that it doesn't put in an efi folder is a deliberate design decision because i want people to actually learn to make their own efi folder, giving a pre-made efi folder would just generate many issues for me and let them just not use an optimized EFI folder right away. I want to avoid going in the same rabbithole as the "tony tools" do, and actually encourage good practices.

 

Also at it's core TINU uses apple's Createinstallmedia with some erro checking andutomation, and doesn't mess with the bootable drive createinstallmedia makes, (besides adding some files to the root, which can be disabled), so it just works out of the box with macs and any hackintosh bootloader which supports the Createinstallmedia boot drives and you are guaranteed to have a pure and untouched vanilla installation when you are done.

 

i have also implemented an automated Clover/Open Core EFI folder copy tool, that you can use if you already got an EFI folder ready to use. You can find it into the options menu (that you can access from the confirmation screen before staring the installer creation process). This tool just mounts the ESP, copies the EFI folder inside of it, and then unmounts the ESP. I made this tool mostly for convenience to be honest.

 

For the UI of the app i have done a little design study, together with a UX/UI designer i know, to make the app very intuitive and convenient to use, i have also put some great deal of time into polishing the app and implementing fixes based on user feedback. For this kind of tool to be successful in any way you have to make a good and polished UI.

 

About the whole it's also all completely free and open source, written in Swift, using AppKit as the Ui frameowrk, and it only uses my own open source libraries and the system api.

 

BTW i want just to tell you that i am working on a brand new mac app (no idea for a release date, we are still early in development, and we also have many related-non-technical works to do yet) so stay tuned for that.

Edited by ITzTravelInTime
  • Like 2
Link to comment
Share on other sites

  • 3 weeks later...
1 hour ago, Slice said:

What is my mistake?

 

As i said tinu doesn't really manipulate what apple's createinstallmedia executable creates, it mainly, perform checks and closes programs if necessary to ensure a successful outcome of createinstallmedia, other than providing a gui to use it, there for this is an apple issue .

 

So i think this might be a code signing issues as of my experience, try setting the bios date back to when that particular build of the macos installer app was released and also make sure your ethernet kexts are loaded and working into the installer and that you have a working internet connection, it's known that recent macOS versions could throw out macOS installer errors when offline.

 

If none of the above worked download a new copy of the macOS installer app and re-create the usb installer from scratch using that, perhaps apple fixed the codesigning issue by re-signing an updated build of the installer, it's known that some installer apps used certificates that expired just a few years after their release, and apple released some newly signed copies of those to provvide ways of recovering older macs that don' officially support newer versions.

Edited by ITzTravelInTime
Link to comment
Share on other sites

I set BIOS date to 2020 but is it good for Mojave? Internet is active inside the installer. I checked by Safari in the installer.

But having internet I got real date back. Yes?

Link to comment
Share on other sites

On 10/4/2022 at 9:09 PM, Slice said:

I set BIOS date to 2020 but is it good for Mojave? Internet is active inside the installer. I checked by Safari in the installer.

But having internet I got real date back. Yes?

Oh ok, so try an offline install with the bios date back to 2019 which is when the last major mojave build was releasedd.

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...