[Resolved] [SOLVED!!][ROOT ONLY] Insufficient Storage Space: Titanium Backup Error - General Questions and Answers

If you have Titanium Backup installed on your previous version, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working (ForceClose). Reinstalling the app might lead to an "insufficient storage" error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup in the system.
Disclaimer
This information comes with no warranty! What you're going to do is completely at your own risk!
I shall not be held responsible for any damage to your device if you had chosen to follow the steps below. Cheers!!
Here's how to do it:
## Make sure your phone is rooted. :good:
1- Use any file explorer like Root Explorer or ES File Explorer, etc.
2- go to /data/app,
3- find and delete "com.kermidas.TitaniumBackup-1.odex".
4- Now you can install Titanium Backup again!
[source: Insufficient Storage Space]
Another Solution:
Saint AAI said:
If deleting ODEX files does not work, or there are none. Try the following:
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
I've had this problem for days now on my HTC One and it has been doing my head in. Found a similar solution in the galaxy S4 forums, so thought I would share as this solved it for me.
Source: http://forum.xda-developers.com/showthread.php?t=2391363
Click to expand...
Click to collapse
Useful feedback:
buu1152 said:
If you have done like me, and tried deleting ODEX files, changing path of folder to /legacy and trying reinstall and still get insufficient free space, then changing file location back to emulated/0...should solve the problem..
OH BTW i'm running PA 3.99 RC-2 with franco's r184.. so if your running earlier versions of those, you may need to stick with emulated/legacy.. all in all, try both paths and which ever works for you is where your power lies
Click to expand...
Click to collapse
============================
Hit THANKS if this helped. :good:

m0e_03 said:
If you have Titanium Backup installed on your previous version, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working (ForceClose). Reinstalling the app might lead to an "insufficient storage" error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup in the system.
Here's how to do it:
1- Use any file explorer like Root Explorer or ES File Explorer,
2- go to /data/app,
3- find and delete "com.kermidas.TitaniumBackup-1.odex".
4- Now you can install Titanium Backup again!
[source: Insufficient Storage Space]
Click to expand...
Click to collapse
Thanks.. I had this issue.. and solved..

m0e_03 said:
If you have Titanium Backup installed on your previous version, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working (ForceClose). Reinstalling the app might lead to an "insufficient storage" error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup in the system.
Here's how to do it:
1- Use any file explorer like Root Explorer or ES File Explorer,
2- go to /data/app,
3- find and delete "com.kermidas.TitaniumBackup-1.odex".
4- Now you can install Titanium Backup again!
[source: Insufficient Storage Space]
============================
Hit THANKS if this helped. :good:
Click to expand...
Click to collapse
I used this method and find more *.ODEX files. After deleting those, my problem was completely gone. Thanks :good:

axel4401 said:
I used this method and find more *.ODEX files. After deleting those, my problem was completely gone. Thanks :good:
Click to expand...
Click to collapse
I know this might sound weird but..my app folder is nowhere to be found ANYWHERE which kind of freaks me out. I did manage to find a few .odex files hanging around which I deleted but the apps that were experiencing this error was facebook messenger and kii keyboard. I only found a .odex file for kii keyboard which I deleted but it still did not fix the storage error.

I don't have this odex file but I do have this issue.

good job boy
:good:

If deleting ODEX files does not work, or there are none. Try the following:
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
I've had this problem for days now on my HTC One and it has been doing my head in. Found a similar solution in the galaxy S4 forums, so thought I would share as this solved it for me.
Source: http://forum.xda-developers.com/showthread.php?t=2391363

thank you for your support Mr.Saint, but I believe this thread was to solve the issue of NOT being able to install TB..then how is someone even supposed to run TB if its not even installed on the device, right? "

Saint AAI said:
If deleting ODEX files does not work, or there are none. Try the following:
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
I've had this problem for days now on my HTC One and it has been doing my head in. Found a similar solution in the galaxy S4 forums, so thought I would share as this solved it for me.
Source: http://forum.xda-developers.com/showthread.php?t=2391363
Click to expand...
Click to collapse
Thank you!
I was having this issue on my Nexus 4 with Paranoid Android and i had no "data/app" folder but you method worked!

