FORUMS
Remove All Ads from XDA

[FIXED] Remount failed: operation not permitted

91 posts
Thanks Meter: 12
 
By Nextelian, Member on 20th May 2010, 03:11 PM
Post Reply Email Thread
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:
  1. Flashed the 1.5 RUU that Flipz has had out for months. No errors
  2. Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
  3. updated my profile
  4. updated my PRL (which is now 65000??)
  5. 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.
The Following User Says Thank You to Nextelian For This Useful Post: [ View ] Gift Nextelian Ad-Free
 
 
20th May 2010, 03:35 PM |#2  
Member
Flag Kentucky
Thanks Meter: 0
 
More
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.
20th May 2010, 03:39 PM |#3  
Nextelian's Avatar
OP Member
Thanks Meter: 12
 
More
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
#
20th May 2010, 03:55 PM |#4  
Member
Flag Kentucky
Thanks Meter: 0
 
More
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.
20th May 2010, 04:49 PM |#5  
Nextelian's Avatar
OP Member
Thanks Meter: 12
 
More
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.
20th May 2010, 05:27 PM |#6  
Member
Flag Kentucky
Thanks Meter: 0
 
More
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://forum.xda-developers.com/showthread.php?t=684873
20th May 2010, 05:35 PM |#7  
Nextelian's Avatar
OP Member
Thanks Meter: 12
 
More
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
23rd June 2010, 09:38 PM |#8  
mrsato's Avatar
Senior Member
Flag Yokohama
Thanks Meter: 8
 
More
Quote:
Originally Posted by Nextelian

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?
7th September 2010, 03:36 PM |#9  
ghost_boy1412's Avatar
Member
Thanks Meter: 6
 
Donate to Me
More
Quote:
Originally Posted by mrsato

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!!

Quote:

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

The Following 2 Users Say Thank You to ghost_boy1412 For This Useful Post: [ View ] Gift ghost_boy1412 Ad-Free
23rd September 2010, 11:35 PM |#10  
Junior Member
Thanks Meter: 0
 
More
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.
24th September 2010, 02:09 AM |#11  
ASimmons's Avatar
Retired Recognized Developer
Flag Tampa Bay
Thanks Meter: 115
 
More
Quote:
Originally Posted by mojotexas

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
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes