Database Develop

[BETA][2017.10.01] SuperSU v2.82 SR5

This thread is for SuperSU releases that are still in testing, and are not yet available through the Play store. The main thread for stable SuperSU releases is located here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703. The changelogs are in the old release thread.
Please keep track of the version numbers in the thread titles, as the latest test release may not always be newer than the latest stable release.
The latest test release is:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
RELEASE NOTES
That is a recovery flashable ZIP (I recommend FlashFire or TWRP). If you want to install via APK, it is also present inside the ZIP, in the common folder.

--- reserved ---

@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.

StupidIdea said:
@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.
Click to expand...
Click to collapse
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.

Chainfire said:
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.
Click to expand...
Click to collapse
No pressure. Its up to you if you decide to publish it before L release or not but I will be glad to test it on L and report if functions that I use in my apps work with it. As for xposed in theory these 5 points rovo89 posted should work with "permissive" but I guess he will verify it himself.
Of topic: I understand its beyond su binary but did you even thought about adding an option to start activity in system or root process? Benefits are simpler interaction with system services and improved service life (faster restarts). Let me know if question is not clear.

Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.

CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone

cioce said:
Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.
Click to expand...
Click to collapse
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Have you tried completely removing the com.sec.knox.seandroid package from your device?
MasterMind33 said:
CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone
Click to expand...
Click to collapse
The reason device default theme is not selected by default is because a lot of OEMs have some godawful themes set by default that everybody would nag me about ...

Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.

MikeRL100 said:
Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.
Click to expand...
Click to collapse
#realworldproblems

I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.

Chainfire said:
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Click to expand...
Click to collapse
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Chainfire said:
Have you tried completely removing the com.sec.knox.seandroid package from your device?
Click to expand...
Click to collapse
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.

cioce said:
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Click to expand...
Click to collapse
I'm not talking about not having root at all. The problem (as I understand it) is caused by having any packages at all in a "disabled" state. This may ultimately cause a crash which triggers a reboot.
At the same time, keeping that package enabled in combination with root, will break various root commands, which you may not even notice (root apps will just appear to randomly fail and be unreliable) which in turn is also known to cause reboots.
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.
Click to expand...
Click to collapse
Just because you haven't noticed the issue doesn't mean it isn't there. As for using it, having root prevents KNOX from working anyway.
...
The point is, solving this problem is not as easy as making that popup optional.

dhampire said:
I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.
Click to expand...
Click to collapse
Please clarify what happens in the following circumstances:
- in-app binary update: normal, and reboot
Keeps saying binary needs updating? Or also results in bootloop?
- in-app binary update: TWRP/CWM
Bootloop?
- latest flashable ZIP with TWRP/CWM
Also bootloop?
It's strange if they don't all result in bootloops...
I know testing is very annoying for you because you need to reflash your system every failed test, but if you want to help solve this problem it's going to require some work.
First test:
- If you have SuperSU 1.94 installed, use the "full unroot" option from settings to remove it.
- Reboot into CWM/TWRP
- Install the latest BETA ZIP but do not reboot
- Adb shell into the device
- "mount /system"
- "ls -l /system/xbin/*su*", post the output here
- "ls -lZ /system/xbin/*su*", post the output here
- Remove /system/app/Superuser.apk
- Reboot into Android
- See if there is a bootloop

Sorry for my poor english. not bootloop. never bootloop. but su binary update loop -> need su binary update again on every boot after update su binary....continue...keep saying need update.
---------- Post added at 09:10 AM ---------- Previous post was at 09:07 AM ----------
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
If 1.9.4, there are no problem like that. but only twrp use su binaly update. normal update makes unroot.

dhampire said:
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
Click to expand...
Click to collapse
Not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
dhampire said:
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
Click to expand...
Click to collapse
Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
...
Please:
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)

Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Frank

Frank Westlake said:
Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Click to expand...
Click to collapse
No it was not a busybox issue, it was an odd bug somewhere in the binary

Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.

dhampire said:
Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.
Click to expand...
Click to collapse
Please confirm the app actually says 2.06
This logcat does not list the output I expect. Did you open SuperSU again after rebooting?
How did you make the logcat? "adb logcat > logcat.txt" ?

