Develop Bugs

update to KRT16S while keeping root?

I just got the KRT16S OTA update, how can I update keeping root? Would root keeper do the trick?

You'll lose root, but you can root it again by installing supersu binary from recovery mode or custom recovery.
Sent from my Nexus 7

Worked. Thanks

I received the OTA update (SRT16S) this evening. I was previously rooted with SuperSU 1.69 and TWRP.
When I boot into recovery, it comes up and says "No command" -- how do I re-install SuperSU?
My Nexus 7 works fine otherwise, just no root.

ncshawng said:
I received the OTA update (SRT16S) this evening. I was previously rooted with SuperSU 1.69 and TWRP.
When I boot into recovery, it comes up and says "No command" -- how do I re-install SuperSU?
Click to expand...
Click to collapse
Same way you installed the first time.
boot to bootloader
fastboot boot twrp.img
choose install
select supersu update.zip

sfhub said:
Same way you installed the first time.
boot to bootloader
fastboot boot twrp.img
choose install
select supersu update.zip
Click to expand...
Click to collapse
Ok, thanks -- that's what I figured it would have to be but wanted a confirmation.

[Q] TWRP doesn't install recovery

So i went through the rooting process just fine. Go to install TWRP with the Install TWRP app. When i get to the install part, i choose the recovery version to install then click install recovery, reboots found then i get a dead android with a red triangle.
From what i assume something is locked. the bootloader i believe?
I've searched and searched and all i can seem to come up with is having to downgrade to kitkat. Is this true and no way around it?

I think you are on lollipop .. Cos it doesnt work on lollipop

forget about twrp manager. use auto rec to get custom recovery.
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

Take a look at this, it is a response to rooting and getting TWRP on 20l
http://forum.xda-developers.com/showpost.php?p=61029248&postcount=2431

kp_q said:
forget about twrp manager. use auto rec to get custom recovery.
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
Click to expand...
Click to collapse
for some reason when i first tried this nothing happened the other day.
just tried it again and it did install TWRP for me finally. So thanks!:good:

Custom recovery issues! Help please!

Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?

Suren Manukyan said:
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Click to expand...
Click to collapse
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!

I'm experiencing this issue as well. I tried to install TWRP after installing that October security updates. I wonder if there's something in the update that is preventing TWRP from installing?

hilla_killa said:
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
Click to expand...
Click to collapse
It has something called perm.flash.recovery.zipor something which is described to do the thing you said but the problem is when the phone gets the" flash perm.flash.recovery.zip" it does nothing. It does nothing even when I try to flash it manually when I get the "trial" TWRP which disappears after rebooting.

Had the same problem. I solved it by using the old fashioned way, with fastboot commands found on the TWRP page: https://twrp.me/devices/lgnexus5x.html
Of course, I used the last image: twrp-3.0.2-2-bullhead.img

stuck in twrp after OTA update

i installed the official nougat update via VPN. Then rooted my op3 with nougat using modified twrp. Today i receieved OTA of 30mb, i downloaded it and click reboot. And then the problem started. The device continues to boot in twrp and im not able to use my op3.
Please HELP.......!!!!!!!!!!!!!!!

You messed up! Everyone knows that before flashing ota you should be on OnePlus recovery now you can sideload oos or flash through twrp.

neeraj679 said:
You messed up! Everyone knows that before flashing ota you should be on OnePlus recovery now you can sideload oos or flash through twrp.
Click to expand...
Click to collapse
should I flash any other rom or the oos 4.0...???

pranav_j619 said:
should I flash any other rom or the oos 4.0...???
Click to expand...
Click to collapse
which twrp version are you using? also do you have encryption issues in twrp? you might not need to reflash the rom butmay be reset the phone and install updated twrp. there are couple of threads. i myself saw this issue on my device

I faced the same issue. Just flash the stock recovery and boot the phone. The update will fail and you'll be back on.

You can flash newest BluSpark TWRP and the the 4.0.2 Full ZIP, then it should work