thanks, it works

Saint AAI said:
If deleting ODEX files does not work, or there are none. Try the following:
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
I've had this problem for days now on my HTC One and it has been doing my head in. Found a similar solution in the galaxy S4 forums, so thought I would share as this solved it for me.
Source: http://forum.xda-developers.com/showthread.php?t=2391363
Click to expand...
Click to collapse
Exactly my Problem, perfectly solved. Thanks!

m0e_03 said:
4- Now you can install Titanium Backup again!
Click to expand...
Click to collapse
Thanks - it worked!
I had this problem on my smashed GN2 and was desperately trying to get the backup so I could restore onto a new phone...

Saint AAI said:
If deleting ODEX files does not work, or there are none. Try the following:
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
I've had this problem for days now on my HTC One and it has been doing my head in. Found a similar solution in the galaxy S4 forums, so thought I would share as this solved it for me.
Source: http://forum.xda-developers.com/showthread.php?t=2391363
Click to expand...
Click to collapse
you made my day <3

Saint AAI said:
If deleting ODEX files does not work, or there are none. Try the following:
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
I've had this problem for days now on my HTC One and it has been doing my head in. Found a similar solution in the galaxy S4 forums, so thought I would share as this solved it for me.
Source: http://forum.xda-developers.com/showthread.php?t=2391363
Click to expand...
Click to collapse
OMG thanks so much this worked perfectly for me on Nexus4. I guess its a prob with P.A? Never gave me this error before it was weird i deleted stuff and made space and was freaking out! thanks again!!:good:

Ok so I've tried the ODEX file way.. no ODEX files found.. my storage location is in legacy.. ive unistalled, deleted my cache and dalvik cache rebooted and reinstalled and switched back to legacy and still gives me the same message when i backup modified data.. 'Interrupted: Insufficient free space' ive gotten the insufficient storage before but now this says insufficient free space so im wondering if that has anything to do with this.. please can someone help, all other methods still failing and i dont really want to hastle a system wipe.. also in my data file there is not 'app' file its just data then com.keramidas.TitaniumBackup.. tried deleting that too and nothing .. any input appreciated thanks
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
m0e_03 said:
If you have Titanium Backup installed on your previous version, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working (ForceClose). Reinstalling the app might lead to an "insufficient storage" error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup in the system.
Disclaimer
This information comes with no warranty! What you're going to do is completely at your own risk!
I shall not be held responsible for any damage to your device if you had chosen to follow the steps below. Cheers!!
Here's how to do it:
## Make sure your phone is rooted. :good:
1- Use any file explorer like Root Explorer or ES File Explorer, etc.
2- go to /data/app,
3- find and delete "com.kermidas.TitaniumBackup-1.odex".
4- Now you can install Titanium Backup again!
[source: Insufficient Storage Space]
============================
Hit THANKS if this helped. :good:
Click to expand...
Click to collapse
Saint AAI said:
If deleting ODEX files does not work, or there are none. Try the following:
1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.
Then try doing your normal backup procedure.
I've had this problem for days now on my HTC One and it has been doing my head in. Found a similar solution in the galaxy S4 forums, so thought I would share as this solved it for me.
Source: http://forum.xda-developers.com/showthread.php?t=2391363
Click to expand...
Click to collapse
buu1152 said:
Ok so I've tried the ODEX file way.. no ODEX files found.. my storage location is in legacy.. ive unistalled, deleted my cache and dalvik cache rebooted and reinstalled and switched back to legacy and still gives me the same message when i backup modified data.. 'Interrupted: Insufficient free space' ive gotten the insufficient storage before but now this says insufficient free space so im wondering if that has anything to do with this.. please can someone help, all other methods still failing and i dont really want to hastle a system wipe.. also in my data file there is not 'app' file its just data then com.keramidas.TitaniumBackup.. tried deleting that too and nothing .. any input appreciated thanks
Click to expand...
Click to collapse
This apparently happened right after i setup my wifi HD mouse which was already installed a week prior but never connected.. just incase that might have any relevance
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
If you have done like me, and tried deleting ODEX files, changing path of folder to /legacy and trying reinstall and still get insufficient free space, then try changing file location back to emulated/0 i told my friend about it and he said he found on a recent post to change back to emulated/0 so i cant credit that post right now, but changing file location back to emulated/0 should solve the problem.. thanks
OH BTW im running PA 3.99 RC-2 with franco's r184.. so if your running earier versions of those you may need to stick with emulated/legacy.. all in all try both paths and which ever works for you is where your power lies

