Related
Alright, so I just flashed MRA58N yesterday, and today there is a new MRA58R image added? What's the difference here? The first build was a security update, but what's this new one? And why only a day difference? Thanks!
Sent from my Nexus 6
Changelogs aren't made readily available.
Perhaps this script will help people who update their local AOSP repo's will help.
https://groups.google.com/forum/#!msg/android-building/0DtsHawjs4k/And8o3Dni_UJ
Obviously some modification will be required
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Quetzalcoalt_Lp said:
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Click to expand...
Click to collapse
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Rektifying said:
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Click to expand...
Click to collapse
What kernel are you using?
H4X0R46 said:
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
Click to expand...
Click to collapse
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
scryan said:
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
Click to expand...
Click to collapse
I never do a dirty flash just to avoid conflict, but I guess it couldn't hurt to try right? So not wiping userdata should work?
Sent from my Nexus 6
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
I have always had zero issues applying newer stock images over older stock images on a Nexus device. I do this all the time when the OTA is not available and only the main updated Google Factory image is available.
I think the trick is to always wipe dalvik and cache after a flash of system and use TWRP that supports encryption. When you wipe the dalvik and cache the system acts like an OTA and performs an upgrade on all your apps. I *think* it effectively rebuilds the cache for all apps, but it never touches the app data or user data (sdcard/pictures/etc).
I also always flash the radios and bootloader *IF* they are updated from the last image. I used to flash the stock boot images too, but now that looks like from a going forward point we won't be able to do this and have root. I do look forward to system-less root
scryan said:
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
Click to expand...
Click to collapse
Cool dude! Thanks for the advice! Yea, I use ElementalX kernel on my device, unencrypted device makes no noticeable difference for performance to me, but the battery life is another story! ElementalX has superb battery life!
Sent from my Nexus 6
Any word on the changes between this and previous build yet?
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
dahawthorne said:
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
Click to expand...
Click to collapse
The security updates were also in the previous build, MRA58N.
All we really know for sure is that the OTA for MRA58R is being pushed out by Verizon. The OTA path skips MRA58N.
Pushed out by big red.... I think that's something I'll definitely wait on.
jbeezley said:
Pushed out by big red.... I think that's something I'll definitely wait on.
Click to expand...
Click to collapse
I've never had a problem with their updates and, realistically, this is actually a Google update. I'm just impressed that they're leading the charge.
I'm on MRA58K after sideloading the first Marshmallow OTA. I just noticed there's an OTA from K to N but there's nothing from any Marshmallow build to R.
I'm on N and haven't seen anything detailing what's different in R. I'm just a bit suspicious of anything pushed by Verizon, although you are correct @GilmourD3. It's Google's update, but why would Verizon spearhead the rollout? I would rather just stay on N awhile until we have someone in the know look over the details of the update to R.
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
H4X0R46 said:
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
Click to expand...
Click to collapse
Anything change from K to N? I might just sideload the N OTA since I'm currently on K and I'm not finding an OTA path from K to R.
R is apparently the OTA update to 6.0 and the November security update for Verizon Nexus 6. My wife got it Thursday and her build and security date both changed.
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
You cannot apply Google OTA updates with a custom recovery. Replace your recovery with the stock version and try again.
Not just custom recovery - any system change such as root will stop the OTA. Depending on how you rooted, you might be able to unoot using the built-in SuperSU function (I'm guessing Supersu?) but more likely than not it still won't work.
The simplest thing to do is forget about the OTA entirely. Download the full ROM from Google, unzip it, unzip the zip inside the zip, and there you'll find system.img, which you can flash in Fastboot, then reroot. Done.
sonic2kk said:
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
Click to expand...
Click to collapse
How did TWRP ended on your phone in the first place?
istperson said:
How did TWRP ended on your phone in the first place?
Click to expand...
Click to collapse
I installed TWRP.
Thanks for the suggestions everyone!
sonic2kk said:
I installed TWRP.
Thanks for the suggestions everyone!
Click to expand...
Click to collapse
Oh, then as other people said, if you want OTA then totally unroot it, then reflash system of the current version, and flash stock recovery. But it's much better when a new version arrives, just download it, flash system and boot, reroot it, clear cache and dalvik. This way you'll have your updated Android days or even weeks before the OTA.
Moving this here to a separate thread.
I hope both of you are willing to test, because I have not been able to reproduce the issue on my own (international) Note 4 so far.
dbzgod, which firmware are you running?
dbzgod said:
@Chainfire updating from 2.65 to 2.66 breaks data on Canadian Note 4.
IMEI and baseband become unknown. Downgrading back to 2.65 restored it.
Not sure what log to provide or how to go about getting one in this case, as it installs fine in twrp and apps get root access without issue.
Click to expand...
Click to collapse
ShrekOpher said:
Trouble with v2.66 beta.
I flashed the 2.66 beta with TWRP on my Note 4 (910T). after reboot I lost signal and IMEI. I am not sure what changed, but it looks like something from 2.65 to 2.66 broke the cell signal on the Note 4.
I am running stock firmware 5.1.1 DOK2
Just wanted to let you know.
Click to expand...
Click to collapse
Yeah I'm down. Let me know what you need.
Log for no signal issue.
https://mega.nz/#!zxJXwAxA!pWCkObE1PrwRz4ZhYAHhEw8bJKhk-fyjlqpuL7bCwmo
Chainfire said:
Moving this here to a separate thread.
I hope both of you are willing to test, because I have not been able to reproduce the issue on my own (international) Note 4 so far.
dbzgod, which firmware are you running?
Click to expand...
Click to collapse
For sure ill test.
I am running the latest stock Canadian rom 5.1.1 N910W8VLU1COK3
Which logs to provide? Is there an app that will quickly provide all the logs like you did @ShrekOpher
dbzgod said:
For sure ill test.
I am running the latest stock Canadian rom 5.1.1 N910W8VLU1COK3
Which logs to provide? Is there an app that will quickly provide all the logs like you did @ShrekOpher
Click to expand...
Click to collapse
Yeah I used sys log. Link below.
https://play.google.com/store/apps/details?id=com.tortel.syslog
Thanks for the logs and info. Trying to use them combined with dissected firmwares to figure out what the issue is.
What can we do to help test? I just moved back to the stock 5.1.1 firmware (DOK2) from having been using VisionX Rom (A port from the international note 4). I flashed the stock image using odin and then flashed TWRP. I jumped straight to SU version 2.66. I had an IMEI before I flashed that file. Afterwards, it was null. I re-flashed the stock image using odin, which restored the system image and effectively deleted any ramdisk mods. I restarted and had my IMEI back and full lte signal. Each flash that I did was dirty, I have not factory reset. The custom ROM that I was running prior to going back to stock was pre-rooted with the xposed framework running. Please let me know what other information you require and I will get it to you. Thanks.
BJHiltbrand said:
What can we do to help test? I just moved back to the stock 5.1.1 firmware (DOK2) from having been using VisionX Rom (A port from the international note 4). I flashed the stock image using odin and then flashed TWRP. I jumped straight to SU version 2.66. I had an IMEI before I flashed that file. Afterwards, it was null. I re-flashed the stock image using odin, which restored the system image and effectively deleted any ramdisk mods. I restarted and had my IMEI back and full lte signal. Each flash that I did was dirty, I have not factory reset. The custom ROM that I was running prior to going back to stock was pre-rooted with the xposed framework running. Please let me know what other information you require and I will get it to you. Thanks.
Click to expand...
Click to collapse
Which exact device is this?
Chainfire said:
Which exact device is this?
Click to expand...
Click to collapse
Sorry, I forgot to mention. It's a T-Mobile Note 4 (SM-910T). I am using it on the Cricket Cell network, however, so I have had to manually enter the settings for their APN to get it to connect. Don't know if that's relevant.
@dbzgod @ShrekOpher @BJHiltbrand
Please try the attached version.
I'm more or less stabbing in the dark here, I don't have too much hope of this fixing it, but it just might. Let me know.
(download removed, try newer one below)
Chainfire said:
@dbzgod @ShrekOpher @BJHiltbrand
Please try the attached version.
I'm more or less stabbing in the dark here, I don't have too much hope of this fixing it, but it just might. Let me know.
Click to expand...
Click to collapse
No Dice still could not get Cell signal. No Idea why either. I got another sys log for you though. thanks for the help.
Is there a reason why on 2.65 beta the cell signal works fine, but on 2.66 its broken. Maybe looking at what changed is the only way to figure it out.
thanks for the effort either way, as you know all of the Android community appreciates your hard work.
https://mega.nz/#!30xBDJaS!mos23pH9RtqumWEbPof4cGy5wLW6JsGF_EWPmtztgzo
I am in fact looking at what has changed. The problem is that some of these things cannot be rolled back without breaking other phones/firmwares.
I really only have two options left on what the issue is. Either the rollback in the attached version fixes the problem, or its likely the problem is in the ZIP installer script or your recovery. Which recovery and version are you running?
(download removed, try newer one below)
@ShrekOpher btw I can't really see anything obvious in your logs either. But its a lot of logs
Chainfire said:
I am in fact looking at what has changed. The problem is that some of these things cannot be rolled back without breaking other phones/firmwares.
I really only have two options left on what the issue is. Either the rollback in the attached version fixes the problem, or its likely the problem is in the ZIP installer script or your recovery. Which recovery and version are you running?
Click to expand...
Click to collapse
I'm using TWRP 2.8.7.0. Trltetmo.
What can I do to help you get a log with the issue visable?
ShrekOpher said:
I'm using TWRP 2.8.7.0. Trltetmo.
What can I do to help you get a log with the issue visable?
Click to expand...
Click to collapse
Honestly, I don't know. I do need you to test that ZIP a few posts above, though.
If that one still doesn't work, I'll revert the ZIP installer script changes as well, see if that solves the issue.
EDIT: Something that might help is a log of the same device with 2.65 and without the signal issue
SUCESS the last zip SuperSU-v2.66-20160119182909 worked. Data and cell service is up and running great.
ShrekOpher said:
SUCESS the last zip SuperSU-v2.66-20160119182909 worked. Data and cell service is up and running great.
Click to expand...
Click to collapse
That is unfortunate. To further narrow it down, how about the attached ZIP ?
(download removed, try newer one below)
Chainfire said:
That is unfortunate. To further narrow it down, how about the attached ZIP ?
Click to expand...
Click to collapse
I'm using TWRP 2.8.7.0 for trltecan
Same results as ShrekOpher SuperSU-v2.66-20160119182909.zip works and restores cell data.
Just try'd SuperSU-v2.66-20160119205512.zip and it went back to no cell data/imei.
I would guess that what's killing it is changes in what gets patched to the boot img?
dbzgod said:
I'm using TWRP 2.8.7.0 for trltecan
Same results as ShrekOpher SuperSU-v2.66-20160119182909.zip works and restores cell data.
Just try'd SuperSU-v2.66-20160119205512.zip and it went back to no cell data/imei.
I would guess that what's killing it is changes in what gets patched to the boot img?
Click to expand...
Click to collapse
(also @ShrekOpher )
Please try the attached version.
What's killing it are the latest sepolicy patches. A patch that is needed for Android 6.0 to work is apparently messing with your Note4 (on 5.1). I'm trying to fix it so it works on both, and shouldn't pose a problem in the future for other devices.
Also, do you guys just get no cell signal, or also no Wi-Fi ?
Chainfire said:
(also @ShrekOpher )
Please try the attached version.
Also, do you guys just get no cell signal, or also no Wi-Fi ?
Click to expand...
Click to collapse
WiFi is working fine on all of them so far. The most current BETA-SuperSU-v2.66-20160119220513.zip - killed the data/cell signal again.
I have android one device namely Karbonn Sparkle V. I am well aware with flashing custom roms and kernels and risks involved.
I had my devices earpiece giving muffled voice so i replaced it in local shop i was on stock rom then with no problems.Later on i decided to flash cm13 nightly but i was on adopted storage so i went with twrp 3.3 flashed cm13,then thunderzap through app all went well at night.Then in the morning for some reason unknown display was dead,touchpad was responding though. Local store wants me to replace my display but i fear it got something to do with software side which will again burn display replaced.
Is there anyway go to fastboot and flash stock without using display?
And second do you have any suggestion what would have caused it?
rohitsonone said:
I have android one device namely Karbonn Sparkle V. I am well aware with flashing custom roms and kernels and risks involved.
I had my devices earpiece giving muffled voice so i replaced it in local shop i was on stock rom then with no problems.Later on i decided to flash cm13 nightly but i was on adopted storage so i went with twrp 3.3 flashed cm13,then thunderzap through app all went well at night.Then in the morning for some reason unknown display was dead,touchpad was responding though. Local store wants me to replace my display but i fear it got something to do with software side which will again burn display replaced.
Is there anyway go to fastboot and flash stock without using display?
And second do you have any suggestion what would have caused it?
Click to expand...
Click to collapse
Did you try SP flash tools ?
Yes i found t
Yes i would i will try that today and will get screen replaced then. @Saurabh K Thank you for replying.
rohitsonone said:
I have android one device namely Karbonn Sparkle V. I am well aware with flashing custom roms and kernels and risks involved.
I had my devices earpiece giving muffled voice so i replaced it in local shop i was on stock rom then with no problems.Later on i decided to flash cm13 nightly but i was on adopted storage so i went with twrp 3.3 flashed cm13,then thunderzap through app all went well at night.Then in the morning for some reason unknown display was dead,touchpad was responding though. Local store wants me to replace my display but i fear it got something to do with software side which will again burn display replaced.
Is there anyway go to fastboot and flash stock without using display?
And second do you have any suggestion what would have caused it?
Click to expand...
Click to collapse
Dude, where did u get twrp 3.3 for Android one. The twrp built for our device is 2.8.0.0 (and lower versions) which you will found in this thread.
https://goo.gl/3vODMX
Edit: 2.8.6.0 is the latest get it here: https://dl.twrp.me/sprout/
Many users reported getting bootloped and black screen with higher twrp. 2.8.7.0 has got some bugs related to backups and storage.
rajputmiles said:
Dude, where did u get twrp 3.3 for Android one. The twrp built for our device is 2.8.0.0 (and lower versions) which you will found in this thread.
https://goo.gl/3vODMX
Edit: 2.8.6.0 is the latest get it here: https://dl.twrp.me/sprout/
Many users reported getting bootloped and black screen with higher twrp. 2.8.7.0 has got some bugs related to backups and storage.
Click to expand...
Click to collapse
It is in @icefire 's afh download directory for sprout.In hindsight i should have asked him about it.
rajputmiles said:
Dude, where did u get twrp 3.3 for Android one. The twrp built for our device is 2.8.0.0 (and lower versions) which you will found in this thread.
https://goo.gl/3vODMX
Edit: 2.8.6.0 is the latest get it here: https://dl.twrp.me/sprout/
Many users reported getting bootloped and black screen with higher twrp. 2.8.7.0 has got some bugs related to backups and storage.
Click to expand...
Click to collapse
It is in @icefire 's afh download directory for sprout.In hindsight i should have asked him about it.
rohitsonone said:
It is in @icefire 's afh download directory for sprout.In hindsight i should have asked him about it.
Click to expand...
Click to collapse
The official maintainer of twrp for sprout ie Android one is dev 'varunchitre15' as stated here https://twrp.me/devices/androidone.html
Therefore you must go with it only
and please note the final thing :-
"Use 2.8.4.0
It has No issues
2.8.5.0 has backup problem 2.8.6.0 has reboot problem".
Thank you for your @rajputmiles but twrp unofficial builds by @icefire work better than official ones anyway.But dev hasn't posted twrp 3.0 build on xda yet for unknown reason,but its present in afh ,and recovery worked great even supported adaptive storage on marshmallow.
"Hi all,
OxygenOS 4.1.5 was withdrawn, we are pushing out the incremental roll-out of OxygenOS 4.1.6 (7.1.1) OTA for OnePlus 3 and 3T instead.
Here are some highlights
New additions:
• Added system push notifications for important information from OnePlus
Updates:
• Updated network settings for select carriers
• Updated OnePlus Community app to v1.8
• Updated Android Security Patch level to 1st May 2017
• Modified WiFi no internet indication icon
Bug fixes:
• Fixed storage issue present on 3rd party filemanagers
• Fixed VoLTE issue on certain Jio SIM cards
• Fixed connection issue on Android Auto
Optimizations:
• Battery
• Proximity sensor
• Camera low light focus
• Expanded screenshot
Other changes:
• Enhanced system stability
For those who were on previous versions for OnePlus 3 and 3T, we appreciate your active feedback and attempts to reach out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.net/feedback/.
As always, this OTA will be incremental. The OTA will reach a small percentage of users today, and we'll begin a broader rollout in a few days.
Your feedback is appreciated. We may not always be able to respond to every comment in the forums, but please be assured that we take your comments and feedback seriously. Hope you enjoy!
Please make sure to fill out our user survey here: https://goo.gl/forms/Pvr6KisTvbFoqZkl1
Never Settle.
****Special thanks to @ Stephan Mävers for helping out with rom validation."
https://forums.oneplus.net/threads/oxygenos-4-1-6-7-1-1-ota-for-oneplus-3-and-3t.547283/
Full ROM: https://drive.google.com/open?id=0B8wU-_ssGUuoSGJqUVYzYWlEUlk
MD5: 3db32c320ebce696e9b058a31e77e9a8
So quick, just now got someone OTA adn informed at OP forum and uploaded in xda. Great effort @piats
[email protected] said:
So quick, just now got someone OTA adn informed at OP forum and uploaded in xda. Great effort @piats
Click to expand...
Click to collapse
Hehe, time to give something back for this community :good::highfive:
Edit: remember to backup everything before flashing. I dirty flashed this ROM over stock OOS 4.1.5 via bluespark recovery v35 and it didn't boot back to system. So I booted back to recovery and somehow twrp asked password to decrypt data partition. I was decrypted before. So I installed stock recovery. Wiped everything and flashed this ROM via stock recovery. Everyhthing works now.
Can I flash this zip using TWRP?
DouglasDuZZ said:
Can I flash this zip using TWRP?
Click to expand...
Click to collapse
Well you can try but remeber to backup everything before flashing. See my previous post.
I would recommend stock recovery for now.
I would really like to know the reasons behind these withdrawns, but thats just me. Thanks for the mirror.
batt002 said:
I would really like to know the reasons behind these withdrawns, but thats just me. Thanks for the mirror.
Click to expand...
Click to collapse
Because there was an issue they missed through QC. OTAs are always incremental/staged just in case something like this happens. This way only small number of devices are affected
bhake said:
Because there was an issue they missed through QC. OTAs are always incremental/staged just in case something like this happens. This way only small number of devices are affected
Click to expand...
Click to collapse
Yes I'm interested in that issue that was missed, but we'll never know
I instaled new Twrp blu spark 3.1.1.37 by eng stk.
Full wipe, clean flash the rom, full zip. Recovery ok. No need to reflash recovery..
All apps work for me. Root, everything.
piats said:
Hehe, time to give something back for this community :good::highfive:
Edit: remember to backup everything before flashing. I dirty flashed this ROM over stock OOS 4.1.5 via bluespark recovery v35 and it didn't boot back to system. So I booted back to recovery and somehow twrp asked password to decrypt data partition. I was decrypted before. So I installed stock recovery. Wiped everything and flashed this ROM via stock recovery. Everyhthing works now.
Click to expand...
Click to collapse
I dirty flashed full zip from encrypted 4.1.5 with TWRP 3.0.4-1 and everything went fine.
I am on OOS 4.1.5 . rooted with magisk and twrp recovery. I thought magisk would help hide root and update using OTAs. I did hide the oneplus update process in magisk hide and updates prompted a 45 mb download.(with root it would say go download the full zip). I downloaded the OTA . but as expected flashing it via twrp failed. is there any way to just do OTA update with root and twrp ? I did see some threads where people went to stock recovery and installed it. is that a simple procedure ?
I just updated to oxygen os 4.1.6 and I am unable to root my device, i was able to root on previous versions using the same supersu file but now it does not work, if anyone has a solution please help me out.
Olal said:
I just updated to oxygen os 4.1.6 and I am unable to root my device, i was able to root on previous versions using the same supersu file but now it does not work, if anyone has a solution please help me out.
Click to expand...
Click to collapse
Hi, try latest supersu 2.82 or magisk
Sent from my OnePlus3 using XDA Labs