I'm having troubles with replacing the trackpad on my MBPr 13" Late 2013. I've tried two replacement parts. With the first part only click works, but nothing else (I cannot move the mouse pointer at all), and with the second part nothing works at all. I tried the original cable and replacement cables but the results are the same (old trackpad works with the new cables / new trackpads do not work with the old cable...). So I'm kind of baffled because I could not find anybody having troubles doing this. One of the quirks of my makbook may be that it has a Russian keyboard. I've tried resetting SMC and NVRAM to no avail. Have anybody had any luck replacing the trackpad? Where did you get the parts? I'm kind of reluctant purchasing yet another one... Thanks

After a recent repair my MacBook Air M2 was working good as new. I used it 5 hours and shut it down. The next day after start up the keyboard was unresponsive. Touch pad was okay but no key worked. A restart and a power button restart did not help. I read about the SMC reset for older Macs not knowing the M2 does not have System Management Control. I pressed Shift + Control + Option + Power Button. The M2 started and the keyboard was still dead. I pushed the same key combination with power on. The M2 restarted **and the keyboard functioned again.** I understand those key presses are for DFU mode. I had no second Mac connected to the M2 with dead keys so no DFU action was taken. The M2 had gone bad after a glass of wine was spilled upon it. A local non-Apple authorized fix it shop replaced two capacitors and cleaned the circuit board and keyboard with isopropyl. I'm typing right now on the M2 that was broken, fixed, then lost its keyboard, then got its keyboard back by the key presses mentioned above. *Does anyone have an idea of what happened here? How could pressing DFU mode keys with no second Mac connected revive a dead keyboard?* I have bought an M4 since the keyboard quit on the M2 after the repair. I am thinking something else may also go bad on it at any time, but maybe not. It would be nice to have the $900 back for the M4 if this repaired M2 is good to go. Is there a keypress that will test the Mac M2 system for functionality and tell me if this repaired computer has an unseen issue?

I have two iPads, I think iPad 2, certainly that sort of age, which have been sitting in a cupboard for quite a few years. I pulled them out yesterday, and plugged them in to charge. On one of them, I got the grey Apple logo (like when the device does a cold start), which showed for about 30 seconds. Then the screen went black, flickering every 10 seconds or so. After a couple of minutes, the Apple logo came back, and the process repeated itself. I left it for about 12 hours, in case it was a lack of power, but it stayed the same. If I try to start it, I get the Apple logo for about 30 seconds, then the screen goes black and that's it. With the other one, I also left it charging for about 12 hours, but didn't even get the Apple logo. Nothing happened, either during charging or when I tried to start it up afterwards. As far as I know, both were working fine when they were last used. It would be nice if I could get them going again.

I recently picked up an iPhone 8 that someone had thrown away, since I have one myself and I don't turn down free original spare parts. Two days later I crack the back glass on mine... Since the spare is locked to a previous owner it will invariably have to be used as a donor (to the best of my knowledge). A bit of a waste since it seemed to work, but it is what it is. I mention it in case it affects the reuse of some specific part. I did some investigating and decided against trying to pry off the glass back, and instead decided that the best course of action would be to migrate my components to the spare metal frame and glass. My question, since I'd like to minimize work, is then: **What components must I transfer with the logic board, either because they won't work at all or won't work as well with a different logic board?** I found this list at iFixit : - Logic board - Touch ID sensor - Battery (if you don’t have a programmer) - Taptic engine (it’s also serial linked if I’m not mistaken) > if you use the screen from the none broken phone without re-programming it you’ll loose the truetone functionality. Is this list exhaustive? Is it correct? What about camera module, charging coil, etc? I'm asking because I want to have a plan before deciding to start, and not discover in the middle of it that I should have swapped the camera as well. The negative consequences of an unpaired battery wasn't clear to me either, so any explanation of what benefits I'd be missing after a non-paired battery swap would be greatly appreciated. I have iOS 16.7.10 installed, if that affects the list.

