I have searched the entire forum and haven't found the answer to my problem...I have even asked in the rom specific thread (where other people have had a similar problems) but my question (and theirs) just gets overlooked!!
So here it is.
I have both radio S-off and the End Hboot and have flashed three different custom roms on my HD (the Core Droid, Revolution HD and LeeDroid) all giving me the same problem.....I cannot set the system as r/w using apps such as Root Explorer and SUFBS!
I tried entering the mount command by itself in a terminal on the phone and I get:
# mount
mount: no etc/mtab
I can however mount the system from adb shell by inputting: mount -o remount,rw /dev/block/mmcblk0p25 /system
but that isn't really a solution!
I have a nandroid backup of my original stock rom which I have rooted and I can mount the system fine using root explorer and do not get this 'no etc/mtab' message when I type mount in the terminal.
I find it odd that it occurs with three different custom roms but not on my original stock rom so maybe it could be the way I flash the roms? ...I always use the Full_Wipe.zip with CWM recovery which formats the boot, system, data and cache partitions and then I apply the rom.
I've been pulling my hair out over this...and I know it must be something simple, but I've been stuck with this problem with no solution for a week!
Does anyone have any ideas?
EDIT: It turns out that some of the custom roms have limits in place that prevent editing the system and therefore were causing errors. Have tried the Cyanogen rom and have not encountered the errors/restrictions so it was definitely due to those custom roms. Not really a solution, but found the 'cause' of the problem.
Hmmm....looks like I'm the only one with this problem. Has no one else had anything similar?
your not the only one, i hbave had this too, this prevents you from removing apps doesnt it, now is it the 1.72 rom or the 1.34 rom
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
mariosraptor said:
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
Click to expand...
Click to collapse
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
fkofilee said:
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
Click to expand...
Click to collapse
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
after doing what you have to do you can go again to Root Explorer and remount as read only.
fl4r3 said:
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
Click to expand...
Click to collapse
mariosraptor said:
after doing what you have to do you can go again to Root Explorer and remount as read only.
Click to expand...
Click to collapse
I guess thats the best option for now...not a complete solution, but a work around that doesn't require a pc at least.
Would still be good to find the cause and fix it!
I've got the same issue! Are you sure the error you receive is 'no etc/mtab' and not 'no etc/fstab'?
Anyway I've been using the App 'Mount System (rw/ro)' as my solution for now and it works a treat. Still, as you can imagine it is not a permanent solution!
The only thing I feel may have contributed to the problem was my original root attempy via Visionary failed and I had to wait until the R13 before I could unroot and root again. Possibly something got borked along the way. Did you have any similar issues?
Will be keeping my eye on this thread and if I do find a solution I'll let you know.
Regards.
It’s definitely a ‘no /etc/mtab’ error.
When I rooted I used Visionary r14 and the only hiccup I had was that it didn’t permaroot on the first try so I had to redo it.
It’s odd that my nandroid backup of stock doesn’t give me the error and its only the custom roms that do! I have a feeling it might be something to do with an incorrect/incompatible Busybox installation with the custom roms...
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
cattleprod said:
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
Click to expand...
Click to collapse
I've tried looking for /etc/mtab in my stock rom but its not present..I don't think its a physical file thats why it can't be copied....
But I think you may be right about it being an app based problem...just tried LeeDroid V1.3 (based on 1.72 rom) out of curiosity and root explorer still wasn't working. I then wiped again but installed root explorer fresh from the market instead of titanium backup and it is now working!! YAY!!
However, SUFBS still does not work and returns 'no /etc/mtab' when I type 'mount' in its terminal and reinstalling (either from titanium backup or fresh from the market) does not make a difference. Since root explorer is now working I believe that the dev for SUFBS needs to update his app maybe?..or is there still something wrong with my system?
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
fkofilee said:
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
Click to expand...
Click to collapse
Ahhhh, if thats true then it makes sense! Thats why the custom roms were giving me trouble but not my rooted stock rom and why adb commands from a pc work. I guess its a precaution but still an inconvenience...especially when I want to make changes/do something away from the pc.
......the question is: is it true? are you 100% sure the custom roms don't allow changes?
its 100% true, well most of the new ones anyway, CM was built from open source code and is completly there creation BUT
custom roms created from stock are basically modded ROMS
Just tried Cyanogenmod rom 6.1.2 and have had no issues at all! So it seems fkofilee is right...some of the custom roms just don't allow changes to the system.
So not really a solution but atleast found the 'cause' of the problem.
I noticed you said you used the full wipe .zip has everyone else used it ??? As I did not use it the first Rom I flashed was leedroid 1.2 and then 1.3 the only thing I used was cw recovery wipe/factory reset and my root explorer never failed can toggle between the two and when I first booted all my apps synced back via market did not use titanium backup not keen on it also I've read a few posts problems with titanium not restoring apps also read somewhere the full wipe zip doesn't always work right maybe its the wipe and titanium that causing it
Just a thought
Sent from my leedroid v1.3a DhD via xda app
I use full wipe. Zip but I never have problems with root explorer. Been using more than 1 Rom. ( Modaco r 2, leedroid 1. 3, Hd revolution. And also I have modded them a lot to look aosp.
Sent from my LeeDroided Desire HD
Related
Hey Guys.
I "rooted" my HTC Desire by T-Mobile using Unrevoked3.
Then i flashed a Pre-Rooted Froyo:
http://forum.xda-developers.com/showthread.php?t=773997
Now i wanted to use the "Root Explorer" to remove Apps like "FriendStream" and stuff.
I was able to delete them, but the still keep running.
Then i rebooted and they are still there although deleted with Root Explorer and Super-User permit.
Is it possible that unrevoked is just a "*****-root" i can just use to flash Images but not for mounting /system (R/W) and removing Apps?
What can i do now? Hope u can help me
erichbitch said:
Hey Guys.
I "rooted" my HTC Desire by T-Mobile using Unrevoked3.
Then i flashed a Pre-Rooted Froyo:
http://forum.xda-developers.com/showthread.php?t=773997
Now i wanted to use the "Root Explorer" to remove Apps like "FriendStream" and stuff.
I was able to delete them, but the still keep running.
Then i rebooted and they are still there although deleted with Root Explorer and Super-User permit.
Is it possible that unrevoked is just a "*****-root" i can just use to flash Images but not for mounting /system (R/W) and removing Apps?
What can i do now? Hope u can help me
Click to expand...
Click to collapse
the desire dosent have an unlocked spl yet so even a rooted desire dosent have r/w access to /system/ when booted, there are two ways around it, either delete the apps using adb in recovery mode or flash a rom that utilises the new file overlay system that will give you r/w access to /system/
It more or less sounds like you don't understand the meaning of being root. On a system like android, running something with root or superuser permissions will normally allow the app or command to have full access and rights. This is gained by adding a binary called su and the superuser app, which is for controlling which apps gets root access. So actually unrevoked or any other root methods is not about gaining root, but about being able to put these files on the system partition, which it also does.
Now this is not the case on newer HTC handsets, because they have nand protection, which prevent write access to /system even though an app is run with root access. this is controlled by hboot, and in order to allow rw to /system, we will need an s-off hboot. This is not yet available, but the unrevoked team is working on it.
So the socalled "*****" root just shows me that you don't know, what you are talking about
edit: for now if you want to remove apps, you will need to flash a new rom, where you have removed the apk files yourself, or you will have to learn some adb commands, which you can use to edit system partition while in recovery with rw access.
Using adb in Recovery to backup/remove them is very simple (for removal i.e adb shell rm dir/name.apk) however many default apps break other workings and/or cause confusing unexpected errors if removed. I learnt first hand when removing many pre-installed apps. So be careful and always backup.
-----------------------------------
- Sent via my HTC Desire -
AndroHero said:
there are two ways around it, either delete the apps using adb in recovery mode or flash a rom that utilises the new file overlay system that will give you r/w access to /system/
Click to expand...
Click to collapse
How can I tell which roms utilize the new file overlay system? Im also having the same problem especially with programs starting up after I've disabled them.
shaliru said:
How can I tell which roms utilize the new file overlay system? Im also having the same problem especially with programs starting up after I've disabled them.
Click to expand...
Click to collapse
We have s-off now. Look for that, or use adb.
Sent from my HTC Desire using XDA App
Hi everyone
I know this thread might look like a dublicated thread, but its not
I searched the forum for similar threads but I couldnt find similar, so I posted it.
I've rooted my HTC desire and tried removing the original apps(like stock,footprint,...etc ) but I couldnt.
After rooting I tried the following apps and got those messages :
File Manager : No suffessient permission
Root Explorer : can't be deleted because the file system is read-ony.
Uninstaller for root : Root access is granted,Can't uninstall app, an unknown error occured.
Any Ideas or apps that could help me in getting rid of such apps
You need to be s-off to remove apps from the system partition while booted, you can however remove the apps in recovery with ADB. Also know that you won't gain any extra space in data because that are different partitions.
Sent from my HTC Desire using XDA App
TheGhost1233 said:
You need to be s-off to remove apps from the system partition while booted, you can however remove the apps in recovery with ADB. Also know that you won't gain any extra space in data because that are different partitions.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks alot
To be frank with you, I'm a newbie to android
I'm not that much aware of system commands or programming
so my question is : is it that much complicated using the ADB method or any biggner can do it
Follow this tutorial.
You can also modify the zip before flashing it no ?
Yes, which is also the better way but if you don't want to flash a custom rom that's not a option.
Sent from my HTC Desire using XDA App
I have flashed a custom Sense ROM that includes certain original apps, but now if I want to remove them can I just reflash the ROM but just removing the apk files before flashing?
Will I lose any data, settings, etc?
[EDIT: Nvm, found the answer]
TheGhost1233 said:
Follow this tutorial.
Click to expand...
Click to collapse
Thanks a lot for the help
I'll give it a try and get back to you for the final result
Same problem here.
Seems like for HTC Desire, you need to have S-OFF and NAND unlocked.
Google it and let me know if you made any progress, I'm trying too.
Hi there. You do not need to be S-Off-ed to remove system apps. You need to have write permissions for the system partition. A lot of apps can do that for you as long as you have superuser installed and you have granted access to the application. Personally when I was removing my sys apps i used Sysapp remover. I have even done it with titanium backup but I am not sure if it had the option to give you write permission for the system partition. Just check a some sysremoving apps and at least a couple will have that option.
COOLBGT said:
Hi there. You do not need to be S-Off-ed to remove system apps. You need to have write permissions for the system partition. A lot of apps can do that for you as long as you have superuser installed and you have granted access to the application. Personally when I was removing my sys apps i used Sysapp remover. I have even done it with titanium backup but I am not sure if it had the option to give you write permission for the system partition. Just check a some sysremoving apps and at least a couple will have that option.
Click to expand...
Click to collapse
AFAIK, not for the Desire. I was checking some sys app remover programs - all of them stated you need to be S-OFF if you have a Desire.
But It is true, you can remove apps even if you are S-ON. Using ADB.
davebugyi said:
AFAIK, not for the Desire. I was checking some sys app remover programs - all of them stated you need to be S-OFF if you have a Desire.
But It is true, you can remove apps even if you are S-ON. Using ADB.
Click to expand...
Click to collapse
I never S-Offed my Desire and also I do not know how to use ADB but still as I said some apps offer you to gain write permissions on the system partition and they will do the trick. I can guarantee you that because this is how I did it
What program was it?
RootUninstaller
https://market.android.com/details?id=com.danesh.system.app.remover
These did not work, when I was S-ON.
personally i've used 3 methods:
adb: works but is such a faff to type in all the apk names exactly!
delete from .zip: easiest way so they're never flashed in the first place. remember not to unzip the ROM, just delete them directly in winzip or similar program before flashing.
if you're S-OFF: i recently took the plunge, was scared of bricking but turned out to be much easier than i thought. then used root explorer to directly delete fancy widget after flashing Leedroid no-sense patch.
Do the s-off procedure at alpharev.nl - this takes less time than rooting (or it did for me) and then you can just delete the apps using Ti Backup or root explorer.
You might also want to flash one of the custom partition tables at this site to give yourself more room for apps. I have about 250mb free (internal) and nothing on SD - this means apps run faster and is apparently better for the battery!
I have a problem when trying to change the lock screen sound in MIUI XJ 1.2.25.
I can copy the new lock sound to /system/media/audio/ui allright, everything seems fine.. But when i reboot, the sound (and all the files) go back to before i copied the new sound(s)..
I'm thinking it might be a "signing" problem, but i'm completely lost in how to do this... So a step by step guide would be nice, as i'm rather new to this whole rooting business
Been using root explorer and/or adb to push the files.
(Btw, when i try to change permissions for the new sound file, nothing happens after i click "ok" in roote explorer.. Any ideas?)
Oh, my device is a HTC Desire
Thanks!
Of you are S-ON, that's your problem. You must push the files via ADB, while in recovery to make them stay there after reboot.
Sent from my customized HTC Desire using TTP
Ok, I know i'm S-On.. I tried pushing the files via adb, which worked fine, but after reboot things were back to normal.. I tried to install a soundpack from a zip (via recovery), that worked well, the sounds didn't revert back to the original. But when i tried to do it manually, things get screwed up
Perhaps the zip file change some settings somewhere that i don't know of?
Guess i'll go S-off then, then i can also change the splash screen
-------
After some more research, i now understand that the soundpack zip-file i installed must have been signed, to pass the HTC security feature...thing.. Thus being able to install new system sounds without the phone reverting back to the original.. Isn't that right?
As I said, files remain there if you flash via ADB while in the custom RECOVERY! Not while the phone is booted & running. At least for me it's working.
Yeah i tried that, but with same result..
Actually, the reason i used adb in pushed the files while in recovery mode, was because i had some issues when using root explorer on the phone.
Sometimes (but not everytime!!?) i couldn't copy/paste the files from my SD card and into the system, it gave me a message about not having enough free space. Which was complpetely wrong, as i generally had about 90-100mb free space. And nothing would happen when i tried changing permissions on the files either.. I read some where that updating busybox could fix the problem with the free space issue, so i did.. Then i could copy the files, but then they wouldn't show up in the destination folder.. Really weird.. So i thought adb was the way to go..
As said, everything went fine until reboot. the files i pushed would still be there, but the originals would have come back too. Meaning i'd have 2 files with the same name, but different sizes, dates and permissions..
It makes much sense with the security feature, as you say..
I'm seriously considering to try an S-off procedure, to get full root and full control
Well then IDK, if I remove a file then push the version I want -it always stay there (via ADB in Recovery).
That's why I never tried S-Off, since I don't need resizing the NAND partitions, and copying to system via ADB always works.
Got tired of experimenting with this, so i made my phone S-off using Virtualbox method. Now everything works perfect!
I can change files and permissions in the system partition and everythings stays as i leave it when rebooting
Somehow the phone boots way faster now ?? But certainly welcome!
Thankyou for your replies
Yeah..as the title says.. 3 weeks ago this hacker hacked into my network..
placed rootkits in all my 3 computers and then hacked its way to my Desire and my wifes iphone. good thing i had wireshark running same time.
So.. 5 units hacked with the method in like 1 houre. Bad luck for me i guess.
And kaspersky didnt give me any warnings at all. bye bye kaspersky.
Anyway... i flashed my desire's HBOOT just to be sure. after i did a check with "AutoKiller Memory Optimizer" all kinds of malware services was attached to most of my apps.
1- downgraded HBOOT
2- flashed stock HBOOT from alpharev
3- Changed recovery from CWM to 4EXT as i suspected the recovery being infected somehow.
I checkd my log... the hacker had removed some files and moved shell files from an folder to another as well as busybox and so on. it was so many i thought il be better of installing new ROM.
I tried with Gingervillain first... everything installed fine..
checking with "root explorer" i see same files that had been moved and added was still there.
OK.. i tried again..
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
any idees...? im not sure if my kernel is right. it should be, when i installed Runnymede. when checking kernel v.
it says.. "[email protected] #11"
May be kernel rootkit? does the kernel start before recovery?
can someone plz confirm this?
baseband seem to be the same
any advise as for how to start from scratch will be much appreciated.
Clawsman said:
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
Click to expand...
Click to collapse
Full wipe wipes /cache, /data and /sd-ext to my knowledge. There is a possibility some of the files remain on /system. Use 4EXT to manually format each partition using format option.
Clawsman said:
it says.. "[email protected] #11"
Click to expand...
Click to collapse
That seems in order. Long name in attach marks modules added to that kernel.
Sent from my HTC Desire using Tapatalk
Ok
well.. i did the format manually in 4EXT.
I suspect some files still to be there..also some boot files containing malware script.
what file contains the boot script? i mean.. what file is the first to be triggered when booting in HBOOT. because many things in the recovery doesnt seem right. and the hboot fastrecovery starts with a delay.
Like when i want to partition or when i want to format all partitions except sd. Acts like it doesnt want to.
Anyway.. was just wondering if i could just adb and delete every file folder that is in in my phone and then flash recovery and ROM again.
Is that what RUU does?
is that something to recomend?
RUU is complete wipe of everything. /system, /hboot etc.
Download the correct one for your phone, *follow its instructions* (may need a gold card - google it) and run it on a clean pc.
Clean your pc ie format and reinstall after taking backups.
Then start again wit ha new hboot/rom setup.
Is that even possible? Infecting an Android phone via a Wi-fi network?
And Recovery shouldn't be able to get infected. I think ONLY /data can, and eventually /system if it's mounted as RW.
But on a wipe data gets deleted, and on a ROM install /system and boot (which holds the kernel and ramdisk) is deleted anyway.
RADIO starts before HBOOT. And there's absolutely no way they can be infected.
To be safe:
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot erase recovery *OVERKILL*
Then just do fastboot flash recovery {RECOVERY}
And there's nothing more you must do. HBOOT reflashing is 100% pointless.
Maybe top-notch hackers are shifting their interest from hacking NASA, FBI and similar organizations in the US to hacking Android phones. Or maybe it's one of their favourite ways to have fun in their idle time. Who knows?
Anyways, here's a Thanks from me, mr. Andrei, for your contribution to this community.
TVTV said:
Maybe top-notch hackers are shifting their interest from hacking NASA, FBI and similar organizations in the US to hacking Android phones. Or maybe it's one of their favourite ways to have fun in their idle time. Who knows?
Anyways, here's a Thanks from me, mr. Andrei, for your contribution to this community.
Click to expand...
Click to collapse
I do what i can. There are many devs that know much more than me. Your thanks are appreciated
For me it's still strange, tho. Only data and system could be "infected"
Take a look at this: http://forum.xda-developers.com/showthread.php?t=1399076
It's a scheme i made on how HTC and Nexus devices work. (How they boot, what are the individual partitions, etc)
Clawsman said:
Yeah..as the title says.. 3 weeks ago this hacker hacked into my network..
placed rootkits in all my 3 computers and then hacked its way to my Desire and my wifes iphone. good thing i had wireshark running same time.
So.. 5 units hacked with the method in like 1 houre. Bad luck for me i guess.
And kaspersky didnt give me any warnings at all. bye bye kaspersky.
Anyway... i flashed my desire's HBOOT just to be sure. after i did a check with "AutoKiller Memory Optimizer" all kinds of malware services was attached to most of my apps.
1- downgraded HBOOT
2- flashed stock HBOOT from alpharev
3- Changed recovery from CWM to 4EXT as i suspected the recovery being infected somehow.
I checkd my log... the hacker had removed some files and moved shell files from an folder to another as well as busybox and so on. it was so many i thought il be better of installing new ROM.
I tried with Gingervillain first... everything installed fine..
checking with "root explorer" i see same files that had been moved and added was still there.
OK.. i tried again..
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
any idees...? im not sure if my kernel is right. it should be, when i installed Runnymede. when checking kernel v.
it says.. "[email protected] #11"
May be kernel rootkit? does the kernel start before recovery?
can someone plz confirm this?
baseband seem to be the same
any advise as for how to start from scratch will be much appreciated.
Click to expand...
Click to collapse
An example of those infecting file?? What file in your root partition?? What path? Rom files are only on /system
Inviato dal mio Galaxy Nexus usando Tapatalk
I never use a anti virus and until now never have a problem...As i know!
Well it happened to me..
I have deleted everything.. I remember i checkd my log, and busybox files was moved to the system folder.. And all kinds of services was attached to Google map, calender, Facebook, wifi apps, market, etc..
And new apps installed like vpn, cam apps, recorders.. etc
Im currently using the free lookout...
And want to Buy a security tool.
Any advice Will be much appreciated.
Sent from my HTC Desire using xda premium
Alright, I'm running CyanogenMod 11 with TWRP as my recovery. When I try to change my build.prop it tells me that the action is not allowed because the system folder is mounted as Read only and not as R/W. I have tried using the chmod syntax 755 while in recovery but, after rebooting nothing has changed. Using my file manager (Solid Explorer) I have tried changing the permissions to be R/W by using the same chmod syntax. What have I done or am I doing wrong? I have never crossed this issue before with any other ROM or phone and I would like to add some additional speed and smoothness tweaks to the ROM build.prop. Have I tried another ROM to see if the same thing continues to happen? Nope, I sure haven't. If I did though and something magically changes to where it would begin working using another ROM, I still would not know how to fix the issue that I'm faced with now. Will ya please help? Thank you for your time in advance as well!
The drive isn't being mounted by solid Explorer as read/write. I'm not familiar with the app so can't explain how to do it but it may be in the options somewhere or a button on the screen.
You could try es file Explorer. It's free and works for me.
-> Sent from my mind to your screen.
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.
Well, I just tried ES File Explorer and it said that I'm mounted as R/W on my system folder, same as it did on Solid Explorer, yet once I try to alter anything I still receive the same "Operation Failed......System Mounted as Read Only" message. I have even switched ROM's to see if maybe, just maybe, it was some sort of CM 11 bug. Everywhere I look online says to correct it through my recovery and since that doesn't work..........? I'm at a bit of a loss now! I have granted both file managers Superuser rights. Hell my Superuser auto-response is always set to grant all apps that permission. And as far as the form of Superuser I'm using goes, I'm just sticking with the CM stock Superuser because whenever I attempt to use SuperSU all sorts of stuff begins to fail.
Is your SD card formatted as FAT32....or EXFAT...???
Needs a possible format again it sounds like....IMHO..g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Haven't thought about it possibly being my SD's format being that I am trying to access my systems files (i.e.- build.prop, system apps, etc.) and not the external SD Card, but what the hell?! I reckon I can always give it a shot. Could very well be that simple since I just dropped $100.00 on a stupid Lexar 64 Gig. Micro SD about the same time this issue arose. Hope so even if i do end up feeling like a dumb ass later on. It's getting annoying! I've tried several different ROM's, file managers, running syntax in the emulator, and anything else I could dig up now and this isn't quite my first Android experience, still relatively new though, so I know I'm not flashing anything wrong or outta the ordinary. Give me bit to take care of some every day life crap and I'll report my findings back to ya.
Dead serious, I did not do anything different whatsoever and it began to allow me to change permissions on my system files or whatever else I wished to do to it......?! No Earthly idea what was/did go on for it not to allow me to for the time it didn't, but outta nowhere, as I said, it is working again. I did wipe and flash numerous ROM's without any luck and even had flashed the one that it is working on now, but it didn't work the first or second time I flashed it. Never even got the chance to reformat my SD Card. Hell, I don't know.....!
countryboy092782 said:
Dead serious, I did not do anything different whatsoever and it began to allow me to change permissions on my system files or whatever else I wished to do to it......?! No Earthly idea what was/did go on for it not to allow me to for the time it didn't, but outta nowhere, as I said, it is working again. I did wipe and flash numerous ROM's without any luck and even had flashed the one that it is working on now, but it didn't work the first or second time I flashed it. Never even got the chance to reformat my SD Card. Hell, I don't know.....!
Click to expand...
Click to collapse
Running Jellywiz Extreme Rom 4.3 for my Note 2 on Verizon, and ever since i updated it to 4.3 on an unstable original ROM (Davidson3680's OG 4.3 ROM pre-2014), i havent been able to mount system as R/W.
I keep coming back to the possibility that in both of these recent cases that the file structure is somehow corrupted...
A possible 4.3 return to stock using Zen Arcades 4.3 stock rom may correct the file issues and restore the external functionality...
I'm still perplexed about the differences in flashing success based on whether or not a user has taken an official 4.3 update versus a user who has not...and the variables in function using the exact same software's...
The Zen thread method seems to be the stable and reliable way back to full function...or at least the best way to build the file structures back within their respective partitions...
We are playing very near the partition level...but I don't think it's a partition/pit issue....rather the broken file structure inside...
I'd be interested in the results of that test using Zen's files in the attempt to repair the files...and path to the SD...
If you are willing to try that...and meet success...it would solve a good half dozen device issues across different users in one pass....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...