I need help as soon as it possible I will copy log here:Installing update...line 152 col 3:syntex error,unexpected BAD,expecting $end 1 parse errors
E:error in /sdcard/ROM/WFSY10.1-v0.2.zip
(Satus 6)
Instalation aborted.
mtd:successfully wrote block at c7e0400000000
Cosmodix said:
I need help as soon as it possible I will copy log here:Installing update...line 152 col 3:syntex error,unexpected BAD,expecting $end 1 parse errors
E:error in /sdcard/ROM/WFSY10.1-v0.2.zip
(Satus 6)
Instalation aborted.
mtd:successfully wrote block at c7e0400000000
Click to expand...
Click to collapse
You can ask it on my thread,I said in changelog that v0.2 couldn't boot,now you can use v0.3 which is perfectly working
Related
HI. Please help me! I wasn't able to modify an article on the WIKI (wiki.xda-developers.com).
All the time I press the "Edit" Button, FireFox give me the option to download the php file :?: :?: :shock: WEIRD
The address I was modifying was:
http://wiki.xda-developers.com/index.php?pagename=List of HimaUpgradeUt.exe Error Code
After trying it several times, I could get inside and edit the page, then I saved it, and now is BLANK!!!!
HEEEEELLPPPP
The contets of the page at the time of my edit were:
--------------------------
ERROR 100: MODEL ID ERROR
Definition: ROM image is not design for the device you are upgrading. It happens when you try to use Himalaya's ROM image into other HTC like MAGICIAN, BlueAngel or Alpine
Solution: Use appropriate ROM Upgrade image for your Device, no two device can share the same ROM
ERROR 101: CONNECTION ERROR
ERROR 102: CE IMAGE FILE CHECKSUM ERROR
ERROR 103: ROM IMAGE FILE NOT FOUND
ERROR 104: CANNOT OPEN ROM IMAGE FILE
ERROR 105: OPEN PORT FAILURE
ERROR 106: EXECUTE REMOTE COMMUNICATION PROGRAM FAILURE
WARNING 111: POWER ADAPTER NOT PLUGGED IN
ERROR 112: CE ROM UPDATE ERROR
ERROR 113: EXTENDED ROM UPDATE ERROR
ERROR 114: RADIO ROM UPDATE ERROR
ERROR 115: INVALID VERSION OF ACTIVESYNC
ERROR:116 GENERAL ERROR
ERROR 117: INVALID MODEL ID
ERROR 120: COUNTRY ID ERROR
ERROR 121: LANGUAGE ID ERROR
ERROR 122: EXTENDED IMAGE FILE CHECKSUM ERROR
ERROR 123: RADIO IMAGE FILE CHECKSUM ERROR
ERROR 130: CREATE CE ROM IMAGE ERROR
ERROR 131: ALLOCATE MEMORY ERROR
ERROR 132: WRITE DATA ERROR
ERROR 133: COMMUNICATION ERROR
ERROR 134: READ CE ROM IMAGE ERROR
ERROR 135: COMMUNICATION ERROR
ERROR 136: COMMUNICATION INTERRUPT
ERROR 137: COMMUNICATION ERROR
ERROR 150: ROM UPGRADE UTILITY ERROR
ERROR 200: WRITE EXTENDED ROM FAIL
Error 201: GET DEVICE DATA ERROR
This error is a bit misleading. The BAUpdate tool is trying to switch the phone into bootloader mode, and the phone for some reason is being uncooperative. This happens to me from time to time. The best, and quickest way around this is to force the phone into Bootloader manually. By pressing the record button, while doing a hard reset (Power + Reset) your phone will enter bootloader mode. You can verify this as the screen will say, Serial, and change to USB when you cradle it.
Once you cradle your phone, Windows will detect it as new hardware, and take a minute or two configure the right driver(Microsoft USB Sync). Once this is complete, you can run the BAUpgrade utility again, and this time you should get past error 201.
Error 202: READ IMAGE ERROR
ERROR 210: CREATE EXTENDED ROM IMAGE ERROR
ERROR 211: ALLOCATE MEMORY ERROR
ERROR 212: WRITE DATA ERROR
ERROR 213: COMMUNICATION ERROR
ERROR 214: READ EXTENDED ROM IMAGE ERROR
ERROR 215 COMMUNICATION ERROR
ERROR 216: COMMUNICATION INTERRUPT
ERROR 310: CREATE RADIO ROM IMAGE ERROR
ERROR 311: ALLOCATE MEMORY ERROR
ERROR 312: WRITE DATA ERROR
ERROR 313: COMMUNICATION ERROR
ERROR 314: READ RADIO ROM IMAGE ERROR
ERROR 315: COMMUNICATION ERROR
ERROR 316: COMMUNICATION INTERRUPT
ERROR 317: COMMUNICATION ERROR
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Yup, I thought it was a temporary problem. Moreover, I'm having the same strange behaviour in some wiki links.
For instance:
http://wiki.xda-developers.com/index.php?pagename=BA_Versions
It is the first link on this page:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Radio
Thanks for your answer. I'll try later........
oltp said:
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Click to expand...
Click to collapse
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Luckily, I think you can allways get an older version of the page.
Cheers
oltp said:
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Click to expand...
Click to collapse
arieltools said:
Luckily, I think you can allways get an older version of the page.
Click to expand...
Click to collapse
Ok learned something again, I didn't know that.
I have a Dream running 1.5 and I want to download 1.6 (because for some reason I can't get it OTA) and it works perfectly until it installs the update and says "E: Failure at line 2: assert file_contains("SYSTEM:buildprop", "ro.build.fingerprint=tmobile/kila/dream/trout:1.5/CRC1/150275:user/ota-rel-keys,release-keys") == "true" l l file_contains("SYSTEM:build.prop", "ro.build.fingerprint=tmobile/kila/dream/trout:1Installation aborted." Any idea what's going on?
Hello.
I have exactly the same problem.
is there any way to update system without waiting for automatic update?
Greetings
hnnknr
Hi guys, first post. Need a little bit of help here..firstly let me apologize if i have asked this in the wrong place...ive got no idea whats going on here sorry!
Ive got a Nexus S 3g..running version 2.3.6
The baseband version is I9023XXKF1 and kernel version 2.6.35.7-gf5f63ef
I had no problems rooting the phone and getting to the clockwork recovery, and after having downloaded the new b9 build of the ICS from http://forum.xda-developers.com/showpost.php?p=18622852&postcount=1 i put it on the sd card and then tried to load it but i got this message....
Finding update package...
Opening update package...
Installing update...
assert failed: get prop ("ro.product.device") =="crespo" l l getprop (ro.build.product") == "crespo" l l getprop ("ro.product.board") == "crespo"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Is there something i have done wrong, or something i need to do in order to get this running alright on my phone? Any help would be much appreciated
Cheers guys
Hello,
Well, I live in Brazil, and here, the SE xPeria Live w/ Walkmant has a modelname as WT19a, not WT19i as in other countries.
Now, I'm tryin' to install the 'Coconut' 46 or RC1 version of the Cyanogenmod, but in CWM, when i go to install the .zip, it says: "asser failed: getprop("ro.product.device")== "wt19a" || [............] getprop("ro.product.device")== "wt19i" || [............]
getprop("ro.build.product")== "coconut" || E: Error in /sdcard/update-cm-7.2.0-RC1-coconut-signed.zip // or "E: Error in /sdcard/cm_coconut_full-46.zip"
(Status 7)
Please, answer me!
Did you try to change the ro.product.model with https://play.google.com/store/apps/details?id=org.nathan.jf.build.prop.editor&hl=de
Btw: You need root.
halilgoecer said:
Did you try to change the ro.product.model with https://play.google.com/store/apps/details?id=org.nathan.jf.build.prop.editor&hl=de
Btw: You need root.
Click to expand...
Click to collapse
Thank You so much.. I think now it'll work.
Sent from my WT19i using xda premium
Also you can rename build prop in package zip to wt19a
zip will be actualize and it will also work
Hello,
I also have a WT19a, and I'm unable to install the recent CyanogenMod 7.2.0 RC1.
I've tried changing the build.prop on my phone and on the .zip file, and it still says that error: ""asser failed: getprop("ro.product.device")== "wt19a" || [............] getprop("ro.product.device")== "wt19i" || [............]
getprop("ro.build.product")== "coconut"
What, exactly, should I do?
Thanks in advance.-
Same problem
vbobarth said:
Hello,
Well, I live in Brazil, and here, the SE xPeria Live w/ Walkmant has a modelname as WT19a, not WT19i as in other countries.
Now, I'm tryin' to install the 'Coconut' 46 or RC1 version of the Cyanogenmod, but in CWM, when i go to install the .zip, it says: "asser failed: getprop("ro.product.device")== "wt19a" || [............] getprop("ro.product.device")== "wt19i" || [............]
getprop("ro.build.product")== "coconut" || E: Error in /sdcard/update-cm-7.2.0-RC1-coconut-signed.zip // or "E: Error in /sdcard/cm_coconut_full-46.zip"
(Status 7)
Click to expand...
Click to collapse
Hello!
I am having the exact same problem... I have been searching for a lot of hours.
When I find something, I'll post it here.
Xperia Play R800i
PLEASE HELP ME I tried to put cyanogenmod 9 on my xperia play R800i GSM version 2.3.4, i did all the steps by the guide but after reboot my device does not open. Sorry For Bad English.:crying::crying::crying:
TheVeteran said:
PLEASE HELP ME I tried to put cyanogenmod 9 on my xperia play R800i GSM version 2.3.4, i did all the steps by the guide but after reboot my device does not open. Sorry For Bad English.:crying::crying::crying:
Click to expand...
Click to collapse
Is your Xperia Play stuck on "Sony Ericsson" logo screen?
Try these instructions (steps 1, 2 and 3 only) - credits for vokal1992
http://forum.xda-developers.com/showthread.php?t=1762372
(the mentioned ROM is Android ICS, newer than your 2.3.4)
Hi, noob to CM13. Currently have cm-13.0-20160604-NIGHTLY-Z00T running on my Asus Zenfone 2 (ZE551KL). I have been trying to update to a newer build with no success, any build newer than 6/14 fails, and 6/14 itself is horribly unstable. The error message from the log file is as follows:
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.R2-00064script aborted: assert failed:, asus.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.R2-00064
assert failed: asus.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/data/media/0/cmupdater/cm-13.0-20160704-NIGHTLY-Z00T.zip
By the way, I am using TWRP to update.
From my google searches, other people have claimed this is an outdated firmware problem, but I couldn't find anything on how to update my firmware.
Any help is greatly appreciated.
Hi,
Thanks for using XDA assist.
Please create a XDA account and post here:
[GENERAL HELP] Post Your Questions Here Instead of Making a New Thread
Good Luck! - gsstudios