Replace TWRP with stock recovery to install OTA - LG G5 Questions & Answers

Today I've flashed the recovery with TWRP to install SuperSU.
Is there any possibility of installing the stock recovery to be able to install Android updates normally again without losing all data and SuperSU?

You sir, are not alone with this question. Been eagerly looking for an answer for the same question..

reconman said:
Today I've flashed the recovery with TWRP to install SuperSU.
Is there any possibility of installing the stock recovery to be able to install Android updates normally again without losing all data and SuperSU?
Click to expand...
Click to collapse
Use the search function, it has already been covered.

Anarchist77 said:
Use the search function, it has already been covered.
Click to expand...
Click to collapse
I can't find anything for the G5, only for other phones.
The only option I currently know of is to flash the whole KDZ and then install TWRP and SuperSU again. Is there another way?

As long as the system is modified in any way, the only way to install ota updated is through LGUP because before applying the update there is a system integrity check ran and if that fails you will most likely get into bootlops or worst

Here is what I did to get a 10D rooted system
Thank you @gwolfu.

Related

Process for rooting/decrypting 6.0.1

So either I suck or I literally have the process wrong, but I was trying to install 6.0.1 last night for 2 hours. Originally I had 6.0 installed rooted, twrp, etc. OTA didnt work because I'm guessing twrp was installed as it errored out. So I decided to take WUG downloaded the binaries/newest stuff and decided to just manually flash 6.0.1. However at the same time I wanted to use the decrypter tool here.
My process was/is:
Flash Stock/Unroot button in WUG (with newest 6.0.1 already downloaded
Root button and flash customer recovery button/checkbox
Flash the perm recovery zip, supersu, and busybox
Flash the decrypter zip
Wipe data/cache/system/davik/etc and then freshly reboot
The problem is, it just hangs on the animation screen and never loads. I've tried it twice now, and its driving me insane. Where could I have went wrong? What is flawed about my process or maybe I'm using the wrong stuff. Thank you in advance guys!
chugger93 said:
So either I suck or I literally have the process wrong, but I was trying to install 6.0.1 last night for 2 hours. Originally I had 6.0 installed rooted, twrp, etc. OTA didnt work because I'm guessing twrp was installed as it errored out. So I decided to take WUG downloaded the binaries/newest stuff and decided to just manually flash 6.0.1. However at the same time I wanted to use the decrypter tool here.
My process was/is:
Flash Stock/Unroot button in WUG (with newest 6.0.1 already downloaded
Root button and flash customer recovery button/checkbox
Flash the perm recovery zip, supersu, and busybox
Flash the decrypter zip
Wipe data/cache/system/davik/etc and then freshly reboot
The problem is, it just hangs on the animation screen and never loads. I've tried it twice now, and its driving me insane. Where could I have went wrong? What is flawed about my process or maybe I'm using the wrong stuff. Thank you in advance guys!
Click to expand...
Click to collapse
I don't think the NRT is updated to properly root on 6.0.1 (Could be wrong).
Get the Latest SuperSU-v2.62-3 and flash that, It will modified the boot.img for you and include no forced encryption.
As long as you remove the encryption of the data partion in twrp from this guide
You shouldn't need the decrypter zip, also if you flash TWRP and boot into it before booting the system, you also won't need perm recovery.
Going by what I have read, still encrypted on my Device.
corkiejp said:
I don't think the NRT is updated to properly root on 6.0.1 (Could be wrong).
Get the Latest SuperSU-v2.62-3 and flash that, It will modified the boot.img for you and include no forced encryption.
As long as you remove the encryption of the data partion in twrp from this guide
You shouldn't need the decrypter zip, also if you flash TWRP and boot into it before booting the system, you also won't need perm recovery.
Going by what I have read, still encrypted on my Device.
Click to expand...
Click to collapse
ok so everytime I flash the supersu, it does its thing, then I format data, the reboot and twrp says supersu is not installed, do you wanna install it now? You can swipe to install or do not install.
Which I dont get becuase clearly I flashed the supersu zip a sec ago. if I continue to just flash it like it says, when I boot up, all I see in my drawer is the "SuperSU Installer" I have no idea what I'm doing wrong. If I dont have twrp install it when it asks, I got nothing in my app drawer
think I may have gotten it, had to download supersu from play store, then reflash, then let twrp flash it when it says it needed too, not I can launch supersu from the app drawer and it works.
Next problem is encryption. Under security it still says "Encrypted" do I need to actually hit the "Format Data' button in twrp? I just did a factory wipe slide.
chugger93 said:
ok so everytime I flash the supersu, it does its thing, then I format data, the reboot and twrp says supersu is not installed, do you wanna install it now? You can swipe to install or do not install.
Which I dont get becuase clearly I flashed the supersu zip a sec ago. if I continue to just flash it like it says, when I boot up, all I see in my drawer is the "SuperSU Installer" I have no idea what I'm doing wrong. If I dont have twrp install it when it asks, I got nothing in my app drawer
Click to expand...
Click to collapse
From the linked SuperSU thread
From the linked SuperSU thread said:
If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
Click to expand...
Click to collapse
This is do with the new systemless root and TWRP needs to be updated to reflect this change.
chugger93 said:
think I may have gotten it, had to download supersu from play store, then reflash, then let twrp flash it when it says it needed too, not I can launch supersu from the app drawer and it works.
Next problem is encryption. Under security it still says "Encrypted" do I need to actually hit the "Format Data' button in twrp? I just did a factory wipe slide.
Click to expand...
Click to collapse
From the linked guide above said:
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
Click to expand...
Click to collapse
Answers in quoted messages.
Never had to get SuperSU app from the store, maybe because I already had it installed, the app is also in the SuperSU zip.

January Security Update incremental .zip - Directly from Google's servers

I got the update for the January Security Update today. I grabbed the .zip's location and the link on Google's servers is:
https://android.googleapis.com/pack...51c56752.signed-angler-MMB29P-from-MMB29M.zip
Hope it helps others!
PSA: this is not flashable over custom ROMs, and cannot be used to install the factory OS from nothing. That's what the factory images are for . This .zip is solely to incrementally update from the December security update to the January one.
Is there an easy way to flash this update.zip without the need of a computer?
tinker_tf said:
Is there an easy way to flash this update.zip without the need of a computer?
Click to expand...
Click to collapse
Unless you have a custom recovery, no. Sorry about that
Updated. Thanks for the link!
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Also, I don't have the December update, where do I find that?
And lastly, I'm on MDB08L Build, will that work?
For those wanting to use this update and have completely stock system based on MMB29M. Boot into recovery and do an ADB sideload update.zip (rename zip first). Mine updated with no issues.
CipherSec said:
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Click to expand...
Click to collapse
If you've got all that set up, why not just update using the full factory image (without the wipe)
LeoRex said:
If you've got all that set up, why not just update using the full factory image (without the wipe)
Click to expand...
Click to collapse
I assumed I'll lose all my system modifications (i.e. Xposed Modules and their settings) as well as losing root and TWRP and having to reroot again.
pmedwards25 said:
Unless you have a custom recovery, no. Sorry about that
Click to expand...
Click to collapse
This is exactly the file you need if you don't have custom recovery, don't have root, and have not unlocked bootloader. It is the same file that would eventually come to you OTA. You do however need access to adb and a computer. I don't think this is flashable with a custom recovery.
Thanks..
Thanks for this file bro. dont need to wait.
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Casyis said:
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Click to expand...
Click to collapse
Try flash stock system image
Does this update fix the LTE issue?
HRodMusic said:
Does this update fix the LTE issue?
Click to expand...
Click to collapse
No it does not
I got it:
For systemless root, fastboot flash: 1) boot.img; 2) recovery.img; 3) vendor.img; 4) system.img
Boot to recovery and enter sideloade mode. adb sideload [update].zip
Reboot to bootloader. Re-flash TWRP, then in TWRP re-flash kernel (if custom) & superSU.
I used a toolkit to root my 6P. I'm using rooted stock rom. I got an OTA update but it seems I can't update it that way as per all others. So how do I go about installing this on my mobile? Do I need to unroot, flash stock recovery & then flash the new image? Then again I have to root?
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
asj0422 said:
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
Click to expand...
Click to collapse
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
kmp14 said:
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
Click to expand...
Click to collapse
i just tried this again with the same results. it says that the installer is expecting a different build (the one that my settings app shows i'm on) but that i have a build called huawei/mmasomething/ dee_stroyer somethingsomething. (i would post exactly what it says but i've already rebooted into system). I do remember something with "dee_stroyer" when i was rooting but it's not the system...
anyone else have any ideas? i'd like to just update normally and keep my data... and the stock android with root.
EDIT: also, the update won't update my recovery will it? i don't want to have to reflash that. i should be able to update even when i'm away from a computer haha.
Rooted with TWRP. I just tried an ADB sideload and get the same error.

