im new in here and i tried this to my device..
it aborts for it will overlap..
no support for 240x320 device..
can you please add..
thanks in advance..
@asura0421
Build your own. There are several tutorials on how to do it in the root and cwm forums here.
Also no offense, but it might be time for a new phone.
Hi, in the original post you advise -
(*MTK6572 with UBIFS format EMMC is NOT supported)
In the MTK Engineering Mode I can see that I have EMMC memory but that is all.
Is there a way I can check whether or not I have this UBIFS format?
Thanks!
(2014-04-16, 03:03)Craigmill Wrote: [ -> ]Hi, in the original post you advise -
(*MTK6572 with UBIFS format EMMC is NOT supported)
In the MTK Engineering Mode I can see that I have EMMC memory but that is all.
Is there a way I can check whether or not I have this UBIFS format?
Thanks!
There are many ways, easiest is to either use adb or android terminal.
for adb
adb shell
mount
for terminal
mount
Thanks for your fast reply!!
I input a command line "adb shell mount" and got a long list.
In that list I could see the following lines beginning with emmc
/emmc@android /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/emmc@usrdata /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/emmc@cache /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/emmc@protect_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/emmc@protect_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
Does this tell me anything?
Did I use the correct adb command line?
(2014-04-16, 04:53)Craigmill Wrote: [ -> ]Thanks for your fast reply!!
I input a command line "adb shell mount" and got a long list.
In that list I could see the following lines beginning with emmc
/emmc@android /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/emmc@usrdata /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/emmc@cache /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/emmc@protect_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/emmc@protect_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
Does this tell me anything?
Did I use the correct adb command line?
Says you are using ext4 not UBIFS.
The process finished for me on my Star (alps) mtk6592
But at the end when it tried to boot into recovery it stalled on the Android logo.
I removed the battery and its booting up fine and the phone still works however I cant get into the recovery it always stalls on the Android logo.
Any ideas?
(2014-04-17, 19:47)dermo Wrote: [ -> ]The process finished for me on my Star (alps) mtk6592
But at the end when it tried to boot into recovery it stalled on the Android logo.
I removed the battery and its booting up fine and the phone still works however I cant get into the recovery it always stalls on the Android logo.
Any ideas?
This happens when something is different in your recovery.img, you would need to unpack your stock recovery.img and the cw_recovery.img and see what is missing most likely a module, if it's a module you need to add module to the cw-recovery.img and make a call to it via init.rc then repack and flash.