thread top ad

Collapse

Announcement

Collapse
No announcement yet.

820-00165 not booting fully, tried practically everything.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 820-00165 not booting fully, tried practically everything.

    I am getting the strangest issues lately..
    This MacBook Air 2017 is not booting; the loading bar takes a long time to fill up, and then it's stuck.
    In verbose mode, it stops and waits for the iGPU apparently: keeps repeating this line every 60seconds:

    busy timeout[0], (60s): 'IGPU'
    busy timeout[1], (60s): 'IGPU'
    etcetera..

    I have tried with everything disconnected but known-good IO board and LCD.
    Even tried only external screen.
    Tried booting up several different known good flash drives with different OS-es: all same thing.

    Tried cleaning ME region (with Medusa2)
    Tried using 3 different 00165 BIOS files found all over the web (with or without cleaning the ME-region after writing it to the board).

    Anyone have any ideas?

    *EDIT: by the way, this board is absolutely clean.

  • #2
    Probably bad CPU would not be surprised at all

    Comment


    • #3
      Could be CPU issue.
      Try to boot Linux, or Windows; let see if anything change.

      Comment


      • #4
        Got a Ubuntu boot disk: boots up fine, everything works

        Comment


        • #5
          Install Intel graphics now and see if still good.
          It may used generic one.

          Comment


          • #6
            ok, so that would basicaly tell me if the intel gpu is defective right?
            what else could it be at this point..? I mean, i dont have a lot of time to start fiddling with ubuntu-drivers and such, and basically this is boiling down to either a bad cpu or integrated gpu right?

            Comment


            • #7
              RAM, or CPU issue...

              Comment


              • #8
                Just to let you know, i installed the intel graphics drivers for ubuntu, and everything works properly. so i am now assuming its a RAM issue? Weird that it works perfectly on Ubuntu..

                Comment


                • #9
                  BIOS files you've tried, 2017 year?
                  One should be already posted on the forum...

                  Comment


                  • #10
                    My Google Fu is not good enough to find it on here so far, lots of dumps, but none clearly stated for 2017.
                    I can try getting a dump from a fixed 2017 MacBook Air from the queue, flash it on this one and clean ME?

                    Comment


                    • #11
                      Yes, try that.
                      In fact, you can try the dump as is; just to see any difference about graphics.
                      And finally clean ME...

                      Comment


                      • #12
                        yeah figured as much..
                        i just did: flashed it on there without cleaning ME: no change in symptoms
                        Cleaned ME afterwards: Same difference..

                        Comment


                        • #13
                          I don't know how Linux manages the graphics.
                          Can you try Windows and run some graphics stress, after driver installed?

                          Comment


                          • #14
                            I might not have time for this.. but what would that eventually tell me? I mean, if it's about to be the iGPU (CPU) than i'm calling it quits

                            Comment


                            • #15
                              Only to confirm the issue...

                              Comment

                              thread bottom ad

                              Collapse
                              Working...
                              X