Database Users

[Q] New update vs Root

I have a D803 (Rogers, Canada) running stock KK 4.4.2 rooted (4.2.2 was rooted and I kept it when upgrading to KK).
Now, a new update is available (with, among other goodies, Knock Code).
Phone notifies me an update is ready. I can download it but can't install because the installer stops and displays "root is suspected".
Anyone knows a way to install the update?
Do I have to "unroot" for real or can the installer be tricked into thinking the phone is unrooted (like some sort of temporary unroot).
Thanks!

alexvtr said:
I have a D803 (Rogers, Canada) running stock KK 4.4.2 rooted (4.2.2 was rooted and I kept it when upgrading to KK).
Now, a new update is available (with, among other goodies, Knock Code).
Phone notifies me an update is ready. I can download it but can't install because the installer stops and displays "root is suspected".
Anyone knows a way to install the update?
Do I have to "unroot" for real or can the installer be tricked into thinking the phone is unrooted (like some sort of temporary unroot).
Thanks!
Click to expand...
Click to collapse
Have you removed bloat/modified the system(xposed/mods) If so then you have to put everything back to stock
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

I am in the same boat. My phone is rooted and has no bloat but it took the Kit Kat update. Now that the knock code update is out, it won't let me take the update. I get the "suspected of rooting" error message too. Only difference is I am running some Xposed modules.
I disabled my Xposed modules but left everything installed. Rebooted and attempted the update again. Still the same problem.
Then I uninstalled Xposed and all its modules and still the same problem.
If you find out how to take the update, please up date this post so the rest of us know how as well.
Thanks
XxZombiePikachu said:
Have you removed bloat/modified the system(xposed/mods) If so then you have to put everything back to stock
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse

rezadue said:
I am in the same boat. My phone is rooted and has no bloat but it took the Kit Kat update. Now that the knock code update is out, it won't let me take the update. I get the "suspected of rooting" error message too. Only difference is I am running some Xposed modules.
I disabled my Xposed modules but left everything installed. Rebooted and attempted the update again. Still the same problem.
Then I uninstalled Xposed and all its modules and still the same problem.
If you find out how to take the update, please up date this post so the rest of us know how as well.
Thanks
Click to expand...
Click to collapse
everything needs to be completely stock so that you can ota, if it gives the suspected of rooting then the only way to ota is to flash a stock kdz via r&d/flash tool and then update

You mean using this thread to flash back to complete stock?
http://forum.xda-developers.com/showthread.php?t=2432476
Thanks
XxZombiePikachu said:
everything needs to be completely stock so that you can ota, if it gives the suspected of rooting then the only way to ota is to flash a stock kdz via r&d/flash tool and then update
Click to expand...
Click to collapse

rezadue said:
You mean using this thread to flash back to complete stock?
http://forum.xda-developers.com/showthread.php?t=2432476
Thanks
Click to expand...
Click to collapse
yes that's correct

Updating through the 'LG PC Suite' or 'LGMobile Support Tool' should work though

Yes, except the LG suite wants to flash the Bell version of the ROM and using the KDZ file, I can flash the Rogers version of the ROM.
JeffreyNijnatten said:
Updating through the 'LG PC Suite' or 'LGMobile Support Tool' should work though
Click to expand...
Click to collapse

Have stock with root and exposed and modded camera. Not risking the update. I just tap to install and then when prompted to continue, hit cancel.
Knock code does not offer me anything. So unless there is a good reason to have to re-configure the whole bloody phone ... this update will not be missed.

Have I killed my Nexus 2012?

Hi guys,long time lurker here.
I have recently tried to update my old Nexus 2012 to Kitkat, and messed it up!:crying:
I can only get into TWRP now, and only get roms on there via a USB OTG cable.
Thing is, i've tried loads of roms and they all seem to fail. I've obviously messed up somewhere, anyone give me any poiinters?
Cheers.
EDIT
Think I'm sorted - seems i can't update to Kitkat, I tried a 4.2 rom, and all is good.
Note to self - do more research before 'updating':silly:

seymour71 said:
Hi guys,long time lurker here.
I have recently tried to update my old Nexus 2012 to Kitkat, and messed it up!:crying:
I can only get into TWRP now, and only get roms on there via a USB OTG cable.
Thing is, i've tried loads of roms and they all seem to fail. I've obviously messed up somewhere, anyone give me any poiinters?
Cheers.
Click to expand...
Click to collapse
If you took an OTA with stock firmware and TWRP, that's the issue. You can't boot into the bootloader to flash stock?

