Is it possible to root my motorola moto z play? And still get ota updates/ install them?
Only if you flash back to stock recovery and have the entire os back to stock, is it possible.
You don't need to flash back stock recovery if you don't replace it. Only change needed should be restore original boot partition. This is modified by f2fs fix kernel and any root I know to be working, they work systemless.
You should care not to use the power of root to modify anything (hosts, build.prop, logo, recovery and much more), otherwise you'll end up flashing whole ROMs. Which also isn't that bad.
tag68 said:
You don't need to flash back stock recovery if you don't replace it. Only change needed should be restore original boot partition. This is modified by f2fs fix kernel and any root I know to be working, they work systemless.
You should care not to use the power of root to modify anything (hosts, build.prop, logo, recovery and much more), otherwise you'll end up flashing whole ROMs. Which also isn't that bad.
Click to expand...
Click to collapse
How do does he or she root without having TWRP? Which replaces the stock recovery.
SupahCoojie said:
Is it possible to root my motorola moto z play? And still get ota updates/ install them?
Click to expand...
Click to collapse
You can unlock your bootloader and still receive otas.
All you have to do is flash back boot and recovery before installing the ota.
It Will Works If you not touch on system partition.
Jimi Mack said:
How do does he or she root without having TWRP?.
Click to expand...
Click to collapse
Do not flash it but boot on per-use-base.
fastboot flash twrp
Versus
fastboot boot twrp
Check it out
tag68 said:
Do not flash it but boot on per-use-base.
fastboot flash twrp
Versus
fastboot boot twrp
Check it out
Click to expand...
Click to collapse
Thanks, but what a PITA...
dedraks said:
You can unlock your bootloader and still receive otas.
All you have to do is flash back boot and recovery before installing the ota.
It Will Works If you not touch on system partition.
Click to expand...
Click to collapse
thanks its work with me :good:
OK, is there a guide somewhere that will tell us how to get the OTAs back without losing root?
If not, does anyone have links to the files needed and I'll write one up?
No, it is not possible to generally write such a guide.
1. OTA is not possible while rooted. You need to restore firmware without root, then you can do OTA, then you can root again.
2. OTA is based on blocks, not on files. You need to restore partitions which are modified. If you delete a file and then save it again, it will probably be saved on a different position on the partition.
3. The files which you need (the img-files for the modified partitions) depend on your firmware.
4. The modified partitions differ. Some people flash recovery. Others modify build.prop without using systemless interface of Magisk. Other modify logo.
A complete guide would just be a manual how to flash a stock firmware. At least boot, recovery, system, logo. And you need the exact version which you rooted. A backup after OTA update before rooting or doing other modifications therefore is a good idea.
tag68 said:
No, it is not possible to generally write such a guide.
1. OTA is not possible while rooted. You need to restore firmware without root, then you can do OTA, then you can root again.
2. OTA is based on blocks, not on files. You need to restore partitions which are modified. If you delete a file and then save it again, it will probably be saved on a different position on the partition.
3. The files which you need (the img-files for the modified partitions) depend on your firmware.
4. The modified partitions differ. Some people flash recovery. Others modify build.prop without using systemless interface of Magisk. Other modify logo.
A complete guide would just be a manual how to flash a stock firmware. At least boot, recovery, system, logo. And you need the exact version which you rooted. A backup after OTA update before rooting or doing other modifications therefore is a good idea.
Click to expand...
Click to collapse
I want to lose my moto z play without computer
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
tag68 said:
No, it is not possible to generally write such a guide.
1. OTA is not possible while rooted. You need to restore firmware without root, then you can do OTA, then you can root again.
2. OTA is based on blocks, not on files. You need to restore partitions which are modified. If you delete a file and then save it again, it will probably be saved on a different position on the partition.
3. The files which you need (the img-files for the modified partitions) depend on your firmware.
4. The modified partitions differ. Some people flash recovery. Others modify build.prop without using systemless interface of Magisk. Other modify logo.
A complete guide would just be a manual how to flash a stock firmware. At least boot, recovery, system, logo. And you need the exact version which you rooted. A backup after OTA update before rooting or doing other modifications therefore is a good idea.
Click to expand...
Click to collapse
I want to lose my moto z play without computer which application, please thanks
Related
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Rooting will also mess up Ota too, but if u install a custom recovery, now that we have stock recovery it will be very easy to revert back for OTAs, there should be a way to root without a custom recovery but I am not sure how though, but with how oneplus makes it so easy to unlock bootloader and flash customers stuff there is really no need to stay stock
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
pileot said:
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Click to expand...
Click to collapse
As far as I know, you'd have to have TWRP to get root.
I don't think getting it rooted will mess up the OTA updates, other users sprovide flashable zips for the OTA anyway.. so you can still flash the zips manually with TWRP to keep you updated.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
To get root yes, you would need TWRP to flash to certain partitions but to keep root no. Your phone will operate just fine with root and stock recovery. Check what the user a few posts above mine said about temporary flashing TWRP to achieve your short term goals
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
TheSvensson said:
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
Click to expand...
Click to collapse
Yes, I have the stock recovery and it is rooted.
The recovery partition has nothing to do with all the other partitions except that it can read and write them.
This is the zip I flashed to get systemless root:
https://www.androidfilehost.com/?fid=24591000424939898
Some users reported that some Root-apps are not supported this way.
I am using Titanium Backup, Adaway, Trimmer and Root Explorer without issues.
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
All I did was manually flash OxygenOS 3.1.3 in TWRP (not flashed but booted) and reflash the root package afterwards.
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
I have an unlocked bootloader and tried this on my PC:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.709s]
booting...
OKAY [ 0.373s]
finished. total time: 1.092s
Nothing happens, bootloader start screen stays frozen. Until I hold down the power button. Might you know why?
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
i tried to boot into twrp recovery with above command, but the phone seems to be stuck in the bootloader and not responding. Any ideas?
edit: comment above describes exact same behaviour, sorry for double post
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
AcmE85 said:
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
Click to expand...
Click to collapse
Thanks, that twrp img worked for me. The one I was using didnt allow me to boot to it.
AcmE85 said:
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
Click to expand...
Click to collapse
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
hahamuntz said:
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
Click to expand...
Click to collapse
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
AcmE85 said:
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
Click to expand...
Click to collapse
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
hahamuntz said:
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
Click to expand...
Click to collapse
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
AcmE85 said:
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
Click to expand...
Click to collapse
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
hahamuntz said:
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
Click to expand...
Click to collapse
Yes, OTAs will come and because of Root you will get the full OTA regardless, which does not cause any issues with TWRP.
I tried my previous method and the regular OTA would fail because of root which changes the kernel or the system partition.
OnePlus reacted to this and introduced the full rom OTAs at some point.
So with root on my device this is how I do OTAs now:
- get the OTA notification for the full rom
- download but don't install
- move the downloaded zip from android/data/com.oneplus.ota/files/.OnePlusOta to my download folder
- manually boot into twrp and flash full rom zip + SuperSU
AcmE85 said:
Yes, OTAs will come and because of Root you will get the full OTA regardless which does not cause any issues with TWRP.
Click to expand...
Click to collapse
Okay, thanks so much for your help
I am stock rooted. I got an OTA that I'd like to update but it looks like it doesn't want to flash through twrp. I want to stay stock rooted. Do I need to reflash entire image?
Try Flashfire.
If flashfire doesn't work (like in my case), just flash stock recovery and apply OTA. You'll have stock unrooted ROM and you can follow these steps:
1. have stock rom + stock recovery
2. use "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3.
_mysiak_ said:
If flashfire doesn't work (like in my case), just flash stock recovery and apply OTA. You'll have stock unrooted ROM and you can follow these steps:
1. have stock rom + stock recovery
2. use "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3.
Click to expand...
Click to collapse
Do you know if OTA will work if I have any other system modifications? I pushed some apps to /system for example. :silly:
Thanks for your help!
Ascertion said:
Do you know if OTA will work if I have any other system modifications? I pushed some apps to /system for example. :silly:
Thanks for your help!
Click to expand...
Click to collapse
As far as I know, even mounting system as R/W can prevent OTA update. I wouldn't even try to apply OTA with modified system partition. In your case I would download full factory image, flash everything without data wipe, root as suggested above and apply next OTA without struggles
Ascertion said:
Do you know if OTA will work if I have any other system modifications? I pushed some apps to /system for example. :silly:
Thanks for your help!
Click to expand...
Click to collapse
Have you tried flashfire? I'd recommend it. You can flash the ota, download the full ota from Google, and retain root and a custom recovery. Support chainfire and get the pro version. Although, functionally there is no difference.
jd1639 said:
Have you tried flashfire? I'd recommend it. You can flash the ota, download the full ota from Google, and retain root and a custom recovery. Support chainfire and get the pro version. Although, functionally there is no difference.
Click to expand...
Click to collapse
Flashfire worked. I had to uninstall SuperSU and reinstall magisk and TWRP but much easier than wiping everything and flashing.
Thanks all for your help! :good:
_mysiak_ said:
If flashfire doesn't work (like in my case), just flash stock recovery and apply OTA. You'll have stock unrooted ROM and you can follow these steps:
1. have stock rom + stock recovery
2. use "fastboot boot twrp.img" (boots TWRP without flashing it)
3. install magisk from TWRP
When OTA cames in, I just apply it and then repeat steps 2 and 3.
Click to expand...
Click to collapse
Holy it WORKS!!!!
Thanks!
Thats the question, can "easily" install magisk on stock rom (.236) unrooted ? since magisk thread says that root is not necessary, its ask for stock boot img that cant be obtained w/o root
JIJOK said:
Thats the question, can "easily" install magisk on stock rom (.236) unrooted ? since magisk thread says that root is not necessary, its ask for stock boot img that cant be obtained w/o root
Click to expand...
Click to collapse
Never tried, but even though root may not be needed, unlocked bootloader probably is. Magisk non-system works by patching boot img... If you unlock bootloader you probably can use it.
levone1 said:
Never tried, but even though root may not be needed, unlocked bootloader probably is. Magisk non-system works by patching boot img... If you unlock bootloader you probably can use it.
Click to expand...
Click to collapse
so, can get the image by just unlock the bootloader ? I though root was necessary for that
JIJOK said:
so, can get the image by just unlock the bootloader ? I though root was necessary for that
Click to expand...
Click to collapse
You can unlocked bl by official Sony method, then flash recovery with adb. Boot to recovery and flash Magisk.
Backup ta - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Recovery img - https://androidfilehost.com/?fid=961840155545588613
You can try flashing recovery within locked bl, but I don't think it would work.
levone1 said:
You can unlocked bl by official Sony method, then flash recovery with adb. Boot to recovery and flash Magisk.
Backup ta - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Recovery img - https://androidfilehost.com/?fid=961840155545588613
You can try flashing recovery within locked bl, but I don't think it would work.
Click to expand...
Click to collapse
So, if you was wondering it, no, cant flash it with locked bl.
At the moment Backup ta didnt work, will check that thread
And thanx the help, nice to have you on z1c forum :good:
perfect. thx! i was already wondering, if i had to downgrade my z1c in order to get the recovery back. but now, how i do i flash magisk from here?
when i try to flash, i get an error message saying, that the ftf is in sony elf32 format and that i need bootbridge from @AdrianDC to flash.
anyone ever did that or has a better idea?
just tried it now and ended up in a bootlop
It is many months after this post, but in case this helps anyone, here is the answer.
BootBridge method is pretty simple and it worked for me.
On an un-rooted device. (important)
Just rename magisk zip to "install.zip" put it in a folder called install.
Then with 7zip, create a zip-file, include the bootbridge folders, "META-INF" and "scripts" with the "install folder" you just created.
Then name it "anything_you_like.zip" and flash with TWRP
Basically Magisk is SuperSU alternative and provides SuperSU service for your device. ( roots it )
No problems for me at this point. Working on 14.5.A.0.270 and can also get working on 14.6.A.0.236 but have other problems related to getting compatible recovery on 236.
Eventually in recovery, system mount and unmount break for me, then other mounts eventually fail after trying to get Nanodroid working (My Goal to UnGoogle my Z1c) and can't wipe format or anything (only way to fix is reflash with flashtool)
Deodexed ROM seems to be necessary for Nanodroid and this is causing additional problems for me.
If I have to run with unlocked bootloader, I think AOSP may be a better starting point.
I'm planning on rooting my Moto Z Play but staying on the stock ROM as it has better battery life (according to XDA members) compared to LineageOS. I also really like Moto Display and all of the other exclusive features to this ROM.
However, I still want to receive OTAs after doing so. I've read that an app called FlashFire can help me with this.
Question 1: Do the OTAs download even if your system is rooted? I've read that some phones do download the OTAs, but fail when the flashing starts as they have a custom recovery, while some phones don't even download at all once it detects that you're rooted.
Question 2: Will it work even if I have TWRP installed?
Thank you.
Hi i dont think you can receive OTAs after unlocking bootloader and iff you do they will fail on installation as you have said. Secondly in my opinion you are right and i have tried almost all the roms on here and by far the stock N is the best rom for fluidity battery life app compatibility etc so i went back to stock but the deodexed N debloated version because im rooted. Iff i were you i would not root at this time because i think Official Oreo is about to be released for our phone and it would be a good idea to hangon a while but that is entirely your choice.
djdelarosa25 said:
However, I still want to receive OTAs after doing so. I've read that an app called FlashFire can help me with this.
Click to expand...
Click to collapse
Never really tested Flashify and FlashFire. If you succeed please write how it works, which steps to do to be on the safe side
djdelarosa25 said:
Question 1: Do the OTAs download even if your system is rooted? I've read that some phones do download the OTAs, but fail when the flashing starts as they have a custom recovery, while some phones don't even download at all once it detects that you're rooted.
Click to expand...
Click to collapse
Download fine. Install fails, yes.
djdelarosa25 said:
Question 2: Will it work even if I have TWRP installed?
Click to expand...
Click to collapse
No. That's why I never install twrp, I just boot it when needed. You need a computer and a cable every time you want to start twrp, but recovery partition stays untouched using fastboot boot.
Idea is:
1. Take a backup of boot partition before rooting
2. Install the kernel you need to avoid f2fs problems, then Magisk. Both modifies the boot partition, nothing else.
When an OTA arrives, you restore your backup of boot partition and everything is stock. OTA is supposed to work fine.
In theory, if I just run TWRP off from the PC and flash SuperSU on my phone without flashing TWRP, I would be rooted, right? And the OTAs would install, but I will lose root access?
djdelarosa25 said:
And the OTAs would install, but I will lose root access?
Click to expand...
Click to collapse
No. SuperSU modifies boot partition. OTA do not install while boot partition is modified.
You need to restore NANDROID backup of original stock boot partition prior to rooting, then you should be fine for install OTA.
---------- Post added at 11:45 ---------- Previous post was at 11:29 ----------
Just an additional hint: Modifying logo also prevents OTA. If you suppress that unlocked bootloader warning with a different logo, of course you need to restore the original logo partition before applying OTA.
tag68 said:
No. SuperSU modifies boot partition. OTA do not install while boot partition is modified.
You need to restore NANDROID backup of original stock boot partition prior to rooting, then you should be fine for install OTA.
Just an additional hint: Modifying logo also prevents OTA. If you suppress that unlocked bootloader warning with a different logo, of course you need to restore the original logo partition before applying OTA.
Click to expand...
Click to collapse
That's a pity. Oh well, I might just have to wait for Oreo.
Thanks a lot!
"'Just an additional hint: Modifying logo also prevents OTA"
Actually...not my experience. I have an unlocked bootloader, flashed a stock rom file by file, except for logo.bin, which is a modded one to get rid of the annoying "untrustworthy" startup screen.
All worked well and recently got the OTA update all installed as normal by the system.
Will wait now to get the official oreo update before i muck around further.
Actually, on the 22-2-8 build on the phone now it runs really well and battery life is great. Getting over 2 days in my usage pattern easy.
Camera good as well. Got some nice photos of the local beach last night.
You can get back to stock, and get ota's
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Note: Lock of Bootloader is not required to get OTA update. It makes sure that you do no action which prevents OTA, but if you take care this does not happen (for instance not rooting which modifies system or boot partition), you eg can take advantage of Nandroid backup only booting TWRP for this purpose.
Hello ,
I will have a ONE PLUS 5T.
I would like to root this one to have adblocker...
First question : How could root this?
Second question: If my phone is rooted, is it possible to have update OTA (or like samsung, impossible after)?
Thank you;
If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.
jim262 said:
If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.
Click to expand...
Click to collapse
it's chinese for me your answer... is there a tutorial for that?
ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
Guide: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
You can't use OTAs after you root. You'll need to download the full update every time one is released and flash it in TWRP.
ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.
jim262 said:
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.
Click to expand...
Click to collapse
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
If we root our device.can we install ota manually via twrp ??
If yes, then how??
Amanpreetsingh said:
If we root our device.can we install ota manually via twrp ??
If yes, then how??
Click to expand...
Click to collapse
Let me clarify: OTA stands for Over-The-Air and implies that you're going to download the partial update from OnePlus and install it in stock recovery. Do NOT do this.
OnePlus usually publishes full zips of their updates when the OTA is released. Currently a mirror for them exists in the guides section. You can flash those (>1 GB) safely in TWRP to update OOS.
santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
What's the difference? You still need to reroot.
jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
I apologize if I'm out of the loop. When I first read about OTAs with root I was on a Samsung device and everyone said that it would either brick the phone or upgrade the OS with no way to re-root the device. Looking through your answer it's obvious that that fear probably only applies to Samsung devices. Thanks for correcting me on this.
jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
Thanks Jim , I can confirm this works without problems on op5t. I had TWRP flashed and rooted with xposed installed.
I clean flashed the 4.7.1 stock ROM and got stock recovery and fresh os.
Just booted to TWRP using fastboot boot and rooted / installed xposed.
I got OTA updated to 4.7.2 and rerooted using fastboot boot TWRP and now rooted with xposed on stock ROM and stock recovery. ?
I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?
ilan78 said:
I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?
Click to expand...
Click to collapse
Exactly like I said. Rooting, by itself, does not wipe your storage. The only time your storage is wiped is when you unlock your (bootloader) phone, when you manually choose to wipe storage in TWRP or when you do a factory reset. If you do not have an unlocked bootlader, you must make a backup of your files first, as once you unlock it does a factory reset. You can then run TWRP and restore your files. You are now rooted with your files and ability to take OTAs. There are plenty of tutorials here on XDA describing the process step by step. May I suggest you do a search first. You are very likely to get all the answers to these questions as they have been asked many, many times.
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Look through the Magisk forum. They have a method of rooting that doesn't require a custom recovery.
I use helium backup for my non-root app backup needs. Settings are trickier and I typically do them over every time. Super backup & restore is good for call logs, texts, and contacts.
ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Did you read my post? The answers are all there. SEARCH! This question has been asked several times a day. You need to back up your data to another site, such as cloud, other device or PC. Then unlock bootloader, run TWRP and root file, then restore data. Tutorials are online. Now SEARCH!
ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Man seriously! You got your answers and still you keep asking. Makes me wonder if you are just trolling
Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?
Tefzors said:
Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?
Click to expand...
Click to collapse
Yes, as far as I know, if on stock OOS, you download the full zip (over 1GB in size), flash that in TWRP, and then flash root solution right after (before leaving TWRP) to prevent it being overwritten by the stock recovery.
I don't think dirty flashing has any downsides, but if you do end up running into issues, a clean flash usually solves them