error processing Rom mannager pls help - Android Q&A, Help & Troubleshooting

i have micromax a27 bolt
Its the important problem nw i faced.... pls help meee.....................also i attach a report.log file
I got a error when i select 'UPDATE TOOL' in mobileuncle.......
i select 'check start safe flash update .zip(null package)-' - click next- click start test.....
phone reboot into recovery mode....
" sd card marker not fount
error proccesing ROM mannager script
please verify that you are performing the back uo,restore from rom mannager v4.4.0.0 or higher
please open rom mannager to report issue
before i run mobileuncle i install rom mannager and take a backup by boot into recovery by rom mannager...
i got this error by run mobile uncle and select update tool...and click check test.....
then i delete backup...i uninstall rom mannager.... bt cannot solve this problem
the report log file is here
Starting recovery on Wed May 25 16:49:49 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v6.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk0p1 (null) 0
2 /system yaffs2 system (null) 0
3 /cache yaffs2 cache (null) 0
4 /data yaffs2 userdata (null) 0
5 /misc mtd misc (null) 0
6 /boot mtd boot (null) 0
7 /recovery mtd recovery (null) 0
8 /fixnv yaffs2 fixnv (null) 0
9 /runtimenv yaffs2 runtimenv (null) 0
10 /backupfixnv yaffs2 backupfixnv (null) 0
11 /productinfo yaffs2 productinfo (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
persist.msms.phone_count=2
persist.sys.sprd.modemreset=1
ro.device.support.wifi=true
ro.device.support.bt=true
ro.device.support.gps=false
ro.device.support.fm=true
ro.device.support.gsensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.cmmb=false
ro.device.support.vt=false
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=MocorDroid2.3.5
ro.build.display.id=TD206B_HTO_H06A_V1.5
ro.build.version.incremental=W12.20_P20_20120926.181054
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=2012.09.26 18:16:25 CST
ro.build.date.utc=1348654585
ro.build.type=user
ro.build.user=jsm
ro.build.host=jsm-desktop
ro.build.tags=test-keys
ro.product.model=H06A
ro.product.brand=HTO
ro.product.name=H06A
ro.product.device=hsdroid
ro.product.board=sp8810ga
ro.ctl_baseband_ver=ctl_kernel_td206b_hto
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=CELLTEL
ro.wifi.channels=
ro.board.platform=sprdbp
ro.build.product=hsdroid
ro.build.description=sprdroid_base-user 2.3.5 MocorDroid2.3.5 W12.20_P20_20120926.181054 test-keys
ro.build.fingerprint=sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P20_20120926.181054:user/test-keys
persist.sys.timezone=Asia/Yekaterinburg
ro.product.carrier=
ro.product.locale.language=ru
ro.product.locale.region=RU
ro.msms.phone_count=2sim
wifi.supplicant_scan_interval=48
android.keylayout.sprd-keypad=/system/usr/keylayout/sprd-keypad.kl
android.keychar.sprd-keypad=/system/usr/keychars/sprd-keypad.kcm
ro.hardware=mtk6515
ro.telephony.default_network=2
ro.sprd.volume_control_icon=1
ro.sf.lcd_density=160
dalvik.vm.heapsize=32m
ro.opengles.version=131072
ro.internalstorage.threshold=95
persist.sys.language=ru
persist.sys.country=RU
ro.com.android.dateformat=yyyy-MM-dd
ro.com.android.dataroaming=true
net.bt.name=Android
net.change=net.tcp.buffersize.edge
ro.calibration=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.revision=0
ro.recvkeys=115,114,116,212
ro.recvkey.up=115
ro.recvkey.down=114
ro.recvkey.enter=116
ro.recvkey.home=212
ro.recvkey.power=116
ro.gpu=mali
net.tcp.buffersize.edge=4093,48000,64000,4096,10240,14336
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
4ae096ee66868ef0541608427b75d756
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
please help meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

Related

[Q] What Does this mean?

Got this error when i try to flash the custom rom "Overcome 10.1 Series v2.1.1"
on my sg tab 10.1
Starting recovery on Tue Jan 8 13:11:29 2019
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v4.0.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /efs ext4 /dev/block/mmcblk0p1 (null)
2 /recovery emmc /dev/block/mmcblk0p2 (null)
3 /boot emmc /dev/block/mmcblk0p3 (null)
4 /system ext4 /dev/block/mmcblk0p4 (null)
5 /cache ext4 /dev/block/mmcblk0p5 (null)
6 /data auto /dev/block/mmcblk0p8 (null)
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_p7100-eng 2.3.4 GINGERBREAD eng.koush.20110614.231606 test-keys
ro.build.version.incremental=eng.koush.20110614.23 1606
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Tue Jun 14 23:16:26 PDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_p7100
ro.product.device=p7100
ro.product.board=p7100
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=p7100
ro.build.description=full_p7100-eng 2.3.4 GINGERBREAD eng.koush.20110614.231606 test-keys
ro.build.fingerprint=Android/full_p7100/p7100:2.3.4/GINGERBREAD/eng.koush.20110614.231606:eng/test-keys
ro.cwm.prefer_tar=true
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=C8F135C17DDFD8E
ro.bootmode=unknown
ro.baseband=P7500XWKG1
ro.carrier=unknown
ro.bootloader=P7500XXKG8
ro.hardware=p3
ro.revision=11
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
W:using /data/media, no /sdcard found.
SD Card mounted...
I:Running script:
I:
ui_print("ROM Manager Version 4.8.0.7");
ui_print("January 8, 2012");
ui_print("Preparing to install ROM...");
assert(backup_rom("/sdcard/clockworkmod/backup/2012-01-08-21.11.17"));
assert(install_zip("/sdcard/001001-P7500_KI1_Restock.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 4.8.0.7
January 8, 2012
Preparing to install ROM...
W:using /data/media, no /sdcard found.
SD Card space free: 19742MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
tar: data/.pcsync_stream: socket ignored
tar: data/.usb_stream: socket ignored
No /sdcard/.android_secure found. Skipping backup of applications on external storage.
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup complete!
-- Installing: /sdcard/001001-P7500_KI1_Restock.zip
Finding update package...
I:Update location: /sdcard/001001-P7500_KI1_Restock.zip
W:using /data/media, no /sdcard found.
Opening update package...
Installing update...
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/001001-P7500_KI1_Restock.zip")
W:using /data/media, no /sdcard found.
Click to expand...
Click to collapse
What should i do?
My tab is already rooted...
thanks in advance!
This is a bit of a stab in the dark, and i doubt this is what the error message about says, but i would recommend flashing a new cwm. So thats a cwm 5.x
adamski123 said:
This is a bit of a stab in the dark, and i doubt this is what the error message about says, but i would recommend flashing a new cwm. So thats a cwm 5.x
Click to expand...
Click to collapse
Nope
As i see you try to install some zip with set of stock files instead of real overcome rom.
Restock zip file which you try to install is not CWM file, its zip archive with set of files, programs and instructions for restocking your tab
Please, read developers guide before installation here: http://www.teamovercome.net/p7500/?page_id=5
and install something like this: Overcome_10.1_Series_v2.2.0_P7500_Full.zip ( if you have 7500 device)
Of course, upgading your CWM is good idea
Sent from my GT-P7500 using xda premium

Clockwork Mod Backup Issues

Hey all,
I rooted my phone yesterday via zedomax's method. Today, I got S-OFF via LazyPanda. I'm trying to use ROM Manager and ClockworkMod Recovery v5.8.3.5 to backup my stock ROM before I try installing any new ROMS. My problem is that the backup doesn't seem to be working.
I get the output:
ClockworkMod Recovery v5.8.3.5
Waiting for SD Card to mount (20s)
SD Card Mounted
Verifying SD Card marker...
ROM Manager Version 5.0.0.8
July 22, 2012
E:unkonw volum for path [/emmc/clockworkmod/backup/2012-07-22-15.49.15]
Can't mount backup path.
/tmp/recover.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I have tried partitioning the SD via ROM Manager (with various sizes) and also ran Fix Permissions and I'm still having this problem.
The recovery.log contains:
Starting recovery on Sun Jul 22 19:49:43 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v5.8.3.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p21 (null) 0
2 /cache ext4 /dev/block/mmcblk0p36 (null) 0
3 /data ext4 /dev/block/mmcblk0p37 (null) 0
4 /misc emmc /dev/block/mmcblk0p23 (null) 0
5 /recovery emmc /dev/block/mmcblk0p22 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 /dev/block/mmcblk1 0
8 /system ext4 /dev/block/mmcblk0p35 (null) 0
9 /devlog ext4 /dev/block/mmcblk0p26 (null) 0
10 /internal_sdcard vfat /dev/block/mmcblk0p38 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=IMM76I
ro.build.display.id=cm_jewel-userdebug 4.0.4 IMM76I eng.koush.20120602.132403 test-keys
ro.build.version.incremental=eng.koush.20120602.132403
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sat Jun 2 13:24:31 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=jewel
ro.product.brand=htc
ro.product.name=cm_jewel
ro.product.device=jewel
ro.product.board=jewel
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8660
ro.build.product=jewel
ro.build.description=cm_jewel-userdebug 4.0.4 IMM76I eng.koush.20120602.132403 test-keys
ro.build.fingerprint=htc/cm_jewel/jewel:4.0.4/IMM76I/eng.koush.20120602.132403:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=jewel
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-jewel-UNOFFICIAL
ro.modversion=9.0.0-RC0-jewel-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT276S404885
ro.bootmode=recovery
ro.baseband=1.02.12.0427
ro.carrier=COMMON
ro.bootloader=1.12.1111
ro.hardware=jet
ro.revision=128
ro.emmc=1
init.svc.choice_fn=stopped
init.svc.adbd=running
init.svc.recovery=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
153f1a2a3286dec89e65b291b371e071
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.8");
ui_print("July 22, 2012");
assert(backup_rom("/emmc/clockworkmod/backup/2012-07-22-15.49.15"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.8
July 22, 2012
E:unknown volume for path [/emmc/clockworkmod/backup/2012-07-22-15.49.15]
Can't mount backup path.
result was NULL, message is: assert failed: backup_rom("/emmc/clockworkmod/backup/2012-07-22-15.49.15")
I would really appreciate any help that anyone can provide me on this. I have tried searching but can't find any solution and similar most posts related are a year or two old. Thank you in advance.
The simple solution is use TWRP recovery. AFAIK, cwm doesn't work properly for the LTE. Just switch over to TWRP and you should be good to go.
Sent from my ELTE using Tapatalk 2
crump84 said:
The simple solution is use TWRP recovery. AFAIK, cwm doesn't work properly for the LTE. Just switch over to TWRP and you should be good to go.
Sent from my ELTE using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much for the info! TWRP seems to have worked for backing up my stock ROM. Great to know!
Yep stay away from that buggy rom manager program and twrp is the recovery of choice for our device.
Sent from my EVO using Tapatalk 2
clockworkmod recovery dont work on the lte.. only twrp!!!!!!:good:

Error in cwm recovery for micromax bolt a27.. Pls help meeeeee

HELLO.
Am new here...so i request your help..advice..i dnt knw where this thread to post.......pls 4give me..
i rooted my micromax bolt A27 by unlock root...by following the thread 'how to root micromax a27 ' here
and i installed cwm recovery by following the thread
http://forum.xda-developers.com/showthread.php?t=2191285
succesfully installed....
BUT FIRST PROBLEM IS....
I cant enter cwm recovery by pressing volume+ && power button
i try to re flash recovery.img by adb folder method 3 or 4 times
it cannot solve my problem
then i erase recovery and flash again....by command erase flash recovery
hell.... it cant solve problem...............NO SUCCESS IT GOES TO FACTORY MODE WHEN PRESS VOLUME+ && POWER BUTTON
A TEMP SOLUTION I FOUND BY USE BOOT INTO RECOVERY MODE BY ROM MANAGER OR MOBILEUNCLE TOOLS....
PLEASE HELP ME A TRUE SOLUTION... TO GET CWM WITHOUT ROM MANNAGER OR MOBILE UNCLE , BRICK BOOT..........NLY BY BOOT KEYS
SECOND PROBLEM
Its the important problem nw i faced.... pls help meee.....................also i attach a report.log file
I got a error when i select 'UPDATE TOOL' in mobileuncle.......
i select 'check start safe flash update .zip(null package)-' - click next- click start test.....
phone reboot into recovery mode....
" sd card marker not fount
error proccesing ROM mannager script
please verify that you are performing the back uo,restore from rom mannager v4.4.0.0 or higher
please open rom mannager to report issue
before i run mobileuncle i install rom mannager and take a backup by boot into recovery by rom mannager...
i got this error by run mobile uncle and select update tool...and click check test.....
then i delete backup...i uninstall rom mannager.... bt cannot solve this problem
the report log file is here
Starting recovery on Wed May 25 16:49:49 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v6.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk0p1 (null) 0
2 /system yaffs2 system (null) 0
3 /cache yaffs2 cache (null) 0
4 /data yaffs2 userdata (null) 0
5 /misc mtd misc (null) 0
6 /boot mtd boot (null) 0
7 /recovery mtd recovery (null) 0
8 /fixnv yaffs2 fixnv (null) 0
9 /runtimenv yaffs2 runtimenv (null) 0
10 /backupfixnv yaffs2 backupfixnv (null) 0
11 /productinfo yaffs2 productinfo (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
persist.msms.phone_count=2
persist.sys.sprd.modemreset=1
ro.device.support.wifi=true
ro.device.support.bt=true
ro.device.support.gps=false
ro.device.support.fm=true
ro.device.support.gsensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.cmmb=false
ro.device.support.vt=false
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=MocorDroid2.3.5
ro.build.display.id=TD206B_HTO_H06A_V1.5
ro.build.version.incremental=W12.20_P20_20120926.181054
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=2012.09.26 18:16:25 CST
ro.build.date.utc=1348654585
ro.build.type=user
ro.build.user=jsm
ro.build.host=jsm-desktop
ro.build.tags=test-keys
ro.product.model=H06A
ro.product.brand=HTO
ro.product.name=H06A
ro.product.device=hsdroid
ro.product.board=sp8810ga
ro.ctl_baseband_ver=ctl_kernel_td206b_hto
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=CELLTEL
ro.wifi.channels=
ro.board.platform=sprdbp
ro.build.product=hsdroid
ro.build.description=sprdroid_base-user 2.3.5 MocorDroid2.3.5 W12.20_P20_20120926.181054 test-keys
ro.build.fingerprint=sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P20_20120926.181054:user/test-keys
persist.sys.timezone=Asia/Yekaterinburg
ro.product.carrier=
ro.product.locale.language=ru
ro.product.locale.region=RU
ro.msms.phone_count=2sim
wifi.supplicant_scan_interval=48
android.keylayout.sprd-keypad=/system/usr/keylayout/sprd-keypad.kl
android.keychar.sprd-keypad=/system/usr/keychars/sprd-keypad.kcm
ro.hardware=mtk6515
ro.telephony.default_network=2
ro.sprd.volume_control_icon=1
ro.sf.lcd_density=160
dalvik.vm.heapsize=32m
ro.opengles.version=131072
ro.internalstorage.threshold=95
persist.sys.language=ru
persist.sys.country=RU
ro.com.android.dateformat=yyyy-MM-dd
ro.com.android.dataroaming=true
net.bt.name=Android
net.change=net.tcp.buffersize.edge
ro.calibration=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.revision=0
ro.recvkeys=115,114,116,212
ro.recvkey.up=115
ro.recvkey.down=114
ro.recvkey.enter=116
ro.recvkey.home=212
ro.recvkey.power=116
ro.gpu=mali
net.tcp.buffersize.edge=4093,48000,64000,4096,10240,14336
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
4ae096ee66868ef0541608427b75d756
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
please help meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
dnt know
Hey dude me too having same problem with same phone... I know getting into recovery partition with hardware combination is little dif as compair to other phones.. i have searched all over google but cant find how to change or view key combination.... fastboot is working with power+vol- but dont know to access recovery by hardware combination.....
Same problem here. As the purpose of the recovery is to be able to restore a nandroid backup when something goes horribly wrong, we need to be able to boot into recovery without the Android GUI.
There is a workaround for this problem, when you can boot into recovery when the phone is turned off.
Connect your Bricked or Turned Off phone to your pc via USB cable. Open ADB. Send this command
Code:
[FONT="Courier New"]adb reboot recovery[/FONT]
And boom! Your phone will boot into CWM recovery. I am still looking into the issue of hardware buttons....and getting rid of the stock recovery altogether. I post soon.
Is "adb reboot recovery" will work when my phone is bricked or switched off? Pls help, I badly need this answer.
Sent from my Micromax A27 using xda app-developers app
for first problem (flashing CWM), use mtk droid tools (video below)

[Q] BEE 9500 - MT6589 Dead ? Need Stock Firmware ROM ? Need urgent help please.

Hi.. (This was first posted in here -> http://forum.xda-developers.com/general/xda-assist/bee-9500-android-phone-mt6589-dead-t2830724 )
So to start off, I'm really desperate right now...
I had a BEE 9500 Phone with an MT6589 board, it was all working fine, until I accidently formatted the system partition, and I have no backup even... I only have a system folder backup, but is that even useful ?
When it was working, this is what MtkDroidTools showed :
i.imgur.com/hNBv1a7.png < I cant post link normally since I'm new.
Now it shows this, and mind you, the phone is stuck in boot loop and it will only show this when I'm mounting USB via CWM Recovery ONLY, It won't detect the phone normally when in boot loop (driver issue maybe) :
i.imgur.com/wY3yPFy.png
IMEI is blank ... everything is wrong... I don't know ...
(I have no idea why, but its showing the android L stuff, I have no idea whats going on...)
And I tried going into fastboot mode and using fastboot.exe to flash a system.img I created but it will keep saying <waiting for device> the whole time...
-----------
I'm wondering if anyone could kinda tell me where I can find the stock firmware for my BEE 9500 if there is any one, please.
Any idea ? I think my phone is dead at this rate....
Reserved, Any idea ? any help ? would it be possible to use the system folder backup I have to restore it ? I would have gladly uploaded the phones stock rom but I had no idea how that works then.
Ok guys, good news maybe, MTKDroidTools made a backup of my bootimage early on, it has my phone's name model and all and its the first one and most accurate, I think its the stock one.
I was able to pack it along with system into a zip file, but when I install it on my phone it gives this error...
Here is the recovery dumped on Sd Card using "Report Error" function in CWM :
Starting recovery on Wed Jan 2 14:38:16 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 27.07.2014 23:05:40
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /emmc vfat /dev/block/mmcblk0p8 (null) 0
8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
9 /sd-ext auto /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6589
ro.revision=0
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Script Asserts: Enabled
No files found.
No files found.
-- Installing: /sdcard/Download/StockRomUpdate.zip
Finding update package...
I:Update location: /sdcard/Download/StockRomUpdate.zip
Opening update package...
Installing update...
about to run program [/sbin/mount] with 3 args
minzip: Error writing 32768 bytes from zip file from 0xbeec7c84: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/app/AccidentBiological.gnz"
about to run program [/sbin/unmount] with 3 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
script result was [Enjoy!]
Enjoy!
Install from sdcard complete.
Click to expand...
Click to collapse
minzip: Error writing 32768 bytes from zip file from 0xbeec7c84: No space left on device ???
there is no other way too, and I can't flash boot.img using MTKDroidTools during recovery mode either.
I think boot installs fine ? using 's recovery flasher from here -> http://forum.xda-developers.com/showthread.php?t=2245724
and clicking "show log" in CWM shows no error at all.
I'm not really sure how??
and why does MTKDroidTools detects my phone as nexus or another phone ? is it because of build.prop ? what determines that ?
And I'm using the following Binary files btw for install ... http://forum.xda-developers.com/showthread.php?t=1721680
Another question, can it be possibly that there is not enough space on the SD Card instead ? where is it extracted ?
Apparently not though, I just cleared my SD Card and I'm getting the same error.

[Q] Can't update CWM : (bad) Installation aborted.

Hi all,
I want to flash CM10.2 for Android 4.3
but, I can't flash any ROM.
when i want to Update CWM, it's impossible.
see the log :
Code:
Starting recovery on Tue Sep 2 12:35:39 2014
framebuffer: fd 4 (480 x 800)
E:unknown volume for path [/system]
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /efs ext4 /dev/block/mmcblk0p1 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p10 (null) 0
7 /preload ext4 /dev/block/mmcblk0p12 (null) 0
8 /emmc vfat /dev/block/mmcblk0p11 (null) 0
9 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
PhilZ Touch 3
CWM Base version: 6.0.1.8
Command: "recovery"
ro.boot.serialno=0009aa09441a2f
ro.sec_debug.enable=0
ro.serialno=0009aa09441a2f
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.debug_level=unknown
ro.emmc_checksum=unknown
ril.dualmode.change=unknown
ro.hardware=smdk4210
ro.revision=14
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp
init.svc.ueventd=running
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
Finding update package...
I:Update location: /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
Opening update package...
E:Can't open /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
(bad)
Installation aborted.
Have you an idea ?
Sorry for my poor english
Check the md5 of the downloaded zip.
Looks like a corrupted one.
Also make sure you copy / paste the zip on your phone correctly.
Sent from my Nexus 5 using Tapatalk 2
corrupted file
From my own experience it normally is a bad/corrupted file that you downloaded. I've waste hours downloading a file through my phone only to fbd out that I couldn't flash it. Check your downloaded program cause this can affect the result of your download files. I use Internet download manager for windows which is a very useful download manger for all your needs. For the android I used ADM or advance download manager but I suggest using idm on PC insyead .
One rule I always do now is check the archive if they work or unzip in your PC if not then it won't work on your phone when flashing

Categories

Resources