Database Develop

Why the root message isn't showed like Hero&Others ?

All others rooted phones have a message showed when an application asks root, why don't we have this on Tattoo ?

On Tattoo root permissions are always enabled

Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/

JoOoSs said:
Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/
Click to expand...
Click to collapse
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.

I'm on stock ROM, this is the problem i think!
Anybody has SetCPU ?

The problem with this is that every application can obtain root without our knowledge.
It is a serious security flaw.

Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.

Netbuster said:
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.
Click to expand...
Click to collapse
Because that rom you've flashed contains custom boot.img by mainfram3 that gives to you root at startup and loads tattoo-hack.ko (partition r/w always mounted)

Coburn64 said:
Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.
Click to expand...
Click to collapse
Actually i wasn't having viruses in mind. More like keyloggers and such. SU prompt wasn't invented for no reason...

I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.

mainfram3 said:
I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.
Click to expand...
Click to collapse
Exactly my point.

MoDaCo Custom ROM 1 includes Superuser apk for root access.
P

Anyone know how to fix Superuser Permissions manually?
I have Tattoo with rooted boot.img (mainfram3)
I pushed su into /system/bin/
Made chmod 4577 /system/bin/su
Pushed superuser.apk from Modaco Rom to /system/app/
Restart sure...
SuperUser Permissions can be executed (list is clear)
But any app doesn't send request to Superuser Permissions.
What i could forget?

Finally, I solved it partially.
Sure, i have rooted boot.img
I extracted from Modaco Custom ROM for Tattoo:
su
Superuser.apk
copied su to: /system/bin/su
copied Superuser.apk to: /system/app
run in terminal: chmod 4577 /system/bin/su
restarted and everything works fine now... Superuser Permissions shows all root-requests, Titanium Backup works, other root-things works too
But i notice, that su-binary from Modaco ROM is about 34-36 kb, but
su-binary from guide of getting root is about 80-85 kb.
1-2 months ago we faced with difference in size of su. We choosed bigger su in case, what it can run "flash_image", smaller su can't run.
But maybe it fixed already? I did not test it yet.

Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.

lukic said:
Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.
Click to expand...
Click to collapse
What exactly wrote TB?
Did you download busybox via TB?

I don't remember exactly.
It did ask me to download busybox and I did that, but still it didn't work.

Root Technical Details

Hi, I've been searching for technical details of how root is actually obtained on the Android system. Specifically, I'm interesting in the Nexus One, but I'm curious about any methods that are available.
After reading the adb documentation among others, I've come to the belief that at least on the N1 it's as simple as remounting system as root and changing the permissions of su followed by installing busybox. After that the superuser application is installed, and it updates su with it's own version.
(This is only for updating the application on an already rooted system)
Superuser appears to grant root privileges to itself then overwrites su with it's own variation that uses its database for permissions, and calls the app with:
Code:
sprintf(sysCmd, "am start -a android.intent.action.MAIN -n com.koushikdutta.superuser/com.koushikdutta.superuser.SuperuserRequestActivity --ei uid %d --ei pid %d > /dev/null", g_puid, ppid);
I'm curious how cyanogen handles it without having the user install busybox, etc. before flashing his mod. I would think the Android system would only allow signed updates, but I have a feeling that the custom recovery image bypasses that.
If someone could just link me to a forum link/blog/etc. (if they exist) or give me some advice on things to search for, that would be great.
I'm just now getting into Android kernel development, and would love to know everything I can about it. I've been way to busy with a research project at school, but it's pretty much over at this point. I plan on becoming much more involved here especially with some programming some ideas I have for improvements to both the kernel and Google's applications.

