Database Info

[FIX]Fix external SD Card permissions (updated 2012-02-05)

NOTE: Please see the following post for the original modification (as far as I'm aware) and the manual method of doing the same thing: http://forum.xda-developers.com/showpost.php?p=20869996&postcount=7
This "update.zip" style installer simply automates the process of modifying /system/etc/permissions/platform.xml to make the tablet permissions act the same as previous versions of android.
In particular, programs with the WRITE_EXTERNAL_STORAGE permission will be able to write to the removable storage card. (Honeycomb changes this to require WRITE_MEDIA_STORAGE which very few, if any, 3rd party programs use.)
If you are having issues with programs writing to your storage card, this might fix it.
This uses 'sed' to make the edits. If this is installed twice, it won't re-modifying the file. (However, if you have manually edited the platform.xml file, and then run this script, it might make create duplicate, but harmless, <group> entries. Before making the modification to platform.xml, it will create a backup of the file (called platform.xml.backup) in the /system/etc/permissions directory (if the backup doesn't already exist.)
Instructions:
Download the file, and place on your sdcard. Reboot into recovery and install .zip from sdcard. Choose this file. Done..
(I've tested this with my CWM based recovery and it works. It _should_ work with the factory recovery as well, but I haven't tested... Please reply with your results.)
Support:
None. If you aren't familiar with using recovery to install updates, you should research the topic before continuing.
More info:
If you are curious, here is the sed command I'm sending, using busybox compiled from the cyanogenmod sources:
Code:
sed -e '/WRITE_EXTERNAL_STORAGE" >$/N;s/\n\(\([ \t]*\)<group gid="sdcard_rw".*$\)/\n\2<group gid="media_rw" \/>\n\1/' -i /system/etc/permissions/platform.xml
What that means is: do an "in-place" edit on /system/etc/permissions/platform.xml, and find the line containing "WRITE_EXTERNAL_STORAGE >", then if the next line contains some whitespace followed by "<group gid="sdcard_rw" />", replace that sdcard_rw line with two new lines, the first being "<group gid="media_rw" />" and the second being the exact line that contained "sdcard_rw". I purposely put the media_rw line before the sdcard_rw line to prevent this same sed command from finding the same match again. In other words, if you run this sed command 50 times on the same file, it'll only make the change the first time.
(I'm not fluent with sed, so if someone knows a better way to do that, please feel free to educate me.)
File is attached below...
UPDATED Feb 5th, 2012: the script will change the filesystem permissions of the platform.xml file before attempting to edit it. This MAY overcome issues people have been having with non-rooted devices, but I'm unable to test so I don't know. Okay, well, it appears that this won't work for a device that doesn't have CWM Recovery installed. Not sure why, but at least I've repeated it.
Take care
Gary

I assume this is for the 6210, but will it work for all versions?
Sent from my Galaxy Tab 7 Plus

Sweet, thinking about flashing this. Will it work on non-root systems?

ringnutz said:
I assume this is for the 6210, but will it work for all versions?
Click to expand...
Click to collapse
It should, but I have no way to test. I can tell you that it won't cause any harm. Go ahead and install it, and then (using adb or a file explorer tool) copy the /system/etc/permissions/platform.xml (and platform.xml.backup) files and compare them (or send them to me and I'll compare them) to verify.

pacmanftw said:
Sweet, thinking about flashing this. Will it work on non-root systems?
Click to expand...
Click to collapse
It should, but I haven't tested it. It shouldn't cause any harm, however, so feel free to try it.

garyd9 said:
It should, but I have no way to test. I can tell you that it won't cause any harm. Go ahead and install it, and then (using adb or a file explorer tool) copy the /system/etc/permissions/platform.xml (and platform.xml.backup) files and compare them (or send them to me and I'll compare them) to verify.
Click to expand...
Click to collapse
I have the 6210 as well, just wanted to clarify to cut down on the inevitable questions that would follow. Thanks again
Sent from my Galaxy Tab 7 Plus

Worked perfectly for me.

Absolutely fine here. Before I couldn't move files to the SD card using AirDroid now I can

