[Q] How to build custom ROM include Superuser? - Nexus 7 (2013) Q&A

Hi everyone! I'm researching about build custom ROM with AOSP. Now I get problem about how to include Superuser in the ROM. I want after flash ROM user can be already using. I tried copy su binary and superuser apk from zip file and put into system/xbin/su and system/app folder. After flash ROM superuser appear but it notify Su binary need update... Second way I tried work with the guide from Cyanogenmod but same problem. How can I add superuser into custom ROM by other solution?

What superuser and what binaries are you using
Sent from my LG-D803 using XDA Free mobile app

deadgiveaway said:
What superuser and what binaries are you using
Sent from my LG-D803 using XDA Free mobile app
Click to expand...
Click to collapse
I downloaded it from github Superuser. After extract I get su binary and superuser.apk.

You need to set file permissions on su and Superuser.apk.
Download the flashable installer and check the install script, all the permissions that need to be set are listed in it.

TheManii said:
You need to set file permissions on su and Superuser.apk.
Download the flashable installer and check the install script, all the permissions that need to be set are listed in it.
Click to expand...
Click to collapse
How can I change permission file on the system folder, I tried to use Root Browser and copy su binary to another file but can not change.

hoang.l.nguyen said:
How can I change permission file on the system folder, I tried to use Root Browser and copy su binary to another file but can not change.
Click to expand...
Click to collapse
Help me, plz!!!

Related

SuperUserInstall Issues?( SOLVED)

Did the EVO 4G recent root instructions for 2.3.3
Downloaded Superuser from the link in the instructions and extracted to root of SD card and then installed. All programs requiring root say I have none (I do have S-OFF).
So, deleted the superuser stuff and tried to install it from the market. Says it installed fine but still I have no full root according to titianium,Rom Manager,etc.
Installed ROOT CHECK and ran advanced mode.
Says Superuser apk is installed.
The adb binary is set to default shell user access as a standard non root user
Standard su binary location:Is-I/ system/bin/su:
/system/bin/su: No such file or directory
Standard SU binary location: Is-I/system/xbin/su
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
SU binary not found or not operating properly.
Any assistance out there?
Thanks in advance....
Flash the zip from recovery and it works just fine.
DUH
Having same issue I've tried several times to no avail and the duh comment was a bit juvenile and not at all helping
Sent from my PC36100 using XDA App
Disregard the end of my post wasn't paying attention
Sent from my PC36100 using XDA App

[Q] su permission denied

Hello there,
I just flashed a new ROM (Gingerbread 2.3.7) last night. After signing in the Google account everything is great; the old apps got redownloaded and all. I noticed that there is no apps listed in the superuser. I tried 'su' command in the emulator terminal & I got permission denied.
Luckily all the apps are working in perfect harmony. However, how do I get the superuser permission back? It seems like my device is not rooted. Do I need to root my phone again? Fingers crossed I don't.
Initially, I tried to flash the Ice Cream Sandwich. I tried multiple times but to no avail. I even tried to change the HBOOT (from CM7 > downgrader > Stock HBOOT) but the process failed. I afraid that this might be the cause my root access got lost. Anyone can verify this?
Thanks!
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
beachcomber said:
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
xuminarc said:
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
Click to expand...
Click to collapse
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Alaa said:
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Click to expand...
Click to collapse
Thank you! It works!

[Q] Superuser after OTA

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!

[Q] Su Binary

