search

Ben216k / Patched-Sur

A simple, but powerful UI patcher for macOS Big Sur designed for everyone.
Other
318 stars 56 forks source link

Curl error when updating (Error 1x18) #17

Closed vasmane411 closed 2 years ago

vasmane411 commented 2 years ago

Describe the bug On downloading the update,

image

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context Add any other context about the problem here.

If there are any red boxes, click on them to copy the logs. Error 1x18 Message: " % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 11.5G 0 3565k 0 0 4264k 0 0:47:25 --:--:-- 0:47:25 4259k 0 11.5G 0 8474k 0 0 4615k 0 0:43:49 0:00:01 0:43:48 4613k 0 11.5G 0 12.8M 0 0 4621k 0 0:43:46 0:00:02 0:43:44 4621k ... curl: (18) transfer closed with 11624133880 bytes remaining to read" Output: ""

RokyHorror commented 2 years ago

Same thing happening to me, trying to update from macOS 11.6 to 11.6.1, what could I do? I'm using MacBook Pro mid-2012 13". Thanks in advance Schermata 2021-11-09 alle 12 30 02

blueysh commented 2 years ago

You've probably run out of storage space while Patched Sur was trying to download the patches.

blueysh commented 2 years ago

Or macOS, either which way that error is usually attributed to running out of storage space. You can go to settings in patched sur and then select clean leftovers

RokyHorror commented 2 years ago

Or macOS, either which way that error is usually attributed to running out of storage space. You can go to settings in patched sur and then select clean leftovers

Hi, thanks for the answer, unfortunately I tried the update again after cleaning up the leftovers as you suggested but the error still occurs. My internal SSD has at least 395GB of free space, so that shouldn't be the problem. Hope someone can help me fix and successfully update to macOS 11.6.1. This is the error message contained in the red box:

Error 1x18
Message: "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0 11.5G    0  462k    0     0   829k      0  4:03:48 --:--:--  4:03:48  828k
  0 11.5G    0 2861k    0     0  1849k      0  1:49:21  0:00:01  1:49:20 1848k
 ...
  6 11.5G    6  766M    0     0  2660k      0  1:16:01  0:04:55  1:11:06 2293k
curl: (18) transfer closed with 11624395952 bytes remaining to read"
Output: ""
vasmane411 commented 2 years ago

I haven’t tried it, but I am using the 1.02 post version. I have 652 gig free so it’s not a space issue either. Is there a way of just picking up the file locally, rather than downloading it. I’m also hearing there are issues with graphics and Monterrey not supporting in the latest version.

From: Gordon Fielden

Rossano Media UK Tel: +44 1892 884301 Ext 106 Email: @.***

On 9 Nov 2021, at 21:58, RokyHorror @.***> wrote:

 Or macOS, either which way that error is usually attributed to running out of storage space. You can go to settings in patched sur and then select clean leftovers

Hi, thanks for the answer, unfortunately I tried the update again after cleaning up the leftovers as you suggested but the error still occurs. I can't even copy the error code to post it entirely. My internal SSD has 395GB of free space, so that shouldn't be the problem. Hope someone can help me fix and successfully update to macOS 11.6.1

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

vasmane411 commented 2 years ago

Yep I have cleared the leftovers and still the same problem

Error 1x18

Message: "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

  0 11.5G    0 3293k    0     0  4606k      0  0:43:54 --:--:--  0:43:54 4599k

  0 11.5G    0 8810k    0     0  5131k      0  0:39:25  0:00:01  0:39:24 5128k

 ...

curl: (18) transfer closed with 11354730688 bytes remaining to read"

Output: ""

