Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
The update to catalina went smoothly, thank you for your advice
I have a problem with my NVME sabrent rocket and the Sintech adapter (same with Mojave and Catalina). I have from time to time crashes of the IONVMeController, I had this problem for a few months (after 8-10 months without any problem). Do you have any idea where the problem could be?

The firmware is ECFM12.2, i dont know if updating the firmware to ECFM12.3 could solve my problem and if it is possible on mac without erasing all ssd?
Hi,

Glad the update went smoothly.

I really don't know if the firmware will solve the kernel panic.

At this point, I would create a Time Machine backup and update the drive's firmware. If the drive is erased during the upgrade process, you can restore the Time Machine backup.
 
Just upgraded my mid 2015 15” Macbook pro ssd to a Samsung 970 Evo Plus 2TB. Installation was a breeze. Just make sure you dont tighten the ssd screws all the way down. You dont want to bend the ssd nor make unnecessary contact. After three days of use everything has been running flawlessly.

No sleep problems: 57% the night before. 56% in the morning.
pmset: standbyhigh and low to 3600 and 1800. autopoweroffdelay 3000. keychain disabled. find my mac disabled. wifi and bluetooth off.

Bootcamp installation is also painless. The only problem i have is that i cant access boot camp control panel, saying i don’t have administrative privileges to change the start up disk. Have never gotten this before. This might or might not have anything to do with the ssd. It could also be because of the recent Mojave security update.

The solution is to create a shortcut that points to:
C:\Windows\System32\runas.exe /trustlevel:0x20000 AppleControlPanel.exe
then change it to always run as administrator in the Properties/Advance tab.


Power consumption is probably the only drawback: istats report 0,27-0,33A on idle and light tasks and playing youtube videos on firefox. Some spikes to 0,59-0,7A.

its also a bit warmer on the armrest while i’m syncing my cloud files to the ssd. I’m syncing 50k+ files, so everyday work loads would be lower than that. But so far, despite being warm to the touch (more like lukewarm), overall cpu temps and performance has not been much affected.

Other than power consumption the 970 Evo Plus behaves exactly like a native drive.

More detail of my setup:
MacOS Mojave 10.14.6 (Clean Install)
bootroom 199.0.0.0.0 (updated from a separate install of catalina)
Mid 2015 15” Macbook Pro
Sintech Long adapter

Link Width x4
Link Speed 8.0 GT/s

benchmark.jpg



Next thing i wanna try is nvmefix. I’ve tried installing the kext using hackintool but it wont work. I guess Lilu has to be injected properly first by the bootloader.


Anybody got any guides to install opencore + Lilu + nvmefix on a macbook pro?
All guides are for hackintosh or unofficial hardware. What EFI file configurations do i have to use for a native supported macbook? i dont want to brick my macbook.


[edit. changed to Amperes]
 
Last edited:
  • Like
Reactions: icecruncher
Next thing i wanna try is nvmefix. I’ve tried installing the kext using hackintool but it wont work. I guess Lilu has to be injected properly first by the bootloader.


Anybody got any guides to install opencore + Lilu + nvmefix on a macbook pro?
All guides are for hackintosh or unofficial hardware. What EFI file configurations do i have to use for a native supported macbook? i dont want to brick my macbook.

It’s actually much easier than that!

Quick guide based on my experience:

You just need the LiLu.kext and NVMeFix.kext. Note: they will not load unless you do a csrutil disable in a recovery terminal session.

Once disabled, simply use the hackintool kext install function to load them into /Library/Extensions and reboot.

Don’t try to install opencore or clover on a real Mac... I have heard doing so might mess up the EFI and brick your board.
 
Last edited:
It’s actually much easier than that!

Quick guide based on my experience:

You just need the LiLu.kext and NVMeFix.kext. Note: they will not load unless you do a csrutil disable in a recovery terminal session.

Once disabled, simply use the hackintool kext install function to load them into /System/Library/Extensions and reboot.

Don’t try to install opencore or clover on a real Mac... I have heard doing so might mess up the EFI and brick your board.

I just tried your method and......my power consumption increased to 0,6w idle LMAO. Does that mean it previously worked?? but i have already removed the kext.