buu1152 said:
Ok so I've tried the ODEX file way.. no ODEX files found.. my storage location is in legacy.. ive unistalled, deleted my cache and dalvik cache rebooted and reinstalled and switched back to legacy and still gives me the same message when i backup modified data.. 'Interrupted: Insufficient free space' ive gotten the insufficient storage before but now this says insufficient free space so im wondering if that has anything to do with this.. please can someone help, all other methods still failing and i dont really want to hastle a system wipe.. also in my data file there is not 'app' file its just data then com.keramidas.TitaniumBackup.. tried deleting that too and nothing .. any input appreciated thanks
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
This apparently happened right after i setup my wifi HD mouse which was already installed a week prior but never connected.. just incase that might have any relevance
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
If you have done like me, and tried deleting ODEX files, changing path of folder to /legacy and trying reinstall and still get insufficient free space, then try changing file location back to emulated/0 i told my friend about it and he said he found on a recent post to change back to emulated/0 so i cant credit that post right now, but changing file location back to emulated/0 should solve the problem.. thanks
OH BTW im running PA 3.99 RC-2 with franco's r184.. so if your running earier versions of those you may need to stick with emulated/legacy.. all in all try both paths and which ever works for you is where your power lies
Click to expand...
Click to collapse
The post advising to change back to emulated/0 was on the Paranoid Android mako thread. I updated to PA 3.99 RC2 yesterday and got the insufficient free storage error. Changing back to emulated/0 fixed it.

steviemch said:
The post advising to change back to emulated/0 was on the Paranoid Android mako thread. I updated to PA 3.99 RC2 yesterday and got the insufficient free storage error. Changing back to emulated/0 fixed it.
Click to expand...
Click to collapse
After trying each of the other solutions in this thread, changing to emulated/0 is what fixed it for me.
This started for me when I went from a couple of weeks old Unofficial Shelnutt E970 CM10.2 to the first Official nightly.

wallsg said:
After trying each of the other solutions in this thread, changing to emulated/0 is what fixed it for me.
This started for me when I went from a couple of weeks old Unofficial Shelnutt E970 CM10.2 to the first Official nightly.
Click to expand...
Click to collapse
I know this is an older thread, but I wanted to throw in my 2 cents and say that changing back to emulated/0 also fixed it for my Nexus 4 on the latest cm10 nightlies.

I am on SlimBean 4.3, and I am now faced with the fact that I will have to reinstall everything. No solution on this page has worked. I don't have Odex files, I've done literally every suggestion and with the newest TIBU I've come to the conclusion that nothing but a full wipe may work. If anyone can think of anything else please let me know.

I am in the same boat. Have a HTC One with CM 10.2 and Nothing works

Related

[Q] PowerAmp - UID mismatch issue - Settings getting reset

