Upgrading HTC Hero CM7.0.3-Heroc to Elelinux 3.* - General Questions and Answers

Hey guys,
I'm having an issue utilizing ROM Manager to upgrade my HTC Hero from CM7 to Elelinux 3.x*. If anybody else has had this issue or may be able to help me please don't hesitate . Thanks!
Code:
Starting recovery on Sat Aug 20 18:34:28 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v2.5.0.7
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=ECLAIR
ro.build.display.id=koush_heroc-eng 2.1-update1 ECLAIR eng.koush.20110205.145452 test-keys
ro.build.version.incremental=eng.koush.20110205.145452
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Sat Feb 5 14:56:34 PST 2011
ro.build.date.utc=1296946594
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=Hero CDMA (US)
ro.product.brand=generic
ro.product.name=koush_heroc
ro.product.device=heroc
ro.product.board=heroc
ro.product.cpu.abi=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=heroc
ro.build.description=koush_heroc-eng 2.1-update1 ECLAIR eng.koush.20110205.145452 test-keys
ro.build.fingerprint=generic/koush_heroc/heroc/heroc:2.1-update1/ECLAIR/eng.koush.20110205.145452:eng/test-keys
rild.libpath=/system/lib/libhtc_ril.so
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=160
ro.telephony.default_network=0
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT067HF00786
ro.bootmode=recovery
ro.baseband=2.42.01.04.27
ro.carrier=COMMON
ro.bootloader=1.47.0000
ro.hardware=heroc
ro.revision=2
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...
I:Running script:
I:
print "ROM Manager Version 4.2.0.2"
print "Preparing to install ROM..."
run_program /cache/dowipedalvikcache.sh
install_zip SDCARD:/Elelinux-7.1.0-RC1-Hero-v3.2.zip
Parsed /tmp/extendedcommand
calling command print
ROM Manager Version 4.2.0.2
calling command print
Preparing to install ROM...
calling command run_program
mount: mounting /dev/block/mtdblock4 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
calling command install_zip
-- Installing: SDCARD:/Elelinux-7.1.0-RC1-Hero-v3.2.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:/Elelinux-7.1.0-RC1-Hero-v3.2.zip
Opening update package...
I:Update file path: /sdcard/Elelinux-7.1.0-RC1-Hero-v3.2.zip
Installing update...
I:Trying update-binary.
================================script aborted: assert failed: getprop("ro.product.device") == "hero" || getprop("ro.build.product") == "hero" || getprop("ro.product.board") == "hero"
Welcome to
Elelinux-7.1.0-RC1-Hero-v3.2!
================================
assert failed: getprop("ro.product.device") == "hero" || getprop("ro.build.product") == "hero" || getprop("ro.product.board") == "hero"
E:Error in /sdcard/Elelinux-7.1.0-RC1-Hero-v3.2.zip
(Status 7)
Installation aborted.
Failure at line 4:
install_zip SDCARD:/Elelinux-7.1.0-RC1-Hero-v3.2.zip
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I:Set boot command ""
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
E:Can't mount /dev/block/mmcblk0p2
(File exists)
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.

Nobody knows what's going on?

Related

[Q] Can't Update Moto Xoom Verizon 3g from 3.1 to 3.2