From: RokyHorror @.> Reply to: Ben216k/Patched-Sur @.> Date: Tuesday, 9 November 2021 at 21:58 To: Ben216k/Patched-Sur @.> Cc: vasmane411 @.>, Author @.***> Subject: Re: [Ben216k/Patched-Sur] Post patcher (Issue #17)

Or macOS, either which way that error is usually attributed to running out of storage space. You can go to settings in patched sur and then select clean leftovers

Hi, thanks for the answer, unfortunately I tried the update again after cleaning up the leftovers as you suggested but the error still occurs. I can't even copy the error code to post it entirely. My internal SSD has 395GB of free space, so that shouldn't be the problem. Hope someone can help me fix and successfully update to macOS 11.6.1

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

vasmane411 commented 2 years ago

Error 1x18

Message: "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

  0 11.5G    0 3293k    0     0  4606k      0  0:43:54 --:--:--  0:43:54 4599k

  0 11.5G    0 8810k    0     0  5131k      0  0:39:25  0:00:01  0:39:24 5128k

...   8 11.5G    8 1024M    0     0  5294k      0  0:38:12  0:03:18  0:34:54 5436k

curl: (18) transfer closed with 11354730688 bytes remaining to read"

Output: ""

From: RokyHorror @.> Reply to: Ben216k/Patched-Sur @.> Date: Tuesday, 9 November 2021 at 21:58 To: Ben216k/Patched-Sur @.> Cc: vasmane411 @.>, Author @.***> Subject: Re: [Ben216k/Patched-Sur] Post patcher (Issue #17)

Or macOS, either which way that error is usually attributed to running out of storage space. You can go to settings in patched sur and then select clean leftovers

Hi, thanks for the answer, unfortunately I tried the update again after cleaning up the leftovers as you suggested but the error still occurs. I can't even copy the error code to post it entirely. My internal SSD has 395GB of free space, so that shouldn't be the problem. Hope someone can help me fix and successfully update to macOS 11.6.1

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

Ben216k commented 2 years ago

Those are just curl/your WiFi acting up, and there's nothing I can do about it. Also btw I don't need 99% of that error, aka the gibberish part. Only the end matters.

What you can do is download the installer with Safari/FireFox/Chrome/whatever then tell Patched Sur to use that.

RokyHorror commented 2 years ago

Those are just curl/your WiFi acting up, and there's nothing I can do about it. Also btw I don't need 99% of that error, aka the gibberish part. Only the end matters.

What you can do is download the installer with Safari/FireFox/Chrome/whatever then tell Patched Sur to use that.

Hi, tanks for the reply, I also tried doing the update with a ethernet connection but the result is the same:

Error 1x18

curl: (18) transfer closed with 11354730688 bytes remaining to read"
Output: ""

You say we could download the installer directly from internet and then use patched sur with it, could you explain this alternative procedure in detail to make sure we can't go wrong? Many thanks in advance

blueysh commented 2 years ago

When you've got an installer you can select Browse where you select a macOS version to install. Then find the InstallAssistant.pkg that you downloaded for it.

RokyHorror commented 2 years ago

When you've got an installer you can select Browse where you select a macOS version to install. Then find the InstallAssistant.pkg that you downloaded for it.

Thank you very much for the explanation, finally after downloading the update with Safari I was able to install macOS 11.6.1 through the Patched Sur installer. Schermata 2021-11-10 alle 19 13 05

blueysh commented 2 years ago

When you've got an installer you can select Browse where you select a macOS version to install. Then find the InstallAssistant.pkg that you downloaded for it.

Thank you very much for the explanation, finally after downloading the update with Safari I was able to install macOS 11.6.1 through the Patched Sur installer.

Schermata 2021-11-10 alle 19 13 05

Great to hear! Glad you got it working

rotorgoat28 commented 2 years ago

Ive got a very similar issue trying to update Big Sur. Each time I get error 1x18. Im now downloading v11.6.1 pkg but can't see the 'Browse' option in the patched sur update app. It just gives release or beta? Any help is appreciated.

nonameplum commented 2 years ago
Screenshot 2021-12-19 at 10 54 48

Click on the View Other Versions and then on the box in the top-right corner.

g2ndy commented 2 years ago
Screenshot 2021-12-19 at 10 54 48

Click on the View Other Versions and then on the box in the top-right corner.

Thanks.

aaroncox82 commented 2 years ago

I have tried all the above and I am still having this error come up

Ben216k commented 2 years ago

If you saw something from Ozzie, just know he's an unstable adult who doesn't believe in apologizing or forgiving, but does believe in hypocrisy and lies.

So yeah, he's not going to solve your problems, don't interact with him, and ping me if anyones acting rude or is suggesting unreasonable things. Always check with me if a suggestion requires significant change. (For impersonation reasons, also check my name against the name of the GitHub repo.)

Also pitch in on other issues you're not apart of if you notice him (or anyone like him) there. Just tell the participants what I've told you.

aaroncox82 commented 2 years ago

Thank you but can you tell me how I can resolve this issue?

Please note, although I am not IT illiterate, I am not as technical as many on here.

Ben216k commented 2 years ago

Did you try downloading the package?

Get it from here then choose Browse and select the package file when Patched Sur has you choose a macOS version.

aaroncox82 commented 2 years ago

This is potentially where I get a little lost do I run the downloaded pkg file?

And where do I browse from?

aaroncox82 commented 2 years ago

I ask as it would not let me run the PKG file yesterday

Ben216k commented 2 years ago

Patched Sur installs the package for you, if that fails too then the package is corrupt.

Here's the browse button: image (Yes, I'm using an old screenshot)

aaroncox82 commented 2 years ago

IT seems like that link you sent for the pkg is corrupt as it will not open.I will try again later though.AaronOn Jan 7, 2022, at 1:53 PM, Ben @.> wrote:Patched Sur installs the package for you, if that fails too then the package is corrupt.Here's the browse button: —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.Message ID: @.>

Ben216k commented 2 years ago

The package link isn't corrupt, it'd be the package (it could of got corrupt during the download or you downloaded the wrong thing). In the chart on the site I sent, you should have found a InstallAssistant.pkg text (next to 11.6.2) which links to:

http://swcdn.apple.com/content/downloads/04/42/002-42341-A_4PL6G0S8GN/cs65avpi1aelh133lc36fy0ste3lihe71n/InstallAssistant.pkg

aaroncox82 commented 2 years ago

Hi Ben

Seems it was me I went through the Browser option you directed me to, it raised a new error, that being that my drives are not formatted correctly.

It is saying both my Mac and the USB if formatted in APFS Volume, which is not fully correct as my USB is set up in MacOS Extended. So I am guessing the Mac drive is the issue.

Sorry to be a pain but how can I format that drive to Mac OS and install Big Sur? I ask as I can not download on to there USB drive due to the above issue.

Aaron

On 7 Jan 2022, at 22:09, Ben @.***> wrote:

The package link isn't corrupt, it'd be the package. In the chart on the site I sent, you should have found a InstallAssistant.pkg text (next to 11.6.2) which links to:

http://swcdn.apple.com/content/downloads/04/42/002-42341-A_4PL6G0S8GN/cs65avpi1aelh133lc36fy0ste3lihe71n/InstallAssistant.pkg http://swcdn.apple.com/content/downloads/04/42/002-42341-A_4PL6G0S8GN/cs65avpi1aelh133lc36fy0ste3lihe71n/InstallAssistant.pkg — Reply to this email directly, view it on GitHub https://github.com/Ben216k/Patched-Sur/issues/17#issuecomment-1007775473, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFR2YKBLT44G4P6UKBLBW3UU5QALANCNFSM5HU6I6AA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.

Ben216k commented 2 years ago

Can you send a screenshot of error?

Also, it says to select a usb drive not your macOS volume (I can't filter the macOS drives from the error list), your macOS volume should always be APFS and your usb drive should always be MacOS Extended Journaled w/ GUID Partition Map.

aaroncox82 commented 2 years ago

Hi

The USB Drive I don’t think has a GUID Partition Map, and it will not let me Partition (the option is greyed out)…

Here is what comes up with the error…

Thank you so much for your continued help and patience with this.

Regards

Aaron

On 8 Jan 2022, at 15:14, Ben @.***> wrote:

Can you send a screenshot of error?

Also, it says to select a usb drive not your macOS volume, your macOS volume should always be APFS and your usb drive should always be MacOS Extended Journaled w/ GUID Partition Map.

— Reply to this email directly, view it on GitHub https://github.com/Ben216k/Patched-Sur/issues/17#issuecomment-1008021831, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFR2YKFTOUFZAM6PBTN54DUVBIENANCNFSM5HU6I6AA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.

vasmane411 commented 2 years ago

May I be as bold to say use the OpenCore legacy patcher, work's perfectly with Monterey, not download issues although it is command line process, but is very easy. There are a lot Video out there to watch. I gave up on patched-sur because like others found it didn’t work.

G

On 8 Jan 2022, at 15:56, aaroncox82 @.***> wrote:

Hi

The USB Drive I don’t think has a GUID Partition Map, and it will not let me Partition (the option is greyed out)…

Here is what comes up with the error…

Thank you so much for your continued help and patience with this.

Regards

Aaron

On 8 Jan 2022, at 15:14, Ben @.***> wrote:

Can you send a screenshot of error?

Also, it says to select a usb drive not your macOS volume, your macOS volume should always be APFS and your usb drive should always be MacOS Extended Journaled w/ GUID Partition Map.

— Reply to this email directly, view it on GitHub https://github.com/Ben216k/Patched-Sur/issues/17#issuecomment-1008021831, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFR2YKFTOUFZAM6PBTN54DUVBIENANCNFSM5HU6I6AA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.

— Reply to this email directly, view it on GitHub https://github.com/Ben216k/Patched-Sur/issues/17#issuecomment-1008037644, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASKPNF3IQTXTAWKCLOH4FU3UVBNCNANCNFSM5HU6I6AA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

Ben216k commented 2 years ago

This is an issue for a network error, and currently I am trying to solve another person's dilemma (was going to say issue, but it's not an issue) that's technically a user error. OCLP is not the perfect, just use this instead of even trying, option. Part of the reason Patched Sur had a downtime was OCLP users, because it somehow became this crazy perfect thing. (Yes, I've used OCLP before, I know how it works)

