[Q] Help!!!semi bricked rk3600 tablet - Android Q&A, Help & Troubleshooting

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

Related

Online Android Backup **DO BACKUP WHILE YOUR PHONE STILL ON**

ANNOUNCEMENT:
Official version that support most (including our) device has been released. See HERE
Hi All.
Here are the modified version of Online Android Backup from ORIGINAL THREAD. I've changed some codes to make it works for our HTC Legend.
How To Install:
Through CWM
1. Download from attachment onandroidv3.7_cwm.zip
2. Copy it to your sdcard
3. Reboot into recovery
4. Flash the file
Manual
1. Extract onandroid.zip attached and use adb/root explorer to push/copy the file onandroid to your /system/bin
2. change permission to rwxr-xr-x
How To use:
From PC:
1. Open terminal/command prompt
2. type adb shell
- if using CM9, type su to gain root access after step 2.
3. type onandroid
From your phone:
1. open terminal emulator, type su
2. type onandroid
UPDATE:
If you use ogo2's ROM HERE, please download SENSE_fix_tool.zip from attachment and flash it. Mediafire link are HERE
Changes:
12.06.2012: Initial modification from original version
13.06.2012: Power checking corrected
14.06.2012: Added CWM flashable file
20.06.2012: Update v3.7 from original developer. confirm to work in cm9
Changelogs from original developer:
:: Latest onandroid fixes from v3.7
:: Made "dd" not spit results.
:: Added partition detection for boot and recovery partitions.
02.07.2012: Fix for sense ROM
screenshots and file are attached.
Credits:
ameer1234567890 Original Developer
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
vriz27 said:
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
Click to expand...
Click to collapse
Yes, download the file from attachment (onandroid_CWM.zip)
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
smithchipz said:
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
Click to expand...
Click to collapse
Thanks. I just do some simple modification to the original version, praise to ameer1234567890 for the great tools.
Restoring is working fine with me but make sure you check the backup folder after onandroid is finish running and check if all required files is there especially if you do something else during the backup process.
Fix for sense ROM attached in 1st post.
feed3 said:
Fix for sense ROM attached in 1st post.
Click to expand...
Click to collapse
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
alligator_asl said:
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
Click to expand...
Click to collapse
That is due to an issue in XDA (one of the servers crashed). Should be fixed in a couple of days!
Sense fix
Sense fix tool uploaded to mediafire. Link in the post #1.
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Click to expand...
Click to collapse
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
ameer1234567890 said:
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
Click to expand...
Click to collapse
Here is it:
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /mnt/asec/sd ext3 rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/nadsoft.physicscheatsheetsfree-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/jwtc.android.chess-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
How did you partition your sdcard? Which app2sd or link2sd version do you use?
Also, post output from below command!
Code:
echo $SD_EXT_DIREECTORY
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
alligator_asl said:
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
Click to expand...
Click to collapse
Thank you for the information. I am working on a fix.
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
Click to expand...
Click to collapse
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
feed3 said:
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
Click to expand...
Click to collapse
I have fixed this in the next version. Shall be releasing soon.
ameer1234567890 said:
I have fixed this in the next version. Shall be releasing soon.
Click to expand...
Click to collapse
Thanks ameer..

Help Rooting/CWM'ing New Scroll Basic Plus Tablet