How to ota update rooted phone?

I rooted my phone and don't know how to install ota updates after rooting phone without any data loss...
Can anyone guide me eith full steps?
Ikaushal said:
I rooted my phone and don't know how to install ota updates after rooting phone without any data loss...
Can anyone guide me eith full steps?
Click to expand...
Click to collapse
xiaomi provides ota to all roms just unroot it for a while and u will also loose twrp
Do I need to go back to the default kernel to get the ota ?
Ikaushal said:
I rooted my phone and don't know how to install ota updates after rooting phone without any data loss...
Can anyone guide me eith full steps?
Click to expand...
Click to collapse
You can install ota after being rooted. There is a custom recovery ORANGEFOX RECOVERY which offers ota. You have to install miui from it and after that you can install ota from it.
You can try flashfire. Download it through google play. You won't lose your data nor root. You can google the steps or go to youtube for more info.
If you want to update to latest stable pie,follow these steps:
1. DOWNLOAD THE GLOBAL STABLE 10.1.3
2. disable all MAGISK MODULES
3. reboot to recovery and flash the latest GLOBAL STABLE PIE ROM
4. wipe cache and dalvik
5. FLASH FED 17.3.zip
6. reboot
[email protected] said:
xiaomi provides ota to all roms just unroot it for a while and u will also loose twrp
Click to expand...
Click to collapse
I unrooted the phone but still not able to update it..
SamyakJ said:
You can install ota after being rooted. There is a custom recovery ORANGEFOX RECOVERY which offers ota. You have to install miui from it and after that you can install ota from it.
Click to expand...
Click to collapse
Will give it a try
mecoromeo said:
You can try flashfire. Download it through google play. You won't lose your data nor root. You can google the steps or go to youtube for more info.
If you want to update to latest stable pie,follow these steps:
1. DOWNLOAD THE GLOBAL STABLE 10.1.3
2. disable all MAGISK MODULES
3. reboot to recovery and flash the latest GLOBAL STABLE PIE ROM
4. wipe cache and dalvik
5. FLASH FED 17.3.zip
6. reboot
Click to expand...
Click to collapse
Flashfire has been discontinued
Ikaushal said:
I rooted my phone and don't know how to install ota updates after rooting phone without any data loss...
Can anyone guide me eith full steps?
Click to expand...
Click to collapse
wihout rebooting the device:
install OTA zip from TWRP
restore recovery image (TWRP),
re-install magisk
wipe dalvik/cache
voilà, that's all it needs. I've done it many times running llineage16.
SamyakJ said:
You can install ota after being rooted. There is a custom recovery ORANGEFOX RECOVERY which offers ota. You have to install miui from it and after that you can install ota from it.
Click to expand...
Click to collapse
Does ORANGE FOX works with updating OTA if the /system partion is modified? Getting error 7 in TWRP with decryption. Help please!
I use Magisk :
1) Uninstall Magisk to restore stock boot image
2) Flash the update through TWRP with encryption support
3) Flash Magisk again
nilg0lap said:
Does ORANGE FOX works with updating OTA if the /system partion is modified? Getting error 7 in TWRP with decryption. Help please!
Click to expand...
Click to collapse
See you have to flash ORANGEFOX RECOVERY using any other TWRP recovery. After you have flashed the recovery you have been asked for password just cancel it. Now go to wipe clear data and reboot to recovery(this will decrypt the device). After that you have to copy the desired miui rom and flash it(copy it from your computer or use sd card or usb to flash). After that flash magisk and you are good to go.

