Related
I have read several threads on debloating this device, including this really good one: http://forum.xda-developers.com/galaxy-tab-s/help/debloating-t2805503 . The info there that eliminating split-screen capability should be most useful!
However, I don't have enough experience to find the answer to my question from what I have read. If I use any of the relevant root tools to de-crap the machine, or if I just root, will I lose the ability to receive OTA updates? If so, is there any way to apply them short of waiting for someone to come out with a new ROM?
Is freezing with Titanium safe for this purpose, since nothing is removed? Or do I need to save the old stock ROM, and reload it, do the update, and then re-root and re-freeze everything?
Thank you for your indulgence, given that I'm sure that the answer is in several threads and I just don't know enough to identify it.
Root = no OTA, simple. Once an update comes out easiest thing to do is to download the new firmware from somewhere like Sammobile and flash using Odin, then re-root. Sammobile often releases the update before the OTA starts rolling out!
45 - Alba gu bráth
For titanium backup freezing just stops the apk from running and is safe because nothing is removed and when you install a new rom update, the things that were frozen will unfreeze since it requires root to freeze apps. Just follow what @killall said and that should do it. And if you root you can install twrp to backup your whole rooted rom as it was and restore back too it if you did something wrong while you were on the rooted rom.
killall said:
Root = no OTA, simple. Once an update comes out easiest thing to do is to download the new firmware from somewhere like Sammobile and flash using Odin, then re-root. Sammobile often releases the update before the OTA starts rolling out!
45 - Alba gu bráth
Click to expand...
Click to collapse
Doesn't flashing with Odin wipe data also, so it's not just simple re-rooting? Rooting doesn't prevent updating with Kies if I'm correct, does it matter whether you have custom recovery or not?
miloytyn said:
Doesn't flashing with Odin wipe data also, so it's not just simple re-rooting? Rooting doesn't prevent updating with Kies if I'm correct, does it matter whether you have custom recovery or not?
Click to expand...
Click to collapse
No, It should wipe the device's data.
I found a way to set my device status to official even though im rooted. Since I set the status to official I can check for updates without the custom software popup but I not tryed installing any updates since there are not any new updates atm.
kable said:
No, It should wipe the device's data.
Click to expand...
Click to collapse
I mean that of course it doesn't wipe your pictures and such, but flashing with Odin will wipe application data and restoring it from e.g. Titanium backup does take long time.
Here's hoping the custom ROM community picks up the slack and puts out a decent ROM this device sorely needs...
DUHAsianSKILLZ said:
I found a way to set my device status to official even though im rooted. Since I set the status to official I can check for updates without the custom software popup but I not tryed installing any updates since there are not any new updates atm.
Click to expand...
Click to collapse
What method did you use to root your Galaxy Tab S 8.4 SM-T705 LTE? And did you use CW or TWRP?
jadid said:
What method did you use to root your Galaxy Tab S 8.4 SM-T705 LTE? And did you use CW or TWRP?
Click to expand...
Click to collapse
I have a Galaxy tab s 10.5inch and rooted with cfautoroot and have twrp recovery installed. I used an xposed module called wanam xposed and changed my status to official. There is a ota update right now and Im scared to try the update becuase I dont know the risks. I have super su pro with survival mode on. Im not sure if its safe to do an ota update on rooted device as I dont want to brick it.
DUHAsianSKILLZ said:
I have a Galaxy tab s 10.5inch and rooted with cfautoroot and have twrp recovery installed. I used an xposed module called wanam xposed and changed my status to official. There is a ota update right now and Im scared to try the update becuase I dont know the risks. I have super su pro with survival mode on. Im not sure if its safe to do an ota update on rooted device as I dont want to brick it.
Click to expand...
Click to collapse
Thanks man, I followed your example and successfully rooted my device
What is xposed module called wanam xposed and what is it for?
jadid said:
Thanks man, I followed your example and successfully rooted my device
What is xposed module called wanam xposed and what is it for?
Click to expand...
Click to collapse
Yeah the module is wanam xposed and its for like customzing things such as hiding your carrier label and customize your lockscreen and nofications.
Do u know what the update changes?
I got my OP3 1-2 weeks . before i had a S4 (rooted). I'm really happy with this phone but i got some questions and problems.
1. When i video call via skype the camera will freeze in 50sec. when I switch the camera to the back and front it's fixed for 50 sec again and same thing happening again....
2. Rooting the OP3 is it safe to do ? And does someone got a guide for it ? I saw allot off them but I don't know which one works for Oxygen 3.2.1. I got some rooting experience with the S4 but rooting op3 is kinda different.
3. When i got a rooted op3 without a custom rom. Do i still get updates via System updates in the settings ?
Sorry for my bad English and thanks for reading.
1. Don't know
2. Yes, https://forums.oneplus.net/threads/...nlock-bootloader-flash-twrp-root-nandroid-efs
3. No after rooting you won't get updates
J_Dutch said:
1. Don't know
2. Yes, https://forums.oneplus.net/threads/...nlock-bootloader-flash-twrp-root-nandroid-efs
3. No after rooting you won't get updates
Click to expand...
Click to collapse
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.
crysen said:
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.
Click to expand...
Click to collapse
Ok, didn't know that. How do you install that?
J_Dutch said:
Ok, didn't know that. How do you install that?
Click to expand...
Click to collapse
Via TWRP both.
Here you can find the systemless SuperSU https://forums.oneplus.net/threads/guide-oneplus-3-how-to-unlock-bootloader-flash-twrp-root-nandroid-efs-backup-and-more.448149/
And here is systemless Xposed: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
crysen said:
Via TWRP both.
Here you can find the systemless SuperSU https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.448149/
And here is systemless Xposed: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
Seriously? I've been told several times installing a custom recovery and OTA is a no go...
But thanks, I'm still stock but I don't know for how long. I'm still a flashaholic inside.
crysen said:
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.
Click to expand...
Click to collapse
You are right that you will get a prompt for upcoming OTA updates.
But they won't install because your kernel and system are not stock.
My device is also rooted systemless and I can confirm that you will get an error inside TWRP
when trying to install the OTA patches.
When rooted, regardless which way, it is always necessary to flash the full rom zip.
So in the end @J_Dutch was right to say that you won't get updates
because you will always have to manually flash the full rom.
On the other hand, when somebody only uses TWRP (for backups for example) without modifying the system and kernel at all,
OTAs will work just fine.
AcmE85 said:
You are right that you will get a prompt for upcoming OTA updates.
But they won't install because your kernel and system are not stock.
My device is also rooted systemless and I can confirm that you will get an error inside TWRP
when trying to install the OTA patches.
When rooted, regardless which way, it is always necessary to flash the full rom zip.
So in the end @J_Dutch was right to say that you won't get updates
because you will always have to manually flash the full rom.
Click to expand...
Click to collapse
Oh thanks, I didn't know that, I would've flashed it via normal OTA after work otherwise
From the official thread, I've installed XposedInstaller_3.1.1.apk and successfully flashed xposed-v87-sdk23-arm64.zip via TWRP.
Xposed says no framework is installed. Is this common? I am using the correct files, yes?
typhoonikan said:
From the official thread, I've installed XposedInstaller_3.1.1.apk and successfully flashed xposed-v87-sdk23-arm64.zip via TWRP.
Xposed says no framework is installed. Is this common? I am using the correct files, yes?
Click to expand...
Click to collapse
What version of android are you running? If it's N then xposed isn't working yet. If it's MM then just flash xposed framework, then the apk, then activate the modules and reboot should work.
dladz said:
What version of android are you running? If it's N then xposed isn't working yet. If it's MM then just flash xposed framework, then the apk, then activate the modules and reboot should work.
Click to expand...
Click to collapse
I'm doing just that- isn't working. I even removed some system apps to give the partition some room because I got short write error a few times. No good.
typhoonikan said:
I'm doing just that- isn't working. I even removed some system apps to give the partition some room because I got short write error a few times. No good.
Click to expand...
Click to collapse
Are you on nougat
typhoonikan said:
I'm doing just that- isn't working. I even removed some system apps to give the partition some room because I got short write error a few times. No good.
Click to expand...
Click to collapse
As the others asked, are you on Nougat because if so, that's why. If I were you I'd use the Xposed uninstaller zip to uninstall that Marshmallow Xposed as you're not going to want to still have that when you install the Nougat one eventually. The Xposed app v3.1.1 doesn't need you to download and flash Xposed manually anyway. Once Xposed for Nougat is available, assuming it will be, then you just go to the Xposed app's Firmware tab while connected to the internet and it'll tell you if Xposed for Nougat is available. Of course, the app itself might need updating too.
If you look here https://source.android.com/source/build-numbers.html you can see what SKD level is equivalent to which Android version. The SDK23 Xposed you flashed is for Marshmallow. You need SDK24 for Nougat 7.x and SDK25 for Nougat 7.1.x.
Also, as soon as Nougat Xposed is released, I'm sure the thread title "[OFFICIAL] Xposed for Lollipop/Marshmallow [Android 5.0/5.1/6.0, v87, 2016/11/24]" will be changed to reflect Nougat compatibility.
roirraW "edor" ehT said:
As the others asked, are you on Nougat because if so, that's why. If I were you I'd use the Xposed uninstaller zip to uninstall that Marshmallow Xposed as you're not going to want to still have that when you install the Nougat one eventually. The Xposed app v3.1.1 doesn't need you to download and flash Xposed manually anyway. Once Xposed for Nougat is available, assuming it will be, then you just go to the Xposed app's Firmware tab while connected to the internet and it'll tell you if Xposed for Nougat is available. Of course, the app itself might need updating too.
If you look here https://source.android.com/source/build-numbers.html you can see what SKD level is equivalent to which Android version. The SDK23 Xposed you flashed is for Marshmallow. You need SDK24 for Nougat 7.x and SDK25 for Nougat 7.1.x.
Also, as soon as Nougat Xposed is released, I'm sure the thread title "[OFFICIAL] Xposed for Lollipop/Marshmallow [Android 5.0/5.1/6.0, v87, 2016/11/24]" will be changed to reflect Nougat compatibility.
Click to expand...
Click to collapse
dladz said:
Are you on nougat
Click to expand...
Click to collapse
dladz said:
What version of android are you running? If it's N then xposed isn't working yet. If it's MM then just flash xposed framework, then the apk, then activate the modules and reboot should work.
Click to expand...
Click to collapse
Sorry everyone- I got tired of having to restore/wipe/start fresh from various issues I was having for this. No- I am not on Nougat.
However, I WAS on Nougat! I downgraded because reasons- FFRK (game) has nougat issues and is unplayable until 7.1 comes, and being HTC, that might be a while. Also, the whole TWRP thing on Nougat (which may be resolved soon, though).
Anyway, I'm wondering if the fact that I was MM --> N --> MM has anything to do with this? I'm on base 1.96.617.20 currently.
I do plan to try again soon. I plan to uninstall some system apps, wipe caches, flash xposed, wipe caches, install xposed app, see where that takes me, in that order. Unless there is something better you recommend?
typhoonikan said:
I do plan to try again soon. I plan to uninstall some system apps, wipe caches, flash xposed, wipe caches, install xposed app, see where that takes me, in that order. Unless there is something better you recommend?
Click to expand...
Click to collapse
If in doubt, flash an entire RUU, re-flash the stable TWRP and the Marshmallow ROM you want, and this time I'd try letting the Xposed app install the proper Xposed zip itself. The one you said would be correct for this phone on Marshmallow, but it's just easier letting the app install the correct one.
Good luck!
roirraW "edor" ehT said:
If in doubt, flash an entire RUU, re-flash the stable TWRP and the Marshmallow ROM you want, and this time I'd try letting the Xposed app install the proper Xposed zip itself. The one you said would be correct for this phone on Marshmallow, but it's just easier letting the app install the correct one.
Good luck!
Click to expand...
Click to collapse
I actually just came from the RUU when I downgraded. I will post my results on my next attempts at this.
Could something from an installation of N have messed up any future installations of Xposed regardless of OS, or could the firmware have been the problem.
Xposed is 100% functional on MM so this should not be a problem, I can only imagine that something has been left behind.
Heres my walkthrough for installing Xposed and mods
Just incase you've missed something
http://forum.xda-developers.com/htc-10/how-to/walkthrough-screen-off-animation-using-t3384651
roirraW "edor" ehT said:
If in doubt, flash an entire RUU, re-flash the stable TWRP and the Marshmallow ROM you want, and this time I'd try letting the Xposed app install the proper Xposed zip itself. The one you said would be correct for this phone on Marshmallow, but it's just easier letting the app install the correct one.
Good luck!
Click to expand...
Click to collapse
dladz said:
Could something from an installation of N have messed up any future installations of Xposed regardless of OS, or could the firmware have been the problem.
Xposed is 100% functional on MM so this should not be a problem, I can only imagine that something has been left behind.
Heres my walkthrough for installing Xposed and mods
Just incase you've missed something
http://forum.xda-developers.com/htc-10/how-to/walkthrough-screen-off-animation-using-t3384651
Click to expand...
Click to collapse
I do believe you're right in that N has left something behind. I have a little more information to share-
I enjoy the HTC gallery and music apps, so I tried flashing them via the zip here. Turns out, via the log from flashing, this occurred (see below). After booting into the OS, the apps were no where to be found and not installed. It seems the system is not mounting. How though am I able to restore with backups in TWRP? Any possible causes (specifically from the N firmware) and fixes for this?
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Missing Sense Apps, Widgets, and Plugins
ROM Version : 1.1
ROM Author : topjohnwu
Device : HTC 10
Start at : Thu Dec 15 19:31:43 2016
Missing Sense Apps and Widgets
by @topjohnwu
>> Mounting partitions
mount: failed to mount /dev/block/bootdevice/by-name/system at /system: Device or resource busy
>> Installing HTC Gallery
>> Installing HTC Music
>> Installing HtcMusicWidget
>> Unmounting partitions
script result was [1.0]
Installer Sucessfull (Status 0)
End at : Thu Dec 15 19:31:44 2016
UPDATE:
I flashed ViperRom for Marshmallow. Decided to try xposed again while I was starting fresh- it worked! I'm not sure why it wouldn't work previously. The world may never know.
typhoonikan said:
UPDATE:
I flashed ViperRom for Marshmallow. Decided to try xposed again while I was starting fresh- it worked! I'm not sure why it wouldn't work previously. The world may never know.
Click to expand...
Click to collapse
which TWRP you on? 3.0.2-7?
wiQbold said:
which TWRP you on? 3.0.2-7?
Click to expand...
Click to collapse
3.0.2-4
typhoonikan said:
3.0.2-4
Click to expand...
Click to collapse
did you tried 3.0.2-6?
It worked because you full wiped and installed it properly. That's all..
Also, give thanks to people who thanked you lol..
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
nujackk said:
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
Click to expand...
Click to collapse
Just dismiss the notification.
rbox said:
Just dismiss the notification.
Click to expand...
Click to collapse
I've been doing that, just wondering if i can/should update ? Will It cause problems if i flash latest version?
got the same idea: just flash super su 2.79 sr3 should work?
That's what I'm thinking, just wanting rbox to confirm it shouldn't hose anything. I know some roms on phones don't work with latest versions. And since he is using such an old version, I'm think that might be the case here
Hmm i think i will try it next time. Create a backup and flash supersu.
Spillunke said:
Hmm i think i will try it next time. Create a backup and flash supersu.
Click to expand...
Click to collapse
flashing/updating SuperSU is not working and you will lose root
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
rainman74 said:
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
Click to expand...
Click to collapse
What FW where you on & what method did u try using ?
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
rainman74 said:
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
Click to expand...
Click to collapse
Although it is much more of a pain to do fresh installs. I think when dealing with root it should be more stable to mess with it that way.
One can also do the build.prop mod to stop updates if one wants to test older FW versions.
Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
First thanks for the link to the xposed fix:good: And now that you mention it I don't know why i didn't think of that sooner, should be relatively easy to just replace the files in the zip with 7zip DUH. Only problem is I have everything all setup perfect.
I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?
djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.
KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june
JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...
KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.
djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't
KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)
JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.
djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?