Hi i have a new tablet, its a storage options scroll basic plus. I have searched everywhere on google to find a way to root and install CWM recovery.
Specs:
Code:
Software
AndroidTM 4.0
Hardware
Processor 1GHz CPU InfoTM® Imapx210 ARM11
Display 7” TFT 800 x 480 Capacitive
Memory 512MB DDR2 RAM
Internal Memory 4GB, Micro SD Card Expandable Up to 32GB
Camera 0.3MP Front
Battery 3.7V 3000mAh Li-Polymer Rechargeable Battery
G-Sensor 3 Axis
Headphones 3.5mm Earphone Jack
Connectivity
Wireless Networking Wi-Fi 802.11b/g/n
Video Output via Mini HDMI
USB Host Port USB host x1, USB OTGx1
Power 5V DC
Multimedia
Video Support avi, mov,mp4, asf,wmv,rm,rmvb, 3GP, m4a, mpg, flv
Music Support mp3,wav, wma, aac, ac3, AAC+, RealAudio
E-Book Support TXT
Dimensions
202.1 x 123.5 x 10.5mm
Firmware DG4.0.1-7C3.B1
OS: Android 4.0.3
Now its comes to me with no surprise that the OS installed is not optimised correctly and i'd like to root it and dump a image for every partition for it then remake ICS 4.0.3 from sources. It comes to something when my HTC Wildfire out performs this device in most things.
If anyone could help me Get this device rooted and CWM installed so i can then backup the firmware and then make a custom rom from sources i'd be grateful.
Complete information of Devices output are here at paste bin.
http://pastebin.com/SGrfdW3c
Thanks in advance!
Device is now Rooted but i need some help with CWM looks like i need to port over so to speak.
MTD output
dev: size erasesize name
mtd0: 00200000 00200000 "ramdisk"
mtd1: 02000000 00200000 "kernel"
mtd2: 10000000 00200000 "system"
mtd3: 40000000 00200000 "userdata"
mtd4: 04000000 00200000 "cache"
mtd5: a8200000 00200000 "Local-disk"
mtd6: 01000000 00200000 "misc"
mount output
rootfs / rootfs rw 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
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 /proc/bus/usb usbfs rw,relatime 0 0
/dev/block/mtdblock2 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/94:0 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp936,iocharset=cp936,shortname=mixed,utf8,e rrors=remount-ro 0 0
/dev/block/vold/94:0 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp936,iocharset=cp936,shortname=mixed,utf8,e rrors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:9 /mnt/sdcard/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp936,iocharset=cp936,shortname=mixed,utf8,e rrors=remount-ro 0 0
Which partitions need dd'ing for a custom CWM Recovery to be made. Thanks in advance.
Boot: http://www.mediafire.com/?52jlegdef5e6awm (Ram-Disk)
What i think is recovery: http://www.mediafire.com/?ntun3i0u1h3e775 (Kernel)
Can anyone Help Please
I've just been given one of these to play about with. So far all it does is hang during boot, even after a full wipe and factory reset.
How did you root it and did you get anywhere with CWM etc?
hacktrix2006 said:
Device is now Rooted but i need some help with CWM looks like i need to port over so to speak.
MTD output
dev: size erasesize name
mtd0: 00200000 00200000 "ramdisk"
mtd1: 02000000 00200000 "kernel"
mtd2: 10000000 00200000 "system"
mtd3: 40000000 00200000 "userdata"
mtd4: 04000000 00200000 "cache"
mtd5: a8200000 00200000 "Local-disk"
mtd6: 01000000 00200000 "misc"
mount output
rootfs / rootfs rw 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
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 /proc/bus/usb usbfs rw,relatime 0 0
/dev/block/mtdblock2 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/94:0 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp936,iocharset=cp936,shortname=mixed,utf8,e rrors=remount-ro 0 0
/dev/block/vold/94:0 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp936,iocharset=cp936,shortname=mixed,utf8,e rrors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:9 /mnt/sdcard/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp936,iocharset=cp936,shortname=mixed,utf8,e rrors=remount-ro 0 0
Which partitions need dd'ing for a custom CWM Recovery to be made. Thanks in advance.
Can anyone Help Please
Click to expand...
Click to collapse
hi. do you have the firmware saved? I am having some issues with my device. Could you please email me the firmware to my email ? j.vincze yahoodotcodotuk
regards
Sorry my Tablet had a major problem and i cracked the screen, also when i tried to back up the partitions the .img files wasn't the right size either and there for i didn't carry one i still have the tablet and it still powers on just need to replace the screen. What issues are you having ?
hacktrix2006 said:
Sorry my Tablet had a major problem and i cracked the screen, also when i tried to back up the partitions the .img files wasn't the right size either and there for i didn't carry one i still have the tablet and it still powers on just need to replace the screen. What issues are you having ?
Click to expand...
Click to collapse
hi. it stuck on bootscreen. i have no backup, no firmware
---------- Post added at 12:42 AM ---------- Previous post was at 12:38 AM ----------
hacktrix2006 said:
Sorry my Tablet had a major problem and i cracked the screen, also when i tried to back up the partitions the .img files wasn't the right size either and there for i didn't carry one i still have the tablet and it still powers on just need to replace the screen. What issues are you having ?
Click to expand...
Click to collapse
hello.
my device stuck on bootscreen. I have no firmware to reload it. do you sell your unit?
Are you sure there is no firmware on the device, Have you tried to hard reset the device?? can you get into recovery??
TO go into recovery Press the power button with Home button pressed once the device powers up release the power button and still hold home.
hacktrix2006 said:
Are you sure there is no firmware on the device, Have you tried to hard reset the device?? can you get into recovery??
Click to expand...
Click to collapse
I can get into recovery.
I have tried to reset the device many times. with no luck. it hangs on the start picture.
that seems strange i can have a look at backing up the tablet though but can't promise i can.
hacktrix2006 said:
that seems strange i can have a look at backing up the tablet though but can't promise i can.
Click to expand...
Click to collapse
that would be really kind of you.
Would you sell your tablet anyway? I am in the UK
PM me mate!
help needed
hi mate I also have this tablet but all it does is boot loop and I can't find the firmware no one can you help me ? thanks
Sorry can't help i no longer own one.
But go and do a factory reset via recovery mode. That should do the trick.

