I'm new here and have no rights to post in dev section.
I have tried many possible tools and tips for getting root on o4x... No success yet..
But I found out that SupeOneClick tool could write on some sections on /data.
The main problem remains that we couldn't get WRITE access to /system section.
I'm not expert on Linux but I let run some scripts on /system/bin and /root... Till now unfortunately no success.
I found interesting scripts for FOTA like lgdms.fota_update.rc.
As I see our system path is /dev/block/Platform/sdhci-tegra.3/by-name/APP /system
can someone of devs confirm that?
That would mean all other tools trying to gain access with "mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system"
will not help us anyway.. Or I'm wrong?
cat /proc/mounts cmd brings me no other /system path...
Here what I get on "cat /proc/mounts":
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ cat /proc/mounts
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
debugfs /sys/kernel/debug debugfs rw,relatime 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,resuid=1000,errors=continue,user_xattr,acl,barrier=1,nodelalloc,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAL /cal ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/MLT /mpt ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/DRM /persist-lg ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:17 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
P.S. Excuse for my bad English.
Androgenic said:
I'm new here and have no rights to post in dev section.
I have tried many possible tools and tips for getting root on o4x... No success yet..
But I found out that SupeOneClick tool could write on some sections on /data.
The main problem remains that we couldn't get WRITE access to /system section.
I'm not expert on Linux but I let run some scripts on /system/bin and /root... Till now unfortunately no success.
I found interesting scripts for FOTA like lgdms.fota_update.rc.
As I see our system path is /dev/block/Platform/sdhci-tegra.3/by-name/APP /system
can someone of devs confirm that?
That would mean all other tools trying to gain access with "mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system"
will not help us anyway.. Or I'm wrong?
cat /proc/mounts cmd brings me no other /system path...
Here what I get on "cat /proc/mounts":
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ cat /proc/mounts
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
debugfs /sys/kernel/debug debugfs rw,relatime 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,resuid=1000,errors=continue,user_xattr,acl,barrier=1,nodelalloc,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAL /cal ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/MLT /mpt ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/DRM /persist-lg ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:17 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
P.S. Excuse for my bad English.
Click to expand...
Click to collapse
Thanks for posting
I also have two files that might be worth having a look at.
http://db.tt/dPOQmB5H
Sent from my LG-P880 using xda premium
WOW!
Thanks... Thats interesting to look at...
Can you tell me how you dump sys files? I would take a look on some other too..
ianford10 said:
Thanks for posting
I also have two files that might be worth having a look at.
Sent from my LG-P880 using xda premium
Click to expand...
Click to collapse
So I found a complete dump of /system... Thats fine.
Maybe there would be something that would help to gain write access to /system.
Related
Root Explorer is unable to re-mount /system in R/W. The button simply does nothing when I press it. I am also unable to update AdFree, which re-writes the hosts file in /system. Anything I can do to remedy this?
stupid question, but I have to ask: are you rooted?
o0beaner said:
Root Explorer is unable to re-mount /system in R/W. The button simply does nothing when I press it. I am also unable to update AdFree, which re-writes the hosts file in /system. Anything I can do to remedy this?
Click to expand...
Click to collapse
Try backing all the way out of the folder by pressing the (...) button at the top. Keep pressing that until you are at the root folder (it won't be there anymore). Now press the r/w button at the top. It should change, and will stay changed once you go back into the other folders.
Sorry, it was early, and my brain wasn't good for specifics. I am rooted, running SRE 1.2.
Root is mounted R/W, but /system will not change state. Is there anything I can try from the terminal?
Same problem here on my wife's Captivate. I used SRE 1.2.1a and noticed that I was still seeing ads. So I tried installing Adfree and updating the host file and ran into the same mounting error.
On my own Captivate, I had used 1-Click root before SRE came out and no problems updating there.
same here no ADFREE in SREv2b7. I tried R/W on Root explorer and even trying to change permissions on sys,system, data/data, and still get same error as you guys re-mount /system.
Let's see where /system is mounted:
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
# exit
$ exit
Thanx but that didnt work this are my setting
C:\AndroidSDK\tools>adb shell
$ mount
mount
rootfs / rootfs rw 0 0
proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
/dev/block/mmcblk0p4 /data ext4 rw,barrier=1,data=ordered 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 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
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=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
$
IM STILL GETTING failed to remount system partition read-only
I can't update AdFree either.
shilob said:
Let's see where /system is mounted:
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
# exit
$ exit
Click to expand...
Click to collapse
Didn't work for me either--still got the "failed to mount read-only file system" or something like that. Also, when I tried the "-o remount,ro" adb said device or resource busy. I'm pretty sure this has been discussed in the SRE thread, but i really, really, want adree to work
Can someone please provide the output of the "mount" command from a Stock Captivate on Froyo (no lagfix)?
* Connect Captivate via USB
* open up a terminal window
* adb shell
* mount
* copy/paste the entire results (or place in a text file and attach to your response)
Thank you in advance!
-h8
EDIT.....sorry, i just realized this said STOCK froyo....lol. this is andromeda3. derp
Code:
/ $ mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 ro,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/ $
bump.............
Can Some One Dump Boot.img ( Kernel) from device? Asap!
Cheers..!
eaglerazor123 said:
Can Some One Dump Boot.img ( Kernel) from device? Asap!
Cheers..!
Click to expand...
Click to collapse
https://www.dropbox.com/s/vv94z7kazvfkdig/boot.img sent link in pm also
b3ltazar said:
https://www.dropbox.com/s/vv94z7kazvfkdig/boot.img sent link in pm also
Click to expand...
Click to collapse
Firmware no?! And i need mount partitions too!
adb mount
Houston, The EAGLE has landed! :laugh:
eaglerazor123 said:
Can Some One Dump Boot.img ( Kernel) from device? Asap!
Cheers..!
Click to expand...
Click to collapse
Our first interested Dev, people, whatever he wants, give it to him, beer, sex, etc... :victory:
easyguy said:
Our first interested Dev, people, whatever he wants, give it to him, beer, sex, etc... :victory:
Click to expand...
Click to collapse
Mount partitions would be enough for me to keep going!
run this in adb
adb mount
cheers..!
eaglerazor123 said:
Mount partitions would be enough for me to keep going!
run this in adb
adb mount
cheers..!
Click to expand...
Click to collapse
Is this what your looking for:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ord
ered 0 0
/dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrie
r=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier
=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0133,dmas
k=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0133,
dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
/dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,b
arrier=1,data=ordered 0 0
/dev/block/vold/179:28 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,n
odiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp43
7,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
tmpfs /mnt/sdcard/external_sd tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodir
atime,size=0k,mode=755,gid=1000 0 0
tmpfs /mnt/sdcard/usbStorage tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodira
time,size=0k,mode=755,gid=1000 0 0
/dev/block/vold/179:33 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noex
ec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,c
odepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noat
ime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage
=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
And this one too
/proc/mtd
eaglerazor123 said:
And this one too
/proc/mtd
Click to expand...
Click to collapse
That was the entire output.
I did adb shell, mount in windows terminal.
How do I get the one you want?
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/vold/179:28 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
tmpfs /mnt/sdcard/external_sd tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
tmpfs /mnt/sdcard/usbStorage tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
/dev/block/vold/179:33 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.mobilityflow.torrent-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
Here ya go.
eaglerazor123 said:
Can Some One Dump Boot.img ( Kernel) from device? Asap!
Cheers..!
Click to expand...
Click to collapse
Here is the boot.img http://forum.xda-developers.com/showthread.php?t=1837907. Fourth in the list.
Hi All,
Somehow my IMEI number become 000000000, I do not know exactly when and how that happened. I am currently on custom CM10.1 rom.
I tried to back to stock rom 2.3 from ODIN and IMEI was still 000000000.
In stock 2.3 /efs folder exists, in my current rom there is no /efs folder.
I tried some methods, like: http://forum.xda-developers.com/showthread.php?t=1264021 but unfortunately on i9001 /efs folder looks different
My phone works well on my operater, but I do not know will it wokr when I go for holiday in other country.
In second post I will put mu current mount state.
Any suggestions are welcome.
mount
Code:
[email protected]:/ # mount
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
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p15 /system ext4 ro,relatime,data=ordered 0 0
/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,nobarrier,data=ordered 0 0
/dev/block/mmcblk0p17 /data ext4 rw,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/vold/179:33 /storage/sdcard1 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:28 /storage/sdcard0 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:28 /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 /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.kiloo.subwaysurf-2 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
I have found here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001 that IMEI is stored at partisions /efs and /persist,
I do not have them mounted, but they exists.
I can mount them manually and see content from adb shell.
I also created backup using following command.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/sdcard/efs.ext4 bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/persist.ext4 bs=4096"
Any idea how to get them mounted on system boot ?
" If it aint broken then don't fix it"..
Enter these in in CMD:
adb shell su -c "dd if=/dev/block/mmcblk0p27 of=/sdcard/efs.ext4 bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/persist.ext4 bs=4096"
There is no need for you to mount anything. If it still works dont touch it.
Q&A for Read-Only Filesystem?
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Read-Only Filesystem?. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
adb mount problems with read only, need read/write
cbstryker said:
Maybe you're typing it in too literally. It should actually read like this:
mount -o remount,rw /dev/block/mtdblock3 /system
There was a typo with -oremount, there should be a space after -o.
Hope that helps.
PS. That command worked for me on a device where everything else failed.
Click to expand...
Click to collapse
Ok, when I type just "mount" in, I get this long string of info back:
mount
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/secure tmpfs rw,relatime,mode=700 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
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p35 /system ext4 ro,noatime,data=ordered 0 0
/dev/block/mmcblk0p37 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc
,data=ordered 0 0
/dev/block/mmcblk0p36 /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p25 /devlog ext4 rw,nosuid,nodev,noatime,errors=continue,data=
ordered 0 0
/dev/block/mmcblk0p32 /carrier ext4 rw,nosuid,nodev,noatime,grpid,data=ordered 0
0
/dev/block/mmcblk0p16 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,all
ow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-
ro 0 0
/dev/block/mmcblk0p17 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:38 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,relatime,uid
=1000,gid=1015,fmask=0202,dmask=0202,allow_utime=0020,codepage=cp437,iocharset=i
so8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro,discard 0 0
/dev/block/vold/179:38 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid
=1000,gid=1015,fmask=0202,dmask=0202,allow_utime=0020,codepage=cp437,iocharset=i
so8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro,discard 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:65 /storage/sdcard0/ext_sd vfat rw,dirsync,nosuid,nodev,noex
ec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp
437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
but when I try typing the command in that is given in above posts, get this:
1|[email protected]:/ # mount -0 remount,rw /dev/block/mtdblock3/system
mount -0 remount,rw /dev/block/mtdblock3/system
unknown option -- 0mount: invalid option -0
adb remount gets this:
[email protected]:/ # adb remount
adb remount
error: device not found
Any help with this is much appreciated..
Thanks,
lee