Jump to content
Andy Vandijck

ReadSMC for EFI, a tool to enter read SMC keys from EFI shell on real Macs

63 posts in this topic

Recommended Posts

Try reinstalling yosemite or el Capitan and if you're lucky perhaps the correct SMC will be re-flashed.

Either that, or try running the smc update package from inside OSX, not using rEFIt.

Share this post


Link to post
Share on other sites
Advertisement

Try reinstalling yosemite or el Capitan and if you're lucky perhaps the correct SMC will be re-flashed.

Either that, or try running the smc update package from inside OSX, not using rEFIt.

 

Ok, which package should i use? I have macbook pro late 2011 (8,1) running mavericks 10.9.5 os x (i'm worried now to use the wrong one ..)

 

If i reinstall should i install it by  the apple store or by bootable usb? 

Share this post


Link to post
Share on other sites

Try it anyway and see what happens. You do understand that there is a possibility that what you did cannot be undone, right?

 

Even if i flash wih refit with the right firmware it will not work?

Share this post


Link to post
Share on other sites

It would but I am not certain you can actually flash anything from the mode you are booted in. It's basically the only thing that might be able to help you but I don't know for sure whether you'll be able to flash it.

Share this post


Link to post
Share on other sites

You sure it's late 2011 and not early 2011? (both are 8,1)

 

In that case you should try this one http://support.apple.com/kb/DL1474

 

About the reinstall... don't think it matters. Whatever is easier.

 

So i installed it and it didn't do anything .. 

 

There a 3 files .pk (macbookprosmcupdate.pkg, mbp15.pkg, mbp17.pkg) i used the 1st one but fans still running high speed

 

I have SMC: 1.62f7 for 8.1 late 2011 model

Share this post


Link to post
Share on other sites

Did it install succesfully?

Try rebooting and see whether there's any change.

 

So basically the root of the problem is you force-flashed the early 2011 SMC instead of late 2011... try flashing the correct one (1.68f98 (SMC 1.5)) from rEFIt and see what happens.

Try without doing the reset first, though, as resetting the SMC in this state will most likely make the machine power off.

Share this post


Link to post
Share on other sites

In that case try resetting the SMC, and pray for the macbook to not turn off when you do that. If it turns off, you're {censored}ed. The only way to fix it is by finding a way to manually reprogram the chip or replacing that chip altogether.

Share this post


Link to post
Share on other sites

Ok,

 

Didn't worked, the comp doesnt start, it attempt to start, but the reboot and start with fan at full speed

 

960615FullSizeRender1.jpg


and with -norestart command if simply doesnt want to start ... 

Share this post


Link to post
Share on other sites

It obviously doesn't work because for some reason it is not flashing succesfully.


Try Smcflasher.efi -force -update instead of -force -LoadApp

Share this post


Link to post
Share on other sites

in the same folder as the update?


ok i updated by the appstore to el capitan but it does nothing, even if i try to reinstall the smc (with the update, not refit) it doesnt work.

 

What about the smcflasher above?

Share this post


Link to post
Share on other sites

The problem is most likely you need to find a way to patch SmcFlasher to ignore the hardware verification routine... However, I do not know how to do that.

So, most likely you just killed your mac.

Share this post


Link to post
Share on other sites

The problem is most likely you need to find a way to patch SmcFlasher to ignore the hardware verification routine... However, I do not know how to do that.

So, most likely you just killed your mac.

 

How its possible that i cant RE-flash the smc with a newer firmware?

 

i have 2 possibilities maybe?

- Change de chip

- Manually fix the smc with a buspirate  ( http://ho.ax/posts/2012/06/unbricking-a-macbook/ )

 

In both case i never did that, and i'm kind of geek not really a programmer or something ;) 

Share this post


Link to post
Share on other sites

Changing the chip is much harder and would require you to buy the chip and hope it's properly programmed. The buspirate might work but I have no idea how to do it either. It's also possible to patch smcflasher but once again i don't know how. Some guys did it for a macpro but their walkthrough isn't really usable because their version of smcflasher was very very different.

Share this post


Link to post
Share on other sites

Yeah, that's exactly the page I had found. However, I was comparing the binary they used (the original) and the one included in the MBP updates and they're completely different. So... I cannot really recommend you use it because I'm not sure it can handle your SMC. On the other hand... if you want to try it, it's probably the only alternative you've got left. (i.e. flashing your smc with that version of smcflasher)

Share this post


Link to post
Share on other sites

Hey Lord Kamina,

 

I managed to fix the smc issue. I had the mbp 2010 smc installed on my late 2011 as mentioned above.

 

to fix it i took the smcflasher.efi from the mbp2010 bundle and the mbp13smc15.smc from the right bundle (bundle of the late 2011) and simply force the flash with -reset 1 then force - LoadApp - norestart.

 

And it worked, i booted with the right firmware (1.68f98) with low fans and no more kernel_task.

 

I also removed the battery (only with magsafe now), genius bar told me that i might be the problem sometimes ..

 

Hope you can fix yours with this method :)

Share this post


Link to post
Share on other sites

Hey Lord Kamina,

 

I managed to fix the smc issue. I had the mbp 2010 smc installed on my late 2011 as mentioned above.

 

to fix it i took the smcflasher.efi from the mbp2010 bundle and the mbp13smc15.smc from the right bundle (bundle of the late 2011) and simply force the flash with -reset 1 then force - LoadApp - norestart.

 

And it worked, i booted with the right firmware (1.68f98) with low fans and no more kernel_task.

 

I also removed the battery (only with magsafe now), genius bar told me that i might be the problem sometimes ..

 

Hope you can fix yours with this method :)

 

 

Thank you for posting the fix. Have you seen any other issues since flashing the correct firmware?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By DarkHarthur
      DH67CL
      R7 250
      2 discos duros
      En el 1: Windows 10 y una partición de datos
      En el 2: High Sierra y una particion de datos
       
      Hola, mi problema es el siguiente Clover ya no me muestra EFI Windows; Tenia todo funcionando bien con High Sierra 10.13.6, quise actualizar a Mojave y como tuve muchos problemas decidí volver a High Sierra con el disco duro USB en el que había hecho una copia con Carbon Copy;
      La situacion es algo así, en la carpeta EFI si dejo la carpeta Microsoft, al encender la PC entra directo a Windows, si elimino la carpeta Microsoft si entra con Clover pero no aparece la entrada EFI Windows, ya active legacy en Clover Configurator pero solo me aparecen otras entradas de Windows pero no EFI, todo esto desde el disco duro supuestamente restaurado a como lo tenia antes.
      Si entro con el disco duro USB que tiene la copia que había hecho, me aparecen todas las opciones.
      Si conecto un pendrive tampoco me aparece la opción EFI Windows. 
      Probablemente paso después de desconectar el disco duro de Windows, pero recuerdo que me seguía apareciendo EFI Windows después de haberlo desconectado. Saludos
    • By EWaffle
      Hey guys, I have a ridiculously convoluted issue. Take a seat.
       
      I am trying to use Logic Pro X on a 2012 Mac Mini I have, but I currently have Snow Leopard OS X 10.6.8, and will need to update to Sierra 10.12. However, I realize I need to update to a newer OS such as El Capitan in order to be able to update to Sierra. Except I cannot sign into the App Store. I am greeted with an error message along the lines of "this computer or device cannot be verified." So I did some digging and it seems to be because my Ethernet port and Wifi don't work. I use a USB Wifi adapter to get around this but now it seems like I finally have to fix it for good so I can get into the App Store to get these updates I need.
       
      In System Preferences > Network, I do not see Ethernet or Wifi listed. Only my USB Wifi Adapter and Firewire. In System Profiler > Hardware > Ethernet Cards, it says, "This computer does not appear to have any PCI Ethernet cards installed."
       
      I'm pulling my hair out over here to get Logic Pro X on this computer, that's all that I really want, and that's all I want this computer to do. If you can help, God bless your soul.
    • By ITzTravelInTime
      Hi guys, this thread is to show you a new and open source app, created by me, that I called TINU:
       
      The name means: TINU Is Not #####, the U refers to a popular software that is used to create Mac OS hackintosh installers (that for good reasons is banned on this forum), but the aim of the name is to explain that this app is a totally different thing from that software and works in a totally different way.
       
      This app basically is a graphical interface for the createinstallmedia executable that is inside the Mac OS installer apps, it is capable to create a Mac OS installer on a drive completely vanilla like what you do using the command line method, and also this method is recommended by apple itself. In addition to this, this app provvides also to you some customization features and a better management of the hall macOS isntall media creation process
       
      Allows you to create easily a macOS install media without messing around with command line stuff and without using disk utility, all you need to do is use the app and then install clover on the usb drive once TINU has finished or leave it as is you want to use it on a Mac.
       
      Features:
        - Simple to use UI that allows you to easily start the macOS install media creation process
        - It can work with every Mac OS installer app that has the createinstallmedia executable inside of it's resources folder (including also beta and newly released installers)
        - You can use any drive or partition you want that can be erased and is at least 7 GB of size
        - Works on Mac OS recovery, so you can create a macOS install media from a bootable macOS installer or from the macOs recovery, and you can use TINU to install macOS too.
        - All vanilla, the macOS install medias created with this tool are 100% vanilla, just like you created them using the command line "createinstallmedia" method in the terminal, with also some extra optiona features
        - Open source, you will know what this program does on your computer and also you can create your own version by downloading and playing with the source code
        - Does not requires to do anything of special first, just open the program
        - No need to go in disk utility first, TINU can format your drive for you
        - Uses recent and more modern APIs and SDKs and Swift 3 language
        - Transparent graphics style available (use alt + s on the keyboard or View->Use transparent style)
        - Works using the latest versions of macOS and will also support newer Mac installers out of the box without needing for an update
        - Advanced section, to customize your macOS install media
        - Installer customization: Kernelcache/prelinkedknerel and boot files replacement (a feature that can be handy while dealing with old Macs or with beta installers when you need to mod or change the boot files some times)
        - Clover EFI folder installer
       
        Features that are planned for some future versions:
        - Integrated EFI partition mounter tool (TINU can already mount EFI partitions from version 2.0, but a dedicated section which allows to mount every EFI partition in the system will be added)
        - Install clover and configure clover
        - Install kexts inside the kexts folder of clover
        - Clover drivers customization
        - Use custom dsdt in clover
        - integrated pre-made clover config templates database from a remote and open repository
        - Support for other languages, at least Italian   Rquirements:  - A computer that runs Mac OS X Yosemite or a more recent version (Mac OS X El Capitan is required to use TINU in a macOS recovery or installer)  - A drive or a free partition of at least 7 GB that you want to turn into a macOS/Mac OS X installer  - A copy of a macOS/Mac OS X installer app (Maveriks or newer versions are supported) in the /Applications folder or in the root of any storage device in your machine (excepted the drive or volume you want to turn into your macOS install media)   Note that this app is under the GNU GPL v3 license so any reuse of the source code must follow the license's terms   Latest stable TINU release:   Download the app:                                https://github.com/ITzTravelInTime/TINU/releases   View the source code:                            https://github.com/ITzTravelInTime/TINU/       Frequently asked questions about TINU:  https://github.com/ITzTravelInTime/TINU/wiki/FAQs     NOTE: if you have problems with your USB installer of 10.13.4 or newer version not being detected by clover you have to use the latest clover and if it still does not detectets your usb installer you have to remove the invivible file called .IAPhysicalMedia located into the root of the usb installer. This issue is caused by a changement in the apple's createinstallmedia, don't blame TINU for that, TINU does only uses the installer creation method from apple, which has been changed by appleitself, causing this problem for hackintosh users some times, this issue should be resolved in the latest versions of clover which will no longer require that you do changements to let your usb dive to be detected, a setting to do this fix automatically in tinu is also present TINU in the adavnced settings, starting from the version 2.0 of the app. I leave also some screenshots as well
       
       
       
       
       
       
       
       

×