[Q] Tried to upgrade to Nightly CM10.1-20130109 - No Google Account and other issues - Verizon Samsung Galaxy S III

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.

Related

[Q] [HELP] Loading a ROM on Captivate

Feeling dumb, but I have successfully rooted and loaded (multiple times) ROMS on my Droid Incredible. Though I can't seem to get ROM manager to load a downloaded (CM7) rom onto my captivate - YES the phone is rooted .
I think i'm missing the bootloader, but i'm unsure. All the phone does is go to "Samsung Recovery Utils" and offers the following options only
*reboot system now
*reinstall packages
*delete all user data
*delete cache data
*format internal sd-card
Can anyone tell me what i'm doing wrong or point me to a thread that doesn't just say "download rom, install from SD card and done"?
let me give you a hint. there is a sticky section.....read
dudeicles said:
Feeling dumb, but I have successfully rooted and loaded (multiple times) ROMS on my Droid Incredible. Though I can't seem to get ROM manager to load a downloaded (CM7) rom onto my captivate - YES the phone is rooted .
I think i'm missing the bootloader, but i'm unsure. All the phone does is go to "Samsung Recovery Utils" and offers the following options only
*reboot system now
*reinstall packages
*delete all user data
*delete cache data
*format internal sd-card
Can anyone tell me what i'm doing wrong or point me to a thread that doesn't just say "download rom, install from SD card and done"?
Click to expand...
Click to collapse
Can you give more details? Going from what to what etc....?
chappatti said:
Can you give more details? Going from what to what etc....?
Click to expand...
Click to collapse
Going from Stock Froyo 2.2 to CM7. but when i go into the boot screen it's blue and gives me the options above. Then when I press the "reinstall updates" I get a
E:failed to verify whole-file signature
E:signature verification failed"
I must be doing something just simple and stupid, but thought i'd ask anyways. I'll try to find the sticky and see if it tells me something i haven't tried. Thanks!
SEARCH FOR :captivate signature verification error
FIND:
million threads.
OR READ MY SIG.... the answer is in there.
@TRusselo: I've tried your guide step by step and I still end up at the Android system recovery and not CWM. Is there a step I might be missing? I downloaded the links you gave, followed all instructions and still same problem.
Thanks alot for the guide, if it worked i'd be even happier about it.
dudeicles said:
@TRusselo: I've tried your guide step by step and I still end up at the Android system recovery and not CWM. Is there a step I might be missing? I downloaded the links you gave, followed all instructions and still same problem.
Thanks alot for the guide, if it worked i'd be even happier about it.
Click to expand...
Click to collapse
After doing all the steps, did you reinstall packages in recovery.
Sent from my SGH-I897 using xda premium
b-eock said:
After doing all the steps, did you reinstall packages in recovery.
Click to expand...
Click to collapse
I tried that multiple times.
my understanding is the text at that point should be green, but it's still blue and gives the same exact error. "E:failed to verify whole-file signature E:signature verification failed"
Alright, I tried the Heimdall version which shows more promise, i'm just now unable to boot into any recovery. I hold the volume buttons and power for the 3-5 seconds and it boots to a boot screen with "TALON" on it. but nothing else from there.
Am I missing something else?
to first issue.... you followed the wrong link in my signature....
" 3e recovery fix " is what you were looking for.... since you were having truoble with 3e recovery.... thought that would be self explanatory.....
make sure usb debugging is ONturn OFF anti-virus for 5 minutes or until reboot
plug in phone.
click the bat file in this file.
you will have THE SAME RECOVERY with NO error
signature verification pass...
flash any update.zip package
but since you have a custom kernel with cwm now.....
What heimdall method are you talking about? for recovery? for flashing roms? what are you talking about. heimdall can do alot of stuff. did you upgrade bootloaders? or??
keep trying the button combo.. if it turns on, it will go into recovery.
Please search before posting, on that note thread closed.

[Q] CM10.1 ROM gapps install

