https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
On 11/25/2021 10:11 AM, Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
That was an earlier machine than yours.
On Thursday, November 25, 2021 at 7:46:03 PM UTC-5, John wrote:are rare.
On 11/25/2021 10:11 AM, Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/ >>>That was an earlier machine than yours.
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
True, but the same issue and the same lack of any recovery options other than take in in for repair. It's also basically the same architecture scaled up. The new models have not been out there long enough for problems like this to show up unless they
In my 30 years Windows experience and DOS back to 1983 I have never seen a computer fail to boot unless the hard drive had failed. Even then it got past the POST. One of my laptops was dropped, totally destroying the screen, but it would still boot toand external monitor. Another had a broken LCD cable, and it still booted. That experience spans IBM, Tandy, Dell, Compaq, HP, ASUS and Toshiba.
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
A video which predates your claim that you had a problem...
...so it proves nothing about your claims.
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/ >>>A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.
You will do and say anything to not have to admit you are wrong!
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/ >>>A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.I didn't lie, Idiot.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are wrong!
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:Never said it did, but it's a M1 machine with no recovery options if it bricks. That's the point, idiot.
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:I didn't lie, Idiot.
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/ >>>>>A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are wrong!
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:Never said it did, but it's a M1 machine with no recovery options if it bricks. That's the point, idiot.
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:I didn't lie, Idiot.
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are wrong!
Then what was I supposedly wrong about, Idiot?
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:Never said it did, but it's a M1 machine with no recovery options if it bricks. That's the point, idiot.
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:I didn't lie, Idiot.
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are wrong!
Then what was I supposedly wrong about, Idiot?
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:Then what was I supposedly wrong about, Idiot?
On 2021-11-27 5:49 a.m., Thomas E. wrote:Never said it did, but it's a M1 machine with no recovery options if it bricks. That's the point, idiot.
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:I didn't lie, Idiot.
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are wrong!
That a documented M1 MacBook bricking behavior has nothing to do with the M1 MacBook I bought.
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recovery optionsI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all the
components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that
can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are
wrong!
if it bricks. That's the point, idiot.
Read this: https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&
iOS), Apple is locking down the macOS boot process. The M1 boot
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple. No
seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even an
external bootable drive won't boot. Yep, your Mac is bricked."
"It's as if the hidden volumes were part of the firmware, except they
aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot process
is locked down tight.
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recovery optionsI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all the
components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that
can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are
wrong!
if it bricks. That's the point, idiot.
Read this: https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&
iOS), Apple is locking down the macOS boot process. The M1 boot
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple. No
seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even an
external bootable drive won't boot. Yep, your Mac is bricked."
"It's as if the hidden volumes were part of the firmware, except they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot process
is locked down tight.
None of which proves you were being honest when you claimed yours went
into a boot loop.
On Tuesday, November 30, 2021 at 2:55:48 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan
wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recoveryI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all
the components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues
that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you
are wrong!
options if it bricks. That's the point, idiot.
Read this:
https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
iOS), Apple is locking down the macOS boot process. The M1 bootNone of which proves you were being honest when you claimed yours
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple.
No seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even
an external bootable drive won't boot. Yep, your Mac is
bricked."
"It's as if the hidden volumes were part of the firmware, except
they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot
process is locked down tight.
went into a boot loop.
Alan, you saw the boot loop video taken on my desk. You saw a photo
of my desk with the MacBook removed. Apple took the product back
outside their 14-day return policy. Explain how I could have faked
all that.
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:Never said it did, but it's a M1 machine with no recovery options if it bricks. That's the point, idiot.
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:I didn't lie, Idiot.
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are wrong!
Then what was I supposedly wrong about, Idiot?That a documented M1 MacBook bricking behavior has nothing to do with the M1 MacBook I bought.
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recovery optionsI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all the
components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that
can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are
wrong!
if it bricks. That's the point, idiot.
Read this: https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&
iOS), Apple is locking down the macOS boot process. The M1 boot
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple. No
seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even an
external bootable drive won't boot. Yep, your Mac is bricked."
"It's as if the hidden volumes were part of the firmware, except they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot process
is locked down tight.
None of which proves you were being honest when you claimed yours went
into a boot loop.
On 2021-11-30 12:10 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 2:55:48 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan
wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recoveryI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all
the components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues
that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you
are wrong!
options if it bricks. That's the point, idiot.
Read this:
https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
iOS), Apple is locking down the macOS boot process. The M1 bootNone of which proves you were being honest when you claimed yours
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple.
No seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even
an external bootable drive won't boot. Yep, your Mac is
bricked."
"It's as if the hidden volumes were part of the firmware, except
they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot
process is locked down tight.
went into a boot loop.
Alan, you saw the boot loop video taken on my desk. You saw a photo
of my desk with the MacBook removed. Apple took the product back
outside their 14-day return policy. Explain how I could have faked
all that.
I saw a video you claim was taken by you.
And Apple's return policy is 15 days, so you are continuing with your lie.
The fact that you continue that lie explains why I don't trust a word
you say.
On Tuesday, November 30, 2021 at 3:22:01 PM UTC-5, Alan wrote:
On 2021-11-30 12:10 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 2:55:48 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan
wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recoveryI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all
the components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues
that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you
are wrong!
options if it bricks. That's the point, idiot.
Read this:
https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
I saw a video you claim was taken by you.iOS), Apple is locking down the macOS boot process. The M1 bootNone of which proves you were being honest when you claimed yours
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple.
No seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even
an external bootable drive won't boot. Yep, your Mac is
bricked."
"It's as if the hidden volumes were part of the firmware, except
they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot
process is locked down tight.
went into a boot loop.
Alan, you saw the boot loop video taken on my desk. You saw a photo
of my desk with the MacBook removed. Apple took the product back
outside their 14-day return policy. Explain how I could have faked
all that.
And Apple's return policy is 15 days, so you are continuing with your lie. >>
The fact that you continue that lie explains why I don't trust a word
you say.
You are the one who lied. Apple's policy where I live is 14 days.
On Tuesday, November 30, 2021 at 12:13:45 PM UTC-7, Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:Never said it did, but it's a M1 machine with no recovery options if it bricks. That's the point, idiot.
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:I didn't lie, Idiot.
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are wrong!
It is easy to exaggerate by bragging about hardly any special cases different from what is common. What a better tactic from an honest advocates standpoint are the expected events.Then what was I supposedly wrong about, Idiot?That a documented M1 MacBook bricking behavior has nothing to do with the M1 MacBook I bought.
chrisv's indictment is misplaced up front, and not true second of all.
Is Michael Glasser AKA Snit destined to be just as much of a deceitful
liar as chrisv is already known as being? Any horrendously wounded welfare receiver could easily do the same. Don't look now, but I think chrisv
has a serious brocrush on Michael Glasser AKA Snit.
Can you stop seeking for my attention?
--
Curious how these posts are made? https://youtu.be/hYQ4Tg0r0g0
On 2021-12-01 7:13 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 3:22:01 PM UTC-5, Alan wrote:
On 2021-11-30 12:10 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 2:55:48 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan
wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recoveryI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all
the components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues
that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you
are wrong!
options if it bricks. That's the point, idiot.
Read this:
https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
I saw a video you claim was taken by you.iOS), Apple is locking down the macOS boot process. The M1 bootNone of which proves you were being honest when you claimed yours
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple.
No seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even
an external bootable drive won't boot. Yep, your Mac is
bricked."
"It's as if the hidden volumes were part of the firmware, except
they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot
process is locked down tight.
went into a boot loop.
Alan, you saw the boot loop video taken on my desk. You saw a photo
of my desk with the MacBook removed. Apple took the product back
outside their 14-day return policy. Explain how I could have faked
all that.
And Apple's return policy is 15 days, so you are continuing with your lie. >>
The fact that you continue that lie explains why I don't trust a word
you say.
You are the one who lied. Apple's policy where I live is 14 days.
So then you're admitting you lied too...
...since you presented Apple's policy for online educational sales.
On 2021-12-01 7:13 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 3:22:01 PM UTC-5, Alan wrote:
On 2021-11-30 12:10 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 2:55:48 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan
wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recoveryI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all
the components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues
that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you
are wrong!
options if it bricks. That's the point, idiot.
Read this:
https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
I saw a video you claim was taken by you.iOS), Apple is locking down the macOS boot process. The M1 bootNone of which proves you were being honest when you claimed yours
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple.
No seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even
an external bootable drive won't boot. Yep, your Mac is
bricked."
"It's as if the hidden volumes were part of the firmware, except
they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot
process is locked down tight.
went into a boot loop.
Alan, you saw the boot loop video taken on my desk. You saw a photo
of my desk with the MacBook removed. Apple took the product back
outside their 14-day return policy. Explain how I could have faked
all that.
And Apple's return policy is 15 days, so you are continuing with your lie. >>
The fact that you continue that lie explains why I don't trust a word
you say.
You are the one who lied. Apple's policy where I live is 14 days.
So then you're admitting you lied too...
...since you presented Apple's policy for online educational sales.
On Wednesday, December 1, 2021 at 10:49:52 PM UTC-5, Alan wrote:
On 2021-12-01 7:13 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 3:22:01 PM UTC-5, Alan wrote:So then you're admitting you lied too...
On 2021-11-30 12:10 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 2:55:48 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan
wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recoveryI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all
the components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues
that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer. >>>>>>>>>>>
You will do and say anything to not have to admit you
are wrong!
options if it bricks. That's the point, idiot.
Read this:
https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
I saw a video you claim was taken by you.iOS), Apple is locking down the macOS boot process. The M1 bootNone of which proves you were being honest when you claimed yours
process requires a working SSD to boot macOS. The SSD contains a >>>>>>> Signed System Volume that is cryptographically sealed by Apple.
No seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even
an external bootable drive won't boot. Yep, your Mac is
bricked."
"It's as if the hidden volumes were part of the firmware, except >>>>>>> they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot
process is locked down tight.
went into a boot loop.
Alan, you saw the boot loop video taken on my desk. You saw a photo
of my desk with the MacBook removed. Apple took the product back
outside their 14-day return policy. Explain how I could have faked
all that.
And Apple's return policy is 15 days, so you are continuing with your lie. >>>>
The fact that you continue that lie explains why I don't trust a word
you say.
You are the one who lied. Apple's policy where I live is 14 days.
...since you presented Apple's policy for online educational sales.
Which it exactly the same as all other U.S. sales, 1
On 2021-12-01 7:13 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 3:22:01 PM UTC-5, Alan wrote:
On 2021-11-30 12:10 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 2:55:48 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan
wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan
wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (&Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recoveryI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all
the components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues
that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you
are wrong!
options if it bricks. That's the point, idiot.
Read this:
https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
I saw a video you claim was taken by you.iOS), Apple is locking down the macOS boot process. The M1 bootNone of which proves you were being honest when you claimed yours
process requires a working SSD to boot macOS. The SSD contains a
Signed System Volume that is cryptographically sealed by Apple.
No seal, no bootable System."
"So if the internal drive on your M1 Mac fails completely, even
an external bootable drive won't boot. Yep, your Mac is
bricked."
"It's as if the hidden volumes were part of the firmware, except
they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot
process is locked down tight.
went into a boot loop.
Alan, you saw the boot loop video taken on my desk. You saw a photo
of my desk with the MacBook removed. Apple took the product back
outside their 14-day return policy. Explain how I could have faked
all that.
And Apple's return policy is 15 days, so you are continuing with your lie. >>
The fact that you continue that lie explains why I don't trust a word
you say.
You are the one who lied. Apple's policy where I live is 14 days.
So then you're admitting you lied too...
...since you presented Apple's policy for online educational sales.
On 2021-12-01 8:38 p.m., Thomas E. wrote:
On Wednesday, December 1, 2021 at 10:49:52 PM UTC-5, Alan wrote:
On 2021-12-01 7:13 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 3:22:01 PM UTC-5, Alan wrote:So then you're admitting you lied too...
On 2021-11-30 12:10 p.m., Thomas E. wrote:
On Tuesday, November 30, 2021 at 2:55:48 PM UTC-5, Alan wrote:Here was the solution
On 2021-11-30 11:19 a.m., Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote: >>>>>>>> On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan
wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan >>>>>>>>>>> wrote:
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/
"LOCKING DOWN THE BOOT To keep malware off Apple Silicon macOS (& >>>>>>> iOS), Apple is locking down the macOS boot process. The M1 boot >>>>>>> process requires a working SSD to boot macOS. The SSD contains a >>>>>>> Signed System Volume that is cryptographically sealed by Apple. >>>>>>> No seal, no bootable System."Then what was I supposedly wrong about, Idiot?Never said it did, but it's a M1 machine with no recoveryI didn't lie, Idiot.A video which predates your claim that you had a
"in the end Apple replaced the motherboard and all >>>>>>>>>>>>> the components inside, it was a hardware fault."
problem...
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues >>>>>>>>>>> that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer. >>>>>>>>>>>
You will do and say anything to not have to admit you
are wrong!
options if it bricks. That's the point, idiot.
Read this:
https://www.zdnet.com/article/how-bad-is-the-m1-macs-ssd-failure-problem/#:~:text=Your%20M1%20Mac%20may%20not%20boot%20at%20all,process%20requires%20a%20working%20SSD%20to%20boot%20macOS.
I saw a video you claim was taken by you.None of which proves you were being honest when you claimed yours >>>>>> went into a boot loop.
"So if the internal drive on your M1 Mac fails completely, even >>>>>>> an external bootable drive won't boot. Yep, your Mac is
bricked."
"It's as if the hidden volumes were part of the firmware, except >>>>>>> they aren't in firmware."
As was pointed out earlier a system board failure is also
unrecoverable from the boot menu. In any event, the M1 boot
process is locked down tight.
Alan, you saw the boot loop video taken on my desk. You saw a photo >>>>> of my desk with the MacBook removed. Apple took the product back
outside their 14-day return policy. Explain how I could have faked >>>>> all that.
And Apple's return policy is 15 days, so you are continuing with your lie.
The fact that you continue that lie explains why I don't trust a word >>>> you say.
You are the one who lied. Apple's policy where I live is 14 days.
...since you presented Apple's policy for online educational sales.
Which it exactly the same as all other U.S. sales, 1
So when you read the wrong policy...
(And don't pretend you knew it was the right policy)
...it's a mistake...
On Tuesday, November 30, 2021 at 7:36:40 PM UTC-7, STALKING_TARGET_14 wrote:
On Tuesday, November 30, 2021 at 12:13:45 PM UTC-7, Thomas E. wrote:
On Sunday, November 28, 2021 at 11:06:06 PM UTC-5, Alan wrote:
On 2021-11-28 7:57 p.m., Thomas E. wrote:
On Saturday, November 27, 2021 at 10:51:25 AM UTC-5, Alan wrote:
On 2021-11-27 5:49 a.m., Thomas E. wrote:Never said it did, but it's a M1 machine with no recovery options if it bricks. That's the point, idiot.
On Friday, November 26, 2021 at 6:38:09 PM UTC-5, Alan wrote:I didn't lie, Idiot.
On 2021-11-25 10:11 a.m., Thomas E. wrote:
https://forums.macrumors.com/threads/m1-macbook-pro-in-boot-loop.2306909/A video which predates your claim that you had a problem...
Here was the solution
"in the end Apple replaced the motherboard and all the components inside, it was a hardware fault."
...so it proves nothing about your claims.
You lie again! It proves that there are hardware issues that can make a M1 Mac boot loop. It's a precedent.
It DOESN'T prove anything about your particular computer.
You will do and say anything to not have to admit you are wrong! >>>
It is easy to exaggerate by bragging about hardly any special cases differentThen what was I supposedly wrong about, Idiot?That a documented M1 MacBook bricking behavior has nothing to do with the M1 MacBook I bought.
from what is common. What a better tactic from an honest advocates standpoint
are the expected events.
chrisv's indictment is misplaced up front, and not true second of all.
Is Michael Glasser AKA Snit destined to be just as much of a deceitful
liar as chrisv is already known as being? Any horrendously wounded welfare receiver could easily do the same. Don't look now, but I think chrisv
has a serious brocrush on Michael Glasser AKA Snit.
Can you stop seeking for my attention?
--Having to suffer the use of AZ cryptology would just confuse the general user.
Curious how these posts are made? https://youtu.be/hYQ4Tg0r0g0
His desire is to see me harmed by the spraying of the groups outside. And hey, that could kill this group. For the record, spending time potentially researching a problem isn't wasted time. Insisting you know more than everyone
else and attempting to convince Snit that it's true, as FromTheRafters tries to do? That is a waste.
Lying sack of shit AKA FromTheRafters does it every time. Then the deluge begins. Because the troll just has to run to other groups.
I want FromTheRafters to support their spamming accusation. Let's see the quotes FromTheRafters. When I accused FromTheRafters of trolling as Snit
I actually supported it with proof.
--
One Smart Penny! https://www.bing.com/search?q=Dustin%20Cook%20functional%20illiterate%20fraud Dustin Cook the functional illiterate fraud
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 292 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 206:15:25 |
| Calls: | 6,618 |
| Calls today: | 2 |
| Files: | 12,168 |
| Messages: | 5,316,882 |
