Scale 1680x1050 on rMB without an app

[5piN]

Yeah I have no idea how you got it working with EDID option or not in Big Sur haha.

when I do

csrutil disable
and then
csrutil authenticated-root disable

in recovery mode terminal

then normally booting into Big Sur and launching terminal:

sudo mount -o nobrowse -t apfs DISK_PATH MOUNT_PATH

and replace MOUNT_PATH with:

/System/Library/Displays/Contents/Resources/OVerrides/DisplayVendorID-610

ensuring I have the right DISK_PATH (the disk1s blah blah thats greyed out in my normal boot of Catalina)

(using that folder we are trying to be able to modify to get to those DisplayProduct-ID files to change values for in the array, manually or with that GitHub script, creating a new folder to be able to have write permissions to like ~/mount as was the placeholder example won't do us any good since we need to get to that path)

I get failed with 75 reliably.

that Github script returns that the file is read only and I'm SOL

seems Big Sur has new integrity checks beyond disabling SIP, maybe something changed in beta 4 / PB1 (same build) that doesn't allow one to tinker with that, that allowed you to on prior builds and will now carry over your changes

Bummer, means even if I move onto Big Sur final one day as my daily driver, I'll have to keep Catalina around for 1920x1200 toggle-able option .

Some more reference material I looked up:

Big Sur’s Signed System Volume: added security protection

From SIP to a protected read-only System volume, macOS 11 takes system protection a big step further with cryptographic verification.

eclecticlight.co

Can I mount the root (system) filesystem as writable in Big Sur?

After updating to big sur, I can no longer mount the root as writable (even with SIP disabled): sudo mount -uw / mount_apfs: volume could not be mounted: Permission denied mount: / failed with 66 ...

apple.stackexchange.com

If anyone figures out some magic, please let me know! I'd be willing to give it a shot

I'm running 11.0 Beta (20A5343j)

Initially was able to edit the file in
/System/Library/Displays/Contents/Resources/OVerrides/DisplayVendorID-610 using the above method but it did nothing.

Only got it to work using the script, have you got RDM installed?

 

[thadoggfather]

I'm running 11.0 Beta (20A5343j)

Initially was able to edit the file in
/System/Library/Displays/Contents/Resources/OVerrides/DisplayVendorID-610 using the above method but it did nothing.

Only got it to work using the script, have you got RDM installed?

Interesting!

1- so you put that as the mount path for yours , the full path to DisplayVendorID-610? And Terminal took it - no errors?

'Was able to edit the file and did nothing'

2- so only when you ran the GitHub script it worked? And before that you could replace the DisplayProduct-ID file, but a reboot did nothing to change resolution in System Preferences?

That build you're referencing is PB1. Did you make the edits on any Big Sur builds prior to then, or just on that one as a clean install?

--

Also RDM shouldn't have anything to do with anything, just makes it toggle-able from menu bar instead of buried in System Preferences->Displays. Its a matter of convenience. Doesn't factor into changing that DisplayProduct-ID file if that makes sense

I find these new layers of protection beyond csr-util funny because Craig was toting when discussing Big Sur how they've always allowed SIP to be disabled for hobbyist purposes, and for people that want to do that sort of thing for the right reason, Apple has always been 'encouraging' of it more or less

It appears not to be so.

Maybe someone smarter than I can help me understand where I'm snagged. I dont see why yours worked but mine wouldn't with the same instructions performed

 

[5piN]

Interesting!

1- so you put that as the mount path for yours , the full path to DisplayVendorID-610? And Terminal took it - no errors?

'Was able to edit the file and did nothing'

2- so only when you ran the GitHub script it worked? And before that you could replace the DisplayProduct-ID file, but a reboot did nothing to change resolution in System Preferences?

That build you're referencing is PB1. Did you make the edits on any Big Sur builds prior to then, or just on that one as a clean install?

--

Also RDM shouldn't have anything to do with anything, just makes it toggle-able from menu bar instead of buried in System Preferences->Displays. Its a matter of convenience. Doesn't factor into changing that DisplayProduct-ID file if that makes sense

I find these new layers of protection beyond csr-util funny because Craig was toting when discussing Big Sur how they've always allowed SIP to be disabled for hobbyist purposes, and for people that want to do that sort of thing for the right reason, Apple has always been 'encouraging' of it more or less

It appears not to be so.

Maybe someone smarter than I can help me understand where I'm snagged. I dont see why yours worked but mine wouldn't with the same instructions performed

1. correct I created a mount point, edited the file and then saved the snapshot. On reboot the file DisplayProductID-a027 had my changes but I couldn't change resolution.

2. it was an upgrade from Catalina

I was suggesting RDM to manually change the resolution without HIDPI.

In all fairness I tried so many things was driving me crazy .... who knows which combination got it to work! .... maybe if I have time I spin a VM to test.

 

[thadoggfather]

1. correct I created a mount point, edited the file and then saved the snapshot. On reboot the file DisplayProductID-a027 had my changes but I couldn't change resolution.

2. it was an upgrade from Catalina

I was suggesting RDM to manually change the resolution without HIDPI.

In all fairness I tried so many things was driving me crazy .... who knows which combination got it to work! .... maybe if I have time I spin a VM to test.

1-

created a mount point - specifically towards that folder that contained DispalyProductID-a027 (in your case) or you created a new arbitrary folder like ~/mount as the example provided?

2- I wonder if this is part of the equation, some piece of it carried over vs. a clean Big Sur install


--

im at wit's end for now, but maybe #1 will clarify something for my situation

 

[5piN]

1-

created a mount point - specifically towards that folder that contained DispalyProductID-a027 (in your case) or you created a new arbitrary folder like ~/mount as the example provided?

2- I wonder if this is part of the equation, some piece of it carried over vs. a clean Big Sur install


--

im at wit's end for now, but maybe #1 will clarify something for my situation

I used ~/mount

I will get sometime on the weekend. Will try it from a clean install!

 

[thadoggfather]

Alright guys I'm an idiot... got it working in Big Sur PB1 on my 2020 Air:
I can finally give the OS an actual try, since 1680x1050 is sometimes ok but I've gotten used to the real estate of 1920x1200 and certainly appreciate having the option.

didn't think to check Github issues reported while caught in an 'infinite loop' with this last night, and google translated Chinese to English to get sent in the right direction. What a waste of a few hours... but not a waste in the end because I got it working!

The dev created an alternate link for the 'Big Sur fixed' script but was getting error 404 - must be down. Still, was getting 'warmer'

the tl;dr for where things went wrong is the readme points you to a hosted file that isn't factoring in Big Sur fixes (which is weird, because the code itself has a commit from 2 months ago with comment 'Big Sur fixes')

SO follow these instructions to a tee and should be good

1) hold cmd+r on boot to get to Big Sur recovery (if dual booting, make Big Sur the primary boot OS and then do it to ensure BS recovery mode vs. Catalina, earlier versions, etc.):

