I'll start out by saying I'm a total noob at this whole android rooting process, hence why I'm posting a thread here rather than posting a reply in the appropriate thread. I rooted and unlocked my phone using this guide: http://forum.xda-developers.com/showthread.php?t=1762709&nocache=1
I opted for the "flashing rooted stock ROM" option.
As the title of my post states, after installing CM10.1, I open superuser to update binary and everything appears to work fine until the very end, it reads "making sure new su works...fail!". Now when I restore back to rooted TW, I have no problem updating the su binary. I've tried Superuser update fixer, I've installed busybox; i cant find any other solution on Google. Any ideas?
The CM file I downloaded is: cm-10.1-20130714-NIGHTLY-d2vzw.zip
Gapps file is: gapps-jb-20130301-signed.zip
Liam1987 said:
I'll start out by saying I'm a total noob at this whole android rooting process, hence why I'm posting a thread here rather than posting a reply in the appropriate thread. I rooted and unlocked my phone using this guide: http://forum.xda-developers.com/showthread.php?t=1762709&nocache=1
I opted for the "flashing rooted stock ROM" option.
As the title of my post states, after installing CM10.1, I open superuser to update binary and everything appears to work fine until the very end, it reads "making sure new su works...fail!". Now when I restore back to rooted TW, I have no problem updating the su binary. I've tried Superuser update fixer, I've installed busybox; i cant find any other solution on Google. Any ideas?
The CM file I downloaded is: cm-10.1-20130714-NIGHTLY-d2vzw.zip
Gapps file is: gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
Make sure your using the latest version of the Superuser app, another option would be to try using SuperSU as an alternative to the Superuser app. Also is root access functioning normally for you?
Sent from my SCH-I535 using xda premium
Hi and thanks for the reply.
Yes superuser is up to date and I've tried supersu. Root seems to be functioning as I can open apps that require root access.
But when I try to restore missing apps via titanium backup, I get a msg saying "restore finished, 'x' elements failed". X being the number of apps I try to restore
Sent from my SCH-I535 using xda app-developers app
Check to see if the root apps are granted root access.
chevyowner said:
Check to see if the root apps are granted root access.
Click to expand...
Click to collapse
When I open SuperSU, it has a list of apps with superuser status. Is that what you mean? I can run root apps and as far as I can tell they're functioning, with the exception of when I try restoring apps with Titanium Backup
Also, right after I flashed CM10.1, I made a backup right away. Not sure if it means anything, but If I wipe/reset and restore the CM10.1 backup, and the first thing I do is try updating the binary in Superuser, it reads "checking installed version: 9 com.Android.Settings", until I open SuperSU and "update binary". Then if I go to Superuser, it'll say "checking installed version: 1.41:Superuser" as I imagine it should. But at this point I still run into "making sure new su works..fail!"
Superuser has no problem updating when I'm on my rooted stock. I'm sure I messed up somewhere along the way while flashing CM10.1, I just don't know where
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Towel Pie Root is a one click untethered app to root the Moto X, Moto G and the Droid Series(maybe others but these for sure) running 4.4.3 and below. It does NOT and WILL NOT root 4.4.4 so stop asking about it!
I want to started off by Thanking Geohot for Towelroot and JCase for Pie root, without them this wouldn't have been possible and I take NO credit for their exploits. If either of them doesn't want this posted they may contact me and I will gladly remove it.
Towel Pie Root combines Towelroot's futex exploit with a modified version of Pie root's xbin.img mount into one app. To achieve a one click untethered root for write protected devices! This DOES NOT remove write protection, and is still technically a temp root, I did include the option to enable root on boot. Which will re-root your device every time you reboot your phone, it also includes the option to perform a full reboot, or a soft reboot from within the app.
Here is a more technical description of what my app does. It includes TR's libexploit.so(aka the native exploit by Geohot) which I use to gain root privileges. Once it has root privileges it then echo's the file path to my modified Pie root file to uevent_helper. It then causes a hotplug event to trigger the kernel to execute the file path just echoed to uevent_helper. My modified Pie root files, kill TR's daemonsu and mounts Pie root's xbin.img over /system/xbin. Then it copies the newer version of SuperSU's su binary and executes the new daemonsu daemon and viola root
If you enjoyed my app, please donate to Geohot at https://towelroot.com/, and JCase at [email protected]ninglogic.com! I do not want any donations, I set out to develop this app purely as a challenge to broaden my development skills not to get a donation.
Installation Instructions: You need to have unknown sources checked in Settings>>Security, and if you have Towelroot installed uninstall it. In order to use TR's exploit I had to name the app's package name to the same name as TR's package name, so you will have to uninstall TR to install my app. Also if you are currently rooted with Pie root please reboot before running my app, to clear Pie's su daemon, and to unmount Pie's xbin.img. Then just click Make it ra1n on Moto, and wait for it to say Root Acheived Enjoy! If you encounter any issues please uninstall v1.0 then re-install v1.1.
Download link:
Version 1.2 for 4.4.2 devices
Version 1.2 for 4.4.3 devices
Version 1.1
Version 1.0
Known Issues: If after running it says Failed to Achieve Root, close the app and clear it from most recent's then reopen the app.
Screen Recording: https://www.youtube.com/watch?v=f6fXs3VJQHg (I will try to update this video with the full installation steps)
Changelog
-v1.2 10/5/2014
---Created a new bin.img from the tmo 4.4.3 sbf to fix the wifi issues
---Changed the modstring for the XT1032 hopefully it works now if it doesn't then there isn't anything else I can do
---Redid the device check to not allow unsupported devices to run the app
-v1.1 9/22/2014
---Added Moto G support, if I missed a model number let me know
---Fixed the issue with Xposed not working by mounting a bin.img over /system/bin
---Added in the ability to Uninstall the app and all files
---Added in various checks and prompts
Additional Thanks:
Verttex(Dier325) - for being my main tester and testing the numerous test apk's I sent him
jpond83 - for testing
mohlsen8 - for testing on the Moto G
NipplesOfTheFuture - for testing, some workflow ideas, and for convincing me to try and get the bin.img method working correctly
iKrYpToNiTe said:
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Towel Pie Root is a one click untethered app to root Motorola devices running 4.4.2 maybe 4.4.3 and below.
I want to started off by Thanking Geohot for Towelroot and JCase for Pie root, without them this wouldn't have been possible and I take NO credit for their exploits. If either of them doesn't want this posted they may contact me and I will gladly remove it.
Towel Pie Root combines Towelroot's futex exploit with a modified version of Pie root's xbin.img mount into one app. To achieve a one click untethered root for write protected devices! This DOES NOT remove write protection, and is still technically a temp root, I did include the option to enable root on boot. Which will re-root your device every time you reboot your phone, it also includes the option to perform a full reboot, or a soft reboot from within the app.
Here is a more technical description of what my app does. It includes TR's libexploit.so(aka the native exploit by Geohot) which I use to gain root privileges. Once it has root privileges it then echo's the file path to my modified Pie root file to uevent_helper. It then causes a hotplug event to trigger the kernel to execute the file path just echoed to uevent_helper. My modified Pie root files, kill TR's daemonsu and mounts Pie root's xbin.img over /system/xbin. Then it copies the newer version of SuperSU's su binary and executes the new daemonsu daemon and viola root
If you enjoyed my app, please donate to Geohot at https://towelroot.com/, and JCase at [email protected]! I do not want any donations, I set out to develop this app purely as a challenge to broaden my development skills not to get a donation.
Installation Instructions: You need to have unknown sources checked in Settings>>Security, and if you have Towelroot installed uninstall it. In order to use TR's exploit I had to name the app's package name to the same name as TR's package name, so you will have to uninstall TR to install my app. Then just click Make it ra!n on Moto, and wait for it to say Root Acheived Enjoy!
Download link: http://www.androidfilehost.com/?fid=23578570567716728
Screen Recording: https://www.youtube.com/watch?v=f6fXs3VJQHg
Click to expand...
Click to collapse
Thank you Sir, and Jcase and geohot... now the big question... I just factory reset 4.4.2 and rooted Pie.. installed your entitlement hack.. worked dandy... than I tried the tr... and guess what..... your app no longer works.. so, do I need to do another factory reset and install this new towelpie app or will your entitlement hack not work with this either? Or should I be the test pilot and find out myself...
doitinthedirt said:
Thank you Sir, and Jcase and geohot... now the big question... I just factory reset 4.4.2 and rooted Pie.. installed your entitlement hack.. worked dandy... than I tried the tr... and guess what..... your app no longer works.. so, do I need to do another factory reset and install this new towelpie app or will your entitlement hack not work with this either? Or should I be the test pilot and find out myself...
Click to expand...
Click to collapse
No need to factory reset. Just make sure you uninstall the towelroot app.
Then install this Towel-root-pie app. JUST this app. Run it, you should be good from there.
iKrYpToNiTe, I know you don't want creditz, but this is also such a helpful and much appreciated tool. I do want to thank you for sharing it with us.
My thanks go out to jcase and geohotz as well. A smörgåsbord of thanks to all of you!!
tapa'd on my moto x
Not good, I can't get it to stop rebooting. 4.4.3 moto g. Selected root on reboot, and now it reboots over and over.
Edit: Factory reset my phone through recovery using instructions at https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
I'm at least back where I started from.
Sent from my Nexus 7 using Tapatalk
side note, don't try it on the moto G. I'm stuck in a bootloop.
edit: was going to try and uninstall the app before it reboots but so far no good.. might have to factory reset
edit2: apparently I'm not fast enough to hit okay for the uninstall.
edit3: YES! I win. I uninstalled faster than towelpieroot could trigger the reboot! whew... took like 20 tries...
For future reference, you can (attempt to) uninstall using adb. It takes a bit more knowledge, but it's simpler.
adb uninstall (package)
tapa'd on my moto x
chrisp6825 said:
For future reference, you can (attempt to) uninstall using adb. It takes a bit more knowledge, but it's simpler.
adb uninstall (package)
tapa'd on my moto x
Click to expand...
Click to collapse
I tried! I couldn't get to ADB while in fastboot. How would I get into ADB Shell if I can't get into anything outside of recovery?
chrisp6825 said:
No need to factory reset. Just make sure you uninstall the towelroot app.
Then install this Towel-root-pie app. JUST this app. Run it, you should be good from there.
iKrYpToNiTe, I know you don't want creditz, but this is also such a helpful and much appreciated tool. I do want to thank you for sharing it with us.
My thanks go out to jcase and geohotz as well. A smörgåsbord of thanks to all of you!!
tapa'd on my moto x
Click to expand...
Click to collapse
Worked perfect! thanks!
So I was already Pied... Pie files already pushed to phone prior to running trpie app.. does this app do the pushing or do we still need to run Pie on its own to push the files?
doitinthedirt said:
Worked perfect! thanks!
So I was already Pied... Pie files already pushed to phone prior to running trpie app.. does this app do the pushing or do we still need to run Pie on its own to push the files?
Click to expand...
Click to collapse
According to the message the OP sent me, PIE is no longer necessary - at all. He advised me that you can run this app on a bone-stock Moto X that has never had PIE used on it.
Have fun guys, AND HIT THE "THANKS" BUTTON TO THE OP!!!!!!
tronmech said:
Not good, I can't get it to stop rebooting. 4.4.3 moto g. Selected root on reboot, and now it reboots over and over.
Edit: Factory reset my phone through recovery using instructions at https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
I'm at least back where I started from.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
windraver said:
side note, don't try it on the moto G. I'm stuck in a bootloop.
edit: was going to try and uninstall the app before it reboots but so far no good.. might have to factory reset
edit2: apparently I'm not fast enough to hit okay for the uninstall.
edit3: YES! I win. I uninstalled faster than towelpieroot could trigger the reboot! whew... took like 20 tries...
Click to expand...
Click to collapse
I'm sorry it caused bootloops for you, I remove 4.4.3 from the OP so others don't try.
iKrYpToNiTe said:
I'm sorry it caused bootloops for you, I remove 4.4.3 from the OP so others don't try.
Click to expand...
Click to collapse
I --really-- can't believe this isn't getting more attention than this!!! Not to mention more "THANKS" for the OP?!?!
Guys, if you use this method, SHOW SOME APPRECIATION! Five-Hundred-Seven (507) views, as of this posting, and only 7 "THANKS"? Where's the other 500?
EXCELLENT Job, Sir.
I have been having issues using this method. I was already using Pie for several weeks and wanted to try this to survive reboots. As soon as I installed and ran it I actually lost the root that I already had. The Towel Pie Root app would say that I had root access but none of my other apps would agree. I would get the message at the bottom of the screen stating the app was granted super user permissions but then the app would tell me that i don't have root, I tried adaway, xposed, and root checker. I uninstalled SuperSU and switched over to the ClockworkMod SuperUser and that worked for root. The problem that I had after that is that the root apps that I was using no longer work. Adaway shows as disabled and when I try to enable it it fails. The same whit xposed, every time I try to update/install it fails. I removed Towel Pie Root and went back to rooting with Pie and I am getting the same results. Has the Towel Root portion of this changed something that I am now going to have to factory reset?
Edit:
After a few more reboots once TowelPieRoot was removed and starting Pie again from the beginning I now have root as it was with everything working. For now I am just going to keep things the way they were. I have my terminal emulator setup to run the last Pie command on every start so it always attempts to root first. This makes it really easy regain root even if my device does get restarted and I lose root..
wow thanks, will this work with Xposed framework? I was looking for a simple root method without voiding my warranty, this seems nice, I'm gonna try it, thank yoU!
I like the app.. seems to work great.. but the only issue I have is is the OTA going to be stopped from downloading? I have two moto x, one still on 4.4 and rooted with slap, and a new one on 4.4.2 rooted with this app. below is a shot of what I get when i force check an update with the slapped moto, this is with the 3c_OTA files renamed to .bak
I dont get the same message with the new moto on 4.4.2, what I get is "your moto is up to date" and the same two 3c_OTA files are also renamed to .bak files.
xposed works with gravity
yabbandroid said:
wow thanks, will this work with Xposed framework? I was looking for a simple root method without voiding my warranty, this seems nice, I'm gonna try it, thank yoU!
Click to expand...
Click to collapse
yes, it works. have it running now. make sure that you softboot from within xposed.
i realize this is my first post here, finally decided to sign up ONLY for the reason to thank the OP for this.
I've been frustrated trying to get towel to work come to find out that geohot sold out and replaced the .apk on the site, wow........ then you had something secret for us and it was this thread and release of towelpie, GREAT work and goodjob!
xt1058 worked in 4.4.3!
most excellent!!!!!!!!
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
can someone tell me or point me in the direction of how to get the exposed modules up and running. i use this towel root, then open exposed framework installer and hit install/update and get a pop up with some info where the last line says "failed to create a backup or /system/bin/app_process" i hit ok and there is still red dashes under active columns for both App_process and XposedBridge.jar? am i missing a step? the towel root app says "root achieved enjoy" when i use it.
yamaha83 said:
most excellent!!!!!!!!
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
can someone tell me or point me in the direction of how to get the exposed modules up and running. i use this towel root, then open exposed framework installer and hit install/update and get a pop up with some info where the last line says "failed to create a backup or /system/bin/app_process" i hit ok and there is still red dashes under active columns for both App_process and XposedBridge.jar? am i missing a step? the towel root app says "root achieved enjoy" when i use it.
Click to expand...
Click to collapse
You have to do a softreboot in exposed to get it to activate.
wooddale said:
You have to do a softreboot in exposed to get it to activate.
Click to expand...
Click to collapse
i tried that? it seems i have root since i can access the system folder with Solid Explorer. but when i open framework installer. hit install/update i get the error, when i softreboot and go it and hit install/update i get the same error. i have the instal set to classic, should it maybe be something different?
yamaha83 said:
i tried that? it seems i have root since i can access the system folder with Solid Explorer. but when i open framework installer. hit install/update i get the error, when i softreboot and go it and hit install/update i get the same error. i have the instal set to classic, should it maybe be something different?
Click to expand...
Click to collapse
Were getting off topic here PM me Thanks
I ran the autoroot script found here to to root my stock device (with TWRP installed).
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
SuperSu is now installed, and when running TitaniumBackup I get a prompt for root however after granting permissions it complains that it could not acquire root privileges. Did I do something wrong?
EchoVelocity said:
I ran the autoroot script found here to to root my stock device (with TWRP installed).
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
SuperSu is now installed, and when running TitaniumBackup I get a prompt for root however after granting permissions it complains that it could not acquire root privileges. Did I do something wrong?
Click to expand...
Click to collapse
Solved it myself, next time I'll spend 10 more minutes diagnosing before asking. Turns out the version of TitaniumBackup from the Play Store doesn't play nice with Android 5.0, so I'm using the beta they posted to their twitter feed instead.
question
EchoVelocity said:
Solved it myself, next time I'll spend 10 more minutes diagnosing before asking. Turns out the version of TitaniumBackup from the Play Store doesn't play nice with Android 5.0, so I'm using the beta they posted to their twitter feed instead.
Click to expand...
Click to collapse
do you have a link for that twitter feed?? same thing is happening to me right now!!
The current play store version should work correctly now. Just in case it doesn't, have a look here.
https://twitter.com/titaniumbackup
I was about to put this in the main discussion thread of FlashFire, but it was closed so i decided to post it here.
So this is what happened, i rooted my Xiaomi Redmi Go with Magisk, the latest one, and when i opened FlashFire, it basically said that i have root, but access couldn't be acquired. It added "Found root: 19.4:MAGISKSU".
It was said in the Supported roots that Magisk is included so can't i use this app? I also tried to change my SELinux to permissive mode by going to the terminal and putting "setenforce 0", and the app still won't let me.
Any solutions to this? I was about to do perform a live backup through this app because the current TWRP version for this device is defective for my phone, the Backup option doesn't work and I've been looking for ways to backup my phone without custom recovery, but still with root of course.
Any help would be appreciated, thankyou!
Flashfire is discontinued so it is no longer compatible with the latest versions of Magisk
You might try going back to a older Magisk. It's definitely going to be before 19.3 but it may need to be older than that. There are two ways of doing this.
Set a custom channel in Magisk manager (install the older manager first).
Download the older release. If you're not familiar with github, expand the assets link under the release you want. The zip files will be listed there.
Make sure to remove the newer Magisk first.
spider1163 said:
Flashfire is discontinued so it is no longer compatible with the latest versions of Magisk
Click to expand...
Click to collapse
So is there solution that i can bypass that error ?