istats.jpg


  1. i have disabled csrutil before because i use volta to undervolt my cpu. do i have to do csrutil disable again?
  2. i previously installed the kext to Library/Extension (LE) not SLE. does it make a difference?
  3. How do i know that nvmefix works? any checks that say "ASPM = Enabled" or something? i've tried "log show --style compact --last boot --predicate "processID == 0 && eventMessage CONTAINS \"NVMe\"" --debug --info" and it show assertion failed.
  4. and lastly how do i rebuild the kext cache in SLE?
Thank you!


====
Update:

i removed the kext and rebuild the cache using hackintool. Rebooted. Clean slate with no nvmefix: Idle power consumption around 0.6A. with spikes to 0,8A

Installed Lilu and nvmefix using kextbeast to LE. Rebooted. Now idle power consumption hovers nicely around 0,3A. CPU temps also kind of drops to 47 C.

drop2.jpg


So i guess it works?

Most importantly: do we have any checks that say "ASPM = Enabled" or something?

[edit. changed watts to amperes]
 
Last edited:
I just tried your method and......my power consumption increased to 0,6w idle LMAO. Does that mean it previously worked?? but i have already removed the kext.

View attachment 952392

  1. i have disabled csrutil before because i use volta to undervolt my cpu. do i have to do csrutil disable again?
  2. i previously installed the kext to Library/Extension (LE) not SLE. does it make a difference?
  3. How do i know that nvmefix works? any checks that say "ASPM = Enabled" or something? i've tried "log show --style compact --last boot --predicate "processID == 0 && eventMessage CONTAINS \"NVMe\"" --debug --info" and it show assertion failed.
  4. and lastly how do i rebuild the kext cache in SLE?
Thank you!


====
Update:

i removed the kext and rebuild the cache using hackintool. Rebooted. Clean slate with no nvmefix: Idle power consumption around 0.6w. with spikes to 0,8w

Installed Lilu and nvmefix using kextbeast to LE. Rebooted. Now idle power consumption hovers nicely around 0,3w. CPU temps also kind of drops to 47 C.

View attachment 952403

So i guess it works?

Most importantly: do we have any checks that say "ASPM = Enabled" or something?

Looks like it's working!

If you want to confirm NVMeFix is working, you would need to install the "debug" build and add "-nvmefdbg" to your boot-args, that will let "log show --style compact --last boot --predicate "processID == 0 && eventMessage CONTAINS \"NVMe\"" --debug --info" work.

It would show some data like this:

2020-09-11 16:54:29.597958-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) APST enabled: max PS = 4, max round-trip latency = 50000us
2020-09-11 16:54:29.598052-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) APST status 1
2020-09-11 16:54:29.598085-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 4 : 0x0
2020-09-11 16:54:29.598088-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 3 : 0x9c420
2020-09-11 16:54:29.598092-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 2 : 0xc818
2020-09-11 16:54:29.598095-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 1 : 0xc818
2020-09-11 16:54:29.598099-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 0 : 0xc818
 
  • Like
Reactions: _penguinman_
Looks like it's working!

If you want to confirm NVMeFix is working, you would need to install the "debug" build and add "-nvmefdbg" to your boot-args, that will let "log show --style compact --last boot --predicate "processID == 0 && eventMessage CONTAINS \"NVMe\"" --debug --info" work.

It would show some data like this:

2020-09-11 16:54:29.597958-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) APST enabled: max PS = 4, max round-trip latency = 50000us
2020-09-11 16:54:29.598052-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) APST status 1
2020-09-11 16:54:29.598085-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 4 : 0x0
2020-09-11 16:54:29.598088-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 3 : 0x9c420
2020-09-11 16:54:29.598092-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 2 : 0xc818
2020-09-11 16:54:29.598095-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 1 : 0xc818
2020-09-11 16:54:29.598099-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) entry 0 : 0xc818

you mean installing the debug version of Lilu? And then just set "nvram boot-args=-nvmefdbg" ?

Okay something strange happened, now my power consumption readings show an idle value of 0,00-0,06A. I uninstalled and reinstalled the kexts and rebuild the cache a few times. At first it shows that it didnt work (0,6A+ readings) but after a few reboots, SMC resets, and sitting idle for 20+ minutes, my readings finally show 0,00-0,1ish.

