I'v just rooted my Tab, I don't know if I'm losing the plot but I can't figure out how to write to the system partition? I can't find any apps that will work (for free) and "adb remount" doesn't work. "remount failed: Operation not permitted"
Am I missing something?
alias_neo said:
I'v just rooted my Tab, I don't know if I'm losing the plot but I can't figure out how to write to the system partition? I can't find any apps that will work (for free) and "adb remount" doesn't work. "remount failed: Operation not permitted"
Am I missing something?
Click to expand...
Click to collapse
adb remount doesn't work because /default.prop needs ro.secure set to 0 (not 1). This can't be changed easily without modifying the boot.img.
However, you can remount /system as a r/w filesystem using ADB by opening a shell and:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p1 /system
or
Code:
su
mount -o rw,remount -t ext3 /dev/mtdblock3 /system
Regards,
Dave
foxmeister said:
adb remount doesn't work because /default.prop needs ro.secure set to 0 (not 1). This can't be changed easily without modifying the boot.img.
However, you can remount /system as a r/w filesystem using ADB by opening a shell and:
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p1 /system
or
Code:
su
mount -o rw,remount -t ext3 /dev/mtdblock3 /system
Regards,
Dave
Click to expand...
Click to collapse
Thanks, so which should I actually use, the former or the latter?
I've personally used the first command, but I saw the second one on another thread and it seems to work as well.
To be honest, I think it's ignoring the parameter anyway.
Regards,
Dave
hello, i need to restore my framework-res.apk from backup on my phone. i googled around and found some ways but they arent working. i can adb shell in while in recovery but i cant boot to android and /system isnt mounted.
i tried mount -o rw,remount /dev/block/mtdblock3 /system and mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system in adb shell and get "mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument"
also tried doing adb remount but get "remount failed: Unknown error: 0"
anyone know whats going on? i have 318 rom and streakmod recovery. sorry if this is considered android development. i dont think it is so its in streak general.
I believe /system shound be /dev/block/mtdblock6, so you should be able to use: mount -t yaffs2 /dev/block/mtdblock6 /system
yeah i just got the answer in freenode irc #dellstreak too and this did work. thank you.
[11:18pm] meralias: mount /dev/block/mtdblock6 /system
[11:21pm] meralias: actually: mount -t yaffs2 /dev/block/mtdblock6 /system
edit: [11:24pm] • meralias also goes as 'kantras'
sly.
I got a new Evo 3D and decided to play around with my old Tattoo. I am an absolute noob, so please excuse any silly questions.
I was able to root my phone, but am not able to flash the recovery/boot. I was following instructions as listed here:
wiki.cyanogenmod.com/index.php?title=HTC_Tattoo:_Full_Update_Guide
I am stuck at this step:
flash_image recovery /sdcard/recovery-clockwork-3.0.2.7-click.img
Click to expand...
Click to collapse
Here is the error message I get:
# ls -l
ls -l
-rwxrwxrwx shell shell 26172 2009-10-03 21:07 flash_image
-rwsrwxrwx root root 26256 2011-07-04 20:08 su
-rwxrwxrwx shell shell 4695 2010-02-23 23:05 m7
# chmod 4755 su
chmod 4755 su
# flash_image recovery /sdcard/recovery-clockwork-3.0.2.7-click.img
flash_image recovery /sdcard/recovery-clockwork-3.0.2.7-click.img
flash_image: not found
# pwd
pwd
/data/local/bin
# ls -l
ls -l
-rwxrwxrwx shell shell 26172 2009-10-03 21:07 flash_image
-rwsr-xr-x root root 26256 2011-07-04 20:08 su
-rwxrwxrwx shell shell 4695 2010-02-23 23:05 m7
# ./flash_image recovery /sdcard/recovery-clockwork-3.0.2.7-click.img
./flash_image recovery /sdcard/recovery-clockwork-3.0.2.7-click.img
mtd: erase failure at 0x00000000 (I/O error)
mtd: erase failure at 0x00000000 (I/O error)
mtd: skipping write block at 0x00000000
.
.
.
mtd: erase failure at 0x004e0000 (I/O error)
mtd: erase failure at 0x004e0000 (I/O error)
mtd: skipping write block at 0x004e0000
error writing recovery: No space left on device
#
Click to expand...
Click to collapse
Any help is greatly appreciated.
try to free some space in internal memory, man. ))
I did. Didn't help. The Clockworkmod recovery image is under 3Mb. I get the same error even after I cleared more than 60Mb.
I installed ClockworkMod Recovery with instructions on a french website, and they don't do it the exact same way :
adb push flash_image ./data/local/bin/flash_image
adb push recovery-clockwork-3.0.2.7-click.img /sdcard/recovery-clockwork-3.0.2.7-click.img
adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko
adb shell
$ su
# insmod /data/local/bin/tattoo-hack.ko
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
# chmod 755 /data/local/bin/flash_image
# /data/local/bin/flash_image recovery /sdcard/recovery-clockwork-3.0.2.7-click.img
I'm a noob too and i didn't really understand why they use tattoo-hack.ko, but this worked for me
you can download the tattoo-hack file by searching for it on google
(I'm new here so i can't put links yet, sorry :S)
jujuwilde said:
I installed ClockworkMod Recovery with instructions on a french website, and they don't do it the exact same way :
adb push flash_image ./data/local/bin/flash_image
adb push recovery-clockwork-3.0.2.7-click.img /sdcard/recovery-clockwork-3.0.2.7-click.img
adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko
adb shell
$ su
# insmod /data/local/bin/tattoo-hack.ko
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
# chmod 755 /data/local/bin/flash_image
# /data/local/bin/flash_image recovery /sdcard/recovery-clockwork-3.0.2.7-click.img
I'm a noob too and i didn't really understand why they use tattoo-hack.ko, but this worked for me
you can download the tattoo-hack file by searching for it on google
(I'm new here so i can't put links yet, sorry :S)
Click to expand...
Click to collapse
tattoo_hack.ko is used to defeat the system NAND protection on the device
Problem with /efs partition (can't mount but IMEI OK)
Hi guys,
I've been searching for two days before posting this.. I'm completely mad on how to repair this problem.
I tried to flash a custom recovery on my GT-9505 doing this in terminal (of course my phone was rooted):
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
The problem is that I flashed the recovery on the wrong partition, as /mmcblk0p10 is for /efs (right?)
I was on stock firmware I9505XXUDMH8.
When I reboot, phone went on factory mode and I couldn't make calls. Wifi was working right.
I flashed CM 10.1.3 last night and now I can make calls. IMEI and wifi mac are shown ok in status, but bt is not not available and I think serial number is wrong (3403a6f2??)
I suppose that if I go back to stock the problem will be the same with factory mode and no calls because flashing this won't write on /efs.
I have a backup of efs (efs_19700508_054443.img) (~13MB) done in philz touch recovery, but this was made after I corrupted the /efs.
So the problem is I can't mount /efs in recovery neither in File Manager or terminal.
Any ideas on what can I do to repair it?? Thanks in advance and sorry if I have posted in wrong place
Update:
I've made another backup but with EFS Professional: GT-I9505_20131026_190930.tar.gz -> efs.img.ext4
If it holds for something...
Edit: BT address is showing correctly when BT is ON (sorry for that mistake!)
So the only thing is showing wrong (i think) is serial number.
i still cannot mount /efs nor access it via root explorer...:crying:
If I'm on Windows 7, is there any way to mount the efs.img file to edit files into it? (I.e. Like in daemon tools)
If I can format /efs then I'll only hace to edit the files in efs.img to edit my serial number for the good one and copy these files into /efs.
Then my /efs partition won't be corrupted and I will be able to mount it
Someone can give any idea?
Up!
Up!
Uuuup..!
If I restore the .img backup that I have of /efs in recovery it doesn't change anything... Maybe cause it's corrupted?
fran41 said:
If I restore the .img backup that I have of /efs in recovery it doesn't change anything... Maybe cause it's corrupted?
Click to expand...
Click to collapse
try these commands in terminal emulator:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
sync
reboot
samersh72 said:
try these commands in terminal emulator:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
sync
reboot
Click to expand...
Click to collapse
Thanks for reply.
First line (mount -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs) Mount: invalid argument
Something spelled wrong?
fran41 said:
Thanks for reply.
First line (mount -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs) Mount: invalid argument
Something spelled wrong?
Click to expand...
Click to collapse
Ok, try without first command (mount....)
if not try this
Code:
mount -w -t ext4 /dev/block/mmcblk0p10
samersh72 said:
Ok, try without first command (mount....)
if not try this
Code:
mount -w -t ext4 /dev/block/mmcblk0p10
Click to expand...
Click to collapse
[email protected]:/ # echo -n ON > /efs/FactoryApp/keystr
sh: can't create /efs/FactoryApp/keystr: No such file or directory
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Should be like this??:
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10 /efs
mount: Invalid argument
fran41 said:
[email protected]:/ # echo -n ON > /efs/FactoryApp/keystr
sh: can't create /efs/FactoryApp/keystr: No such file or directory
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Should be like this??:
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10 /efs
mount: Invalid argument
Click to expand...
Click to collapse
it is weird! try:
Code:
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
or
Code:
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
samersh72 said:
it is weird! try:
Code:
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
or
Code:
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
Click to expand...
Click to collapse
[email protected]:/ # mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
mount: Invalid argument
fran41 said:
[email protected]:/ # mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
ext4 /dev/block/mmcblk0p10 /efs <
mount: Invalid argument
Click to expand...
Click to collapse
this command work for me (mount -o remount,rw -t ext4 /dev/block/mmcblk0p10)
i dont know what is the matter with your efs partition!
by the way, install busybox then do the commands
samersh72 said:
this command work for me (mount -o remount,rw -t ext4 /dev/block/mmcblk0p10)
i dont know what is the matter with your efs partition!
by the way, install busybox then do the commands
Click to expand...
Click to collapse
I have busybox installed! I'm getting mad with this Nothing seems to work...
fran41 said:
I have busybox installed! I'm getting mad with this Nothing seems to work...
Click to expand...
Click to collapse
try to re-partition the phone partitions using pit file with the firmware, it may help
samersh72 said:
try to re-partition the phone partition using pit file with the firmware, it may help
Click to expand...
Click to collapse
I did that once flashing it with stock and nothing...
fran41 said:
I did that once flashing it with stock and nothing...
Click to expand...
Click to collapse
my last commands to mount efs (make sure that busybox binaries are installed from the application)
Code:
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10 /efs
or
Code:
busybox mount -w -t ext4 /dev/block/mmcblk0p10 /efs
you can try also to flash the modem twice in odin as "phone"
if not, i guess you have the service center option
samersh72 said:
my last commands to mount efs (make sure that busybox binaries are installed from the application)
Code:
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10 /efs
or
Code:
busybox mount -w -t ext4 /dev/block/mmcblk0p10 /efs
you can try also to flash the modem twice in odin as "phone"
if not, i guess you have the service center option
Click to expand...
Click to collapse
This doesn't work:
[email protected]:/ # busybox mount -w -t ext4 /dev/block/mmcblk0p10 /efs
busybox mount -w -t ext4 /dev/block/mmcblk0p10 /efs
mount: mounting /dev/block/mmcblk0p10 on /efs failed: Invalid argument
This works:
255|[email protected]:/ # mke2fs /dev/block/mmcblk0p10
mke2fs /dev/block/mmcblk0p10
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
3488 inodes, 13952 blocks
697 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=14417920
2 block groups
8192 blocks per group, 8192 fragments per group
1744 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[email protected]:/ #
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10 /efs
mount -w -t ext4 /dev/block/mmcblk0p10 /efs
[email protected]:/ #
Now I go to /efs in root explorer and there's a folder lost+found
Hi,
I am unable to edit build.prop (flashing B15 and B13-chinese bootstack enabled nav bar - I want to remove it) as I can not mount /system as RW. When doing so, either via Terminal, ADB Shell or simply a file explorer app, I generally get a "Device busy" error or some other random error.
I have tried those commands so far in Shell:
mount -o remount,rw /system
mount -o remount,rw -t ext4 /dev/block/bootdevice/by-name/system /system
All commands have been tried on the three available kernels.
Any help is much appreciated!