Can someone test CWM and report.
mount: mounting /dev/block/mmcblk0p10 on /system failed: Device or resource busy
run_program: child exited with status 255
---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------
Starting recovery on Sun Oct 14 11:46:06 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /cache ext4 /dev/block/mmcblk0p12 (null) 0
2 /data ext4 /dev/block/mmcblk0p11 (null) 0
3 /system ext4 /dev/block/mmcblk0p10 (null) 0
4 /sdcard vfat /dev/block/mmcblk0p14 (null) 0
5 /boot emmc /dev/block/mmcblk0p9 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.setupwizard.mode=DISABLED
persist.sys.usb.config=mtp,adb
drm.service.enabled=true
ro.semc.sim.bip.enabled=true
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.semc.version.sw=1254-4233
ro.semc.version.sw_revision=6.1.B.0.544
ro.semc.version.sw_variant=GENERIC
ro.semc.version.sw_type=user
ro.factorytest=0
ro.serialno=CB511ZDGA2
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=s1
ro.hardware=st-ericsson
ro.revision=0
ro.crypto.state=unsupported
persist.chargemon.active=1
persist.sys.profiler_ms=0
persist.sys.language=de
persist.sys.country=AT
persist.sys.localevar=
persist.sys.timezone=Europe/Vienna
persist.sys.boot.sound.volume=0
init.svc.tad=stopped
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p10 (Device or resource busy)
Error mounting /system!
W:failed to mount /dev/block/mmcblk0p10 (Device or resource busy)
Error mounting /system!
I:Trying /dev/block/mmcblk0p14 on LUN file /sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/file
I:Successfully shared /dev/block/mmcblk0p14 on LUN file /sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/file
Starting recovery on Sun Oct 14 11:46:36 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /cache ext4 /dev/block/mmcblk0p12 (null) 0
2 /data ext4 /dev/block/mmcblk0p11 (null) 0
3 /system ext4 /dev/block/mmcblk0p10 (null) 0
4 /sdcard vfat /dev/block/mmcblk0p14 (null) 0
5 /boot emmc /dev/block/mmcblk0p9 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.setupwizard.mode=DISABLED
persist.sys.usb.config=mtp,adb
drm.service.enabled=true
ro.semc.sim.bip.enabled=true
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.semc.version.sw=1254-4233
ro.semc.version.sw_revision=6.1.B.0.544
ro.semc.version.sw_variant=GENERIC
ro.semc.version.sw_type=user
ro.factorytest=0
ro.serialno=CB511ZDGA2
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=s1
ro.hardware=st-ericsson
ro.revision=0
ro.crypto.state=unsupported
persist.chargemon.active=1
persist.sys.profiler_ms=0
persist.sys.language=de
persist.sys.country=AT
persist.sys.localevar=
persist.sys.timezone=Europe/Vienna
persist.sys.boot.sound.volume=0
init.svc.tad=stopped
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p10 (Device or resource busy)
Error mounting /system!
SD Card space free: 9301MB
Backing up boot image...
Backing up system...
W:failed to mount /dev/block/mmcblk0p10 (Device or resource busy)
Can't mount /system!
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
XperianPro said:
I need partition blocks with you can see by executing mount in terminal.
Could you guys upload pics of output.
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Hi XperianPro,
first of all congratulations on making working CWM for Xperia U ICS :good: Fantastic job!
I can hardly wait to see one for Xperia P. If any one can do it, I'm sure you can :good:
Here is output of mount in terminal:
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
[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
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
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p10 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /modemfs ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data/idd ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/vold/179:14 /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:14 /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.wyse.pocketcloudfull-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ #
Output is also in attach and is from ICS of course
If you need anything else please don't hesitate to ask. I'll test what ever you want
Thank you very much in advance!
Best regards!
I will post test build in next few hours,thanks for reports.
Sent from my ST25i using xda app-developers app
Alpha uploaded.
XperianPro said:
Alpha uploaded.
Click to expand...
Click to collapse
Will test it right away...
seky0405 said:
Will test it right away...
Click to expand...
Click to collapse
Super.
Sent from my ST25i using xda app-developers app
Installation went fine but can not boot in recovery, any suggestion?
I even try with x-parts and when phone reboot I continuously press volume down button and phone vibrate once and continue with normal booting...
How can I help to debug this?
seky0405 said:
Installation went fine but can not boot in recovery, any suggestion?
I even try with x-parts and when phone reboot I continuously press volume down button and phone vibrate once and continue with normal booting...
How can I help to debug this?
Click to expand...
Click to collapse
Can you point me to recovery that boots but for locked bootloader.
Sent from my ST25i using xda app-developers app
XperianPro said:
Can you point me to recovery that boots but for locked bootloader.
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Sure Here it is in attach... Looking forward to test another version
seky0405 said:
Sure Here it is in attach... Looking forward to test another version
Click to expand...
Click to collapse
Next version will in next one or two hour or tommorow.
Sent from my ST25i using xda app-developers app
XperianPro said:
Next version will in next one or two hour or tommorow.
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
OK Looking forward to test it Thank you very much for your hard work :good:
the Phone vibrate,but doest boot in the Recovery
but i think ,you will manage that
Epic thread, I've been waiting to this since I had the phone. I installed the alpha version, it won't work yet, but good luck, I'll be here to test anything.
test
hello and good job for your work
i test it and nothing else happened non of the tap on screen or push the lower button rapidly.
i appreciate for your work and i can test all of the scripts you will make to help you to finish this wonderfull project
keep up and stay tuned
Hi XperianPro,
can we expect another version tonight?
Thank you very much in advance!
Great!
I will wait for someone that certify that it works 100% on Xperia P :fingers-crossed:
Hi XperianPro
Thank you for your work and look forward to the next one : Good:
XperianPro said:
Sorry for waiting but something went wrong during win 8 installation.
I hope you understand,eta will be in next few days.
Click to expand...
Click to collapse
take your time xperianpro we can wait for 10 days and glad to see you again with new windows 8 skins
Any novelty?
Enviado desde mi Xperia P usando Tapatalk 2
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 created this thread to have some help from the active developers out there, currently the Ainol Novo Venus / Cherry Mobile Fusion Bolt still have no CWRM and TWRP although I am one step closer to achieving it but due to I lack of time modding this tablet I badly need help from the community to further continue the deveploment of this.
although there are a lots of firmware updates already been realease but I really don't want to jump into it until I get the CWRM (Clockworkmod) or TWRP recoveries.
so far here is the development that I have accomplished it just need to be converted to CWMR ot TWRP hoping to have some contributors out here will be much appreciated for the help guys
Code:
139|[email protected]:/ # cat /proc/partitions
major minor #blocks name
93 0 49152 acta
93 8 49152 actb
93 16 368640 actc
93 24 1048576 actd
93 32 65536 acte
93 72 5906432 actj
93 80 524288 actk
Code:
127|[email protected]:/proc # cat filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext2
ext3
ext4
cramfs
nodev ramfs
vfat
msdos
ntfs
romfs
exfat
[email protected]:/proc # cat 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
/dev/block/actb /misc vfat ro,noatime,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 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/actc /system ext4 rw,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/actd /data ext4 rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,data=ordered 0 0
/dev/block/acte /cache ext4 rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,gid=1015,fmask=0002,dmask=0002,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
Code:
127|[email protected]:/dev/block # 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
/dev/block/actb /misc vfat ro,noatime,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 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/actc /system ext4 rw,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/actd /data ext4 rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,data=ordered 0 0
/dev/block/acte /cache ext4 rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,gid=1015,fmask=0002,dmask=0002,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
Code:
1|[email protected]:/dev/block # cat /cache/recovery/last_log
Starting recovery on Thu Jan 1 00:00:03 1970
framebuffer: fd 4 (800 x 1280)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /mnt/sdcard vfat /dev/block/actj (null) 0
2 /system ext4 /dev/block/actc (null) 0
3 /cache ext4 /dev/block/acte (null) 0
4 /data ext4 /dev/block/actd (null) 0
5 /boot vfat /dev/block/actb (null) 0
6 /recovery vfat /dev/block/acta (null) 0
7 /misc emmc /dev/block/actb (null) 0
8 /mnt/sd-ext vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
I:Boot command: XMAKEBOOT
E:set_bootloader_message_block fs_type "emmc"
Command: "/sbin/recovery"
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=gs702a
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.debuggable=1
ro.setupwizard.mode=DISABLE
persist.sys.timezone=Asia/Taipei
persist.sys.strictmode.disable=true
wifi.supplicant_scan_interval=120
wifi.interface=wlan0
ro.allow.mock.location=0
persist.sys.usb.config=mass_storage,adb
ro.build.id=JRO03C
ro.build.display.id=Cherry_A610_V2
ro.build.version.incremental=eng.paduser.20130301.011658
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Mar 1 01:17:30 CST 2013
ro.build.date.utc=1362071850
ro.build.type=userdebug
ro.build.user=paduser
ro.build.host=pad--e6430-02
ro.build.tags=test-keys
ro.product.model=Fusion Bolt
ro.product.brand=Android
ro.product.name=full_gs702a
ro.product.device=gs702a
ro.product.board=full_gs702a
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ainol
ro.wifi.channels=
ro.board.platform=ATM702X
ro.build.product=gs702a
ro.build.description=full_gs702a-userdebug 4.1.1 JRO03C eng.paduser.20130301.011658 test-keys
ro.build.fingerprint=Android/full_gs702a/gs702a:4.1.1/JRO03C/eng.paduser.20130301.011658:userdebug/test-keys
ro.build.characteristics=tablet
ro.sf.lcd_density=160
ro.opengles.version=131072
ro.config.softopengles=0
ro.config.used_hw_vsync=0
ro.launcher.swipe=enable
ro.settings.config.hdmi=off
ro.systemui.volumekey=disable
ro.systemui.capture=enable
ro.launcher.config.cling=enable
ro.launcher.hideAPP=disable
ro.launcher.hideactivity=disable
ro.launcher.allapp.landX=10
ro.launcher.allapp.landY=6
ro.launcher.allapp.portX=5
ro.launcher.allapp.portY=8
ro.launcher.workspace.landX=8
ro.launcher.workspace.landY=7
ro.launcher.workspace.portX=8
ro.launcher.workspace.portY=7
launcher.force_enable_rotation=true
ro.product.usbdevice.VID=10d6
ro.product.usbdevice.PID=fffe
ro.product.mtpdevice.PID=4e41
ro.product.ptpdevice.PID=4e43
ro.shutmenu.recovery=disable
ro.shutmenu.planemode=disable
ro.shutmenu.restart=enable
ro.usb.descriptor=ainol,Fusion Bolt,3.00
ro.usbdevice.volumelabel=Fusion Bolt
ro.config.quickboot=0
ro.im.keysounddefenable=true
ro.support.gpswithwifi=1
ro.wifi.signal.level.1=-70
ro.wifi.signal.level.2=-65
ro.wifi.signal.level.3=-60
ro.wifi.signal.level.4=-55
ro.product.pribrand=actions
ro.product.primodel=owlx1
ro.sf.triplebuffer=0
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Adara.ogg
ro.config.alarm_alert=Cesium.ogg
ro.carrier=unknown
hwui.render_dirty_regions=false
ro.product.locale.language=en
ro.product.locale.region=US
dalvik.vm.dexopt-flags=v=n,o=v
dalvik.vm.checkjni=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
persist.sys.profiler_ms=0
persist.vold.set_label_done=1
init.svc.recovery=running
init.svc.adbd=running
127|[email protected]:/dev/block # cat /dev/block/acta > /sdcard/recovery.img
here is the link for the stock recovery.img and some of the stock rom files
Stock Rom Files: Download Link
Stock Recovery.img: Download Link
Alternative Link
Stock Recovery.img: LINK
I already know how to port the recovery.img back to the system but I am having problem on how to extract the stock recovery.img it is not the usual recovery.img because it is using a different table structure.
I have tried the kitchen and other tools but I think it is not unpacking it properly once this is successfully done I will create also a video tutorial on how the process went on hoping for some contributions out there and some modders to customize this rom
Reserved for tutorials
rnovino said:
I already know how to port the recovery.img back to the system but I am having problem on how to extract the stock recovery.img it is not the usual recovery.img because it is using a different table structure.
Click to expand...
Click to collapse
at first, please run following commands on adb root shell.
Code:
# mkdir /dev/xxx
# mount /dev/block/acta /dev/xxx
# ls /dev/xxx/
I noticed you used the cat command to get the boot.img and recovery.img. Can I use dd if= as well?
bumslayer said:
I noticed you used the cat command to get the boot.img and recovery.img. Can I use dd if= as well?
Click to expand...
Click to collapse
yes it is just the same
fun_ said:
at first, please run following commands on adb root shell.
Code:
# mkdir /dev/xxx
# mount /dev/block/acta /dev/xxx
# ls /dev/xxx/
Click to expand...
Click to collapse
this showed
Code:
255|[email protected]:/ # mount /dev/block/acta /dev/rec
mount /dev/block/acta /dev/rec
Usage: mount [-r] [-w] [-o options] [-t type] device directory
is there some code missing?
rnovino said:
this showed
Code:
255|[email protected]:/ # mount /dev/block/acta /dev/rec
mount /dev/block/acta /dev/rec
Usage: mount [-r] [-w] [-o options] [-t type] device directory
is there some code missing?
Click to expand...
Click to collapse
is used this and it worked
Code:
1|[email protected]:/ # busybox mount /dev/block/acta /dev/xxx
busybox mount /dev/block/acta /dev/xxx
[email protected]:/ # ls /dev/xxx
ls /dev/xxx
bin_cfg.xml
bin_cfg_UserView.xml
boot_lcd.bin
boot_pic.bin
config.xml
config_UserView.xml
gpiocfg.xml
lpow_pic.bin
pinctrl.xml
rec_bak.img
recovery.img
[email protected]:/ #
getting stock on bootloop of the recovery hmmm I just overwritted the recovery.img inside that /dev/block/acta
rnovino said:
this showed
Code:
255|[email protected]:/ # mount /dev/block/acta /dev/rec
mount /dev/block/acta /dev/rec
Usage: mount [-r] [-w] [-o options] [-t type] device directory
is there some code missing?
Click to expand...
Click to collapse
hmm, "-t vfat" may be needed. (not sure because I can't use any android shell for now, sorry)
anyway, it should be easy.
rnovino said:
getting stock on bootloop of the recovery hmmm I just overwritted the recovery.img inside that /dev/block/acta
Click to expand...
Click to collapse
what recovery.img you used?
fun_ said:
hmm, "-t vfat" may be needed. (not sure because I can't use any android shell for now, sorry)
anyway, it should be easy.
what recovery.img you used?
Click to expand...
Click to collapse
the one we converted via builder.clockworkmod.com , we copy the recovery.img inside the dev/block/acta then put it in the builder.clockworkmod.com is there any alternative I currently don't have an ubuntu to convert it via source http://www.mediafire.com/download.php?kzoysz6s164scx7
Hey rnovino bro. Were you able to fix the bootloop? I hope you did.
Looking at your recovery.img, I noticed they lack a lot of things which are included in the stock recovery.img (.rc scripts, /dev files, etc.). Does this have anything to do with your bootloop?
bumslayer said:
Hey rnovino bro. Were you able to fix the bootloop? I hope you did.
Looking at your recovery.img, I noticed they lack a lot of things which are included in the stock recovery.img (.rc scripts, /dev files, etc.). Does this have anything to do with your bootloop?
Click to expand...
Click to collapse
still figuring out I just got a small time to check out everyday so a big contribution is much welcome
Me too. So, have you recovered your tablet back to working condition?
bumslayer said:
Me too. So, have you recovered your tablet back to working condition?
Click to expand...
Click to collapse
I just port back the stock recovery and yes it is still working fine
that's good to know.
Sent from my GT-S5360 using Tapatalk 2
Pushing this thread up, for good measure. Developers out there, please help us out. Unfortunately I haven't been able to flash a recovery.img thru fastboot mode as we still lack ADB USB interface drivers for it. We can only work with ADB wirelessly.
any update
hi guys, any one working on this actively....I am not a developer but can test any build.
tnx
I built mine as well but my tablet got stuck on a boot loop and I had to reflash the firmware in order to revive it. Thank God I was so afraid I killed our tablet.
Looking back I think I forgot to include the recovery.fstab file when I built my cwm recovery. I am starting again later.
Sent from my GT-S5360 using Tapatalk 2
How did you make the CWM or TWRP recovery? Can you share your file & procedure to install the recovery.
Thanks a lot.
mGforCe said:
How did you make the CWM or TWRP recovery? Can you share your file & procedure to install the recovery.
Thanks a lot.
Click to expand...
Click to collapse
we still don't have it that is why we need contribution from other developers here in xda
I will start by excusing for the messed up mail.
Have a HTC Desire X(Y13) that is bricked. It have been unlocked and rooted. Original FW. Got OTA notice yesterday. I reinstalled the recovery and locked it.
After i ran the update and rebooted, it stayed on the welcome/beats screen.
I unlocked it and reinstalled the recovery(CWM).
And now I get the “Can't mount /cache/recovery” ect.
I do have a backup from the CWM. But when trying to restore it. It exits just after it restore the boot.img.
Tried to install different roms. Both cooked and “DesireX1.14.401.1.zip".
Get’s “Installing update”. Assert failed: write_raw_image(“/tmp/boot.img”. “boot”)
I have tried to lock it and restore a stock recovery. And then run the RRU:
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed”
It starts by erasing the user data. Says Starting and Sending. Updating Signature. And after 1min or so it fails with Error 158:Image error.
But it's a Proto ?
I can lock/unlock it. Flash boot.img and recovery’s. Have tried working with the WINTEAM loader. Same problem.
So no matter what I do, I just cant unbrick it. Any ideas on how to do that ?
Could I do an ADB format of the different partitions and flash them? ANY suggestion are welcome.
Log snippets:
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p21 (null) 0
2 /boot emmc /dev/block/mmcblk0p22 (null) 0
3 /cache ext4 /dev/block/mmcblk0p27 (null) 0
4 /data ext4 /dev/block/mmcblk0p26 (null) 0
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
6 /system ext4 /dev/block/mmcblk0p25 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p28 (null) 0
9 /emmc vfat /dev/block/mmcblk0p31 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
magiske said:
I will start by excusing for the messed up mail.
Have a HTC Desire X(Y13) that is bricked. It have been unlocked and rooted. Original FW. Got OTA notice yesterday. I reinstalled the recovery and locked it.
After i ran the update and rebooted, it stayed on the welcome/beats screen.
I unlocked it and reinstalled the recovery(CWM).
And now I get the “Can't mount /cache/recovery” ect.
I do have a backup from the CWM. But when trying to restore it. It exits just after it restore the boot.img.
Tried to install different roms. Both cooked and “DesireX1.14.401.1.zip".
Get’s “Installing update”. Assert failed: write_raw_image(“/tmp/boot.img”. “boot”)
I have tried to lock it and restore a stock recovery. And then run the RRU:
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed”
It starts by erasing the user data. Says Starting and Sending. Updating Signature. And after 1min or so it fails with Error 158:Image error.
But it's a Proto ?
I can lock/unlock it. Flash boot.img and recovery’s. Have tried working with the WINTEAM loader. Same problem.
So no matter what I do, I just cant unbrick it. Any ideas on how to do that ?
Could I do an ADB format of the different partitions and flash them? ANY suggestion are welcome.
Log snippets:
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p21 (null) 0
2 /boot emmc /dev/block/mmcblk0p22 (null) 0
3 /cache ext4 /dev/block/mmcblk0p27 (null) 0
4 /data ext4 /dev/block/mmcblk0p26 (null) 0
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
6 /system ext4 /dev/block/mmcblk0p25 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p28 (null) 0
9 /emmc vfat /dev/block/mmcblk0p31 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
Click to expand...
Click to collapse
You need a jb optimized recovery...
Stereo8 said:
You need a jb optimized recovery...
Click to expand...
Click to collapse
Thanks. Now I can get it up and running. Can I downgrade from here ? Would like to be able to restore my backup ??
/Mads
Yes!
Flowed from my HTC branded muffin...
Surely kernel problem
Hahahahha the same here...For that we need RUU JB aways can fix the mess that we make
I have a Huawei T-Mobile Mytouch 4G Q slider (U8730) and i have successfully rooted it. I havent flashed any ROM's or anything like that and i have browsed through alot of the forums and Google and havent found what i need to know. I need to know how to use the "mount a filesytem read-write" command, i know the syntax:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
i just dont know what information to input in the command.
i know i can use:
# mount
and that will give me a lot of info but im not too sure what im looking for.
if theres another thread about this, i apologize, im new to this forum and not 100% how to navigate.
heres what it says when i do # mount
im not sure what im looking for here
please help O:
mount
rootfs / rootfs rw,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
/dev/block/mmcblk0p14 /HWUserData vfat rw,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
/dev/block/mmcblk0p1 /.cust_backup vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/loop0 /cust ext3 ro,relatime,barrier=0,data=writeback 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/mmcblk0p12 /system ext4 ro,relatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered 0 0
hwvefs /data/huawei_hwvefs fuse.hwvefs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:33 /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:33 /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,er
rors=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.ultimateguitar.tabs-1 vfat ro,dirsync,nosuid,nodev,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/com.ovelin.guitartuna-1 vfat ro,dirsync,nosuid,nodev,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/net.andchat-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.ddm.iptools-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
Which specific partition do you want to mount read write?
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
Which specific partition do you want to mount read write?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
oh man!! im not sure what that means! just need to mount rw for apps
orionsfl said:
oh man!! im not sure what that means! just need to mount rw for apps
Click to expand...
Click to collapse
Partition refers to a specific file system. For example the /boot partition contains the kernel and ramdisk for booting up your device (Note: /boot partition and bootloader partition are not the same thing), the /cache partition contains cache files, the /system partitions contains your system apps and other system folder such as bin and xbin and other. What apps are you trying to use that you need to mount rw for? But if you wanted to modify your /system partition for example you would run the following command from ADB shell or terminal emulator to mount it rw (Read/write):
Code:
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p12 /system
Let me know if you still have questions about this.
Try this:
https://play.google.com/store/apps/details?id=com.beansoft.mount_system
Hit thanks if I helped.
Sent from my Nexus 4 using Tapatalk 2
Hi all,
I want to flash CM10.2 for Android 4.3
but, I can't flash any ROM.
when i want to Update CWM, it's impossible.
see the log :
Code:
Starting recovery on Tue Sep 2 12:35:39 2014
framebuffer: fd 4 (480 x 800)
E:unknown volume for path [/system]
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /efs ext4 /dev/block/mmcblk0p1 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p10 (null) 0
7 /preload ext4 /dev/block/mmcblk0p12 (null) 0
8 /emmc vfat /dev/block/mmcblk0p11 (null) 0
9 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
PhilZ Touch 3
CWM Base version: 6.0.1.8
Command: "recovery"
ro.boot.serialno=0009aa09441a2f
ro.sec_debug.enable=0
ro.serialno=0009aa09441a2f
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.debug_level=unknown
ro.emmc_checksum=unknown
ril.dualmode.change=unknown
ro.hardware=smdk4210
ro.revision=14
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp
init.svc.ueventd=running
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
Finding update package...
I:Update location: /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
Opening update package...
E:Can't open /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
(bad)
Installation aborted.
Have you an idea ?
Sorry for my poor english
Check the md5 of the downloaded zip.
Looks like a corrupted one.
Also make sure you copy / paste the zip on your phone correctly.
Sent from my Nexus 5 using Tapatalk 2
corrupted file
From my own experience it normally is a bad/corrupted file that you downloaded. I've waste hours downloading a file through my phone only to fbd out that I couldn't flash it. Check your downloaded program cause this can affect the result of your download files. I use Internet download manager for windows which is a very useful download manger for all your needs. For the android I used ADM or advance download manager but I suggest using idm on PC insyead .
One rule I always do now is check the archive if they work or unzip in your PC if not then it won't work on your phone when flashing