Related
Totally new issue now...every ROM I try to flash, I get an error when installing the zip in CWM saying something along the lines of
assert failed: getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" || getprop("ro.product.board") == "aries" || getprop("ro.product.device")) == "fascinate"
And continues to repeat that pattern of the first three using "fascinate", "fascinatemtd" and "SCH-I500"
What's the deal?
kaze06 said:
Totally new issue now...every ROM I try to flash, I get an error when installing the zip in CWM saying something along the lines of
assert failed: getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" || getprop("ro.product.board") == "aries" || getprop("ro.product.device")) == "fascinate"
And continues to repeat that pattern of the first three using "fascinate", "fascinatemtd" and "SCH-I500"
What's the deal?
Click to expand...
Click to collapse
a little more information would be helpful... what rom were you currently on and what rom are you trying to flash? Also what version of cwm are you using?
Personally, i strongly dislike CWM recovery. I recommend using Odin or Heimdall instead. They are a lot more straight forward. I tried to install CWM recovery and it was just a huge mess. Although I've never had a problem with odin
killerkiwiHD said:
Personally, i strongly dislike CWM recovery. I recommend using Odin or Heimdall instead. They are a lot more straight forward. I tried to install CWM recovery and it was just a huge mess. Although I've never had a problem with odin
Click to expand...
Click to collapse
Huh? The majority of roms out there need cwm to flash. You odin the appropiate recovery, three finger into cwm, wipe all three, then flash the zip. Thats how most roms work unless they are tar'd up, then you can flash in odin, but only a few are that way... pwgb, geewiz, and stock rom packages are odin compatible.
I had the same issue when trying to update my wife's phone today. Turned out I just needed to run an updated clockwork mod recovery.
Hi,
I tried installed ROM of CM9 from FXP116 version and I found the error message below when i installed the ROM from recovery mode. Any idea of this?
Installing update...
assert failed: getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/FXP116-update-cm-9.0.0-RC0-nozomi-UNOFFICIAL-signed.zip
(Status 7)
Installtion aborted
No files found.
Could anybody please suggest how to fix this? Now I couldn't boot in normal mode either.
Thanks.
Isnt it the case that there are no working roms atm?
You've broken your own system now so you need to reflash .73.
How to re-flash from the recovery mode now?
I have flashed with the recovery image and now struck in the recovery mode. Thanks.
ED1: I managed to resolve this already. Thanks
First of all, i searched but nothing close to mine..
i tried flashing paranoid android yesterday to try the rom and this came:
assert failed: getprop("ro.product.device") == "galaxys2" || getprop ("ro.build.product") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || getprop("ro.product.device") == "GT-I9100" and so on...... getprop("ro.product.device") == "GT-I9100M" and so on.......... getprop("ro.product.device") == "GT-I9100T" and so on.........
E:Error in emmc/zzzips/Modem......................
(status 7)
Installation aborted.
i factory reset and it worked..
i reverted back to my backup and this day i tried changing my modem and again (status 7) appeared again in which i cant flash the modem..
any solutions guys?
im on rootbox ics v1.7 and siyah v4.0
So no one else experienced this or have a clue??
Are you sure the ROM you downloaded is for your own device, the GT-I9100, and not for any other variant?
Sent from my GT-I9100 using xda app-developers app
The messages he is getting show that the install is checking to make sure it is an i9100, or an i9100 variant that is not the i9100G.
OP, are you sure you have an i9100 device?
yep im very sure..
first i tried flashing paranoid android v1.97 and then that message came for the first time..
i tried factory reset in recovery and i was able to flash paranoid android..
after which i restored my backup of rootbox v1.7 with siyah v4...
as usual all is good until the next morning in which i try to flash a different modem and the message came out again.. i tried flashing other modems too and it aborted..
and yes im very sure what i flash is for gt-i9100 and i alwasy double check it coz i dont have money to buy new phone or repair it if brick so im very careful..
Hey, guys. I'm one of the unfortunate lads that isn't able to unlock his bootloader. So I thought I'd give MIUI a try (2.8.10) since it claims to be able to flash on to lockedBL through CWM. So the problem is this, once the phone is rooted and in android 4.0.4 (for the right kernel) I go to CWM and follow the steps which should allow me to flash the rom (wiping cache, data, system etc.). However, the problem is this error right here,
"asset failed: getprop("ro.product.device") == "LT26i" | | getprop("ro.build.product") == "LT26i"
E: error in /sdcard/miuiandroid_LT26i-2.8.10.zip (status 7)
Installation aborted
No matter what I try, nothing gets rid of this error code. No one else is having this issue are they? I'm sick fed up of stock 4.0 on Sony, not optimised enough. Need a custom rom, especially since my bootloader is locked.
Thanks in advance for the help.
Can you install another cwm or it's the only recovery available for locked BL???
The problem is that the update script is made for another cwm.
Sent from my LT26i using Tapatalk 2
keewanchoapsss said:
Hey, guys. I'm one of the unfortunate lads that isn't able to unlock his bootloader. So I thought I'd give MIUI a try (2.8.10) since it claims to be able to flash on to lockedBL through CWM. So the problem is this, once the phone is rooted and in android 4.0.4 (for the right kernel) I go to CWM and follow the steps which should allow me to flash the rom (wiping cache, data, system etc.). However, the problem is this error right here,
"asset failed: getprop("ro.product.device") == "LT26i" | | getprop("ro.build.product") == "LT26i"
E: error in /sdcard/miuiandroid_LT26i-2.8.10.zip (status 7)
Installation aborted
No matter what I try, nothing gets rid of this error code. No one else is having this issue are they? I'm sick fed up of stock 4.0 on Sony, not optimised enough. Need a custom rom, especially since my bootloader is locked.
Thanks in advance for the help.
Click to expand...
Click to collapse
you can try 2 things:
1. in the CWM, choose mount -> format /system (careful) and then try flashing the rom or
2. open the zip file using 7zip, navigate to \META-INF\com\google\android\ folder edit "updater-script". remove assert(getprop("ro.product.device") == "LT26i" | | getprop("ro.build.product") == "LT26i" . You must use notepad++ for this
Sent from a neXus
I already tried your first suggestion and it failed on me horribly ha! So I guess I must have to try stage two thanks <3
edit: Right so I did your second suggestion and i had a different outcome, just simply says 'Installation aborted'. Any more ideas. I cant find another 'Locked Booloader' recovery.
Sent from my LT26i using xda premium
keewanchoapsss said:
I already tried your first suggestion and it failed on me horribly ha! So I guess I must have to try stage two thanks <3
edit: Right so I did your second suggestion and i had a different outcome, just simply says 'Installation aborted'. Any more ideas. I cant find another 'Locked Booloader' recovery.
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
I replaced update-script from older version of miui and it work for me ...
I had the same problem today after unsuccessfully trying to install CM 9.0.
Luckily I had the SSpeed Kernel and KA ROM on the internal storage, so after doing a wipe and cleanup dalvik, I was able to flash the Kernel and then the ROM
keewanchoapsss said:
Hey, guys. I'm one of the unfortunate lads that isn't able to unlock his bootloader. So I thought I'd give MIUI a try (2.8.10) since it claims to be able to flash on to lockedBL through CWM. So the problem is this, once the phone is rooted and in android 4.0.4 (for the right kernel) I go to CWM and follow the steps which should allow me to flash the rom (wiping cache, data, system etc.). However, the problem is this error right here,
"asset failed: getprop("ro.product.device") == "LT26i" | | getprop("ro.build.product") == "LT26i"
E: error in /sdcard/miuiandroid_LT26i-2.8.10.zip (status 7)
Installation aborted
No matter what I try, nothing gets rid of this error code. No one else is having this issue are they? I'm sick fed up of stock 4.0 on Sony, not optimised enough. Need a custom rom, especially since my bootloader is locked.
Thanks in advance for the help.
Click to expand...
Click to collapse
this happen to me too.i m not able to flash any version of CM9 rom now.i m running on unlock bootloader.anny idea?
o
Older CWM compatible?
gm007 said:
Can you install another cwm or it's the only recovery available for locked BL???
The problem is that the update script is made for another cwm.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
Which CWM version should work? How can you tell? I have 5.0.2.0, which is the latest for N1, but I can't flash MIUI.us_passion_v4.1_2.11.23_Eng_Deo_ZipA_Signed_0xD34D
I get a Status 7 abort error
Status 7 problem not solved!
I have a Sony Xperia LT22i (nypon). I had the stock version of jb by sony i.e., 6.2.A.1.100.
I have been trying to flash FXP233-cm-10 for xpeira p on my phone but the process has not been successfull.
the cwm recovery kernel alongwith the ROM is 6.0.2.8
I also have a cwm recovery kernel version 6.0.3.2
I successfully pushed the files into the sdcard but the installation from zip failed due to status 7.
The error shown is:
assert failed: getprop("ro.product.device") == "LT22i" || getprop("ro.build.product") == "LT22i" || getprop("ro.build.product") == "LT22i" || getprop("ro.product.device") == "LT22a" || getprop("ro.build.product") == "LT22a" || getprop("ro.product.device") == "nypon" || getprop("ro.build.product") == "nypon"
E:Error in /sdcard/update.zip
(Status 7)
Installtion aborted
I tried editing the updater-script & then running the installation but then the log shows:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
My current status of phone is:
Recovery= CWM v6.0.2.8
Wiped dalvik cache
Wiped system("I did that accidentally")
Factory reset also
I also have the zip file FXP228-cm-10 for xperia p
both of them use the same cwm version
when i tried installing it, it showed the same error as above
Please help
the kernel version that i've is 3.0.8-FXP-g9426a6e
Pkeshin said:
I have a Sony Xperia LT22i (nypon). I had the stock version of jb by sony i.e., 6.2.A.1.100.
I have been trying to flash FXP233-cm-10 for xpeira p on my phone but the process has not been successfull.
the cwm recovery kernel alongwith the ROM is 6.0.2.8
I also have a cwm recovery kernel version 6.0.3.2
I successfully pushed the files into the sdcard but the installation from zip failed due to status 7.
The error shown is:
assert failed: getprop("ro.product.device") == "LT22i" || getprop("ro.build.product") == "LT22i" || getprop("ro.build.product") == "LT22i" || getprop("ro.product.device") == "LT22a" || getprop("ro.build.product") == "LT22a" || getprop("ro.product.device") == "nypon" || getprop("ro.build.product") == "nypon"
E:Error in /sdcard/update.zip
(Status 7)
Installtion aborted
I tried editing the updater-script & then running the installation but then the log shows:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
My current status of phone is:
Recovery= CWM v6.0.2.8
Wiped dalvik cache
Wiped system("I did that accidentally")
Factory reset also
I also have the zip file FXP228-cm-10 for xperia p
both of them use the same cwm version
when i tried installing it, it showed the same error as above
Please help
the kernel version that i've is 3.0.8-FXP-g9426a6e
Click to expand...
Click to collapse
I'm curious, put a copy of the updater script on here please. . .
Nathan.7118391 said:
I'm curious, put a copy of the updater script on here please. . .
Click to expand...
Click to collapse
Actually i successfully completed the process bydoing the following:
i flashed the jb stock rom for xperia p again...
unlocked the bootloader again,
then copied the rom.zip & gapps.zip to sdcard,
flashed cwm v6.0.2.8 (provided with the rom),
flashed the zip files
& voila! everything worked fine....
though i still don't understand why it didn't install first 'coz, i followed the procedure to edit the 'updater-script' to the word....but nothing happened
guess i managed to get lucky a bit!
by now i've successfully flashed & tried the following roms:
FXP233 (cm10) ["THE BEST ON THE LIST"]
Pac man rom(based on cm10.1, pa, aokp) ["Buggy, can't install purchased apps, problems in installing apps on sdcard, bluetooth doesn't work, but overall customization, performance is pretty good, though i would've been glad if the devs had included some sort of inbuilt battery saver mode, like the battery stamina in stock jb roms for 2012(some models) & 2013 xperia series)
Revolution v33.4 (lagged a lot on my phone, hope someone else had a better time using this one)
Good for you! You have to be careful when dealing with scripts, its very easy to insert a space or forget to close quotes and it doesn't work. Format could have been amend instead of edify but that's provably not likely.
Sent from my LG-P769 using xda-developer's app. Hit thanks' cause it makes me feel good.
status 7 error
I m updating from MIUI version 4.2.23 to version 4.3.4 ota updat.
The error Msg says
Verifying current system.
Assert failed. apply patch check and bla bla bla... n then
error in sd card location and then
Status 7
Kindly help...
Hello everybody,
I always had CWM in the past, but after I flashed Omni-rom 4.4 i realized that it has TWRP 2.6.3.0 as recovery, anyway the problem is that I want to get back to cyanogenmod 10.2 but everytime i tried to flash the rom it failed, it happens also if i try to flash Dorimanx kernel, but nothing and the problem that used G2ROMNuke, to wipe all i needed so now I'm without OS at all. Someone can help me to solve the issue?
Thanks
Moae said:
Hello everybody,
I always had CWM in the past, but after I flashed Omni-rom 4.4 i realized that it has TWRP 2.6.3.0 as recovery, anyway the problem is that I want to get back to cyanogenmod 10.2 but everytime i tried to flash the rom it failed, it happens also if i try to flash Dorimanx kernel, but nothing and the problem that used G2ROMNuke, to wipe all i needed so now I'm without OS at all. Someone can help me to solve the issue?
Thanks
Click to expand...
Click to collapse
SOLVED!
Moae said:
SOLVED!
Click to expand...
Click to collapse
Actually the problem is not been solved, also with CWM I have now problem flashing several roms, the only one who works is Cyanogenmod 11, I'm trying to flashing Rootbox 4.2 and I get this error:
assert failed: getprop ("ro.product.device") =="galaxys2" || assert failed: getprop ("ro.build.device") =="galaxys2" || assert failed: getprop ("ro.product.device") =="i9100" || assert failed: getprop ("ro.build.device") =="i9100" || assert failed: getprop ("ro.product.device") =="GT-i9100" || assert failed: getprop ("ro.build.device") =="GT-i9100" etc....
Is still a recovery problem?
Moae said:
Actually the problem is not been solved, also with CWM I have now problem flashing several roms, the only one who works is Cyanogenmod 11, I'm trying to flashing Rootbox 4.2 and I get this error:
assert failed: getprop ("ro.product.device") =="galaxys2" || assert failed: getprop ("ro.build.device") =="galaxys2" || assert failed: getprop ("ro.product.device") =="i9100" || assert failed: getprop ("ro.build.device") =="i9100" || assert failed: getprop ("ro.product.device") =="GT-i9100" || assert failed: getprop ("ro.build.device") =="GT-i9100" etc....
Is still a recovery problem?
Click to expand...
Click to collapse
I dont think so. seems updater-script or build.prop problem.
assert command checks to make sure you are flashing ROM on correct device.
why dont you flash stock rom. It will reset your recovery to stock one then you can flash custom recovery as you did before
Nikhil said:
I dont think so. seems updater-script or build.prop problem.
assert command checks to make sure you are flashing ROM on correct device.
why dont you flash stock rom. It will reset your recovery to stock one then you can flash custom recovery as you did before
Click to expand...
Click to collapse
I forgot i had a NAND backup before all the mess, now I'm trying that way and let's see if it works .
Thanks for the help
Nikhil said:
I dont think so. seems updater-script or build.prop problem.
assert command checks to make sure you are flashing ROM on correct device.
why dont you flash stock rom. It will reset your recovery to stock one then you can flash custom recovery as you did before
Click to expand...
Click to collapse
I solved just restoring the Nandroid backup .