In terminal run:
csrutil disable
csrutil authenticated-root disable

2) Reboot into OS

3) go to : https://github.com/mlch911/one-key-hidpi

Click code (top right green button)-> zip-> run hidpi.command
Allow it to run in System Preferences-> Security

4) select option 2 (HiDPI with EDID patches)
5) option6 to not change icon
6) option 6 for custom resolution

if on 13" MBP or Air input the following exactly with spaces:
1920x1200 1680x1050 1440x900 1280x800

if on 12" MB:
1680x1050 1440x900 1280x800 1152x720

7) reboot, cmd+r back into recovery mode
csrutil enable
csrutil authenticated-root enable

thanks @5piN for finding the GitHub and trying to troubleshoot with me. It finally clicked what I had to do.

I'll update original post to point to this one.

 

[5piN]

Nice work! But you may want to change
Step 3). to run "hidpi.command" in the unzipped folder.

 

[thadoggfather]

Nice work! But you may want to change
Step 3). to run "hidpi.command" in the unzipped folder.

Good catch , edited!

 

[Paulejonesy]

Just ran this on a late 2020 M1 Air. Works like a charm

 

[thadoggfather]

Just ran this on a late 2020 M1 Air. Works like a charm

Big Sur looks nice at 1920x1200 imo

still my most used resolution, and recently been booting in Big Sur more than Catalina on my i5 2020 Air.

 

[nanoblade]

Alright guys I'm an idiot... got it working in Big Sur PB1 on my 2020 Air:
I can finally give the OS an actual try, since 1680x1050 is sometimes ok but I've gotten used to the real estate of 1920x1200 and certainly appreciate having the option.

didn't think to check Github issues reported while caught in an 'infinite loop' with this last night, and google translated Chinese to English to get sent in the right direction. What a waste of a few hours... but not a waste in the end because I got it working!