I used hide my root to hide mu root and when I hid my su binary and tride to restore it will not restore at all. Is there any way I can restore it without factory reset. I still have root as xbmc launcher works perfect.I am on latest build and used custom rom via clockworkmod.
Any body that can help me with this please
Boot into recovery and adb push the su binary back into its location
{ParanoiA} said:
Boot into recovery and adb push the su binary back into its location
Click to expand...
Click to collapse
do you know where I can get the su binary from as tried google but no joy and thanks for your help
alba1978 said:
do you know where I can get the su binary from as tried google but no joy and thanks for your help
Click to expand...
Click to collapse
I am using supersu pro by chainfire and need to install binary for it and wondered if any one can upload a zip of it please.
Here you go....
I also lost su binary using Hide my root app, can you please check if I am going to perform the correct steps to recover it:
download su apk from the post above
reboot in recovery mode: adb reboot recovery
push SuperSU_v2.01.apk to /system/app: adb push SuperSU_v2.01.apk /system/app
reboot
Thanks a lot,
6MHz

[How-To][No Recovery/No Flashfire] Install "Xposed Framework" on Lenovo Vibe K4 Note

Finally i found a method to install Xposed framework on K4 note (I am on S152 ROW version) :victory::cyclops: ​Requisites:-
1. Rooted Phone
2. Busybox
3. Terminal Emulator
4. Xposed zip and installer apk files
5. SuperSu and not Kinguser
Here are the steps:-
1. Download the Zip file from here: [url]https://drive.google.com/file/d/0B7DMgItCtbjhY2hwQlM0dWdVVlE/view?usp=sharing[/URL]
2. Extract it into your phone's internal storage using any of the file manager (Though i prefer ES)
3. Install busybox from the folder and open it. Click on install and let it install the lib files.
4. Now copy the installer.bin file and xposed-sdk22-arm64.zip to root of your internal storage.
5. Now install terminal emulator and open it.
Type su and enter and allow SuperSu permission and then it will show '#' instead of '$'.
6. Now type sh /sdcard/installer.bin and press enter. (Note:- If it fails to install, rename the xposed.zip file in the root folder with xposed-vsdk.zip and installation should go through. Thanks @Ondipuli for this suggestion.)
7. It will ask whether to install Xposed or not. Press 1
Wait for the process to finish and then it will say install is successful.
8. Reboot the Phone. It might seem it is stuck at boot but give it some time(5 mins). Then it will start optimizing the apps and let it finish with that.
Now open xposed app and Voila! Xposed is installed​Enjoy Xposing!!​Credit goes to Razor Beam from youtube...
Hit Thanks if i helped:fingers-crossed::fingers-crossed:..​
Dear Bro, I Installed several times but never ever this installer.bin file ever used. And every time I got succeded. Via Flashfire 0.24
ramisumi said:
Dear Bro, I Installed several times but never ever this installer.bin file ever used. And every time I got succeded. Via Flashfire 0.24
Click to expand...
Click to collapse
Bro, this method is for those who don't want to install flashfire to flash xposed or for those who simply cant get xposed working through Flashfire(I myself was unable to install it through flashfire).
Though flashfire is recommended, sometimes it fails to flash the zip on some devices and that is a known issue. Chainfire is working on the solution.
It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
Ondipuli said:
It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes its true. I also tried but renaming is useful or I have xposed zip already i flashed with flashfire. That also worked with this installer.bin. But as it is provided zip is not installing without renaming or the otherr copy.
Ondipuli said:
It works great. Thanks, but at first installer.bin doesn't detect xposed zip file, as the installer search for a file xposed-v*, then i renamed zip file as xposed-vsdk like that & it installed perfectly.
Sent from my Lenovo A7010a48 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ramisumi said:
Yes its true. I also tried but renaming is useful or I have xposed zip already i flashed with flashfire. That also worked with this installer.bin. But as it is provided zip is not installing without renaming or the otherr copy.
Click to expand...
Click to collapse
Actually, for me it installed without the need of renaming. But still if you guys say so, I will edit the post and mention the need to rename the zip if it's not working by default.
Thanks..
Worked for me after renaming. Thanks.
Virus0044 said:
Worked for me after renaming. Thanks.
Click to expand...
Click to collapse
I am glad it did!
Krishnas096 said:
Finally i found a method to install Xposed framework on K4 note (I am on S152 ROW version) :victory::cyclops: ​Requisites:-
1. Rooted Phone
2. Busybox
3. Terminal Emulator
4. Xposed zip and installer apk files
5. SuperSu and not Kinguser
Here are the steps:-
1. Download the Zip file from here: https://drive.google.com/file/d/0B7DMgItCtbjhY2hwQlM0dWdVVlE/view?usp=sharing
2. Extract it into your phone's internal storage (Though i prefer ES)
3. Install busybox from the folder and open it. Click on install and let it install the lib files.
4. Now copy the installer.bin file and xposed-sdk22-arm64.zip to root of your internal storage.
5. Now install terminal emulator and open it.
Type su and enter and allow SuperSu permission and then it will show '#' instead of '$'.
6. Now type sh /sdcard/installer.bin and press enter. (Note:- If it fails to install, rename the xposed.zip file in the root folder with xposed-vsdk.zip and installation should go through. Thanks @Ondipuli for this suggestion.)
7. It will ask whether to install Xposed or not. Press 1
Wait for the process to finish and then it will say install is successful.
8. Reboot the Phone. It might seem it is stuck at boot but give it some time(5 mins). Then it will start optimizing the apps and let it finish with that.
Now open xda installer app and Voila! Xposed is installed​Enjoy Xposing!!​Credit goes to Razor Beam from youtube...
Hit Thanks if i helped:fingers-crossed::fingers-crossed:..​
Click to expand...
Click to collapse
[email protected]:/ $ su
[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # '$'.
k_shell/10161:17229: $.: not found
127|[email protected]:/ #
Plz help how to install
Help
executed installer.bin then pressed 1 but after that it shows cant create folder
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Are you trying this method on Lollipop or Marshmallow. If so then on what version(Build no).
Sorry for the late reply. I am a student and i am not able to come online on xda regularly.
Permission ?
Hi,
I try this method, follow every steps, but it tell me this:
mount: Operation not permitted
/sdcard/installer.bin[25]: can't create /test.txt: read-only file system
Error: Busybox is not installed
I'm rooted under SuperSu, Xposed installer is installed, same as Busybox (by install the lib file too)
Can i get some help please.
Thnx BUT...
OK the first time I tried it did not work so I renamed the xposed package to xposed-vsdk.zip but it did not install the zip so xposed did not recognize or find it. So I when online and downloaded the latest sdk22 (sdk22=lollipop). I renamed it and it worked so I think you should update the master zip with the latest xposed zip.
BTW This also this works on Kindle Fire HD 8 cuz FlashFire doesn't support it.
shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Your command is missing " "(space)
The correction command is
sh /sdcard/installer.bin
Enjoy
chitranjn_k said:
[email protected]:/ $ su
[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # sh /sdcard1/installer.bin
sh: /sdcard1/installer.bin: No such file or directory
127|[email protected]:/ # '$'.
k_shell/10161:17229: $.: not found
127|[email protected]:/ #
Plz help how to install
Click to expand...
Click to collapse
may be the installer.bin is in sdcard, not sdcard1
can i install on any device using this method actually I have mobile which has android 5.1.1 and arm 32bit system can i install frame work using this technique
Rename the file txt at the place of bin.then try
shanky_x said:
PLEASE HELP**
In terminal window it is saying :
k_shell/10259:12535: sh/sdcard/installer.bin: not found
i did rename xposed-sdk22-arm64.zip into xposed-vsdk.zip but it still saying failed . what should i do now ?
Click to expand...
Click to collapse
Ans:-Give space after sh. (sh /sdcard/installer.bin)
atif ahmad said:
can i install on any device using this method actually I have mobile which has android 5.1.1 and arm 32bit system can i install frame work using this technique
Click to expand...
Click to collapse
No. You cannot. The script and the xposed apk inside the zip file are for arm64 so it wont be possible. Don't try it and brick your device.

Categories

Resources