Hi, I have been flashing nightlies since CM11 came out with no issues (maybe once a week, so quite a few times).. The version I currently have installed is 11-20140204. I have been just dirty flashing manually in CWM, installing from SD card / install ZIP.
For some reason I cannot update anymore ? Any of the new Nightly versions give me a STATUS 7 and to my knowledge nothing on my phone has changed ?
I have updated to the latest CWM - 6.0.4.7. and still wont work.
Here is the error I am getting :
Installing Update:
Assert failed:
getprop (“re.bootloader”) == “I747UCDMG2”
getprop (“re.bootloader”) == “I747UCUEMJ2”
getprop (“re.bootloader”) == “I747UCUEMJB”
getprop (“re.bootloader”) == “I747MVLDMF1”
getprop (“re.bootloader”) == “I747MVLUEMK5”
getprop (“re.bootloader”) == “I747MUMUEMK3”
E: Error in /data/media/0/cm-11-20140216-NIGHTLY-d2att.zip (STATUS 7)
Installation aborted.
Please help, Thanks
I was having the same problem and if you look around a little you can try editing the updater script.... There is a whole step by step tutorial somewhere in this forum. You have to unzip the ROM and edit the updater-script file but here is the link just copy and paste it, its a couple comments down and it has worked for a ton of people, I'm still having issues but its helped a ton of people to flash successfully.
http://forum.xda-developers.com/showthread.php?p=38880428
Is your bootloader included in the list of supported loaders?
Use TWRP instead.
Flash this, http://invisiblek.org/d2firmware.html
Format /cache, dalvik, /system, /data, and your internal SD card, then try again.
Sent from my SGH-I747 using Tapatalk
RJantu said:
Use TWRP instead.
Flash this, http://invisiblek.org/d2firmware.html
Format /cache, dalvik, /system, /data, and your internal SD card, then try again.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Won't formatting your internal SD card delete your nandroid backups if that's where your cwm stuff is? I'd like to find a solution for my issue to I have the new bootloader from 4.3 UCUEMJB and I successfully rooted it and installed philz cwm and removed Knox with the Knox remover zip and then I successfully flashed beanstalk 4.4.1 which I'm still running and with no issues......but I haven't been able to flash anything else.... So I was considering trying twrp because at first I was getting those errors then edited the updater scripts in the ROMs I was trying to flag just for it to abort installation again and not because of a status 7 error I think it said something about data/0 / volume or something crazy like that which is all foreign to me.
Related
Hi,
I'm having problems to install cm7 port. First of all, i would like to thanks Alquez by the great job he's done in this port.
And now, my problem. When i try to install cm7 from recovery, and after wipe data, cache and all, i select install from zip, and when start the proces i obtain this error message:
I've checked the zip md5sum, and i don't obtain the same result indicated by Alquez. I tried downloading the file several times, even downloading it from the different available servers, and I always get the same md5, being different to that indicated by Alquez.
I don't know what to do. Can anyone, that have the correct file, upload it to another server?. Or i'm doing anything wrong?
Thank you very much.
the error message
Sorry,
The error message is:
Installing update.....
assert failed: getprop("ro.product.device")=="marvel" ||getprop("ro.build.product")=="marvel" || getprop(ro.product.board") =="marvel"
E: Error in /sdcard..../update-cm-7.2.0.RC0....zip (Status 7)
What version of CWM do you use? Make sure you are using the version that alquez posted on development section
Sent from my A953
The md5sum of the current version (2011-12-16) doesn't match.
$ md5sum -c update-cm-7.2.0-RC0-marvel-KANG-signed.zip.md5
update-cm-7.2.0-RC0-marvel-KANG-signed.zip: FAILED
md5sum: WARNING: 1 computed checksum did NOT match
I'm using CWM version 3.2.0.1_xda.cn.
I'll try to install ClockworkMod Recovery v.5.0.2.6 and i'll try to flash CM7 port again.
Thanks for replies. I'll post the results of this try.
Problem solved
OK,
Finally I've could install CM7 on my wildfire s. The problem was at the CWM i was using.
I've installed the new version (5.0...) and the problem was solved.
Thank you all.
Sorry if my english is not very good.
Hi!
Every time I try to flash a rom through CWM it gives me this "E:Can't open sdcard/rom.zip (bad)" error. I thought it's because of a corrupt download, but I downloaded it again and again, and it still ain't working. I also tried different roms and zips, but always the same error.
I formatted my SD card. I actually did it three times. Still no luck.
I hope someone can help. Thanks.
ArmorD said:
Hi!
Every time I try to flash a rom through CWM it gives me this "E:Can't open sdcard/rom.zip (bad)" error. I thought it's because of a corrupt download, but I downloaded it again and again, and it still ain't working. I also tried different roms and zips, but always the same error.
I formatted my SD card. I actually did it three times. Still no luck.
I hope someone can help. Thanks.
Click to expand...
Click to collapse
i have found that "bad" generaly means a problem with the zip. what have you been trying to flash?
Pvy.
I hope it was the problem. But I have tried downloading the same file a couple of times and tried different zip files, but none of 'em works. Also I can't install zips through Rom Manager.
Ugh, now what it does is when I go to flash a zip file, it just stucks into the "Opening update package"... It does it on every rom I try to install, even with matching kernels...
ArmorD said:
Ugh, now what it does is when I go to flash a zip file, it just stucks into the "Opening update package"... It does it on every rom I try to install, even with matching kernels...
Click to expand...
Click to collapse
can you show me the zips also have you got a diff SDcard to try?
Pvy.
pvyParts said:
can you show me the zips also have you got a diff SDcard to try?
Pvy.
Click to expand...
Click to collapse
Unfortunately I have no spare card anymore...
I tried
http://forum.xda-developers.com/showthread.php?t=1515148
http://forum.xda-developers.com/showthread.php?t=1537717
http://forum.xda-developers.com/showthread.php?t=1308849
roms.
Great, now I can't even flash CM9 anymore. I think I've made helluva expensive book weight.
Did you format it with windows or via cwm?
sinkster said:
Did you format it with windows or via cwm?
Click to expand...
Click to collapse
I don't use Windows, but I formatted it with Ubuntu. And yes, I also formatted it with CWM(which wasn't a good idea)
Okay, now when I try to flash CM9 Nightly, I got this:
Code:
Installing update...
assert failed: getprop("ro.product.device") ==
"| | getprop(ro.product.device") == "LT18i"
a" assert failed: getprop("ro.product.device") ==
"| | getprop(ro.product.device") == "LT18i"
a" getprop("ro.product.device") == "LT15i" || getprop("ro.product.device) == "LT15a"
E:error in /sdcard/update-cm-9-20120404-NIGHTLY-anzu-signed.zip
[B](Status 7)[/B]
Installion aborted.
Geez...
Any way to restore phone to complete stock? I could start from a clean table...
Allright, got that one fixed. Just needed to erase "getprop" lines from roms updater-script.
Now my phone isn't a brick anymore Able to boot it to CM9. Still, can't flash any roms...
It's alive!
I don't know what I did exactly to get it work, but I think formatting SD card via CWM had something to do with it...
(and sorry for double posts)
Maybe you have formatted in nfts instead of fat32..
Sent from my LT18i using XDA Premium App
Anyone who knows a solution to this? It just appeared on my CWM screen as well out of nowhere. Didn't do anything in MGLDR menu for weeks but it just happened?
fixcho
I want to install custom rom but it shows me that error. Before 1 weak i install cm7 and naw i am with it. Naw i try to install megatron but error then i try void but again error I am with lg p500.
Hey all!
I have Korean LG SU640. When trying to install any rom, e.g. CM9, 9.1, 10, i have the same error:
assert failed: getprop ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640"
E: Error in/sdcard/cm-9.0.0-su640.zip
(status 7)
Installation aborted.
As I found, this error appears when you're trying to install rom from another device
Installation of ROMs from P930 goes ok, but wifi doen'ts works and screen oriebtation is wrong.
Tried to flash CWM for SU640 from here, but this didn't help.
Solution I found is to put into SU640 rom META-INF and system\build.prop from P930. Rom installed successfully and everything works.
However, making this manipulation for each update is quite annoying.
Does anybody knows how to make my phone 'think' he is SU640, not P930?
chukerer said:
Hey all!
I have Korean LG SU640. When trying to install any rom, e.g. CM9, 9.1, 10, i have the same error:
assert failed: getprop ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640"
E: Error in/sdcard/cm-9.0.0-su640.zip
(status 7)
Installation aborted.
As I found, this error appears when you're trying to install rom from another device
Installation of ROMs from P930 goes ok, but wifi doen'ts works and screen oriebtation is wrong.
Tried to flash CWM for SU640 from here, but this didn't help.
Solution I found is to put into SU640 rom META-INF and system\build.prop from P930. Rom installed successfully and everything works.
However, making this manipulation for each update is quite annoying.
Does anybody knows how to make my phone 'think' he is SU640, not P930?
Click to expand...
Click to collapse
All you need to do is go to CWM, select "Install zip from sdcard", then select "toggle script asserts" (so that the setting is disabled).
drumist said:
All you need to do is go to CWM, select "Install zip from sdcard", then select "toggle script asserts" (so that the setting is disabled).
Click to expand...
Click to collapse
Doesn't help. The same error
chukerer said:
Doesn't help. The same error
Click to expand...
Click to collapse
Solution found!
Download the latest recovery for LG Optimus LTE from http://www.clockworkmod.com/rommanager/.
Flash it with Android Terminal Emulator how it was described here
Reboot into recovery and install any rom for SU640.
The only problem is that Rom Manager still wants to flash recovery for P930
chukerer said:
Hey all!
I have Korean LG SU640. When trying to install any rom, e.g. CM9, 9.1, 10, i have the same error:
assert failed: getprop ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640"
E: Error in/sdcard/cm-9.0.0-su640.zip
(status 7)
Installation aborted.
As I found, this error appears when you're trying to install rom from another device
Installation of ROMs from P930 goes ok, but wifi doen'ts works and screen oriebtation is wrong.
Tried to flash CWM for SU640 from here, but this didn't help.
Solution I found is to put into SU640 rom META-INF and system\build.prop from P930. Rom installed successfully and everything works.
However, making this manipulation for each update is quite annoying.
Does anybody knows how to make my phone 'think' he is SU640, not P930?
Click to expand...
Click to collapse
It's really easy. what you need to is delete(
"ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640")of META-INF then pack and sign zip,this will work well.
Sent from my LG-SU640 using xda premium
flash recovery 6.0.1.2
Sent from my LG-SU640 using xda app-developers app
HELP!!!!!!
pxrphj said:
flash recovery 6.0.1.2
Sent from my LG-SU640 using xda app-developers app
Click to expand...
Click to collapse
I just flashed recovery 6.0.1.2 but it still error. I want to try flashing rom by deleting ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640") of META-INF, but I don't know how to do. Could you please help me? I want to flash custom rom.
Used to have this problem... but it was solved when I flashed cwm 6.0.1.4
http://me.zing.vn/apps/sharefile?params=/download/downloadfile/file/NzEzMys2NjAyMzkzMQ==
Sent from my LG-SU640
navik said:
It's really easy. what you need to is delete(
"ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640")of META-INF then pack and sign zip,this will work well.
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
Please can you tell me how to delete ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640")of META-INF
Some ROMs will give an error: "assert failed getprop(ro.product.device==SU640)" or something like that.
Open that ROM using Winrar, go to "META-INF\com\google\android " and open the file named "updater-script" and remove the first line and save.
On closing the text editor, winrar will ask you if you want to replace the edited file, click "Yes" or "OK" . and flash the ROM again. This time, it will work.
Ref: http://wiredsoup.blogspot.com/2013/02/lg-optimus-su640-comfirmed-working.html
TeamWin Recovery Project
Restore in the old 2.4.1 version doesnt work for me. I build from source, now it works, I share.
Download
http://dualhoki.vim.hu/bubor/dev/twrp-i927/
http://rpi.bubor.hu/bubor/dev/twrp-i927/
Current Issues:
display timeout blank screen disabled
Issue report:
Give everything I need to reproduce the problem (logs, guide, dumps etc), I wont reply useless reports.
Changelog:
Changelog can be found : http://www.teamw.in/project/twrp2
2.6.1 wipe data make smaller data partition, that need for encyption. Encypt mount support.
2.6.3 removed superuser, compiled with cm-10.2
2.6.3-2 add fuse, it should support extfat
2.6.3-3 remove encypt, puth superuser (Rooting)
2.6.3-4 put security fs, selinux, it will need for flash cm-11.0
2.6.3.1 update twrp from git (actually its 2.7.0, but you will see 2.6.3 in the corner)
2.7..1: update twrp, compiled with cm-10.2
2.8.4: compild with cm-11.0, fix MTP
Credit:
Terinfire(Source)
Dman(Source)
thegreatergood
TWRP TEAM
Install
Install zip from TWRP or ClockworkModRecovery
Put device to download mode ( power on, while hold volume up, hit volume up again when asked to do ), and use odin (included in the zip, browse to pda, dont flash other)
Changelog: http://www.teamw.in/project/twrp2
You may want to install older rom, you must change assert tag in rom zip file META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "i927" || getprop("ro.build.product") == "i927" ||
getprop("ro.product.device") == "SGH-I927" || getprop("ro.build.product") == "SGH-I927" ||
getprop("ro.product.device") == "SGH-I927R" || getprop("ro.build.product") == "SGH-I927R" ||
getprop("ro.product.device") == "SGHI927" || getprop("ro.build.product") == "SGHI927" ||
getprop("ro.product.device") == "SGHI927R" || getprop("ro.build.product") == "SGHI927R" ||
getprop("ro.product.device") == "n1" || getprop("ro.build.product") == "n1" || abort("This package is for \"i927,SGH-I927,SGH-I927R,SGHI927,SGHI927R,n1\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Awesome! Thanks so much for fixing this for Team Glide!
Sent from my Rooted Samsung SGH-i927 Captivate Glide
Running @ndroid JB4.2.2 CM10.1 & TWRP 2.4.4.0 using xda-dev app.
They just released a newer version 2.5.0.0
Sent from my Rooted Samsung SGH-i927 Captivate Glide
Running @ndroid JB4.2.2 & TWRP 2.4.4.0 using xda-dev app.
*thanks bubor for keeping twrp up to date.
*please keep twrp up to date since it can then use rom manager to do all the wipes, flash and install roms and gapps package an dother patches along he way.
*can the img extension just be use through adb to get that to the phone or not?
*how is this done and steps pleas?
dd if=recovery.img of=/dev/block/mmcblk0p8
You can find recovery.img inside the zip.
update to 2.6.1
Oh my...
I think this is one of the best finds for the Cappy Glide since CM10.1...
Thank you! Thanks SOOOOO MUCH!
I was about fed-up with CWMR, having to spam the volume buttons, but now with touch controls, I mean, COME ON! How much better could it get to flash and recover and restore and backup stuff! Thank you! BIG THUMBS UP!
:good::good::good::good::good:
great thanks, its time to udate it. i see we have a version from odin and one to flash via CWMR.
Initially got some strange "assert getprop" errors when flashing stock Samsung flashable packs (CWM does the job), but flashing CM and PAC looks alright. Just why does the stock flashables all require ro.product.device=SGHI927... (normally it would be SGH-I927)
Sent from Samsung Captivate Glide @ CM10.1.2
AndyYan said:
Initially got some strange "assert getprop" errors when flashing stock Samsung flashable packs (CWM does the job), but flashing CM and PAC looks alright. Just why does the stock flashables all require ro.product.device=SGHI927... (normally it would be SGH-I927)
Sent from Samsung Captivate Glide @ CM10.1.2
Click to expand...
Click to collapse
assert tag changed a year ago, old custom 4.0/4.1 doesnt work with newer recoveries.
New roms test both assert tags. You can change test in rom's zip file.
Well after upgrading to 2.6.3 I get fail to create directory & failed to backup? This is to either internal or external. On 2.6.1 I was getting fails to restore? Anyone else having these issues?
Sent from my Rooted Samsung SGH-i927 Captivate Glide Running Android ICS 4.0.4 LiteRom 0.9.0 & TWRP 2.6.3 using xda-dev app.
amppcguru said:
Well after upgrading to 2.6.3 I get fail to create directory & failed to backup? This is to either internal or external. On 2.6.1 I was getting fails to restore? Anyone else having these issues?
Sent from my Rooted Samsung SGH-i927 Captivate Glide Running Android ICS 4.0.4 LiteRom 0.9.0 & TWRP 2.6.3 using xda-dev app.
Click to expand...
Click to collapse
could you write detail? uploading /tmp/recovery.log helps lot.
I just made a backup and restore, and it works.
TWRP 2.6.3 bu failure
bubor said:
could you write detail? uploading /tmp/recovery.log helps lot.
I just made a backup and restore, and it works.
Click to expand...
Click to collapse
Hm I don't see a tmp folder in root or twrp. I did a search for all recovery.log files & only found the ones from 2.6.1 backups
I had to go back to 2.6.1 & got it to backup & restore.
I've attached one of those.
When trying using 2.6.3 it says it "Unable to create Folder: /external_sd/TWRP/..."
"Failed to make backup folder"
I am running TGG Literom 0.9.0
amppcguru said:
Hm I don't see a tmp folder in root or twrp. I did a search for all recovery.log files & only found the ones from 2.6.1 backups
I had to go back to 2.6.1 & got it to backup & restore.
I've attached one of those.
When trying using 2.6.3 it says it "Unable to create Folder: /external_sd/TWRP/..."
"Failed to make backup folder"
I am running TGG Literom 0.9.0
Click to expand...
Click to collapse
try to rename TWRP to TWRP2,and lets it creates new one.
2.6.3 backup unable to create folder
bubor said:
try to rename TWRP to TWRP2,and lets it creates new one.
Click to expand...
Click to collapse
I tried renaming them & reflashed 2.6.3 but still get the same error messages of it not being able to create backup folders? Very strange.... I could have sworn it was working the first time I flashed it? But now these repeated errors have me mystified?
Edit: I also tried redownloading 2.6.3 & reflashing but still getting the same error messages?
Ive had to reflash 2.6.1 & it works perfectly!
2.6.3
Doesn't seem capable of mounting 64gb exfat formatted SDXC card.
Just says failed to mount or something along those lines, mounted a 8gb FAT32 card, wouldn't mount an old FAT 512mb card.
I know for a fact the 2.6.1 is capable of mounting the 64gb exfat card. Flashed back to it and no issues.
amppcguru said:
I tried renaming them & reflashed 2.6.3 but still get the same error messages of it not being able to create backup folders? Very strange.... I could have sworn it was working the first time I flashed it? But now these repeated errors have me mystified?
Edit: I also tried redownloading 2.6.3 & reflashing but still getting the same error messages?
Ive had to reflash 2.6.1 & it works perfectly!
Click to expand...
Click to collapse
I had the same error, so i just downloaded nandroid backup from the play store, and it works wonders if you choose TWRP as your recovery.
Sent from my SGH-I927 using XDA Premium 4 mobile app
I also had the same problem, but with d2att - changed the auto generated backup name and it worked (also fixed permissions but not sure if it was necessary to or not).
bubor said:
assert tag changed a year ago, old custom 4.0/4.1 doesnt work with newer recoveries.
New roms test both assert tags. You can change test in rom's zip file.
Click to expand...
Click to collapse
Went to older recovery, still not able to flash.
WTF?
Sent from my SGHI927 using Tapatalk
Changing the auto-generated name fixed for me too.
I've been experiencing random reboots and audio issues with the nightly d2spr build from 5-14. There has been a few builds available to flash using the OTA push/pull function. Each new ROM fails to install however. I get an error:
"Assert failed getprop ("ro.bootloader") == L710VPBLJ7 (followed by other alphanumeric patterns)
Error in the nightly.zip (status 7).
Aborted."
I've had no issues updating in the past this way. FWIW, I am able to revert back to the 5-14 build which is saved in a cmupdater folder on my SD card. I can't recall doing anything new to the device except installing Faster Fix which replaces the gps.conf file with a different one to lock a signal faster.
For the newer nightlies you have to have the MD4 bootloader/modem.