Related
I used universal androot to root my phone and I want to unroot it. I can't get rid of the superuser permission icon with the skull and crossbones. How can I get rid of that to return my phone back to normal?
The only way I was able to do this was to flash the old ERE27 passimg then the FRF91 Rom. Yes this wipes everything and takes your phone back to stock.
Not sure if anyone else was able to remove the SU icon and app without a full reflash back to the old version.
There has to be an easier way than that.
Get root explorer and go to system/app/superuser delete that is the easiest way
Sent from my Nexus One using XDA App
Is root explorer in the market? Priced in ₤.? I have android mate. Can I do it with that? Or another free app? I couldn't find a delete option in android mate.
rm is the delete command in linux. /system/app is the directory. Just use terminal and delete the apk. Don't forget to mount the /system/ dir as rw. Google should help you with that.
evilkorn said:
rm is the delete command in linux. /system/app is the directory. Just use terminal and delete the apk. Don't forget to mount the /system/ dir as rw. Google should help you with that.
Click to expand...
Click to collapse
That's pretty much Greek to me. Are there some instructions to do that somewhere? I just want to put my phone back to normal.
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=remove+system+applications+android
I think you can delete pretty much anything using titanium backup while rooted. Then, unroot and become a slave to your device.
NO ONE KNOWS HOW TO REMOVE THIS DAMN ICON? I can't delete it using Titanium Backup or Android Mate
tardman91 said:
NO ONE KNOWS HOW TO REMOVE THIS DAMN ICON? I can't delete it using Titanium Backup or Android Mate
Click to expand...
Click to collapse
Not anyone that's been in this thread...LoL!
tardman91 said:
NO ONE KNOWS HOW TO REMOVE THIS DAMN ICON? I can't delete it using Titanium Backup or Android Mate
Click to expand...
Click to collapse
Do you still have root?
Actually why would you want to unroot?
Tardman
I promise you I went through this all. SU is not an "app" and cannot be removed like any app can. It becomes part of the ROM. As far as I could tell. It wont even go away if you re-flash the stock ROM.
The only way I got rid if it was through installing the passimg from boot so the whole system wiped. Then flashed froyo clean.
Everything else, including all mentioned here, did not work.
And it only takes about 10 minutes to get through the process.
Sent from my Nexus One using Tapatalk
I unrooted. If I just leave it there it doesn't affect anything, right?
I tried to reflash froyo clean, but I kept getting some kind of errors (see my Restore Nexus One for Dummies thread). Oh well.
I want to unroot so that I get all of my over the air updates without any hassles. I thought about jumping ship to the new Cyanogen Mod now that it's a stable release, but I just don't feel comfortable enough messing with the phone like that just yet. Although tonight I did get adb and fastboot working, so I'm making progress. Maybe one day...
tardman91 said:
... I thought about jumping ship to the new Cyanogen Mod now that it's a stable release, but I just don't feel comfortable enough messing with the phone like that just yet. Although tonight I did get adb and fastboot working, so I'm making progress. Maybe one day...
Click to expand...
Click to collapse
All it takes is patience.
I was once where you are. Afraid of messing up my expensive phone.
I followed enough threads. Read enough wikis. Kept up with the Android™ blogs, and now?! I'm pretty good at this stuff.
Good enough that I rooted, and flashed a new ROM on a friends EVO today.
Although I DID BRICK IT for a while, I was confidant that I would find the solution on these forums.
Chance are it's happened to MANY MORE PEOPLE, aside from you and I.
No need to start a new thread. It's been asked before.
SEARCH, and YE SHALL FIND!
I used universal androot to root my phone an i selected unroot just to see if it actually unroots ur phone an when it said my phone wasnt rooted anymore i noticed that superuser was gone. So unrooting deleted superuser for me
chris6278 said:
I used universal androot to root my phone an i selected unroot just to see if it actually unroots ur phone an when it said my phone wasnt rooted anymore i noticed that superuser was gone. So unrooting deleted superuser for me
Click to expand...
Click to collapse
The problem with that is, Universal Androot no longer works after the FRG22D update. I forgot to unroot before updating and now universal androot can't unroot nor can I remove the superuser.apk since I'm no longer rooted...even though androot says I am and can't unroot. I guess universal androot is dead because I've been watching for an update and there has been no activity for 2+ months. I only used androot to enable the wireless tether option.
SuperOneClick...
Sent from my Nexus One using XDA App
My first post This worked for me after hours of research
Hey I'm new here and wow this forum has ton of information. Thanks all for sharing!
Hope this help!
But for this specific problem (superuser permission icon) won't delete. After hours of looking and trying multiple solutions, only one worked. The other ones deleted it, but as soon as I reformat my phone it would come back. Got this from another forum (travisFC thx!!) and it WORKS!!
I used Z4root (off the market) to re-root, fantastic app!!
1. Re-root your phone (yes make sure your phone is "jailbroke" again) and download an app in the market called Terminal Emulator (its free)
2. Now type the following in the terminal emulator app. One line at a time and pressing enter after each line
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
3. Sync phone with google (in the settings). (Not sure what the hell this meant, but sent an email to myself, don't think you need this step.)
4. Reboot phone
5. App should now be gone, but you will probably see the NEW superuser icon (widget)
6. Reapply unrooted OS (Z4root select unroot) and wipe device .
7. Should be unrooted and the app will be gone..you can check your root status by using the Terminal Emulator app and typing "su" it should say permission denied.
FYI - I'm on Rogers Captivate.
Hope this helps...what a headache.
get rid of superuser icon
Want to rid yourself of the superuser icon and be able to take your phone back to provider without worry? Here's how and it's less steps than Thumpers way (no disrespect intended).
1. I'm assuming you have unrooted your phone and just have the annoying su icon.
2. Download z4root from market. root your phone with it. Use the "temporary root" bar.
3. Once rooted go in and out of a few apps, then go back to z4oot and press it. It will ask for superuser permission and say yes.
4. Z4root will open and then tap on the "unroot" bar and that's it. It removes everything including superuser icon.
Enjoy.
By the way I have Galaxy S Vibrant i9000M with 2.1 eclair.
Hey all -- so i flashed back to JH6 with ODIN, got the JH7 update through Kies Mini, and then rooted. I also decided to use Launcher Pro as my default homescreen launcher.
Now i'm trying to use SWM to sideload some apps, but I always get the error (something like this) FAILED INSTALL PARSE UNKNOWN EXCEPTION ... the program recognizes my device just fine and loads up the .apk just fine but fails on trying to install it onto my phone.
anyone have an idea of what might be going on
SWM is unnecessary after root isn't it
Sent from my SAMSUNG-SGH-I897 using XDA App
Tchem said:
SWM is unnecessary after root isn't it
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The 2 are not related. You do NOT need to root to use Sideload. The SWM just uses the ADB command from the SDK. You can do this all day long without root.
If you want to install apps from your phone (not your PC) then you need to root and then you need to edit the settings.db file to allow sideload on the phone. You can't get to settings.db without rooting your phone.
Does that help?
alphadog00 said:
The 2 are not related. You do NOT need to root to use Sideload. The SWM just uses the ADB command from the SDK. You can do this all day long without root.
If you want to install apps from your phone (not your PC) then you need to root and then you need to edit the settings.db file to allow sideload on the phone. You can't get to settings.db without rooting your phone.
Does that help?
Click to expand...
Click to collapse
sort of not really, as i'm trying to upload apps/widgets from my pc. i want to hold off buying Root Explorer, and apparently Droid Explorer doesnt work on win7 64-bit systems yet ... just kind of odd that SWM can't load to my phone. i either get the INSTALL PARSE FAILURE UNKNOWN EXCEPTION or INSUFFICIENT SPACE or OLDER SDK errors. doesn't make sense to me...
turn debugging on ,
don't put the .apk files in the sideloader folder at all. caused the whole no space avaliable for me when i did that
try that... works for me.
updated with the ota an i'm rooted.
yeah i had debugging on, left the apks in a completely separate folder (didnt put them in the payload folder). the main failure i get is the install parse unknown exception one
im thinking it might actually be the apks i'm trying to upload. i got one apk to upload successfully, so maybe the other ones have some bad code in them. *shrug*
specifically i've been trying to upload the REVOlution transparent apps. all of them fail for me. then i uploaded minimal icons apk just fine.
I did Google and searched in this forum (Not just Dell streak 7 but all XDA forums)
1. I tried to root my DS7 (WIFI only ) using super one click and it did not work. I was able to root my device using Gingerbreak.apk. so one issue down
2. here comes main issue. once i have rooted my device i wanted delete some stuff rename some stuff and intall some new apk's. I chose ADB and my device does get listed when i search using ADB devices and i granted SU(Super user) permissions.
I wanted to remove phone.apk and telephoenprovider.apk (I have overcome this probelm using Super manager i have deleted both APK's) but i want to do this kinda stuff using ADB and i tried several methods. when ever I tried to mount or delete overwrite or push a file i get permission denied or read only file or some kinda message which means that i can do what I'm trying to do.
3. now i want to replace my existing email.apk with the provided here http://forum.xda-developers.com/showthread.php?t=951815
I was able to rename existing apk using Super Manger but i ahve to install the modified email.apk using ADB and now i'm stuck. I cant figure out how to install this apk using ADB or any other way.
why do guys think i'm not getting 100% true SU access over my DS7 using ADB and i get using Super manager or some root required tools like Busty Box Titanium backup........
two things:
what else i can do to resolve my issues with ADB
what is alternative way to install APPS besides ADB and Side load wonder machine.
Also said that I also have a captivate and i use all kinda ADB commands with no issues.
Not sure if this the right place.
This has me baffled.
I have a Samsung gt3113. Everything was fine until I stupidly uninstalled calendar storage and killed my calendar capabilities. So I flashed it back to a stock rom and rooted it. Ì then installed the Romswell v1.1 custom rom.
Got my calendars back but since then any app that requests su rights has a 50% chance of timing out when reading or writing files. At the best it will just take a long time to work.
I am using superSU pro.
I have completely reflashed. I have reformated my sdcard, just in case.
My first thought was it was superSU but people swear by it so I'm thinking that may not be the issue but I don't know. Ànd my system will not allow me to replace the su binaries, it fails either during the copy or testing the su function when I try to replace it with superuser.
When I am in droidwall and click to updatr thr iptables most of the time it times out but if I use the droidwall widgdt it does enable / disable but only after about a 30 second delay.
SD Maid will hang when scanning the file system.
The two common things are su access and reading / writing to the file system (either internal or external sdcard).
HELP!!! I have no idea what to try next. I've scoured the internet but had no luck finding a solution. Anyone have ANY ideas? I'm getting very frustrated by this.
Sent from my GT-P3113 using XDA Premium HD app
Gt3113 then this is the wrong place.
This is galaxy tab 7" original forum, GT-P1000 and it's variants.
Sent from my GT-I9300 using xda app-developers app
Hi All,
Since I am getting nowhere and no replies for my questions, I am going to rephrase them differently here so hopefully someone can jump in and give me a helping hand... (and please forgive if I seem to bombard the forums with questions).
My Note 3 SM-N900A, build KOT49H.N900AUCUCNC2, running 4.4.2. It is having issues with permissions that effectively block the phone from seeing any SD Card, USB, and internal memory space. It won't access any remote resources like internet or Google Play...either
Issues arose after I changed platform.xml. I since then unrooted the phone and uninstalled SuperSU. I can see that these 3 changes were reckless on my part, that I just put the phone into a very bad state that made it very very difficult to recover. I am still banging my head for the blunders but obviously that didn't help fix the phone. :crying:
I would like to know if there is a way to gain access to the phone's system area again to fix the permission issues. Can I use ADB Shell along with USB debugging? If yes, what are the commands I need? Can I somehow send towelroot and SuperSU to the phone via Odin and execute them? The reason I ask this is that I have no way to access any storage area on the phone, and there is no way to go online to download apps. Or can I put the phone into service mode by typing in the *# numbers on the keypad and hopefully fix it there?
Thank you
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
OK, Something Positive
andygev35 said:
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
vbcomer said:
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
Click to expand...
Click to collapse
Here's the original stock platform.xml if it helps you.
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Edit: instead of using adb push, use "adb install towelroot.apk" (if that's the actual package name). Go through the rooting process, download the ES File Explorer apk to your computer install it using adb. Hopefully if all that works, you'll be able to check and fix any permissions that got messed up with your platform.xml. It should be rw-r-r.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
A Step Forward
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Update: I saw the Towelroot app in the App Drawer, but after clicking on it and choosing "make it ralr", I got message "Unfortunately, towelroot has stopped."
vbcomer said:
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Click to expand...
Click to collapse
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
vbcomer said:
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
Click to expand...
Click to collapse
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
vbcomer said:
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
Click to expand...
Click to collapse
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
brisinger08 said:
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
Click to expand...
Click to collapse
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
vbcomer said:
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
Click to expand...
Click to collapse
The all-in-one file is the same as the 4 files, the only difference is installing it doesn't wipe the internal storage.
Have you tried running adb backup? That would be a heck of a lot easier than pulling a bunch of folders...if that doesn't work the databases are in /data/data
Calls: /data/data/com.android.providers.contacts
SMS and MMS: data/data/com.android.providers.telephony
Is there is any shell command to long tap