So I installed this ROM last night which went smoothly. A few posts down there is a link to gapps which I donwloaded. There are the steps that I took:
Put the .zip on my flash card (gapps-jb-20121212-signed.zip)
Booted into recovery
Selected "apply update from external storage"
Pointed it to the .zip
The install process starts. It fails saying "failed to verify whole-file signature" and "signature verification failed". Installation aborted.
Do I have the correct process for installing these?
Am I using the incorrect gapps? Seems to be why most people have this issue. I read the thread and as far as I can tell it is supposed to be the correct one. I didnt' hear of anyone else complaining about it.
Thanks in advance...
Dustin
You have to boot into Custom recovery, and then, select 'Install zip from sdcard', then flash the gapps. Like you did it when you've installed the ROM. But, now, you're using CM10 recovery instead the Atrix 2 Bootstrapper.
dmroeder said:
So I installed this ROM last night which went smoothly. A few posts down there is a link to gapps which I donwloaded. There are the steps that I took:
Put the .zip on my flash card (gapps-jb-20121212-signed.zip)
Booted into recovery
Selected "apply update from external storage"
Pointed it to the .zip
The install process starts. It fails saying "failed to verify whole-file signature" and "signature verification failed". Installation aborted.
Do I have the correct process for installing these?
Am I using the incorrect gapps? Seems to be why most people have this issue. I read the thread and as far as I can tell it is supposed to be the correct one. I didnt' hear of anyone else complaining about it.
Thanks in advance...
Dustin
Click to expand...
Click to collapse
Yeah, those are the correct gapps for your ROM, but it should say something along the lines of "install zip from SD card" or something like that. Also, wipe cache and dalvik before flashing. :thumbup:
Brought to you by time and relative dimensions in space.
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
brianmoyano said:
You have to boot into Custom recovery, and then, select 'Install zip from sdcard', then flash the gapps. Like you did it when you've installed the ROM. But, now, you're using CM10 recovery instead the Atrix 2 Bootstrapper.
Click to expand...
Click to collapse
Hahaha, you must've posted this while I was typing. At least we gave pretty much the same answer.
Brought to you by time and relative dimensions in space.
1BadWolf said:
Yeah, those are the correct gapps for your ROM, but it should say something along the lines of "install zip from SD card" or something like that. Also, wipe cache and dalvik before flashing. :thumbup:
Brought to you by time and relative dimensions in space.
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
Hahaha, you must've posted this while I was typing. At least we gave pretty much the same answer.
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Aah, thanks fellas. I think I see what was going on. If I held the Up/Down arrows before betting the motorola boot screen, it would put me into what looked like the stock motorola. If I did it after the motorola logo appeared, I got into a different looking recovery that had the options that you guys described.
dmroeder said:
Aah, thanks fellas. I think I see what was going on. If I held the Up/Down arrows before betting the motorola boot screen, it would put me into what looked like the stock motorola. If I did it after the motorola logo appeared, I got into a different looking recovery that had the options that you guys described.
Click to expand...
Click to collapse
Sounds like you've got it. If I understand correctly from what I've read, the reason the stock recovery is still there is due to the locked bootloader. Any custom recovery for this phone has to be installed on the system partition. So after installing a custom recovery, you'll have 2 recoveries. One before the boot process starts, and one is a hijack that happens just after the Motorola logo appears. That is, if I understand it right. If anyone wants to correct me or further clarify, feel free....
Sent from my SGH-I897 using xda premium
How to install custom recovery atrix 2
1BadWolf said:
Sounds like you've got it. If I understand correctly from what I've read, the reason the stock recovery is still there is due to the locked bootloader. Any custom recovery for this phone has to be installed on the system partition. So after installing a custom recovery, you'll have 2 recoveries. One before the boot process starts, and one is a hijack that happens just after the Motorola logo appears. That is, if I understand it right. If anyone wants to correct me or further clarify, feel free....
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
----------------------------------------------************************************---------------------------
can you tell me How should I install custom recovery now at this stage where I cant boot my android?
So your phone currently won't boot? If that's true, search the forum for FXZ
RSD Lite not shows my Atrix 2
dmroeder said:
So your phone currently won't boot? If that's true, search the forum for FXZ
Click to expand...
Click to collapse
yeah .. won't boot.
I read FXZ forum and then,
I download RSD Lite 5.7,
I start my phone in with Volume Up/Down and Power button.
I try to flash with RSD LITE now.
but I got error .
I attaching snapshot of error in RSD Lite.
It's Like "Failed Flashing Process. 1/14 flash "cdt.bin" -> USB error occurred while reading/writing."
------------------There is Any other way which I can try------------
Make sure you have the latest drivers from Motorola.
Swadheer said:
yeah .. won't boot.
I read FXZ forum and then,
I download RSD Lite 5.7,
I start my phone in with Volume Up/Down and Power button.
I try to flash with RSD LITE now.
but I got error .
I attaching snapshot of error in RSD Lite.
It's Like "Failed Flashing Process. 1/14 flash "cdt.bin" -> USB error occurred while reading/writing."
------------------There is Any other way which I can try------------
Click to expand...
Click to collapse
Why are you flashing the hktwn fxz??..is your phone AT N T??..if yes flash ONLY the AT N T FXZ..
ATRIX 2 its like dead
devilhunter47 said:
Why are you flashing the hktwn fxz??..is your phone AT N T??..if yes flash ONLY the AT N T FXZ..
Click to expand...
Click to collapse
No, It's Not AT & T.
Ohh..!!
Now its not going to Android recovery Mode also.
When I kept phone in charge it shows MOTOROLA Logo and its freeze there only.
I try to start but It's Not started.
Even Volume Up/Down and Power button is not working...

