I'm a happy new owner of 5X for almost a week now and really love the stock Android experience and the lovely monthly patches. But what I'm missing is few useful tools like AdAway and BetterBatteryStats, so I'm considering rooting my devices. What is the painless method to root and still be up to date with google's patches, even if I have to flash them manually with FlashFire?
I download the factory image and flash all but the userdata in fastboot. Then I reflash custom recovery and reflash SuperSU and Xposed. If you leave userdata intact, SuperSU will remember your superuser permissions. I prefer that over a flashable ota image because I can see and control what's going on at each step.
Related
I am new to the whole understanding of root on non-Nexus devices seeing how I had to root my Nexus 4 after each update and I had a fair bit of knowledge hacking/modding/rooting the Nexus.
Kedros over at oppoforums (http://www.oppoforums.com/threads/how-to-root-your-oppo-find-7a-w-oppo-recovery.11309/) provided a root method that is permanent. I have no plans to install custom ROMs nor do I feel the need to flash a custom recovery (ex. TWRP).
My question is:
1. Will I still receive OTA updates from Oppo after I root?
2. If no to step 1, will flashing ColorOS updates remove the "permanent" root?
Thanks.
Root and OTA
anwedr said:
I am new to the whole understanding of root on non-Nexus devices seeing how I had to root my Nexus 4 after each update and I had a fair bit of knowledge hacking/modding/rooting the Nexus.
Kedros over at oppoforums provided a root method that is permanent. I have no plans to install custom ROMs nor do I feel the need to flash a custom recovery (ex. TWRP).
My question is:
1. Will I still receive OTA updates from Oppo after I root?
2. If no to step 1, will flashing ColorOS updates remove the "permanent" root?
Thanks.
Click to expand...
Click to collapse
1. Yes. OTA updates will work so long as you're using stock recovery and haven't made drastic changes to the /system partition.
2. Flashing an incremental (OTA) update in recovery will have the same effect as tapping "install update" from the about phone menu. You will lose root. If you flash a complete dump of the /system you will lose root as well since you are replacing /system.
Losing root isn't a big deal. Just flash again from recovery. You could try the OTA survival option built into SuperSu. I didn't bother trying because it takes less than a minute to reboot to recovery and flash SuperSu/su binary. What might be a big deal with the OTA update is that it wipes /data. This is odd because the pop-up that appears prior to installing the update specifically states that you won't lose apps or data. Your custom ROM plans may change after you use ColorOS. I hate it. It's glitchy and has a huge memory footprint. I'd recommend trying the 2.0 beta. I haven't had my Find 7a for long, but I've had no bugs thus far with the 2.0 beta. It's available on the Oppo Forums.
-Sent from my Panasonic 3DO
Hi everyone
I want to root my nexus 5x to have xposed but the main issue is that I wouldn't be able to install otas even if I rooted with systemless root because xposed misses up system partition , so systemless root becomes pointless .
My question is if I rooted with systemless root and installed xposed , if I wanted to install any new ota if i just removed xposed will this be enough to return system to unmodified status and I can now install the ota , or my system will become modified untill I reinstall the whole binary image ??
Hope I made my question clear as possible and sorry for my bad English
Thanks in advance ...
Or, instead of worrying about OTAs, you could just get the images from the Google website since this is a Nexus device, we are supported for something like 3 years I think I read, with security updates persisting 1.5 years after that.
https://developers.google.com/android/nexus/images
(you would use fastboot flash to accomplish this)
I know , but I don't want to flash everytime the whole binary image if I just can install a ~< 10 mb OTA .
If i can Just uninstall xposed then install the ota that will be much easier ...
I don't think you can take ota updates with a custom recovery and without a custom recovery you would have to flash a system image to get it back to stock in order to take the ota
flashing updates manually via TWRP is very easy once youre used to doing it.
No I can install OTAs using flash fire if the system partition is unmodified , so that's why I'm asking if uninstalling xposed return system partition to unmodified status ?
@2x4 installing updates is very easy with chainfire's flashfire only if you have unmodified system partition , and I want to install xposed but at the same time I want to know if I just uninstalled xposed will that make my system unmodified again ...
Running the xposed uninstalled will undo any changes to the system partition. So to answer your question, yes.
@t-r-e you're coming from the angle of keeping your system partition intact for the SOLE purpose of OTAs (you've said nothing about android pay). Given that, it's easier to just update manually via TWRP instead of doing OTAs, so you won't have to worry about xposed or any other mods.
Hello all,
For the last 4-5 firmware updates I've had no issue using fastboot to flash the firmware images, then flashing SuperSU, ElementalX kernel, Viper4Android and AdAway host lists through recovery to update to the latest build but keep my root mods.
I would like to now to the same with DP5 (or, at the very least, the first official Nougat build when it drops soon) and make sure I do it safely without any bricking.
Here's the current status -
Bootloader: Unlocked
Build: Android 6.0.1 MTC19Z, July Security Patch
Root Status: Rooted
Root Mods: ElementalX Kernel, Viper4Android, AdAway
Essentially, I want the same set up/root mods as above, only on 7.0. My questions are as follows:
1. Does the process differ at all for both installation of the firmware (through fastboot) or root method (flash TWRP, flash SuperSU)?
2. Is a full data wipe required? Recommended?
3. Anything else I should know?
Thanks in advance for the help. I'd love to make this as painless as the monthly firmware updates without any hiccups.
- Moonboots
The process does not differ much for the installation of the firmware; all you need to do is flash the factory images and TWRP through fastboot, and flash SuperSU/root through TWRP.
However, for a working TWRP and root, you'll need to decrypt your phone again, which will of course wipe your phone's data and internal storage.
I suggest looking at this helpful thread over on the Nexus 6P forums saying how to switch to 7.0 here:
http://forum.xda-developers.com/nexus-6p/general/how-to-switch-to-android-n-preview-t3409538
Even though it's for the 6P, I have used it myself and the procedure is the same. Once you've done all that, you're good to flash the latest SuperSU through TWRP.
As for V4A, I'm not sure whether it is compatible with Android N yet. You can install the ElementalX kernel normally after installing 7.0, but I don't think it's been updated to DP5.
If you do decide to update to Nougat, the modified boot.img for NPD90G can be found here:
http://forum.xda-developers.com/nexus-5x/general/4-17-16-t3360574
Thank you! I actually kept my phone encrypted all this time. Have you seen significant performance increases by decrypting?
EDIT: I see it's actually necessary for working TWRP in 7.0, thus far. Interesting. I'll have to work on getting my data backups set tonight.
I would like to get to the point where I'm able to OTAs instead of manually flashing factory images but I'm not passing safety net when I uninstall magisk and reinstall it when the update reaches step 2. I'm not sure what is causing the update to fail. I recently switched from system root via supersu (obviously wouldn't pass safety net) to systemless root with magisk. I'm running 8.1 feb. security update with the following apps installed: adaway, busybox, CF. Lumen, greenify, magisk manager, & titanium backup. (rootless substratum & andromeda as well).
I do not have TWRP installed, I only boot to it to flash magisk and kept TWRP systemless. The purpose for this post I guess is to try understand which of the installed apps listed may affect the /system files. I was under the impression that since i now root systemlessly I would be able to accept OTAs. What am I missing here?
As far as I know you cannot be rooted and/or have a custom recovery. You can have a unlocked bootloader but you have to be stock in order to receive OTAs.
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
......... you can flash full OTAs from TWRP?? I knew I was missing something.
So download the full OTA to internal storage. flash in TWRP. then magisk and if i choose not to install TWRP (i usually only boot to it), I'm done?
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
Wait, doesn't flashing the full OTA get rid of TWRP?
Do you have instructions how to install full images without TWRP being uninstalled?
Also... How do you get ota to install if the original bootloader is replaced by twrp? I thought installing twrp permanently voids the possibility to install ota...!
I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom
Tom2112 said:
I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom
Click to expand...
Click to collapse
I have seen postings about people fastboot flashing back the original boot.img, then taking the ota then repatching the new boot image and flashing it via fastboot. Not as simple as you hoped i am sure but it works.
The other way is to download the full image, remove the -w option in the flashsall.bat and then run the modded flashall file. You then need to patch the new boot image as above and fastboot flash that to regain root. I have not found any other ways to get updates besides doing one of the 2 above every month
Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.
Tom2112 said:
Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.
Click to expand...
Click to collapse
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Sideloading the ota would be a great option EXCEPT he said he was on a much older version... Like sept.
My understanding is that the ota for dec would only contain changes implemented for the month of December, this in this scenerio he would not get the patches for October and November with your method and i am not even sure if it would boot after that mismatch
It's really not saving much work if any over flashing the full version, and with the full version they're is no potential for bootloop due to missing some patches or updates. It's just much safer.
thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?
Tom2112 said:
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?
Click to expand...
Click to collapse
https://developers.google.com/android/ota
The most simple way to update while keeping root would be to follow the instructions for "Devices with A/B Partitions" at the following link in the Magisk documentation:
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Basically, Magisk allows you to restore the original boot image to the current partition so you can take the OTA when it arrives on your phone. Before rebooting you install Magisk to the inactive slot so that when the phone restarts you retain root without having to mess with Fastboot.
Delete Me!
Think all you have to do is click uninstall magisk, dont reboot... Take ota, but before reboot click install magisk/ install to empty slot...
Oops didnt see the reply above
OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?
Tom2112 said:
OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?
Click to expand...
Click to collapse
This should be a one time issue. One of the latest versions of Magisk changed the default location of the boot.img backup. They released it in December after most of us had already upgraded to the December Pixel update. This means we used the older version of Magisk when we installed the Dec update and it saved the backup to the old/original location. We then updated Magisk sometime later in December, but the Magisk update doesn't move the backup file to the new location (a poor execution from the Magisk team IMHO). Because we are now on the updated version, it expects the boot.img backup to be in the new location, but it is still in the old location and Magisk doesn't check that old location (again, a poor execution from the Magisk team IMHO).
To fix this you have several options.....
Option one is to find the original backup location that Magisk used for the boot.img and move it to the new backup location that Magisk uses. Unfortunately, I don't know where those backup locations are and didn't feel like researching it, so I used one of the other methods.
Option two is to "reinstall" Magisk (choose the patch file option and select the stock boot.img that may still on the phone from whatever the last update was (if you sideloaded the update and then had to rerooted the phone)- or download it from the applicable factory image and move it to the phone) to force Magisk to backup the current boot.img file to the new location. Stop after this initial step (ie you don't actually need to flash the patched file because it has already been done). Then you should be able to follow the normal Magisk update process to move to the January update.
That being said, I have horrible success being able to take the updates OTA (they usually fail) and usually end up sideloading the update. That is the final option - sideload the Jan update and then reroot the phone using the normal root method (ie getting Magisk to patch the stock boot.img file and then flashing the patched file).