meinhimmel said:
I'm curious how cyanogen handles it without having the user install busybox, etc. before flashing his mod. I would think the Android system would only allow signed updates, but I have a feeling that the custom recovery image bypasses that.
If someone could just link me to a forum link/blog/etc. (if they exist) or give me some advice on things to search for, that would be great.
.
Click to expand...
Click to collapse
bingo. upon unlocking the bootloader, you are able to flash a custom recovery which does not require google keys and you are able to install custom roms. the roms usually have busybox and the other applications built in. custom recovery also has all the binaries require for flashing roms.
a good site would be platform.android.com (something like that) for developing roms/editing kernel. you can also check the "android development" on the xda main forum homepage, there are a couple of stickies there worth reading

Adaway problems on Nexus 6 marshmallow

I've researched and tried every method to get AdAway to work. I uninstalled some system apps which allowed me to install it but I cannot get past that because of the S-off warning screen.
I am rooted and bootloader is unlocked. Ive attatched a screenshot of my kernel etc

Do you have a folder called init.d in system/etc?

I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Just FYI, this is a development area. You will have more luck posting in the Q&A section.

You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.

miguelito18 said:
Do you have a folder called init.d in system/etc?
Click to expand...
Click to collapse
No i do not

Mike02z said:
I have installed Adaway on at least 6 different Marshmellow ROM's with no issue.
Switch ROM and Kernels and see what happens.
Click to expand...
Click to collapse
Do you have a suggestion on a kernel? And id like to stay stock on the ROM if possible
Mike02z said:
Just FYI, this is a development area. You will have more luck posting in the Q&A section.
Click to expand...
Click to collapse
Ya sorry, i was tryng to post it quick on my phone and didnt look at all the options as to where the best place to post would be

Khizar said:
You seem to be using system less root, that's probably the issue. In the adaway thread there is a zip that must be flashed if you're using system less root.
Also questions belong in the Q&A section not dev section. I've reported the thread, a mod should move it but just letting you know for next time.
Click to expand...
Click to collapse
What is system less root if i may ask? and ill look for that zip you mentioned
*update* installed that zip. attempted to install and get the same error about s-off

@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?

gee2012 said:
@trbomp5 Adaway working flawless on systemless (2.66) rooted stock rom, @ OP do you have busybox installed?
Quote: *update* installed that zip. attempted to install and get the same error about s-off
What do you mean with s-off?
Click to expand...
Click to collapse
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message

trbomp5 said:
Yes busybox is installed.
and if you look at the op youll see the screenshots where i get the s-off error message
Click to expand...
Click to collapse
Symlink to /data/data/hosts in settings.

gee2012 said:
Symlink to /data/data/hosts in settings.
Click to expand...
Click to collapse
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again

trbomp5 said:
yes.
its seems fine till it says symlink missing. then when i click yes to create i get the symlink creation failed. like in the screenshot.
just tried it again
Click to expand...
Click to collapse
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?

gee2012 said:
Clear all Adaway data in /settings/apps/ and try again. It should work fine as it does for me. What rom/kernel/recovery are you running?
Click to expand...
Click to collapse
cleared data and tried again same results.
stock rom, unlocked bootloader, kernel is 3.10.40-ElementalX-N6-3.00, twrp 2.8.7.1

Universal init.d install it from play store and follow instructions

miguelito18 said:
Universal init.d install it from play store and follow instructions
Click to expand...
Click to collapse
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"

trbomp5 said:
downloaded it, installed fine. Opened it, granted it SU and then it says "unfortunately, Universal init.d has stopped"
Click to expand...
Click to collapse
I don't have an init.d folder as I run the stock kernel. There must be another problem.

I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts

gee2012 said:
I don't have an init.d folder as I run the stock kernel. There must be another problem.
Click to expand...
Click to collapse
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/

Yasharkhan said:
I was facing the same problem, for every one trying to get adaway to work on android 6.0.1, follow these steps
Boot to TWRP recovery -> Mount system
adb shell
cd system
cd etc
rm hosts
ln -s /data/data/hosts /system/etc/hosts
In AdAway -> Settings -> hosts file to use is /data/data/hosts
Click to expand...
Click to collapse
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
any way i can get you to step by step these with all i need to do?

