So I got a Nexus 6p yesterday, and after messing around I wanted to mess with layers a bit to make certain things more AMOLED friendly like the settings, messenger, etc. So I tried using Dark Material layer only selecting a few of the overlays I wanted. Anyway after applying and a reboot my Settings would FC anytime I tried to access...okay fine, happened on my Nexus 5 also. No big deal I would just restore the backup I made PRIOR to messing with layers at all. After doing a factory reset in TWRP and restoring my backup, settings still FC, and my layers are STILL applied! The messenger one still opens and is fine, but settings FC. In TWRP I did the factory reset wipe and a manual wipe of System, Data, Cache...only thing I didn't wipe is internal storage. What is going on and how can I fix this??
perhaps layers is stored in internal storage?
Layers is stored in the vendor partition. There's a flashable zip for the latest vendors in the PureNexus ROM thread, flash that with TWRP and it'll clear your vendor partition.
PS. This has been asked a few times, a quick search probably would have turned up the answer you needed.
Sent from my Nexus 6P
Heisenberg said:
Layers is stored in the vendor partition. There's a flashable zip for the latest vendors in the PureNexus ROM thread, flash that with TWRP and it'll clear your vendor partition.
PS. This has been asked a few times, a quick search probably would have turned up the answer you needed.
Sent from my Nexus 6P
Click to expand...
Click to collapse
I did search for layers not uninstalling...and I did see the vendor solution however I figured since I was wiping system during my wipes I thought that wasn't the issue(I should have checked the actual folder, my misake). I also even did a full wipe and clean install, and still my settings and layers were installed. I couldn't understand why. After reading your suggestion I finally checked the vendors folder and seen they were still there...I removed them and after a clean install all was right with the world.
However I'm having a problem now with my password not working. I restored my backup I made prior to applying any layers and now my phone is saying my password is incorrect....ahhhh I'm getting so frustrated. Anyway thanks for your help!
Jonnyredcorn said:
I did search for layers not uninstalling...and I did see the vendor solution however I figured since I was wiping system during my wipes I thought that wasn't the issue(I should have checked the actual folder, my misake). I also even did a full wipe and clean install, and still my settings and layers were installed. I couldn't understand why. After reading your suggestion I finally checked the vendors folder and seen they were still there...I removed them and after a clean install all was right with the world.
However I'm having a problem now with my password not working. I restored my backup I made prior to applying any layers and now my phone is saying my password is incorrect....ahhhh I'm getting so frustrated. Anyway thanks for your help!
Click to expand...
Click to collapse
The password problem is fixable...within twrp you need to delete the password file. See this thread for details: http://forum.xda-developers.com/showthread.php?t=3245070
Jonnyredcorn said:
I did search for layers not uninstalling...and I did see the vendor solution however I figured since I was wiping system during my wipes I thought that wasn't the issue(I should have checked the actual folder, my misake). I also even did a full wipe and clean install, and still my settings and layers were installed. I couldn't understand why. After reading your suggestion I finally checked the vendors folder and seen they were still there...I removed them and after a clean install all was right with the world.
However I'm having a problem now with my password not working. I restored my backup I made prior to applying any layers and now my phone is saying my password is incorrect....ahhhh I'm getting so frustrated. Anyway thanks for your help!
Click to expand...
Click to collapse
Vendor is independent of system now, so wiping system doesn't affect it. There's a sticky thread in the general section detailing the problem with security and backups, very easy to find.
tfly212 said:
The password problem is fixable...within twrp you need to delete the password file. See this thread for details: http://forum.xda-developers.com/showthread.php?t=3245070
Click to expand...
Click to collapse
Ended up just doing a clean install after everything was straightened out.
Heisenberg said:
Vendor is independent of system now, so wiping system doesn't affect it. There's a sticky thread in the general section detailing the problem with security and backups, very easy to find.
Click to expand...
Click to collapse
I didn't know about the overlays being stored in vendor at the time so the sticky thread wouldn't have stood out as being helpful [emoji14]
I never messed with layers on my Nexus 5 as I like the stock MM theme, but now on my Nexus 6p with it having an AMOLED screen I wanted something dark for battery savings and such. Also kinda wanted to switch things up being a new phone and all.
If my settings keeps FC when I apply dark material layer, what could be the culprit? Someone mentioned needing to installing busy box since I'm on Cataclysm... Well I have the app installed, but I'm not quite sure how to install it further... There is smart install and the other option. Not even sure what busy box does lol.
Sent from my Nexus 6P running Cataclysm & ElementalX.
Fixing permissions in twrp fixed my FC's when I first installed layers.
Related
I have got this issue since I wiped the dalvik cache on Android 4.2.2 to fix a Play Store issue which I should of deleted that dalvik cache file with Titanium Backup or use Lucky Patcher to remove that left over file in /data/app/ but also wiping the cache somehow broke the APN API not allowing me to add the wiped APNs and such.
Since then I had to reflash EVERYTHING using the Nexus Stock Image flasher from Google Developers, since then I had no issues until a recent Android 4.3 update which caused the dalvik cache issue to arise since it wiped the dalvik cache.
I also do not have root because of the update but the su binary and SuperSU is still there so I cannot fix the issues manually.
When I come back on holiday I will root the device to see if I can fix the issue
but if that does not help then I can use the root to backup ALL the user apps, backup ALL the internal SD contents and reflash also rooting it.
Because I paid for the TB licence I can just restore my stuff in a touch of a "button".
I have removed apps which I don't use and the ones which I suspect is causing the issue but that does not help.
It seems that wiping the cache partition now does not break anything.
The dialog box says in the title "Android is upgrading..." and it says below "Starting apps..." and then gets off in a second.
I have seen forums of people having this strange issue but there are no replies.
I am getting back from holiday on the 31/8/13.
I really want this haunting issue to stop so please help so others can fix this issue without going though annoyance caused by this issue.
andyabc said:
I have got this issue since I wiped the dalvik cache on Android 4.2.2 to fix a Play Store issue which I should of deleted that dalvik cache file with Titanium Backup or use Lucky Patcher to remove that left over file in /data/app/ but also wiping the cache somehow broke the APN API not allowing me to add the wiped APNs and such.
Since then I had to reflash EVERYTHING using the Nexus Stock Image flasher from Google Developers, since then I had no issues until a recent Android 4.3 update which caused the dalvik cache issue to arise since it wiped the dalvik cache.
I also do not have root because of the update but the su binary and SuperSU is still there so I cannot fix the issues manually.
When I come back on holiday I will root the device to see if I can fix the issue
but if that does not help then I can use the root to backup ALL the user apps, backup ALL the internal SD contents and reflash also rooting it.
Because I paid for the TB licence I can just restore my stuff in a touch of a "button".
I have removed apps which I don't use and the ones which I suspect is causing the issue but that does not help.
It seems that wiping the cache partition now does not break anything.
The dialog box says in the title "Android is upgrading..." and it says below "Starting apps..." and then gets off in a second.
I have seen forums of people having this strange issue but there are no replies.
I am getting back from holiday on the 31/8/13.
I really want this haunting issue to stop so please help so others can fix this issue without going though annoyance caused by this issue.
Click to expand...
Click to collapse
that android is upgrading dialog box is the dalvik getting rebuilt, it get rebuilt after you wipe it, it is SUPPOSED to happen when you wipe your dalvik. it isnt an issue. if not, you wouldnt have a bootable or usable phone. the real issue here is you using lucky patcher. we all know what it is used for, and is disrespectable to the developers that hang out on xda.
simms22 said:
that android is upgrading dialog box is the dalvik getting rebuilt, it get rebuilt after you wipe it, it is SUPPOSED to happen when you wipe your dalvik. it isnt an issue. if not, you wouldnt have a bootable or usable phone. the real issue here is you using lucky patcher. we all know what it is used for, and is disrespectable to the developers that hang out on xda.
Click to expand...
Click to collapse
I only use Lucky Patcher for important stuff and not really for what you think so that is NOT the issue what so ever and misleading to this thread and plus, other people use it.
I mean that in EVERY boot it says that it is starting apps, nothing to do with building at all.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
I only use Lucky Patcher for important stuff and not really for what you think so that is NOT the issue what so ever and misleading to this thread and plus, other people use it.
I mean that in EVERY boot it says that it is starting apps, nothing to do with building at all.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Late reply, but Lucky Patcher did this to my phone just now and I don't know what to do, other than reflash. Which sucks because I spent all night modding out my phone and was stupid enough to not to a nandoid backup.
Edit: The first boot it upgraded everything then everything force closed, 2nd boot everything upgraded, but seems to be working fine. Woo. Was scared for a moment.
evilpig said:
Late reply, but Lucky Patcher did this to my phone just now and I don't know what to do, other than reflash. Which sucks because I spent all night modding out my phone and was stupid enough to not to a nandoid backup.
Edit: The first boot it upgraded everything then everything force closed, 2nd boot everything upgraded, but seems to be working fine. Woo. Was scared for a moment.
Click to expand...
Click to collapse
Well you was LUCKY (pun alert!).
Anyway it seems that the stock rom was always the issue, even reflashing does not fix this issue when you wipe the dalvik cache.
I am on ParanoidAndroid 3.98 at the moment and I am not getting any issues just by wiping the dalvik cache and/or the cache partition.
Sent from my Nexus 4 using Tapatalk 4
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attached image for help.
:good:Hits Thanks If I helped u:good:
Garu8 said:
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attached image for help.
:good:Hits Thanks If I helped u:good:
Click to expand...
Click to collapse
I just removed the odex files and worked great. Thank you.
I havent done much of the root and rom thing in a long time but it was always pretty straight forward. I don't know what is going on. I unlocked the bootloader and installed SU. Attempted to use layers and nothing seemed to work I rebooted my phone and I got an error "NFC has stopped working". I have been able to get into the system but this red theme will not go away. I have wiped davlik and cache and performed a full wipe. I have even installed a new rom and still thisbred theme wont go away. I'm sure it's something I am doing but any help would be appreciated.
If you installed the layers via Layers Manager, just use that to uninstall. Otherwise, you can delete the files from /vendor/overlay.
same thing here
after installing got same error message and unable to uninstall through the manager, cant find the folder layers. It isn't under the vendor folder.
Same problem
Nexus 6P with layers
Tried uninstalling through layers manager, overlays won't go, they keep showing up in uninstall panel. Any help?
Vendor is a separate partition and it's no longer under system partition in nexus 6p and few other recent phones.
Your best bet is to delete overlay folder under vendor partition or flash the vendor.img alone from the factory images.
Sent from my Nexus 6P using Tapatalk
Hi all,
I think I might have a problem, after I flashed xposed framework on my nexus 6p and got the modules that I wanted up and running no problem, during 4 or 5 days all worked fine but had constant reboots,
I decided to go back before I flashed xposed with twrp and restored a full backup, it failed to restore all selected at the same time, so did one a time and restored but phone would just not boot, so
Having data partition restored and then dirty flash stock without wipe data I was able to get my phone back and running, and re-root fine and flashed twrp no problems
Went to twrp to wipe cashe and dalvik but it just takes like 2 seconds optimizing apps and boots to desktop right up, now my question is
Shouldn't it take a very long time to optimize all my apps after the wipe????
all seems to be working fine but kind of bothers me that I might have something in not working right that might develop into something worst in the future
It is at this point I usually full-wipe and reflash. =) Setting things up again can suck, but it's better than wondering what unknown thing is broken and will rear it's ugly head later.
Elnrik said:
It is at this point I usually full-wipe and reflash. =) Setting things up again can suck, but it's better than wondering what unknown thing is broken and will rear it's ugly head later.
Click to expand...
Click to collapse
full wipe and reflash, want to avoid that, any other commands perhaps?
OK so I did a full re flash, back to stock, re root, installed my apps, used for a while, log in on all, went to twrp to test wipe cache and dalvik, same thing, optimizing apps at first boot took like one second and boot to desktop, is this normal or should take longer to optimize all apps?? Anyone??
is my understanding that only apps that havent already been optimized will upon boot... (new installs from like a zip)
chaco81 said:
is my understanding that only apps that havent already been optimized will upon boot... (new installs from like a zip)
Click to expand...
Click to collapse
thats what i am thinking too now that you mention it, like when I installed xposed initially and did whipe cache/dalvik thing after it took long time to boot because was on something like optimizing app 3 out 78, same thing I have seen on my old nexus 5 when dirty flash a new firmware, but not sure if I have something broken or is normal
Recipe:
TWRP 2.8.7.2
TWO Nexus 6Ps on 6.0.1
One N6P systemless rooted
Official Android SDK (fastboot)
So I got a replacement N6P from Fi as I noticed some slight bending on my original, and I was working on moving my data over using TWRP so I could keep all my app data, etc. When I backed up my original 6P, I forgot to remove screen and boot security, so when I flashed on to my new 6P, I was locked out (as expected, known bug). I tried this fix to get in to my system, and it worked! I was able to log in. However, I noticed that my old fingerprints were still enrolled and I wanted to start those fresh, so I tried to remove them. When I selected "Delete" for each enrolled fingerprint, nothing happened. This was the first clue. I then tried to enroll new fingerprints and got the following message:
Code:
[B]Enrollment was not completed[/B]
Fingerprint enrollment didn't work. Try again or use a different finger.
The other odd thing is that on the lockscreen, I was getting a red text error message that read something like "Fingerprint hardware not available."
So I figured something got messed up security wise from the fix I tried after flashing a locked nandoird. I then went back and made a new nandroid backup (boot, system, data) on my old phone making sure that all security was turned off. Same thing!
Wondering if the hardware did actually get messed up somehow, I flashed back to official stock 6.0.1 from Google. Fingerprinting then started working!
So nothing I have done since then has made any difference when trying to restore my userdata from my old phone. I've tried wiping cache/dalvik, and removing the locksettings.db file, but these didn't change anything either.
Has anyone had this issue before? It seems really bizarre to me. I'm probably going to end up flashing stock and restoring userdata via TB, but that is a headache compared to nandroid so if possible I'd like to get this to work.
Tried wiping userdata then flashing userdata from my old 6P and that did not work either.
Have you tried wiping data, setting up the device again, and then checking if you can add a fingerprint?
I tried restoring data from a device I had to RMA too, and got that exact message every time - I gave up in the end as I tried wiping everything but the only thing that worked was clearing userdata & restoring my apps from the nandroid via TiBu.
All in all, I presume it's something to do with the fingerprint scanner having a different hardware key/serial to the new one and retaining that info somewhere in the data partition when you back it up.
DanielF50 said:
Have you tried wiping data, setting up the device again, and then checking if you can add a fingerprint?
I tried restoring data from a device I had to RMA too, and got that exact message every time - I gave up in the end as I tried wiping everything but the only thing that worked was clearing userdata & restoring my apps from the nandroid via TiBu.
All in all, I presume it's something to do with the fingerprint scanner having a different hardware key/serial to the new one and retaining that info somewhere in the data partition when you back it up.
Click to expand...
Click to collapse
Yup I did try that, didn't work either. I'm right where you were too, currently restoring apps for TB. Your hypothesis seems plausible to me, I hadn't thought of that. Kind of a bummer for swapping devices if that is the case. I wonder if we could find where the fingerprint key is stored in userdata and back it up prior to flashing the nandroid?
Thanks for the reply!
No problems & yes, it is, though I presume it's either been done for some sort of security, or as a complete oversight - I can't see Google deliberately doing so, especially on a Nexus device.
I think it's probably highly likely that someone will find the hardware/serial file soon and find a way to stop it from being overwritten when TWRP restores the data partition, though it is annoying that it hasn't been discovered yet... Thankfully restoring from a nandroid through TitaniumBackup isn't too bad nowadays!
Srry for necro but I think I might have found a workaround solution to this problem or at least the problem which is very similar to this one. Please check "symptoms" in the description of the solution to make sure we are talking about the same issue.
Here's the link to the solution: http://forum.xda-developers.com/showpost.php?p=68374321&postcount=1446
erikem said:
Srry for necro but I think I might have found a workaround solution to this problem or at least the problem which is very similar to this one. Please check "symptoms" in the description of the solution to make sure we are talking about the same issue.
Here's the link to the solution: http://forum.xda-developers.com/showpost.php?p=68374321&postcount=1446
Click to expand...
Click to collapse
Sorry for another necro, but this doesn't work for me on Android 7.1.1
Edit: Correct fix here: https://forum.xda-developers.com/showpost.php?p=68199207&postcount=9
Hello,
I flashed the latest img and vendor from Pure Nexus and i got a little problem, I cant see notifications though the vibration happens, and i can't draw the notifications menu either same about the quicktiles settings.
I also noticed that recent apps button doesn't do anything anymore, i rebooted in safe mode, still same issues, can you help me?
Sberdila said:
Hello,
I flashed the latest img and vendor from Pure Nexus and i got a little problem, I cant see notifications though the vibration happens, and i can't draw the notifications menu either same about the quicktiles settings.
I also noticed that recent apps button doesn't do anything anymore, i rebooted in safe mode, still same issues, can you help me?
Click to expand...
Click to collapse
Sounds to me like you didn't wipe properly when flashing the ROM. You need to wipe system, data, cache, dalvik cache before flashing, is that what you did?
Usually when you update the same rom it's better to dirty flash no? i cant wipe all my data everytime i want to update the rom, though i might go back to stock, i
what's the best way to backup apps within the phone, and should i go deodex or Oden
Sberdila said:
Usually when you update the same rom it's better to dirty flash no? i cant wipe all my data everytime i want to update the rom, though i might go back to stock, i
what's the best way to backup apps within the phone, and should i go deodex or Oden
Click to expand...
Click to collapse
My mistake, I didn't realise you were just updating the same ROM. Yes, usually you can just dirty flash, but the way something is implemented may have changed in the latest update, causing the issues you're having now. The solution is pretty simple though: backup your user apps with Titanium Backup, boot into TWRP and perform a full wipe (system, data, cache, dalvik cache), flash ROM + gapps, boot into ROM and set up your settings, restore your user apps with Titanium Backup.
Thanks a lot!
I had this same issue after the March security updates. Was given this and it fixed my issues completely! It manually runs the setup wizard. Not sure if it will fix it or not, but worth a shot.
http://forum.xda-developers.com/showpost.php?p=65767953&postcount=7