File System set to read only

[ochness]

I'm trying to rename some of the "bloatware" on my Fascinate but I'm unable to change the names as I'm getting an error that says the file system is set to read only. Did something happen to my root? I just noticed that I am unable to start Titanium backup either. Did the last update EA28 break my rooting?

I'm new to this so I'm a little confused...any suggestions to fix this would be great.

Thanks.

 

[Landshark]

I'm trying to rename some of the "bloatware" on my Fascinate but I'm unable to change the names as I'm getting an error that says the file system is set to read only. Did something happen to my root? I just noticed that I am unable to start Titanium backup either. Did the last update EA28 break my rooting?

I'm new to this so I'm a little confused...any suggestions to fix this would be great.

Thanks.

How are you trying to rename the files? Are you going directly to them on the phone or are you using root explorer. If you have not re-rooted since accepting the EA28 update, then you are not currently rooted. The EA28 OTA update is stock verizon.

 

[ochness]

Yes I am using Root Explorer...it must be because I have not rerooted since the EA28 update. I will reroot and see what I get.

Thanks for your help.

 

[DroidXcon]

Yes I am using Root Explorer...it must be because I have not rerooted since the EA28 update. I will reroot and see what I get.

Thanks for your help.

Why dont you just upgrade to froyo debloated with odin?

 

[Landshark]

That would be a better suggestion

 

[ochness]

Thank you for all the responses. DroidXcon, I want to go to Froyo but I'm concerned about the issues with Active Sync. I have to get my mail for work from my Exchange server via Active Sync and I'm still running the stock mail client. I guess I really need to download Touch Down and that would probably solve that issue.

So DroidXcon I tried to reroot using your one click FascinateRoot_V02 but I'm getting the following errors:

mount: Operation not permitted
/data/local/tmp/com.sh: cannot create /system/xbin/su: read-only file system
/data/local/tmp/com.sh: cannot create /system/xbin/busybox: read-only file syste
m
/data/local/tmp/com.sh: cannot create /system/app/Superuser.apk: read-only file
system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system

Any thoughts on what I need to do to fix this?

 

[ochness]

Ok, I was finally able to get the root to go through. So now the phone is rooted (I can run Titanium backup), yet I am still unable to rename any of the apps through Root Explorer. I'm still getting an error message that the file system is set to read only.

Not exactly sure what I'm doing wrong, any suggestions would be great.

 

[vi3tboiii54]

Ok, I was finally able to get the root to go through. So now the phone is rooted (I can run Titanium backup), yet I am still unable to rename any of the apps through Root Explorer. I'm still getting an error message that the file system is set to read only.

Not exactly sure what I'm doing wrong, any suggestions would be great.

in root explorer theres a tab top right that enables you to mount R/W to rename that file

 

[ochness]

Thank you Vi2tboiii54...that worked. I should have noticed that button, but I guess I didn't.

 

[gunnermike53]

your name is cool.

 

[vi3tboiii54]

lol thanks i like giving ppl a hard time spelling it out

 

[DroidXcon]

Ok, I was finally able to get the root to go through. So now the phone is rooted (I can run Titanium backup), yet I am still unable to rename any of the apps through Root Explorer. I'm still getting an error message that the file system is set to read only.

Not exactly sure what I'm doing wrong, any suggestions would be great.

Sorry i missed your lasts 2 posts what was the problem

 

[vi3tboiii54]

dont worry droidxcon resolved it for him

 

[uglyyeti]

I tried to reroot using your one click FascinateRoot_V02 but I'm getting the following errorsuld probably solve that

mount: Operation not permitted
/data/local/tmp/com.sh: cannot create /system/xbin/su: read-only file system
/data/local/tmp/com.sh: cannot create /system/xbin/busybox: read-only file syste
m
/data/local/tmp/com.sh: cannot create /system/app/Superuser.apk: read-only file
system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system

Sorry to dig up an old post, but this is exactly where I'm currently stuck - how do I get past this point?

 

[Landshark]

Sorry to dig up an old post, but this is exactly where I'm currently stuck - how do I get past this point?