I have had the xoom Verizon 3g for the last 3 months and rooted + unlocked long ago - applied 3.1 with no problem; now that i received from Xoom to update to 3.2 (Verizon pushed it OFC), every time i click update it restarts and ur usual Android with Exclamation Mark is there. and when i try to update MANUALLY i get this (Basically check the LAST part in BOLD)
Starting recovery on Fri Aug 12 22:17:12 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
2 /system ext4 /dev/block/mmcblk1p8 (null)
3 /cache ext4 /dev/block/mmcblk1p9 (null)
4 /data ext4 /dev/block/mmcblk1p10 (null)
5 /misc emmc /dev/block/mmcblk1p3 (null)
6 /boot emmc /dev/block/mmcblk1p7 (null)
7 /recovery emmc /dev/block/mmcblk1p6 (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: "/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_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.version.incremental=eng.chris.20110610.115222
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Fri Jun 10 11:52:40 NZST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=chris
ro.build.host=upsilon
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_stingray
ro.product.device=stingray
ro.product.board=stingray
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=stingray
ro.build.description=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.fingerprint=Android/full_stingray/stingray:2.3.4/GINGERBREAD/eng.chris.20110610.115222:eng/test-keys
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=02885045434042d7
ro.bootmode=unknown
ro.baseband=N_02.0F.00R
ro.carrier=unknown
ro.bootloader=1045
ro.hardware=stingray
ro.revision=33536
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)
Opening update package...
Installing update...
installing moto updater extensions
script aborted:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
TheKicKer69 said:
I have had the xoom Verizon 3g for the last 3 months and rooted + unlocked long ago - applied 3.1 with no problem; now that i received from Xoom to update to 3.2 (Verizon pushed it OFC), every time i click update it restarts and ur usual Android with Exclamation Mark is there. and when i try to update MANUALLY i get this (Basically check the LAST part in BOLD)
Starting recovery on Fri Aug 12 22:17:12 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
2 /system ext4 /dev/block/mmcblk1p8 (null)
3 /cache ext4 /dev/block/mmcblk1p9 (null)
4 /data ext4 /dev/block/mmcblk1p10 (null)
5 /misc emmc /dev/block/mmcblk1p3 (null)
6 /boot emmc /dev/block/mmcblk1p7 (null)
7 /recovery emmc /dev/block/mmcblk1p6 (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: "/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_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.version.incremental=eng.chris.20110610.115222
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Fri Jun 10 11:52:40 NZST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=chris
ro.build.host=upsilon
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_stingray
ro.product.device=stingray
ro.product.board=stingray
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=stingray
ro.build.description=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.fingerprint=Android/full_stingray/stingray:2.3.4/GINGERBREAD/eng.chris.20110610.115222:eng/test-keys
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=02885045434042d7
ro.bootmode=unknown
ro.baseband=N_02.0F.00R
ro.carrier=unknown
ro.bootloader=1045
ro.hardware=stingray
ro.revision=33536
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)
Opening update package...
Installing update...
installing moto updater extensions
script aborted:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
If you are rooted you can't update OTA.There is an update thread in Development to update rooted 3.1 to 3.2 rooted stock. I think its by stachre. Or you could just flash the Hammerhead Rom and get the update to 3.2, preserve your root and enjoy the new Rom-works with 3G too.
Thanks for the response
I have a similar challenge
Verizon 3g Motorola Xoom
Android version 3.0.1
Kernel version 2.6.36.3Tiamat_Xoom-v1.3.0-g5019ece-dirty [email protected]_PC #3
Build number HR166
Device has been re-configured for another 3g network and is working well, except that I am unable to upgrade. I like to get my tablet to version 3.2 and later to 4.0.3 and without losing data
Will “flash the Hammerhead Rom and get the update to 3.2” option work for me? If yes, please help with instructions and required software links

Cannt install Teamhacksung build 15 or 16

