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.
Hi All,
I am getting a status 7 error whwn I try to install any version of Cyanogenmod ROM on my device. The error log is as follows:
Installing: /sdcard/cm-10.0.0-i9100g.zip
Finding update package...
I:Update location: /sdcard/cm-10.0.0-i9100g.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "i9100g" || getprop("ro.build.product") == "i9100g" ||
getprop("ro.product.device") == "GT-I9100G" || getprop("ro.build.product") == "GT-I9100G"
assert failed: getprop("ro.product.device") == "i9100g" || getprop("ro.build.product") == "i9100g" || getprop("ro.product.device") == "GT-I9100G" || getprop("ro.build.product") == "GT-I9100G"
E:Error in /sdcard/cm-10.0.0-i9100g.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/cm-10.0.0-i9100g.zip")
I have tried different versions of CM ROMs like CM9, CM10 (for which I got the above error) and CM10.1 (monthly build)
The details of my phone are as follows:
Model: GT-I9100G
Android Version: 4.0.4
Baseband Version: I9100GDDLP7
Kernel Version: 3.0.8-I9100G-v1.0.2 [email protected] #3
Build Number: IMM76D.XXLPZ
I Googled to troubleshoot this problem but could not find anything. Please let me know a solution this problem.
Thanks in advance
Mudit
Flash a different kernel and try again.
Can you suggest a good ICS kernel for GT-I9100G? Basically, most of the kernels I am able to find are for gingerbread. There are certain versions which are for ICS but I have already faced problems with a kernel which in some forum was written to be for ICS but actually was for GB and I was able to get my phone running again only after replacing that kernel with my current kernel.
This is my first time rooting my phone and I really want to get this right
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
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
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?