I was originally rooted by using invisiblek's original "stock" root, which contained some Sprint stuff, so I opted to do a clean start from a stock Verizon rom, but to save time I rooted using the adb script method from GS3DebugFSRoot http://forum.xda-developers.com/showthread.php?t=1792342 instead of Root66, which requires a 1.5 GB image download then must be flashed through Odin.
I did this to avoid some of the strange app behaviors from the rooted "Sprint" rom, but after rooting through adb with an automated script, some root apps don't function properly, even though they're getting root permission.
After doing some research and restoring my sprint NAND backup several times to compare, the main things I noticed are:
1. After rooting through adb, the Superuser.apk app is installed in /data/app (which is a user app location) as opposed to /system/app in the case of the flashable root method.
2. Superuser.apk is called com.noshufou.android.su-1.apk instead
3. Superuser.apk from a flashed rom has these permissions (seen using root-expl)
rwsr-sr-x, but the adb method file xxxxxx.su-1.apk has these permissions rwxrwxr-x
4. The owner of the file is "root" when flashed through Odin, but "system" when rooted with adb.
Otherwise, the su binary itself is ok, it is a newer version and larger in size compared to the flashed versions, but it has the right permissions and is located correctly in /system/xbin.
I tried deleting the xxxxx.su-1.apk in /data/app and copying Superuser.apk to /system/app, to make it a system app, reset permissions and "owner" and "group" to root, but lost root after rebooting, so had to start back from my NAND backup again.
Does anyone know how to make Superuser a system app in the /system/app folder without losing root?
Also, I'm not sure this is the cause, but Titanium Backup has a hard time detecting root every time I start it, and has to be restarted multiple times, which wasn't a problem when flashed root w/ Odin, and most importantly, DroidWall is not blocking ANYTHING, whether it's in whitelist or blacklist mode, which it did when I used Odin to flash a rooted rom. I've tried everything, bu to no availe, can a dev that might have an idea what is going on here, help me with this and point me in the right direction to look for what to fix to get DroidWall to work, and if that is causing these issues, to get Superuser installed in the right folder?
Thank you
Nvm, I can't seem to find it again, I know I saw it somewhere though. If this was the OG Droid or Droid 2 I could tell you how to adb push no problem, but it's my first Samsung device. I don't know if anything is different, and I don't wanna be responsible for a brick :S
Related
Ever since I upgraded to 2.2 I've been having issues with superuser. I always receive the notification when an app requests SU, and SU does list those items as having SU permissions, however - I'm having varying results;
Titanium backup - Can remove non system apps fine, can freeze system apps fine, but if I try to uninstall one (for example, stock MMS) it just hangs, and does nothing (I'm able to press home to get out but the process continues to run until I end it.) The rest of the app appears to function as normal.
Quickboot- works just fine (yet requires superuser)
Root Explorer- I'm able to delete system files but as soon as I refresh the folder where I deleted the app, it's still there. (And yes I'm mounted as R/W)
Flashing through recovery - works just fine, no issues.
So far this is what I've done that I thought would correct the issue;
(Firstly, I tried using superoneclick before PNP came out) Tried attempting with both ways and superoneclick advised that root was a success. After doing so, I still had the issues above.
Lastly, I decided to do a clean start when PNP came out so I went back and re-did the 2.2 leak (with odin) re-did CWM, re-flashed PNP (and a theme) yet I'm still in the same situation.
My question is, is anyone else having this issue?
If i'm the only one I will just try to start over again (this time using the updated leak that includes recovery)
I know Ti Backup had issues with removing system apps. As for root explorer I haven't tried to remove any system apps with it.
___________________________________
Just when you think you have it idiot proof, they come out with a better idiot.
bdemartino said:
Ever since I upgraded to 2.2 I've been having issues with superuser. I always receive the notification when an app requests SU, and SU does list those items as having SU permissions, however - I'm having varying results;
Titanium backup - Can remove non system apps fine, can freeze system apps fine, but if I try to uninstall one (for example, stock MMS) it just hangs, and does nothing (I'm able to press home to get out but the process continues to run until I end it.) The rest of the app appears to function as normal.
Quickboot- works just fine (yet requires superuser)
Root Explorer- I'm able to delete system files but as soon as I refresh the folder where I deleted the app, it's still there. (And yes I'm mounted as R/W)
Flashing through recovery - works just fine, no issues.
So far this is what I've done that I thought would correct the issue;
(Firstly, I tried using superoneclick before PNP came out) Tried attempting with both ways and superoneclick advised that root was a success. After doing so, I still had the issues above.
Lastly, I decided to do a clean start when PNP came out so I went back and re-did the 2.2 leak (with odin) re-did CWM, re-flashed PNP (and a theme) yet I'm still in the same situation.
My question is, is anyone else having this issue?
If i'm the only one I will just try to start over again (this time using the updated leak that includes recovery)
Click to expand...
Click to collapse
Has anyone figured out the deal woth TB? Ive been having the same issues.
nickrl said:
Has anyone figured out the deal woth TB? Ive been having the same issues.
Click to expand...
Click to collapse
Still doesn't work for me to uninstall apps. I just downloaded Uninstaller for Root from the market and it works fine. Do my backups in TB and uninstall from UfR.
akellar said:
Still doesn't work for me to uninstall apps. I just downloaded Uninstaller for Root from the market and it works fine. Do my backups in TB and uninstall from UfR.
Click to expand...
Click to collapse
I updated my root explorer and did a fresh install and it corrected the problem also.
Had same issue with TI, used Uninstaller for root but using pick'n'pack was pretty much the same experience
Dually noted on the uninstallation and reinstall of root explorer...
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Questions belong in Q&A. Moved
artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
i cant c y u would have to unroot, it shouldnt matter as apps dont care if it is rooted or unrooted, correction some apps u have to b rooted to work properly.
do u actually get an error message when trying to install an app
the only way is to restore back to stock, or if u just rooted ur stock firmware, meaning u didnt flash a rom, u can try flashing the system.img file, that might work but i never heard of any1 doing that
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
artisticcheese said:
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
Click to expand...
Click to collapse
dont think there is a temporary unroot method, going back to stock was the true method to unrooting, which app were u trying to install.
u can trying going back to stock, installing app, let it do its thing, backup with tibu or some other backup, reroot and then restore backup of app.....maybe wont work as restoring a backup is actually reinstalling the app
edit: try this i havent so try at ur own risk http://www.thespicygadgematics.com/2012/06/how-to-easily-unroot-any-android-phone.html it seems easy enough, i didnt think it was possible but it seems to b
artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
Thanks,
How do I root back after that though?
vincom said:
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
Click to expand...
Click to collapse
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
artisticcheese said:
Thanks,
How do I root back after that though?
Click to expand...
Click to collapse
Flash superuser zip in cwm.
cschmitt said:
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
Click to expand...
Click to collapse
kool. i learn something everyday
There is cool app in Playstore (free) which allows rooting/unrooting with no reboots and other complicated steps
FYI
https://play.google.com/store/apps/...51bGwsMSwxLDMsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0
Voodoo OTA can do a temp unroot as well. The Flixter app will not allow you to stream movis on a rooted phone. I used Voodoo to temp unroot then went back into Flixter and it started to play the movie.
I use an app called Temp root remover
It allows you to temporarly unroot and reroot in a matter of seconds
I bought this phone yesterday, Rooted this morning before work, Voodoo backed it up, and updated to the newest update,
Now when I try to Restore root everything looks grand except Superuser says the su binary is not found.
The su binary is located in /system/bin I believe or xbin but none the less its there. some apps can access root while other cannot..
Any Ideas anyone can give me besides rooting once again, Not an option at work.
Thanks in advanced,
If not let me know and Ill Root again once I'm home, Just looking to play on the slow day.
It's been my experience that on this particular phone Voodoo OTA Root Keeper isn't effective. Simply save the SuperSU.zip on your external SD card and reflash via custom recovery after updating..
The only thing simple is the belief in simplicity.
Haven't Bootloader unlocked yet, used the moto2failgo, or how ever it was to root this morning, so this is what it will be once again once I get home, Thanks for the response, Makes my wonder, the only App that continues to function with root access (aside from Voodoo its self) is Titanium Backup, I am wondering if this is because it has its own busybox and i had not install busybox prior to the update, and cannot now due to lost root.
Hey guys,
I've done a little Google-ing but I can't find an answer to this one...
So I rooted my new Nexus yesterday but today I started to create myself some backups of the stock ROM just in-case I ever need or want them.
While I was doing this I went through the following process:
1. Ran Google's Factory Image: https://developers.google.com/android/nexus/images#hammerhead.
2. Installed TWRP through Fastboot.
3. Rebooted my bootloader.
4. Opened TWRP's File Manager.
5. Noticed a weird folder...
So from the steps that I have listed above, I'm pretty sure that It's safe to say that the only data/software that is held on my device's storage at the particular point in time is Google's (excluding TWRP), correct?
So back to this weird folder... I noticed a folder in the following directory "/" and it was called "supersu". Is this folder something to do with the Stock Google OS or is this some kind of left-over folder from the ROM that I had used yesterday (unlikely seeing as I have just ran the factory image)?
Here is a DIR Listing of "/":
boot
cache
data
dev
etc
firmware
licence
persist
proc
recovery
res
root
sbin
sdcard
supersu (the folder which raised my suspicion)
sys
system
tmp
usb-otg
Am I in the wrong mindset? Does Google's Factory Image re-format the whole device including "/" or does it just do certain DIRs? Is that "supersu" folder mine or did Google already have that?
Thanks,
LewisD94
EDIT: I know what it is!
TWRP have a built-in service that allows you to install SuperSU to your device without having to download or flash it manually, I'm pretty sure that this folder would have landed it's self on my device when I installed the TWRP recovery through Fastboot... It's the only thing I can think of, testing it now but flashing the Factory Image without a custom recovery. Will report back with results.
FIXED: It must be something to do with TWRP's SuperSU service as I previously mentioned...
I have just ran Google's Factory Image: (https://developers.google.com/android/nexus/images#hammerhead) and installed ES File Explorer then navigated to "/" and I no longer have the folder in question...
New DIR listing of "/"
I don't have that folder. I have the latest TWRP installed. I really wouldn't worry about it though. Just delete it if you don't use Super SU
Sent from my Nexus 5
SuperSU is superuser which grants root access to apps. It was likely left over from a previous ROM because unless you completely wiped the SD card it remains inert.
When you return to completely stock like in the general sticky everything is going byebye.
There are stock ROMs hanging around development that are deodexed or odexed whatever you want. Some of them even have goodies inside.
When you root and unlock bootloader, the super user is installed during the process. Nothing to worry about. SU acts as your phones front door security screening any elevated/administrative task. This is what sprint personnel look for when excepting returns on devices. They know if your rooted and you try to say there is a issue with your device, if they see SU installed they'll know it was probably you who caused it. Besides the main fact but you have nothing to worry about. If you go completely stock and re lock your bootloader, just delete the folder off your SD card.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Must be a TWRP thing. I use CWM and I dont have a supersu folder.
Hi all,
I recently moved from Windows Phone to Android and have been enjoying fiddling with my phone. I rooted the phone using ODIN and CF Auto Root (CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5). I used Titanium Backup to remove a lot of bloatware from my device, but ended up making a mess of things. I then flashed the stock firmware for my Telstra device from Sammobile (G930FXXU1APF2_G930FTEL1APF2_TEL).
Everything seemed fine, but I now cannot use Titanium Backup to integrate updates or move apps to the system partition. I have tried using ES File Explorer and an adb shell to do this also, but with no luck. The apps either do not work, or are installed back into /data/app. It seems to move the apk to /system/app (I can see it there), then removes the app from /data/app and then hangs. If I reboot the phone, the app is uninstalled (but the apk is still in /system/app). I have noticed via /proc/mounts that the /system partition is often mounted RO. Even when I remount RW after TB starts processing it immediately becomes RO.
I have set the TB to use indirect app loading, enabled USB debugging and unknown sources for apps.
Before I reflashed with the stock firmware I was able to move apps to the system partition (I did Gmail and Google Keyboard and they worked well). Could I have stuffed up my firmware flashing? I only used the AP file, not BL/CP/CSC/UMS that were included in the download.
I apologise in advance if I am all over the shop here with my description. I know enough to get myself into trouble but not enough to get out! And yes, first thing I did after flashing was to back everything up so I don't make the mistake again...