Related
Hi Folks,
So, something weird is happening to my phone--every time I attempt to enter the "Security" settings in my phone, the Settings app crashes.
Observations:
1. This happened when I attempted to add my company e-mail via the Email app.
2. Initial sync failed, so I removed the account and added it again.
3. Tried to add it again, success! It asked my to enter a 4-digit lock screen pin (for security).
4. Removed it again, but still can't open "Security".
This results in me not able to set (a) a new lock screen pattern (stuck with "Slide"), and (b) I cannot modify "Device Administrators".
Tried wiping data/cache/davlik cache, still no dice
I'm running stock everything. Rooted. 4.2.2.
Any help would be greatly appreciated. Thanks!
gamercado said:
Hi Folks,
So, something weird is happening to my phone--every time I attempt to enter the "Security" settings in my phone, the Settings app crashes.
Observations:
1. This happened when I attempted to add my company e-mail via the Email app.
2. Initial sync failed, so I removed the account and added it again.
3. Tried to add it again, success! It asked my to enter a 4-digit lock screen pin (for security).
4. Removed it again, but still can't open "Security".
This results in me not able to set (a) a new lock screen pattern (stuck with "Slide"), and (b) I cannot modify "Device Administrators".
Tried wiping data/cache/davlik cache, still no dice
I'm running stock everything. Rooted. 4.2.2.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
So were you rooted when you did the 4.2.2 ota update and used OTA rootkeeper?
You need to flash system.img and reroot.
There is a thread already about the security not working after OTA
DXM31 said:
So were you rooted when you did the 4.2.2 ota update and used OTA rootkeeper?
You need to flash system.img and reroot.
There is a thread already about the security not working after OTA
Click to expand...
Click to collapse
Yup i was rooted before flashing 4.2.2.
After flashing 4.2.2 I added my corporate e-mail, then removed it again.
Was stuck at the PIN lockscreen. Couldn't change it so i had to wipe data.
So I will flash system.img of 4.2.2 right?
Creating a duplicate thread won't improve your chances of getting the answer.
Closed.
Sorry if this is in the wrong place but I've looked everywhere for an answer and i cannot find one,
I have a rooted Nexus 4 with Franco Kernel and Xylon ROM on giffgaff
Whenever i receive a call i cannot answer it because this message shows up and i have to click 'OK' which hangs up, also at the end of outbound calls it shows this message.
This message only occurs when i call/ get called.
I have tried clearing the data from 'Phone' with no avail, also updated my ROM and Kernel. I have reset my Mobile Networks/Access Point Names to default but still this problem occurs. I will be grateful if anyone help and fixes this, Thanks
Hi, I had this problem too and searching around I found a solution that fixed this problem twice for me:
Go to settings -> applications -> all and go to Phone. Clear data & clear cache. Do the same thing with Phone/Messaging Storage apk. You will loose your contacts but it fixed it.
I have my phone contacts sync with my google account so in 10 secs my address book was back and no more "process" problem.
Apparently some kind of corrupted contact causes this, so every time the phone tries to access your contacts and match the phone number, the process crashes.
I hope this helps.
Best,
Ive cleared the Phone data but Phone/Messaging Storage is all blanked out so i cannot click on it? :/ Any ideas?
Jonno13452 said:
Ive cleared the Phone data but Phone/Messaging Storage is all blanked out so i cannot click on it? :/ Any ideas?
Click to expand...
Click to collapse
Were you able to clear your address book? In the end it seems that is what fixes it. Try to delete all your contacts and reboot. Than you can tell if it helps. As far as I know, the next option is to factory reset. That's what I did the first time I got the error, but later it came back because of some bad contact. And if you do that test it by calling yourself from another phone before adding contacts.
mamar said:
Were you able to clear your address book? In the end it seems that is what fixes it. Try to delete all your contacts and reboot. Than you can tell if it helps. As far as I know, the next option is to factory reset. That's what I did the first time I got the error, but later it came back because of some bad contact. And if you do that test it by calling yourself from another phone before adding contacts.
Click to expand...
Click to collapse
I have cleared all my contacts manually and rebooted the phone but still it comes up with the message, Im thinking that i need to clear the data from Phone/Message Storage but i probably clicked force stop on it before and i need to 'Start' it again.
I would just factory reset and flash the rom again.
Honestly i havent got a clue what happened but i did a factory reset and my custom Kernel and ROM were still there and i tried calling myself and it fixed it, somehow :/ Thanks guys
Jonno13452 said:
Sorry if this is in the wrong place but I've looked everywhere for an answer and i cannot find one,
I have a rooted Nexus 4 with Franco Kernel and Xylon ROM on giffgaff
Whenever i receive a call i cannot answer it because this message shows up and i have to click 'OK' which hangs up, also at the end of outbound calls it shows this message.
This message only occurs when i call/ get called.
I have tried clearing the data from 'Phone' with no avail, also updated my ROM and Kernel. I have reset my Mobile Networks/Access Point Names to default but still this problem occurs. I will be grateful if anyone help and fixes this, Thanks
Click to expand...
Click to collapse
Redownload and reflash the ROM including Gapps, if it still doesn't work then try a different ROM. Make sure you re-download the ROM though, since you may be getting this error due to corruption that occurred when it was downloaded.
Edit:
Oh you fixed it. Never mind.
There's a chance my error started because I flashed the. 33 radio after the ROM and gapps. The correct way is first the radio, than RoM, than gapps. I don't know if that's your case, but be aware of that.
have this occasionally on cm10.1 flashing different nightlies.
mamar said:
Hi, I had this problem too and searching around I found a solution that fixed this problem twice for me:
Go to settings -> applications -> all and go to Phone. Clear data & clear cache. Do the same thing with Phone/Messaging Storage apk. You will loose your contacts but it fixed it.
Click to expand...
Click to collapse
I have the same problem which is "unfortunately the process com.android.phone has stopped". I hardly can reach settings -> applications -> all and go to Phone because of the error popping up but when I press it, it display another error behind the first one says: "unfortunately the process com.android.settings has stopped"
Any suggestions ??
Eklado said:
I have the same problem which is "unfortunately the process com.android.phone has stopped". I hardly can reach settings -> applications -> all and go to Phone because of the error popping up but when I press it, it display another error behind the first one says: "unfortunately the process com.android.settings has stopped"
Any suggestions ??
Click to expand...
Click to collapse
This problem is mainly caused by corrupt or incompatible APN predefined settings. Try clearing all of them and just using the one you need.
To speed up the process, navigate closing the error as many times as required to the apn list, and once in the list, toggle airplane mode ON, that will stop the force close to show up, now delete all the entries, and toggle off airplane mode.
jak3z said:
This problem is mainly caused by corrupt or incompatible APN predefined settings. Try clearing all of them and just using the one you need.
To speed up the process, navigate closing the error as many times as required to the apn list, and once in the list, toggle airplane mode ON, that will stop the force close to show up, now delete all the entries, and toggle off airplane mode.
Click to expand...
Click to collapse
First thank you for the fast response.
I have just updating my rom (from cm 10 to cm 10.1) and when the system starts after the end of booting the error appears.
I have activated the airplane mode and no changes the error is continuing and when I go to settings --> the press on more in networks it says: "unfortunately the process com.android.settings has stopped".
Eklado said:
First thank you for the fast response.
I have just updating my rom (from cm 10 to cm 10.1) and when the system starts after the end of booting the error appears.
I have activated the airplane mode and no changes the error is continuing and when I go to settings --> the press on more in networks it says: "unfortunately the process com.android.settings has stopped".
Click to expand...
Click to collapse
Then it's one app that you got installed. Try removing any non essential apps.
jak3z said:
Then it's one app that you got installed. Try removing any non essential apps.
Click to expand...
Click to collapse
Thank you sir for your help
but I solved it installing another kernel
Ever since I have unlocked my bootloader I have 2 things that bug me.
1. Whenever I restart my phone it asks for my password/pin/pattern everytime before it will start. It's not a huge deal except when I restart my phone and forget I have to do that part it sits a while waiting for the password.
2. The little "warning" screen that tells me my bootloader is unlocked. Just like the way the old Nexus's were with no warning, just the little white unlocked pad lock on the google screen.
It will ask for your password on restart even if your bootloader is locked.
That's standard behavior, It will prompt you for manual password entry on every restart. If you don't want it, then disable secure startup. The bootloader unlock warning is common as well.
When you set your pattern or password it asks you if you want it enabled before android boots.. If you don't want that then set it to none, then reset it to pattern and answer no when it asks the question if you want pattern/pin required before the system boots
Sent from my Nexus 6P using Tapatalk
You can disable it in Settings -> Security -> Screen Lock, and click Password, select "No thanks". Same with PIN or pattern lock.
The weird thing is that I selected 'No thanks' to pin on boot, and it is still there in the settings. But, should I reboot the device and use fingerprint to unlock it requires a pin.
graffixnyc said:
When you set your pattern or password it asks you if you want it enabled before android boots.. If you don't want that then set it to none, then reset it to pattern and answer no when it asks the question if you want pattern/pin required before the system boots
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
That must only work with an encrypted device?
I don't get the prompt or the setting.
tech_head said:
That must only work with an encrypted device?
I don't get the prompt or the setting.
Click to expand...
Click to collapse
Same here, rooted with mod boot image
I've tried all of the above and don't get the prompt or setting. I'm also modded, but this is driving me crazy. Is there no way to turn this setting off?
This setting is set when you're initially setting up the phone for sure - you have to manually choose "no thanks" on the page right before where you actually start tapping on the fingerprint sensor to set it up. I'm not certain about the encrypted vs. unencrypted piece, although I wouldn't think that would make a difference...
I did it once, and then reflashed my entire system and upgraded twice since then. I didn't have the option after that first time.
kboya said:
The weird thing is that I selected 'No thanks' to pin on boot, and it is still there in the settings. But, should I reboot the device and use fingerprint to unlock it requires a pin.
Click to expand...
Click to collapse
The exact same thing happened to me so it must be a bug
Pilz said:
The exact same thing happened to me so it must be a bug
Click to expand...
Click to collapse
Yep. Same here. I've tried everything and it still always asks me for my password on startup.
Really annoying since random reboots are an issue too.
Basically, if my phone reboots at during my sleep (which it has done a few times already) I don't have my alarm in the morning.
Same problem here. I selected 'No thanks' (don't ask for a password on reboot), but it still asks for a password after I use my fingerprint every time I reboot the phone. Changing from password to pattern and back and turning "ask for password" on/off didn't help.
Myrrhman said:
Yep. Same here. I've tried everything and it still always asks me for my password on startup.
Really annoying since random reboots are an issue too.
Basically, if my phone reboots at during my sleep (which it has done a few times already) I don't have my alarm in the morning.
Click to expand...
Click to collapse
gnadenlos said:
Same problem here. I selected 'No thanks' (don't ask for a password on reboot), but it still asks for a password after I use my fingerprint every time I reboot the phone. Changing from password to pattern and back and turning "ask for password" on/off didn't help.
Click to expand...
Click to collapse
It will always do this.
Unlock using your backup screen lock method
Sometimes you might need to use your backup PIN, pattern, or password:
*When your fingerprint isn't recognized after a few tries
*After restarting your device
*After switching to a different user on the device
*After more than 48 hours have passed since you last unlocked using your backup method
Click to expand...
Click to collapse
From "How to use your fingerprint" on Nexus Imprint Help page: https://support.google.com/nexus/answer/6285273?hl=en
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
It will always do this.
Click to expand...
Click to collapse
In that case, the option and dialogs to turn that behavior off are useless.
gnadenlos said:
In that case, the option and dialogs to turn that behavior off are useless.
Click to expand...
Click to collapse
I'm almost positive the "Password on boot" option y'all see blocks access to recovery as well. When enabled, I think it locks access to the phone on the recovery level with a password. With it off, you can fully access recovery. Could y'all try and see if that's what happens?
I don't see the "password on boot" setting in Chroma's security settings, idk if being decrypted affects this.
SlimSnoopOS said:
I'm almost positive the "Password on boot" option y'all see blocks access to recovery as well. When enabled, I think it locks access to the phone on the recovery level with a password. With it off, you can fully access recovery. Could y'all try and see if that's what happens?
I don't see the "password on boot" setting in Chroma's security settings, idk if being decrypted affects this.
Click to expand...
Click to collapse
Sorry, i'm not entirely sure what you mean.
I have TWRP installed and i do know when first booting into TWRP, you must enter the password. After that, you can normally boot into TWRP.
BTW: I've gotten rid of the random reboots it seems. I simply flashed the official firmware from the Google Developers site a few days ago. I've not had a random reboot since. Really happy about that.
Myrrhman said:
Sorry, i'm not entirely sure what you mean.
I have TWRP installed and i do know when first booting into TWRP, you must enter the password. After that, you can normally boot into TWRP.
BTW: I've gotten rid of the random reboots it seems. I simply flashed the official firmware from the Google Developers site a few days ago. I've not had a random reboot since. Really happy about that.
Click to expand...
Click to collapse
Does TWRP always prompt you for a password regardless of whether you have "Password on boot" on/off?
Editv Glad you resolved your random reboots! That's always a good feeling.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Does TWRP always prompt you for a password regardless of whether you have "Password on boot" on/off?
Editv Glad you resolved your random reboots! That's always a good feeling.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I tried (had to install the latest TWRP anyways) and no.
If you choose Password off at boot, TWRP won't prompt you.
I'm not sure what happened, but my Google Keyboard seems to have disappeared. Google Keyboard is not showing as an option under "Keyboard & input methods". I have Flesky and Swiftkey, so I'm getting by, but I don't know how to get it working. Gboard shows under Apps, and I've tried clearing cache, clearing data, force stop, and uninstall/reinstall, but it still doesn't appear as an option to use as a keyboard. How can I rectify this? Thanks in advance to anyone who has a solution.
sbs8331 said:
I'm not sure what happened, but my Google Keyboard seems to have disappeared. Google Keyboard is not showing as an option under "Keyboard & input methods". I have Flesky and Swiftkey, so I'm getting by, but I don't know how to get it working. Gboard shows under Apps, and I've tried clearing cache, clearing data, force stop, and uninstall/reinstall, but it still doesn't appear as an option to use as a keyboard. How can I rectify this? Thanks in advance to anyone who has a solution.
Click to expand...
Click to collapse
Google keyboard is replaced by Gboard but I think you already knew that. Also if you are on a custom ROM flash Gapps again. Gboard will appear on input options. If not maybe you have factory reset or wait for the app to be updated again .
PS did you reboot after clearing cache?
guessingagain said:
Google keyboard is replaced by Gboard but I think you already knew that. Also if you are on a custom ROM flash Gapps again. Gboard will appear on input options. If not maybe you have factory reset or wait for the app to be updated again .
PS did you reboot after clearing cache?
Click to expand...
Click to collapse
Thanks for the reply. I'm not rooted and therefore don't have a custom ROM, just the one that came with the device, so therefore I can't really flash anything. I went into recovery mode and did a cache wipe there, which, of course, requires reboot, to no avail. I'll wait to see if an update comes out soon and will live with 3rd party keyboards in the meantime. For what it's worth, I've included screen shots showing that Gboard is showing as an app but is not showing as an available keyboard. When I click "Current Keyboard", my only options are Flesky and Swiftkey.
The reply is appreciated.
sbs8331 said:
Thanks for the reply. I'm not rooted and therefore don't have a custom ROM, just the one that came with the device, so therefore I can't really flash anything. I went into recovery mode and did a cache wipe there, which, of course, requires reboot, to no avail. I'll wait to see if an update comes out soon and will live with 3rd party keyboards in the meantime. For what it's worth, I've included screen shots showing that Gboard is showing as an app but is not showing as an available keyboard. When I click "Current Keyboard", my only options are Flesky and Swiftkey.
The reply is appreciated.
Click to expand...
Click to collapse
Sorry to hear. If you do manage to get it fixed please reply to this thread. Thanks. I am on 7.0 and Gboard is running fine.
guessingagain said:
Sorry to hear. If you do manage to get it fixed please reply to this thread. Thanks. I am on 7.0 and Gboard is running fine.
Click to expand...
Click to collapse
Update: I finally got Gboard back. I tried a number of things, including a manual download and install of the apk. I decided to try Slash keyboard, and, when I installed it, I was taken to the screen to enable it, and, voila', Gboard shows up with an enable option. I don't know what happened, but it's working now.
sbs8331 said:
Update: I finally got Gboard back. I tried a number of things, including a manual download and install of the apk. I decided to try Slash keyboard, and, when I installed it, I was taken to the screen to enable it, and, voila', Gboard shows up with an enable option. I don't know what happened, but it's working now.
Click to expand...
Click to collapse
Actually, in your second screenshot, if you tap on "Current Keyboard" there will be a button to choose keyboard. If you press that, it will bring you to the screen where you can enable/disable keyboards. That's probably why Gboard was hidden.
doomed151 said:
Actually, in your second screenshot, if you tap on "Current Keyboard" there will be a button to choose keyboard. If you press that, it will bring you to the screen where you can enable/disable keyboards. That's probably why Gboard was hidden.
Click to expand...
Click to collapse
Yep. Not intuitive to me, but you're correct. I thought "Current Keyboard" was just a prompt to select one from the pop-up window. Often the answers are simple if you know where to look. Thanks! :good:
sbs8331 said:
Yep. Not intuitive to me, but you're correct. I thought "Current Keyboard" was just a prompt to select one from the pop-up window. Often the answers are simple if you know where to look. Thanks! :good:
Click to expand...
Click to collapse
No worries! They changed the menu structure in Nougat so it's more intuitive now.
Probably off topic but does anyone else not like the update they did to the keyboard? No way to remove that search menu row? I have never used the suggestions and wished I could remove it.
daverobinson88 said:
Probably off topic but does anyone else not like the update they did to the keyboard? No way to remove that search menu row? I have never used the suggestions and wished I could remove it.
Click to expand...
Click to collapse
Go to input > virtual > Gboard > settings > search and disable it.
It removes the search G but still keeps the row there. See attachment.
daverobinson88 said:
It removes the search G but still keeps the row there. See attachment.
Click to expand...
Click to collapse
Yeah that's true. I can't find an option to disable that. Maybe it's not possible in this update.
I am sort of in the same boat
Hey everyone.
Lastnight I installed, an android 7.0 custom rom to my tab pro 10.1. I used TWRP to flash install the ROM when it installed it automatically rebooted my device before I could go on to Gapps and install them with the the ROM. So when the ROM loaded up I connected to my hub (using the keyboards) then had a look at the new OS and the wife had a look out of interest with me and everything was working well in fact it was quicker than it was when we got it brand new.
Then playtime over rebooted back into TWRP and flashed Gapps. Then it rebooted again. When it finally loaded back in I was met with a loading screen saying Android is Starting which wouldn't go away but it asked me to sign back on to the Hub so went to do this on problem was.....no Keyboard.....so I managed to get into my setting through quick menu settings and find input settings and there is no keyboard installed to the device...it asked me to add one but I can't because I can't type and even if I could the android is starting message is still going.
Please help I am new to this and I want to learn all this type of thing but I am completely puzzled on what to do. I tried clear chase and data and even tried factory reset.....tried installing gapps on twice (before the factory reset) and nothing was working.
I am tough to use odin to flash it back to standard rom and start again but I could do with some pointers with what i have done wrong.
Thanks people
Owenboy89 said:
Hey everyone.
Lastnight I installed, an android 7.0 custom rom to my tab pro 10.1. I used TWRP to flash install the ROM when it installed it automatically rebooted my device before I could go on to Gapps and install them with the the ROM. So when the ROM loaded up I connected to my hub (using the keyboards) then had a look at the new OS and the wife had a look out of interest with me and everything was working well in fact it was quicker than it was when we got it brand new.
Then playtime over rebooted back into TWRP and flashed Gapps. Then it rebooted again. When it finally loaded back in I was met with a loading screen saying Android is Starting which wouldn't go away but it asked me to sign back on to the Hub so went to do this on problem was.....no Keyboard.....so I managed to get into my setting through quick menu settings and find input settings and there is no keyboard installed to the device...it asked me to add one but I can't because I can't type and even if I could the android is starting message is still going.
Please help I am new to this and I want to learn all this type of thing but I am completely puzzled on what to do. I tried clear chase and data and even tried factory reset.....tried installing gapps on twice (before the factory reset) and nothing was working.
I am tough to use odin to flash it back to standard rom and start again but I could do with some pointers with what i have done wrong.
Thanks people
Click to expand...
Click to collapse
You may wish to ask over in the Galaxy Tab Pro forums at https://forum.xda-developers.com/galaxy-tab-pro-12-10-8 - you've somehow wandered into the Moto G4 forums
But as a very general suggestion - sounds like your GApps isn't happy with your custom ROM. You may have to clean flash your custom ROM again and verify that the GApps you're flashing is suitable for your device/custom ROM.
I agree with you I have just download the same rom and a stock gapps and I had the same message and again with no keyboard.....agian. Difference this time I haven't rushed to do a factory reset and gone back and reflashed the android 7.0 rom and I am back working again with keyboard but no google apps.
Is there a way of installing them a different way, only 2 google apps I use is play store and gmail. I have tried installing a google play store and play services apk but doesn't work. It goes to load and then just stops.....feels like I need a list of apps to get them going.
Hope someone can help
I worked out my problem with Gapps, "android is starting messages" and no keyboard.
1. I needed to wipe my cache, data and davarlik (whatever it says....looks like darlik to me...lol) before and after.
2. Like fella before said my ROM didn't like the Gapps package I had downloaded, so everytime I had the android message I went back on to TWRP and restored back to the orginal point where the lineage ROM worked, then went back on to the net and installed the next Gapps package and repeated till I found a package that worked......that package was the "Micro" package.
Any google apps I was missing I simply just downloaded them via the playstore after.
I realise this is a moto G forum but I find that sometimes you need to go other places to find answers and I had originally looked in the samsung Tab Pro 10.1 forum section and couldn't find anything similar to my problem this fella at the beginning of the thread was the closest to my problem I could fine.
Hope this helps
Hi everyone,
so in my immense stupidity, I actually managed to set my phone password wrongly, and now I can't get in. Spent a day trying passwords to find the typo but that was unsuccessful.
I have crDroid Android 11, bootloader unlocked, rooted with magisk, and TWRP 3.5.0.
How can get my phone back? I would love to save the internal storage since I have important stuff, but you know, if wiping it is the only way I have to go for it.
Thanks in advance.
Use this method. I have seen many people online suggesting it works.
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
You are essentially removing lockscreen settings completely and should work as you still have TWRP access.
madman said:
Use this method. I have seen many people online suggesting it works.
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
You are essentially removing lockscreen settings completely and should work as you still have TWRP access.
Click to expand...
Click to collapse
Thanks for the responce, but unfortunately that didn't work.
I deleted the files as explained in the thread you linked but now the lockscreen doesn't work at all, it's just a black screen. The power menu appears if I hold the power button, but nothing else. I tried swiping in some direction on the black screen but it doesn't unlock.
Also tried to sideload the rom again (dirty and clean flash), and magisk, still no luck.
Read the entire thread but nothing helpful.
DarkLudo77 said:
Thanks for the responce, but unfortunately that didn't work.
I deleted the files as explained in the thread you linked but now the lockscreen doesn't work at all, it's just a black screen. The power menu appears if I hold the power button, but nothing else. I tried swiping in some direction on the black screen but it doesn't unlock.
Also tried to sideload the rom again (dirty and clean flash), and magisk, still no luck.
Read the entire thread but nothing helpful.
Click to expand...
Click to collapse
Is TWRP able to decrypt the data? I'm guessing that's a no as the password is not accepted by the lockscreen. If TWRP was magically OK with the password, you could have adb pulled the files.
But apart from reseting the lockscreen using TWRP, I don't know a way to fetch the files.
madman said:
Is TWRP able to decrypt the data? I'm guessing that's a no as the password is not accepted by the lockscreen. If TWRP was magically OK with the password, you could have adb pulled the files.
But apart from reseting the lockscreen using TWRP, I don't know a way to fetch the files.
Click to expand...
Click to collapse
TWRP can decrypt if the correct passoword is provided. Tried pulling with adb the files anyway, even if they are encrypted, but the phone doesn't allow that either.
Thanks anyway