Earlier attempts somehow only show 0,3A idle, but now we've reached native territory. i guess its a kext cache thing. Not only do we reduce power consumption, we also reduce CPU temps by about 10 C (from 55-61ish to 45-49ish). That is really good. That means nvmefix has done its job.

Who knew the 970 Evo Plus can run 0,00A during idle in a macbook pro. Granted, the drive is a real power hog when its active, but there's potential for good battery life for light use. Wonder how real life battery life would be like.

Before:
before.jpg



After NVMeFix:
significant drop.jpg
 
Last edited:
you mean installing the debug version of Lilu? And then just set "nvram boot-args=-nvmefdbg" ?

Okay something strange happened, now my power consumption readings show an idle value of 0,00-0,06A. I uninstalled and reinstalled the kexts and rebuild the cache a few times. At first it shows that it didnt work (0,6A+ readings) but after a few reboots, SMC resets, and sitting idle for 20+ minutes, my readings finally show 0,00-0,1ish.

Earlier attempts somehow only show 0,3A idle, but now we've reached native territory. i guess its a kext cache thing. Not only do we reduce power consumption, we also reduce CPU temps by about 10 C (from 55-61ish to 45-49ish). That is really good. That means nvmefix has done its job.

Who knew the 970 Evo Plus can run 0,00A during idle in a macbook pro. Granted, the drive is a real power hog when its active, but there's potential for good battery life for light use. Wonder how real life battery life would be like.

Before:
View attachment 952474


After NVMeFix:
View attachment 952472
It always difficult to measure, because macOS does a lot even when idle. Especially after new installs. There are logging, caches, indexing etc.
 
  • Like
Reactions: _penguinman_
you mean installing the debug version of Lilu? And then just set "nvram boot-args=-nvmefdbg" ?

Okay something strange happened, now my power consumption readings show an idle value of 0,00-0,06A. I uninstalled and reinstalled the kexts and rebuild the cache a few times. At first it shows that it didnt work (0,6A+ readings) but after a few reboots, SMC resets, and sitting idle for 20+ minutes, my readings finally show 0,00-0,1ish.

Earlier attempts somehow only show 0,3A idle, but now we've reached native territory. i guess its a kext cache thing. Not only do we reduce power consumption, we also reduce CPU temps by about 10 C (from 55-61ish to 45-49ish). That is really good. That means nvmefix has done its job.

Who knew the 970 Evo Plus can run 0,00A during idle in a macbook pro. Granted, the drive is a real power hog when its active, but there's potential for good battery life for light use. Wonder how real life battery life would be like.

Before:
View attachment 952474


After NVMeFix:
View attachment 952472
Hi, can you share the .kext of Lilu and NVME fix that you use ? Been searching for it, but the information is kinda vague am not sure which file to use. Thank You !
 
MacBook Pro 13" early 2015, MacBookPro12,1, older Boot ROM Version: 186.0.0.0.0. Earlier I had updated to 10.14.6 Mojave, system update without using a USB thumb drive. I still had the old boot rom version.

Today, I tried a re-install using a installer from a USB thumb drive. It did not update the Boot ROM (to 192.0.0.0 or 196.0.0.0?).

I really don't want to install 10.15 Catalina, but would doing so from a USB thumb drive update the boot ROM? I might be able to install Catalina on a partition.

Do I need to re-install the Apple SSD in order to update the Boot ROM? If so, should I update that Apple SSD to 10.15 Catalina, even though I intend to put in my HP SSD EX900 and run 10.14.6 Mojave?

Thanks.

Edit, PS: It's been stable running a boot ROM version behind, but I did get two or three crashes - over 4 months - which the logs showed as NVME related. I'm mainly learning and preparing for Big Sur 11.1 or 11.2. The HP EX900 has been great; good speed and fine re: power.

And thanks for all of the great information here that has really helped extend a 2015 MacBook Pro, with it's nice keyboard. I tried a MacBook 12" while traveling, and the keyboard, well, its earned its poor reputation.
 