Yup... its working fine with my plus...
Sent from my GT-P6200 using xda premium

Thanks for this. I started to script a fix for this but then I found yours. Thanks again!a

It's work for P6200

thank you gary it worked for me!!!

Still the same hier, it worked for me
P6200

Tested! It works for galaxy tab 7.0 Plus P6200,
nice work garyd9
Sent from my GT-P6200 using xda premium

garyd9 said:
It should, but I haven't tested it. It shouldn't cause any harm, however, so feel free to try it.
Click to expand...
Click to collapse
It does not work on non-root P6210.

Brightxda said:
It does not work on non-root P6210.
Click to expand...
Click to collapse
That doesn't make sense. What leads you to believe that it didn't work? Which program/option isn't working how you expect (and how do you expect it to work?) (sorry for all the questions, but if I can't repeat exactly what you are experiencing, I can't really help you.)
Do you have some kind of file explorer installed? If so, please browse to /system/etc/permissions and view the "platform.xml" file. Scroll down to find the line with "WRITE_EXTERNAL_STORAGE". There should be two lines below that that start with "<group gid". One should have the string "media_rw" and the other "sdcard_rw". If so, then the fix DID apply properly.
"root" shouldn't matter for this...

There is no change to the "platform.xml" after I installed the .zip under the recovery though it shows install completed. I even repeated it twice. It fails when I use ES file explorer to create a folder in ext. SD Card.
Then I rooted the device and manually modified the "platform.xml" (added the <group gid="media_rw" />), and it works now.