I'm having a serious issue with PowerAmp app. My settings are getting reset to default every time the program is completely closed (either by a task manager or after a reboot). Not only that, the change log and Thank you popups come up every startup after the complete shutdown. Pls help resolve.
On contacting the Dev, he says its a UID mismatch issue and it can be solved by uninstalling and reinstalling the program. However that has not fixed the issue.
XXJPY, Speedmod kernel, ULF, SGSI9000
mithunjo said:
I'm having a serious issue with PowerAmp app. My settings are getting reset to default every time the program is completely closed (either by a task manager or after a reboot). Not only that, the change log and Thank you popups come up every startup after the complete shutdown. Pls help resolve.
On contacting the Dev, he says its a UID mismatch issue and it can be solved by uninstalling and reinstalling the program. However that has not fixed the issue.
XXJPY, Speedmod kernel, ULF, SGSI9000
Click to expand...
Click to collapse
Strange, I'm using the PowerAmp app and I don't experience this. Have you tried contacting the Dev again about this?
Have you tried downloading it again and then installing it?
One possibility is that when you re-install it you are restoring corrupt settings back onto your device.
Have you tried a hard reset/factory reset then installing it again to see if it works?
It's working now. I used root explorer and navigated to the dbdata folder. Then I deleted the folder corresponding to Poweramp. Since then settings are not getting reset every time I end the app using a task manager.
None of the above works for me:
- uninstalled PowerAMP
- uninstalled PowerAMP Full Version Unlocker
- Deleted sdcard/Android/data/com.maxmpz.audioplayer directory with Super Manager
- reset the phone
- installed PowerAMP
- installed PowerAMP Full Version Unlocker
Same problem! Any ideas?
-----------
Kyocera QCP 6035 > Kyocera 7135 > Palm 600 > Palm 680 > Samsung GT-I9000
- 8GB int and 32B ext SDs
- unlocked, not branded
- froyo 2.2.1 XXJPY
- rooted
- voodoo EXT4
You will need a file explorer like root explorer since you are rooted. You got the wrong folder. You have to first uninstall full version. Then go to dbdata folder which is above the sdcard folder. Go to the power amp folder and delete the shared peers file. After that reinstall power amp it should be fine..
@mithunjo - you are so right! Super Manager was not it, Root Explorer did it. Thanks!
mithunjo said:
You will need a file explorer like root explorer since you are rooted. You got the wrong folder. You have to first uninstall full version. Then go to dbdata folder which is above the sdcard folder. Go to the power amp folder and delete the shared peers file. After that reinstall power amp it should be fine..
Click to expand...
Click to collapse
im having the same problem with power amp. however i couldnt find the folder "dbdata".i evn tried to use the search feature in root explorer to locate the folder but no use!. any suggestions?
im using sony ericsson official 2.1 firmware 0.24 and am rooted
same problem here... will try... thanks!
The dbdata folder is above the internal sdcard folder. In that delete the preferences file in the power amp folder which goes something like maxmp.player..
If you don't want to spend money for the 'Root Explorer', like me, get the 'Terminal Emulator'. It's free, and will give you a terminal interface. Open the app, press the menu button and choose the option to show the keyboard. The following commands will 1) give root permissions to the app and 2) delete the settings folder of PowerAMP:
su
rm -r /dbdata/databases/com.maxmpz.audioplayer
Thats it. The folder is gone. In my case I had to deinstall poweramp before this procedure, and reinstalled afterwards. Finally I can use PowerAmp again.
I've also had that problem (Galaxy S with Darky 8.0 (JPY) ) and deleting dbdata\databases\com.maxmpz.audioplayer helped me. I didn't even have had to uninstall and install PowerAMP.
embrion said:
I've also had that problem (Galaxy S with Darky 8.0 (JPY) ) and deleting dbdata\databases\com.maxmpz.audioplayer helped me. I didn't even have had to uninstall and install PowerAMP.
Click to expand...
Click to collapse
Tried deleting only the folder with RootExplorer without uninstalling and then reinstalling PowerAMP.
I'll see if this is enough.
I have a rooted htc Inspire running CyanogenMod nightlies.
I have used RootExplorer to look for dbdata and have not been able to find it. I've been through every file with RExplorer and have also used it to search for the file. Both ways I have come up empty. Am I missing something?
And I did read the enitire thread first
Thanks for any help.
[email protected]

Weird error

