I'm running the stock ROM, rooted, and just with a few mods (back button menu, 1% battery, remove ATT bloatware).
Whenever I make a change to the host file at /system/etc/hosts, after I reboot to apply, it's been reset to the 60-byte default host file, wiping my changes out. Yes, I am mounting /system R/W before making my changes. It doesn't matter if I remount /system back to R/O before rebooting, the file still reverts. Even if I set the permissions on the file to read-only after making my change, it still reverts.
Is there anything I can set to make my modified host file stick? Or is /system always reloaded?
I do see that the Cognition ROM has writable /system as one of its features, suggesting that the stock ROM does something like this with /system.
There's a kernel mod you can flash over on the international side that disables the stock kernel protection, or you can flash one of the custom kernels that have no such protection.
gunnyman said:
There's a kernel mod you can flash over on the international side that disables the stock kernel protection, or you can flash one of the custom kernels that have no such protection.
Click to expand...
Click to collapse
Thanks.
Flashed Cognition ROM and my host file stayed modified after a reboot. May have been more heavy-handed a change than required, but it worked.
:laugh:use root explorer to make the host's file will be read only and try again
Related
Cannot get r/w access with root explorer after install dl30 and using current superuser/root files.
I always had it before, updated all the files, when I go into root explorer it will not change from r/o to r/w. Its upsetting me as it worked before.
easiest fix is to download "Mount /system (rw / ro)" by Beansoft from the market. open it and set it to mount /system as rw on boot, give it root permission, and you're set.
also please remember to post questions (even if they seem development related) in the general section, or in the existing topic for the rom you're using. Thanks.
This didn't work, still cannot get /system to give any type of r/w access. What could be wrong?
Did you have Voodoo installed beforehand?
Don't doublepost!!!
http://forum.xda-developers.com/showthread.php?p=11384883#post11384883
I have the exact same issue. Just talked it over with Adrynalyne.
You are going to have to download an All-In-One Odin Package such as
http://forum.xda-developers.com/showthread.php?t=867648
Then, you're going to have to start over and flash your CWM Recovery from jt
http://forum.xda-developers.com/showthread.php?t=942021
Then you Odin flash the modem of the ROM that you want to install, then you use CWM to flash the ROM that you want to install...
Make sure that you do to not flash using Phone. Use PDA option in Odin.
Apparently, it's a corrupt dbdata partition that is causing it. This can happen occasionally when installing VooDoo... Just another reason to stay away from VooDoo...
I have installed the Deodexed 407 Rom, and installed Streakmod Recovery and also installed superuser.zip, so in theory, from what I have read my streak should now be rooted.
But when I try and edit a file, the build.prop file in /system with Astro File Manager I alter some of the settings and save it, but when I reopen the file the changes had not been saved. I have tried seeing if I can change the permissions on the file, but without success.
I would be grateful if someone could assist me in where I am going wrong, hopefully it is something simple or a wrong setting that I am not quite doing correct.
spanner44 said:
I have installed the Deodexed 407 Rom, and installed Streakmod Recovery and also installed superuser.zip, so in theory, from what I have read my streak should now be rooted.
But when I try and edit a file, the build.prop file in /system with Astro File Manager I alter some of the settings and save it, but when I reopen the file the changes had not been saved. I have tried seeing if I can change the permissions on the file, but without success.
I would be grateful if someone could assist me in where I am going wrong, hopefully it is something simple or a wrong setting that I am not quite doing correct.
Click to expand...
Click to collapse
You have to mount the system as ReadWrite and there was no need for a new thread. You should've posted in the rooting thread
Sorry, for not putting it in the rooting thread, but didn't want to clog a general rooting thread with a specific problem.
I have solved this now thanks, but not with Astro File manager as I still cannot seem to change the permissions with that app, but used advanced tools app instead.
Thanks again anyway.
Yes i had same problem trying do root operations with file expert. I used root file explorer instead. Weird thing being that even with rooting permissions ticked file explorer failed.
For most root-enabled browsers, just enabling root permissions won't give you write access. You'll need to find a second option to mount the /system directory as read/write. That's normally somewhere in the Settings menu or on the directory's long-press menu.
ChicoKiri said:
For most root-enabled browsers, just enabling root permissions won't give you write access. You'll need to find a second option to mount the /system directory as read/write. That's normally somewhere in the Settings menu or on the directory's long-press menu.
Click to expand...
Click to collapse
It's mainly dependant on the kernel, all custom kernels automatically mount system as RW and all stock kernels mount it as RO
At least root explorer tells you that it's read only if you attempt to modify it without remounting, I havnt used ASTRO in a long time so I cant comment on that
Root explorer better for me
Sent from my PC36100 using xda premium
I had the GLaDOS kernel installed, but I changed to Eugene's, but the Aperture boot animation is still here... How do I reset it back to the normal stock ICS animation?
Or do I really have to flash my custom ROM again?
You can pull the bootanimation.zip from your ROM (I'm not sure where it's located for you, sorry). Once you have it on your SD card, copy it and then override the one currently there using Root Explorer. Just to be safe you can rename the current one to bootanimation.bak or whatever you'd like. Be sure to set permissions on the file to match the old one (mine are rwxrwxr-x, meaning everything is checked except write for "others", but yours could be different). With Root Explorer you can do so by long-pressing the file and selecting "permissions" from the menu. It should be similar for any other root file explorer.
You can reflash your ROM, but you'll lose any other mods you've made and will need to reflash your kernel if it's a custom one. To reflash without losing data, just wipe cache and dalvik then flash.
Supersonic Evo 4G | MIUI | Tapatalk
I'm noticing that changes I make to /system/bin get undone upon reboot on stock 5589 software.
My particular change is the wpa_supplicant ad hoc fix.
I used terminal to rename the old file to wpa_supplicant.back and put my new file in.
It works fine, I can connect to ad-hoc wifi fine, until I reboot. After reboot, the backup is gone, and the old file is back to it's original spot (breaking wifi).
I'm using temporary root under z4root if that makes a difference.
Anyone have any ideas, is there some type of "system restore" functionality in 5589 that refreshes system/bin upon startup?
Any workarounds if I want to remain on stock?
ml_boston said:
I used terminal to rename the old file to wpa_supplicant.back and put my new file in.
Click to expand...
Click to collapse
You shouldn't replace binaries while they're being used. Install CWM and use it to do the switch. Make sure you remount /system read-only afterwards.
The file wasn't in use, as I was able to run adhoc wifi (meaning the replace worked) until I rebooted.
I think I found the problem, from this link:
There is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1 unbeknownst to you. Watch out.
Click to expand...
Click to collapse
So I've got to learn how to build an img file with my one swapped file. Or perhaps (will try soon and post back), deleting the recovery.img file will also do the job.
ml_boston said:
The file wasn't in use, as I was able to run adhoc wifi (meaning the replace worked) until I rebooted.
Click to expand...
Click to collapse
Unless the wifi was switched off or put into airplane mode or something like that as the default state, I assure you that the wpa_supplicant binary would've been in use. It's how modern Unixes work.
I think I found the problem, from this link:
Click to expand...
Click to collapse
Most of the specific details in that link a) either isn't relevant to your specific problem and/or b) does not apply to the gTab and the ROMs that run on it. For example, in the quote you pulled:
There is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1 unbeknownst to you. Watch out.
Click to expand...
Click to collapse
Here,
1. There is no /system/recovery.img file on the stock ROM.
2. The quote talks about restoring "recovery"--not "system". Plus, those 2 partitions have radically different sizes (16 MB max for "recovery" and 200MB max for stock "system"). Think about what would happen to the boot times if a 200MB image had to be restored on every boot.
So, my advice is unchanged. Install CWM temporarily, then use it to switch the binary, and finally, sync and unmount /system before rebooting out of CWM. You can always restore the stock recovery using the recovery.img file in the 5699 update zip file from within CWM.
How do I add scripts/tweaks to my rom properly? For ex. I want to add the operation kill joy script to my rom which is build from kitchen.
As a general rule of thumb, you would need to mount the /system as RW and the script would be placed into /system/etc/init.d folder with the correct permissions set and then reboot to take effect. Depending on the phone and rom, there might need to be other things done.
es0tericcha0s said:
As a general rule of thumb, you would need to mount the /system as RW and the script would be placed into /system/etc/init.d folder with the correct permissions set and then reboot to take effect. Depending on the phone and rom, there might need to be other things done.
Click to expand...
Click to collapse
No, I mean from a dump rom that I'm editing right now thru the android kitchen. I can add tweaks thru copying those files to the system but I dont feel the tweaks when I flashed them with the rom itself.
Clairelicious said:
No, I mean from a dump rom that I'm editing right now thru the android kitchen. I can add tweaks thru copying those files to the system but I dont feel the tweaks when I flashed them with the rom itself.
Click to expand...
Click to collapse
Gotcha. You might find this article helpful then:
http://apcmag.com/how-to-make-your-own-android-rom-part-4.htm