[Q] SDFix on S5 suddenly stopped working. - Galaxy S 5 Q&A, Help & Troubleshooting

Hi
I'm running a rooted Samsung S5 (SM-900F) with the SDFix ( https://play.google.com/store/apps/details?id=nextapp.sdfix).
Today it suddenly wouldn't allow me to move files from the internal memory to my SD-card or from one folder on the SD-card to another folder on the SD-card. I tried re-fixing it with the SD-fix app, but the app tells me it's already fixed. I use QuickPic as a gallery and Solid Explorer as a file explorer. These have worked flawlessly since the S5 was released, now they don't.
Any idea on how to fix this? I'm so pissed off at Google for even implementing this idiotic restriction!

randomher0 said:
Any idea on how to fix this?
Click to expand...
Click to collapse
Well the obvious way would be to revert to a backup from yesterday or a few days ago when it was working fine. Easy peasy. done.
But as you haven't done that.. I can only assume that you don't make backups, which is very bad. Everyone should make backups. If you had a backup your issue would already be solved.
Moving on, what has changed? Did you accept any OTA updates, what was the last program you installed? If the problem started at the same time, try uninstalling that program temporarily.
Check the properties in platform..xml to see if your SD card permissions are intact. Wipe the cache partition from recovery mode, and wipe your file explorer and photo viewer cache and data from the settings menu applications manager for those two apps. If the problem persists, then try reinstalling your file explorer.
.

Related

[Q] /storage/emulated/0 not accessible

I would appreciate some help with the following issue:
After upgrading android to 4.4.2, the directory /storage/emulated/0 became inaccessible to the apps using it, such as GO Contacts EX (export contacts), viber and sms backups, among many. Whenever I can set the directory to the external SD card I am able to make backups, but not otherwise. The phone is rooted, and if using root explorer I can browse this directory and permissions on it appears to be fine (on storage and emulated the are rwxr-x--x, on 0rwxrwx--x)
Please advise how to resolve this issue.
Thanks,
john.smith1972 said:
I would appreciate some help with the following issue:
After upgrading android to 4.4.2, the directory /storage/emulated/0 became inaccessible to the apps using it, such as GO Contacts EX (export contacts), viber and sms backups, among many. Whenever I can set the directory to the external SD card I am able to make backups, but not otherwise. The phone is rooted, and if using root explorer I can browse this directory and permissions on it appears to be fine (on storage and emulated the are rwxr-x--x, on 0rwxrwx--x)
Please advise how to resolve this issue.
Thanks,
Click to expand...
Click to collapse
using this useful tool would most likely sort the problem for you...
spamtrash said:
using this useful tool would most likely sort the problem for you...
Click to expand...
Click to collapse
Thanks for getting back to me. Unfortunately this did not fix the issue. I tried also to change the configuration of the permissions.xml as discussed in other topics, but that did not help either.
I would appreciate any other ideas on the topic.
john.smith1972 said:
Thanks for getting back to me. Unfortunately this did not fix the issue. I tried also to change the configuration of the permissions.xml as discussed in other topics, but that did not help either.
I would appreciate any other ideas on the topic.
Click to expand...
Click to collapse
1. IF you are able to access the card with explorer (NOT root explorer)
2. IF the installed apps cannot access it
THEN I'd check the name of card, if its mounting point changed etc. In that case, reinstallation of app could potentially sort out the issue.
spamtrash said:
1. IF you are able to access the card with explorer (NOT root explorer)
2. IF the installed apps cannot access it
THEN I'd check the name of card, if its mounting point changed etc. In that case, reinstallation of app could potentially sort out the issue.
Click to expand...
Click to collapse
Thanks again for the suggestions. One thing that apparently I am not clear is whether this directory is part of the internal memory. So far I thought it was, and it was emulating external storage, while being an internal memory. Otherwise I can access it, and reinstalling an app did not help - the issue still persists in its original state. Also, I tried changing the permissions of the directories with root explorer to rwxrwxrwx, and I was able for the /storage and /storage/emulated, but not for /storage/emulated/0, where I got an error message that the operation failed.
I would gladly do a backup and revert back to 4.3, but I cannot do backups of anything, mostly I care about my viber and whatsapp messages (they also fail to create backups).
Thanks,
john.smith1972 said:
I would gladly do a backup and revert back to 4.3, but I cannot do backups of anything, mostly I care about my viber and whatsapp messages (they also fail to create backups).
Thanks,
Click to expand...
Click to collapse
Beside other things, you cannot return back because of different bootloader. since you are with 4.4.2, you are with 4.4.2 or HIGHER. Period.
spamtrash said:
Beside other things, you cannot return back because of different bootloader. since you are with 4.4.2, you are with 4.4.2 or HIGHER. Period.
Click to expand...
Click to collapse
I see, so I am stuck with the 4.4.2, which is too bad but it is what it is. I guess it is a hard reset without a backup then, and if that doesn't work, off the phone goes to the garbage...
Did you not get su prompt to disable Knox when first rooted. I did and I have read/write access to both internal and external SD card.
Also froze all Knox related apps with TB.
Sent from my Nexus 7 using XDA Premium 4 mobile app
bored_stupid said:
Did you not get su prompt to disable Knox when first rooted. I did and I have read/write access to both internal and external SD card.
Also froze all Knox related apps with TB.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hard reset and installation of CM 10.2 based on android 4.3 resolved the issue. After this I would advise noone to upgrade to 4.4.
Thanks to everyone who helped with the issue.

