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.
Related
I take it that it's not a good thing to remove your SD card when you're running A2SD. I wanted to see if my apps were "really" running on the card, so I figured I'd just pop it out, see if the apps worked or not, then pop it back in. Well, the apps didn't work, but after re-inserting the card, I don't see any of the apps I had installed.
Anyone know how to fix this?
Reboot it?
snooginsguy said:
Reboot it?
Click to expand...
Click to collapse
I did that about 5 times.
I also tried reflashing the PlainJaneT2 ROM I have on the SD card, but oddly enough that didn't fix it either...probably because I didn't do a factory reset prior to doing it. I don't want to lose all my data and downloaded apps...
If you have Titanium Backup and have done a recent backup, it might work to restore the links to your SD apps, not sure though...
BTW sorry for the obvious first response, but you never know what people have/haven't tried.
Well, I just flashed the PlainJaneT2 ROM to my phone last night, so I didn't get around to making a backup. I'm just not sure if there's a way to restore the links without doing a factory reset and starting over.
lostpilot28 said:
Well, I just flashed the PlainJaneT2 ROM to my phone last night, so I didn't get around to making a backup. I'm just not sure if there's a way to restore the links without doing a factory reset and starting over.
Click to expand...
Click to collapse
Try "a2sd install"
That commands makes sure everything is set for a2sd. see if that works.
Thanks, T2noob...do I need to run that from the command prompt with the phone connected via USB? I was surprised to see that almost every app on my phone was moved to the SD card! Right now I can still use it, but any app, including Market, is gone!
lostpilot28 said:
Thanks, T2noob...do I need to run that from the command prompt with the phone connected via USB? I was surprised to see that almost every app on my phone was moved to the SD card! Right now I can still use it, but any app, including Market, is gone!
Click to expand...
Click to collapse
You can either run it from the adb with this
Code:
adb shell a2sd install
or you can run it from a terminal emulator from the phone with this
Code:
su
a2sd install
and about the market being gone reboot your phone and it should come back.
That market issue may not if he can't get to his ext partition.
That was an issue when I had zipalign running at boot. You have a market app that is located in /system/app (this is where it should be). When market updates, it puts an updated copy of itself in /data/app (which is on his ext partition). The icon is pointed to that app.
I didn't remove the market app fix program (though I did remove the command to get there).
If you still can't get market back, try the following:
1. Remount your phone (adb remount)
2. Go into the adb shell
3. Type /system/xbin/busybox cp -fp /data/a2sd/Vending.apk /system/app
4. Type /system/xbin/busybox rm -f /data/data/com.android.vending/cache/*
5. I'm not sure, but you may just want to reboot the phone.
This should bring back your market.
t2noob said:
You can either run it from the adb with this
Code:
adb shell a2sd install
or you can run it from a terminal emulator from the phone with this
Code:
su
a2sd install
and about the market being gone reboot your phone and it should come back.
Click to expand...
Click to collapse
I am running WW 4.6 right now and i did a titanium back up to try out one of the new Froyo ROMs. I didnt like it so i tried to nandroid restore back to WW and that wouldnt even work.
So i reflashed WW and tried to reinstall my apps and it says "not enough memory" or something along those lines every time i try to reinstall an app.
So i partitioned my SD card and it STILL wont download anything..any ideas?
Edit: After some research this seems to be a Titanium back up issue and a simple uninstall/reinstall of the apps works. I have no apps installed on my phone and i cannot install anything...thats not good.
Also i have the adb shell open on the command prompt with all the listed app on my phone by doing
mount -o rw,remount /dev/block/mtdblock3 /system
cd /system/app
ls
...and there is nothing there that is installed, just all of the .apks that come with the ROM.
Installed a new ROM and working now, very strange.
WW requires you to partition your SD card for app2sd, that is why it's telling you that you do not have enough space. Get ROM Manager from the market and it will do this for you, then just flash WW back onto your phone.
http://androidforums.com/all-things...-manager-will-now-partition-your-sd-card.html
EDIT: I forgot to add that after you install WW you need to go into (Settings, Applications) and enable App2SD before you can install anything.
reinert012 said:
I am running WW 4.6 right now and i did a titanium back up to try out one of the new Froyo ROMs. I didnt like it so i tried to nandroid restore back to WW and that wouldnt even work.
So i reflashed WW and tried to reinstall my apps and it says "not enough memory" or something along those lines every time i try to reinstall an app.
So i partitioned my SD card and it STILL wont download anything..any ideas?
Edit: After some research this seems to be a Titanium back up issue and a simple uninstall/reinstall of the apps works. I have no apps installed on my phone and i cannot install anything...thats not good.
Also i have the adb shell open on the command prompt with all the listed app on my phone by doing
mount -o rw,remount /dev/block/mtdblock3 /system
cd /system/app
ls
...and there is nothing there that is installed, just all of the .apks that come with the ROM.
Click to expand...
Click to collapse
If you do a "chmod -R 777 /data/app" (without quotes) through ADB shell, that should enable you to install apps from the market onto internal memory.
ATTENTION: Cyanogenmod version 6.1.0 has A2EXT support built into the rom so an edited boot.img is no longer needed just flash the add-on to enable it and also you must do the commands to move dalvik-cache to the EXT partition as well...
Thank You for reading this if you actually took the time to!
Ok so i decided to post some things on here. Let me explain why I did things the way I did first of all. I decided to only edit the boot.img in each of the froyo roms that we all use and post those here along with a flashable .zip file that allows you to activate apps2ext on froyo roms. I did it this way to show respect to the developers of the roms by not stealing there downloads with my own. Doing it this way means that you have to download the actual rom from them which I hope makes things better for them.
You will need to already have an EXT partition setup already to be able to do this.
To any Dev if you do not like me doing this to your rom then by all means PM me and i will remove it ASAP.
To any downloader/user if there is a rom that you want me to include that isn't or a rom that isn't Froyo let me know and i will try to get that for you ASAP.
Credit for this goes to the Dev's of each rom and the darktremor a2sd method maker:
Cyanogen and teamdouche
Tkirton
Arayray
r0man
infinitybiff
migueltherocker
XDA of course!! :-D
Everyone that uses my edits
If i didn't mention you then PM me i will add you.
Now on to the Goods:
All of these are just boot.img from each rom. This is not an one for all boot.img type thing because each rom could have done something to the boot.img that may cause a bootloop if added to a different rom.
Rename each to boot.img and place into your rom.
After that you don't actually have to do any resigning since we all are using clockwork recovery just make sure its setup to allow flashing without signatures.
This only supports EXT2 or EXT3 which is pretty much all slide users have considering its nothing new.
Download the a2sd.zip and flash it at any time after you get your base rom flashed.
I will try to keep these updated to the latest versions if there is enough demand for them. Also i will try to keep the latest 3 nightlies up-to-date.
Boot.imgs:
Boot Images Here
A2sd Enabling package
Instructions:
OK as stated above these are only boot.img.
You need to rename each to just boot.img and place them inside the rom you like.
Make sure you wipe everything and do a fresh install it helps a lot to do everything fresh. (if your worried about apps use titanium backup or some other backup app)
Flash the a2sd add-on
Once the add-on has been flashed and there aren't any problems there are a few ways to enable actual a2ext.
You can either use adb or a terminal app on your phone.
If using adb phone can be turned on or in recover with system mounted.
once you pick a way here are the commands:
(if using a terminal app skip steps 1, 2, 5, 6)
1. ./adb remount (windows: adb remount)
2. ./adb shell (windows: adb shell)
Su will be needed for terminal app and may be needed for adb method(just do it in case its needed)
3. cd /system/bin/
4. sh a2sd reinstall
some things will popup and phone should reboot
5. once rebooted ./adb remount
6. ./adb shell
7. cd /system/bin/
8. sh a2sd cachesd
more things will popup and phone should reboot. The last reboot can take 5 minutes or longer especially if you already had apps downloaded. I know on a fresh install it can take what seems like ages.
saved just in case may use this for non froyo roms or requested roms
Through some experimenting i have found out that just including the boot images into the roms without flashing the add-on pack could cause your phone to stick at the boot screen so you should always flash the add-on
Teamfenix 1.7.1 for those people that use it because they need tether support
The best backup app i have found is mybackup pro and activate the root privileges. if you dont have paid apps or just dont wanna pay it there is a free version but it only lasts a certain amount of time. it restores all apps and data without causing market problems like i have experienced with titanium backup. either/or they are both good apps but everyone has a preference.
This is great man, thanks. You saved me the time and trouble of incorporating it myself.
Sent from my T-Mobile myTouch 3G Slide using XDA App
migueltherocker said:
This is great man, thanks. You saved me the time and trouble of incorporating it myself.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
lol thanks i just noticed a lot of people want it so i figured this way is easier although i could upload each individual rom with it already enabled and ready to run but i thought that might step on a few toes around here
great work! ill add a link to my post if you dont mind
arayray said:
great work! ill add a link to my post if you dont mind
Click to expand...
Click to collapse
thats ok with me
cool mod, gonna give ita shot!
SiL3nTKiLL said:
cool mod, gonna give ita shot!
Click to expand...
Click to collapse
let me know how it works out for you. also updated first post with the 2 9/26 nightlies and 2nd post with the teamfenix 1.7.1 boot image
just to be clear, we need to have the ext partition setup before trying this right? it won't make it for us?
I didn't think so... just wondering hahaha
Thanks guys!
you rock!
- faylix / local
Just wondering... what's the difference b/w app2ext and app2fat? It seems like app2ext is better since people tend to want it
And also, if we want to partition app2ext, we can just do so via rom manager, right?
daniel60104 said:
Just wondering... what's the difference b/w app2ext and app2fat? It seems like app2ext is better since people tend to want it
And also, if we want to partition app2ext, we can just do so via rom manager, right?
Click to expand...
Click to collapse
the benefits of a2ext are that you dont have to move each app as you install them. once its setup they are automatically installed to the ext partition. another thing is it doesn't matter what apps are on it they all show up without any problems unlike with the a2fat where if widgets or home apps are placed on it they disappear. also when rebooting your phone your home screen apps wont get that generic icon with a2ext like they can with a2fat. its a lot easier to partition the sdcard compared to the old android days when everything was manual so its a whole lot more appealing. plus even with a2fat your internal memory continued to decrease even if you placed them on the memory card. this is because only part of the app is moved over and also the dalvik cache for the app was left on internal. so you are still limited on how much you can download. with a2ext no internal memory is lost to apps or dalvik cache because everything is on the ext partition this would allow rom makers to add more to the data or system partitions with there rom so you can have other apps or more room for themed images that may take up more memory.
your other question yes rom manager should have the option to partition your sdcard. another option is to use gparted if you are running ubuntu there are also other programs that should work as well for other os.
on another note working on the latest nightly and will upload shortly
A question I have is that if we use the boot image for the newest Cyan nightly? What happens when we want to install a newer nightly? Do we have to patch that with the new Boot.img also?
acejoker25000 said:
once you pick a way here are the commands:
(if using a terminal app skip steps 1, 2, 5, 6)
1. ./adb remount (windows: adb remount)
2. ./adb shell (windows: adb shell)
Su will be needed for terminal app and may be needed for adb method(just do it in case its needed)
3. cd /system/bin/
4. sh a2sd reinstall
some things will popup and phone should reboot
5. once rebooted ./adb remount
6. ./adb shell
7. cd /system/bin/
8. sh a2sd cahcesd
more things will popup and phone should reboot. The last reboot can take 5 minutes or longer especially if you already had apps downloaded. I know on a fresh install it can take what seems like ages.
Click to expand...
Click to collapse
The last command (#8) should be
Code:
sh a2sd cachesd
you transposed a couple letters in cachesd.
Ok I had a 2.1 ROM with a2sd enabled and i had my ext2 partition working. I installed a 2.2 ROM and followed all directions properly. After the 2nd reboot I am not seeing my apps populate into the phone. They should still be on the ext2 partition no? Thoughts please?
If you wiped before flashing then your ext partition was wiped as well but you could try a fix permissions and see if that works
Sent from my T-Mobile myTouch 3G Slide using XDA App
acejoker25000 said:
If you wiped before flashing then your ext partition was wiped as well but you could try a fix permissions and see if that works
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Ah crap I did do a full wipe. Trying the fix permissions now. I do have a nandroid backup of my last ROM. If this doesnt work is there a way to put that ext2 contents onto the ext2 now?
Restore the rom and use titanium backup or mybackup and backup your apps that way but I think if you pick advanced under the nandroid options you can restore only the ext partition. I never did that but a fix permissions might help with any problems
Sent from my T-Mobile myTouch 3G Slide using XDA App
acejoker25000 said:
Restore the rom and use titanium backup or mybackup and backup your apps that way but I think if you pick advanced under the nandroid options you can restore only the ext partition. I never did that but a fix permissions might help with any problems
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Fix Permissions and a reboot didn't make the apps show up. Doing advanced nandroid restore now and only restoring the sd-ext. Will post results in a few. Thanks!
pettigrew95 said:
Fix Permissions and a reboot didn't make the apps show up. Doing advanced nandroid restore now and only restoring the sd-ext. Will post results in a few. Thanks!
Click to expand...
Click to collapse
I meant a fix permissions after an advanced restore otherwise there could be problems
Sent from my T-Mobile myTouch 3G Slide using XDA App
acejoker25000 said:
I meant a fix permissions after an advanced restore otherwise there could be problems
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Hmm sitting at the white t-mo boot screen for quite some time now...but i remember your 1st post saying this was normal with apps on the ext2
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.
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??