Ben216k commented 2 years ago

Here is what comes up with the error…

I can't see images sent with mail clients. You have to go to the GitHub site to send images.

Here's how you get it to have a GUID Partition Map:

  1. Open Disk Utility and in the View menu, choose Show All Devices
  2. Find the top-level device for your USB Drive, it should be the brand name, not the name you set for your drive.
  3. Click Erase, choose MacOS Extended Journaled and GUID Partition Map, and erase again to start it.
  4. Wait for it to finish.
  5. Click the Refresh button in Patched Sur and it should recognize the drive.
aaroncox82 commented 2 years ago

Hi BenThank you for your ongoing support and sorry about the delay.I am now having a new issue after getting the patch downloaded onto the USB.When I restart my PC and select the USB drive to Boot, a grey circle with a slash through comes up on a grey background. After this the PC turns off.Am I doing something wrong?AaronOn Jan 8, 2022, at 6:15 PM, Ben @.> wrote:Here is what comes up with the error…I can't see images sent with mail clients. You have to go to the GitHub site to send images.Here's how you get it to have a GUID Partition Map:Open Disk Utility and in the View menu, choose Show All DevicesFind the top-level device for your USB Drive, it should be the brand name, not the name you set for your drive.Click Erase, choose MacOS Extended Journaled and GUID Partition Map, and erase again to start it.Wait for it to finish.Click the Refresh button in Patched Sur and it should recognize the drive.—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.Message ID: @.>

