Related
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
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
Hey guys,
Here's a dump of /system from the Google I/O GT10.1. Let me know if there's anything else you're interested in.
http://www.mediafire.com/?hmjy4w04u9cb4j4
smaskell said:
Hey guys,
Here's a dump of /system from the Google I/O GT10.1. Let me know if there's anything else you're interested in.
http://www.mediafire.com/?hmjy4w04u9cb4j4
Click to expand...
Click to collapse
EDIT: Haha fail wasn't even thinking.....
Thanks mate. Can you dump boot and recovery as well? Not even sure if you can, but...
I could if I knew where they were. Someone more knowledgeable than I would probably know where they usually are. Unfortunately, I cannot search the device because most standard commands are not available(find, grep, etc.)
smaskell said:
I could if I knew where they were. Someone more knowledgeable than I would probably know where they usually are. Unfortunately, I cannot search the device because most standard commands are not available(find, grep, etc.)
Click to expand...
Click to collapse
Cool. Thanks.
Have you tried adding busybox? Im surprised that the root 'package' didn't include them. I think Titanium Backup will add it for you but not the symlinks AFAIK so you need to prefix each command with busybox. eg:
Code:
busybox chmod +x <file>
it won't let me create a link to /system/bin/ because it's stuck at read only. I created a thread about this already, but does anyone know how to remount /system? I've tried the standard ways and they don't seem to work
This worked for me:
mount -o remount,rw /system
If all else fails, use Root Explorer to remount /system
Just thinking "out loud" here, but would it be fair to say that if someone could extract the boot and recovery images from these google 10.1's that they could be flashed onto a 10.1v with Odin or fastboot and allow the 10.1v to be rooted in the same way as the 10.1g?
That's what I'm hoping
Sent from my GT-P7100 using XDA Premium App
ObsidianX said:
This worked for me:
mount -o remount,rw /system
Click to expand...
Click to collapse
wow, that was stupid of me. I was trying
mount -o remount,rw /dev/block/mmcblk0p4 /system
but obviously that isn't needed.
Thanks
alright, so I have busybox working
but all the tutorials I've found have said to use
cat /proc/mtd
to find out what to pull but for me, it just returns
dev: size erasesize name
also, they say to use
cat /dev/mtd/mtdX > /sdcard/mtdX.img
but /dev/mtd doesn't exist on this device
any ideas what I could be doing wrong?
smaskell said:
alright, so I have busybox working
but all the tutorials I've found have said to use
cat /proc/mtd
to find out what to pull but for me, it just returns
dev: size erasesize name
also, they say to use
cat /dev/mtd/mtdX > /sdcard/mtdX.img
but /dev/mtd doesn't exist on this device
any ideas what I could be doing wrong?
Click to expand...
Click to collapse
Stupid question, but you did do a
Code:
su
before running these commands?
Sometimes it's the simple things
it certainly wouldn't be the first time I'd missed something as blatantly obvious as that, but no I did remember this time. That's not to say that I'm not missing something else that should be completely obvious, but I did at least remember to run it as root.
smaskell said:
it certainly wouldn't be the first time I'd missed something as blatantly obvious as that, but no I did remember this time.
Click to expand...
Click to collapse
Haha - yeah, Ive certainly been stumped by simpler things than that. Usually success if followed by a facepalm
Really appreciate your persistence with this!
Could you possibly post the output of:
Code:
adb shell mount
and
Code:
adb shell su ls -l /cache
You should see from this output which device is mounted as /cache and how the /cache/recovery is mounted/linked.
certainly
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
debugfs /sys/kernel/debug debugfs 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/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,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
Code:
drwxrwx--- root root 1969-12-31 16:00 lost+found
drwxrwx--- system cache 2011-05-11 23:38 recovery
in /cache/recovery/last_log, I see this(among other things)
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) '(null)' 0000 '(null)' 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) '(null)' 0000 '(null)' 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) '(null)' 0000 '(null)' 0
3 /boot emmc /dev/block/mmcblk0p3 (null) '(null)' 0000 '(null)' 0
4 /system ext4 /dev/block/mmcblk0p4 (null) '(null)' 0000 '(null)' 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) '(null)' 0000 '(null)' 0
6 /data ext4 /dev/block/mmcblk0p8 (null) '(null)' 0000 '(null)' -16384
I'll try pulling mmcblk0p2 and 3
Edit: here they are. Hopefully this is what you were looking for
or not.. I tried uploading twice and both times it appeared to succeed but they're not showing up. let's try again.
still not working. let's try mediafire
http://www.mediafire.com/file/r37q8vluzshkdu8/boot.img
http://www.mediafire.com/file/bhi4q2wrqgl2ms5/recovery.img
Fantastic! Thanks again.
Downloading now although I just discovered I have blown my 120Gb/month allowance in 14 days so it may take a while to download at 256k
EDIT: smaskell, you are truly a champ! Recovery works on the 10.1v so I now have root!
Will be posting a guide here and asking all to thank smaskell
http://forum.xda-developers.com/showthread.php?t=1079781
smaskell said:
or not.. I tried uploading twice and both times it appeared to succeed but they're not showing up. let's try again.
still not working. let's try mediafire
http://www.mediafire.com/file/r37q8vluzshkdu8/boot.img
http://www.mediafire.com/file/bhi4q2wrqgl2ms5/recovery.img
Click to expand...
Click to collapse
You need to zip them. XDA only accepts ZIPs and media files for upload. Only discovered this myself yesterday
excellent! just glad I could help =]
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.
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.