Can't get ICS to install.
I hadn't used my Thinkpad Tablet in a few months, so I just learned that ICS had been released for this device. I first set Voodoo Rootkeeper to preserve root, then manually checked for System Updates and it found that 0089 had never been applied. It applied that successfully. After installed, I verified that root was preserved, then tried several times to do the same to get the ICS update (A400_03_0069_0130_US), but it always failed, so I put the update ZIP and XML files in the root of a FAT32 SD Card and then booted into recovery. After booting into recovery, I first wiped the cache, then wiped data/factory reset, then tried to "apply update form external storage." It saw A400_03_0069_0130_US.zip and I ran it. This is the error that it returned.
-- Install /sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0065_0128_US:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0130_US:user/release-keys"
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I read in another thread that this error arises when a previous update did not complete correctly. My system about shows ThinkPadTablet_A310_02_0039_0089_US
I read in another thread that if you edit META-INF/com/google/android/updater-script in ThinkPadTablet_A400_03_0069_0130_US.zip by removing this line:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_ROW:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0121_ROW:user/release-keys");
that the update won't perform the check that is tripping me up. I tried that, but then it failed when a critical file was not the size that the updater expected.
I am rooted, but I'm turning off root (using RootKeeper) before trying to install the updated. I don't remember ever installing anything else (like CWM or CMR). I don't understand why my update is failing.
Any suggestions?
The contents of my currently installed /System/Build.Prop file are in the code box below. This was copied straight off of my TpT and pasted here, so it's the real deal, character for character. Does anyone notice any errors in this file? Particularly anything that would make the install routine fail with this error:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0065_0128_US:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0130_US:user/release-keys"
E:Error in /tmp/sideload/package.zip
Click to expand...
Click to collapse
Notice how my build.prop file has these lines:
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Indigo
The first line is a comment ("# ro.build.product is obsolete; use ro.product.device"), but the line immediately after uses ro.build.product anyway ("ro.build.product=Indigo"). WTF?
Also notice:
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=ventana-user 3.1 ThinkPadTablet_A310_02 0039_0089_US release-keys
ro.build.fingerprint=Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_US:user/release-keys
Is my build.prop file screwed up? Is that why my update is failing?
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ThinkPadTablet_A310_02
ro.build.display.id=ThinkPadTablet_A310_02_0039_0089_US
ro.build.version.incremental=0039_0089_US
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Tue Feb 14 18:39:35 CST 2012
ro.build.date.utc=1329215975
ro.build.type=user
ro.build.user=build
ro.build.host=build-desktop
ro.build.tags=release-keys
ro.product.model=ThinkPad Tablet
ro.product.brand=Lenovo
ro.product.name=ThinkPadTablet
ro.product.device=Indigo
ro.product.board=ventana
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Lenovo
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Indigo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=ventana-user 3.1 ThinkPadTablet_A310_02 0039_0089_US release-keys
ro.build.fingerprint=Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_US:user/release-keys
ro.build.characteristics=tablet
ro.product.input.defaultpkg=com.nuance.flext9_OEM.input
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
service.mtp.defult_lock=true
keyguard.no_require_sim=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
tf.enable=y
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.1_r2
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-lenovo
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Tried Update.Zip (OTA) instead of Download From Lenovo -- Diff Failure
Ok... I've been trying to install A400_03_0069_0130_US.zip which I had downloaded from Lenovo's ThinkPad Tablet download site. I decided just for grins, to try installing update.zip which is what is placed in your /cache/ on your TpT when you attempt a System Update from within the TpT itself. After instructing my TpT to "check for system updates" and letting it fully download, then choosing "install later..." after which I copied update.zip and update.xml to the root of my (external) SD Card. After that, I rebooted into Recovery (by now, CMW 5.5.0.4 -- I installed it this afternoon in frustration) and this time to tried to install the Update.zip instead of the A400_03_0069_0130_US.zip that I'd downloaded this morning from Lenovo.
Anyway... this failed too, but with a different error:
Assert failed: getprop("ro.product.device") == "Indigo" || get prop("ro.build.product") == "Indigo"
If you read the previous post, there's a statement in Build.Prop that, "ro.build.product is obsolete; use ro.product.device." I wonder if this has anything to do with the error that is stopping my install.
It will install if you comment out the build.prop check. You may have just done that incorrectly. There is an issue with editing the file in wordpad on windows. Use a different text editor.
There likely isn't an issue with your build.prop. The issue comes from CWR, it spoofs a different device (I think Asus Transformer) to install CWR, hence when in CWR the device report incorrect build.prop info.
I first tried this (and tried it for hours) without CWM installed, but got that error. I tried installing from the menu (Check for System Updates) and from the SD Card (using both [1] the update.zip that the "check for updates" method puts in your cache, by copying it to the root the external SD Card, and [2] the ThinkPadTablet_A400_03_0069_0130_US.zip that you can download from http://download.lenovo.com/slates/think/tablet1. I ran these from the SD Card using the default/factory Recovery that you get to through boot (power + volume up until boot starts, then volume up until you see the Recovery message).
Out of frustration, I installed CWM after several hours, thinking that maybe it would help. As you might guess, it did not. I would mention, however, that there are some posts out there where a user successfully updated to ICS using CWM (although his CWM was unusable after the ICS install, I assume). This resulted in the same errors.
I guess that my next step is to modify the updater.script found inside /META-INF/com/google/android/ which is found inside the update.zip or other zip you're trying to install (e.g. ThinkPadTablet_A400_03_0069_0130_US.zip). I believe that I can modify the updater.script to comment out the lines that are failing.
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_ROW:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0121_ROW:user/release-keys");
Unfortunately, after you modify the updater.script, you can't just shove it back into update.zip (or whatever). You have to generate a new zip using the method described in this post of this thread. Even worse, the instructions on how to generate a new zip install are above my head.
If I don't care about preserving anything on this TpT, isn't there a simple way to nuke this back to the way that it shipped from the factory and then update to ICS from there? I've owned dozens or hundreds of computers, but installing a new OS on this device is more complicated and more frustrating than all of the rest combined.
If I try to install update.zip from the root of the SD Card using CWM Recovery, I get this error:
Assert failed: getprop("ro.product.device") == "Indigo" || get prop("ro.build.product") == "Indigo"
If try to install ThinkPadTablet_A400_03_0069_0130_US.zip) from teh SD Card using CWM Recovery, I get this error:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0065_0128_US:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0130_US:user/release-keys"
Having read the updater.script in both of these ZIPs, I know that the install is tripping at nearly the very first line. I've seen other threads where people are missing certain APKs / ODEXs, such as Busybox and WPA_Supplicant to name a few. Those people got around the problem by replacing those apps from previous (usually 0089 or 0086) versions. A few go around the problem by editing the updater.script, then rebuilt their zip, re-signing it, and sprinkling it with magic fairy dust per
http://fokke.org/site/content/howto-create-android-updatezip-package. I wish my situation were merely about replacing some APKs.
Is rebuilding updater.script my only hope? If so, could someone talk me through the lines to remove or comment out and how to re-sign the zip, please?
Tell me, Lenovo, why do you have to make this so difficult? I could install a new OS on 1000 PCs with less effort and frustration.
Shouldn't you be doing this update first;
ThinkPadTablet_A310_03_0069_01..>
Related
I have an HTC Magic, and have just managed to downgrade hboot/spl and install a custom recovery.
But now, when i'm trying to install CM 6 (not the RC), i get a verification error..
Starting recovery..
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
Build : RA-hero-v1.6.2
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.ril.ecc.HTC-WWE=999
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.u70000.20090827.103405
ro.build.version.incremental=eng.u70000.20090827.103405
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Thu Aug 27 10:35:04 CST 2009
ro.build.date.utc=1251340504
ro.build.type=user
ro.build.user=u70000
ro.build.host=Android-X02
ro.build.tags=test-keys
ro.product.model=HTC Hero
ro.product.brand=htc_wwe
ro.product.name=htc_hero
ro.product.device=hero
ro.product.board=hero
ro.product.manufacturer=HTC
ro.product.locale.language=
ro.product.locale.region=
ro.board.platform=msm7k
ro.build.product=hero
ro.build.description=2.73.405.5 146733 CL#61267 release-keys
ro.build.changelist=61267
ro.product.ua=
ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/2.73.405.5/61267:user/test-keys
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep=1
wifi.interface=tiwlan0
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=160
ro.com.google.locationfeatures=1
persist.service.mount.playsnd=0
settings.display.autobacklight=1
settings.display.brightness=102
ro.ril.def.agps.mode=2
ro.com.google.networklocation=1
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-htc
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-hero-v1.6.2
ro.factorytest=0
ro.serialno=HT95WKF11405
ro.bootmode=recovery_manual
ro.baseband=6.35.08.29
ro.carrier=HTC-Nor
ro.bootloader=1.76.2007
ro.hardware=sapphire
ro.revision=128
ro.cid=HTC__Y13
init.svc.recovery=running
init.svc.adbd=running
I:Set boot command ""
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:
I:Set boot command ""
Enabling USB-MS : ./dev/block/mmcblk0
USB Mass Storage enabled
USB-MS enabled!
Press HOME to disable,
and return to menu
Disabling USB-MS : .USB Mass Storage disabled
USB-MS disabled!
I:Set boot command ""
I:Set boot command ""
Install : SDCARD:update-cm-6.0.0-DS-signed.zip ?
Press HOME to confirm,
any other key to abort.
Install from sdcard...
Finding update package...
I:Update location: SDCARD:update-cm-6.0.0-DS-signed.zip
Opening update package...
I:Update file path: /sdcard/update-cm-6.0.0-DS-signed.zip
Verifying update package...
I:Verified META-INF/CERT.RSA
I:Verified META-INF/MANIFEST.MF
<VERIFIED A LOT OF FILES>
I:Verified system/media/audio/ui/KeypressStandard.ogg
I:Verified system/lib/libGLESv1_CM.so
Installing update...
I:read: ui_print Welcome to CyanogenMod-6.0.0-DS!
Welcome to CyanogenMod-6.0.0-DS!script aborted: assert failed: getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||
getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire"
I:read: ui_print
I:read: ui_print assert failed: getprop("ro.product.device") == "trout" || getprop("ro.bassert failed: getprop("ro.product.device") == "trout" || getprop("ro.bI:read: uild.product") == "trout" || getprop("ro.product.board") == "trout" ||
E:unknown command [uild.product")]
I:read: ui_print getprop("ro.product.device") == "sapphire" || getprop("ro.build. getprop("ro.product.device") == "sapphire" || getprop("ro.build.I:read: product") == "sapphire" || getprop("ro.product.board") == "sapphire"
E:unknown command [product")]
I:read: ui_print
E:Error in /sdcard/update-cm-6.0.0-DS-signed.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I have no idea what to to, as i have never installed CM before.
the fastboot specs are:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Aug 21 2009, 18:19:15
help is much appreciated ^_^
It should not give any errors...
But you could always remove the error giving line from the install script..
Then resign the rom and flash it.
i'm sorry, i am a real noob on this, is it any chance you can do it for me? thanks.
EDIT: i tried once, but it got corrupted
You have to resign it.
Or it will get corrupted as the error gives you...
Or you could flash clockwork recovery instead of amon_ra... and deactivate the signing check.
thanks, i'll try that and report back
okay, now i reflashed the recovery with ROM Manager, pressed install from SD(in rom manager) and selected the CM rom(unmodified). it reboots, runs backup, everything looks good, and then the same error repeats itself until it sends me back to the recovery menu, where it is there for about 5 seconds, and then my phone reboots normally. all data is flashed.
how do i deactivate the signing check? or is there another solution?
EDIT... sorry just found that clockwork recovery does not work with the 6.35 radio...
**** it... i'll do it..
Give me link to the rom you want.
THANK YOU!
http://khsk.uberitz.net/cm/update-cm-6.0.0-DS-signed.zip
that's it. i need an EB1 kernel patch and google apps too(thats what cyanogenmod wiki said), dunno if they need to be changed too ..
link for google apps: http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-tiny-20101020-signed.zip
the EB1, though i dunno if it supports 6.35.x: http://briancrook.ca/android/cm-por...d.zip[/url
thanks SO much for doing this! :D
I found the problem...
You have 1.76.2007 spl...
This rom only works for old spl/radio...
Code:
getprop("ro.bootloader") == "1.33.2005" ||
getprop("ro.bootloader") == "1.33.2003AF" ||
getprop("ro.bootloader") == "1.33.0004" ||
getprop("ro.bootloader") == "1.33.2004" ||
getprop("ro.bootloader") == "1.33.3004" ||
getprop("ro.bootloader") == "1.33.0005" ||
getprop("ro.bootloader") == "1.33.2005" ||
getprop("ro.bootloader") == "1.33.3005" ||
getprop("ro.bootloader") == "1.33.0006" ||
getprop("ro.bootloader") == "1.33.2006" ||
getprop("ro.bootloader") == "1.33.3006" ||
getprop("ro.bootloader") == "1.33.0007" ||
getprop("ro.bootloader") == "1.33.2007" ||
getprop("ro.bootloader") == "1.33.3007" ||
getprop("ro.bootloader") == "1.33.0008" ||
getprop("ro.bootloader") == "1.33.2008" ||
getprop("ro.bootloader") == "1.33.3008" ||
getprop("ro.bootloader") == "1.33.0009" ||
getprop("ro.bootloader") == "1.33.2009" ||
getprop("ro.bootloader") == "1.33.0010" ||
getprop("ro.bootloader") == "1.33.2010" ||
getprop("ro.bootloader") == "1.33.0011" ||
getprop("ro.bootloader") == "1.33.2011" ||
getprop("ro.bootloader") == "1.33.3011" ||
getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013");
so i can downgrade via the instructions in this thread, and then install CM as normal?
No... use my tool to downgrade... MUCH EASIER :0)
Find it in my signature... Fastboot commander (magic).
Just find the magic 32A tab... then choose "flash old"...
It will flash a combo... so you also have the right recovery :0)
Then flash the rom, EBI1 and then gapps from recovery.
If you ever want to revert back to new radio.. then just choose "flash new" :0)
thanks, now i just have to make rapidshare stop hating me.. can't you upload to mediafire or something?
Done.............
okay, i just want to make sure about this.. what are the chances that ill brick my phone upgrading the radio? because im not sure if my magic supports the old radio..
I will never suggest to upgrade/downgrade your radio if i'm not sure that you device can support it.
Checking the op, i could see that you have the same device as i have... and i made the tool and tested my self... It will work :0)
ah, good. because i downgraded my SPL from S-ON and hboot 1.76.2009..
but since i did install the engineer spl, i suppose it works
EDIT: it didnt. i got this error:
"hboot" flash FAILURE.
FLASH OF OLD FILES FAILURE - SPL FAILURE.
then tried to flash new again, got this error:
"radio" flash FAILURE.
FLASH OF NEW FILES FAILURE - RADIO FAILURE.
EDIT2: unplugged and restarted into fastboot. it shows:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Aug 21 2009, 18.19.15
trying to boot normally, it gets into a boot loop. i can still get into fastboot and recovery(clockwork works!), so i dont think im bricked.
Easy now... and keep you comments in one thread or i will get confused...
YOU ARE NOT BRICKED!
You can fix this easy.
But lets agree on that you write on the fastboot commander thread where it's relevant.
See my reponse there
Hi,
It seems im in same error as you are.
Can you take a look at my thread.
http://forum.xda-developers.com/showthread.php?t=828300
Im almost done, stuck at flash the last 3 files according to instructions.
------------------------
17. After phone powers off, reboot into recovery by holding Home + Power keys.
.
18. Using the trackball, select "Flash ZIP from SD Card" and flash the following files.
Select the home key to confirm each file
a)update-cm-6.0.0-DS-signed.zip
b)bc-6.0.0-ebi1-signed.zip
c)gapps-mdpi-tiny-20100816-signed.zip
.
19. After the last file has finished flashing reboot the phone normally.
It can take anywhere from 5-15 min for the first boot.
--------------------------
thanks.
hi,
I read that I can update from 2.3.2 to 2.3.3.
So i downloaded the File:
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip
copied to /sdcard/ renamed it to updated.zip
went in the recovery mode and tried to apply it.
But instead of updating I got:
Code:
Starting recovery on Fri Feb 25 11:33:53 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/platform/s3c-sdhci.0/by-name/media (null)
2 /system ext4 /dev/block/platform/s3c-sdhci.0/by-name/system (null)
3 /cache yaffs2 cache (null)
4 /data ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata (null)
5 /misc mtd misc (null)
6 /boot mtd boot (null)
7 /recovery mtd recovery (null)
8 /bootloader mtd bootloader (null)
9 /radio mtd radio (null)
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
stat() of /dev/block/platform/s3c-sdhci.0/by-name/userdata succeeded on try 1
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.build.id=GRH78C
ro.build.display.id=GRH78C
ro.build.version.incremental=93600
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.2
ro.build.date=Thu Jan 20 00:02:31 PST 2011
ro.build.date.utc=1295510551
ro.build.type=user
ro.build.user=android-build
ro.build.host=android-test-15.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus S
ro.product.brand=google
ro.product.name=soju
ro.product.device=crespo
ro.product.board=herring
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=crespo
ro.build.description=soju-user 2.3.2 GRH78C 93600 release-keys
ro.build.fingerprint=google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.config.ringtone=Sceptrum.ogg
ro.config.notification_sound=Castor.ogg
ro.opengles.version=131072
wifi.interface=eth0
wifi.supplicant_scan_interval=15
dalvik.vm.heapsize=32m
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
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.config.alarm_alert=Alarm_Classic.ogg
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
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=39303EB8546600EC
ro.bootmode=unknown
ro.baseband=I9020XXJK8
ro.carrier=TMB
ro.bootloader=I9020XXJK1
ro.hardware=herring
ro.revision=11
init.svc.recovery=running
init.svc.adbd=stopped
mtd: successfully wrote block at 0
I:Set boot command ""
-- Install /sdcard ...
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1604 bytes; signature 1586 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
Verifying current system...
contents of partition "boot" didn't match MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b:2945024:754a5866e3918318bdc85dc6a75f81c08f6c5427
file "MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b:2945024:754a5866e3918318bdc85dc6a75f81c08f6c5427" 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("MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b:2945024:754a5866e3918318bdc85dc6a75f81c08f6c5427")
assert failed: apply_patch_check("MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b:2945024:754a5866e3918318bdc85dc6a75f81c08f6c5427")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
mtd: successfully wrote block at 0
I:Set boot command ""
I remembered that I installed theft aware in root mode, so I went and uninstalled it as they told me, but I got the same error again
I have samba file sharing, root explorer and connect droid as root apps which are in the superuser list.
I looked through the system dir and saw that the app "app/superuser" and xbin/su have newer date infos.
are they the reason it wont work?
What do you suggest what to do?
thanks in advance devzero.
Avalun said:
hi,
I read that I can update from 2.3.2 to 2.3.3.
So i downloaded the File:
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip
copied to /sdcard/ renamed it to updated.zip
went in the recovery mode and tried to apply it.
But instead of updating I got:
Code:
Starting recovery on Fri Feb 25 11:33:53 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/platform/s3c-sdhci.0/by-name/media (null)
2 /system ext4 /dev/block/platform/s3c-sdhci.0/by-name/system (null)
3 /cache yaffs2 cache (null)
4 /data ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata (null)
5 /misc mtd misc (null)
6 /boot mtd boot (null)
7 /recovery mtd recovery (null)
8 /bootloader mtd bootloader (null)
9 /radio mtd radio (null)
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
stat() of /dev/block/platform/s3c-sdhci.0/by-name/userdata succeeded on try 1
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.build.id=GRH78C
ro.build.display.id=GRH78C
ro.build.version.incremental=93600
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.2
ro.build.date=Thu Jan 20 00:02:31 PST 2011
ro.build.date.utc=1295510551
ro.build.type=user
ro.build.user=android-build
ro.build.host=android-test-15.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus S
ro.product.brand=google
ro.product.name=soju
ro.product.device=crespo
ro.product.board=herring
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=crespo
ro.build.description=soju-user 2.3.2 GRH78C 93600 release-keys
ro.build.fingerprint=google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.config.ringtone=Sceptrum.ogg
ro.config.notification_sound=Castor.ogg
ro.opengles.version=131072
wifi.interface=eth0
wifi.supplicant_scan_interval=15
dalvik.vm.heapsize=32m
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
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.config.alarm_alert=Alarm_Classic.ogg
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
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=39303EB8546600EC
ro.bootmode=unknown
ro.baseband=I9020XXJK8
ro.carrier=TMB
ro.bootloader=I9020XXJK1
ro.hardware=herring
ro.revision=11
init.svc.recovery=running
init.svc.adbd=stopped
mtd: successfully wrote block at 0
I:Set boot command ""
-- Install /sdcard ...
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1604 bytes; signature 1586 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
Verifying current system...
contents of partition "boot" didn't match MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b:2945024:754a5866e3918318bdc85dc6a75f81c08f6c5427
file "MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b:2945024:754a5866e3918318bdc85dc6a75f81c08f6c5427" 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("MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b:2945024:754a5866e3918318bdc85dc6a75f81c08f6c5427")
assert failed: apply_patch_check("MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b:2945024:754a5866e3918318bdc85dc6a75f81c08f6c5427")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
mtd: successfully wrote block at 0
I:Set boot command ""
I remembered that I installed theft aware in root mode, so I went and uninstalled it as they told me, but I got the same error again
I have samba file sharing, root explorer and connect droid as root apps which are in the superuser list.
I looked through the system dir and saw that the app "app/superuser" and xbin/su have newer date infos.
are they the reason it wont work?
What do you suggest what to do?
thanks in advance devzero.
Click to expand...
Click to collapse
Did you install an insecure boot image?
You might be able to apply the full rom, not the incremental upgrade - found here: http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
I just did the general root manual and my rom is the stock version.
If I apply the full rom, are my apps and contacts gone, so I have to reinstall them?
As the prior poster suggested, it appears to be your boot partition has been modified, and the script fails at that point. From your output you posted:
"Verifying current system...
contents of partition "boot" didn't match MTD"
Click to expand...
Click to collapse
If you're adventurous, you could open the update zip file and remark out/delete the lines that check the boot partition AND the ones that actually patch it. Critical you do both of those!!!! You wouldn't want to patch something via script that isn't what is expected by the script.
Warning: like I said, do this only if you're adventerous. i haven't tried it specifically with the boot partition, but we managed to force the upgrade to 2.3.2 for several people who had modded Google files on the /system partition by removing the lines in the script that do that.
krohnjw said:
Did you install an insecure boot image?
You might be able to apply the full rom, not the incremental upgrade - found here: http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
Click to expand...
Click to collapse
offtopic: ... how you find this URL? Now I don't need to worry about bricking my phone when it comes modifying
Someone here on xda was sill on 2.3.0 and received the full update over ota instead of an incremental update, they grabbed the url last night.
Sent from my Nexus S using XDA App
Avalun said:
I just did the general root manual and my rom is the stock version.
If I apply the full rom, are my apps and contacts gone, so I have to reinstall them?
Click to expand...
Click to collapse
If you don't wipe your apps and data will still be present.
Sent from my Nexus S using XDA App
I had this same problem when trying to update. The solution in my case was to download the backup in this thread: http://forum.xda-developers.com/showthread.php?t=965686
After downloading it extract the boot.img file and fastboot it.
Hope this helps.
krohnjw said:
If you don't wipe your apps and data will still be present.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
whoohoo, the full update with you full image worked *bighug* thanks very much.
The OS got unrooted again but thats not so urgent that I need to reroot it
Avalun said:
whoohoo, the full update with you full image worked *bighug* thanks very much.
The OS got unrooted again but thats not so urgent that I need to reroot it
Click to expand...
Click to collapse
I'm having the same issue. Will try the full upgrade as well....
Easiest Way To Update And Keep Root
mabco said:
I'm having the same issue. Will try the full upgrade as well....
Click to expand...
Click to collapse
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
Is the update supposed to change the baseband version coming from 3.1?
Sent from my Nexus S using XDA App
Bronk93 said:
Is the update supposed to change the baseband version coming from 3.1?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
it changes the baseband but if you have clockwork mod you can always go back with no issues.
That's odd. I tried the upgrade using the rooted nandroid image and it worked but my baseband stayed at jk8 for some reason.
Sent from my Nexus S using XDA App
Bronk93 said:
That's odd. I tried the upgrade using the rooted nandroid image and it worked but my baseband stayed at jk8 for some reason.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
So are you good or is there some issues
Sent from my Nexus S using XDA App
I have 2.3.2 rooted with clockwork recovery as the default recover (renamed install.recovery.sh to stop it loading).
Can I apply this update using clockwork, or do i have to rename stock recovery so it takes over again.
buachaille said:
I have 2.3.2 rooted with clockwork recovery as the default recover (renamed install.recovery.sh to stop it loading).
Can I apply this update using clockwork, or do i have to rename stock recovery so it takes over again.
Click to expand...
Click to collapse
If you have cw already just unzip the file and put the it in your backup folder and restore
Sent from my Nexus S using XDA App
Isn't the baseband version the radio? If so why did mine not change going from 3.1 to 3.3
Sent from my Nexus S using XDA App
chuck666 said:
I had this same problem when trying to update. The solution in my case was to download the backup in this thread: http://forum.xda-developers.com/showthread.php?t=965686
After downloading it extract the boot.img file and fastboot it.
Hope this helps.
Click to expand...
Click to collapse
How can I do this?
When I try to do:
fastboot flash boot boot.img
I get this error:
ERROR: could not get pipe properties
sending 'boot' (8192 KB)... OKAY
writing 'boot'... FAILED (remote: Write Fail)
hi, is Baseband is supposed to change, i am bit scared to apply this officially update as i have root with cw recovery , i am on stock 2.3.2 wanted 2.3.3 very badly but i am in Uk & most of our folks didnt get the update, so i am becoming desperate, can i apply this zip, as i read on engadget as to before doing manual update i need to check the version, whats all that about, i thought nexuss is same everywhere at least in UK US
I am on stock ROM (rooted and with clockworkmod recovery).
I am getting a popup for OTA system update saying "Would you like to install the following system software update?
System upgrade 1.67.720.70 (2.54 MB) Update: HTC Peep Client).
When i say install now, it reboots into recovery and tries to install the downloaded system updated from /cached/OTA... signed..zip.
But it fails reporting
E: Signature verification failed.
I have tried to toggle signature verification to off and try to put the update to /sdcard/update.zip.
Can someone help me, guiding how can i install the update.
Put file on SD(in root - /)
Boot in latest ClockworkMod recovery.
Select
1) "install zip from SDcard"
2) "Choose zip from SDcard"
3) Choose the zip file
4) Yes - Install.......
That's all
No clockwork will not install update
flash anon_ra recovery & install update
clockwork not support 1.6 update script
Still Error
Code:
Starting recovery on Tue Mar 1 21:04:22 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (240 x 320)
Build : RA-tattoo-v1.6.2
Fixing execute permissions for /cache
I:Got arguments from CACHE:recovery/command
I:Set boot command "boot-recovery"
Command: "/sbin/recovery" "--update_package=CACHE:OTA_Click_HTC_Asia_India_1.67.720.70-1.67.720.8_release_signedwybnyccqr4zky08o.zip"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-Russia=01,02,03,04,001,002,003,004
ro.ril.ecc.HTC-EastEurope=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.build.id=DRC79
ro.build.display.id=DRC79
ro.build.version.incremental=74178
ro.build.version.sdk=4
ro.build.version.codename=REL
ro.build.version.release=1.6
ro.build.date=Tue Oct 6 23:09:53 CST 2009
ro.build.date.utc=1254841793
ro.build.type=user
ro.build.user=u70000
ro.build.host=Oven-X04
ro.build.tags=release-keys
ro.product.model=HTC Tattoo
ro.product.brand=htc_wwe
ro.product.name=htc_tattoo
ro.product.device=bahamas
ro.product.board=bahamas
ro.product.cpu.abi=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=
ro.product.locale.region=
ro.board.platform=msm7k
ro.build.product=bahamas
ro.build.description=1.67.405.6 CL#74178 release-keys
ro.build.changelist=74178
ro.build.modelid=CLIC*****
ro.build.fingerprint=htc_wwe/htc_tattoo/bahamas/bahamas:1.6/DRC79/74178:user/release-keys
ro.product.version=1.67.405.6
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.hsdpa.category=8
ro.ril.hsxpa=1
wifi.interface=tiwlan0
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=120
ro.com.google.locationfeatures=1
view.fading_edge_length=8
view.touch_slop=15
view.minimum_fling_velocity=25
view.scroll_friction=0.008
persist.service.mount.playsnd=0
ro.ril.def.agps.mode=2
ro.workaround.noautofocus=1
settings.display.brightness=143
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.com.google.clientidbase=android-htc
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.setupwizard.mode=DISABLED
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-tattoo-v1.6.2
ro.factorytest=0
ro.serialno=HT9A6N502860
ro.bootmode=recovery
ro.baseband=3.35.07.20
ro.carrier=HTC-India
ro.bootloader=0.52.0001
ro.hardware=bahamas
ro.revision=128
ro.cid=HTC__038
init.svc.recovery=running
init.svc.adbd=running
adb.connected=
Finding update package...
I:Update location: CACHE:OTA_Click_HTC_Asia_India_1.67.720.70-1.67.720.8_release_signedwybnyccqr4zky08o.zip
Opening update package...
I:Update file path: /cache/OTA_Click_HTC_Asia_India_1.67.720.70-1.67.720.8_release_signedwybnyccqr4zky08o.zip
Verifying update package...
[COLOR="Red"]W:Can't verify META-INF/CERT.RSA
E:No signature (9 files)
E:Verification failed[/COLOR]
Installation aborted.
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Move recovery.log to SD
Press DPAD to confirm,
any other key to abort.
Moving : .
Still getting similar error
Okay solved. I flashed stock recovery (glad maverixx had shared it, i had no backup of it :| )
then everything went smoothly
http://forum.xda-developers.com/attachment.php?attachmentid=295564&d=1268920582
Hey guys, I have a few questions, maybe basic, or maybe not, but if you could help itd be amazing! First off, I want to access files from one of the secondary roms on the internal rom, is that possible (Im using ESFile explorer this may be the issue as well if it doesnt support android L)? Second, I seem to be having trouble installing the bodhi zip. Did i miss something or are others having this issue? I installed the multirom via the app in android L, then put on CM11 as a second(thats where i put the files i want to access as well), I booted into the recovery and clicked the install button right on the main page and select the zip of Bodhi-MultiROM-Installer-20130109.zip and get
Code:
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Bodhi-MultiROM-Installer-20130109 (1).zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper" ||
getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia"
assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper" || getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia"
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Bodhi-MultiROM-Installer-20130109 (1).zip'
Error flashing zip '/sdcard/Bodhi-MultiROM-Installer-20130109 (1).zip'
Updating partition details...
I:Data backup size is 506MB, free: 19255MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
Is there something I missed?
No, you cannot access the files on another ROMs filesystem from a secondary, or vice versa.
As for the second question, the Bodhi ROM you are trying to flash is for a different device, you need a ROM which is made for your device.
OP, you have already posted this in Q&A (http://forum.xda-developers.com/nex...ons-involving-multi-rom-t2826337/post54361735), please do not double post. Closed.
Hi all
Trying to install the latest nightly has been impossible since June. Have left things as is, the phone works fine with the installed ROM version.
Now I tried to research where the problem lies, but don't have the necessary tech know-how to remedy it.
When trying to install the zip the following messages appear on TWRP:
Updating partition details......
...... done
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/LineageOS/lineage-15.1-20181214-nightly-klte-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteusc,kltevzw,kltexx; this device is .
(now text in red)
E:unknown command[log]
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/LineageOS/lineage-15.1-20181214-nightly-klte-signed.zip'
(text in red ends)
Updating partition details....
...done
Until June, the nightly updating never was a problem.
I am 100% sure my S5 is the klte version
The red line E:unknown command [log] always popped up when updating, but did not interrupt the updating process.
The latest version that worked for updating and that is installed on my phone is: 14.1-20180629-NIGHTLY-klte
Kernel Version
3.4.113-lineageos-g31d25d7
[email protected] #1
Fri Jun 29 14:12:53 CEST 2018
Build Number
lineage_klte_userdebug 7.1.2 NJH47F 6fc3da3341
Hope this info helps to identify, why the nightly does not recognize the klte (see the 9th line, where it says ' this device is . '
My guess is that either some file on my phone is missing or not in the spot where the nightly is looking for it???
How can i repair this so that i can get my S5 up to date?
Appreciate your help!!
Delete the first line in updater script using notepad++
Where is the updater script?META-INF/com/google/android/updater-script
Thank you for your answer. Unzipped the nightly file, but I can not find a script named updater? Do you mean the file I list below:
updater-script ???
The first line reads:
assert(getprop("ro.product.device") == "klte" || getprop("ro.build.product") == "klte" ||
getprop("ro.product.device") == "klteacg" || getprop("ro.build.product") == "klteacg" ||
getprop("ro.product.device") == "klteatt" || getprop("ro.build.product") == "klteatt" ||
getprop("ro.product.device") == "kltecan" || getprop("ro.build.product") == "kltecan" ||
getprop("ro.product.device") == "kltelra" || getprop("ro.build.product") == "kltelra" ||
getprop("ro.product.device") == "kltetmo" || getprop("ro.build.product") == "kltetmo" ||
getprop("ro.product.device") == "klteub" || getprop("ro.build.product") == "klteub" ||
getprop("ro.product.device") == "klteusc" || getprop("ro.build.product") == "klteusc" ||
getprop("ro.product.device") == "kltevzw" || getprop("ro.build.product") == "kltevzw" ||
getprop("ro.product.device") == "kltexx" || getprop("ro.build.product") == "kltexx" || abort("E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteub,klteusc,kltevzw,kltexx; this device is " + getprop("ro.product.device") + ".");
If that is correct, please let me know. prefer to be 100% sure before bricking my phone. Thanks for your patience with a newb
unzipping the nightly I see:
folder install/bin with backuptool.functions and backuptool.sh
folder META-INF/com/android with metadata and otacert
folder META-INF/com/google/android with update-binary and updater-script ??? any of these 2????
folder META-INF/org/lineageos with releasekey
folder system with build.prop
and the files
boot.img
file_contents.bin
system.new.dat.br
system-patch.dat
system.transfer.list
Once more: Appreciate your help a lot!
Edit: THIS WORKED JUST FINE! Thank you a million! Using notepad++ makes editing the file a snap, as it does not insist on .txt ending of file. Edited the line above out and saved the file, zipped the lot up again and then did the Install in TWRP. The Install process ran smoothly. Wiped the Davlik and rebooted. System comes up just fine!!!! AD FOX You were a great help!!!!
same problem on lineage 16 any fix yet?
Octaved said:
same problem on lineage 16 any fix yet?
Click to expand...
Click to collapse
Can confirm, same problem, also same solution, as described above:
open the zip, edit META-INF/com/google/android/updater-script
Remove from the start of assert(getprop("ro.product.device") == "klte" || ... untill ...+ getprop("ro.product.device") + ".")
Save, and use this modified zip. I just tried it with no problems. Thanks!
Updater process ended with signal: 11
xananaxx said:
Can confirm, same problem, also same solution, as described above:
open the zip, edit META-INF/com/google/android/updater-script
Remove from the start of assert(getprop("ro.product.device") == "klte" || ... untill ...+ getprop("ro.product.device") + ".")
Save, and use this modified zip. I just tried it with no problems. Thanks!
Click to expand...
Click to collapse
Tried this solution but now get different error Updater process ended with signal: 11
According to the updater-script its failing at this point
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
The same here. I also got the error 11 message after flashing the modified updater script. My solution: Just flash the next older version of TRWP (e.g. instead of twrp-3.4.0-0-klte.img use twrp-3.3.1-0-klte.img). It worked just fine.
plapic said:
Updater process ended with signal: 11
Tried this solution but now get different error Updater process ended with signal: 11
According to the updater-script its failing at this point
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
Click to expand...
Click to collapse
If editing the code and removing some open brackets, make sure to also remove the corresponding closing brackets. I.e. I changed line 1 from:
Code:
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper" || abort("E3004: This package is for device: grouper; this device is " + getprop("ro.product.device") + "."););
into:
Code:
getprop("ro.product.device") + ".";
When I made this change to line 1 of updater-script it worked fine and the ROM installed.
By the way, if you edit updater-script, you have edited the zip file and so you will need to uncheck TWRP's 'zip signature verification' tickbox.