I accidentally unplugged my Mac and then it sent me to Windows 10 using Bootcamp. Now I'm trying to hold Opt so I can switch back to macOS but that's not working and it's showing me "Automatic repair couldn't fix your PC".

I got an iMac 27-inch Mid 2011 (A1312, EMC 2429) that does not fully boot. Here’s what happens: - Pressing the power button, the fans, HDD, and optical drive spin up. - The startup chime plays, but nothing appears on the screen. - After a few seconds, the fans ramp up to maximum speed, then the system shuts down. I opened it up and found a burnt inductor (L9000) near C9020, right next to the INT DP connector on the motherboard. The diagnostic LEDs behave as follows: - LED 1: Turns on - LED 2: Turns on - LED 3: Turns on - LED 4: Stays off Additional info: - It has 32GB RAM (all slots populated) - The GPU is an AMD Radeon HD 6970M - I also tried booting it without the dedicated GPU, but that didn’t change anything. - I tried booting in Safe Mode (Shift key) – no response. - I tried an external monitor via Mini DisplayPort – no signal. - I checked with a multimeter, and 12V is present on the pins where the inductor was. **Question**: Could replacing the burnt inductor (L9001) restore the functionality? >

I’m working on an A2179 2020 MBA. My old friend spilled something in the topcase and right-side keys weren’t working. Everything else was working fine when I took possession. I did the repair once with a case/battery combination unit. When I powered on, the fan went full speed and the CPU was throttled to a near halt. It booted and worked, but barely. Also, the battery wouldn’t receive charge. I read elsewhere that behavior can result if there is a thermal sensor somewhere not properly sending information, or if the battery is completely dead. I reseated all of the cables to no avail, so I returned the component figuring there was an error with the battery or its daughterboard. I ordered a better grade battery (from here!) and case. I repeated the repair and I’m getting the same result. I’ve gone through and reseated the cables. Same thing. So I’m stumped. Here are the basic conditions: 1. Previous to disassembly, the CPU worked fine. The only issue was problematic keying. Work arounds included external keyboard. 2. Two repairs with different components have both resulted in the computer protecting itself. 3. I’m reasonably certain the second battery and its controller are good quality. 4. I've come to learn this is a not uncommon issue with MBA topcase and screen repairs, and I even read a conversation about it with an iMac. Reseating cables hasn’t fixed it. Having said that, I am wondering about some of the cabling around the trackpad. I’m also wondering about the tiny daughterboard just north of the trackpad on the A2179. I do wonder if something is goofy with the power/fingerprint button. I may order a new one of those, but that shouldn’t be sufficient for the unit to go into temperature protection. Any thoughts or advice is super appreciated. Cheers!

I had a corrupt APFS volume (caused by bad SATA connection — has since been alleviated) of 150 GB reported by First Aid so I decided to create a new volume and reinstall macOS there. In the end of my migration efforts the files I deleted from the bad volume didn't free up any space for any volumes in the same container, so I decided to completely delete the volume using Disk Utility. After doing that I still don't have any more free space in the container, according to Disk Utility. Instead I now have "1 Not Mounted" volume taking up all that space (155.15 GB). I don't see this volume with diskutil list:

% diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         321.5 GB   disk0s2
   3:           Linux Filesystem                         52.5 GB    disk0s3
   4:       Microsoft Basic Data Windows                 125.9 GB   disk0s4

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +321.5 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Preboot                 4.9 GB     disk1s2
   2:                APFS Volume Recovery                1.7 GB     disk1s3
   3:                APFS Volume VM                      1.1 GB     disk1s4
   4:                APFS Volume Ventura – data          67.1 GB    disk1s5
   5:                APFS Volume Ventura                 9.4 GB     disk1s6
   6:              APFS Snapshot com.apple.bless.B70F... 9.4 GB     disk1s6s1
   7:                APFS Volume Mojave igen             78.0 GB    disk1s8

