Database errors and unable to to sync sdcard folder: [SOLVED] - Sprint HTC One (M7)

Hi,
Well I am running a build of 4.2 attempted to go back to 4.1.2 and having not read the articles on the sdcard symlinks, had issues. So I went back to my 4.2 build.
I then proceeded to move files to the correct folder and now In some apps (Astro File Manager, Dropsync) I am getting errors. Astro says Error Code 14 database error and Dropsync says folder not writeable.
I am thinking it has to do with symlinks but not sure how to fix.
Thanks
Kevin
[Edit]
it was a permissions issue. Just had to run some commands to fix data/media. for reference
http://forum.xda-developers.com/showthread.php?t=2222297 sdcard Fix Permissions script

Related

Can't delete folder on my internal memory.

I had ktoonsez installed on my previous rom, I switched over to a different rom and now I can't delete the folder in my internal memory called, "device." When I look in the folder it has ktweaker and other stuff, I've tried to mount the system as r/w but it still doesn't work. Does anyone else have this folder? Photos attached.
Try looking in /data/media/0 or /data/media/legacy
See if the folder is there and try deleting it. Sometimes the files on /sdcard are just images of the data folder. GL!
Delete any folder easily
If you fell any problem to do copy,paste,error Deleting File or Folder.Then you should use Long Path Tool to solve your problem.
If Long Path Tool fails on start up, please ensure you have .net framework installed on your PC.

[Q] TWRP Nandroid Backup/Lollipop Issue...

I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
lords8n said:
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?
lords8n said:
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
Click to expand...
Click to collapse
husky69 said:
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?
Click to expand...
Click to collapse
FAQ
Google Play Edition 5.0.1
SdCard
Q.)
The sdcard not being visible via PC is annoying.
Is there any fix for this yet?
A.)
Yes, here is a work-around
Install Terminal Emulator then type:
Code:
su
restorecon -FR /data/media/0
and sdfix in the play store should do it
husky69 said:
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?
Click to expand...
Click to collapse
The issue definitely seems to be related to Lollipop. I didn't have the problem running KK, either. From all the research I've done it seems to be related to Lollipop looking for the sdcard in data/media/0 while KK and TWRP point to storage/emulated/0. The terminal command restorecon -FR /data/media/0 fixed it for me.
As for the automated Nandroid and sync, I use a combination of Tasker, OpenRecoveryScript, and FolderSync on the Android side and a few .bat scripts on the server side.
Tasker deletes the previous backup, copies the OpenRecoveryScript to the proper folder, sets a variable to show backup has started, then reboots into recovery where TWRP then performs the Nandroid and reboots. On reboot Tasker checks that the Nandroid folder exists, triggers a notification saying same, then triggers FolderSync to sync to my server. I only keep one backup on my phone and 2 on my server. I set Foldersync to sync deletions which deletes the previous backup on my server, but I also have my server set to copy the Nandroid to a separate directory, so I always have 2 backups if necessary. I use a script on my server that checks for the newest Nandroid, then copies it to separate directory before deleting the oldest one. When I wake up in the morning I can see Tasker notification that Nandroid file exists and FolderSync notification of successful sync. I also have Tasker set to trigger a notification if Nandroid fails, and Foldersync will also notify if an error occurred during sync. I use a Tasker profile to trigger all of this at 3am but I also have a shortcut that allows me to perform it manually whenever I want, with 1 click.
Note that this method requires the paid version of FolderSync for Tasker integration and is a little involved, but I've tried other methods (Onandroid, etc...), and this one is the most reliable. I know I can count on Tasker and TWRP to do their jobs, no third party necessary. The only redundancy variable I haven't taken into consideration is if the Nandroid backup is corrupt, but TWRP seems pretty reliable in that dept and that hasn't happened yet...
If you're interested, I'll send you the corresponding Tasker profiles and tasks.
lords8n said:
If you're interested, I'll send you the corresponding Tasker profiles and tasks.
Click to expand...
Click to collapse
I am interested
husky69 said:
I am interested
Click to expand...
Click to collapse
Sorry for the delay, been busy with holiday stuff. Here are the Tasker/Nandroid files. Extract the .prf files to /Tasker/profiles and the .tsk files to /Tasker/tasks, then import each into Tasker. You will need to edit (in Tasker) Nandroid_Backup.tsk.xml to reflect your TWRP Nandroid backup folder, and openrecoveryscript (in txt editor) to add/remove backup options if necessary.

