Related
Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4
Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app
You just need to have the stock recovery to receive OTAs.
Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4
Takes 10 seconds to reflash the stock recovery.
UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
It was common on other platforms I've used, but I don't know about here.
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.
phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.
TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.
Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)
phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?
Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.
If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?
I have 5.01 and I want to update to 6.01. I want to wipe it clean. Got factory image from Google site.
What's the difference between the OTA and factory downloads?
I can just flash the factory in TWRP right? Will I lose root, or will TWRP ask if I want to keep root?
I still have boot loader unlocked.I just can't remember for the life of me, haven't done flashing etc in a few years.
Thanks!
So...not a single person can tell me if I lose root, or if TWRP will re-root?
Please?
N7 is no longer supported by Google and there will be no more OTA.
You can't flash the entire factory image directly from TWRP (but it is doable).
When you flash the factory image, you will lose root, TWRP and all your data.
NRT can simplify flashing, rooting and restoring TWRP.
You have unlocked boot loader
Just fastboot flash all as yiu want clean install
After that fastboot flash twrp
After that flash superSU
Done.
No need for any toolkit's, try to stay away of them and do it manually.
Sent from my XT1565 using Tapatalk
k23m said:
N7 is no longer supported by Google and there will be no more OTA.
You can't flash the entire factory image directly from TWRP (but it is doable).
When you flash the factory image, you will lose root, TWRP and all your data.
NRT can simplify flashing, rooting and restoring TWRP.
Click to expand...
Click to collapse
I know it isn't supported anymore. They still have the image's though.
Im just confused... Long time ago when I was really into all this, I just went to Googles page, downloaded the .zip and flashed it in TWRP. Now, the Google page is different and there isn't just 1 anymore. Can I just open the factory image and unzip the update part and flash that in TWRP?
The OTA files are only for updating from version to version correct? Can't go from what I'm on, 5.01 to the current 6.1 right? That's what I talking about and why I'm so confused now
Googles page used to have the OTA zip to update from prior newest to newest(5.0 to 5.01 for example) but than they also had the full OTA so you could do a 4.0 to 5.1 or whatever. Why they change the site? Which one do I use now to go from my 5.01 to current 6.1?
atifsh said:
You have unlocked boot loader
Just fastboot flash all as yiu want clean install
After that fastboot flash twrp
After that flash superSU
Done.
No need for any toolkit's, try to stay away of them and do it manually.
Click to expand...
Click to collapse
That's the pronlem, normally yes I would do that no problem. I'm in the middle of upgrading my PC after had a surge or something and fried my ****.
That's why I want to do it via TWRP like I always did before. Every time TWRP asked if I wanted to retain root after updating also. So what in the world happened in the last year that It doesn't seem like I can now? Like I said above, I can't find a full update OTA on!y the incremental OTAs...
Syntax323 said:
I know it isn't supported anymore. They still have the image's though.
Im just confused... Long time ago when I was really into all this, I just went to Googles page, downloaded the .zip and flashed it in TWRP. Now, the Google page is different and there isn't just 1 anymore. Can I just open the factory image and unzip the update part and flash that in TWRP?
The OTA files are only for updating from version to version correct? Can't go from what I'm on, 5.01 to the current 6.1 right? That's what I talking about and why I'm so confused now
Googles page used to have the OTA zip to update from prior newest to newest(5.0 to 5.01 for example) but than they also had the full OTA so you could do a 4.0 to 5.1 or whatever. Why they change the site? Which one do I use now to go from my 5.01 to current 6.1?
That's the pronlem, normally yes I would do that no problem. I'm in the middle of upgrading my PC after had a surge or something and fried my ****.
That's why I want to do it via TWRP like I always did before. Every time TWRP asked if I wanted to retain root after updating also. So what in the world happened in the last year that It doesn't seem like I can now? Like I said above, I can't find a full update OTA on!y the incremental OTAs...
Click to expand...
Click to collapse
Ok yes that's possible
If you have twrp already
Check development forum and choose one of the ROM.
Download it to your tablet plus gapps
Wipe system, cache and data leaving internal storage.
Flash ROM reboot, come back to twrp and flash gapps. ( Can do ROM + Gapps in one go)
Download SuperSU and flash to get root.
You can't flash stock image / OTA via twrp.
While you're doing all this try the 7.0 ROM its good enough now.
atifsh said:
Ok yes that's possible
If you have twrp already
Check development forum and choose one of the ROM.
Download it to your tablet plus gapps
Wipe system, cache and data leaving internal storage.
Flash ROM reboot, come back to twrp and flash gapps. ( Can do ROM + Gapps in one go)
Download SuperSU and flash to get root.
You can't flash stock image / OTA via twrp.
While you're doing all this try the 7.0 ROM its good enough now.
Click to expand...
Click to collapse
Ahhh what happened??? Why can you not flash them with TWRP???
Thats what I used to do no problem. Not referring to custom roms either.
I am wanting stock rooted.
I used to download the update when one was released from Google's site, put the update.zip in main directory, go in recovery and flash update.zip. TWRP would ask me if I wanted to keep root, I say yes, reboot, update installs... than i'm on the new Android version still rooted.
How is that not possible now?
I am so annoyed... I never had to go through ADB or fastboot to update to latest. I did everything on my N7, it kept root for me and everything.
I feel so dumb right now its ridiculous lol
So than what way can I go about updating my N7 2013 Wifi, which I currently have 5.01. I am Rooted w/ unlocked bootloader.
What is the best way not using ADB, or a PC at all for that matter to update to the latest, 6.01. If possible, how can I keep root, if not i'm not worried about it, i'll just re-root myself.
I appreciate all the responses, sorry if i'm just being an idiot. I just know for a fact I never had to use ADB or my PC to update and keep root...
I'm not familiar with Stock OTA done with twrp (if that's even possible)
Already told you get a custom ROM, get the one mostly stock or if there's a stock ROM in zip format available.
In future you might need to update that bootloader of yours for newer ROMs
Sorry if this sounds harsh why are you so into keeping root as you can't do it again? It's simple as flashing SuperSU. Root method changed after 6 you cant have old methods with 6.
Best bet for you at the moment.
http://forum.xda-developers.com/showthread.php?t=3219148
Sent from my XT1565 using Tapatalk
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Cyber Akuma said:
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Click to expand...
Click to collapse
If you have twrp installed it wont update the firmware only software. You need to flash firmware seperatly with fastboot.
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Cyber Akuma said:
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Click to expand...
Click to collapse
Correct.:good:
Can somebody please explain how to flash the firmware with fastboot?
So I have to flash the OTA with TWRP, afterwards I have to extract the firmware file out of the OTA.zip and flash it with fastboot. But which commands are necessary in fastboot?
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
kjjejones42 said:
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
Click to expand...
Click to collapse
Thats not true. You flash in ruu mode when S - ON. If your are S - Off you can do it from download mode. I think you are a little confused with that thread. Those firmwares are modified and for S -Off phones only.
yldlj said:
Thats not true. You flash in ruu mode. If soff you can do it from download mode.
Click to expand...
Click to collapse
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
kjjejones42 said:
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
Click to expand...
Click to collapse
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
yldlj said:
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
Click to expand...
Click to collapse
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
kjjejones42 said:
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
Click to expand...
Click to collapse
Correct. Also unmodified boot. But if your flashing unmodified system image, boot and stock recovery you may aswell just boot to android and take the ota.
Hi,
Problem starting oneplus 3, let me explain.
1) purchased oneplus3, 4 months ago.
2) Rooted,updated oxygen 3.2.8 with TWRP recovery3021 and super SU 2.74-2
3) updated oxygen4.00 with twrp32128 and super SU 2.79SR2 everything was fine.
4) Received OTA update through VPN for oxygen 4.0.1 (30mb), installed but unable start instead it was always going into twrp mode.
5) i changed twrp recovery back to 3021 and install stock oxygen 3.2.8,was working fine.
6) Now i wanted to UNROOT the device and back to stock so that i can get OTA Oxygen 4 and 4.0.1.
7) i followed steps below,
a) downloaded oxygen 3.2.1 and stock recovery.img
a) fastbootloader, and connect device.
b) fastboot devices
c) fastboot fastboot flash recovery recovery.img
d) fastboot oem lock - when i used this command and accept YES, screen got black and no further instruction for ADBsideload.
8) i used to restart the device in recovery but black screen, fastboot loader working.
FASTBOOT MODE
PRODUCT NAME - ....
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - .....
SECURE BOOT - enabled
DEVICE STATE - locked
9) and if i start the device in normal it asked for screen pattern lock but my existing unlock pattern doesnt work.
10) by using all the chance for screen pattern unlock it showed DECRYPTION UNSUCCESSFULL, clicked on RESET PHONE but again screen black in recovery mode.
11) NOW if i start my device it again shows DECRYPTION UNSUCCESSFULL and asking for RESET PHONE......
What to do now.....
regards,
Zahir
use the mega unbrick guide method 2, always work
Don't panic mate!
mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
Thanks mirko8054, I will let you know soon......
mirko8054 said:
use the mega unbrick guide method 2, always work
Click to expand...
Click to collapse
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
mirko8054 said:
Device is back to stock, this method is used by One plus asstance for unbrick hard bricked device by remote control your PC. Then device is back to completly stock. No root no custom recovery etc. You Can now use OTA for update or using adb sideload or manually flash the entire ROM from sdcard. Thank you for appreciate :good:
Click to expand...
Click to collapse
thanks a lot, I will do accordingly.
samadayesha said:
thanks a lot mirko8054, my oneplus 3 live again, using mega unbrick guide method 2.
appreciated.
at present oxygen3.1.2
how to install latest OTA since it is not showing any update by SYSTEM UPDATES.
my oem lock. I don't know if twrp installed.
how can I check if still my device is rooted.
I don't want to root it, just need OTA update directly.
kindly let me know the steps to update the device by oxygen4.
Many thanks
Zahir
Click to expand...
Click to collapse
just wanted to highlight the things you did that caused the issue
1- flashing the stock rom through twrp, it's possible specially with the latest TWR0-11 but not advisable, you better always flash stock recovery and then sideload rom (full rom not update) and then fast boot TWRP back and reflash root... any other method always causes issues...
2- the 30mg updates do not work on a rooted device
3- unrooting without immediately sideloading rom will always cause the black screen and loop to recovery, it's not required to unroot unless you want to go back to full stock experience...
4- this the biggest problem you made, you relocked the devices bootloader, you also did it while the device has a lot of issues (some mentioned above) so the device bricked instantly, if you are planning on unlocking the device again ...NEVER NEVER relock the device again , there's no need to do that , all you need to do to go back to a full stock experience is to wipe everything in TWRP , flash stock recovery then wipe everything again from there, then sideload full rom (latest stable version) , then for good majors in the new rom recovery wipe everything agian and boot to system and from system do a factory reset. then recharge your device to 100% and re encrypt it if it's not...after that you're 100% on a full stock exerience and will receive ota and it'll work... and at that state only (without root or TWRP) you can relock the bootloader (which is gain not necessary at all, there's no benefit to it)
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?