Geohot stated in his thread "Possibly invited: Every Android phone with a kernel build date < Jun 3".
Do we fall under that? And is there any potential for using his root exploit somwhere in our X?
I too was wondering. Just read the article on Android Police.
http://www.androidpolice.com/2014/0...ve-and-maybe-almost-any-other-current-device/
Sent from my Moto X
I think it might be possible if you haven't updated to 4.4.3 yet.
EDIT: Known bugs:
su binaries don't seem to update. This may not be the root's fault.
Moto and HTC don't currently work because /system is write protected.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can confirm that this does not work. Just tried on my att moto x
I saw somewhere that it doesn't work because of the system write protection on the Moto X, but geohot is looking into finding a way around.
Sent from my SAMSUNG-SM-G900A using Tapatalk
linuxgator said:
I saw somewhere that it doesn't work because of the system write protection on the Moto X, but geohot is looking into finding a way around.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
You probably saw it where I did. Right above you. Good ol Brett.
Sent from my Moto X
Nevermind.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Sent from my Moto X
So I got it working for Titanium Backup and Greenify. Just have to enable Towel Root after each restart. Minor inconvenience till (if I'm able) I finally get unlocked. We'll see.
Sent from my Moto X
Jersey846 said:
So I got it working for Titanium Backup and Greenify. Just have to enable Towel Root after each restart. Minor inconvenience till (if I'm able) I finally get unlocked. We'll see.
Sent from my Moto X
Click to expand...
Click to collapse
Does this work on any type of moto x? I have a Verizon moto x.
Sorry didn't realize I was on the Verizon forums. I was searching this on my phone. So this does in fact work then? Just if you reboot your phone, you have to enable it again. I can deal with that to use WiFi tether.
Sent from my XT1060 using XDA Free mobile app
tu3218 said:
Does this work on any type of moto x? I have a Verizon moto x.
Sorry didn't realize I was on the Verizon forums. I was searching this on my phone. So this does in fact work then? Just if you reboot your phone, you have to enable it again. I can deal with that to use WiFi tether.
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
I'm on Verizon as well. (4.4.2) It's a bit tedious (should be very easy), but seems to work with Titanium Backup for freezing apps. I'm not even exactly sure how I've gotten it working but here is what I did. I'd love for somebody to chime in and let me know why my "root" has been a bit unreliable.
1. Downloaded and ran TowelRoot. Changed the last number in the string from "0" to "1".
2. Download SuperSU (Doesn't seem to install correctly, but does seem to (at least temporarily) give root privileges to Titanium Backup and the root options for Greenify.. But here's how..
3. When installing SuperSU I get a notification telling me it fails to install properly. However when I try running a root app and it requests SuperSU root privileges, and I do get a pop up asking. I grant the app privileges. However that app doesn't seem to start correctly... Until after I deleted SuperSU. Then Titanium Backup starts easily and it seems to have root access as I've successfully frozen some apps through this method.
I'm sure that I am getting lucky somehow and either missing a step or two or... I don't even know. After the only restart I have done since, I did the same thing. Towel Root 0 to 1 > Install SuperSU > Doesn't install correctly > Run root app > Grant app privileges > Delete SuperSU > Run app.
Somebody did tell me in a different thread that I need to run PieRoot once and I'll be fine after that. Not exactly sure what he meant by that since I'm unfamiliar with PieRoot, so it's possible that is the necessary step in my method that is missing and causing all sorts of nonsense. If this is indeed the step I'm missing, I'd love precise and exact directions on how to run pie root.
Sent from my Moto X
Jersey846 said:
I'm on Verizon as well. (4.4.2) It's a bit tedious (should be very easy), but seems to work with Titanium Backup for freezing apps. I'm not even exactly sure how I've gotten it working but here is what I did. I'd love for somebody to chime in and let me know why my "root" has been a bit unreliable.
1. Downloaded and ran TowelRoot. Changed the last number in the string from "0" to "1".
2. Download SuperSU (Doesn't seem to install correctly, but does seem to (at least temporarily) give root privileges to Titanium Backup and the root options for Greenify.. But here's how..
3. When installing SuperSU I get a notification telling me it fails to install properly. However when I try running a root app and it requests SuperSU root privileges, and I do get a pop up asking. I grant the app privileges. However that app doesn't seem to start correctly... Until after I deleted SuperSU. Then Titanium Backup starts easily and it seems to have root access as I've successfully frozen some apps through this method.
I'm sure that I am getting lucky somehow and either missing a step or two or... I don't even know. After the only restart I have done since, I did the same thing. Towel Root 0 to 1 > Install SuperSU > Doesn't install correctly > Run root app > Grant app privileges > Delete SuperSU > Run app.
Somebody did tell me in a different thread that I need to run PieRoot once and I'll be fine after that. Not exactly sure what he meant by that since I'm unfamiliar with PieRoot, so it's possible that is the necessary step in my method that is missing and causing all sorts of nonsense. If this is indeed the step I'm missing, I'd love precise and exact directions on how to run pie root.
Sent from my Moto X
Click to expand...
Click to collapse
Same thing I did. SuperSU doesn't seem to work, since it tries to update the SU binary every time you launch it. Just keep it on your device and don't open it. Should work for giving Root access.
dier325 said:
Same thing I did. SuperSU doesn't seem to work, since it tries to update the SU binary every time you launch it. Just keep it on your device and don't open it. Should work for giving Root access.
Click to expand...
Click to collapse
I might be missing something that you are doing then. Even if I keep it on my device but don't open it, it fails to give anything root access. Titanium, for instance, just gets stuck on the requesting root rights screen. If I delete SuperSU though, I'm able to somehow gain root for Titanium. Males no sense to a guy like me who doesn't always understand this kind of thing. Not very technically savvy.
Sent from my Moto X
Jersey846 said:
I might be missing something that you are doing then. Even if I keep it on my device but don't open it, it fails to give anything root access. Titanium, for instance, just gets stuck on the requesting root rights screen. If I delete SuperSU though, I'm able to somehow gain root for Titanium. Males no sense to a guy like me who doesn't always understand this kind of thing. Not very technically savvy.
Sent from my Moto X
Click to expand...
Click to collapse
Remove SuperSU, and try restarting your phone then applying Towelroot with 1 option again, and then check Titanium. I didn't need SuperSU to actually get root access. I only installed it because I wanted the power to deny things.
What do you mean change the number from 0 to 1? All I had to do when I loaded towel root was click "make it rain" I believe. It said I then had root but when I went into titanium backup, no root permissions were found. Is it because I didn't install superuser?
Sent from my XT1060 using XDA Free mobile app
dier325 said:
Remove SuperSU, and try restarting your phone then applying Towelroot with 1 option again, and then check Titanium. I didn't need SuperSU to actually get root access. I only installed it because I wanted the power to deny things.
Click to expand...
Click to collapse
Ok gotcha. I thought I actually had done that but no app actually gained permission till SuperSU, but I could be mistaken. Will give that a try.
Sent from my Moto X
---------- Post added at 09:06 AM ---------- Previous post was at 09:05 AM ----------
tu3218 said:
What do you mean change the number from 0 to 1? All I had to do when I loaded towel root was click "make it rain" I believe. It said I then had root but when I went into titanium backup, no root permissions were found. Is it because I didn't install superuser?
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
For the Moto X, we are supposed to change the last number in the Towelroot number string from 0 to 1. This can be achieved by triple tapping "Welcome to TowelRoot V3" in the TowelRoot app itself and then changing that last number from 0 to a 1.
Sent from my Moto X
Jersey846 said:
...Somebody did tell me in a different thread that I need to run PieRoot once and I'll be fine after that. Not exactly sure what he meant by that since I'm unfamiliar with PieRoot, so it's possible that is the necessary step in my method that is missing and causing all sorts of nonsense. If this is indeed the step I'm missing, I'd love precise and exact directions on how to run pie root.
Click to expand...
Click to collapse
PIE is the exploit/process that JCASE released to Root the X on 4.4.2 a little before Geohot released TowelRoot. Neither address write protection on the X, so there are some limits.
Since PIE was made specifically for the X, it will likely work better, more reliably.
But no matter how you root, if write protection is still enabled (which will be the case if you can't unlock your bootloader), you'll have issues with apps and things that rely on or require write permissions on /system, /system/bin, etc. That is the reason SuperSU is giving you problems.
Jersey846 said:
For the Moto X, we are supposed to change the last number in the Towelroot number string from 0 to 1. This can be achieved by triple tapping "Welcome to TowelRoot V3" in the TowelRoot app itself and then changing that last number from 0 to a 1.
Sent from my Moto X
Click to expand...
Click to collapse
Oh okay. See all I want root for is to use wifi tether. I will have try what you said later.
tu3218 said:
Oh okay. See all I want root for is to use wifi tether. I will have try what you said later.
Click to expand...
Click to collapse
What WiFi tether app will you be using or do you use? That is one of my things I want too. Tried one app yesterday and it didn't work.
Sent from my Moto X
Jersey846 said:
What WiFi tether app will you be using or do you use? That is one of my things I want too. Tried one app yesterday and it didn't work.
Sent from my Moto X
Click to expand...
Click to collapse
I Dont have one yet. Need to first try and get root.
Sent from my XT1060 using XDA Free mobile app
Related
There have been many people looking for an easy way to root the Samsung Galaxy Music S6010 (single sim model) and the S6012 (dual sim variant) since this phone came out six months ago. These people have all been frustrated. If anyone found a reliable way to root these phones, they have not posted them here on XDA.
So, here it is, with pics, so that it is easy for the noobiest of noobs.
standard disclaimer: BEFORE STARTING BE AWARE THAT ROOTING VOIDS YOUR WARRANTY (THOUGH YOU CAN EASILY UNROOT AND GET YOUR WARRANTY BACK) . I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE!!!
First of all, thanks to XDA member stat'o'flow who posted the method for Chinese tablets and phones, which seems to be pretty universal, but I am going adapt his method a little to focus on this particular device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HOWEVER IT SHOULD WORK ON MOST DEVICES, INCLUDING CHINESE PHONES AND TABLETS.
Do check if it works on your device and let us know in this thread.
On your PC:
1. Install USB/ADB drivers from Sumsung's website or simply install the Kies software for the Galaxy Music.
2. Install this software: http://www.moborobo.com Management Tools, loads own device specific ADB-drivers
3. Download & install this software from http://www.shuame.com/
- Install on your pc. During Installation uncheck every checkbox except the one that grays out the next-button upon unchecking. Now, there should be three shortcuts on your desktop. we are only going to use the first two.
4. On your device: turn on USB-debugging. Settings>Developer Options>OK>Tick USB debugging
On your PC:
5. Run Moborobo Software, then plug your device to USB-Port, wait until Moborobo has recognized it
6. Run the Shuame software.
7. Wait until shuame app appears on your device's screen. Then on your pc, in the Shuame window click the 4th icon in the top row (step 1). On the screen that appears, click on the 4th icon in the 2nd icon-row (step 2)
8. On the device click the 'Restore my Data' button
9. On the pc, wait for the green line to finish moving to the end (your device might restart in between)
Click the blue button!
On the Phone:
10. Download and install SuperSU app from Play store.
11. Shuame will ask for permission to grant superuser to SuperSU in Japanese, so remember you have to click on the left-hand side button.
12. Download and install root checker app from play store. Check if you are rooted.
13. Uninstall shuame and maroboro using ES explorer or Titanium (you will have to grant these programs superuser permissions first).
14. That is IT!!!
You can also use this Shuame software to unroot the device (always remember to do this before giving it in for service or claiming warranty!!!)
And also may other things, as you can see in this pic, with easy to understand translations of the chinese lettering.
You just have to click on 'REMOVE ROOT'
Can u give any method for installing custom recovery guide on this music duos after rooting ??????
I also wanted a good call recording mod
Pls anybody on this forum guide me
thanks
Sent from my GT-N7000 using xda premium
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
Can u give any method for installing custom recovery guide on this music duos after rooting ??????
I also wanted a good call recording mod
Pls anybody on this forum guide me
thanks
Sent from my GT-N7000 using xda premium
Sent from my GT-N7000 using xda premium
Can u give any method for installing custom recovery guide on this music duos after rooting ??????
Click to expand...
Click to collapse
Some developer has to make a custom recovery for this particular model before you can install it on your device. AFAIK there are no ROMS or recoveries available for the Samsung Galaxy Music phones.
Someone asked me this question on PM so I am quoting it here for other people.
Hey bro, do you know what I'm doing wrong? I don't get the recovery option on my phone but it get root... Maybe I'm I deleting the wrong archives on the last part or I just get a temporary root because 30 minutes later it say the us file don't exist
Click to expand...
Click to collapse
I have not encountered this situation before (not getting the 'restore my data' window) but try doing the entire process again. This time install the superSU app before restarting the phone after it gets root. Then delete the kinguser or kingroot app from your /system/app folder with ES Explorer (you have to grant it superuser permission first, and also change permissions for the app).
Uninstall the shuame and moroboro apps the normal way.
Now restart and see if you still got root.
Also please ask questions in the thread instead of pm, so others can also read (or offer) solutions.
FallenAngelmxw said:
Hello! I was looking into your thread about rooting the Galaxy Music, and I just wanted to say that I had the same problem than the other guy that sent you a PM!
I downloaded all the softwares you said, made everything correctly.
And after the sad result, I formatted the phone with Factory Data Reset.
The problem is: I can't make the root, the Android don't asks me if I'll accept the Full Restore, and when it finishes, I go to the root app checker that says my phone isn't rooted.
And even if I make the factory reset the Japanese crazy apps remains there!
And sorry about sending the message through here, I can't post on your thread because the rulles don't let me.
I'm a little desperate about my phone because it came with a lot of apps that eat the entire ram memory, so it starts to be very slow.
I already had tried another root option that didn't solve the problem.
Thanks for reading.
If you discover something about that problem, I'll be very glad!
Click to expand...
Click to collapse
If the phone does not ask you to restore your data, it might mean that there is some anti-virus or other security software that is interfering with the root process.
Or you do not have the correct ADB drivers for the phone. Check that you have the drivers for your model, disable security software temporarily and try again. Use the original USB cable that came with the Galaxy music phone to connect to the PC.
When are you factory-resetting the phone, right after you check with the root checker app or before? Factory reset can remove root. The fact that the Jap apps are still there after you reset means that they have succeeded in installing themselves into the system. Which superuser app are you using, Superuser or SuperSU? SuperSU is better since it also replaces the binaries.
FallenAngelmxw said:
Hello! Thank you for the support!
After resetting the phone I tried to root it again.
It occurs that when you open the root app checker, pops up a message in Japanese (that is the "root" permission), and on you have 2 options, the left one is to allow the access and the right one have a countdown and is the one that deny the access!
When I rooted for the first time, I denied without knowing what was happening.
Now I press the left one that is the allow one, and it works!
I wanna thank you for the thread, and I'm asking you again to quote this and post in the thread, because I don't have a permission.
I always entered in this forum, but never made an account, now that I saw this root a resolved to make one, so that's why I can't post. I have to post at least 10 messages on the general forum to grant my permission in other forums.
Click to expand...
Click to collapse
Thank you for providing this solution. I had also clicked on the wrong button, but somehow forgot to include this in the tutorial! I have now updated the guide.
:laugh:
NEW: UPDATE YOUR SAMSUNG GALAXY MUSIC DUOS S6012 TO OFFICIAL JELLY BEAN 4.1.2!!!
THE COMPLETE GUIDE IS HERE
:victory::victory::victory:
Tried the above rooting method but didn't get the RESTORE option so clicked the blue button on the monitor which created an application in Japanese language and the phone shows rooted now.
Only problem is if I disable that new Japanese app the phone says not rooted. so i have kept the app and every app which requires rooting permission takes permission from that Japanese application.
The SuperSU app also works but only for 10-15mins, have to give that admin rights in every 15mins, so i use the japanese app itself to grant permissions. Is this ok what I have done ?
rahulsinha said:
Tried the above rooting method but didn't get the RESTORE option so clicked the blue button on the monitor which created an application in Japanese language and the phone shows rooted now.
Only problem is if I disable that new Japanese app the phone says not rooted. so i have kept the app and every app which requires rooting permission takes permission from that Japanese application.
The SuperSU app also works but only for 10-15mins, have to give that admin rights in every 15mins, so i use the japanese app itself to grant permissions. Is this ok what I have done ?
Click to expand...
Click to collapse
Ya, it's ok. But ideally you should install an English language app such as Superuser or SuperSU. When you install SuperSU, do you also update the binaries? That is required for SuperSU to work. When Shuame asks for supersuser permission for an app, here should be option allow for ever. Once you have SuperSU installed, you can uninstall Shuame with the method described above. The trick is to allow SuperSU superuser permission for ever instead of just 15 mins. The English language apps have this option.
BTW, did you root the ICS build or the new Jelly Bean build?
itsnotmeatall said:
Ya, it's ok. But ideally you should install an English language app such as Superuser or SuperSU. When you install SuperSU, do you also update the binaries? That is required for SuperSU to work. When Shuame asks for supersuser permission for an app, here should be option allow for ever. Once you have SuperSU installed, you can uninstall Shuame with the method described above. The trick is to allow SuperSU superuser permission for ever instead of just 15 mins. The English language apps have this option.
BTW, did you root the ICS build or the new Jelly Bean build?
Click to expand...
Click to collapse
Ya, I did update the binaries, it asks as soon as the app opens but after every 10mins it used to ask me to update binaries. Now what I did is that I made it install as the system app and also checked TRUST SYSTEM USER & now on every app is seeking the permission from Supersu & not Shuame, so i have just disabled not deleted the Shuame permission app.
I had rooted the ICS version not Jelly Bean, quoted the wrong message by mistake.
I have one question, will this root method work with all the phones if you have all the needed USB / ADB Drivers ??
rahulsinha said:
I have one question, will this root method work with all the phones if you have all the needed USB / ADB Drivers ??
Click to expand...
Click to collapse
Ya it should work on most devices.
Only way to know for sure is to try it!
Thanx
itsnotmeatall said:
Ya it should work on most devices.
Only way to know for sure is to try it!
Click to expand...
Click to collapse
There is a great tutorial on "How to root MSI Windpad Enjoy 71" by kibaruk which uses only one English tool Cydia Impactor. I could root my Samsung Music Duos GT-S6012 updated to 4.1.2. JB very easily. No hassle with chinese language. I also faced the problem of not getting "Restore Your data" window while using Shuami software.But with this tool every thing is very smooth.
Vist this page: http://forum.xda-developers.com/showthread.php?p=45409641
mattanur said:
There is a great tutorial on "How to root MSI Windpad Enjoy 71" by kibaruk which uses only one English tool Cydia Impactor. I could root my Samsung Music Duos GT-S6012 updated to 4.1.2. JB very easily. No hassle with chinese language. I also faced the problem of not getting "Restore Your data" window while using Shuami software.But with this tool every thing is very smooth.
Vist this page: http://forum.xda-developers.com/showthread.php?p=45409641
Click to expand...
Click to collapse
Just tested it, it works smooth as butter!! Thanks Mattanur!!
It really is a much easier way to root the Samsung Galaxy Music (Note that I haven't tested with the stock ICS build, only the Jelly Bean 4.1.2 official update)
I will update my 'Update S6012 to Jelly Bean' thread with the method.
Thanks again!!
Not Work
Why not work, i can't see anything on my phone (when i try to install SUPERSU). I've done all you asked. Help
-iCode said:
Why not work, i can't see anything on my phone (when i try to install SUPERSU). I've done all you asked. Help
Click to expand...
Click to collapse
Check with root checker to see if you are rooted
itsnotmeatall said:
Check with root checker to see if you are rooted
Click to expand...
Click to collapse
Oh my god. Home i can reportage the Chinese Root with SuperSU I or Superuser??
Sent from my Kindle Fire HD using Tapatalk
-iCode said:
Oh my god. Home i can reportage the Chinese Root with SuperSU I or Superuser??
Sent from my Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Nothing happens when you try to install either of those apps? There is no popup in Japanese asking for permission? By your rather cryptic (possibly google-translated) reply above I assume you are already rooted?
Try clearing cache of both the japanese apps (in app manager) then try again.
Curious to see if anyone else has lost root after the latest supersu update? Rebooting did not change anything. I'm unable to use any root apps (xposed, root explorer, etc).
Any ideas?
Thx!
Sent from my XT1060 using Tapatalk
jco23 said:
Curious to see if anyone else has lost root after the latest supersu update? Rebooting did not change anything. I'm unable to use any root apps (xposed, root explorer, etc).
Any ideas?
Thx!
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
You should tell is if you are using a root exploit (and which one), what android version you are on, and whether or not you are BL-Unlocked.
I can tell you that my unlocked devices had no issues updating SuperSU, and root apps still work fine.
(I'm guessing you are locked since your signature says "Status 0")....but please confirm.
samwathegreat said:
You should tell is if you are using a root exploit (and which one), what android version you are on, and whether or not you are BL-Unlocked.
I can tell you that my unlocked devices had no issues updating SuperSU, and root apps still work fine.
(I'm guessing you are locked since your signature says "Status 0")....but please confirm.
Click to expand...
Click to collapse
sorry. correct locked. on 4.4.2 with root exploits.
but I got it back after installing other superuser apps.
Sent from my XT1060 using Tapatalk
jco23 said:
sorry. correct locked. on 4.4.2 with root exploits.
but I got it back after installing other superuser apps.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Oh, great! So problem solved, or are you seeking a solution to work with the most recent SuperSU?
I would rather use supersu, but so long as super user from click clockworkmod works, its all the sane for me.
Thx for the reply though.
I had to uninstall supersu, install super user, attempt to install it, reboot, make sure have root access via root explorer, install xposed, install adaway, soft reboot.
Sent from my XT1060 using Tapatalk
So I rooted with the towelpieroot method on my 4.4.2 Verizon Non-Dev Moto X. And Xposed won't install. I keep getting either a Root not detected, Write error, or I/O error. Here is a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to atleast be able to try it on my Moto X before the 4.4.4 update rolls around so I can decide if I want to delay it or not, if it lets me.
So any idea?
I used Root checker and I have root, and I tried this Mount System R/W app on the playstore because I don't know how to use ES explorer to do it. Still not working.
The only way I've been able to get exposed to work is using just pie root. There is a moto x tool kit which makes it easy but you have to use your computer. I can't get exposed to install with towel root or pietowel root. I'm on 4.4.2 with locked bootloader
Sent from my XT1058 using Tapatalk
superp32 said:
The only way I've been able to get exposed to work is using just pie root. There is a moto x tool kit which makes it easy but you have to use your computer. I can't get exposed to install with towel root or pietowel root. I'm on 4.4.2 with locked bootloader
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Alright, I heard some people had sucess but I guess not. So how would I go about un-rooting and rooting with this tool kit? (Where is it? Is it just the pie root thread?)
Just reboot to unroot any of the methods except pietowel if you clicked root on reboot then go to development section look for moto x tool kit I'd give you the link but I'm on my phone. Then use pie root its Jcases work but I think the tool kit just includes it.
Sent from my XT1058 using Tapatalk
superp32 said:
Just reboot to unroot any of the methods except pietowel if you clicked root on reboot then go to development section look for moto x tool kit I'd give you the link but I'm on my phone. Then use pie root its Jcases work but I think the tool kit just includes it.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Alright so I unchecked the towelpieroot from rooting on reboot, and used the Moto X Toolkit. I got Xposed to install, and thats it. Do I have to re-root each time I reboot to install a module? I did, and now I don't have root acess and the tool kit isn't working, it keeps checking for adb for quite a while now.
OK so when you plug in your phone it brings up a rsa code or something turn off USB debugging then turn it back on it should bring that up then reroot also don't reboot install the power menu module so you can soft reboot instead of going through the rerooting process every time
Sent from my XT1058 using Tapatalk
TechTinker said:
So I rooted with the towelpieroot method on my 4.4.2 Verizon Non-Dev Moto X. And Xposed won't install. I keep getting either a Root not detected, Write error, or I/O error. Here is a screenshot:
I want to atleast be able to try it on my Moto X before the 4.4.4 update rolls around so I can decide if I want to delay it or not, if it lets me.
So any idea?
I used Root checker and I have root, and I tried this Mount System R/W app on the playstore because I don't know how to use ES explorer to do it. Still not working.
Click to expand...
Click to collapse
For what it's worth, every time I reboot I need to try TowelPieRoot and Xposed 4-5 times before it will finally stick. I don't know why, but it is very difficult to get it to work.
I also got the same error as above in your screenshot. I can only have success in applying Xposed after a fresh, full reboot. If I do anything else with my phone first, I get the error.
Here is what I do:
1. Full reboot of phone
2. I wait 1-2 min for everything to completely start up and load (including any autorun apps or notification background processes -- I do not touch the phone or open any apps while I'm waiting)
3. Run TowelPieRoot
4. Use Root Checker or better yet, Busybox Checker to verify root and Busybox installed
5. Open Xposed, go to Framework, tap Install/Update
6. Back out of the reboot dialog and then tap Soft Reboot
From there, the phone will usually initiate a soft reboot. Sometimes, the phone will make it through and begin reloading any startup processes. I am careful not to touch the phone for 2 min while it does its thing. But most times, it fails and will do a hard reboot on its own. Back to square one. Using Root Checker verifies that I don't have root anymore.
So I do it again from step 1. As I mentioned, I go through the steps 4-5 times before finally, the soft reboot works, all startup items are loaded, and going into Xposed shows that it is running and up to date.
Obviously, this isn't very scientific. But, try it in succession a few times and see if it works.
same problem for me with towel pie root
I installed 3.75 B03 safestrap on my S5A from AT&T. After I backed up my stock rom, I noticed that Safestrap was disabled and I lost my root on my phone. Does anyone know what might of happened? I have no custom roms or that sort of thing on my device. Please keep in mind that I just switched from IOS to Android a few weeks ago and am trying to learn everything via google. Thanks for any input on this matter.
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Rakuu said:
When you say sfaestrap is disabled do you mean while your phone is booting it shoss the safestrap splashscreen with a red [Safestrap: disabled] because in that case safestrap is working that just means you aren't currently booted in to a rom slot which is fine. As for loosing root, what all have you done to verify this? Have you considered just rerooting?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
citron2k1 said:
Yes, you are correct. It shows red [Safestrap: disabled]. I used root checker from the play store to check if I was still rooted. It determined that I was not. The weird thing is, I rebooted my device and got root access again. So I rebooted it yet once again and I lost root access. It seems to be an intermittent problem. If I keep rebooting, it will eventually give me root access again. I was also able to successfully backup my stock rom and restore the device to give me root access again as well. I've just been playing around with it to try and figure out what is causing it to lose root access. Any ideas? I do have a 64gb evo samsung class 10 card if that makes any difference.
Click to expand...
Click to collapse
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Rakuu said:
Do you have supersu or superuser or any root manager app like that? If not install one and ser it up(install binaries, etc) and give it another go. If yiu do what exactly happens when you check, does any popup come up asking if you want to grant or disallow access?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
citron2k1 said:
I already had supersu installed. I don't recall ever having to set anything up. So I think everything is set at default. Should I "install SuperSu into /system"?
Click to expand...
Click to collapse
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Rakuu said:
That shouldnt be necesaary. So i assume everything ran smooth with installing busybox(required for safestrap) and any other root applications? The dialogs came up and such? You never answered my question last time, have you already allowed root checker root access, or has it ever asked for it at all?
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Yes, I did allow root checker root access. Sorry I missed that question. Further, everything ran smoothly with busybox. I'll just keep an eye on it. I hardly ever have to reboot my phone. Its just a minor hiccup that I have to deal with for now. Thanks for your help in this matter.
My ability to purchase and use Sunshine has been thwarted by this horrible root APK known as Kingroot. I've rebooted my phone more times than I can count. I get root some times, but then it quickly forgets it actually has root. Even the root junky video posted below had issues with it. We really need a more reliable temp root method.
I know this has probably been done/said/repeated about 100 times, but did you toggle the "root authorization" in the three dots "general setting" menu after you hit "Try to Root" and rooting gets to 100%? If it doesn't work, try again. If it still doesnt work, turn off the phone, turn it back on, and start fresh with Kingroot. I didn't figure the toggling out the first time. Once I did, sunshine runs and passes all tests.
Agreed it sucks and it doesn't work flawlessly 100% of the time, and sometimes needs a reboot to work properly, but it does work. I just tested right now to confirm the procedure. I'm still not ready to buy / unlock but I've gotten to this point a couple times.
Try to factory reset your phone. Then try to use kingroot to unlock your bootloader. Should probably work.
Sent from my XT1254 using Tapatalk
Run Sunshine b4 kingroot then when its rooted go to settings unthick and thick root aut then switch to sunshine with recents button and cross fingers..if done quickly works like a charm
In all fairness calling kingroot **** when it doesn't even support the turbo is ridiculous. It has atleast allowed most to temp root and unlock and it's free.
Sent from my XT1585 using XDA Premium 4 mobile app
I also had trouble with king root until I tried this:
1) Install both sunshine and king root
2) Run king root
3) While king root is running switch to sunshine and go through the steps. It should say that it is rooted (at least is did for me)
4) Once your bootloader is unlocked, re-run king root to get actual root.
5) Flash twrp
6) uninstall king root from the app setting
7) flash supersu from twrp
8) run the beta apk of super su
9) profit
Hope this helps
y8s said:
I know this has probably been done/said/repeated about 100 times, but did you toggle the "root authorization" in the three dots "general setting" menu after you hit "Try to Root" and rooting gets to 100%? If it doesn't work, try again. If it still doesnt work, turn off the phone, turn it back on, and start fresh with Kingroot. I didn't figure the toggling out the first time. Once I did, sunshine runs and passes all tests.
Agreed it sucks and it doesn't work flawlessly 100% of the time, and sometimes needs a reboot to work properly, but it does work. I just tested right now to confirm the procedure. I'm still not ready to buy / unlock but I've gotten to this point a couple times.
Click to expand...
Click to collapse
I did this about 20 times so far. It get's root, even Sunshine detects it sometimes, but then shortly after forgets it has root.
I'm not going to dig too much into this, but even with the issues, King Root is an amazing app if you think about it. Talk about ungrateful when a week ago we didn't think our phones would ever even be rooted let alone unlocked.
Keep trying and eventually it will work, or if you get fed up go build your own temp root, that's not too hard right?
Sent from my DROID Turbo using Tapatalk
Have you tried a factory reset or fxz'd back to stock first?
ostriches3064 said:
I also had trouble with king root until I tried this:
1) Install both sunshine and king root
2) Run king root
3) While king root is running switch to sunshine and go through the steps. It should say that it is rooted (at least is did for me)
4) Once your bootloader is unlocked, re-run king root to get actual root.
5) Flash twrp
6) uninstall king root from the app setting
7) flash supersu from twrp
8) run the beta apk of super su
9) profit
Hope this helps
Click to expand...
Click to collapse
After multiple attempts this method worked for me also.
Sent from my XT1254
golgothagecko said:
My ability to purchase and use Sunshine has been thwarted by this horrible root APK known as Kingroot. I've rebooted my phone more times than I can count. I get root some times, but then it quickly forgets it actually has root. Even the root junky video posted below had issues with it. We really need a more reliable temp root method.
Click to expand...
Click to collapse
Try the desktop version of Kingroot. I had your very same problem and once I tried the desktop version, everything went as it was supposed to go. Beware that the interface is in Chinese, but very intuitive though, so just click on the highlighted button.
After no less than 3 hours of fighting with Rootking, I finally got this phone rooted. Whew!
Although it was very frustrating for a day and a half, Kingroot finally worked for me. The three dots did not open a menu so there was no setting to toggle authorizations, only the per-app settings once an app requested root. Trying to use it more than once between reboots was a waste of time. In the end, it was: reboot; run sunshine to just before it needs root; run kingroot; and as it rapidly approaches 100%, switch back to sunshine and let it finish. It took well over 30 tries for me.
Sent from my XT1254 using Tapatalk
Kingroot worked like a charm for me. It did take a few tries and a couple of reboots. Sunshine recognized root for me however and I purchased the unlock code. I am now running resurrection remix ROM and I am loving it. $25.00 may sound expensive to some. However, I never thought I would be able to root and unlock this phone being a Motorola. Just keep at it and eventually you will attain root and be unlocked. Most definitely worth it.
dnwhome3 said:
Although it was very frustrating for a day and a half, Kingroot finally worked for me. The three dots did not open a menu so there was no setting to toggle authorizations, only the per-app settings once an app requested root. Trying to use it more than once between reboots was a waste of time. In the end, it was: reboot; run sunshine to just before it needs root; run kingroot; and as it rapidly approaches 100%, switch back to sunshine and let it finish. It took well over 30 tries for me.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
ostriches3064 said:
I also had trouble with king root until I tried this:
1) Install both sunshine and king root
2) Run king root
3) While king root is running switch to sunshine and go through the steps. It should say that it is rooted (at least is did for me)
4) Once your bootloader is unlocked, re-run king root to get actual root.
5) Flash twrp
6) uninstall king root from the app setting
7) flash supersu from twrp
8) run the beta apk of super su
9) profit
Hope this helps
Click to expand...
Click to collapse
For step 6, I assume you mean open up the kingroot app, go to the settings and select uninstall? When I do that I get a warning that I will lose root access. Is that true? Will flashing supersu in step 7 once again give me root?
m4rk0358 said:
For step 6, I assume you mean open up the kingroot app, go to the settings and select uninstall? When I do that I get a warning that I will lose root access. Is that true?
Click to expand...
Click to collapse
You are correct on the first question. For you second, you'll lose it temporarily, if at all. As soon as you uninstall king root, boot into twrp and flash supersu. Then run the beta apk from another thread (i forget which one) and you will have root. As proof, I'm running apps such as adaway, xposed, etc.
golgothagecko said:
My ability to purchase and use Sunshine has been thwarted by this horrible root APK known as Kingroot. I've rebooted my phone more times than I can count. I get root some times, but then it quickly forgets it actually has root. Even the root junky video posted below had issues with it. We really need a more reliable temp root method.
Click to expand...
Click to collapse
Yeah it is a nuisance, but I enabled airplane mode started my WiFi, installed sunshine, installed kingroot, installed flashify, ran kingroot, it failed rebooted, ran sunshine got to the checking for root part, hit home, started kingroot, rooted at about 50% used recents to switch to sunshine, it asked for permissions, granted them, ran sunshine. Rebooted, ran kingroot again, at 50% started flashify, granted root, flashed twrp, rebooted into twrp did the fix write permissions thing it asks you about on first twrp boot, rebooted, rooted once more with kingroot (its now stable) uninstalled kingroot (because you can after it is stable) and downloaded supersu, and rebooted into recovery and flashed supersu.
Sent from my DROID Turbo using XDA Free mobile app
dnwhome3 said:
Although it was very frustrating for a day and a half, Kingroot finally worked for me. The three dots did not open a menu so there was no setting to toggle authorizations, only the per-app settings once an app requested root. Trying to use it more than once between reboots was a waste of time. In the end, it was: reboot; run sunshine to just before it needs root; run kingroot; and as it rapidly approaches 100%, switch back to sunshine and let it finish. It took well over 30 tries for me.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Are you looking at the 3 dots in the upper right or the broken 3 dots at the bottom? I'm talking upper right. The bottom one is vestigial and you can ignore it.
Remember to do it AFTER you get to 100% root. Not at this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
y8s said:
Are you looking at the 3 dots in the upper right or the broken 3 dots at the bottom? I'm talking upper right. The bottom one is vestigial and you can ignore it.
Remember to do it AFTER you get to 100% root.
Click to expand...
Click to collapse
I never would have guessed that the auth setting doesn't show up until later.
Ok so I have managed to get sunshine to work by using king root through the process described earlier and I now have an unlocked bootloader. I am not sure however how to go about getting my root access to be more permanent so I don't have to try and use king root. I don't want to install any custom ROMs of any sort at this point, just looking to get root access for apps.
Also a side question has anyone been able to or come up with a method to relock the bootloader on this device?