i have a samsung galaxy s (gingerbread 2.3.3) and after doing some tweaking there was a problem with the google search widget. when i open it up it says: the application google search process com.google.android.googlequicksearchbox has stopped. i did manage to find a temporary fix for this by reinstalling the stock apk i found from a website. however every time i reboot the device the message appears again and then i have to reinstall it again to make it work. This is very annoying how can i fix this? is it some kind of autostart issue?Any help would be appreciated
DanTheMan62 said:
i have a samsung galaxy s (gingerbread 2.3.3) and after doing some tweaking there was a problem with the google search widget. when i open it up it says: the application google search process com.google.android.googlequicksearchbox has stopped. i did manage to find a temporary fix for this by reinstalling the stock apk i found from a website. however every time i reboot the device the message appears again and then i have to reinstall it again to make it work. This is very annoying how can i fix this? is it some kind of autostart issue?Any help would be appreciated
Click to expand...
Click to collapse
Quite likely. When you re-installed it, did you make it a system app?
yes i believe it it is a system app
Theonew said:
Quite likely. When you re-installed it, did you make it a system app?
Click to expand...
Click to collapse
it did say that its going to replace a system application but i believe it must be a bug in the autostart. is there anyway i can fix this?thx for your reply i appreciate it. you have earned a thx for caring
DanTheMan62 said:
it did say that its going to replace a system application but i believe it must be a bug in the autostart. is there anyway i can fix this?thx for your reply i appreciate it. you have earned a thx for caring
Click to expand...
Click to collapse
Try making it a system app. Right now its probably installed as an update to the system app, but its better if it remains by itself. This can be done in many ways. You could use Titanium Backup, or simply place the app in /system/app/ (and set the permissions).
dont work
Theonew said:
Try making it a system app. Right now its probably installed as an update to the system app, but its better if it remains by itself. This can be done in many ways. You could use Titanium Backup, or simply place the app in /system/app/ (and set the permissions).
Click to expand...
Click to collapse
i tryed to copy and paste it using es file explorer but it said that it failed. Any ways even if i do get past that how do i set the permissions ?
Or maybe delete the whole apk with titanium backup or a root explorer, reboot and install it again.
Happened to me with apex launcher and this solved the problem
DanTheMan62 said:
i tryed to copy and paste it using es file explorer but it said that it failed. Any ways even if i do get past that how do i set the permissions ?
Click to expand...
Click to collapse
Titanium Backup - Select the app in the list and choose "integrate update into ROM".
Manual Way - Use Root Explorer, etc. to copy and paste the file in /system/app/. Make sure you mount it as R/W first. Using Root Explorer, long press the file and choose permissions. It should be set to "rw-r--r--".
Reboot after either of these methods.
thx
Theonew said:
Titanium Backup - Select the app in the list and choose "integrate update into ROM".
Manual Way - Use Root Explorer, etc. to copy and paste the file in /system/app/. Make sure you mount it as R/W first. Using Root Explorer, long press the file and choose permissions. It should be set to "rw-r--r--".
Reboot after either of these methods.
Click to expand...
Click to collapse
thanks sorrry for the lack of replies but i will try it and inform u if it has worked

[Q] Fuhu Nabi 2 - Root and Removing Monarch

