Related
So I'm running OOS 3.2.6. which is rooted. In the software update it shows 3.2.7 (1.3GB) available for download but it also says "Root detected, downloading full upgrade. Note: your device will be unrooted." So if i download and install this will it work ? Also, whats the best way to install official updates on a rooted OOS ?
You need clean install of oxygen before you can update regardless, just have to reflash su again afterwards and any kernels xposed you use.
MM MaD said:
So I'm running OOS 3.2.6. which is rooted. In the software update it shows 3.2.7 (1.3GB) available for download but it also says "Root detected, downloading full upgrade. Note: your device will be unrooted." So if i download and install this will it work ? Also, whats the best way to install official updates on a rooted OOS ?
Click to expand...
Click to collapse
You can easily install it, but after the download su will be removed, so you will have to reflash it.
MM MaD said:
So I'm running OOS 3.2.6. which is rooted. In the software update it shows 3.2.7 (1.3GB) available for download but it also says "Root detected, downloading full upgrade. Note: your device will be unrooted." So if i download and install this will it work ? Also, whats the best way to install official updates on a rooted OOS ?
Click to expand...
Click to collapse
I'd recommend flashing stock recovery before downloading the OTA update as twrp "sometimes" fail to flash OTA updates. Also flashing the 1.3 gb full update will remove your root. You'll have to flash supersu again for root. And you'll have to do this everytime an OTA comes.
The best way to install official updates on rooted phone is to download the patch only file for 3.2.7 and flash it via twrp. The patch file will be around 40-50MB and it is available somewhere in the XDA threads. Search for it.
MM MaD said:
So I'm running OOS 3.2.6. which is rooted. In the software update it shows 3.2.7 (1.3GB) available for download but it also says "Root detected, downloading full upgrade. Note: your device will be unrooted." So if i download and install this will it work ? Also, whats the best way to install official updates on a rooted OOS ?
Click to expand...
Click to collapse
Best way is to download OTA update from oneplus forum instead of complete ROM and just flash update
AJay27 said:
I'd recommend flashing stock recovery before downloading the OTA update as twrp "sometimes" fail to flash OTA updates. Also flashing the 1.3 gb full update will remove your root. You'll have to flash supersu again for root. And you'll have to do this everytime an OTA comes.
The best way to install official updates on rooted phone is to download the patch only file for 3.2.7 and flash it via twrp. The patch file will be around 40-50MB and it is available somewhere in the XDA threads. Search for it.
Click to expand...
Click to collapse
I did try that for the 3.2.7 update. Dirty flashed the OTA patch but it didn't seem to work. It's still 3.2.6
MM MaD said:
I did try that for the 3.2.7 update. Dirty flashed the OTA patch but it didn't seem to work. It's still 3.2.6
Click to expand...
Click to collapse
Wipe the system partition. Flash the 3.2.6 full update + ota patch together.
AJay27 said:
Wipe the system partition. Flash the 3.2.6 full update + ota patch together.
Click to expand...
Click to collapse
You can use flashfire app to flash the new update.
CHAKREKEVIN said:
You can use flashfire app to flash the new update.
Click to expand...
Click to collapse
Haven't tried it before but thanks for letting me know.
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
I'm not sure, but, you can just flash the ota in twrp and make sure to flash the twrp img after flashing the ota. And, always make a twrp backup
AFAIK you need stock recovery for OTA to work (not 100% sure).
If downloading whole 1.4GB ROM is not a big issue, it's safer to dirty flash the whole ROM. Otherwise you could flash back stock recovery, install small OTA, then flash TWRP again. A bit more work, but less downloading.
Sent from my OnePlus 3 using Tapatalk
This question doesn't belong in this section. @Stephen please move this to the Q&A section. Thanks.
DroidJay123 said:
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
Click to expand...
Click to collapse
Let me make it clear, the full rom flash is a better option and you can do so from twrp. You would not loose twrp after the flash and need not flash the recovery again. SuperSU/Magisk flash is optional after the ROM flash. I see that you are running 3.0.4-1 which is a 7.1.1 compatible TWRP so there is no need to worry of any data loss. TWRP is also able to flash the OTA's provided you have not made any changes to your system partition and have remained unrooted.
You can come to General / OOS thread and ask there for further understanding :fingers-crossed:
You can flash OTA as long as your kernel is on default, what I mean is stock/untouched which is basically same situation as yours since youre unrooted. ? So yes you can flash OTA no need for full flash
If me, i like waiting full ROM zip release and do clean install.
Sometimes, flash OTA getting error (cause root, bla bla bla hahaha )
Yeah, it could be lazy gonna install back all apps at least you backup it
My advice, if you update same Android version, no problem to do a dirty flash (same ROM like LOS 14 to LOS 14, but if different ROM, i suggest better do clean install)
But if different version, mean 7.0 to 7.1.1, better clean install (dirty also no problem, but wonder in future got problem)
But hey, different people, different way right? This just my 2cent
It is my understanding that when moving from whole version number changes (6 to 7, 7 to 8) etc that a clean install is definitely way to go but even from 7.0 to 7.1? Also when you download the OTA, is the file saved somewhere so you can then locate it in TWRP for flashing? I don't want to allow the system to install the ota automatically correct?
DroidJay123 said:
Hello all-
I have looked everywhere for clarification on this to no avail. I am currently UN-rooted, Unlocked Bootloader & TWRP (OOS 4.0.3, 12/1/16 Android Security patch). Can I take the OTA for OOS 4.1.3 or will that make me lose TWRP? I know there are instances when you can take the OTA and where you have to flash the entire ROM but I can't locate the differences and which route I need to take? Please advise if you know this answer.
Thank you!
Click to expand...
Click to collapse
It is best to clean flash if you've major upgrade like 6->7 or 7>8 something like that but if as your question you're still on marshmallow so you can flash OTA zip through twrp and make sure after OTA you've to flash twrp again to maintain it. If the system shows OTA it can't flash it via open recovery on twrp, you must have stock recovery to do it.
This thread is not for ROM development. Please get a mod move this thread to the Q&A section.
Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help
Kap_Tutan said:
Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help
Click to expand...
Click to collapse
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Jimi Mack said:
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Click to expand...
Click to collapse
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.
BtbN said:
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.
Click to expand...
Click to collapse
I downloaded the nougat april security patch of RETAIL. What do you mean by this "But generally you should install the stock version you originally had on your device, and then update from there"!
And is the retail april is working with my reteu dual sim? Do i still able to receive ota uodate when i flash the april patch?
Kap_Tutan said:
I downloaded the nougat april security patch of RETAIL. What do you mean by this "But generally you should install the stock version you originally had on your device, and then update from there"!
And is the retail april is working with my reteu dual sim? Do i still able to receive ota uodate when i flash the april patch?
Click to expand...
Click to collapse
I have no idea in what channel a phone will end up with the generic RETAIL images. I just did a dump of every single partition on my phone before I installed custom stuff, so I can always get back to how it was originally, and OTA from there.
BtbN said:
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.
Click to expand...
Click to collapse
Below is a link on how to properly downgrade and then be able to take OTA.
---------- Post added at 07:22 AM ---------- Previous post was at 06:54 AM ----------
[/COLOR]
Kap_Tutan said:
Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help
Click to expand...
Click to collapse
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118[/QUOTE]
Actually this is my first non-samsung phone. That's why totally noob in recovering my phone and revert back to stock. Please sorry for such a noob
Kap_Tutan said:
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118
Click to expand...
Click to collapse
Actually this is my first non-samsung phone. That's why totally noob in recovering my phone and revert back to stock. Please sorry for such a noob[/QUOTE]
No problem... any time you change a phone I always suggest to really look at the Guides and Discussion section and get to know the phone well before jumping in and hacking it.. Plus Moto did not make this one as simple to flash and recover as some of their others.
Good Luck.
Jimi Mack said:
Below is a link on how to properly downgrade and then be able to take OTA.
---------- Post added at 07:22 AM ---------- Previous post was at 06:54 AM ----------
[/COLOR]
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118
Click to expand...
Click to collapse
FYI link is broken.
ViperX85 said:
FYI link is broken.
Click to expand...
Click to collapse
Sorry, try this one...
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Jimi Mack said:
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Click to expand...
Click to collapse
Is this image signed?
Srandista said:
Is this image signed?
Click to expand...
Click to collapse
As far as I Moto has not released any signed firmware for the Addison.
Just flash this with RSD lite and you`ll have 7.1.1 with aug patch )
St.Noigel said:
Just flash this with RSD lite and you`ll have 7.1.1 with aug patch )
Click to expand...
Click to collapse
Flashing that on my reteu device resulted in a bootloop with the phone playing the "Hello Moto" sound over and over again.
I could flash LineageOS over it and it worked fine, but it did not give me a working stock OS.
BtbN said:
Flashing that on my reteu device resulted in a bootloop with the phone playing the "Hello Moto" sound over and over again.
I could flash LineageOS over it and it worked fine, but it did not give me a working stock OS.
Click to expand...
Click to collapse
You can try to do next:
1. Wipe everything (incl internal storage with TWRP)
2. Format (not wipe) data with TWRP
3. Go to fastboot and flash stock ROM with RSD lite
P.S. If you still have bootloop - just flash TWRP and SuperSU with it. But if you`ll do everything, what i wrote - You`ll have fully worked device.
Good luck )
St.Noigel said:
You can try to do next:
1. Wipe everything (incl internal storage with TWRP)
2. Format (not wipe) data with TWRP
3. Go to fastboot and flash stock ROM with RSD lite
P.S. If you still have bootloop - just flash TWRP and SuperSU with it. But if you`ll do everything, what i wrote - You`ll have fully worked device.
Good luck )
Click to expand...
Click to collapse
Step 3 is what I did originally, including erasing userdata. With that exact stock ROM.
I only wanted to update the bootloader and radio firmware, so I don't overly care it does not boot by itself, as I'm using LaOS.
Just as a note for anyone trying to use that image.
Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.
blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.
Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.
I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.
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?