I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
vafangool said:
I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
Click to expand...
Click to collapse
I didn't think the me7 exploit was supposed to ran with terminal emulator. Have you tried safe root another windows tool?
Nvidia Shield Root and More Doing a little bit of reading goes a long way.
hexitnow said:
I didn't think the me7 exploit was supposed to ran with terminal emulator. Have you tried safe root another windows tool?
Nvidia Shield Root and More Doing a little bit of reading goes a long way.
Click to expand...
Click to collapse
I havent tried anything else....according to the thread it was supposed to be for the me7 build...I am kind of new to all this..
vafangool said:
I havent tried anything else....according to the thread it was supposed to be for the me7 build...I am kind of new to all this..
Click to expand...
Click to collapse
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
vafangool said:
I have a galaxy s4 running android 4.2.2 , its model # sch i545 and its build vruame7 .http://forum.xda-developers.com/showthread.php?t=2380325 I am following the directions here word by word ,,,, Devoloper options is enabled, card formatted to exfat and in the terminal emulater when I change directories and try to run the 2nd command I am getting this error
Try to find address in memory....
Attempt fb_mem exploit...
Failed to open /dev/graphics/fb0 due to permission denied
You need to manage to get remap_pfn_range addresses
failed to get prepare_kernel_cred addresses
failed to get commit_creds addresses
failed to get ptmx_fops addresses
() device is not supported
failed to setup variables
and I dont know why its where it says device detected () shouldnt it say the device?
I searched the forums and saw someone having problems with it on an AT$T phone.....THanks in advance guys
Click to expand...
Click to collapse
Further info on what @Surge1223 said:
Go to this thread and follow the directions in the first post.
Surge1223 said:
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok..I will try that one...I also have a note 2, but the software is 4.3 .. I know the bootloader is locked on this one. But if I can use saferoot to root it and than load safestrap to load custom roms on it? From what I read you cant put safestrap on the note 2 with 4.3 but i read somewhere that you can put safestrap on here since I still have the 4.2.2 ....Thank you for the help so far..
vafangool said:
Ok..I will try that one...I also have a note 2, but the software is 4.3 .. I know the bootloader is locked on this one. But if I can use saferoot to root it and than load safestrap to load custom roms on it? From what I read you cant put safestrap on the note 2 with 4.3 but i read somewhere that you can put safestrap on here since I still have the 4.2.2 ....Thank you for the help so far..
Click to expand...
Click to collapse
You have got to be pretty careful, since there's lots of variants of these models. For example, there's at least 6 incompatible models of the Samsung Galaxy S4 (AT&T, Sprint, T-Mobile, Verizon, International (a couple of models as far as I can tell) the "L" variant, etc.
Following directions for a "Galaxy S4" without knowing if it's the same variant as yours can lead to bricks.
People have successfully used Saferoot to root Note 2 with the MK7 build. Then you'll have to research if Safestrap works - it's likely if you're running 4.3, but I have no idea. Do the research before you flash.
Surge1223 said:
Use saferoot. It will root all versions of the sch-1545 (Verizon Galaxy S4).
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used saferoot but I am not sure if it worked all the way..towards the end my phone didnt reboot when it said it would..I dont know if that busybox was installed I dont see it but I have superuser installed.. I also dont have that padlock unlock when I restart the phone....
vafangool said:
I used saferoot but I am not sure if it worked all the way..towards the end my phone didnt reboot when it said it would..I dont know if that busybox was installed I dont see it but I have superuser installed, My device status says official...is that where its suppsed to say custom?
Click to expand...
Click to collapse
What kind of phone do you have? I assume an i545 given that this is the Verizon GS4 forum, but it's worth asking.
If the phone did not reboot, then it's probably rooted but no busybox installed, but that's OK. Just install it from the play store.
Or, you can just re-root, and provide a bit more detail on what happened.
Yeah like @k1mu just said post more info, specifically what the output of the adb script says. Also if you dont get a SuperSu prompt after the script finishes. Then try typing su into terminal or adb shell and tell us what it says
Sent from my SCH-I545 using XDA Premium 4 mobile app
k1mu said:
What kind of phone do you have? I assume an i545 given that this is the Verizon GS4 forum, but it's worth asking.
If the phone did not reboot, then it's probably rooted but no busybox installed, but that's OK. Just install it from the play store.
Or, you can just re-root, and provide a bit more detail on what happened.
Click to expand...
Click to collapse
I may try and reroot it and see what happens...its hard to explain but it was at the part where it was telling me my phone was going to reboot and to unlock it and press any key when it does..I waited and the phone didnt reboot
... I just did it again and it looked like it worked...I kept seeing the popup that ADB shell has been granted superuser permissions....it said all done and the command prompt closed..
Surge1223 said:
Yeah like @k1mu just said post more info, specifically what the output of the adb script says. Also if you dont get a SuperSu prompt after the script finishes. Then try typing su into terminal or adb shell and tell us what it says
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I typed SU into terminal emulater and a window popped up asking for super user permissions and I granted them and Im at the [email protected] with a # sign...so Im assuming the # sign at the prompt also means that I gained root...
I did make sure I was using the right software..I was aware of the build # and I made sure I was trying the right stuff..From what I read safestrap should work using the 4.2.2 android version..with the ME7 build that I have...
I have been all over this site the last 3 days since I got into this when I should be studying for my networking certifications...lol...Thanks for all the help so far..I really appreciate it guys..
vafangool said:
I typed SU into terminal emulater and a window popped up asking for super user permissions and I granted them and Im at the [email protected] with a # sign...so Im assuming the # sign at the prompt also means that I gained root...
I did make sure I was using the right software..I was aware of the build # and I made sure I was trying the right stuff..From what I read safestrap should work using the 4.2.2 android version..with the ME7 build that I have...
I have been all over this site the last 3 days since I got into this when I should be studying for my networking certifications...lol...Thanks for all the help so far..I really appreciate it guys..
Click to expand...
Click to collapse
Congratulations, you have root.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Congratulations, you have root.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome..Thanks alot for all the help...
Related
I got the phone offa craigslist.
how can I tell if the phone is already rooted?
Menu > settings > about phone > software > build number if out says release keys at the end it's one of the leaks, if it says test keys you have root. Hope that helps
Sent from my Eris using the XDA mobile application powered by Tapatalk
it says release-keys, but build number 1.17.605.1
the reason I asked is because I am having problems rooting it per the instructions on this website.
this phone recently got sent back to htc for service, and they flashed it to the "latest" rom they said. dunno what that means.
What exactly are you having problems with while rooting?
it says release-keys, but build number 1.17.605.1
the reason I asked is because I am having problems rooting it per the instructions on this website.
this phone recently got sent back to htc for service, and they flashed it to the "latest" rom they said. dunno what that means.
Click to expand...
Click to collapse
Im not sure htc services phones do they?
Sent from my Eris using the XDA mobile application powered by Tapatalk
korben dallas said:
Im not sure htc services phones do they?
Sent from my Eris using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
yes they do ,if u call and have issues with ur phone , they do offer to fix ur phone but not sure for any cost tho , hope this helps
I had audible crackling, and they fixed the speaker, but also reflashed the phone to 1.5, unrooted.
tazzpatriot said:
yes they do ,if u call and have issues with ur phone , they do offer to fix ur phone but not sure for any cost tho , hope this helps
Click to expand...
Click to collapse
shagpal said:
I had audible crackling, and they fixed the speaker, but also reflashed the phone to 1.5, unrooted.
Click to expand...
Click to collapse
view my thread to help you root your phone. the link is the first one in my signature. read threw the thread and make sure you download the full version and the update.
Good to know! Thanks!
ECLIPS3 said:
view my thread to help you root your phone. the link is the first one in my signature. read threw the thread and make sure you download the full version and the update.
Click to expand...
Click to collapse
noob question........my phone says firmware 1.5 build number 1.17.605.1 cl104882 release-key and its flashed to metropcs......if i root my phone and change to 2.1 will i have to reflash to metro........thanks
kingkat186 said:
noob question........my phone says firmware 1.5 build number 1.17.605.1 cl104882 release-key and its flashed to metropcs......if i root my phone and change to 2.1 will i have to reflash to metro........thanks
Click to expand...
Click to collapse
good news is, that you are stock, so you can root your phone.
and yes, chances are you will then have to reflash it to metropcs. but since you already did that once, the next time will be easier. if you do run into trouble, then just ask us in the IRC channel at irc.wastate.net #droideris or #erisroothelp
thanks for your help
jearl75 said:
Menu > settings > about phone > software > build number if out says release keys at the end it's one of the leaks, if it says test keys you have root. Hope that helps.
Click to expand...
Click to collapse
I think I have rooted my phone, but what is "leaks" also my phone has "realease" keys at he end of the build. Superuser app is on my phone and Titanium Backup seems to be working. Just entered, "su" into Terminal and got permission denied. I'm lost.
Additional details:
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
MobileWon said:
I think I have rooted my phone, but what is "leaks" also my phone has "realease" keys at he end of the build. Superuser app is on my phone and Titanium Backup seems to be working. Just entered, "su" into Terminal and got permission denied. I'm lost.
Click to expand...
Click to collapse
Check out this link. I think it might help answer your questions.
Also google theunlockr.com
Bayhill Jacket said:
Check out this link. I think it might help answer your questions.
Also google theunlockr.com
Click to expand...
Click to collapse
The link is not working.
Edit:Nevermind, I managed to find the information on Android Central. So, I'm rooted, but whenever I would do the g free verify I would get an error. Thanks given.
MobileWon said:
The link is not working.
Click to expand...
Click to collapse
I think that he meant this one. Basically, install a terminal app , if one is not already installed, and open it. If you see a "#" prompt, you are rooted. If you see a "$" prompt and then enter the command "su" (and grant permission to the terminal app if you get prompted to by the SuperUser app), if it changes to a "#" you are rooted.
doogald said:
I think that he meant this one. Basically, install a terminal app , if one is not already installed, and open it. If you see a "#" prompt, you are rooted. If you see a "$" prompt and then enter the command "su" (and grant permission to the terminal app if you get prompted to by the SuperUser app), if it changes to a "#" you are rooted.
Click to expand...
Click to collapse
That's the link, thanks doogald. Sorry for the broken one
Thanks guys thats the exact one I used. Maybe I'm doing something wrong when I do the g free verify, but I also wanted to see if I had the cid and sim unlocked.
MobileWon said:
I think I have rooted my phone, but what is "leaks" also my phone has "realease" keys at he end of the build. Superuser app is on my phone and Titanium Backup seems to be working. Just entered, "su" into Terminal and got permission denied. I'm lost.
Click to expand...
Click to collapse
For the Eris, there are at least 5 different ways to "root" your phone, and the most recent & easiest methods (One Click or Dummies) don't even touch the primary OS - they just install a custom recovery boot which allow you to replace the entire OS by flashing a "rooted" OS into place (or, add a root toolkit to the existing "stock" ROM). So, running "su" may not tell you much.
For most rooted ROMs, the "su" terminal/shell program and the Superuser app act as a pair - when any other app requests superuser privileges the first time, the Superuser app will pop up on the screen and ask you whether you want to allow or deny the app requesting root privileges. There will be a check-box on that screen that will allow the Superuser app to remember your choice. If you have ever seen this pop-up, then I suppose you have a rootkit installed correctly.
Note that if you look away from your phone for too long while that pop-up is on screen, the Superuser app will time out - and decide that the requesting app should always be denied.
The Superuser app keeps a list of apps that have previously requested root - start the Superuser app directly from the launcher, and you will see the list. If there is one in there that is erroneously marked as "deny", tap on that entry and select "forget". Then, the next time you start the app in question, keep a lookout for that Superuser app pop-up.
The fact that you get a "permission denied" message when trying "su" from a terminal session means one of two things, either:
- you previously denied access to "su" (or looked away from the screen, and missed the pop-up), or
- your ROM is not correctly rooted.
HTH
PS note that this thread is extremely old - it references methods and techniques which will still work, but are quite a bit more tedious than newer methods. Also, it helps people responding to your inquiry if you mention a few tidbits about your phone : what you have done to the phone,the bootloader version, the (full) kernel version, the "Software #", etc.
MobileWon said:
Thanks guys thats the exact one I used. Maybe I'm doing something wrong when I do the g free verify, but I also wanted to see if I had the cid and sim unlocked.
Click to expand...
Click to collapse
Doesn't SIM Lock only apply to GSM phones?
I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
killdawabbit said:
I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
Click to expand...
Click to collapse
Looks like you are in store for a full system restore to the original stock image. You can try the recovery image from my signature to get rid of the TWRP recovery if you want. Just place the recovery file in the PDA box and start.
So, is that why I am getting that message when I am trying to root my phone again?
killdawabbit said:
So, is that why I am getting that message when I am trying to root my phone again?
Click to expand...
Click to collapse
It could be but not 100% sure. Each user is different. I would start there though and see if it works.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
killdawabbit said:
I have a Verizon S4 I had it rooted and working fine with TWRP recovery installed but, my Google play store stopped working is why I am in this situation now. I did the No Wipe Factory Image posted in the Verizon S4 forum and once that was done I still saw the TWRP recovery still popping up and installed. So I proceed to try and restore the root access and now I keep running into this running mottochop...
Device found...
Pushing exploit...
cannot stat 'pwn' : No such file or directory
Unable to chmod /data/local/twp/pwn No such file or directory...
Pushing Root tools...
*leaving out this part because I don't want to type it*
Rooting phone...
/system/bin/sh: /data/local/twp/pwn: not found
Cleaning up...
rm failed for /data/local/twp/pwn, No such file or directory...
Exploit complete. Press enter to reboot and exit
Help!!!
Click to expand...
Click to collapse
While I don't know the specifics of the exploit, it sounds like it was unable to push files to the device. Is your USB Debugging enabled prior to running the exploit?
Cilraaz said:
While I don't know the specifics of the exploit, it sounds like it was unable to push files to the device. Is your USB Debugging enabled prior to running the exploit?
Click to expand...
Click to collapse
Yes
killdawabbit said:
Yes
Click to expand...
Click to collapse
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
DarkMenace said:
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
I am back to stock rom without TWRP. Thanks to the Dark Menace. Appreciate your help and I will not screw with my Google Play Store anymore after I root this time!
DarkMenace said:
PM sent
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Why would you PM the solution? Perhaps other people might have this same issue and need the solution as well.
killdawabbit said:
I am back to stock rom without TWRP. Thanks to the Dark Menace. Appreciate your help and I will not screw with my Google Play Store anymore after I root this time!
Click to expand...
Click to collapse
crikfromcincy said:
Why would you PM the solution? Perhaps other people might have this same issue and need the solution as well.
Click to expand...
Click to collapse
Sent
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. prerelease kernel boot.img (MD5: cd49d9c337d624abec5f6f1229e1abf6)
3. stock 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 prerelease kernel boot.img (MD5: cd49d9c337d624abec5f6f1229e1abf6) in an easy place to find and make sure you keep it seperate from the stock 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 type
Code:
sudo heimdall flash --BOOT <full path to prerelease kernel>
Enter your password.
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 type
Code:
sudo chmod +x run.sh
Then type
Code:
sudo ./run.sh
Follow the on screen prompts.
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 type
Code:
sudo heimdall flash --BOOT <full path to stock kernel>
Then go to Settings > 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 Doppletronica for confirming the method.
If you found this guide helpful please hit the thanks button
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.
klabit87 said:
Is there anybody willing to test a root method running a Mac?
I may have found a way but I don't have any way to test it myself otherwise I would.
If interested please pm me.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
does it have an unroot? i'd be willing to try it out. if so
theidoctor said:
does it have an unroot? i'd be willing to try it out. if so
Click to expand...
Click to collapse
I'm not too sure about an unroot method.
I'm sure if I looked at it hard enough I could come up with something.
Are you looking for an unroot method via Mac?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
klabit87 said:
I'm not too sure about an unroot method.
I'm sure if I looked at it hard enough I could come up with something.
Are you looking for an unroot method via Mac?
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
yea. i mean, just for testings sake. i dont want to have to go through the whole unroot just to test a root method drama.
i could unroot on my VM and try your root, but what are the possible effects to it going down? does it work with you?
theidoctor said:
yea. i mean, just for testings sake. i dont want to have to go through the whole unroot just to test a root method drama.
i could unroot on my VM and try your root, but what are the possible effects to it going down? does it work with you?
Click to expand...
Click to collapse
Pm sent.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Update:
I tried making an unroot method.
That completely failed.
So I had to use Odin to get running again.
I did however get a chance to test the root method for Mac users.
It worked with no problems for me.
I may continue working on the unroot method but that depends on my own free time.
If anyone is interested in assisting with it that would be great.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
klabit87 said:
Update:
I tried making an unroot method.
That completely failed.
So I had to use Odin to get running again.
I did however get a chance to test the root method for Mac users.
It worked with no problems for me.
I may continue working on the unroot method but that depends on my own free time.
If anyone is interested in assisting with it that would be great.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Click to expand...
Click to collapse
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
theidoctor said:
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
Click to expand...
Click to collapse
I will finish my write-up and get it to you as soon as I can.
I'm not around a computer at work so it may be later this evening possibly.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
theidoctor said:
pm me instructions and i will try it out tonight. i dont mind being a flashaholic tonight
Click to expand...
Click to collapse
Pm has been sent. Let me know if you have any questions or concerns.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
You can unroot it the same way you root. Use Heimdall.
DarkMenace said:
You can unroot it the same way you root. Use Heimdall.
Click to expand...
Click to collapse
Thanks. I knew I was making it harder than it was supposed to be.
I was really only interested in the root guide since a good few people were asking about it.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
I was wondering if someone can help me. I keep getting this error message:
patxp:desktop ArmandoOrona$ sudo heimdall detect
Password:
Device detected
patxp:desktop ArmandoOrona$ sudo heimdall flash --BOOT boot.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
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.
Has anyone else tested this? Just curious.
anothamexican said:
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.
Click to expand...
Click to collapse
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.
Doppletronica said:
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.
Click to expand...
Click to collapse
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.
klabit87 said:
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.
Click to expand...
Click to collapse
Yep. Once I got the kernel to flash okay, The rooting process worked flawlessly.
Doppletronica said:
Yep. Once I got the kernel to flash okay, The rooting process worked flawlessly.
Click to expand...
Click to collapse
Great! Thanks for your confirmation.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Man.....I wish I saw this yesterday. I spent 2 hours getting my old imac up and running with bootcamp to install windows.....another hour looking for my old XP disc to actually install it on the iMac, another half hour to install XP, then a good 45 minutes or so trying and failing to gett all the samsung drivers to wok (too several installs and unistalls til it finally worked). After all that, I downloaded the all in one root kit and install recovery as well.
Doppletronica said:
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.
Click to expand...
Click to collapse
I got heimdall frontend to detect the device, where do I type in the commands? Under which tab?
anothamexican said:
I got heimdall frontend to detect the device, where do I type in the commands? Under which tab?
Click to expand...
Click to collapse
The guide has been updated.
You need to continue the process in terminal.
Sent from my Verizon Galaxy S4 using Tapatalk 2.
Warning: Total Noob here.
Just rooted my VZW S4 following the instructions for the ME7 build on the forums here with no problems. Installed "ROM Manager" via Play store and went thru the steps of flashing CWM. The app reports, under "Recovery Setup" that my current recovery is ClockworkMod 6.0.3.2.
BUT, when I "Reboot into Recovery" ... it always go to the default "Android System Recovery <3e>"
How can I get CWM running instead?
Thanks
You can't install a custom recovery on ME7 yet. It's been well covered here on XDA.
Sent from my SCH-I545 using xda app-developers app
AliceBToklas said:
You can't install a custom recovery on ME7 yet. It's been well covered here on XDA.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks. As someone new to Android and the rooting community, is there an explanation on the whys and hows of CWM (e.g. what is required for it to work, why it requires more than rooted phone, how it should best be used, etc...)?
Just trying to figure out how everything plays together and what I should and shouldn't do.
-wg
wgpubs said:
Thanks. As someone new to Android and the rooting community, is there an explanation on the whys and hows of CWM (e.g. what is required for it to work, why it requires more than rooted phone, how it should best be used, etc...)?
Just trying to figure out how everything plays together and what I should and shouldn't do.
-wg
Click to expand...
Click to collapse
The bootloader on this phone is locked, meaning you will need an exploit to bypass it in order to install a custom recovery. The loki method that was previously working has been patched by the most recent update, eliminating the only publicly known hole to install custom recovery. Without an exploit to bypass or an unlocking method we have no way to install a custom recovery like CWM or TWRP, without these it makes it nigh on impossible to install a custom ROM.
Anyone else please correct me if I am wrong but this was my understanding of the current state of things.
Your 100% correct sir...
Sent from my SCH-I545 using xda premium
I tried to run the root but when putting the commands in the emulator I get file not found. SD card is exfat
Hope someone makes a bootstrap like we had for the old droids.
goherd said:
I tried to run the root but when putting the commands in the emulator I get file not found. SD card is exfat
Click to expand...
Click to collapse
Make sure you are very specific on letters that need to be caps.
For example; when you type cd /mnt/extSdCard......make sure the S and C are caps or it will not work.
First time I did it I put in extSdcard and not extSdCard and I got the file not found error.
That should do the trick.
MikeyFid said:
Make sure you are very specific on letters that need to be caps.
For example; when you type cd /mnt/extSdCard......make sure the S and C are caps or it will not work.
First time I did it I put in extSdcard and not extSdCard and I got the file not found error.
That should do the trick.
Click to expand...
Click to collapse
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
ballsagna said:
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
Click to expand...
Click to collapse
Um, Linux command line is often case sensitive. The question above wasn't about custom recoveries, it was simply referring to rooting ME7 which has long been possible.
Sent from my SCH-I545 using Tapatalk 2
ballsagna said:
Im sorry your answer was wrong.
To OP... Custom recovery has not been working on ME7. No exploit has even been found to get a custom bootloader on them. Research can teach a lot if found.
Click to expand...
Click to collapse
That command line is in fact case sensitive. So you're wrong. The previous post was about using the root exploit method which has been done already, not unlocking the bootloader.
This will void your warranty, like all root exploits. Use this at your own risk. Do not take OTAs on rooted devices unless you know what you are doing, as it may cause a bootloop or a soft brick.
RockMyMoto is designed for MotoXs that have recieved the Camera update, patching PwnMyMoto. If you are unsure of your firmware, try PwnMyMoto first.
First step is to install Cydia Impactor, by Saurik. http://www.cydiaimpactor.com/ This is required. You will also need adb installed and working, and be comfortable with the command line. Your phone must be on the same network as your PC.
Figure out the ip address of your phone:
adb shell getprop dhcp.wlan0.ipaddress
Click to expand...
Click to collapse
unzip RockMyMoto-{version}.zip and push the exploit and su to /sdcard/:
adb push su /sdcard/
adb push RockMyMoto.jar /sdcard/
Click to expand...
Click to collapse
Run Impactor and select "# start telnetd as system on port 2222", then hit start.
Once the process is complete, run telnet:
telnet {your phone's ipaddress} 2222
Click to expand...
Click to collapse
Run the exploit through telnet
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
The exploit will tell you to use adb to reboot:
adb reboot
Click to expand...
Click to collapse
Run the exploit through telnet for the second time, it will reboot on it's own:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
Run the exploit through telnet for the third time, it will not reboot:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
Wait 0-60 seconds, for su to install, then install SuperSu from the market.
Enjoy!
Known issues:
If you have AP isolation mode enabled in your AP (aka WiFi router) you won't be able to connect to your phone via telnet, disable isolation.
Windows users having trouble see here
I confirm that this does work on the Droid Maxx on the new OTA update !!!
Thanks JCASE Much Appreciated !!!
Thank you!
Looks like I'm going to be at a loss. I never learned how to use adb :/
Sent from my XT1080 using XDA Premium 4 mobile app
This might a dumb question, but why don't we just release a rooted OTA update?
Quick question about this exploit. I know that the issue with the first two earlier methods is that everything is still signature checked, which prevents Custom ROM/Kernel flashing, as well as Custom Recoveries.
Does this exploit bypass the signature check to allow for custom recovery, or not just yet?
PS: Your skills are godlike. A million thanks for your root hacks!
Where's the Rockmymoto download link? Has it been pulled?
Mike
runner1717 said:
Where's the Rockmymoto download link? Has it been pulled?
Mike
Click to expand...
Click to collapse
LoL he made this for the MotoX then after someone tested in on the droid maxx he coppied the post over to here but didnt post the link. Dont worry I used this method on my droid maxx it works. just download RockMyMoto from post 1 right here
http://forum.xda-developers.com/showthread.php?t=2509590
runner1717 said:
Where's the Rockmymoto download link? Has it been pulled?
Mike
Click to expand...
Click to collapse
no, just me forgetting to attach it, seems ppl were using hte one i have in the motox forum. attached and fixed, thanks
I'm not sure why or how I did this but I am rooted with no write protection off I still have stock recovery. Everything went smooth but when I entered dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto for the first time it said I was rooted and to install super user I have tried since to go through the steps but i end up in the same spot
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
You are rooted, please install SuperSu. Exiting...
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
You are rooted, please install SuperSu. Exiting...
bigv5150 said:
I am rooted with no write protection off
Click to expand...
Click to collapse
youve almost got a triple negitive going on there, so to clarify, you are rooted, with write protection disabled (ie cant make lasting changes to /system) and you still have stock recovery. is that right?
I am getting link failed file exists when attempting to start telnet.
Forget all that, I was using the wrong port, now the process beings to start the telnet process hangs at waiting for completion then goes back to the impactor main menu, the telnet connection is not successful after that.
I am using the latest soak test update, Am I wrong thinking that this method works with that update?
---------- Post added 6th November 2013 at 12:05 AM ---------- Previous post was 5th November 2013 at 11:47 PM ----------
I uh, i'm an idiot, forgot I have multiple subnets at home. Worked like a charm.
TheWhiteChallenger said:
youve almost got a triple negitive going on there, so to clarify, you are rooted, with write protection disabled (ie cant make lasting changes to /system) and you still have stock recovery. is that right?
Click to expand...
Click to collapse
Yup sorry if it was confusing.
Ok I think I figured it out my phone is already rooted even after a factory reset. I used voodoo when I took the update and everything worked but I had no touchless controls so I did a factory reset after installing stock recovery. I must have had the protected su on the phone still and it stayed unless jcase has a work around for this I am stuck until the new fxz comes out. Then I can completely wipe su out and I will be able to start all over. It really is not that big of a deal I can use almost everything with just root even xpsosed setting work. It would appear the exploit does not allow you to run it if you have root it must verify you do and thinks all is well so it never installs the writer protection off and replaces the stock recovery. My stupid mistake for trying to short cut this I should have just did an fxz took the update and used this method.
Aaaaaaaaand back to rooted. JCASE you are the man!!
If anyone has questions on what to do ask away. it was very simple
I've never used adb before in my life. Would you recommend me trying it lol. Meaning would it be easy for a first timer.
Sent from my XT1080 using XDA Premium 4 mobile app
ADB is not difficult. There are tons of tutorials all over the web. I wish I knew more about telnet and the other stuff involved tho
Sent from my XT1080 using Tapatalk
how come there is no more development options in the new ota update?
ceelos218 said:
how come there is no more development options in the new ota update?
Click to expand...
Click to collapse
You need to go into settings and about phone. Scroll to the bottom to build number and tap it like 6-7 times you'll see it countdown and say "now you are a developer". This enables developer options
Sent from my XT1080 using Tapatalk
Franzie3 said:
You need to go into settings and about phone. Scroll to the bottom to build number and tap it like 6-7 times you'll see it countdown and say "now you are a developer". This enables developer options
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
ohh man thank you.. i was about to give up and just wait for kitkat. im off to try this rockmymoto again... so frustrating for my noobiness,
ceelos218 said:
ohh man thank you.. i was about to give up and just wait for kitkat. im off to try this rockmymoto again... so frustrating for my noobiness,
Click to expand...
Click to collapse
No problem. The rest should be cake if you have adb and have used it before. Let me know if you have trouble
Sent from my XT1080 using Tapatalk