How would I go about updating from M to N without losing data, keeping root, and staying decrypted?
Sent from my Nexus 6P using Tapatalk
You can't keep root. The rest is no different than flashing a factory image after removing the -w flag from the script if you have an unlocked bootloader, or flashing a non incremental OTA via sideloading. Version doesn't matter. After updating, you boot into recovery and reroot.
Related
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Just reflash the superSU.zip from here http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in CWM and you should be rooted again. You will not loose any data so no need to backup. Download OTA Rootkeeper from Play to regain root after installing future OTA`s.
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
AAhrens said:
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
Click to expand...
Click to collapse
Try cmd and type: adb reboot recovery. If you see the androidian (stock recovery) you have to reflash the TWRP img file in fastboot mode.
Will this reset my phone? Or does only rooting do that?
You will not loose any data.
Sent from my Nexus 4 using xda premium
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Let me guess, you used a toolkit to root?
a) You did the full OTA, so you lost your custom recovery.
b) flash images through fastboot and skip the recovery.
c) Only after you flash a custom recovery. If your recovery is sitting in the same folder as fastboot and named "recovery.img, simply cd into the fastboot folder in a command prompt and type
fastboot flash recovery recovery.img
d) Not unless you lock or relock your bootloader.
OP, you need to do some more research and uninstall the toolkit from your computer. You know just enough to cause yourself problems, but not enough to know why they happen or how to fix them.
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Rizy7 said:
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Click to expand...
Click to collapse
Thanks all, was able to get it fixed by re-rooting!
I have a Verizon HTC 10 on 1.85.605.8 with s-off (locked), systemless SuperSU, systemless Busybox and systemless nano (text editor).
Using the no red text aboot for 1.85.605.8 and TWRP 3.1.0-1.
fuzzynco said:
I have a Verizon HTC 10 on 1.85.605.8 with s-off (locked), systemless SuperSU, systemless Busybox and systemless nano (text editor).
Using the no red text aboot for 1.85.605.8 and TWRP 3.1.0-1.
Click to expand...
Click to collapse
Not entirely, no.
Mainly due to firmware flashing limitations.
Stock RUU/or stock system.img+boot.img and stock recovery is the recommended path for a proper OTA update.
Sent from my HTC6545LVW using Tapatalk
santod040 said:
Not entirely, no.
Mainly due to firmware flashing limitations.
Stock RUU/or stock system.img+boot.img and stock recovery is the recommended path for a proper OTA update.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
If I understand correctly, Nougat's partitioning is different than MM.
If I do a flashfire backup of my data partition and internal sdcard.
Should I be able to RUU to .8 or .9 and then OTA,
flash twrp, and then redo the systemless SuperSU / Busybox / Nano again?
then restore the data partition and internal card to get back my apps
and setup?
Or does TWRP & SuperSU need fixing for the new partitioning and setup
first?
If TWRP can't install the OTA does it just fail? I'm thinking maybe I should wait
until someone comes up with how to safely do an update (with a way back).
Do the RUU's setup the partitioning (or just assume it's correct)?
What I mean is since 7.x changes the partitioning, would the
6.x RUU change it back?
I'm thinking the hardware and bootloader partitions would stay in
the same places, so the bootloader can setup the 7.x partitioning
before it loads the partitions.
I'm about to provision my One Plus 5 for use I will be running it with TWRP a unencrypted data partition (makes restores easier) and root via Magisk day one.
I'm curious if I'm running it in this configuration when an OTA comes down the pipe will it do any of the following?
re apply fastboot oem lock?
flash the recovery to stock recovery?
remove magisk?
re-enable dm-verity?
Curious if the process after an OTA apply is to re-flash TWRP potentially re-apply magisk? Does applying ota mess with your data partition if you already decrypted it?
Also was thinking about leaving the data partition decrypted so I can push things to it via ADB or manipulate it when it's in a non-functional state can anyone here comment on if that's still possible while encrypted? And if so what dis-advantages of leaving it encrypted I hear one is you have to remove the lock screen password before you create a backup since the keys are not backed up and you might be locked out after a restore.
With some more research I've answered my own question I'll put them here in case anyone wants to refer to them in the future.
TWRP users will lose TWRP after a flash of the OTA.
Root will be lost regardless if you flash using TWRP or stock.
Data is not touched during flash so it should stay as is.
DM-verity requirement is unknown.
For rooted users it's better to do a full flash with TWRP OTA through TWRP will cause a problem.
Actually, you won't get the small incremental OTA, you will download the complete 1.5 - 2gb rom... This happens when you have root whether you have got TWRP or stock recovery.
Root will always be lost, yes but if you flash with TWRP you can flash magisk oe SuperSU immediately afterwards to gain root again. Not having TWRP you will need to either boot TWRP or install it to install root again.
DM-Verity, I have never had any problems with this after flashing and then rooting...
I dirty flash the 4.5.10 and i had to reflash the ROM + no_verity_op5.zip. My first and only issue was a sort of bootlop to the recovery.
So wait. If I flash the OTA, then flash Magisk, I will have root and lose TWRP, right?
Then could I use some app like Flashify or the TWRP app to install the recovery?
I don't own a PC right now and want to know if it's possible.
Hi all, my phone is still on Nougat with SuperSU (I know, I know) and I want to upgrade to Oreo and also do a clean re-root with Magisk. Can I simply backup what I need, factory reset, take OTA update, and root? Will having TWRP, SuperSU, and the bootloader unlocked have any issues with a factory reset? Thanks.
kram12085 said:
Hi all, my phone is still on Nougat with SuperSU (I know, I know) and I want to upgrade to Oreo and also do a clean re-root with Magisk. Can I simply backup what I need, factory reset, take OTA update, and root? Will having TWRP, SuperSU, and the bootloader unlocked have any issues with a factory reset? Thanks.
Click to expand...
Click to collapse
An unlocked bootloader is no problem for taking OTA, TWRP and SuperSU are definitely.
You've got two ways to upgrade to Oreo:
- Fastboot flash the nougat firmware you're on and apply the OTA updates until you are on Oreo.
- Fastboot flash latest Oreo firmware for your region.
In both cases you will lose your data so back it up before.
After that you have to flash twrp again, decrypt your data partition if you wish to and reroot the phone, I recommend magisk 18.
Thank you, that's very helpful! Literally for no reason other than downloading podcasts my phone rebooted and is now bootlooping, so good timing to get a clean slate going!
I've been out of the loop with rooting on newer versions of android and I just upgraded to the OP8. Does rooting disable OTA updates or will I continue to receive them as normal? Are there any other issues with it I should be aware of?
Also: does OEM unlock still wipe the device?
As per my knowledge you have to download the whole rom package after root. Unlocking the bootloader wipes the phone.Make sure to backup fp partition after flashing twrp.
https://topjohnwu.github.io/Magisk/ota.html
Follow this to keep root when updating.