About keeping OTA and TWRP

Just unlocked the bootloader , latest MIUI global beta. Here are the questions which needs valid answers
1. Need to flash TWRP and root. Which twrp image will not need any encryption disabler flashed every time I flash a rom? please give the link of the most stable and recent version of it.
2. I will flash magisk. How will it behave with OTA on miui global beta?
3. Will I receive OTA update? If I do, how to flash it properly? I dont want to roll back to stock recovery just to flash an ota and then again flash twrp. And I dont want to flash full rom either.
4. If I am able to flash OTA through twrp, do I have to wipe anything? Im asking if I will loose any data or not.
5. As far as I know, I need to unroot everytime before I flash OTA? what does that mean actually? If im rooted, will I not be notified of the OTA update through the updater app? Or do I have to manually downlaod the ota from the web?
6. And one more thing. I dont want the clock on the top left in any screen, lock or home. Which mod will remove the clock and add regular notification icon? (working with miui beta ofcourse)
Sohan_Saymum said:
Just unlocked the bootloader , latest MIUI global beta. Here are the questions which needs valid answers
1. Need to flash TWRP and root. Which twrp image will not need any encryption disabler flashed every time I flash a rom? please give the link of the most stable and recent version of it.
2. I will flash magisk. How will it behave with OTA on miui global beta?
3. Will I receive OTA update? If I do, how to flash it properly? I dont want to roll back to stock recovery just to flash an ota and then again flash twrp. And I dont want to flash full rom either.
4. If I am able to flash OTA through twrp, do I have to wipe anything? Im asking if I will loose any data or not.
5. As far as I know, I need to unroot everytime before I flash OTA? what does that mean actually? If im rooted, will I not be notified of the OTA update through the updater app? Or do I have to manually downlaod the ota from the web?
6. And one more thing. I dont want the clock on the top left in any screen, lock or home. Which mod will remove the clock and add regular notification icon? (working with miui beta ofcourse)
Click to expand...
Click to collapse
I can answer your questions partially.
2 & 3. Flashing TWRP and Magisk will result in OTA zip not being downloaded. Instead, the full ROM will be downloaded automatically.
4. AFAIK, you can't flash the OTA zip through TWRP.
5. If you want the OTA, you will have to be completely stock, no modifications to system files. Only then the OTA zip will download and only then you can flash it. You will ofcourse be notified of the availability of the OTA zip even if you are rooted but it will not download because it does a check of your system before downloading. Only the full zip will download if you are rooted.
It is much easier (atleast for me) to accept the full download and flash it through TWRP and then boot back to TWRP (to preserve it and to avoid overwriting by stock recovery) before booting into system. If you only wipe Dalvik and cache, there is no need to reflash TWRP and Magisk. Ofcourse if TWRP gets overwritten somehow, then flashing it and Magisk again is not a big thing.
tnsmani said:
I can answer your questions partially.
2 & 3. Flashing TWRP and Magisk will result in OTA zip not being downloaded. Instead, the full ROM will be downloaded automatically.
4. AFAIK, you can't flash the OTA zip through TWRP.
5. If you want the OTA, you will have to be completely stock, no modifications to system files. Only then the OTA zip will download and only then you can flash it. You will ofcourse be notified of the availability of the OTA zip even if you are rooted but it will not download because it does a check of your system before downloading. Only the full zip will download if you are rooted.
It is much easier (atleast for me) to accept the full download and flash it through TWRP and then boot back to TWRP (to preserve it and to avoid overwriting by stock recovery) before booting into system. If you only wipe Dalvik and cache, there is no need to reflash TWRP and Magisk. Ofcourse if TWRP gets overwritten somehow, then flashing it and Magisk again is not a big thing.
Click to expand...
Click to collapse
Thanx a bunch. Now I am ready to flash, but not sure which recovery should I use? and what about that force encryption disabler.zip thing? which recovery wont need that thing? its just too complex to flash various things everytime I update miui rom
Sohan_Saymum said:
Thanx a bunch. Now I am ready to flash, but not sure which recovery should I use? and what about that force encryption disabler.zip thing? which recovery wont need that thing? its just too complex to flash various things everytime I update miui rom
Click to expand...
Click to collapse
OrangeFox Recovery has a feature to disable force encryption without flashing the DFE.zip everytime you flash a custom rom.
And it supports MIUI OTA Updates.
Darklouis said:
OrangeFox Recovery has a feature to disable force encryption without flashing the DFE.zip everytime you flash a custom rom.
And it supports MIUI OTA Updates.
Click to expand...
Click to collapse
can i said like this.
unlock bl and install magisk will not lose any feature of MIUI.
how about custom rom? what feature i need to abandon from stock rom?
locolyric said:
can i said like this.
unlock bl and install magisk will not lose any feature of MIUI.
how about custom rom? what feature i need to abandon from stock rom?
Click to expand...
Click to collapse
unlock bl and install magisk will not lose any feature of MIUI.
Click to expand...
Click to collapse
You will not lose any feature
how about custom rom? what feature i need to abandon from stock rom?
Click to expand...
Click to collapse
Some custom roms are AOSP based so all MIUI bloatware or features are not available in AOSP based custom roms.
Darklouis said:
You will not lose any feature
Some custom roms are AOSP based so all MIUI bloatware or features are not available in AOSP based custom roms.
Click to expand...
Click to collapse
from my last experience unlock bootloader will wipe all f my data. is that same on poco f1?
locolyric said:
from my last experience unlock bootloader will wipe all f my data. is that same on poco f1?
Click to expand...
Click to collapse
Ohh yeah.. Unlocking Bootloader will wipe all data (internal partition and data partition) except on the sdcard partition

Help with Pocophone F1 ROOT

I have a pocophone f1 which I attempted to root.
I already unlocked it using my MI account with MI unlocker on windows.
I installed TWRP 3.2, as well as SupersU.zip in TWRP.
I go and check root access using various root checker apps from playstore but i have no root access. One of them says that my supersu $Path does not contain a binary.
I tried uninstalling superSu using the supersSu uninstaller.zip in TWRP and then attempted flashing magisk, but i got the error about patched boot image. I wiped everything and then flashed stock global ROM for miui 11. Still i get the patched boot image when trying to flash magisk.
Any ideas?
Follow this
Silvershot said:
I have a pocophone f1 which I attempted to root.
I already unlocked it using my MI account with MI unlocker on windows.
I installed TWRP 3.2, as well as SupersU.zip in TWRP.
I go and check root access using various root checker apps from playstore but i have no root access. One of them says that my supersu $Path does not contain a binary.
I tried uninstalling superSu using the supersSu uninstaller.zip in TWRP and then attempted flashing magisk, but i got the error about patched boot image. I wiped everything and then flashed stock global ROM for miui 11. Still i get the patched boot image when trying to flash magisk.
Any ideas?
Click to expand...
Click to collapse
Just uninstall SuperSU root and root again with magisk! There is unroot option in the SuperSU app which you have to use or:
https://forum.xda-developers.com/showpost.php?p=63615067
@Silvershot
My POV: Noone needs to install TWRP to root phone's Android.
jwoegerbauer said:
@Silvershot
My POV: Noone needs to install TWRP to root phone's Android.
Click to expand...
Click to collapse
i just followed a tutorial on xda. what simple method do you know to root a poco f1? i need root urgent
abhi_tech said:
Just uninstall SuperSU root and root again with magisk! There is unroot option in the SuperSU app which you have to use or:
https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
thanks for your reply. I already mentioned i used the supersu uninstaller.zip from the link you provided. but magisk still says the boot image is patched...
Silvershot said:
i just followed a tutorial on xda. what simple method do you know to root a poco f1? i need root urgent
Click to expand...
Click to collapse
It's clear that something has gone very wrong. Instead of wasting time with troubleshooting, I recommend that you restore the phone to its original state via re-flashing its Stock ROM and when that's done retry to root its Android the proper way.
FYI: Once TWRP got installed on phone, you can't get rid off of it unless you re-flash phone's Stock ROM.
jwoegerbauer said:
It's clear that something has gone very wrong. Instead of wasting time with troubleshooting, I recommend that you restore the phone to its original state via re-flashing its Stock ROM and when that's done retry to root its Android the proper way.
FYI: Once TWRP got installed on phone, you can't get rid off of it unless you re-flash phone's Stock ROM.
Click to expand...
Click to collapse
i flashed stock rom. i already said it.... still the problem exists
Silvershot said:
i flashed stock rom. i already said it.... still the problem exists
Click to expand...
Click to collapse
If you flash phone's Stock ROM then neither Magisk nor TWRP is existing , you can't run either of them ...
jwoegerbauer said:
If you flash phone's Stock ROM then neither Magisk nor TWRP is existing , you can't run either of them ...
Click to expand...
Click to collapse
yea, i flashed stock rom, then installed TWRP.
i will now flash stock rom again. i wiped everything using TWRP first.
could you tell me what to do once i flash stock rom again?
i attached a screenshot of trying to flash Force Encryption Disabler V4 for Magisk 18. even the disabler doesnt work... please someone help! i am working with stock clean rom. what is going on
0
Silvershot said:
could you tell me what to do once i flash stock rom again?
Click to expand...
Click to collapse
I could but I don't want to: IMO you simply didn't get it - you do anything without questioning the meaning.
Happy fiddling around with Magisk etc.pp.
jwoegerbauer said:
I could but I don't want to: IMO you simply didn't get it - you do anything without questioning the meaning.
Happy fiddling around with Magisk etc.pp.
Click to expand...
Click to collapse
why are you on this forum if you dont want to help? i explicitly said i tried both supersu and magisk. or how can i root without these 2? why do you say i didnt get it? im pretty sure i did the steps correctly
Silvershot said:
why are you on this forum if you dont want to help?
Click to expand...
Click to collapse
ROFL
BTW: Being active in this forum does not force me to give help in every case. Accept it.
Seppppx said:
You don't have to disable encryption to use magisk. Atleast I think from my experience.
This is the step-by-step tutorial.
1. Flash this global stock miui with TWRP. https://c.mi.com/in/miuidownload/detail?device=1700355 (if this is not the official ROM please correct me, there are a lot of fakes there)
2. Flash Magisk with TWRP. Download and flash it from this github repo. DO NOT DOWNLOAD IT FROM ANYWHERE ELSE!
https://github.com/topjohnwu/Magisk/releases
3. Reboot
Click to expand...
Click to collapse
thank you. this worked. i was using older version of magisk. the latest one did the trick.

Categories

Resources