At what point in the process are you getting this message? What is your ultimate goal in this? Root and stay at stock Eclair, or root and upgrade to Froyo?

 

[uglyyeti]

At what point in the process are you getting this message? What is your ultimate goal in this? Root and stay at stock Eclair, or root and upgrade to Froyo?

Using one click FascinateRoot_V02, after the "Successfully exploited, installing permanent root files and deleting temp files* mount: Operation not permitted"

Ultimate goal is to restore my battery life to more than an hour - want to root to do a Titanium backup and start with a back-to-stock Eclair.

If that works and I'm feeling frisky, I'll make the jump to Froyo.

Thing is, I don't need the bells and whistles - I need reliability - I don't have that now. Had to battery pull halfway through the morning when I couldn't make an outgoing phone call or or send a text - but emails worked fine.

Weird stuff like that is killing me with this phone. This thing was cool for a few weeks - it kicked butt and I know it can again - just have to find my way back to the starting point.

Thanks again for helping me out.

 

[Landshark]

Using one click FascinateRoot_V02, after the "Successfully exploited, installing permanent root files and deleting temp files* mount: Operation not permitted"

Ultimate goal is to restore my battery life to more than an hour - want to root to do a Titanium backup and start with a back-to-stock Eclair.

If that works and I'm feeling frisky, I'll make the jump to Froyo.

Thing is, I don't need the bells and whistles - I need reliability - I don't have that now. Had to battery pull halfway through the morning when I couldn't make an outgoing phone call or or send a text - but emails worked fine.

Weird stuff like that is killing me with this phone. This thing was cool for a few weeks - it kicked butt and I know it can again - just have to find my way back to the starting point.

Thanks again for helping me out.

Which thread were you following to use the one click root? There is an older thread that has outdated files which do not work. If you can let me know which one you used that would be great. Also did you get the drivers from that thread and did you have a choice of 64 bit or 32 bit? I have found the Samsung drivers directly from the Samsung site have worked better for me. Also after you downloaded the drivers file make sure you double click on the downloaded driver file in order to actually complete the installation process. And just making sure you followed the instructions and have usb debugging checked under menu=>settings=>applications=>development. Not trying to insult or anything, just trying to cover all the bases as we troubleshoot this. If you have done all of that, try restarting the phone while usb debugging is checked and the phone is connected to your computer with the usb cable that came with your phone.

 

[uglyyeti]

I've had so many "how to root" threads open today, I don't know which one I started with. I just refreshed my drivers from the Samsung website for good measure - I'm using 32 bit Vista. It's connecting no problem - USB debugging is on. Earlier in the process it has problems with a rage.bin file...

Here's where I'm stuck...

 

[Landshark]

I've had so many "how to root" threads open today, I don't know which one I started with. I just refreshed my drivers from the Samsung website for good measure - I'm using 32 bit Vista. It's connecting no problem - USB debugging is on. Earlier in the process it has problems with a rage.bin file...

Here's where I'm stuck...

Ok, I used one click root back in January, so my memory is a bit fuzzy, but despite the error messages you are seeing, it looks like it went through. After it said complete in the command prompt did you hit CTRL+C, unplug your phone and restart it? If I remember correctly, you will not get that complete message if the root did not work. If you are already unplugged, try it again, and as long as you see the complete at the end, hit CTRL+C, unplug and restart. Your phone is being recognized so the drivers are not a problem.

If you run into any stumbling blocks, check out this thread by DroidXcon and post any questions in there. He is the one who held my hand and walked me through one click root.
http://forum.androidcentral.com/ver...eturn-stock-remove-system-apps-other-how.html

 

[DroidXcon]

delete that oneclick folder you are using and use the one in this thread

http://forum.androidcentral.com/ver...eturn-stock-remove-system-apps-other-how.html

for some reason you are missing files,
in the first pictures it says pushing files, there are 5 files. yet under it you only see 3 packets of data moved. so it is missing some stuff

Edit: If you try again make sure you pull your battery before you do