I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
Go into the settings of ES file explorer and check everything under root settings. The only folder you want to get rid of is the Apps in the vendor folder. Anything else can harm the system. I just used the cut feature on the apps folder and pasted it to my sd card to make sure it worked first. Good Luck!
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
theonyxphoenix said:
. then switch to boot in parent mode, .
Click to expand...
Click to collapse
how ?
theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
Guess I missed something and should've read better, how did you set it to boot only into parent mode.
Sent from my SAMSUNG-SGH-I957 using xda premium
theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
How do you set it to boot into parent mode?
byohaserd said:
How do you set it to boot into parent mode?
Click to expand...
Click to collapse
Did you try going to settings -Security - put a TIC in " Set Parent Mode as default mode " ?
---------- Post added at 07:15 AM ---------- Previous post was at 07:07 AM ----------
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
---------- Post added at 07:28 AM ---------- Previous post was at 07:15 AM ----------
theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
I used TWRP to do anything - rooted or unrooted you can make change as you wish .
when you are in TWRP mount system then use advanced and file manager
hope this helps
I did not see that until you mentioned it...thanks
I was able to get it to work by going into a startup manager and freezing kidsmode2 and nabimode. I erased the apps folder though cause I wanted the space freed up.
Sent from my NABI2-NV7A using xda app-developers app
I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?
Rest to Factory setting
mikewhit001 said:
I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?
Click to expand...
Click to collapse
1-switch off.
2-press power button & vol + together.
3-press vol - to go to recovery kernel and press vol + to select it.
3-android model should come lying down with red triangle!.
4-press vol - & vol + together.
5-select the system reset and press power button.
6-after that switch off and on with all new factory settings.
Best Regards.
Eric Karz said:
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
Click to expand...
Click to collapse
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1
Nabi 2 Charge/Reboot problem
t499user said:
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1
Click to expand...
Click to collapse
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!
I flashed your package but the android upgrading still shows up for me,only for a few secs and it seems as if no programs get upgraded...what are your thoughts on this? How can I find the stray files that are causeing this?
Sent from my NABI2-NV7A using xda app-developers app
stuck in TWRP
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.
mikewhit001 said:
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.
ALD3 said:
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.
Click to expand...
Click to collapse
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.
mikewhit001 said:
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.
Click to expand...
Click to collapse
Ok your backups are all bad, that's why it finishes so quick and won't boot out of TWRP recovery. You will have to download a image file and get it into the TWRP folder on your sdcard. You will have to download it on your computer unrar it and name the folder something like unrooted 1.9.37 and transfer it to your micro sdcard. Then put micro sdcard back in tablet. In TWRP recovery, you will have to go into Advanced>File Manager. In file Manager, you will have to click on external sdcard and copy the file from there back to sdcard>TWRP>backups>serial#>unrooted 1.9.37 it doesn't matter what the folder name is that you put in the serial# folder but the all the others are as named and your new folder HAS TO BE IN THE SERIAL# FOLDER, or Restore will not see it. When that is done go back to main menu and Restore, you should see your new folder, choose it and swipe to restore. This should take 10+ minutes. You should be able to reboot to system then.
Unrooted1.9.37 file to download
https://www.box.com/shared/ew0jcmch2ohvr43ubjqe
This thread can help you a lot quicker.
http://forum.xda-developers.com/showthread.php?t=1905674
If you have problems, PM me and I will send you my email so we can work quicker and won't trash up this thread.
I'm having the same issue since the gapps update, where the Nabi shuts itself down while charging. Sometimes it can be a real pain to reboot after it does this.
Funhog51 said:
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!
Click to expand...
Click to collapse
i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???
streetglide13 said:
i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???
Click to expand...
Click to collapse
In es go to the menu where you turn on root explorer and tap the words 'root explorer' then a menu will pop up, tap mount r/w and then set /system to rw. You then should be able to delete the files. After you're done deleting set system back to read-only.

[Resolved] Titanium Backup saying not enough space