Yes I done the same after root, but I have to change the attribut ( sorry I' french) of "platform.xml" with Root explorer to write before (long press on the name), then I access to "platform.xml" with es file explorer to add the code line, save the file and reboot. and it works now (for model 6210)
"platform.xml" is at system/etc/permissions/
add
</permission name=android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="media_rw" />
</permission>

Okay, if the attributes of the file aren't allowing writing, then I'm obviously not allowing for that in the package. It seemed like a reasonable assumption that the file was writable, being that it worked for so many people...
I wonder why samsung isn't being consistant with the file permissions. Well, that's something I can probably fix in an update. Not a big deal to change perms on a file.
(It's also not a high priority, as this is working for the majority of people without me tinkering with file permissions.)
take care
Gary

I have a P6200, no root and using stock recovery as of this writing.
I had a P6210 and I was able to fix External SD Card writing on it manually.
I tried the .zip in this thread and it didn't work on my P6200.
I am thinking it didn't because my device is either rooted, or using stock recovery.
I will root and perhaps install CWM, and test further.
My test was using ES Explorer to create a new directory in the SD card. It couldn't, so I'm pretty sure the fix didn't work with my particular configuration.
garyd9 said:
That doesn't make sense. What leads you to believe that it didn't work? Which program/option isn't working how you expect (and how do you expect it to work?) (sorry for all the questions, but if I can't repeat exactly what you are experiencing, I can't really help you.)
Do you have some kind of file explorer installed? If so, please browse to /system/etc/permissions and view the "platform.xml" file. Scroll down to find the line with "WRITE_EXTERNAL_STORAGE". There should be two lines below that that start with "<group gid". One should have the string "media_rw" and the other "sdcard_rw". If so, then the fix DID apply properly.
"root" shouldn't matter for this...
Click to expand...
Click to collapse
Wait... how can you get into /system/etc/permissions if you haven't rooted the device? I was of the impression that you can only access that directory if you are rooted. I certainly can't get there.
I was able to on my P6210 when it was rooted.

[Q] newb problem How to rezip a rom

I have googled this alot and have not found any helpful results. I have unziped a rom I like to remove some .apks and add some of the ones I always find myself re-installing. I also have been playing with the build.prop, and the framework. I'm not trying to steal anyones work I just want to have a fresh version of this rom when I go back to it (which I do about once a week). my intent would be to flash, enter my wifi and google passwords, and start using it. I know I can just do a backup and reinstall that, but this has been helpful with my trying to understand how to build a rom and what makes it work. My question being what are the steps to rezip this rom into a flashable update. I have tried dsixda kitchen with no luck, just reziping it, and some other dumb methods. What am I missing here? plz help thank you.
also don't think it matters but this is for a o.g. evo

we got same problem, i edited a working rom for galaxy y (adding and removing some apk) then i was like huh??? what to do next, tried zipping it but doesnt work. hope.someone will reply here.
Sent from my Nokia 3310 running ICS

The problem is the signature verification of the ROM. We sign the ROMS when we create them.
No idea what custom recovery you might use but there should be an option to disable it before you try flashing.
I hope this helps.

No I have cwm and I disabled signature verification, it still starts fine says updating than immediately says its failed
Sent from my PC36100 using XDA App

I also just have it in the folders it unzips in then inside a folder and I just zip that folder is that not right I don't know lol hope someone can help
Sent from my PC36100 using XDA App

That's what's wrong. You can't zip an entire ROM as a folder then zip that folder. Doesn't work that way.
Open a ROM. See how its packed. You'll have a system folder, data, sdcard perhaps. But that's how you package it.
This isn't as easy as you think. You can't just hack stuff up and expect it to work if you don't do it properly.

MattCrystal said:
That's what's wrong. You can't zip an entire ROM as a folder then zip that folder. Doesn't work that way.
Open a ROM. See how its packed. You'll have a system folder, data, sdcard perhaps. But that's how you package it.
This isn't as easy as you think. You can't just hack stuff up and expect it to work if you don't do it properly.
Click to expand...
Click to collapse
No I'm leaving the folders inside the ROM intact. everything is in a folder with all the folders ( data folder, META-INF folder, system folder ect..., and the boot image inside that single folder and then I am ziping all those items in the folder into a zip. I just can't get it to flash it starts then after a second of installation it says aborted.

sknight13602 said:
No I'm leaving the folders inside the ROM intact. everything is in a folder with all the folders ( data folder, META-INF folder, system folder ect..., and the boot image inside that single folder and then I am ziping all those items in the folder into a zip. I just can't get it to flash it starts then after a second of installation it says aborted.
Click to expand...
Click to collapse
Zip up the ROM you want. Take that ROM to the kitchen then build it again. Try that. Sign it and everything. If you want a walk through PM me and ill give you my gtalk address.

sknight13602 said:
No I'm leaving the folders inside the ROM intact. everything is in a folder with all the folders ( data folder, META-INF folder, system folder ect..., and the boot image inside that single folder and then I am ziping all those items in the folder into a zip. I just can't get it to flash it starts then after a second of installation it says aborted.
Click to expand...
Click to collapse
After reading this more I'm still understanding that the data and meta, system folders are in a folder, then that folder is zipped.
This is incorrect way to package it. The data, meta, system etc needs to be zipped all together as one. Not in a folder that is zipped. Make sense? Hope this explains more.

I'll try that I guess Mabry them all being in a folder is the prob I hope thanks man
Sent from my PC36100 using XDA App

Yup. Let me know if you need anymore help and if that works for you.

MattCrystal said:
After reading this more I'm still understanding that the data and meta, system folders are in a folder, then that folder is zipped.
This is incorrect way to package it. The data, meta, system etc needs to be zipped all together as one. Not in a folder that is zipped. Make sense? Hope this explains more.
Click to expand...
Click to collapse
lol so I find this funny but after some research I found that their were some commands in my update script I was leaving in that needed to be removed because I was removing the apk from the rom but it was looking for them and causing errors so after all my headaches it was something simple that'll teach me not to mess with something that aint broke

just tryed to flash it and now after it almost finished flashing I got
"update sdcard/romname/blah blah. failed"(status 6)
does that mean anything to you besides that I messed something up?
I playing with a sense 3.5 rom on a gb 2.3.5 base. Is their an easier rom to play with thats is more user freindly for a newb? mabey takeing the original ruu and tweaking that? I just want to start somewhere and develop my skills.

sknight13602 said:
just tryed to flash it and now after it almost finished flashing I got
"update sdcard/romname/blah blah. failed"(status 6)
does that mean anything to you besides that I messed something up?
I playing with a sense 3.5 rom on a gb 2.3.5 base. Is their an easier rom to play with thats is more user freindly for a newb? mabey takeing the original ruu and tweaking that? I just want to start somewhere and develop my skills.
Click to expand...
Click to collapse
k I got it now thnx for your help MattCrystal

Your welcome. Every phone works a little differently but get used to having problems and fixing them. Part of the struggle. And to me the fun. I love troubleshooting.

i think just open the zip (not unzip it)..
when dialog box open,,you can choose the apk or the others you want to delete..
if you want add somthing to zip,,just open the folder location you want add that,,and than drag n drop the file(s)..
thats it..
than close the dialog box..
winrar will ask you to save the change or not,,choose,,save..
its work for me..
P.S.
use the rom by yourself..
as your personal rom..
if you want to publish it,,ask the permit from the devs..

[TOOL][EFS][LINUX][ROOT]Simple efs backup S2 Plus

Hello XDA,
because I saw more and more development for our device ( :good: ), I created a simple script for backing up the efs partition.
It is only tested using a GT-I9105P using Cyanogenmod 10.2
Instructions
1. Download the .zip file
2. Extract it
3. Open terminal and "cd" to the directory, where you extracted it.
4. type
Code:
./efs_backup.sh
if you got "rm failed for /sdcard/efs_tmp.img, No such file or directory", just ignore it
5. You can now find a file named "efs_backup_cwm.zip", you can flash it with cwm to restore your efs-partition
Why should I do that?
That's a simple question: Every Rom you flash and every root-app you use could have a simple bug and override/delete your efs-partition
What is the efs-partition?
It's a partition, wich is needed for any device-specific number like IMEI, Wlan-MAC-adress and so on. If it gets deleted/damaged, your mobile
will nothing more than a Mp3-player, unless you can flash back your old efs-partition.
Can you release it for Windows?
No, because I think every android-user should have linux installed on their pc and it doesn't cost anything. I have a dual-boot, too. If you want it on Windows, feel free to port it, it
won't be hard. If you want to install linux, I suggest you a debian-based distribution, because there will be the best support for android.
I WILL NOT ANSWER TO STUPID QUESTIONS!
I AM NOT RESPONSIBLE FOR ANY DAMAGE ON YOUR DEVICE!

where can i find efs_backup_cwm.zip??

jetwoot said:
where can i find efs_backup_cwm.zip??
Click to expand...
Click to collapse
In the directory where the script is.
Sent from my GT-I9105P using XDA Premium 4 mobile app

Sorry I made a mistake and it couldn't work. I uploaded a fixed version with some other improvements.

Awesome tool man.. :thumbup:
Sent from my Android using xda premium

Duplicate an app

Hi all,
so in IOS its pretty easy to duplicate an app.... but i search through the web for duplicating an app on android and i cant find any guides....
Therefore, any way to do that on android devices?

skylun said:
Hi all,
so in IOS its pretty easy to duplicate an app.... but i search through the web for duplicating an app on android and i cant find any guides....
Therefore, any way to do that on android devices?
Click to expand...
Click to collapse
What You mean by "duplicate" an app???
And what is the goal of do that ?

hi
EnricoD said:
What You mean by "duplicate" an app???
And what is the goal of do that ?
Click to expand...
Click to collapse
i mean making 2 same apps in a single device.
My goal is just to play 2 accounts in a single game and in the same device.

skylun said:
i mean making 2 same apps in a single device.
My goal is just to play 2 accounts in a single game and in the same device.
Click to expand...
Click to collapse
Simultaneously on 2 different accounts or separately?
I have 3 solutions I can think of:
- To Play Them Separately -
Multi User on Android
Using 2 different backup apps and restoring them to the other when you want to change
- To Play Them Simultaneously -
You would need to decompile the apk of the app you want to clone (pull it from data/app then use something like APK Multi Tools or APKTool) and change the package name under AndroidManifest.xml, recompile, push to /SDcard and install as a normal app. Then you will have a second same app you can use with the other one at any time with it's own data.
Also : Dev/WrongSection
Sent from my Nexus 5 using Tapatalk

hi
sewer56lol said:
Simultaneously on 2 different accounts or separately?
I have 3 solutions I can think of:
- To Play Them Separately -
Multi User on Android
Using 2 different backup apps and restoring them to the other when you want to change
- To Play Them Simultaneously -
You would need to decompile the apk of the app you want to clone (pull it from data/app then use something like APK Multi Tools or APKTool) and change the package name under AndroidManifest.xml, recompile, push to /SDcard and install as a normal app. Then you will have a second same app you can use with the other one at any time with it's own data.
Also : Dev/WrongSection
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
just did the first one... actually i have been studying on rooting few hours ago and just rooted my phone 10mins ago lol... just done making another profile, but your second option is more convenient than restarting my phone everytime i wanted to switch accounts....
any video guide that i can follow?

Quickly peeking over XDA I found this guide which is quite well explained for people who haven't decompiled an app before:
http://forum.xda-developers.com/showthread.php?t=2341351
Steps 6-8 are unnecessary hence you're not modifying a System APP but is recommended anyway just for future use (and avoiding any problems - which shouldn't occur anyway).
Your app (assuming it's installed) should be under data/app (from root directory of the device, copy it from there to /sdcard/ and then to PC. (There are many file managers which have root access, ES File manager or Total Commander are recommended)
(Follow guide)
Once you decompile the app (will be under a folder called projects) there should be a AndroidManifest.xml in the root of the decompiled app folder, edit it (I recommend NotePad++ for many reasons, but WordPad/Notepad are still viable), the XML is in human readable format and is generally small so there should be no issues.
Somewhere there should be a package name (these 99% of the time start with com. and often include the developer name after it then the name of the app e.g. com.android.chrome or com.handlerexploit.tweedle), simply modify it to something different, save and go back to the guide to recompile.
After recompiling simply push the app back to the phone and install it through a file manager.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 01:06 PM ---------- Previous post was at 12:58 PM ----------
Also seeing you have not probably used ADB you'd need the drivers for it (as well as USB Debugging enables in phone) for APK multi tool to pull system files if you decide to do Steps 6-8 (although unnecessary).
The tool here : http://www.wugfresh.com/nrt/ has easy to do instructions on installing drivers or if you know what you're doing grab the official driver here ( http://developer.android.com/sdk/win-usb.html ) and install in device manager if your device has no driver installed there. (Do Browse manually and point it to USB_driver directory)
Sent from my Nexus 5 using Tapatalk

[shell][utility][terminal] munky-tool

***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
​
DOWNLOAD
github

Dude once again you're creativity and hard work is paying off. Great job man
Style point for the rip bud!

Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.

SaschaKH said:
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
Click to expand...
Click to collapse
Yes. I tested it on my OPO. It went out for a rip. It will run on any device, and it will find the partitions on most.

Where's the download link dude, i'm not find download link from github ?

itsnie said:
Where's the download link dude, i'm not find download link from github ?
Click to expand...
Click to collapse
On the right side of page near the clone url, there should be a button that says download as zip.

Just realized you have to be in desktop view to see the download as zip button. I will post an additional link a little later.

Just added backup and restore contacts.

N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.

Rukbat said:
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Click to expand...
Click to collapse
Thanks, man. Glad to hear you like it.

mike the inkman said:
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
​
DOWNLOAD
github
Click to expand...
Click to collapse
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.

Azlun said:
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Click to expand...
Click to collapse
It is usually done in bootloader, but I am pretty sure I can make it work. Just need to test it before I release it. I am also going to release this as an apk soon. (Don't know how soon, but I probably won't have time for a few weeks)

An app that we can point new users to that will back up their userdata partition? Fantastic!

Rukbat said:
An app that we can point new users to that will back up their userdata partition? Fantastic!
Click to expand...
Click to collapse
Yeah, I think it will fill a need. I am going to do an APK to do the things from this script, and a corresponding GUI Linux package for APK modding, and maybe do something for Windows as I get time. In the process of moving somewhat unexpectedly, so it is taking longer than I would have liked.