Last edited:
MacBook Pro 13" early 2015, MacBookPro12,1, older Boot ROM Version: 186.0.0.0.0. Earlier I had updated to 10.14.6 Mojave, system update without using a USB thumb drive. I still had the old boot rom version.

Today, I tried a re-install using a installer from a USB thumb drive. It did not update the Boot ROM (to 192.0.0.0 or 196.0.0.0?).

I really don't want to install 10.15 Catalina, but would doing so from a USB thumb drive update the boot ROM? I might be able to install Catalina on a partition.

Do I need to re-install the Apple SSD in order to update the Boot ROM? If so, should I update that Apple SSD to 10.15 Catalina, even though I intend to put in my HP SSD EX900 and run 10.14.6 Mojave?

Thanks.

Edit, PS: It's been stable running a boot ROM version behind, but I did get two or three crashes - over 4 months - which the logs showed as NVME related. I'm mainly learning and preparing for Big Sur 11.1 or 11.2. The HP EX900 has been great; good speed and fine re: power.

And thanks for all of the great information here that has really helped extend a 2015 MacBook Pro, with it's nice keyboard. I tried a MacBook 12" while traveling, and the keyboard, well, its earned its poor reputation.

I have the same model. Boot ROM v192 came with the latest Catalina update 10.15.6 Supplemental. If you don’t wish to install Catalina, then you’re stuck on your current version.
 
This thread was very helpful for me. I have an Early 2015 MacBook Air 13". When I bought it used a couple years ago, I replaced the 128gb that came in it with a 512gb Apple drive for which I paid a hefty price.. I've been wanting to increase storage for quite some time as I can't fit all my movies music, and photos/vids on it now, and have read this thread on and off for quite a while. Finally pulled the trigger. I ordered a 2tb XPG ADATA SX8200PNP and the Sintech long adapter off Amazon on Friday. Weren't supposed to show up till tomorrow, but showed up today. I've been working on getting this all back together most of the day. Did a new full Time Machine backup on 2tb external before I started. Formatted new drive with Catalina 10.15.6 startup USB. Restored from the backup. Everything back to normal. SSD finally finished encrypting. Started at 1430. Everything done by 2000. Just downloading all my movies now. Oh.. and stupid Photos is "uploading" all 13,000+ items.. I read in a different thread somewhere that it doesn't actually re-upload everything but is just checking with iCloud Photos for anything missing. THAT is still running... Taking forever.. Hope that's true.. I don't want 26000 items up in iCloud. After I'm done downloading all movies and music that I don't currently have on this, I'll wipe that external 2tb and do a full new backup on it. I'll have to get rid of the 1tb I was using cuz it won't be big enough by the time I'm done.. Anyway, thanks to all for the help! I'll post back after running this drive for a while and notify of any weird crashing issues etc. I've NEVER had any issue with this machine, or with the 2 Apple drives that have been in this machine(still have them). I hope this ADATA is as reliable. Any other thoughts from anyone on this machine model, that drive model, and adapter setup would be appreciated. Thanks! Oh, forgot to add... I went from
Original Apple 512gb drive
738.5mb write
948.8mb read

To new 2tb XPG ADATA SX8200PNP
1414.4 write
1484.1 read

HUGE storage and speed upgrades! and that's with encryption enabled.
and another note.. I used the heat sink that came with the drive. It seems the bottom case may be pressing down on this drive.. I hope it isn't.. it didn't seem to screw down as nicely as it was. I have a feeling it is. I hope that doesn't lead to failures later.. I'm guessing it may..
 
Last edited:
  • Like
Reactions: notgonna
I have the same model. Boot ROM v192 came with the latest Catalina update 10.15.6 Supplemental. If you don’t wish to install Catalina, then you’re stuck on your current version.

Thank you. Did you do a Catalina install from a USB drive? And did it update the boot ROM from an earlier version with the aftermarket SSD already having been installed?
 