[IMG][XT1096] TotalX | root-tether-busybox-sqlite-xposed-hosts-bootanimation-dialer

***** TotalX *****​
I've built a mofo-flashable system image for the Verizon Moto X 2014 containing root, WiFi tethering, Busybox, SQLite3, Xposed, a symlinked hosts file for adblocking, a custom bootanimation, and the stock Google Dialer that has caller ID and allows you to search for business phone numbers. I also added the stock Google Messenger app. I'm currently working on getting CF.lumen to work, and AirAudio is fully functional with this image. I really didn't do much, most of the hard work was thanks to @JulesJam, @Slack3r, @slogar25, @btdownloads7, and @mikeoswego. Shout out to all of them for their hard work.
Download here:
TotalX-1.3.rar
TotalX-1.2.rar
TotalX-1.1.rar (do not recommend flashing, very buggy and drains battery)
TotalX.rar
Instructions:
Download the Xposed installer if you don't already have it, and install it to your phone but don't do anything with it. Also install AdAway 3.0.
If this is your first time flashing an image with Xposed, go into your file manager and delete /data/dalvik-cache/arm and /data/dalvik-cache/profiles. If you don't already have root, just do this step after flashing and reboot.
Wipe cache prior to flashing:
Code:
adb reboot bootloader
fastboot erase cache
Next, extract TotalX.rar to your mofo directory, flash the image with mofo, and wipe cache when its done:
Code:
mofo flash TotalX-1.1.img
fastboot erase cache
It might take a while to boot up, but at least you can enjoy the crazy new bootanimation. When it finally boots, open up AdAway and go to preferences, scroll down to "Target hosts file" and select /data/data/hosts. This sets it so that AdAway modifies the hosts file in /data/data, which is where the /system/etc/hosts file is pointing to.
If you'd like extra heavy-hitting adblocking, add XXXXXXXXXX to your hosts sources (EDIT: Don't do this, it screws up MMS). Then hit download and apply on the main screen and reboot once its done.
Install any Xposed modules you want and reboot. And here's a great module you can't get through the Xposed app: Pandora Patcher
That's it! You should be all set after that with no ads and the power of Xposed. If you have any trouble flashing, don't be afraid to post here and I'll try to help out. And if you'd like to buy me a beer, feel free to shoot [email protected] some cash on Google Wallet
Changelog:
Version 1.3:
- AirAudio is now fully functional!
Version 1.2:
- Removed build.prop edits due to HDR bug and battery drain
Version 1.1:
- Switched to @mikeoswego's base to fix busybox due to Xposed installation removing busybox for some reason
- Google Messenger app added
- build.prop edits by @trimax84
- New bootanimation taken from @motomotomotoG's collection (Geometry Dark), if you'd like any of the others from that page let me know and I'll make you an image!
- Fixed bootanimation memory leak using fix by @arter97
Version 1.0:
- Original, based on @btdownloads7's image, added Xposed, hosts symlink, 5.1 bootanimation, and Google Dialer.
Click to expand...
Click to collapse
Known Bugs:
- Upon flashing, you may experience Google Play Services constantly crashing. Still not sure what causes this. To fix it, uninstall updates for the Google Play Store and Google Play Services, reboot, and then reinstall the update. No more crashing after that.
- If you followed my instructions earlier to add http://adblock.mahakala.is/ to your hosts sources in AdAway, you will most likely be unable to send MMS. To fix this, revert your hosts file and remove this source, then reboot, reapply, and reboot again.
- Version 1.1 was very buggy due to the build.prop edits. The edits create a bug where the camera app crashes when taking pictures in HDR mode. It also seemed to drain battery at a ridiculous pace and created huge slowdowns. I fixed this in later versions and will not be editing the build.prop in future versions.
Click to expand...
Click to collapse

You are the man. I'm downloading now and will flash as soon as I can. [emoji106]

Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.

contesauce said:
Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.
Click to expand...
Click to collapse
hmmm.. that sound a little scary might hold off until its confirmed that this was a one off issue. But thanks for the upload!

