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:Loaded font:/res/font.datcan't open /dev/tty0: No such file or directorypredefine pixel_format is 4framebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentLoaded (event0): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event2): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event1): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)CWM-based Recovery v6.0.3.0I: using hack for MTK ext4 [email protected]:[MTK]Get size of ext4 device /cache[/dev/block/mmcblk0p7] from fseek =0x7e00000.I:[MTK]Get size of ext4 device /data[/dev/block/mmcblk0p8] from fseek=0x40000000.I:[MTK]Get size of ext4 device /system[/dev/block/mmcblk0p5] from fseek =0x600000.I:[MTK]Get size of ext4 device /cust[/dev/block/mmcblk0p6] from fseek=0x2bc00000.recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /boot emmc /dev/bootimg (null) 02 /cache ext4 /dev/block/mmcblk0p7 (null) 1319895043 /data ext4 /dev/block/mmcblk0p8 (null) 10736107524 /misc emmc /dev/misc (null) 05 /pro_info emmc pro_info (null) 06 /recovery emmc /dev/recovery (null) 07 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 08 /system ext4 /dev/block/mmcblk0p5 (null) 61603849 /cust ext4 /dev/block/mmcblk0p6 (null) 733872128W: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!W:Unable to get recovery.fstab info for /external_sd during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Got arguments from /cache/recovery/commandI:Checking arguments.Warning: No file_contextsI:device_recovery_start()移动叔叔专版www.ydss.cn技术支持: 银狐(yyjdelete)Apr 15 2013 23:19:27Command: "/sbin/recovery""--update_package=CACHE:update.zip"(replacing path "CACHE:update.zip" with"/cache/update.zip")ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=running正在查找刷机包...I:Update location: /cache/update.zip正在打开刷机包...I:read key e=3I:read key e=3I:2 key(s) loaded from /res/keys正在验证刷机包...I:comment is 1738 bytes; signature 1720bytes from endI:whole-file signature verified against key 0I:verify_file returned 0正在安装刷机包...Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 argsrm: /etc: is a directoryabout to run program [/sbin/busybox] with 4 argssh: invalid number 'root'sh: can't kill pid 3468: No such processsh: invalid number 'S'sh: invalid number '/sbin/adbd'sh: invalid number 'recovery'sh: can't kill pid 106: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/adbd'sh: invalid number 'root'sh: can't kill pid 14980: No such processsh: invalid number 'S'sh: invalid number '/sbin/recovery'sh: can't kill pid 109: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/recovery'run_program: child exited with status 1script result was [256]Starting recovery on Wed Sep 25 01:18:52 2013can't open /dev/tty0: No such file or directoryframebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentioctl(): blank: Invalid argumentClockworkMod Recovery v5.5.0.4recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /system ext4 /dev/block/mmcblk0p1 (null) 02 /cache ext4 /dev/block/mmcblk0p2 (null) 03 /misc emmc /dev/block/mmcblk0p3 (null) 04 /staging ext3 /dev/block/mmcblk0p4 (null) 05 /data ext4 /dev/block/mmcblk0p8 (null) 0W: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 /sdcard 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.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=runningI:Checking for extendedcommand...I:Skipping execution of extendedcommand, file not found...-- Installing: /sdcard/update.zipFinding update package...I:Update location: /sdcard/update.zipI:using /data/media, no /sdcard found.Opening update package...E:Can't open /sdcard/update.zip(No such file or directory
Card to mount (20s)SDCard mounted..../tmp/recovery.logwas copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
abhilaab said:
I:Loaded font:/res/font.datcan't open /dev/tty0: No such file or directorypredefine pixel_format is 4framebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentLoaded (event0): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event2): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event1): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)CWM-based Recovery v6.0.3.0I: using hack for MTK ext4 [email protected]:[MTK]Get size of ext4 device /cache[/dev/block/mmcblk0p7] from fseek =0x7e00000.I:[MTK]Get size of ext4 device /data[/dev/block/mmcblk0p8] from fseek=0x40000000.I:[MTK]Get size of ext4 device /system[/dev/block/mmcblk0p5] from fseek =0x600000.I:[MTK]Get size of ext4 device /cust[/dev/block/mmcblk0p6] from fseek=0x2bc00000.recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /boot emmc /dev/bootimg (null) 02 /cache ext4 /dev/block/mmcblk0p7 (null) 1319895043 /data ext4 /dev/block/mmcblk0p8 (null) 10736107524 /misc emmc /dev/misc (null) 05 /pro_info emmc pro_info (null) 06 /recovery emmc /dev/recovery (null) 07 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 08 /system ext4 /dev/block/mmcblk0p5 (null) 61603849 /cust ext4 /dev/block/mmcblk0p6 (null) 733872128W: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!W:Unable to get recovery.fstab info for /external_sd during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Got arguments from /cache/recovery/commandI:Checking arguments.Warning: No file_contextsI:device_recovery_start()移动叔叔专版www.ydss.cn技术支持: 银狐(yyjdelete)Apr 15 2013 23:19:27Command: "/sbin/recovery""--update_package=CACHE:update.zip"(replacing path "CACHE:update.zip" with"/cache/update.zip")ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=running正在查找刷机包...I:Update location: /cache/update.zip正在打开刷机包...I:read key e=3I:read key e=3I:2 key(s) loaded from /res/keys正在验证刷机包...I:comment is 1738 bytes; signature 1720bytes from endI:whole-file signature verified against key 0I:verify_file returned 0正在安装刷机包...Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 argsrm: /etc: is a directoryabout to run program [/sbin/busybox] with 4 argssh: invalid number 'root'sh: can't kill pid 3468: No such processsh: invalid number 'S'sh: invalid number '/sbin/adbd'sh: invalid number 'recovery'sh: can't kill pid 106: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/adbd'sh: invalid number 'root'sh: can't kill pid 14980: No such processsh: invalid number 'S'sh: invalid number '/sbin/recovery'sh: can't kill pid 109: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/recovery'run_program: child exited with status 1script result was [256]Starting recovery on Wed Sep 25 01:18:52 2013can't open /dev/tty0: No such file or directoryframebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentioctl(): blank: Invalid argumentClockworkMod Recovery v5.5.0.4recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /system ext4 /dev/block/mmcblk0p1 (null) 02 /cache ext4 /dev/block/mmcblk0p2 (null) 03 /misc emmc /dev/block/mmcblk0p3 (null) 04 /staging ext3 /dev/block/mmcblk0p4 (null) 05 /data ext4 /dev/block/mmcblk0p8 (null) 0W: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 /sdcard 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.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=runningI:Checking for extendedcommand...I:Skipping execution of extendedcommand, file not found...-- Installing: /sdcard/update.zipFinding update package...I:Update location: /sdcard/update.zipI:using /data/media, no /sdcard found.Opening update package...E:Can't open /sdcard/update.zip(No such file or directory)Installation aborted.I:using /data/media, no /sdcard found
Click to expand...
Click to collapse
as it says no sd card is found .. so is your sd card is working fine or not and in cwm check the mounts and storage that the sd card is mounted or not
Hope this is the right place to post, I've been lurking around the forums since I got my first smart phone a few years ago but never posted as I've usually found what I'm looking for through googling and rtfm'ing, only reason I came out of the shadows was to get my Kobo Arc 7 rooted. No way I could live without it, I had been watching this thread http://forum.xda-developers.com/showthread.php?t=2507886, checking it every few days to see if there was any development when I saw development was pretty much abandoned on the Arc 7. So this all started with a pm that made me try getting root myself with a little help from dazza9075.
Basically was told to trade in the arc 7 for an arc 7hd, barring that I could try the new cydiaimpactor update and see if it worked. It went something like this. I followed the instructions for the 7hd:
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Click to expand...
Click to collapse
Everything went fine until plugging in the device to let it install a USB composite device. As expected it did fail on the third but when trying to install Google USB drivers it couldn't find any for the device. Just for kicks I opened up Impactor and pressed "Start" it did nothing, I then clicked "USB Scan" and let it complete, then pushed "Start" again. Quick popup on the screen, so I swiped the screen and ran Root Checker Basic and voila I had root.
Since then I've pretty much been badgering dazza9075 through pm to see about getting a recovery for it, I'm an old school linux guy, but never spent much time doing any development, so trying to figure things out myself is usually not an issue but this is new to me. I've been utilizing my google fu to try getting a recovery image made and had some success. Basically started with the instructions for dumping the partition info via dazza's instructions. Turned out to be a little more frustrating than anything, all the commands were turning up nothing, then finally I checked chipset specific stuff, it's running an MTK8125 so after getting nowhere with:
cat /proc/mounts
Code:
[email protected]:/ # cat /proc/mounts
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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /storage/emulated tmpfs rw,relatime,mode=705,uid=1023,gid=1023 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=or
dered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
cat /proc/partitions
Code:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
179 0 7523456 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 786432 mmcblk0p5
179 6 524288 mmcblk0p6
179 7 6145664 mmcblk0p7
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15633408 mmcblk1p1
So trying to find the ls -al /dev/block/platform/dw_mmc/by-name was the first hurdle as there was no "by-name"
Code:
ls -al /dev/block/platform/dw_mmc/by-name
ls -al /dev/block/platform
drwxr-xr-x root root 2014-01-29 20:33 mtk-msdc.0
drwxr-xr-x root root 2014-01-29 20:33 mtk-msdc.1
ls -al /dev/block/platform/mtk-msdc.0
drwxr-xr-x root root 2014-01-29 20:33 by-num
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p7 -> /dev/block/mmcblk0p7
ls -al /dev/block/platform/mtk-msdc.1
drwxr-xr-x root root 2014-01-29 20:33 by-num
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk1p1 -> /dev/block/mmcblk1p1
but an ls -l revealed:
Code:
[email protected]:/ # ls -l
ls -l
drwxr-xr-x root root 2014-01-31 08:16 acct
-rw-r--r-- root root 16927 1969-12-31 18:00 advanced_meta_init.rc
drwxrwx--- system cache 2014-01-28 19:01 cache
dr-x------ root root 2014-01-31 08:16 config
-rw-r--r-- root root 4 1969-12-31 18:00 custom_build_verno
lrwxrwxrwx root root 2014-01-31 08:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-01-31 08:17 data
-rw-r--r-- root root 185 1969-12-31 18:00 default.prop
drwxr-xr-x root root 2014-01-31 08:16 dev
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p7
So I focused on googling emmc partition tables and stumbled upon this thread http://forum.xda-developers.com/showthread.php?t=2450045 which again I followed with little success. I had already tried way 1 and way 2 and way 3 couldn't read the partition table. So I followed the comments and #3 mentioned "cat /proc/emmc", so:
Code:
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00006800 00005000 "protect_f"
emmc_p3: 0000b800 00005000 "protect_s"
emmc_p4: 00016c00 00003000 "sec_ro"
emmc_p5: 00020c00 00180000 "android"
emmc_p6: 001a0c00 00100000 "cache"
emmc_p7: 002a0c00 00bb8d00 "usrdata"
Still not giving me a good picture of the partition table so I followed that thread till the end which took me to this thread, http://forum.xda-developers.com/showthread.php?t=1959445. So in fashion I started following that. So
Using fdisk:
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Disk /dev/block/mmcblk0: 7704 MB, 7704018944 bytes
1 heads, 16 sectors/track, 940432 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1665 2944 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2945 4224 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 5825 6592 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8385 106688 786432 83 Linux
parted:
Code:
[email protected]:/ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
p
Error: Can't have a partition outside the disk!
gdisk:
Code:
[email protected]:/ # gdisk -l /dev/block/mmcblk0
gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
EBR signature for logical partition invalid; read 0x0000, but should be 0xAA55
Error reading logical partitions! List may be truncated!
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Disk /dev/block/mmcblk0: 15046912 sectors, 7.2 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E01B69E6-D822-467F-B1D2-97C0B7BA9ABA
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15046878
Partitions will be aligned on 1024-sector boundaries
Total free space is 13420733 sectors (6.4 GiB)
Number Start (sector) End (sector) Size Code Name
2 26624 47103 10.0 MiB 8300 Linux filesystem
3 47104 67583 10.0 MiB 8300 Linux filesystem
4 93184 105471 6.0 MiB 8300 Linux filesystem
5 134144 1707007 768.0 MiB 8300 Linux filesystem
Still no love. So I read on to the emmc section of that thread and understand nothing, more google fu gets me here: https://github.com/ameer1234567890/OnlineNandroid/wiki/How-To-Gather-Information-About-Partition-Layouts. So now I'm looking at the emmc stuff thinking this really doesn't help me, but remembering I'm running an mtk chip I was pretty happy when I got:
Code:
[email protected]:/ # cat /proc/dumchar_info
cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0
resv 0x0000000000080000 0x0000000003400000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003480000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003780000 2 /dev/block/mmcblk0
android 0x0000000030000000 0x0000000004180000 2 /dev/block/mmcblk0p5
cache 0x0000000020000000 0x0000000034180000 2 /dev/block/mmcblk0p6
usrdata 0x00000001771a0000 0x0000000054180000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
Bingo, so finally, root, partition info, next recovery. Again I'm green here so I searched and searched and searched until finally I found the lenovo has the same chip that someone else had managed to get a recovery installed. So I've spent most of my day with this page, trying to get a recovery installed http://forum.xda-developers.com/newthread.php?do=postthread&f=613. So I managed to get everything done, booted into CWM recovery, finished up all excited, then started testing CWM first reboot and I'm back to the stock android recovery. So I ended up finding the recovery.img that was created through the steps in the above link and did:
Code:
adb shell
mount -o remount,rw /system
mv /system/recovery-from-boot.p /system/recovery-from-boot.p-orig
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-orig
As this was apparently a known problem with some samsung devices. Then:
Code:
fastboot flash recovery "path to recovery"
Which I cut and pasted the path, then rebooted the Arc 7 into fastboot by holding down the Volume up and power slider for aproximately 30 seconds. Fastboot was successful but hung after installing the recovery.img so I hard rebooted and got back into the arc. So I've tested it a few times and now it's booting into CWM recovery, I had two backups made during the image creation process and have been able to restore from both backups, tried creating a backup which completed with an error, can't remember what it is at this point though I will try again later. Only thing I'm noticing is when I boot into recovery it throws the following errors.
Code:
CWM automade 03.02.2014 11:23:02
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last-log
E:Can't open /cache/recovery/last_log
At this point I'm not sure if this is a problem or not as so far everything seems to be working, I will continue testing this recovery out then hopefully post it to dazza9075's original thread. At this point I really don't know what to do from here and any input would be greatly appreciated, dazza has been a great help but I'm at the mercy of being in different countries and timezones, so the pm process is always a little hurry up and wait. Apologies again if this is the wrong place to post, and thanks to all the people in the other posts above for all the hard work they have put in. Hopefully having some of this information in one place will help others with Microtek Chips.
Good work mate!
Have you tried creating a backup yet? and can you post the contents of your FSTAB?
The important one for you is probably to get the SD card mounted, with the internal storage quite low backups will be tricky, so we need to be able to mount an external SD card and use that for the backup.
I wouldn't be to worried about the other partitions that haven't mounted yet, lets concentrate on the important ones, /system /cache /recovery /boot
once we can confirm that you can back then restore we can tidy up the other issues.
Good work mate!
Here is my fstab:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/[email protected] /system ext4 ro,noatime wait
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
It appears that my external sdcard is getting mounted for backups anyways as my backups are all being found in /storage/sdcard1/clockworkmod/backup/. Here is the output from CWM during the backup:
Code:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
SD Card space free: 7225MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
No /sdcard/.android_secure found. Skipping backup of applications on external storage.
Backing up cache...
Can't mount /cache!
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Checking the new backup folder created only yields boot.img, data.ext4.tar, recovery.img and system.ext4.tar
Pretty much looks like we just need to get the /cache mounting properly then it should go off without a hitch.
Correction, just tried wiping the cache from CWM rebooted to delete the failed backups off the device, booted back into recovery and was greeted by the stock android recovery.
Okay so after getting the stock android recovery after wiping the cache 3 times I decided to start fresh.
Factory reset
Selected english
Forced to update
Rooted with impactor
Installed SU
Installed rom toolbox
fastboot flash recovery "path-to"\recovery.img
power down the volume up powerslider til menu pops up
select fastboot
image flashes and says complete, hold power slider to power down and
rebooted into cwm (volume up and power slider till menu pops up then restore) and this is what I got:
Code:
rua1 autoCWM v5.5.0.4 for arc 7
-reboot system now
-install zip from sdcard
-wipe data/factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
CWM automade 03.02.2014 11:23:02
SD Card space free: 7852MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
No sd-ext found. Skipping backup of applications on external storage.
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup complete!
Rebooted
From rom toobox "Rom Management"
selected custom cwmr
swiped to backups
selected backup I just made and rebooted into cwm from rom toolbox
Code:
CWM automade 03.02.2014 11:23:02
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
#############################
# ROM Toolbox Lite v. 5.9.8 #
# Feb 04, 2014 #
#############################
E:unknown volume for path [/storage/sdcard1/clockworkmod/backup/2014-02-04.17.00.21]
Can't mount backup path
/tmp/recovery.log was copied to /sdcard/clockworkmod/revoery.log. Please open ROM Manager to report the issue.
So for kicks I tried to restore the backup manually from /storage/sdcard1/clockworkmod/backup/*
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore complete!
rebooted kobo, everything seems to be in place. Boot back into recovery to make sure it's cwm not stock android.
Rom Toolbox Lite -> Rebooter -> Reboot Recovery. Bam, back into CWM.
So it is backing up to the external sdcard and can restore from there it just can't do it automagically!?
Regardless aside from not finding ext-sd everything seemed to work.
Have you disabled the auto recovery repair thing? I'm away from my computer at mo but if you kook at the arc recovery rom process there is a file you need too delete, that stops custom recovery getting replaced at boot
Sent from my GT-I8750 using XDA Windows Phone 7 App
I renamed those files as I had read they were causing similar issues on Samsung devices. Now they are renamed and moved to another folder. I'm flashing http://forum.xda-developers.com/showthread.php?t=1916098 right now. it backed up okay, but couldn't find the file. The zip was saved to /sdcard/downloads but its reading my sdcard which is /storage/sdcard1 as /sdcard.
I did a wipe to flash that and when it couldn't find it it rebooted to factory. I'm back in CWM doing a system restore from the backup it just made. So it is working, just seems to be issues with paths. I am able to flash manually once in CWM though.
howlinwolf430 said:
I renamed those files as I had read they were causing similar issues on Samsung devices. Now they are renamed and moved to another folder. I'm flashing http://forum.xda-developers.com/showthread.php?t=1916098 right now. it backed up okay, but couldn't find the file. The zip was saved to /sdcard/downloads but its reading my sdcard which is /storage/sdcard1 as /sdcard.
I did a wipe to flash that and when it couldn't find it it rebooted to factory. I'm back in CWM doing a system restore from the backup it just made. So it is working, just seems to be issues with paths. I am able to flash manually once in CWM though.
Click to expand...
Click to collapse
your Fstab is very odd looking, it does look exactly like what you find within android but the recovery ones I have been using are a little different
here is mind
Code:
/system ext4 /dev/block/mmcblk0p3
/sdcard datamedia /dev/block/mmcblk0p8 /dev/block/platform/mmcblk0
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p1
/boot emmc /dev/block/mmcblk0p2
/misc emmc /dev/block/mmcblk0p5
/staging emmc /dev/block/mmcblk0p6
/metadata emmc /dev/block/mmcblk0p7
That is for the 10HD, /SDcard in this case is an internal chip, there is no external chip, I have to have it set at "data media" but on the original Arc I have it set to "vfat". For the 10HD I cant manually mount /SDCARD, but it does do it itself when backing up and restoring but on the Arc it works fine, I can manually mount and unmount. Im a little unsure why its not working on the 10HD, a chap was going to have a look for me but hasn't yet got back to me.
format is
/mount_point Mount_type /location
below is the fstab of Astrali, his been a good help with mine
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p16
/cache ext4 /dev/block/mmcblk0p18
/data ext4 /dev/block/mmcblk0p21 length=-16384
/recovery emmc /dev/block/mmcblk0p13
/misc emmc /dev/block/mmcblk0p11
[B]/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1[/B]
/system ext4 /dev/block/mmcblk0p17
/sys_boot vfat /dev/block/mmcblk0p3
/FOTA emmc /dev/block/mmcblk0p19
[B]/sdcard1 vfat /dev/block/mmcblk0p20[/B]
[B]/sd-ext auto /dev/block/mmcblk1p2[/B]
#added sd-ext support by Astrali
[B]/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1[/B]
#added for rom manager support
Here we can see /external_SD and /sdcard are actually the same thing (?) mounted from blk1p1 (likely an external Sdcard) I don't know why there is two mounts, perhaps different software looking for the same thing but in different places?
/SDcard1 is mounted from blk0p20 so probably internal storage,
/sd-ext however is mounted from blk1p2, likely a second partition on an external card
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
/sd-ext ext4 /dev/block/mmcblk0p2
keep this in mind, im just building a recovery img just now based on this...
Can you please upload kobo arc 7 stock rom or system.img
Hello all,
I'm new to the world of ROMS and custom recoveries, I've rooted my phone and for educational purposes, I wanted to build CWM 6 but I have trouble with my recovery.fstab or something because I only get a blank screen flashing periodically.
Here's the stock recovery.fstab of the recovery.img
Code:
/dev/block/platform/sprd-sdhci.0/mmcblk1p1 /sdcard vfat default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/HIDDEN /preload ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 default wait,length=-16384
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/PRODNV /productinfo ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/KERNEL /boot emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/RECOVERY /recovery emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/modem /modem emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/DSP /modem2 emmc default recoveryonly
I've also tried this version (after changing the names with partitions)
Code:
# mount point fstype device
/system ext4 /dev/block/mmcblk0p18
/preload ext4 /dev/block/mmcblk0p19
/data ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p17
/efs ext4 /dev/block/mmcblk0p7
/productinfo ext4 /dev/block/mmcblk0p5
/boot emmc /dev/block/mmcblk0p11
/recovery emmc /dev/block/mmcblk0p12
/modem emmc /dev/block/mmcblk0p13
/modem2 emmc /dev/block/mmcblk0p14
/sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk1p1
but to no avail, the only result that I got was when I used the fstab of the boot.img
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,barrier=1 wait
#/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit wait,encryptable=footer,check
#/dev/block/platform/sprd-sdhci.3/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit wait,check
#/dev/block/platform/sprd-sdhci.3/by-name/prodnv /productinfo ext4 noatime,nosuid,nodev,nomblk_io_submit wait,check
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,noatime,errors=panic wait
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check,encryptable=footer
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/dev/block/platform/sprd-sdhci.3/by-name/PRODNV /productinfo ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/devices/platform/sprd-sdhci.0/mmc_host/mmc1 auto vfat defaults voldmanaged=extSdCard:auto,noemulatedsd
would you please tell me what I'm missing here ?
Just want to know
Could you tell me how you got root for this phone..? Been searching all over with no luck