The guide has been updated.
You need to continue the process in terminal.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
followed the updated op and I still get the same message.
The guide has been updated.
You need to continue the process in terminal.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
This guide is for the select few that need to root their Samsung Galaxy S4 via Mac.
This guide only shows how to swap kernels in order for you to run motochopper then swap back to stock kernel.
Please keep in mind this is technical and involves using manual commands for heimdall in terminal.
If you have anything to add or have any questions, don't hesitate to ask.
I have tested this method using Heimdall on my Windows 7 machine.
I do not own a Mac to fully test this.
I am not an expert nor do I portray myself to be one.
I am not responsible to any problems from this method including bricking any devices, loss of data, or other issues that may arise with your device or computer. (Just to cover my behind.)
Things you need:
1. Heimdall
2. 423399 kernel boot.img (MD5: cd49d9c337d624abec5f6f1229e1abf6)
3. 562219 kernel boot.img (MD5: 3c776b87c2c1390787189e60d311c769)
4. Motochopper Root Exploit Tool
5. Drivers can be installed by installing Kies
First install Heimdall.
And make sure you have the drivers installed.
Make sure you have the 423399 kernel boot.img (MD5: cd49d9c337d624abec5f6f1229e1abf6) in an easy place to find and make sure you keep it seperate from the 562219 kernel boot.img (MD5: 3c776b87c2c1390787189e60d311c769).
If you have Kies installed, uninstall it.
Then open the heimdall-frontend application that was installed with heimdall.
Use the heimdall-frontend app to detect the device by going to Utilites > Detect.
Next open a terminal typeEnter your password.Code:sudo heimdall flash --BOOT
The prerelease kernel will be flashed and your device will reboot.
Go to Settings > More > About phone
and check to make sure your kernel version is 423399.
Then go into Settings > More > About phone > tap "Build number" about 7 times until it unlocks Developer options
Verify in Developer options setting on your device that you have "USB debugging" checked.
Verify in Developer options setting on your device that you have "Verify apps via USB" unchecked.
Verify in Security setting on your device that you have "Unknown sources" checked.
Verify in Security setting on your device that you have "Verify apps" unchecked.
Extract the motochopper.zip file.
Open terminal, navigate to the motochopper folder and typeThen typeCode:sudo chmod +x run.sh
Follow the on screen prompts.Code:sudo ./run.sh
After you are rooted, make sure you update the su binaries.
Otherwise you will lose root later on.
Next boot your phone into download mode in order to put the stock kernel back.
Open the heimdall-frontend application and detect your device once again. (Utilities > Detect)
Next open a terminal and typeCode:sudo heimdall flash --BOOT More > About phone and make sure the stock 562219 kernel is installed. Credits go to djrbliss, chainsdd, Samsung, creators of Heimdall, and if I missed anybody please let me know and I will add them to it. Thanks to [URL="http://xdaforums.com/member.php?u=3597789"]Doppletronica[/URL] for confirming the method. EDIT: If this thread now belongs somewhere else due to its nature, please move it mods. Also anybody is free to share this guide, just link them to this thread and please give credit where credit is due. Thanks.[/QUOTE] Let me know if you have any questions or concerns. Clubvegas999
I updated superuser from the play store but that was it. Is there something else I need to do to update the binaries?You have to update superuser and the su binaries before flashing the stock kernel back on.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
I updated superuser from the play store but that was it. Is there something else I need to do to update the binaries?
Okay, thank. Trying again now.Open the superuser app and it will prompt you to update the su binaries.
When it gives you a choice between doing it with twrp or the normal way, choose the normal way.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Tried it again. Updated it and opened the app and nothing happens. Is there another way to update the binaries?Open the superuser app and it will prompt you to update the su binaries.
When it gives you a choice between doing it with twrp or the normal way, choose the normal way.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
It is 1.0.1.8I've always had mine do it automatically.
I'm not sure about how to update manually.
What is the su version number?
It should be somewhere in the settings.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
That's really weird/frustrating. I tried using the links provided in the play store to manually do it but it just keeps giving me the same version.I have 1.23 there should be a way to update it manually from the app.
You may need to ask around or Google it.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Oh sweet! That did the trick! Thanks for that. I did end up trying a different superuser but not SuperSU . Thank you so much for helping me.You could try installing supersu and see if it will update from there.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
I got this same error. What I did was uninstall kies and then open the heimdall-frontend app that was installed with heimdall, and use it to detect the phone. (In Utilities->Detect) From there I could run the command line part successfully. Worked for me.
sudo heimdall flash --BOOT <full path to prerelease kernel>
sudo chmod +x run.sh
sudo ./run.sh
sudo heimdall flash --BOOT <full path to stock kernel>
I was wondering if someone can help me. I keep getting this error message:
Initialising connection...
Detecting device...
Claiming interface...
libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
patxp:desktop ArmandoOrona$
I uninstalled kies and android file transfer and restarted mac. Any help would be greatly appreciated.
So just to clarify, are you saying the whole process worked for you?
Whereas you successfully rooted your phone?
Sent from my Verizon Galaxy S4 using Tapatalk 2.