Related
Hi
I'm a noob, there we go I admit it
This is actually my first install of a new ROM on a Samsung Galaxy S2 (and in fact any device) and I'm stuck, I thought I'd followed all the instructions on the cyanogenmod wiki correctly but it appears that somewhere along the line I went awry!
I have rooted the device and successfully installed ClockworkMod Recovery v4.0.14. However, when I go to install Cyanogenmod 7.1 (update-cm-7.1.0-GalaxyS2-signed.zip) via the 'install zip from sdcard' I get the following error and the installation is aborted:
----------------------------------------
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") =="galaxys2" || getprop("ro.build.product") =="galaxys2" || getprop("ro.product.board") =="galaxys2" || getprop("ro.product.device") =="GT-I9100" || getprop("ro.build.product") =="GT-I9100" || getprop("ro.product.board") =="GT-I9100" || getprop("ro.product.device") =="GT-I9100M" || getprop("ro.build.product") =="GT-I9100M" || getprop("ro.product.board") =="GT-I9100M" || getprop("ro.product.device") =="GT-I9100T" || getprop("ro.build.product") =="GT-I9100T" || getprop("ro.product.board") =="GT-I9100T"
E:Error in /sdcard/update-cm-7.1.0-GalaxyS2-signed.zip
(Status 7)
Installation aborted.
----------------------------------------
I have tried to install a number of times with the same result.
There is no backup to a previous ROM so at the moment I seem to be as I said 'stuck'. I have tried installing other ROMs also and get the same result. Any help would be greatly appreciated!
Many thanks in advance!
open the updater script within the meta inf folder and remove the line (that should be the first action line) that includes:
getprop("ro.build.product")
Thanks very much for the reply!
I found the updater script file in the following directory 'update-cm-7.1.0-GalaxyS2-signed\META-INF\com\google\android', is that right?
The text within that file appears to just wrap so how much do I delete or do I simply delete 'getprop("ro.build.product") =="galaxys2" ||'
Sorry for all the questions and thanks for your help!
Also this could be caused by corrupted file. Check zip file size. Download again and try to flash.
I tried that and also another ROM (MIUI) but got exactly the same message
tigertim22 said:
Thanks very much for the reply!
I found the updater script file in the following directory 'update-cm-7.1.0-GalaxyS2-signed\META-INF\com\google\android', is that right?
The text within that file appears to just wrap so how much do I delete or do I simply delete 'getprop("ro.build.product") =="galaxys2" ||'
Sorry for all the questions and thanks for your help!
Click to expand...
Click to collapse
If you can't read the file correctly, I'd suggest you open it with a better editor (like Notepad++), there you won't have problems with encoding, wrapping or new lines.
EDIT: Its also possible that this updater script is not compatible with your CWM version (or as said before, the file is corrupted)
right, thanks again for everyones input, I've tried all of it, changing the CWM version to ClockworkMod 4.0.0.2, re-downloading the Cyanogenmod and removing the first line of the script updater file as suggested and it all either ends in the installation being aborted immediately or I get the same message (as in my initial post).
If I enable signature verification when I try and install, the process gets aborted whilst trying to verify the update package with the following error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Should I be doing something with the 'md5sum: ca096fd81a8a699d291ea12152a84137' displayed under the Cyanogenmod download link?
Is anyone able to help me...pleeeeease?
Thanks again guys!
Why are you trying flash cm if you see no luck? You can flash another rom. It's lot of them.
Well, I did it! I followed 078gregory's suggestion and tried another ROM, I wasn't convince it was going to work as I'd previously tried MIUI with the same result, but I thought what have I got to loose . I went for DarkyROM2_KI3_Base.zip and followed exactly the same installation process 'et voila'! it installed first time! I flashed it twice to be sure and rebooted the phone and was away!
Once I knew I could get a ROM on the phone, I (just for the hell of it) tried to install Cyanogenmod again and to my surprise it worked, it installed first time! The only thing I can think of is that the version of Clockworkmod that I was using initially was v4.0.1.2 and the version that got installed with DarkyROM was a later version so I guess more up-to-date. Incidentally the CWM version that installed with Cyanogenmod 7.1 was later still (v5.0.2.6).
Thanks so much to everyone that helped me!
Status 7 Installation aborted
Hello.I also had the same problem when i installed Biftor Rom V3.6. After installing this rom i have no chance to install CM 10.1 on my galaxy S2.After a few weeks i installed Revolt Rom and after that i tried to install CM 10.1,and it works.The only problem of this is the recovery i use. In Biftor Rom its the Philz recovery and the other roms have cwm-based recovery v6.0.2.3. I do evreything exactly the same way only with this recovery and it works. Hope can help anybody who had the same problem.(And with Philz recovery i also couldnt install Hellybean and Jellybam Rom,with cwm-based recovery it works).
error after status 7 error
Mr.Greg said:
Also this could be caused by corrupted file. Check zip file size. Download again and try to flash.
Click to expand...
Click to collapse
i followed suggestion for status error7 .. of deleting first 3 lines of updater script
after placing that updated zip file in sd card .
i again got error
installation update
installation aborted ..
i tried searching ,many links didnt got it .. pls help me from 4 days m stuck in it as i have
xperia mini pro sk17i
unlocked bootloader
rooted
cmw 5.0.2
thanks in advance
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
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 .
Help! Micromax unite 2 kkt flashng err! Assert failedwrite_raw_image("/tmp/boot.img")
While flashing a custom rom I received an error message stating assert failed: write_raw_image("/tmp/boot.img", "bootimg")
E:Error executing Updater binary in zip 'file location's
I am using twrp 2.8.1.0 to flash the ROM and I have wiped everything from system to data and cache. I don't have any king of backup thus in short my phone is stuck on recovery only. Even I tried to reboot after this error, but got only black screen. Please help!