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
So yesterday I posted that I was having issues after trying to load the HairBean from AndroWook, and after the WW_epaduser_10_4_2_9_UpdateLauncher.zip flash I lost my bootloader, and thought I was BRICKED.
After a LOT of reading about NVFLASH, and some posting in other website/forums, I've been able to recover my TFP and I'm looking at a Team EOS Jelly Bean nightly on it now.
Steps taken....(I'm running Ubuntu 12.04 on an old MacBook)
1) Download *externallinknotallowed*/androidroot.mobi/download/rec_bootloader.bin
2) In a terminal window run the following command
[email protected]:/home/charlie/Downloads/NVFLASH/tf201_nvflashpack# ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
3) Connected TFP to macbook and power cycled while holding the Volume UP key
[=] Chip UID: 0x98091256096231435
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
[email protected]:/home/charlie/Downloads/NVFLASH# ./nvflash --resume --download 4 rec_bootloader.bin
Nvflash v1.5.66719 started
[resume mode]
sending file: rec_bootloader.bin
/ 1021997/1021997 bytes sent
rec_bootloader.bin sent successfully
[email protected]:/home/charlie/Downloads/NVFLASH# ./nvflash --resume --go
Nvflash v1.5.66719 started
[resume mode]
The device rebooted and immediately went into TWRP.
I wiped everything and then installed fresh from external SDCARD the Team EOS nightly and the gapps packages.
I'm beyond happy that this worked.
--Charlie
Special thanks to jrodder for his post. Helped a lot mate!
so this really worked out?
i have the same problem with HairBean from AndroWook...
Yes it works! As long as you have the blob file from NVFlash setup... AND you download the file listed, you can recover the bootloader.
Sent from my vivow using Tapatalk 2
what if i don't have blob file?
Did you perform all the steps in the NVFlash recovery guide? It's part of those tools. It starts the NVFlash recovery via the wheelie command also included in that tool set.
Once you are in NVFlash recovery, then you can nvflash the file rec_bootloader.bin
Sent from my vivow using Tapatalk 2
ecatsab said:
Did you perform all the steps in the NVFlash recovery guide? It's part of those tools. It starts the NVFlash recovery via the wheelie command also included in that tool set.
Once you are in NVFlash recovery, then you can nvflash the file rec_bootloader.bin
Sent from my vivow using Tapatalk 2
Click to expand...
Click to collapse
I too did this to get the bootloader back, but something is much worse for me. I have a thread in the other general forum here:
*edit* I guess it got moved to this forum, sorry!
http://forum.xda-developers.com/showthread.php?p=32041006
It really looks like I hosed my partitions somehow after the initial HB failure. When I flashed the original JB rom, I saw it tried to do a /system format I think, and it was all bad after that. Can you maybe do me a HUGE favor and do an adb shell, and post the output of "df -h"? I seem to be missing at the very least a /staging partiton amongst others, and an desperately trying to find a way to get the partition structure fixed so I can flash. Thanks!
jrodder said:
I too did this to get the bootloader back, but something is much worse for me. I have a thread in the other general forum here:
*edit* I guess it got moved to this forum, sorry!
http://forum.xda-developers.com/showthread.php?p=32041006
It really looks like I hosed my partitions somehow after the initial HB failure. When I flashed the original JB rom, I saw it tried to do a /system format I think, and it was all bad after that. Can you maybe do me a HUGE favor and do an adb shell, and post the output of "df -h"? I seem to be missing at the very least a /staging partiton amongst others, and an desperately trying to find a way to get the partition structure fixed so I can flash. Thanks!
Click to expand...
Click to collapse
I'll do this first thing when I go home for lunch. 1200 MST
Click to expand...
Click to collapse
Here is the df -h output from an adb shell while the TFP was in TWRP recovery.
Filesystem Size Used Available Use% Mounted on
tmpfs 491.5M 52.0K 491.4M 0% /dev
/dev/block/mmcblk0p2 421.3M 16.4M 404.9M 4% /cache
/dev/block/mmcblk0p8 26.4G 274.1M 26.1G 1% /data
/dev/block/mmcblk1p1 14.9G 523.0M 14.4G 3% /external_sdcard
/dev/block/mmcblk0p8 26.4G 274.1M 26.1G 1% /sdcard
/dev/block/mmcblk0p1 755.9M 262.3M 493.6M 35% /system
ecatsab said:
Here is the df -h output from an adb shell while the TFP was in TWRP recovery.
Filesystem Size Used Available Use% Mounted on
tmpfs 491.5M 52.0K 491.4M 0% /dev
/dev/block/mmcblk0p2 421.3M 16.4M 404.9M 4% /cache
/dev/block/mmcblk0p8 26.4G 274.1M 26.1G 1% /data
/dev/block/mmcblk1p1 14.9G 523.0M 14.4G 3% /external_sdcard
/dev/block/mmcblk0p8 26.4G 274.1M 26.1G 1% /sdcard
/dev/block/mmcblk0p1 755.9M 262.3M 493.6M 35% /system
Click to expand...
Click to collapse
Thanks, that's what I have as well, at first glance. Can you paste what your /etc/fstab is by chance? It looks like my /system partition isn't mounting on a regular boot, only when done manually via TWRP...
(adb pull /etc/fstab filename.txt)
Mine:
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk1p1 /external_sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext rw
Click to expand...
Click to collapse
jrodder said:
Thanks, that's what I have as well, at first glance. Can you paste what your /etc/fstab is by chance? It looks like my /system partition isn't mounting on a regular boot, only when done manually via TWRP...
(adb pull /etc/fstab filename.txt)
Mine:
Click to expand...
Click to collapse
Just went back into the shell and did a cat on /etc/fstab.....
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk0p8 /data ext3 rw
/dev/block/mmcblk0p2 /cache ext3 rw
/dev/block/mmcblk1p1 /external_sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext rw
Here is what is is output with the mount command in the shell......
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext3 (rw,relatime,barrier=0,data=writeback)
/dev/block/mmcblk0p8 on /sdcard type ext3 (rw,relatime,barrier=0,data=writeback)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
I hope this helps.
ecatsab said:
Just went back into the shell and did a cat on /etc/fstab.....
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk0p8 /data ext3 rw
/dev/block/mmcblk0p2 /cache ext3 rw
/dev/block/mmcblk1p1 /external_sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext rw
Here is what is is output with the mount command in the shell......
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext3 (rw,relatime,barrier=0,data=writeback)
/dev/block/mmcblk0p8 on /sdcard type ext3 (rw,relatime,barrier=0,data=writeback)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
I hope this helps.
Click to expand...
Click to collapse
It might, it might not. Honestly, I am feeling totally lost. I just wish I knew how to make this tablet work again. I have full access to it, and am just not sure what I need to attack. So when you boot into TWRP 2.2.2, and check the mounts, is /system already mounted? Mine isn't, and I am thinking that's the issue. I can manually mount in TWRP and all the ROM data is there...
jrodder said:
It might, it might not. Honestly, I am feeling totally lost. I just wish I knew how to make this tablet work again. I have full access to it, and am just not sure what I need to attack. So when you boot into TWRP 2.2.2, and check the mounts, is /system already mounted? Mine isn't, and I am thinking that's the issue. I can manually mount in TWRP and all the ROM data is there...
Click to expand...
Click to collapse
I have to actually check the box to mount system. Usually it's not mounted.
I would try loading a Team EOS nightly or some other ROM just to see if you are able to get a basic load on it.
Having access to TWRP (TFP version right!?!?!) you should be able to perform all the functions of loading/flashing a ROM.
When I recovered my bootloader, I went into TWRP, performed a wipe on all partitions (even if they failed) and then loaded Team EOS JB Nightly with gapps.
I was running CM10 before I did the HairBean failure.
--Charlie
ecatsab said:
I have to actually check the box to mount system. Usually it's not mounted.
I would try loading a Team EOS nightly or some other ROM just to see if you are able to get a basic load on it.
Having access to TWRP (TFP version right!?!?!) you should be able to perform all the functions of loading/flashing a ROM.
When I recovered my bootloader, I went into TWRP, performed a wipe on all partitions (even if they failed) and then loaded Team EOS JB Nightly with gapps.
I was running CM10 before I did the HairBean failure.
--Charlie
Click to expand...
Click to collapse
We both were then, I as well was running CM10. I have tried about 4 or 5 different roms, and nothing will boot. I have wiped everything over and over. Everything ends up with the same result, the Eee Pad bootloader screen using AndroidBoot loader, and the rom never loads up. I reflashed the recovery several times as well, just in case. The warning from Androwook page about the whole TF300 recovery thing worries me. :/ So am I supposed to be using a TF300 recovery, since I was broken halfwat there? (I tried)
**NOTE** Before proceeding please note that by following these instructions and flashing this ROM you are essentially turning you TF201 into a TF300. Therefore if you have issues with or want to update recovery for example you must use the TF300 recovery and NOT the TF201 version unless other wise stated. By using the incorrect version you could BRICK YOUR PRIME IRREVERSIBLY!! You have been warned...!! **NOTE**
Click to expand...
Click to collapse
jrodder said:
We both were then, I as well was running CM10. I have tried about 4 or 5 different roms, and nothing will boot. I have wiped everything over and over. Everything ends up with the same result, the Eee Pad bootloader screen using AndroidBoot loader, and the rom never loads up. I reflashed the recovery several times as well, just in case. The warning from Androwook page about the whole TF300 recovery thing worries me. :/ So am I supposed to be using a TF300 recovery, since I was broken halfwat there? (I tried)
Click to expand...
Click to collapse
I hope you're subscribed to this thread, my man. I see you're green... lol. Anyway, it looks like my /system is the difference here. Did you mount the /system then in TWRP mounts menu before you issue a mount command? Check this out: Also, ext4 partitions, but I don't think that should matter.
cat /etc/fstab
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk1p1 /external_sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext rw
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Click to expand...
Click to collapse
Anyone have an idea? Should I make a fresh thread with specific questions?
Warning..... Code
Everything in BOLD are notes
This was ran after booting the device into TWRP, then running adb shell in a linux terminal
~ # mke2fs -t ext3 -m 0 /dev/block/mmcblk0p8
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p8 is apparently in use by the system; will not make a filesystem here!
~ # umount /dev/block/mmcblk0p8
~ # mke2fs -t ext3 -m 0 /dev/block/mmcblk0p8
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1757840 inodes, 7023232 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
215 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # blkid
/dev/block/mmcblk0p8: UUID="8d2f6f94-082c-4ec8-87e7-0ef7f6f3bf9f" TYPE="ext3"
/dev/block/mmcblk0p4: UUID="eceb44ac-5cd8-4a55-be93-1046eb25c887" TYPE="ext3"
/dev/block/mmcblk0p2: UUID="f7c6a895-ad00-4103-aa9c-009b0639cd78" TYPE="ext3"
/dev/block/mmcblk0p1: UUID="6070af7b-4190-4e36-85d2-3e0a7661e636" TYPE="ext4"
Notice that the system block device is still ext4. TWRP tried wiping it but failed earlier
~ # mke2fs -t ext3 -m 0 /dev/block/mmcblk0p1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
49152 inodes, 196608 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=201326592
6 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
I mounted all the partition checkboxes in TWRP recovery
~ # blkid
/dev/block/mmcblk1p1: UUID="48A0-C8EC" TYPE="vfat"
/dev/block/mmcblk0p8: UUID="8d2f6f94-082c-4ec8-87e7-0ef7f6f3bf9f" TYPE="ext3"
/dev/block/mmcblk0p4: UUID="eceb44ac-5cd8-4a55-be93-1046eb25c887" TYPE="ext3"
/dev/block/mmcblk0p2: UUID="f7c6a895-ad00-4103-aa9c-009b0639cd78" TYPE="ext3"
/dev/block/mmcblk0p1: UUID="87de235c-e978-43c5-997f-76eef8910187" TYPE="ext3"
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/mmcblk0p2 on /cache type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
~ #
Click to expand...
Click to collapse
Still having an issue with loading any other ROM than Team EOS JB Nightly
TWRP Output from log file when flash was failing. Can someone (or you) assist in what that error is?
-- Install /sdcard/goomanager/cm-10-20120924-NIGHTLY-tf201.zip ...
Finding update package...
I:Update location: /sdcard/goomanager/cm-10-20120924-NIGHTLY-tf201.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "tf201" || getprop("ro.build.product") == "tf201"
assert failed: getprop("ro.product.device") == "tf201" || getprop("ro.build.product") == "tf201"
E:Error in /sdcard/goomanager/cm-10-20120924-NIGHTLY-tf201.zip
(Status 7)
Click to expand...
Click to collapse
Nevermind. I just went into the update script in the zip and removed that line. A
Running CM10 now.
ecatsab said:
Everything in BOLD are notes
This was ran after booting the device into TWRP, then running adb shell in a linux terminal
Still having an issue with loading any other ROM than Team EOS JB Nightly
TWRP Output from log file when flash was failing. Can someone (or you) assist in what that error is?
Nevermind. I just went into the update script in the zip and removed that line. A
Running CM10 now.
Click to expand...
Click to collapse
No kidding. I was figuring the recovery was smart enough to format with the correct type, considering I verified that the recovery was flashing data to the system partition without a problem, just wouldn't boot up. I will try changing mine to ext3 as well and post back with results.
ecatsab said:
Yes it works! As long as you have the blob file from NVFlash setup... AND you download the file listed, you can recover the bootloader.
Sent from my vivow using Tapatalk 2
Click to expand...
Click to collapse
which blobfile you mean? can you please upload your blobfile so i can use it too :/ would be very nice man..because im trying to follow your guide..but my problem is i dont know which blob you mean..and what did you do with ubuntu? for what is that? please help!
kind regards
edit: ok now i know what you mean..i had to do a special process for getting this blob.bin via fastboot..damn! -.- can you upload your blob.bin though..maybe it will work ! i have nothing to lose anymore.
0din said:
which blobfile you mean? can you please upload your blobfile so i can use it too :/ would be very nice man..because im trying to follow your guide..but my problem is i dont know which blob you mean..and what did you do with ubuntu? for what is that? please help!
kind regards
edit: ok now i know what you mean..i had to do a special process for getting this blob.bin via fastboot..damn! -.- can you upload your blob.bin though..maybe it will work ! i have nothing to lose anymore.
Click to expand...
Click to collapse
How broken are you? Did you reflash the bricksafe.img via nvflash?
jrodder said:
How broken are you? Did you reflash the bricksafe.img via nvflash?
Click to expand...
Click to collapse
i have a bootloop to asus logo..cant use fastboot or adb..just have the apx-mode! coming from cm10,cwm 5.8.2.0.. tried to flash TWRP via Android Terminal Emulator..after that started in recovery mode..and then the bootloop began..i didnt flash any nvflash stuff before..thats why I'm asking for his blod-file..coz maybe it will work. Hope dies last. cheers
0din said:
i have a bootloop to asus logo..cant use fastboot or adb..just have the apx-mode! coming from cm10,cwm 5.8.2.0.. tried to flash TWRP via Android Terminal Emulator..after that started in recovery mode..and then the bootloop began..i didnt flash any nvflash stuff before..thats why I'm asking for his blod-file..coz maybe it will work. Hope dies last. cheers
Click to expand...
Click to collapse
Now, you have no recovery at all? I don't think you can nvflash without running the nvflash procedure first. I could be totally off base, but pretty sure there's some signing and encryption involved with the blob.bin creation. Anyone else reading this feel free to correct me.
jrodder said:
I don't think you can nvflash without running the nvflash procedure first. I could be totally off base, but pretty sure there's some signing and encryption involved with the blob.bin creation. Anyone else reading this feel free to correct me.
Click to expand...
Click to collapse
you are correct sir, thank you.
sent from my i9250
I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.
So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?
thanks!
Adromir said:
I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.
So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?
thanks!
Click to expand...
Click to collapse
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
globula_neagra said:
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
Click to expand...
Click to collapse
Because with just the stock Recovery it doesn't mount all needed partitions correctly. I took the stock recovery i extracted from the latest RUU.
give me the stock recovery and i will do the recovery.fstab for you
globula_neagra said:
give me the stock recovery and i will do the recovery.fstab for you
Click to expand...
Click to collapse
Here it is. Thats really great! Thanks a lot
try this recovery
what i did, i used the recovery.fstab from this http://forum.xda-developers.com/showthread.php?t=1484753
i would like to try the recovery from the 4ext and see what mount points and how the filesystem is managed.
if you have one share`it with me.
the attached files is the cwm that i cooked, using the stock recovery and adding the fstab from the 5.8 cwm
you can flash it and see what results you have (if you get anny errors)
but don`t use the recovery to flash something till you don`t get the mount results to see if the mounting points are like this, if the mounting points are like this you should be ok to try and flash a rom.
# mount point fstype device
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
/data ext4 /dev/block/mmcblk0p26 fstype2=ext3
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p25 fstype2=ext3
to find out the mounting points
adb shell
mount
and you should have a long output like this (This are not from a htc desire s ! )
C:\Android\android-sdk\platform-tools>adb shell
uid=0 [email protected]:/ # mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,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)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p12 on /system type ext4 (ro,relatime,user_xattr,barrier=1,dat
a=ordered)
/dev/block/mmcblk0p13 on /data type ext4 (rw,nosuid,nodev,relatime,user_xattr,ba
rrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p14 on /persist type ext4 (rw,nosuid,nodev,relatime,user_xattr
,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,b
arrier=1,data=ordered)
/dev/block/mmcblk0p17 on /content type ext4 (rw,nosuid,nodev,relatime,user_xattr
,barrier=1,data=ordered)
/dev/block/vold/179:97 on /mnt/external_sd type vfat (rw,dirsync,nosuid,nodev,no
exec,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:20 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:20 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
exec,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)
uid=0 [email protected]:/ #
Thanks for your effort, but i can't test the recovery properly because there is a key missing to run an option. I can browse through the menu with volume +/- though, but can't enable the selected option.
I found an 4ext Recovery (version 1005.5.0), i attached it with the fstab i extracted from it
well, i could use the maping key from the cwm 5.8
there are some cwm`s that need enabling
for example on a tablet i need to press 27 times the volume key -, or a combination of + - + (volume keys) to enable the selection.
i can not test the recovery, i will rebuild later on a version based on the 5.8 key maping.
on the screen did you got any errors ?
No, it didnt show any errors yet. Is it possible to make it touch too? I tried to cook up a cwm with the fstab of 4ext but it completly failed to load any partition. 4ext itself is working though
here is the touch one, check also if the key`s are working
the recovery that you made, the keys where working ?
Havent tried the keys on my Build, but with yours they are working.
In the cwm i got this errors:
I:Skipping execution of extended command, file not found
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
Now trying to make a Backup, that seems to work, but i am not completly sure, havent tried to restore it yet. Will do that tomorrow
this is the first cwm that i made for you, but with the key maping from the stock recovery
http://www.mediafire.com/?kc8dk9gl2c9660o
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
you can check the recovery files on the sd card, if you see there the boot.img recovery, and system/data mds5 it should be ok to restore.
Is this different from the built you attached last? This works fine with the keys.
btw. can you maybe give me some tips how you built it? Later i want to make a new cwm for my tablet, but i dont want to bother you with that too
yes it is different, it is like the first build but i used the key mapping from the htc desire s stock recovery, the one from the ruu
well the tips are, keep trying till you get something working.
for example on my tablet i am using a htc sensation xl recovery (not all the stuff only the recovery which is in the sbin directory if you unpack the recovery)
unpack the stock recovery, and analyse the recovery.fstab by comparing it to the mount points, if they are ok is very good, you will have bigger chance to get something working.
try and use the clockwork builder and see if you get any results, but select the stock recovery.fstab (you have the option when you cook the recovery, is the second option)
if you don`t get any results like this try to find a similar device from a spec point of view and steal the /sbin/recovery from the device cwm recovery, put it on your recovery, repack and test.
it depends on what tablet you have also
If you need help in the future, send me a pm, because i check only once per week this section of the forum.
Ok, found boot.img but no system/data and system.ext3.dup is only about 100kb of size. Is that correct?
in the logfile there are three errors:
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
no, is not corect, that means that the recovery made by the clockworok server has some flaws
i will try to make a new one, based on 4ext recovery
---------- Post added at 07:47 PM ---------- Previous post was at 07:31 PM ----------
K, i remade the fstab
it looks like this now
# mount point fstype device
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
/data ext4 /dev/block/mmcblk0p26 fstype2=ext3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p25 fstype2=ext3
/sd-ext ext4 /dev/block/mmcblk1p2 fstype2=ext4
/system_lib ext4 /dev/block/mmcblk0p28 fstype2=ext4
You could try and find a similar device that has the version 6 recovery and try the recovery from that device (am talking about getting the recovery, unpack it, take the recovery file which is in boot.img-ramdisk\sbin\recovery
In the end, it`s all about testing
I did all my stuff alone, nobody helped me.
http://www.mediafire.com/?69a74qq9idko02v this is the recovery based on the recovery.fstab from the 4ext recovery which looks more complete.
Thanks very, very much, i really appreciate your efforts. So now, i'll start trying and trying until i get a working one
Help me plz..
I don't haved knowledge about android scripting or any something like that,.. but I was try hard to get and learn about creating CWM of my stock recovery.img .. after all is unfortunately .. always failed.
I haved try on builder.clockworkmod.com but itsn't success,...
would any member in here should help me to create CWM from my stock recovery.img please... my phone is One Scribe ZA987 with MTK6577
Hi Guys, I have a quick question
I am new to this but im learning quickly.... I think!
im making up my own recovery and so far my recovery.fstab looks like this:
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/cache ext4 /dev/block/mmcblk0p10 fstype2=ext3
/data ext4 /dev/block/mmcblk0p12 fstype2=ext3
/system ext4 /dev/block/mmcblk0p11 fstype2=ext3
/factory ext4 /dev/block/mmcblk0p4 fstype2=ext3
/crypo emmc /dev/block/mmcblk0p3
but when trying to do a backup it throws up an error saying it cant write to SDCARD, which makes sense as its not mounted
So, the question is, how do I go about mounting it for recovery?
Now, the sdcard is internal, there is no external card, I believe its symlinked to /storage/sdcard within android which is all located in the partition /data/ (mmcblk0p12)
sooo, can anyone help, ive been trawling the interweb and I can find lots of ways to do this within the main OS, but how do I go about it for recovery.fstab to be used in a custom clockwork recovery img
globula_neagra said:
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
Click to expand...
Click to collapse
can you explain to me how to dump? my phone is brigadier
Hi,
first i want to say i viewed and searched a lot of threads, and am posting here just because i'm not sure which way to follow.
I installed mateo111's 10.2 custom rom, and after a few days it started acting weird, slow and stuff... when i rebooted it, it stuck at cm logo and it stayed like that for 2 days now. When i enter cwm i get a lot of errors, can't mount anything basically.
It can't mount cache, data, system, sd card, it can only mount extsd. It also can't show any recovery logs, and thus i can't format any of it. So i'm guessing some partition got messed up or something, but i'm not that experienced to be sure. I tried restoring backup but it can't restore anything except boot.
What are my options? I can't flash any roms, i can only use adb sideload, so any advice is very welcome and i will be most thankful if someone helps me in this matter.
Thanks in advance.
Bokee88 said:
Hi,
first i want to say i viewed and searched a lot of threads, and am posting here just because i'm not sure which way to follow.
I installed mateo111's 10.2 custom rom, and after a few days it started acting weird, slow and stuff... when i rebooted it, it stuck at cm logo and it stayed like that for 2 days now. When i enter cwm i get a lot of errors, can't mount anything basically.
It can't mount cache, data, system, sd card, it can only mount extsd. It also can't show any recovery logs, and thus i can't format any of it. So i'm guessing some partition got messed up or something, but i'm not that experienced to be sure. I tried restoring backup but it can't restore anything except boot.
What are my options? I can't flash any roms, i can only use adb sideload, so any advice is very welcome and i will be most thankful if someone helps me in this matter.
Thanks in advance.
Click to expand...
Click to collapse
You don't need to mount partition to format it. Did you try to format system and data in CWM? Did it get any error log? If even CWM cannot format your partition, it may be a hardware problem.
If you can boot into CWM you can use adb to push rom file to external sdcard and install it.
> adb push your-rom.zip /external_sd/
Thank you for your response. ADB doesn't recognize my device, probably because i've managed to format system before. Because i'm a newbie, i tried pushing the file through adb nonetheless, but it displays error: device not found.
Is the only solution for this going back to stock?
system and cache can be formatted, data and sdcard can't (error mounting /data!, Skipping format... Done.). I've tried it all and after that tried installing rom and gapps, it appears as it's a succesfull install and when i reboot i'm stuck at static LG logo.
Bokee88 said:
Thank you for your response. ADB doesn't recognize my device, probably because i've managed to format system before. Because i'm a newbie, i tried pushing the file through adb nonetheless, but it displays error: device not found.
Is the only solution for this going back to stock?
system and cache can be formatted, data and sdcard can't (error mounting /data!, Skipping format... Done.). I've tried it all and after that tried installing rom and gapps, it appears as it's a succesfull install and when i reboot i'm stuck at static LG logo.
Click to expand...
Click to collapse
It's ok that you cannot mount /data because in some CWM that patition cannot be mounted. Please try to wipe dalvik cache in advanced menu. You need to do this everytime you install new rom.
artit said:
It's ok that you cannot mount /data because in some CWM that patition cannot be mounted. Please try to wipe dalvik cache in advanced menu. You need to do this everytime you install new rom.
Click to expand...
Click to collapse
When i try to wipe dalvik nothing happens, the menu just reloads quickly, no log, nothing.
Regarding data, i said "mount" because i'm getting errors when i try to wipe data "can't mount data". Also, when i try to restore a cwm backup i can only restore boot, other parts - data, system, cache - can't be mounted "error mounting /system" for example.
edit: could this have to do with my previous rom's feature that removes internal memory simulation? * disabled internal sdcard emulation: http://forum.xda-developers.com/showpost.php?p=43382611&postcount=2
I took out a log, this is what i get after trying to hard reset from cwm:
E:can't mount /cache/recovery/log
E:can't mount /cache/recovery/last_log
W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache (Invalid argument)
W:Can't unlink /cache/recovery/command
I:Can't partition non-vfat : datamedia
I:Can't format unknown volume: /emmc
W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata (Invalid argument)
Bokee88 said:
I took out a log, this is what i get after trying to hard reset from cwm:
E:can't mount /cache/recovery/log
E:can't mount /cache/recovery/last_log
W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache (Invalid argument)
W:Can't unlink /cache/recovery/command
I:Can't partition non-vfat : datamedia
I:Can't format unknown volume: /emmc
W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata (Invalid argument)
Click to expand...
Click to collapse
I'm not sure maybe your CWM is damaged. Please try to boot into CWM then issue following commands
Code:
> adb shell
# cat /proc/partitions
You should get some output like
Code:
major minor #blocks name
179 0 3784704 mmcblk0
179 1 384 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 20480 mmcblk0p8
179 9 512 mmcblk0p9
179 10 1024000 mmcblk0p10
179 11 2482176 mmcblk0p11
179 12 204800 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 16384 mmcblk0p14
179 40 2048 mmcblk0boot1
179 20 2048 mmcblk0boot0
179 60 7798784 mmcblk1
179 61 7797760 mmcblk1p1
Then check your mount point
Code:
# mount
This is my output
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata on /data type ext4 (rw,nodev,noatime,nodiratime,resuid=1000,user_xattr,barrier=1,data=ordered)
If there're something broken, please try to flash new recovery. If that still don't help, try to flash stock rom or recovery your phone by LG tool.
artit said:
I'm not sure maybe your CWM is damaged. Please try to boot into CWM then issue following commands
Code:
> adb shell
# cat /proc/partitions
You should get some output like
Code:
major minor #blocks name
179 0 3784704 mmcblk0
179 1 384 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 20480 mmcblk0p8
179 9 512 mmcblk0p9
179 10 1024000 mmcblk0p10
179 11 2482176 mmcblk0p11
179 12 204800 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 16384 mmcblk0p14
179 40 2048 mmcblk0boot1
179 20 2048 mmcblk0boot0
179 60 7798784 mmcblk1
179 61 7797760 mmcblk1p1
Then check your mount point
Code:
# mount
This is my output
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata on /data type ext4 (rw,nodev,noatime,nodiratime,resuid=1000,user_xattr,barrier=1,data=ordered)
If there're something broken, please try to flash new recovery. If that still don't help, try to flash stock rom or recovery your phone by LG tool.
Click to expand...
Click to collapse
As i said, i cannot use ADB because i formatted system, hoping to flash a new ROM, which i later discovered to be mission impossible.
I have tried troubleshooting through LG mobile tools, it upgraded to 50% and then just stopped with an error. Also, installed fastboot and tried flashing a KDZ, also stopped at 50%.
Bokee88 said:
I have tried troubleshooting through LG mobile tools, it upgraded to 50% and then just stopped with an error. Also, installed fastboot and tried flashing a KDZ, also stopped at 50%.
Click to expand...
Click to collapse
This sounds like a hardware failure
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
This sounds like a hardware failure
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In the end you were right, i returned the device to my operator and fortunately, they couldn't see that i rooted it and played with it for over a year now so they replaced the hardware in the phone, not saying what it was that died (i'm thinking the internal memory).
Anyway, thanks for your help!
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