[Q] Superuser update - Android Q&A, Help & Troubleshooting

Simple question...
I'm developing a custom ROM and I got the idea to update the SuperUser apk and the binaries so I've downloaded the .zip and got the su binary and the app, but it has other files...
Should I replace all the files that has in that .zip to my custom ROM?
Thanks in advance and happy new year!

---

Read the update-script and do as it says...
Sent from my Nexus 4 using Tapatalk

---

SMillerNL said:
Read the update-script and do as it says...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying, but how I can do the permissions and the symlink part?
Happy new year!

---

If you're doing it in dsixda's kitchen then it will do it for you, otherwise you have to do it in your own update-script

---

XxPixX said:
If you're doing it in dsixda's kitchen then it will do it for you, otherwise you have to do it in your own update-script
Click to expand...
Click to collapse
Is there a way to do without it?
Trying to not using Kitchen at all.

---

manudo said:
Is there a way to do without it?
Trying to not using Kitchen at all.
Click to expand...
Click to collapse
To add the set permissions part and symlinks park you can use the following commands in your updater-script (These references here and here will also be helpful):
To set permissions:
Code:
set_perm(uid, gid, mode, "filepath1", "filepath2");
Example:
Code:
set_perm(0, 0, 06755, "/system/xbin/su");
To set symlinks:
Code:
symlink("filepath", "filepathyouwanttolinkto");
Example:
Code:
symlink("/system/xbin/su", "/system/bin/su");
Let me know if you still have questions I'll be happy to answer them.

---

shimp208 said:
To add the set permissions part and symlinks park you can use the following commands in your updater-script (These references here and here will also be helpful):
To set permissions:
Code:
set_perm(uid, gid, mode, "filepath1", "filepath2");
Example:
Code:
set_perm(0, 0, 06755, "/system/xbin/su");
To set symlinks:
Code:
symlink("filepath", "filepathyouwanttolinkto");
Example:
Code:
symlink("/system/xbin/su", "/system/bin/su");
Let me know if you still have questions I'll be happy to answer them.
Click to expand...
Click to collapse
Thanks, that commands I have to enter them in Linux Terminal?

---

manudo said:
Thanks, that commands I have to enter them in Linux Terminal?
Click to expand...
Click to collapse
These are the commands that you add to the updater-script file found in your custom ROM's flashable .zip file. The commands are not entered in terminal. If you need me to explain this further just let me know.

---

shimp208 said:
These are the commands that you add to the updater-script file found in your custom ROM's flashable .zip file. The commands are not entered in terminal. If you need me to explain this further just let me know.
Click to expand...
Click to collapse
Ok, so, let me get this straight...
When I download a update package it comes with an updater script with few commands written in it.
All I have to do is copy and paste every command to the updater-script file in my custom ROM folder, for any change I make to the ROM.

---

manudo said:
Ok, so, let me get this straight...
When I download a update package it comes with an updater script with few commands written in it.
All I have to do is copy and paste every command to the updater-script file in my custom ROM folder, for any change I make to the ROM.
Click to expand...
Click to collapse
This is correct, plus any resources included in the .zip package. It's essential that you preserve the directory structure of the .zip package in your custom ROM .zip package in order for the updater-script to execute properly. For example if the updater package .zip includes a /system folder your custom ROM .zip package must include the /system folder with the resources from the updater .zip package as well as whatever resources your custom ROM needs. Let me know if you need me to clarify or explain this further.

---

shimp208 said:
This is correct, plus any resources included in the .zip package. It's essential that you preserve the directory structure of the .zip package in your custom ROM .zip package in order for the updater-script to execute properly. For example if the updater package .zip includes a /system folder your custom ROM .zip package must include the /system folder with the resources from the updater .zip package as well as whatever resources your custom ROM needs. Let me know if you need me to clarify or explain this further.
Click to expand...
Click to collapse
Yeah, I have to place the other files in the directory as the update zip is, example:
update.zip/system/app/
rom/system/app

---

manudo said:
Yeah, I have to place the other files in the directory as the update zip is, example:
update.zip/system/app/
rom/system/app
Click to expand...
Click to collapse
That is correct, you got it! To answer the question in your signature I would stay away from using a name like Splenda while it is a clever idea, but it's best to avoid trademarks when branding your custom ROM.

---

shimp208 said:
That is correct, you got it! To answer the question in your signature I would stay away from using a name like Splenda while it is a clever idea, but it's best to avoid trademarks when branding your custom ROM.
Click to expand...
Click to collapse
Thank you for your help and your opinion, I'll build it tomorrow.
Are you kidding me? I can have issues with trademarks if I name a custom ROM like that?
Ha, the worst case scenario is that I'm in a court because of naming Splenda a custom ROM. Doesn't seem possible.

---

manudo said:
Thank you for your help and your opinion, I'll build it tomorrow.
Are you kidding me? I can have issues with trademarks if I name a custom ROM like that?
Ha, the worst case scenario is that I'm in a court because of naming Splenda a custom ROM. Doesn't seem possible.
Click to expand...
Click to collapse
While I doubt the Splenda company would personally come hunting through the XDA forums to come after you it's still proper practice to not use trademarked names or copyright trademarks in your projects. Besides you never know what kind of popularity and exposure your ROM may get. Looking at your modified signature if you named your ROM "Splenda ROM" that would be questionable. However if you named it Jelly Bean sweetened with Splenda then I believe that falls under fair use context (Full disclosure: I am not a lawyer and as such any opinion of mine that reflects legal matters should not be taken a official legal advice).

---

shimp208 said:
While I doubt the Splenda company would personally come hunting through the XDA forums to come after you it's still proper practice to not use trademarked names or copyright trademarks in your projects. Besides you never know what kind of popularity and exposure your ROM may get. Looking at your modified signature if you named your ROM "Splenda ROM" that would be questionable. However if you named it Jelly Bean sweetened with Splenda then I believe that falls under fair use context (Full disclosure: I am not a lawyer and as such any opinion of mine that reflects legal matters should not be taken a official legal advice).
Click to expand...
Click to collapse
Splenda ROM sounds great, but it's basically the same thing.
Chill dude, I'm not taking your advice.
Gotta email Splenda company, I hope they don't take it as a joke.
Sent from my XT1034 using XDA Premium 4 mobile app

---

SU Binary
I am using ODIN Rom and when I run SuperSU I get msg " The SU Binary needs to be updated. Continue?" I do so and get..
a question to use "Normal" or TWRP/CWM. I am using PHILZ. It says the SuperSU will attempt to reboot your device into TWRP or CWM. and it does nothing. So I then restart and select normal, it tell me the install failed ande reboot and try again.
Nothing seems to work, what am i missing?
Israel

---

Download the latest SuperUser.zip and flash it trough recovery by yourself.
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Gesendet von meinem GT-N8010 mit Tapatalk 2