I've been trying to modify my build.prop to enable carrier billing on my T-mobile One S with Zen Rom 1.05, but every time I reboot it reverts back to the one that came stock with the rom. I'm mounting R/W and I've copied the file onto my SD card after editing it to be sure it was actually saving. The copied file shows all of the changes, so I'm sure it is, but as soon as I reboot, the one in \system reverts. I've tried build.prop editors from the market, and editing it from root explorer's text editor, and it's all the same. Any ideas?
Thanks!
Related
I just applied Daoist's CWM stock ROM update (should still be rooted, right?). It came up first time.
Then, I modded my build prop (set dpi to 120 because I like it that way). But maybe I screwed up the file name in Root explorer, because now I'm in a boot loop and if I try ADB PULL /system/build.prop it says "file not found."
I can't get SU through adb, so can't push build.prop to /system. ADB remount returns an error. permission denied. Transformer won't boot, so I can't do anything from it.
I CAN get to cwm, and have been trying to create an update.zip that will just copy build.prop to /system, but everything I have tried quits with "install aborted" message.
What can I do?
restore a nand and dont try and **** with it again, lol. no but really, restore a nand and then copy your build. prop and make a flashable zip and place on your sd card in case it happens again, so you can just flash it in cwm.
Resolved..
Well, why go back when you can go forward?
I went ahead and installed the Prime ROM. Looks like it is eating all my currently installed apps.
Y'all should know, though, that if your system can't find a build.prop it won't start. You can ADB to it and have a rudimentary set of commands, but your ability to significantly alter anything in your file system will be prohibited.
Lesson learned.
glg
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
mrevankyle said:
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
Click to expand...
Click to collapse
That is true. I had backups. But without a build.prop, the virtual machine won't start. There is no way to do a file operation to replace the backup. At least none that I found. I had to flash the whole system.
glg
I recently rooted my Inspire and loaded CM7.2 RC1 and I was just trying to increase my download speeds by editing the build.prop file. I'm using explorer v1.1 to get to the system folder and then editing the build.prop file using the text editor. When in explorer it says r/w and I can actually edit the file and save it but it never seems to actually save the changes even though it says it did. I tried using mount/system(rw/ro) to ensure that it was actually mounted but I am getting the same result. Any suggestions would be appreciated!
ES file explorer
Hi, I use the es file explorer, when you open it up hit "menu" scroll to bottom and make sure both root settings boxes are checked, then restart app. You should be good to go.
I recommend ROM Toolbox. It has a root file explorer and many other tools which come in handy on a rooted phone.
I recently Wiped my Phone completely and decided to Re-Flash Viper 1.2.1.
I noticed a problem prior to re-installing but thought nothing of if since it wasn't crucial at the time.
In Root explorer, I am able to delete [i normally delete boot animations] system files but not add where I need to add. Example, I wanted to add a ringtone to my system/media/ringtones folder. I normally [for the last six years] could just copy and paste such files using a root file manager.
However, when I any these files to for example /system/customize/resource/ it doesnt add it. BUT IT DOES rename the file and save it under a dif folder.
Example. Tried copying-copy to-moving to "androidtwirp.mp3" from sdcard to /system/media/notifications and a message pops up saying"notificationsandroidtwirp.mp3 successfully copied-moved to" and it saves notificationsandroidtwirp.mp3 to /system/media/ and it stays there. retrying from that location only results in "notificationsnotificationsandroidtwirp.mp3".
So not only does it rename the file but it saves it in the wrong location. I am at a loss for word. I tried the basics to tryand fix this but i cant seem to hit it on the head.
Thanks!
Edit: Not updating Super SU app, file explorer seems to have worked. Will attempt to duplicate problem to see what actually caused.it.
FOUND IT!
Updating my ES File explorer broke my system writing ability. DO NOT UPDATE is because when you do...
Any file you move, copy/paste to the system will not work properly.
This first happened when I tried to copy and paste a boot animation after I updated ES root explorer. It would rename whatever file i was trying to paste/move/copy over and save it under a sub folder.
example.
copying a ringtone [i.e. androidtwirp.mp3] from SDCard to System folder, the path is /system/media/audio/ringtones/ and it would rename it "ringtonesandroidtwirp.mp3" and save it under /system/media/audio/.
So basically not only was it renamed [which i didnt want it to be] but it would save it to the folder before the actual folder i needed it to be in, plus it would corrupt the file deeming it useless.
moving "ringtonesandroidtwirp.mp3" into the correct folder would only result in "ringtonesringtonesandroidtwirp.mp3"
this happened across the board with all files being moved around
The ES File Explorer version 1.2.1 comes with works flawlessly so don't update it.
I uninstalled ES [also any folders in SDcard related to it] and downloaded JRummy's root explorer and everything is back to normal except i have to reboot the phone to see files [like ringtones and notifications] that i added to the system.
I think it has something to do with our devices having an unlocked bootloaader, but still S-ON. There's S-OFF in the Dev section now if you really need to write to the system folder a lot.
I came from the Vibrant so I know what you're going through
Yeah, im on a low hboot so s-off might not be in my plans since I can practically flash what I want but it was ES file explorer, when I updated the apk the root permissions broke when writting to the system. I emailed the dev and they said they'd have it fixed on the next update.
echo en Android
Can someone help me out with the Multi-view hack to add all apps?...I just used the editing method for adding all apps to the multi-view window. All the steps went fine, but now that I'm done I can't get Multi-view to work AT ALL! I enabled it, held the back button down over and over and it does absolutley NOTHING. I am on stock 4.1.1, rooted with unlocked bootloader and I have a nandroid backup that I made just before attempting this, but since everything else on my Note 2 is still working I'm waiting and hoping that someone out there knows what's going on and has a fix for it.
Here are the steps that I took:
----------------------------------------------------------------------------------------------------------------------------------------
1. Download modified odex file (multiwindow.zip) by hairdewx (mirror), and extract services.odex FlashBarService.odex files. After that copy both files into your device.
2. Get file manager app that can open the system apps, such as ES File Explorer or Root Explorer that can be found on Play Store.
3. Mount the system partition as Read/Write (R/W).Mount to R/W and Replace Files
4. Copy and replace “FlashBarService.odex” to “/system/app” folder, as well as “services.odex” to “/system/framework” folder. If you have difficulty to replace services.odex, reboot your device. In case you experiencing bootloop after replacing services.odex, then you need to pull out and reinsert the battery, if the bootloops remains, just flash the root image with ODIN to fix it.
5. Reboot your Galaxy Note II.
6. Open the file manager again, delete “com.sec.android.app.FlashBarService” from “/data/data” folder, then reboot once again.
7. (Optional) Open “/data/data” folder again, if you find the “/flashbar” folder, just delete it.
Now you should have been able to add any apps to the Multi Window bars on Verizon Galaxy Note 2, and also run two applications at the same time (MultiView). If you can’t find an edit button, it’s likely that you on 240 DPI, just switching back to 320 DPI, edit button will reappears.
-----------------------------------------------------------------------------------------------------------------------------------------
That's it. I did all of these steps with no problems but as mentioned, now I can't get Multiview to work at all. I have tried restarting several times and also did a battery pull but no luck. Please HELP!
Edited...PROBLEM SOLVED AFTER FACTORY DATA RESET. Thanks.
Anyone experience the above before?? Mine disappeared somehow....
Edit: I did the changes many times to cfm this is happening to mine. Changing the edited build.prop back to 480 does not solve this. Only way is to use back the original build.prop.
I am sure nothing else is edited so it's quite strange this is happening.
Did a hard reset didn't quite solve the problem. When the phone restarted with the sim, it defaulted to 4g. But once I enter the network selection menu, it jumped back to 3g again as there was no 4g selection available.
I realize what is the problem. I was using the built in editor of root Explorer to change the lcd density in build.prop. When I make changes and reboot, the lte options in network settings will disappear. Using back the backup build.prop solves the issue.
Can anyone verify this?
scpion said:
I realize what is the problem. I was using the built in editor of root Explorer to change the lcd density in build.prop. When I make changes and reboot, the lte options in network settings will disappear. Using back the backup build.prop solves the issue.
Can anyone verify this?
Click to expand...
Click to collapse
Yes I can. I had the same issue after editing bulid.prop with editor from Root Explorer. The only way to edit your build.prop is to copy it to Downloads folder on storage and than copy it to your PC to edit it. After editing copy it back to Downloads folder and later with root explorer to /system folder and change permissions to rw-r-r. And reboot. That works everytime.