Unable to write/delete files?

Did a swap from a 64 GB 6P to a 128 GB and tried just doing a nandroid. That would've worked but the fingerprint reader wouldn't work without a factory reset. I also accidentally restores the old EFS in TWRP without knowing I shouldn't, but used the original EFS (did a backup on new device before transfer) and restored it back to what came the device.. So I did that and re-did everything and it seemed to have no problems at first. I downloaded some Google Music playlists, Viper4A + busybox, and at some point my phone stopped letting me modify the files.
Camera can't take pictures. Chrome can't download files. I can't add/remove files via PC. I can't modify files via file managers. I tried chmod 777 sdcard but it doesn't fix the problem. I tried reflashing the ROM and all, and did a complete wipe but restored the data (only) from TWRP - so the problem might be somewhere in there. I haven't changed anything from the setup I had on the 64 GB, so I don't know what the hell happened - it was working fine and then just stopped letting me do stuff.
I'll probably try a complete factory firmware restore then flash the ROM all over again, but wanted to see if there was a simple fix first.
Nitemare3219 said:
Did a swap from a 64 GB 6P to a 128 GB and tried just doing a nandroid. That would've worked but the fingerprint reader wouldn't work without a factory reset. I also accidentally restores the old EFS in TWRP without knowing I shouldn't, but used the original EFS (did a backup on new device before transfer) and restored it back to what came the device.. So I did that and re-did everything and it seemed to have no problems at first. I downloaded some Google Music playlists, Viper4A + busybox, and at some point my phone stopped letting me modify the files.
Camera can't take pictures. Chrome can't download files. I can't add/remove files via PC. I can't modify files via file managers. I tried chmod 777 sdcard but it doesn't fix the problem. I tried reflashing the ROM and all, and did a complete wipe but restored the data (only) from TWRP - so the problem might be somewhere in there. I haven't changed anything from the setup I had on the 64 GB, so I don't know what the hell happened - it was working fine and then just stopped letting me do stuff.
I'll probably try a complete factory firmware restore then flash the ROM all over again, but wanted to see if there was a simple fix first.
Click to expand...
Click to collapse
I would just flash the factory image and start over. Sounds like something went wrong with the various issues you had.

Samsung S4 I9505 no Whatsapp backup possible

