System not allowing to copy files to System Folder (Desperate!) - Android Q&A, Help & Troubleshooting

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

Related

[GUIDE] Correctly using Root Explorer to manually replace modded/stock system files

Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!

ES File Explorer System Write

ES file explorer isn't mounting system as writeable. Can't copy any file to system or change any files within system using the apps root explorer. Anyone else have this issue? Anyone know a solution?
Please dont suggest using another app. I have tried that and they do work. I just prefer ES.
Sent from my SCH-I545
I had the same issue, and ended up buying Root Explorer. No idea why. I couldn't even find the option to make it writeable like I used to be able to.
..
thanx for chart
I noticed this too. Has anyone tried previous the version to see if that makes a difference?
Update: I tried the older version and it tries to run a test which fails, resulting in not being able to use that feature. I would assume the same test is failing in the new version.
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Im_Gumby said:
Update: I tried the older version and it tries to run a test which fails, resulting in not being able to use that feature. I would assume the same test is failing in the new version.
Click to expand...
Click to collapse
Not sure, but maybe related to OP's issue: after rooting, using ES File Explorer version 3.0.4 (dl'd from play store), I can't use the built in root explorer. After selecting "Root Explorer" from the menu, after a delay (appoximately 20 seconds) I get the "Sorry, test failed. This feature cannot run on your phone." message in the attached screenshot.
Interestingly, I was able to access ES's root explorer while still on the pre-release kernel, before flashing back to the stock kernel.
The new ES is a little different. Pull up the fast access menu and open the tools tab on the left. from there, tap on root explorer, mount R/W, then change the bubbles to RW. I had to do this to edit my build.prop so I assume this is what you're asking. Hope this helps!
whichonespink73 said:
The new ES is a little different. Pull up the fast access menu and open the tools tab on the left. from there, tap on root explorer, mount R/W, then change the bubbles to RW. I had to do this to edit my build.prop so I assume this is what you're asking. Hope this helps!
Click to expand...
Click to collapse
I don't get any options for mount as R/W. I think I've seen that menu before so I know what you're talking about. But it doesn't show up on the S4. At least not for me.
Sent from my SCH-I545
atrohde said:
I don't get any options for mount as R/W. I think I've seen that menu before so I know what you're talking about. But it doesn't show up on the S4. At least not for me.
Sent from my SCH-I545
Click to expand...
Click to collapse
So when you pull up the fast access menu and click root explorer under tools, you dont see mount R/W like in this picture?
Not at all. Just wiped app data and tried again and nothing. Just the test failed message.
Sent from my SCH-I545
atrohde said:
Not at all. Just wiped app data and tried again and nothing. Just the test failed message.
Sent from my SCH-I545
Click to expand...
Click to collapse
I don't get that menu either. My test fails also.
same here. ES's new update sucks anyway. i've used ES since day one, and with the new update, every single time you wanna do root things you have to mount system....EVERY time. the old one would stay mounted. it's very annoying.
i started using root browser or something..the free one.
I was reading through some other posts on a different thread and I came to the understanding it may have to do with the file system format or kernel. I would test a kernel but not sure if I can easily get back to stock as I don't want to lose functionality. Can anyone else test a different kernel to see if that works?
Sent from my SCH-I545
i'm running ktoonz kernel and it doesn't work.
jayochs said:
i'm running ktoonz kernel and it doesn't work.
Click to expand...
Click to collapse
Touchwiz or AOSP?
Sent from my SCH-I545
ah sorry. stock touchwiz. didn't flash a new rom yet
Sent from my SCH-I545 using Tapatalk 4 Beta
I ran into this exact same problem with ES File Explorer. I thought it might have to do with using SuperSU, but I haven't been brave enough to downgrade to Superuser.
As with others, I've gotten very comfortable with Root Explorer. I now only use ES to copy between the local file system and Windows shares.
- Dave
____________________________________________
Sent from my Galaxy S4 using Tapatalk 2
Worked with developer and got the version that can mount read write on system.
tsangwc said:
Worked with developer and got the version that can mount read write on system.
Click to expand...
Click to collapse
I have also and can confirm the new release works.
tsangwc said:
Worked with developer and got the version that can mount read write on system.
Click to expand...
Click to collapse
Also confirmed, once.
Now that I go back into the app a second time, it doesn't seem to ask SuperSU for permissions and /data (for example) is empty.
I'm still not 100% convinced I fully understand the new ES Explorer's root paradigm. In the old one I fell in love with, you enabled root with one simple checkbox and you had Root Explorer (kinda; I have both installed). In this latest major update, you have to pick Root from the side menu, after which you're prssented with a list of tools that I don't want/need. To browse as root, do I just hit Back to this helpful, unwanted list and start browsing? This is what I did during the first successful test of this test code, but it won't work a second time.
- Dave
____________________________________________
Sent from my Galaxy S4 using Tapatalk 2

