I have a Nexus 7 (2013) with TWRP recovery and CleanROM installed do I have to return to the stock ROM or do anything else before flashing Android L?
matt_man said:
I have a Nexus 7 (2013) with TWRP recovery and CleanROM installed do I have to return to the stock ROM or do anything else before flashing Android L?
Click to expand...
Click to collapse
No. Make a nandroid. Use the flash_all batch file after modifying it by removing the -w from the text using a text editor like notepad. Removing the -w text will prevent your storage from being wiped. Using the flash_all batch file will replace TWRP with the stock recovery. Or you can fastboot flash the bootloader, boot and system images, this way you don't have to replace TWRP. With a major update it will probably be more reliable if you do a factory reset from inside TWRP (will not wipe storage) before flashing the new OS (Android L). You will also need the SuperSu zip on your device so that you can install it with TWRP if you want root.
Edit: As it turns out you need a modified version of the stock kernel for root to work and the correct version of supersu. I flashed the L preview last night and flashed SuperSu v2.13 and the binaries didn't work so I just blew it off because I had no plans to stay on the preview. After maybe an hour I went back to 4.4.4 anyway Right now I'm not a big fan of a lot of the UI changes.
Related
Hi,
I recently purchased a used Galaxy Nexus which came with root, CWM, and the stock 4.2.2 ROM. I tried searching and couldn't find a direct answer so I'm hoping someone can help me with the following question.
Can I flash the next available Verizon Stock Image using the custom CWM recovery? I would be getting the factory image from the Google Developers Site.
I'm used to flashing custom ROMs where I would wipe and flash, but I'm not sure if this works for factory images. I would like to keep root and CWM, but just want to flash images from Google rather than wait for Verizon's OTA push.
Sorry for the noob question.
Peter
factory images dont work like that. you flash them from fastboot/bootloader
but lets think for a moment.
what is root?
essentially it is comprised of superuser.apk and an su binary
that su binary is installed to /system
when you install ANY rom, that rom will wipe and take over /SYSTEM
how exactly would you retain root access that way unless that su binary is included in the /system image?
you can flash the system image from the stock factory image files (extract it out and in fastboot/bootloader mode, run 'fastboot flash system nameofsystemimg.img', that wont touch your recovery partition
then you can just re-root it by flashing the superuser.zip from CWM
in case of a bootloop after rebooting, just boot back into recovery and do 'factory reset' ( you will lose all your installed apps/settings/sms/call log/etc)
Thanks for the detailed explanation, it was very helpful. Just to make sure I'm clear, ROMs which are flashed that don't make you lose root access are the ones with the SU Binaries built in? e.g. Cyanogenmod.
I believe there was a version of Android 4.2.2 which was released which was geared towards rooted users. I'm assuming this is a modified version of the factory image. Is that also correct?
There are quite a bit of 4.2.2 roms, and all the roms on here are rooted, unless you were to just install the factory image.
I recommend just flashing the google factory image, then flash a recovery.img that is TWRP or ClockworkRecoveryMod (Do this in command line or if you wanna risk it, a toolkit) and flash a supersu.zip from chainfire.
peterwong26 said:
Thanks for the detailed explanation, it was very helpful. Just to make sure I'm clear, ROMs which are flashed that don't make you lose root access are the ones with the SU Binaries built in? e.g. Cyanogenmod.
I believe there was a version of Android 4.2.2 which was released which was geared towards rooted users. I'm assuming this is a modified version of the factory image. Is that also correct?
Click to expand...
Click to collapse
Root is only applicable to the OS itself so yes ROMs already contain the necessary binary and apk
Sent from my Galaxy Nexus
Guys I am facing this weird issue. Earlier I had TWRP installed on my nexus 7 with android 4.4.2 but since I was unable to install any OTA updates for 4.4.4 I figured maybe it was an issue with the TWRP so I wanted to get rid of it. I used One Click Factory Restore 4.4.4 KTU84P tool in the dev forums and it kinda did restore my tab to a stock version. The issue is now when I try to boot into recovery mode, it shows an error logo and seemingly there is no recovery installed. How do I go to stock recovery from here? Any help will be appreciated.
Thanks
ammy_91 said:
Guys I am facing this weird issue. Earlier I had TWRP installed on my nexus 7 with android 4.4.2 but since I was unable to install any OTA updates for 4.4.4 I figured maybe it was an issue with the TWRP so I wanted to get rid of it. I used One Click Factory Restore 4.4.4 KTU84P tool in the dev forums and it kinda did restore my tab to a stock version. The issue is now when I try to boot into recovery mode, it shows an error logo and seemingly there is no recovery installed. How do I go to stock recovery from here? Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
If you mean by error logo, you see an image of an android on its back, that is recovery, stock recovery. You can still use the OTA with TWRP, so you pretty much wasted your time removing it, the only difference is with TWRP you have to flash the OTA manually (the OTA zip is located in /cache).
So reinstall the latest TWRP, and reroot, and have fun with 4.4.4.
If you want your device to be even more useful and future upgrades to be easier, instead of leaving normal TWRP on it, after rooting, install MultiROM along with its modified TWRP, and make your device even better.
I got the notification about the 5.1 OTA update on my Nexus 7 2013, downloads fine, but can't install because I have TWRP and a custom kernel. What should I do to update it?
EDIT: so I flashed the stock recovery with Wug's root toolkit, and tried to install it again. When I press the button to reboot and install the update, it gives just an error message and a picture of an android laying on his back with a red exclamation mark
What else should I do?
Turns out that with Wug's toolkit the stock recovery will not install, this is the actual problem, is there any other way to get back the stock recovery?
Flash the update from /cache
I tried it but won't install.
It says: E: Error executing updater binary in zip ' /cache/update.zip'
Under the advanced options you should be able to flash the stock recovery if that's what you want to do.
scrosler has a pre-rooted stock 5.1 TWRP-flashable ROM and a flashable bootloader zip. I just flashed those and everything is working fine.
Szighy said:
EDIT: so I flashed the stock recovery with Wug's root toolkit, and tried to install it again. When I press the button to reboot and install the update, it gives just an error message and a picture of an android laying on his back with a red exclamation mark
What else should I do?
Click to expand...
Click to collapse
I'm going to add onto this question. OTA update won't work for me. The red android comes up.
I had flashed android 5 with wugfresh, rooted, unlocked bootloader. I don't think I modified the system after that. I tried to unroot and flash stock recovery and bootloader. No change to the OTA failure.
I see that there was a bug with the 2012 nexus 7 bootloader that would cause this. Google coincidentally just updated that bootloader, perhaps to fix said problem. But I'm not sure what to do about my particular 2013 razor/flo problem.
Does anyone know how to get OTA updates working with a stock rom you flashed yourself?
Edit: Wugfresh says it is impossible to OTA update a rooted android 5 lollipop device? http://forum.xda-developers.com/showpost.php?p=60262545&postcount=1072
Edit 2: I unrooted but that still didn't work. To workaround, I extracted system.img from the factory image zip for the same version of the OS I currently have. Then I wrote that image to the system partition using the universal android toolkit img flash feature (#11.). The system and data seemed identical upon boot. Now the OTA update will work naturally. But this has all been very confusing! Many mixed messages were found by google searching.
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Sebacestmoi said:
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Click to expand...
Click to collapse
If you had TWRP touch your /system in R/W mode even if it made no changes, the system partition is tainted (there is meta-data that changed)
The only practical way to get back to untainted /system is to flash the stock system.img. The flashing is simple, but it might take a little time to download the factory image and extract the system.img.
I usually keep twrp in the recovery partition, probably chainfire has something to boot twrp directly. I do know that if you boot twrp over usb there is a problem where it doesn't accept your pin/pattern/pass to decrypt the user partition. I don't know if it suffers the same problem through other booting methods.
BTW even with systemless root, you cannot flash the differential OTA you receive over the air directly. You need to restore the stock boot.img before flashing the OTA.
The FULL OTA you get from the factory image website, on the other hand, can flash over anything, regardless of whether you have boot, system, or vendor modified.
Thank you for the clear answer
Sebacestmoi said:
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Click to expand...
Click to collapse
The command
Code:
[I]fastboot boot <img file name>[/I]
will boot twrp from your computer with out having to install it.
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.
simply flash the OTA, then re-root
xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O
Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!
xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.
Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe
toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!