Getting error message while flashing m9 update to m8 cm11

hi guys!
i followed the following steps to update my m8 to m9 on cm11 :-
1) download from http://get.cm/get/iwr
2) boot in recovery.
3) create a backup from recovery. (didnt do this as i already took a titanium backup before)
4) then simply install the zip, without wiping anything.
5) reboot.
its showing me the following message :-
E: failed to verify whole-file signature
E: signature verification failed
installation aborted
pls help
P.S here is my 'about phone' stats if that would help
model - nexus 5
cyonagenmod version - 11.0-installerXNPQ29S
android version - 4.4.4 (but showing on cyanogenmod site 'my account' that its 4.4.2...any help on this will also be appreciated)
baseband version - M8974A-2.0.50.1.16
kernel version - [email protected]#1
cpu - ARMv7 processor rev 0 (v71)
build number - cm_hammerhead-userdebug 4.4.4 KTU84P installerXNPQ29S release-keys
SELinux status - enforcing
What recovery are you using?
Lethargy said:
What recovery are you using?
Click to expand...
Click to collapse
hi
current recovery : clockworkmod 6.0.4.5
latest recovery : clockworkmod 6.0.4.5
as shown in my rom manager application
Try turning signature verification off.
Don't use ROM manager. User recovey manually
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
Try turning signature verification off.
Don't use ROM manager. User recovey manually
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
hi
i am recovering manually by pressing power button then clicking on reboot then recovery. just checked the version from rom manager
and how do i turn signature verification off... im very new to rooting and its technicalities so im sorry for sounding like a simpleton
pls any help would be greatly appreciated
also in my developer options ive got USB DEBUGGING checked but its not highlighted and ive got something called ANDROID DEBUGGING above it which is not checked but is highlighted
You don't need any options set in android.
There is an option to toggle signature verification in recovery. Possibly under "install zip"
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
You don't need any options set in android.
There is an option to toggle signature verification in recovery. Possibly under "install zip"
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
tried that didint work
also followed the steps mentioned here http://jaxov.com/2010/10/fix-android-no-signature-verification-failed-error/
also disabled my signature verification
here is the complete log :-
signature check : disabled
installing : /sdcard/0/download/cm-11-201408 05-SNAPSHOT-M9-hammerhead.zip
finding update package...
openeing update package...
installing update...
cant install this package on top on incompatible data. please try another package or run a factory reset
E: Error in /data/media/0/download/cm-11-201408 05-SNAPSHOT-M9-hammerhead.zip
(Status 7)
installation aborted
Did you try and do the factory reset as it suggests? Take a backup first.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
Did you try and do the factory reset as it suggests? Take a backup first.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
thanks alot for taking ur time out and helping /guiding me through this problem )
just 1 last question pls (3 parts )
suppose i take a nandroid backup and factory reset then when i restore will EVERYTHING (apps+data) come back as it is except that i will be on the M9 version?
i already have a titanium backup transfered on my dropbox will that do the trick?
also any link to easily restore the backup containing all apps+data? (from cwm i think u can do that from recovery and titanium has the recover data in the app itself)
rootSU said:
You don't need any options set in android.
There is an option to toggle signature verification in recovery. Possibly under "install zip"
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
hi
i did a complete factory wipe along-with wipe cache
went into browser downloaded the m9 snapshot file again from cyanogenmod website went into recovery tried flashing still same error is being shown to me
E: failed to verify whole-file signature
E: signature verification failed
installation aborted
any input as to what i can do now pls?
ayush88 said:
3) create a backup from recovery. (didnt do this as i already took a titanium backup before)
Click to expand...
Click to collapse
this is the most important step, and you failed miserably. a backup in recovery is not the same thing as backing up with titanium. a backup in recovery is for when you flash something bad that has serious issues, or you flash something and cant boot up. if you flashed a bad download, and you wont pass the google screen, a titanium backup can not help you. thats when a backup in your recovery helps. in that case, you would just restore your backup, and you would boot up with how your rom was exactly before flashing something bad. otherwise, i can see you posting a new thread title.. "I flashed cm now my phone is bricked".;

error executing updater binary