kcipopnevets said:
If you took an OTA with stock firmware and TWRP, that's the issue. You can't boot into the bootloader to flash stock?
Click to expand...
Click to collapse
Cheers dude, I think I'm sorted now, albeit at a 4.2 rom. What's the easiest way to update to 4.4?

seymour71 said:
Cheers dude, I think I'm sorted now, albeit at a 4.2 rom. What's the easiest way to update to 4.4?
Click to expand...
Click to collapse
For stock KitKat, use Nexus Root Toolkit and flash the stock binary, and enable USB debugging! Toolkit really takes over so it's kinda one click.
For a ROM? Update TWRP, CWM, or PhilZ to the latest version and pick a ROM that suits your fancy! Good luck on your journey!

kcipopnevets said:
For stock KitKat, use Nexus Root Toolkit and flash the stock binary, and enable USB debugging! Toolkit really takes over so it's kinda one click.
For a ROM? Update TWRP, CWM, or PhilZ to the latest version and pick a ROM that suits your fancy! Good luck on your journey!
Click to expand...
Click to collapse
Ah yes, I tried the toolkit when I thought I'd furbared by tablet, I'll enable debbinging & give it another go.
Cheers.

You probably need to update your bootloader to the latest.
You could flash stock 4.2.2 with fastboot.... And when you reboot, it will give you the kit kat ota. Which will update your bootloader and leave you on 4.4.2. Then you just need to flash recovery and root again.

kj2112 said:
You probably need to update your bootloader to the latest.
You could flash stock 4.2.2 with fastboot.... And when you reboot, it will give you the kit kat ota. Which will update your bootloader and leave you on 4.4.2. Then you just need to flash recovery and root again.
Click to expand...
Click to collapse
Hmmm, just tried this, everything seemed to go well, but it hasn't given the option of an ota update when I've rebooted. It's still showing as as CyanogenMod Version too?

seymour71 said:
Hmmm, just tried this, everything seemed to go well, but it hasn't given the option of an ota update when I've rebooted. It's still showing as as CyanogenMod Version too?
Click to expand...
Click to collapse
Hi, seymour71...
If you're running Googles official factory stock Android 4.2, then you can download the relevant OTA update(s) from here, directly to your Nexus 7, and flash in CWM or TWRP.
You can find out the specifics of the ROM build number your currently running by going to SETTINGS>>ABOUT TABLET>>BUILD NUMBER on your Nexus 7.
You may need to upgrade incrementally, that is to say, from 4.2 to 4.3 (and their successive point updates) right through to the latest version, Android 4.4.2 (Build number: KOT49H).
NOTE: OTA UPDATES ONLY WORK WITH OFFICIAL UNMODIFIED FACTORY STOCK... If you're running a Custom 4.2 based ROM, then flashing them will fail.
Good luck.
Rgrds,
Ged.

GedBlake said:
Hi, seymour71...
If you're running Googles official factory stock Android 4.2, then you can download the relevant OTA update(s) from here, directly to your Nexus 7, and flash in CWM or TWRP.
You can find out the specifics of the ROM build number your currently running by going to SETTINGS>>ABOUT TABLET>>BUILD NUMBER on your Nexus 7.
You may need to upgrade incrementally, that is to say, from 4.2 to 4.3 (and their successive point updates) right through to the latest version, Android 4.4.2 (Build number: KOT49H).
NOTE: OTA UPDATES ONLY WORK WITH OFFICIAL UNMODIFIED FACTORY STOCK... If you're running a Custom 4.2 based ROM, then flashing them will fail.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Cheers dude. Just checked, the build number says: BeatMod CrystalClear v2.3
Android version is 4.2.2
I thought i'd just flashed it back to a 4.2 stock rom via the toolkit, but apparently not.

seymour71 said:
Cheers dude. Just checked, the build number says: BeatMod CrystalClear v2.3
Android version is 4.2.2
I thought i'd just flashed it back to a 4.2 stock rom via the toolkit, but apparently not.
Click to expand...
Click to collapse
"BeatMod CrystalClear v2.3"... Never heard of that one before. There are some pretty obscure ROMs out there. This one sounds like it has some sort of 'music' orientation.
Anyhow... it's a Custom ROM... and you wont be able to update it to 4.4.2 unless the developer has released a 4.4.2 version.
---------------------------------------------------------
Your best bet is to fastboot flash the official Google factory stock image for your specific Nexus 7(2012) model (WiFi only, or WiFi & 3G).
The Nexus 7(2012) factory image(s) can be found here...
https://developers.google.com/android/nexus/images#nakasi
Instructions on how to fastboot flash can be found here...
http://forum.xda-developers.com/showthread.php?t=1907796
Hope this helps.
Rgrds,
Ged.

