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.
Related
So, it seems that everything I have tried after s-OFF, installing perm-root, etc has gained root access without issue, except Titanium Backups.
it's the only thing that says it can't obtain root. just wondering if anyone else noticed this, have fixed it. etc.
UPDATE: answered by WillJitsu
I fixed it. Here's what I had to do:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/showthread.php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
I'm having the same problem. Tried everything I can think of, but no luck.
Install BusyBox
HSadler93 said:
Install BusyBox
Click to expand...
Click to collapse
I have BusyBox 1.18.4 installed in /system/xbin/
HSadler93 said:
Install BusyBox
Click to expand...
Click to collapse
Nope, Titanium backups will tell you if Busybox is installed or not and give you that option.
it doesn't even get the the point of seeing if busybox is installed or not. flat out says "NO ROOT" and that's that.
I have busybox installed.
felacio said:
Nope, Titanium backups will tell you if Busybox is installed or not and give you that option.
it doesn't even get the the point of seeing if busybox is installed or not. flat out says "NO ROOT" and that's that.
I have busybox installed.
Click to expand...
Click to collapse
I'm not trying to be a ****, but you do have Superuser installed right?
Yes. All of our other root apps work just fine. I'm blocking ads, Root Explorer works, etc. Titanium Backup is the only app that doesn't recognize root.
HSadler93 said:
Install BusyBox
Click to expand...
Click to collapse
Like WillJitsu, I also have Busybox installed in /system/xbin, and terminal can access root, and busybox functions, however TitBack says it doesn't have root.
mine works fine weird
The only thing I can think of is that one of the temp root methods I used in the past has messed something up, but I have no idea what to do to remove all remnants of that.
WillJitsu said:
The only thing I can think of is that one of the temp root methods I used in the past has messed something up, but I have no idea what to do to remove all remnants of that.
Click to expand...
Click to collapse
I would probably just wait till reliable roms release and perform a factory data reset =(
EDIT: I should probably add that I'm running 1.11 and never did any of the temp-root methods and mine is working fine after installing the latest version of SU/BusyBox
i have Superuser installed but TB wont work says no root :/
Did you upgrade the su binaries with the ones listed on the revolutionary site? I was having the same problem till I i flashed that.
I fixed it. Here's what I had to do:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/showthread.php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
WillJitsu said:
I fixed it. Here's what I had to do:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/showthread.php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
Click to expand...
Click to collapse
Worked great. Thanks for tracking down the missing link.
Compusmurf said:
Worked great. Thanks for tracking down the missing link.
Click to expand...
Click to collapse
Sure thing. Glad I could help.
See PM.
WillJitsu said:
I fixed it. Here's what I had to do:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/showthread.php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
Click to expand...
Click to collapse
worked perfect !!
I can't use titanium backup anymore, everytime i run the app i get this:
Code:
Error
Sorry, I could not acquire root privileges. This application will *NOT* work!
Please verify that your ROM is rooted and includes Busybox, and try again
This attempt was made using the "/system/xbin/su" command
I'im running HWMOD's rooted firmware, with superuser "installed and updated", and also busybox "installed and updated". there's nothing wrong, but somehow i can't run titanium backup anymore somehow.
what can be the problem be please, i've googled it and i got no solutions whatsoever!
run the app root checker.
Also from someone who has been there, i dont think titanium works with our unit. Our unit has sd1 and sd2 and sd3. Titanium will backup to sd1, which is internal memory, you can see where this is going. I did a titanium backup, then full wipe, and lost everything because it was not backed up onto sd2...
nightanole said:
run the app root checker.
Also from someone who has been there, i dont think titanium works with our unit. Our unit has sd1 and sd2 and sd3. Titanium will backup to sd1, which is internal memory, you can see where this is going. I did a titanium backup, then full wipe, and lost everything because it was not backed up onto sd2...
Click to expand...
Click to collapse
I don't have to run ROOT CHECKER because i have already other root apps and they function flawlessly (SD maid, quick boot, Busybox installer...) but i run the ROOT CHECKER anyway and it says i do have root privileges.
i forgot to mention that i already used Titanium B to backup apps and data, everything was stored on the external sd card. i could also restore. after all this app is for all android devices.
hamdimo said:
I can't use titanium backup anymore, everytime i run the app i get this:
Code:
Error
Sorry, I could not acquire root privileges. This application will *NOT* work!
Please verify that your ROM is rooted and includes Busybox, and try again
This attempt was made using the "/system/xbin/su" command
I'im running HWMOD's rooted firmware, with superuser "installed and updated", and also busybox "installed and updated". there's nothing wrong, but somehow i can't run titanium backup anymore somehow.
what can be the problem be please, i've googled it and i got no solutions whatsoever!
Click to expand...
Click to collapse
Hi
Also running HWMOD's rooted firmware and Titanium Backup works perfectly well or me. I also have an
Advent Vega and I was able to transfer my SD card from it to the Media pad and restore apps from my Titanium
Backup on it to the Media pad.
Stransky
Sent from my VegaCream RC2 using xda premium
Stransky said:
Hi
Also running HWMOD's rooted firmware and Titanium Backup works perfectly well or me. I also have an
Advent Vega and I was able to transfer my SD card from it to the Media pad and restore apps from my Titanium
Backup on it to the Media pad.
Stransky
Sent from my VegaCream RC2 using xda premium
Click to expand...
Click to collapse
that's what makes the app perfect, BACKUP and RESTORE between different android devices.
have you updated superuser? this seems to have been the cause. Titanium Backup was working fine before I updated superuser and error message is the same as yours. currently i'm using MyBackups.
you can check HWMOD's thread for details as somone also has him about this already.
{SOLVED}
ferdz33 said:
have you updated superuser? this seems to have been the cause. Titanium Backup was working fine before I updated superuser and error message is the same as yours. currently i'm using MyBackups.
you can check HWMOD's thread for details as somone also has him about this already.
Click to expand...
Click to collapse
I solved it, the problem is that titaniumbackup is using the "/system/bin/su" command but the SU binaries are actualy installed in "/system/xbin/"
what i did is going to BUSYBOX and from there switching the install location to "/system/xbin/"
i tried "mybackups" but i prefer TB
hamdimo said:
I solved it, the problem is that titaniumbackup is using the "/system/bin/su" command but the SU binaried are actualy installed in "/system/xbin/"
what i did is going to BUSYBOX and from there switching the install location to "/system/xbin/"
i tried "mybackups" but i prefer TB
Click to expand...
Click to collapse
thanks hamdimo! will try your solution when I get home later.
btw, HWMOD just released HWMOD kernel 3.0.42 + custom updates and this issue was also addressed.
ferdz33 said:
thanks hamdimo! will try your solution when I get home later.
btw, HWMOD just released HWMOD kernel 3.0.42 + custom updates and this issue was also addressed.
Click to expand...
Click to collapse
I fear that my hack could led to believe that searching for the "su" binary only in predefined positions is a good thing ...
I still believe applications should gather the correct informations from the PATH environment variable, as good ol' *NIX does.
But as you said it's kind of addressed, let's hope the hack will have a story
These problems arise only if one updates the "Superuser" application past the 3.0.7 (with "su" binary 3.0.3.2).
That one version is the latest one working as expected.
And yes I am a bit sceptical about my own choice of including 3.1.3 instead of the 3.0.7 in my latest update.
The "su" binary executable alone has grown from a mere 22Kb to 380Kb and "apk" has doubled it's size too (1.5Mb).
Related to these changes in "Superuser" several applications does not work any more for many users and upgrades are needed.
The process of getting "root" privileges for any application has turned tremendously slow. From almost immediate to 2/3 secs. each time.
this solution worked for me
Since superuser is working and granting root permissions to other apps (except TB). Using root explorer, I tried renaming the original su file from /system/bin/su and replacing it (copy-paste) with the su file from /system/xbin
Reloaded TB and it worked =)
Actually i have no problem in my 1st install for titanium backup. but soe how i uninstall accidentally. when i reinstall, it prompt memory not enough but i hve abt 3.5 gb left. my fone is rooted S3. can anybody help. tks in advanced...
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
Evening!
I recently bought Z2. Its ROOTED. SuperSU and BusyBox are successfully installed. For some reason I uninstalled some of my System Apps which I never used. All these apps are backup'ed by Titanium Backup before uninstalling them.
But when I tried to restored it from Titanium Backup it gave me the notification error – “Batch restore Finished (1 element failed).
I also used Root Explorer and Total Commander to mount my Internal Card with r/w and was Successful. But when trying to change permission to the above i.e. system/app and fix permission to rw -r -r, it gives me error pop up stating – “Permissions change was not successful. Please note that some file systems (e.g. SD card) do not allow permission changes.”
Then I thought of using System Apps Installer to install those missing apps but it also gave me this note at the end – “Cannot mount system partition as Read/Write”.
Can somebody please guide me how can I restore those System Apps using Titanium Backup or install them as NON OF THE APPS ARE ABLE TO WRITE TO SYSTEM FILES though my Cell is ROOTED.
Your kind cooperation in this matter is highly solicited.
Thanks a lot.
Arvind
I believe you need to disable ric. Try installing XZDUALRECOVERY and see whether that works.
Sent from my SGP311 using XDA Free mobile app
guhvanoh said:
I believe you need to disable ric. Try installing XZDUALRECOVERY and see whether that works.
Sent from my SGP311 using XDA Free mobile app
Click to expand...
Click to collapse
How to disable 'ric'??
Moreover I haven't installed any recovery yet. But will try to install XZDualRecovery today. But is there any way to come out of my issue without installing any recovery brother??
Thanks!
Anyways I successfully installed XZDualRecovery on my Z2 and its working fine [Thanks to NUT, DooMLoRD n other developers ].
Though Link2SD and Titanium Backup are able to convert any of my User Apps to System Apps without any problem but while restoring System Apps with Titanium Backup it's unsuccessful. The same goes when trying to integrate updates to System i.e. unsuccessful. But User Apps are successfully been restored by TB.
Please help me what am I doing wrong or what must be wrong in my TB settings.
This is driving me crazy.
Also Xposed Framework too is installed [long back] and running flawlessly.
Bump
I know this problem of mine must be really small but am still unable to trace why am I facing this situation.
Any help from senior members will be highly solicited.
Regards.
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.