I have an apex solo 7i (TM772) and I was able to gain root access from adb only. I modified the build.prop file and it is now stuck in a boot loop.
I have the original build.prop file on my PC (I also have the entire /system directory) but from recovery mode the only adb access I can get is to side load a zip.
I can access fastboot through droidboot.
During the boot loop it is found as a device (in production builds so I can not use the "adb root" command).
With the adb device shell I can use the su command, but while trying to mount the system rw it fails and says:
Code:
# mount -o rw,remount -t yaffs2 /dev/block/mccblk0p8 /system
mount: Operation not permitted
Is there any way to make it mount the system partition rw or could I make a flashable zip file to restore the build.prop?
Related
I tried copying files to the system folder but I keep getting "failed to copy, out of memory". Any idea why? I also tried using Root Explorer but despite the pasting animation being displayed, the files were not copied.
I've tried both the terminal emulator
Code:
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cp /sdcard/libt9.so /system/lib
and adb
Code:
adb remount
adb push lib/libt9.so /system/lib/libt9.so
It seems the file has been moved successfully through recovery mode, but I still can't see the file when the phone is booted.
i rooted my verizon galaxy tab and i can run Root apps, but i cant move a wpa_supplicant file to my /system/root using Astro.
Is this a root issue or do i need something better than Astro? I also tried OI file manager but it just says "cannot move file here".
By default, /system is (usually) mounted read-only. You probably need to remount it read-write.
Code:
adb remount /system
adb push [path-to-file] /system/bin
If remount doesn't work, try
Code:
adb shell mount -t yaffs2 -o rw,remount /dev/block/mtdblock3 /system
Have an HTC hero with CM7 stable. Been trying to modify sysctl.conf to increase the speed a little (if thats possible, CM7 is fast). I've used the command in ./adb shell and terminal emulator:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When I type mount it displays /system as a r/w partition but I still can't edit the sysctl.conf file. When I do try to edit, the shell says that the directory doesn't exist (/ect/sysctl.conf).
Even with simpler commands like "adb pull /system/ect/sysctl.conf /" still come back as directory doesn't exist.
What am I doing wrong? Ultimately if I can want to get the sysctl file to my PC to edit and place back on the phone.
Have you tried using something like Root Explorer? While learning & knowing ADB comes in handy, I find most things are easier through Root Explorer. You can just copy the file to your SD card, then to your computer.
EDIT: On second look, you have /system/ect... instead of /system/etc...
I also believe it should be mtdblock4 instead of mtdblock3, but I could be wrong. I'm not good with this kind of stuff.
Type in mount to see what device is currently mounted as /system...I would just double check
Sent from my Droid using XDA App
This command should also work:
Code:
mount -w -o remount /system /system
I typed mount in cmd. Says that /system is in mtdblock3. I will try root explorer and see if it fixes my woes. Thanks.
Hi guys,
If any one getting error while remounting system partition in rw mode using adb, please follow these steps :
C:\Android\android-sdk-windows\tools> adb remount
remount failed: No such file or directory
SOLUTION:
Connect to your device usb adb: [FOR ROOTED DEVICES ONLY]
C:\Android\android-sdk-windows\tools> adb shell
$su
#mount -o remount,rw /dev/stl12 /system
(do your desired work like copy some files on system/media folder , then remount the system partition in ro mode again)
# cd /
#mount -o remount,ro /dev/stl12 /system
#exit
$exit
Thats all
FYI if you want to know the dev partitions mounted on your device :
C:\Android\android-sdk-windows\tools> adb shell
$ su
# mount
cheers
Did you map the other partitions by any chance? I'd like to be able to make a full backup to eventually be flashed back with Heimdall or ODIN. I already have a system.rfs (stock + root) that could be made in a tar image.
I've see tutorials for other Samsung phones but these need to be adapted to our exact setup. I haven't found anything generic enough to know how to go about mapping things.
It might also help those who flashed GT-S5660 ROMs on the Bell Canada GT-S5660M, as the screen brightness issues sound very much like kernel issues to me...
I can't quite tell what the difference is between stl and bml either. (I'll probably try dd'ing the different blocks, except stl5, and peek around with a hex editor...)
Goodbye,
Darkshado
I m unable to mount my filesystem in rw mode, I have used so many scripts in order to remount it rw, terminal emulator displays that's its in rw mode but when I chmod a file in xbin or try to to create a folder it displays read-only filesystem. I have used few scripts & terminal commands but to no avail also on Supersu beta. I m using s3 Verizon with the latest safestrap(twrp) recovery. Please help !!!