To be fair it happened to someone else on one of the other threads with a dif image. Seems to be a one off after a reboot. Understand your trepidation though.

It actually just happened to me too. Rebooted and hasn't happened again. But yeah, it also happened to me with one of the previous builds as well, so I think it might just be a one-off problem. Will report if it happens again.

It does that with every new flash. Not sure why, but a reboot fixes that sucker.

Thanks for this! Any chance of getting this image without Xposed?

TokedUp said:
Thanks for this! Any chance of getting this image without Xposed?
Click to expand...
Click to collapse
I can do that, do you want everything except Xposed?

ClydeDroid said:
I can do that, do you want everything except Xposed?
Click to expand...
Click to collapse
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.

Is this based off the image that has the HDR fix?

TokedUp said:
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.
Click to expand...
Click to collapse
Alternatively you could flash this image and not use Xposed i.e. don't install the APK. Libs are't doing anything important.

Mayze23 said:
Is this based off the image that has the HDR fix?
Click to expand...
Click to collapse
Yep!

ClydeDroid said:
Yep!
Click to expand...
Click to collapse
Installed! Thanks for the Birthday Present -
As a suggestion you could modify the Build.prop to add a custom Rom Name under settings and custom details etc. That way you can really feel ownership of your changes.
Also if you really wanted you could delete Verizon Apps under the /system/app partition to remove bloatware but I understand that may be a bit tedious and undesirable. Otherwise really good build, worked well - no issues.

Haxxa said:
Also if you really wanted you could delete Verizon Apps under the /system/app partition
Click to expand...
Click to collapse
Or you could just freeze them with TiBU. If you are not going to be able to use the space for anything else, no sense in deleting them. Also some Verizon customers actually use NFL Mobile, Verizon Navigator, MyVerizon, etc.

I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.
My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...
Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!

ClydeDroid said:
Yep!
Click to expand...
Click to collapse
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.
http://forum.xda-developers.com/showthread.php?t=2711912
There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.

JulesJam said:
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.
http://forum.xda-developers.com/showthread.php?t=2711912
There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.
Click to expand...
Click to collapse
Sure, I'll give it a shot!

tjohnstone3 said:
I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.
My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...
Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!
Click to expand...
Click to collapse
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.

ClydeDroid said:
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.
Click to expand...
Click to collapse
It's been 5 hours since I did the uninstall updates and reinstall them and I haven't had any issues since. So hopefully it's a thing of the past.
Though I haven't retested the bluetooth since this morning.

Oxygen OS 3.2.1 Released

Source: https://forums.oneplus.net/threads/...s-starting-on-oneplus-3.454469/#post-15056543
Usual 48h to hit devices thing is probably in effect here swell but i'm sure the VPN trick will work for most if you're impatient or waiting for this fix for your SIM issue.
The changelog seems to have added just the SIM fix but for some reason the changelog on the phone says there's more Notification fixes but have to wait and see on that
Here are some of the highlights:
Fixed some notification issues
Addressed SIM recognition issue
Enabled sRGB mode in developer options
Improved RAM management
Improved GPS performance
Enhanced audio playback quality
Updated custom icon packs
Improved camera quality/functionality
Fixed some issues in Gallery
Implemented latest Google security patches
Fixed bugs in Clock/Music apps
Thanks to @Patschi_ for the links
OTA file
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Edit2:
Full ROM
http://otafs.coloros.com/patch/amaz...6_OTA_011_all_1607052050_0e5983ace5314161.zip[/QUOTE]
Full ROM Mirror (Soon)

deleted.

The direct link, if anyone is interested in:
OTA file
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Edit2:
Full ROM
http://otafs.coloros.com/patch/amaz...6_OTA_011_all_1607052050_0e5983ace5314161.zip
Edit3:
Mirrors for all updates and ROMs are available here:
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870

already installed 3.2.0. and its working very well
should i need to update again for 3.2.1

JumboMan said:
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
Click to expand...
Click to collapse
no notification issues?

