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
Related
Starting recovery on Sat Jan 1 00:06:02 2011
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p5 (null)
2 /system ext4 /dev/block/mmcblk0p9 (null)
3 /data ext4 /dev/block/mmcblk0p10 (null)
4 /cache ext4 /dev/block/mmcblk0p7 (null)
5 /sdcard vfat /dev/block/mmcblk0p11 (null)
6 /emmc vfat /dev/block/mmcblk1p1 (null)
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: "recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc210
ro.revision=14
ro.emmc=0
dpm.allowpolicy=1
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.UGKG2
ro.build.version.incremental=UGKG2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=Tue Jul 12 10:19:43 KST 2011
ro.build.date.utc=1310433583
ro.build.type=user
ro.build.user=dh130.yoo
ro.build.host=SEP-48
ro.build.tags=release-keys
ro.product.model=GT-I9100M
ro.product.brand=samsung
ro.product.name=GT-I9100M
ro.product.device=GT-I9100M
ro.product.board=GT-I9100M
ro.product.cpu.abi=armeabi-v7a
ro.build.PDA=I9100MUGKG2
ro.build.hidden_ver=I9100MUGKG2
ro.build.changelist=371789
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=s5pc210
ro.build.product=GT-I9100M
ro.build.description=GT-I9100M-user 2.3.3 GINGERBREAD UGKG2 release-keys
ro.build.fingerprint=samsung/GT-I9100M/GT-I9100M:2.3.3/GINGERBREAD/UGKG2:user/release-keys
ro.camera.sound.forced=1
ro.tether.denied=false
ro.flash.resolution=1080
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
persist.service.usb.setting=0
dev.sfbootcomplete=0
ro.url.legal=
ro.url.legal.android_privacy=
ro.com.google.locationfeatures=1
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=2.3_r4
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
keyguard.no_require_sim=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.opengles.version=131072
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.recovery=running
init.svc.adbd=running
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/AndyX_Rom_v3.1_ICS_4.0.3_XXLP2 (1).zip
Finding update package...
I:Update location: /sdcard/AndyX_Rom_v3.1_ICS_4.0.3_XXLP2 (1).zip
Opening update package...
minzip: Missed a central dir sig (at 0)
E:Can't open /sdcard/AndyX_Rom_v3.1_ICS_4.0.3_XXLP2 (1).zip
(bad)
Installation aborted.
odlin back to stock cf rooted
but try to flash any rom with cwm
get this error
thanks for any help
Sheldon
Based on the error message, my guess would be a damaged zip. Redownload it.
Someone (for a different device) had the same error here http://forum.xda-developers.com/showthread.php?t=1319857 and indicated the file was corrupt while copying between computer and phone.
tried 2 different
tried 2 different custom roms
downloaded on different computers
on internal sd and tried on micro sd card
when back to stock
did cf root again same error
tried kernal just wondering if something wrong
with boot or something else
odlin stock back on never checked anything it didn't say to in guide
no pit file just pda and phone
help bought off ebay wondering if start claim
thanks again
Sheldon
That OP is saying i9100M
ro.product.model=GT-I9100M
Is the firmware you are flashing i9100 M compatible
Its also saying bad zip
.zip
(bad)
Not sure about an EBay claim if its an add on that you have installed not working .
I would personally try .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
tried rebooted cwm
format all but get error on formating /sdcard
tried unmounting /sdcard error
got it format
on download what does custom binary downlaod yes(2 counts)
and Current binary:Custom mean
was on phone first time
thanks again
javaman1966 said:
got it format
on download what does custom binary downlaod yes(2 counts)
and Current binary:Custom mean
was on phone first time
thanks again
Click to expand...
Click to collapse
Means the person or persons who owned the phone before you flashed 2 kernels not signed by Samsung.
Plus that meant that custom rom or root = no Samsung warranty.
Stock rom and reset custom rom counter with usb jig. Warranty back.
jje
Sent from my GT-I9100 using xda premium
rooted my tf201 by unlocking and installing cm9 thru clockwork recovery. I got the touch version of recovery and tried using that to make a backup of my ROM but it didnt work - folder was created but the transformer prime just rebooted. I tried the regular recovery and the same thing happened, below is the error log (thanks):
Starting recovery on Thu Jun 14 02:59:48 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v5.8.3.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /staging ext3 /dev/block/mmcblk0p4 (null) 0
5 /data ext4 /dev/block/mmcblk0p8 (null) 0
6 /boot emmc /dev/block/mmcblk0p10 (null) 0
7 /recovery emmc /dev/block/mmcblk0p9 (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 /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=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IMM76I
ro.build.display.id=cm_tf201-userdebug 4.0.4 IMM76I eng.koush.20120601.133409 test-keys
ro.build.version.incremental=eng.koush.20120601.133409
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Jun 1 13:34:38 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=Transformer Prime TF201
ro.product.brand=asus
ro.product.name=EeePad
ro.product.device=tf201
ro.product.board=cardhu
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=tf201
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.4.2.21-20120323 release-keys
ro.build.fingerprint=asus/US_epad/TF201:4.0.3/IML74K/US_epad-9.4.2.21-20120323:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=tf201
ro.carrier=wifi-only
ro.com.android.dateformat=MM-dd-yyyy
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
persist.tegra.nvmmlite=1
ro.epad.model=TF201
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
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.dataroaming=false
ro.cm.version=9.0.0-RC0-tf201-UNOFFICIAL
ro.modversion=9.0.0-RC0-tf201-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=015d0787be3c180d
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.mischelp=restarting
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
cf32f57db85e48016a5b2e3564f0c9cb
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.7");
ui_print("June 13, 2012");
assert(backup_rom("/sdcard/clockworkmod/backup/cm9_v1.0"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.7
June 13, 2012
I:using /data/media, no /sdcard found.
SD Card space free: 24882MB
Backing up boot image...
Error while backing up boot image!result was NULL, message is: assert failed: backup_rom("/sdcard/clockworkmod/backup/cm9_v1.0")
I:using /data/media, no /sdcard found.
sorry i dont think i put this thread in the right section
What version of CWM are you using? Restore is borked in the latest release.
ROM Manager v5.0.0.7
Current Recovery: ClockworkMod 5.8.3.4
If i flash ClockworkMod 5.5.0.4 would it work, you think?
cassato said:
ROM Manager v5.0.0.7
Current Recovery: ClockworkMod 5.8.3.4
If i flash ClockworkMod 5.5.0.4 would it work, you think?
Click to expand...
Click to collapse
I would give TWRP a shot, it's been working really well so far and seems to be very stable. If you're going to use clockwork maybe try 5.8.3.2 I believe it is, the regular one not the touch version.
cassato said:
ROM Manager v5.0.0.7
Current Recovery: ClockworkMod 5.8.3.4
If i flash ClockworkMod 5.5.0.4 would it work, you think?
Click to expand...
Click to collapse
If you want to stay with CWM, use 5.8.1.8.
CharliesTheMan said:
I would give TWRP a shot, it's been working really well so far and seems to be very stable. If you're going to use clockwork maybe try 5.8.3.2 I believe it is, the regular one not the touch version.
Click to expand...
Click to collapse
TWRP does not seem to have a version for the Asus TF201 - will one of the others work?
What do you mean, there's no version for the TF201?
http://forum.xda-developers.com/showthread.php?t=1615990
pandaball said:
What do you mean, there's no version for the TF201?
http://forum.xda-developers.com/showthread.php?t=1615990
Click to expand...
Click to collapse
thanks, i only looked http://teamw.in/project/twrp and it wasnt on there.
looks like CWM 5.8.2.0 worked, thanks everyone for your help
cassato said:
thanks, i only looked http://teamw.in/project/twrp and it wasnt on there.
looks like CWM 5.8.2.0 worked, thanks everyone for your help
Click to expand...
Click to collapse
It was filed under TWRP 2.1, not the original TWRP.
http://teamw.in/project/twrp2/93
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:
Alright so I'm starting out by saying I'm relativity new to this. So I'm in the dark on this issue.
Also If I posted this in the wrong section of the forum, please let me know so I don't do it again
The issue is that Whenever I try to back-up my ROM through ROM Manager it gives me some error
it boots into Clockworkmod and it gives me this
ClockworkMod Recovery v5.8.3.5
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
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.
Click to expand...
Click to collapse
It says to check the log file
Now before anything, I already uninstalled ROM Manager, reinstalled, reflashed Clockworkmod, and confirmed that everything is up to date.
Can anyone shed some light on this?
here's my LOG file:
Starting recovery on Tue Nov 13 18:08:31 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=
ro.url.legal.android_privacy=
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=HT25YS403492
ro.bootmode=recovery
ro.baseband=1.02.12.0427
ro.carrier=COMMON
ro.bootloader=1.12.0000
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...
SD Card marker not found...
6a71c31c436f8231e32c8de389c24e24
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.
Click to expand...
Click to collapse
In case you ask (doubt you will) I erased the privacy and legal links in the LOG file due to the site blocking me from posting since I'm new.
That's because clockwork has issues with the EVO LTE.
install twrp (team win recovery project). Search on google or xda for download. Also, don't use Rom manager anymore, it is pretty much dead. Use goo manager.
Or download goo manager from market and install twrp as recovery. U will lose any backups u did on cwm, but they won't work anyways.
Sent from my EVO using xda app-developers app
Log70 said:
Alright so I'm starting out by saying I'm relativity new to this. So I'm in the dark on this issue.
Also If I posted this in the wrong section of the forum, please let me know so I don't do it again
The issue is that Whenever I try to back-up my ROM through ROM Manager it gives me some error
it boots into Clockworkmod and it gives me this
It says to check the log file
Now before anything, I already uninstalled ROM Manager, reinstalled, reflashed Clockworkmod, and confirmed that everything is up to date.
Can anyone shed some light on this?
here's my LOG file:
In case you ask (doubt you will) I erased the privacy and legal links in the LOG file due to the site blocking me from posting since I'm new.
Click to expand...
Click to collapse
bro DO NOT USE clockwork recovery on this phone.. it ***ks up ya misc partition.. flash teamwin recovery.. aka twrp.. its the only recovery that works on the LTE at this moment..
evo401 said:
bro DO NOT USE clockwork recovery on this phone.. it ***ks up ya misc partition.. flash teamwin recovery.. aka twrp.. its the only recovery that works on the LTE at this moment..
Click to expand...
Click to collapse
^^^^^ he said
bigdaddy619 said:
^^^^^ he said
Click to expand...
Click to collapse
Or what I said first? Why am I always invisible on here?
Sent from my EVO using xda app-developers app
Anthonicia said:
Or what I said first? Why am I always invisible on here?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
He said first^^^^^^^ My bad
Didn't realize. A friend recommended clockwork since he had used it on his original EVO 4G.
I already flashed the new recovery and wiped all trace of clockwork and rom manager.
Thanks for the help guys. If you ha e anything else to add then please do.
Sent from my EVO using xda premium
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.