Ben216k commented 2 years ago

You must have skipped the EFI Boot step. You should see a purple EFI Boot thing on the boot screen (with a symbol that looks similar to the symbol you're seeing), choose that instead of Install macOS Big Sur. Your Mac should immediately shut off after pressing it. After that, you can choose Install macOS Big Sur.

aaroncox82 commented 2 years ago

Thank you this has now worked perfectly.

Cheers for your patience and guidance.

Aaron

On 10 Jan 2022, at 13:49, Ben @.***> wrote:

You must have skipped the EFI Boot step. You should see a purple EFI Boot thing on the boot screen (with a symbol that looks similar to the symbol you're seeing), choose that instead of Install macOS Big Sur. Your Mac should immediately shut off after pressing it. After that, you can choose Install macOS Big Sur.

— Reply to this email directly, view it on GitHub https://github.com/Ben216k/Patched-Sur/issues/17#issuecomment-1008891007, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFR2YJOHVB34EB6LRV74ZDUVLPXBANCNFSM5HU6I6AA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.

toyotaman1178 commented 2 years ago

I assume it is this one he was saying I duplicated. in the same words that you used to be an ass ben you could have just said curl error.

Ben216k commented 2 years ago

(I have no idea how to write this without sounding like "an ass", so pretend it doesn't sound like that.

There are certain questions I stopped answering, mostly because I got tired of them, so I decided to try something else. I started saying "Duplicate issue" instead of "This issue is covered in #17", which was enough for most people to check the list. (As I said, I have no idea how to say this without sounding like "an ass")

There are only 8 open issues and you could have just checked before making a new issue or after I told you it was a duplicate. (Wow I really have no idea how to say that without sounding like "an ass")

aaroncox82 commented 2 years ago

Hi

I am not sure where this has come from but thanks to your help I am now working off Big Sur. So thank you!!!

Aaron

On 31 Jan 2022, at 05:02, Ben @.***> wrote:

(I have no idea how to write this without sounding like "an ass", so pretend it doesn't sound like that.

There are certain questions I stopped answering, mostly because I got tired of them, so I decided to try something else. I started saying "Duplicate issue" instead of "This issue is covered in #17 https://github.com/Ben216k/Patched-Sur/issues/17", which was enough for most people to check the list. (As I said, I have no idea how to say this without sounding like "an ass")

There are only 8 open issues and you could have just checked before making a new issue or after I told you it was a duplicate. (Wow I really have no idea how to say that without sounding like "an ass")

— Reply to this email directly, view it on GitHub https://github.com/Ben216k/Patched-Sur/issues/17#issuecomment-1025382267, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFR2YKBJCFI3HNV422MODDUYYJVJANCNFSM5HU6I6AA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.

Ben216k commented 2 years ago

Assuming this hasn't gotten a comment in 6 months and this is a dumb bug with curl not the patcher, I'm going to close this issue.