Related
it does it everywhere else except for the system folder. i really want to get this version of pandora off, but it's not doing anything. it worked with my other android devices, not sure why it's happening with this
Do you have the latest version of Root Explorer?
yeah what version of root explorer???
Generally if you can mount R/W in other folders you should also be able to do so in the system folder. You may have already tried this but you may want to boot into recovery and wipe cache and try again. If you have ADB set-up you should also be able to mount the device in R/W by doing the following command: su [enter] mount -o remount,rw -t /dev/block/mtdblock5 /system [enter] if that goes out without a hitch you should be able to delete in the system folder. You can also put that command in to terminal (if you have it) and that also should put the system into R/W. To remount the device in R/O just replace rw with ro. Hope this helps.
2.9.3...wow i'm restarted...i updated and it works now
I have had this issue a couple of times and a simple reboot has fixed it.
Sent from my B.A.M.F. Thunderbolt
Simple to use. Useful for those who want ROOT access via ADB or Device for Backup, etc. It is a modified scripts from Doomlord and some1 in the CDMA threads...
Prerequisites
1) Uninstall all HTC Sync & Drivers
2) Download and install http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
3) Make sure your device Display is set to NEVER TURN OFF & not locked in the lockscreen
Instructions
1. Download attachment
2. Extract to C:\
3. Execute file Step 1
4. Execute file Step 2. If doesnt work, go to C:\files and execute Step 2
5. Remount SD card again from the DEVICE SETTINGS page
This will work for all devices not limited to EVO 3D.
For locked bootloaders (any versions), this will result in a temporary ROOT access, and will be lost after reboot.
Please feedback for whichever H-Boot this works on.
Thanks to our following comrades...
Team Revolutionary with their ZergRush exploit
http://forum.xda-developers.com/show...1296916&page=2
DoomLord with the automated script
http://forum.xda-developers.com/show....php?t=1321582
For the third guy I cant remember where.. maybe the CDMA section with the permatemproot stuff..
With this script, Titanium Backup and Root Explorer will definitely work even on LOCKED bootloaders (will lose root after reboot, just rerun the script)
For problems especially with SUPERUSER FCs, please download and run the .bat file in the UNROOT.zip. This will clean the system of all old temp root stuffs like superusers, etc...
Appreciate your thanks..
i dun understand why but it didn't work as did ur last tool, it always saids adb server out-of-date, re running or sth, it does the same in every step, and when it comes to moving files/manipulating permissions, i just get loads of errors
I'm on HBOOT 1.49.0012
P.S. i cant unlock using HTC Unlock method too no matter how many times i try (i read the instructions carefully and followed them closely) but still got unlock token check failed error......
tomanlam said:
i dun understand why but it didn't work as did ur last tool, it always saids adb server out-of-date, re running or sth, it does the same in every step, and when it comes to moving files/manipulating permissions, i just get loads of errors
I'm on HBOOT 1.49.0012
P.S. i cant unlock using HTC Unlock method too no matter how many times i try (i read the instructions carefully and followed them closely) but still got unlock token check failed error......
Click to expand...
Click to collapse
Reboot your device and try again... see edited post above..
Not sure about HTC Unlock method...
For UNLOCKED evos, it will give permanent ROOT access
For LOCKED evos, it will give temporary ROOT access
If you have problem unlocking, try grabbing a RUU file here and reflash your ROM... maybe factory reset wont hurt either...
it has run thru all the process with success, but when i try to open root explorer it show superuser force close???
looknsee said:
it has run thru all the process with success, but when i try to open root explorer it show superuser force close???
Click to expand...
Click to collapse
Also the Same thing happened to me !!!!
Yup, not working here either.
It says it installs everything ok, but when I go to update the su binary, it force closes out. When I use TI backup, it says I don't have root access.
Hope this helps so that we can at least get temp root. I just want to remove the bloatware!
Thanks for the hard work in any event!
tried this on sensation xl and it worked, root access to some apps like root explorer but terminal says access denied. it seems to unmount the internal sd card which programs need to run and only a reboot remounts sdcard but obviously root is gone after reboot. hope one of the XL devs can use this to create a working solution for our XL
ObsoleteSoldier said:
Yup, not working here either.
It says it installs everything ok, but when I go to update the su binary, it force closes out. When I use TI backup, it says I don't have root access.
Hope this helps so that we can at least get temp root. I just want to remove the bloatware!
Thanks for the hard work in any event!
Click to expand...
Click to collapse
dont need to update the SU binary.. just run the scripts and they are good to go...
however, SYSTEM/APP are in locked partition of the bootloader.. you may need to unlock your bootloader first.. but you may remove some in the Data/app llike gmail and stuffs (i prefer Exchange email than using Gmail app)
shingers5 said:
tried this on sensation xl and it worked, root access to some apps like root explorer but terminal says access denied. it seems to unmount the internal sd card which programs need to run and only a reboot remounts sdcard but obviously root is gone after reboot. hope one of the XL devs can use this to create a working solution for our XL
Click to expand...
Click to collapse
If your bootloader is unlocked, then you may be able to reboot and still have root..
Can I use these scripts to get root access without s-off ?
wasdly said:
Can I use these scripts to get root access without s-off ?
Click to expand...
Click to collapse
S-OFF not required.
FULL ROOT if UNLOCKED BOOTLOADERS
TEMP ROOT if LOCKED BOOTLOADERS
Reason : Files in SYSTEM partition are locked, hence changes made are temporary and will be lost after reboot
Yep full root acheived with u.locked bootloader on HTC sensation xl. Confirmed and working
Sent from my HTC Nexus One using xda premium
Just tried on my HK Evo3D (HBoot 1.49.0012, completely stock, no HTC unlock) and it works. But it took me a few trials to get it working.
For those who have problems with the script (e.g., permission problems during the script) try:
(In the following steps, make sure ur evo3d is disconnected from ur pc when you reboot it. Just to make sure that it is clean.)
1) reboot your phone
2) run the unroot script
3) reboot once more
4) run the root script "Step 1.bat"
5) *** go into the "files" directory ***, and run the "Step 2.bat"
6) at this step you should see the superuser is installed (check the app drawer)
7) go to Settings to mount your sd card
I have managed to root it and run through a titanium backup successfully. Thanks for the great work!
Though temp root is gained, system is still mounted as read-only
tried these, neither one worked:
1) adb remount
"remount failed: Read-only file system"
2) su; busybox mount -o remount,rw /system
No messages, no errors. But still system is in ro mode:
# busybox mount -o remount,rw /system
busybox mount -o remount,rw /system
# mount | grep system
mount | grep system
/dev/block/mmcblk0p22 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
3) su; fixit; busybox mount -o remount,rw /system
Same result.
Seems, after running "Step 1.bat", the /system is temporary mounted as "rw", (that's why the script could complete without warnings/errors). But after Step 2 finishes, /system is back to "ro" no matter what...
Any insights?
ktchana said:
Just tried on my HK Evo3D (HBoot 1.49.0012, completely stock, no HTC unlock) and it works. But it took me a few trials to get it working.
For those who have problems with the script (e.g., permission problems during the script) try:
(In the following steps, make sure ur evo3d is disconnected from ur pc when you reboot it. Just to make sure that it is clean.)
1) reboot your phone
2) run the unroot script
3) reboot once more
4) run the root script "Step 1.bat"
5) *** go into the "files" directory ***, and run the "Step 2.bat"
6) at this step you should see the superuser is installed (check the app drawer)
7) go to Settings to mount your sd card
I have managed to root it and run through a titanium backup successfully. Thanks for the great work!
Click to expand...
Click to collapse
ktchana said:
Though temp root is gained, system is still mounted as read-only
tried these, neither one worked:
1) adb remount
"remount failed: Read-only file system"
2) su; busybox mount -o remount,rw /system
No messages, no errors. But still system is in ro mode:
# busybox mount -o remount,rw /system
busybox mount -o remount,rw /system
# mount | grep system
mount | grep system
/dev/block/mmcblk0p22 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
3) su; fixit; busybox mount -o remount,rw /system
Same result.
Seems, after running "Step 1.bat", the /system is temporary mounted as "rw", (that's why the script could complete without warnings/errors). But after Step 2 finishes, /system is back to "ro" no matter what...
Any insights?
Click to expand...
Click to collapse
1) Reboot phone
2) Connect in DEBUG MODE
3) Run Step 1 script
4) Run Unroot script
5) Reboot phone
6) Connect in DEBUG MODE
7) Run Step 1
8) Run Step 2
You may have previously attempted some other methods, therefore you need to clean the system first...
If your bootloader is LOCKED, you still can gain TEMPORARY ROOT access and run you Titanium Backup (restore settings, data apps).. however, the SYSTEM partition is still locked, which means, whatever changes you done to the SYSTEM partition (like restoring some SYSTEM apps) will be lost after reboot.
I got forceclose with the superuser.
I dont know why, but i guess the root process was finished
Got temp root and su support with untampered stock (vodafone branding), unlocked bootloader HBoot 1.49.0018 on HTC EVO 3D GSM shooteru
System continues to be (expectedly) in ro mode.
Lost access to SD card, had to reboot to use it again...
Permanently disabled without any problems some apps that were bugging me - Thanks
Christoph
bdigitalstudio said:
1) Reboot phone
2) Connect in DEBUG MODE
3) Run Step 1 script
4) Run Unroot script
5) Reboot phone
6) Connect in DEBUG MODE
7) Run Step 1
8) Run Step 2
You may have previously attempted some other methods, therefore you need to clean the system first...
If your bootloader is LOCKED, you still can gain TEMPORARY ROOT access and run you Titanium Backup (restore settings, data apps).. however, the SYSTEM partition is still locked, which means, whatever changes you done to the SYSTEM partition (like restoring some SYSTEM apps) will be lost after reboot.
Click to expand...
Click to collapse
Thanks for your inputs. But my phone was completely stock and I have never tried other root methods before trying this one.
I observed that, /system actually get rw for a short time after the mount -o remount,rw command in step 1. But somehow it will get back to ro by itself. The time is unpredictable in a sense that sometimes step 1 script cannot finish successfully (cannot copy busybox, su to /system because it changes back to ro so quickly).
I know that the SYSTEM rw is just an overlay and all changes will be gone once rebooted. I am asking this because I just wonder if I could playaround and test something like changing fonts without s-off or HTC unlock.
---------- Post added at 05:13 AM ---------- Previous post was at 05:10 AM ----------
-Ho- said:
I got forceclose with the superuser.
I dont know why, but i guess the root process was finished
Click to expand...
Click to collapse
After temp root, go to market and install superuser again. Then run apps like titanium backup and it should work. At least in my case.
---------- Post added at 05:18 AM ---------- Previous post was at 05:13 AM ----------
chw9999 said:
Got temp root and su support with untampered stock, unlocked bootloader HBoot 1.49.0018 on HTC EVO 3D GSM shooteru
System continues to be (expectedly) in ro mode.
Lost access to SD card, had to reboot to use it again...
Permanently disabled without any problems some apps that were bugging me - Thanks
Christoph
Click to expand...
Click to collapse
After temp root the SD card is unmounted, that's why you can't use it. Did you go to Settings to mount the SD card again?
ktchana said:
Thanks for your inputs. But my phone was completely stock and I have never tried other root methods before trying this one.
I observed that, /system actually get rw for a short time after the mount -o remount,rw command in step 1. But somehow it will get back to ro by itself. The time is unpredictable in a sense that sometimes step 1 script cannot finish successfully (cannot copy busybox, su to /system because it changes back to ro so quickly).
I know that the SYSTEM rw is just an overlay and all changes will be gone once rebooted. I am asking this because I just wonder if I could playaround and test something like changing fonts without s-off or HTC unlock.
---------- Post added at 05:13 AM ---------- Previous post was at 05:10 AM ----------
After temp root, go to market and install superuser again. Then run apps like titanium backup and it should work. At least in my case.
---------- Post added at 05:18 AM ---------- Previous post was at 05:13 AM ----------
After temp root the SD card is unmounted, that's why you can't use it. Did you go to Settings to mount the SD card again?
Click to expand...
Click to collapse
Re-do it again only the first time got FC from superuser
After i got the FC, i cleared the data of superuser
Everything seems work
Thanks
ktchana said:
After temp root the SD card is unmounted, that's why you can't use it. Did you go to Settings to mount the SD card again?
Click to expand...
Click to collapse
Yep, it dawned on me and I found that option - now I can use Titan to backup everything
Is there a possibility to add automatic remounting the SD into the script using adb? I am not really familiar with this...
Thanks again
Christoph
I'm trying to push files to /system via ADB. However I'm having problems (getting permission errors). I am running Eclipse 2.0.2, so yes, my phone is rooted, I have su and busybox.
Phone is connected to PC and is set as "USB Mass Storage".
USB Debugging is ON
Here is my CMD log:
Code:
C:\android-sdk\tools>adb remount
remount failed: Operation not permitted
I tried to remount and it failed
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to
'/system/myfile.apk': Read-only file system
I tried to push, and got a READ-ONLY FILE SYSTEM error (keep this in mind)
Code:
C:\android-sdk\tools>adb shell
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
I try to push inside of ADB shell. Nothing again...
Code:
$ su
su
# mount -o remount,rw /dev/block/mtdblock4 /system
mount -o remount,rw /dev/block/mtdblock4 /system
# exit
exit
I go into SU and attempt to remount the /system
Code:
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
$ exit
exit
I go back up to ADB shell and try to push again... same error as before
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to '/system/myfile.apk': Permission denied
I go back to the main command line and try to push again. This time I get PERMISSION DENIED. This error is different than before.
Any help on the matter?
I've read about ro.secure needing to be set to 1, but I need to edit the boot.img in order to do this, correct? Does that require an unlocked bootloader? Is root ADB even possible on the DX2.
Thanks!
I am no expert (don't even know if i know enough to b called a newb) but maybe try a root explorer. I use es file explorer because it's free. In settings check root explorer and mount file system. I received similar errors and this solved my problem.
Sent from my DROID X2 using XDA App
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
wesf90 said:
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
Click to expand...
Click to collapse
I was using adb also and had similar problems. After i changed those settings i was able to push a file. I had to have system mounted.
Sent from my DROID X2 using XDA App
No luck on my end :/
Sorry i couldn't be more help. I am new to adb and may have done more to get it working. I'm sure there's someone else around here that can help u out.
Sent from my DROID X2 using XDA App
Make sure there are no spaces in the file path to your android-sdk folder. Can't say if this is your issue but its worth a shot as it has always caused weird problems with android development since day one.
Sent from my DROID X2 using Tapatalk
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
CadenH said:
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
wesf90 said:
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
Click to expand...
Click to collapse
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
ashclepdia said:
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
Click to expand...
Click to collapse
Thanks for that! It's not quite what I'm aiming to eventually do, but did give me more insight on how the whole adb/shell/su systems work. From inside of su, I was able to mount the /system as RW, however I'm only able to do this from inside of SU. I want to be able to do this from the initial CMD so that I can ADB PUSH from my computer to the phone.
Here's my latest log:
Code:
C:\android-sdk>adb shell
[[TRYING TO MOUNT FROM ADB SHELL]]
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
[[TRYING TO MOUNT FROM ADB SHELL USING BUSYBOX]]
$ busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: permission denied (are you root?)
[[GO TO SU]]
$ su
su
[[MOUNTING AS RW SUCCESSFUL]]
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[[COPYING A FILE INSIDE /SYSTEM SUCCESSFUL]]
# cp framework/framework-res.apk framework/framework-res-test.apk
cp framework/framework-res.apk framework/framework-res-test.apk
[[REMOUNTING /SYSTEM AS RO]]
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
[[ATTEMPTING TO COPY AGAIN, FAILED]]
# cp framework/framework-res.apk framework/framework-res-test2.apk
cp framework/framework-res.apk framework/framework-res-test2.apk
cp: can't create 'framework/framework-res-test2.apk': Read-only file system
#
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Maybe its because im tired but im confused as to why it wont let you push your files if you have remounted as rw. At that point it should be cake. You gained access to system by remounting it as rw successfully already.
Sent from my DROID X2 using xda premium
wesf90 said:
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Click to expand...
Click to collapse
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
I'm no expert in ADB, but I had run into the same issue as you and for me the fix was to go into ADB SHELL , then type SU to get SU access, then type exit twice to get out of shell completely. Then I tried pushing the APK and it worked fine with no read only errors.
This worked for me on my SGS2, could work for you ! Goodluck !
Come to IRC and I can help you with this. http://webchat.freenode.net Come to the #cm7dx2 channel. I'm usually there... Look for the nick(s) Moon|Work|(something), Moon|Home|(something), or MoonShadow-NM. If the (something) says Busy, I might not answer right away. If it says Away, I'm away from the keyboard and you won't receive a response until I return.
Ciao!
Any update
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
I've got a better idea to fix your issue brotha!
From my nexus tappin the talk
<edit post successful>
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
From my nexus tappin the talk
<edit post successful>
jamesh0317 said:
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
Click to expand...
Click to collapse
This won't work with Eclipse since it's not using 2nd init. I asked this question in the Eclipse forums and Nitro responded with the following:
Not without using 2nd init. All of that works due to being able to load its own init.rc which starts services and passes parameters, etc.. during boot time. It is possible to make a stock rom use 2nd init. CM9 will not even have root enabled by default. The only other way to push stuff is to enable root shell prior to pushing.
Click to expand...
Click to collapse
I know that CM7 allows using the adb remount, but that's because it's using 2nd init. I had also asked the question about why CM7 defaults to root shell when you adb shell into it and that's why he mentions how CM9 won't have root enabled by default.
The way I push to Eclipse is to run root explorer on my phone and mount the directory r/w. Then, I can use "adb push" to the phone.
ashclepdia said:
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
Click to expand...
Click to collapse
I think I may have tried that in one of my iterations. Originally I had it rooted with One-Click and then I was having issues with the 2.3.5 OTA update (quickoffice.apk) and at this point I've SBF'ed and rooted it probably 5 times this week so far. Rooted with both One-click and zergRush at various times. Actually I think every time except this last time has been with one-click. So I don't think that has seemed to make a difference for me so far. I can try it again, but if there's any other advice to throw out in the mean time, I'll take it.
Alternatively, I may take the new phone (the first replacement they sent had 2.3.5 on it, but a bad menu key causing the phone to flip out), load Titanium Backup on it, backup all the system apps and restore them to my original phone. Worst case is I have to SBF it again. But that seems like a logical process since I will have two phones available.
Of the 20+ Android phones I have had, and each being rooted and ROM'd, this is the first that I have seen.
On the TPC ROM, when my phone boots, my /system & /etc are mounted by default as Read/Write rather than Read Only. I have no such problem when I flash SAUROM.
I can set it to R/O, reboot, it becomes R/W again.
I asked the question in the ROM thread but got no help. It seems that others don't have this problem.
Why is this and how do I fix it?
Thanks.
Edit: The mount point is /dev/block/mmcblk0p24 for /system and /etc. There are some remount commands in a file located in init.d. Could that be the cause?
I'm no dev, but have you looked at the superuser logs to see what app might be changing r/rw modes? You say when you reboot it changes back. So that makes me think an app you have auto starting is mounting the system rw to make a change and failing to mount back to R.
Go in SuperUser.. clear the logs, set it to R, make note that it saved that change in the log using whatever program you use it to set with... Reboot, check Superuser logs to see what gained root and changed it back.
snovvman said:
Of the 20+ Android phones I have had, and each being rooted and ROM'd, this is the first that I have seen.
On the TPC ROM, when my phone boots, my /system partition is mounted by default as Read/Write rather than Read Only. I have no such problem when I flash SAUROM.
I can set it to R/O, reboot, it becomes R/W again.
I asked the question in the ROM thread but got no help. It seems that others don't have this problem.
Why is this and how do I fix it?
Thanks.
Click to expand...
Click to collapse
jb0nd38372 said:
I'm no dev, but have you looked at the superuser logs to see what app might be changing r/rw modes? You say when you reboot it changes back. So that makes me think an app you have auto starting is mounting the system rw to make a change and failing to mount back to R.
Go in SuperUser.. clear the logs, set it to R, make note that it saved that change in the log using whatever program you use it to set with... Reboot, check Superuser logs to see what gained root and changed it back.
Click to expand...
Click to collapse
Thanks for the suggestion. I removed all the apps that requested SU on boot, but the ROM still had /system as R/W. I don't think it's an app doing it.
Is there a way for me to add something into a boot script to set it as R/O?
Thanks.
I'm still trying to track down this problem.
I noticed that /etc also mounts as R/W by default. I see that both /system and /etc share the same mount point: /dev/block/mmcblk0p24.
I look in init.d and found one file which contained these lines:
#mount fs for faster IO speeds
mount -o remount,nodev,noatime,nodiratime /dev/block/mmcblk0p24 /system
mount -o remount,noauto_da_alloc,nodev,noatime,nodiratime /dev/block/mmcblk0p25 /data
mount -o remount,noauto_da_alloc /dev/block/mmcblk0p26 /cache
Would the first line cause this?
Is there something I can add to init.d to re-mount as R/O?
I'm still curious as to what is causing this. Thanks for any help.
Through trial and error, I found this command works to set /system and /etc to RO:
mount -o remount,ro /dev/block/mmcblk0p24 /system
I added it to init.d, and it works. Once the phone completes the boot, those directories are RO. It's just a patch.
But nevermind that--I am still very interested in the "why" and if there is some other script/boot command somewhere that is causing this.
I'd appreciate some guidance. Thanks.
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
nasenstueber said:
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
Click to expand...
Click to collapse
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
mauricio.valladolid said:
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
Click to expand...
Click to collapse
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
nasenstueber said:
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
Click to expand...
Click to collapse
why dont you just install ext4 recovery and flash supersu.zip?
I really dont get it why are you trying to do it the hard way