This thread was very helpful for me. I have an Early 2015 MacBook Air 13". When I bought it used a couple years ago, I replaced the 128gb that came in it with a 512gb Apple drive for which I paid a hefty price.. I've been wanting to increase storage for quite some time as I can't fit all my movies music, and photos/vids on it now, and have read this thread on and off for quite a while. Finally pulled the trigger. I ordered a 2tb XPG ADATA SX8200PNP and the Sintech long adapter off Amazon on Friday. Weren't supposed to show up till tomorrow, but showed up today. I've been working on getting this all back together most of the day. Did a new full Time Machine backup on 2tb external before I started. Formatted new drive with Catalina 10.15.6 startup USB. Restored from the backup. Everything back to normal. SSD finally finished encrypting. Started at 1430. Everything done by 2000. Just downloading all my movies now. Oh.. and stupid Photos is "uploading" all 13,000+ items.. I read in a different thread somewhere that it doesn't actually re-upload everything but is just checking with iCloud Photos for anything missing. THAT is still running... Taking forever.. Hope that's true.. I don't want 26000 items up in iCloud. After I'm done downloading all movies and music that I don't currently have on this, I'll wipe that external 2tb and do a full new backup on it. I'll have to get rid of the 1tb I was using cuz it won't be big enough by the time I'm done.. Anyway, thanks to all for the help! I'll post back after running this drive for a while and notify of any weird crashing issues etc. I've NEVER had any issue with this machine, or with the 2 Apple drives that have been in this machine(still have them). I hope this ADATA is as reliable. Any other thoughts from anyone on this machine model, that drive model, and adapter setup would be appreciated. Thanks! Oh, forgot to add... I went from
Original Apple 512gb drive
738.5mb write
948.8mb read

To new 2tb XPG ADATA SX8200PNP
1414.4 write
1484.1 read

HUGE storage and speed upgrades! and that's with encryption enabled.
and another note.. I used the heat sink that came with the drive. It seems the bottom case may be pressing down on this drive.. I hope it isn't.. it didn't seem to screw down as nicely as it was. I have a feeling it is. I hope that doesn't lead to failures later.. I'm guessing it may..
One thing i can suggest is, to use short adapter for 8200 pro, because 8200 is a two sided SSD, thus it has extra thickness from the bottom part component. With long adapter, it has less space.
 
  • Like
Reactions: xboxbml
Okay, I see that there is an adapter for non Touch Bar models A1708 from 2016 and 2017. For single-sided drives only and those cards that are 2230 or 2242 (Sabrent Rocket has several 2242).


I have no connection in any way with this product or seller.

I also see a Sintech model on Amazon.
 
Last edited:
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Hello everyone, this is my first time posting on this forum. I don't know much about technology but I like trying to fix my own things. All your posts have been very helpful.

I have a Macbook Air 2013 and the SSD died last week. There was an interrogation sign on a black screen, and Utility Disk couldn't recognize any disk. I took it to the technician and he offered a second hand apple SSD but it was very expensive.

I purchased a XPG SX8200 PRO M.2 2280 PCIE Gen 3x4 SSD 256GB and an adapter from a turkish website (Sintech adapter is not sold in Turkey). I followed all instructions, removed the battery, installed the SSD with the adapter, etc.
I started the laptop with recovery mode but Disk Utility is not reading the new SSD.

I noticed most people used XPG SX8200 instead of XPG SX8200 PRO, can that be the reason is not working? Or is just the adapter?

Any info will be highly appreciated!!
 
Hi all!

So, with over 7000 posts, this is a bit of a daunting read :-/

I have a late 2013 MacBook Pro Retina 2.4Ghz Dual Core i5 running Catalina 10.15.6. My Boot ROM Version is: 162.0.0.0.0. I have a 2TB external HDD which I use to backup my MacBook Pro with Time Machine.

I wanted to upgrade my internal 256Gb SSD to 512Gb, and it seems like the Sabrent Rocket is a recommendation. I had hoped this would be a straightforward process, but having read some posts on here & elsewhere regarding sleep & other issues, I’m having second thoughts. I have also read of varying ways to correctly transfer the data. Is there an accepted way ahead for my machine (SSD model / adapter etc) that is known to work and won’t present with issues going forward?

Many thanks.
 
Last edited:
MacBook Pro 13" early 2015, MacBookPro12,1, older Boot ROM Version: 186.0.0.0.0. Earlier I had updated to 10.14.6 Mojave, system update without using a USB thumb drive. I still had the old boot rom version.

Today, I tried a re-install using a installer from a USB thumb drive. It did not update the Boot ROM (to 192.0.0.0 or 196.0.0.0?).

