Announcement

Collapse
No announcement yet.

User Profile

Collapse

Profile Sidebar

Collapse
Avatar
ugamazing
Senior Member
Last Activity: 06-20-2024, 04:39 PM
Joined: 06-26-2013
Location: georgia
  •  
  • Filter
  • Time
  • Show
  • Source
Clear All
new posts

  • Most likely a damaged T2 in this case. You actually can throw any SPI ROM on these to check DFU conflictions. If the original ROM chip was corrupted/damaged, then that leads me even-more to suspect the T2 in this case. I bet the board is cycling during DFU due to T2 losing communications to/with PMU/U7800, or halting due to a damaged internal DFU/restore voltage (which you guys are onto now). The few times I've found one cycling, it was always the T2 at fault. If no liquid were involved, I'd have a bit higher hopes.
    See more | Go to post

    Leave a comment:


  • 820-02020 Super Weird Issue: Keyboard Input Character Map "Wrong"?

    So, I have a really bizarre issue that I'm struggling to identify the cause of. Working on an 820-02020 board with some bizarre keyboard/input-source character mapping. My suspicion is a possible damaged SPI ROM (U1970), perhaps, but I'm really not sure in this case:

    1. The issue is pretty weird, but when installing MacOS, I noticed my WiFi password did not work. I quickly realized the special characters (!@#$%^& etc) were not mapping correctly.

    2. I noticed the keyboard layout/input-source is defaulting to JAPANESE every single time I restore the board. I am not...
    See more | Go to post
    Last edited by ugamazing; 04-10-2024, 09:04 AM.

  • Do note that the PMIC likely blew from a shorted/cracked ceramic capacitor, so make sure you trace the actual short and find the culprit once you remove PMIC.

    You can replace PMIC from that board and you should get most functions. I cannot confirm if there will be ZERO problems, but we have swapped those two PMICs (specifically 02016-->02098) and it worked. We have also done 02016-->02020, and it worked. So, I would presume 02020-->02098 will work fine as well. However, it's best-practice to always source programmed ICs from identical models. In this case it may be OK; try...
    See more | Go to post

    Leave a comment:


  • Re: Macbook Pro 820-01700 - 2TB Nand bin dump request

    Here are the 'rules' for replacing nands:

    1. You can swap like-sets from like-model boards. Manufacturer not important as long as the board model is identical (you cannot mix manufacturers). If you swap from varying configurations, you must mind all SSD/board cfg resistors.

    2. If swapping only a PARTIAL SET--i.e. only 'one side' of an 820-01700 is shorted, you MUST program (JCP13) the new chips with empty/blank firmware/boot-sector-blocks, or the board will give an SSD error when restoring. You can either...
    See more | Go to post

    Leave a comment:


  • Re: Unserialized M1 Pro



    Yup, you just did the normal MDM bypass method that many others have done over the past ~4-5 years. That solution still exists--to my knowledge--FOR MDM LOCKED BOARDS ONLY. It is of no use with iCloud-locked boards. It sounds like the critical piece missing from your scenario, is a DFU restore. The ROM chip you reference stores a copy of the serial/firmware that is written to it during a restore. It is not written-to, but only read, during update processes and/or internet recovery (which is not a proper DFU restore). So your experiment didn't...
    See more | Go to post

    Leave a comment:


  • Re: Unserialized M1 Pro

    The serial will certainly be written-to and stored-in a writable sector of CPU/memory on the chip. It's not at all unusual that Apple would have a way to provide blank/unserialized chips for their refurbishing facilities, who then write serials as the boards go out the door. But, this one--for whatever reason--was missed. I know the Apple stores used to serialize boards in-house, but unsure if that's still the case. If it is, then it's possible a board sent for an AASP repair wasn't serialized before being sent out the door. Who knows, but it's easily explainable....
    See more | Go to post

    Leave a comment:


  • Re: Unserialized M1 Pro



    Take 2 working M1/Pro/Max/M2 boards. Swap the CPUs. The serials will be swapped, after you restore them both. So yes, I think it's pretty definitive that the serials are within the CPUs--at least PRIMARY copy, which is the one you're worried about.

    That being said, I'm am POSITIVE that Apple has a way to write a serial a very quick and simple way, but they have access to tools/software that we do not. So, we are speaking of two different worlds here, keep in mind....
    See more | Go to post
    Last edited by ugamazing; 10-08-2023, 03:40 PM.

    Leave a comment:


  • Re: Unserialized M1 Pro

    Serial stored in CPU and is linked to WiFi chip, unsure how this even happens. You won't be programming a new serial (don't bother, unless you feel determined to figure out something that nobody else has been able to for years at this point), and if DFU doesn't do anything to resolve, you are out of luck unless you pay Apple to take care of it.
    See more | Go to post

    Leave a comment:


  • Re: Macbook M1 Unlocked!



    Serial isn't stored in the nands--at least not the primary/master copy. That is in the CPU. CPU is tied to WiFi card; storage not tied at all, no concerns about nands in any way for purposes of unlock conversation.

    If you have a holed-PCB M1/Pro/Max board with good/unlocked CPU and non-shorted WiFi card, you can transfer them to a locked (but otherwise working) board, and have an unlocked board with the serial of the original/holed board. It works fine. If you want to also transfer the data, just transfer all the nands as well--it...
    See more | Go to post
    Last edited by ugamazing; 09-15-2023, 06:57 AM.

    Leave a comment:


  • Re: M1 MacBook Air 820-02016 possible to swap ROMs to unlock a locked board?

    Nope. But, if you swap the M1 CPU and the WiFi card over to the locked board, yes, it will work. Be prepared for a brutal 4-6 hours of work though.
    See more | Go to post

    Leave a comment:


  • Re: Help with this FPC connector 820-01521-A

    Remove it with an IR preheater. Best way to pull things from these boards. The PCB is too good at sinking heat to use traditional "heat below board" to remove these connectors, and the inset pins make applying low-melt solder to the pins impossible. Preheater is 100% the way to go.
    See more | Go to post

    Leave a comment:


  • Re: Macbook M1 Unlocked!



    Depends on who is paying! ...
    See more | Go to post

    Leave a comment:


  • Re: Macbook M1 Unlocked!



    What specific way(s) do you intend to "read the M1 CPU"? And then what's your plan to read/modify the WiFi chip that is tied to the CPU/serial?...
    See more | Go to post

    Leave a comment:


  • Re: Macbook M1 Unlocked!

    M1 serial is in the CPU, 100%. You can move an unlocked M1 CPU+WiFi to a locked board and it will work, with unlocked serial in-tact. Being capable of doing that without damaging anything, however...

    But you aren't unlocking M1 boards, or changing serials, or anything like that. You can honestly just stop waiting for it.
    See more | Go to post

    Leave a comment:


  • Re: 820-02020-A missing pad on U5200

    It's not connected to anything ("NC"=not connected), no need to worry about it. Those come off a lot when replacing BGA chips.
    See more | Go to post

    Leave a comment:


  • Data Recovery Question PCIe Samsung Apple SSD

    Working on a data-recovery job on a 2017 Apple/Samsung PCIe blade SSD (from 2017 A1466). Cause of failure of the drive is a shorted controller (S4LN058A01-8030). I am now wondering what the best option to move forward with this one is, and had some questions to anyone who may know more about this:

    1. I have a TON of dead SSDs with the same controller IC (S4LN058A01-8030), but I do believe the firmware version is important. Is this correct?

    2. When removing the shorted/bad controller, I found the undercoat on the drive PCB was very, very thin and came off VERY EASILY,...
    See more | Go to post

  • Re: a1932 820-01521 - SSD issues

    CPU and T2 faults are much more common on this model than standalone SSD/nand faults. Still possible, but if the board boots fine and you can wipe the SSD and DFU-Restore fine, then odds are SSD/nands are actually OK.

    Issue more likely related to CPU/PCH. This assumes you've confirmed no damage to the board, and no prior repairs or liquid-exposure.
    See more | Go to post

    Leave a comment:


  • Re: MacBook Pro 16” 2019 Boots installs os Catalina but won't install Ventura or lowe

    When you keep saying the updates/installs (beyond Catalina) "fail", do they all fail the same way--i.e. hanging during final stages of install (black screen, Apple logo, progress bar, XX minutes remaining, etc)? What happens if you try to install Monterey/Ventura on a connected USB drive (after disabling T2 boot security settings on board via IR)?

    Do you see any indications of this board being a previously-refurbished (Apple or otherwise) board? Look for any markings or...
    See more | Go to post

    Leave a comment:


  • Re: MacBook Pro 16” 2019 Boots installs os Catalina but won't install Ventura or lowe

    This may be a RAM failure after all, as piernov alluded to, but could still be a CPU issue. I'd run memtest over and over (3-5x) to start with. If nothing pops up, this board would be a good reflow candidate. Reflow RAM first and test. If that doesn't resolve the issue, reflow the T2 and try again. If that doesn't work, I'd suspect CPU at that point. You can then try to reflow the CPU, but generally this will only help confirm the issue, not resolve it. If reflowing CPU changes the symptoms in...
    See more | Go to post
    Last edited by ugamazing; 06-07-2023, 09:22 AM.

    Leave a comment:


  • Re: can you help me with 820-01700-A missing 20v and 12v

    You should first confirm the SSDs are not shorted--a common issue with the 01700 and a very common cause of shorted ppbus_g3h.
    See more | Go to post

    Leave a comment:

No activity results to display
Show More
Working...
X