The dev created an alternate link for the 'Big Sur fixed' script but was getting error 404 - must be down. Still, was getting 'warmer'

the tl;dr for where things went wrong is the readme points you to a hosted file that isn't factoring in Big Sur fixes (which is weird, because the code itself has a commit from 2 months ago with comment 'Big Sur fixes')

SO follow these instructions to a tee and should be good

1) hold cmd+r on boot to get to Big Sur recovery (if dual booting, make Big Sur the primary boot OS and then do it to ensure BS recovery mode vs. Catalina, earlier versions, etc.):

In terminal run:
csrutil disable
csrutil authenticated-root disable

2) Reboot into OS

3) go to : https://github.com/mlch911/one-key-hidpi

Click code (top right green button)-> zip-> run hidpi.command
Allow it to run in System Preferences-> Security

4) select option 2 (HiDPI with EDID patches)
5) option6 to not change icon
6) option 6 for custom resolution

if on 13" MBP or Air input the following exactly with spaces:
1920x1200 1680x1050 1440x900 1280x800

if on 12" MB:
1680x1050 1440x900 1280x800 1152x720

7) reboot, cmd+r back into recovery mode
csrutil enable
csrutil authenticated-root enable

thanks @5piN for finding the GitHub and trying to troubleshoot with me. It finally clicked what I had to do.

I'll update original post to point to this one.

Just followed this on a new M1 MacBook Air (except for holding power button to get into recovery mode of course). No luck unfortunately, after restart I just remain on the default resolutions & 1920x1200 is not available.

The script appears to run with no errors, not sure where to look to debug.

 

[thadoggfather]

Just followed this on a new M1 MacBook Air (except for holding power button to get into recovery mode of course). No luck unfortunately, after restart I just remain on the default resolutions & 1920x1200 is not available.

The script appears to run with no errors, not sure where to look to debug.

Did you pay special attention to step 1?

and step 6? those specific resolutions?

if so I'll defer to @Paulejonesy since I dont have an M1 machine, just the i5 2020 Air and seems this guy does and has done it successfully on an M1

 

[nanoblade]

Did you pay special attention to step 1?

and step 6? those specific resolutions?

if so I'll defer to @Paulejonesy since I dont have an M1 machine, just the i5 2020 Air and seems this guy does and has done it successfully on an M1

Yeah, followed step one - I had to disable FileVault encryption first in order to disable the authenticated-root.

Same with the resolutions, tried both with copy paste of the instructions & also typing them manually.

 

[thadoggfather]

Yeah, followed step one - I had to disable FileVault encryption first in order to disable the authenticated-root.

Same with the resolutions, tried both with copy paste of the instructions & also typing them manually.

you ran those terminal lines in boot recovery mode?

how do you mean held down power button for recovery mode?
Should be cmd+r and second disk on boot up. Unless it’s changed with m1

 

[nanoblade]

you ran those terminal lines in boot recovery mode?

how do you mean held down power button for recovery mode?
Should be cmd+r and second disk on boot up. Unless it’s changed with m1

Yes, it’s all changed with M1, you now hold power to get into a boot options menu & then enter recovery mode from there.

Does the old manual method of adding a line to the Display file still work or better to try and do it with the new GitHub script method?

 

[thadoggfather]

Yes, it’s all changed with M1, you now hold power to get into a boot options menu & then enter recovery mode from there.

Does the old manual method of adding a line to the Display file still work or better to try and do it with the new GitHub script method?

interesting

the folder permissions are super locked down so old method won’t work of drag and drop

now in step 3 you grabbed it the way I specified not just the installer in the readme?

because the committed code version is newer than the installer linked version in the readme

that’s where I had difficulties in the past

 

[nanoblade]

interesting

the folder permissions are super locked down so old method won’t work of drag and drop

now in step 3 you grabbed it the way I specified not just the installer in the readme?

because the committed code version is newer than the installer linked version in the readme

that’s where I had difficulties in the past

Yeah, I ran the hdpi.command script with appropriate options, I didn't get any error messages.

in /System/Library/Displays/Contents/Resources/Overrides/ there appear to be no changes e.g. no HDPI backup directory as expected & on restart there was no change in the available resolutions in System Preferences.

My display model is A03C & vendor is 610, however in /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-610/ there is no DisplayProductID-a03c file, am I missing something?

 

