Related
I am looking at guides on how to create roms using 'adb shell' for my Samsung Galaxy Player and I have noticed something. Also these guides aren't meant for my device specifically.
I am using instructions from this page....
http://www.freeyourandroid.com/guide/building_roms_for_odin
and this page...
http://forum.xda-developers.com/showthread.php?t=1082288
Now on the "Free your Android" page they want me to use the commands...
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
and for the XDA-Developers page they want me to use the commands...
Code:
dd if=/dev/block/stl10 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/bml8 of=/sdcard/zImage bs=4096
Now I noticed that there are differences in the commands and therefore, how do I know if the dev/block/ folder structure used is correct for my device.
Is there a way to know the dev/block folder structure for my device? I am hoping I am making sense.
It depends which device you have;either the 4.0 or 5.0. For the 4.0 the factoryfs.rfs is on /dev/block/stl9 and zImage is on bml7.
The partitions are exactly the same as a galaxy s phone.
Sent using Tapatalk
I have the 4.0 US. Is there anyway to know for sure? Is there a command that lets me see a directory list of the partitions? I can post them here.
'mount' in terminal emulator
Sent using Tapatalk
Okay. I typed in mount. Here is my results....
# 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
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfsrw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
#
I am assuming that...
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
...must be the factoryfs.rfs file.
Where is the listing for the zImage though?
I don't know why it's not shown, but I can guarantee 100% it's bml7. I've pulled the zImage from my device many times and flashed it without problems.
Yeah, its weird, results of 'mount' change for me every time. The partitions are identical to a galaxy S, I know as I compared sizes of both (using merticulus's awesome tool). For some reason you can't rip using the bml but have to use stl, even though from my underatanding they are the same. Someone tried recovering with a bml backup, but it wouldn't work, had to use stl. There is probably a logical, obvious explanation for that but I am afraid I don't know it, lol! ATTENTION; EVERYTHING SAID ABOVE APPLIES TO THE 4.0 ONLY! (just thought I should throw in a disclamer)
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..
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
Anyone had any luck? Tried a flash drive I use on other Androids and the Am2 won't register it. I'm not yet rooted or anything for what it's worth.
JJ2525 said:
Anyone had any luck? Tried a flash drive I use on other Androids and the Am2 won't register it. I'm not yet rooted or anything for what it's worth.
Click to expand...
Click to collapse
It may be your otg cable. My ham 2 worked unrooted and rooted with a 1tb external and a 16gb flash drive. It almost worked with my Ps4 gold headset but the audio cuts in and out.
aragon257 said:
It may be your otg cable. My ham 2 worked unrooted and rooted with a 1tb external and a 16gb flash drive. It almost worked with my Ps4 gold headset but the audio cuts in and out.
Click to expand...
Click to collapse
Hmm. It's a 2-way drive (with a micro usb plug on one side and usb on the other). I tried plugging directly into AM2 with the micro, then tried plugging the usb side into an otg cable that plugged into the AM2. Neither worked. The drive works flawlessly on my Z2 and Tab S.
I've now tried 2 drives, both in FAT format, and the AM2 does not recognize either, but each drive works perfectly on other devices. I've also tried the device on both mine and my friend's AM2's, same result. Perplexing.
Instead of referring to your device as the HAM2 it may be more proficient to actually specify which one you have so it doesn't cause confusion for other readers who are still learning the basics. For example, the MT2-L05 has OTG support but the MT2-L03 does not.
My apologies, I did not realize there was a discrepancy in USB support between the two models.
Yes, I have the L03. So there is no way to use a USB drive with my device?
JJ2525 said:
My apologies, I did not realize there was a discrepancy in USB support between the two models.
Yes, I have the L03. So there is no way to use a USB drive with my device?
Click to expand...
Click to collapse
OTG support would have to be built in to the MT2-L03 by modifying the kernel source and the ramdisk from your boot.img. It's a very difficult task. I have tried to do this on my daily device and wasn't successful, but came very close to it lol. However, I gave up on that project for my phone a while back. I'm currently working on making my device F2FS compatible to replace ext4 for system, data, and cache.
Modding.MyMind said:
Instead of referring to your device as the HAM2 it may be more proficient to actually specify which one you have so it doesn't cause confusion for other readers who are still learning the basics. For example, the MT2-L05 has OTG support but the MT2-L03 does not.
Click to expand...
Click to collapse
I have the MT2-L03 and OTG works fine. I have used both a Sony 2-way flash drive and a regular flash drive with an OTG cable. I can read, stream and write to and from the drives. I am rooted, but it also worked before rooting. I use ES File Explorer to access the drives.
gale2000 said:
I have the MT2-L03 and OTG works fine. I have used both a Sony 2-way flash drive and a regular flash drive with an OTG cable. I can read, stream and write to and from the drives. I am rooted, but it also worked before rooting. I use ES File Explorer to access the drives.
Click to expand...
Click to collapse
If this is true then maybe you can inform me of the directory path which would be mounted for OTG? I can add this to TWRP. However, I must admit, I did not see any evidence of OTG support for the MT2-L03, but I did see it with the MT2-L05.
Modding.MyMind said:
If this is true then maybe you can inform me of the directory path which would be mounted for OTG? I can add this to TWRP. However, I must admit, I did not see any evidence of OTG support for the MT2-L03, but I did see it with the MT2-L05.
Click to expand...
Click to collapse
I don't know how to find the path, but I am attaching a screen shot from ES file explorer. The device is USB1002. Any instructions as to how to find the path.
gale2000 said:
I don't know how to find the path, but I am attaching a screen shot from ES file explorer. The device is USB1002. Any instructions as to how to find the path.
Click to expand...
Click to collapse
With the OTG plugged up, type and enter in the terminal emulator (download from playstore if need be):
Code:
mount
Modding.MyMind said:
With the OTG plugged up, type and enter in the terminal emulator (download from playstore if need be):
Code:
mount
Click to expand...
Click to collapse
I have to go now, but will do this tomorrow morning.
Modding.MyMind said:
With the OTG plugged up, type and enter in the terminal emulator (download from playstore if need be):
Code:
mount
Click to expand...
Click to collapse
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/log /log ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/vold/179:25 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /storage/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
[email protected]:/ $
Sent from my MT2L03 using Tapatalk
---------- Post added at 09:17 PM ---------- Previous post was at 09:16 PM ----------
I have an otg cable connected to a cf card reader and able to access the files.
Sent from my MT2L03 using Tapatalk
"mount" didn't show any results for OTG. Were you plugged up before you ran the mount command?
Modding.MyMind said:
With the OTG plugged up, type and enter in the terminal emulator (download from playstore if need be):
Code:
mount
Click to expand...
Click to collapse
Here's my results. OTG is plugged in:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/log /log ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/vold/179:65 /storage/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:25 /storage/sdcard0 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
The full path given in properties for the USB device is: usb://1002/SANDISKBLUE
Will have to look deeper on my end. Mount isn't showing what I need.
Modding.MyMind said:
Will have to look deeper on my end. Mount isn't showing what I need.
Click to expand...
Click to collapse
I've tried OTG previously and I thought that OTG was not working. After seeing gale2000's screenshot, I gave it another try. After a reboot, I can see the SD card reader ONLY in ES File Explorer. It doesn't appear anywhere else in ES either. (It only appears in the LOCAL section as shown on gale2000's screen. ) I can't find it in 3c Toolbox. It doesn't appear in mount report. It doesn't appear in Huawei's own supplied file manager and it doesn't even appear in the settings screen. So there is no graceful way of disconnecting the reader without rebooting or powering down.
At the top of the screen ES normally has a box for the parent folder but for the USB reader, it is blank and ES reports the device as USB://1002/
After seeing these posts I tried my own 2-way drive. Sure enough, it shows up in ES under local/usb 1002. Fully functional, did not have to reboot before/after plugging it in, able to xfer files to/from drive flawlessly. Awesome
I was looking through build.prop and noticed the line
ro.config.hw_otg_support=false
I changed it to
ro.config.hw_otg_support=true
Now otg works without having to use ES File Explorer.
This is all perplexing! I too have the L03 and was surprised that it wouldn't read my flash drive. But I knew SOMETHING was happening, because the light on the drive lit up, but I couldn't find the directory anywhere in the stock explorer or in Total Commander. I'll have to try ES as well now :good: