ok can you also upload and link to your original boot image.
some facts discovered from your original recovery image in no particular order
a) size of image 6.3 Mb
b) ro.build.id=IMM76L
c) ro.build.date=Вто Янв 29 11:51:46 MSK 2013
d) ro.product.model=Full Android on Emulator
e) from init.rc...... write /sys/class/android_usb/android0/idVendor 18D1
from initrc...... write /sys/class/android_usb/android0/idProduct D001
f) from init.usb.rc.....write /sys/class/android_usb/android0/idProduct 0C01
from init.usb.rc.......setprop sys.usb.vid 0BB4
comment vid = idVendor
comment 2 built in Russia on an emulator
recovery builder does not do any quality control
----means can not use adb in stock recovery
comment3 build id claims to be a Motrola XOOM phone
comment4 vendor id claims to be a google phone or a HTC
#############
I have built a ctr1 which will also fail until I see your boot.img for the same reason. That is....in recovery mode ....adb needs consisent ids that match across files.
###########
but if we do not use adb in recovery mode....it should work for filesystem
clearing of cache and data and davlik cache
---which is what you should have done between each ROM flash IMHO
-------but I don't use windows and so don't know flashtools
#####################
I would like you to use fastboot which I claim does NOT need any windows drivers.....and you are going to prove it!
first read this post on sideload
download the first link from Packages needed
ignore next download and jump to Windows adb command preparation
assuming you are a windows user.
and set up adb and fastboot but see this line
ignore drives installed.....fastboot does not need any.
ignore usb debugging as you are in boot loop for normal boot up
###############
now download my ctr1 allegedly for your device
try at own risk
size is 5.6 mb so there is no way its going to overlap any other flash area
and "in theory" should be safe to flash.
copy that download into the folder where you run adb/fastboot from
or if you did the Optional instructions you can leave it in your download folder.
###############
how to flash a recovey in fastboot mode
1) on your phone you need to use buttons to get to bootloader menu
and either that will take you direct to fastboot mode or offer a menu
2) if you are in fastboot mode on phone then on PC with cable connected
commands as admin as folllows
you must see a device name it will be something like
only if you see this or a similar device name then you can flash with
your result will differ from mine but will look a little like this
good luck
PS don't forget to link to your boot image
PS2...if fastboot fails Athos will guide you on hopefully how to flash ctr1 using flashtools
but I may have to rebuild ctr1
some facts discovered from your original recovery image in no particular order
a) size of image 6.3 Mb
b) ro.build.id=IMM76L
c) ro.build.date=Вто Янв 29 11:51:46 MSK 2013
d) ro.product.model=Full Android on Emulator
e) from init.rc...... write /sys/class/android_usb/android0/idVendor 18D1
from initrc...... write /sys/class/android_usb/android0/idProduct D001
f) from init.usb.rc.....write /sys/class/android_usb/android0/idProduct 0C01
from init.usb.rc.......setprop sys.usb.vid 0BB4
comment vid = idVendor
comment 2 built in Russia on an emulator
recovery builder does not do any quality control
----means can not use adb in stock recovery
comment3 build id claims to be a Motrola XOOM phone
comment4 vendor id claims to be a google phone or a HTC
#############
I have built a ctr1 which will also fail until I see your boot.img for the same reason. That is....in recovery mode ....adb needs consisent ids that match across files.
###########
but if we do not use adb in recovery mode....it should work for filesystem
clearing of cache and data and davlik cache
---which is what you should have done between each ROM flash IMHO
-------but I don't use windows and so don't know flashtools
#####################
I would like you to use fastboot which I claim does NOT need any windows drivers.....and you are going to prove it!
first read this post on sideload
download the first link from Packages needed
ignore next download and jump to Windows adb command preparation
assuming you are a windows user.
and set up adb and fastboot but see this line
Quote:1. Connect your phone to PC with USB debugging enabled, and drivers installed.
ignore drives installed.....fastboot does not need any.
ignore usb debugging as you are in boot loop for normal boot up
###############
now download my ctr1 allegedly for your device
try at own risk
size is 5.6 mb so there is no way its going to overlap any other flash area
and "in theory" should be safe to flash.
copy that download into the folder where you run adb/fastboot from
or if you did the Optional instructions you can leave it in your download folder.
###############
how to flash a recovey in fastboot mode
1) on your phone you need to use buttons to get to bootloader menu
and either that will take you direct to fastboot mode or offer a menu
2) if you are in fastboot mode on phone then on PC with cable connected
commands as admin as folllows
Code:
fastboot devices
you must see a device name it will be something like
Quote:mt6572_phone fastboot
only if you see this or a similar device name then you can flash with
Code:
fastboot flash recovery ctr1
your result will differ from mine but will look a little like this
Quote:fastboot flash recovery ctr1
sending 'recovery' (5156 KB)...
OKAY [ 0.132s]
writing 'recovery'...
OKAY [ 0.714s]
finished. total time: 0.847s
good luck
PS don't forget to link to your boot image
PS2...if fastboot fails Athos will guide you on hopefully how to flash ctr1 using flashtools
but I may have to rebuild ctr1