I am locked out of my Nexus S due to a Force Close loop with Nfc.app caused by installing a non-working fix for the Google Wallet app on the T-Mobile (thanks Google!). I therefore can't run root explorer etc.
I am trying to remove Nfc.app using but get these errors:
Code:
$ rm /system/app/nfc.app
rm failed for /system/app/nfc.app, Read-only file system
$ remount
remount: permission denied
# mount -w -o remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Any way I can get past the read-only error, and the failure of remount?
Boot in recovery and run adb shell. That'll give you root permissions and access to the file system.
Greetz
That gives me:
error: device not found
I am using stock recovery (because it was a soft ClockworkMod recovery and I can't get back into ROM manager to reflash it).
Flash recovery with fastboot.
Thanks but I get:
$ fastboot flash recovery clockwork.img
fastboot: permission denied
Doing it wrong. Read the guides to learn how to set up and use fastboot.
I tried but that's all I came up with. If you could type the line of command I need, I'd really appreciate it, and give thanks
frutelaken said:
Boot in recovery and run adb shell. That'll give you root permissions and access to the file system.
Greetz
Click to expand...
Click to collapse
adb shell only inherently grants root permissions on an insecure boot image. If he's stock, rooted he'll get the standard user prompt and have to request elevated privileges.
CJSnet said:
I am locked out of my Nexus S due to a Force Close loop with Nfc.app caused by installing a non-working fix for the Google Wallet app on the T-Mobile (thanks Google!). I therefore can't run root explorer etc.
I am trying to remove Nfc.app using but get these errors:
Code:
$ rm /system/app/nfc.app
rm failed for /system/app/nfc.app, Read-only file system
$ remount
remount: permission denied
# mount -w -o remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Any way I can get past the read-only error, and the failure of remount?
Click to expand...
Click to collapse
No offense, but the Thanks Google is a bit snarky - they didn't provide for T-Mobile users and never distributed the APK to flash.
For something helpful though - go ahead and boot up normally. Grab a shell, su and remount /system manually
Code:
mount -o remount,rw /dev/mtdblock3 /system
You have to tell mount which partition to mount, it won't accept just a mount point.
Thanks, but how do I request elevated privileges? E.g. I get this:
$ mount -o remount,rw /dev/mtdblock3 /system
mount: Operation not permitted
And this:
$ fastboot OEM unlock
fastboot: permission denied
Seems I can't do anything from the $ prompt.
PS: My snark at Google was for releasing a fragmented product that was not available to T-Mobile in the first place, hence these problems with the cracked version.
CJSnet said:
Thanks, but how do I request elevated privileges? E.g. I get this:
$ mount -o remount,rw /dev/mtdblock3 /system
mount: Operation not permitted
And this:
$ fastboot OEM unlock
fastboot: permission denied
Seems I can't do anything from the $ prompt.
PS: My snark at Google was for releasing a fragmented product that was not available to T-Mobile in the first place, hence these problems with the cracked version.
Click to expand...
Click to collapse
Are you rooted - if so then su prior to issuing the mount command?
If not, Is the bootloader current unlocked? You don't use fastboot from the device shell. Fastboot is a command line utility used from your local computer to operate on the device when it is in the boot loader.
Bootloader was already unlocked.
I solved it:
Rebooted into fastboot mode by holding volume up and power
On computer navigated to folder containing fastboot and put the clockwork.img in there
Typed fastboot flash recovery clockwork.img
I now have CWM recovery back, thanks.
Related
I'm having trouble mounting the /system directory on my Captivate. When I try an "adb remount" I get
Code:
remount failed: no such file or directory
When I try to push my framework, I get
Code:
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': Read-only file system
I've tried
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
and this and get "Permission Denied."
It is confusing, because before when I had this problem, the fix I linked to worked for me. Now I can't get it. Also, I can pull from the /system just fine, but can't push.
I'm definitely rooted, and have Busybox installed.
Thanks in advance!
Bump?
I have read throug tons of guides, but nothing seems to be working. I went back to stock and flashed my rom again, but no luck. Any ideas would be appreciated.
Did you type su first? It acts as if you're not root. /system is readable by everyone so you can pull, but it's only writeable by root so you can't push to it unless you're logged in as root.
I've only used adb once to root my phone so I'm not entirely sure how it should be typed in, but in a terminal you'd just type su and hit enter, then type in your remount command.
Also, for what it's worth, you can shorten it to just: mount -o rw,remount /system
Your method is fine, it's just not necessary to type it all out.
fubaya said:
Did you type su first? It acts as if you're not root. /system is readable by everyone so you can pull, but it's only writeable by root so you can't push to it unless you're logged in as root.
I've only used adb once to root my phone so I'm not entirely sure how it should be typed in, but in a terminal you'd just type su and hit enter, then type in your remount command.
Also, for what it's worth, you can shorten it to just: mount -o rw,remount /system
Your method is fine, it's just not necessary to type it all out.
Click to expand...
Click to collapse
Thanks for the reply.
If I type su in the terminal, this is what I get.
Code:
C:\Android\tools>su
'su' is not recognized as an internal or external command,
operable program or batch file. C:\Android\tools>
However, when in shell, I can get it to recognize su, but it still doesn't like to mount.
Code:
C:\Android\tools>adb shell
$ su
su
# mount -o rw,remount /system
mount -o rw,remount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
I have an Atrix on AT&T. Which means there's a bootloader encryption, and the carrier prevents non-market apk installations, which I have resolved since my phone is rooted and I have changed the boot animation already.
In order to do these things, I found Ghost Commander that would let me chmod my system directories...which is fine, but I feel kind of gimped that I can't do it on terminal.
Basically, what I want to be able to do is remount /system as rw using terminal.
This method doesn't work on both terminal and emulator on my phone. I have done:
Terminal:
Code:
sudo su
cd [sdk directory]
./adb devices
./adb shell
su
mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system
and this is where I get stuck because I just get an Invalid argument error.
Here is some info about my sytem -
Usage: mount [-r] [-w] [-o options] [-t type] device directory
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime, data=ordered 0 0
Been searching for the answers for a while now and tried all kinds of syntax, and now I'm here. What am I doing wrong? Thanks
Try:
mount -o remount,rw /system
The remount option automatically looks up the info for /system so you shouldn't have to bother with the details.
Hmm, I tried that thanks, and I still got 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
Hmm, I can't think of any reason that wouldn't work but it sounds like your phone is locked down pretty tight. Do you know if others have been able to remount /system?
What version of busybox do you have? Maybe you could try updating it. There are one or two free busybox updater apps on the market, if you can use them.
Have you tried just 'adb remount'?
Does the mount command require busybox? Do you have that properly installed?
That requires adbd itself to be run in root mode (this is different from being rooted on the phone) & you could do that only on insecure boot image. mount/unmount both happen to come from the busybox package. It would be hard to contemplate that Motorola actually changed that but nothing would stop them from. You could try updating the busybox utility onboard your phone. There is nothing with your usage of the command - it would work the same way on my Nexus S
I do have Busybox in /system/xbin. Thinking that maybe the xbin directory may need to have the rewrite permissions, I changed its permissions to 777 using the chmod command in phone Terminal. I did the remount command 'mount -o remount,rw -t ext3 /dev/block/mmcblk0p12 /system' in shell on the phone, and I THOUGHT I BRICKED! Haha, but it just turned off, and I rebooted to find that my button backlights were turned off...which I fixed with the brightness file.
Anyhow, I think I'll just use the chmod command because that seems to work. NeoA, I think you are right about the adbd to run in root mode, because I've seen discussions about that before.
Thanks for the feedback guys! At least I know I wasn't having syntax errors to say the least
So did it remount it as rw? The mount command was running before, just giving errors, but if it's running that should mean the permissions were ok.
try
Code:
busybox mount -o remount,rw /system
Fr4gg0r said:
try
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
"mount: can't find /system/app in /proc/mounts"
but
Code:
busybox chmod 777 /system
is good enough for me, for now
marlasinger said:
Code:
busybox chmod 777 /system
is good enough for me, for now
Click to expand...
Click to collapse
Using chmod to change permissions won't actually give you rw access to the system partition since it won't change whether it's mounted as read-only or r/w. To be able to run the chmod command, the system must already have been mounted as r/w or you would have received a "Read-only file system" error. It must have gotten mounted as read/write when the remount command caused a reboot. You can see how /system is mounted by just typing "mount" in adb shell which will list all of the mounted partitions.
Hi
I tried SuperOSR for a few months now, but i really want to use the camera so therefor i want to return to stock firmware.
I used this thread:
http://forum.xda-developers.com/showthread.php?t=1164468
Now the problem is, when i download stockrecovery and install it to the SDCARD and then i try to update it via CWM, it says:
Error in sdcard/stockrecovery.zip (Status 0) and then it stops, what now?
To flash stock recovery back you need to rename it to PH06img.zip.
and if you wanted to go back to stock rom alone, you dont need stock recovery. Just download the stock rom and install the RUU
If you want to flash the stock recovery, here is one:
File name: recovery.img
File will remain active for: 24 Hrs
Link: http://www.streamfile.com/myid/sA81KohsAsgN
(if some1 could mirror it, I can't seem to access any file sharing from here)
place the file in your sdcard (don't change the name), and flash from CWM recovery using adb:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img
Adlx u went from clique to chacha development?
Sent from my LT15i using XDA App
zainthesnipe said:
Adlx u went from clique to chacha development?
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
lol, yeah, I started with the Cliq, then Cliq XT, Defy, and now I'm working on CM7/SuperOSR for the Chacha, check http://forum.xda-developers.com/showthread.php?t=1291232
You got a Chacha?
adlx.xda said:
(if some1 could mirror it, I can't seem to access any file sharing from here)
Click to expand...
Click to collapse
Up on http://alex.swtesting.ro/downloads/ or http://swtesting.ro/alex/downloads/ for unlimited time.
when i type mount sdcard,adb show me this:
$ mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
whats wrong?
and its all of this comands:
$ mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
$ cd /sdcard
cd /sdcard
$ flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: permission denied
ok, sorry about that, my mistake
Try that:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img
all of my phone:
C:\Users\Pasha\Desktop\adb\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# cd /sdcard
cd /sdcard
# flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: not found
#
file not found but i placed recovery.img into root of my sdcard!
From your post you're missing a / in "mount /sdcard".
not found again..
$ su
su
# mount /sdcard
mount /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# cd /sdcard
cd /sdcard
# flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: not found
#
The only thing that worked to get stock recovery was to change back to OTA firmware, which i downloaded on the 2nd page. Then i updated to OTA1.54 (official from HTC) and then i put CWM on it again to root my device.
All the other methodes like, use recovery.zip etc. etc. do not work the phone gives error 0 and hangs
Justphemy said:
flash_image: not found
[/COLOR]
Click to expand...
Click to collapse
Damn it! I thought CWM had flash_image...
help
pongzor said:
The only thing that worked to get stock recovery was to change back to OTA firmware, which i downloaded on the 2nd page. Then i updated to OTA1.54 (official from HTC) and then i put CWM on it again to root my device.
All the other methodes like, use recovery.zip etc. etc. do not work the phone gives error 0 and hangs
Click to expand...
Click to collapse
Could you write step by step how to back to stock revocery or show which file should I download, please
That should be a useful guide I agree
Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
flash_image is a small utility to be used on the device that allows you to re-write system partitions with image files. If you don't have it, it can be found here: http://cyanogen-files.carneeki.net/flash_image.zip (Unzip it)
You will need to install flash_image on the device, this requires the use of the SDK. So if you do not have the SDK installed, do it now.
Then go to the tools directory in the SDK,
Code:
example: cd c:\android-sdk-windows\tools
or
Code:
example: cd ~/android-sdk-linux/tools
At this point you will need to use your command line or terminal on your PC to access ADB, if you do not know how to use ADB and it is causing you to unsuccessfully perform these actions please read one of the many guides on ADB, also if the device is not recognized, you may need to uninstall HTC sync and install the ADB USB drivers in the SDK after downloading them from the setup program. (You will also need to turn on USB debugging on the device, in Settings/Applications/Development)
From command prompt or terminal:
Copy flash_image to the sdcard on the device
Code:
adb push flash_image /sdcard/
To use flash_image to flash a recovery image called recovery.img in the root of your sd card
Code:
adb shell
su [/CODE]
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
Code:
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I hope it works for you. It did for me.
adlx.xda said:
If you want to flash the stock recovery, here is one:
File name: recovery.img
File will remain active for: 24 Hrs
Link: http://www.streamfile.com/myid/sA81KohsAsgN
(if some1 could mirror it, I can't seem to access any file sharing from here)
place the file in your sdcard (don't change the name), and flash from CWM recovery using adb:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Hi !
When i write su and press enter it's says permission denied
tokafondo said:
Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
I hope it works for you. It did for me.
Click to expand...
Click to collapse
tokafondo said:
Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
I hope it works for you. It did for me.
Click to expand...
Click to collapse
C:\Fastboot>adb shell
$ mount -o remount, exect /dev/block//vold/179:1 /sdcard
mount -o remount, exect /dev/block//vold/179:1 /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
$ cd /sdcard
cd /sdcard
$ ./flash_image recovery /sd/card/recovery.img
./flash_image recovery /sd/card/recovery.img
./flash_image: not found
$ ./flashimage.zip recovery /sdcard/recovery.img
./flashimage.zip recovery /sdcard/recovery.img
./flashimage.zip: not found
$ ./flash_image.zip recovery /sdcard/recovery.img
./flash_image.zip recovery /sdcard/recovery.img
./flash_image.zip: permission denied
Anybody a little help ...
Hi,all, I just get start with Nexus 5. can anybody tell me what the problem? follow with the command I input in windows shell.
K:\N5\ROOT>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount system /system
mount -o remount system /system
mount: Permission denied
255|[email protected]:/ #
Anyone on this?
Cheers!
su
mount -o remount,rw /system
However this only works if you have a custom "insecure" kernel that allows adb to do root things.
Sent from my Nexus 5 using Tapatalk
Thanks for the reply!
So, I will write my story here, hopefully to help some other guy in the future!
Basically I was on debug build from AOSP for the N5! And I installed all proprietary files from Google, LG, Qualcomm etc! But camera was faulty! So I decided to flash the stock images from Google! Then I 've lost
Code:
adb root
So I flashed the boot image from the debug build I had previously!
adb root works like charm!
to flash it, I used: fastboot flash boot boot.img
This phone is kinda diehard. Thanks to dirtycow and free time, now I have root on this phone. But only shell root access.
Code:
255|[email protected]:/ # id
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:runas:s0
[email protected]:/ # mount -o remount,rw /system
mount: Operation not permitted
There are custom bootloaders, is there a way install them directly from the phone? All the info I got is fancy app/gui. There is no hardcore docs on how to gain the full root access or flash the bootloader.
I have access to the /cache partition. I also have access to the /cache/delta/boot_delta.bin (looks like it is encrypted), I can reboot to the recovery menu and pass commands into /cache/recovery/command
I can use dd to dump whole flash (read access works). But dd doesn't work with /dev/block/ devices on write (it works without problems, but when you check actual content - it appeared to be unmodified at all). Is it a common write protection or something?
Also there is a FOTA partition. How can I determine which reboot command should I send to reboot to the fota recovery?