Rooted Users: Edit the Volume

Guys,
I can't post in the official thread here:
http://forum.xda-developers.com/lg-g3/development/guide-headphone-speaker-volume-booster-t2819821
But I just wanted to confirm that if you root your device and follow the directions here, I've got confirmed working on the Sprint LS990 variant of this phone. The thread mentions nothing of this on Sprint or the LS990 but I can confirm that it is indeed working.
You'll need to:
1. Have root with SuperSU installed
2. Install Root Browser and 920 Text Editor (Available in market for free)
3. Navigate to system/etc and then mixer_paths.xml
4. Change file permissions to rw-r-r
5. Save to your downloads folder just in case you trash your phone or something
6. Navigate to markers mentioned in thread link above. The LS990 variant will have aforementioned markers listed approximately 15 lines later in the code. Edit them to your liking.
7. Save, reboot, pray not to get caught in limbo.
8. Enjoy having better sound than everyone else with a phone.
Just an FYI anyone attempting this: If you do not edit the permissions correctly when overwriting the file the phone will not boot. It will get stuck at the yellow sprint screen and you will have to preform a reset.
Root browser did not allow me to change permissions correctly and when going quickly I did not notice it when overwriting.
However, second attempt after recovery it worked great.
Thanks for the info TROPhouse
So i havnt edited yet but permissions look right here. Will they change after I edit and save. And then change them back right. I don't wanna get stuck since we have no custom recovery yet.
Did it. It was way worth sweatin through the reboot process. Haha.
Has anyone thats using Viper used this mod?
Sent from my LGLS990 using Tapatalk
sinisin said:
Has anyone thats using Viper used this mod?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
I'm using viper. Works perfect. After installing I moved the app from data/app to system/app. Heard people were having it being stopped after using it for awhile and this was there fix for that.
Kept having permission issue and was kind of nerve wrecking with no recovery.... However, phone sounds awesome now!
stagejuan said:
Kept having permission issue and was kind of nerve wrecking with no recovery.... However, phone sounds awesome now!
Click to expand...
Click to collapse
What settings did you end up with. I used 68 or 69 on all mine and it's pretty good. Not sure if I want it louder or quieter but it's definitely way better than stock was.
delete
Mahapederdon said:
What settings did you end up with. I used 68 or 69 on all mine and it's pretty good. Not sure if I want it louder or quieter but it's definitely way better than stock was.
Click to expand...
Click to collapse
I did 69 which seems perfect to be honest... I mainly hear music at the gym and usually use soundcloud... at 69, I don't even get close to full volume on the phone now. Its perfect
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Super loud
Thanks! Great volume!:victory:
dk2463 said:
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Click to expand...
Click to collapse
Don't know if this is too late to help, but...
I don't use 920, but my guess is there's an option somewhere (probably in settings for the app) to switch the file system to read - write mode, instead of read-only. I use the FX app, and that's what I had to do with it. Be sure to set it back to read-only when you're done.
dk2463 said:
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Click to expand...
Click to collapse
SUCCESS!
So you need to download an app that will mount your system, I used an app called mount/system. You launch it then select Mount r/w. Once you do that you have the needed access to edit the files as listed. I used this guide as well and had success....hope this helps others!
copy the original mixer_paths to your memory by ES file
edit it by notepad++ on windows and put it again in your memory
copy it from internal to your /system
highlight it and set permissions rw r r
move it from /system to /system/etc/
reboot and enjoy
Has anyone tryied playing with bluetooth volume i cant find where to change it any sugestions?
Nice, I haven't had any issues with my phone being too quiet, but I also came from a Verizon G2. Those were noticeably horrible for volume levels, so the G3 is a welcome change.
In regards to all the questions about which app to use for which function:
You could use Root Explorer, or any other file explorer that has root capabilities (ES File Explorer, Total Commander). You do NOT need to use a specific app set and if your file explorer can't mount/unmount the system partition with root permissions, try a new one because that one sucks.
You also should not be downloading three separate apps to accomplish this. It's kind of overkill to have a file explorer, a text editor, and a system partition mounter when any decent file explorer has all three of those built in. I think ROM Toolbox even has all those capabilities in the free version.
RandomPooka said:
Nice, I haven't had any issues with my phone being too quiet, but I also came from a Verizon G2. Those were noticeably horrible for volume levels, so the G3 is a welcome change.
In regards to all the questions about which app to use for which function:
You could use Root Explorer, or any other file explorer that has root capabilities (ES File Explorer, Total Commander). You do NOT need to use a specific app set and if your file explorer can't mount/unmount the system partition with root permissions, try a new one because that one sucks.
You also should not be downloading three separate apps to accomplish this. It's kind of overkill to have a file explorer, a text editor, and a system partition mounter when any decent file explorer has all three of those built in. I think ROM Toolbox even has all those capabilities in the free version.
Click to expand...
Click to collapse
Agreed but I downloaded ES File Explorer and several others and I was unable to find the ability to mount as r/w. If the option is in those apps, it's very much hidden so an app to mount your file system then an editor was what I needed and it worked.
dk2463 said:
Agreed but I downloaded ES File Explorer and several others and I was unable to find the ability to mount as r/w. If the option is in those apps, it's very much hidden so an app to mount your file system then an editor was what I needed and it worked.
Click to expand...
Click to collapse
ES's current interface does hide a lot, and is in almost every way inferior to the original interface. But the option is there. It's also in FX (File Explorer) which is my root editor of choice.
the pursuit of sound quality! bullet for my valentine cant be heard on stock!!!!!!!
tried this. guess i messed up. stuck on spark screen. sat and read through the pages here. gotta fix my phone when i get home tonight.
what did you change you volume levels to?
So can those who have successfully made the edits share what volume levels you changed and what are the new numbers? I've made the change to mine and even with my $100 earphones there's distortion at what I feel is a low level. I'm thinking maybe there's a balance among these that I need to achieve?
thanks!
dk2463