trbomp5 said:
ill find the guide i used to root and link it here to see if anyone see's a problem there
http://nexus5.wonderhowto.com/how-to/root-nexus-device-running-android-6-0-marshmallow-0165131/
Click to expand...
Click to collapse
Look in the stickies thread in general for how to root.
Usually what i do is:
Flash or boot into TWRP
Flash superuserSU
Install BusyBox
That's it as i use the stock rom, kernel and recovery. I just need root.
---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------
trbomp5 said:
just to clearify, those steps are all done in recovery? And im not the best at ADB on the computer, used to odin on samsung the last 3 years
Click to expand...
Click to collapse
No, when the device is turned on.

Using Link2SD on the R1HD?

Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?

darkensx said:
Has anyone got Link2SD to work on the R1 HD? It always seems to give the error: mount script cannot be created "mount:No such file or directory" when trying to create mount script. Any ideas what going on.?
Click to expand...
Click to collapse
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201

mrmazak said:
yes. the android toybox/ toolbox used by blu has been altered and the mount function is not working properly. Same issue some have had with adaway, and other mods. The solution should be to install busybox and fully symlink it to /sbin.
I have not done it but based on your reported error it should be the correct solution.
old disscussion about "mount" linked here.
https://forum.xda-developers.com/showpost.php?p=71359910&postcount=201
Click to expand...
Click to collapse
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )

darkensx said:
Where should BusyBox be installed? ( mines currently in /system/xbin ) which BusyBox is best for this solution? ( mines v1.27.1.YDS )
Click to expand...
Click to collapse
that should be correct. I made typo , didnt mean "sbin" meant "xbin"

mrmazak said:
that should be correct. I made typo , didnt mean "sbin" meant "xbin"
Click to expand...
Click to collapse
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.

darkensx said:
Ok so what should be symlink then I thought busybox install took care of the symlinking. What's the command too? Also I'm trying to use Link2SD instead of the lovely Android m adoptive sdcard stuff basically keep sd as portable while using Link2SD so I can have my PC see the fat32 partition if i needed.
Click to expand...
Click to collapse
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.

mrmazak said:
the symlinking is done from in the bustbox installer.
so, you still have problem with busybox installed?
not so sure what to try next. Ah, check in the list of installed links for busybox and see if "mount" is shown as installed.
you can try to install the "toybox" from V12. It is untested method and you would need to know how to undo if needed.
link to the twrp install of that file is in my earlier post.
Click to expand...
Click to collapse
Got it to work had to tell BusyBox installer to overwrite and symlink it apparently it's unchecked by default as its "not recommended to replace the systems version" :silly: go figure maybe under normal circumstances with a correctly functioning mount its bad but it fixed it stericson BusyBox installer did others weren't tested but I assume same result. But thanks for your help greatly appreciated it.

Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.

darkensx said:
Just a note to anyone who comes across this thread if you use Titanium Backup at all don't use "BusyBox X" it seems to break T.B.'s ability to detect root this might be just magisk... or both SuperSU and magisk. but i had this happen with other devices some on SuperSU Some magisk but un-install "BusyBox X" (install any other busybox) and problem goes away not sure what direct cause is in "BusyBox X" might be because X is 1.26.1 and others are 1.27.1 ( ATM ) seems its always one version behind.
Click to expand...
Click to collapse
magisk is working well in the r1?

dark8899 said:
magisk is working well in the r1?
Click to expand...
Click to collapse
yes but because of the way we have to initially unlock/root the r1 it doesn't pass safety net with magisk unless android is not passing safety net again with magisk. but like i mentioned some things can break root "busy box X" with certain apps. also xposed framework systemless and normal seem to work well.

Rooting LN14????

Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).

have you enabled Developer Options?

I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!

harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.

digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.

harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".

Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.

I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse