[Q] System update prompt after manual 4.4 install and root - Nexus 7 Q&A, Help & Troubleshooting

I'm on the first release of 4.4. Now an update has appeared and wants me to restart. Should I do it? Can I ignore (remove) the warning? If I let it update will it screw up my well functioning ROM? Will I just have to re/root? What is the meaning of life?
Skip the last question, I was getting carried away.

It came out yesterday...its safe to go ahead and update, its only a couple MB in size...You won't lose data or anything however some people have had to re-flash superSU as well as re-flash custom recovery...nothing too difficult
This thread may be of interest to you

bobbytomorow said:
It came out yesterday...its safe to go ahead and update, its only a couple MB in size...You won't lose data or anything however some people have had to re-flash superSU as well as re-flash custom recovery...nothing too difficult
This thread may be of interest to you
Click to expand...
Click to collapse
I went to do it...got to part where CWM warned me that it was unsigned...and I chickened out. I have no idea what the update even was. Does anyone have a flashable zip (or know where the update download is stored)

You can get a flashable zip here

bobbytomorow said:
You can get a flashable zip here
Click to expand...
Click to collapse
Hey! That's very nice of you sir
Edit: what's in the update anyway?.

Nothing that I've noticed, everything seems the same...here is the official changelog

bobbytomorow said:
Nothing that I've noticed, everything seems the same...here is the official changelog
Click to expand...
Click to collapse
Anyone notice constant buffering issues.... Like in YouTube?

Related

Root, OTA, Market update

