I generated Chainfire`s CF-Auto-Root, so you can try use it.
1. Download and unpack CFAR-taimen-default.zip.
2. Reboot your device into bootloader mode.
3. Install standart fastboot drivers.
4. Run "root.bat" file.
This batch file unlock your bootloader (if it`s not) and boot modified kernel.
Wait, when device automaticaly reboot. Then just install SuperSU apk.
Download: https://drive.google.com/open?id=0B4acSOboIe6RQXpYNVp5NXJ1Ync
I do not give any guarantees of it. If it causes bootloop - flash factory image.
Tell me if it works.
Tell me if it works.
Click to expand...
Click to collapse
LOL
Much wiser to simply wait for official post from Chainfire.
Born<ICs said:
Much wiser to simply wait for official post from Chainfire.
Click to expand...
Click to collapse
Yup. This method doesn't work. I already gave it a shot. SuperSU just states "Root undetected". At least I didn't get a bootloop...
Born<ICs said:
Much wiser to simply wait for official post from Chainfire.
Click to expand...
Click to collapse
Didn't @Chainfire retired?
Born<ICs said:
Much wiser to simply wait for official post from Chainfire.
Click to expand...
Click to collapse
lucky_strike33 said:
Didn't @Chainfire retired?
Click to expand...
Click to collapse
Yes he did just a week or so ago.
I'm pretty sure chainfire retired and we will have to wait for magisk now
Sent from my Pixel 2 XL using XDA-Developers Legacy app
bajasur said:
I'm pretty sure chainfire retired and we will have to wait for magisk now
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
And the magisk Dev just finally got the pixel one, so we maybe waiting awhile. I was thinking we might want to start a fund for either him or goodwin_c he's the one who built the unofficial versions of magisk most of this year for our og pixels. I have talked to him and he doesn't plan on getting one.
Firmware.mobi (Chainfire's site) has an option to automatically generate and download a CFAR package. Was the OP generated using this site? If not, someone should try that route.
Never mind. It was. Ignore me.
Still on a pixel xl 1. So sorry if thos is off base, but has anyone tried to use our method on this phone? Boot to the twrp image then flash Chainfires latest SU?
I am guessing it is TWRP that fails?
TonikJDK said:
Still on a pixel xl 1. So sorry if thos is off base, but has anyone tried to use our method on this phone? Boot to the twrp image then flash Chainfires latest SU?
I am guessing it is TWRP that fails?
Click to expand...
Click to collapse
There is currently no TWRP for this device.
TonikJDK said:
Still on a pixel xl 1. So sorry if thos is off base, but has anyone tried to use our method on this phone? Boot to the twrp image then flash Chainfires latest SU?
I am guessing it is TWRP that fails?
Click to expand...
Click to collapse
Twrp fails. SuperSU 2.82 SR1 boot to root fails.
lucky_strike33 said:
Didn't @Chainfire retired?
Click to expand...
Click to collapse
Apparently CCMT has been running SuperSU for the last couple years anyways: http://www.androidpolice.com/2017/10/03/chainfire-announces-end-involvement-supersu/
So it's possible that the CCMT team will update SuperSU for Pixel 2 devices.
arh2o said:
Apparently CCMT has been running SuperSU for the last couple years anyways: http://www.androidpolice.com/2017/10/03/chainfire-announces-end-involvement-supersu/
So it's possible that the CCMT team will update SuperSU for Pixel 2 devices.
Click to expand...
Click to collapse
Assuming they have the device?
arh2o said:
Apparently CCMT has been running SuperSU for the last couple years anyways: http://www.androidpolice.com/2017/10/03/chainfire-announces-end-involvement-supersu/
So it's possible that the CCMT team will update SuperSU for Pixel 2 devices.
Click to expand...
Click to collapse
They bought it a couple years ago, but Chainfire's still been actively developing with them, until the beginning of October when he finally "quit". He's still going to consult until the end of February though, so there might still be hope that he will be able to assist and speed things up for us! XDA Article About It Here
Boot to TWRP just fails in Fastboot. It just reboots the phone to bootloader. ?
Can confirm that this does NOT work. Will wipe your phone without giving you root. I have my bootloader unlocked as well. Seems we'll have to wait for a better solution.
Maybe it's just me but I feel like the title of this should be changed because it could be a bit misleading for many people. There is also already a topic for WIP Magisk so we shouldn't split topics on trying to get root into several areas.
Not So Pro said:
Maybe it's just me but I feel like the title of this should be changed because it could be a bit misleading for many people. There is also already a topic for WIP Magisk so we shouldn't split topics on trying to get root into several areas.
Click to expand...
Click to collapse
lol. there are lots of posts from people who have no clue what they're doing, posting guides like they know what they're doing. and just as many who don't have the device, saying 'try this!'
i dunno if any REAL devs even got this device or have any interest, seems like no.
but seriously, like we didn't try cf-auto-root yet? lol. lol...
Magisk and CF Auto Root are 2 different things but I do agree this one should be removed or even say WIP.
Related
I was wondering if there is any specific person or group we could reach out to to help root the Nexus Player. The bootloader is easily unlocked so all we need is root to enabled quite a few features that the NP needs (access to usb drives/keys from all apps, etc).
Chainfire is, of course, the obvious first contact, but is there anyone else that has shown Lollipop kernel experience to date on any other Nexus platforms?
You need to wait for the insecure-boot.img to be uploaded by someone.
Insecure boot.img
Insecure boot.img for Nexus Player tested and works, compiled from aosp_fugu-eng.
adb shell returns a #.
I imagine it is only a matter of time until we'll see TWRP for the NP. TWRP for the Nexus 9 was just released today.
guylamar2006 said:
Insecure boot.img for Nexus Player tested and works, compiled from aosp_fugu-eng.
adb shell returns a #.
Click to expand...
Click to collapse
can someone try this with supersu? Chainfire released 2.23 version for the 5.0 devices. I'd try it myself but my NP didn't manage to leave the warehouse yet.
I asked ChainFire on the official cf-autroot thread about autoroot for the NP earlier this week. He said he will getting a NP soon and would look at providing an autoroot package for it.
I like the TRWP approach a little more and may move to that for my Nexus 9.
IskiE
isketerol said:
I asked ChainFire on the official cf-autroot thread about autoroot for the NP earlier this week. He said he will getting a NP soon and would look at providing an autoroot package for it.
I like the TRWP approach a little more and may move to that for my Nexus 9.
IskiE
Click to expand...
Click to collapse
just released root myself :good:
bunchies said:
just released root myself :good:
Click to expand...
Click to collapse
Thanks !
But where ? I looked at your recent posts and didn't see anything downloadable.
mikereidis said:
Thanks !
But where ? I looked at your recent posts and didn't see anything downloadable.
Click to expand...
Click to collapse
Check the development section
About to release the latest OTA version any minute now
【Version】
V2.20.40.165_20160118_6541
【Model Name】
ZenFone2 ZE551ML
1.Fixed Miracast connection issue (with car screen)
2.Enhance Cell broadcast stability
3.Remove Dr. Safety
update via system update
Ota link
Here we go again.
http://fota.asus.com/delta_package/...19_2/WW_Z00A-20160107-20160118-20160119_2.zip
Wow Asus working overtime
Not really, this happened with last update too.
Someone tried rooting this system? I have bootloop after every attempt :/
I have noticed a better performance with release 2.20.40.164. The battery is not draining as in previous version. I am happy with this.
GorgorothGdynia said:
Someone tried rooting this system? I have bootloop after every attempt :/
Click to expand...
Click to collapse
Which method have you been using?
Method 1 from this guide http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 It always worked
GorgorothGdynia said:
Method 1 from this guide http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 It always worked
Click to expand...
Click to collapse
I have been using the Method 3 from this thread: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
The root persists after every OTA. So no need to un-root and root again, after any OTA.
rooting does well, but i getting bootloped when install xposed v79.
ps : currently rolled back to .156 using pre-root then updating again to .165
wish me luck
You mean 1 Click Root Tool for Zenfone 2? Thanks for info, I will try and inform the rest of the community
once again for everyone: ONE-CLICK root (Zenfone_quickroot.zip) doens't work on .165!
@piway I'm doing the same righ now haha...
piway said:
rooting does well, but i getting bootloped when install xposed v79.
ps : currently rolled back to .156 using pre-root then updating again to .165
wish me luck
Click to expand...
Click to collapse
I was about to update and install xposed 79. Thanks for the info.
GorgorothGdynia said:
You mean 1 Click Root Tool for Zenfone 2? Thanks for info, I will try and inform the rest of the community
once again for everyone: ONE-CLICK root (Zenfone_quickroot.zip) doens't work on .165!
@piway I'm doing the same righ now haha...
Click to expand...
Click to collapse
Yap thats the one. "Method 3 (1 CLICK ROOT TOOL)"
orlapa said:
I have noticed a better performance with release 2.20.40.164. The battery is not draining as in previous version. I am happy with this.
Click to expand...
Click to collapse
yep I noticed that too
GorgorothGdynia said:
You mean 1 Click Root Tool for Zenfone 2? Thanks for info, I will try and inform the rest of the community
once again for everyone: ONE-CLICK root (Zenfone_quickroot.zip) doens't work on .165!
@piway I'm doing the same righ now haha...
Click to expand...
Click to collapse
well..done for now with .164 :victory:
any news that xposed will running in this version? just in case i dont wanna to rolled back if get bootlop again haha
update : confirmed xposed v.79 work in this version .164
GorgorothGdynia said:
You mean 1 Click Root Tool for Zenfone 2? Thanks for info, I will try and inform the rest of the community
once again for everyone: ONE-CLICK root (Zenfone_quickroot.zip) doens't work on .165!
@piway I'm doing the same righ now haha...
Click to expand...
Click to collapse
This is confusing. As far as I know, the 1-click root package is called "ZenFoneRootKit.zip". This is what's described in Method 3.
I've never heard of "Zenfone_quickroot.zip"...
Now is Method 3 (ZenFoneRootKit) usable for .165 or is it not?
@Shaxine, thank you. Method 3rd (ZenFoneRootKit) from here http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 works good on .165.
This is s.h.i.t > http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 - bootloop is certain.
@piway thank you for info about xposed. Now we have to wait for an update xposed :<
They Should provide use Marshmallow Instead :'(
GorgorothGdynia said:
@Shaxine, thank you. Method 3rd (ZenFoneRootKit) from here http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 works good on .165.
This is s.h.i.t > http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 - bootloop is certain.
@piway thank you for info about xposed. Now we have to wait for an update xposed :<
Click to expand...
Click to collapse
Show some respect for the developers they are doing and sharing it for free in their free time if you don't like go make one for yourself and use it :silly::silly:
xposed v79 and root are both working for me on the 165 update. I did my typical dance to upgrade from 164 to 165:
Boot tethered twrp
Do a full backup
"install" the xposed-uninstaller
Reboot
Wait for apps to be optimized
Go into SuperSU and do full uninstall
Reboot
Let the upgrader install the update
Reboot and wait for apps to be optimized
Boot tethered twrp
Install SuperSU
Install xposed
Reboot
Wait for apps to be optimized
Because of the backup and optimizing apps three times, the whole process takes an hour or more. The tethered TWRP also requires a computer. This method of running TWRP gives me some of the benefits of an unlocked bootloader---easy rooting and easy install of xposed---without having to actually unlock my boot loader and (possibly) void my warranty. I can understand some people preferring the ease of the one-click type installers, but I've not had good luck with them.
I put up the tethered package I use in a post on the tethered TWRP thread. Some of the components are updated, and it seems more reliable than the original tethered package.
I can confirm that xposed 79 it's working. And I was able to update as usual.
Hey guys,
Anyone using systemless root with any versions of 6.0.1? I am still on 6.0.0 because I did not find a systemless root version except the original one posted on chainfire's site from late last year. I know the version of the systemless root matters as the kernel version matters for it to build the correct boot image.
I am not asking how to do it, just if anyone has successfully done this and which files (file names would be nice, so I can google 'em) did you use, to do it.
I have done a ton of searches all over the place and can not find one way or the other out there.
I don't want to hear a bunch of systemless vs non-systemless root stuff, please.
Thanks!
Hello old friend! I don't see many folks from the Atrix2 around anymore.
Sent from my Nexus 6P using XDA-Developers mobile app
jimbridgman said:
Hey guys,
Anyone using systemless root with any versions of 6.0.1? I am still on 6.0.0 because I did not find a systemless root version except the original one posted on chainfire's site from late last year. I know the version of the systemless root matters as the kernel version matters for it to build the correct boot image.
I am not asking how to do it, just if anyone has successfully done this and which files (file names would be nice, so I can google 'em) did you use, to do it.
I have done a ton of searches all over the place and can not find one way or the other out there.
I don't want to hear a bunch of systemless vs non-systemless root stuff, please.
Thanks!
Click to expand...
Click to collapse
I am using SuperSU 2.72 systemless with the latest stock 6.01. You could also use the newer BETA-SuperSU-v2.74-2-20160519174328.zip, I suppose.
mtnlion said:
Hello old friend! I don't see many folks from the Atrix2 around anymore.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Wow! Hey there, been a long time. Good to see you over here. Yeah I haven't seen too many of the old Atrix2 crew around the site for a while. It was almost as if most fell off the face of the earth.
This is my 4th Nexus device, and I will not go to anything else at this point. I am still working on the Ubuntu phone from a dev standpoint, plus a few things here with Android.
Hope to see you around here more often.
mtnlion said:
Hello old friend! I don't see many folks from the Atrix2 around anymore.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
meekrawb said:
I am using SuperSU 2.72 systemless with the latest stock 6.01. You could also use the newer BETA-SuperSU-v2.74-2-20160519174328.zip, I suppose.
Click to expand...
Click to collapse
Hey meekrawb thanks for the info. I went to chanfire's site an took a look and the only boot image for the 6P is the mb08k image, which is the 6.0.0 release, and not a boot image for the later releases including the newer 6.0.1. I am guessing that since it is the boot image that the actual release verision is arbitrary, but just want to be sure. I plan on trying it anyhow as I can just flash a proper image if it gets into a bootloop.
jimbridgman said:
Hey meekrawb thanks for the info. I went to chanfire's site an took a look and the only boot image for the 6P is the mb08k image, which is the 6.0.0 release, and not a boot image for the later releases including the newer 6.0.1. I am guessing that since it is the boot image that the actual release verision is arbitrary, but just want to be sure. I plan on trying it anyhow as I can just flash a proper image if it gets into a bootloop.
Click to expand...
Click to collapse
You don't need those special boot images anymore. When you flash the zip it automatically patches your boot.img.
This is the thread to follow: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
mtnlion said:
Hello old friend! I don't see many folks from the Atrix2 around anymore.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I joined this forum on 21-02-2011 when I received the first Atrix 4G.
Asus has released a small update of around 80meg, security patch level now July.
If not for OS update, atleast ASUS is keeping our phone's security up-to-date by giving monthly security patches
Fix APP2SD issue? why fix it even though they'll remove this capability on MM?
for those of you wondering what are the release notes, here it is:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=87445&extra=page=1&filter=typeid&typeid=199
Can someone post link for OTA for manual flash?
Wysłane z mojego HTC One_M8 przy użyciu Tapatalka
Flynhx said:
Fix APP2SD issue? why fix it even though they'll remove this capability on MM?
for those of you wondering what are the release notes, here it is:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=87445&extra=page=1&filter=typeid&typeid=199
Click to expand...
Click to collapse
Maybe M is not coming anytime soon
ZE551ML from 184 to 194
http://fota.asus.com/delta_package/...160715/WW_Z00A-20160504-20160713-20160715.zip
Flynhx said:
Fix APP2SD issue? why fix it even though they'll remove this capability on MM?
for those of you wondering what are the release notes, here it is:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=87445&extra=page=1&filter=typeid&typeid=199
Click to expand...
Click to collapse
Because as hard as it is for you to believe, some people wont upgrade to MM. They still need to support them.
Sent from my ASUS_Z00A using Tapatalk
dan8541 said:
Maybe M is not coming anytime soon
Click to expand...
Click to collapse
Yeah your right, they've just give us a hint with this OTA that ZE551ML/ZE550ML MM Final will take a long time to release
kenbo111 said:
Because as hard as it is for you to believe, some people wont upgrade to MM. They still need to support them.
Click to expand...
Click to collapse
Zenfone 2 ZE551ML/ZE550ML users have been supporting this device for 1 year & 4 months already, as if it is one of the best selling flagship for the year 2015 and yet Asus turned down its users for just a simple update. Intel SOC they say? Zenfone Zoom also has Intel Chipset and they've release MM earlier.
Flynhx said:
Yeah your right, they've just give us a hint with this OTA that ZE551ML/ZE550ML MM Final will take a long time to release
Zenfone 2 ZE551ML/ZE550ML users have been supporting this device for 1 year & 4 months already, as if it is one of the best selling flagship for the year 2015 and yet Asus turned down its users for just a simple update. Intel SOC they say? Zenfone Zoom also has Intel Chipset and they've release MM earlier.
Click to expand...
Click to collapse
Not being argumentative but I'm not sure what you mean by "turned down its users for just a simple update"
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Not being argumentative but I'm not sure what you mean by "turned down its users for just a simple update"
Click to expand...
Click to collapse
Well as you can see, many Zenfone 2 Intel users are frustated for the delayed response of just a simple update(i meant MM Final), that already has been using by many other 2014 Smartphone variants since May(eg: Galaxy S5, Xperia Z3).
I'll be lying if i say i'm not waiting for MM update. but when i think that i had this phone for 15 months and or works really fine with lollipop and i know for a fact that they will release MM for it i know for sure that I'll keep using out for another year.
Sent from my ASUS_Z00AD using XDA Premium HD app
I have rooted my device with method 3. Is it safe to install the update without uprooting first?
perama said:
I have rooted my device with method 3. Is it safe to install the update without uprooting first?
Click to expand...
Click to collapse
I'd like to know this as well please. I'm rooted so can I just go ahead and apply this OTA or ? Thank you.
Sent from my ASUS ZenFone 2
xuggs said:
I'd like to know this as well please. I'm rooted so can I just go ahead and apply this OTA or ? Thank you.
Click to expand...
Click to collapse
I have applied two OTA updates since I rooted. Yeah, go ahead. :good:
Hi,
I have my Zenfone 2 rooted, with xposed installed and bootloader unlocked with TWRP (3.0) installed. I know that I have to uninstall xposed framework, and root, but I never had my bootloader unlocked with stock ROM, and I'd like to update. I can't seem to find an answer in the forum, so I'm asking here. Will it work directly from the notification if xposed and root are removed ? If not can i sideload it from adb into the twrp adb sideload ? If not can I just fastboot flash the recovery to be able to install it ? I don't really need to be unlocked on this phone anymore but I don't want to flash the raw firmware, because it's going to take a long time to reinstall everything and set everything up properly. So how am I supposed to do it ? Thanks
mickey36736 said:
ZE551ML from 184 to 194
http://fota.asus.com/delta_package/...160715/WW_Z00A-20160504-20160713-20160715.zip
Click to expand...
Click to collapse
Thanks for this. I have successfully installed it, so far everything is working smoothly!
miniGAMER01 said:
Hi,
I have my Zenfone 2 rooted, with xposed installed and bootloader unlocked with TWRP (3.0) installed. I know that I have to uninstall xposed framework, and root, but I never had my bootloader unlocked with stock ROM, and I'd like to update. I can't seem to find an answer in the forum, so I'm asking here. Will it work directly from the notification if xposed and root are removed ? If not can i sideload it from adb into the twrp adb sideload ? If not can I just fastboot flash the recovery to be able to install it ? I don't really need to be unlocked on this phone anymore but I don't want to flash the raw firmware, because it's going to take a long time to reinstall everything and set everything up properly. So how am I supposed to do it ? Thanks
Click to expand...
Click to collapse
from my experience, yes you can.
as long you enable all system app(and have all system apps) to avoid any issues.
make sure you uninstall BusyBox first.
Iqballoon said:
from my experience, yes you can.
as long you enable all system app(and have all system apps) to avoid any issues.
make sure you uninstall BusyBox first.
Click to expand...
Click to collapse
I read that i needed to edit the script file for TWRP to install it, do I still have to do it ? Thanks for the answer
It's weird. I am rooted and I took the OTA update. It gave an error when installing but it said it reverted to original configuration. Now when I check for updates, it shows no updates and I am still on 184. How can I take the OTA update again? I don't see the OTA update in the /cache folder either. Thank you.
miniGAMER01 said:
I read that i needed to edit the script file for TWRP to install it, do I still have to do it ? Thanks for the answer
Click to expand...
Click to collapse
U need to remove assertions from first lines before mounting system.
Wysłane z mojego ASUS_Z00AD przy użyciu Tapatalka
Got a message from Google Pay saying that my phone is rooted or is running uncertified software.
I have a T-Mobile variant that I converted , without root, to international. Anyone else see this issue?
Read. This is an old problem for years. Is your bootloader unlocked? Not rooted? Yes this breaks GPay. Hence, Magisk, root, systemless and Hide.
Easy fix.
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
coolmaster121 said:
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
Click to expand...
Click to collapse
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
plasmamax1 said:
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
Click to expand...
Click to collapse
Thanks for the suggestion.
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
coolmaster121 said:
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
Click to expand...
Click to collapse
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
p51d007 said:
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
Click to expand...
Click to collapse
It was a zip I downloaded and did a local update.
Caltinpla said:
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Click to expand...
Click to collapse
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
Yep
No, works fine. But I don't have a converted variant - all stock.
If you go back to stock as it is with T-variant (search for MSM tool), is it certified again?
https://forum.xda-developers.com/showpost.php?p=80844361&postcount=7
noideas4thisname said:
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
Click to expand...
Click to collapse
Nope, I tried everything I heard of but nothing worked. Hopefully, OP releases an update with the fix soon!