Related
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.
Yesterday I got official M ota on my Moto G 2 Lte (Xt 1078 - Brazil)!
Just updated and everything was ok, no reset was needed.
Some tips:
- Can't activate System Ui Tuner:
In the developer options I turned off animations. Just restored the default option (1x) in all 3 animations, restarted
the device and voila, I could activate the System Ui Tuner (holding the cog icon). After that, disable the animations
again did no mess.
- Igo stopped working:
Just uninstalled and reinstalled the app (without delete the files), and it's working again.
- Greenify stopped showing black screen while hibernating apps (screen flickering):
Needed to give it permission to overlap other apps (in Settings > Applications > Advanced (cog wheel))
- Smart unlocker stopped working:
Works on the "Universal version"
A factory reset is always a good thing when you do a major version update, and reading "Just uninstalled and reinstalled the app (without delete the files???), and it's working again" lead me to think a factory reset should fix all your problems. Sad thing you can't backup your appdata or you will end in the same situation, not sure but mostly possible.
dr.nic said:
A factory reset is always a good thing when you do a major version update, and reading "Just uninstalled and reinstalled the app (without delete the files???), and it's working again" lead me to think a factory reset should fix all your problems. Sad thing you can't backup your appdata or you will end in the same situation, not sure but mostly possible.
Click to expand...
Click to collapse
But the only problem I had was the app Smart Unlock that isn't working in 6.0, I found the solution.... everything else is fine.
Factory reset is a last resort, because if I do it my bank app will require an activation in the bank, and I don't want to go there...
Ota file on the thread http://forum.xda-developers.com/moto-g-lte/general/mm-ota-xt1078-captured-brazilian-thea-t3313559
rafaelrgi said:
But the only problem I had was the app Smart Unlock that isn't working in 6.0, I found the solution.... everything else is fine.
Factory reset is a last resort, because if I do it my bank app will require an activation in the bank, and I don't want to go there...
Click to expand...
Click to collapse
For banking app, Take app+data backup using
Titanium (if rooted)
Helium (even without root)
nazir221 said:
For banking app, Take app+data backup using
Titanium (if rooted)
Helium (even without root)
Click to expand...
Click to collapse
Thanks for the advice, but my device isn't rooted and the Helium backup doesn't works for my bank (it has a #@$ seed for code generation, just Titanium can backup it, but I didn't rooted it).
I won't worry about it, because didn't reset it and it's working flawlessly....
Howdy,
I got a new Note 4 from Bell Mobility about a month ago...
I updated the software, rooted it and installed the Wanam modified Xposed framework.
I have lost the automatic rotation, except for the built in camera software. Nothing else will auto-rotate. Checked the gyroscope and checked a few 'leveler' applications - all tests pass. Oddly I noticed the camera software still auto-rotates, no idea why it is special.
I tried the Wanam Xposed module to 'Enable all rotation angles' it has made no difference. With screen rotation software, currently have "Rotation - Orientation Manager by Pranav Pandey" installed. Auto-Rotate On and Forced Auto-Rotate neither option will rotate the screen when I turn my phone. If I choose Forced Landscape, it will go into Landscape mode. The only way to return to Portrait though is to use one of the Force Portrait options though.
My other issue is with turning on Device Encryption... Using SuperSU Pro for su..
If I just go through the prompts without changing anything, it reboots but doesn't encrypt.
First I tried installing as a system app so I could use the Disable function in the Android Application Manager, as I did with my Note 2, SuperSU tells me "Not (currently) available in system-less root mode".
If I turn off "Enable Superuser" in SuperSU, encryption enables properly, but I am unable to turn the "Enable Superuser" again, it says it has to update, but the fails. Suggests a reboot and try again. Sadly, this did not help.
I had success with one of the exploit root methods, KingRoot. While this worked when my phone was encrypted, it wasn't stable and kept popping up stuff. I tried to replace it with SuperSU, there are a few guides written to do just that, but they all indicate that it is very hard to get rid of, regardless, none of the guides worked for me. I ended up resetting the phone and starting over...
I tried the CLI command to start the device encryption from a # prompt..
vdc cryptfs enablecrypto inplace password 1234567890abcdef
The phone rebooted a couple times, but took a very long time (hour plus) to come back to the Android Lock-Screen.. But still a non-encrypted device. If I intrupted the process because I thought it had crashed, it started up and immediately told me something when wrong with the encryption and I need to use Recovery to reset the device..
As for root methods, I was using the CF-Auto-Root at first, trying to look for solutions to both issues, I tried a few ways of getting SuperSU installed.. The last time I reset I tried the "SkipSoft Unified Android Toolkit" method. 'Grasping at straws' to get SuperSU installed into /system so can use the Applicaiton Manager to disable and enable it...
My mobile's specifics, if it matters..
Samsung Galaxy Note 4
Model number - SM-N910W8
Android Version 5.1.1
Baseband version - N910W8VLU1COK3
Build number - LMY47X.N910W8VLU1COK3
Currently have the Team Win Recovery Project v2.8.7.0 recovery software installed.
I am looking for suggestions for both issues, but really want to avoid resetting the phone if I can at all possible... Yes, I have Titanium Backup Pro installed, but have never actually gotten a restore to properly restore all my applications and data... I rely on it now just for the Uninstall and Freeze features.
For an update,
I also noticed that rotation works on the Lock Screen and in the camera applicaiton.
If I rotate my screen on the Lock Screen, the red handset picture and camera icons rotate.
If I rotate in the camera application, nothing changes position, but all the icons rotate as well.
I'm still completely stuck though, open to suggestions...
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
uchihakurtz said:
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
Click to expand...
Click to collapse
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
kevinds said:
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
Click to expand...
Click to collapse
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
kevinds said:
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
Click to expand...
Click to collapse
This is amazing, can you please post the odin flashable file? I am having this exact problem right now because I removed it in TB. Is it just the facebook file that are flashed? Thanks so much in advance, you're saving my life here
Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10
Device:
Rooted OP 6t, OxygenOS 10.3, stock recovery, Magisk 20.2, Magisk Manager 7.5.0
What did I do:
I updated from the last OxygenOS 9 Version to OxygenOS 10.3 by uninstalling magisk, restoring images and doing the manual update through the downloaded full image. Reinstall magisk. It all went well. First boot took a while but went through.
SIM was not recognised at all.
I've reset all network settings and cleared cache and data of com.android.phone.PhoneApp.
Found out here that its due to a call record magisk module which I uninstalled. Mobile data is working just fine since then.
I tried to uninstall magisk and reinstall it before rebooting in order to keep the possibility to keep root as I do not have twrp installed. (suggested here). I guess this is unrelated.
Issue:
I cannot access the SIM & Network Settings. When I try, the app com.android.phone crashes instantly.
Logs throw these warnings:
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.telephony.action.CARRIER_CONFIG_CHANGED flg=0x15000010 (has extras) }: process is bad
Is there a way to check the carrier config or renew it?
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 (has extras) }: process is bad
Hows the SIM state changing?
and this Error:
Code:
Sending non-protected broadcast com.android.internal.telephony.ACTION_IMS_CAPABILITY_STATUS_CHANGE from system 1102:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:15963)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16666)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15980)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16808)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1422)
at com.android.server.TelephonyRegistry.broadcastImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2644)
at com.android.server.TelephonyRegistry.notifyImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2636)
at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:964)
at android.os.Binder.execTransactInternal(Binder.java:1032)
at android.os.Binder.execTransact(Binder.java:1005)
I am not sure what to do. But I do want to avoid a full factory reset.
Thanks for your hints.
Alternatively is it possible to access the settings of this submenu through a different app or way?
hey_malik said:
Alternatively is it possible to access the settings of this submenu through a different app or way?
Click to expand...
Click to collapse
Sounds like a bad flash, or you didn't factory reset. If you update from 9 to 10 without wiping data, **** can happen
True, I did not because I don't want to set up the whole phone afterwards.
Could it be a solution to flash the ROM again through the integrated update system? Or would I then need to install twrp? I haven't done this in ages
Have you got any magisk module active?
estapagu said:
Have you got any magisk module active?
Click to expand...
Click to collapse
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
hey_malik said:
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
Click to expand...
Click to collapse
I had some SIM problems at the beginning related to a magisk module but I can't remember which. And another problem with WiFi after OTA update using magisk OTA udapte method, so finaly I deleted Magisk completely and updated from TWRP
Just to get this straight:
I may in a first step boot a twrp image (just boot) dirty flash the latest stock image, flash magisk (or not and lose root for the moment which is no issue because I have an unlocked boot loader) and see if the issue is still present. If yes a clean wipe and install is in order?!
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Dadditz said:
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Click to expand...
Click to collapse
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
hey_malik said:
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
Click to expand...
Click to collapse
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Dadditz said:
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Click to expand...
Click to collapse
I suggest you boot to Twrp, then flash the Twrp. Get inside twrp and flash these > OOS, Twrp, Magisk Then reboot again to twrp repeat > OOS, Twrp, Magisk. And for the last time reboot again to twrp and flash the Magisk.
You will be good to go. :good:
Is there any risk involved concerning the encryption?
hey_malik said:
Is there any risk involved concerning the encryption?
Click to expand...
Click to collapse
As you already mentioned, you are in Android 10, and if you are using the correct Twrp. There won't be any.
Still it's always better to take a back up just in case if something goes wrong.
Stuck with the same issue. Did you manage to get it fixed somehow?
Actually the latest available oo update to 10.3.1 fixed it.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Lucky you. I got this issue when switching to 10.3.1 from 9. I tried flashing 10.3.1 once again. Didn't work.
You need to uninstall Magisk then factory reset, it will get rid of all Magisk modules ghost residues. Then flash Magisk again with fastboot twrp method. I had this and going back to factory state was the only fix. No need to flash again and again the rom it doesn't touch Magisk data in /data partition.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Just an update, this worked for me too. Thanks for posting that tip else I would have went ahead and reset the phone. You saved me a hell lot of trouble.
Additionally, I figured out a solution which might work for people still having this issue. I haven't tested this myself since I found this after my issue was solved.
The reason why the issue happened to us is because the system app "Phone Services" was missing, or not installed properly while dirty flashing. There is an alternative hidden activity for sim settings called "com.android.settings.network.telephony.MobileNetworkActivity", which is not a part of Phone Services app, but a part of the Settings app itself. This could be invoked using any activity launcher apps available in the Play Store.
Also, this activity gives more advanced sim settings too. So, probably worth a look if interested.
Same problem here, but fixed!!
Sim not working anymore after update to Magisk 21.2. nothing would change it.
After installing previous version (21.1) the problem persisted. After almost giving up, I found this thread. Simply uninstalled the OOS Native Call Enabbler module and everything workes like a charm again!!!
So it was an easy fix (once you know) and I am very thankful, because I would never have thougt of it! Unfortunately I cannot record Calls anymore, nor find the module now that I am successfully running on 21.2 again with working SIM. Though the choice between being able to use my SIM or record calls was easy
Hope someone finds use of this info.
As mentioned before Encryption is not a problem if the right TWRP version is used.
Put in you password (or pin) and all is nicely decrypted and reachable in TWRP Recovery.
Good luck to all!
PS: still hoping for a new (compatible) call recorder module though
Hello XDA community,
I recently purchased the Nothing Phone 1 running on the latest version of Android 13. After rooting my phone using Magisk, I installed several Magisk modules which worked fine initially.
Here's a list of Magisk modules that I installed in chronological order:
Font Manager
NotoCJK
Fullscreen/Immersive Gesture
G-visual (later closed as I didn't see any effect)
Shamiko
DRM disabler
Revanced Youtube
Webview Manager (replaced with ungoogle chromium)
Nexus Media Before installing the 10th module, I took a full backup of my device using Titanium Backup. However, during the backup process, it got stuck while backing up a file named "Media 13-9427200." After several attempts, I had to cancel the backup for this file to complete the backup process.
Pix3lify (failed to unpack boot image and finally used slim mode)
Safetynet fix
After installing the 11th module, I went to bed and installed several applications before sleeping, such as Kiwi, Shizuku, App Ops, Buzzkill, Automate, Vmos, Brevent, and Greenify.
12.Audio Modification Library
13.Ainur Narsil
After installing the 13th module, I noticed that my phone started behaving abnormally, and it would automatically reboot. Every time I start the phone, the interface freezes after two minutes, and it restarts automatically after several seconds. This scared me, so I uninstalled all the Magisk modules and applications installed after the 11th module and disabled the two audio modules, but it didn't seem to work. So, I turned off the phone for a few hours, and it seemed to work fine after that.
When I tried to log in to my Reddit account, I found that I couldn't use "Continue with Google." When I went to the Google section in Settings, I found that I couldn't open it either.
I searched for solutions online and found that the problem might be due to the Webview. I replaced it with Ungoogle chromium and downloaded the latest version of Android Webview from the Play Store and disabled WebView Manager. But nothing worked. I tried updating the Carrier Services and clearing the Google Service's cache, but it didn't work either. (All Google apps can be opened and used normally.)
After updating the WebView, things got worse. I use a third-party launcher called Smart Launcher, and I have many customized app icons. I found that all customized app icons no longer work, only the native icons can open the app.
I am really frustrated and everything seems out of my control. I decided to restore all the data from the backup I made last night using Titanium Backup (in snap mode). Unfortunately, after the restore was complete and I restarted the phone, I found that my phone was bricked. I can see the boot animation and select the launcher, but once I choose the launcher, the screen goes black, and I cannot do anything. I am also unable to enter Safe Mode as it keeps restarting.
At the same time, I used a software control my phone. I can see NOTHING in sdcard.
What can I do? Is there any way to fix my phone and preserve my data? If not, I am willing to wipe all my data. Also, if I restore my phone to factory settings, can I still use the backup data I made with Titanium Backup?
Thank you in advance for your help.
Additionally, please find attached a screenshot of the only interface I can see on my phone after booting up.
Seems you've broken lot of system apks , clearly Nothing Launcher is first . See if you have a intact bootloader and use fastboot commands to flash the launcher but I'm quite sure there many culprits in system .
So maybe short way is to flash entirely system image shown here in one of all threads about phone unbrick
muppetz said:
Seems you've broken lot of system apks , clearly Nothing Launcher is first . See if you have a intact bootloader and use fastboot commands to flash the launcher but I'm quite sure there many culprits in system .
So maybe short way is to flash entirely system image shown here in one of all threads about phone unbrick
Click to expand...
Click to collapse
Thanks for your advice!