Hi,
I can't perform a Whatsapp backup since January this year, regardless if Google Drive Backup is checked, if the Whatsapp app is stored in the local or on sd card memory, automatic backups are being cancelled, too.
After I hit "Backup", the Dialogue "Messages are being backed up" shows up, which closes after 10 sec without any error message.
I tried to contact the WA Support, but they insist that my S4 is rooted (which it isn't, maybe because of the custom ROM I use).
I have flashed my Samsung I9505 in January this year from CM 12.1 to CM 13. At the beginning, the phone ran smoothless except BT. After a while, WiFi stopped working as well. I tried to flash the CM 12.1 backup and radios without any success, just a new mainboard helped. I installed my CM 12.1 backup from January via TWRP from my old mainboard, which ran without any errors on it (after a fullwipe on the new one).
The phone works great, except the WA backup.
WA gets always updated to the current version, I have ~1,2 GB free internal memory, I tried to update to the latest CM 12.1 5.1.1 version from 12/26/2015, perform a backup via 4G, 3G, Wifi, with an without Google Backup checked, cleared the cache and wiped Dalvic Cache, there is no app deactivated.
I use Baseband I9505XXUHOD7 and Kernel: 3.4.107-cyanogenmod-gab9afd6clyde.
Running a custom ROM means you are rooted.
Now, I don't know why whatsapp wouldn't work on a rooted ROM, but if you want to backup you can use titanium backup.
GDReaper said:
Running a custom ROM means you are rooted.
Now, I don't know why whatsapp wouldn't work on a rooted ROM, but if you want to backup you can use titanium backup.
Click to expand...
Click to collapse
There is no root, please check the screenshot below.
Since there is no root, I can't use Titanium Backup, however, it wouldn't be the most practicable way to backup your Whatsapp history every time with Titanium Backup.
Besides that, I don't think this would work if I would like to transfer my history to a new phone on which WA Backup should work as intended as I won't flash the ROM/install root and void the warranty.
WA backup worked perfect with the old logicboard before flashing CM 13.
m_pa said:
There is no root, please check the screenshot below.
Since there is no root, I can't use Titanium Backup, however, it wouldn't be the most practicable way to backup your Whatsapp history every time with Titanium Backup.
Besides that, I don't think this would work if I would like to transfer my history to a new phone on which WA Backup should work as intended as I won't flash the ROM/install root and void the warranty.
WA backup worked perfect with the old logicboard before flashing CM 13.
Click to expand...
Click to collapse
Root has to be activated from developer options.
That is definitely a whatsapp problem if it worked before.
GDReaper said:
Root has to be activated from developer options.
That is definitely a whatsapp problem if it worked before.
Click to expand...
Click to collapse
Well, I haven't even unlocked the developer options until now..
Any idea how to convince WA doing it's job? Anybody with this problem before?
if you really want a backup it makes more sense that you either activate root or flash superSU yourself rather than wait on whatsapp to change their code just for you. they've already told you effectively that they aren't going to do anything for you and don't have to.
backing up the app and data with TiBu and copying the whatsapp folder achieves everything you want and has worked flawlessly for me many many times.
Well guys, got a new phone but the problem persists when trying to restore my history on the new phone and really need your help.
Got root on the old phone and saved the com.whatsapp folder of it with the key file and databases. How can I encrypt the msgstore.db to msgstore.db.crypt8?
I have tried the app Whatcrypt, which creates a msgstore.db.crypt file, as large as msgstore.db, but Whatsapp on the new phone does not recognize it as a backup file.
When using whatcrypt.com and uploading the key and msgstore.db, it tells me "Encryption failed / Incorrect account?"
Also tried Omni-Crypt app. It creates msgstore.crypt, which Whatsapp ignores as well ("searching for Backups" with waiting triangle for hours)
I don't know any other way and I'm literally stuck now
when i mentioned copying the apps folder i was thinking of the one on the root of your internal storage, not the one in Android/data/...
you can paste that onto a new phone and restore the app and data with titanium.
3mel said:
when i mentioned copying the apps folder i was thinking of the one on the root of your internal storage, not the one in Android/data/...
you can paste that onto a new phone and restore the app and data with titanium.
Click to expand...
Click to collapse
Of course I can copy the Whatsapp folder on the root of the storage but this folder only contains the wa media files of my old phone since there are no msgstore.db.cryptX files created by Whatsapp.
For TiBa I would need to root the new phone which is a S7 Edge and I would like to avoid this until the warranty has expired. It is not as easy to do repairs by yourself as the S4..
fair enough, have you tried copying both folders over and installing from playstore ? or rather, install the app but don't open it, copy over both folders and then try and see what happens...

Not so Easy Backup; storage snafu has MXPE stuck in cyclical forced reboots

So I ran into an issue with my locked-bootloader, unrooted MXPE 2015. I am running stock Marshmallow. I will note that I don't think this is really a bootloop, it seems to boot for a few seconds before a crash/reboot. I am able to boot into recovery, and am even able to trigger a safe-mode boot during the few seconds of uptime, where the safe-mode boot does not crash/reboot. I also suspect a Factory Reset will fully resolve the issue, unless the factory image got corrupted somehow... I do apologize, this is a long post.
I was essentially trying to make a backup to do a factory reset. Long story short, I was trying to use an app called Easy Backup that consolidates sms, mms, call logs, and that I had used in the past without issue. However this time that was not the case. I have a 16 GB version with an SD card, but have used ~8.5 GB of the internal free ~9.8 GB (I can't remember the exact numbers) and I constantly run into low storage situations with app caches and install sizes when doing updates. Normally clearing all app cache data is enough to get the downloads to go through.
So I go to run this backup app (with the default storage directory set on my external SD card) to have it uploaded to Google Drive, and after it gets close to finishing, I get errors about running out of storage, and then a cascade of apps crashing, and then a reboot. After the reboot, I check my Drive folder and see that the file never uploaded; the storage seems to have cleared up, but I clear my cache and the backup app's storage just in case (though it had already pretty much cleared back to the 8.5 GB used from before). I also notice some oddities like random settings suddenly having changed in certain apps. But I stupidly think no harm has been done, so maybe retrying after clearing up Cache space will work. So I tried to get the backup to run again after verifying the upload and storage location options (SD Card -not internal - and G Drive), but the same storage and crashing thing happens. It "finishes" the backup, and after a few seconds of the phone hanging and lagging, it reboots again. This time after the reboot I notice that apps are missing from my Nova Launcher home screen (but still in my app drawer), and go to restore a backup of Nova, except the overview and home buttons don't do anything, and then see that the notification shade can't be pulled to open the settings toggles. Then it suddenly reboots again. And now, unless I boot into safe mode, I get a few seconds of of it sitting at the home screen before the phone reboots. This same nav button and settings shade behavior are persistent in safe mode.
I guess my question is whether or not there is a way to pull off my SMS, MMS, Call log data (maybe in ADB?) while in safe mode. I have been trying to uninstall extraneous apps in Safe Mode to see if I can break the rebooting cycle, but no luck thus far.
On another note, should I go ahead and do a factory reset or should I contact Moto first (I have a Moto Care policy, though I've heard horror stories). I have never had this issue with this app before,
Any other recommendations and tips? It almost seems like the app tries to cache on my internal storage before moving to the destination folder, and in a low storage situation it seems to have corrupted something in the actual OS as well as my other apps.
Thank you, I appreciate your time!
If memory serves, apps like Easy Backup may store things on external storage or upload to the cloud, but use app cache space as temporary working space, thus most likely causing your storage issue. Erasing app cache likely wiped that out, and your are correct that a factory reset will likely clear up this issue.
Moto care doesn't care if an app messed up your system, and they won't help you with it other than to walk you through a factory reset first before sending the device in for replacement, as I suspect a factory reset will clear your issues up.
Have you tried clearing the cache partition in recovery?
Recovering your data will be impossible if you can't get it booted long enough to enable ADB and copy the files off.
If you can get if booted, I suggest using SMS Backup & Restore over your existing backup tool for this type of data... I have used it successfully for many years without issues (except when they accidentally had it set by default to delete all but the last 2 backup file on Google Drive, geesh, that sucked, but that isn't an issue anymore).
acejavelin said:
If memory serves, apps like Easy Backup may store things on external storage or upload to the cloud, but use app cache space as temporary working space, thus most likely causing your storage issue. Erasing app cache likely wiped that out, and your are correct that a factory reset will likely clear up this issue.
Moto care doesn't care if an app messed up your system, and they won't help you with it other than to walk you through a factory reset first before sending the device in for replacement, as I suspect a factory reset will clear your issues up.
Have you tried clearing the cache partition in recovery?
Recovering your data will be impossible if you can't get it booted long enough to enable ADB and copy the files off.
If you can get if booted, I suggest using SMS Backup & Restore over your existing backup tool for this type of data... I have used it successfully for many years without issues (except when they accidentally had it set by default to delete all but the last 2 backup file on Google Drive, geesh, that sucked, but that isn't an issue anymore).
Click to expand...
Click to collapse
Yes, I did try cleaning the cache partition, but to no avail. Ironically because I was messing with ROMs on my old 2013 moto x, I'm currently using that with CM 13. When I get back from work tonight I'll see about ADB, I think I may have set it up on it in the past, however I may have deactivated it. And yeah, I think I may have used that tool in the past, so I'll have to give it another look!
I thought that the Moto Care route may not be worth it, but I thought that I might as well check. If a reset doesn't solve things, I'll take another look. Thanks for the help, really appreciate it!
acejavelin said:
If memory serves, apps like Easy Backup may store things on external storage or upload to the cloud, but use app cache space as temporary working space, thus most likely causing your storage issue. Erasing app cache likely wiped that out, and your are correct that a factory reset will likely clear up this issue.
Moto care doesn't care if an app messed up your system, and they won't help you with it other than to walk you through a factory reset first before sending the device in for replacement, as I suspect a factory reset will clear your issues up.
Have you tried clearing the cache partition in recovery?
Recovering your data will be impossible if you can't get it booted long enough to enable ADB and copy the files off.
If you can get if booted, I suggest using SMS Backup & Restore over your existing backup tool for this type of data... I have used it successfully for many years without issues (except when they accidentally had it set by default to delete all but the last 2 backup file on Google Drive, geesh, that sucked, but that isn't an issue anymore).
Click to expand...
Click to collapse
So I did get in and take another look, however developer options just shows "Developer permissions not available for this user." So I think i may be hosed. I'll give it another go and see what I can try to salvage from booting into safe mode again. Thank you for the help and recommendations, this willteach me not to be using something like SMS backup instead (and consistently, haha).
jtflynnz said:
So I did get in and take another look, however developer options just shows "Developer permissions not available for this user." So I think i may be hosed. I'll give it another go and see what I can try to salvage from booting into safe mode again. Thank you for the help and recommendations, this willteach me not to be using something like SMS backup instead (and consistently, haha).
Click to expand...
Click to collapse
Sounds like you are in a Guest user account, can you switch users?
acejavelin said:
Sounds like you are in a Guest user account, can you switch users?
Click to expand...
Click to collapse
So I looked at that, and it says I am logged into my account. Photos below:
So coincidentally, I just got it connected to my wifi while in safe mode, and it hasn't crashed/rebooted since that (it still was doing that prior). I can get into the play store, so I am going to try to get my sms/call logs/mms. Home and overview buttons are still broken, and the notification shade is still borked. So No ADB backup, but at least I have most things on my SD card and was on MM, so the app backups should help get restarted. Once I get everything checked/backed-up that I can, I'll try a factory reeset, and failing that a call to moto care *cringes*.
Thanks for the help everyone! I learned my lesson on small-storage phones...
jtflynnz said:
So I looked at that, and it says I am logged into my account. Photos below:
So coincidentally, I just got it connected to my wifi while in safe mode, and it hasn't crashed/rebooted since that (it still was doing that prior). I can get into the play store, so I am going to try to get my sms/call logs/mms. Home and overview buttons are still broken, and the notification shade is still borked. So No ADB backup, but at least I have most things on my SD card and was on MM, so the app backups should help get restarted. Once I get everything checked/backed-up that I can, I'll try a factory reeset, and failing that a call to moto care *cringes*.
Thanks for the help everyone! I learned my lesson on small-storage phones...
Click to expand...
Click to collapse
Do you have a corporate account on the device that is a Device Administrator? That is the only other thing I can think of that could cause something like that.
acejavelin said:
Do you have a corporate account on the device that is a Device Administrator? That is the only other thing I can think of that could cause something like that.
Click to expand...
Click to collapse
No, nothing like that. It's my own personal device with no work emails, and in fact I had previously used USB debugging to backup pictures when my SD Card got corrupted. All of this weirdness occured after the failed backups, and just speculating it honestly seems like when the app ran out of room it just kept going and started overwriting random bits (ie the Nova Launcher settings/ homescreen), and might be why the Navigation buttons/Notification shade are broken. But that's just me spit-balling , so really there might be no telling what happened.
jtflynnz said:
No, nothing like that. It's my own personal device with no work emails, and in fact I had previously used USB debugging to backup pictures when my SD Card got corrupted. All of this weirdness occured after the failed backups, and just speculating it honestly seems like when the app ran out of room it just kept going and started overwriting random bits (ie the Nova Launcher settings/ homescreen), and might be why the Navigation buttons/Notification shade are broken. But that's just me spit-balling , so really there might be no telling what happened.
Click to expand...
Click to collapse
Well... Try to get off what you can, then factory reset, I imagine things will improve greatly.
I just had an issue similar to this... phone (1575) would reboot (continuous reboot) after about 30-45 seconds every time (reminded me of TV show Lost where you had only a certain amount of time before you had to reset)... enough to uninstall a GPS app I was tinkering with a few hours prior... enough to delete cache... enough to reboot into recover to wipe cache partition... about 4 reboots to finally download a Google app update (which in the end said it couldn't successfully install) etc. Sometimes powering off would reboot instead (and after a while could not reboot into safe mode, just a normal reboot) so the few times I had the phone off, I took out/reset the SIM and SD card. What seemed to solve it was taking out the SD card (formatted as External, but was always a pain -- a week or so ago it "disappeared" and had to reformat the SD card (just downloaded stuff)) and when I powered it up this morning, no more reboots. Of course for now, no more added storage But saved me a full factory reset.

Titanium Backup Crashes If You Try To Restore

So over the weekend, I chose to root my phone and get the newest 10u update (model h918) and everything seemed to work fine and everything works well.
However, that changed when I transferred my titanium backup files to my v20 from my note 3 and tried to restore a few games. The thing is that I can backup apps, but can't restore them at all. It crashes in response to it. I've checked google play store reviews and others are experiencing this on the model number, so I hope that there can be a fix to this.
Here's what I did:
Dragged and copied all the backup files from my note 3 to my computer
Created a com.kermidas.TitaniumBackup folder into my sd card.
Dragged and copied all the backup files from my computer to v20
Tried to restore from files, crashes every time.
Tested to see if backing up works, indeed it does.
Restarted my phone and tried again, fails.
Uninstalled and reinstalled
Same thing happens again.
If there's something wrong I hope I get to fix it, otherwise oh well, guess I have to get used to it.
Looking forward for a fix, so please give me some suggestions.
Thanks
ZenovajXD said:
So over the weekend, I chose to root my phone and get the newest 10u update (model h918) and everything seemed to work fine and everything works well.
However, that changed when I transferred my titanium backup files to my v20 from my note 3 and tried to restore a few games. The thing is that I can backup apps, but can't restore them at all. It crashes in response to it. I've checked google play store reviews and others are experiencing this on the model number, so I hope that there can be a fix to this.
Here's what I did:
Dragged and copied all the backup files from my note 3 to my computer
Created a com.kermidas.TitaniumBackup folder into my sd card.
Dragged and copied all the backup files from my computer to v20
Tried to restore from files, crashes every time.
Tested to see if backing up works, indeed it does.
Restarted my phone and tried again, fails.
Uninstalled and reinstalled
Same thing happens again.
If there's something wrong I hope I get to fix it, otherwise oh well, guess I have to get used to it.
Looking forward for a fix, so please give me some suggestions.
Thanks
Click to expand...
Click to collapse
what did you use to root the lg phone? which su mgr?
did you change the name space manager or whatever titanium backup errors on startup?
Alibaba0101 said:
what did you use to root the lg phone? which su mgr?
did you change the name space manager or whatever titanium backup errors on startup?
Click to expand...
Click to collapse
I used lafsploit with Magisk 17.1. I did get a "this su may not be compatible with titanium backup, if not, try using SuperSU" obviously we know what happened to that however...
ZenovajXD said:
I used lafsploit with Magisk 17.1. I did get a "this su may not be compatible with titanium backup, if not, try using SuperSU" obviously we know what happened to that however...
Click to expand...
Click to collapse
And you have magisk manager 5.9 or 6 installed? Does magisk have the same namespace settings as supersu? Did you try and install titanium backup from googleplaystore? You are trying non-system apps?
NVM this post I accidentally erased it while editing
Alibaba0101 said:
And you have magisk manager 5.9 or 6 installed? Does magisk have the same namespace settings as supersu? Did you try and install titanium backup from googleplaystore? You are trying non-system apps?
Click to expand...
Click to collapse
Magisk Manager version is 6.0.0, I did install Titanium Backup through play store and I'm only restoring non system apps. My namespace settings are Inherited Namespace, not sure what SuperSU has.
Seems a general issue which started since August security patch update.
Tried on two different devices (oneplus one and Mix 2S), both with Android P with August/September security patch and there is no way to avoid this FCs after the first one, at the best you can make it start on the first launch and restore only data, but if it crashes then for some reason it doesn't matter what you do, it will always crash after this.
mustang_ssc said:
Seems a general issue which started since August security patch update.
Tried on two different devices (oneplus one and Mix 2S), both with Android P with August/September security patch and there is no way to avoid this FCs after the first one, at the best you can make it start on the first launch and restore only data, but if it crashes then for some reason it doesn't matter what you do, it will always crash after this.
Click to expand...
Click to collapse
I have the May Security Patch, I have the system version 10u so I haven't updated to Oreo as of yet
I have the same problem on another device. I got a rom on which titanium worked before but now after a clean install not. I only changed the gapps pack. so I think and has something to do with different or newer packs.
Edit: fixes it by installing titanium 8.1.0 instead of newest build. But I needed to clean install rom because it kept crashing from the previous install
gohan456 said:
I have the same problem on another device. I got a rom on which titanium worked before but now after a clean install not. I only changed the gapps pack. so I think and has something to do with different or newer packs.
Edit: fixes it by installing titanium 8.1.0 instead of newest build. But I needed to clean install rom because it kept crashing from the previous install
Click to expand...
Click to collapse
I did a clean install of 10u when I unlocked my phone, but I found out that I can only restore data only, which I'm all good for, at least if anything it's livable, but still looking for fixes.
I had problems with some apps (usually system apps) but most of what i needed like google playstore apps restored fine. Apps that need accounts was always 50/50. I'm still on 10u too. There is a warning on titanium startup about if you have problems try turning off mount namespace separation. May be worth a try.
Also,
I'm running supersu on my v20.

Categories

Resources