Related
I'm not the original author of this, but I changed a few commands to make it work with the Vibrant. I found it here:
http://android.modaco.com/content/htc-hero-hero-modaco-com/295691/easy-system-remount-script/
Requires busybox.
Take this and save it as a file named "remount" or unzip it from attached archive
#!/system/bin/sh
#
# Remount /system partition
case "$1" in
ro)
echo "Setting /system to RO (read only)"
mount -o ro,remount -t rfs /dev/block/stl9 /system
echo ""
echo "Current status of /system mount:"
mount |busybox grep "/system rfs"
echo ""
;;
rw)
echo "Setting /system to RW (read write)"
mount -o rw,remount -t rfs /dev/block/stl9 /system
echo ""
echo "Current status of /system mount:"
mount |busybox grep "/system rfs"
echo ""
;;
status)
echo ""
echo "Current status of /system mount:"
mount |busybox grep "/system rfs"
echo ""
;;
*)
echo "Valid input format:"
echo " remount [ro|rw|status]"
echo " ro = read only (default)"
echo " rw = read write (to make modifications)"
echo " status = current mount mode"
echo ""
echo "Current status of /system mount:"
mount |busybox grep "/system rfs"
echo ""
exit 1
esac
Click to expand...
Click to collapse
From Windows:
adb push c:\path\to\remount /sdcard/
adb shell
su
mount -o rw,remount -t rfs /dev/block/stl9 /system
busybox mv /sdcard/remount /system/bin/
chmod 755 /system/bin/remount
remount ro
Ctrl+C. Tada!
I have Android SDK on my pc. I got Busybox installed on the phone. when I use command prompt to navigate to \tools directory and i type adb remount, i get the error message of "remount failed: no such file or directory"
Is there something im doing wrong here?
Please help
Sent from my SAMSUNG-SGH-I897 using XDA App
I've never used the command adb remount. Only adb shell and adb devices.
Sent from my SAMSUNG-SGH-I897 using XDA App
If I use adb shell it doesnt let me push files into certain folders. It says push is not a command... I'm trying to change my bootscreen
Sent from my SAMSUNG-SGH-I897 using XDA App
Hmm, I would help you if I could, but I don't know the steps for changing the boot screen. I haven't had the need for adb remount, sorry.
Sent from my SAMSUNG-SGH-I897 using XDA App
Just curious if you made sure usb debugging is on.
I've also never used the adb remount, but as for your comment about pushing... push isn't ran from "adb shell"
you should be doing "adb push <file to push> /path/to/where/it/goes/<file>"
Of course this needs root and, in places where the NAND is mounted as read only, you must do the remount option with r/w
There are tons of guides on how to do this on our forum, but I'm too lazy to find them.
The thing is, I'm already rooted so I don't know why I can't do those commands. I will try to mount with "adb remount r/w"?
Sent from my SAMSUNG-SGH-I897 using XDA App
flashman2002 said:
Just curious if you made sure usb debugging is on.
Click to expand...
Click to collapse
yes i have usb debugging mode on.
i tried adb remount r/w and i get the following message:
D:\ANDROID SDK\android-sdk-windows>cd tools
D:\ANDROID SDK\android-sdk-windows\tools>adb remount r/w
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
D:\ANDROID SDK\android-sdk-windows\tools>
can somebody please point me a a guide that works. the ones that ive searched for does not seem to work for me. complete newb here
I get exactly the same thing but can't seem to find any help
I was having a similar issue. Maybe I can help.
First, I am already rooted and have busybox installed. Don't know if that matters, but can't hurt.
Here's what you can do:
Code:
C:\Program Files\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
[COLOR="Red"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
At this point, we can see that /system is mounted at /dev/block/stl9. With that knowledge:
Code:
$ su
# mount -o remount,rw /dev/block/stl9 /system
Now your free to do whatever it is you were trying to do. When you're done, don't forget to :
Code:
# mount -o remount,ro /dev/block/stl9 /system
That should do it. Standard disclaimer, not responsible, blah,blah,blah...
How can I add these commands as aliases to the phone's shell?
shilob said:
I was having a similar issue. Maybe I can help.
First, I am already rooted and have busybox installed. Don't know if that matters, but can't hurt.
Here's what you can do:
Code:
C:\Program Files\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
[COLOR="Red"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
At this point, we can see that /system is mounted at /dev/block/stl9. With that knowledge:
Code:
$ su
# mount -o remount,rw /dev/block/stl9 /system
Now your free to do whatever it is you were trying to do. When you're done, don't forget to :
Code:
# mount -o remount,ro /dev/block/stl9 /system
That should do it. Standard disclaimer, not responsible, blah,blah,blah...
Click to expand...
Click to collapse
Everything is fine until I get to
$ su
I get "Permission denied"
Hmm... anyone has any tips? Thanks!
when you type su into the command prompt, you should get a pop-up on your phone saying unknown is requesting superuser permissions and you need to allow it or you will get denied permission.
Thanks! I passed that.. Now Im confused about whats the next step to push an apk into /system/app. I tried exiting from shell ("exit" twice until I saw C:\Program Files\android-sdk-windows\tools>) and then tried adb push.... but again I got No permission message ..
any advice?
jvanja said:
Thanks! I passed that.. Now Im confused about whats the next step to push an apk into /system/app. I tried exiting from shell ("exit" twice until I saw C:\Program Files\android-sdk-windows\tools>) and then tried adb push.... but again I got No permission message ..
any advice?
Click to expand...
Click to collapse
Did you do the "mount -o remount,ro ..." before you exited the shell ? sounds like your still on Read-only .
-First thing copy the .apk app into the sdk tools folder.
-Then do the following
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
-Now from your windows command prompt in sdk tools folder
adb push my_app.apk /system/app
-Once your finish
adb reboot
After the reboot your /system is returned to it's original read-only state.
Thats exactly what I did..:/ Does shell give you a confirm that you got the rw rights after doing:
mount -o remount,rw /dev/block/stl9 /system??
In my case it only responded with the same line below..
jvanja said:
Thats exactly what I did..:/ Does shell give you a confirm that you got the rw rights after doing:
mount -o remount,rw /dev/block/stl9 /system??
In my case it only responded with the same line below..
Click to expand...
Click to collapse
No it wont say anything. After you've done the remount,rw check your mount with "mount" in the shell. The /dev/block/stl9 /system line should read like this.
Code:
/dev/block/stl9 /system rfs [color=green]rw[/color],vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
rather then
Code:
/dev/block/stl9 /system rfs [color=red]ro[/color],vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
Hey there,
it's known that ext4 with disabled journaling is little faster than default, but it is also less reliable.
This can result in screwed up homescreens and force-closes after reboot/shutdown/battery pull.
I have successfully re-enabled journaling for system and cache partition, but it seems not to work correctly for data partition, at least for me. Can you help?
Code:
echo ..............system Partition...............
/sbin/busybox umount -l /system
/sdcard/tmp/tune2fs -O +has_journal -c 5 -i 5d -m 0 -o journal_data_ordered /dev/block/mmcblk0p1
fsck.ext4 -Dfy /dev/block/mmcblk0p1
/sbin/busybox mount -t ext4 -o nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=ordered,noauto_da_alloc /dev/block/mmcblk0p1 /system
echo ...............done...............
echo ...............cache Partition...............
/sbin/busybox umount -l /cache
/sdcard/tmp/tune2fs -O +has_journal -c 100 -i 100d -m 0 -o journal_data_writeback /dev/block/mmcblk0p2
fsck.ext4 -Dfy /dev/block/mmcblk0p2
/sbin/busybox mount -t ext4 -o nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=ordered,noauto_da_alloc /dev/block/mmcblk0p2 /cache
echo ...............done...............
echo ...............data Partition...............
/sbin/busybox umount -l /data
/sdcard/tmp/tune2fs -O +has_journal -c 5 -i 5d -m 0 -o journal_data_ordered /dev/block/mmcblk0p8
fsck.ext4 -Dfy /dev/block/mmcblk0p8
/sbin/busybox mount -t ext4 -o nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=ordered,noauto_da_alloc /dev/block/mmcblk0p8 /data
sync
echo ...............done...............
Semi-finished:
Flash journaling.zip via CWM to enable back journaling
Download
Download 'terminal emulator' from market and type the following to test if it works.
If 'has_journal' is present then journaling is enabled.
For /system
Code:
/system/bin/tune2fs -l /dev/block/mmcblk0p1 | grep features
For /cache
Code:
/system/bin/tune2fs -l /dev/block/mmcblk0p2 | grep features
For /data
Code:
/system/bin/tune2fs -l /dev/block/mmcblk0p8 | grep features
Please post feedback if it works for you (fully)!
nice good work!
Thanks!
Another easy, though more time consuming, way to re-enable journaling is to let CWM do it by a complete backup and restore.
(You can also switch between ext3 and ext4 by changing the file names in clockworkmod/backup/.../ and of course also in the nandroid.md5 file.)
Please post feedback if it works for you (especially for data partition)
Hey guys i cant seem to root my phone I've tried to use z4root but it does not work.
I also tried superonclick
1. turned usb debugging on
2. removed my SD card
3. plugged in phone
4. started root process and got this message:-
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$
export TEMPRANDOM=75288;export PS1=END:$TEMPRANDOM;getprop ro.build.version.release
export PS1=""
$ 2.2.1
END:75288
export TEMPRANDOM=42250;export PS1=END:$TEMPRANDOM;getprop ro.product.manufacturer
export PS1=""
samsung
END:42250
export TEMPRANDOM=37017;export PS1=END:$TEMPRANDOM;getprop ro.product.model
export PS1=""
GT-I9003
END:37017
export TEMPRANDOM=62657;export PS1=END:$TEMPRANDOM;getprop ro.build.version.incremental
export PS1=""
XWKB4
END:62657
export TEMPRANDOM=34626;export PS1=END:$TEMPRANDOM;ls -l /system/xbin/su
export PS1=""
/system/xbin/su: No such file or directory
END:34626
export TEMPRANDOM=90536;export PS1=END:$TEMPRANDOM;ls -l /system/bin/su
export PS1=""
/system/bin/su: No such file or directory
END:90536
export TEMPRANDOM=67512;export PS1=END:$TEMPRANDOM;chmod 755 /data/local/tmp/busybox
export PS1=""
END:67512
export TEMPRANDOM=36865;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/boomsh
export PS1=""
END:36865
export TEMPRANDOM=49199;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/sh
export PS1=""
END:49199
export TEMPRANDOM=69085;export PS1=END:$TEMPRANDOM;chmod 700 /data/local/tmp/zergRush
export PS1=""
END:69085
export TEMPRANDOM=58620;export PS1=END:$TEMPRANDOM;cd /data/local/tmp/
export PS1=""
END:58620
export TEMPRANDOM=36046;export PS1=END:$TEMPRANDOM;./zergRush
export PS1=""
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a Froyo ! 0x00017108
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000170f0
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[+] Overseer found a path ! 0x000170f0
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[-] Zerglings did not leave interesting stuff
END:36046
export TEMPRANDOM=41873;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount -o rw,remount /system
export PS1=""
mount: permission denied (are you root?)
END:41873
export TEMPRANDOM=72969;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount
export PS1=""
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl9 on /system type rfs (ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/mmcblk0p3 on /data type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
debugfs on /debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime ,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_uti me=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
END:72969
export TEMPRANDOM=34249;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount -o rw,remount /dev/block/stl9 /system
export PS1=""
mount: permission denied (are you root?)
END:34249
export TEMPRANDOM=24980;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount
export PS1=""
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl9 on /system type rfs (ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/mmcblk0p3 on /data type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
debugfs on /debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime ,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_uti me=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
END:24980
export TEMPRANDOM=96442;export PS1=END:$TEMPRANDOM;mount -o rw,remount /dev/block/stl9 /system
export PS1=""
mount: Operation not permitted
END:96442
-----------------------------------------------------------
Additional info
Firmware version 2.2.1
Baseband version I9003XXKB1
Kernel version 2.6.32.9 [email protected]#1
Build number FROYO.XWKB4
Any help would be much appreciated thanks guys
Hello,
First of all Im posting this after a long search so plz bear with me.
Ive read most of the guides but I want to understand it a bit more,and just to be clear Im not asking to explain every thing(although it could be nice ^^) but point me to some reading material.
Ill use #Darkyy guide for example : http://forum.xda-developers.com/showthread.php?t=960946
*I hope ur ok with this (I couldn't post on ur thread cuz im anoob here..)
Code:
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
tar -H ustar -c factoryfs.rfs cache.rfs modem.bin zImage > darky.tar
md5sum –t darky.tar >> darky.tar
mv darky.tar darky.tar.md5
dd if=/dev/block/bml2 of=/sdcard/darky.pit bs=4096
Q-I want to understand what each command is for?
Q-How do I know the location and roll of every file (so this can be use on different devices)? *Edit A-I found that the files are in /dev/block wich brings me to the next question:
Q-How can I know With file is witch ? (right now I cant find the bml7 partition(kernel\zimage).
Q- Is there a guide about Odin- the roll of every file, what it contains, where its on the device?
*** Plz help me fully understand the process and not just coping it... ***
Thx for every reply and information
***Edit***
After reading http://forum.xda-developers.com/showthread.php?t=1171211&highlight=make+odin
I got to this point:
I backed up the factory and the cache partition, but I cant find the kernal (zimage)partition (bml7).
For some unknown reason my 'mount' chart is as follows:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock2 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock6 /datadata yaffs2 rw,relatime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:24 /mnt/emmc vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
How can I see other partitions ?
Is there any way to know witch is witch in the /dev/block directory?
Plz Help me ..
**Edit**
I used "ls command" (Astor browser actually to brows /dev/block and I cant pinpoint the kernel file)
I tried to make a tar file but I end up with " Read-only file system" Error.
the commands I Used:
Code:
126|[email protected]:/ # sh
sh
[email protected]:/ # mount -o remount,rw /dev/block/mtdblock2 /system
mount -o remount,rw /dev/block/mtdblock2 /system
[email protected]:/ # dd if=/dev/block/mtdblock2 of=/sdcard/test/factoryfs.rfs bs=4096
sdcard/test/factoryfs.rfs bs=4096 <
/dev/block/mtdblock2: read error: I/O error
29952+0 records in
29952+0 records out
122683392 bytes transferred in 38.834 secs (3159174 bytes/sec)
[email protected]:/ # dd if=/dev/block/mtdblock3 of=/sdcard/test/cache.rfs bs=4096
dd if=/dev/block/mtdblock3 of=/sdcard/test/cache.rfs bs=4096
4480+0 records in
4480+0 records out
18350080 bytes transferred in 5.626 secs (3261656 bytes/sec)
[email protected]:/ # dd if=/dev/block/bml12 of=/sdcard/test/modem.bin bs=4096
dd if=/dev/block/bml12 of=/sdcard/test/modem.bin bs=4096
3072+0 records in
3072+0 records out
12582912 bytes transferred in 1.985 secs (6338998 bytes/sec)
[email protected]:/ # tar -c cache.rfs >> CSC.tar
tar -c cache.rfs >> CSC.tar
sh: cannot create CSC.tar: Read-only file system
The "read only" message is because you're on your root folder. Move up to your sd card:
Code:
cd /sdcard/test/
tar -c cache.rfs > CSC.tar
FaultException said:
The "read only" message is because you're on your root folder. Move up to your sd card:
Code:
cd /sdcard/test/
tar -c cache.rfs > CSC.tar
Click to expand...
Click to collapse
Thx. Didn't notice that XD
Some one else about the other questions plzz
Can't find zImage mount point in Slim Jelly Bean (Android 4.1)
I think I have the same situation as yours. I tried everything, but couldn't find the /dev/block device associated to zImage...
deadwolf666 said:
Thx. Didn't notice that XD
Some one else about the other questions plzz
Click to expand...
Click to collapse