I recently unrooted my desire. But the Superuser.apk is still there. I understand I will need to root my phone again but what methods can I go about remove the superuser.apk. Previous methods i have tried have failed.
If you still have superuser.apk you didn't unroot completely. But just flash a stock ruu file by running the exe. This will flash the stock firmware and recovery. An you will get rid of any customizations you have made.
I am on orange and they do not have a stock RUU to flash with I need to find an alternate method.
look in /system/app/ or /data/app/ and if its in /data/app/ just delete it, if its in /system/app/ delete it using adb ..... to be honest ive never looked for it
Related
Hey! So I got my G2 from a member on here last night (woohoo!) but I can't seem to root it. I tried every method on here including visionary and gfree. I had some success with gfree since I was able to sim unlock it. When in bootloader I get 's-off' on the first line. But when I go into Rom Manager it tells me I'm not rooted and when I type 'su' into terminal I get 'suermission denied'. Any help here? I really need to flash a new ROM due to ORD.
And just some info from System Info in the boot loader even though I think it's not needed here.
OS ver.-1.22.531.8
eMMC- unknown 2151MB 4407295sectors
Also under IMAGE CRC
hboot: 0x6570c0db
boot: 0x1b87420d
recovery: 0xd4af6ad9
system 0x9f52fea6
Any Update???
OK so you were able to get S-OFF via gfree but not permanent root, when you followed the gfree method, the last step (before the verify) of the gfree rooting guide on the wiki (not sure if that's the one you used) has you run a command to "lock in" root:
You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
Code:
# /data/local/tmp/root
# sync
Click to expand...
Click to collapse
I suspect this is where it went wrong.
You should be able to use the same method again to get perm root, just skip the gfree parts. Summary:
1. Get all the files on your phone (they are probably already there)
2. Get temp root using rage
3. Run the command (script) that I listed above
Link to the full instructions: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#How_To_Get_R.2FW_Access_.28Permanent_Root_.2F_.22Permaroot.22.29
I tried the wiki method three times, making sure I typed everything correctly. After I type the line you put up I get a series on lines that show that some files can't be shown (I dont remember the exact ones off the top of my head, I'll redo it soon so I can tell you which ones). I also tried it with two different SD cards.
SO I found the errors in another thread started today:
Code:
/data/local/tmp/root
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
Strange, /data/local/tmp/root is just a script that does all of the stuff to get you permanent root, not sure why it shouldn't be working for you.
I think once you are temp rooted you should be able to install CWM recovery and use that to install a new (pre-rooted) ROM. If you are not ready to or don't want to jump into a custom ROM you can load the stock pre-rooted ROM and should not even have to wipe (would advise a nandroid backup of course)
http://forum.xda-developers.com/showthread.php?t=836042
raitchison said:
Strange, /data/local/tmp/root is just a script that does all of the stuff to get you permanent root, not sure why it shouldn't be working for you.
I think once you are temp rooted you should be able to install CWM recovery and use that to install a new (pre-rooted) ROM. If you are not ready to or don't want to jump into a custom ROM you can load the stock pre-rooted ROM and should not even have to wipe (would advise a nandroid backup of course)
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
I should try temprooting again and flashing CWM. And The only reason I want to root is to flash custom roms. lol.
EDIT: Well that didn't help. I followed the guide for temproot. I did get the root prompt (#) in terminal, but when testing with 'su' gives me 'su:not found'. And CWM still tells me I'm not rooted and wont let me flash the recovery.
Try using visionary to temp root, that may yield more success.
You may want to use ADB to pull out the remnants from your previous attempts.
If you have # in the terminal you should not need to su.
If you can't flash CWM using ROM manager try this method instead http://forum.xda-developers.com/showthread.php?t=902493
With visionary I push temp root, it makes me wait for like 10 minutes, and does nothing. I was just doing su to see what it does. I'll try removing everything with adb and redownloading all the files. Anyway, what's the command to remove with adb? lol
Open an ADB shell and use the rm command to remove individual files, I would remove everything you ADB pushed originally.
Code:
rm /sdcard/su
rm /sdcard/Superuser.apk
rm /data/local/tmp/rage
rm /data/local/tmp/busybox
rm /data/local/tmp/root
Will only run if you have root access (a # prompt) and you may get errors with some since clearly something isn't as it should be on your system.
Did you try using the flash_image utility to flash CWM?
Also if you can flash the engineering hboot you should be able to load CWM from fastboot.
So I removed the files, redownloaded, and redid the wiki root method.
Still no luck. Same error as posted before. This is getting on my nerves. lol
Did you try to install recovery using this method?
If that didn't work did you try to install the engineering HBOOT?
raitchison said:
Did you try to install recovery using this method?
If that didn't work did you try to install the engineering HBOOT?
Click to expand...
Click to collapse
I will attempt these methods soon and report back.
Phone: Incredible 2, running Android 2.3.3 Stock Verizon ROM
S-OFF and Rooted : using revolutionary 0.4pre4
HBoot: 6.13.1002
Recovery: Revolutionary CWM 4.0.1.4
I'm having ROOT Access/SU problems. I need access to some files in the root/System/ directory and am unable to get r/w.
I s-off/rooted my Incredible 2 using the instructions on this tutorial http://forum.xda-developers.com/showthread.php?t=1219246 (The How To Root DInc2) and the instructions on the revolutionary.io website. (Essentially: Get S-Off via revolutionary> flash recovery CWM> flash su.2.3.6.3-efgh)
The revolutionary s-off process was successful and I got s-off.
I flashed Superuser su.2.3.6.3-efgh-signed.zip and seem to have Root. The binaries are upto date according to the app.
I have Titanium Backup, Root Check, BusyBox Installer installed. I had to install Busybox. All these apps run properly. I can wipe, backup, and install system app data via Titanium Backup. Root Check says I have root access and the correct Busybox location.
The Problem
I installed Root Explorer today and I am successfuly able to change from R/O to R/W and back on the root directory and on the SDCard. But when I go to the System directory I cannot change from R/O to R/W.
Tryed to connect to the Inc2 from my PC (winXP) via ADB. ADB Devices command shows my device. When in ADB Shell the default profile is $. When I type in SU I get back the message "SU: permission denied" I do not get a prompt from Superuser on the phone to give access.
(To see if the problem was in the steps I was doing I tried this on my rooted Incredible 1 and in Root Explorer I was successfully able to remount the System directory from R/O to R/W and back. But the same problem with ADB I have on both Inc1 and Inc2. (Inc1 was s-off/rooted with Unrevoked3/Unrevoked Forever, with su.2.3.6.1-ef-signed.zip.)
I'm not sure what went wrong where, since some of the root access is working. Any suggestions? Help?
Thanks,
that happen to me before. and the only way to change the r/o to r/w is going back to stock,if you have a stock back up rom you have to run that one,and then you can install the rom you want,and the you can change with root explorer s/o to r/w.if you dont have a stock back up you have to install the PG32IMG,and then you have to go to revolutionary and install the recovery.dont forget to turn off the fast boot.if you dont know how to do that,setting,power,and then uncheck the fast boot to off.
I dont think your binaries are up to date.
Try installing SuperUser 3.0 and report back - with updated binaries. The binaries should show at least verison 3.
I had issues to with the Root access that came with revolutionary and this worked for me.
You are on the right path though.
I'd like to try and avoid flashing the original Verizon ROM back on the phone. I'll leave that for last resort. There is stuff that I've done to the phone that I would rather not have to go through to do again.
In Superuser I tap on the 'check for binary updates', the respone after checking is that the 'su is up to date'. The version that I'm currently using su.2.3.6.3-efgh-signed.zip the files are modified in 2008 and 2011. So it seems to be upto date.
Is there a place I can download the latest version of Superuser 3.0?
The version of Superuser3.0 that I was able to find, when I open the zip file, shows all the files last modifed in 2008.
You wont have to flash back.
Follow my advice and install the new SuperUser on the market. It is 3.0.
Once in the application go to update binaries and update anyway.
Reboot and let us know how it works.
Those 2.3.6.3 binaries didnt work for me either. Now im fine after following my own advice.
Oh - and also - check to make sure that you have allowed specific permission for the application you are having issues with - within SuperUser.
You will be pleased to see that the new SuperUser can automatically grant Root to all of your apps...dangerous, but speeds things up.
@tinkbtrar. Thanks!
Ugrading to the latest Superuser 3.0 and updating the binaries did help! Still some problems, but making progress.
I can connect via adb shell and get SU privileges. # shows up! I think I now have r/w privilege on /system. Not sure, but I think I do. (I'm still learning adb shell and linux commands)
But I still cannot get Root Explorer on the phone to work properly. Same problem as before. I can get r/o and r/w on the root directory, but cannot get r/w on the System directory. The button turns green, but the nothing changes.
I can live with getting SU privileges in adb shell, but it would really be nice to get r/w on System in RootExplorer.
gunnyp said:
@tinkbtrar. Thanks!
Ugrading to the latest Superuser 3.0 and updating the binaries did help! Still some problems, but making progress.
I can connect via adb shell and get SU privileges. # shows up! I think I now have r/w privilege on /system. Not sure, but I think I do. (I'm still learning adb shell and linux commands)
But I still cannot get Root Explorer on the phone to work properly. Same problem as before. I can get r/o and r/w on the root directory, but cannot get r/w on the System directory. The button turns green, but the nothing changes.
I can live with getting SU privileges in adb shell, but it would really be nice to get r/w on System in RootExplorer.
Click to expand...
Click to collapse
Be sure to click thanks if you haven't already. Lol.
Try wiping data...force closing and uninstalling root explorer (thru manage applications...not CWR).
Should take care of it. And because you are rooted you should have full access to filesystem via adb already.
Sent from my Xoom using xda premium
try mount -t ext3 -o remount,rw /dev/block/mmcblk0p25 /system with adb. thatll remount /system as readwrite
Sent from my Incredible 2 using XDA App
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
gunnyp said:
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
Click to expand...
Click to collapse
trust me you will have to do what i said before in the second post...
gunnyp said:
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
Click to expand...
Click to collapse
You paid for Root Explorer. It doesn't work for you. I'd be bugging the developer since it's clearly not doing the job.
@android-incredible
yes, i looking more and more like i may have to flash my rom backup that i made right after s-off. let's see, since i can get su in adb shell i can get done what i need to so reflashing is not utmost urgent.
i'm not sure it's rootexplorer since i've not seen other posts with similar issue. if the flash of the rom backup does not do it, that may then point to rootexplorer. lets see...
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
TheAngelus said:
Ok so my one x is on stock jb "rooted" now but im having a problem with su only seemingly picking up half of the requests apps send to it. the rootchecker app says the su/superuser dirs are there but it says there is no root.
It was working before the OTA and i still have some apps working fine that need root but others aren't getting allowed and theres no prompt for them, but if i remove the apps that are allowed root and reinstall they get prompted by su for auth or deny as normal.
I cant delete the su files in esfileexplorer as it just gives me an error, i cant select RW on the system dir as it gives root error but i can browse the root dir.
I want to remove su completely and reroot but none of the unroot apps i have found will work (probably because of JB) and i don't know the fastboot commands to remove what i need to remove.
Anyone have any ideas?
Click to expand...
Click to collapse
reroot via recovery mode, have you ever think of that ?
or try to use adb command to delete the old superuser file / replace the old superuser file with the working one
Reboot into recovery (turn on whilst holding Volume - [down])
adb uninstall superuser.apk (or whatever its named on your device)
Download new SuperUser
adb install SuperUserNew.apk (Or whatever the file name of the new one is)
Goodluck
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
TheAngelus said:
Thanks Wilks3y, ive tried the uninstall command but i get this error:
/sbin/sh: pm: not found
The apk in the system/app folder is called superuser.apk
Click to expand...
Click to collapse
what is the name of the superuser that you have downloaded ? (the new one, not the old one at system/app/)
if it's the same name "superuser.apk" then the command is "adb install superuser.apk"
or go to recovery mode and apply flashable zip to replace the superuser files
download this one http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
put in your sdcard
go to recovery
apply this supersu package
more information -> http://forum.xda-developers.com/showthread.php?t=1538053
Yeh thanks its working now after reflashing the cwm superuser.
So I usually use the toolkit to root, in fact I have been for many versions now.
However with the installation of 4.2.1 I haven't been able to root at all. I use the toolkit in the same way but it simply doesn't root the phone.
So today I tried the manual way. I downloaded and installed SDK tools from google navigated to the adb folder and went through the commands. Everything seemed to go okay apart from when I typed adb shell chmod 06755 /system/bin/su. The command window did nothing.
I carried on and typed adb shell chmod 06755 /system/app/Superuser.apk, when it said "bad command" or something similar.
Rebooted the phone, no root... still.
However the Superuser app is there. So:
1) How do I delete the superuser app, bearing in mind it has system permissions. I'd like to simply start again.
2) I don't have CW recovery installed and would prefer not to bother with it if I can.
3) Just to confirm, when I root the phone, does that allow me to delete files in the /system/app folder?
4) Following this guide on rooting manually. Is that all alright?
5) In a couple of sentences, can someone explain rooting to me? From what I understood, rooting simply opens up the phone to allow access to everywhere, where you can copy and delete files, or apks.
6) If 5 is true, when following the rooting guide (4), which command am I actually telling the system to run as root? Is it simply the "root" command?
7) If 6 is true, how come when I re-boot, the phone won't let me delete things from the system/app folder?
Thanks for any help.
1) stop using a toolkit, and no you didnt root the manual way.
2) download this: http://forum.xda-developers.com/showthread.php?t=1538053 - its supersu, superuser is unreliable on 4.2+
3) fastboot flash a recovery
4) flash the supersu.zip
5) done.
Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Don't these superuser apps just manage app permissions? They don't actually enable the root access do they?
Thanks
anotherxdauser said:
Sorry, I should have explained the Su app is SuperSU.
Just gave it another go using a manual toolkit but still no root access. I also now have an su.apk, superuser.apk (SuperSU) and a su file. Need to delete them all.
What do you mean by "fastboot flash a recovery"? You mean flash a new recovery centre like CW?
Thanks
Click to expand...
Click to collapse
follow this: http://forum.xda-developers.com/showthread.php?t=1529058
Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.
anotherxdauser said:
Quick Q...
If I flash a 4.2.1 system.img to the phone, it will replace what exactly?
I'm thinking this might be a way to get rid of the root apps which are protected and allow me to update to 4.2.2, THEN look at manually rooting.
Click to expand...
Click to collapse
it replaces anything in /system... basically the OS.
I did a half ass job in trying to unroot. I deleted the su binary and superuser.apk file but didn't restore the stock ROM or recovery or boot before deleted them. I didn't wipe disk and relock the bootloader either, I just stopped there.
After that, my ROM, Viperx 3.7.7 can still grant apps permission to access root, albeit a little buggy (can't grant for one time but must choose either 10min of access or forever). But after I update to Viper 4.1.1 or CM 12, that ability is lost completely and CWM start asking me if I wanted to fix root upon exit. Right now I can still access root and do things to its file (maybe) but I can't grant any permission, root checker told me my root is not properly installed and like I said above, CWM keep asking me and what I choose (Yes or No) makes no difference.
Anyone got a clue about what I should do? I've already tried to reflash the su binary from the onexroot zip file available on this forum, It didn't do anything.
Updated: I still have my su binary, but I don't have any superuser.apk in system/app
And I can't deleted or do anything to the files in root dir.