Related
i have a samsung epic 4g. iused super1click but it is saying that busybox was not installed properly and now rooted apps are saying i do not have root access but root checker says i have root access please help
download "busybox installer" from the android market. you can install the latest busybox from it
i installed busybox installer but it is sayin it is already installed but not installed correctly
go into /system/xbin and /system/bin and look for the file "busybox." delete it and try installing it again with busybox installer
i have tried that in both system/bin and system/xbin but it will not delete. do i need a specific file management app
nalanotae said:
i have tried that in both system/bin and system/xbin but it will not delete. do i need a specific file management app
Click to expand...
Click to collapse
i forgot to mention that you will need to mount your system as read/write. to do this, a file management app would be very helpful. root explorer in particular (a paid app, but as you may already know there are always ways to get apps for free; that is all i will say about warez as it is prohibited on xda). in root explorer, you can mount your phone between r/w (read/write) and r/o (read only). once you mount it as r/w, i believe you can now delete those files
one other thing i forgot to mention, i keep getting a notification that my su binary is outdated when i click to update it says fail.
ok so i was able to delete the busybox files out of the 2 folders but when i went to install it with the busybox app it says "it looks like busybox is installed but it does not appear to be the version that you selected to have installed, you may want to try the intalation again but this using a different istalation location." i try a different location and check my root checker and it keeps telling me that busybox is installed incorrectly
as i have not used superoneclick before, i have no knowledge about the su binary being updated. i used z4root to root my phone.
your best bet is to do one of the following:
a) if you can unroot your phone, then do so (i believe superoneclick allows you to unroot your phone). then try rooting it again using z4root. download z4root from here and tell me what options it gives you when you open the app (it should say either temporary root and permanent root; select permanent root). z4root should work on your phone as it has the same requirements as superoneclick (which is having android version 2.2/2.2.1)
b) if step a didnt work, post in the superoneclick thread for help. but step a should work
Nexus 5
Rooted
Stock image
Used nexus root toolkit
Busy box crashes when attempting to install from within busybox
Says not installed
Used root explorer to check system/bin
And
System/xbin
No filename that says busybox
Not sure what to do.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
Resolved
Set system to r/w at boot as root.
Launched bb
Says installed
mjs1231 said:
Nexus 5
Rooted
Stock image
Used nexus root toolkit
Busy box crashes when attempting to install from within busybox
Says not installed
Used root explorer to check system/bin
And
System/xbin
No filename that says busybox
Not sure what to do.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
Resolved
Set system to r/w at boot as root.
Launched bb
Says installed
Click to expand...
Click to collapse
I have this same issue on my Nexus 6, i also used Nexus Root Toolkit, how did you set your system to r/w at boot as root?
I am not able to install buzybox due to "try to installing to a different location that may resolve isuue..please help me
I know this is old!
Hello readers,
I am aware that my resolution might not help everyone but it will definitely help some. This might only help if you are rooted and using the SuperSu app..
I know this is a really old thread. But there might still be people out there that have this problem and are having a hard time finding the the answer for it. I was just 5 mins prior searching on google for an answer but could not find one.
And so how did I fix it you may ask? (I hope)
Well long story short I turned the following option of in the SuperSu application: "Mount namespace separation"
I thought of this because I had seen a pop-up message when using Titanium Backup that if I experience problems, I should disable that option. And it was probably referring to the Titanium Backup app alone and not any other. But I gave it a shot and it worked.
In detail for those who need it:
It does not matter if you have the Busybox (by Stephen (Stericson)) application installed during this or not. (I had it uninstalled during)
Open the SuperSu app, swipe left on the screen twice so you get to the Settings page (or just click the Settings tab)
Scroll down until you see the option "Mount namespace separation".
If it is activated, disable it.
Reboot
Go ahead and install Busybox if you haven't.
Open Busybox and wait for it to load completely
Click install
Hurray!
Hello, i have bought busybox pro but i can't manage to install it through the app, in /system/xbin, i only have one file named "dexlist" and in /system/bin i have many files but none named busybox, when i try to install busybox on /su/bin, i get a message: "it looks like the installation of busybox was not successful / try installing it to a different location that may resolve the issue", but i tried differ'ent locations and it didn't work
---------- Post added at 09:03 PM ---------- Previous post was at 08:53 PM ----------
don't forget to reboot after unchecking "mount namespace separation" !! if not it won't work. my phone was quite long to reboot though...
it still doesn't work for me... on huawei p8 lite 2017 (PRA-LX1)
I'm still using the old version not BusyBox V+ .. anyone tried the latest version? it seems quite confusing and I couldn't execute scripts
Busybox
Example if use custom rom viper10 you can set system r/w in tweak > misc
lovemajj said:
Hello readers,
I am aware that my resolution might not help everyone but it will definitely help some. This might only help if you are rooted and using the SuperSu app..
I know this is a really old thread. But there might still be people out there that have this problem and are having a hard time finding the the answer for it. I was just 5 mins prior searching on google for an answer but could not find one.
And so how did I fix it you may ask? (I hope)
Well long story short I turned the following option of in the SuperSu application: "Mount namespace separation"
I thought of this because I had seen a pop-up message when using Titanium Backup that if I experience problems, I should disable that option. And it was probably referring to the Titanium Backup app alone and not any other. But I gave it a shot and it worked.
In detail for those who need it:
It does not matter if you have the Busybox (by Stephen (Stericson)) application installed during this or not. (I had it uninstalled during)
Open the SuperSu app, swipe left on the screen twice so you get to the Settings page (or just click the Settings tab)
Scroll down until you see the option "Mount namespace separation".
If it is activated, disable it.
Reboot
Go ahead and install Busybox if you haven't.
Open Busybox and wait for it to load completely
Click install
Hurray!
Click to expand...
Click to collapse
Hey, really glad you posted this even though you said it was old, and I'm still on it :laugh: but the combo of your solution, and mounting my /system as "r/w" through Root Explorer worked on my 6P on Oreo!! (OPR6)
Thanks again!! :good:
Williquah said:
Hey, really glad you posted this even though you said it was old, and I'm still on it :laugh: but the combo of your solution, and mounting my /system as "r/w" through Root Explorer worked on my 6P on Oreo!! (OPR6)
Thanks again!! :good:
Click to expand...
Click to collapse
What exactly do you mean by "and mounting my /system as "r/w" through Root Explorer" can you explain further? I can't get Busybox to install after OPR6 update
idbl_fanatic said:
What exactly do you mean by "and mounting my /system as "r/w" through Root Explorer" can you explain further? I can't get Busybox to install after OPR6 update
Click to expand...
Click to collapse
I'd be happy to help. It's been a little while and I haven't repeated the process yet so forgive me if I'm not super clear, even though I think I should be.
So what I meant was get the app Root Explorer ($3.99 on the app store) I don't know how 'piracy' is really looked at on XDA, though I can't imagine well, but you can download the Root Explorer 'pro' apk, and then - as long as it helps - purchase the app from GPlay to make sure to support the devs, which is what I did.
So to get to the actual process - should be quite easy as I did this on OPR6 myself - open Root Explorer, navigate to the "root" tab at the top. Then you should see "Mounted as r/o" and right next to it, a button that says "Mount R/W". Toggle that button, and the text on the left should state "Mounted as r/w", then try to install busybox (however you prefer - I used BusyBox Free by Stephen (Stericson) like I always do).
Hope you are successful with that method, please keep me updated with your outcome so I can help as best as I can.
Williquah said:
I'd be happy to help. It's been a little while and I haven't repeated the process yet so forgive me if I'm not super clear, even though I think I should be.
So what I meant was get the app Root Explorer ($3.99 on the app store) I don't know how 'piracy' is really looked at on XDA, though I can't imagine well, but you can download the Root Explorer 'pro' apk, and then - as long as it helps - purchase the app from GPlay to make sure to support the devs, which is what I did.
So to get to the actual process - should be quite easy as I did this on OPR6 myself - open Root Explorer, navigate to the "root" tab at the top. Then you should see "Mounted as r/o" and right next to it, a button that says "Mount R/W". Toggle that button, and the text on the left should state "Mounted as r/w", then try to install busybox (however you prefer - I used BusyBox Free by Stephen (Stericson) like I always do).
Hope you are successful with that method, please keep me updated with your outcome so I can help as best as I can.
Click to expand...
Click to collapse
Well that didn't work
Update, I had to change the path to /system/bin instead of /system/xbin
Device: Motorola Droid
ROM: CyanogenMod 6.1.2
Let me know if you need any other info other than this.
1. Cannot update su binary without flashing it from CWM recovery. I am currently up to date with 3.0.3 binary and 3.0.6 apk. See #2 for possible explanation.
2. Everything that calls for root access works except for, what I've noticed, apps that need /system/ and/or its subdirectories to be mounted as rw. *Superuser grants them the privileges, but the apps swear up and down that that isn't the case. Examples: ROM Toolbox, root file managers, etc. *Also, I cannot update busybox. It actually accepts the su privileges, but then fails. I can, however, install it to /mnt/sdcard/, not that that helps me. *There is also an app that has the option of mounting /system/ as rw, and while it says it works, I can't write to the directory or any of its subdirectories from any program. *I have Terminal Emulator, but I don't know enough about it to know what to do if that could help. I've gotten su privileges for it, but it won't let me access /system/. (side note: is there a way to flash busybox from CWM recovery and replace the WLAN files that I need to replace in /system/xbin/ and/or /system/bin/? In other words, since this worked for the su binary, would it work for those? If so, do u know of existing zip files or how I would go about making one?)
3. My wifi connects, tries to establish an ip address, and then is marked disabled and doesn't connect. I currently have it inactive. This has been happening since shortly after installing the CyanogenMod 6.1.2 -- not directly afterwards, but likely after installing and updating all my apps (I didn't install or update any system apps, as I knew not to).
Please let me know if you need to know anything else. I have searched and searched and searched for the answers to this problem, but I can't find it. In a nutshell I can't write to /system unless in recovery, and I can't use wifi at all. I did find some WLAN, etc files to replace the ones in /system with (a supposed wifi fix), but I obviously can't so that without write permissions.
Thank you so much in advance! I've figured out all my other previous issues on my own, but this one is a doozy!
Best,
SNJ
Me too - no mounting rw, busybox pro fails
Hi, I have the same problem on a Galaxy S with CM7.1. It just happened after I updated the last version of busybox pro. My wifi can't connect, everything which needs to mount system as rw fails, root explorer can't even start, and so the installation of busybox pro as well. It shows a huge list of apps which I need to symlink (never asked that before), and after trying installation it says that it appears as a different version of busybox than the one I selected was installed. I wonder if removing all the symlinked apps could do some good instead of leaving the overwrite option checked.
Anyone can help?
thanks
---------- Post added at 12:57 PM ---------- Previous post was at 12:24 PM ----------
just a small add-on. I tried a different busybox installer, and even if superuser indicated root access was granted, the app shut down telling it didn't detect root access.
???
OK, not really....I decided to do a system restore....bang, now I can only boot in recovery mode, not even the previous version but v.3.0.0.5, and I can't mount a thing, I get messages as unknown volume for path, unable process volume!....Now, how can I in any way wipe all and try to reinstall CM 7.1? phone doesn't get in download mode either.
Try flashing and moving files through adb.
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Thats OK said:
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
Click to expand...
Click to collapse
I finally managed to get back to ICS, then ran the rooting procedure. However, it always failed when it came to testing Superuser. Tried it four or five times. Then I tried installing the other Superuser apks. Every last one of them said the su binary needed to be updated, but every one of them failed to do so.
That's where I am right now. Unrooted ICS.
buhohitr said:
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Click to expand...
Click to collapse
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
Is there a previous version of SU installed or leftover?
See if it's still in running apps under settings.
If you're on ICS I'd try a factory reset and go from there.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
buhohitr said:
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
Click to expand...
Click to collapse
I did launch the app and it did tell me the su binary needed to be updated. So I told it to go ahead with a normal install. Installation failed. Also tried the SU update fixer from the play store, and that failed as well.
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Lim Wee Huat said:
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Click to expand...
Click to collapse
Yes, I would agree, this is the only way left for what to do next!
buhohitr said:
Yes, I would agree, this is the only way left for what to do next!
Click to expand...
Click to collapse
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
iCurmudgeon said:
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
Click to expand...
Click to collapse
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
buhohitr said:
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
Click to expand...
Click to collapse
Well, I tried, but when I rebooted with the power and vol-down buttons, I only got an "Android" icon and something else to its left, no RCK at all. The pad rebooted eventually and I was stunned when Superuser started working! I immediately ran Voodoo OTA Rootkeeper, then let the tablet update to 4.1.1. I then ran SuperSU and it said the su binary needed to be updated. I told it to do a normal install. "Installation failed." Said bad words in several languages and tried again. Update of SU binary succeeded.
Restored root. Success. Now restoring last Titanium backup backup.
I'm still worried, though. The symptoms would seem to point to flaky or at least unstable flash memory. What do you think?
I gotta decide whether to get a Samsung Galaxy Note tablet (7-inch) or the updated Nexus 7 tablet when they come out. I don't trust this TF700 anymore..
mudge
I have the same problem, but didn't downgrade!
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
IT Wannabe said:
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
Click to expand...
Click to collapse
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
buhohitr said:
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
Click to expand...
Click to collapse
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
IT Wannabe said:
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
Click to expand...
Click to collapse
Since motochopper has the ablility to root JB, you should remove superuser root (open supersuser and select remove root then reboot), then re root using motochopper if needed.
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
IT Wannabe said:
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
Click to expand...
Click to collapse
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
sgtrwe said:
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
Click to expand...
Click to collapse
Oh, sure!
After a search through my PATH, I've found that 'su' no longer lives in /system/bin, but in /system/xbin, with busybox and dexdump and every POSIX command you can think of symlinked to busybox. It is owned by root:root.
I guess that's just the way the JB root method does it...
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
Hello!
I need some Help with my Shield Tablet. I own the "Nvidia Shield 32GB LTE" Version and did root it 2 or 3 Days ago. Now i got the Message for the new "4.2 Upgrade" but after trying to install said Upgrade, i get the laying Android with an "Error". I tried the Installation 2 Times with the same Result. Do i have to Factory Reset my Shield to be able to install OTA 4.2?
I have no Experience with anything related to Software modification and got my root with a YouTube Tutorial on the Shield. I'd like to keep the root, and would reroot if necessary.
Any Help is appreciated!
Informations that may be helpfull:
- I have the Nvidia Family Drivers installed
- I have "minimal ADB and Fastboot "
- I own the "32GB LTE P1761" Model
- I have Android 6.0.1 installed with the Security Patch from 1. March 2016 and Shield 4.1 (24.3.67.35) Software
- I used the "TUTORIAL - Root NVIDIA SHIELD Tablet / K1 - Android 6.0" Tutorial on YouTube
Once you're rooted, you cannot update via normal means as the regular OTA update will check the system partition to make sure it is untouched.
The easiest way to update is to simply have the updater download the Full OTA and install. Go to Settings -> About tablet -> System upgrade -> 3 vertical dots on top right -> Advanced -> Check full upgrade (check it).
When it updates, it will remove root and very likely the TWRP recovery.
After it's updated, you can then go back and flash TWRP 3.0.2-2 to the recovery partition and then flash SuperSU 2.76 within TWRP. You may have older versions of TWRP and SuperSU if you used the YouTube tutorial, so be sure to get these newer versions.
Thanks for the the Advice, it helped!
Now im facing another Problem. After updating and rerooting, i can't use Lucky Patcher to install FakeGPS as an System App. I get the Error "there is not enough space within the system partition to move the application. please free up space in /system then try again.". I should have plenty of Space left on Internal and the full 180GB on my SDXC but it doesn't want to install. :I Any Suggestions?
Also "Hide my root" tell's me that it can't finde the "su binary".
Damn i want a one-push-do-it-for-me button. :crying:
[email protected] said:
Thanks for the the Advice, it helped!
Now im facing another Problem. After updating and rerooting, i can't use Lucky Patcher to install FakeGPS as an System App. I get the Error "there is not enough space within the system partition to move the application. please free up space in /system then try again.". I should have plenty of Space left on Internal and the full 180GB on my SDXC but it doesn't want to install. :I Any Suggestions?
Also "Hide my root" tell's me that it can't finde the "su binary".
Damn i want a one-push-do-it-for-me button. :crying:
Click to expand...
Click to collapse
Your not allowed to discuss LP here so I can't help with that. But if I were you I'd look at enabling compatibility mode in supersu. This helps with programs that haven't been updated to work with systemless su. I think the reason you can't install as a system app is because the program isn't properly calling su.
Sent from my SHIELD Tablet K1 using Tapatalk
I haven't found anything regarding compatability mode in supersu. Hidden option?
[email protected] said:
I haven't found anything regarding compatability mode in supersu. Hidden option?
Click to expand...
Click to collapse
Google search it. It's a command you can enter, I think in adb, that will let legacy root apps be granted root properly. I know it's all over the supersu thread in relation to es file explorer
Sent from my Nexus 5X using Tapatalk
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
Exile1975 said:
Google search it. It's a command you can enter, I think in adb, that will let legacy root apps be granted root properly. I know it's all over the supersu thread in relation to es file explorer
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Also, do you have busybox installed? If not start there
Sent from my Nexus 5X using Tapatalk
Yes I have busybox installed, but didn't help much. I will look in to Factory reset since I don't have private Data on this Tablet and I belive i may have done something wrong with the reroot.
I did a quick search on the supersu compatibility mode bit with no useful Results.
[email protected] said:
Yes I have busybox installed, but didn't help much. I will look in to Factory reset since I don't have private Data on this Tablet and I belive i may have done something wrong with the reroot.
I did a quick search on the supersu compatibility mode bit with no useful Results.
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...hare_fid=3793&share_type=t&share_pid=67710325
[BETA][2016.07.05] SuperSU v2.76
Sent from my Nexus 5X using Tapatalk
Thank you Guys for all the Help! \o/ Feel Brofistet from me.
I found the cause for the Error. It was the actual .apk that i tried to install. I went back trough my Chrome History to find the first one i used and it worked flawlessly. I sometimes have to wonder how i survive outside my Room...