Ah, it seems I didn't do it right properly first time.
I'm now on 4.2.2 with the build number JDQ39.
Would I be safe to flash a stock 4.4 rom using the toolkit now? It hasn't offered me an ota update - not yet, anyway.
Edit- It's doing it now, I think. Watch this space!

WARNING: Android 5.0 Bootloader and KitKat Compatibility

Android 5.0 (Lollipop) Bootloader and KitKat Compatibility​
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.​
Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Downgrading to KitKat also possible even with Lollipop Bootloader.
Bootloader:
A new Bootloader (BL) will almost certainly be is included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the Kernel DEVs can find a workaround.
Root: (DONE)
It may take some time to gain root access on Lollipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Chainfire releases Android 5.0 Root for Moto G (2013) (All Models)
In addition; apps that use root access in KitKat, require further development to have functional root access in Lollipop.
Xposed Framework:
Developer has said he will wait for CyanogenMod based on Lollipop before properly starting development of an ART version of Xposed. CM12 may take a few weeks to release. Expect to do without Xposed for at least a month, probably longer since root is also required (see above.) Related: Alternatives to popular Xposed Modules
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries. Obviously, you would not be able to restore a CWM / TWRP backup without a functional custom recovery; but even then, it is unlikely you will [not] be able to boot your KitKat backup. CWM unaffected, TWRP not fully supported yet.
Custom ROMs:
This is another area that could be affected by a new Bootloader. It is unknown if existing custom ROMs will require new Kernels / system changes in order to work with the new BL - something that could take days, weeks or months. CyanogenMod 12 (Lollipop) for Moto G (Falcon) now available and does not appear to require a new BL.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop for Moto G has performance issues, you may be unable to revert back to stock KitKat.​Possible solution:
Wait for a flashable zip [NOT OTA Update zip] of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change 'back and forth' between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels. Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader.

That is what I thought, since something like that happened because of the upgrade from JB to KK. Taking all of this into account, I'm not sure to upgrade immediately when the OTA comes out, maybe I'll try to still alive waiting for reviews from someone who dares to OTA right then.

You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.

nice info

lost101 said:
Android 5.0 Bootloader and KitKat Compatibility​
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Bootloader:
A new Bootloader (BL) will almost certainly be included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the kernel DEVs can find a workaround.
Root:
It may take some time to gain root access on Lolipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop has performance issues on Moto G, you may be unable to revert back to stock KitKat.
Alternative solution:
Wait for a flashable zip of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels.
Click to expand...
Click to collapse
UUUUUUHHHHHHHH iam afraight. a little. who needs bootloaders. i dont.

juanchotazo99 said:
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
Click to expand...
Click to collapse
Will you be able to wait when you see that little notification saying there's a new system update awaiting you?? I'll eat my nails until then!

Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
I don't think so....

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:

As always, very informative thread @lost101.

lost101 said:
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Click to expand...
Click to collapse
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.

Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
You need stock recovery and rid of xposedand any modules

MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.

Is stock recovery and stock firmware same? If not how do i get stock recovery back?

S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
How about if you are using Adaway?
I know this will change something to the file hosts.
Do you need to get this original hosts file as well?

Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:

MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
Almost always it is enough to flash only system img files without erasing userdara. It should rewrite system block so it becames stock

MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039

Drift0r said:
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Click to expand...
Click to collapse
You can try the guide I've done with some help from other users here at XDA...
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884

Lollipop 5.1.1 stock image is up !

Finally ! Straight from Google DEVS
"razor" for Nexus 7 [2013] (Wi-Fi) 5.1.1 (LMY47V)

Thank You

Just flashed it. I wasn't having any issues, but I hope it fixes problems for others.

just lou said:
Just flashed it. I wasn't having any issues, but I hope it fixes problems for others.
Click to expand...
Click to collapse
Can you check if the bootloader is still 04.05 or it changed?

I heard, it is the same

idCyber said:
Can you check if the bootloader is still 04.05 or it changed?
Click to expand...
Click to collapse
Its 4.05 bootloader still. Somehow in the zip its called bootloader-flo-flo-04.05.img
There's a new kernel, some changes in the source. Its compiled March 21
Not much else changed

Has any one got the ota yet ?

@Vkk187
ofc not.
Flash the stock image with NRT and check "dirty flash" and that will not delete your apps and data.

Yet to unlock my BL ...I know it's simple . Will do it some day [emoji18]

AonI updated to 5.1 rooted stock via TWRP a couple weeks ago.
Today I just got this update notification for 5.1
Is today's notification for 5.1.1? Because it only says 5.1
Do we have a rooted stock file we can flash in TWRP?

