Related
Hi all -
Thanks for the wealth of knowledge. I have been rooted and successfully been running CM10 for about a month and a half now. I decided to check out the changelog for the latest nightly and decided to upgrade via the CM upgrade tool (to cm-10.1-20130109-NIGHTLY-d2vzw.zip).
When rebooting into Android System Recovery, I try to 'apply update from external storage' and run gapps but receive the error: E: failed to verify whole-file signature and E: signature verification failed.
I've run into all sorts of issues, so I wanted to wipe. I wiped and now I am running into a few issues I was hoping someone could assist:
- I cannot access my Google Account (add it, access Play, etc.)
- My 4g signal strength is very poor compared to earlier versions.
Attached are two screenshots to give you an idea what I am working with.
http : // i.imgur.com/YXE4u.png
(remove spaces to see link)
Thanks for your help.
When rebooting into Android System Recovery, I try to 'apply update from external storage' and run gapps but receive the error: E: failed to verify whole-file signature and E: signature verification failed
Click to expand...
Click to collapse
You chose the wrong option. While in CWM, you were supposed to select "Install zip from sd card"
I've run into all sorts of issues, so I wanted to wipe. I wiped and now I am running into a few issues I was hoping someone could assist:
- I cannot access my Google Account (add it, access Play, etc.)
- My 4g signal strength is very poor compared to earlier versions.
Click to expand...
Click to collapse
Do you actually have the Play Store and Google Apps in your app drawer? If not, you need to install the GApps along with the rom.
If you do have the Play Store but can't sign in, try wiping data for Play Store and also Google Services Framework in Settings/Apps
First off, thanks for the response.
SlimSnoopOS said:
You chose the wrong option. While in CWM, you were supposed to select "Install zip from sd card"
Click to expand...
Click to collapse
That is not an option when recovery boot for me.
SlimSnoopOS said:
Do you actually have the Play Store and Google Apps in your app drawer? If not, you need to install the GApps along with the rom.
Click to expand...
Click to collapse
I do not. I tried to install GApps and that's when I received the message I've bolded above.
etm124 said:
First off, thanks for the response.
That is not an option when recovery boot for me.
I do not. I tried to install GApps and that's when I received the message I've bolded above.
Click to expand...
Click to collapse
Hmm, and that's with the CM10 Upgrade tool? What happens when you manually boot into CWM (notice the difference) recovery then flash? Which version of CWM are you using?
SlimSnoopOS said:
Hmm, and that's with the CM10 Upgrade tool? What happens when you manually boot into CWM (notice the difference) recovery then flash? Which version of CWM are you using?
Click to expand...
Click to collapse
Good point, I actually didn't try that.
I think If I was booting into CWM, I would have had the option.
I ended up getting frustrated, went back to stock, and will try it fresh.
Thanks for the help Slim.
It sounds like you were in stock recovery. Cwm must be installed manually.
Sent from my SCH-I535 using Tapatalk 2
etm124 said:
Good point, I actually didn't try that.
I think If I was booting into CWM, I would have had the option.
I ended up getting frustrated, went back to stock, and will try it fresh.
Thanks for the help Slim.
Click to expand...
Click to collapse
No problem, I'm on TW so I don't have any experience with the CM upgrade tool. Just a reminder, make sure to use CWM 6.0.2.3 or TWRP 2.3.3 for AOSP JB 4.2 roms.
hi..
i've ota'd my device with JB, and flashed it with CWM.. the problem is i cannot flash the superSU, i've checked a few a threads and guides, and although one says rooting only works for 4.0.4 firmwares ,another http://forum.xda-developers.com/showthread.php?t=2256821 says it will work on all firmwares, the message i get is E:failed to verify whole-file signature
E: signature verification failed.
which to me seems to indicate a problem with SU rather then rom. i've tried it with both 1.34 version and 1.25 version, i've read somewhere that SuperSU may not work on all devices, but i didn't see any alternatives. i've looked into CF-Auto_root but it doesn't seem to have a version for the relay..
Did you use this su flashable *.zip?
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
md5: 6462ac14cd38ed7c539ce3e29a6b92a8
yes, stil same message
can i use twrp?
emaayan said:
can i use twrp?
Click to expand...
Click to collapse
To flash SU? Sure. I think there even is a function of some sort to install su in twrp.
Sent from my SGH-T699
sadly i cannot flash that as well
due to the same problem with cwm , i need it in odin format. so my real problem is to find a cwm twrp in odin format that is compatible with the relay and enables signature verifiaction skip
QUOTE=Kueber;42798462]To flash SU? Sure. I think there even is a function of some sort to install su in twrp.
Sent from my SGH-T699[/QUOTE]
emaayan said:
due to the same problem with cwm , i need it in odin format. so my real problem is to find a cwm twrp in odin format that is compatible with the relay and enables signature verifiaction skip
Sent from my SGH-T699
Click to expand...
Click to collapse
[/QUOTE]
If you flash this cwm.tar.md5 file via odin you should be able to install the stock jelly bean rom and SU in recovery mode right after that.. I did this few days ago, just to test stock jelly bean.
If you already tried this.. wellp, no idea what's going on.
this is the exact cwm i tried, via odin, and no matter, i try to flash through it, (well i didn't try to original stock rom) whether it's TWRP su on several versions, i always go the same issue with signature verification, so my first problem is how do i install a cwm or TWRP which allow me to disable signature verification? i'm assuming i can't just pick up any cwm or twrp, and try to odin them, i need the ones compatible with relay.
Maybe a silly prompt, but is the date and time current in phone?
Yea, why shouldn't they be?
Sent from my SGH-T699 using Tapatalk 2
Someone tried any rooting method on 4.1.2 ?
I dont want to mess my phone...
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
scott_doyland said:
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
Click to expand...
Click to collapse
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
kieranc88 said:
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
Click to expand...
Click to collapse
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
scott_doyland said:
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
Click to expand...
Click to collapse
Yeah,send it,I'll try copying it,unrooting and then trying the update
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
And will it matter what version of the stick recovery I'm using( if there are different versions)
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
tee_pot said:
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
Click to expand...
Click to collapse
OK,well at the moment I'm trying out cm11 unofficial builds,I'll see how they go, I'll try the full unroot option when I restore my cwm backup and reflash stock recovery and see if that works ,as I only tried the temporary unroot option in supersu(which is probably leaving some root files behind so it can reinstall su ) if that don't work I'll flash back to stock and try again.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I will send file tomorrow when I'm at my PC.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I have attached the file /system/etc/install-recovery.sh file to this post (had to gzip it as couldnt upload when it was just called .sh)
Im not sure what the original persmissions of the file should be on your phone, but if you make it read/write/executable by everyone then should be OK I guess.
As I mentioned it'd be good if you unrooted and did a backup and extracted the file to see the contents (before copying over the file). That would first tell you for sure if the file does revert back to original or if it stays as a 'superSU' file when you unroot.
If its reverted back to original then my theory is wrong anyway so no need to copy over the file.
Re the stock recovery type/version being different from what is expected - I dont know if that makes a difference to the OTA working or not. Its an interesting question though so I may do some googling and find out.
I also have a UK retail stock recovery.img (taken with CWM) (my phone is 16GB from phones4u). So if you want that you can have it. Should rule out the recovery type as a problem.
FYI the install-recovery.sh original file actually flashes a new stock recovery when an OTA is performed. At least if you look in the comments of the file I attached above thats what it says.
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
JayZeus said:
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
Click to expand...
Click to collapse
If you made some modification to the 4.4.2 rom you'll have to restore the stock before upgrading to 4.4.4.
Bootloader can be unlocked, Recovery can be custom but any mod/root to the room will cause the error.
To restore to stock follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219
Thanks a lot, it worked!
By the way is the part where you erase you data mandatory ? In case I have to do this again.
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ! Thank you.
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) [emoji481]
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
This way I'll keep my installed applications?
Thanks.
4.4.2 > 4.4.4. just rolled out in UK (o2 moto g).
right after i get my phone rooted and started setting it up...
Thanks for this thread.. what's the minimum we have to restore, basically the system partition so it's unrooted?
If we have stock 4.4.2 (rooted) can we flash JUST these 3 files?
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
and skip the rest? I want to save redo-ing as much as possible..
I got the 4.4.4 OTA today (210.12.40.en.GB) and I have unlocked bootloader + Philz recovery - Philz worked fine for the 4.4.2 OTA update, but when I downloaded the 4.4.4 OTA and rebooted Philz would abort with "a status 7" mismatch error and then the phone would boot to Android, then 20 seconds later shutdown and reboot to Philz again, continuously. After some playing, I did the following:
1. Flashed stock recovery (taken from Mototool AIO's 4.4.2 stock.img) from fastboot - re-downloaded the 4.4.4 OTA but that failed with "Error!"
2. Flashed stock kernel (I was running faux123) - same issue, 4.4.4 OTA failed still.
3. Flashed latest Philz recovery again (philz_touch_6.50.6-falcon.zip) then
4. Flashed stock 4.4.2 GB kernel (to match my OTA version) - kernel from here http://forum.xda-developers.com/showthread.php?t=2649763 - success... OTA downloaded and this time installed.
SO, conclusion is you don't need stock recovery to flash OTA, BUT you do need the correct kernel for your update and having a custom kernel causes the mismatch error.
Hope this helps someone!
So the UPDATE-SuperSU-v1.91.zip in MotoG-Tools.zip still works to root 4.4.4 right?
i found it here
http://www.swedroid.se/forum/showthread.php?t=106595
and this is what i used for 4.4.2
Most of the old guides around no longer worked in 4.4.2, i dunno if they closed any other holes in 4.4.4?
edit: version typo sorry
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
JayZeus said:
I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error.
Click to expand...
Click to collapse
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
agoodhi said:
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
Click to expand...
Click to collapse
I figured it out... I simply did a delete cache from CWM recovery and now no more boot loop.
fatechand said:
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
Click to expand...
Click to collapse
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Smiff2 said:
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Click to expand...
Click to collapse
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
fatechand said:
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
Click to expand...
Click to collapse
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
---------- Post added at 06:32 AM ---------- Previous post was at 06:14 AM ----------
agoodhi said:
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
Click to expand...
Click to collapse
CWM message:
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
assert failed: getprop("ro.product.device) == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma"
E: Error in /cache/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
(Status 7)
Installation aborted.
Rebooting...
fatechand said he had CWM 6047 installed and OTA update was ok. he just had to re-root? perhaps difference between 6046 and 6047 CWM, or some difference in way you rooted?
I have same recovery, rooted, 4.4.2, so should work... ?
I'm using nexus 5 running stock android 4.4.4 build no. KTU84Q. Got notification for android lollipop upgrade and i started downloading on wifi. After completion of download it shows verifying and then shows verification failed and after sometime starts downloading again. I have not installed custom ROM anytime in my phone.i have stable net connection and I have repeated the download for 4 times now but it's still showing verification failed.pls help
milan100kar1 said:
I'm using nexus 5 running stock android 4.4.4 build no. KTU84Q. Got notification for android lollipop upgrade and i started downloading on wifi. After completion of download it shows verifying and then shows verification failed and after sometime starts downloading again. I have not installed custom ROM anytime in my phone.i have stable net connection and I have repeated the download for 4 times now but it's still showing verification failed.pls help
Click to expand...
Click to collapse
Same here..... I tried with adb sideload and it shows that unexpected contents in platform.XML which is in Systems/etc/permission/platform.XML I and used SD fix tool and it changed my platform.XML file and I don't have backup.
Please if you found any way to update it than do lemme know. Thanks in advance.
milan100kar1 said:
I'm using nexus 5 running stock android 4.4.4 build no. KTU84Q. Got notification for android lollipop upgrade and i started downloading on wifi. After completion of download it shows verifying and then shows verification failed and after sometime starts downloading again. I have not installed custom ROM anytime in my phone.i have stable net connection and I have repeated the download for 4 times now but it's still showing verification failed.pls help
Click to expand...
Click to collapse
Did you make any modifications to the system? Xposed? Everything must go back to stock in order for OTA to be applied.
jasonftfw said:
Did you make any modifications to the system? Xposed? Everything must go back to stock in order for OTA to be applied.
Click to expand...
Click to collapse
Yes everything is stock . i never tweaked my system anyway. I dunno can any app cause this thing. I dont wanna sideload..
milan100kar1 said:
Yes everything is stock . i never tweaked my system anyway. I dunno can any app cause this thing. I dont wanna sideload..
Click to expand...
Click to collapse
If you are 100% stock there should be no issue. Are you running custom recovery? Do you have Xposed?
jasonftfw said:
If you are 100% stock there should be no issue. Are you running custom recovery? Do you have Xposed?
Click to expand...
Click to collapse
Not running on custom recovery .. Not Xposed ever. I never tweaked my nexus anyway. I'm trying agin to update!! May be I have to do a factory reset !!
milan100kar1 said:
Not running on custom recovery .. Not Xposed ever. I never tweaked my nexus anyway. I'm trying agin to update!! May be I have to do a factory reset !!
Click to expand...
Click to collapse
Try to sideload first, I had some issues with ota failing on device but then sideload worked.
jasonftfw said:
Try to sideload first, I had some issues with ota failing on device but then sideload worked.
Click to expand...
Click to collapse
Ok , I'll try that first. May be it has do with network connection. I'm using my othe cellphone's data and using its tethring to update ??