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.
Related
My 4.4.3 OTA installed just fine this afternoon and I immediately grabbed the latest SuperSU .zip and installed it with TWRP to get re-rooted, but after I told SuperSU to get itself re-installed from Google Play, it wanted to update the binary, and the "normal" method wouldn't work, even after a couple of reboots and retrys.
I don't have TWRP installed on my Nexus 7, instead just using fastboot to boot it when I need it for something, so the technique that finally got the binary updated was to tell SuperSU to use the TWRP update mode, then when it I got the popup saying it was about to reboot to recovery, I plugged in the USB cable and ran:
adb reboot bootloader
fastboot boot openrecovery-twrp-2.7.1.0-flo.img
That worked. As soon as TWRP booted, it installed the script SuperSU had prepared for it, and the binary was indeed updated.
I never had a problem with the "normal" binary update method before. Something new and "helpful" in 4.4.3 I guess.
You can share the script SuperSU?
RazrBR said:
You can share the script SuperSU?
Click to expand...
Click to collapse
If still having issues, try the 1.99r4 from the link in my signature.
Hello,
I have TWRP installed and I would like to install the OTA update using the manual method (http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835)
However, each time I try, it just boots me in TWRP and nothing applied... anything I can do?
JulioQc said:
Hello,
I have TWRP installed and I would like to install the OTA update using the manual method (http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835)
However, each time I try, it just boots me in TWRP and nothing applied... anything I can do?
Click to expand...
Click to collapse
NO
Ok!
reverted to stock recovery, removed root, applied OTA, switched to TWRP
all is working now
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
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
Running stock image with root, is it usually safe to take ota's?
You will receive error when installing the OTA. Unroot and then update, or... since you already have the bootloader unlocked (for rooting) you can flash from a PC the latest factory image (with the -w removed form the flash-all.bat script).
If you use magisk, you can go into it and select uninstall and restore images. Do not reboot your phone. Install the OTA and once you're at step to, go into magisk and select install and select the OTA option. Wait for the update to finish and reboot. Afterwards you're rooted and updated.
severedsnake said:
Running stock image with root, is it usually safe to take ota's?
Click to expand...
Click to collapse
Magisk Uninstall never worked for me for some reason.
Download OTA to PC
Boot into TWRP
ADB Sideload OTA
reboot
powerdown
Boot into TWRP again
flash Magisk.zip
Done
You can even flash the OTA.zip in twrp as well. When done, just fastboot into twrp, flash the twrp installer zip, then kernel, then magisk, reboot, done :good: