[Q] Editing /system/etc/hosts file - restores itself after reboot - One (M8) Q&A, Help & Troubleshooting

Hi
So I am looking at blocking a number of websites - no, I don't really want to do this through app's as a mere uninstall can undo the blocks.
I've rooted my phone, I've given +rw mount to /system/ and I'm able to etc hosts under /system/etc/hosts just fine.
However, as soon as I reboot, the system restores the hosts file to it's original state and all my edits to that file are undone.
Is there anything I can do about this? Please be a bit more specific than just "flash the kernel", thanks.

MohamedH93 said:
Hi
So I am looking at blocking a number of websites - no, I don't really want to do this through app's as a mere uninstall can undo the blocks.
I've rooted my phone, I've given +rw mount to /system/ and I'm able to etc hosts under /system/etc/hosts just fine.
However, as soon as I reboot, the system restores the hosts file to it's original state and all my edits to that file are undone.
Is there anything I can do about this? Please be a bit more specific than just "flash the kernel", thanks.
Click to expand...
Click to collapse
any time i edit anything in system folders i copy it to sdcard do my edits then copy it back and make sure the permissions are set correct i think it rw-r--r-- reboot and it should be good to go... for some reason i cant edit them in that folder but moving it to edit then move it back works for me maybe it will work for you too...

buby78 said:
any time i edit anything in system folders i copy it to sdcard do my edits then copy it back and make sure the permissions are set correct i think it rw-r--r-- reboot and it should be good to go... for some reason i cant edit them in that folder but moving it to edit then move it back works for me maybe it will work for you too...
Click to expand...
Click to collapse
I can edit it no probs. I do my changes, test them out and they all work OK.
As soon as I reboot, everything becomes undone. AFAIK this might be some kernel protection.

The system partition is write-protected.
http://forum.xda-developers.com/showthread.php?t=2701816

Related

how do i edit my build.prop

if i edit my build.prop with astro, on a reboot the changes are lost, the file is marked r-w, so something altering it on bootup, anybody know where the source comes from??
Download Root Explorer and use that. Trust.
tried that, it keeps getting overwritten with some king of backup.
mallard729 said:
tried that, it keeps getting overwritten with some king of backup.
Click to expand...
Click to collapse
If that's the case, then it's a problem specific to the ROM. I haven't tried it on my TP2 but it worked flawlessly on my G1.
Lemme take a look once I get a second.
why cant i find the directory /system/ ?!?! i cant find the build.prop from within windows or winmo?!
norpan111 said:
why cant i find the directory /system/ ?!?! i cant find the build.prop from within windows or winmo?!
Click to expand...
Click to collapse
Because it does not excist in winmo. It only excists in android.
I tried Root Explorer and it workers . I use latest froyo build with lower incall volume kernel .
Can somebody tell me when I delete apps in system/apps folder I delete from data.img or from system.ext2 ?
Same here, I change my build.prop file or replace it and it gets overwritten.
Using the build.prop for protected apps but can't get it to stay.
I am using the latest BLAZEN build from PPCGEEKS/Reefer.
Being an Ext2 file instead of sqsh I figure this would have worked flawless.
I'd really like to download logmein, gbahours, paypal and a few other protected apps. I can't without fixing this build.prop file....
OR
Find some way to get a working fingerprint Google has already approved.
Glad to see I'm not the only one looking into this I have the same problem in my android OS - different phone, but same custom OS. Hopefully this thread won't die - if I ever figure it out I'll be sure to post here as well

Completely hide the virtual keys in A70