Enable EXTSD as writable on Rooted SGS4

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.

Extracting Stock Camera

I am trying to figure out how to extract the camera app from the stock ROM to use in the CM13 ROM. Partly because I would like to use it for slow-motion video and to experiment with it, but also because I would like to turn this into a learning experience. I've been following instructions to flash ROMs for a few years now, but haven't gone farther than that.
So here has been my experience so far:
- Backed up CM13, flashed stock (rooted), and converted the app to user app in order to back it up.
- I noticed that it would crash on startup as a user app, so I converted it back to a system app as an experiment. It still would crash on startup.
- I decided to try going another route and extracted the stock ROM in SuperR's Kitchen. Got the apk, flashed it in CM13. Same situation: crash on startup as user or system app.
I am unsure where to go from here. Any help is greatly appreciated. Thanks in advance.
Side note: I know there is a questions sub-forum too, but I figured it fit here better as it is about extracting an app to mod the ROM. If I was mistaken, please just move the thread over to the appropriate sub-forum.
Masterjuggler said:
I am trying to figure out how to extract the camera app from the stock ROM to use in the CM13 ROM. Partly because I would like to use it for slow-motion video and to experiment with it, but also because I would like to turn this into a learning experience. I've been following instructions to flash ROMs for a few years now, but haven't gone farther than that.
So here has been my experience so far:
- Backed up CM13, flashed stock (rooted), and converted the app to user app in order to back it up.
- I noticed that it would crash on startup as a user app, so I converted it back to a system app as an experiment. It still would crash on startup.
- I decided to try going another route and extracted the stock ROM in SuperR's Kitchen. Got the apk, flashed it in CM13. Same situation: crash on startup as user or system app.
I am unsure where to go from here. Any help is greatly appreciated. Thanks in advance.
Side note: I know there is a questions sub-forum too, but I figured it fit here better as it is about extracting an app to mod the ROM. If I was mistaken, please just move the thread over to the appropriate sub-forum.
Click to expand...
Click to collapse
Did the logcat give any pointers as to why it might have crashed?
It's a camera app, for MiFavor, and only for MiFavor. It's probably depending on something else from the stock ROM, and that's why it's crashing in CM.
I like this idea. I might even look into modifying the app itself, to see if we can get it working outside of MiFavor.
I don't think I worded it clearly enough, the first time I converted it to a user app and back to system, it was still in the stock ROM. Something about the conversion screwed things up. I'll have to flash stock again at some point and grab logcats while it's working and after I screw it up.
In the meantime, I attached a logcat for everything containing "camera" after it was converted to a system app in cm13. It's kind of harsh to look at it in pure text format, but I used the matlog app with its color coding to record it.
To be honest, I'm not quite sure what I'm looking at with this, or if I went about this in the right way.
EDIT: I have no idea why the logcat is not attaching correctly. I'll need to find some other way of doing it.
It works fine under CM according to a friend. You just need the libs to go along with the app.
Here is the WHOLE folder of ZTE camera, he just put this inside the /system/priv-app/ folder and apparently it's working just fine after a reboot.
https://my.mixtape.moe/znyabg.7z
Remember to press thanks and buy me a beer.
It's still not working properly for me, but here are a few things I noticed:
- When I extracted the app from the ROM using SuperR's Kitchen, that folder did exist in /system/priv-app/ZTE_Camera/. However, the directory was completely empty, unlike your download.
- When I installed the app in CM13 and converted it to a system app, it moved to /system/priv-app/ rather than /system/priv-app/ZTE_Camera/.
- I copied the lib folder to /system/priv-app/, didn't work. I then created the folder ZTE_Camera and copied both lib and the apk into it. Didn't change anything. Of course rebooting with each change. I didn't think this would work in the first place, as the application shortcut on my home screen points to /system/priv-app/.
Definitely thanks though for helping me out. Beer... that's another matter. Nasty stuff that is. I can just hear people yelling at me behind their screens lol.
Was it a deodexed ROM? Might need to try it with the odex files? When I check /system/priv-app/ZTE_Camera, there's also an "oat" folder with odex files since this hasn't been deodexed...
Or maybe SuperR's kitchen was trying to automatically deodex while you were extracting.
To be honest, I never understood odex, just throwing ideas out at this point.
Masterjuggler said:
It's still not working properly for me, but here are a few things I noticed:
- When I extracted the app from the ROM using SuperR's Kitchen, that folder did exist in /system/priv-app/ZTE_Camera/. However, the directory was completely empty, unlike your download.
- When I installed the app in CM13 and converted it to a system app, it moved to /system/priv-app/ rather than /system/priv-app/ZTE_Camera/.
- I copied the lib folder to /system/priv-app/, didn't work. I then created the folder ZTE_Camera and copied both lib and the apk into it. Didn't change anything. Of course rebooting with each change. I didn't think this would work in the first place, as the application shortcut on my home screen points to /system/priv-app/.
Definitely thanks though for helping me out. Beer... that's another matter. Nasty stuff that is. I can just hear people yelling at me behind their screens lol.
Click to expand...
Click to collapse
I'm sure it works, friend confirmed it works on CM13 and I'm using it on BrokenOS. To clear it up.
It should be /system/priv_app/ZTE_Camera. And inside that folder should be the apk along with the lib. If you just extract the zip I gave you into priv_app it should just work. I have no idea why it doesn't work for you. Everything about the camera works. Slomo, video h265, the works.
You can try making a backup of the stock camera app using titanium backup then install it on your phone after flashing CyanogenMod. What I would do is flash zad miix then back up the stock camera app with titanium backup. Then transfer the back up to your PC. Then flash CyanogenMod and reinstall the camera app with titanium backup.
as already I will have this phone I start doing this mods
if anyone can search the file this and tell me if an entry is interesting?
I'm currently using LOS 14.1, and the method suggested does not work - File Manager throws an error about R/W, TWRP claims /system is empty, and ADB push says "Successful" but isn't.
NadavCE said:
I'm currently using LOS 14.1, and the method suggested does not work - File Manager throws an error about R/W, TWRP claims /system is empty, and ADB push says "Successful" but isn't.
Click to expand...
Click to collapse
It is working for me, just copied the files with root explorer to priv-app, restarted and it is up and running.
Thanks @BlazingBullets for providing the files!
PS. the only problem so far is that you can't access the pictures right through the app, i think we need the zte gallery for that.
lian00 said:
It is working for me, just copied the files with root explorer to priv-app, restarted and it is up and running.
Thanks @BlazingBullets for providing the files!
PS. the only problem so far is that you can't access the pictures right through the app, i think we need the zte gallery for that.
Click to expand...
Click to collapse
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
NadavCE said:
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
Click to expand...
Click to collapse
Used SuperSU 2.79SR3.
I can confirm using the files provided works. I have the stock MM camera working with all of it's shooting modes !
Any body have the files in a .zip they can upload? I have no computer access and the few apps I tried on my phone seem to corrupt the files.
First app I tried extracted the 7zip file just fine.
NadavCE said:
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
Click to expand...
Click to collapse
You have to disable the write-protect on the system partition: in a terminal emulator, preferably in TWRP, type out:
Code:
reboot disemmcwp
Erahgon said:
You have to disable the write-protect on the system partition: in a terminal emulator, preferably in TWRP, type out:
Code:
reboot disemmcwp
Click to expand...
Click to collapse
Thanks, that did it. Copied successfully to /system/priv_app, but it doesn't show up after a reboot. When I accessed the folder and tapped the APK, I got "there is a problem parsing the package."
NadavCE said:
Thanks, that did it. Copied successfully to /system/priv_app, but it doesn't show up after a reboot. When I accessed the folder and tapped the APK, I got "there is a problem parsing the package."
Click to expand...
Click to collapse
Maybe the app permissions are wrong?
Erahgon said:
Maybe the app permissions are wrong?
Click to expand...
Click to collapse
Should I give it full permissions then?
---------------------------------------------------------------------------------------------------------------------------
Update: After giving everything (ZTE_Camera folder, the APK, the lib folder, the arm folder, and all the libs) full permissions, the app works. However resolution is limited to 8Mp 4:3 (3200 x 2400). Can anyone else confirm this?

Categories

Resources