I have unlocked the bootloader on my encrypted N6 and installed TWRP.
I was invited by my phone to install the 5.1.1 update so I downloaded it, tapped on install and my phone duly rebooted. It booted into TWRP and then nothing happened. I am quite happy to flash the update myself although I'm not sure why it didn't work but I don't know where the update is.
Can I just flash the update like flashing any other ROM using TWRP and if so, where did my phone download the update to?
lotus49 said:
I have unlocked the bootloader on my encrypted N6 and installed TWRP.
I was invited by my phone to install the 5.1.1 update so I downloaded it, tapped on install and my phone duly rebooted. It booted into TWRP and then nothing happened. I am quite happy to flash the update myself although I'm not sure why it didn't work but I don't know where the update is.
Can I just flash the update like flashing any other ROM using TWRP and if so, where did my phone download the update to?
Click to expand...
Click to collapse
no, you can not flash an ota unless you are completely stock with a stock recovery and without any system file changes.
Thank you, that answers that question.
In the past I have always flashed non-stock ROMs and I knew I couldn't install OTA updates but now my phone is at least running a stock ROM. I haven't been in this position before.
lotus49 said:
Thank you, that answers that question.
In the past I have always flashed non-stock ROMs and I knew I couldn't install OTA updates but now my phone is at least running a stock ROM. I haven't been in this position before.
Click to expand...
Click to collapse
Its new since lollipop
Related
I bought the T-Mobile HTC One and then promptly flashed the Google Play edition 4.2.2 ROM and then after that I flashed the 4.3 ROM a few months ago when it came out. But just a few minutes ago I got an OTA notification for 4.3.
I never converted using and RUU or changing the CID/GID or anything complicated like that, I just flashed a ROM in TWRP. Anyone got a clue whats going on?
TheOozyMan said:
I bought the T-Mobile HTC One and then promptly flashed the Google Play edition 4.2.2 ROM and then after that I flashed the 4.3 ROM a few months ago when it came out. But just a few minutes ago I got an OTA notification for 4.3.
I never converted using and RUU or changing the CID/GID or anything complicated like that, I just flashed a ROM in TWRP. Anyone got a clue whats going on?
Click to expand...
Click to collapse
It will still give you the OTA notification and let you download it, it just wont install because of your custom recovery among many other things.
4.3 Build JWR66Y.H1
aooga said:
It will still give you the OTA notification and let you download it, it just wont install because of your custom recovery among many other things.
Click to expand...
Click to collapse
That last part is not quite true, It will install
I just updated with this 15Mb update to 4.3 Build JWR66Y.H1
It booted me into TWRP and installed the update, then rebooted into system, only issue is it's not rooted anymore
Lightning N1 said:
That last part is not quite true, It will install
I just updated with this 15Mb update to 4.3 Build JWR66Y.H1
It booted me into TWRP and installed the update, then rebooted into system, only issue is it's not rooted anymore
Click to expand...
Click to collapse
Thats odd. Maybe it can install minor updates then. When I got the OTA for 4.3 from 4.2.2, TWRP had no clue what to do with the update file and just rebooted.
Okay, so here's the deal.
I have an AT&T HTC One that was running 4.4 Kit Kat (Click: this ROM) and is S-OFF via RumRunner. I am running the latest TWRP recovery.
Yesterday I got prompted for an OTA and accepted it (in the past, with GPE ROMs, it would just reboot to recovery and do nothing). This is the only way I know of to get rid of the annoying "System update available" notification. I figured it wouldn't do anything and I would simply reboot and be good for a few more days until it prompted again. Low and behold, it actually updated my phone to 4.4.2.
Now, I'm having some issues.
I was a user of DashClock Widget...but now I use Better DashClock. However, this app is now prompting me to download a key. When I try to download the key from the Play Store, I get the message:
Error: Couldn't install on USB storage or SD Card.
SwiftKey Keyboard has the same issue.
Other apps (such as ES File Explorer, ESPN, Fandango, etc. update just fine).
-------------
I have read a bunch of posts that suggest cleaning up temp files (which don't exist on my phone) and to download SELinux Mode Changer and change the mode to Passive...but to no avail.
Can someone help me? Is this the developers issue or did my phone do something wonky?
Thanks!
Exactly the same problem here. I've narrowed it down to paid apps that won't install. Followed the same possible solutions in the 1st post, nothing works. HTC One GE 4.4.2.
IlyaKol said:
Okay, so here's the deal.
I have an AT&T HTC One that was running 4.4 Kit Kat (Click: this ROM) and is S-OFF via RumRunner.
Yesterday I got prompted for an OTA and accepted it (in the past, with GPE ROMs, it would just reboot to recovery and do nothing). This is the only way I know of to get rid of the annoying "System update available" notification. I figured it wouldn't do anything and I would simply reboot and be good for a few more days until it prompted again. Low and behold, it actually updated my phone to 4.4.2.
Now, I'm having some issues.
I was a user of DashClock Widget...but now I use Better DashClock. However, this app is now prompting me to download a key. When I try to download the key from the Play Store, I get the message:
Error: Couldn't install on USB storage or SD Card.
SwiftKey Keyboard has the same issue.
Other apps (such as ES File Explorer, ESPN, Fandango, etc. update just fine).
-------------
I have read a bunch of posts that suggest cleaning up temp files (which don't exist on my phone) and to download SELinux Mode Changer and change the mode to Passive...but to no avail.
Can someone help me? Is this the developers issue or did my phone do something wonky?
Thanks!
Click to expand...
Click to collapse
I had a similar problem. I downloaded the 4.4.2 OTA update and tried flashing it with TWRP three different times. All three times I got that same error message with some apps. It was extremely frustrating. I ended up flashing the stock 4.4 recovery and then flashing the update. It worked perfectly and the problem went away. I then reflashed TWRP.
arfon said:
Exactly the same problem here. I've narrowed it down to paid apps that won't install. Followed the same possible solutions in the 1st post, nothing works. HTC One GE 4.4.2.
Click to expand...
Click to collapse
I had a similar experience. Paid apps would not install from Play Store. Amazon app store or F-Droid apps would install.
But my journey was that I had a 4.4 GPE device suffering through an issue where I can't get my bootloader to unlock. So when 4.4.2 came out I wasn't getting the OTA so I tried flashing just the firmware package from the OTA download. That's when I was getting this error (after a factory reset).
But then next day I got the real OTA and after that the problem went away. So for me it was a firmware issue in that it wasn't the right firmware for my OS.
Weird that you are running 4.4.2 but having this issue. Any chance you didn't come to have 4.4.2 the "natural" way?
msw141 said:
I had a similar experience. Paid apps would not install from Play Store. Amazon app store or F-Droid apps would install.
But my journey was that I had a 4.4 GPE device suffering through an issue where I can't get my bootloader to unlock. So when 4.4.2 came out I wasn't getting the OTA so I tried flashing just the firmware package from the OTA download. That's when I was getting this error (after a factory reset).
But then next day I got the real OTA and after that the problem went away. So for me it was a firmware issue in that it wasn't the right firmware for my OS.
Weird that you are running 4.4.2 but having this issue. Any chance you didn't come to have 4.4.2 the "natural" way?
Click to expand...
Click to collapse
Update was OTA last night, so I guess its as natural as it comes.
arfon said:
Update was OTA last night, so I guess its as natural as it comes.
Click to expand...
Click to collapse
Yeah...my process was as natural as possible.
I was on 4.3 at first...so when I was going to 4.4 KitKat I first flashed back to some basic stock Sense ROM to run RumRunner and attain S-OFF. Then I COMPLETELY NUKED my phone and went to 4.4 KitKat. Had no problems, got the OTA, and now this.
It's aggravating, that's for sure.
I really don't want to completely wipe my phone again and have to re-setup all of my home screens, etc.
I received the OTA which installed despite me having TWRP, not stock recovery (as per http://forum.xda-developers.com/showpost.php?p=48586329). Now I have the same issue installing paid apps (the ones I had already installed before the OTA disappeared off the device).
Short of starting from scratch, I'm at a bit of a loss for a solution...
Nick
Sounds like this is wide-spread...or at least amongst the people who are running newer GPE ROMs on their Ones.
im having the exact same issues here
artmunkie said:
I had a similar problem. I downloaded the 4.4.2 OTA update and tried flashing it with TWRP three different times. All three times I got that same error message with some apps. It was extremely frustrating. I ended up flashing the stock 4.4 recovery and then flashing the update. It worked perfectly and the problem went away. I then reflashed TWRP.
Click to expand...
Click to collapse
Can you point me to where you got the stock recovery from please?
Fixed
It looks like this is all to do with custom recovery and OTA updates. I have TWRP installed. This morning I flashed stock recovery. I then put the OTA update file on the phone storage. Then booted into the stock recovery (which is the first time I've seen it, it would be nice if it was the last as it's tricky to get into), then flashed the 4.2.2. update from there. Once I booted the phone again all my paid apps reappeared. No data lost in the process. I'm not sure if going back to TWRP not will cause the problem again, so for now I'll stick with stock recovery....
arfon said:
It looks like this is all to do with custom recovery and OTA updates. I have TWRP installed. This morning I flashed stock recovery. I then put the OTA update file on the phone storage. Then booted into the stock recovery (which is the first time I've seen it, it would be nice if it was the last as it's tricky to get into), then flashed the 4.2.2. update from there. Once I booted the phone again all my paid apps reappeared. No data lost in the process. I'm not sure if going back to TWRP not will cause the problem again, so for now I'll stick with stock recovery....
Click to expand...
Click to collapse
Can you please detail the procedure ?
If possible including where you got the files (OTA and stock recovery ) and how to put OTA on the sdcard to "provoque" que update.
Thanks in advance!
franciscols said:
Can you please detail the procedure ?
If possible including where you got the files (OTA and stock recovery ) and how to put OTA on the sdcard to "provoque" que update.
Thanks in advance!
Click to expand...
Click to collapse
This.
Also, you left 4.4.2 on the device and just 're-applied' the OTA update? Or did you go back to a NANDROID backup of you on 4.4 or 4.3?
arfon said:
Can you point me to where you got the stock recovery from please?
Click to expand...
Click to collapse
Here you go! I can't remember the thread where I found it, so the file is attached. Just to be clear, this is the stock Android 4.4 recovery for the HTC One GPE.
artmunkie said:
Here you go! I can't remember the thread where I found it, so the file is attached. Just to be clear, this is the stock Android 4.4 recovery for the HTC One GPE.
Click to expand...
Click to collapse
So I flash this recovery and then flash the OTA update (this one?) and I should be good?
IlyaKol said:
So I flash this recovery and then flash the OTA update (this one?) and I should be good?
Click to expand...
Click to collapse
Yeah, that's about it. I used adb to flash the stock recovery to replace TWRP, then used the stock recovery to flash the same update you linked to. After it was done updating I reflashed TWRP. And don't forget to make a nandroid.
Thank you! Will report back when I'm done!
What is the fastboot command to flash the OTA zip file?
I'm back on the stock recovery...phone is still booting/working so I just need to do the OTA part now.
IlyaKol said:
What is the fastboot command to flash the OTA zip file?
I'm back on the stock recovery...phone is still booting/working so I just need to do the OTA part now.
Click to expand...
Click to collapse
Sorry, hectic day at work. I should have said that I applied the update with the stock recovery. Not fastboot.
I basically used the guide linked below to flash the update.
Read Step 2
http://www.androidpolice.com/2012/1...e-nexus-7-now-manual-download-link-available/
artmunkie said:
Sorry, hectic day at work. I should have said that I applied the update with the stock recovery. Not fastboot.
I basically used the guide linked below to flash the update.
Read Step 2
http://www.androidpolice.com/2012/1...e-nexus-7-now-manual-download-link-available/
Click to expand...
Click to collapse
What if you don't have an "apply from adb" option?
I have:
- reboot system now
- apply from sd card
- apply from phone storage
- apply from cache
- wipe data/factory reset
- wipe cache partition
Can't I just open a ADB shell while on the fastboot USB option?
I've got a question.
My moto g is rooted and has got a custom recovery installed.
Today I got the notification for the ota Lollipop update.
I wondered what would happen if I installed with the ota update?
Is there a way to disable checking for updates as I'm not interested in Lollipop an don't want to be bothered by the constant notifications?
schpongo said:
I've got a question.
My moto g is rooted and has got a custom recovery installed.
Today I got the notification for the ota Lollipop update.
I wondered what would happen if I installed with the ota update?
Is there a way to disable checking for updates as I'm not interested in Lollipop an don't want to be bothered by the constant notifications?
Click to expand...
Click to collapse
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.
Lucian Armasu said:
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.
Click to expand...
Click to collapse
Ok.
But i'm not really interested in the update anyway.
I would just prefer to stay on kitkat at the moment because I'm not convinced that lollipop is an "upgrade".
How do I turn of the constant notifications? I have already "froze" the update service with titanium backup but that didn't seem to help.
Lucian Armasu said:
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.
Click to expand...
Click to collapse
Because OTA.zip has to be used with stock recovery , unrooted and /system files unaltered - not for use via TWRP
If you ever want to reflash your phone to stock plenty of guides how to... or if xt1068 just use my signature links
Hello XDA,
Im quite sure this has already been asked on the forum but i couldn't find an answer.
I need some advise about my recently rooted Nexus 6. I want to fully enjoy from a custom recovery but i dont want to lose the option of receiving OTA updates to my phone.
What do you guys do so your nexus keeps getting the lastest of Android?
Can i use WugFresh's root toolkit to sideload OTA updates even when i have a custom recovery?
What other ways can i use to update Android?
Thanks,
No but you could use the tool kit to reload recovery and stock then take your OTA then reroot and reload TWRP.
And you can side load but it is important you understand exactly what you're doing. the kit does nothing more than you can from the command line it just tries to save you from yourself. it can be a help or hindrance. If you don't understand what's going on it will be the latter
Sent from my Benzo'd Google N6 on VZ
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Agreed. OTA is overrated. If I was on T-Mobile or the factory image was not available. I would grab the radio and load what I wanted.
Now I am running the E radio and the i build on VZ
Sent from my Benzo'd Google N6 on VZ
Didgeridoohan said:
you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
torecdude said:
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
Click to expand...
Click to collapse
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Evolution_Freak said:
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Click to expand...
Click to collapse
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Updating via OTA on a Nexus is an undesirable method IMO. As mentioned previously, if you download and flash the factory images, you avoid the potential update failures in an OTA from modified stock parameters. As for recovery, you don't need to flash a custom recovery, you can simply boot a custom recovery from the PC using fastboot and having the recovery image of choice in your platform tools.
fastboot boot name_of_recovery_image_here.img
I don't flash from the device any more. Keeps me out of trouble. Being connected to the PC helps remind me to move a copy of my backup to the PC before flashing.
torecdude said:
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Click to expand...
Click to collapse
I put the link to that thread in mine as a quick way for people who are rooted/unlocked and running a custom recovery to find. Those are not the "official" way of updating. They work because someone here put the time in to make them work for unlocked/rooted users. No, you can't use an "official" OTA process if you've altered your device but that method uses TWRP to flash just like you were flashing a custom ROM.
I'm glad my thread has helped you! Since I'm not a developer yet, it is my sole purpose here to help users with anything I can. So a comment like that is very reassuring that I'm on the right path.
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
You cannot apply Google OTA updates with a custom recovery. Replace your recovery with the stock version and try again.
Not just custom recovery - any system change such as root will stop the OTA. Depending on how you rooted, you might be able to unoot using the built-in SuperSU function (I'm guessing Supersu?) but more likely than not it still won't work.
The simplest thing to do is forget about the OTA entirely. Download the full ROM from Google, unzip it, unzip the zip inside the zip, and there you'll find system.img, which you can flash in Fastboot, then reroot. Done.
sonic2kk said:
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
Click to expand...
Click to collapse
How did TWRP ended on your phone in the first place?
istperson said:
How did TWRP ended on your phone in the first place?
Click to expand...
Click to collapse
I installed TWRP.
Thanks for the suggestions everyone!
sonic2kk said:
I installed TWRP.
Thanks for the suggestions everyone!
Click to expand...
Click to collapse
Oh, then as other people said, if you want OTA then totally unroot it, then reflash system of the current version, and flash stock recovery. But it's much better when a new version arrives, just download it, flash system and boot, reroot it, clear cache and dalvik. This way you'll have your updated Android days or even weeks before the OTA.