It seems ~160 GB have gone missing. I'm not sure what to make of that. My question: **How do I free up the invisible space?** #### Additional info I've run First Aid (in Ventura) several times on the old volume, the new volume, and the container during my migration efforts. As far as I know it has only ever complained about the old volume. Now, after I've set everything up on the new volume and deleted the old one, running First Aid on the entire container seems to tell me that my *new* volume is corrupt ("The volume /dev/rdisk1s8 was found to be corrupt"). Really? I just created it with the sole purpose to fix that exact problem. Did I copy the old volume's corruption with its files..? Also, "overallocation detected on Main device" -- sounds relevant, but I don't know... What does "Main device" refer to?

Running First Aid on “AppleAPFSMedia” (disk1)

Verifying the startup volume will cause this computer to stop responding.

Verifying storage system
Using live mode.
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking the container superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking the encryption key structures.
Checking volume /dev/rdisk1s2.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s2 appears to be OK.
Checking volume /dev/rdisk1s3.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s3 appears to be OK.
Checking volume /dev/rdisk1s4.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s4 appears to be OK.
Checking volume /dev/rdisk1s5.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the document ID tree.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s5 appears to be OK.
Checking volume /dev/rdisk1s6.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 2 (com.apple.os.update-E7844E4A19775C7E8469F08126D2C007CABC3427263D35492B1C05AD70A95CF3)
Checking snapshot 2 of 2 (com.apple.bless.B70FD331-59F2-44A4-9745-6C86F42CA118)
Checking the fsroot tree.
Checking the file extent tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s6 appears to be OK.
Checking volume /dev/rdisk1s7.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s7 appears to be OK.
Checking volume /dev/rdisk1s8.
Checking the APFS volume superblock.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the document ID tree.
Checking the fsroot tree.
warning: inode (id 1218814): Resource Fork xattr is missing for compressed file
warning: inode (id 1218859): Resource Fork xattr is missing for compressed file
warning: inode (id 1218861): Resource Fork xattr is missing for compressed file
warning: inode (id 1218864): Resource Fork xattr is missing for compressed file
warning: inode (id 1218866): Resource Fork xattr is missing for compressed file
warning: inode (id 1218868): Resource Fork xattr is missing for compressed file
warning: inode (id 1218871): Resource Fork xattr is missing for compressed file
warning: inode (id 1218873): Resource Fork xattr is missing for compressed file
warning: inode (id 1218876): Resource Fork xattr is missing for compressed file
warning: inode (id 1218878): Resource Fork xattr is missing for compressed file
warning: inode (id 1218880): Resource Fork xattr is missing for compressed file
warning: inode (id 1218882): Resource Fork xattr is missing for compressed file
warning: inode (id 1218886): Resource Fork xattr is missing for compressed file
warning: inode (id 1218890): Resource Fork xattr is missing for compressed file
warning: inode (id 1218896): Resource Fork xattr is missing for compressed file
warning: inode (id 1218898): Resource Fork xattr is missing for compressed file
warning: inode (id 1218904): Resource Fork xattr is missing for compressed file
warning: inode (id 1218906): Resource Fork xattr is missing for compressed file
warning: inode (id 1218910): Resource Fork xattr is missing for compressed file
warning: inode (id 1218912): Resource Fork xattr is missing for compressed file
warning: inode (id 1218914): Resource Fork xattr is missing for compressed file
warning: inode (id 1218916): Resource Fork xattr is missing for compressed file
warning: inode (id 1218920): Resource Fork xattr is missing for compressed file
warning: inode (id 1218922): Resource Fork xattr is missing for compressed file
warning: inode (id 1218924): Resource Fork xattr is missing for compressed file
warning: inode (id 1218926): Resource Fork xattr is missing for compressed file
warning: inode (id 1218928): Resource Fork xattr is missing for compressed file
warning: inode (id 1218930): Resource Fork xattr is missing for compressed file
warning: inode (id 1218932): Resource Fork xattr is missing for compressed file
warning: inode (id 1218934): Resource Fork xattr is missing for compressed file
warning: inode (id 1218936): Resource Fork xattr is missing for compressed file
warning: inode (id 1218938): Resource Fork xattr is missing for compressed file
warning: inode (id 1218940): Resource Fork xattr is missing for compressed file
warning: inode (id 1218942): Resource Fork xattr is missing for compressed file
warning: inode (id 1218944): Resource Fork xattr is missing for compressed file
warning: inode (id 1218946): Resource Fork xattr is missing for compressed file
warning: inode (id 1218948): Resource Fork xattr is missing for compressed file
warning: inode (id 1218950): Resource Fork xattr is missing for compressed file
warning: inode (id 1218952): Resource Fork xattr is missing for compressed file
warning: inode (id 1218954): Resource Fork xattr is missing for compressed file
warning: inode (id 1218956): Resource Fork xattr is missing for compressed file
warning: inode (id 1218958): Resource Fork xattr is missing for compressed file
warning: inode (id 1218960): Resource Fork xattr is missing for compressed file
warning: inode (id 1218962): Resource Fork xattr is missing for compressed file
warning: inode (id 1218964): Resource Fork xattr is missing for compressed file
warning: inode (id 1218966): Resource Fork xattr is missing for compressed file
warning: inode (id 1218968): Resource Fork xattr is missing for compressed file
warning: inode (id 1218970): Resource Fork xattr is missing for compressed file
warning: inode (id 1218972): Resource Fork xattr is missing for compressed file
warning: inode (id 1218974): Resource Fork xattr is missing for compressed file
Too many warnings of this type generated; suppressing subsequent ones.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s8 was found to be corrupt and needs to be repaired.
Verifying allocated space.
warning: container keybag (63873836+1): UUID CB2248E1-C55E-44EC-86BA-5585934659E6 of entry 0 (tag 3) does not reference any volume
warning: overallocation detected on Main device: (0x28d+1) bitmap address (0xe92f9)
warning: overallocation detected on Main device: (0x2db+1) bitmap address (0xe92f9)
warning: overallocation detected on Main device: (0x321+1) bitmap address (0xe92f9)
warning: overallocation detected on Main device: (0x19ae9+5) bitmap address (0xe9532)
warning: overallocation detected on Main device: (0x206e7+1) bitmap address (0xe9533)
warning: overallocation detected on Main device: (0x224fe+1) bitmap address (0xe9533)
warning: overallocation detected on Main device: (0x22bca+1) bitmap address (0xe9533)
warning: overallocation detected on Main device: (0x28497+2) bitmap address (0xe956c)
warning: overallocation detected on Main device: (0x2b2c7+1) bitmap address (0xe956c)
warning: overallocation detected on Main device: (0x2b2d0+1) bitmap address (0xe956c)
warning: overallocation detected on Main device: (0x2b3a7+1) bitmap address (0xe956c)
warning: overallocation detected on Main device: (0x2dee1+1) bitmap address (0xe956c)
warning: overallocation detected on Main device: (0x2df63+16) bitmap address (0xe956c)
warning: overallocation detected on Main device: (0x33097+3) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x33175+1) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x33187+1) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x33221+1) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x34767+1) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x34769+1) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x3476b+1) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x347a0+2) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x347af+1) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x34d9c+1) bitmap address (0xe94c8)
warning: overallocation detected on Main device: (0x3ec55+1) bitmap address (0xe9535)
warning: overallocation detected on Main device: (0x48226+1) bitmap address (0xe9c68)
warning: overallocation detected on Main device: (0x48232+1) bitmap address (0xe9c68)
warning: overallocation detected on Main device: (0x70001+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70003+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x7000d+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70012+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x7001f+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70065+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x7007d+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70093+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x7009f+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x700b3+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x700ca+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70110+2) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70194+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x701a0+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x701a3+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x701a9+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x701bd+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x701df+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70204+2) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70217+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70221+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70234+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x70287+1) bitmap address (0xe9113)
warning: overallocation detected on Main device: (0x702d1+1) bitmap address (0xe9113)
Too many warnings of this type generated; suppressing subsequent ones.
Performing deferred repairs.
warning: need to clear bsd flags (0x20) in inode (object-id 1218814)
Skipped 78/78 repairs of this type in total.
warning: found orphan/invalid xattr (id 1218814, name com.apple.decmpfs)
Skipped 78/78 repairs of this type in total.
The container /dev/disk0s2 appears to be OK.
Storage system check exit code is 0.