I really don't want to install 10.15 Catalina, but would doing so from a USB thumb drive update the boot ROM? I might be able to install Catalina on a partition.

Do I need to re-install the Apple SSD in order to update the Boot ROM? If so, should I update that Apple SSD to 10.15 Catalina, even though I intend to put in my HP SSD EX900 and run 10.14.6 Mojave?

Thanks.

Edit, PS: It's been stable running a boot ROM version behind, but I did get two or three crashes - over 4 months - which the logs showed as NVME related. I'm mainly learning and preparing for Big Sur 11.1 or 11.2. The HP EX900 has been great; good speed and fine re: power.

And thanks for all of the great information here that has really helped extend a 2015 MacBook Pro, with it's nice keyboard. I tried a MacBook 12" while traveling, and the keyboard, well, its earned its poor reputation.

Try installing Catalina on a separate partition. Thats how i updated my bootrom while still on Mojave. Some people managed to successfully do that on a 3rd party ssd. If not, you can always reinstall your original ssd to your macbook and install Catalina. Then update it to the latest supplemental update.

Catalina installs the bootrom on your macbook (EFI ? cmiw), its a firmware, it doesnt install it on the ssd, so it doesnt matter which ssd you use later. After you've finished updating it, you can even erase the catalina partition (that's what i did).
 
Last edited:
Is there an accepted way ahead for my machine (SSD model / adapter etc) that is known to work and won’t present with issues going forward?
Not likely to be perfect, but disable hibernation and you should not experience much issues.
 
Hello everyone, this is my first time posting on this forum. I don't know much about technology but I like trying to fix my own things. All your posts have been very helpful.

I have a Macbook Air 2013 and the SSD died last week. There was an interrogation sign on a black screen, and Utility Disk couldn't recognize any disk. I took it to the technician and he offered a second hand apple SSD but it was very expensive.

I purchased a XPG SX8200 PRO M.2 2280 PCIE Gen 3x4 SSD 256GB and an adapter from a turkish website (Sintech adapter is not sold in Turkey). I followed all instructions, removed the battery, installed the SSD with the adapter, etc.
I started the laptop with recovery mode but Disk Utility is not reading the new SSD.

I noticed most people used XPG SX8200 instead of XPG SX8200 PRO, can that be the reason is not working? Or is just the adapter?

Any info will be highly appreciated!!
What is your OS version when your old ssd dead ? If its lower than high sierra, then internet recovery wont be able to help you initialize the new ssd,

create a Mojave USB installer, and boot from that. If there are no issue with ssd or adapter, you should be able.to format the ssd using disk utility in the installer.
 
  • Like
Reactions: linamar
So is there a list here of the most preferred SSDs (ranked), that one can browse to determine which one is suitable for a certain model of Macbook Pro?
 
Try installing Catalina on a separate partition. Thats how i updated my bootrom while still on Mojave. Some people managed to successfully do that on a 3rd party ssd. If not, you can always reinstall your original ssd to your macbook and install Catalina. Then update it to the latest supplemental update.

Catalina installs the bootrom on your macbook (EFI ? cmiw), its a firmware, it doesnt install it on the ssd, so it doesnt matter which ssd you use later. After you've finished updating it, you can even erase the catalina partition (that's what i did).

Thank you. I do have a spare volume, and tried this as you described. But, instead of truly booting from the USB drive and directly going to Install macOS Catalina, I briefly get a Recovery window and then it goes straight into the four options, of which one is the reinstall, and then select Install and choose install Catalina. This doesn't update the internal to machine Boot Rom EFI.

I deleted my Recovery volumes,

https://www.makeuseof.com/tag/delete-repair-mac-recovery-partition
diskutil list

Don’t work:
diskutil eraseVolume APFS Blank disk2s3<code></code>
diskutil eraseVolume APFS Blank [disk2s3]<code></code>\

Works:
diskutil eraseVolume APFS Blank disk1s3

Yet, when restarting with the USB drive selected (built with DiskMaker X 9 for macOS Catalina), I see the same Recovery not the expected Install Catalina page.

Ugh. Any tips on how to avoid this Recovery process? Thanks.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.