Hello,
I am a recent smartphone user and I did what good friends told me to do. So I rooted my phone and installed CWM recovery in order to change the bootloader and the logo. Not important changes but only to change the background of the logo and bootloader from white to black.
I haven't installed any ROM.
My phone is a ZOPO C3 - Android 4.2.1
SuperSU, MobileUncle and Root Explorer apps installed
Since a few days I have an "upgrade 1" available in the update system app. The upgrade is called "untrusted.zip.
When I try to install this upgrade, I get an error message at the bottom of the screen. Here the complete message:
"CWM-based recovery v.6.3.0.2"
"E: invalid command argument"
"Finding update package..."
"Opening update package..."
"Verifying update package..."
"E: signature verification failed"
Then I click to install "untrusted.zip" and the following is added to the message:
"Installing update..."
"Flashing logo..."
"Patched"
"Now you can reboot your phone".
After reboot the phone, the upgrade is still available. It seem not to have been applied.
Any idea what I missed please ?
as it says signature verification is failed hence the update was not installed
before selecting zip change the verification check in cwm-install zip from- here
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
stadeverois said:
Hello,
I am a recent smartphone user and I did what good friends told me to do. So I rooted my phone and installed CWM recovery in order to change the bootloader and the logo. Not important changes but only to change the background of the logo and bootloader from white to black.
I haven't installed any ROM.
My phone is a ZOPO C3 - Android 4.2.1
SuperSU, MobileUncle and Root Explorer apps installed
Since a few days I have an "upgrade 1" available in the update system app. The upgrade is called "untrusted.zip.
When I try to install this upgrade, I get an error message at the bottom of the screen. Here the complete message:
"CWM-based recovery v.6.3.0.2"
"E: invalid command argument"
"Finding update package..."
"Opening update package..."
"Verifying update package..."
"E: signature verification failed"
Then I click to install "untrusted.zip" and the following is added to the message:
"Installing update..."
"Flashing logo..."
"Patched"
"Now you can reboot your phone".
After reboot the phone, the upgrade is still available. It seem not to have been applied.
Any idea what I missed please ?
Click to expand...
Click to collapse
one more thing I forgot
if it is a phone upgrade then it wont work with root you have to try any temporary unroot for installing that
sangalaxy said:
as it says signature verification is failed hence the update was not installed
before selecting zip change the verification check in cwm-install zip from- here
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
one more thing I forgot
if it is a phone upgrade then it wont work with root you have to try any temporary unroot for installing that
Click to expand...
Click to collapse
Thank you for your reply sangalaxy !
As I told in my message, I am a recent user and Android is new for me (I just left my old GSM for a few weeks ).
Sorry if my question seem to be so stupid but how/where can I check in my CWM-install and how to temporary unroot ?
Thanks for your support
stadeverois said:
Thank you for your reply sangalaxy !
As I told in my message, I am a recent user and Android is new for me (I just left my old GSM for a few weeks ).
Sorry if my question seem to be so stupid but how/where can I check in my CWM-install and how to temporary unroot ?
Thanks for your support
Click to expand...
Click to collapse
for temporary unroot there are some apps even superuser has this option search google
for the check in cwm I don't remember correctly but in cwm home when you choose zip from sd there are 4 options
1 choose zip from sd
2 blah blah
in these 4 options there is one with verified option check that
sangalaxy said:
for temporary unroot there are some apps even superuser has this option search google
for the check in cwm I don't remember correctly but in cwm home when you choose zip from sd there are 4 options
1 choose zip from sd
2 blah blah
in these 4 options there is one with verified option check that
Click to expand...
Click to collapse
I found the way to unroot via SuperSu but I have a problem for the rest. I can only start in recovery mode via MobileUncle Tools (Vol (+) + Power doesn't work) and if I do that, I don't see anywhere an option to check in. Only install ZIP file is allowed. May be it not that way you mean but sorry again I'm a beginner :silly:
stadeverois said:
I found the way to unroot via SuperSu but I have a problem for the rest. I can only start in recovery mode via MobileUncle Tools (Vol (+) + Power doesn't work) and if I do that, I don't see anywhere an option to check in. Only install ZIP file is allowed. May be it not that way you mean but sorry again I'm a beginner :silly:
Click to expand...
Click to collapse
do you have a cwm zip for your phone if yes install that zip from recovery it will give you options
and if you are temporary unrooted check again with that update zip
Cershma suji
sangalaxy said:
do you have a cwm zip for your phone if yes install that zip from recovery it will give you options
and if you are temporary unrooted check again with that update zip
Click to expand...
Click to collapse
I don't have a cwm zip (my cwm recovery file was an IMG file) and if I'm temporary unrootet, after applying the Upgrade file, it is still the same situation: after reboot, the upgrade is still there.
stadeverois said:
I don't have a cwm zip (my cwm recovery file was an IMG file) and if I'm temporary unrootet, after applying the Upgrade file, it is still the same situation: after reboot, the upgrade is still there.
Click to expand...
Click to collapse
Idk what to do friend may be you have to unroot or leave the update
Sent from my GT-S6102 using xda app-developers app
Related
Okay xda, I'm in a bit of a pickle here. Last night I tried to flash the Siyah kernel, Siyah-s3-v1.9.1.tar using Odin3 v3.09 on my Galaxy S3 which was currently running Android 4.4.2 on Slimkat, with stock everything else. As soon as I tried this I knew it was completely the wrong thing and knew something was going to go wrong. Sure enough, the Siyah splash screen comes on for a couple of seconds, then goes to a black screen and gets stuck there.
At this point all I can do is watch it do a couple of seconds of the splash screen, put it into Download mode, or put it into recovery mode. The first time I tried recovery mode it was the CWM recovery, but I can no longer get this to happen, so I'm stuck with stock recovery. When just plugged in my phone has a red LED, and the battery status screen you get when you start charging a turned off phone comes up.
I read a guide on here about how to fix a failed flashing with Odin (I forget which one), which led me to flashing I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 I believe, or if that's not it the stock Samsung firmware. So that goes down, and now I get stuck in the stock Samsung bootloader.
I've since tried to flash a .zip of Stock samsung firmware and Cyanogenmod 11 with another phone's SD card (which I no longer have access to), to no avail. At least that hasn't made it any worse.
What should I do? Ideally I want to get my phone back without losing any data, but I feel a reset may be the only way. Eventually, I want to be able to use it on Cyanogenmod11 with the Boeffla kernel.
Thanks!
Do you get any error messages in stock recovery?
ArkThompson said:
Do you get any error messages in stock recovery?
Click to expand...
Click to collapse
When I first get into it it says on the bottom
# MANUAL MODE #
-- Applying Multi-CSC....
Applied the CSC-code : BIU
Successfully applied multu-CSC.
Which I assume is normal. I can't check again, but I did get an error while flashing CM11 which went very similarly to
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
I can't flash .zip files from External Storage at the moment, so other suggestions would be preferred.
I did try converting .zip files into .tar files with 7z but I don't think it was successful.
Obesidia said:
When I first get into it it says on the bottom
# MANUAL MODE #
-- Applying Multi-CSC....
Applied the CSC-code : BIU
Successfully applied multu-CSC.
Which I assume is normal. I can't check again, but I did get an error while flashing CM11 which went very similarly to
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
I can't flash .zip files from External Storage at the moment, so other suggestions would be preferred.
I did try converting .zip files into .tar files with 7z but I don't think it was successful.
Click to expand...
Click to collapse
You're trying to flash custom ROMs in the stock recovery?
ArkThompson said:
You're trying to flash custom ROMs in the stock recovery?
Click to expand...
Click to collapse
Pretty much, yeah, I was trying anything.
What next?
Obesidia said:
Pretty much, yeah, I was trying anything.
What next?
Click to expand...
Click to collapse
You need a custom recovery to flash custom ROMs. You could try flashing one in Odin and then flashing a stock ROM .zip using the recovery.
ArkThompson said:
You need a custom recovery to flash custom ROMs. You could try flashing one in Odin and then flashing a stock ROM .zip using the recovery.
Click to expand...
Click to collapse
I'll try that, but how do I get the .zip file in the right place to install from SD Card?
Obesidia said:
I'll try that, but how do I get the .zip file in the right place to install from SD Card?
Click to expand...
Click to collapse
Use ADB (USB debugging is enabled by default in custom recoveries).
ArkThompson said:
Use ADB (USB debugging is enabled by default in custom recoveries).
Click to expand...
Click to collapse
Okay thanks! I'll try that and get back.
ArkThompson said:
Use ADB (USB debugging is enabled by default in custom recoveries).
Click to expand...
Click to collapse
First time doing this, and I have discovered I have no idea what to do. I'm using
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
as a guide but I don't even know how to open the adb so I can input something into the command line.
Obesidia said:
First time doing this, and I have discovered I have no idea what to do. I'm using
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
as a guide but I don't even know how to open the adb so I can input something into the command line.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2141817
You need to use the adb push command to move the file onto your phone. You just use cmd (type cmd into run and press enter).
ArkThompson said:
http://forum.xda-developers.com/showthread.php?t=2141817
You need to use the adb push command to move the file onto your phone. You just use cmd (type cmd into run and press enter).
Click to expand...
Click to collapse
I tried that but I got an error about the file locations. I think it's because there was a space in the one of the folder names, or at least that's what the command line suggested; it basically said "could not push file to '...\Desktop\Fix'" but the folder is called Fix phone.
I was about to rename the folder and move it to C:\ but I just went to reboot the phone in cwm recovery and it said DOES NOT HAVE ROOT ACCESS. ROOT NOW?
I selected yes and it rebooted as normal and got stuck in the samsung boot animation, so no progress there.
I have a backup in CWM recovery from a couple of months ago, I've just found but obviously doing that would lose all my recent pictures and messages. There isn't really a way to get them back by continuing with this method, is there?
Obesidia said:
I tried that but I got an error about the file locations. I think it's because there was a space in the one of the folder names, or at least that's what the command line suggested; it basically said "could not push file to '...\Desktop\Fix'" but the folder is called Fix phone.
I was about to rename the folder and move it to C:\ but I just went to reboot the phone in cwm recovery and it said DOES NOT HAVE ROOT ACCESS. ROOT NOW?
I selected yes and it rebooted as normal and got stuck in the samsung boot animation, so no progress there.
I have a backup in CWM recovery from a couple of months ago, I've just found but obviously doing that would lose all my recent pictures and messages. There isn't really a way to get them back by continuing with this method, is there?
Click to expand...
Click to collapse
I think you probably lost your messages when you flashed a stock ROM with Odin. Your pictures could be ok, check with adb and pull them if they are still there.
This Update Provides power improvements and security enhancement for your device
Heating and Battery issues are seems to be fixed
Before you proceed:
Updating to this update doesn’t wipe your data. Still, you should back up all your important data, just in case.
This is an official bug fix update. Installing this, even manually using the method we are providing, doesn’t void your manufacturer warranty in any way.
Make sure that your phone isn’t low on battery. Anything above 35% should be good enough to go ahead with. (Any guide on the internet that asks you to charge your phone above 80% before following a guide, is simply taking unrequired precaution.)
Update Yu Yureka
1.Download the Update file from below (official link).
2.Transfer this zip file as it is (don’t extract it) to the internal storage of your Yureka.
3.Once you’ve done so, reboot your Yureka in recovery mode. To do that, do either of the following steps:
Go to Settings > About phone and tap on the Build Number field seven times. This would unlock Developer Options. Now go to Settings > Developer Options and tick the Advanced Reboot option. Now long press the power button, and then 4.
select the reboot option to get the reboot to recovery option. Select it to boot into the recovery option.
Otherwise, power off your Yureka. Once it shuts down completely, press and hold the Volume Up, Volume Down and 5.
4.Power buttons together till the phone boots up into the recovery mode.
When you enter the recovery mode, select the Apply update option, then the Choose from internal storage option, then the 0/ option, and finally select the cm-tomato-56deeca328-to-00b2e333e8-signed.zip file that you copied to your phone in step 2.
5.Once you select the file in the last step, the recovery will start flashing the update. When the flashing completes, you will be back on the main screen in the Recovery mode.
6.Select the Reboot system now option and wait for the reboot process to complete
Download link
great!
We desperately needed this!
how to flash this update, you provided
Rakesh251 said:
how to flash this update, you provided
Click to expand...
Click to collapse
Thread updated with Procedure
Sangeet007 said:
This Update Provides power improvements and security enhancement for your device
Heating and Battery issues are seems to be fixed
Before you proceed:
Updating to this update doesn’t wipe your data. Still, you should back up all your important data, just in case.
This is an official bug fix update. Installing this, even manually using the method we are providing, doesn’t void your manufacturer warranty in any way.
Make sure that your phone isn’t low on battery. Anything above 35% should be good enough to go ahead with. (Any guide on the internet that asks you to charge your phone above 80% before following a guide, is simply taking unrequired precaution.)
Update Yu Yureka
1.Download the Update file from below (official link).
2.Transfer this zip file as it is (don’t extract it) to the internal storage of your Yureka.
3.Once you’ve done so, reboot your Yureka in recovery mode. To do that, do either of the following steps:
Go to Settings > About phone and tap on the Build Number field seven times. This would unlock Developer Options. Now go to Settings > Developer Options and tick the Advanced Reboot option. Now long press the power button, and then 4.
select the reboot option to get the reboot to recovery option. Select it to boot into the recovery option.
Otherwise, power off your Yureka. Once it shuts down completely, press and hold the Volume Up, Volume Down and 5.
4.Power buttons together till the phone boots up into the recovery mode.
When you enter the recovery mode, select the Apply update option, then the Choose from internal storage option, then the 0/ option, and finally select the cm-tomato-56deeca328-to-00b2e333e8-signed.zip file that you copied to your phone in step 2.
5.Once you select the file in the last step, the recovery will start flashing the update. When the flashing completes, you will be back on the main screen in the Recovery mode.
6.Select the Reboot system now option and wait for the reboot process to complete
Download link
Click to expand...
Click to collapse
OTA or manual update, both have to be flashed using stock recovery, right?
Plz give me the link for stock recovery compatible with CM12S
i am using ThunderZap 4.1 kernel, i am on official lollipop rom,and using twrp recovery. so can i direct flash this.zip via twrp?
Mohammed Raza said:
OTA or manual update, both have to be flashed using stock recovery, right?
Plz give me the link for stock recovery compatible with CM12S
Click to expand...
Click to collapse
Rakesh251 said:
i am using ThunderZap 4.1 kernel, i am on official lollipop rom,and using twrp recovery. so can i direct flash this.zip via twrp?
Click to expand...
Click to collapse
Stock recovery :- http://d-h.st/oYvV
and maybe if youre on stock rom you can flash it using thunderzap's kernel (But im not sure)
Better to use Stock recovery thou
Mohammed Raza said:
OTA or manual update, both have to be flashed using stock recovery, right?
Plz give me the link for stock recovery compatible with CM12S
Click to expand...
Click to collapse
Rakesh251 said:
i am using ThunderZap 4.1 kernel, i am on official lollipop rom,and using twrp recovery. so can i direct flash this.zip via twrp?
Click to expand...
Click to collapse
@Rakesh: no you can not flash it with twrp. ammm may be you will get "installation aborted" error
here is link for stock Recovey.
Stock kernel and recovery
Following error
sal_rc said:
Stock kernel and recovery
Following error
Click to expand...
Click to collapse
amitroutray said:
I am rooted With stock recovery by temporary method.. I am purely on Stock only. When I am manually updating through my stock recovery.. It is showing me the errors...
I have checked the md5 also it is correct.
Thank I advance.
Triggered from YU
Click to expand...
Click to collapse
donwload this whole rom which is included update.
LINK
this should be flash by CM stock recovery only.
I don't feel any change specifically can anyone suggest me why
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
Getiing same error
And can I know the size of the ROM u have given link
#akadroid said:
I don't feel any change specifically can anyone suggest me why
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
Getiing same error
And can I know the size of the ROM u have given link
Click to expand...
Click to collapse
the size of the rom is 643.767MB
i am downloading it.
I can't afford downloading it dude please send me a CD
Lol
But plzzz tell surely if u feel any change
I am rooted With stock recovery by temporary method.. I am purely on Stock only. When I am manually updating through my stock recovery.. It is showing me the errors...
I have checked the md5 also it is correct.
Thank I advance.
Triggered from YU
I think we have to relock the boot loader..
The zip is too large. If I download the OTA on phone, is it the same size or is it a smaller file size?
And if I manually flash from recovery, don't I need to clear cache?
sal_rc said:
Stock kernel and recovery
Following error
Click to expand...
Click to collapse
Hi
The message is very clear:
Your /system partition is RW (read write)
Thats becouse you rooted the device and enabled RW on /system.
Put the /system partition back to his stock state (Read only) and you should be good to go
Cheers
superdragonpt said:
Hi
The message is very clear:
Your /system partition is RW (read write)
Thats becouse you rooted the device and enabled RW on /system.
Put the /system partition back to his stock state (Read only) and you should be good to go
Cheers
Click to expand...
Click to collapse
Mine also same error how to put it back to read only
Worked For ME!!!
I'm on Stock Kernel+Stock Recovery+Non-Rooted+Bootloader Locked :silly:
That Means I have not tinkered with my Device in any means, It is as it was when It was Delivered .
I flashed this update and it was successful. :good: Thanks Pressed.
Faizal Mhate said:
I'm on Stock Kernel+Stock Recovery+Non-Rooted+Bootloader Locked :silly:
That Means I have not tinkered with my Device in any means, It is as it was when It was Delivered .
I flashed this update and it was successful. :good: Thanks Pressed.
Click to expand...
Click to collapse
You flashed the one which is 120MB or so or the 600MB one?
Lollipop OTA can't install on my stock T6ULA 3.23.1540.1 with stock recovery & locked
Hi,
I've recently received software update 4.13.1540.7 notification on my stock, rooted T6ULA 3.23.154.1 - (s-off)(locked bootloader)
I did a few steps before trying to install it :
- uninstalling "exposed installer", viper audio, busy box and everything that I thought it would be a mess with OTA process, completely.
- unlocking bootloader (scotty1223 method) & flashed stock recovery
- locking bootloader ( scotty1223 method)
- unrooting via superuser cleanup setting
- applying the update
But when my phone goes to recovery for installing it, the red triangle shows up after a minute.
I press V.up & P.button few times to see the hidden texts in recovery & realize that the process stopped at a line with an assert check error : system/build.prop has unexpected contents. operation failed ...
Does anyone know what else should i do to update my phone? or where was my mistake? If no, can anyone give me a link to ruu or any stock backup of this lollipop that is compatible with my phone? if no, Is there any method that switch off the "system update" notification pop up? It really bothers. we can stop it just for 4 hours..
Thanx a lot
kam5iz said:
Hi,
I've recently received software update 4.13.1540.7 notification on my stock, rooted T6ULA 3.23.154.1 - (s-off)(locked bootloader)
I did a few steps before trying to install it :
- uninstalling "exposed installer", viper audio, busy box and everything that I thought it would be a mess with OTA process, completely.
- unlocking bootloader (scotty1223 method) & flashed stock recovery
- locking bootloader ( scotty1223 method)
- unrooting via superuser cleanup setting
- applying the update
But when my phone goes to recovery for installing it, the red triangle shows up after a minute.
I press V.up & P.button few times to see the hidden texts in recovery & realize that the process stopped at a line with an assert check error : system/build.prop has unexpected contents. operation failed ...
Does anyone know what else should i do to update my phone? or where was my mistake? If no, can anyone give me a link to ruu or any stock backup of this lollipop that is compatible with my phone? if no, Is there any method that switch off the "system update" notification pop up? It really bothers. we can stop it just for 4 hours..
Thanx a lot
Click to expand...
Click to collapse
hi
copy the ota file to your computer from your download folder. extract it. you will see firmware.zip, extract it too, you will see recovery file. flash it via bootloader and after that try to update the Ota, you will success.
thx
Sent from my HTC One max using XDA Free mobile app
Sheythan... said:
hi
copy the ota file to your computer from your download folder. extract it. you will see firmware.zip, extract it too, you will see recovery file. flash it via bootloader and after that try to update the Ota, you will success.
thx
Sent from my HTC One max using XDA Free mobile app
Click to expand...
Click to collapse
Thanx شیطان but still the Same error again (with newer version of stock recovery from firmware.zip)
system/build.prop has unexpected contents.
error (status 7)
Hi Everyone,
I know, I fell in a noob trap doing this and I already hate myself for it : I tried to OTA update my rooted Honor 7 and the device remained stuck in TWRP after reboot.
Log showed the following message in red : "E: error executing updater binary in zip"
I proceeded to a wipe and managed to start the system. This allowed me to unroot my phone, thinking I would then be able to update from a clean basis.
Unfortunately, the same error occurred and I am now stuck in TWRP again...
I would be grateful if anyone could provide me some leads to get out of my noob trap...
Thank you very much !
Edit : I finally understood how i managed to start system (I deleted the update.zip file and wiped again). Still, now how can I update to the latest version without getting stuck again in TWRP ? Thank you !
Prowls said:
Hi Everyone,
I know, I fell in a noob trap doing this and I already hate myself for it : I tried to OTA update my rooted Honor 7 and the device remained stuck in TWRP after reboot.
Log showed the following message in red : "E: error executing updater binary in zip"
I proceeded to a wipe and managed to start the system. This allowed me to unroot my phone, thinking I would then be able to update from a clean basis.
Unfortunately, the same error occurred and I am now stuck in TWRP again...
I would be grateful if anyone could provide me some leads to get out of my noob trap...
Thank you very much !
Edit : I finally understood how i managed to start system (I deleted the update.zip file and wiped again). Still, now how can I update to the latest version without getting stuck again in TWRP ? Thank you !
Click to expand...
Click to collapse
You have to flash stock recovery before update and unroot of course.
Sent from PLK-TL01H
Lucki_X said:
You have to flash stock recovery before update and unroot of course.
Sent from PLK-TL01H
Click to expand...
Click to collapse
Thank you for your answer ! I found the image of the stock recovery but I can only find instructions for windows and I run on mac... Do you happen to know how can I get to flash the recovery image using terminal ?
Thank you again !
I have a 4g 2nd gen boost mobile (Surnia), and so far, I've used windroid to unlock bootloader, twrp 4g recovery, and last step to root it (Flash Supersu), and I cant.
It puts it in recovery screen, where i press the power and up volume button, select apply update from sd card, and press to install supersu.zip
I get the error:
E: footer is wrong
E: signature verification failed
Installation aborted
Anyone can help me out? Thanks.
Flash Squid's custom TWRP recovery, preferably the 3.0.2-r1 version. Here's the link. This should resolve your issues.
http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649
Also, in TWRP settings, you can disable signature verification checking.
TaylorT88 said:
I have a 4g 2nd gen boost mobile (Surnia), and so far, I've used windroid to unlock bootloader, twrp 4g recovery, and last step to root it (Flash Supersu), and I cant.
It puts it in recovery screen, where i press the power and up volume button, select apply update from sd card, and press to install supersu.zip
I get the error:
E: footer is wrong
E: signature verification failed
Installation aborted
Anyone can help me out? Thanks.
Click to expand...
Click to collapse
yup...fornat data via TWRP in the Wipe section....this should fix it , but maybe you need to get a signed su zip...but im thinkjn its tue first method yiu wanna use....backup data as it wipes everything ....but are u sure u unlocked bootloader? jw....but it sounds like u may also he trying to do his stock recovery which will never flash zips
hope helped
Regards YoungDoctur aka Chiraqian