Operation successful.

Not entirely sure what I'm supposed to do with this information. I've since tried repairing the new volume and the container several times in recovery mode (only Mojave recovery is available on this machine). No effect. So basically I'm in this situation: 1. Disk Utility complains about corrupt volume that is unrepairable -- container is "OK" 2. I create a new volume and delete the bad volume lest I run out of space, whereupon I reclaim no space 3. Disk Utility complains about the newly created volume being "corrupt" and insists it be repaired, without actually ever repairing it (and simultaneously concluding that the volume is "OK") 4. I conclude that nothing I'm doing seems to make any difference. Do I continue following the breadcrumbs from Disk Utility, or do I do something else? Suggestions welcome.

So let's get this out of the way first. I know this PC is very old now. I got it for free from a friend and with my "more than beginner" electronics repair knowlege, I would like to learn further and if possible fix this computer. **Diagnosing:** Plugging in the AC cable, it remains OFF. Upon pressing the power button, I can hear fans, HDD and disc reader come to life and remain like that, fans stay at a low speed like during normal operation. No chime, nothing. After seeing this, I decided to swap RAM, try all the slots with just one stick and swap in between 2 ram sticks for each slot at a time. Nothing. So I knew it was time to take it apart, after removing the screen and finding diagnostic LEDs, after plugging in AC cable, LED1 is green, which is a good sign. After pressing the power button, LED1 stays on but all other LEDs are off. Fans spinning, now going to MAX speed after 15 seconds as it should when unplugging temp sensor on the screen, and everything remains as mentioned before. The fact fans go full speed tells me that motherboard works, but main components aren't getting proper power to work. This is where I got stuck as I don't want to disassemble the iMac further before doing some more research. It does react to the power button, shuts down after holding it down and all. I wasn't able to find this exact problem anywhere on the internet, so I am asking for your help. From my research it appears as if the power supply switches on but the motherboard does not power on properly, maybe faulty voltage regulators, PSU not sending proper voltage, who knows. My friend gave it to me thinking the GPU is dead but I don't think so from the diagnosis to this point. Maybe both, GPU and motherboard are faulty, I am lost as it could be anything with these machines. It seems that the PSU works by the fact that all accessory parts get power but it may just be "lying" to me. Can anyone provide guidance on triage or repair for this vintage of Mac and described symptoms?

I’m running Sonoma. My external HDD has 4 partition (volumes). One of them can’t be repaired by macOS. However when plugged to old Mac with High Sierra it shows no problem. Is there a known fix for this?

I’ve been using my iPhone 11 for more than 5 years as my daily phone for communication and work, and it’s still performing well. However, I know that phone batteries have a limited lifespan due to chemical aging . The battery health has declined, but I can still get around 12 hours of use. I’m concerned that the battery might affect the LCD since the phone sometimes gets hot. Should I replace the battery soon?

This weekend my Apple TV 4K (1st gen) started erratically responding to remote commands, and then a very small circular progress indicator in the middle of the screen. I waited for a long time, then removed the power and connected again, and this time it exhibited the dreaded blinking white light of death. The TV it's connected to just says "No signal". I tried removing the power for long periods of time and connecting again, still the blinking white light. I was surprised to learn that the 4K model lost the USB cable that would allow me to connect it to a computer and try to restore it. I called Apple, and since it's out of warranty, they said I have to pay a $149 repair fee (actually more in my country, but either way it makes to sense to pay this to get an older-generation one when the price for the latest one is the same). Is there really nothing else that can be done? Perhaps a hidden USB connector inside the Apple TV if I were to open it up? Maybe a magic sequence of buttons on the remote, a hidden button or touch surface that triggers a DFU mode/restore operation? Or is it really a $149 paperweight/e-waste now? I just can't believe a $149 device is completely disposable like this.

