I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
keeganjk said:
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
Click to expand...
Click to collapse
I wiped my device and reinstalled FreedomOS, once I restore all my settings, folders, etc. I'm going to see if it works.
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
I just wiped and reinstalled OxygenOS http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.10/. Once I reconfigure all my settings, files, etc, I'm going to see if it works.
I got it working by installing the official recovery, official OOS Image, and then flashed the Bluspark TWRP. It worked a few days ago, but now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
keeganjk said:
I got it working by installing the official recovery, official OOS Image, and then flashed the Bluspark TWRP. It worked a few days ago, but now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
Click to expand...
Click to collapse
There seems to be a bug I guess it unmounts data storage while backing it up. I've had this issue specially when the backup was pretty huge and was stored on external sd so I guess it's similar to it have you tried google it?
And even better copy a log after you got the message so we can see what cause it
Sent from my FRD-L09 using Tapatalk
keeganjk said:
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
Click to expand...
Click to collapse
I have the same error only if theme for twrp is present. S7edge twrp 3.1 nougat
LastStandingDroid said:
There seems to be a bug I guess it unmounts data storage while backing it up. I've had this issue specially when the backup was pretty huge and was stored on external sd so I guess it's similar to it have you tried google it?
And even better copy a log after you got the message so we can see what cause it
Click to expand...
Click to collapse
I don't have a log, I just got it working again (for now). I restored an earlier backup and now backups are not having errors. I think it had something to do with a substratum theme.
totoascend88 said:
I have the same error only if theme for twrp is present. S7edge twrp 3.1 nougat
Click to expand...
Click to collapse
Hmmm... I've been wanting to theme TWRP bit couldn't find out how. I've fixed the problem for now, I restored from an earlier backup. I think it had something to do with a substratum theme.
keeganjk said:
Hmmm... I've been wanting to theme TWRP bit couldn't find out how. I've fixed the problem for now, I restored from an earlier backup. I think it had something to do with a substratum theme.
Click to expand...
Click to collapse
It can be so. Next time try get a log so it can be fixed by twrp theme
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
It can be so. Next time try get a log so it can be fixed by twrp theme
Click to expand...
Click to collapse
Ok
LastStandingDroid said:
It can be so. Next time try get a log so it can be fixed by twrp theme
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
It started happening again... I don't know why, I restored from a backup and all I did after before trying to backup again was install a couple of apps...
Here is the "important part"of the log:
Code:
Backing up Data (excl. storage)
Backups of Data do not include any files in internal storage such as pictures of downloads.
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
It then goes into read-only mode; I can't delete backups or anything in the terminal until I reboot into recovery...
LastStandingDroid said:
It can be so. Next time try get a log so it can be fixed by twrp theme
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
I fixed it by booting into TWRP and running:
Code:
rm -rf /data/local/nhsystem
.
nhsystem is from Kali Nethunter, something I believe needs to be removed and reinstalled after a restore
keeganjk said:
I fixed it by booting into TWRP and running:
Code:
rm -rf /data/local/nhsystem
.
nhsystem is from Kali Nethunter, something I believe needs to be removed and reinstalled after a restore
Click to expand...
Click to collapse
hello, can you explain how you run twrp :
Code:
rm -rf /data/local/nhsystem
.
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.
keeganjk said:
I fixed it by booting into TWRP and running:
Code:
rm -rf /data/local/nhsystem
.
nhsystem is from Kali Nethunter, something I believe needs to be removed and reinstalled after a restore
Click to expand...
Click to collapse
I have the same issue, funnily it only breaks after installing kali-linux-full in the chroot.
Anybody any ideas what could cause it within the nhsystem folder??
Related
READ AT THE END OF THIS POST FOR THE SOLUTION
I accidentally used Titanium Backup's widget to frost all system and user apps, leaving mi phone in a infinite boot animation loop. I dont have aNandroid Backup and I would really love to solve this issue without flashing.
I found at Titanium Backup's troubleshooting webpage that I could use this command with adb to solve my issue:
Code:
Type the following command (replace with /dbdata/system/packages.xml if you have a Samsung phone):
busybox sed -n 's/<package name="\([^"]\+\)".*enabled="false".*/\1/p' /data/system/packages.xml | while read PKG; do pm enable "$PKG"; done
but it just says: No such file or directory (yes, I changed /data to /dbdata as stated in the webpage)
Any idea on how to solve this issue?
Thank you!
**EDIT:
This is the way I managed to get my phone working again without having to flash or wipe:
1. Boot in recovery mode and used adb pull command to extract "packages.xml" and "packages-more-backup.xml" from /data/system/
2. Open both files with Wordpad and replaced all protection="2" or "3" lines to protection="1".
3. Also, and very important, replaced all enabled="false" lines to enabled="true"
4. Boot in recovery again and used adb to delete old "packages.xml" and "packages-more-backup.xml" files and push the new ones.
5. Reboot and Voila!
6. Boot once again in recovery mode and fix permissions to avoid any problem.
Hope that this could be usefull to someone else having this horrible problem.
Thank you all!
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
nitox.n2o said:
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
Click to expand...
Click to collapse
I tried with /data too but same result.
shadow65781 said:
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I know I could do that but I would really like to restore my system as it was
Help please
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Simba501 said:
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
Click to expand...
Click to collapse
Pretty sure that's not gonna work because the frozen apps settings are at packages.xml file, but I can't access it I don't know why
jhermit said:
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Click to expand...
Click to collapse
I tried doing that right now but it didn't worked
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
shokuchi said:
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
Click to expand...
Click to collapse
Wrong forum dude
Sent from my Zanpakuto using Getsuga Tensho!
<deleted>
ZIP for unfreezing apps
For those, who accidentally frozen important system app: here quick solution without factory reset, reflashing and ADB
It automatically edits files as described in first post.
You should have unlocked bootloader. If no, ZIP useless because unlocking wipes all data.
Download both ZIP's and just flash them via custom recovery (TWRP / CWM)
If first throws error try second and vice versa. 2nd with mark "New" contains newer updater-binary that must be compatible with recent TWRP.
Then all apps will be unfrozen, so phone will boot.
Fix compatible with all Android versions.
Note: also you can somehow (ADB or filemanager in TWRP) delete file /data/system/0/package-restrictions.xml
More correct to edit that file which ZIP actually do, but deleting not harmful too.
tags: unfroze apps, auto-unfroze, defrost apps, unfreeze apps, 5596
Bonoboo said:
For those, who accidentally frozen system app there is quicker solution without factory reset and ADB.
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen.
Compatible with all Android versions.
Click to expand...
Click to collapse
THANKS MAN!! i just signed up to say thanks! you just saved my life :highfive:
Bonoboo said:
For those, who accidentally frozen system app here quicker solution without factory reset and ADB
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen, so phone will boot.
Compatible with all Android versions.
tags: unfroze apps, auto-unfroze
Click to expand...
Click to collapse
Thanks very much for the zip. It worked great
Same Problem
Does anyone have an updated version of that zip? I also froze an app linked to the device and it won't boot, even after factory resetting it. Tried running the zip on my t-mobile GS4 (probably newer than that zip) from the SD card in recovery mode, however it didn't unfreeze it.
Any help greatly appreciated!
pianoplayer55 said:
Does anyone have an updated version of that zip?
I also froze an app linked to the device and it won't boot, even after factory resetting it.
Click to expand...
Click to collapse
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Bonoboo said:
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Click to expand...
Click to collapse
Yup, unfortunately I did select wipe data on the recovery screen. I am also stuck in an infinite boot up loop and cannot access the phone to install any apps. How can I use a custom recovery to run the zip file if i cannot access the phone? Instructions much appreciated. Thanks again.
pianoplayer55 said:
How can I use a custom recovery to run the zip file if i cannot access the phone?
Click to expand...
Click to collapse
ZIP – it's not app.
Again, you need to install custom recovery.
Here link to TWRP and how install it via Odin on PC.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Bonoboo said:
ZIP – it's not app.
Again, you need to install custom recovery.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Click to expand...
Click to collapse
Downloaded TWRP with Odin and ran custom recovery without a change after the zip (this must have been a deeper-rooted problem in the OS itself), however in the meantime I formatted the system partition, removing the operating system. Installed Kies and ran the update. It reinstalled the OS and I'm good now. Most stuff was backed up anyways. Thanks guys for your time :good::good:
Which apk is the culprit?
Man, I wish I'd found this thread before restoring my phones internal ROM. Had it rooted and set up in every way I like except removing bloatware.
Using TB, I froze a system apk that shut down my System UI and sent the phone bootlooping. What I'm trying to determine is WHICH apk(s) I froze that caused this. I thought I had researched each one that didn't seem obvious, but I musta missed one or one of the 'obvious' ones wasn't so obvious.
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
Hi all,
since I use Temasek's UNOFFICIAL CM11 my device has various reboots and I do not know why. This occurs since the first V3 I used up to current V20. With my old CM10.1 I nearly hat the same configuration and apps and did not have such reboots.
Because I do not know the real source of the problem (CM11, Boeffla-Kernel, Xposed/Xprivacy, ???) maybe someone can help me finding out the root cause of my problems? Or whom I shall address it to!?
Attached you will find some logcat syslogs of some device reboots including backtraces ecc. (I just stripped some private data). If you need more or with different settings, let me know!
I am not very keen on analyzing those logs, so I'd appreciate your help.
Tnx in advance,
Enkidu
Did you start from scratch already? Factory reset + /system format + fsck on /data + Rom re-installation?
There are several 'Could not write' and 'Too many open files' errors. They look suspicious. If they don't go away after clean reinstallation you might be affected by a low level NAND/eMMC bug.
enkidu70 said:
Because I do not know the real source of the problem (CM11, Boeffla-Kernel, Xposed/Xprivacy, ???) maybe someone can help me finding out the root cause of my problems?
Click to expand...
Click to collapse
Sure, here is how I analyse errors. I think it's called "divide and conquer". If the root cause of an issue in a complex system isn't obvious, try to exclude possible causes. Either start with a few modifications as possible (i.e. only CM11, their kernel, no flashed modifications, uninstall Xposed) or take one modification away at a time (e.g. keep CM11 and the kernel, but disable the Xposed modules one after another, then uninstall Xposed, etc.) Every modification you take away while the error keeps showing up can be excluded as possible cause. With this, you should be able to narrow down which modification makes the error show up. To be sure, try again without the modification for some time and then with only this modification. Once you are sure, check if you can narrow it down even further, e.g. by reverting to default settings.
Both logs show that there are "Too many open files", but that doesn't come out of nowhere. It's probably a symptom as well, but might help to find the root cause once you have narrowed it down to the modification (or to the ROM itself).
enkidu70 said:
(CM11, Boeffla-Kernel, Xposed/Xprivacy, ???)
Click to expand...
Click to collapse
I'm on the same setup (but Temasek kernel) with Xposed/XPrivacy and it runs stable. Maybe try another kernel.
DualJoe said:
Did you start from scratch already? Factory reset + /system format + fsck on /data + Rom re-installation?
Click to expand...
Click to collapse
Yes and no. I started from scratch with CM11. And I have these reboots since the beginning.
I frequently do nandroid backups and restores, so filesystems should be ok...
DualJoe said:
There are several 'Could not write' and 'Too many open files' errors. They look suspicious.
Click to expand...
Click to collapse
In my opinion this is part of the problem. For me it seems that something is opening too many files and after a while system is out of free filehandels and has to reboot... But I am not sure.
rovo89 said:
Sure, here is how I analyse errors. ... Once you are sure, check if you can narrow it down even further, e.g. by reverting to default settings.
Click to expand...
Click to collapse
Tnx. I already wanted to do something similar. Today I installed a kind of permanent logcat via init.d writing all to my internal sd so that I can see if it reboots. (Soft reboots are so fast and I did may have missed some of them.)
rovo89 said:
Both logs show that there are "Too many open files", but that doesn't come out of nowhere. It's probably a symptom as well, but might help to find the root cause once you have narrowed it down to the modification (or to the ROM itself).
Click to expand...
Click to collapse
I still hope someone just tells me "ah take a look at ... that's it!" So that I need not to track it down by degrading all my security settngs.
Tnx for your replies!
Enkidu
enkidu70 said:
I still hope someone just tells me "ah take a look at ... that's it!" So that I need not to track it down by degrading all my security settngs.
Click to expand...
Click to collapse
I doubt you can degrade yourself into such state - at least not with any high level stuff. Your problems are below DalvikVM. I would rather accuse the kernel or even lower the eMMC itself. That's why i recommended to take a backup and reinstall from scratch (with Temasek or stock kernel) to make sure the hardware is ok.
- Check dmesg output (cat /proc/kmesg).
- Filesystem integrity errors cannot be fixed by restoring backups since /data won't be formatted by this (due to internal sdcard). I still point to fsck from recovery.
- dd create an image in Android (busybox dd if=/dev/urandom of=/data/test.bin bs=1M count=1000; sync) and watch if errors occur. If they do try the same in recovery.
But my first pick is still kernel issue...
DualJoe said:
I still point to fsck from recovery.
Click to expand...
Click to collapse
How can I do a fsck from recovery? I use CWM 6.0.4.4 but I can not connect with adb:
$ adb shell
error: insufficient permissions for device
DualJoe said:
- Check dmesg output (cat /proc/kmesg).
Click to expand...
Click to collapse
What shall I look for??? There is lot of output...
DualJoe said:
- dd create an image in Android (busybox dd if=/dev/urandom of=/data/test.bin bs=1M count=1000; sync) and watch if errors occur. If they do try the same in recovery.
Click to expand...
Click to collapse
Tnx, I will do so.
Anyway. When I do a full backup of my int. sd, format /data, restore a nandroid backup and restore my backup of int. sd, this would ensure that /data is ok?
Enkidu
I don't know current CWM versions but maybe try 'adb root' first.
Also make sure it's SELinux aware (CM11 compatible). Maybe this is even the culprit that its somehow mixed up or something due to older backups (in case your using incremental backups) and SELinux permissions are corrupt. I prefer TWRP these days because it uses standard tar format.
Regarding dmesg.. I don't know. Maybe pipe in a file and search for 'error' or something.
Doing a backup/format/restore should recreate the filesystem, yes. It doesn't help though if SELinux permissions of the backup are messed up. I have no clue how to check that though. If in doubt you can start from scratch and inject the data manually (after manually unpacking the backup). This might be not so easy on incremental updates though.
DualJoe said:
I don't know current CWM versions but maybe try 'adb root' first.
Click to expand...
Click to collapse
(Un)fortunately this did not change anything. BUT now I switched to TWRP Recovery 2.6 and this seems to work perfect! adb shell works as expected. And it looks and seems to be much better than CWM! (I was on CWM since ages and didn't look for alternatives... )
DualJoe said:
Regarding dmesg.. I don't know. Maybe pipe in a file and search for 'error' or something.
Click to expand...
Click to collapse
I will include it in my "syslog" script that collects all logs. (I installed it to init.de and initiate a logcat to write it to my internal sd...)
DualJoe said:
It doesn't help though if SELinux permissions of the backup are messed up.
Click to expand...
Click to collapse
Well, when I find time I will install it from scratch and restore my apps by using Titanium...
Tnx for you support.
Cheers,
Enkidu
DualJoe said:
- Filesystem integrity errors cannot be fixed by restoring backups since /data won't be formatted by this (due to internal sdcard). I still point to fsck from recovery.
Click to expand...
Click to collapse
Well... Now I installed TWRP 2.6.3.1 (latest available) but I have more issues:
Where do I find fsck? Trying 'fsck' just results in file not found.
When I try to install e.g. pa_gapps my phone does not boot anymore. It just shows Temasek's logo forever... What can I do?
Tnx in advance,
Enkidu
1. Look in /sbin or use 'ls /sbin |grep fsck'. Should be 'fsck.ext4' 'e2fsck'.
Be sure to have /data unmounted and do '/sbin/e2fsck -fy /dev/block/mmcblk0p12'. Optionally you can do an 'echo $?' afterwards to get the exit code. You can look up corresponding codes here.
(Its a pain but it's even possible to do that in TWRPs built-in terminal.)
2. Use Banks Gapps (see Temasek 1st post). Mount /system, go to /system/addon.d and delete all scripts there (rm /system/addon.d/*.*). Then (re-)install/update Temaseks rom first (will delete old gapps) and Banks Gapps afterwards.
The addon.d scripts are called when you update/install roms. They would save/backup the old gapps if not deleted beforehand. (Only) this time we don't want that so we delete them.
DualJoe said:
2. Use Banks Gapps
Click to expand...
Click to collapse
*Pooohhh* pa_gapps were just nice because there is just ONE package with all in it! Now I have to download and install a bunch of files...
Also it seems that there are not all gapps included? (pa_gapps is arounf 270MB or so. BaNkS just around 100MB!?)
Ok, I will give this a try because TWRP is much better...
What a never ending story this time...
Tnx,
Enkidu
I have no clue if pa-gapps are still valid for cm11.
There should be a full package for banks as well.. The smaller ones are just optional if i remember correctly.
DualJoe said:
I have no clue if pa-gapps are still valid for cm11.
Click to expand...
Click to collapse
Yes, they are. See http://forum.xda-developers.com/showthread.php?t=2397942
Currently I am back to TWRP but I have some problems... Let's see if I can fix'em...
Well... The more I try the worser it becomes...
TWRP installed, all filesystems checked (only problems on fat32 extSD, nothing really important), /data is formatted, other gapps, permissions fixed, ...
So it is better to do a full wipe... Damned, I hate that.
Tnx for all your help. I learned a lot!
Cheers,
Enkidu
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
I have the same problem. Initially, I thought that the sdcards were not mounted (for su root) but that wasn't the issue.
TB will currently backup VIRTUAL items (e.g. Accounts, WiFi access points) which have the TB logo next to it. It seems to fail for all other items.
gale2000 said:
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
Click to expand...
Click to collapse
Same problem here. According to this post:
http://forum.xda-developers.com/showthread.php?t=2391363&page=7
the small app called sdfix could solve the problem. I haven't tried yet.
cr2069 said:
Same problem here. According to this post: http://forum.xda-developers.com/showthread.php?t=2391363&page=7 the small app called sdfix could solve the problem. I haven't tried yet.
Click to expand...
Click to collapse
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Anybody have luck with Helium?
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
iammudd said:
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Click to expand...
Click to collapse
Too bad, seems to be TB's problem. Waiting for any progress...The main reason I want rooting is to use TB, but it's not working...
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/ascend-mate2/orig-development/2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
iammudd said:
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
Click to expand...
Click to collapse
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
foltz61 said:
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Yes, fastboot boot TWRP_MT2-L03_RECOVERY.img allowed me to try it out first. If it had failed, then hopefully I would still have had the stock recovery. (After playing around with TWRP a bit, I DID eventually flash it.)
foltz61 said:
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
iammudd said:
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
Click to expand...
Click to collapse
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
Click to expand...
Click to collapse
Same problem and this also fixed it for me thanks
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
Click to expand...
Click to collapse
This workaround has been made obsolete. See next post:
I didn't know what the drawbacks are to using this folder so I was initially reluctant but I've given up and went down this path as well. However, I've reduced some permissions and here's what appears to be working for me:
Use ES Explorer to create the new folder and change its permissions to rwx for group and others. (I didn't need to change owners for any of the folders.)
Use ES Explorer to TEMPORARILY add read-only permission to /data for OTHERS.
Change TiBu backup folder location by manually navigating to the new folder.
Once the new folder has been selected, I restore /data to its original permissions. (The read permission was only needed temporarily for TiBu to find the new folder.)
Copying the files back to my PC, I can see that the zip files for the apks appear to have "reasonable" apk sizes (i.e. not zero-length as before).
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
kemonine96 said:
In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Click to expand...
Click to collapse
Thanks, this appears to have done the trick. It was very baffling when TiBu would work for some tasks but not others. Glad you stumbled onto this thread.
And another follow up for those using Helium or looking for an "adb backup" based solution
This device does not appear to include the full adb backup stack. From some limited testing tonight the pop-up prompt when running "adb backup' or using Helium Backup does not produce prompt on the device so it just fails. This is a known problem on some devices and it's too bad Huawei decided this wasn't a necessary inclusion.
kemonine96 said:
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
Click to expand...
Click to collapse
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
nrfitchett4 said:
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
Click to expand...
Click to collapse
Were you able to get adb backup to work at all? I never was able to get it to work.
I solved my titanium backup issues by going into SuperSU, then settings for SuperSU, and unchecked the mount namespace seperation box, then reboot
kemonine96 said:
Were you able to get adb backup to work at all? I never was able to get it to work.
Click to expand...
Click to collapse
It worked just fine for me. Used it to backup kids unrooted phones. That's been a couple years though.
hi, when i am trying to convert an user app to system app or vise versa this error pops up. anyone know what this error is and how to solve it. i am currently on xiomi.eu rom with twrp 3.1.1
[email protected]!$h said:
hi, when i am trying to convert an user app to system app or vise versa this error pops up. anyone know what this error is and how to solve it. i am currently on xiomi.eu rom with twrp 3.1.1
Click to expand...
Click to collapse
Try using another app like Titanium backup instead and see if its work.
GabrielScott said:
Try using another app like Titanium backup instead and see if its work.
Click to expand...
Click to collapse
if i use titanium backup then when i covert that app to system app 'please wait..' goes on and goes on.after waiting long time i closed titanium backup and rebooted. when i check that app it actually got converted into system app. but then when i try to delete this app or any other system app with titanium backup or link2sd both app shows uninstall was succesfull but actually app didnt get uninstalled. I think someyhing is restricting them to modify system.
Please give me any solution bro.
[email protected]!$h said:
if i use titanium backup then when i covert that app to system app 'please wait..' goes on and goes on.after waiting long time i closed titanium backup and rebooted. when i check that app it actually got converted into system app. but then when i try to delete this app or any other system app with titanium backup or link2sd both app shows uninstall was succesfull but actually app didnt get uninstalled. I think someyhing is restricting them to modify system.
Please give me any solution bro.
Click to expand...
Click to collapse
Then directly uninstall the app through the system using Root explorer (paid app) / mixplorer
Or you can use ADB method
Code:
adb shell
cd system/app
ls
(Search the app package then)
rm example.apk
Source:
https://blog-archive.josephcs.com/removing-system-stock-apps-android/#main_content
Dont forget to reboot afterwards
GabrielScott said:
Then directly uninstall the app through the system using Root explorer (paid app) / mixplorer
Or you can use ADB method
Code:
adb shell
cd system/app
ls
(Search the app package then)
rm example.apk
Source:
https://blog-archive.josephcs.com/removing-system-stock-apps-android/#main_content
Dont forget to reboot afterwards
Click to expand...
Click to collapse
thats ok. but why is this error showing up.
[email protected]!$h said:
thats ok. but why is this error showing up.
Click to expand...
Click to collapse
Im not sure.
I came to that problem before in SLIMrom
I think it is something to do with mounting the /system at root. But problem persist so i changed ROM.
I tried running this command in terminal
1) Open terminal
2) Type "su" (enter)
3) Type "mount -o remount,rw /system" (enter)
Maybe it will work for you
GabrielScott said:
Im not sure.
I came to that problem before in SLIMrom
I think it is something to do with mounting the /system at root. But problem persist so i changed ROM.
I tried running this command in terminal
1) Open terminal
2) Type "su" (enter)
3) Type "mount -o remount,rw /system" (enter)
Maybe it will work for you
Click to expand...
Click to collapse
when i type that command in terminal the exact same error is given as response in terminal. here you are saying you also got that error(atleast i am not the only one) and changing rom fixed that error as i also tried reinstalling official miui rom in place of my current xiaomi.eu rom but in that rom too i am getting same error.
Does it have something to with twrp. because in 'mount' in twrp 'system' is always unmounted, even if i mount the system it again gets unmounted.
And many many thanks for your reply. please give me another suggestion bro.
[email protected]!$h said:
when i type that command in terminal the exact same error is given as response in terminal. here you are saying you also got that error(atleast i am not the only one) and changing rom fixed that error as i also tried reinstalling official miui rom in place of my current xiaomi.eu rom but in that rom too i am getting same error.
Does it have something to with twrp. because in 'mount' in twrp 'system' is always unmounted, even if i mount the system it again gets unmounted.
And many many thanks for your reply. please give me another suggestion bro.
Click to expand...
Click to collapse
The way I'd fix the error is to wipe the /system , after that, i made a decision to change ROM.
So yet again, i did a clean flash.
About the mounting problem, you probably got into that situation due to the fact that is something wrong with the system permission hence you got that error.
If you decided to go with the official MIUI, make sure to wipe everything (except internal/external) before flashing the ROM.
GabrielScott said:
The way I'd fix the error is to wipe the /system , after that, i made a decision to change ROM.
So yet again, i did a clean flash.
About the mounting problem, you probably got into that situation due to the fact that is something wrong with the system permission hence you got that error.
If you decided to go with the official MIUI, make sure to wipe everything (except internal/external) before flashing the ROM.
Click to expand...
Click to collapse
according to what you did i also tried changing rom(to ressurection remix) and problem actually got solved. but i dont want to migrate from miui. isn't there any other way.