Related
Hey guys and gals,
I've got a 7.7 on stock ROM rooted using the original root method the day I purchased the tablet. I've been using my tablet happily for over a month now.
Unfortunately, late last night I opened up Google Play and started updating all my apps, including Busybox by stericson. There was a new busybox version out (1.20.1) and I decided to install it using "Smart install." I'm not sure if it tried to install to /system/bin or /system/xbin but after the install I saw the app give me an error message explaining that the install was unsuccessful. Anyways, now a lot of my root-requiring apps including Titanium Backup Pro is not functioning at all. It seems that my BusyBox installation is corrupt.
I tried using BusyBox Pro by stericson to uninstall but the corrupt busybox seems to have prevented a proper uninstall, so it still lingers. I downloaded JadeEyedWolf's root.zip from his pinned "Root" post which includes SU & BusyBox thinking that installing the root.zip from CWM Recovery would over-write the corrupt busybox. After flashing I rebooted the tablet and I still got the same corrupt busybox issues.
Anyone have any suggestions?
Thanks!
Edit: The corrupt busybox causes the Wifi to show Error when I try to turn on the radio. Not that internet is vital in repairing the tablet, but I've worked around it by tethering Bluetooth internet off of my OG HTC Evo 4G. It's strange though - I can peruse websites and view the items in the Google Play Store but it will never actually download, though the "Downloading --- " bar does display.
I had the same problem, stock rom as well. If you check the reviews for Stericson's Busybox on Google Play, the two top ones a few minutes ago both mentioned the same issue.
Trying to root again and reinstalling Superuser didn't help, neither did a factory reset (manually salvaging settings and data was a pain too).
Re-flashing the original rom fixed it, following the guide at http://forum.xda-developers.com/showthread.php?t=1469635
I switched to JRummy16 Busybox installer and it seems to work.
Surprising that no one else here mentioned the problem ...
Try this fix.
To be more specific: BusyBox installer 8.0 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Installer 8.1 and above has this bug fixed.
Had the same problem with busybox and had to re-install the rom. What does this fix do?
Sent from my GT-P6800 using xda premium
Already answered, see post above.
Deleted
Sent from my GT-P6800 using xda premium
Too late for me to try it, but thanks the same
ginkage said:
To be more specific: BusyBox installer 1.20.1 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Click to expand...
Click to collapse
Thank you so much it works well now! You're a life-saver ginkage. Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Thanks again!
Thank you so much it works well now!
Click to expand...
Click to collapse
That's why we are here.
Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Click to expand...
Click to collapse
Personally I always use /system/xbin, so that some custom kernel (like CWM) could use /system/bin if it wanted to.
BTW, the BusyBox installer bug was fixed in version 8.1, and current version is 8.2, so you should update it anyway. I was wrong to mention "1.20.1" version. Post edited.
Hi guys,
First of all, I want to apologize sincerely for the bug that my application introduced in 8.0. I didn't catch the bug because my device wasn't affected by the bug.. (I always test my app myself before releasing..yet I still miss things due to devices file structure being so different.)
At any rate, the bug was that the application symlinked all applets to Busybox. Normally, this is done if you use smart install and change the settings manually. By default smart install will not overwrite applets that are not already symlinked to Busybox.
This was not a problem with Busybox 1.20.1 but was a problem with my application and how it performed the install.
Again, I am very very sorry that this has occured, as a result I am scouring the web trying to find people with the issue and help them resolve it.
If you have this problem, it can easily be fixed by reflashing your current rom. you do not have to wipe or clear any data. Once this is done, you can download my installer, version 8.1 or greater and upgrade busybox as normal.
Please let me know if you guys have any questions.
Best Regards,
Stephen - Stericson
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Deleted
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
ninpo said:
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
Click to expand...
Click to collapse
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
regius said:
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
Click to expand...
Click to collapse
A thousand thanks kind sir, I'm back in business, that was pain free
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thanks for posting this, I'm in love with my 7.7 once again.
Appreciate the response stericson. I had purchased your Pro version but even after I fixed the uninstall failed and it also did not detect superuser permissions even though SU gave a notification that Busybox Pro was granted superuser. All other root-requiring apps work. Had to refund the Pro purchase though
No problem. there seems to be an issue with the application detecting root sometimes, that's why you can still try the install.
I'm looking into this issue, it just started showing up so I am not sure what is going on.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Really appreciate this fix. On the verge of wiping out everything....
But decide to see if its busy box since its the last thing i install before all this happens....
Just to note that uninstall busybox also doesnt solve the issue...
so need to fix.
I had a lot of problems with root permissions not being granted by Superuser app. Recently I have tried SuperSu from the market and uninstalled original Superuser app (important to follow the instructions for the App! ).
My main problem was that ntfssd was not granted root permissions at startup, so I had to start it again manually. With SuperSu it is no problem. Also I use Busybox and successfully updated to the latest binary recently.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thank you so much for that, I had been driven crazy and had also gone through a factory reset to try and get my device back working, to no avail. Can I ask where you got the ash you're including here? It worked for my Samsung Galaxy Tab 7 Plus, on 3.2, but is it a generic enough file that it can be dropped on nearly all Android devices without any issues arising?
I only ask out of curiosity and understanding the system more.
Hi guys android newbie here! My friend rooted my Nexus 5 and it was working fine for a couple of weeks. Yesterday I tried to open SuperSU and it didn't work! Other apps that required root didn't work either.
I have been looking around and it seems OTA updates may have screwed up my root. Every time I try to open SuperSU it says: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" If you just upgraded to Android 4.3 (I have 4.4), you need to manual re-root. Consult the relevant forums for your device!" I have used root checker by joeykrim and it says "Sorry! this device does not have proper root access" (to confirm my root is busted).
My question is, is there any way to fix this without re-rooting? If I have to re-root, can I just directly re-root it again using something like Wugs rootkit?
Thank you very much in advance!
Just flash the newest version of supersu and you'll be good to go..... http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
simms22 said:
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
Click to expand...
Click to collapse
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
seyba said:
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
Click to expand...
Click to collapse
cant even get into it?
Yea it says there is no SU binary installed. I think I've lost root access
seyba said:
Yea it says there is no SU binary installed. I think I've lost root access
Click to expand...
Click to collapse
flash this with your custom recovery, its the latest supersu http://download.chainfire.eu/supersu
bodooo said:
Just flash the newest version of supersu and you'll be good to go.....
Click to expand...
Click to collapse
I can install/update to v1.8! I just can't open it. Gives me a "SU binary not installed" when I do!
Did you install/update from the playstore or flashed the new update?
simms22 said:
flash this with your custom recovery, its the latest supersu
Click to expand...
Click to collapse
Sorry if this is a stupid question .. but how/ do I flash this or what program do i use?
My friend helped me root it so i have no idea on how to do this @@ Very sorry.
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
bodooo said:
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
Click to expand...
Click to collapse
Ok so I can't open flashify either. It also says I have lost root access and my superuser is busted. I have attached a screenshot!
http://i42.tinypic.com/2mgw0v6.png
Of course, you don't have root access, silly me lol Well guess we'll have to do it the hard way (it's not really that complicated) ok read carefully. Power off your phone, afterward hold the power and volume down buttons which should get you into the bootloader, cycle trough the options with the volume buttons and when you see recovery mode select it with the power button, now depending on which Recovery you have you'll have to choose the option that says install or install from sd card, again, depending on which one you have this will be slightly different. After doing i believe the paths will be the same, chose 0/ then look for the download/ folder which you should have that supersu.zip file, if you're using twrp recover it should be touch screen and you simply select it and swipe to install, if you're using cwm (which i do) you'' have to scroll with the volume buttons and select the file with the power button to install. I hope I was as clear as i could be, good luck
after going into recovery mode, there is just a android robot with his chest open and an exclamation mark! can't proceed after that.
Ouhhh you don't have a recovery then, do you have adb or any kind of toolkit?
I have wugs toolkit. but every time i try to do anything at all on it. It says ADB device not found? That seems to be preventing me from doing anything as well.
Do you have the adb drivers installed or/and usb debug turned on in developer settings?
how/where do i install adb drivers? I have not done so, and i doubt my friend did it when he rooted.
I do turn on usb debugging when i tried to unroot/root on wugs toolkit
In wugs toolkit it has a walk-through on how to do so, i suggest you use the RAW drivers option
I must be blind to not have seen this before. Thank you very much for your help I'll let you know how it goes!
*** 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 know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Boffortes said:
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Click to expand...
Click to collapse
uninstall supersu and try this one. some people have issues with supersu and have found superuser to work correctly.
I hired someone not super familiar with flashing a custom rom, but who knew more than me. We got MM installed but I am having some problems. First, the only reason, I updated the rom was to get mirroring. However: 1. there is no mirroring, but there is cast. I have a Tab 4 and mirroring works perfectly with it and KitKat. I tried about 5 mirroring apps from the Play Store and they all require that the Smart TVs I have (Samsung and LG) be connected to the Internet because using the TV's internet connection is a major nuisance for me. That is not required with my KK Mirroring, and I am wondering whether I should get rid of MM and flash KK. Or, is there an app that will work without mirroring. 2. My SD card is now invisible. When I link my Tab to my windows 7 computer, my SD card doesn't show. (Additionally, come to think of it, none of my files show. All I get is an image of 5100, but when I click on it nothing shows on my windows 7 computer.) 3. Probably related to No. 2 -- Some apps seem to install, but I have no way to access them because no shortcut is placed on the screen and I have no tree of files. (Titanium Backup for instance, can't be accessed. However, when I downloaded ai-keyboard, it mostly worked)
Hate to ask so many questions, but this is what I now have. Would call the person who did the flash, but his wife is due any day, and for all I know, gave birth yesterday.
which M Rom did you installed? kindly mention Rom and recovery build number as well.
are you using any other home launcher than the default? how did you installed titanium backup? normal or copy pasted apk to the system partition?
have you checked the luncher setting? for instance I can hide some apps from the nova launcher but can find it with it's search bar.
check with the default launcher or any other.
did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?
I haven't tested screen mirroring with this device. although I checked briefly with a Samsung S, S4 and a G3 on a LG smart tv with webOS 3 using LG TV plus app, I had to be on a same network with wifi hotspot enabled from my device (didn't required a working internet) and selecting LG tv plus option from the TV.
I still haven't been used to with screen mirroring and cast. so others can help.
Hi Billys,
Thanks a lot for your response. My Internet has been down for about 2.5 days and that is the reason I am late responding to you. The CM version was 13.0.20160222-2140-UNOFFICIAL -P5110. The CM Recovery Version was GT-P5113 CM Recovery 6.0.1.0.tar.
The Launcher is the default that comes with MM. I installed Titanium Backup through the Google Play Store. I have been fooling around with the device and Root checker basic says that root access is not properly installed, which might explain why Titanium Backup is not working. Also, SuperSu won't open.
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.
decijp said:
Hi Billys,
Thanks a lot for your response. My Internet has been down for about 2.5 days and that is the reason I am late responding to you. The CM version was 13.0.20160222-2140-UNOFFICIAL -P5110. The CM Recovery Version was GT-P5113 CM Recovery 6.0.1.0.tar.
The Launcher is the default that comes with MM. I installed Titanium Backup through the Google Play Store. I have been fooling around with the device and Root checker basic says that root access is not properly installed, which might explain why Titanium Backup is not working. Also, SuperSu won't open.
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.
Click to expand...
Click to collapse
Device specific builds are too outdated. Kindly flash these depending on your model
Espresso3g - P3100 & P5100
EspressoWifi - P3113, P5113, P3110, P5110
For more info, visit this thread http://forum.xda-developers.com/gal...fied/rom-cyanogenmod-13-cm13-0-t3303798/page1
And flash it with the latest TWRP recovery found on andi34.github.io under recoveries
Sent from my espresso3g using XDA Labs
Root is enabled through developer options. Go settings, about tablet. Tab build number 7 times. Back out and open dev options. Scroll down a bit and enable roo & adb. You should be good to roll then
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Champ1919,
I did what you suggested and was able to download TWRP from Andi's. I unzipped the file with the ES File Explorer. Nothing happened. Could you tell me what I should do next. Thanks again.
decijp said:
Champ1919,
I did what you suggested and was able to download TWRP from Andi's. I unzipped the file with the ES File Explorer. Nothing happened. Could you tell me what I should do next. Thanks again.
Click to expand...
Click to collapse
if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery.
decijp said:
Hi Billys,
You asked me: "did you unlocked the tab while it was connected to your pc? did you changed the mode to MTP?" Don't understand the questions, particularly the second one. If you could be more explicit maybe I could answer the question. Thanks again for your help.
Click to expand...
Click to collapse
when you connect the tab to PC, there is a logo of CM in the status bar, drag the notification menu, and tap the CM menu, there, check If MTP is enabled or it's set on charging only mode. you can also set this in setting-developer. make sure the keypad is not locked as well
billysam said:
when you connect the tab to PC, there is a logo of CM in the status bar, drag the notification menu, and tap the CM menu, there, check If MTP is enabled or it's set on charging only mode. you can also set this in setting-developer. make sure the keypad is not locked as well
Click to expand...
Click to collapse
Billys,
There was no CM logo, but went to settings and USB and you were right. Now I can view the files of my tablet on my PC. Thanks a lot.
Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?
decijp said:
Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?
Click to expand...
Click to collapse
It won't automatically get the zip file because you select the zip you flash. Just navigate to whet you put the zip and flash that
Sent from my espresso3g using XDA Labs
decijp said:
Smart-T "if you want install or upgrade twrp, dont extract the zip. boot into recovery and install it with your current recovery. "
I did the recovery boot, and it shows CWM v. 6.0.1.0. It also shows install zip from sd card. However, I have multiple zips on my sd card. How can I be sure that it is installing the right zip? Will it automatically grab the right zip file.?
Click to expand...
Click to collapse
install the latest twrp by using cwm. after install reboot back into recovery. you shuold see the graphical differences between twrp and cwm.
To make a long story short, it appears that my Superuser is misbehaving. Used root checker to analyze and it found that Superuser was installed and that SU Binary files were installed. However, it found a Root User Account Error. (Error: stderr: null, stdout: null, exit..value: 1) It suggested that I reinstall Superuser app from TWRP. .
After much experimentation, I can get into TWRP when I reboot in the recovery mode. (not when I hit the icon on home page -- tells me I need root access) When I hit install, I see CWM 13, An android 4.4 (omni-4-4-4-20160305-1323 expresso-HOMEMADE.zip) and a gapp 6 --- a long time ago when I downloaded 4.4, I didn't know how to get to the corresponding gapp, so I didn't do so. Also, SuperUser doesn't show up at this place, so I don't know how to reinstall it.
Can anyone tell me how to reinstall Superuser and get full SuperUser access?
Also, I am thinking of going back to Android 4.4 to get mirroring. Can someone point me to the gapp file for that. Additionally, when I possibly would be installing 4.4, would I first install 4.4 and then reboot and install gapps. Or should 4.4 and gapps be installed at the same time?
Thanks for everyone's help. Sorry to ask so many questions. However, have gone to youtube and web many times and still am confused about what is going on.
decijp said:
To make a long story short, it appears that my Superuser is misbehaving. Used root checker to analyze and it found that Superuser was installed and that SU Binary files were installed. However, it found a Root User Account Error. (Error: stderr: null, stdout: null, exit..value: 1) It suggested that I reinstall Superuser app from TWRP. .
After much experimentation, I can get into TWRP when I reboot in the recovery mode. (not when I hit the icon on home page -- tells me I need root access) When I hit install, I see CWM 13, An android 4.4 (omni-4-4-4-20160305-1323 expresso-HOMEMADE.zip) and a gapp 6 --- a long time ago when I downloaded 4.4, I didn't know how to get to the corresponding gapp, so I didn't do so. Also, SuperUser doesn't show up at this place, so I don't know how to reinstall it.
Can anyone tell me how to reinstall Superuser and get full SuperUser access?
Also, I am thinking of going back to Android 4.4 to get mirroring. Can someone point me to the gapp file for that. Additionally, when I possibly would be installing 4.4, would I first install 4.4 and then reboot and install gapps. Or should 4.4 and gapps be installed at the same time?
Thanks for everyone's help. Sorry to ask so many questions. However, have gone to youtube and web many times and still am confused about what is going on.
Click to expand...
Click to collapse
If you installed CM13, is actually pre rooted. Just enable it from the developer settings
Sent from my espresso3g using XDA Labs
Finally figured out that I could transfer SuperSu zip file to my Tab and then install it from TWRP. Did so and also wiped clean the cache and now SuperSu is functional and I can get rid of the bloatware and speed up the Tab. Thanks for everyone's help.