I've flashed a new ROM and restored the app from Google Play.
Among them, Titanium Backup and it's Pro key.
First I've saw the error "not enough free storage".
Then uninstalled both the app and the key. Reinstalled.
Wipe dalvik cache and cache...
Nothing works more.
I can install but it always shown Version Pro (donation) - Thank you! but I cannot backup anything.
P.S. I do not have an .odex file in system\data folder (as suggested in other threads).
What can I do?
Technical said:
I've flashed a new ROM and restored the app from Google Play.
Among them, Titanium Backup and it's Pro key.
First I've saw the error "not enough free storage".
Then uninstalled both the app and the key. Reinstalled.
Wipe dalvik cache and cache...
Nothing works more.
I can install but it always shown Version Pro (donation) - Thank you! but I cannot backup anything.
P.S. I do not have an .odex file in system\data folder (as suggested in other threads).
What can I do?
Click to expand...
Click to collapse
Find the solution: http://forum.xda-developers.com/showpost.php?p=45457317&postcount=14
tobymacfreak said:
Follow these steps to fix...
1.) Open Preferences and choose backup folder location
2.) Select Detect and choose whole device
3.) Choose the option /storage/emulated/legacy
4.) Select Use the current folder
5.) Benefit
Click to expand...
Click to collapse
Thanks xda forum.
Technical said:
Find the solution: http://forum.xda-developers.com/showpost.php?p=45457317&postcount=14
Thanks xda forum.
Click to expand...
Click to collapse
having the same issue, but not being given the option to select a different directory..
faaaaq said:
having the same issue, but not being given the option to select a different directory..
Click to expand...
Click to collapse
It's on the TB Preferences: Backup location.
Technical said:
It's on the TB Preferences: Backup location.
Click to expand...
Click to collapse
yes, thats where i was, but it did not detect the legacy location and give me that option like it normally does. Tried editing the post after I figured it out, but I had to wait 5 minutes then didnt care any more lol. In the screen where you select to scan or use current, the back button goes up a level in the directories, so I just had to manually navigate to the proper location
Do for me the job!
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en_GB
Why not use root?
Vincho said:
Do for me the job!
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en_GB
Click to expand...
Click to collapse
Sadly This did not help me either. It's a root app — why not use root power to write to the SD card?
---------- Post added at 03:26 PM ---------- Previous post was at 02:49 PM ----------
Technical said:
What can I do?
Click to expand...
Click to collapse
Several fixes have suggested so far and different fixes have helped different people. So here an additional option wich migth help.
I moved the backup folder from it's previous location to /storage/B3EC-1310/Android/data/com.keramidas.TitaniumBackup/Backup using adb shell which is a lot faster then using a file manager which moves every file in a directory separately.
The B3EC-1310 is the ID of the SD card which will be different for every SD card.
Then I changed the location in Titanium Backup itself as well. That works for now but is still not perfect. I guess I need to change from the AOKP rom to a rom which does not protect the SD card.
AtlanDaGonozal said:
Sadly This did not help me either. It's a root app — why not use root power to write to the SD card?
---------- Post added at 03:26 PM ---------- Previous post was at 02:49 PM ----------
Several fixes have suggested so far and different fixes have helped different people. So here an additional option wich migth help.
I moved the backup folder from it's previous location to /storage/B3EC-1310/Android/data/com.keramidas.TitaniumBackup/Backup using adb shell which is a lot faster then using a file manager which moves every file in a directory separately.
The B3EC-1310 is the ID of the SD card which will be different for every SD card.
Then I changed the location in Titanium Backup itself as well. That works for now but is still not perfect. I guess I need to change from the AOKP rom to a rom which does not protect the SD card.
Click to expand...
Click to collapse
if i may know, what makes it imperfect? is there something bothering you during backup / restore?
and one more thank you for your help, its solution for me

[Q] Titanium Backup not working on 4.4.2

I tried backing up from Titanium Backup, but whatever I tried, it kept complaining about insufficient space.. Tried changing the backfolder to either /storage/0/TitaniumBackup and /storage/legacy/TitaniumBackup, but it still failed. Had to resort to backupping to a USB-OTG stick..
Any settings I need to change or something?
May be you bro, I tried it on my N5, 4.4.2 and I had no issue. I'm assuming you do have plenty of space? You have 6.1.4.3 running?
jackpollard said:
May be you bro, I tried it on my N5, 4.4.2 and I had no issue. I'm assuming you do have plenty of space? You have 6.1.4.3 running?
Click to expand...
Click to collapse
4.something GB free.. Even trying to backup a single app fails. Checking settings shows that every TitaniumBackup-folder is Write-protected...
Latest version
Humm, plenty of space. I checked mine and my files are being stored on; /storage/emulated/legacy/titaniumbackup. Let me know if I can check any settings for you, sorry I could not help more.
---------- Post added at 05:25 PM ---------- Previous post was at 05:22 PM ----------
I checked my folder for TB and it shows DRW, I think and I could be wrong, that means the owner can read/write. Are you using a different profile?
jackpollard said:
Humm, plenty of space. I checked mine and my files are being stored on; /storage/emulated/legacy/titaniumbackup. Let me know if I can check any settings for you, sorry I could not help more.
Click to expand...
Click to collapse
Think I found the problem, permissions on that folder was effed up some how, couldn't even delete the folder, had to delete it from TWRP.. Trying now again!
Yeah, I think you got it.
The_Hamster said:
Think I found the problem, permissions on that folder was effed up some how, couldn't even delete the folder, had to delete it from TWRP.. Trying now again!
Click to expand...
Click to collapse
Did you manage to solve your problem...? I am having the exact same issues right now, could you please tell m e what/if your fix was? I was able to delete the Titanium Backup folder from/storage/emulated/0 But now as I cannot make a backup it can't make a new folder and I no longer have a backup folder location, even if i make a folder via Root Explorer it still can't detect it....
thanks
Edit Device: Galaxy S5 Rom: Alliance v5.3 Android version 4.4.2

Categories

Resources