Tablet ICOO D50 Lite (A13)
OS: Android 4.0.4 ICS
How do I know which section is the boot, which is the recovery, emmc and other nand*
The system has /dev/block/nand[a-i] (9pcs)
nandh - cache
nande - data
nandd - system
and sdcard - /dev/block/vold/93:64 (?)
How do I know the rest of the mount point?
mount does not show the boot and recovery.
xorkrus said:
Tablet ICOO D50 Lite (A13)
OS: Android 4.0.4 ICS
How do I know which section is the boot, which is the recovery, emmc and other nand*
The system has /dev/block/nand[a-i] (9pcs)
nandh - cache
nande - data
nandd - system
and sdcard - /dev/block/vold/93:64 (?)
How do I know the rest of the mount point?
mount does not show the boot and recovery.
Click to expand...
Click to collapse
Using terminal emulator or ADB shell type:
mount
This will list the mount points. If your rooted you can also type (Run as root in ADB shell or terminal emulator):
cat /proc/dev
This will also provide mount information and other similar information.
Sent from my SCH-I535 using xda premium
shimp208 said:
Using terminal emulator or ADB shell type:
mount
This will list the mount points. If your rooted you can also type (Run as root in ADB shell or terminal emulator):
cat /proc/dev
This will also provide mount information and other similar information.
Click to expand...
Click to collapse
View attachment mounts.txt
Not found any information about boot or recovery in mounts (and /proc/dev - not found)
xorkrus said:
View attachment 1395857
Not found any information about boot or recovery in mounts (and /proc/dev - not found)
Click to expand...
Click to collapse
Try running the following command from ADB shell
Code:
# cat /proc/mtd
This should return an output similar to but not exactly identical to
Code:
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 00140000 00020000 "misc"
mtd3: 00060000 00020000 "splash"
mtd4: 0ba00000 00020000 "system"
mtd5: 03f00000 00020000 "cache"
mtd6: 0a0a0000 00020000 "userdata"
mtd7: 01400000 00020000 "userdata2"
mtd8: 01400000 00020000 "cust"
From here you should be able to tell which ones is boot, recovery, etc.
shimp208 said:
Try running the following command from ADB shell
Code:
# cat /proc/mtd
This should return an output similar to but not exactly identical to
From here you should be able to tell which ones is boot, recovery, etc.
Click to expand...
Click to collapse
Code:
adb shell cat /proc/mtd
/proc/mtd: No such file or directory
and other *mtd* devices in /dev or /proc - not found.
xorkrus said:
Code:
adb shell cat /proc/mtd
/proc/mtd: No such file or directory
and other *mtd* devices in /dev or /proc - not found.
Click to expand...
Click to collapse
Seems your disk device got an internal FTL and does not uses MTD. Look for the device node (e.g. /dev/nand, /dev/block/nand, compare device node id with the partitions) and run [busybox] fdisk on it to print out the partition sizes. Now you can by the sizes guess which is the boot partition. Use dd if=/dev/block/nandx of=testboot.img and see if you'll get a valid boot image. Now you know for sure.
kuisma said:
Seems your disk device got an internal FTL and does not uses MTD. Look for the device node (e.g. /dev/nand, /dev/block/nand, compare device node id with the partitions) and run [busybox] fdisk on it to print out the partition sizes. Now you can by the sizes guess which is the boot partition. Use dd if=/dev/block/nandx of=testboot.img and see if you'll get a valid boot image. Now you know for sure.
Click to expand...
Click to collapse
View attachment fdisk.txt
I need not only the boot-partition. I would like to know, for example, nanda - /, nandb - / system, nandc - boot, nandd - recovery, etc...
On the output of commands fdisk, i was not able to correlate the sections.
Only nandi - /mnt/sdcard and nande - system partition.
xorkrus said:
View attachment 1409237
I need not only the boot-partition. I would like to know, for example, nanda - /, nandb - / system, nandc - boot, nandd - recovery, etc...
On the output of commands fdisk, i was not able to correlate the sections.
Only nandi - /mnt/sdcard and nande - system partition.
Click to expand...
Click to collapse
You already know system, cache and data. Also, root and boot lives in the same partition.
I successfully ported CWM on my device (my first ever :victory but I'm having a problem with flashing update zips. The device is using EXT4 on the cache/data/system partitions and through CWM I'm able to mount and browse them via adb. When I'm trying to flash a CM10.1 build, this is the error I'm getting:
Code:
[...]
format: unsupported fs_type "ext4" partition_type "EMMC"script aborted (no error message)
[...]
I inspected the updater-script both in my custom CM10.1 build and in the manufacturer's OTA package and they match, I guess this means that my configs are fine at this point. There must be something I missed when I created the *.mk files that adds some EXT4 tools. Any help appreciated!
I don't know about your device, but for mine, modifying recovery.fstab solves the issue
Replace the file partition mentioned there (Eg: RFS) to EXT4
I have defined the partitions as ext4 in recovery.fstab, but the problem still persists. I'm missing something very obvious....
Code:
/system ext4 /dev/block/system
/cache ext4 /dev/block/cache
/data ext4 /dev/block/data
I also tried TWRP with the same results. I'm dumping all the information I have collected just in case anyone knows something about it. This thread is on the top of the Google results, it seems that noone else has seen this error. At least I'm first at something.
This is an Amlogic 8729-MX tablet, a g34ref(maybe) reference board. It is different from all the other Amlogic 8729-MX tablets, at least on the partition level.
Code:
[email protected]:/ $ cat /proc/mtd
dev: size erasesize name
mtd0: 00800000 00200000 "bootloader"
mtd1: 00800000 00200000 "logo"
mtd2: 00800000 00200000 "aml_logo"
mtd3: 00800000 00200000 "recovery"
mtd4: 00800000 00200000 "boot"
mtd5: 40400000 00200000 "system"
mtd6: 10000000 00200000 "cache"
mtd7: 40000000 00200000 "userdata"
mtd8: 16bc00000 00200000 "NFTL_Part"
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
31 0 8192 mtdblock0
31 1 8192 mtdblock1
31 2 8192 mtdblock2
31 3 8192 mtdblock3
31 4 8192 mtdblock4
31 5 1052672 mtdblock5
31 6 262144 mtdblock6
31 7 1048576 mtdblock7
31 8 5959680 mtdblock8
250 20 917504 system
250 24 229376 cache
250 28 917504 data
250 32 5216256 media
253 0 7639040 cardblksd
253 1 7638016 cardblksd1
Code:
[email protected]:/ $ cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/system /system ext4 rw,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/data /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
Code:
# mount point fstype device device2
/bootloader mtd bootloader
/logo mtd logo
/aml_logo mtd aml_logo
/recovery mtd recovery
/boot mtd boot
/system ext4 /dev/block/system
/cache ext4 /dev/block/cache
/data ext4 /dev/block/data
/emmc vfat /dev/block/media
/sdcard vfat /dev/block/cardblksd1 /dev/block/cardblksd0
This is the error I'm getting:
Code:
Installing '/sdcard/cm_c97-ota-eng.giannoug.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm_c97-ota-eng.giannoug.zip.md5
Skipping MD5 check: no MD5 file found.
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 10.1
run_program: child exited with status 127
format: unsupported fs_type "ext4" partition_type "EMMC"script aborted (no error message)
script aborted (no error message)E:Error executing updater binary in zip '/sdcard/cm_c97-ota-eng.giannoug.zip'
Error flashing zip '/sdcard/cm_c97-ota-eng.giannoug.zip'
Any help is appreciated.
Hi, I've been having the same problem for the longest time, and also couldn't find any solutions online. However, I may have stumbled upon the solution going through the source code. Looking at /recovery/updater/install.c, it seems the format command looks for a definition "#ifdef USE_EXT4" before going through with formatting as ext4. I'm not certain, but I think you have to have the following in one of your .mk files, such as BoardConfig.mk:
TARGET_USERIMAGES_USE_EXT4 := true
This line was in a .mk for a build I succesfully managed to install, but wasn't in the ones that did not work. I hope this helps anyone else who is encountering this error.
Tag for search: Clockworkmod Status 7 error
xenogenesis1 said:
Hi, I've been having the same problem for the longest time, and also couldn't find any solutions online. However, I may have stumbled upon the solution going through the source code. Looking at /recovery/updater/install.c, it seems the format command looks for a definition "#ifdef USE_EXT4" before going through with formatting as ext4. I'm not certain, but I think you have to have the following in one of your .mk files, such as BoardConfig.mk:
TARGET_USERIMAGES_USE_EXT4 := true
This line was in a .mk for a build I succesfully managed to install, but wasn't in the ones that did not work. I hope this helps anyone else who is encountering this error.
Tag for search: Clockworkmod Status 7 error
Click to expand...
Click to collapse
Unluckily I have that option set in my configs (it was commented on the configs I'm basing on and I just uncommented it). Is there a way to tell the build system to output all the variables so I can triple check it is enabled? Let's hope it is disabled somewhere and I can't find it.
One other thing I'm suspecting is the Flash Translation Layer of the kernel... It doesn't really make sense, but I can't think of anything else. I'll guess I'll have to switch to other partition types. Last question, does anyone know if EXT4 is required? I think I read somewhere that it's needed for multiuser mode in the latest Android versions.
Thanks everyone!
EDIT: The weird part is that I can format the partitions through the "Format" menu... That means that EXT4 tools are compiled in the recovery, right?
I finally managed to fix it. There was a custom ota_from_target_files script that was generating UBIFS scripts... I had it commented at first (that's why it worked suddenly and then broke again) but I messed up my commits and undid the change.
Thanks everyone!
Hi i have an RK3600 Nemesis tablet which i rooted last week and it worked fine for a few days. To free up some space i moved some apps from the device to the sd card.When i switched it off and back on it will not boot up it just stays on the android logo screen and thats it.I have tried many ways to put it in recovery mode but to no avail.I have pressed the reset button,held the volume buttons with the power button,ive looked at all the different ways but my tablet will not go into recovery mode.i have tried restoring a firmware using the rockchip batchtool v1.7 but the device idicator box is pink and when i press the switch button it turns tablet off disconnects and the rockchip usb drivers dissapear from the device manager.I really need help to get my tablet back on please any help will be appreciated i would like to reflash with the latest firmware and if possible one thats pre rooted.
Full Specification:
Detailed product Information
Tablet Colour Black only (from 24.8.13)
Processer Rockchip 3066 Dual core 1.6 Ghz,combind 3.2ghz
Quad Core Mali 400
Display 10.1 "TFT screen:1024*600
Nand Flash 8GB
RAM 1GB
Touch Screen Capacitive touch screen
Socket/Jack 1*USB , 1*OTG USB
1*HDMI Jack
1* Micro Sd Slot
1*DC-in jack
1x 3.5mm stereo headphone jack
Wifi 802.11b/g/n
HDMI Mini HDMI Port
Dual Camera 0.3MP Front/2.0MP Rear
Battery Lithium-ion Polymer 5000mAh/ 3.7V
Tablet is super efficient so it will out last
8000mah batteries in older tablets.
O/S ANDROID 4.1 latest version (jelly bean)
Adobe flash 11.0
Graphics acceleration
2D/ 3D/ OpenGL ES2.0(AMD Z430)/ OpenVG1.1(AMD Z160)@27M Tri/sec
manni84 said:
Hi i have an RK3600 Nemesis tablet which i rooted last week and it worked fine for a few days. To free up some space i moved some apps from the device to the sd card.When i switched it off and back on it will not boot up it just stays on the android logo screen and thats it.I have tried many ways to put it in recovery mode but to no avail.I have pressed the reset button,held the volume buttons with the power button,ive looked at all the different ways but my tablet will not go into recovery mode.i have tried restoring a firmware using the rockchip batchtool v1.7 but the device idicator box is pink and when i press the switch button it turns tablet off disconnects and the rockchip usb drivers dissapear from the device manager.I really need help to get my tablet back on please any help will be appreciated i would like to reflash with the latest firmware and if possible one thats pre rooted.
Click to expand...
Click to collapse
can anybody help please give me some advice on fixing this boot loop?
tablet is a rockchip rk3600 nemesis 10.1" 3.2ghz dualcore cpu quad core graphics.
Full Specification:
Detailed product Information
Tablet Colour Black only (from 24.8.13)
Processer Rockchip 3066 Dual core 1.6 Ghz,combind 3.2ghz
Quad Core Mali 400
Display 10.1 "TFT screen:1024*600
Nand Flash 8GB
RAM 1GB
Touch Screen Capacitive touch screen
Socket/Jack 1*USB , 1*OTG USB
1*HDMI Jack
1* Micro Sd Slot
1*DC-in jack
1x 3.5mm stereo headphone jack
Wifi 802.11b/g/n
HDMI Mini HDMI Port
Dual Camera 0.3MP Front/2.0MP Rear
Battery Lithium-ion Polymer 5000mAh/ 3.7V
Tablet is super efficient so it will out last
8000mah batteries in older tablets.
O/S ANDROID 4.1 latest version (jelly bean)
Adobe flash 11.0
Graphics acceleration
2D/ 3D/ OpenGL ES2.0(AMD Z430)/ OpenVG1.1(AMD Z160)@27M Tri/sec
I found a flasing tutorial with the tool you mentioned before.
http://www.arctablet.com/blog/featured/flashing-arnova-g2-rockchip-2918-rockchip-flashing-tool/
When you tell that usb drivers dissapear from the device manager do you mean that you can see your device but as unknown device or it doesn't appear at all?
In the guide I found this guy install the drivers by hand browsing into the right folder.
If your device doesn't appear at all have you try to disconect and reconect the usb cable to see if your device appears?
Here you can choose recovery for your device:
CWM-based Recovery images for RK3066 devices
The only topic I found with rom for RK3066 is this (It has prerooted rom too but I don't know if it fits to your device):
[ROMS][UG007/Imito MX1/2][RK3066] Post em here!
If you can access recovery mode try to wipe cache partition (maybe it's good to try clean dalvik cache too if you have cwm installed / even better if you try a factory reset).It may corrects the bootloop.
You could try this tool too for flashing:
Installing firmware using the Rockchip RKAndroid Tool
Tell me if something helps.
Gatosbil said:
I found a flasing tutorial with the tool you mentioned before.
http://www.arctablet.com/blog/featured/flashing-arnova-g2-rockchip-2918-rockchip-flashing-tool/
When you tell that usb drivers dissapear from the device manager do you mean that you can see your device but as unknown device or it doesn't appear at all?
In the guide I found this guy install the drivers by hand browsing into the right folder.
If your device doesn't appear at all have you try to disconect and reconect the usb cable to see if your device appears?
Here you can choose recovery for your device:
CWM-based Recovery images for RK3066 devices
The only topic I found with rom for RK3066 is this (It has prerooted rom too but I don't know if it fits to your device):
[ROMS][UG007/Imito MX1/2][RK3066] Post em here!
If you can access recovery mode try to wipe cache partition (maybe it's good to try clean dalvik cache too if you have cwm installed / even better if you try a factory reset).It may corrects the bootloop.
You could try this tool too for flashing:
Installing firmware using the Rockchip RKAndroid Tool
Tell me if something helps.
Click to expand...
Click to collapse
hi first of all thanks for the reply.i have tried to get into recovery mode but ive not found any solution.when i try to use a flashing tool it doesnt recognise the device even after installing the drivers i will try again with RKAndroid but when i tried with the rockchip batch tool.it recognised my device with a pink box and it said rockchip usb on my devices on my laptop but when i press the switch button to put the tablet in flash mode it turns the tablet off and on my devices the rockchip usb disappears.I think the problem is putting the tablet in a flash mode so the laptop recognises the tablet ive been searching everywhere for a solution but the tablet is just stuck on a boot loop.
rkandroid tool
manni84 said:
hi first of all thanks for the reply.i have tried to get into recovery mode but ive not found any solution.when i try to use a flashing tool it doesnt recognise the device even after installing the drivers i will try again with RKAndroid but when i tried with the rockchip batch tool.it recognised my device with a pink box and it said rockchip usb on my devices on my laptop but when i press the switch button to put the tablet in flash mode it turns the tablet off and on my devices the rockchip usb disappears.I think the problem is putting the tablet in a flash mode so the laptop recognises the tablet ive been searching everywhere for a solution but the tablet is just stuck on a boot loop.
Click to expand...
Click to collapse
hi just for an update i tried the RKAndroid tool and it recognises my device through mass storage when i click switch it says it cannot switch because of no drive. When i click erase it says MSC cannot erase i havent got much experience with flashing or RKAndroid.Is there a tut on how to use it properly to flash or restore my device through mass storage because my tab refuses to switch.
manni84 said:
hi first of all thanks for the reply.i have tried to get into recovery mode but ive not found any solution.when i try to use a flashing tool it doesnt recognise the device even after installing the drivers i will try again with RKAndroid but when i tried with the rockchip batch tool.it recognised my device with a pink box and it said rockchip usb on my devices on my laptop but when i press the switch button to put the tablet in flash mode it turns the tablet off and on my devices the rockchip usb disappears.I think the problem is putting the tablet in a flash mode so the laptop recognises the tablet ive been searching everywhere for a solution but the tablet is just stuck on a boot loop.
Click to expand...
Click to collapse
Even if you are in a bootloop you could try to use if adb commands are working on your device to clear your cache and dalvik cache.
At first open a cmd prompt in the place you have adb.exe and do an attempt to get into recovery by giving the command adb reboot recovery.
If you still can't get into recovery but you are able to use adb give the command adb shell to get into the shell.If you can see a $ you need to type su to get root privilages (Then you will probably see a #).If you can see this without to type su command you are probably rooted.
As long as you see # symbol run one of these commands to give your partition table on your device:
cat proc/mtd
cat /proc/emmc
It should print you something like this:
Code:
[email protected]:/ $ cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 18000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 80000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 14000000 00004000 "system"
mtd9: 04000000 00004000 "cdrom"
mtd10: 310800000 00004000 "user"
Code:
[email protected]/# cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p32: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffc00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p22: 31fffc00 00000200 "system"
mmcblk0p24: 077f5c00 00000200 "cache"
mmcblk0p23: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p25: 00008000 00000200 "extra"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p19: 01000000 00000200 "adsp"
mmcblk0p18: 007ffa00 00000200 "radio_config"
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
You can see the partition numbers like that.
If you use mount command you will see all your partition informations like this (just give this command to check if you have ext4 or rfs filesystem).
Code:
[email protected]/# mount
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
/dev/block/mmcblk0p22 /system ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc
,data=ordered 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=00
00,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=re
mount-ro 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow
_other 0 0
/dev/block/vold/179:65 /storage/sdcard0 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
/dev/block/vold/179:65 /mnt/secure/asec 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
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.fingersoft.hillclimb-2 ext4 ro,dirsync,nosuid,node
v,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.mobilityflow.torrent.prof-1 ext4 ro,dirsync,nosuid
,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.hapogames.BubbleParadise-1 ext4 ro,dirsync,nosuid,
nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.zeptolab.ctr.paid-1 ext4 ro,dirsync,nosuid,nodev,n
oatime 0 0
/dev/block/dm-4 /mnt/asec/com.navngo.igo.javaclient-1 ext4 ro,dirsync,nosuid,nod
ev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.alexvas.dvr.pro-1 ext4 ro,dirsync,nosuid,nodev,noa
time 0 0
/dev/block/dm-6 /mnt/asec/org.videolan.vlc.betav7neon-2 ext4 ro,dirsync,nosuid,n
odev,noatime 0 0
/dev/block/dm-7 /mnt/asec/dk.logisoft.aircontrolhdfull-1 ext4 ro,dirsync,nosuid,
nodev,noatime 0 0
/dev/block/dm-8 /mnt/asec/com.kuhakuworks.DOOORS-2 ext4 ro,dirsync,nosuid,nodev,
noatime 0 0
/dev/block/dm-9 /mnt/asec/com.game.CeramicDestroyer-1 ext4 ro,dirsync,nosuid,nod
ev,noatime 0 0
/dev/block/dm-10 /mnt/asec/info.gargy.hangman-1 ext4 ro,dirsync,nosuid,nodev,noa
time 0 0
/dev/block/dm-11 /mnt/asec/ru.zdevs.zarchiver-1 ext4 ro,dirsync,nosuid,nodev,noa
time 0 0
/dev/block/dm-12 /mnt/asec/com.adobe.reader-1 ext4 ro,dirsync,nosuid,nodev,noati
me 0 0
/dev/block/dm-13 /mnt/asec/com.game.JewelsLegend-2 ext4 ro,dirsync,nosuid,nodev,
noatime 0 0
/dev/block/dm-14 /mnt/asec/com.twodboy.worldofgoofull-1 ext4 ro,dirsync,nosuid,n
odev,noatime 0 0
/dev/block/dm-15 /mnt/asec/com.halfbrick.fruitninja-1 ext4 ro,dirsync,nosuid,nod
ev,noatime 0 0
/dev/block/dm-16 /mnt/asec/com.game.DragonGem-1 ext4 ro,dirsync,nosuid,nodev,noa
time 0 0
/dev/block/dm-17 /mnt/asec/air.com.adobe.pstouch-1 ext4 ro,dirsync,nosuid,nodev,
noatime 0 0
/dev/block/dm-18 /mnt/asec/com.bitknights.dict.enggre.free-2 ext4 ro,dirsync,nos
uid,nodev,noatime 0 0
/dev/block/dm-19 /mnt/asec/com.byril.battleship-2 ext4 ro,dirsync,nosuid,nodev,n
oatime 0 0
/dev/block/dm-20 /mnt/asec/devian.tubemate.home-2 ext4 ro,dirsync,nosuid,nodev,n
oatime 0 0
Then you need to give a command like this (I will give you an example for my filesystem / I gave cat /proc/emmc and mount command to my Sensation):
**I will try to mount my data partition as rewritable.It is the one with "userdata" name.**
mount -o remount,rw -t ext4 /dev/block/mmcblk0p23 /data
For you will be something similar.
mount -o remount,rw {your partition format} /dev/block/{partition number} /{your mount point}
Do the same for cache partition.
Example (for my device):
mount -o remount,rw -t ext4 /dev/block/mmcblk0p24 /cache
As long as you have mount your partitions as rewritable you can clear cache and dalvik catche by giving these commands:
rm -rf /cache/*
rm -rf /data/dalvik-cache/*
manni84 said:
hi just for an update i tried the RKAndroid tool and it recognises my device through mass storage when i click switch it says it cannot switch because of no drive. When i click erase it says MSC cannot erase i havent got much experience with flashing or RKAndroid.Is there a tut on how to use it properly to flash or restore my device through mass storage because my tab refuses to switch.
Click to expand...
Click to collapse
Try to uninstall the drivers from device manager and then reinstall them by hand.Have you try to disconnect and reconect the cable when your device is into flash mode to see if it appears?Are you running windows 32bit or 64bit?
If you like you can take a look to this guide here:
RK3066 Update Process
Gatosbil said:
Even if you are in a bootloop you could try to use if adb commands are working on your device to clear your cache and dalvik cache.
At first open a cmd prompt in the place you have adb.exe and do an attempt to get into recovery by giving the command adb reboot recovery.
If you still can't get into recovery but you are able to use adb give the command adb shell to get into the shell.If you can see a $ you need to type su to get root privilages (Then you will probably see a #).If you can see this without to type su command you are probably rooted.
As long as you see # symbol run one of these commands to give your partition table on your device:
cat proc/mtd
cat /proc/emmc
It should print you something like this:
Code:
[email protected]:/ $ cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00800000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 18000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 80000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 14000000 00004000 "system"
mtd9: 04000000 00004000 "cdrom"
mtd10: 310800000 00004000 "user"
Code:
[email protected]/# cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p32: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffc00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p22: 31fffc00 00000200 "system"
mmcblk0p24: 077f5c00 00000200 "cache"
mmcblk0p23: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p25: 00008000 00000200 "extra"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p19: 01000000 00000200 "adsp"
mmcblk0p18: 007ffa00 00000200 "radio_config"
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
You can see the partition numbers like that.
If you use mount command you will see all your partition informations like this (just give this command to check if you have ext4 or rfs filesystem).
Code:
[email protected]/# mount
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
/dev/block/mmcblk0p22 /system ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc
,data=ordered 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=00
00,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=re
mount-ro 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow
_other 0 0
/dev/block/vold/179:65 /storage/sdcard0 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
/dev/block/vold/179:65 /mnt/secure/asec 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
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.fingersoft.hillclimb-2 ext4 ro,dirsync,nosuid,node
v,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.mobilityflow.torrent.prof-1 ext4 ro,dirsync,nosuid
,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.hapogames.BubbleParadise-1 ext4 ro,dirsync,nosuid,
nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.zeptolab.ctr.paid-1 ext4 ro,dirsync,nosuid,nodev,n
oatime 0 0
/dev/block/dm-4 /mnt/asec/com.navngo.igo.javaclient-1 ext4 ro,dirsync,nosuid,nod
ev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.alexvas.dvr.pro-1 ext4 ro,dirsync,nosuid,nodev,noa
time 0 0
/dev/block/dm-6 /mnt/asec/org.videolan.vlc.betav7neon-2 ext4 ro,dirsync,nosuid,n
odev,noatime 0 0
/dev/block/dm-7 /mnt/asec/dk.logisoft.aircontrolhdfull-1 ext4 ro,dirsync,nosuid,
nodev,noatime 0 0
/dev/block/dm-8 /mnt/asec/com.kuhakuworks.DOOORS-2 ext4 ro,dirsync,nosuid,nodev,
noatime 0 0
/dev/block/dm-9 /mnt/asec/com.game.CeramicDestroyer-1 ext4 ro,dirsync,nosuid,nod
ev,noatime 0 0
/dev/block/dm-10 /mnt/asec/info.gargy.hangman-1 ext4 ro,dirsync,nosuid,nodev,noa
time 0 0
/dev/block/dm-11 /mnt/asec/ru.zdevs.zarchiver-1 ext4 ro,dirsync,nosuid,nodev,noa
time 0 0
/dev/block/dm-12 /mnt/asec/com.adobe.reader-1 ext4 ro,dirsync,nosuid,nodev,noati
me 0 0
/dev/block/dm-13 /mnt/asec/com.game.JewelsLegend-2 ext4 ro,dirsync,nosuid,nodev,
noatime 0 0
/dev/block/dm-14 /mnt/asec/com.twodboy.worldofgoofull-1 ext4 ro,dirsync,nosuid,n
odev,noatime 0 0
/dev/block/dm-15 /mnt/asec/com.halfbrick.fruitninja-1 ext4 ro,dirsync,nosuid,nod
ev,noatime 0 0
/dev/block/dm-16 /mnt/asec/com.game.DragonGem-1 ext4 ro,dirsync,nosuid,nodev,noa
time 0 0
/dev/block/dm-17 /mnt/asec/air.com.adobe.pstouch-1 ext4 ro,dirsync,nosuid,nodev,
noatime 0 0
/dev/block/dm-18 /mnt/asec/com.bitknights.dict.enggre.free-2 ext4 ro,dirsync,nos
uid,nodev,noatime 0 0
/dev/block/dm-19 /mnt/asec/com.byril.battleship-2 ext4 ro,dirsync,nosuid,nodev,n
oatime 0 0
/dev/block/dm-20 /mnt/asec/devian.tubemate.home-2 ext4 ro,dirsync,nosuid,nodev,n
oatime 0 0
Then you need to give a command like this (I will give you an example for my filesystem / I gave cat /proc/emmc and mount command to my Sensation):
**I will try to mount my data partition as rewritable.It is the one with "userdata" name.**
mount -o remount,rw -t ext4 /dev/block/mmcblk0p23 /data
For you will be something similar.
mount -o remount,rw {your partition format} /dev/block/{partition number} /{your mount point}
Do the same for cache partition.
Example (for my device):
mount -o remount,rw -t ext4 /dev/block/mmcblk0p24 /cache
As long as you have mount your partitions as rewritable you can clear cache and dalvik catche by giving these commands:
rm -rf /cache/*
rm -rf /data/dalvik-cache/*
Try to uninstall the drivers from device manager and then reinstall them by hand.Have you try to disconnect and reconect the cable when your device is into flash mode to see if it appears?Are you running windows 32bit or 64bit?
If you like you can take a look to this guide here:
RK3066 Update Process
Click to expand...
Click to collapse
hi thanks for the help this sounds really complicated i have a limited amount of experience with adb and cmd i rooted my tablet ok but this is a whole new area i cant find adb.exe in the platform tools folder, and do you mean open a windows cmd whilst the folder is in the background sorry to sound so stupid but i really need a step by step tut thanks anyway for your time is there a post or thread on here that i could follow?
manni84 said:
hi thanks for the help this sounds really complicated i have a limited amount of experience with adb and cmd i rooted my tablet ok but this is a whole new area i cant find adb.exe in the platform tools folder, and do you mean open a windows cmd whilst the folder is in the background sorry to sound so stupid but i really need a step by step tut thanks anyway for your time is there a post or thread on here that i could follow?
Click to expand...
Click to collapse
I know that mounting partitions and deleting files manually with adb is a little complicated situation but you can try only one command with adb that could help you get into recovery without pressing buttons.Just run a cmd prompt (as administrator / right click --> run as Administrator).Then give the command cd ,find the directory you have an adb.exe and copy paste it to cmd like this:
cd C:\Android
Then give the command (While your device is in a bootloop):
adb reboot recovery
If the adb is working you have a chance to boot into recovery with this way.
After that you can wipe cache , factory reset and if you still have cwm you can wipe dalvik-cache too.
You can see this topic if you like:
rebooting in into recovery or boot loader directly from ABD For beginners