Related
I'm running 2.03 and my browser started crashing so I did a reboot. Now I keep looping between the ViewSonic screen and gtablet screen. I've tried several restores through ClockWorkMod and it still doesn't work. I thought I could try to do the upgrade.zip off of a sd card but how do I get the system to recongize it and not the internal memory?
Stupid question : Have you done a user data wipe/system data wipe from CW?
If cw is not seeing the internal sd and the updates located on the internal sd are not working with full users data wipe, then a nvflash push from pc will have to be done to vanilla tnt, then do an update to get clockwork back, then tnt lite 2.0 with clockwork?
You might need to do a re-partition of your SD card (or rather, of the internal SD card memory) from clockwork mod. That has gotten other people out of a boot loop. This most likely has something to do with partitions getting corrupted, which seems to occasionally happen when you are flashing ROMs. You might want to search the forum for SD card partition and boot loop, I know several people have had the same issue.
There is also the APX mode as a backup mechanism if that fails. Search forum for that one too - it's basically a backup to the normal CW or other recovery that lets you flash a fresh ROM even if all else has failed. But I don't think you need to go there if your recovery is still working fine.
arrow21 said:
Stupid question : Have you done a user data wipe/system data wipe from CW?
Click to expand...
Click to collapse
Yes, tried nearly everything I can in Clock and nothing changes the loop. I thought in the worst case you could always find a way to get the system back to it's original state but no luck so far.
another option is this
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
I have never done the partiton of my sdcard... so I guess that might work also.
arrow21 said:
another option is this
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
I have never done the partition of my sdcard... so I guess that might work also.
Click to expand...
Click to collapse
HELP!!! I think my data partition just go hosed, all I tried to do was restore a backup since I was getting a lot of FC, all trying to access my data folder according to logcat....what do I do, will redoing the partition of my sdcard fix the errors below. How do I repartition and what settings do I use? I was trying to do the restore since I too got stuck in reboot loop. I have the logcat ouput if any dev is interested in seeing it.
Trying to restore backup in clockworkmod I get this:
ClockworkMod Recovery v2.5.1.1-bekit-0.8
Checking MD5 sums...
Erasing boot before restore
Restoring system...
Restoring data...
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Error mounting /data/!
Skipping format...
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Can't mount /data/!
rcgabriel said:
You might need to do a re-partition of your SD card (or rather, of the internal SD card memory) from clockwork mod. That has gotten other people out of a boot loop. This most likely has something to do with partitions getting corrupted, which seems to occasionally happen when you are flashing ROMs. You might want to search the forum for SD card partition and boot loop, I know several people have had the same issue.
There is also the APX mode as a backup mechanism if that fails. Search forum for that one too - it's basically a backup to the normal CW or other recovery that lets you flash a fresh ROM even if all else has failed. But I don't think you need to go there if your recovery is still working fine.
Click to expand...
Click to collapse
rc, thanks for the help. Honestly partitioning is something I've never fully understood so I wasn't even sure how to do that. I went into CW and then advanced settings and chose to partition the sd card. The only problem is I didn't know what settings to use so I just used the first ones to pop up. After doing that I did a reboot and things worked fine.
I was going to go back and try a CW restore and see if I could get everything back but now it can't find the restore file. I assume that happened when I tried to reformat the card.
scmobileman said:
I was going to go back and try a CW restore and see if I could get everything back but now it can't find the restore file. I assume that happened when I tried to reformat the card.
Click to expand...
Click to collapse
The restore files were are stored on the internal sdcard, so when you formatted, you wiped them out...is my guess. You could have used adb to save them off before hand and then put them back after format.
For the benefit of others, here is how I fixed this:
-Boot into clockworkmod
-Used adb to copy off all sdcard files (including backup files to use in restore)
-Use CW to partition the sdcard (2048mb ext, 256mb swap)
-Tried to copy backup files back...see issues below
-Restore backup files
-Back to working tab
Two issues I had, one is that for the life of me, I could not get the backup files back onto the sdcard. adb must not like windows because it had issues copying the files back unless you copy them to the root of the device. Even then I tried to shell into the device and move the files to the sdcard, but then CW would not see the files, when I reboot the device and try again, the files were gone. I tried to just copy the update.zip file, again CW didn't see the file, and reboot caused it to disappear as well. I managed to mount the tab in USB mode and copy the files to the sdcard using windows. Afterwards CW didn't see the files either.
I figured the system image was good, rebooted to start from scratch, and the setup program ran. I tried to tap the screen bu nothing would happen. Issue two from the log, is that it the setup wizard ignores touch evens if there is no phone interface...reboot again, back into CW, and this time it saw my backup files, restore, then good to go.
My next step would have been to delete the setupwizard apk, wipe data, boot into android, copy backup files, reboot, restore, but not needed finally.
Have other people run into the above issue where you copy files to the sdcard uin adb while within CW, and the files don't stick. How do you get around this?
raydog.. thank you thank you thank you
thanks
raydog, your post helped greatly. thank you.
Life in LA said:
raydog, your post helped greatly. thank you.
Click to expand...
Click to collapse
Thanks, sad to say I am back in a reboot loop, so I have to do this all over again...uggg
I have shut my tablet off by holding down the power button and bypassing the shutdown screen, wonder if this corrupted the data partition.
I had the reboot problem when trying to load 2.0.0
My fix: Loaded original vanilla via sdcard (took two load tries) then retried 2.0.0 via sdcard and it worked.
please help to make my data read write
raydog153 said:
Have other people run into the above issue where you copy files to the sdcard uin adb while within CW, and the files don't stick. How do you get around this?
Click to expand...
Click to collapse
1|[email protected]:/sbin # su
[email protected]:/sbin # is
sh: is: not found
127|[email protected]:/sbin # cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/sbin # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/sbin # fs
sh: fs: not found
127|[email protected]:/sbin # df
Filesystem Size Used Free Blksize
/dev 407.7M 32.0K 407.6M 4096
/sys/fs/cgroup 407.7M 12.0K 407.7M 4096
/mnt/asec 407.7M 0.0K 407.7M 4096
/mnt/obb 407.7M 0.0K 407.7M 4096
/system 1.3G 443.6M 934.3M 4096
/efs 19.7M 8.1M 11.5M 4096
/data 11.9G 5.5G 6.3G 4096
/cache 689.0M 129.8M 559.1M 4096
/mnt/shell/emulated 11.9G 5.5G 6.3G 4096
[email protected]:/sbin # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 12640239 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
[email protected]:/sbin # format 259
sh: format: not found
127|[email protected]:/sbin # del
sh: del: not found
127|[email protected]:/sbin # mount /efs rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,remount /efs
[email protected]:/sbin # mount -o rw,remount /dev
[email protected]:/sbin # mount -o rw,remount /sys/fs/cgroup
[email protected]:/sbin # mount -o rw,remount /mnt/asec
[email protected]:/sbin # mount -o rw,remount /mnt/obb
[email protected]:/sbin # mount -o rw,remount /system
[email protected]:/sbin # mount -o rw,remount /syste
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,remount /efs
[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /cache
[email protected]:/sbin # mount -o rw,remount /mnt/shell/emulated
[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw, del /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,del /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # help
sh: help: not found
127|[email protected]:/sbin # Read-only file system
sh: Read-only: not found
127|[email protected]:/sbin # rw
sh: rw: not found
127|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin #
this is my partition table and errors for p3100.
please help me how to make it read write.
please mailm e the steps.
[email protected]
thanks in advance
I instaled root explorer and am trying to replace efs files from backup but i have a problem as can not mount ir as RW it is RO
Is there any way around that?
it looks like only efs folder have this problem
Is your phone rooted?
yes i just checked again if i rooted it and i did
$ cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp: can't create '/efs/nv_data.bin': File exists
$ rm /efs/nv_data.bin
rm /efs/nv_data.bin
rm: remove '/efs/nv_data.bin'? y
y
rm: can't remove '/efs/nv_data.bin': Read-only file system
any help???
i can not get efs to be rw
mount
rootfs on / type rootfs (rw,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)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/usb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /app-cache type tmpfs (rw,relatime,size=7168k)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data
=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (ro,relatime,barrier=1,data=ordered)
nil on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data
=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/dev/block/vold/179:11 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,
noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
#
Did you try to remount /efs in rw (instead of ro) ?
Yes and it remounts it instead of ext4 in ext3 i can delete and edit what i want no permission errors but once i leave hex editor it gets back to ro and all files I deletes reaiires and files i have changed show as unchanged and it gets RO. I feel that i am missinf some linux command to made this changes succesfull.
same problem my efs is read only and i would like to restore my efs, please help
mahatma said:
I instaled root explorer and am trying to replace efs files from backup but i have a problem as can not mount ir as RW it is RO
Is there any way around that?
it looks like only efs folder have this problem
Click to expand...
Click to collapse
Didnt try the app but have a look http://forum.xda-developers.com/showpost.php?p=16512129&postcount=73
Sent from my GT-I9100 using Tapatalk
ANNOUNCEMENT:
Official version that support most (including our) device has been released. See HERE
Hi All.
Here are the modified version of Online Android Backup from ORIGINAL THREAD. I've changed some codes to make it works for our HTC Legend.
How To Install:
Through CWM
1. Download from attachment onandroidv3.7_cwm.zip
2. Copy it to your sdcard
3. Reboot into recovery
4. Flash the file
Manual
1. Extract onandroid.zip attached and use adb/root explorer to push/copy the file onandroid to your /system/bin
2. change permission to rwxr-xr-x
How To use:
From PC:
1. Open terminal/command prompt
2. type adb shell
- if using CM9, type su to gain root access after step 2.
3. type onandroid
From your phone:
1. open terminal emulator, type su
2. type onandroid
UPDATE:
If you use ogo2's ROM HERE, please download SENSE_fix_tool.zip from attachment and flash it. Mediafire link are HERE
Changes:
12.06.2012: Initial modification from original version
13.06.2012: Power checking corrected
14.06.2012: Added CWM flashable file
20.06.2012: Update v3.7 from original developer. confirm to work in cm9
Changelogs from original developer:
:: Latest onandroid fixes from v3.7
:: Made "dd" not spit results.
:: Added partition detection for boot and recovery partitions.
02.07.2012: Fix for sense ROM
screenshots and file are attached.
Credits:
ameer1234567890 Original Developer
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
vriz27 said:
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
Click to expand...
Click to collapse
Yes, download the file from attachment (onandroid_CWM.zip)
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
smithchipz said:
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
Click to expand...
Click to collapse
Thanks. I just do some simple modification to the original version, praise to ameer1234567890 for the great tools.
Restoring is working fine with me but make sure you check the backup folder after onandroid is finish running and check if all required files is there especially if you do something else during the backup process.
Fix for sense ROM attached in 1st post.
feed3 said:
Fix for sense ROM attached in 1st post.
Click to expand...
Click to collapse
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
alligator_asl said:
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
Click to expand...
Click to collapse
That is due to an issue in XDA (one of the servers crashed). Should be fixed in a couple of days!
Sense fix
Sense fix tool uploaded to mediafire. Link in the post #1.
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
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/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type 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)
/dev/block/vold/179:1 on /mnt/secure/asec type 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)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Click to expand...
Click to collapse
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
ameer1234567890 said:
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
Click to expand...
Click to collapse
Here is it:
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /mnt/asec/sd ext3 rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback 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/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/nadsoft.physicscheatsheetsfree-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/jwtc.android.chess-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
How did you partition your sdcard? Which app2sd or link2sd version do you use?
Also, post output from below command!
Code:
echo $SD_EXT_DIREECTORY
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
alligator_asl said:
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
Click to expand...
Click to collapse
Thank you for the information. I am working on a fix.
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
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/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type 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)
/dev/block/vold/179:1 on /mnt/secure/asec type 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)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
Click to expand...
Click to collapse
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
feed3 said:
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
Click to expand...
Click to collapse
I have fixed this in the next version. Shall be releasing soon.
ameer1234567890 said:
I have fixed this in the next version. Shall be releasing soon.
Click to expand...
Click to collapse
Thanks ameer..
Can anyone help with this...
The phone is called the n7103, It's a chinese phone and the specs can be found here: https://my.dx.com/MyOrders/OrderDetail/130421001070495638
Root: Yes
Version: 4.1
Carrier: Three (UK)
My hosts files are wrong, so I can't connect to the play store and use some apps, my hosts file currently read:
127.0.0.1 localhost
#74.125.93.113 android.clients.google.com
#74.125.93.113 mtalk.google.com
Click to expand...
Click to collapse
I presume this is correct, if not please do correct me.
Now I want to use ADB to send the to the phone, however I can't for the life of me make the system read/write, The reason being I dont know what to mount, so I found the following instructions:
Very often when you want to write files to a particular partition on ADP1, you will get a "Permission Denied" if the partition is mounted read-only.
To get around this, you need to mount the partition read-write. Typically this is done with /system partition
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
(Replace /dev/block/mtdblock3 & /system with appropriate device path and mount point, as obtained from cat /proc/mounts)
Click to expand...
Click to collapse
I have looked in the /proc/mounts file and get the following read out:
rootfs / rootfs rw,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
/[email protected] /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected]_ro /system/secro ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:96 /mnt/sdcard2 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:6 /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:6 /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
Click to expand...
Click to collapse
So basically I get stuck at this part as I don't know what to type:
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 .........
I have looked for other methods including using totalcommander with root to edit hosts file but to no avail.
I can't push the file as the destination is not read write. I have also tried using terminal and chmoding the system folder as 777 but no joy.
There is also an app called "HOSTS EDITOR" however it wont allow me to insert the "#" character.
I am sorry for the very long post, I'd appreciate any help!
Thanks :good:
mount -o remount, rw /system
Click to expand...
Click to collapse
This returns no errors however when i then try the follwing command it fails.
[email protected]:/ # adb push hosts /etc/hosts
adb push hosts /etc/hosts
error: device not found
Click to expand...
Click to collapse
This phone was gently placed in a bin.
Sent from my GT-I9505 using XDA Premium 4 mobile app
adb is a program in your PC, not in Android itself, so this command:
philipkroberts said:
adb push hosts /etc/hosts
Click to expand...
Click to collapse
should be typed outside of the Android shell (type exit after you remount system, then try that command again).
Hi,
No matter what I do, I can't remount "/system" and "/" to RW. :crying:
Does anyone know how to resolve this issue?
I am running on KK 4.4.2 version 14.3.A.0.757.
My Current File System Status
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apps_log /mnt/idd ext4 rw,seclabel,nosuid,nodev,noexec,noatime,discard,nobarrier,data=ordered 0 0
tmpfs /storage/remote tmpfs rw,seclabel,relatime,size=1024k,nr_inodes=256,mode=750,gid=1028 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
[email protected]:/ #
You obviously do not have the permission to do that, so the question is, are you rooted, and if so root again and be sure to have the latest SuperSU installed with updated binaries.
Sent from my Z Ultra
LordManhattan said:
You obviously do not have the permission to do that, so the question is, are you rooted, and if so root again and be sure to have the latest SuperSU installed with updated binaries.
Sent from my Z Ultra
Click to expand...
Click to collapse
Yes, I am able to gain root access but unable to boot into recovery
Sent from my C6833 using XDA Premium 4 mobile app
[email protected] said:
Yes, I am able to gain root access but unable to boot into recovery
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What kernel are you on?
How did you get root?
Bootloader unlocked?
blueether said:
What kernel are you on?
How did you get root?
Bootloader unlocked?
Click to expand...
Click to collapse
My kernel version is 3.40-perf [email protected] #1 and bootloader is unlocked.
I gained root by downgrading my firmware to .532 version and install rooting using a program called Root_with_Restore_by_Bin4ry_v33. After rooting is successful, install dualrecovery and upgrade my firmware to .757 version by flashing a specific zip file via recovery followed by flash FTF with Flashtool.
Am I doing it correctly? Is there a better way to do it?
[email protected] said:
My kernel version is 3.40-perf [email protected] #1 and bootloader is unlocked.
I gained root by downgrading my firmware to .532 version and install rooting using a program called Root_with_Restore_by_Bin4ry_v33. After rooting is successful, install dualrecovery and upgrade my firmware to .757 version by flashing a specific zip file via recovery followed by flash FTF with Flashtool.
Am I doing it correctly? Is there a better way to do it?
Click to expand...
Click to collapse
I would try to reflash supersu and see if that fixes it
I'm not sure. I'm having the same issue, sort of. I can mount /system to read write easily but can't mount back to read only. Getting "resource busy" message. Running a 4.4.2 LG G2 ROM. Could it have anything to do with how /system is formatted within TWRP recovery? Idk.. Luckily not being able to mount as read only isn't exactly an issue but more of a nuisance.
Edit:: Found a solution minutes after posting.
Code:
su
mount -o remount,rw /system # works fine
mount -o remount,ro /system # resource busy error
mount -o remount ro /system # works fine without comma
With this knowledge I can go through and fix a few scripts that have the comma between remount and ro. Not sure why this is as it's always worked fine ever since my OG DROID.
Any updates ??
EvilMember said:
Any updates ??
Click to expand...
Click to collapse
Strange I'm using this rom: http://forum.xda-developers.com/xpe...14-4-0-118-t2859660/post56113642#post56113642
And I can't mount system to RW, had same issue before on stock but Super SU reflash fixed it...now no way to moint system to RW
MidnightHarvester said:
I'm not sure. I'm having the same issue, sort of. I can mount /system to read write easily but can't mount back to read only. Getting "resource busy" message. Running a 4.4.2 LG G2 ROM. Could it have anything to do with how /system is formatted within TWRP recovery? Idk.. Luckily not being able to mount as read only isn't exactly an issue but more of a nuisance.
Edit:: Found a solution minutes after posting.
Code:
su
mount -o remount,rw /system # works fine
mount -o remount,ro /system # resource busy error
mount -o remount ro /system # works fine without comma
With this knowledge I can go through and fix a few scripts that have the comma between remount and ro. Not sure why this is as it's always worked fine ever since my OG DROID.
Click to expand...
Click to collapse
FAIL:
this doing nothing.
mount -o remount ro /system
[email protected]:/ # mount | grep /system
mount | grep /system
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,noatime,nodiratime,noauto_da_alloc,data=ordered)
dmesg
<6>EXT4-fs (mmcblk0p30): re-mounted. Opts: (null)
kernel ignoring your command. problem is with some service open file for writing in /system and not letting go.
find the service! kill it, mount as RO.