ymDroid said:
Do we have a rooted stock file we can flash in TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nex...my47v-root-t3098137/post60479181#post60479181

I just got the 5.1 update. It shows 5.1.1 as the Android version.
Sent from my BN Nook HD using XDA Free mobile app

I just completely flash-all every time a new build comes out as I do not know how to side load using NRT or TWRP (am I wasting my time on doing it this way). If someone could please explain to me how to side load I would be forever grateful. I have searched and cannot find clear instructions or walk through on side loading

Having read wugfresh page,it says Since lollipop,its hard to sideload OTA now. I myself try it last night with my rooted stock recovery,it fails to install the OTA from google,even if file has been downloaded automatically. Its harder to get OTA install smoothly nowadays especially if you on lollipop. No choice had full flash without wipe. And reroot again.
Sent from my Nexus 7

ksloh1 said:
Having read wugfresh page,it says Since lollipop,its hard to sideload OTA now. I myself try it last night with my rooted stock recovery,it fails to install the OTA from google,even if file has been downloaded automatically. Its harder to get OTA install smoothly nowadays especially if you on lollipop. No choice had full flash without wipe. And reroot again.
Sent from my Nexus 7
Click to expand...
Click to collapse
Actually, it's just as easy sideloading as it's always been. The difference is that you can't sideload an OTA (or receive one in any way) if you've done any kind of alterations to the system. This includes rooting and/or flashing custom recoveries and kernels. Even if you unroot there are still residue alterations in your system, meaning you'll have to do a full system flash anyway.
It's worth mentioning that unlocking your bootloader does not prevent installing an OTA.

How is this version running compare to the 5.0?

Jaylex31 said:
How is this version running compare to the 5.0?
Click to expand...
Click to collapse
Any versions of Android on the Nexus 7 2013 ran fine for me.

Galaxy Tab S2 (T817T) Marshmallow Update

I found this on T-Mobile's site stating the update would be available starting today. https://support.t-mobile.com/docs/DOC-23647 Don't have my tablet to confirm. Has anyone with this tab checked for the update to confirm?

Milly7 said:
I found this on T-Mobile's site stating the update would be available starting today. https://support.t-mobile.com/docs/DOC-23647 Don't have my tablet to confirm. Has anyone with this tab checked for the update to confirm?
Click to expand...
Click to collapse
Dowloading now, 1.02 gigs...

eric_mac said:
Dowloading now, 1.02 gigs...
Click to expand...
Click to collapse
Installing...

Thanks for confirming. I stumbled on the link just trying to see if I could find some eta on the update.

Just updated. Now time to root.

I saw this on T-Mobile's site a couple of days ago, but I'm on the fence about updating. I updated my Note 4 (910T) when MM came out and I'm used to it, but they removed the ability to alter the quick settings toggles (Samsung disabled system ui tuner) so you can no longer add hidden features like mobile data or VPN. While I can grudgingly live without it on the Note 4, I find it too handy to do without on the 817T. Unless someone finds a way around this, I'm staying put for the time being.

Just updated my T817T to MM.. thanks for the info. Updated and rooted as well with supersu 2.74

kingwicked said:
Just updated my T817T to MM.. thanks for the info. Updated and rooted as well with supersu 2.74
Click to expand...
Click to collapse
How did you root your T817T with MM? Did you already have TWRP and it was retained with the update and you just flashed SuperSu?

I flashed twrp 3.0.0.2 for t810 it works for marshmallow and then I flashed super su 2.74.
It was not retained after update. I flashed it via Odin again

kingwicked said:
I flashed twrp 3.0.0.2 for t810 it works for marshmallow and then I flashed super su 2.74.
It was not retained after update. I flashed it via Odin again
Click to expand...
Click to collapse
I had issues with xposed and the machine becoming unresponsive. Had to reinstall and root. Works fine without xposed.

hgill2412 said:
I had issues with xposed and the machine becoming unresponsive. Had to reinstall and root. Works fine without xposed.
Click to expand...
Click to collapse
I have no issues with xposed .works perfect for me with wanam's xposed V86 for MM

Success!
Since I had installed TWRP and rooted, I could not update to MM. I re-flashed back to stock 5.1.1 with Odin and then was able to update to MM.
After the update I flashed the T815 TWRP with Odin (make sure you don't auto-reboot and boot into TWRP right after flashing to make it stick). Then I flashed the SuperSu 2.76 ZIP from TWRP.
So I now have a stock rooted 6.0.1 ROM. Everything seems to work fine for me. I can use LTE and even enable the mobile hotspot.