Hi Guys,
I have tried many of the ROMs available however, for the most part, I get this error "error executing updater binary" in TWRP. I have also tried CWM and Philz recovery. The only ROM that installs is CM11. Does any one know what is the issue? Anyone got a solution? Thanks.
Current Recovery: TWRP 2.7.1.1
I'm the only one experiencing this issue?
Specifically which ROMs have you tried?
Transmitted via Bacon
I've tried the following:
AOSP from the Oneplus homepage
AOSP flapped
mahdi-rom
Team GUMMY
Are you checking the md5 when you download?
Transmitted via Bacon
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
bill1clinton said:
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
Click to expand...
Click to collapse
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Well, just re-downloaded AOSP from the oneplus homepage and flapped AOSP. I also checked their md5 hashes; they match. I will report back.
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
timmaaa said:
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Click to expand...
Click to collapse
Just tried to flash both, both times I get the "error executing updater binary" error. I do not have the technical expertise to try to correct this.
Anyone else with any ideas?
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
demkantor said:
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
Click to expand...
Click to collapse
The ROM that works is CM11 nightly and the one that I would like to install is pure AOSP. Are you certain that their update binary files would/could be interchangeable?
And how to do you "set to store"? I use 7zip.
I have the international 64GB. And I am not sure how to check my bootloader.
I really do apologize for my newb-ness on this matter.
There shouldn't be an issue, but of course I can't promise as I don't know what specifically is going on in your case
When you choose zip, there you will have different compression options, choose store
Try
fastboot oem device-info
Write down output here
No worries, we all are noobs in our own ways
did anyone figure this out? im having the same issue trying to install lollipop roms
Same problem here
jlinn75 said:
did anyone figure this out? im having the same issue trying to install lollipop roms
Click to expand...
Click to collapse
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
viriatis said:
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
Click to expand...
Click to collapse
I get the exact same error, as you I can only flash CM-11, strange cause I was running Euphoria OS Lollipop!
Someone must know the cause!
sad problem
doe or die said:
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
Click to expand...
Click to collapse
I'm having exactly same problem. So is this common problem or what? I had multirom and xposed framework but after uninstalling them both I get the same error again. I hope this does not happen when we are getting the Lollipop-update. Sry for bad enklish.
Anyone help?

Tried to install 38R

I tried to install 38R, but now my phone won't boot. I tried to flash it from a page on the oneplus forums. HelP!
Download the zip from this thread and install it through custom recovery! http://forum.xda-developers.com/showthread.php?t=2898098
I would love to, but it doesn't show up when it is stuck at the screen with the 1+ in a box logo. What do I do?
shiboby said:
I would love to, but it doesn't show up when it is stuck at the screen with the 1+ in a box logo. What do I do?
Click to expand...
Click to collapse
Maybe this could help !
http://forum.xda-developers.com/showpost.php?p=54705363&postcount=4
shiboby said:
I tried to install 38R, but now my phone won't boot. I tried to flash it from a page on the oneplus forums. HelP!
Click to expand...
Click to collapse
You haven't provided anywhere near enough information. What's the zip you flashed? What version were you on previously? What recovery are you using?
Transmitted via Bacon
I have had tons on trouble trying to update today. The error message that I keep getting is "Unfortunately, the process com.android.systemui has stopped" This makes the phone unusable because the message keeps popping up even after I click "OK". I was linked to Calkulins file from another thread. I have factory reset phone, deleted data, and wiped cache. I have copied the zip to the phone and tried to load from CM Recovery [Volume Down and Power] with no success. I get the following messages in Recovery:
Finding update package
Opening update package
Verifying update package
E: footer is wrong
E: signature verification failed
Installation aborted
Anyone have advise on how I can fix this. Thanks in advance.
timmaaa said:
You haven't provided anywhere near enough information. What's the zip you flashed? What version were you on previously? What recovery are you using?
Transmitted via Bacon
Click to expand...
Click to collapse
OK, so I downloaded the two zips from here and followed these instructions https://forums.oneplus.net/threads/...and-modded-device-without-losing-data.137908/
I was on 33R with sensei kernel using TWRP as the recovery
Go back to stock and then update.
Transmitted via Bacon
Worked for me too. Thx a lot
Some questions:
In order to clean up some stuff I never use, I removed some useless apps (Play Games, Play Books, Play Music, …). After flashing the ROM, those apps were installed again.
Was that the reason, why the update failed?
Is it for some stability / update / security fact useful, to keep those apps installed?
timmaaa said:
Go back to stock and then update.
Transmitted via Bacon
Click to expand...
Click to collapse
I just did that again. still can't change the lock screen from swipe. ahh!!!!!!!!

Categories

Resources