[FIXED] Remount failed: operation not permitted

Nextelian · May 20, 2010

Ok, I'm not a total noob. I've been trying to return to 1.5 as cleanly as possible, but now I'm having an error when trying to remount my phone.

Code:

C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306    device


C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted

C:\android-sdk-windows\tools>adb shell
$ su
su
#

This is what I did:

Flashed the 1.5 RUU that Flipz has had out for months. No errors
Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
updated my profile
updated my PRL (which is now 65000??)
rooted through the normal sequence without error, I can boot to the recovery just fine, but when I adb shell into the phone I end up at $ instead of #. I have to su to get to # and at the c:\windows-sdk-windows\tools\adb remount fails with "remount failed: operation not permitted"

Is it possible that the PRI update has foiled the root exploit? I even restored a nand backup that I know had a working root and I still have the same results. This is too weird.

Anyone else have this issue? I searched the forum but I came up empty.

eagle128 · May 20, 2010

Try adb remount before adb shell. I'm pretty sure anythig with adb should be ran at just the command prompt.

Someone feel free to correct me if I'm wrong.

Nextelian · May 20, 2010

right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.

Code:

C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306    device


C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted

C:\android-sdk-windows\tools>adb shell
$ su
su
#

eagle128 · May 20, 2010

Yeah the wording got me. I was hoping it was as simple as that for you tho. Defiantly Strange. Believe me I've had plenty of those moments where hours would have been saved if someone could have just said "no your just doing it wrong".

Maybe try rerunning the RUU and start from scratch the PRI fix should hold thru the RUU but if it did affect something else running the RUU again may correct it.

Nextelian · May 20, 2010

I RUU'd about 4 times so far on two different laptops, one with XP and one with Win7, running both versions of the HTC Sync drivers.

Something is definitely different. I'm thinking of doing the PRI fix again to see if that helps. The PRL being 65000 instead of the normal 60664 is another anomaly I'm curious about.

eagle128 · May 20, 2010

looks as if the 65000 PRL is a new one. I can't confirm (not with Sprint) but there is a thread over in General talking about it.

http://xdaforums.com/showthread.php?t=684873

Nextelian · May 20, 2010

YEAH! I fixed it....well....actually Flipz fixed it for me. I created a custom ROM in the kitchen and flashed it. Now the remount miraculously works. I'm back to being happy...though I don't know why. Its not like I was using root for anything

mrsato · Jun 23, 2010

Nextelian said:
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.

Code:

C:\android-sdk-windows\tools>adb devices List of devices attached HT9C1HF03306 device C:\android-sdk-windows\tools>adb remount remount failed: Operation not permitted C:\android-sdk-windows\tools>adb shell $ su su #

Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?

ghost_boy1412 · Sep 7, 2010

mrsato said:
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?

I found something that help me and you. it properly works!!

I can't spell out instructions for the above mentioned suggestion, since I
don't know which file editor comes on the shipped device, but I have an
alternative solution.From the SDK's tools directory, run adb shell. In the
prompt run the following:
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
and eventually you should restore the original directory permissions by:
# chmod 755 /system (Or any subdirectory you modified permissions to)
Hope this helps,
Yoav

mojotexas · Sep 23, 2010

still no Read/Write on /system

I tried the above, and I could not mount /system as read/write:

Code:

adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted

My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.

ASimmons · Sep 24, 2010

mojotexas said:
I tried the above, and I could not mount /system as read/write:

Code:

adb shell $ su mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system Permission denied $ mount: Operation not permitted

My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.

I'm not at my computer but I think the command is off... check to make sure its exactly how it should be... maybe the coma after the rw

Sent from my HERO200 using XDA App

huedawg · Sep 25, 2010

mojotexas said:
I tried the above, and I could not mount /system as read/write:

Code:

adb shell $ su mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system Permission denied $ mount: Operation not permitted

My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.

Just cd to your tools directory and adb remount

OpenMinded · Oct 2, 2010

huedawg said:
Just cd to your tools directory and adb remount

Is there a solution for this?
I have a rooted HTC Desire.
When I type adb remount I get permission denied.
When I type adb shell and then su , i get permission denied!
This was a stock 2.2 rooted with unrevoked 3.

Any idea?

[edit]
i noticed root permissions pop-up on the phone and allowed so su worked.
[/edit]

julien.me · Oct 4, 2010

Hi,
I have a Desire with stock froyo rooted with unrevocked 3 too and cannot use adb remount:

D:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted

D:\android-sdk-windows\tools>adb shell
$ remount
remount
remount: permission denied
$

I have allowed ADB via the Super user app popup.

Any idea?

EDIT: I have set S-OFF using AlphaRev's recovery fastboot and I am now able to remount in rw (well no access denied anymore)
still missing some access as I fail to remove the Google Maps app (want to use Brut maps only)

neostan · Jun 22, 2011

ghost_boy1412 said:
I found something that help me and you. it properly works!!

This worked perfectly! Thank you!

Bierce22 · Jun 22, 2011

Good freakin lord why the heck did you feel the need to bump this thread thats almost a year old just to say that!!!!!!!! I rarly shout like this, but this crap is starting to drive me crazy!!!!!!!!!!!!

Grrrrrrrrrrrrrrr

DannyMichel · Jul 28, 2011

same thing for me. i get permission denied

il Duce · Jul 28, 2011

DannyMichel said:
same thing for me. i get permission denied

thank you for letting us all know, and in such detail, and with new valuable information no less

/me shakes fists in rage.

PangOS · Aug 1, 2011

Post deleted.

TheSavageSquid · Nov 30, 2011

Don't mean to bring up this dead thread but a more simple solution would be this

adb shell
$ su
# busybox mount -o remount,rw /system (or another desired directory)
# chmod 777 (or another desired permission set) /system (or another desired directory)
# exit
$ exit

[FIXED] Remount failed: operation not permitted

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Inactive Recognized Developer / Retired Forum Mod

Senior Member

Member

Similar threads

Top Liked Posts