I dont know if you guys already know this.
But I just found out that you can completely hide the virtual keys completely, not moving it to the notification bar.
Here's how to do it:
1. Make sure your filesystem is r/w
2. Use root explorer, rename folder /system/board_properties to other name (i just put "z" in the end of the name)
3. Reboot!
I've test it in Urukdroid 1.1b2 and it works like charm. Buttons mode still can be used, but i prefer Button Savior. New version of Button Savior is perfect, no more bug like before.
Try it and tell me if it works!
[UPDATE]
Sibere method (if my method doesnt work) [Post #22]
1. rename or move /system/board_properties folder
2. add this to /data/local.prop:
Code:
ro.board.has_buttonbar=no
ro.board.has_soft_keys=yes
thanks sibere!
btw your kernel for uruk rocks!
Thank you, I will test that afterwards.
But which version is the latest version of button savior? And what's better in the pro version?
And can I undo it, if I rename the folder to board_properties?
Button Savior pro only enable us to change the button arrangement..
The latest version is 1.1.2
Yes, you can undo the change! Just rename it back and reboot..
Why I can't change the name? I've 2.1.08 with chulri's root and r/w filesystem and I can't rename the folder.
What can I do? Should I reinstall the SDE and root?
maybe it only works on UrukDroid because it is fully rooted..
sad to hear that
Now I put the folder to /board_propertiesx but it doesn't work. I could move the folder, and I could rename it, when it was in /.
There isn't a folder in system anymore, but the buttons are still there. Maybe because I don't have Urukdroid?
so you move the folder from /system to / ?
i think it should work..
have you reboot?
Yes, I've rebooted and put the folder from /system/ to / and I renamed it.
But I don't know, why I couldn't rename it in /system but could move it and renamed it in /?...
But is there maybe an other possibility in the local.prop? I tested ro.board.has_soft_keys=yes, but then the touchscreen doesn't work.
I'm still finding other ways to hide the virtualkeys..
Maybe this method only works in UrukDroid I guess..
thank you for trying!
But are there any other guys with stock firmware who want to try it? Maybe I'm not the only one can't hide the buttons.
But what about UrukDroid? Do my files and apps will be removed when I install Urukdroid? Is Urukdroid like the SDE with root?
during Urukdroid installation, there is an option to copy all apps from old firmware to Urukdroid..
but it is not recommended by sauron..
The installation guide can be found @ Urukdroid wiki - http://code.google.com/p/urukdroid/wiki/Installation#Step_one
I think, I will stay with the stock firmware.
But it would be great, if other people with stock firmware would test that, too.
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Edit: After every reboot the Archos-Widget App crashes. I think, it is looking for files in the board_properties folder and can't find them. I freezed this app with titanium-backup and now everything seems fine. Maybe it needs only to disable the archos-widget app without the need to rename the folder to get rid of the buttons.
glimmling said:
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Click to expand...
Click to collapse
nice..
glad to hear that its working
glimmling said:
Hi. It works with chulri's ROOT. I'm on firmware 2.3.26. First it won't work with just renaming the folder. Then I moved the folder to / but it is also still there in /system. I deleted the board_properties - folder in /system, renamed the copy in / to board_properties.bak and moved this one back to /system as a backup. After a reboot the buttons were gone. Hope this helps.
Click to expand...
Click to collapse
I tested the same, but it doesn't work.
I will reinstall the SDE and the kernel and will test it again.
I reformatted my Archos 70, put the SDE on it, but it still doesn't work.
Maybe it's because of the firmware 2.1.08?
Hey. Just recognized, that some games will work now without the softbuttons on my a70. Cut the rope and MonkeyBlast didn't run before the modification and now they do.
Sent from my A70S using Tapatalk
Anyone with Chulri's R/W root, try this:
Go into the board_properties folder, find the file that relates to your model(mine is an A101, so my file was virtualkeys.A101IT), and rename it(add .old to the end of it), and reboot. If that doesn't work, try opening the file as text and delete all the text in it, then save as the original filename(not with the .old extension). Also, make sure you haven't turned off the Soft Buttons through UrukConfig or manual edits. You have to reenable the softkeys(remove them from notification bar) to make them disappear completely with this method.
Another option is to hide them mostly--edit the right board_properties file and set their width to something really small, like 10 pixels. Then they remain usable (though the label will be cut-off), but they take up very little screen space.
Worked for me on Archos 101 Churli's R/W Root
I have the 101 with Chulri's R/W root. All I did was move the board_properties to my sd card and rebooted. Abracadabra, their gone. Renamed to board_properties.bak and put back into the system folder. Rebooted again just to make sure it stuck and it did, no soft buttons.

Can't delete folder - permissions [SOLVED]

Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
warlock257 said:
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
Click to expand...
Click to collapse
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
JoeSyr said:
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
Click to expand...
Click to collapse
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
warlock257 said:
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
Click to expand...
Click to collapse
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
JoeSyr said:
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
Click to expand...
Click to collapse
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
warlock257 said:
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
Click to expand...
Click to collapse
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
simms22 said:
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
Click to expand...
Click to collapse
Found the button, but didn't work
JoeSyr said:
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
Click to expand...
Click to collapse
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
warlock257 said:
Found the button, but didn't work
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
Click to expand...
Click to collapse
Well under normal circumstances, individual files on your sdcard should have permissions rw-rw-r--, and folders have rwxrwxr-x. (For reference, this is read as read, write, execute for Root, System, and Other, with dashes indicating that a permission is denied. So rwxrwxr-x means all permissions are granted to all three groups except for write to Other). This ties into larger aspects of the OS that basically exist to stop individual apps from reading or writing whatever they want without being included in groups.
The fact that you can't do something that shouldn't require elevated permissions, and you're getting that kind of error when you try to execute commands with higher permissions, suggests to me that your sdcard partition is using the wrong filesystem. Sort of sounds like a program tried to treat it like a real sdcard and formatted it to something else, in which case I have a hunch you're going to need to back up your data and do a full reset.
You might get a simpler solution if you ask in the thread for the toolkit you used. It's not something I have any experience with so good luck.
Out of curiosity, are you on Jellybean now? Jellybean changed the address for the sdcard partition, so if the toolkit wasn't updated to reflect this, it seems like the likely place things may have gone wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 06:53 PM ----------
Actually if you want to check if it's using the right filesystem, run the command 'mount' from terminal. It'll give you a bunch of information, probably towards the bottom will be a line that mentions sdcard. Mine reads as
/dev/fuse /storage/sdcard0 fuse [more info about how it's currently mounted]
Yours -should- say that if you're on JB. If you're not, it should say something instead of /storage/sdcard0 (maybe /mnt/sdcard? I forget how it was on ICS). If it says something in place of fuse that may be the problem.
..I actually think mount used to say that the sdcard block was formatted as yaffs2, while everything else was formatted as ext4. Or maybe I just looked up that it was yaffs2 online, not from terminal on my phone? I wonder if this whole thing is the reason why some people seem bootloop-prone when flashing JB roms, if the changes have cut out access to important information about the filesystem, it may be triggering a really long error scan if their sdcard partition is large.
yes, backed up in ICS, and went to Jellybean.
doing a 'mount', I believe the line reads
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The files that have the shield icon have permissions:
rw-rw-r--
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
JoeSyr said:
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
Click to expand...
Click to collapse
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
warlock257 said:
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
Click to expand...
Click to collapse
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
warlock257 said:
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
Click to expand...
Click to collapse
+1 This worked for me as well. Thanks for posting...:good:
Had the same problem. Deleting through the /media path worked.
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+4 You Sir are a genius! Thanks given!
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry to necro this thread almost 4 years later, but I had the exact same issue with deleting a folder on internal storage (Android Lollipop). Regardless if you're still here on XDA or not: thanks for this solution.
So.. Not really a I9250, but I guess my problem on i9100 is the same.
For some weird reason this just happened to WhatsApp directory.. But whatever.
After digging deeper and deeper in recovery, it seems like the folder wasn't own by media_rw group, but root
I just had to run
Code:
chown -R 1023:1023 <folder-path>
For some weird reason neither chown nor ls -l were correctly working when booted on normal system
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Click to expand...
Click to collapse
@Cilraaz, I have no idea if you're still on XDA but after at least a week of intense searching I found your advice which solved my problem! Thank you.
My problem was on i9500 (still) running stock Lollipop. I've been preparing to install a custom recovery, and did a TWRP (2.8.7.0) nandroid backup. Problem was I then couldn't find the TWRP backup folder. It would only show in TWRP's file manager. Root Browser didn't show it with SU privileges, nor ES File Browser and connecting it to the PC didn't help either. It's only after looking in /data/media/0 that I could find the TWRP folder.

Most needed files & folders from 98.30.1

I started this for several reasons.
1) For those who have deleted some system/app(s) & want to manually restore to get ready for the KK ota.
2) /persist dilemma. It is only on our phone yet both recoveries allow you to format it but do not back it up!!!! http://forum.xda-developers.com/showpost.php?p=48941876&postcount=2061
3) /firmware Also not backed up. Both recoveries format it. But Rsd lite will restore it.
I put some very obscure folders here & they may never be needed! DO NOT GO & restore these just because I attached them! If it ain't broke don't fix it!
Get the full zip here http://batakang.com/ftp/?dir=devs/mhous33/XT907/98.30.1
It is the largest one there!
You can extract even a single system/app with Explorer free & paste it with es file to get OTA ready
But some /partitions are only on the phone. Some are created on boot
1 folder not ANYWHERE BUT ON YOUR PHONE is /persist.
Persist permissions are here
http://forum.xda-developers.com/showthread.php?t=2589790
Some wonder why Vzw does not want us rooting?
/Firmware is in the xml/fxz.
/System/app
/Vendor
/Firmware
/System/media.... stock boot animation/Dst animation.
Use Rom Manager fix perms for now. It has never failed me. Set them to all. Then run RM>fix permissions & reboot.
Permissions & ownership need to be set before use.
Rom Manager fix permissions is one good reason to have that app even if it did not WORK on our M, but it does.
Updated op.
So apps from "Data/App" can be deleted and still get the OTA, just don't delete apps from "System/App", is that correct?
VannMann said:
So apps from "Data/App" can be deleted and still get the OTA, just don't delete apps from "System/App", is that correct?
Click to expand...
Click to collapse
You got it.
You, Sir, are the greatest. Have been wondering about this. Finally got root, so I deleted the amazon and some verizon apps fron "Data/App". Thanks!!
VannMann said:
You, Sir, are the greatest. Have been wondering about this. Finally got root, so I deleted the amazon and some verizon apps fron "Data/App". Thanks!!
Click to expand...
Click to collapse
2 things
1)You don't want to "delete" data apps & no need to root to uninstall them. Settings, apps, downloaded, select.... 2)Also the ones you mention sound like system apps?
I deleted them from the Data/App, so they would not be in my app drawer. And all of my system apps are still there, just looked.
Didn't think about disabling them, I got root happy, been to long without it, lol.
aviwdoowks said:
I started this for several reasons.
1) For those who have deleted some system/app(s) & want to manually restore to get ready for the KK ota.
2) /persist dilemma. It is only on our phone yet both recoveries allow you to format it but do not back it up!!!! http://forum.xda-developers.com/showpost.php?p=48941876&postcount=2061
3) /firmware Also not backed up. Both recoveries format it. But Rsd lite will restore it.
I put some very obscure folders here & they may never be needed! DO NOT GO & restore these just because I attached them! If it ain't broke don't fix it!
Get the full zip here http://batakang.com/ftp/?dir=devs/mhous33/XT907/98.30.1
It is the largest one there!
You can extract even a single system/app with Explorer free & paste it with es file to get OTA ready
But some /partitions are only on the phone. Some are created on boot
1 folder not ANYWHERE BUT ON YOUR PHONE is /persist.
Persist permissions are here
http://forum.xda-developers.com/showthread.php?t=2589790
Some wonder why Vzw does not want us rooting?
/Firmware is in the xml/fxz.
/System/app
/Vendor
/Firmware
/System/media.... stock boot animation/Dst animation.
Use Rom Manager fix perms for now. It has never failed me. Set them to all. Then run RM>fix permissions & reboot.
Permissions & ownership need to be set before use.
Rom Manager fix permissions is one good reason to have that app even if it did not WORK on our M, but it does.
Click to expand...
Click to collapse
So is there a package with all the system app .apks somewhere in this mess of links lol, sorry for I'm guessing a very obvious question
Delerios said:
So is there a package with all the system app .apks somewhere in this mess of links lol, sorry for I'm guessing a very obvious question
Click to expand...
Click to collapse
Dl #9 systemAPP!!!

functions root after restarting

Hi, I have the rom European stock "root" I have used several applications to edit the build.prop and delete some files from /system/app and /system/priv-app, with is file explorer give the root permissions, I delete apps and I modify the build.prop and goes well but when I restart the terminal, applications are back in /system/app and build.prop is as if she had not changed. Any idea what it might be?
Your device, although rooted, still has protection against writing to /system.
Flash the file from THIS thread, then repeat what you did, and the changes will stay this time.
thank you very much, worked very well

Categories

Resources