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.
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.
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 )?
*******MAY 2016 UPDATE
Android Pay is working on the PureNexus May 2016 layers build
To attain this, delete the following files
com.google.android.camera2.xml
Located in system/etc/permissions
And
com.google.android.camera2.jar
Located in system/framework
*******BEGIN PRELIMINARY NOTES*******
-->To go from system root to systemless root,
please use the SuperSU Uninstaller zip linked below and not the unroot feature built into the SuperSU app
-->To fully unroot if on systemless root or system root, use the unroot feature in the apk
*******END PRELIMINARY NOTES*******
If, like me, you've become increasingly desirous of having Android Pay functioning on your rooted device, yet preserving that which you love about your custom setup (see thread title), this thread attempts to provide the resources you need to attain your objective.
For me, I believe that the tipping point came as a matter of principle...I wanted a feature from which I'll likely derive zero utility.
Let me be clear: I see no use whatsoever for Android Pay, and yet, like most Americans, I absolutely must have it.
I found myself returning to the same excuse, "I have a debit card, why do I even want this goofy feature?" That's a good question, but the answer is equally obvious...because it exists.
And I'd see yet another user getting the bloody thing to work on a rooted, custom rom. I hope you can see the urgency.
Just like the one ring to rule them all, the lure of Android Pay is really due to its power that it holds over us...
We Wants It...Stupid HOBBITSES
Many users have grown weary of wading through...
-->Disparate posts within rom threads
-->Dedicated threads for various elements of in the title of this thread, now scattered across xda like the diaspora of a lost tribe (how many Viper4android threads are there?)
-->Posts cross-linked within other threads for a given feature
My reticence would again solidify every time I read another post or series of posts about the precise means a given user went about obtaining Android Pay, and the commensurate loss of a different feature...or, no mention of a feature about which I cared.
So this thread is an attempt to redress these issues; specifically, after reading this, you should be able to have...
1.1-1.5. Systemless Root - If Using System Root
1.6. Updating Systemless Root Versions
2. Properly Themed Apps
2a. Hard-coded themed apps
2b. Theme Ready Google Apps
3. Layers
4. Viper4android that does not break your AUX jack or Chromecast
5. Busybox
6. Android Pay
1. Systemless Root
Whether you are running stock, or one of the few AOSP roms claiming to have Android Pay functioning on your device, this is your first step
If you are running a rooted rom, installing a pre-rooted rom, or want to flash a rom that is pre-rooted, to attain Systemless Root, you'll need the following resources...
1.1. The Latest Systemless SuperSU Zip (scroll to the bottom
http://forum.xda-developers.com/showpost.php?p=64161125
1.2. System Root Removal Tool /unSU
http://forum.xda-developers.com/showpost.php?p=63615067
1.3. Busybox for All Devices (scroll down to the section labeled "Busybox Installer")
http://forum.xda-developers.com/showthread.php?t=2239421
1.4. These Two Terminal Commands (have them in a notepad file, on your computer, or just, literally written down on a piece of paper)
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
1.5. To Install Systemless Root
1.5.1. Boot into Recovery
1.5.2. Install Pre-Rooted Rom + Gapps if Needed
1.5.3. Flash unSU Zip
1.5.4. Go to TWRP Main Menu, Go to Advanced, Terminal Command, type each command exactly as above, one at a time), hitting return in between each line
***you'll only do this once if you plan on staying on systemless root
1.5.5. Flash Systemless Root Zip
1.5.6. Flash Busybox Zip
1.5.7. Flash Custom Kernel if Desired
1.5.8. Fix Folder Permissions
-->Boot your device
-->Using Root Explorer or similar app, navigate to the folder labeled "su," as below...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-->Then hard press on the folder labeled "bin" and select the pop-up option for permissions, so below...
-->Set permissions to 0751, or deselect the check boxes as below...
1.5.8. Keep Reading, or...
Boot to System if This Is All You Want
1.6. Updating Systemless Root Versions
If you're already running Systemless Root and wish to upgrade to the latest version, follow these steps...
1.6.1. Flash latest version of SuperSU
1.6.2. Flash custom kernel if desired
***Note that if you omit the second step above, and wish to stay on a stock, no force encryption kernel (like one that ships with PureNexus), there is no need to reflash the kernel that came pre-installed with your rom. Just flash the latest version of Systemless Root.
2. Viper4android
2.1. Grab a Zip from the Viper4android Atmos Thread Here (some recommend the Viper4android Atmos Sony Beats Edition...so why the heck not?)...
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
2.2. Flash in Recovery
3. Properly Themed Apps
If one wants properly themed apps, and since the Gapps packages that allow working Android Pay are minimal, one must add them
3.1. Hard Coded Themed Apps
Using the Team BlackOut Updater (linked below), download those you want and flash in recovery...make sure to grant the app write permissions to your internal SD storage
http://bit.ly/1OcThZg
3.1.1. Download the Gapps that you want, flash in recovery
3.2. Theme Ready Google Apps
Go to this thread, download what you want...
http://forum.xda-developers.com/android/apps-games/apps-themeable-hangouts-layers-cmte-t3113192
3.2.1. Flash is recovery
3.3. All At Once in TWRP, in Sequence
You can and should flash all of these one after the other in TWRP...here are a few reasons why...
3.3.1. If you're using Gmail, and the minimal Gapps doesn't include it, you'll now have it waiting for you upon boot
3.3.2. If you've got a ton of downloaded music from Google Music, it'll still be there waiting for you if you flash Google Music during install (ie, you'll not have to download all of your music again)
3.3.3. Do you really want to set up hangouts, Google Plus (I turn off notifications and sync for this app...why do that every bloody time...), etc?
3.5. Layers
3.5.1. Install the latest version of the layers manager, and install whatever layers your want
3.6. Busybox That Works
You've already done that
3.7. Android Pay
3.7.1. Download from the Play Store, Add Cards
3.7.2. Note that not all cards will work...it's not the fault of the tools you've been given on this site...it's symptomatic of the reality that none of your cards is issued by participating Android Pay partners
4. Test Android Pay
4.1. You can download SafetyNet Helper Sample from the Play Store...
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
The app is temperamental, and can throw up a false negative...but you will get a positive result most all of the time
4.2. Buy a dang soda, pack of gum at CVS, some cheap gift from Walgreens...I don't care from where...to see if it works (it should)
5. Odds & Ends
A few items of note...
5.1. All of your previously apps granted root permission will need so again
5.2. Stay on top of themed apps...layers can never properly theme certain apps if there's a stock version in the data partition of your device.
5.3. Thank all of the devs whose tools are linked in this thread, donate to them, and be sure to buy anything that they may have for sale...they are the best in class.
5.4. Many things may or definitely will break Android Pay, even if you've set it up properly, including Xposed, theme engine, some DPI changing apps, etc. Just be mindful that this could change if you install other items.
6. Credits
@nathanchance, for being such a good dude
@inffy, for being helpful at all times, while maintaining near pitch-perfect, subtle venom
@osm0sis, for just everything he has provided
@BeansTown106, for building his rom, and not just stumbling but actually figuring out what prevented Android Pay from working on his rom
@daveyannihilation, for being such a great guy, themer, forum moderator, and finest pineapple lover I've ever encountered
@Woody, for having done the heavy lifting on most all of this prior to me
Chainfire
Viewers like you that contribute to Public Television...thanks for your support
Good luck!
Solid work! Gonna add it to my signature and I will add it to my posts as soon as I can.
Great post, and thanks for the mention!
Venom indeed flings in my veins
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Subiegsr said:
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Click to expand...
Click to collapse
I am using the all-in-one package by @guitardedhero
Please link to my thread, not my zip. Thanks.
osm0sis said:
Please link to my thread, not my zip. Thanks.
Click to expand...
Click to collapse
Yes sir...taken care of it.
My apologies.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Me from another thread said:
As an aside, I have an almost completely stripped down /system partition as far as gapps go and have even substituted several TBO ThemeReady versions, as well as Clear YouTube. So if I were to put a wager on what trips the Pay failure [I am speaking in systemless root terms], I would lay bets on system/bin, /system/xbin, busybox configurations and changes to some shadow policy that no one has figured out. Because simply adding or removing apks from /system (not including any signature checked apks such as a modified GMusic or Chrome) and utilizing the /su folder correctly doesn't trip the Pay verification, at least not for me.
Click to expand...
Click to collapse
Thanks
Bookmarked in my tips folder.
I'm sure I'll refer to it many times.
viper4android link is down
Sent from my Nexus 6P using Tapatalk
Most excellent! U Rock on XDA!!
galaxys said:
Most excellent! U Rock on XDA!!
Click to expand...
Click to collapse
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Woody said:
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Click to expand...
Click to collapse
This is true...LOL! I'll continue to scout the teams!
galaxys said:
This is true...LOL! I'll continue to scout the teams!
Click to expand...
Click to collapse
Sometimes looking at the forums via browser really has its advantages.
I'm so glad I looked at this exchange...I'm quite thankful for those cheerleaders...they really want me to have my device exactly as I like it.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Woody said:
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Click to expand...
Click to collapse
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
micmars said:
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The links in the OP all work for me...
http://forum.xda-developers.com/showthread.php?t=2952137
ViPER|Audio || ViPER|Atmos 4.1 * SQ Driver * Audiophile Profile * Beats * Huawei *
They are direct downloads at the bottom of the OP...
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
luigidk said:
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
Click to expand...
Click to collapse
Excellent...I'll add this to the OP, along with the one provided by Woody.
Do you mind telling me...
1. The rom you're running
2. The kernel you're on
3. If you're SELinux is set to permissive or enforcing
Many thanks.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Hello everyone. Those days I feel some to root my phone (ALE-L21 6.0 Dual SIM) to install custom ROMs like LineageOS with Android Nougat and use apps like WPS WPA Tester but other some I feel not because I'm still in warranty time (it ends after 1 year + the warranty isn't in my country) and I never rooted any device or even used Android (my lase phone was Nokia 110) so today I wanna to know why root is useful and why not and what can I use it for and what's the root dangerous? I need all informations about root. :laugh:
Edit: Is all custom ROMs has bugs? Like Radio FM doesn't work, screen recorder doesn't work or even has a bug?
AmirGTX said:
I need all informations about root. :laugh:
Edit: Is all custom ROMs has bugs?
Click to expand...
Click to collapse
Root was a good thing on earlier versions of Android. Now I don't think it's a necessity.
Custom ROM's seems a good idea, but if you don't have official version from the developers I myself don't recommend it.
You can try deoxed, modified or trimmed versions of stock ROM, to get more features.
If you have a branded phone I recommend to unbrand it to obtain ROM updates easily.
I recommend to keep stock for now because we get security patches from time to time.
I think main reasons for rooting and unlocking bootloader.
1. Devices with small memory you can install apps in to SD-card.
2. If you realy hate ads you can use Adblocking.
3. Install custom ROM or kernel to get better battery life/performance (with some devices these are only stuff that isn't perfectly stable but sill stable enoughfor daily use).
4. Uninstall unessesary system apps.
5. More customizing possibilities like change screen dpi(dots per inch --> smaller value gives smaller icons and text so you can fit more stuff in screen at the same time).
6. There is more things to do but this was of the top of my head.
IMO root yes, of course, many reasons pick the ones you like most: uninstall bloatware, tweak kernel parameters, activate hidden options, xposed, greenify...
keikari said:
I think main reasons for rooting and unlocking bootloader.
1. Devices with small memory you can install apps in to SD-card.
2. If you realy hate ads you can use Adblocking.
3. Install custom ROM or kernel to get better battery life/performance (with some devices these are only stuff that isn't perfectly stable but sill stable enoughfor daily use).
4. Uninstall unessesary system apps.
5. More customizing possibilities like change screen dpi(dots per inch --> smaller value gives smaller icons and text so you can fit more stuff in screen at the same time).
6. There is more things to do but this was of the top of my head.
Click to expand...
Click to collapse
1. I use my device currently and needn't more space.
2. I already have Adguard, it's enough for me.
3. Yes, I've bored from the stock Android theme and want to change it.
4. I needn't to remove system apps because I don't even use them.
5. IDK what's this obviously. :laugh:
6. What else?
fosco_ said:
IMO root yes, of course, many reasons pick the ones you like most: uninstall bloatware, tweak kernel parameters, activate hidden options, xposed, greenify...
Click to expand...
Click to collapse
What's IMO? What's bloatware? What's tweak kernel? What's all this? :silly:
AmirGTX said:
1. I use my device currently and needn't more space.
2. I already have Adguard, it's enough for me.
3. Yes, I've bored from the stock Android theme and want to change it.
4. I needn't to remove system apps because I don't even use them.
5. IDK what's this obviously. :laugh:
6. What else?
Click to expand...
Click to collapse
Well I forgot to tell most important reason, because you can : D
Nowdays that's prety much all the stuf that matters for regular user.
Maybe bagroundplayback for youtube if it isn't already possible with regular app.
And it's kind of a plus that you can back backup your full system in TWRP, thought main reson for backups is that you are testing something unstable or new stuff which you can only do with unlocked bootloader.
PS. Your logic in 4 is kind of weird XDD
And dpi is kind of like resolution of screen but still very different but you can think of it as a weird resolution setting
Azzureux said:
Root was a good thing on earlier versions of Android. Now I don't think it's a necessity.
Custom ROM's seems a good idea, but if you don't have official version from the developers I myself don't recommend it.
You can try deoxed, modified or trimmed versions of stock ROM, to get more features.
If you have a branded phone I recommend to unbrand it to obtain ROM updates easily.
I recommend to keep stock for now because we get security patches from time to time.
Click to expand...
Click to collapse
Can you explain more? I didn't got it :cyclops:
AmirGTX said:
What's IMO? What's bloatware? What's tweak kernel? What's all this? :silly:
Click to expand...
Click to collapse
Are you kidding?
IMO = In My Opinion
bloatware = preinstalled apps you don't want but can't remove
tweak kernel = change kernel parameters such as min/max speed, governor, i/o scheduler, gpu speed and so
AmirGTX said:
Can you explain more? I didn't got it :cyclops:
Click to expand...
Click to collapse
I'll try to be brief.
First I rooted my Samsung Galaxy S plus, android version was 2.3.6. Was a good thing? Yes, I had good devs who not only made Rom's up to Lollipop (I use now KitKat on it) but also repartitioned the space available through Twrp giving me more space for apps.
My next one was Galaxy S3 mini, android version was 4.1. I rooted it. Was a good thing? Yes and No.
Yes was good because I could use apps for backup, to remove bloatware, and posible to try custom ROMs.
No... Because I didn't had good developers, every custom ROMs had issues. That made me feel cautious and only installed stock ROM's that gave me more personalization and stable use of the phone (that doesn't mean I don't have problems with it, but it's mostly caused by apps who are not 100% compatible with KK ROM's).
Now let's talk about P8 Lite.
1. Can I squeeze more time of use from battery? Yes, we got the option <Ultra battery>.
2. Can I disable bloatware? I can't remove apps but I can disable them (MM has an option for it).
3. Can I backup apps and data? Yes. We got an option for it.
4. Can I get security updates for my ROM? Yes, for now we get security updates from Huawei.
5. Can I customize my ROM? To a point... Yes, you can customize the interface through themes, and the theme itself using other apps.
6. Can I get Nougat (version 7 of Android).
No, and you can start blaming Google for the requirements asked for it.
Yes, if you buy the 2017 version of the phone.
Sorry I was not brief. :good:
fosco_ said:
Are you kidding?
IMO = In My Opinion
bloatware = preinstalled apps you don't want but can't remove
tweak kernel = change kernel parameters such as min/max speed, governor, i/o scheduler, gpu speed and so
Click to expand...
Click to collapse
Oh alright +1, why I need root else? (I'm just collecting info b4 rooting my device)
Azzureux said:
I'll try to be brief.
First I rooted my Samsung Galaxy S plus, android version was 2.3.6. Was a good thing? Yes, I had good devs who not only made Rom's up to Lollipop (I use now KitKat on it) but also repartitioned the space available through Twrp giving me more space for apps.
My next one was Galaxy S3 mini, android version was 4.1. I rooted it. Was a good thing? Yes and No.
Yes was good because I could use apps for backup, to remove bloatware, and posible to try custom ROMs.
No... Because I didn't had good developers, every custom ROMs had issues. That made me feel cautious and only installed stock ROM's that gave me more personalization and stable use of the phone (that doesn't mean I don't have problems with it, but it's mostly caused by apps who are not 100% compatible with KK ROM's).
Now let's talk about P8 Lite.
1. Can I squeeze more time of use from battery? Yes, we got the option <Ultra battery>.
2. Can I disable bloatware? I can't remove apps but I can disable them (MM has an option for it).
3. Can I backup apps and data? Yes. We got an option for it.
4. Can I get security updates for my ROM? Yes, for now we get security updates from Huawei.
5. Can I customize my ROM? To a point... Yes, you can customize the interface through themes, and the theme itself using other apps.
6. Can I get Nougat (version 7 of Android).
No, and you can start blaming Google for the requirements asked for it.
Yes, if you buy the 2017 version of the phone.
Sorry I was not brief. :good:
Click to expand...
Click to collapse
Awesome, that's why I want to root it but I'm still waiting until LineageOS be available and stable without bugs for me. I bought my phone last year and updated it to MM 6.0 at 7 month of last year, now I have UPDATE.APP (got it from here) it has no bugs and too stable for me. So I saw tutorials here for rooting my device but it were too much big and I need to use my computer. NP if I used my computer but can't I root it using apps suck as KingRoot and then install the ROM? Also I want to know all thing about bootloader and unlocking it and all thing in this operation. I want to know to be deep for such as problems. Thanks for info
AmirGTX said:
Also I want to know all thing about bootloader and unlocking it and all thing in this operation.
Click to expand...
Click to collapse
Few years ago, when we could not imagine that phones can get ROM updates, no one bothered about bootloaders. But after few years they were shocked to see old clients use same depleted phones with new ROM's.
If you look back, when Google started to release Android 3 and up, we can see that the manufactures didn't try to much to improve "the smartphones", the selling ideology was the same as before, manufactures imagined just few improvements for the new models.
But then iPhone appeared, Samsung Galaxy smartphone line appeared and rules changed. Everyone tried to sell smarter phones on the market, Apple had a closed system so everyone looked at Google and android delivered.
So after the "Wild West" period, manufactures wanted more control over their devices, don't forget that devices had hardware in many configurations, so to prevent bricked phones, to try to stop clients from destroying their devices and after ask for guaranty, bootloaders were invented. It's a compromising way for users to obtain root access and avoid warranty claims.
Now, we see that Google stepped a bit, with Android 7, by limiting the compatibility asking for minimum hardware from manufactures. It's a way to make clients buy new devices. Same thing we saw at Microsoft when it released Vista and up. It's a good way for manufactures to stop companies like CM to make unwanted ROM's updates. At the beggining CM ROM's where 100% bug free, but now we can't say the same. Manufactures don't release drivers for hardware so developers to implement new versions of Android on old devices.
For me the only viable option for ROM updates is stock modifications that try to remove restrictions in the software available thru all the world.
But why is Huawei giving a legal way to unlock the bootloader? It's a very easy way to see who still got guaranty and who is out of guaranty. And also it's a way to keep clients close by getting ROM updates faster, it's basically a removal of the middle man (manufactures can't live without firms that do installment sales) a way to increase the overall sales.
Imagine a person who needs a smartphone but can't afford it. Carriers can give devices for less, manufactures get the full price, and carriers get the whole price with interest over a limited period. And now manufactures have a problem, they need to keep clients of carriers happy, and need to push updates on the devices. Carriers see this as a loss of control, but can't make the manufacturer to keep the system closed. So for legal requirements bootloaders were invented.
You can ask for root, but manufactures and Google is giving secure control over the devices, that basically do same thing as apps that required root.
My final advice: if you don't plan to learn about android ROM development, if you don't plan to be a developer, then don't root. Wait until you get a new device, maybe with the new iteration of ROM. If you see something you like, then you can start learning and start developing.
:silly: can't believe i wrote so much. Happy reading and good luck.
Azzureux said:
Few years ago, when we could not imagine that phones can get ROM updates, no one bothered about bootloaders. But after few years they were shocked to see old clients use same depleted phones with new ROM's.
If you look back, when Google started to release Android 3 and up, we can see that the manufactures didn't try to much to improve "the smartphones", the selling ideology was the same as before, manufactures imagined just few improvements for the new models.
But then iPhone appeared, Samsung Galaxy smartphone line appeared and rules changed. Everyone tried to sell smarter phones on the market, Apple had a closed system so everyone looked at Google and android delivered.
So after the "Wild West" period, manufactures wanted more control over their devices, don't forget that devices had hardware in many configurations, so to prevent bricked phones, to try to stop clients from destroying their devices and after ask for guaranty, bootloaders were invented. It's a compromising way for users to obtain root access and avoid warranty claims.
Now, we see that Google stepped a bit, with Android 7, by limiting the compatibility asking for minimum hardware from manufactures. It's a way to make clients buy new devices. Same thing we saw at Microsoft when it released Vista and up. It's a good way for manufactures to stop companies like CM to make unwanted ROM's updates. At the beggining CM ROM's where 100% bug free, but now we can't say the same. Manufactures don't release drivers for hardware so developers to implement new versions of Android on old devices.
For me the only viable option for ROM updates is stock modifications that try to remove restrictions in the software available thru all the world.
But why is Huawei giving a legal way to unlock the bootloader? It's a very easy way to see who still got guaranty and who is out of guaranty. And also it's a way to keep clients close by getting ROM updates faster, it's basically a removal of the middle man (manufactures can't live without firms that do installment sales) a way to increase the overall sales.
Imagine a person who needs a smartphone but can't afford it. Carriers can give devices for less, manufactures get the full price, and carriers get the whole price with interest over a limited period. And now manufactures have a problem, they need to keep clients of carriers happy, and need to push updates on the devices. Carriers see this as a loss of control, but can't make the manufacturer to keep the system closed. So for legal requirements bootloaders were invented.
You can ask for root, but manufactures and Google is giving secure control over the devices, that basically do same thing as apps that required root.
My final advice: if you don't plan to learn about android ROM development, if you don't plan to be a developer, then don't root. Wait until you get a new device, maybe with the new iteration of ROM. If you see something you like, then you can start learning and start developing.
:silly: can't believe i wrote so much. Happy reading and good luck.
Click to expand...
Click to collapse
Extremely awesome and thanks a lot. I want to start to learn about root but IDK from where can I start! There are no way to root any Android emulator and learn from it or executing on main device would be more stable?
IMO, root device it's a personal choice, the important question is:
There's something that you want to do and you can't because you need root?
To install custom rom you don't need root, you have to unlock bootloader, install a custom recovery (TWRP) and finally you can flash you custom rom (generally already rooted!)
ItalianWolf said:
IMO, root device it's a personal choice, the important question is:
There's something that you want to do and you can't because you need root?
To install custom rom you don't need root, you have to unlock bootloader, install a custom recovery (TWRP) and finally you can flash you custom rom (generally already rooted!)
Click to expand...
Click to collapse
Ciao amico mio ? (some Italian from school ?) can you give me a tutorial for this? I need to try. Also why there are a lot of stuffs to root ALE-L21? What if I used apps such as KingRoot?
Ciao!
Kingroot, if it's working again, isn't a good root solution; i've tried (we were with lollipop) but messed up a lot of things so i had to re-flash stock firmware.
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Yes for :
Tweak kernel, install AdAway and remove preinstalled apps.
personally for me is a must, i just do much things with root, anyways you could say i'm an advanced user of android so i need root, if you are good with your phone as it is, or a newer user of android, you don't need to root
panchovix said:
personally for me is a must, i just do much things with root, anyways you could say i'm an advanced user of android so i need root, if you are good with your phone as it is, or a newer user of android, you don't need to root
Click to expand...
Click to collapse
I don't like normal things, I need to be special that's why I think to root my device. I'm neither pro nor newer. So I need to know if I rooted my device what will I do else custom ROMs and block ads and remove system apps?
This post is just to warn users of both LineageOS and Magisk to be very careful when updating to LineageOS 15.1 latest release (May 28) as they may end up stuck booting in bootloader mode. My suggestion is to perform a Nandroid backup prior to updating LineageOS 15.1 to May 28 release. I discovered this on a OnePlus 5 ('cheeseburger') and the issue is systematic with both Magisk 16.0 and 16.4. All I could do is wipe everything and revert to the previous release of LineageOS 15.1 (dated May 21) and this one works fine with Magisk 16.0 and also with 16.4. According to a recent (now deleted) post on LineageOS Reddit thread, the same problem happens on OnePlus 5T ('dumpling').
Gynoid said:
This post is just to warn users of both LineageOS and Magisk to be very careful when updating to LineageOS 15.1 latest release (May 28) as they may end up stuck booting in bootloader mode. My suggestion is to perform a Nandroid backup prior to updating LineageOS 15.1 to May 28 release. I discovered this on a OnePlus 5 ('cheeseburger') and the issue is systematic with both Magisk 16.0 and 16.4. All I could do is wipe everything and revert to the previous release of LineageOS 15.1 (dated May 21) and this one works fine with Magisk 16.0 and also with 16.4. According to a recent (now deleted) post on LineageOS Reddit thread, the same problem happens on OnePlus 5T ('dumpling').
Click to expand...
Click to collapse
As a workaround if you flash a different kernel (i.e. Franco) prior to flash magisk everything working fine
the 0605 build also has the same issue. Is anyone has a solution for this trouble?
I met the same issue, and I have to downgrade to 0521 with sideload.
Unfortunately the devs at Lineage don't seem to give a sh... about Magisk - I tried to raise the problem at their Reddit page, but my post and all subsequent users replies (people having the same issues) were deleted - and, true, LineageOS release 0605 still has that same issue. So the only solution If found is to root my Oneplus5 with LineageOS SU instead, but I still had a problem with the current release of Tasker which does not detect root when LineageOS SU is used. Luckily enough, the latest Tasker beta works fine with it.
So I'll live without Magisk for the moment.
Until I get rid of Lineage
Ah - coming into OP5 from a OP3 - has this been fixed in 6/11 release? I read that flashing franco's kernel BEFORE Magisk solves the problem. True?
digger16309 said:
Ah - coming into OP5 from a OP3 - has this been fixed in 6/11 release? I read that flashing franco's kernel BEFORE Magisk solves the problem. True?
Click to expand...
Click to collapse
Unfortunately, the issue is still present in the 6/11 release, at least on my OP5 and most probably on OP5T as well. Regarding other kernels, I don't know and I will not start testing kernels - takes too much time.
Gynoid said:
Unfortunately the devs at Lineage don't seem to give a sh... about Magisk
Click to expand...
Click to collapse
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
It would be like going into a vegetarian restaurant, slipping some gammon into a vegetable lasagna and then complaining cos it tastes horrible. Only in this case you haven't paid any money and they've given you something for free you can take or leave.
OK so just because it's free it should not be criticized? Is that your point? It should never make any progress? Well that's how "free" projects die. Hopefully their developers will be little more ambitious than that..
gurningchimp said:
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
It would be like going into a vegetarian restaurant, slipping some gammon into a vegetable lasagna and then complaining cos it tastes horrible. Only in this case you haven't paid any money and they've given you something for free you can take or leave.
Click to expand...
Click to collapse
It would be more like a vegetarian restaurant not catering ever to specific dietary requirements, allergies etc.
Except the restaurant is free so nearly everyone okay with it in theory, but it might mean that they lose patronage as too many of their visitors have food sensitivities that mean they end up going elsewhere.
batwingnz said:
It would be more like a vegetarian restaurant not catering ever to specific dietary requirements, allergies etc.
Except the restaurant is free so nearly everyone okay with it in theory, but it might mean that they lose patronage as too many of their visitors have food sensitivities that mean they end up going elsewhere.
Click to expand...
Click to collapse
I mean, I did wonder if the thrust of this complaint was related to irritable bowel syndrome :cyclops:
gurningchimp said:
I mean, I did wonder if the thrust of this complaint was related to irritable bowel syndrome :cyclops:
Click to expand...
Click to collapse
Rooting it wouldn't help with that
gurningchimp said:
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
Click to expand...
Click to collapse
OK, they don't support it but hasn't work on SU ended? Does SU still work to root 15.1? v2.82?
Using the food analogy...
A custom ROM without root is like a half-baked cake to many. Edible perhaps, but not complete.
Magisk has or is becoming the standard to root, isn't it?
digger16309 said:
OK, they don't support it but hasn't work on SU ended? Does SU still work to root 15.1? v2.82?
Using the food analogy...
A custom ROM without root is like a half-baked cake to many. Edible perhaps, but not complete.
Magisk has or is becoming the standard to root, isn't it?
Click to expand...
Click to collapse
You're thinking of SuperSU, lineage, for whatever reason, reinvented the wheel and rolled their own implementation.
OP5 Lineage 15.1 after 2018-05-21 results still in bootloader
the problem seems to persist - the last updates will always result in the device being stuck in the bootloader after flashing. I reversed the update by flashing the cheeseburger 2018-05-21-nightly over the latest (thank god for the working TWRP!) and it boots up normally. I checked up to 2018-06-11
How do we know if this is indeed a problem with Magisk (have v 16.0 installed)? Does somebody need more informations regarding the OP5 (cheeseburger) installs? Can I help in some way to resolve this problem (testing? log files?)
any hope for a resolve? The device works fine but I would like to be able to update regulary at least for security reasons (patched bugs)
I installed LOS15.1 and I see it now. Was this also the case in previous versions, 13 and 14? I remember having to turn on root manually in LOS, then Cyanogenmod and flashing SU. But I think the developer of the custom 14.1 ROM I was using took it out of his ROM so I forgot all about it. Breaking Magisk is lame. I can manage without it, but I prefer the systemless Xposed option it provides.
Did anyone try this with the LOS 20180618 build?
IMHO I don't see anything in the June 18 build changelog that would make me think it's gonna work any better than the previous builds. And on the Magisk side, there hasn't been any new release or beta for a while. So ...
Did anybody find a solution? Would upgrading Magisk 16.0 to 16.4 beta be worth a shot? How about deinstalling Magisk (via the deinstall-zip? or the deinstall option in the manager?) - would this enable the LOS update (as of today 2018-06-18-nightly)? And if yes, would it be safe to reinstall Magisk afterwards or is this door permamently closed?
I would give it a try myself but do not have a backup phone in case of bricking it and I need it for work... a report about a successful strategy would help a lot!
I flashed LineageOS 15.1-20180618-NIGHTLY-cheeseburger and Gapps Nano yesterday. After the reboot I installed the latest Magisk Manager.apk and flashed the latest sdk 27. I am now running LineageOS 15.1 with Magisk v16.0.
I didn't know about any problems there were before because this was the first time I flashed Lineage (had xXx - NoLimits). But I can't see any issues by now. It's working fine. I downloaded Youtube Vanced, Watchdogs Bootanimation and Xposed Framework (only gravitybox atm) which are all working.