> Version of Macbook: Macbook Air M1 late 2020 A2337 I’ve replaced my macbook keyboard at home, but the new keyboard has a little gap between the topcase frame because I couldn’t insert the screws on there. The original macbook screws are not fit on the holes of the frame where the rivet screws should be inserted. I need an alternative screws for this task. Are there any recommendation screws to solve the problem?

I have a plan to use a cellophane tape to attach the button-looking plug (the orange circle on picture) on the top case to prevent physical disconnection from the inside while I’m using the machine. The tape that I will use is just a normal transparent tape that you can easily find from anywhere such as at school, a company or home etc. What I’m worrying about is malformation of the tape by heat inside of the top case. Eventually, the battery pack and the plug don’t physically contact wach other, but I don’t want to use the tape on uncertain situation. Will the battery heat melt down the cellophane tape and cause any potential damage on the machine?

I tried to replace the imac screen and accidentally scratched the black frame that comes on the back side of the screen around the lcd area. Just forgot about it and now it has some really noticeable and visible scratches. I thought it would be easy to repair just by dyeing it out, but nope. I tried different kinds of paints but none works. They all looks gray, significantly lighter than original. Btw, original border looks like a kinda adhesive tape or coating, not a dye, so I tried a different kinds of black tapes with heat gun, like insulating and so on, as well as different kinds of dissolved plastics - nothing works, all are grey, not black. The closest and darkest dye was some acrylic paint which still looks grey and still significantly lighter than original. I'm looking for advice. How can I repair this band to be visually black like the original part?

I got some moisture damage on my M1 MacBook Pro that I bought last year (there’s a greenish spot on the logic board). A third-party local repair shop says that the moisture spot is in a place where the voltage difference isn’t very high and it can be repaired (for much less than the cost of replacing the entire board). My question is — if this person tries to repair it but it doesn’t work, can I still bring the MacBook Pro to Apple and ask them to replace the entire logic board with a brand new one? Can they just refuse to replace the board if they think it’s been touched by a third-party repair shop? I know my warranty gets voided, but outside the warranty, can the entire official Apple repair service get voided? Really nervous, so I’d appreciate a response a lot!

I found some stains on my MacBook Pro M1 2020 display glass at the top of the screen. They won't go away with regular cleaning. I'm worried about how they look and if they'll cause problems. Can anyone suggest simple ways or products clean these stains off my laptop screen? Also, how can I stop this from happening again? *I've hardened up the contrast a lot in this & cropped to the most significant area, to make it easier to see…*

I have a 13-inch MacBook Pro M1 and my screen is broken. I found another MBP, same version exactly, from a friend of mine. I would like to know if I can replace my screen with the one from my friends laptop. Am I able to do it or I will face any problem with serial numbers?

I wanted to replace the screen on an iPhone 8 and failed at the first step: One of the screws next to lightning port is stuck. The one the right comes off fine, while the one on the left doesn't provide a hold for the screwdriver. I can spin the screwdriver forever without loosening the screw. There was a little bit of grip at my first intent, but even that's gone by now. It seems I've worsened the problem. What are my options?

I have had a problem with my keyboard for over a year. Most of the time the letters between E and O don't work, so I'm forced to use another keyboard. I have noticed that pushing on the keys can help get them working again for a while. Therefore I think this is a hardware issue. I installed a new battery but it didn't help. I have blown compressed air around the keys with no luck. The Macbook is a 15-inch, Mid 2012, i7 and I updated the RAM to 16gb and installed a 1TB SSD, two years ago. The laptop works really well if I could just get my keyboard working. I have found replacement keyboards, basically the front panel, on ebay and there not expensive so I'm tempted to try and replace it. Is there anything I can do to confirm that it is a keyboard hardware issue?