[Q] TWRP Nandroid/Lollipop SDcard Storage issue...

I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
In a terminal app type
Su
restorecon -FR /data/media/0
Ajxx16 said:
In a terminal app type
Su
restorecon -FR /data/media/0
Click to expand...
Click to collapse
Thanks for the help Ajxx16. Tried your suggestion and get: tmp-mksh: restorecon: not found
You have root correct?
Ajxx16 said:
You have root correct?
Click to expand...
Click to collapse
Yes. Rooted running SuperSu 2.37 and TWRP 2.8.1.0. I also tried applying the restorecon patch through TWRP's terminal. It seems like it did something, but again when I boot back into the system, sdcard folder listed as empty. I just flashed a Nandroid backup I had of 4.4.4 and no sdcard issue. I'm going to update back to 5.01 (slowly, monitoring each step) to see if I can troubleshoot when the issue starts again, if at all (which wouldn't bother me if it didn't, really).
So I updated from 4.4.4 and ran into the same issue. It turns out the ROM I was updating from somehow did not have restorecon in the system/bin folder. I was able to find a 5.01 GPE RUU, flashed that, applied restorecon fix, and issue is resolved. Thanks for the help Ajxx16!

TWRP Backup Failed XT1053; Can't delete folder

Just recently I had to do a full wipe of my phone and reflash the custom rom i was running because of some problems I was having. As soon as i flashed the rom again i got this error:
E:Unable to stat '/data/data/Swiftkey/Files/language_models/user/learned.json
but the flash was succesful so I didn't think too much of it
After I booted up my phone i noticed that i couldn't install Super Swiftkey or the regualr Swiftkey app. I then tried going to ES File Explorer, I searched for the folder and i tried to delete it, but it wouldn't let me i got the message: File not deleted error code 39 so I tried changing the name and path of the folder , I changed the folder's name to "Cristian" and pasted it on the downloads folder where i was able to delete the folder and then I was able to install Super Swiftkey again.
The problem is I just tried doing a nandroid backup with two different TWRP versions and i get the same error:
Updating partition details...
E:Unable to stat '/data/data/Cristian/Files/language_models/user/learned.json
right after that the backup fails. I get the same message for wiping cache or whenever i try to do anything on TWRP. Any ideas on how i can fix this? Turns out the original path from the folder is still there and there's no way to delete it with any app
Delete it using the built in explorer in TWRP recovery.
Sent from my Moto X

Boot Animation issue in 6.0.1

I've updated my device today to 6.0.1 and rooted, however I can't seem to change the boot animation (yes, I have searched for answers and tried quite a few fixes).
Root Explorer tells me I have renamed the old file and copied the new file, however once I leave the directory and go back the old file is still there.
I have used the file explorer in TWRP and managed to delete the stock boot animation, but get a FAILED message when I try to copy the new file.
I used the terminal in TWRP and tried to copy the file manually, and receive a "No space left on device" message.
I've also tried mounting the /system as rw in adb. I can delete the bootanimation.zip file from there, and df -h shows 3mb free. Shouldn't the system partition have more space available than that?
Am I missing something, or has something changed with the new android versions?
Google has filled the system partition up to the brim. Also you can't remount system as rw while Android is running.
But the direction is right, go to TWRP, mount system, delete the old bootanimation. If the new one is not that much bigger then you could just copy it there, set permissions to rw-r--r--. But if the new animation is significantly bigger, you'll have to delete some bloatware first.
Thanks for that. The odd thing is, when I run DF in the terminal, it shows I have 20mb free. The boot animation file I am trying to copy is 6mb.
I'll keep poking around. If it doesn't work, it doesn't. It's not hugely important

Categories

Resources