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.
Related
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.
Hi all, I have just recently purchased a new OnePlus 3 from one of the distributors listed under OnePlus's website. I've been waiting for the 3.2.1 OTA update for a while and its finally in my region. However after it finishes downloading and I press install, the phone reboots and after a while it would appear a screen which says "Installation Failed" with nothing else but a Reboot button. Can anyone shed any light on this potential problem or is it isolated to just my device? Is it possible for me to completely reinstall OxygenOS on the phone again? (wipe the phone and reinstall android + oxygen's). Also when I bought the device and first booted it, I noticed that there was some apps already installed( apart from stock google ones). These looked like malware to me and it doesn't allow me to uninstall them(from app drawer or from settings), is there anyway i can uninstall them as well?
Thanks in advance
I see no one replied to this topic, sadly. I am experiencing exact the same issue. Currenty I am on OxygenOS 3.1.3. When I go to system updates it says OxygenOS 3.2.6 is ready to download. I hit download, it downloads, reboots but then it says the update failed and I can only reboot.
Anyone knows a solution? Would be nice if I could update my phone
if your bootloader is locked and you dont want to unlock it, then you can download the full rom from oneplus's official website and sideload through command prompt. instructions are available there on their website.
If your bootloader is unlocked and you have latest twrp, just use the below link to download the full rom and flash it via twrp.
if you want to do a clean install with twrp go to wipe the select everything and wipe. this will delete everything on your phone including the os. remain in twrp and connect your phone to your pc and copy paste the rom in twrp folder in your phone and flash it.
https://www.androidfilehost.com/?fid=457095661767098500
My oneplus 3, 3.2.8 ota will not update and fails. Device was rooted but is now unrooted w/ stock 3.2.7 w/ twrp recovery. I also flashed back stock recovery and still the ota fails to install. Any idea how to fix this or why it is happening? Bootloader is unlocked as well.
jamjr74 said:
My oneplus 3, 3.2.8 ota will not update and fails. Device was rooted but is now unrooted w/ stock 3.2.7 w/ twrp recovery. I also flashed back stock recovery and still the ota fails to install. Any idea how to fix this or why it is happening? Bootloader is unlocked as well.
Click to expand...
Click to collapse
Try using moded twrp from this post http://forum.xda-developers.com/oneplus-3/how-to/guide-how-to-flash-3-5-4-cb-breaking-t3482572
I have a system update available, but whenever I try to flash it, it ends in an Error 7 in TWRP. The stock rom, I did a factory restore on it. But it was rooted with magisk, and phh superuser before I had to do the factory reset on it. Could it be some of the SuperSU stuff is left over and that is why it keeps throwing that error?
you've provided zero information about your current setup and what version you're updating from/to
you could be talking about OOS OTA updates or CM OTA updates or even a custom CM-based ROM OTA update for all we know.
Sorry, it is oxygen OS, version 3.2.4. I think it updating to version 3.2.5. I did a factory reset, and have not rooted or anything with the exception of flashing Twrp.
Flash patched TWRP via fastboot.
Tried to side load it, it still failed with error 7.
Edit: It looks like I am trying to go from 3.2.4, to 3.2.6. But still not sure what if stopping me from being able to install the update.
Hi.
- I flashed TWRP using ADP, flashed root to change fonts but used Stock OOS 3.2.4
Now i sold device.=, to buy black one or iPhone
- I done data reset in TWRP to unroot, after reboot SU App was gone.
- I flashed stock recovery via ADB
- I left the bootloader unlocked, i was not sure of comand, plus in case of mess up, i could fix it.
New user has no idea as well, he says now when he installs OTA 3.2.6 it fails to install.
What i am missing? how can i fix this?
Help will be much appreciated, thanks in advance.
EDIT: SOLVED
When i locked bootloader, it took me to bootloap, and when i try to sideload new OOS3.2.4 it gave ever, cannot read file.
- I flashed new official TWRP again.
- I flashed stock 3.2.4 with TWRP
- Set up OS
- Flashed stock recovery, in fastboot by doing USB debugging on
- Locked bootloader by "fastboot bootloader oem lock" right after stock recovery
- Set up OS 3.2.4 again, at this moment 3.2.6 fail to down over the air
- I downloaded stock 3.2.6 incremental update, successfully downloaded and install.
Now phone seem to be at stock. I bought it back from to save him from inconvenience, as he was scared as the phone was failing to install update initially.
Also interested on this, same thing happened with me and a friend, modded his phone, he didnt want it modded anymore, flashed a clean stock OOS, flashed stock recovery, and error on install of 3.2.6 OTA, if anyone have any idea how to recover the ability to OTA, appreciated.
What happens if you try to sideload it
https://forums.oneplus.net/threads/...root-non-root-users-without-data-loss.451853/
khaos64 said:
What happens if you try to sideload it
https://forums.oneplus.net/threads/...root-non-root-users-without-data-loss.451853/
Click to expand...
Click to collapse
When i sideload oos.zip which is 3.2.4, it says cannot read zip.
When i relock bootlaoder, it goes into bootloap, i go back to fastboot and unlock bootloader, it boots back into old stock OOS 3.2.4. This rom still has my changed fonts, which i had when i had root and TWRP.
I know there was a firmware change with 3.2.6, so if you flashed the 3.2.6 recovery with OOs 3.2.4, this could possibly be your issue.
Boot into Twrp, don't need to flash it. Clean flash 3.2.6, reboot. Try relocking bootloader see if you still get boot loops.
I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.