Welcome.
For over a month, I look forward to the support, assistance from the manufacturer of the program Titanium Backup (as a licensed user) and until now I did not get any response from them. Therefore, I have a request to the honorable members of this forum, may have solved the problem of conservation of archives in Titanium Backup.
Now, it is the holder of the smartphone HTC One (you know, no SD card slot), and from the beginning there is a problem with the function called "Protected archive".
If you try to select it and other miscellaneous copy is returned in dyku message "Sorry, the operation failed".
HTC is ROOT, S-Off. I use a ROM called "ViperOne v1.1.1," but on other ROMs is the same problem.
Changing the backup directory in the preferences of the Titanium Backup does not work.
I tried the method described here:
http://forum.xda-developers.com/showthread.php?t=2059240
but it also does not give the result and does not change the situation.
Other features TitaniumBackup working properly, except for the protection of files: (((
Does anyone have any ideas, suggestions what to do to be able to protect (selected) copies of the program TitaniumBackupPRO?
I do not have the support to count - they do not write off: (((
greetings
q.
I have the same problem. I wanted to protect a couple old backups for safe keeping. All I get is operation failed. I did it before. But not on my Nexus 10. I will keep searching to see what I come up with. If I find it I will post back here.
Hi,
Same here with my HTC ONE X+ International.
I wrote to TitaniumTrack support here (http://www.titaniumtrack.com/support/product-support.html#usermessagea), you may also do it, this could help.
Concerning me, I went from an HTC DESIRE HD (32GB SDCARD) to an HTC ONE X+ (64GB internal memory).
When I edit my "platform.XML" file, In the "WRITE_EXTERNAL_STORAGE" section, the group definitions line refers to "<group gid="sdcard_rw"/>" instead of "<group gid="media_rw"/>".
I don't know if I should replace the "sdcard" by "media" or if I should add it. If yes, how to add it (syntax. Please write it here, I'll make a copy/paste).
I had to stop backing up my apps for now because of this problem... very annoying.
I may try others solutions, and I'll report them if it help.
tag : titanium backup protection, protéger cette sauvegarde, protect this backup.
Tried this... Didn't work
Tried what was recommended from the link below. Didn't work. Have the same issue with my htc one.
http://androidforums.com/sprint-gal...t-backups-feature-in-titanium-backup-pro.html
The worst thing is that the author/producer of Titanium Backup PRO totally not responsible for any e-mail asking for support.
The problem is from what I can see quite broad, applies to devices without SD card - and this is quite a lot.
We do not honest approach to their customers the application developer.
If someone manages to find a solution - we would ask for a response.
greetings
q
Hi
Did anyone find a solution, or even better an alternative that would make possible the availability to make severals backup of a same app with severals app data ???
Any clone of titanium ?
same problem since upgrading OS to 4.4
Since I upgraded my Note 3 from 4.3 to 4.4, I have not been able to use the "protect this backup" feature. Every time I try I get the error "Sorry, the operation failed". That feature worked fine before I upgraded the OS.
Most of the solutions to this problem seem to relate to the memory not being writable. That doesn't seem to be the case with me though. My backups are stored on my external SD card and I can create new backups just fine. I just can't protect them. And whether the backup was an old one made on 4.3 or a new one made on 4.4, the error message is the same.
I checked the file at /system/etc/permissions/platform.xml as suggested in this thread and elsewhere but the suggested additional group definitions are already there, so I couldn't add any. But again, since I can create new backups I don't think this is the root of the problem anyway.
I have contacted Titanium support and asked for suggestions. I'll report back here if I find a solution. Has anyone else been able to protect backups with TB after upgrading to Kitkat?
you can try with es browser to zip the archive you want to protect than you are good to go and you can also put it on your pc
xfive420 said:
I have contacted Titanium support and asked for suggestions. I'll report back here if I find a solution. Has anyone else been able to protect backups with TB after upgrading to Kitkat?
Click to expand...
Click to collapse
Just an update... Titanium support has been completely unresponsive after two attempts to contact them about this issue. The protect backup feature is still broken and they either don't know about the problem or are choosing to ignore it. Yes, you can manually zip or move backup files to an alternate location to preserve them, but that doesn't fix the feature.
Hi, wondering if anyone may have a suggestion. I'm not getting any action restoring a backed up User Dictionary with TB. It seems to create the backup but not restore it. Tried both data and app+data and reboots but still no action. HTC One rooted ARHD 71.1 (4.4.2)
Sent from my HTC One using XDA Premium 4 mobile app
xfive420 said:
Since I upgraded my Note 3 from 4.3 to 4.4, I have not been able to use the "protect this backup" feature. Every time I try I get the error "Sorry, the operation failed". That feature worked fine before I upgraded the OS.
Most of the solutions to this problem seem to relate to the memory not being writable. That doesn't seem to be the case with me though. My backups are stored on my external SD card and I can create new backups just fine. I just can't protect them. And whether the backup was an old one made on 4.3 or a new one made on 4.4, the error message is the same.
I checked the file at /system/etc/permissions/platform.xml as suggested in this thread and elsewhere but the suggested additional group definitions are already there, so I couldn't add any. But again, since I can create new backups I don't think this is the root of the problem anyway.
I have contacted Titanium support and asked for suggestions. I'll report back here if I find a solution. Has anyone else been able to protect backups with TB after upgrading to Kitkat?
Click to expand...
Click to collapse
Not sure if this will help anyone but it worked for me... I have a Galaxy S4 i9505... backup path was set to storage/extSdCard/ and could not protect backups... out of chance I decided to allow it to detect where any backups may be... well it came up with this funky path... mnt/media_rw/extSdCard... I set it to that and can now protect backups
cdzo72 said:
Not sure if this will help anyone but it worked for me... I have a Galaxy S4 i9505... backup path was set to storage/extSdCard/ and could not protect backups... out of chance I decided to allow it to detect where any backups may be... well it came up with this funky path... mnt/media_rw/extSdCard... I set it to that and can now protect backups
Click to expand...
Click to collapse
Glad you were able to fix the issue on the S4. I was optimistic it would work on my Note 3 but when I click "Detect" it shows me /storage/extSdCard/, I tried to manually browse to /mnt/media_rw/extSdCard but once I descend into the media_rw directory I get the error message "This folder cannot be accessed". I tried selecting /mnt/extSdCard (yet another path to the same place) but protecting backups still fails. So unfortunately the workaround didn't work for me, but hopefully it will fix this issue for someone else. Thanks for the tip.
cdzo72 said:
Not sure if this will help anyone but it worked for me... I have a Galaxy S4 i9505... backup path was set to storage/extSdCard/ and could not protect backups... out of chance I decided to allow it to detect where any backups may be... well it came up with this funky path... mnt/media_rw/extSdCard... I set it to that and can now protect backups
Click to expand...
Click to collapse
Hi there.
@cdzo72, many thanks for tips, I had some hope when reading you, but this was unsuccessful for me and my HTC ONE X+ .
I did try all those paths :
/storage/sdcard0/TitaniumBackup
/storage/emulated/legacy/TitaniumBackup
/mnt/sdcard/TitaniumBackup
/sdcard/TitaniumBackup
/storage/emulated/0/
/mnt/usbdisk/TitaniumBackup
Anyway, thank you so much.
After adding:
Code:
<group gid="media_rw" />
to WRITE_EXTERNAL_STORAGE in /system/etc/permissions/platform.xml I switched backup location in Titanium Backup from /storage/extSdCard/... to /mnt/media_rw/extSdCard/... and I'm able to protect backups now
Galaxy S5 SM-G900F, rooted stock 4.4.2
xfive420 said:
Glad you were able to fix the issue on the S4. I was optimistic it would work on my Note 3 but when I click "Detect" it shows me /storage/extSdCard/, I tried to manually browse to /mnt/media_rw/extSdCard but once I descend into the media_rw directory I get the error message "This folder cannot be accessed". I tried selecting /mnt/extSdCard (yet another path to the same place) but protecting backups still fails. So unfortunately the workaround didn't work for me, but hopefully it will fix this issue for someone else. Thanks for the tip.
Click to expand...
Click to collapse
Try using a file explorer (I prefer solid explorer) to change the permissions on the /mnt/media_rw/ directory. I changed mine to rw for all and then titanium could access the folder and protect backups there.
EDIT: The permissions wouldn't stick so it needed an init.d script.
DarkStarr said:
Try using a file explorer (I prefer solid explorer) to change the permissions on the /mnt/media_rw/ directory. I changed mine to rw for all and then titanium could access the folder and protect backups there.
EDIT: The permissions wouldn't stick so it needed an init.d script.
Click to expand...
Click to collapse
Thanks for the solution! Adding RWX to group permissions did the trick for me, but as you said in your edit the permissions don't stick. After a reboot they are reset and TB can no longer see the backup directory. I suppose an init.d script or maybe a tasker task could address this, but I feel writing a patch for the default folder permissions is more trouble than it's worth just to be able to protect backups again.
After I upgraded to Kitkat, some other apps had issues with writing to the external SD card. It seems they worked around the issue by writing to a specific folder with a name similar to /storage/externalSdCard/Android/data/com...... I tried that solution with TB but still couldn't get the backup protection feature to work.
I hope Titanium fixes or at least addresses this issue. I still have not received a response from their support team, and I'm not holding my breath.
xfive420 said:
Thanks for the solution! Adding RWX to group permissions did the trick for me, but as you said in your edit the permissions don't stick. After a reboot they are reset and TB can no longer see the backup directory. I suppose an init.d script or maybe a tasker task could address this, but I feel writing a patch for the default folder permissions is more trouble than it's worth just to be able to protect backups again.
After I upgraded to Kitkat, some other apps had issues with writing to the external SD card. It seems they worked around the issue by writing to a specific folder with a name similar to /storage/externalSdCard/Android/data/com...... I tried that solution with TB but still couldn't get the backup protection feature to work.
I hope Titanium fixes or at least addresses this issue. I still have not received a response from their support team, and I'm not holding my breath.
Click to expand...
Click to collapse
The easy solution here would be to download ROM Toolbox Lite and go to Scripter then import the script I will attach to this post then tell it to set it on boot. It will take a few seconds after boot to run but it worked fine for me. I had too many ROM issues though so I rolled back to 4.3.
I had to put it in an archive since it has no extension and XDA wouldn't accept it so just extract it and follow the previous instructions.
Your script admittedly allowed to give rights to the directory "/ mnt / media_rw", but despite this still does not solve the problem of copy protections on the device running HTC One ViperOne 6.2.1 (Android 4.4.2, Sense 6.0)
So I set TitaniumBackupPro:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
greetings
q.
qriozum said:
Your script admittedly allowed to give rights to the directory "/ mnt / media_rw", but despite this still does not solve the problem of copy protections on the device running HTC One ViperOne 6.2.1 (Android 4.4.2, Sense 6.0)
So I set TitaniumBackupPro:
[SNIP]
greetings
q.
Click to expand...
Click to collapse
If you look in your image TB is using the wrong directory to reach the backups. It must go through /mnt/media_rw in order to be able to protect backups. Even then another folder may need to be given proper permissions if you are not using an SD card. I haven't tried since I put all my backups on my SD.
In the directory "/MNT/Media_RW" is just one subdirectory called "USB" and it has nothing, is empty.
In the preferences TBP tried to change the directory to copy "/storage/emulated/legacy" and "storage/sdcard0" - but it did not bring any result.
I must mention that the subdirectory "sdcard0" symlinks in storage only and not the physical directory.
In the root directory of the device is a symlink to "sdcard".
But it is known that the symlink is impossible Aug. set of rights and attributes.
---------EDIT:
Curiosity, from the TBP can not create directory "/ mnt" or in "/ mnt / media_rw".
Please look at the screenshots, in theory, rights are granted:
Related
I can't seem to locate the directory folder that the new firefox app downloads to. anyone?
Nevermind, it goes right to the sdcard, no folder. I didn't see the files because the downloads failed...
can't seem to get the download folder to change.
I went into:
about:config
created a new string: browser.download.dir
set the value to: /mnt/extSdCard/Downloads/
Restarted Firefox
But still the downloads go into the sdcard/downloads
I've also tried:
/extSdCard/Downloads/
/sdcard/
/extSdCard/
/mnt/sdcard
none of these have any effect.
Any ideas?
Bump:beer:
Sent from my SGH-I747M using Tapatalk 2
Im also looking for changing my dl directory. It have work once for me when modifying the "browser.download.folderList" after creating the browser.download.dir string. But after reboot of firefox the next dl will go back again to the sdcard.
Wonder if anyone else could tell how to do it
creating a new string is a good step for changing your dl directory. But you should also add this step to make it work.
Modify the value of "browser.download.folderList" from 1 to 2
Thats it!!
Click to expand...
Click to collapse
When editing your old posts, try not to delete the original information that could have been useful to others.
People won't have known what value to put into the string.
Sent from my SGH-I747M using Tapatalk 2
I hate managing folders so now I use directory bind which allows me to bind two folders together. Basically you create another downloads folder on your external sd card and use directory bind to "bind" them. Checkbox to transfer contents and your downloads (source) folder will be dumped into the empty folder you've created automatically (destination must be empty when checking the box). When altering files in either downloads folder, the changes appear in both. When you look at storage, the original source folder is not calculated into your used internal storage amount even though every other app sees files in there (since that would defeat the purpose). I use it for my downloads, camera and several apps and game folders not designed to be pushed to SD. Instead of continuously resetting app download destinations, I sit back and relax knowing every app downloads to the proper place (minus the rogues who think they deserve their own folder lol). When flashing a new ROM, simply unbind everything first and disable autostart, backup with titanium backup, after restore, you should be good (depending on your new version of android in which case you may need to adjust some settings). If setting up from scratch again, assuming your working folder structure is still in tact, you can bind again without ticking the box (since the files are in their proper place and a transfer is no longer necessary).
You can get it here, it looks like it hasn't been updated in a while, but I've tested it from Android 4.0 through 4.2.2 and it's perfect (settings adjustments will likely be required): http://forum.xda-developers.com/showthread.php?t=1410262
Hi everyone, was a solution found to that still issue? I tried to move the default download folder to the ext SD card with settings into about:config, I changed as well the "browser.download.folderList" value to 2 and add a "browser.download.defaultFolder" string, but everything failed, please does someone know what to do? Or is there another setting menu or mod/Exposed module to achieve this..?
Thanks in advance for the help!
May I Taste said:
Hi everyone, was a solution found to that still issue? I tried to move the default download folder to the ext SD card with settings into about:config, I changed as well the "browser.download.folderList" value to 2 and add a "browser.download.defaultFolder" string, but everything failed, please does someone know what to do? Or is there another setting menu or mod/Exposed module to achieve this..?
Thanks in advance for the help!
Click to expand...
Click to collapse
Use this config (I am assuming you're on 4.4 and have used SDFixer)
SeraphSephiroth said:
Use this config (I am assuming you're on 4.4 and have used SDFixer)
Click to expand...
Click to collapse
Hi, thanks for your help, but it still don't work for me. What I don't understand is that the path can be whether
/storage/sdcard1/Download
or
/ext_card/Download
Maybe you know why? I'm running CM11 nightlies (4.4.4) on Xperia Z2
May I Taste said:
Hi, thanks for your help, but it still don't work for me. What I don't understand is that the path can be whether
/storage/sdcard1/Download
or
/ext_card/Download
Maybe you know why? I'm running CM11 nightlies (4.4.4) on Xperia Z2
Click to expand...
Click to collapse
With a r/w sd? Use a root explorer to find the path to the r/w sd
I'm very busy and sorry not to say anything for long but thank you much for your answer and help.
My path is correctly pointing the SD, I checked carefully the settings and got no success. Then suddenly Firefox began to write on ext sd, but still this is only sometimes! I tried to see if the files type or size had something to do with that behavior but it seems to be just erratic..
It actually seems that it's the "Flash Video Downloader" module who sends files into the internal storage regardless of the browser settings..
Hey XDA,
Lately I have been a lurker here eversince the haters on the G2x thread caused me to stop dev'ing. Anyways I have found a fix for the failed updates that a lot of us are getting. Follow the steps below to fix. You need a root file browser'
BEFORE FOLLOWING THESE STEPS
OPEN A ROOT BROWSER AND BROWSE TO /cache/recovery/last_log
This will show why the update failed! Undo whatever changes you made based on the output and you should be Golden
-Thanks to Namidairo and Disconnect from IRC for this tip
Step 0 (Only if you have V6 Script): Launch Script and Unsupercharge
Step 1: Browse to system and open your build prop and if there is a line at the bottom saying something like "#Supercharger Entries" then edit your build.prop and delete it.
Step 2: In system if there is a SU-Backup and another SU file delete it and then open Voodoo Root and Make a protected backup of SU.
Step 3: Browse to data and delete Su-Test
Step 4(Only if you messed with GPS) Make sure to revert GPS to original settings -> etc/gps/gps....xml
Step 5: Launch system settings navigate to apps, find DMClient and clear cache and Data and then in settings goto about and the firmware upgrade and let it download the update again.
Step 6: Once Downloaded apply the update and you will see that the red exclamation wont happen.
Basically if the build.prop file is modified then the update fails the other files mentioned above are just to make sure.
Let me know if you encounter issues. Good Luck
Edit: Once updated you will be greeted with "Please check system date"
Edit 2: New Features
-SystemBar Lock : Under Asus Customized Settings in Settings
-Disconnect Network during sleep under Asus Customized Settings in Settings
-Wifi Direct
-Asus Live WP has sunshine rays that are animated. Night Scene is also animated with glow bugs and transition from Day to Night with Sun Setting.
ASUS MyWater2 changed and modified with more detail and Night-Day Mode
-Searching for more
What your Build.prop should look like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's not always the build.prop that is at fault.
It was mentioned in irc that /cache/recovery/last_log will tell you what went wrong.
thanks for that I had not seen that in XDA. I did though do the steps above and was able to update after 7 failed update attempts.
I will add your suggestion to the OP if its okay?
Great tip on the log file. The update didn't like that I had renamed some files in system/app to stop them loading.
Added more changes found in the OP
Added Suggestion to check Cache in OP
flak0 said:
thanks for that I had not seen that in XDA. I did though do the steps above and was able to update after 7 failed update attempts.
I will add your suggestion to the OP if its okay?
Click to expand...
Click to collapse
Just add credit to Disconnect from IRC, I'm just remembering that it was mentioned.
Namidairo said:
Just add credit to Disconnect from IRC, I'm just remembering that it was mentioned.
Click to expand...
Click to collapse
Done check OP. Also gave you thanks
I seen this thread and im having simular problems. I am rooted but never unlocked.. I did modify lcd density and corrected it via fixing the build.prop and copying files from adb (i didnt make a backup of build.prop. When i look at mine it has lcd density line at the very bottom and there is a blank line directly above that. Is that the way the build.prop is? I have nothing to refer to. Can someone check this for me. I would really like to install this update Been messing with this thing for last 2 hours!
Seems like alot lotta people are having problems with this update and red failed..
flipper2006 said:
I seen this thread and im having simular problems. I am rooted but never unlocked.. I did modify lcd density and corrected it via fixing the build.prop and copying files from adb (i didnt make a backup of build.prop. When i look at mine it has lcd density line at the very bottom and there is a blank line directly above that. Is that the way the build.prop is? I have nothing to refer to. Can someone check this for me. I would really like to install this update Been messing with this thing for last 2 hours!
Seems like alot lotta people are having problems with this update and red failed..
Click to expand...
Click to collapse
I will post a screenshot in 2 minutes below this post to help you. Actually Ill post it on the OP too
I deleted an APK or two from /system/app and was unable to run the update as a result.
I just manually downloaded and reran the .15 update, then ran the .21 OTA update without any problems
Looking at the log file using test viewer....the log file is empty
Build Prop seems OK.....no extra entries
Step 2 - One SU backup there....but protected....can't delete....if I use Rootkeeper to delete, then it's gone, but I'm still rooted....when I try to unroot, it come back.
Step 3 - No Su-test in Data
Step 4 - Only gps.xml in GPs folder
Step 5 - cleared DM file in "Apps"'
Still can't upgrade.
The only files that are not original are for the AD=HOC fix.....BUT....I can't delete them.....This is the only computer/internet access... that I have...tethered to my TouchPro2.....If I change, then I can't download the update.....Catch 22....will be away from home for about 2 weeks
Solved!! Went to Mickey D's and used their free wifi got 15 downloaded/installed, then, using their wifi updated to 21 using OTA....whewwww.....AD-Hoc still works
flak0 said:
I will post a screenshot in 2 minutes below this post to help you. Actually Ill post it on the OP too
Click to expand...
Click to collapse
thx that will help.. i will try it tommorow when i get back from work. domt think its a good idea to mess with build.prop when sleepy.
robertg9 said:
Tried looking at the log file using test viewer....the log file is empty
Build Prop seems OK.....no extra entries
Step 2 - One SU backup there....but protected....can't delete....if I use Rootkeeper to delete, then it's gone, but I'm still rooted....when I try to unroot, it come back.
Step 3 - No Su-test in Data
Step 4 - Only gps.xml in GPs folder
Step 5 - cleared DM file in "Apps"'
Still can't upgrade.
The only files that are not original are for the AD=HOC fix.....BUT....I can't delete them.....This is the only computer/internet access... that I have...tethered to my TouchPro2.....If I change, then I can't download the update.....Catch 22....will be away from home for about 2 weeks
Click to expand...
Click to collapse
Yes - me too. Tried this, no dice.
what`s the name of the widget that shows cpu usage in status bar in the first post screenshots?
product26 said:
I just manually downloaded and reran the .15 update, then ran the .21 OTA update without any problems
Click to expand...
Click to collapse
Can you remind me how to do this? And what do I lose from my current .19 installation as a result of rerunning it?
Thanks.
180490 said:
what`s the name of the widget that shows cpu usage in status bar in the first post screenshots?
Click to expand...
Click to collapse
yeah, which one is that? haven't seen that one before?
-lukin- said:
Can you remind me how to do this? And what do I lose from my current .19 installation as a result of rerunning it?
Thanks.
Click to expand...
Click to collapse
Not sure what you would lose but here is how you do it manually
go to http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Download the .15 update for your sku. It is a zip file, in that zip file is another zip file. Take that 2nd zip file and put it on your micro sd card. remove your sd card and then put it back in and it should detect the update on the sd card.
edit: I too was having issues getting the .21 update(kept failing) and I just flashed .15 manually and just flashed the .21 update and it worked! No laying down droid with red ! mark.
graffixnyc said:
Not sure what you would lose but here is how you do it manually
go to http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Download the .15 update for your sku. It is a zip file, in that zip file is another zip file. Take that 2nd zip file and put it on your micro sd card. remove your sd card and then put it back in and it should detect the update on the sd card.
Click to expand...
Click to collapse
One important part after you do this if you have root and want to keep it, you need to either reappy through voodoo root keeper or re root it. I didn't now I'm waiting for a root method.......
Before you apply .21 update
Namidairo said:
It's not always the build.prop that is at fault.
It was mentioned in irc that /cache/recovery/last_log will tell you what went wrong.
Click to expand...
Click to collapse
Thanks for that. I checked the log and saw that system/bin/wpa.supplicant2 was causing the failure. I had replaced that file so that I could get adhoc back. I just restored the original file and the update worked.
IGNORE - MY POST WAS:
stu•pid
[stoo-pid, styoo‐] -er, -est, noun
adjective
1. lacking ordinary quickness and keenness of mind; dull.
2. characterized by or proceeding from mental dullness; foolish; senseless: a stupid question.
3. tediously dull, especially due to lack of meaning or sense; inane; pointless: a stupid party.
4. annoying or irritating; troublesome: Turn off that stupid radio.
5. in a state of stupor; stupefied: stupid from fatigue.
So after updating to Android JB 4.2 I can no longer write to the ' SdCard/Android/Obb ' directory.
Can anyone confirm if they are having this problem too? Is it due to this stupid and annoying feature that google has now implemented that they wish to check all .apk files before they are able to be installed? I turned this off in settings but it seems that it turns itself back on again after every reboot?
I cannot write to the directory from my PC via USB cable or even through a root app despite the phone telling me that I have -Rw access to the folder and all of it's subfolders etc.
I even tried writing via Linux but it doesn't work either... even if I try and force a write.. plus I cannot access the internal memory when the phone is booted down...
Does anyone have any ideas?
Thanks.
Think you need to have root Explorer to write to obb
Sent from my GT-I9300 using xda app-developers app
Before upgrading I could write to the directory from either my PC or Root Explorer or Solid Explorer. Now I can't seem to write to it at all. So it's not that unfortunately...
R: [Q] Can no longer write to Android/Obb in JB 4.2?
As far as i can remember u can edit the obb directory even without root....but i'm an android kinda novice.
Try another file browser from the phone (the one from rhythm software is very good).
Might also be that problem with directory permissions that get mixed up to which clockwork mod always refers to (they have an option to fix directory problems).
Android, i have noticed, can get corrupted easily, have you done some serious modding to your cel phone or just root and small patching?
Sent from my GT-I9300 using xda app-developers app
Let's leave the moderating to us please and thanks. If you see something that doesn't belong, hit the Report button. Otherwise you could takenit too far and you could be the one breaking the rules. Best to report and move on.
Thread Cleaned. Let's try this again.
R: [Q] Can no longer write to Android/Obb in JB 4.2?
Woody said:
Let's leave the moderating to us please and thanks. If you see something that doesn't belong, hit the Report button. Otherwise you could takenit too far and you could be the one breaking the rules. Best to report and move on.
Thread Cleaned. Let's try this again.
Click to expand...
Click to collapse
?
Sent from my GT-I9300 using xda app-developers app
I've been trying a string of different things for a couple of days...
I've tried root explorer pro, when I press copy it finishes instantly but nothing is happening.
R/w is on..
I tried solid explorer pro, it instantly says "the file(s) could not be copied"
Tried "Fix Permissions" from CWM...
Tried copying from Windows. It copies up to 99% then says: "The directory is no longer available, it may have been removed"
The connection is fine, and I can copy to all other folders no matter where. EXCEPT for this folder..
I am 99.9% sure that it's due to this annoying new Android Guard thing in the settings that asks to scan everything. Even if I turn it off, I bet that it still has some sort of affect. It's probably just denying all writes from outside an accepted source..
This really angers me. I don't want my phone to have ANY directories that I cannot write to. Especially seeing as I have to often copy files back and forth from this folder when I make updates to the 2 games I am developing..
There was no problem before updating to 4.2 and this Android Guard thing.
I'm willing to try all suggestions.. Thanks
are you using the leaked 4.2.1 rom from samsung? or a 4.2.1 aosp rom?
DSA said:
are you using the leaked 4.2.1 rom from samsung? or a 4.2.1 aosp rom?
Click to expand...
Click to collapse
I'm using Android HD Revolution. It's apparently an 'official leaked' one with just the 'improvements' that Mike etc. do.
Thanks also for your reply. I'm trying to keep my device current so I can stay on top of releasing updates, but I really can't do that if I can't fix this issue. I've put it off for awhile now but it's really stalled the development process /tear
leijonasisu said:
I'm using Android HD Revolution. It's apparently an 'official leaked' one with just the 'improvements' that Mike etc. do.
Thanks also for your reply. I'm trying to keep my device current so I can stay on top of releasing updates, but I really can't do that if I can't fix this issue. I've put it off for awhile now but it's really stalled the development process /tear
Click to expand...
Click to collapse
If you mean using ARHD 30.* that is not official, that is the leaked version of 4.2.1, that mike has tweaked
Before flashing ROMs, read changelists carefully please:good:
Ok well then I missed the play on words, it's not 'official' but it's a leaked version. Mike, or whoever updates the thread doesn't usually provide a very verbose changelog.
So I take it that absolutely no one here on XDA has any idea as to why I cannot write to this 'specific' area in my partition?
I have the same problem with Galaxy S4. I rooted the device but this didn't help.
I have tried loading files to obb in Windows 7, ES File Explorer, AntTek Explorer - but no results.
Edit://
I solved my problem using AntTek Explorer (root) and the path is next:
Device root/storage/sdcard0/android/obb - then I had permissions to copy files there.
I hope it help.
Priidik said:
I have the same problem with Galaxy S4. I rooted the device but this didn't help.
I have tried loading files to obb in Windows 7, ES File Explorer, AntTek Explorer - but no results.
Edit://
I solved my problem using AntTek Explorer (root) and the path is next:
Device root/storage/sdcard0/android/obb - then I had permissions to copy files there.
I hope it help.
Click to expand...
Click to collapse
Thankyou very much my friend!
I forgot to write back. I solved my problem by just wiping my device and flashing a new rom. It ended up being a rom issue. No problems now.
hello there,
wondering if there is anyways to copy obb files on galaxy s4 without root?
or even make the app read obb file from where else ?
buy the app
OBB Folder
Hi guys... i have bought new galaxy s4 having 4.2.2 jellybean.... well i want to know how to write/copy files to Android/Obb folder.... i can't copy anything to this folder....... is there any restriction on this folder.... plz help me ... i can't copy games data to this folder......!
Regards...
everjollyfellow said:
Hi guys... i have bought new galaxy s4 having 4.2.2 jellybean.... well i want to know how to write/copy files to Android/Obb folder.... i can't copy anything to this folder....... is there any restriction on this folder.... plz help me ... i can't copy games data to this folder......!
Regards...
Click to expand...
Click to collapse
read the thread before posting
Youtube Video
everjollyfellow said:
Hi guys... i have bought new galaxy s4 having 4.2.2 jellybean.... well i want to know how to write/copy files to Android/Obb folder.... i can't copy anything to this folder....... is there any restriction on this folder.... plz help me ... i can't copy games data to this folder......!
Regards...
Click to expand...
Click to collapse
Search youtube for-How to move OBB file to Android/obb! Android 4.2 Phone! ..
Hope that helps..
reading changelogs doesn't help the problem..
and @leijonasisu probably it would've been bad flash.. but before i say that you should change rom and check once again.. you gotta see if there was any write protection to the specific folder.. so try using an FTP client, if you still cant get access, then you gotta change the rom and try again
You can fix the extsd write lock by using root explorer navigating to etc\platform\permissions.xml
You need to mount as RW and edit the file to match what I'm pasting below.
You can ignore the middle part about syscope info but change your permissions for "write_external_storage" the "access_all_external_storage" and the "write_external_storage"
Don't delete anything from the file or do this without paying attention. Do not alert the syscope permission in between the 2nd and 3rd permissions that relate to storage.
I found this method through Google but it's worked for me so fast with no problems. If you use root explorer and open the file in text editor when you save the modified file, the original file will have .bak appended to it. The guide I used only changed 2 of the 3 permissions I'm saying to edit but the sd lock fix went away after restarting but since I changed the permissions to what I changed below is been working gray even after restarting.
Remember be careful with how you edit the file, only change it in the places I showed to make sure there aren't any complications. If you type it manually make sure to match the formatting and symbols exactly. If you ate going to cut/paste make sure only to change the permissions to exactly how I show it.
I'm not responsible for any damage or issues caused by following this method incorrectly. Remember to save the file with the original name of permissions.xml and then restart the phone to check your now writable ext sd card.
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
I haven't tried that one but I've used the xposed framework app that is supposed to enable extsd write but it didn't seem to work properly for me or was at best unreliable when I tried it. I like knowing what patches or fixes are doing behind the scenes in case I need to change them or if there's a problem or an update and it stops working you can do it yourself especially when its add easy as copy and paste
rbird2 said:
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
Click to expand...
Click to collapse
This one hasn't worked for me very much on a few ROMs but I did have a little better luck using the Xposed module mentioned above.
Many thanks for the post, OP. I'll add that to my notes and try it on the next ROM that gives me write issues.
Awesome glad to be able to help. .. when I first upgrades yo NG6 I couldn't believe Google could screw up one of the best features in android phones compared to the iphone. At least we're able to workaround it in the current versions at least fornow
nj12nets said:
Awesome glad to be able to help. .. when I first upgrades yo NG6 I couldn't believe Google could screw up one of the best features in android phones compared to the iphone. At least we're able to workaround it in the current versions at least fornow
Click to expand...
Click to collapse
People wonder why Google apps which work fine are still considered "beta." It's because Google isn't done with something until they screw it up completely, preferably also changing the UI a zillion times so it's unusable on more than one level.
rbird2 said:
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
Click to expand...
Click to collapse
This one as well...
https://play.google.com/store/apps/details?id=jrummy.sdfix
Thanks for adding the app add an option but can you give an idea of how well or functions and its reliability
I just rooted my phone a few days ago. My phone decided to upgrade to NG6 by itself and it crippled the SD card almost completely. I had some work arounds, but this just made it so much harder. I downgraded to NC5, had a problem, did a full reset and redid my phone. Did Towelroot V3, SuperSU, turned SDM.apk and FWUpgrade.apk into backups. Then I did the SDFix app, rebooted and now the SD card works like it did with MK2. I'm very pleased.
I want to copy a file to the /system/fonts folder, but no matter what file explorer I use, they are all failing to copy any file to the folder. On ES File Explorer, I get "Permission denied," but when the system is mounted Rewritable, I get "Task Failed." Yes, my phone is rooted. Can anyone please help me out? Thanks.
John256145 said:
I want to copy a file to the /system/fonts folder, but no matter what file explorer I use, they are all failing to copy any file to the folder. On ES File Explorer, I get "Permission denied," but when the system is mounted Rewritable, I get "Task Failed." Yes, my phone is rooted. Can anyone please help me out? Thanks.
Click to expand...
Click to collapse
Did you enable Root-Explorer in ES File explorer? Just go into the left menu scroll down and check it :good:
Deathvirus said:
Did you enable Root-Explorer in ES File explorer? Just go into the left menu scroll down and check it :good:
Click to expand...
Click to collapse
Yes, it was enabled. I found out that changing the system to Rewritable may have caused the error. I have an app called Emoji Switcher that always worked whenever I had to change Emojis from Google to ios7. When I installed this app: https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl=en and set the system to RW, Emoji Switcher could no longer change the emoji file in the /system/fonts folder. I was forced to restore a nandroid backup, luckily without losing data. But I want to know what to do the next time I need to modify the /system folders when it doesn't let me.
John256145 said:
Yes, it was enabled. I found out that changing the system to Rewritable may have caused the error. I have an app called Emoji Switcher that always worked whenever I had to change Emojis from Google to ios7. When I installed this app: https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl=en and set the system to RW, Emoji Switcher could no longer change the emoji file in the /system/fonts folder. I was forced to restore a nandroid backup, luckily without losing data. But I want to know what to do the next time I need to modify the /system folders when it doesn't let me.
Click to expand...
Click to collapse
cant really help you, but i may be able to offer some info.
im guessing you are either running Marshmallow, or have a nexus running stock?
if no, then the rest may be irrelevant.
i believe it was in M, google implemented some sort of system write protection, it can be bypassed but i dont know how off hand.
on nexus's, with the M update, google has the system so full, even with write ability, you may not be able to because there is no room.
maybe that will help you to look for a fix, maybe not lol
bweN diorD said:
cant really help you, but i may be able to offer some info.
im guessing you are either running Marshmallow, or have a nexus running stock?
if no, then the rest may be irrelevant.
i believe it was in M, google implemented some sort of system write protection, it can be bypassed but i dont know how off hand.
on nexus's, with the M update, google has the system so full, even with write ability, you may not be able to because there is no room.
maybe that will help you to look for a fix, maybe not lol
Click to expand...
Click to collapse
I have a Moto G 2nd Generation running 5.0.2. Although the info is irrelevant for me, I'll take it if I upgrade to Marshmallow. In my case, I'll just avoid changing the system directory manually for now. Thanks for both of your help!
John256145 said:
I have a Moto G 2nd Generation running 5.0.2. Although the info is irrelevant for me, I'll take it if I upgrade to Marshmallow. In my case, I'll just avoid changing the system directory manually for now. Thanks for both of your help!
Click to expand...
Click to collapse
np
it is usually best to try and post in your devices forum, as everyone there has your device, and may be able to help more.
moto g 2015 help forum http://forum.xda-developers.com/2015-moto-g/help