Hi guys, after a 6 months period with HTC Wildfire S, i decided it was time to upgrade my device, so here i am, a newbie Nexus S user.
The first things i did with my new toy were unlocking the bootloader, gaining root permissions and installing CWM.
But i noticed that Market isn't updating, it's stuck to THIS version (i think it's 2.13)
Has this anything to do with root and cwm? Or it's just a matter of time and i'll eventually get the update?
Same thing with firmware: at the moment i'm running 2.3.3: looking for updates, and even using the *#*#checkin#*#* code, provided the same result: no FOTA available. Is this due to the root+cwm or i just need to wait?
I know this has already be discussed in the faq, but i find them quite confusing.
I mean, i know i could do a manual update, but i'd like to know whether if i'll ever receive a fota update or if i've lost this chance after root.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Click to expand...
Click to collapse
Thanks in advance for the answers!
There is no update due to the root, i advice you to manually update your phone to the latest version 4.0.3 using cwm, after that root again. finally you will have rooted ics on your nexus s.
uhm, you say i won't receive updates.
FAQ says most of the time i won't receive them.
THIS thread says i will receive them.
I am confused.
from what I can make sense of, it sounds like you should be getting updates. The FAQ you posted says that if you try to install one of the official OTA updates through CWM, it will fail most of the time.
i don't know how reliable that "checkin" trick is, and it may depend on your carrier as well.
if you've already rooted your device, then i would just flash one of the custom roms, you won't want to go back to the OTA after...
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
albundy2010 said:
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
Click to expand...
Click to collapse
Thats correct. It has only to do with the install. (It will fail).. if you dont get the notification for an ota i dont know whats wrong...
Sent from my Nexus S using xda premium
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
If you had 2.3.3 the update was probably the 2.3.6 and after that you would have received the 4.0.3 update....anyway from what I remember the version of the ota update is showed in the notification bar...isn't it?!
Sent from my Nexus S using XDA
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
1. I assume it was the a step up from 2.3.3 to a max of 2.3.6 as OTA updates to 4.0.3 are currently on hold due to battery drain issue
2. your OTA install is failing because you have custom recovery (CWM) but the OTA updates require the stock recovery (3e)
if you really really want to install OTA updates, you gonna have to go back to stock recovery (do a nand restore, hope you have one) then flash the OTA updates for your device

[Q] OUYA-StockPlus and updateing

hey guys this is my first android device il be getting it in a few days and my question is if I install OUYA-StockPlus will i be able to update my OUYA though the console or will I have to block updates and only update though a new flash when a new version of stock plus comes out?
Updates are blocked in this rom because the OTA updates overwrite CWM recovery and remove root. I wouldn't expect a new rom for every Ouya update either, only the updates that make major changes.
Also, since this is your first Android device, be very careful. As of right now there is no way to restore your device if you overwrite your kernel. It is also a real pain if you lose access to adb.
What if say someone else started your ouya and installed the update without knowing that they weren't supposed to would it corrupt it or would the ota install as its supposed to and you would just lose root and your rom. Im just wondering cuz I have already installed the playstore and the update blocker but i was just wondering what would happen if for some reason an update were to be installed would i be stuck in a loop and have to restore manually or would the ota install and just overwrite my cwm and just be like it was never there. I seen posts explaining what will happen but they're very vague and it seems as if the people asking messed up in the first place.
huckjam said:
What if say someone else started your ouya and installed the update without knowing that they weren't supposed to would it corrupt it or would the ota install as its supposed to and you would just lose root and your rom. Im just wondering cuz I have already installed the playstore and the update blocker but i was just wondering what would happen if for some reason an update were to be installed would i be stuck in a loop and have to restore manually or would the ota install and just overwrite my cwm and just be like it was never there. I seen posts explaining what will happen but they're very vague and it seems as if the people asking messed up in the first place.
Click to expand...
Click to collapse
The Dev of the StockPlus ROM actually physically removed the OUYA updater, so it's not possible for it to be updated that way. The only way to update StockPlus is by you downloading the .zip file of the new version and installing it manually through CWM, so there's no danger of anything happening automatically or without your say so.
DroidXero said:
The Dev of the StockPlus ROM actually physically removed the OUYA updater, so it's not possible for it to be updated that way. The only way to update StockPlus is by you downloading the .zip file of the new version and installing it manually through CWM, so there's no danger of anything happening automatically or without your say so.
Click to expand...
Click to collapse
Very nice that's kinda what i figured thanks for the clear answer!

Update from NAE to NG2!

Anyone receive this update yet?
I took the update and my build number updated, but my baseband and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.
churchey360 said:
I took the update and my build number updated, but my modem and software still say NAE (Happened to me late time too) so hopefully the .tar file gets released soon or a way to redownload the update file and place it on my external sd card and reflash it.
Click to expand...
Click to collapse
Did you have root? Retain root after the update?
No I was unrooted stock NAE
churchey360 said:
No I was unrooted stock NAE
Click to expand...
Click to collapse
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.
troyboytn said:
Thanks for the reply. I'm all stock with Towelroot only. just wondering if the new "Google security fixes" will break the Towelroot exploit as I'm assuming that it will.
Also assuming that this is pretty much a useless update that only closes that exploit since Sprint was too sorry to include wifi calling as it should have.
Click to expand...
Click to collapse
Were you able to obtain root after the update?
chico1983 said:
Were you able to obtain root after the update?
Click to expand...
Click to collapse
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
Worked just like you said. I tried CF-autoroot and did not work for me. Have you been able to get the hot spot mod to work?
churchey360 said:
Yeah the easiest way for me is to just flash Philz recovery with Odin and it has an option in advanced settings to reroot then just download supersu from the playstore
Click to expand...
Click to collapse
but No baseband downgrade on NG2?
Philz still the bomb?
I want to do the reverse
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?
rastapapa said:
I took the OTA to NG2 and now apps that I regularly use (DoggCatcher and Daily Roads) are reporting storage problems and are unable to write to ext SD card, even after applying NextApp fixes. Maybe I need to reset the paths or something, but if that doesnt work, what would be the best way to revert back to NAE?
Click to expand...
Click to collapse
Read this might help
http://forum.xda-developers.com/showthread.php?t=2840591
This is probably stupid and already answered in another thread but I'm a noob, don't flip out on me... Let's say, theoretically, I was to accept the
NG2 update. I'm rooted with Towelroot, using Supersu and Titanium backup. I've backed up then delete almost all of my bloatware with TB and have no further use for root at the time. If I were to break root with the update, will all that stuff stay the same and be safe until I can root again? I.e. If I break root, touch none of those root apps, then root again later, will they even "know" anything happened?
Since you can't take an OTA while rooted, that won't work.
frostedunit said:
Since you can't take an OTA while rooted, that won't work.
Click to expand...
Click to collapse
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?
tamiller said:
My phone says it has already downloaded it and is pretty enthusiastic about me accepting it. What do I do? Live with the icon in my status bar? Can I remove it? What happens if I hit [accept]?
Click to expand...
Click to collapse
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.
2WhiteWolves said:
Long press on notification it should show app info, push on that should take you to the application, then Clear Cache > uncheck Show Notification, that should stop it from showing.
Click to expand...
Click to collapse
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
Read this, might help with the upgrade. Read all of the thread.
http://forum.xda-developers.com/showthread.php?t=2840591
So far from what I have read, I have know idea where the HD Voice Icon is, and no one else does either, not unless it is known in another thread that I don't know about.
johnnyphive said:
Thanks for posting this...EXACTLY what i was looking for. I didn't even know there was a new update out and this damn thing was nagging me when i woke up this morning. Now the more important question...What does the "HD Voice Icon" look like....lol.
But seriously, if i am stock rooted NAE, is there an upgrade path out there yet, to keep me stock rooted? And what else is in this thing, it's reporting almost 120MB....???
Click to expand...
Click to collapse
You will have to first install the stock NAE tar file with odin to return your phone to a stock unrooted condition with the stock recovery. Then you can take the ota. After that you can reroot again with cf autoroot.
Now the question is can you keep the domestic sim unlock if you do this?

Monthly OTA updates from Google

This is new: http://www.androidpolice.com/2015/08/05/google-announces-new-update-policy-for-nexus-devices-including-monthly-security-patches-for-3-years-and-major-otas-for-2-years-from-release/
That would be a real pain for us rooted users....but I guess the security patches are a good thing
A real pain...
Sent from another Nexus..
6...
No pain, it literally takes minutes to flash stock, update, root using the toolkit. [emoji1]
I wonder if there are again going to be separate builds for each carrier.
meldroc said:
I wonder if there are again going to be separate builds for each carrier.
Click to expand...
Click to collapse
That's a good point...maybe?
I wish there was an app for rooted users to get notifications about these updates (and maybe offer a way to download a flashable zip as well?)
I got a Nexus 6 because I wanted to be able to always have access to a stable, current version of Android. I didn't realize that OTA updates wouldn't work out of the box with rooted devices though.
Would be nice to have some method to get back that functionality!
ArmoredCavalry said:
I wish there was an app for rooted users to get notifications about these updates (and maybe offer a way to download a flashable zip as well?)
I got a Nexus 6 because I wanted to be able to always have access to a stable, current version of Android. I didn't realize that OTA updates wouldn't work out of the box with rooted devices though.
Would be nice to have some method to get back that functionality!
Click to expand...
Click to collapse
There is, stay stock or learn how to manually update to new versions. It's quick to do.
Xplicit84 said:
There is, stay stock or learn how to manually update to new versions. It's quick to do.
Click to expand...
Click to collapse
Both those things ignore the whole point of what I brought up.
I'm saying it would be nice if there was an equivalent automatic notification/update process for rooted users.
ArmoredCavalry said:
Both those things ignore the whole point of what I brought up.
I'm saying it would be nice if there was an equivalent automatic notification/update process for rooted users.
Click to expand...
Click to collapse
That is the equivalent. Stay stock or manually update. Rooted users don't worry about such a thing, since changing ROMs and adding various features are a common occurrence.
Xplicit84 said:
That is the equivalent. Stay stock or manually update. Rooted users don't worry about such a thing, since changing ROMs and adding various features are a common occurrence.
Click to expand...
Click to collapse
Rooted users don't care about convenience? I dunno about you, but I'm rooted, and I still would prefer to do repetitive/manual processes as little as possible...
You can be a rooted user just to use rooted apps, and not care about trying a different ROM every week. In which case, it would be nice to have the same benefits of automatic updates as stock users. Not sure why you seem to be against the idea?
I get that you think it is unnecessary, but I'm saying I would prefer it as an option. So, maybe we can just leave it at that?
ArmoredCavalry said:
Rooted users don't care about convenience? I dunno about you, but I'm rooted, and I still would prefer to do repetitive/manual processes as little as possible...
You can be a rooted user just to use rooted apps, and not care about trying a different ROM every week. In which case, it would be nice to have the same benefits of automatic updates as stock users. Not sure why you seem to be against the idea?
I get that you think it is unnecessary, but I'm saying I would prefer it as an option. So, maybe we can just leave it at that?
Click to expand...
Click to collapse
I would also like that if it was possible...
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
hdtechk said:
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
Click to expand...
Click to collapse
and that's exactly what I am going to do...
hdtechk said:
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
Click to expand...
Click to collapse
I don't think this will work. If your N6 is rooted, you can't sideload the OTA file. Your phone will need to be stock (unrooted) to apply the OTA.
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
jj14 said:
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
Isn't there a chance of losing the ability to reroot with this method though? I've been waiting for users to publish flashable zips for this reason, but maybe that is not necessary?
ArmoredCavalry said:
Isn't there a chance of losing the ability to reroot with this method though? I've been waiting for users to publish flashable zips for this reason, but maybe that is not necessary?
Click to expand...
Click to collapse
Is there a chance that google will publish a new Nexus factory image that can't be rooted? Sure - in theory, that is possible. But unlikely.
Till date, all nexus devices have been rooted (thanks @Chainfire)
jj14 said:
. . . Your phone will need to be stock (unrooted) to apply the OTA.
. . . use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
Recently I used both methods just to see if there were differences.
Both had the same results. That means among others that my settings were gone.
- LCD_density defaults (384)
- WiFi interval defaults (was 200)
- Needed to flash Black Google Now Launcher and uninstall Google.app updates to get my black background back.
When this happens every month . . . [email protected]#$%&
jj14 said:
I don't think this will work. If your N6 is rooted, you can't sideload the OTA file. Your phone will need to be stock (unrooted) to apply the OTA.
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?
Does google always post a whole new image for each ota? What about the carrier variants like tmobile? Is there a new image for each ota?
Thanks. I'm not a N6 owner yet but I plan to be stock rooted and am trying to determine the ota update process in advance.
@NCguy
"When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?" Correct
Does google always post a whole new image for each ota?" Yes
"What about the carrier variants like tmobile? Is there a new image for each ota?" There has been a T-Mobile specific factory image for each OTA.
Here are the factory images > https://developers.google.com/android/nexus/images
cam30era said:
@NCguy
"When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?" Correct
Does google always post a whole new image for each ota?" Yes
"What about the carrier variants like tmobile? Is there a new image for each ota?" There has been a T-Mobile specific factory image for each OTA.
Here are the factory images > https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks cam30era. I was a bit concerned that being a stock rooted device might be too much trouble, especially with the security updates. But this looks manageable to me.

Android Nougat is coming to the M9 sometime in the "far" Future

Lets see if it comes faster to our Device then Marshmellow...after Google released it to the Manufactures.
And it comes as it seems just to three Devices. (A9,M9, HTC 10)
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Got that system security OTA notification as well today. I'm using the stock ROM with root (SuperSU flashed via TWRP). Can I stay rooted to apply the OTA with the stock recovery or do I have to flash the RUU first?
Solved:
Make a backup with Titanium or however you like. Save all your data from internal SD. Afterwards apply latest RUU.exe from HTC (depending on your carrier). If you wanna reroot, I would suggest SuperSU 2.65, because newer versions end up in bootloops.
Don't expect Nougat this year...
It's the August security update
Sent from my HTC One M9 using Tapatalk
hope this year released
matmaneyre said:
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Click to expand...
Click to collapse
Do you have 3.39.531.12 stock recovery??
missicolin said:
Do you have 3.39.531.12 stock recovery??
Click to expand...
Click to collapse
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Amishrabbit said:
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Click to expand...
Click to collapse
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
any news on Android N at least not official
drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
you should
" fastboot oem lock "
to relock your bootloader - remeber - to save alll yor apps / settings (via TitaniumBackup for exaple) before
(re) unlocking bootlader will wipe all data
...
rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
rtoledo2002 said:
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
Click to expand...
Click to collapse
here is a screen shot
rtoledo2002 said:
then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ??
Click to expand...
Click to collapse
That's not a bug but a security feature introduced by google. It's meant to prevent malicious apps from making you accept things/permissions you don't want (keyword: tapjacking). Go to settings > app > open the three dot menu > configure apps > draw over other apps. There you can revoke that permission from any suspicious app.
There is an article about tapjacking on the xda portal if anyone wants more information. It's called "How tapjacking made a return with android marshmallow - and nobody noticed". Btw, the article explains why the security feature isn't perfect, too. (Using xda labs at the moment I can't add a direct link to the article. However google should be able to find it.)
I just hope for the classic Non-GP Sense UI. The one with the Grid View Recent Apps.
HTC One M9 is the last chance for the full Sense experience on Nougat, because is the last Non-GP HTC that is being updated.
Rollout started
rhisendark said:
any news on Android N at least not official
Click to expand...
Click to collapse
Read that Rollout started in America for Brand free devices
HTC root mobiles cannot install OTA, RUU are only way when rooted
drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
Yeah you only need to flasb the RUU it would solve your problem

Categories

Resources