CM Fusion Bolt / Ainol Venus / Ainol Venus Lite CWMR and TWRP Recovery Development

I created this thread to have some help from the active developers out there, currently the Ainol Novo Venus / Cherry Mobile Fusion Bolt still have no CWRM and TWRP although I am one step closer to achieving it but due to I lack of time modding this tablet I badly need help from the community to further continue the deveploment of this.
although there are a lots of firmware updates already been realease but I really don't want to jump into it until I get the CWRM (Clockworkmod) or TWRP recoveries.
so far here is the development that I have accomplished it just need to be converted to CWMR ot TWRP hoping to have some contributors out here will be much appreciated for the help guys
Code:
139|[email protected]:/ # cat /proc/partitions
major minor #blocks name
93 0 49152 acta
93 8 49152 actb
93 16 368640 actc
93 24 1048576 actd
93 32 65536 acte
93 72 5906432 actj
93 80 524288 actk
Code:
127|[email protected]:/proc # cat filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext2
ext3
ext4
cramfs
nodev ramfs
vfat
msdos
ntfs
romfs
exfat
[email protected]:/proc # cat mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/actb /misc vfat ro,noatime,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/actc /system ext4 rw,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/actd /data ext4 rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,data=ordered 0 0
/dev/block/acte /cache ext4 rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Code:
127|[email protected]:/dev/block # cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/actb /misc vfat ro,noatime,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/actc /system ext4 rw,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/actd /data ext4 rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,data=ordered 0 0
/dev/block/acte /cache ext4 rw,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Code:
1|[email protected]:/dev/block # cat /cache/recovery/last_log
Starting recovery on Thu Jan 1 00:00:03 1970
framebuffer: fd 4 (800 x 1280)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /mnt/sdcard vfat /dev/block/actj (null) 0
2 /system ext4 /dev/block/actc (null) 0
3 /cache ext4 /dev/block/acte (null) 0
4 /data ext4 /dev/block/actd (null) 0
5 /boot vfat /dev/block/actb (null) 0
6 /recovery vfat /dev/block/acta (null) 0
7 /misc emmc /dev/block/actb (null) 0
8 /mnt/sd-ext vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
I:Boot command: XMAKEBOOT
E:set_bootloader_message_block fs_type "emmc"
Command: "/sbin/recovery"
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=gs702a
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.debuggable=1
ro.setupwizard.mode=DISABLE
persist.sys.timezone=Asia/Taipei
persist.sys.strictmode.disable=true
wifi.supplicant_scan_interval=120
wifi.interface=wlan0
ro.allow.mock.location=0
persist.sys.usb.config=mass_storage,adb
ro.build.id=JRO03C
ro.build.display.id=Cherry_A610_V2
ro.build.version.incremental=eng.paduser.20130301.011658
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Mar 1 01:17:30 CST 2013
ro.build.date.utc=1362071850
ro.build.type=userdebug
ro.build.user=paduser
ro.build.host=pad--e6430-02
ro.build.tags=test-keys
ro.product.model=Fusion Bolt
ro.product.brand=Android
ro.product.name=full_gs702a
ro.product.device=gs702a
ro.product.board=full_gs702a
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ainol
ro.wifi.channels=
ro.board.platform=ATM702X
ro.build.product=gs702a
ro.build.description=full_gs702a-userdebug 4.1.1 JRO03C eng.paduser.20130301.011658 test-keys
ro.build.fingerprint=Android/full_gs702a/gs702a:4.1.1/JRO03C/eng.paduser.20130301.011658:userdebug/test-keys
ro.build.characteristics=tablet
ro.sf.lcd_density=160
ro.opengles.version=131072
ro.config.softopengles=0
ro.config.used_hw_vsync=0
ro.launcher.swipe=enable
ro.settings.config.hdmi=off
ro.systemui.volumekey=disable
ro.systemui.capture=enable
ro.launcher.config.cling=enable
ro.launcher.hideAPP=disable
ro.launcher.hideactivity=disable
ro.launcher.allapp.landX=10
ro.launcher.allapp.landY=6
ro.launcher.allapp.portX=5
ro.launcher.allapp.portY=8
ro.launcher.workspace.landX=8
ro.launcher.workspace.landY=7
ro.launcher.workspace.portX=8
ro.launcher.workspace.portY=7
launcher.force_enable_rotation=true
ro.product.usbdevice.VID=10d6
ro.product.usbdevice.PID=fffe
ro.product.mtpdevice.PID=4e41
ro.product.ptpdevice.PID=4e43
ro.shutmenu.recovery=disable
ro.shutmenu.planemode=disable
ro.shutmenu.restart=enable
ro.usb.descriptor=ainol,Fusion Bolt,3.00
ro.usbdevice.volumelabel=Fusion Bolt
ro.config.quickboot=0
ro.im.keysounddefenable=true
ro.support.gpswithwifi=1
ro.wifi.signal.level.1=-70
ro.wifi.signal.level.2=-65
ro.wifi.signal.level.3=-60
ro.wifi.signal.level.4=-55
ro.product.pribrand=actions
ro.product.primodel=owlx1
ro.sf.triplebuffer=0
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Adara.ogg
ro.config.alarm_alert=Cesium.ogg
ro.carrier=unknown
hwui.render_dirty_regions=false
ro.product.locale.language=en
ro.product.locale.region=US
dalvik.vm.dexopt-flags=v=n,o=v
dalvik.vm.checkjni=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
persist.sys.profiler_ms=0
persist.vold.set_label_done=1
init.svc.recovery=running
init.svc.adbd=running
127|[email protected]:/dev/block # cat /dev/block/acta > /sdcard/recovery.img
here is the link for the stock recovery.img and some of the stock rom files
Stock Rom Files: Download Link
Stock Recovery.img: Download Link
Alternative Link
Stock Recovery.img: LINK
I already know how to port the recovery.img back to the system but I am having problem on how to extract the stock recovery.img it is not the usual recovery.img because it is using a different table structure.
I have tried the kitchen and other tools but I think it is not unpacking it properly once this is successfully done I will create also a video tutorial on how the process went on hoping for some contributions out there and some modders to customize this rom
Reserved for tutorials
rnovino said:
I already know how to port the recovery.img back to the system but I am having problem on how to extract the stock recovery.img it is not the usual recovery.img because it is using a different table structure.
Click to expand...
Click to collapse
at first, please run following commands on adb root shell.
Code:
# mkdir /dev/xxx
# mount /dev/block/acta /dev/xxx
# ls /dev/xxx/
I noticed you used the cat command to get the boot.img and recovery.img. Can I use dd if= as well?
bumslayer said:
I noticed you used the cat command to get the boot.img and recovery.img. Can I use dd if= as well?
Click to expand...
Click to collapse
yes it is just the same
fun_ said:
at first, please run following commands on adb root shell.
Code:
# mkdir /dev/xxx
# mount /dev/block/acta /dev/xxx
# ls /dev/xxx/
Click to expand...
Click to collapse
this showed
Code:
255|[email protected]:/ # mount /dev/block/acta /dev/rec
mount /dev/block/acta /dev/rec
Usage: mount [-r] [-w] [-o options] [-t type] device directory
is there some code missing?
rnovino said:
this showed
Code:
255|[email protected]:/ # mount /dev/block/acta /dev/rec
mount /dev/block/acta /dev/rec
Usage: mount [-r] [-w] [-o options] [-t type] device directory
is there some code missing?
Click to expand...
Click to collapse
is used this and it worked
Code:
1|[email protected]:/ # busybox mount /dev/block/acta /dev/xxx
busybox mount /dev/block/acta /dev/xxx
[email protected]:/ # ls /dev/xxx
ls /dev/xxx
bin_cfg.xml
bin_cfg_UserView.xml
boot_lcd.bin
boot_pic.bin
config.xml
config_UserView.xml
gpiocfg.xml
lpow_pic.bin
pinctrl.xml
rec_bak.img
recovery.img
[email protected]:/ #
getting stock on bootloop of the recovery hmmm I just overwritted the recovery.img inside that /dev/block/acta
rnovino said:
this showed
Code:
255|[email protected]:/ # mount /dev/block/acta /dev/rec
mount /dev/block/acta /dev/rec
Usage: mount [-r] [-w] [-o options] [-t type] device directory
is there some code missing?
Click to expand...
Click to collapse
hmm, "-t vfat" may be needed. (not sure because I can't use any android shell for now, sorry)
anyway, it should be easy.
rnovino said:
getting stock on bootloop of the recovery hmmm I just overwritted the recovery.img inside that /dev/block/acta
Click to expand...
Click to collapse
what recovery.img you used?
fun_ said:
hmm, "-t vfat" may be needed. (not sure because I can't use any android shell for now, sorry)
anyway, it should be easy.
what recovery.img you used?
Click to expand...
Click to collapse
the one we converted via builder.clockworkmod.com , we copy the recovery.img inside the dev/block/acta then put it in the builder.clockworkmod.com is there any alternative I currently don't have an ubuntu to convert it via source http://www.mediafire.com/download.php?kzoysz6s164scx7
Hey rnovino bro. Were you able to fix the bootloop? I hope you did.
Looking at your recovery.img, I noticed they lack a lot of things which are included in the stock recovery.img (.rc scripts, /dev files, etc.). Does this have anything to do with your bootloop?
bumslayer said:
Hey rnovino bro. Were you able to fix the bootloop? I hope you did.
Looking at your recovery.img, I noticed they lack a lot of things which are included in the stock recovery.img (.rc scripts, /dev files, etc.). Does this have anything to do with your bootloop?
Click to expand...
Click to collapse
still figuring out I just got a small time to check out everyday so a big contribution is much welcome
Me too. So, have you recovered your tablet back to working condition?
bumslayer said:
Me too. So, have you recovered your tablet back to working condition?
Click to expand...
Click to collapse
I just port back the stock recovery and yes it is still working fine
that's good to know.
Sent from my GT-S5360 using Tapatalk 2
Pushing this thread up, for good measure. Developers out there, please help us out. Unfortunately I haven't been able to flash a recovery.img thru fastboot mode as we still lack ADB USB interface drivers for it. We can only work with ADB wirelessly.
any update
hi guys, any one working on this actively....I am not a developer but can test any build.
tnx
I built mine as well but my tablet got stuck on a boot loop and I had to reflash the firmware in order to revive it. Thank God I was so afraid I killed our tablet.
Looking back I think I forgot to include the recovery.fstab file when I built my cwm recovery. I am starting again later.
Sent from my GT-S5360 using Tapatalk 2
How did you make the CWM or TWRP recovery? Can you share your file & procedure to install the recovery.
Thanks a lot.
mGforCe said:
How did you make the CWM or TWRP recovery? Can you share your file & procedure to install the recovery.
Thanks a lot.
Click to expand...
Click to collapse
we still don't have it that is why we need contribution from other developers here in xda

[Q] CWM/TWRP "unsupported fs_type "ext4""

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!

[q] damaged internal sd card tablet .

Best regards . I have a tablet VIXION IRUX model M8 with Android 4.0.3 Ice Cream Sandwicht .
This is my problem: I connected the tablet to the PC and I partitioned the Internal SD 2.2 Gb Fat32 .
I created three partitions, Fat32 first , second ext4 and third Swap ext4 .
The tablet rebooted automarcally and now displays message "the SD card is damaged" (internal).
The system works without problem , read the micro SD card and USB external if connected .
If I click on the notification card damaged it displays the following message :
"Are you sure you want to format the NAND flash? All data on your card will be lost ."
By accepting you are unable to fix the error and returns to the damaged SD message .
I tried to do the recovery and not repair the error either.
The recovery is not CWM and have not any menu .
Now to connect the tablet to the PC does not recognize the internal SD and I can´t undo the partitions and reformat the 2.2 Gb to Fat32 .
I would please me ayudasen to solve my problem.
How could I get access to the internal SD to undo the partitions and reformat ? With terminal emulator ? With adb ? I'm new in Linux and Android.
I have an application that displays the following information about the device that could be useful to find a solution :
MTD
dev = size erasesize name
mtd0 = 00400000 00004000 "misc"
mtd1 = 00800000 00004000 "kernel"
mtd2 = 01000000 00004000 "boot"
mtd3 = 01000000 00004000 "recovery"
mtd4 = 20000000 00004000 "backup"
mtd5 = 07400000 00004000 "cache"
mtd6 = 20000000 00004000 "userdata"
mtd7 = 00400000 00004000 "kpanic"
mtd8 = 20000000 00004000 "system"
mtd9 = 83a00000 00004000 "user"
MOUNT
rootfs = rootfs/rootfs ro,relatime 0 0
tempfs = tempfs/mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
devpts = devpts/dev/pts devpts rw,relatime,mode=600 0 0
proc = proc/proc proc rw,relatime 0 0
none = none/dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock8=dev/block/mtdblock8/system ext3 rw, relatime,barrier=0,data=ordered 0 0
/dev/block/mtdblock6=dev/block/mtdblock6/data ext3 rw,nosuid,nodev,noatime,nodiratime.
errors = continue,barrier=0,data=ordered 0 0
/dev/block/mtdblock5=dev/block/mtdblock5/cache ext3 rw,nosuid,nodev,noatime,nodiratime.
errors = continue,barrier=0,data=ordered 0 0
/sys/kernel/debug = /sys/kernel/debug/sys/kernel/debug debugfs rw,relatime 0 0
Thank yoy, I wait for a friendly answer.
SOLVED
I found the solution!!!!
Simply format the partition in FAT32
You need a rooted device
Steps:
1- Download the app TERMINAL EMULATOR from Play Store
2- Open Terminal Emulator :
Write SU and press enter
Write mkdosfs /dev/block/mtdblock9 and press enter
reboot
mtdblock9 it´s in my case, probably you have another name for your partition, but you can find your name in the same folder. Be carefully and choose the right name.

Categories

Resources