Patschi_ said:
The direct link, if anyone is interested in: (OTA file)
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Click to expand...
Click to collapse
Thanks for this do you mind if I add them to the OP? not that people shouldn't see your post just might be easier i'll give credits swell.
JumboMan said:
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
Click to expand...
Click to collapse
Might swell the Changelog states there's Notification issue fixes as well but still waiting to see if that's true.

Roxas598 said:
Thanks for this do you mind if I add them to the OP? not that people shouldn't see your post just might be easier i'll give credits swell.
Click to expand...
Click to collapse
Feel free to add it to the OP
Downloading the Full ROM right now to provide a mirror... could take a while as the download servers are quite slow right now.

mirrors will be provided here aswell I think: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870

When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?

daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
Are you using the System Update option on the phone to install or the Zip file? either way normally any changes to the system will make OTA fail (like root and xposed)

daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
Actually no. You don't have to unroot but you need to flash stock boot.img . Better option always is to flash Full 3.2.0 ROM twice (sometimes first flash doesn't succeed) and then 3.2.0 -> 3.2.1 OTA immediately and then SuperSU and Xposed. Or wait for Full ROM mirror. Will take me some 20 minutes more. I am downloading it at the moment.

Yes, I tried to install the downloaded ota file via TWRP. Guess I have to download the whole 1.2 GB to get the 15MB update.
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
Naman Bhalla said:
Better option always is to flash Full 3.2.0 ROM twice (sometimes first flash doesn't succeed) and then 3.2.0 -> 3.2.1 OTA immediately and then SuperSU and Xposed.
Click to expand...
Click to collapse
Thank's for the hint! Had the 3.2.0 file on my phone and did it this way.

Sledge2013 said:
no notification issues?
Click to expand...
Click to collapse
can you explained it in detail.which notification issues?

Sorry for the question, just to be clear:
I install the full ROM in twrp, install it again without rebooting and after that immediately SuperSU?
Do I have to wipe Cache/Dalvik?
After that I reboot and all the apps are still there?

Spotted this and just VPNd it my self.
Fingers crossed i get less drain over night

Der-Knuffi said:
Sorry for the question, just to be clear:
I install the full ROM in twrp, install it again without rebooting and after that immediately SuperSU?
Do I have to wipe Cache/Dalvik?
After that I reboot and all the apps are still there?
Click to expand...
Click to collapse
If you install the full 3.2.1 rom just install it once, then supersu and THEN wipe cache/dalvik. Your apps will be still there he just needs to optimize them at the start(might take 10 minutes).
If you want to use this "trick" to install 3.2.1 OTA over a 3.2.0 full rom, i have no clue. But i would rather install the full rom. I tried it with the OTA last time and it didn't worked.

eikaramba said:
If you install the full 3.2.1 rom just install it once, then supersu and THEN wipe cache/dalvik. Your apps will be still there he just needs to optimize them at the start(might take 10 minutes).
If you want to use this "trick" to install 3.2.1 OTA over a 3.2.0 full rom, i have no clue. But i would rather install the full rom. I tried it with the OTA last time and it didn't worked.
Click to expand...
Click to collapse
Ok, thanks. That's the way I used to do it since years, but I'm new to OnePlus 3, so ...

Der-Knuffi said:
Ok, thanks. That's the way I used to do it since years, but I'm new to OnePlus 3, so ...
Click to expand...
Click to collapse
me too. coming from nexus 5 some things definitely changed for us flashoholics

flashed over 3.2.0, no issues so far. supersu, xposed, adaway all is working fine.

daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
daclaus, you have to install the complete rom via twrp, after that you have to install root and xposed again. ota will not work with twrp.

[ROM] Lineage OS for Redmi 4A (CM13)

Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
*Screenshots*
...in the attachment...
*Installation*
- Make sure you have unlocked your bootloader and installed custom recovery like TWRP
- Boot into the recovery and do a clean wipe
- Flash both the rom and Google Apps.
*Links*
Google Apps: http://opengapps.org/
ROM: https://www.fshare.vn/file/GC4BYLT3OW98
=> Updated Google Drive Link: https://drive.google.com/open?id=0BxIquhyX_RgPYmx1UW84NHRSRnM
*Author: zerozaki_ Wang Haozhe from miui.com
*Last updated: 07 March 2017

How is battery life?

marcimix said:
How is battery life?
Click to expand...
Click to collapse
i've only tried it for 1 day, can't make a conclusion

Finally...

Any bugs in this rom and is volte working

mdnaveedb4u said:
Any bugs in this rom and is volte working
Click to expand...
Click to collapse
volte doesnt work even jio4voice doent work

The rom is unstable. It presents some problems in the recovery mode, in the Brazilian 4g network and in the sensors.

skmaiti2050 said:
How much free RAM is available after boot?
I was interested in flashing the ROM for my device also
And does it supports all the inbuilt sensors?
Please give a reply after routine daily usage about battery life
Waiting for a reply :fingers-crossed:
Click to expand...
Click to collapse
yes it supports all sensors. However, sometimes it does a fast reboot (system ui failed maybe?)

mybabysexy said:
yes it supports all sensors. However, sometimes it does a fast reboot (system ui failed maybe?)
Click to expand...
Click to collapse
mine was unusable

Random Reboot
Having random reboots.

Here's what I noticed after a night:
Root is disabled by default as with most Lineage/CyanogenMod builds and can be enabled via dev options, but the only options are None and ADB, no Apps and ADB. So not a proper root stuff. Flash SuperSU or prefered root manager if you want.
Most sensors works just fine, I can run a compass app normally.
Double tap to wake isn't working, use Gravity Screen instead to unlock your screen with your proximity sensor.
Battery drain is relatively faster than stock since there is no 'built-in optimizer' like the MIUI optimization (of course). Just use Greenify, I guess?
Most stuff you'd expect from a LineageOS builds: double-tap statusbar to sleep, live display, privacy manager, button configurations etc. And since this is a Marshmallow build, you can still find the now-discontinued CM theme engine. You can still use CM themes floating around the Store/XDA. Also included an extra 'dark' theme, I suppose.
up until now (7:30 PM GMT +7) there's no random reboots or crashes, even with Xposed + Magisk installed

extra update and also a bump:
whoopsie, I got the reboots now. Seems like it was related to the location services when it was set to "High Accuracy". Can anyone confirms this or something?
mybabysexy said:
yes it supports all sensors. However, sometimes it does a fast reboot (system ui failed maybe?)
Click to expand...
Click to collapse
L4nun_P4s1r said:
Having random reboots.
Click to expand...
Click to collapse
did you enabled the location service on "High Accuracy"?

thatOneWeeaboo said:
extra update and also a bump:
whoopsie, I got the reboots now. Seems like it was related to the location services when it was set to "High Accuracy". Can anyone confirms this or something?
did you enabled the location service on "High Accuracy"?
Click to expand...
Click to collapse
Hard reset my phone, and install only the app i used for my daily. up till now, no random reboots.
After my hard reset, setting is on default. not touch it much,except to activate the developer mode..default already at high accuracy, no random reboot yet.

L4nun_P4s1r said:
Hard reset my phone, and install only the app i used for my daily. up till now, no random reboots.
After my hard reset, setting is on default. not touch it much,except to activate the developer mode..default already at high accuracy, no random reboot yet.
Click to expand...
Click to collapse
Try using maps with GPS on?

thatOneWeeaboo said:
Try using maps with GPS on?
Click to expand...
Click to collapse
yes. done that. no reboot
this is my app list.
gapps pico
youtube
xda app
gmaps
9gag
flight simulator
sky dancer
http injector
opera vpn
spotify
instagram
facebook
i also disable 2 chinese app tht have in system. only disable, not delete.
in setting,
dev option enable
advanced reboot enable
and some change in keyboard
everything else is default.

interesting !
I bought this phone for a friend so i can't flash it now, but the bootloader is already unlock ( i received it like that ) and flashed a twrp + SU.
For sure i will try it !
Thanks ! !! !

L4nun_P4s1r said:
yes. done that. no reboot
this is my app list.
gapps pico
youtube
xda app
gmaps
9gag
flight simulator
sky dancer
http injector
opera vpn
spotify
instagram
facebook
i also disable 2 chinese app tht have in system. only disable, not delete.
in setting,
dev option enable
advanced reboot enable
and some change in keyboard
everything else is default.
Click to expand...
Click to collapse
try using Maps with any Location mode while locating yourself? (The button above the navigate one). It instantly gave me the reboots.

thatOneWeeaboo said:
try using Maps with any Location mode while locating yourself? (The button above the navigate one). It instantly gave me the reboots.
Click to expand...
Click to collapse
Maybe it's the GPS fault. I tried to re-flash the ROM and turn GPS fully off and no reboot happened until now.
.
Just related to this, I once installed MIUI v7 to my old Samsung S4 and everytime I open Google Map it soft-bricked my device

TockTockTicky said:
interesting !
I bought this phone for a friend so i can't flash it now, but the bootloader is already unlock ( i received it like that ) and flashed a twrp + SU.
For sure i will try it !
Thanks ! !! !
Click to expand...
Click to collapse
How could this even be? It supposed to be be locked by default, or else maybe you were scammed.

mybabysexy said:
Maybe it's the GPS fault. I tried to re-flash the ROM and turn GPS fully off and no reboot happened until now.
.
Just related to this, I once installed MIUI v7 to my old Samsung S4 and everytime I open Google Map it soft-bricked my device
Click to expand...
Click to collapse
I also turn location off by default so it won't bug me for most of the time but when I actually need it it does
mybabysexy said:
How could this even be? It supposed to be be locked by default, or else maybe you were scammed.
Click to expand...
Click to collapse
A big chance it's a secondhand

Fortnite root detection ! FOUND FIX

FIX link - https://forum.xda-developers.com/galaxy-s9/themes/how-to-play-fortnite-rooted-device-t3827577
If not working try installing a clean rom with out any magisk or any other rom which has the option to not install root.
Rootless rom Try [ROM][N950F/DS/N][ALEXNDR] * U4CRGA * DevBase v5.9 * Encryption support [Aug-04] Case 3 - do not root device
(place "noroot" string anywhere in the ZIP file name, e.g. "N950Fxxx_DevBase_v5.x_noroot.zip")

try using stock since some says that worked for them and reply back please im having same issue

It's been on Twitter. They have used a detection method that Magisk doesn't support yet. John is working on it.

Omega_300 said:
try using stock since some says that worked for them and reply back please im having same issue
Click to expand...
Click to collapse
So Ya I found a fix..
install a clean rom with out any magisk or any other rom which has the option to not install root.
I used - [ROM][8.0.0] LightWeightWiz 1.0 [Aug-Patch]. rom which dose have auto root installation in TWRP when installing the rom, but thank god magisk failed to install when installing the rom in twrp.

Mrblackm123 said:
So Ya I found a fix..
install a clean rom with out any magisk or any other rom which has the option to not install root.
I used - [ROM][8.0.0] LightWeightWiz 1.0 [Aug-Patch]. rom which dose have auto root installation in TWRP when installing the rom, but thank god magisk failed to install when installing the rom in twrp.
Click to expand...
Click to collapse
do you know of any ROM that has the option to not install root? seems like you got lucky by magisk not properly installing.. I'm afraid I won't have the same luck xD

2000ftt said:
do you know of any ROM that has the option to not install root? seems like you got lucky by magisk not properly installing.. I'm afraid I won't have the same luck xD
Click to expand...
Click to collapse
Try [ROM][N950F/DS/N][ALEXNDR] * U4CRGA * DevBase v5.9 * Encryption support [Aug-04]

So guys did any try that and it's working ??

No need to flash anything!
See this- https://forum.xda-developers.com/galaxy-s9/themes/how-to-play-fortnite-rooted-device-t3827577

Vmb265 said:
No need to flash anything!
See this- https://forum.xda-developers.com/galaxy-s9/themes/how-to-play-fortnite-rooted-device-t3827577
Click to expand...
Click to collapse
thx

that didnt work guys