Hey guys,
I have been reading and researching but cannot find the correct answer. I have installed teamhacksung up to build 14 but cannot install anything later. I have reverted all the way back to stock, and tried everything else that post have recommended. Only thing else that I can think of is that I had install a kernal for USB hosting but that never did work. Seams that was installed around the same time as Build 14. Could that kernal have something to do with the problem?
this is the failed report that i get during fail to install
assert failed: getprop(“ro.product.device”) == “galaxys” getprop(“ro.build.product”) ==”galaxys”
Are you on stock gingerbread 2.3.5 or froyo?
Sent from my SGH-I897 using XDA App
Using build 14 right now
Have been using teamhacksung since build 10
always updated with no problem
will not let me install build 15 or 16
re-downloaded the file several times still no go
reverted back to enclair then froyo and gingerbread
build 14 reinstalls no problem but not 15 or 16
could it be the kernal i installed for the usb host mode?
thanks for the reply
It could be the kernel. Try flashing build 16 using the stock kernel that came with build 14.
First, reflash build 14 to get the stock kernel. You don't have to go all the way back to eclair. Just wipe data, wipe cache, wipe dalvik (found under Advanced in recovery) Then reflash build 14.
After you do that, let it boot normally. Wait till it does, then do another clean flash from recovery: Wipe data, wipe cache partition, and wipe dalvik cache (found under advanced in recovery). Flash build 16.
I flashed build 16 from build 14 just fine.
Sent from my SGH-I897 using XDA App
No luck. Even done the whole procedure 2 times with the same error. Can flash build 14 no problem.
What else could I try?
Aww darn. I can't think of other solutions, but some people might be able to help somehow. You can also try searching the captivate forum for this specific solution as well. Sorry it didn't work out for you though :/
Sent from my SGH-I897 using XDA App
it's wrong ROM
I think u got GalaxyS version of ROM. Or script is not cleaned from Galaxy S check. So.. Try another true Captivate ICS ROM!
Flash this kernel reverter/kernel cleaner
Reboot and flash the THS CM9 ROM
This is from the FAQ from Teamhacksung Q&A http://forum.xda-developers.com/showthread.php?t=1367586
tried this procedure twice still no luck build 14 works
Flash this kernel reverter/kernel cleaner
Reboot and flash the THS CM9 ROM
Starting recovery on Sun Feb 19 03:35:00 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /recovery mtd recovery (null) 0
2 /boot mtd boot (null) 0
3 /radio mtd radio (null) 0
4 /system yaffs2 system (null) 0
5 /cache yaffs2 cache (null) 0
6 /datadata yaffs2 datadata (null) 0
7 /sdcard vfat /dev/block/mmcblk0p1 (null) 0
8 /data ext4 /dev/block/mmcblk0p2 (null) 0
9 /emmc vfat /dev/block/mmcblk1p1 (null) 0
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=mass_storage,adb
ro.build.id=GINGERBREAD
ro.build.display.id=IML74K
ro.build.version.incremental=eng.pawitp.20120127.170611
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jan 27 17:10:24 ICT 2012
ro.build.date.utc=1327659024
ro.build.type=userdebug
ro.build.user=pawitp
ro.build.host=pawitpmbp.local
ro.build.tags=test-keys
ro.product.model=SGH-I897
ro.product.brand=samsung
ro.product.name=SGH-I897
ro.product.device=SGH-I897
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=SGH-I897
ro.build.description=SGH-I897-user 2.3.5 GINGERBREAD UCKK4 release-keys
ro.build.fingerprint=samsung/SGH-I897/SGH-I897:2.3.5/GINGERBREAD/UCKK4:user/release-keys
ro.build.characteristics=default
ro.cm.device=captivatemtd
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=20
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.rommanager.developerid=cyanogenmod
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.cm.version=9.0.0-RC0-Captivate-KANG
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.tcp.buffersize.gprs
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=3132065E2EC300EC
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=aries
ro.revision=48
ro.emmc=0
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
net.tcp.buffersize.default=4096,87380,110208,4096,16384,110208
net.tcp.buffersize.wifi=4095,87380,110208,4096,16384,110208
net.tcp.buffersize.umts=4094,87380,110208,4096,16384,110208
net.tcp.buffersize.edge=4093,26280,35040,4096,16384,35040
net.tcp.buffersize.gprs=4092,8760,11680,4096,8760,11680
init.svc.recovery=running
sys.usb.config=mass_storage,adb
init.svc.adbd=running
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/Download/update-cm-9.0.0-RC0-GalaxyS-KANG-BUILD16-signed.zip
Finding update package...
I:Update location: /sdcard/Download/update-cm-9.0.0-RC0-GalaxyS-KANG-BUILD16-signed.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" ||
getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" ||
getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" ||
getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T"
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" || getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" || getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" || getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T"
E:Error in /sdcard/Download/update-cm-9.0.0-RC0-GalaxyS-KANG-BUILD16-signed.zip
(Status 7)
Installation aborted.
What kernel did you flash?
[KERNEL][ICS-CM9] USB Host mode (OTG) driver for Captivate [BUILD 5]
http://forum.xda-developers.com/showthread.php?p=21542092
Heritagecycles said:
[KERNEL][ICS-CM9] USB Host mode (OTG) driver for Captivate [BUILD 5]
http://forum.xda-developers.com/showthread.php?p=21542092
Click to expand...
Click to collapse
I haven't got any experience with that guy, but I'd say that it's incompatible with CM9 b15/16(obviously). If it were me, there might be 2 things I'd look into. 1 might be take a look at flashing a stock kernel for the build you are on. Or look into flashing Glitch. Now I don't know, how what you have might react with Glitch, so I'd do a bit of research before flashing just so you don't brick. If all else fails, I'd flash back to stock/master clear and start over(Back up all of your stuff, MC erases everything)
So..... Even though I reverted/cleaned, Does that mean the kernel I flashed is probably still there? I have been reading a lot but don't fully understand kernels. If i go all the way back to enclair and master clear, will that take care of it for sure? If so that may be the safest for me.
Heritagecycles said:
So..... Even though I reverted/cleaned, Does that mean the kernel I flashed is probably still there? I have been reading a lot but don't fully understand kernels. If i go all the way back to enclair and master clear, will that take care of it for sure? If so that may be the safest for me.
Click to expand...
Click to collapse
Not knowing what drivers are exactly installed along with that kernel, I would say that something is being leftover. I'd be inclined to FTS/MC, myself. That should clean the slate for you
Have you tried a speedmod kerenel through odin before flashing the ROM?
That's what I did and I'm at build 16
Ok I am going to master clear then flash back to enclair
I will let you know the results.
Thanks I appreciate your help.
Unbelievable
Ran odin3 reverted back to enclair
Performed a Master Clear
Installed CM7
Tired to install THS build 16 SAME results DOES NOT LOAD
assert failed:
reloaded THS build 14 no problem
flashed kernel reverter/kernel cleaner rebooted
still will not load THS build 15 or 16
What Next??
Heritagecycles said:
Unbelievable
Ran odin3 reverted back to enclair
Performed a Master Clear
Installed CM7
Tired to install THS build 16 SAME results DOES NOT LOAD
assert failed:
reloaded THS build 14 no problem
flashed kernel reverter/kernel cleaner rebooted
still will not load THS build 15 or 16
What Next??
Click to expand...
Click to collapse
Maybe you have a bad download?
I would first redownload 15 or 16 to make sure they werent bad downloads. Next question I have when you say you were able to reinstall 14 did you just restore a nandroid backup to get back to 14? If you made that nandroid while having that usb host kernel then your back on it with the kernel. Or are you saying that after you master cleared you are able to install a FRESH build 14? If it is the second choice then it HAS TO BE bad downloads. If it is the first choice then you should be able to flash the kernel reverter over it to get rid of the get.prop issue. Then try to let it boot, IT WILL FAIL and you will be at the bootscreen, then three finger back to recovery after it has been at on the boot animation for a minute or so, once back in recovery flash build 15 or 16, let it finish BUT DO NOT reboot system now, choose zip and then REFLASH build 15/16 a second time. Then reboot. The reboot WILL take a extra long time maybe 5-10 minutes since everything was master cleared and or caches thoroughly cleaned. But it WILL come up.
Usually what happens is that on the FIRST time you install CM7 or even CM9 the first flash will reinstall the new kernel and also possibly put the correct clockworkmod recovery in place, the second flash will finish up with everything a second time for good measure.
Also make sure you have the build 15/16 on the knternal sdcard and not the internal (I know you can flasb sometimes from the removeable sdcard as I have in the past but for safe measure). If that doesnt work put build 15/16 on the internal sdcard AND the external sdcard and try to flash from either until it works.
Last but not least i will try it out for you right now also and get back with ya. I am already on build 16 but have the newest USB OTG kernel working correctly now on my cappy. So i will flash my kernel reverter and see if it works going from the usb host kernel. Also in case it makes a difference i can upload build #16 kernel reverter in case it is based off an older build( in case that is causing an issue). I have also seen people get the "get.prop" error when they have a different version of clockworkmod recovery, have you changed your clockworkmod recovery lately? Maybe to the touch recovery? Or older version? I will let you know how it goes for me flashing back to stock kernel in a few.
Sent From My KickAss ATT SGS2 SPORTING CM7

