Related
I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?
Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.
AzN1337c0d3r said:
I am getting a permission denied when I try to run "adb remount".
I am running the netarchy rooted ROM.
I am Unrevoked3 and Unrevoked Forever.
So my NAND is unlocked and I am rooted. Why does it still say Permission Denied?
Click to expand...
Click to collapse
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?
xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
just out of curiosity, what does your name mean? The last part looks like coder but what is azn 1337?
Click to expand...
Click to collapse
My leetspeak is a little rusty, but I think 1337 is 'leet' as in "elite"....and I'm guessing the young man is of Asian descent.
drmacinyasha said:
Install the latest version of SuperUser (look in the Market). When you try to do adb remount, or su in adb shell, look at your phone. There'll be a popup asking for permission.
Click to expand...
Click to collapse
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
xHausx said:
In Netarchy's kernel thread he mentions something about unrevoked 3 not giving full access to root, not sure if he was just referring to the NAND or what but that may have something to do with it. If all else fails you can always go back and try rooting it manually without unrevoked.
Click to expand...
Click to collapse
I thought Unrevoked Forever took care of the NAND not getting unlocked. It says on their website that it unlocks NAND.
Anyways, the whole reason why I went with unrevoked is because I could keep PRI 1.40_003. I had lost it when I manually rooted and had to go back to stock and then unrevoked to get it back.
I am having the same issues. I am unrevoked3 and unrevoked forever. It is always telling me either device not found or remote not allowed. As far as I can tell all of my drivers are up to date, I am fully rooted with nand unlocked, and the problem didn't start until just recently. Everything worked fine before. I will try to download an updated Superuser app and give some feedback on that when I get off work.
On a side note, does Busybox have anything to do with this sort of matter?
Sent from my regaw rooted EVO.
My problem appears to be a software/OS issue. When I wipe everything and install a stock 2.2 system, I am able to "adb remount".
My guess is that something is continually accessing the /system partition and holding a lock on it.
Does anyone know how I might check for this?
Just to clarify: yes, Unrevoked Forever does unlock NAND.
The issue must be with the rom? Try a different superuser/su...
AzN1337c0d3r said:
Installed latest version of SuperUser.
"adb remount" still saying permission denied.
"adb shell su" did ask me for permission however.
Click to expand...
Click to collapse
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Thank you so much for the info. I have been searching high and low for a straight answer on this. Even though its not fixed I am much happier knowing what the issue is. Again thank you.
When I ran your test I got a $ which as you said means it is a conflict with my current ROM. So, if I flash a different ROM than I should be squared away yes? Again many thanks.
Sent from my regaw rooted EVO.
drmacinyasha said:
Mmmkay, your problem is either:
1) NAND is locked still (unlikely).
2) ROM is not set up to have shells be root by default (likely).
Click to expand...
Click to collapse
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
To test, open adb shell. If you see a $, then it's #2. If you see a #, then it's probably #1. To be extra sure, if you're seeing a $, type "su" then enter, approve the su request, then do "mount -o remount,rw /system", followed by "mkdir /system/testymctest". If you get a permission error, then your NAND is not unlocked.
Click to expand...
Click to collapse
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.
AzN1337c0d3r said:
It says clearly SHIP S-OFF on my bootloader. This is the way to tell if you are Unrevoked Forever.
Everything is as you described. It is #2. and when I do the "mount -o remount,rw /system" I get permission denied.
I'm not sure how Root Explorer works, but I assume it obtains root permissions and then run the mount command as you have described above.
My NAND is unlocked, I can get to it via Root Explorer and mount it as r/w and then access it through shell. However, if I don't use Root Explorer and try the command through the shell, it doesn't work.
It seems almost like I am not getting SU permissions even though my shell changes to a #.
Click to expand...
Click to collapse
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.
drmacinyasha said:
Hrm... Are you sure you have the latest version of ChrisDD's SuperUser from the Market, and then opened up its settings tab to make sure there's the latest su executable? That's the only thing I can think of.
Click to expand...
Click to collapse
Yup I did exactly that.
It's some app I installed that is doing this. I nandroided my current config, reflashed the netarchy 2.2 rooted rom and was able to get access.
Then when I installed all the rest of my apps, I suddenly lost access.
Tommorow I will start fresh again and try apps one by one.
now i got # what else
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...
Forgot to add this to the title: [BOOTLOADER LOCKED]
Hello Fellow XDA'ers,
Using a slightly formatted zergRush (modified by Ch4lky, part of the revolutionary team) i was able to get ADB root!!
Now how do i get from adb to the phone rooted?
Thank you, in advanced!
Note: zergRush (from Ch4lky) is attached.
paxChristos said:
Forgot to add this to the title: [BOOTLOADER LOCKED]
Hello Fellow XDA'ers,
Using a slightly formatted zergRush (modified by Ch4lky, part of the revolutionary team) i was able to get ADB root!!
Now how do i get from adb to the phone rooted?
Thank you, in advanced!
Note: zergRush (from Ch4lky) is attached.
Click to expand...
Click to collapse
I'll test this out later. Some other rooting tools might work with the adb root like SuperOneClick or UniversalAndroot
CrimsonSentinel13 said:
I'll test this out later. Some other rooting tools might work with the adb root like SuperOneClick or UniversalAndroot
Click to expand...
Click to collapse
Tried SuperOneClick, gingerbreak and universalandroot
UniversalAndroot:
Developer of that one stopped updating with froyo, I got nowhere (1.6.2 beta 5) if you have a better version, go for it
Gingerbreak: I ran outta patience with this one and just killed it after 5ish minuts of running it
SuperOneClick: Claims to get root (installed busybox, and superuser) when I reboot I loose root.
Tried chmodding su, but that didn't work out
paxChristos said:
SuperOneClick: Claims to get root (installed busybox, and superuser) when I reboot I loose root.
Tried chmodding su, but that didn't work out
Click to expand...
Click to collapse
I know that SOC has 3 ways to root. Doesn't shell root stick after a reboot with a script that's installed?
Edit: Nevermind... I realized that zergRush does that.
Just tried SOC again, this time using root checker, it says i'm rooted, but rootchecker says otherwise...
So far we're at ADB rooted, so we can remount as whatever we want, but past that, what can we do?
How does all of this work? i wouldn't mind having ADB root, at least its something better then no-root
---------- Post added at 04:51 PM ---------- Previous post was at 04:33 PM ----------
Wouldn't you just push the "su" commands to the correct folder to gain root?
Tried that, no dice
My guess is that it's not changing the /system folder to rw (read write) on boot instead of the default ro (read only)
Sent from my R800x using XDA App
If you change how the OS mounts at boot through fstab or the equivalent in Android, it might work.
Well couldn't you just have it like a tethered root? like every time you restart your phone just set the /system folder to rw? I really don't know because i'm still learning ADB.
Db0y505 said:
Well couldn't you just have it like a tethered root? like every time you restart your phone just set the /system folder to rw? I really don't know because i'm still learning ADB.
Click to expand...
Click to collapse
It's a horrible, horrible loop, to change the /system to rw, you need to have root. To get root you need a way to change /system to rw...
Right now we have a temporary root that only works in adb, but goes away once the phone is rebooted...
I have perma-root now.
remounted /system [adb remount]
pushed su to /system/bin & /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
installed SuperUser through adb
installed BusyBox (if it doesn't show up) via a Market app
Ran SuperUser
installed Insecure ADB via APK & then ran it on phone, system reboots
Reboot has root & rooted insecure adb
All apps that need root have no issue. I'm looking into getting sudo added to the mix, too.
CrimsonSentinel13 said:
I have perma-root now.
remounted /system [adb remount]
pushed su to /system/bin & /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
installed SuperUser through adb
installed BusyBox (if it doesn't show up) via a Market app
Ran SuperUser
installed Insecure ADB via APK & then ran it on phone, system reboots
Reboot has root & rooted insecure adb
All apps that need root have no issue. I'm looking into getting sudo added to the mix, too.
Click to expand...
Click to collapse
you good sir, are my hero!
Do you want to post how you got this in The developers forum?
You are a hero indeed, but could you just make the instructions slightly more "noob" oriented?
You sir are awesome!
---------- Post added at 06:25 PM ---------- Previous post was at 06:04 PM ----------
Ok i just did this and i have root! Thank you so much!
Cl8rs said:
You are a hero indeed, but could you just make the instructions slightly more "noob" oriented?
Click to expand...
Click to collapse
I'll be within on it once I get home, right now I'm in class until 9
Sent from my R800x using XDA App
paxChristos said:
I'll be within on it once I get home, right now I'm in class until 9
Sent from my R800x using XDA App
Click to expand...
Click to collapse
You're the best bro!
CrimsonSentinel13 said:
I have perma-root now.
remounted /system [adb remount]
pushed su to /system/bin & /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
installed SuperUser through adb
installed BusyBox (if it doesn't show up) via a Market app
Ran SuperUser
installed Insecure ADB via APK & then ran it on phone, system reboots
Reboot has root & rooted insecure adb
All apps that need root have no issue. I'm looking into getting sudo added to the mix, too.
Click to expand...
Click to collapse
If you can already use adb remount, you dont need to install insecure adb because you already have it
I'll post my steps in an hour or so w/o the insecure adb step, too, in the dev section. If paxChristos gets around to it before me, I would appreciate the recognition.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=1312859
CrimsonSentinel13 said:
I'll post my steps in an hour or so w/o the insecure adb step, too, in the dev section. If paxChristos gets around to it before me, I would appreciate the recognition.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=1312859
Click to expand...
Click to collapse
No worries man, it's all you.
I need to do some "housekeeping" to get my phone to work with it,
Congrats on finding the hole, and thank you
This is AWESOME! now all we need is a work around like the DX to get some Clockwork mod recovery, or a way to crack the BL.
Never the less, i wanna say thanks to all the devs that did this, you guys rock
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
So you can't use boot unlocker so on play store?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
skyes113 said:
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Maybe you need to fix permissions.
Did you have ROM Manager by any chance with root access granted? If so you could flash CWM from there, and then apply the latest SuperSU zip from CWM.
skyes113 said:
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Use ES File Explorer and change the permissions on /system/bin/su (or /system/xbin/su) to 6755 and you will be all set.
efrant said:
Use ES File Explorer and change the permissions on /system/bin/su (or /system/xbin/su) to 6755 and you will be all set.
Click to expand...
Click to collapse
I see that the Permission of the SU from ES File Explorer is rwx r-x r-x . I believe this is already the correct permission?
I'm thinking if it's possible for me the get the latest binary for Superuser and replace the SU file using the file explorer. Will this work?
Unfortunately I don't have rom manager as well.
skyes113 said:
I see that the Permission of the SU from ES File Explorer is rwx r-x r-x . I believe this is already the correct permission?
I'm thinking if it's possible for me the get the latest binary for Superuser and replace the SU file using the file explorer. Will this work?
Unfortunately I don't have rom manager as well.
Click to expand...
Click to collapse
Those are not the correct permissions. The setuid bit needs to be set as well. What you posted is 0755, not 06755.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Those are not the correct permissions. The setuid bit needs to be set as well. What you posted is 0755, not 06755.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
ES File explorer doesn't seems to be able to allow me to set the setuid bit.
I guess I just have to figure out how to use adb to do that.
skyes113 said:
ES File explorer doesn't seems to be able to allow me to set the setuid bit.
I guess I just have to figure out how to use adb to do that.
Click to expand...
Click to collapse
I just checked and you're right. (i only ever use root explorer.)
In a terminal window:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
chmod 06755 /system/xbin/su
I would also symlink it to bin:
ln -s /system/bin/su /system/xbin/su
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
I just checked and you're right. (i only ever use root explorer.)
In a terminal window:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
chmod 06755 /system/xbin/su
I would also symlink it to bin:
ln -s /system/bin/su /system/xbin/su
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I managed to do the above. However still no luck with updating SuperUser binary and still encounter the error "Gaining root access..... Failed"
I believe after doing the above I should get permissions (-rwsr-xr-x) but i'm seeing the permission as -rwsr-sr-x
seem like something is wrong?
skyes113 said:
I managed to do the above. However still no luck with updating SuperUser binary and still encounter the error "Gaining root access..... Failed"
I believe after doing the above I should get permissions (-rwsr-xr-x) but i'm seeing the permission as -rwsr-sr-x
seem like something is wrong?
Click to expand...
Click to collapse
Strange. I have no idea what the problem would be then.
What I would do is boot up CWM, and re-flash an su package.
The permissions are fine: -rwsr-xr-x = 04755 and -rwsr-sr-x = 06755. Both will do the same thing.
Also I see nothing in the OTA package that would relock your bootloader. You're sure that's exactly what happened? If it did, maybe someone here could pinpoint the component of the OTA package responsible for this?
Sent from my Galaxy Nexus using Tapatalk 2
Looks to be a problem on su.
I download the latest binary and replace it using adb + busybox and now it works fine.
Thanks!
Hi
1. Install NewKingRoot
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
2.Install Busybox
https://play.google.com/store/apps/details?id=stericson.busybox
3. Install Terminal Emulator for Android
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl
4.Install Mount system rw
https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl
5. Install Replace_Kinguser_with_SuperSU-v2.4
http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip
-Install KingRoot
-Install Busybox
-Instanll Mount system and open, click mount /system RW
-Open Replace_Kinguser_with_SuperSU-v2.4 Extracted folder "mrw" to the internal storage of your device
-Open Terminal emulator and write code.
su
sh storage/emulated/0/mrw/root.sh
-open supersu manually.
-Update su binary normal, then manually reboot.
Your devices root
Test: 30.1.A.133
You actually need not to install SuperSU after installing Kingroot (not KingoRoot), there is a built-in one, but he Kingroot one have no option for modifying the apps.
You could just simply click "get now" to root your phon.
AlgebraTheBard
owned devices:
Sony Xperia M5 dual (recent)
ZTE Nubia Z7 mini (backup)
Motorola RAZR XT910 custom
He wants some applications SuperSu. I shared information purposes Thanks, clerical error
algebrathebard said:
You actually need not to install SuperSU after installing Kingroot (not KingoRoot), there is a built-in one, but he Kingroot one have no option for modifying the apps.
You could just simply click "get now" to root your phon.
AlgebraTheBard
owned devices:
Sony Xperia M5 dual (recent)
ZTE Nubia Z7 mini (backup)
Motorola RAZR XT910 custom
Click to expand...
Click to collapse
If you root with dodgy kingroot you must change kinguser to supersu as kinguser does not give the same root access permissions as supersu does and will cause problems...
Good to know, thanks to Aidy Lucas.
AlgebraTheBard
owned devices:
Sony Xperia M5 dual (recent)
ZTE Nubia Z7 mini (backup)
Motorola RAZR XT910 custom
[email protected] said:
If you root with dodgy kingroot you must change kinguser to supersu as kinguser does not give the same root access permissions as supersu does and will cause problems...
Click to expand...
Click to collapse
@[email protected]
When you say kingroot is dodgy, can you go straight to SuperSU?
I would love that without unlocking my bootloader if possible.
icstm said:
@[email protected]
When you say kingroot is dodgy, can you go straight to SuperSU?
I would love that without unlocking my bootloader if possible.
Click to expand...
Click to collapse
There's a zip you flash via recovery probably other ways too, it removes all the kingroot/kinguser files and replaces them with supersu for proper root access. Really don't see the point in buying a Xperia device for the camera ect then unlocking the Bootloader and losing it yes I know there's a workaround for the z ranges but bet it's not as good as the real drm keys
Does this root the Sony Xperia M5 (E5653)?
Dreamer62 said:
Hi
1. Install NewKingRoot
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
2.Install Busybox
https://play.google.com/store/apps/details?id=stericson.busybox
3. Install Terminal Emulator for Android
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl
4.Install Mount system rw
https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl
5. Install Replace_Kinguser_with_SuperSU-v2.4
http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip
-Install KingRoot
-Install Busybox
-Instanll Mount system and open, click mount /system RW
-Open Replace_Kinguser_with_SuperSU-v2.4 Extracted folder "mrw" to the internal storage of your device
-Open Terminal emulator and write code.
su
sh storage/emulated/0/mrw/root.sh
-open supersu manually.
-Update su binary normal, then manually reboot.
Your devices root
Click to expand...
Click to collapse
Can anyone advise whether this works on the SONY M5 (E5653), as sold here in Thailand?
Thanks!
Max
[email protected] said:
There's a zip you flash via recovery probably other ways too, it removes all the kingroot/kinguser files and replaces them with supersu for proper root access. Really don't see the point in buying a Xperia device for the camera ect then unlocking the Bootloader and losing it yes I know there's a workaround for the z ranges but bet it's not as good as the real drm keys
Click to expand...
Click to collapse
@[email protected]
The problem is that the only way I know if via recovery and there is no custom recovery yet for this phone... I was not planning on unlocking the bootloader, but I do want a rooted phone.
I can confirm this method.
Works like a charm.
Not too difficult to do, all though I do like the "one click" magic
Hello, and thank you for the guide. I have some questions that I would like someone to address please.
1. After installing KingRoot, do I have to run the app and go through the rooting process? Or i just install it and follow the other steps?
2. mount /system RW says 'your device may not be rooted or is not compatible'
3. You say '-Open Terminal emulator and write code.
su
sh storage/emulated/0/mrw/root.sh'. However, when I type su, it says SU not found.
Thank you in advance all.
You didn't root your phone.When you install KingRoot you have to open the app and click on Root,you may have to try several times until you are abel too root it,just keep trying for me it took three times to make it work,for some up to 7 times,but when it's rooted it will show you the message that your phone is rooted and then you can follow the rest guide...
Sent from my E5603 using XDA-Developers mobile app
Hello, thank you very much for your reply. I did as you said and now I have SuperSU and kinguser is no longer there. I have one more question, if you dont mind. Is it OK if I remove Purify and SuperBattery now?
PS: I got a bit anxious while installing SuperSU, as it asked to delete other superuser apps, i said OK, and it stuck at 'supersu uninstalling'. However, I restarted the phone and everything was OK.
pren22 said:
You didn't root your phone.When you install KingRoot you have to open the app and click on Root,you may have to try several times until you are abel too root it,just keep trying for me it took three times to make it work,for some up to 7 times,but when it's rooted it will show you the message that your phone is rooted and then you can follow the rest guide...
Click to expand...
Click to collapse
omrtpsycho said:
Hello, thank you very much for your reply. I did as you said and now I have SuperSU and kinguser is no longer there. I have one more question, if you dont mind. Is it OK if I remove Purify and SuperBattery now?
PS: I got a bit anxious while installing SuperSU, as it asked to delete other superuser apps, i said OK, and it stuck at 'supersu uninstalling'. However, I restarted the phone and everything was OK.
Click to expand...
Click to collapse
Yes you can remove those apps...
Sent from my E5603 using XDA-Developers mobile app
Are the steps applicable to M5 Dual E5663 build 30.1.B.1.55 ?
Help
Dreamer62 said:
Hi
1. Install NewKingRoot
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
2.Install Busybox
https://play.google.com/store/apps/details?id=stericson.busybox
3. Install Terminal Emulator for Android
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl
4.Install Mount system rw
https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl
5. Install Replace_Kinguser_with_SuperSU-v2.4
http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip
-Install KingRoot
-Install Busybox
-Instanll Mount system and open, click mount /system RW
-Open Replace_Kinguser_with_SuperSU-v2.4 Extracted folder "mrw" to the internal storage of your device
-Open Terminal emulator and write code.
su
sh storage/emulated/0/mrw/root.sh
-open supersu manually.
-Update su binary normal, then manually reboot.
Your devices root
Test: 30.1.A.133
Click to expand...
Click to collapse
Support Firmware
• 30.1.A.1.55 ?
Hello but can anyone confirm if this method is just for root or also onlocks bootloader? I just want root access and don't want to lose my DRM keys!
Thank you
Works also on 30.1.A.1.55
Osorio_117 said:
Support Firmware
• 30.1.A.1.55 ?
Click to expand...
Click to collapse
Yes, just did it and worked on first try.
confirming its method to be root has been a success and should be noted that when executing commands from the internal memory of the folder mrw also be done through the external memory
Code:
su
sh sdcard1/mrw/root.sh
screenshot :fingers-crossed:
Alzatan said:
Hello but can anyone confirm if this method is just for root or also onlocks bootloader? I just want root access and don't want to lose my DRM keys!
Thank you
Click to expand...
Click to collapse
It works and you wont lose your DRM keys!!!