Related
So, I'm messing about with building android from the source, just as a learning process and for my own personal satisfaction at this point.
I've come most of the way under my own steam.. got a build up and running from the donut-plus-aosp branch, all google apps included and working.. but I don't actually know how to include root access in the build.. I know this is probably an embarrasingly simple question for a dev, and I feel suitably stupid for having to ask.
Also.. now you're here.. apps2sd.. do I need to compile anything special for that or is it just a bunch of symlinks in init.rc?
Muchos gracias.
I believe the root access is located in the kernel (boot.img)
You would also want to include the SU binaries and busybox.
For the apps2sd, the apps2sd script is run from the init.rc IIRC
Do not hold me up on this because I have not even looked at Android yet, but this is what I gather from reading the forums. I'm hoping it may give you a little direction while someone who has actually built from the source steps in
Thanks. I've already included the su binary and superuser apk but couldn't launch them, so I thought I must be missing something either in the kernel or init.rc.
I was hoping not to have to build the kernel manually just yet.. walk before you can fly and all that, but maybe it's time to grow some wings.
You should just compile cyanogen's kernel. he has it on his github. btw.. did you add busybox? i think apps2sd requires it but im not sure.(check logcat on startup, see what errors its throwing)
I've just added busybox in, but I can't do anything with apps2sd until I get root sorted.
I'm sticking with the 2.6.29-donut kernel for now.. cyan's includes loads of patches that I don't understand yet.. I'll compile it and see what happens purely as an experiment but I reckon it'll give me problems...
Just looking at the configuration options for cyan's kernel makes me feel like a dad trying to program a vcr
This post was infected with retardation. Please ignore.
goldenarmZ said:
This post was infected with retardation. Please ignore.
Click to expand...
Click to collapse
LOL
btw if your building from ASOP, it should already have root. I think you only need to add it to T-mobile OTA's
I know I hate looking at kernels. Liquefies my mind
B-man007 said:
btw if your building from ASOP, it should already have root. I think you only need to add it to T-mobile OTA's
Click to expand...
Click to collapse
It's not working for me.. I just get "permission denied"
Well I've got root by running chmod 4777 on /bin/sh, but this leaves root access wide open to everything and bypasses the confirmation check from superuser.apk... Come on devs, I could really do with a few tips here!
I think I've got it now... thanks to all the devs, you were a real help here.
goldenarmZ said:
I think I've got it now... thanks to all the devs, you were a real help here.
Click to expand...
Click to collapse
XD
i know, they are so helpful right?
Actually they never come by here anymore because of the supernoob questions
I suggest you try to pm,twitter, or website the devs. many of them are very helpful, but cannot stand noobs. as long as you do your research (like u did) you should get help
Hmmm, as I'm also building AOSP from scratch, I would have liked you to have at least posted the conclusion. I feel like several pages were ripped out of my copy of the story.
A malware in form of many apps have been identified lurking in android market. A patch is available for existing users and ROM cooks. More details here
http://forum.xda-developers.com/showthread.php?t=977154
Sent from my LG-P500 using XDA App
but if the exploit is based on rageagainstthecage method why it works on android 2.2.1 or 2.2.2?
I'm not sure. I've read around other forums and some have tried and gotten success with RATC using their PC. I'm not sure if 2.2.1 and 2.2.2 only breaks S1C and Z4
I'll rather be safe than sorry
If the exploit roots the phone and does bad stuff, what if the phone has already been rooted? Will superuser still prompt us that the specific program is trying to gain root access? I'll try installing a "bad app" that was listed on the thread link you gave xD
that was good... if you can find affected apps... it was completely removed from the market the 2nd day of its release.
i sure do want to try this too... just to test the waters
i guess a complete flash will kill the malware on the other hand *lol*
i thought 2.2.2 was created just to implement this patch?
well thats what wikipedia told me
10 charact
..........
Also reserved please
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
ROB281 said:
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Well, I'll get to the point soon. still modifying the post. but basically the gist of it is to check ALL of motorola's update servers for updates, not just the one that comes programmed into the device. If we're lucky and we find a hidden update, we may be able to get an unlocked bootloader (or other goodies?), which will allow us to use our device as we please (new kernels, better mods, etc)
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
karthakon said:
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Well, I was bold and basically just created the files. When I ran the *#*#4636#*#* test, I found that it did indeed change my could update server.
also the com.motorola.blur.setup was in /data/data/ and not the system/etc/motorola.
Thank you.
Sent from my ADR6400L using xda premium
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
K.AuthoR said:
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
Click to expand...
Click to collapse
I actually have been testing some methods that may not even req a wipe in between or possible before
Sent from my DROID BIONIC using Tapatalk
Apparently someone found an update somewhere. Good sign. I'm going to check it out in an hour or two. Don't have my hands on it yet.
Sent from my DROID BIONIC using Tapatalk
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
kennethpenn said:
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
Click to expand...
Click to collapse
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
phydo said:
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
Click to expand...
Click to collapse
Just so everyone can see it: the update label will always be for the build ID that the zip is supposed to be installed over. That means if you've got an update:
Blur_Version.1.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "1."
Blur_Version.5.5.886.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "5.5.886."
Was anyone ballsy enough to attempt to install the update? It doesn't have a bootloader inside, but it may still be dangerous.
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
jimmydafish said:
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
Click to expand...
Click to collapse
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Enzopreme said:
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Click to expand...
Click to collapse
S-off doesn't apply to Moto products...
Sent from my DROID BIONIC using xda premium
cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
I suppose I was looking for the wrong things. On other devices, "ap20bl.img" was responsible for bringing such goodies as an unlock capability.
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
See the title. Right now, I dont have ADB on my PC and Java JDK and I cant be arsed to install it, and reinstall Twrp and flash.
Thank you for your time.
SuperSU is propietary and this situation with android and recent developments have pissed me off alot.
You know;, I dont want to use a browser, without 50 trackers spying on me ,and having SuperSU do god knows wha.t.
A clear no no.
I dont care If I have to run Stock AOSP. The only thing I need is to feel private enough without feeling spied on.
no. superuser is old and outdated. it hasn't been worked on in a while.
Kinguser or cyanogenmod?
shadowcore said:
See the title. Right now, I dont have ADB on my PC and Java JDK and I cant be arsed to install it, and reinstall Twrp and flash.
Thank you for your time.
SuperSU is propietary and this situation with android and recent developments have pissed me off alot.
You know;, I dont want to use a browser, without 50 trackers spying on me ,and having SuperSU do god knows wha.t.
A clear no no.
I dont care If I have to run Stock AOSP. The only thing I need is to feel private enough without feeling spied on.
Click to expand...
Click to collapse
Could always make one yourself. Oh wait if you dont want to go through the effort to accomplish what you want, then you most likely wont want to do that either.
At the moment if there is a rom that doesnt use SuperSU then I have never personally seen it. The Dev has earned the trust of users and the staff over the years.
@simms22,
If it's outdated and no longer being supported, then what do you make of this?
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Sent from my Nexus 6 using Tapatalk
Choose any rom you want, flash, and flash unSU script( http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459 ) then.
And proceed with your preference.
If you really think SuperSU is spyware, you can block internet connection(....) of SuperSU, else something other APP OPtionS are available.
If you want open-source app, I guess CM superuser may be.
My guess is you could live in a tinfoil house in the forest and you would still feel spied on.
reignlight said:
@simms22,
If it's outdated and no longer being supported, then what do you make of this?
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
its a fork, someone else is working on it, koush isnt.
The problem the OP is having seems to be the same one doitright has in his "Root Done Right" thread in Nexus 6 General: a lack of transparency. The argument essentially boils down to this. Because SuperSU is closed source, you can't check it and can't trust it. Therefore you shouldn't use it. In that thread, the reasoning behind the lack of trust is because we know nothing about the entity that now owns SuperSU, and that there's no reason known for the SuperSU binary to manipulate the SELinux policies and reload them, if necessary.
Because of the lack of transparency, doitright feels that SuperSU is too dangerous to use. In order to ensure that there is an avenue to provide full control over our devices should the company now owning SuperSU decide to do something underhanded with the software, he forked Koush's Superuser so that it would support the latest versions of Android.
I know the link given was to PHH's Superuser thread, but I think he's thinking along the same lines as doitright, and is concerned about the potential future impact of the change in ownership. Even I have that concern, but it's not enough for me at this time to stop using SuperSU. Until the time comes that SuperSU is no longer a viable option, any FUD regarding SuperSU is premature.
For the OP, if you're that worried about SuperSU, don't root and don't install a custom ROM. With the exception of Cyanogenmod, custom ROMs all use SuperSU. I don't expect that to change any time soon.
Cyanogenmod roms
Sent from my Nexus 6 using Tapatalk
Thanks for the helpful replies people, at least those that arent condescending.
Does anyone know how the CM root is implemented. ? doitright specifically mentioned that the selinux policy is respected with his fork, and I dont know if CM does so aswell.
I am experimenting with stock CM 13.0 a bit. I wish other custom roms respected the user and left flashing superSU as a choice, not come preinstalled.
I cannot trust SuperSU and I wish not to support a propietary root method.
@shadowcore: Koush's SU hadn't been updated in the last few years, once he stopped working on both it and Clockworkmod. ChainsDD's SU hasn't been updated for an even longer period. Neither option supported SELinux, and ROM developers didn't see the need to add it since Chainfire already had done so with SuperSU. I would know. My stock ROM in the Dell Streak forums was a fork of another ROM (with permission of course), and replaced the included custom superuser binary with SuperSU, despite that device being old enough to work with both Koush and ChainsDD's superuser apps as is. The reason I made the change was simple: SuperSU was being actively worked upon, and the options were not.
I do take some exception to your statement that it's up to the ROM developers to respect user choice. Many of these ROMs are personal projects that the developers saw fit to release to the public, rather than commercial efforts like Cyanogenmod. Thus what is included in the ROM is what the developer prefers, and you either accept it, or you fix it. In the case of SuperSU, you can fix it yourself since the SuperSU app includes a means of removing it within the app so you can install an alternative. However it is up to you to find and install that alternative, not the developer.
simms22 said:
no. superuser is old and outdated. it hasn't been worked on in a while.
Click to expand...
Click to collapse
What the frig are you talking about?
http://forum.xda-developers.com/nexus-6/general/root-t3231211
---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------
PielunA said:
Choose any rom you want, flash, and flash unSU script( http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459 ) then.
And proceed with your preference.
If you really think SuperSU is spyware, you can block internet connection(....) of SuperSU, else something other APP OPtionS are available.
If you want open-source app, I guess CM superuser may be.
Click to expand...
Click to collapse
I'm not sure how you think you can accomplish that.... are you talking about app-ops? If so, do you realize that that would only block the android application and not the actual binary? The daemon process has unrestricted access to the kernel and cannot be blocked.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
simms22 said:
its a fork, someone else is working on it, koush isnt.
Click to expand...
Click to collapse
Two words for you: OPEN SOURCE.
Kind of the whole point of it is that it isn't dependent on any single person. Multiple people work on it, multiple people check each other's work, and if that one person stops working on it, the project isn't lost.
---------- Post added at 07:46 PM ---------- Previous post was at 07:42 PM ----------
Strephon Alkhalikoi said:
The problem the OP is having seems to be the same one doitright has in his "Root Done Right" thread in Nexus 6 General: a lack of transparency. The argument essentially boils down to this. Because SuperSU is closed source, you can't check it and can't trust it. Therefore you shouldn't use it. In that thread, the reasoning behind the lack of trust is because we know nothing about the entity that now owns SuperSU, and that there's no reason known for the SuperSU binary to manipulate the SELinux policies and reload them, if necessary.
Because of the lack of transparency, doitright feels that SuperSU is too dangerous to use. In order to ensure that there is an avenue to provide full control over our devices should the company now owning SuperSU decide to do something underhanded with the software, he forked Koush's Superuser so that it would support the latest versions of Android.
I know the link given was to PHH's Superuser thread, but I think he's thinking along the same lines as doitright, and is concerned about the potential future impact of the change in ownership. Even I have that concern, but it's not enough for me at this time to stop using SuperSU. Until the time comes that SuperSU is no longer a viable option, any FUD regarding SuperSU is premature.
For the OP, if you're that worried about SuperSU, don't root and don't install a custom ROM. With the exception of Cyanogenmod, custom ROMs all use SuperSU. I don't expect that to change any time soon.
Click to expand...
Click to collapse
FYI: PHH and I work on the *same* fork of Superuser. I've been pretty lax on it lately due to growing family, but intend to put some more hours into it soon. We aren't competing with each other at all, but rather working on improvements to the same thing. So don't think of it as being along the same lines, but rather *with*.
And also, I think its probably important for me to also point out that Pierre has certainly put a lot more hours into it than I have. Nevertheless, everything useful is useful.
---------- Post added at 07:54 PM ---------- Previous post was at 07:46 PM ----------
shadowcore said:
Thanks for the helpful replies people, at least those that arent condescending.
Does anyone know how the CM root is implemented. ? doitright specifically mentioned that the selinux policy is respected with his fork, and I dont know if CM does so aswell.
I am experimenting with stock CM 13.0 a bit. I wish other custom roms respected the user and left flashing superSU as a choice, not come preinstalled.
I cannot trust SuperSU and I wish not to support a propietary root method.
Click to expand...
Click to collapse
I haven't actually looked at CM's selinux policy in depth. I *suspect* that they probably go permissive in their su-equivalent context.
What you might want to look at, are custom roms that, rather than "shipping" with one or the other, **DON'T** ship with ANY. I know for one that Omnirom ships WITHOUT root, and while they may recommend supersu, you can use anything.
I'm not sure if my stock-ish boot images will work properly with omnirom. You can try it? If not, you could also try PHH's update.zip installation method.
Personally, I prefer omnirom over cyanogenmod. CM is... very unstable, they are too fast and uncontrolled with the "additions", and adds in certain things that are spyware-ish. Omnirom is more balanced. Far less aggressive, but rather focused on bringing in actual useful features rather than blinging the crap out of it.
---------- Post added at 08:03 PM ---------- Previous post was at 07:54 PM ----------
Strephon Alkhalikoi said:
I do take some exception to your statement that it's up to the ROM developers to respect user choice. Many of these ROMs are personal projects that the developers saw fit to release to the public, rather than commercial efforts like Cyanogenmod. Thus what is included in the ROM is what the developer prefers, and you either accept it, or you fix it. In the case of SuperSU, you can fix it yourself since the SuperSU app includes a means of removing it within the app so you can install an alternative. However it is up to you to find and install that alternative, not the developer.
Click to expand...
Click to collapse
While I don't agree with the choice to use supersu, I absolutely agree with this statement and perspective. Those building custom rom's don't owe anything to anybody, and obviously can make it however they like personally. If that happens to line up with the needs or wants of some group of end users, then those end users benefit from the generosity of whoever is sharing it. If not, then there are others sharing their work, and of course, there is the option to run your own builds.
Having said that, I don't think that the statement was actually meant in quite the way it came off. I think it was meant a little more softly, that from an end user point of view, options are nice.
Frankly, the only ones who actually *owe* you anything, in terms of the operating system, is GOOGLE. That is who you paid for the support by purchasing the product. Of course, that only applies to Nexus branded phones, if you buy something from someone else, they are the ones who owe you support.