This is the solution that worked for me
MM MaD said:
I faced the same issue. Just flash the stock recovery and boot the phone. The update will fail and you'll be back on.
Click to expand...
Click to collapse
I had the same issue, flash the stock recovery 2.0 on the phone (the one that takes 64Mb) and then boot the phone. As mentioned it'll fail but then you get out of the loop and can flash whichever recovery and rom you feel like. And thanks for the people that mirrored the recovery while it was not on the official page, and to the people that suggested this, it was a pain to fix the first time.

pranav_j619 said:
i installed the official nougat update via VPN. Then rooted my op3 with nougat using modified twrp. Today i receieved OTA of 30mb, i downloaded it and click reboot. And then the problem started. The device continues to boot in twrp and im not able to use my op3.
Please HELP.......!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Had this issue before, just look on your internal memory, there is a folder called ".OTAsomething", in there the OTA zip is stored, delete it and the phone will boot to Oxygen OS again.

OTA-Update does not work

Hi,
I have Stock Android 8.1.0 ROM from February installed and also Magisk.
I wanted to install March OTA-Update but it just throws "Error" while trying to install OTA-update and reboots back to previous ROM with the hint, that "update could not be confirmed".
Any ideas how to get OTA-Updates to work?
Regards

jsfgsdfhakjf said:
Hi,
I have Stock Android 8.1.0 ROM from February installed and also Magisk.
I wanted to install March OTA-Update but it just throws "Error" while trying to install OTA-update and reboots back to previous ROM with the hint, that "update could not be confirmed".
Any ideas how to get OTA-Updates to work?
Regards
Click to expand...
Click to collapse
OTA's won't work if you're rooted. Get Chainfire's flashfire and flash the ota there. They're are options to retain custom recovery and root.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
OTA's won't work if you're rooted. Get Chainfire's flashfire and flash the ota there. They're are options to retain custom recovery and root.
Click to expand...
Click to collapse
Hi,
but should it not be the reason of using Magisk, that OTA updates are functioning, because it doesn't change the system file system?!
Or does OTA system update also checks the boot loader integrity before updating?
At what state of changing device do OTA updates not work anymore?
Already after unlocking bootloader?
Is there no possibility to get root access and Google OTA updates beside Chainfire's Flashfire?

Magisk, as well as SuperSU, are both systemless root methods. But they also affect the boot image. You need the stock boot image for the ota to work. Magisk can revert the boot image to stock, but I'm much more familiar with using flashfire.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Magisk, as well as SuperSU, are both systemless root methods. But they also affect the boot image. You need the stock boot image for the ota to work. Magisk can revert the boot image to stock, but I'm much more familiar with using flashfire.
Click to expand...
Click to collapse
I restored boot image, tried flashfire but nothing worked for me on my phone.
OTA update still throwed the error after restored boot image.
flashfire throwed a black screen after rebooting and did nothing for a lot minutes. I did a hard reboot after some time.
Finally I did the update manually:
image backup with TWRP boot loaded by Fastboot only
download Google stock ROM from march
extracted ROM
disabled wipe parameter in flash batch file
flashed now
reinstalled current Magisk by TWRP boot loaded by Fastboot only
Finished. :silly:

Nexus 5x
I tried using flashfire myself and got the same results that you did. Thanks for the info. I guess we have to flash the entire ota zip from the google developer site and not just the update.zip.
jsfgsdfhakjf said:
I restored boot image, tried flashfire but nothing worked for me on my phone.
OTA update still throwed the error after restored boot image.
flashfire throwed a black screen after rebooting and did nothing for a lot minutes. I did a hard reboot after some time.
Finally I did the update manually:
image backup with TWRP boot loaded by Fastboot only
download Google stock ROM from march
extracted ROM
disabled wipe parameter in flash batch file
flashed now
reinstalled current Magisk by TWRP boot loaded by Fastboot only
Finished. :silly:
Click to expand...
Click to collapse