exiting status 1 - HTC EVO 3D
I am trying too flash blackened rom too my phone, just got it rooted. S-on with the cwm-4.0.1.4-shooteru.img, here is where the problems starts. After downloading Blackend_E3D_CDMA_2.5.2_010212_050920.zip I moved it over too my SD card, and booted too recovery. Installed from zip from sd card. i get the error
E: error in "file.zip"
(Status 1)
Installation aborted.
Have tryed googling for hours whitout any good answer too this, please help?
Quick update on my situasjon, it seems like i cant add any custom roms too my evo 3d!
forgot too mention its a Hboot 1.49.018 on it. Please help cause i am kinda lost on this one
<! -- edit just flashed clockwork recovery 5.0.2.0 on it, this made recovery crash completely. Had too pull the battery out too reboot it. -->
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/Blackend_E3D_CDMA_2.5.2_010212_050920 (1).zip
Finding update package...
I:Update location: /sdcard/Blackend_E3D_CDMA_2.5.2_010212_050920 (1).zip
Opening update package...
Installing update...
about to run program [/sbin/erase_image] with 2 args
Creating filesystem with parameters:
Size: 4194304
Block size: 4096
Blocks per group: 32768
Inodes per group: 256
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 1024
Block groups: 1
Reserved block group size: 7
error: do_inode_allocate_extents: Failed to allocate 1025 blocks
TTTTTTTTTTTTTTTTTT
TTTTTTTTTTTTTTT
TTTT
TTTT
TTTT
TTTT
NNNNNNN NNNN
NNNN NNNN NNNN
NNNN NNNN NNNN
NNNN NNNN NNNN
NNNN NNNNNNNN
_________________________________________________
* *
* Team Nocturnal Presents *
* Nocturnal Blackend RLS 2.5 *
* Twitter: @Team_Nocturnal *
* Team-Nocturnal.com *
* Custom Roms, Themes & Mods *
* Thanks to all the Nocturnal Team and testers *
_______________________________________________
E:Error in /sdcard/Blackend_E3D_CDMA_2.5.2_010212_050920 (1).zip
(Status 1)
Installation aborted.
-- Installing: /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
Finding update package...
I:Update location: /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "shooter" || getprop("ro.build.product") == "shooter" || getprop("ro.product.board") == "shooter"
assert failed: getprop("ro.product.device") == "shooter" || getprop("ro.build.product") == "shooter" || getprop("ro.product.board") == "shooter"
E:Error in /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
(Status 7)
Installation aborted.
Script Asserts: Enabled
-- Installing: /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
Finding update package...
I:Update location: /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "shooter" || getprop("ro.build.product") == "shooter" || getprop("ro.product.board") == "shooter"
assert failed: getprop("ro.product.device") == "shooter" || getprop("ro.build.product") == "shooter" || getprop("ro.product.board") == "shooter"
E:Error in /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
(Status 7)
Installation aborted.
Attached complete logfile to the thread so those that knows this might understand whats going on.
Most likely a bad zip file. Redownlaod to test that.
If it's a good zip, then it's an error in the updater-script
not a faulty zip file, have downloaded it twice now and still same on both i even tryed downloading a diffrent version of it same thing.
I have tryed too install a completly diffrent rom, didnt get installed ended in error but this time it was a status 7.
Well, are you sure you got a cdma device and not a gsm?
j4n87 said:
Well, are you sure you got a cdma device and not a gsm?
Click to expand...
Click to collapse
I thought i had a cdma but now i am not so sure anymore, because I did abit off checking around and see most off the postings i have read had been in the gsm development not cdma.
I am trying again with a warmtwopoint deodex rom now.
What is the main diffrence between cdma and gsm?
I know 3G networking goes under cdma
Edit: sorry wcdma is 3g
you got definatly a gsm phone m8 =P
OrjanTonder said:
forgot too mention its a Hboot 1.49.018 on it.
-- Installing: /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
Finding update package...
I:Update location: /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "shooter" || getprop("ro.build.product") == "shooter" || getprop("ro.product.board") == "shooter"
assert failed: getprop("ro.product.device") == "shooter" || getprop("ro.build.product") == "shooter" || getprop("ro.product.board") == "shooter"
E:Error in /sdcard/Warm-TwoPointThree-RLS1-ODEXED-shooter.zip
(Status 7)
Installation aborted.
Attached complete logfile to the thread so those that knows this might understand whats going on.
Click to expand...
Click to collapse
To help further the knowledge in this thread and for anybody coming acoss this later, I'll explain how to read/explain the above recovery log error message generally found in /tmp/recovery.log or /cache/recovery.log.
Off the top of my head...
First, hboot version 1.49.018 is only for GSM devices. that should clear up any cdma/gsm confusion. the cdma version only has hboot 1.3, 1.4 and 1.5. maybe cdma will get a newer version sometime soon?
Reading the recovery log error. First we have to understand what is happening. After you select a ROM .zip file from the custom recovery, the updater-script file is processed, found near /META-INF/com/google/android/updater-script.
At the start of this updater-script, and is common in many OTA official .zip file updater-script files is a check against the the type of device currently being used. This checks the device build.prop identification locations, ro.product.device, ro.build.product, etc and for this specific ROM attempts to verify the device is the CDMA version of the EVO 3D, known as the "shooter".
If this were a GSM ROM and were to check for the GSM version of the EVO 3D, it would check for the phrase, "shooteru", as that is the name given to the GSM version of the EVO 3D.
Since, the device currently being used does not match, "shooter", processing the ROM .zip fails. This prevents the developers from getting complaints that flashing their ROM "bricks" a device, or causes a users issues/problems. The prevention mainly means the user is not able to load the ROM.
Hope that helps provide some technical details behind the recovery log and specific error being experienced!
joeykrim said:
To help further the knowledge in this thread and for anybody coming acoss this later, I'll explain how to read/explain the above recovery log error message generally found in /tmp/recovery.log or /cache/recovery.log.
Off the top of my head...
First, hboot version 1.49.018 is only for GSM devices. that should clear up any cdma/gsm confusion. the cdma version only has hboot 1.3, 1.4 and 1.5. maybe cdma will get a newer version sometime soon?
Reading the recovery log error. First we have to understand what is happening. After you select a ROM .zip file from the custom recovery, the updater-script file is processed, found near /META-INF/com/google/android/updater-script.
At the start of this updater-script, and is common in many OTA official .zip file updater-script files is a check against the the type of device currently being used. This checks the device build.prop identification locations, ro.product.device, ro.build.product, etc and for this specific ROM attempts to verify the device is the CDMA version of the EVO 3D, known as the "shooter".
If this were a GSM ROM and were to check for the GSM version of the EVO 3D, it would check for the phrase, "shooteru", as that is the name given to the GSM version of the EVO 3D.
Since, the device currently being used does not match, "shooter", processing the ROM .zip fails. This prevents the developers from getting complaints that flashing their ROM "bricks" a device, or causes a users issues/problems. The prevention mainly means the user is not able to load the ROM.
Hope that helps provide some technical details behind the recovery log and specific error being experienced!
Click to expand...
Click to collapse
Thanks this explained alot
help!
joeykrim said:
To help further the knowledge in this thread and for anybody coming acoss this later, I'll explain how to read/explain the above recovery log error message generally found in /tmp/recovery.log or /cache/recovery.log.
Off the top of my head...
First, hboot version 1.49.018 is only for GSM devices. that should clear up any cdma/gsm confusion. the cdma version only has hboot 1.3, 1.4 and 1.5. maybe cdma will get a newer version sometime soon?
Reading the recovery log error. First we have to understand what is happening. After you select a ROM .zip file from the custom recovery, the updater-script file is processed, found near /META-INF/com/google/android/updater-script.
At the start of this updater-script, and is common in many OTA official .zip file updater-script files is a check against the the type of device currently being used. This checks the device build.prop identification locations, ro.product.device, ro.build.product, etc and for this specific ROM attempts to verify the device is the CDMA version of the EVO 3D, known as the "shooter".
If this were a GSM ROM and were to check for the GSM version of the EVO 3D, it would check for the phrase, "shooteru", as that is the name given to the GSM version of the EVO 3D.
Since, the device currently being used does not match, "shooter", processing the ROM .zip fails. This prevents the developers from getting complaints that flashing their ROM "bricks" a device, or causes a users issues/problems. The prevention mainly means the user is not able to load the ROM.
Hope that helps provide some technical details behind the recovery log and specific error being experienced!
Click to expand...
Click to collapse
hey there--running into this exact status 7 error now wherein assert failed mentions the cdma "toro" then says there is an error in the rom .zip file. (gnex cdma).
I'm fairly saavy on rooting and have done it on both pc and mac with multiple devices, but never run into this. Per your post, can you help me understand how to get my phone to be properly renamed so it will recognize the rom? i can't flash a custom rom, so am assuming flashing stock will get me the same error. Root failed earlier and I have an unlocked boot.
Related
[Q] Error while flashing CM10 FXP133
Can anyone help PLEASE.
I am new to flashing custom ROMS and am having problem flashing this one FXP133 CM10.
The one given here: http://forum.xda-developers.com/showthread.php?t=1780329
I get following error while Flashing:
Code:
-- Installing: /sdcard/FXP133-cm-10-20120813-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-haida.zip
Opening update package...
Installing update...
script aborted:
assert failed: getprop("ro.product.device") == "MT11i" || getprop
("ro.build.product") == "MT11i" || getprop("ro.product.device") ==
"MT11a" || getprop("ro.build.product") == "MT11a" || getprop
("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
E:Error in /sdcard/FXP133-cm-10-20120813-haida.zip
(Status 7)
Installation aborted.
When on .42 (GB) stock firmware and Using MT11i NeoV.
In the Dev Thread I got following 2 replies:
dugzino said:
The thing is I did no clean install, simply overwrited 133 one. And now, I'm even more sure about it, in 134 you can feel the butter project!
First install the recommended Baseband (= .72) then flash the kernel then ROM then GApps then data wipe and you're good to go.
If you still don't know, there are lots of tutorials on how to flash ROMs. Just search
Click to expand...
Click to collapse
AND
music.soul said:
Firstly you need to have ICS with baseband .72
if you get the same error ... then open the rom with any archieve ... open up updater-script in meta-inf folder ... delete the lines till ...
Code:
("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
and save it ... flash it again done!
Click to expand...
Click to collapse
I tried both of them but still with no luck.
Now I am on ICS 4.0.4 with Baseband (.72) and have changed the updater-script and removed the lines (as suggested there) till.....
Code:
("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
But Now I am getting following error while flashing:
Code:
-- Installing: /sdcard/FXP133-cm-10-20120813-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-haida.zip
Opening update package...
Installing update...
(Status 7)
Installation aborted.
PLEASE tell me what am i doing wrong. I want to have JB. PLEASE HELP.
Thanks in advance.
Answer these questions: 1. Are you using A Hallon (a.k.a. Xperia Neo) or a Haida (a.k.a. Neo V) 2. Did you download the correct zip corresponding to your phone (Hallon/Haida) 3. In a previous ROM, was your phone listed as what it was not? (a.k.a. You're using a Hallon, but it is written as Haida) If you answered yes to the third question, then you need to reflash the stock ftf file. THEN flash the custom ROM. Pm me for more help
Jass5991 said: Answer these questions: 1. Are you using A Hallon (a.k.a. Xperia Neo) or a Haida (a.k.a. Neo V) 2. Did you download the correct zip corresponding to your phone (Hallon/Haida) 3. In a previous ROM, was your phone listed as what it was not? (a.k.a. You're using a Hallon, but it is written as Haida) If you answered yes to the third question, then you need to reflash the stock ftf file. THEN flash the custom ROM. Pm me for more help Click to expand... Click to collapse 1. Haida. i.e. (Neo V or MT11i). 2. Yes from here (http://code.google.com/p/freexperia/wiki/CyanogenMod10 THE FXP133 one) 3. Actually I could not understand this question. By the way currently I am on ICS 4.0.4 stock firmware with Base-band (=.72). This is what I see in my about phone (Attached Image below). Thanks again for the support. :good:
khurram.khu said:
Can anyone help PLEASE.
I am new to flashing custom ROMS and am having problem flashing this one FXP133 CM10.
The one given here: http://forum.xda-developers.com/showthread.php?t=1780329
I get following error while Flashing:
Code:
-- Installing: /sdcard/FXP133-cm-10-20120813-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-haida.zip
Opening update package...
Installing update...
script aborted:
assert failed: getprop("ro.product.device") == "MT11i" || getprop
("ro.build.product") == "MT11i" || getprop("ro.product.device") ==
"MT11a" || getprop("ro.build.product") == "MT11a" || getprop
("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
E:Error in /sdcard/FXP133-cm-10-20120813-haida.zip
(Status 7)
Installation aborted.
When on .42 (GB) stock firmware and Using MT11i NeoV.
In the Dev Thread I got following 2 replies:
AND
I tried both of them but still with no luck.
Now I am on ICS 4.0.4 with Baseband (.72) and have changed the updater-script and removed the lines (as suggested there) till.....
Code:
("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
But Now I am getting following error while flashing:
Code:
-- Installing: /sdcard/FXP133-cm-10-20120813-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-haida.zip
Opening update package...
Installing update...
(Status 7)
Installation aborted.
PLEASE tell me what am i doing wrong. I want to have JB. PLEASE HELP.
Thanks in advance.
Click to expand...
Click to collapse
Dud u flash the kernel first? Through fastboot! Use the boot.img from the zip! Then flash the main zip! Then wipe data, catche, dalvik catche! Reboot!
Should work if u have the right file for your phone!
Sent from My Xperia NeoV! Don't be a retard! Press the thanks button!
Alright. This build.prop error is easily fixed. First, flash a stock ROM. Then flash the kernel for the new rom in fastboot mode. Finally, flash the new rom through recovery. Flashing finished! Don't forget wipe everything, including battery stats
Jass5991 said: Alright. This build.prop error is easily fixed. First, flash a stock ROM. Then flash the kernel for the new rom in fastboot mode. Finally, flash the new rom through recovery. Flashing finished! Don't forget wipe everything, including battery stats Click to expand... Click to collapse Great! But battery stats are not necessary to wipe! Dalvik is! Sent from My Xperia NeoV! Don't be a retard! Press the thanks button!
Dev Jaskirat said: Great! But battery stats are not necessary to wipe! Dalvik is! Sent from My Xperia NeoV! Don't be a retard! Press the thanks button! Click to expand... Click to collapse I do it for safety
I tried to flash fxp134, but when I try to reboot, my phone just shows the fxp logo and then goes black. Yes, I did everything in fastboot, flash boot and reboot. Just goes black after that. Flashed back to CM9, and that goes all right. Went to recovery mode in CM9, wiped everything (data, cache, dalvik), rebooted, turned of the phone, went in fastboot mode. Tried fxp134 again, still the same thing. I've been searching fora ever since, but I'm not finding anything that can help me. Everybody seems to at least get to recovery mode. Anyone who can be of help?
Dev Jaskirat said: Dud u flash the kernel first? Through fastboot! Use the boot.img from the zip! Then flash the main zip! Then wipe data, catche, dalvik catche! Reboot! Should work if u have the right file for your phone! Sent from My Xperia NeoV! Don't be a retard! Press the thanks button! Click to expand... Click to collapse Jass5991 said: Alright. This build.prop error is easily fixed. First, flash a stock ROM. Then flash the kernel for the new rom in fastboot mode. Finally, flash the new rom through recovery. Flashing finished! Don't forget wipe everything, including battery stats Click to expand... Click to collapse I am currently on Stock ICS 4.0.4 so I guess I should start by flashing kernel (boot.img) first, then the ROM (.zip). RIGHT??? Earlier, I was flashing the ROM (.zip) first, which obviously failed. BUT this was originally mentioned in the FXP Thread. :fingers-crossed:Anyways, Thanks I will try and let you know the result.:fingers-crossed:
maybe the build.prop file is broken. these informations is stored in the build.prop file under /system folder in the zip of the rom.
Didn't work out Didn't work out that way either. Any other suggestions???
well. there can be either of two problems, or both (donno exactly).
1. updater file is broken. (status 7)
2. build.prop file is broken. getprop("ro.product.device")
OR BOTH.
rajxelton said:
well. there can be either of two problems, or both (donno exactly).
1. updater file is broken. (status 7)
2. build.prop file is broken. getprop("ro.product.device")
OR BOTH.
Click to expand...
Click to collapse
yeah, one thing that i tried in terminal emulator.
I executed the command:
Code:
getprop("ro.product.device")
and it returned
Code:
/system/bin/sh: syntax error: '"ro.product.device"' unexpected
However, when I executed:
Code:
getprop ro.product.device
it returned
Code:
MT11i
Can you provide a possible solution to this??
upload the META-INF folder which is inside the zip. and build.prop file which is in /system folder. I will see what can be done
rajxelton said: upload the META-INF folder which is inside the zip. and build.prop file which is in /system folder. I will see what can be done Click to expand... Click to collapse OK, Here is the asked files in the Attachment (check.zip)
GOTCHA!!
hey buddy!!
i had the same problem with installing cm 9 official, solution is very easy and it did work out for me, hell yeah i got it from xda, forgot the dev's name but all credits to him!!!
so i've uploaded your updater-script with changes which is causing all problems :highfive:
just removed these lines:
assert(getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" ||
getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" ||
getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida");
im not sure if you've edited your script in other ways, if my file does not work, take the stock updater-script from cm10 zip and remove them ^ till the ";"
:good:
any problems?
reply 'em!!
the_neo_v_guy said:
hey buddy!!
i had the same problem with installing cm 9 official, solution is very easy and it did work out for me, hell yeah i got it from xda, forgot the dev's name but all credits to him!!!
so i've uploaded your updater-script with changes which is causing all problems :highfive:
just removed these lines:
assert(getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" ||
getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" ||
getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida");
im not sure if you've edited your script in other ways, if my file does not work, take the stock updater-script from cm10 zip and remove them ^ till the ";"
:good:
any problems?
reply 'em!!
Click to expand...
Click to collapse
Hey buddy,
I have already tried this. You can see in my first post. I get following error:
khurram.khu said:
Code:
-- Installing: /sdcard/FXP133-cm-10-20120813-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-haida.zip
Opening update package...
Installing update...
synmlink: some symlinks failed
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
okay. here is the zip now. replace the files in their respective places. make sure to have a backup of originals. also make a nandroid backup before trying. i dont know if it'll work or not. cant test it on my own cause i dont have the rom. good luck.
rajxelton said: okay. here is the zip now. replace the files in their respective places. make sure to have a backup of originals. also make a nandroid backup before trying. i dont know if it'll work or not. cant test it on my own cause i dont have the rom. good luck. Click to expand... Click to collapse Ok. I will try it later today and tell you the result.:fingers-crossed:
Hey Everyone, :crying::crying: I have tried everything. Nothing works. Is there anything else that i can do. I have tried installing FXP-139, FXP-140, PolishBlood 4.1.1. In each of them I get same error. i.e. Status 7 error (assert failed) with the assert lines in the script. OR Status 7 error (synmlink: some symlinks failed) if i remove the assert lines from the script. I have been searching for solution of this issue from many days now. But to my disappointment Non of the solutions I found out works. PLEASE can anyone help PLEASE :crying:
[Q] Problem with updating hboot on my one s
I am having a problem with my phone, when I plug it into my computer my computer will not detect my phone
Computer:
Windows 7 with all the most up to date htc drivers and windows updates
Phone:
HTC One S ville (S4)
hboot - 1.14
Radio - 1.08
CWM - 6.0.3.1
CyanogenMod - 10.1-20130304 Experimental-ville-m2
I was told if I update to CM nightlys that it has a high chance to fix the problem, however when I install the nightly it aborts saying I need a newer version of hboot
Error Says:
-- Installing: /sdcard/clockworkmod/download/get.cm/get/jenkins/37986/cm-10.1-20130813-NIGHTLY-ville.zip
Finding update package...
I:Update location: /sdcard/clockworkmod/download/get.cm/get/jenkins/37986/cm-10.1-20130813-NIGHTLY-ville.zip
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000"
assert failed: getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" || getprop("ro.bootloader") ==
"2.13.0000"
E:Error in /sdcard/clockworkmod/download/get.cm/get/jenkins/37986/cm-10.1-20130813-NIGHTLY-ville.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/clockworkmod/download/get.cm/get/jenkins/37986/cm-10.1-20130813-NIGHTLY-ville.zip")
that's all well and good however in order to update my hboot I need to connect it to my computer based on reading many forums on the subject, so now can anyone please fill me in on a solution to the problem!
Thank You,
GunKartas
[Q] Problem Updating Hboot On My HTC ONE S
I am having a problem with my phone, when I plug it into my computer my computer will not detect my phone
Computer:
Windows 7 with all the most up to date htc drivers and windows updates
Phone:
HTC One S ville (S4)
hboot - 1.14
Radio - 1.08
CWM - 6.0.3.1
CyanogenMod - 10.1-20130304 Experimental-ville-m2
I was told if I update to CM nightlys that it has a high chance to fix the problem, however when I install the nightly it aborts saying I need a newer version of hboot
Error Says:
-- Installing: /sdcard/clockworkmod/download/get.cm/get/jenkins/37986/cm-10.1-20130813-NIGHTLY-ville.zip
Finding update package...
I:Update location: /sdcard/clockworkmod/download/get.cm/get/jenkins/37986/cm-10.1-20130813-NIGHTLY-ville.zip
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000"
assert failed: getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" || getprop("ro.bootloader") ==
"2.13.0000"
E:Error in /sdcard/clockworkmod/download/get.cm/get/jenkins/37986/cm-10.1-20130813-NIGHTLY-ville.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/clockworkmod/download/get.cm/get/jenkins/37986/cm-10.1-20130813-NIGHTLY-ville.zip")
that's all well and good however in order to update my hboot I need to connect it to my computer based on reading many forums on the subject, so now can anyone please fill me in on a solution to the problem!
Thank You,
GunKartas
Just to let you know: you posted in the forum for the one not the one s. Sent from my HTC One using xda app-developers app
oopse my bad ty
[Q] CM 10.1.3 stable aborts install
EDIT: I was able to get the GSM version of CM to install. I'm not sure why my ATT One is not the att version but oh well.
Hello,
I just got my HTC One and I'm running into a problem trying to install cm-10.1.3-m7att.zip from recovery. When I try to install I get the following:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "m7" ll getprop("ro.build.product") == "m7" ll
getprop("ro.product.device") == "m7att" ll getprop("ro.build.product") == "m7att"
E: Error in /data/media/CyanogenMod/cm-10.1.3-m7att.zip
(Status 7)
Installation aborted.
Any guidance would be appreciated. I'm going to try other builds now but wanted to get this out to see if someone had an idea as to what I can do to solve this. Any ideas? Thanks in advance!
-B
Edit the updater-script and remove the getprop lines. Sent from my One using XDA Premium 4 mobile app
[Q] zte nubia z5s mini MIUI OTA update fails on ro.product.device
I've zte nubia z5s mini with TWRP v. 2.6.3.0 and I installed MIUI V5 on it.
No OTA is able to update, and by reading on the matter, I found out about the build.prop file.
In my current file, I have the line:
Code:
ro.product.device=NX403A
However, the OTAs fail with:
Code:
script aborted: assert failed: getprop("ro.product.device") == "NX403A" ||
getprop("ro.build.product") == "NX403A"
assert failed: getprop("ro.product.device") == "NX403A" || getprop("ro.build.product") == "NX403A"
E:Error executing updater binary in zip
I tried fixing the permissions via Rom Toolbox light & also via TWRP, cleared Dalvik cache, and still, it fails with that message.
Is there anything I can put in the build.prop to fix this?
There are so many threads on the net about status 7. Does anyone know why this happens?