Hello.
I updated TWRP from 2.8.7.0 to 3.0
But when I try to flash a custom Rom, I get error 7, telling me that flashing failed. I tried 2 different CM Roms and were using MIUI before. Backup and Restore files work. Someone knows what's wrong or how to fix it?
reinstall twrp, try older version
I had no problems with the old version. The error comes with 3.0. I already made my backup with 3.0 and I would like to use it in future.
What does that error mean? Maybe there is one option checked or unchecked that causes that? An I the only one with that problem?
gasperoni said:
I had no problems with the old version. The error comes with 3.0. I already made my backup with 3.0 and I would like to use it in future.
What does that error mean? Maybe there is one option checked or unchecked that causes that? An I the only one with that problem?
Click to expand...
Click to collapse
Have you untick the "zip signature verification"?
it was unchecked. I didn't do anything special but today it worked somehow. In the previous version of TWRP the programm asked me to install SuperSU if the device was not rooted. But in 3.0 it doesn't ask or install SuperSU. Someone knows how to do that?
You try full wide include internal card. Reboot and try again. Allow TWRP install SupperSu and mod system, it will ask when you reboot device next time.
I think I may have run into this error as well. See http://forum.xda-developers.com/redmi-note-2/help/issue-flashing-roms-aicp-rom-flashed-t3357783
Related
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
hozza94 said:
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
Click to expand...
Click to collapse
did you root your phone?
what rom are you actually using?
did you try to update Rom Manager to an earlier version?
I assume your phone is rooted already. Don't continue if it's not.
I thought there was an official one released for the phone. Are you using the newest version of ROM Manager?
If yes, and our phone model is still not listed, then you'll need to install Clockworkmod Recovery by following this thread:
http://forum.xda-developers.com/showthread.php?t=1151396
It involves downloading a program called ODIN. You need to flash (transfer) the Clockworkmod file to your phone through USB. It's all in the thread above.
I had the same problem - installing the latest Rom Manager (free version) from the store didn't have Galaxy5 listed as a ClockworkMod possibility.
I flashed the whole thing by hand with ODIN and installed CyanogenMod - and presto; the version supplied with it had Galaxy5 support and I had no problem doing the "read only partition" installation.
Rom Manager is pretty crappy anyway - I prefer manual installation over it...
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Rigardi said:
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Click to expand...
Click to collapse
Why did you say that??? If the phone is rooted you can download CWM by RomManager without fear.. the important is that when the popup with phones versions come up, you choose only - ONLY! - Galaxy 5 voice! If this voice is not present into the popup, don't choose nothing at all! Choosing another phone might brick yours!
I downloaded and installed and even only update CWM by RomManager a lot of times and everything was always fine! No problem at all!!
You cannot scare people for nothing: your problems are not bug or issues, but only YOUR problems! and YOUR errors!!!
So, boyz, don't worry installing CWM by RomManager.. but remember to choose only Galaxy 5 voice, no other phone, 'cause you could brick your phone selecting a CWM that is not compatible with our GT-I5500..
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Anyone please?
rozel said:
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Click to expand...
Click to collapse
You need root access to flash apps or modify your system
pasanjay said:
You need root access to flash apps or modify your system
Click to expand...
Click to collapse
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
rozel said:
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
Click to expand...
Click to collapse
u have to first flash the 'Temporary CWM recovery .zip' then select 'reboot to recovery' option in stock recovery to enter 'temporary cwm recovery' there u select the 'Camera zip file' to flash.
PS- after flashing 'Temporary CWM recovery.zip' do not reboot ur phone the normal way by doing so u will lose ur temporary recovery.
each time before flashing any zip file u have to flash 'temporary cwm.zip' file first.
Hi thanks but I know this.
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
rozel said:
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
Click to expand...
Click to collapse
As the error indicates, it fails to verify the file's signature. You can't flash unsigned packages via stock recovery. The solution is exactly what was already mentioned to you:either root and install a custom kernel/recovery (you don't want it, that's fine), or use a temporary custom (non-stock) recovery. While I had problems with the stock recovery flashing unsigned zips (obviously), I never had an issue with flashing a temp recovery. Try redownloading and reinstalling it - it could be a corrupt file. Which recovery are you trying to use? I recommend the temp touch CWM by Phil (the dev of the PhilZ kernel; use link in his signature). Always works like a charm.
kt-Froggy said:
Try redownloading and reinstalling it - it could be a corrupt file.
Click to expand...
Click to collapse
Nice one! Thank you
It must have been a duff file (temp touch CWM by Phil) as the one I just downloaded, installed without a problem. It was the very same program file but from a different source.
Just installed the 4.2 Camera too so now going to play
Thank you again
I have read all the instruction i can find on installing a custom ROM on Galaxy Tab 10.1 wifi, and once i get to the point of installing zip with ROM it fails. I dont know why its failing, and i think i am missing something. I have TWRP recovery installed and was trying to update with CM 10.1 or 11 but neither would work.
If someone could eith provide a detailed list of steps, i can see if i missed something or maybe someone else has encountered this problem and can advise. When i install from zip it tried so install and then an few seconds later is says failed and then i have to restore using NANDROID backup to have atleast a working tablet
Thanks for the help
Maybe you have an old version of TWRP. For cm11 you need version 2.6.3 or later.
imagn said:
I have read all the instruction i can find on installing a custom ROM on Galaxy Tab 10.1 wifi, and once i get to the point of installing zip with ROM it fails. I dont know why its failing, and i think i am missing something. I have TWRP recovery installed and was trying to update with CM 10.1 or 11 but neither would work.
If someone could eith provide a detailed list of steps, i can see if i missed something or maybe someone else has encountered this problem and can advise. When i install from zip it tried so install and then an few seconds later is says failed and then i have to restore using NANDROID backup to have atleast a working tablet
Thanks for the help
Click to expand...
Click to collapse
Try updating your twrp to a newer version for your tab. If that falis you could try using cwm. I've used it to install my roms including cm11 and other kitkat roms that supposedly require twrp without any errors.
Hi,
Now any application from Google me does not work ... I get an "Application been stopped."
By this, I can not run the part on the function of the system and I can not download or update the application.
I decided that I install the new ROM (Mokee), but Interestingly, during the installation of CWM appears "Instalation aborded Status 7".
I made all the steps of the Internet, which had to delete this mistake, but it did not help ...
I have a phone Huawei Ascend Y550-L01 (c8817d - code name).
I also have a CWM version 6.0.5.1.
I have granted root privileges (administrator)
Please, quick help, because the hard-purpose a phone in this way ...
Comb0 said:
Hi,
Now any application from Google me does not work ... I get an "Application been stopped."
By this, I can not run the part on the function of the system and I can not download or update the application.
I decided that I install the new ROM (Mokee), but Interestingly, during the installation of CWM appears "Instalation aborded Status 7".
I made all the steps of the Internet, which had to delete this mistake, but it did not help ...
I have a phone Huawei Ascend Y550-L01 (c8817d - code name).
I also have a CWM version 6.0.5.1.
I have granted root privileges (administrator)
Please, quick help, because the hard-purpose a phone in this way ...
Click to expand...
Click to collapse
I can tell you the status 7 error in recovery means you need to update the recovery to the newest version, that may be where your problem lies
Sent from my Nexus 5
ShapesBlue said:
I can tell you the status 7 error in recovery means you need to update the recovery to the newest version, that may be where your problem lies
Sent from my Nexus 5
Click to expand...
Click to collapse
For my phone is the latest version. Unless otherwise compatible with my device ... Anyone know if there is another version compatible with my phone?
Can I install the ROM .zip file from your computer?
Is there any other way to install the rom?
Comb0 said:
For my phone is the latest version. Unless otherwise compatible with my device ... Anyone know if there is another version compatible with my phone?
Can I install the ROM .zip file from your computer?
Is there any other way to install the rom?
Click to expand...
Click to collapse
Maybe try another recovery if cwm isn't working properly?
Sent from my Nexus 5
I have downloaded and tried to install several different ROMs on Vibrant T959 . I recently managed to get back to stock 2.1 ROM with ODIN and it works fine. As I understand it I need an older version of ClockworkMod so I have CWM 2.5.1.2 installed .
All attempts to flash a new ROM fail with "Error.....(Status 0) Installation aborted.
Maybe I am missing a step here? Do I need to go to 2.2 first?
Thanks.
Update.....
So I Found an older ROM I once installed it was "Bionics" looks like "Team Whiskey" which did install .
From there I was able to install ROM Manager and update Clockwork Recovery (Updated to 2.5.1.3) . When I tried to initiate a ROM flash from clockwork recovery The error was something like
This Package is for "vibrant.vibrantmtd.SGH-T959" devicethis is a "".
I also notice that google play simply calls this device "phone" , but there is no SIM installed and could the lack of SIM cause any of this?
I have old EFS backups of both locked and unlocked states but I thought this was just IMEI . The IMEI does appear to be intact.
I think the vibrant has an identity crisis
markosjal said:
Update.....
So I Found an older ROM I once installed it was "Bionics" looks like "Team Whiskey" which did install .
From there I was able to install ROM Manager and update Clockwork Recovery (Updated to 2.5.1.3) . When I tried to initiate a ROM flash from clockwork recovery The error was something like
This Package is for "vibrant.vibrantmtd.SGH-T959" devicethis is a "".
I also notice that google play simply calls this device "phone" , but there is no SIM installed and could the lack of SIM cause any of this?
I have old EFS backups of both locked and unlocked states but I thought this was just IMEI . The IMEI does appear to be intact.
I think the vibrant has an identity crisis
Click to expand...
Click to collapse
you might check the build.prop in your/system folder and see what it shows as the device name next to ro.product.model=
some roms change it to i9000 which would not pass the check some flashable zips have to make sure you are flashing them on the right phone.
or in this case it might even be blank or have some odd characters which would cause no name to display.
I would try re-flashing the rom which should replace the build.prop with a clean copy from that rom and then try to flash the new rom.
if that doesn't work it can be edited but I would only do that as a last resort.
on a side note error 0 means the wrong update script type was used (Amend or Edify)
Amend is the older one and Edify the newer.
you either needed a newer or older version of clockworkmod or a rom that used the other type of script.
I know you got that part fixed already by chance but I thought it might help to know what happened just in case it comes up again.
Actually i worked this out , although thanks for the reply. your reply prompted me to post my findings here to help the next poor sap with the same issue.
I installed a bunch of useless efs backup and restore apps which none would work with the efs backup I had previously made . I then installed the original galaxy s unlock app which did restore the efs backup.
Apparently the efs partition was buggered . I had several different backups and found the original locked efs then unlocked it.
I now have omni ROM 5.1.1 installed on my vibrant.
BTW if you install omni ROM 5.1.1 the recommended Google apps packages do not install, but I found another package that did install and also do not use the launcher in omni ROM (launcher 3 ?) It is buggy. The Google launcher was in the Google apps package I installed and it is far better than the omni ROM bundled launcher. I can not say that I like either of them however the seem so ordinary.