I'm not too sure why this has happened, but I have two samsung vibrants... One of them has been rooted, has Clockworkmod's recovery, busybox and the samsung lag fix. It's fast as hell now...
I was repeating the process on the other phone and now I'm stuck... It show's it's rooted, (busy box and also I see the SU in the program list), and the SU program opens, but when I try to run any application that requires root permission, it seems it doesn't prompt to allow root. Ex: If I run the script to fix the lag, it should pop up and say allow/deny... But it's not doing that.
Any clues as to why this would happen, and how to fix it?
People are reporting issues on the Vibrant with the newest root app. Which version are you using?
I had the same issue.try installing the older version of busy box installer from the thread that is referenced in the original post,as soon as I did that it installed with no issue then I re upgraded busy box installer on my phone after patch. Here is the link to the post that has 1.17.1 that made it work for me
http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229
Sent from my Samsung Vibrant using the XDA app
Related
Hey Guys,
I recently bought a Nexus 7 from ebay. The guy I bought it from had put Paranoid Android 3 on it. I am cimplete noob and do not know how to root or flash.
I just did something which I dont know how to correct.
GooManager kept telling me there was an update which when tapped on, would bring me to the .zip file i was supposed to dl.
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh
Josh5321 said:
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh
Click to expand...
Click to collapse
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.
Pirateghost said:
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.
Click to expand...
Click to collapse
but in the past when I would click on the update notification it brought me straight to the download file. now it just brings me to the goomanager main screen.
reboot the device and try again. or you can go in and clear out all data and cache for goomanager in your settings/apps/goomanager page
I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.
Josh5321 said:
I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.
Click to expand...
Click to collapse
open the NEXUS 7 ORIGINAL DEVELOPMENT FORUMS and download yourself, or open GOOMANAGER and BROWSE COMPATIBLE ROMS...
I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.
TyneBridges said:
I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.
Click to expand...
Click to collapse
Hi, TyneBridges...
Well, I've never used GooManager myself... but the apps description on PlayStore certainly suggests you do need to be rooted to be use it.
You're a long way from the Motorola Xoom forums (wherever they may be)... but try, from PlayStore, running some app that requires root... like Titanium backup, or perhaps better, Android Terminal emulator (by Jack Palevich)... run it, and type...
Code:
su
If you're NOT rooted, you should see something like this...
Code:
$su
su: not found
$
-------------------------------------------------------
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
If you have some root SU binary installed, then Chainfire's SuperSU app should detect it... and either replace it, or update it.
Anyway... just some thoughts.
I really have no idea what other technical issues/problems there might be rooting a Motorola Xoom. And so you should hunt out the XDA forum for your specific device for more information... I'd be very surprised if there wasn't one.
Good luck.
Rgrds,
Ged.
GedBlake said:
Hi, TyneBridges...
...
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
...
Click to expand...
Click to collapse
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John
TyneBridges said:
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John
Click to expand...
Click to collapse
Hi, again John...
I'm afraid I'm a bit out of my depth with the Motorola Xoom... I know absolutely nothing about it. Sorry.
Here's where you should really be asking...
http://forum.xda-developers.com/motorola-xoom
...if anybody can solve your problem, then that's where you're likely to find them.
----------------------------------------------
If you can install a Custom Recovery like TWRP or CWM on your device, then it **SHOULD** (theoretically) just be a case of flashing Chainfire's UPDATE-SuperSU-v1.94, via that Custom Recovery.
On Nexus devices, you use FASTBOOT to flash a Custom Recovery.... on Samsung Devices, you need something called Odin to do likewise.
Once you have a Custom Recovery installed, rooting should be a piece of cake.
Problem is, I have absolutely no idea how to get such a Custom Recovery installed on a Xoom.
Do a bit of research... XDA is a vast repository of considerably more knowledgeable people than myself... and somebody is likely to know something.
Good luck.
Rgrds,
Ged.
Hey there everyone,
Just picked up my first smartphone, and obviously the first thing I had to do with it is install a different rom. I was able to get the one from here:
http://forum.xda-developers.com/showthread.php?t=2349077
To install just fine on my Canada SGH-I337m phone. It says one of the features of it is root privileges, and I can see SuperSU installed on the phone, but any app that actually tries to access root functions seem to just get turned away. I've tried both OpenVPN Installer and AdAway and OpenVPN is the only app that gives any helpful logs.
When I try to install it, it just fails and in the logs it's saying that /system/ is still read only even after being granted privileges by SuperSU.
Just wondering if I'm making a mistake or if I needed to do something on the phone before the root will work. I've already tried reinstalling SuperSU to no avail, and using the Motochopper root app ended up with a boot loop after it finished.
Open SuperSU and update binaries see if that doesn't cure your issue
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Yep, one of the first things I did when it didn't work was update SuperSU where it has you download/install it again from the store, which put me on version 1.65 which I believe is the latest version.
For a Canadian phone you will need to use CF-Auto root. However, trying to root a phone that is already supposed to be rooted can cause problems. I suggest you go to the CF Auto Root thread in the Original Development section and read the thread to see if any additional information or tips are given for your situation. Also, depending on the ROM you installed, you might need to install a Kernel specific for your phone to get full functionality. Again, this can be determines by reading the thread from where you got the ROM from. Good luck.
I know many of us are quite frustrated with the xposed module installation on the rooted htc phones. The main culprit for it is the busy box application. This application contains all the terminal commands necessary to break the security of the stock mobile system. It is not a virus application though but install those commands and provide you the functionality to execute the framework changes needed for some important apks like Titanium backup, adfree, xposed module, etc etc..
On HTC devices with Kitkat 4.4.2 specifically, due to the (S-ON) security feature, the busybox app will not get installed easily as apk even on the rooted custom roms. It must be installed separately along with the cwm recovery after updating the supersu. That is why many busybox installers lying on the play store are not working/effective anymore.
It could also be due to the busybox files getting installed either in the incorrect path/location (due to change in the internal sd card path in 4.4.2 kitkat versions) or the S-ON feature must be stopping from installing at the right place. Whatever may be the reasons for not working, there is fix for this issue and the steps are outlined below.
DISCLAIMER: Please don't blame me if you corrupt your device by following the below process. I am pretty sure that the below process works flawlessly, but the reason for failing or corrupting your device could be a combination of several existing issues in your phone. So I take no responsibility for your bricked devices.
Now the coolest part:
1. Your HTC desire 816 must be rooted and should have working clockworkmod recovery. Otherwise this trick doesnt work at all.
2. First lets fix the busy box app - Go to playstore and download Busybox on Rails free apk from here: https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
3. Open the Busybox on Rails app, select the Operation option as "Cleanup & Install" and method as Recovery (and not "normal"). This will reboot your device into recovery and install the busy box application.
4. Reboot the system. Vola Busy box should have installed correctly now. To confirm that reopen the same Busybox on Rails app and see if the System Status shows up as OK. If it does, your busybox is successfully installed. If not by any chance, try repeating the steps 2, 3 and 4 again. It should work.
Some people install the terminal apk from play store and execute some su commands to verify if the busybox is installed properly. But that is for people having much knowledge on software scripting side of things.
5. Now lets install the xposed module - search for the xposed module apk from here http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 and install it. Remember to download the xposed disabler apk zip as well, just in case if your mobile gets corrupted, you can flash that to bring back your original settings.
6. Install the xposed module and open Framework within the apk
7. Before hitting the Install/update option, change the Installation mode from defaulted Classical (Write to /system directly) mode to the middle one Recovery (flash zip automatically) mode. Dont change anything else in the settings.
8. Now hit Install/update
9. Phone will reboot the system into recovery mode, install the xposed module.
10. Reboot the phone and Volaaaaaaaa!!!!!!!!!! Enjoy the xposed framework in your mobile, which opens the endless opportunities to tweak your mobile.
Hit the thanks button if I have helped you in any way.
This method might works on all HTC models with S-ON security feature and 4.4.2 android Kitkat version, but have not tested it myself though. However, my friend did say it worked on HTC one latest model. Dont blame me if it doesn't by any chance.
Xposed
vbrsekhar said:
I know many of us are quite frustrated with the xposed module installation on the rooted htc phones. The main culprit for it is the busy box application. This application contains all the terminal commands necessary to break the security of the stock mobile system. It is not a virus application though but install those commands and provide you the functionality to execute the framework changes needed for some important apks like Titanium backup, adfree, xposed module, etc etc..
On HTC devices with Kitkat 4.4.2 specifically, due to the (S-ON) security feature, the busybox app will not get installed easily as apk even on the rooted custom roms. It must be installed separately along with the cwm recovery after updating the supersu. That is why many busybox installers lying on the play store are not working/effective anymore, mainly because of the files getting installed either in the incorrect path/location (due to change in the internal sd card path in 4.4.2 kitkat versions) or the S-ON feature must be stopping from installing at the right place. Whatever may be the reasons for not working, there is fix for this issue and the steps are outlined below.
DISCLAIMER: Please don't blame me if you corrupt your device by following the below process. I am pretty sure that the below process works flawlessly, but the reason for failing or corrupting your device could be a combination of several existing issues in your phone. So I take no responsibility for your bricked devices.
Now the coolest part:
1. Your HTC desire 816 must be rooted and should have working clockworkmod recovery. Otherwise this trick doesnt work at all.
2. First lets fix the busy box app - Go to playstore and download Busybox on Rails free apk from here: https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
3. Open the Busybox on Rails app, select the Operation option as "Cleanup & Install" and method as Recovery (and not "normal"). This will reboot your device into recovery and install the busy box application.
4. Reboot the system. Vola Busy box should have installed correctly now. To confirm that reopen the same Busybox on Rails app and see if the System Status shows up as OK. If it does, your busybox is successfully installed. If not by any chance, try repeating the steps 2, 3 and 4 again. It should work.
Some people install the terminal apk from play store and execute some su commands to verify if the busybox is installed properly. But that is for people having much knowledge on software scripting side of things.
5. Now lets install the xposed module - search for the xposed module apk from here http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 and install it. Remember to download the xposed disabler apk zip as well, just in case if your mobile gets corrupted, you can flash that to bring back your original settings.
6. Install the xposed module and open Framework within the apk
7. Before hitting the Install/update option, change the Installation mode from defaulted Classical (Write to /system directly) mode to the middle one Recovery (flash zip automatically) mode. Dont change anything else in the settings.
8. Now hit Install/update
9. Phone will reboot the system into recovery mode, install the xposed module.
10. Reboot the phone and Volaaaaaaaa!!!!!!!!!! Enjoy the xposed framework in your mobile, which opens the endless opportunities to tweak your mobile.
Hit the thanks button if I have helped you in any way.
This method might works on all HTC models with S-ON security feature and 4.4.2 android Kitkat version, but have not tested it myself though. However, my friend did say it worked on HTC one latest model. Dont blame me if it doesn't by any chance.
Click to expand...
Click to collapse
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?
heppojo said:
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?
Click to expand...
Click to collapse
The only advantage of installing busybox and xposed installer is to open up endless opportunities of tweaking your mobile to look and behave the way you want (in most cases). Also some finest apps like titanium backup, and others etc use these busy box services too.
The link2sd app may or may not work and in my view it is totally unrelated. I havent tried that much, so cannot comment much on that I am afraid.
heppojo said:
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?
Click to expand...
Click to collapse
I have tried and it worked.
vbrsekhar said:
The only advantage of installing busybox and xposed installer is to open up endless opportunities of tweaking your mobile to look and behave the way you want (in most cases). Also some finest apps like titanium backup, and others etc use these busy box services too.
The link2sd app may or may not work and in my view it is totally unrelated. I havent tried that much, so cannot comment much on that I am afraid.
Click to expand...
Click to collapse
Lnk2Sd is somehow useful for users with partition, very useful for low internal memory devices. Though a high quality SD card is necessary. Thanks to this tutorial. CONFIRMED WORKING for Xposed Framework.
Huge thanks for this. Got xposed working on my phone - running 4.4.2 with S-on / boot loader unlocked from HTC
Sent from my HTC_D816x using XDA Free mobile app
This is a off topic Que , but I require urgent help ..
I haven't rooted my device nor did I do any trick with it , but now my device is showing TAMPERED on hboot menu .. is this means my warranty is void .. how that can happen with even connecting my phone to pc.. can I suggest any way of removing it or unlocking my bootloader other than HTC Dev site, or any way to s off it . .. warranty issues
Sent from my HTC Desire 816 dual sim using XDA Free mobile app
sonnu said:
This is a off topic Que , but I require urgent help ..
I haven't rooted my device nor did I do any trick with it , but now my device is showing TAMPERED on hboot menu .. is this means my warranty is void .. how that can happen with even connecting my phone to pc.. can I suggest any way of removing it or unlocking my bootloader other than HTC Dev site, or any way to s off it . .. warranty issues
Sent from my HTC Desire 816 dual sim using XDA Free mobile app
Click to expand...
Click to collapse
It is very unusual to see that happen without you connecting to pc and trying to unlock the bootloader from HTC dev site. This was first time hearing that this can happen without trying to root or alter the mobiles internal system.
Anyways, to unlock bootloader, you have to go via HTC site and there is no other alternative as of now. The moment you unlock your bootloader, you will see that TAMPERED message in the hboot. If you are also receiving the red text while booting HTC that "This device has been tampered/altered and is development purposes only.... blah blah blah message", then definitely it has been unlocked bootloader.
May be your phone is a unlocked version, which requires the vendor to unlock the bootloader first and then have to unlock the service carrier. In this case you would get that message for sure, without you having to do anything. This way you will not have manufacture warranty, but will have the vendor warranty. Check with the place where you bought that piece.
Btw, if you find out that it has already been unlocked, then you might as well can root it as it makes your piece worth buying. All the best.
Hi, already follow the guides and steps given and now how can I know xposed working on my phone? What should I do next?
You are a genius vbrsekhar :laugh: Installation has been successfully Thank you dear :highfive:
Syria_BoY said:
You are a genius vbrsekhar :laugh: Installation has been successfully Thank you dear :highfive:
Click to expand...
Click to collapse
Cheers buddy, glad to know that it worked. Thank you for acknowledging!
Im a little confused seeing this post. Is this an old probelm? I get xpoaed to install just fine. Some of the status bar mods are wonky . Am I missing something ? Lol.
carnivalrejectq said:
Im a little confused seeing this post. Is this an old probelm? I get xpoaed to install just fine. Some of the status bar mods are wonky . Am I missing something ? Lol.
Click to expand...
Click to collapse
This is for stock ROM's.
Yeah I know. I've only ever used stock and cm11. Never had a problem besides some of the status bar icons not all changing colors. Install always went fine.
Sent from my 710C using XDA Free mobile app
Yeah some HTC 816 devices have the problem with busy box installation and that is why xposed framework doesn't work immediately after rooting.
สุดยอดเลยนาจ๋าาาา
im getting problem to install busybox on rails shows missing applets
pls reply guys
sjadhav252 said:
pls reply guys
Click to expand...
Click to collapse
Don't worry...mine is also showing missing applets.
But exposed still works.
Install xposed using the recovery method.
how can i install viper4android it keep asking for roos access after phone reboot
sjadhav252 said:
im getting problem to install busybox on rails shows missing applets
Click to expand...
Click to collapse
Mine too, in the first try there is warning in CWM about losing root etc. (sorry for my goldfish memory), the second try is ok but Busybox stills show "missing applets". However, you can continue to install Exposed Framework.
Big thanks to vbrsekhar!
Hello.
I have a towel rooted VZW Note 3. I'm trying to install the update but it keeps giving me a error message. Currently I have used the super Su and selected full unroot. And it still has the saresults. Any help would be great.
Chris
[email protected]
I'm in the same boat.. initially did towel root to get CM installed but my laptop wouldn't run Heimdall due to a dll issue I couldn't work out, so I never used root access. The update notification has been super pushy and obnoxious for several weeks now. I didn't realize SU had an unroot option but it looks to be moot?
EDIT: I went into SU and tried the unroot option. It gave a message about some kernals possibly rooting on their own again on boot so after SU closed I chose to start the software update now thinking it would go and do it's thing before the kernals could.... and it worked to upgrade it to 4.4.4
Maybe this needs some testing before I'd recommend it safely as I don't have an understanding of these things like I used to... I didn't even try to make a backup FFS
I'll give that a try thx
Sent from my SM-N900V using XDA Free mobile app
Before I start, my current setup is
Model # Z012DC, Buildnumber: 20.20.1703.38-201704010(Latest update) and rooted successfully using https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926. (I have 3-1-0 TWRP instead of 3-0-2, and used lazy flasher instead of no verify). Bootloader was unlocked via official bootloader unlocker.
Some apps do not work for some reason post root. For example, I use root explorer but when it loads, it just shows blank and after a short while it says it's not responding and I have to close it. The apps I have is genuine and purchased from google play.
Quite a few apps that read/write files in certain scenarios seem to freeze/crash the app after the app is opened.
I have done factory reset to make sure there weren't any other unknown variables.
Coincidentally, if I run root explorer or any other app I have problems with right after a factory reset(pre-root) the app loads up successfully and works just fine(though it shows that certain sections can't be accessed because it needs to be rooted but this is normal.) but it stops working after the root.
I'm trying to figure out if there's something wrong with the actual root process itself, or if there's some issues in regards to the latest firmware or something else entirely.
Any suggestions/inputs are welcome.
I had the same issue with root explorer, but I corrected it by factory resetting and re-installing root from this thread https://forum.xda-developers.com/showthread.php?t=3569926. Maybe it has to do with you using lazy flasher and not following the guide. Worth a shot?
Edit: I jinxed it, latest update caused the same issue again. You're probably right, we need a root v2 method
Install BusyBox and it works again. I installed it from the thread but it didn't work until I installed it from an app on the market
Confirmed. Installing busybox from app store fixed it. For reference the busybox version is 1.26.2.
Thanks!