[Q] HELP NEEDED galaxy s2 (i9100g),cannot mount emmc

when i try to install a rom with cwm,installation is aborted , and when i go to mount and storage menu,and try to mount emmc storage then it says :error cant mount emmc,the log file of error during flashing a rom was :
Starting recovery on Sat Apr 21 16:28:46 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.3
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p5 (null)
2 /recovery emmc /dev/block/mmcblk0p6 (null)
3 /efs ext4 /dev/block/mmcblk0p1 (null)
4 /cache ext4 /dev/block/mmcblk0p7 (null)
5 /system ext4 /dev/block/mmcblk0p9 (null)
6 /data ext4 /dev/block/mmcblk0p10 (null)
7 /sdcard vfat /dev/block/mmcblk0p11 (null)
8 /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: "/sbin/recovery"
ro.secure=0NAL_DEFAULT_PROPERTIES
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=cff1930417fc1ae
ro.bootmode=reboot_recovery
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=t1
ro.revision=7
ro.emmc=0
dpm.allowpolicy=1
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.build.id=GINGERBREAD
ro.build.display.id=juffo.v2.DZKJ2
ro.build.version.incremental=DZKJ2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Fri Oct 21 19:47:33 KST 2011
ro.build.date.utc=1319194053
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-30
ro.build.tags=release-keys
ro.product.model=GT-I9100G
ro.product.brand=samsung
ro.product.name=GT-I9100G
ro.product.device=GT-I9100G
ro.product.board=omap4sdp
ro.product.cpu.abi=armeabi-v7a
ro.build.PDA=I9100GDZKJ2
ro.build.hidden_ver=I9100GDZKJ2
ro.build.changelist=679669
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=GT-I9100G
ro.build.description=GT-I9100G-user 2.3.6 GINGERBREAD DZKJ2 release-keys
ro.build.fingerprint=samsung/GT-I9100G/GT-I9100G:2.3.6/GINGERBREAD/DZKJ2:user/release-keys
ro.tether.denied=false
ro.flash.resolution=1080
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=250
dalvik.vm.heapsize=64m
persist.service.usb.setting=0
com.ti.omap_enhancement=true
media.camerahal.test-esd1=false
media.camerahal.test-esd2=false
media.overlay.cloneStatic=false
media.overlay.cloneDynamic=false
persist.sys.HDMICableConnected=no
persist.sys.GfxRotation=0
opencore.asmd=1
wifi.interface=tiwlan0
debug.video.rotateoverlay=0
omap.audio.mic.main=AMic0
omap.audio.mic.sub=AMic1
omap.audio.power=PingPong
ro.com.google.locationfeatures=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r7
media.stagefright.enable-player=false
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=false
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
ro.com.google.clientidbase=android-samsung
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
tv.hdmi.uicloning.enable=true
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
init.svc.pvrsrvinit=stopped
init.svc.geomagneticd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
-- Installing: /emmc/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /emmc/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
Script Asserts: Enabled
-- Installing: /emmc/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /emmc/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
-- Installing: /sdcard/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /sdcard/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
also i had wiped cache partition by mistake , i am new to xda and flashing roms,so i am a bit inexperienced any help would appreciated
Format emmc from inside cwm. Copy roms u wish to install to external SD card and install from there. Never install from internal memory
Emmc
Ok will try and reply thanks for help though
not able to install?!!
Still instalation is aborted but i noticed that when formated emmc it formated my external sd not internal memory ! Which could be the problem but still i dont know wha[YOUTUBE][/YOUTt to do to fix it it is giving same error during flashing
same problem !!!
I am having the same problem i cant flash a rom and stuck with incompatable ics theme help plzz anyone
Dragon Hunter @666 said:
Still instalation is aborted but i noticed that when formated emmc it formated my external sd not internal memory ! Which could be the problem but still i dont know wha[YOUTUBE][/YOUTt to do to fix it it is giving same error during flashing
Click to expand...
Click to collapse
this is the solution for your device: http://forum.xda-developers.com/gal...-pit-files-creating-larger-partition-t2552738

cm9.1-20121021-nightly-coconut installation error

Hi again. I have tried to install cm9.1-20121021-nightly-coconut but I get this error:
Code:
Data wipe complete.
-- Wiping cache...
Formatting /cache...
mtd: not erasing bad block at 0x03000000
Cache wipe complete.
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
Battery Stats wiped.
-- Installing: /sdcard/cm-9.1.0-coconut/cm-9-20121021-NIGHTLY-coconut.zip
Finding update package...
I:Update location: /sdcard/cm-9.1.0-coconut/cm-9-20121021-NIGHTLY-coconut.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "WT19a" || getprop("ro.build.product") == "WT19a" ||
getprop("ro.product.device") == "WT19i" || getprop("ro.build.product") == "WT19i" ||
getprop("ro.product.device") == "coconut" || getprop("ro.build.product") == "coconut"
assert failed: getprop("ro.product.device") == "WT19a" || getprop("ro.build.product") == "WT19a" || getprop("ro.product.device") == "WT19i" || getprop("ro.build.product") == "WT19i" || getprop("ro.product.device") == "coconut" || getprop("ro.build.product") == "coconut"
E:Error in /sdcard/cm-9.1.0-coconut/cm-9-20121021-NIGHTLY-coconut.zip
(Status 7)
Installation aborted.
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
My device is a Wt19i Sony ericsson live with walkman.
What I am doing wrong?
I love cyanogenmod
After some attempts I managed to install the cm9.1-20121021-nightly-coconut and I am so excited. Finaly we have cyanogenmod update via OTA, I think. There is a "cyanogenmod update" option.
About the installation
mangelasakis said:
After some attempts I managed to install the cm9.1-20121021-nightly-coconut and I am so excited. Finaly we have cyanogenmod update via OTA, I think. There is a "cyanogenmod update" option.
Click to expand...
Click to collapse
Have you unlock the bootloared already? because when i started in this kind of things i see that message over and over again and it's because you don't have unlock the bootloader

Tf700 blocked in 4.4.20

Hi guys,
i'm french, so sorry for my english!
I will try to explain what big problem i have with my tf700,
I was root with Bootloader LOCKED, and when i received last OTA update (4.4.23) I had a droid green belly open with an exclamation point above!
This is what i've got with the last_log:
Starting recovery on Mon Dec 10 19:22:26 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
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 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging emmc /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
10 /cra emmc /dev/block/mmcblk0p7 (null) 0
I:Got arguments from /cache/recovery/command
Command: "/sbin/recovery" "--update_package=/cache/dlpkgfile"
ro.boot.serialno=015d2a508a4c280b
ro.boot.commchip_id=0
ro.boot.productid=0x04
ro.boot.carrier=wifi-only
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
ro.build.id=JRO03C
ro.build.display.id=JRO03C.WW_epad-10.4.4.20-20121026
ro.build.version.incremental=WW_epad-10.4.4.20-20121026
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Oct 26 17:49:57 CST 2012
ro.build.date.utc=1351244997
ro.build.type=user
ro.build.user=android
ro.build.host=Makemake
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
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=EeePad
ro.build.description=WW_epad-user 4.1.1 JRO03C WW_epad-10.4.4.20-20121026 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.4.20-20121026:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
webkit.canvas.ganesh=disable
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.62
gps.version.driver=V7.9.11
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.33
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r2
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
init.svc.ueventd=running
ro.serialno=C7OKAS091097
ro.boot_reason=rebooting
ro.epad.model_id=04
ro.epad.model=TF700T
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.sys.NV_STEREOCTRL=0
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=0
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=16
persist.sys.fw.camera.status=1
persist.sys.language=fr
persist.sys.country=FR
persist.sys.localevar=
persist.sys.Nvidia.didim=0
persist.sys.timezone=Europe/Brussels
persist.sys.NV_STEREOAPP=0
init.svc.recovery=running
init.svc.adbd=running
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13573093
Verifying current system...
file "/system/app/Browser.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
assert failed: apply_patch_check("/system/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Done.
and next i would try to downgrade in ICS maj and again I had a droid green belly open with an exclamation point above!
I am helpless!
Just give me some help please! :/
BinaryLover said:
script aborted: assert failed: apply_patch_check("/system/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
Click to expand...
Click to collapse
Did you somehow modify your Browser.apk?
_that said:
Did you somehow modify your Browser.apk?
Click to expand...
Click to collapse
no i did not modify my browser.apk
if i instal a new original apk of browser.apk do you think this will affect my problem?
BinaryLover said:
no i did not modify my browser.apk
if i instal a new original apk of browser.apk do you think this will affect my problem?
Click to expand...
Click to collapse
Yes, if you restore the original Browser.apk from 10.4.4.20 you will definitely either get a different error message for another file (you already know what to do then), or the update will go through.
_that said:
Yes, if you restore the original Browser.apk from 10.4.4.20 you will definitely either get a different error message for another file (you already know what to do then), or the update will go through.
Click to expand...
Click to collapse
ok, thank you , but where can i find the original Browser.apk from 10.4.4.20 ?
If you have this, can you upload this? :/
BinaryLover said:
ok, thank you , but where can i find the original Browser.apk from 10.4.4.20 ?
If you have this, can you upload this? :/
Click to expand...
Click to collapse
If you have some Linux knowledge, you can do the following:
- download the full 10.4.4.20 firmware from the firmware thread
- unzip twice
- get blobtools from https://github.com/AndroidRoot/BlobTools and compile
- run blobunpack on the blob
- mount -o loop blob.APP /mnt/some/dir
- copy whatever you need from the mounted directory.
If you only need Browser.apk, download this and unzip:
View attachment Browser.zip
Thank you so much but i need to install this apk or replace this in folder?
I try to install and i can't replace application system! And if i try to copy in folder "/system/app/Browser.apk" i can't replace apk.
How can i do this? :/
BinaryLover said:
Thank you so much but i need to install this apk or replace this in folder?
I try to install and i can't replace application system! And if i try to copy in folder "/system/app/Browser.apk" i can't replace apk.
How can i do this? :/
Click to expand...
Click to collapse
You cannot install this apk (it's a system app and also missing the odex file), you need to replace the existing file. To do that, become root and remount the system partition writable - either with your preferred root file manager, or with the command "mount -o remount,rw /system".
Thnak you i success to remplace apk
and now when i try to downgrade, bug... with droid again
last_log:
Starting recovery on Fri Dec 28 18:42:59 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
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 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging emmc /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
10 /cra emmc /dev/block/mmcblk0p7 (null) 0
I:Boot command: launcher-boot-recovery
I:Got arguments from boot message
Command: "recovery" "--update_zip=/sdcard/ASUS_BUNDLE.zip"
ro.boot.serialno=015d2a508a4c280b
ro.boot.commchip_id=0
ro.boot.productid=0x04
ro.boot.carrier=wifi-only
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=JRO03C
ro.build.display.id=JRO03C.WW_epad-10.4.4.20-20121026
ro.build.version.incremental=WW_epad-10.4.4.20-20121026
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Oct 26 17:49:57 CST 2012
ro.build.date.utc=1351244997
ro.build.type=user
ro.build.user=android
ro.build.host=Makemake
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
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=EeePad
ro.build.description=WW_epad-user 4.1.1 JRO03C WW_epad-10.4.4.20-20121026 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.4.20-20121026:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
webkit.canvas.ganesh=disable
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.62
gps.version.driver=V7.9.11
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.33
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r2
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
init.svc.ueventd=running
ro.serialno=C7OKAS091097
ro.boot_reason=rebooting
ro.epad.model_id=04
ro.epad.model=TF700T
persist.sys.NV_STEREOCTRL=0
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=0
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=16
persist.sys.language=fr
persist.sys.country=FR
persist.sys.localevar=
init.svc.recovery=running
init.svc.adbd=running
I:Enable RSA key verification.
Finding update package...
I:Update location: /sdcard/ASUS_BUNDLE.zip
Opening update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installation aborted.
I:result_code: 80000002
Check and format /storage to vfat if needed...
Done.
BinaryLover said:
and now when i try to downgrade, bug... with droid again
Click to expand...
Click to collapse
I thought you wanted to upgrade, not downgrade? The Browser.apk was intended to enable upgrading to 10.4.4.23 using the dlgpkgfile that should still be in your /cache directory.
BinaryLover said:
I:Got arguments from boot message
Command: "recovery" "--update_zip=/sdcard/ASUS_BUNDLE.zip"
Click to expand...
Click to collapse
Looks like the recovery is looking for this file and doesn't find it. How did you start the recovery, and what are you actually trying to do?
_that said:
I thought you wanted to upgrade, not downgrade? The Browser.apk was intended to enable upgrading to 10.4.4.23 using the dlgpkgfile that should still be in your /cache directory.
Looks like the recovery is looking for this file and doesn't find it. How did you start the recovery, and what are you actually trying to do?
Click to expand...
Click to collapse
i want to be in 10.4.4.23 root.
ok now i tryed to upgrade with dlpkgfile to 4.4.23 and.. droid belly open with an exclamation point above!
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13573093
Verifying current system...
file "/system/lib/libwebrtc_audio_preprocessing.so" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Done.
Yes it's not the Browser.apk who make bug! we move forward!!
BinaryLover said:
script aborted: assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
Click to expand...
Click to collapse
OK. You know the drill ... replace your file with the one in the attached zip: View attachment libwebrtc_audio_preprocessing.zip
This is the 5th last file that is checked by the dlpkgfile, so in the worst case we must do it with 4 more files.
_that said:
OK. You know the drill ... replace your file with the one in the attached zip: View attachment 1598826
This is the 5th last file that is checked by the dlpkgfile, so in the worst case we must do it with 4 more files.
Click to expand...
Click to collapse
Ho God you are the best!!!
It's work!!! I'm in 4.4.23!! Thank you very much!!
I ask myself the question why were corrupted apk!But now it's work!!!
Bravo tu m'as bien aidé pour mon problème!, je te remercie!

Categories

Resources