Hi,
I just noticed this was ready to download on my phone today. I downloaded and went to install, but the ClockWordMod Recovery doesn't let me install the update saying, "Image Verification Failed". I assume the problem is that the phone is rooted, and searching through the forums I heard this update isn't really anything big, just removing some German apps or something.
Is there anyway I can stop this update from notifying me? Or anyway to install? My phone is rooted but I'm not bothered about keeping it rooted as at the moment, there is nothing I need the phone to be rooted for. So, either way is fine for me.
Thanks!
If you want to unroot it, just flash generic ruu, more info here http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
Than simply check for updates and update it
Or wait for few hours for rooted version of this rom
Hi!
I have a branded Desire and installed the update via Recovery. I had to disable the verification to do that (Goldcard inside). But all I got was a boot loop and my phone was derooted. I tried much (e.g. delete my data) and after a couple of hours I found the simple solution: Simply install the update again. Then I rooted my phone and restored the NANDROID Backup I made before I started the update because all of my data was gone.
Then I installed the Update again and this time it worked at the first time. All data was still there. I rooted it again and everything is fine. Don't know why my phone got a boot loop after first try but second try was perfect!
My suggestion: copy the zip from the download folder to the SDcard (made to a Goldcard!!!!) root and to the PC. Just if you need it more than once. Then make a Backup in the Bootloader. Then Install the update via Recovery. If anything goes wrong install the update again!
So I've been trying to fix this problem for about 6 hours now and still no luck.
I am very new to this stuff which is probably why I made the mistake. Basically I was trying to install CyanogenMod 10 custom ROM on my phone and I kept receiving this "status 7 error" I did some research on how to fix that, and that's when the problem occurred.
I read that I should clear my Dalvik cache, /system, and do a factory settings wipe. I did all that, continued to get the error, and when I rebooted I was stuck on the boot screen, my theory is that it had something to do with the clearing of the /system, but I don't know.
I can still get into download mode and into the CW recovery, but that's about it. I tried flashing the stock firmware through Odin, but the firmware I downloaded is just a .zip, and there is not .tar when you extract it, so I cant use Odin. I am at a total loss here, please help me.
Thanks a lot in advance.
Have you tried re-downloading the ROM, and flashing the new zip? Your current zip may be corrupt.
LordDiabeetus said:
Have you tried re-downloading the ROM, and flashing the new zip? Your current zip may be corrupt.
Click to expand...
Click to collapse
Where would I download the zip to? I can only access the files that are on my phone through CW. I cannot or at least I do not know how to transfer files to my phone in its current state.
Thanks for the reply.
apolanco115 said:
Where would I download the zip to? I can only access the files that are on my phone through CW. I cannot or at least I do not know how to transfer files to my phone in its current state.
Thanks for the reply.
Click to expand...
Click to collapse
Do you have a spare MicroSD laying around? Use that, if your computer has an SD slot. If you don't have a MicroSD with the adapter to plug it into a normal SD slot, you can find cheap 2 GB ones with an adapter on the cheap. If your computer doesn't has an SD slot, and you have no external tools, the ADB may be able to help you, or you could find an adapter. Simply re-download the zip (or a zip for a different ROM) on the computer, and move it to the external SD. Stick said MicroSD into your phone. When you choose to install a zip in the recovery, there should be an option to choose from an external SD, if it mounted correctly.
LordDiabeetus said:
Do you have a spare MicroSD laying around? Use that, if your computer has an SD slot. If you don't have a MicroSD with the adapter to plug it into a normal SD slot, you can find cheap 2 GB ones with an adapter on the cheap. If your computer doesn't has an SD slot, and you have no external tools, the ADB may be able to help you, or you could find an adapter. Simply re-download the zip (or a zip for a different ROM) on the computer, and move it to the external SD. Stick said MicroSD into your phone. When you choose to install a zip in the recovery, there should be an option to choose from an external SD, if it mounted correctly.
Click to expand...
Click to collapse
I will try that right now, thank you!
apolanco115 said:
I will try that right now, thank you!
Click to expand...
Click to collapse
Did it work out for you?
LordDiabeetus said:
Did it work out for you?
Click to expand...
Click to collapse
I'm backing up the stuff on my SD and formatting to FAT32. It's taking a while, but It's almost done.
apolanco115 said:
I'm backing up the stuff on my SD and formatting to FAT32. It's taking a while, but It's almost done.
Click to expand...
Click to collapse
Alright. Let me know if it works for you. If reflashing the other ROM doesn't work, try another one.
Personally, I would recommend CyanogenMod 10.1.
LordDiabeetus said:
Did it work out for you?
Click to expand...
Click to collapse
When I tried this, It said
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Erro in /sdcard/SGH-T999_T999UVDLI8-OTA-T999UVALH2_TMB_341017054.zip
(Status 7)
Installation aborted.
How do I fix this?
apolanco115 said:
When I tried this, It said
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Erro in /sdcard/SGH-T999_T999UVDLI8-OTA-T999UVALH2_TMB_341017054.zip
(Status 7)
Installation aborted.
How do I fix this?
Click to expand...
Click to collapse
Seems like that certain ROM is broken. The build.prop file is missing. This is an important file, and it holds data about your phones model, ect. Try flashing a different ROM.
LordDiabeetus said:
Seems like that certain ROM is broken. The build.prop file is missing. This is an important file, and it holds data about your phones model, ect. Try flashing a different ROM.
Which is odd seeing as it is CyanogenMod. Never had a problem with it. Is this CM 10 stable, or a CM 10 nightly?
Click to expand...
Click to collapse
I was trying to install the stock firmware before now I tried a different rom, CyanogenMod 10.1 nightly, and I'm getting
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == "d2tmo"
E: Error in /sdcard/cm-10.1-20121224-NIGHTLY-d2tm0.zip
(Status 7)
Installation aborted.
apolanco115 said:
I was trying to install the stock firmware before now I tried a different rom, CyanogenMod 10.1 nightly, and I'm getting
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == "d2tmo"
E: Error in /sdcard/cm-10.1-20121224-NIGHTLY-d2tm0.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Uh, it seems like your build.prop is missing or corrupt.
Try using Odin again, and flash the stock from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
That's the last I can think of. Good luck.
LordDiabeetus said:
Uh, it seems like your build.prop is missing or corrupt.
Try using Odin again, and flash the stock from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
That's the last I can think of. Good luck.
Click to expand...
Click to collapse
Thank you so much for your help. A website like was precisely what I spent about 3 hours looking for. I was able to flash the stock back on and now my phone boots normally thank you once again.
No problem man, glad to help! From now on, make sure you make a backup before you flash, either from recovery, or another app, or from your desktop!
Sent from my SGH-T999 using xda app-developers app
Same Exact Issue
Hey there, I'm having the same exact issue with the same phone.
I have a Galaxy S3 T999 and I'm stuck at my stuck at the Samsung start up screen. I rooted my phone today and I'm not really having trouble understanding all of this, but I am new to it.
Everything was going fine until I decided to try and install a new rom to my phone.
I installed Titanium Back-up and ROM Manager/Recovery mode (whatever it's called)
[[sorry for not being that detailed -for my situation is exactly like the one before me so I'm sparring every detail and I'd just be repeating everything above]]
After researching for hours and following every step, I ended up getting an error (the same as his) Error 7 or something like that when trying to install new rom (It was a Pac Rom version and I really expected it to work) and now the only thing I can do with my phone is go into download mode and recovery mode...
Being cautious that something like this would happen I backed up my whole phone's state with the recovery app but OF COURSE that didn't work because when I try to restore/backup, I get a md5 mismatch.... (and when I researched that, many people had the same 'mismatch error' when trying to restore last rom but the only way of fixing that is renaming and/or deleting some files in my phone -which I cannot access due to the lack of function after the start up screen...)
I really just want any rom to work at this point, I haven't been this frustrated in a long time.
I researched everything before taking every step but apparently staying up all night until 10 a.m. the next day doing what I thought was "Backing Up" my phone so nothing went wrong was a COMPLETE waste of time because EVERYTHING went wrong. :good:
Please HELP
(I don't have extra sd card, can't I just use the sd card I already have....)
Oh, and now my phone won't even turn on
it being dead is probably the most likely cause but for some reason it's not charging plugged up to my computer or wall charger....
what now????
kayrealist said:
Hey there, I'm having the same exact issue with the same phone.
I have a Galaxy S3 T999 and I'm stuck at my stuck at the Samsung start up screen. I rooted my phone today and I'm not really having trouble understanding all of this, but I am new to it.
Everything was going fine until I decided to try and install a new rom to my phone.
I installed Titanium Back-up and ROM Manager/Recovery mode (whatever it's called)
[[sorry for not being that detailed -for my situation is exactly like the one before me so I'm sparring every detail and I'd just be repeating everything above]]
After researching for hours and following every step, I ended up getting an error (the same as his) Error 7 or something like that when trying to install new rom (It was a Pac Rom version and I really expected it to work) and now the only thing I can do with my phone is go into download mode and recovery mode...
Being cautious that something like this would happen I backed up my whole phone's state with the recovery app but OF COURSE that didn't work because when I try to restore/backup, I get a md5 mismatch.... (and when I researched that, many people had the same 'mismatch error' when trying to restore last rom but the only way of fixing that is renaming and/or deleting some files in my phone -which I cannot access due to the lack of function after the start up screen...)
I really just want any rom to work at this point, I haven't been this frustrated in a long time.
I researched everything before taking every step but apparently staying up all night until 10 a.m. the next day doing what I thought was "Backing Up" my phone so nothing went wrong was a COMPLETE waste of time because EVERYTHING went wrong. :good:
Please HELP
(I don't have extra sd card, can't I just use the sd card I already have....)
Click to expand...
Click to collapse
So what I did was I used the link above your post to download a rom that I could flash with Odin and that worked. This was the link btw http://forum.xda-developers.com/showthread.php?t=1949687
Hello,
from here: http://forum.xda-developers.com/showthread.php?t=2642605
Exciting new ROM I wanted to try but when I try to install it through CWM it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/aosb_kk_1.2.8_vision.zip
(status 7)
Installation aborted
The install instructions, step 2, specifically mentions update recovery, and googling for this error suggests that that solved it for others, but I have the latest CWM for the G2/Desire Z: I've tried both 5.0.2.7 and 5.8.1.0, non-touch and touch. There's no where else to upgrade to, unless I'm being completely obtuse. I've tried redownloading the zip to make sure it wasn't corrupted or anything, I've formatted my system and data partitions, all the usual stuff I could think of.
Can anyone provide a little bit of assistance? I've specifically got the G2, not Desire Z, but I don't think that's made a difference in the past but it's been a while since there was a new ROM I wanted to try so I'm probably forgetting something. What about this TWRP I've read about? First try couldn't get it to work but if I did get it to work think that might let me finish the install?
Thanks!
Yes, we'll go with "obtuse". I found the developer thread with a much more up to date CWM. Pity that only such an old version is available through official channels.
Thanks.
Every time I try to install the [ROM][Official][4.4+]CandyKat Rom[2/5/14] I keep getting the Status 7 error whenever attempting to use CWM to flash the rom. I'm running stock rooted and unlocked on the E980. I'm not a novice, I've done this many times before but this one is stumping me. Tried multiple mirrors as well. I'd post this directly on the CandyKat rom post but I lost my previous username and had to recreate it so I don't have the ability as of yet. Anyone have any ideas as to how to fix this?
The exact message is as follows:
Welcome to the New World!
--Installing: /sdcard/CandyKat-4.4.240-20140205-e980.zip
Finding update package...
Opening update package...
Installing update...
This package is for "e986,e980,geefhd,e988,gkatt" devices; this is a "vu2kt".
E:Error in /sdcard/CandyKat-4.4.240-20140205-e980.zip
(Status 7)
Installation aborted.
Update:
Just tried flashing a different ROM and had the same error with the same message. I have a feeling it is because the device is reading as a vu2kt, whatever that is. I'm going to try to reflash the recovery and try again.
Update2:
I reflashed CWM recovery and that did the trick. For some reason the version I had flashed was giving off the wrong device id and prompting an abort.
Problem solved.
Havent updated the phone for months, cause it failed when i installed the update below.
current version. 12_140605
The version i try to install 006_140625
tryed to reset the phone and all but dident work, and never rooted it.
then today i wanted to try local update, so i downloaded and transfers this file to SD card
http://www.oppoforums.com/threads/find-7a-find-7-stable-coloros-v1-2-5i.19757/
and used this guide
http://www.oppoforums.com/threads/how-to-flash-firmware-using-recovery-mode.10894/
I wiped data and cache. tryed to install the the new OS but the messasge "Installation failed".
what should i do now. btw im not a ****ing phone genius.
hope you can help me out..
dannyb9293 said:
Havent updated the phone for months, cause it failed when i installed the update below.
current version. 12_140605
The version i try to install 006_140625
tryed to reset the phone and all but dident work, and never rooted it.
then today i wanted to try local update, so i downloaded and transfers this file to SD card
http://www.oppoforums.com/threads/find-7a-find-7-stable-coloros-v1-2-5i.19757/
and used this guide
http://www.oppoforums.com/threads/how-to-flash-firmware-using-recovery-mode.10894/
I wiped data and cache. tryed to install the the new OS but the messasge "Installation failed".
what should i do now. btw im not a ****ing phone genius.
hope you can help me out..
Click to expand...
Click to collapse
Did you at any point change recoveries?