[nanoblade]

Just checked the latest GitHub commit & it seems the backup directory changed, I guess due to BigSur permissions, checking the new directory: /Library/Displays/Contents/Resources/Overrides it seems HDPI did run & created the below files, does anything look odd here?

 

[Photios]

What can I do to have 1536X960? I'm running a 2017 MacBook 12"

Thank you!

Alright guys I'm an idiot... got it working in Big Sur PB1 on my 2020 Air:
I can finally give the OS an actual try, since 1680x1050 is sometimes ok but I've gotten used to the real estate of 1920x1200 and certainly appreciate having the option.

didn't think to check Github issues reported while caught in an 'infinite loop' with this last night, and google translated Chinese to English to get sent in the right direction. What a waste of a few hours... but not a waste in the end because I got it working!

The dev created an alternate link for the 'Big Sur fixed' script but was getting error 404 - must be down. Still, was getting 'warmer'

the tl;dr for where things went wrong is the readme points you to a hosted file that isn't factoring in Big Sur fixes (which is weird, because the code itself has a commit from 2 months ago with comment 'Big Sur fixes')

SO follow these instructions to a tee and should be good

1) hold cmd+r on boot to get to Big Sur recovery (if dual booting, make Big Sur the primary boot OS and then do it to ensure BS recovery mode vs. Catalina, earlier versions, etc.):

In terminal run:
csrutil disable
csrutil authenticated-root disable

2) Reboot into OS

3) go to : https://github.com/mlch911/one-key-hidpi

Click code (top right green button)-> zip-> run hidpi.command
Allow it to run in System Preferences-> Security

4) select option 2 (HiDPI with EDID patches)
5) option6 to not change icon
6) option 6 for custom resolution

if on 13" MBP or Air input the following exactly with spaces:
1920x1200 1680x1050 1440x900 1280x800

if on 12" MB:
1680x1050 1440x900 1280x800 1152x720

7) reboot, cmd+r back into recovery mode
csrutil enable
csrutil authenticated-root enable

thanks @5piN for finding the GitHub and trying to troubleshoot with me. It finally clicked what I had to do.

I'll update original post to point to this one.

 

[Photios]

What can I do to have 1536X960? I'm running a 2017 MacBook 12"

Thank you!

Ok, I answered my own question... Instead of entering the resolutions cited above, I entered: 1680x1050 1536x960 1440x900 1280x800

It's all working great!!!!

 

[upsguy27]

Yeah, I ran the hdpi.command script with appropriate options, I didn't get any error messages.

in /System/Library/Displays/Contents/Resources/Overrides/ there appear to be no changes e.g. no HDPI backup directory as expected & on restart there was no change in the available resolutions in System Preferences.

My display model is A03C & vendor is 610, however in /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-610/ there is no DisplayProductID-a03c file, am I missing something?

How strange... I haven't tried running the script just yet but on my new M1 MBA I see the a03c file in the DisplayVendor folder, this is on Big Sur 11.1 beta 1

 

[upsguy27]

Just checked the latest GitHub commit & it seems the backup directory changed, I guess due to BigSur permissions, checking the new directory: /Library/Displays/Contents/Resources/Overrides it seems HDPI did run & created the below files, does anything look odd here?


View attachment 1676480

Also, I just tried the steps posted above and got the exact same outcome as this post, I'm going to try manually adding in the custom resolution line and see what happens

EDIT: Nope, didn't work... hopefully someone can figure out how to correctly change resolutions for M1 macs since I can't seem to get it to work!

 

[Paulejonesy]

Just ran this on a late 2020 M1 Air. Works like a charm

Er, apologies. I did run it, it did seem like it worked (no errors), but in fact the added resolutions were not there. I hope I've not had too many people scratching their heads....

 

[oklhost]

Ah, I'm not alone! Thats frustrating me since one hour I first powered on my new M1 MacBook Pro and I really was thinking about to switch back to Intel. I had contact to the founder of SwitchresX. He told me it's unsure if these hacks will ever be work again. Very frustrating... I used 1920x1200 since 2013 on my 13" MBPs. Please post into Apple Dev Forum and use Feedback Assistant (Thats what the SwitchresX guy told me) to let them know, we want it back!

Custom screen resolution for M1 Ma… | Apple Developer Forums

developer.apple.com

 

[fabdub]

See this post.
https://github.com/xzhih/one-key-hidpi/issues/159