Let me start off by saying I was one of the people who were kind of scared about this myth when it first came to light. But then I used a bit of common sense in the matter and now i'm 100% sure this doesn't exist, at least on the Galaxy S III. Let me explain why:
The current myth is: Your NFC/Secure Element will cease to function properly if you don't wipe Google Wallet settings before flashing a ROM.
Let's just say you're on a stock ROM, and you happen to do a factory reset, which is about half the same as flashing a ROM. The same goal is accomplished, your /data partition gets wiped so that you can start over. The only difference being that /system doesn't get touched when doing a factory reset from a stock OR custom ROM. Flashing a ROM in recovery however will usually wipe your /system partition. Data wiping is still left up to YOU. Now that we know factory resetting and flashing a new ROM are almost the same, in that they both usually end up with you wiping your data, let's move along.
I'm sure Google and various OEMs wouldn't make the NFC chip or your secure element that easy to break from a "factory reset." This is a function that's available on every Android phone, and people do it all of the time.
Most ROMs will only wipe /system. Now you have to ask yourself what /system has to do with the NFC chip/Secure Element. Especially if in Stock situations the /system partition is R/O (read only). Are there NFC specific files for your particular device stored on your /system partition? No. But then again, those who have had issues with Google Wallet after a flash I can only assume either flashed a ROM that made other changes to the phone, or that particular phone had NFC issues to begin with.
Now, I'm not discounting the probability of this issue being present on the Galaxy Nexus, as I don't own that phone or know how its NFC chip operates or how sensitive it is. However, this issue does NOT exist on the Galaxy S III. Being a 'developer' of ROMs has of course made me have to flash numerous times to test things out on my ROM, all of which have been done with a wiping of /data and none of them have been done with a wiping of Google Wallet data. Now before you say "Well, you've been flashing the same ROM over and over again." This is true for the most part. However, I DID try CM9 and CM10 for a short time as well and my Google Wallet functions just fine, and with the latest update, I just added all of my current credit cards and debit card. I have purchased numerous things from CVS and McDs between the time I first bought my phone (stock) and now (rooted and flashed a lot of times). So those of you who are scared you're going to forget wiping your Google Wallet settings, don't be. It will have no effect on your ability to use NFC in the future.
That is all!
Excellent Write Up.
I'm really glad you cleared this up. I was difinitely one of the ones scared I was gonna for get to clear my wallet before I flash because I do flash so often and use wallet a lot.
Happy now yousefak.
gaunt_let said:
I'm really glad you cleared this up. I was diffiantly one of the ones scared I was gonna for get to clear my wallet before I flash because I do flash so often and use wallet a lot.
Click to expand...
Click to collapse
http://www.d-e-f-i-n-i-t-e-l-y.com/
Happy now yousefk?
Click to expand...
Click to collapse
i lol'd
The data that the old versions of Google Wallet kept were stored on the secure element. The secure element has its own OS; it is separate from Android. Right now, only Google Wallet has access to the secure element (perhaps some other Google-approved applications, too, and perhaps adb commands, though I'm not 100% on that one).
You also seem to be assuming that flashing a ROM or wiping your phone without resetting wallet will result in a locked secure element 100% of the time. This is not the case. I too had flashed my Galaxy Nexus without resetting Wallet many times back in November; nothing happened. We're not 100% certain of the conditions that cause the secure element to self-destruct, but it definitely happens. The Galaxy Nexus and Galaxy S3 use the same NFC chip, so, if your galaxy S3's secure element believes it's being tampered with -- as is the case sometimes when people flash without resetting Wallet (leaving residual information behind) -- it too will destroy itself.
That's why people who are savvy with the issue advised the community to always reset Wallet before a flash or reset. We don't know the specific conditions that cause it, but it's better to be safe than having to get a new phone.
NFC Guy said:
The data that the old versions of Google Wallet kept were stored on the secure element. The secure element has its own OS; it is separate from Android. Right now, only Google Wallet has access to the secure element (perhaps some other Google-approved applications, too, and perhaps adb commands, though I'm not 100% on that one).
You also seem to be assuming that flashing a ROM or wiping your phone without resetting wallet will result in a locked secure element 100% of the time. This is not the case. I too had flashed my Galaxy Nexus without resetting Wallet many times back in November; nothing happened. We're not 100% certain of the conditions that cause the secure element to self-destruct, but it definitely happens. The Galaxy Nexus and Galaxy S3 use the same NFC chip, so, if your galaxy S3's secure element believes it's being tampered with -- as is the case sometimes when people flash without resetting Wallet (leaving residual information behind) -- it too will destroy itself.
That's why people who are savvy with the issue advised the community to always reset Wallet before a flash or reset. We don't know the specific conditions that cause it, but it's better to be safe than having to get a new phone.
Click to expand...
Click to collapse
Thanks for this information. I wasn't aware that they used the same NFC chip. The reason why I believe that other things were at play and not just the flashing of ROMs is that a factory reset on a stock system would essentially accompilsh the same thing as flashing a new ROM. both ultimately wiping data. But I suppose with Stock, at least you're using the same version of wallet since /system doesn't get touched, where as other custom ROMs may use a different version of Wallet in their installs. This is the number one reason why I always remove Play Store installable apps from any ROM that I create. If you want them, you can download them yourself. Maybe that's one of the conditions that cause a secure element to believe it's being tampered with?
Outstanding edumacating going on here freeza and NFC guy. Had no clue nfc chips have their own is. This thread is the key reason I have been faithful to this place
I have read this twice, but am not sure I completely grasp the issue.
Right now I have wallet setup on my phone. I am on lg2 stock and rooted.
If I am reading this right, I can apply the LG8 update and modem through CMW, I will not have a problem with wallet?
There was just an article on Engadget (and I'm sure on other sites) that mention a new version of Google Wallet which allows for any card to be added as well as the secure element being moved to the cloud instead of locally on the device.
http://www.engadget.com/2012/08/01/google-wallet-moves-to-the-cloud-opens-up-to-all-credit-and-deb/
Does this mean that whatever state your secure element is in at this point won't matter (assuming the new Google Wallet app supports the device)?
Thanks for the write up, I also flashed several rom without resetting Wallet (by accident) and when I realized what I had done I was sweating bullets. I nandroided the first time I did that and Wallet worked.
The next time I flashed something I did not reset Wallet and decided to give it a try and it worked just fine. I never made a thread or told anyone that it was ok since I am no developer such as Freeza and others and I'm pretty sure I would have gotten the old XDA flaming if I did lol.
jbot said:
There was just an article on Engadget (and I'm sure on other sites) that mention a new version of Google Wallet which allows for any card to be added as well as the secure element being moved to the cloud instead of locally on the device.
http://www.engadget.com/2012/08/01/google-wallet-moves-to-the-cloud-opens-up-to-all-credit-and-deb/
Does this mean that whatever state your secure element is in at this point won't matter (assuming the new Google Wallet app supports the device)?
Click to expand...
Click to collapse
i was wondering the same thing
Bit of irony the wallet won't work at a Sprint Store.
I was on Clark's 0.7 rom and just flashed over to .8 as well as flashed a bunch of frameworks since i was trying to mod something. Of course I forgot to clear out my wallet but I just reinstalled it now and it seems to have set back up normal.
I had several flash scares where I would got between ICS and jelly I'd forget to clean wallet when I switch ROMs and reset. It all still worked sadly I can only get wallet to work at school but nowhere else
Sent from my SPH-L710 using xda app-developers app
I can state that before the update that I received on August 1st for Google Wallet, I had my Citi Bank Mastercard in Google Wallet and performed a simple factory reset, since then I was unable to reload my card into Google Wallet. I exchanged my phone for a new one entered my CC information and within a minute Google Wallet was operating again with my Citi Bank Master Card.
The original phone was 1 week old, completely stock, never rooted, I even brought it to a Sprint corporate store that "re-flashed" the phone in an attempt to resolve the problem.
Now I don't know if the update to Google Wallet that I received on August 1st resolved the problem when performing a factory reset or not however the problem absolutely existed.
-TL
Time_Lord said:
I can state that before the update that I received on August 1st for Google Wallet, I had my Citi Bank Mastercard in Google Wallet and performed a simple factory reset, since then I was unable to reload my card into Google Wallet. I exchanged my phone for a new one entered my CC information and within a minute Google Wallet was operating again with my Citi Bank Master Card.
The original phone was 1 week old, completely stock, never rooted, I even brought it to a Sprint corporate store that "re-flashed" the phone in an attempt to resolve the problem.
Now I don't know if the update to Google Wallet that I received on August 1st resolved the problem when performing a factory reset or not however the problem absolutely existed.
-TL
Click to expand...
Click to collapse
good to know. now we need someone to bit the bullet on the post-update wallet.
freeza said:
Let me start off by saying I was one of the people who were kind of scared about this myth when it first came to light. But then I used a bit of common sense in the matter and now i'm 100% sure this doesn't exist, at least on the Galaxy S III. Let me explain why:
The current myth is: Your NFC/Secure Element will cease to function properly if you don't wipe Google Wallet settings before flashing a ROM.
Let's just say you're on a stock ROM, and you happen to do a factory reset, which is about half the same as flashing a ROM. The same goal is accomplished, your /data partition gets wiped so that you can start over. The only difference being that /system doesn't get touched when doing a factory reset from a stock OR custom ROM. Flashing a ROM in recovery however will usually wipe your /system partition. Data wiping is still left up to YOU. Now that we know factory resetting and flashing a new ROM are almost the same, in that they both usually end up with you wiping your data, let's move along.
I'm sure Google and various OEMs wouldn't make the NFC chip or your secure element that easy to break from a "factory reset." This is a function that's available on every Android phone, and people do it all of the time.
Most ROMs will only wipe /system. Now you have to ask yourself what /system has to do with the NFC chip/Secure Element. Especially if in Stock situations the /system partition is R/O (read only). Are there NFC specific files for your particular device stored on your /system partition? No. But then again, those who have had issues with Google Wallet after a flash I can only assume either flashed a ROM that made other changes to the phone, or that particular phone had NFC issues to begin with.
Now, I'm not discounting the probability of this issue being present on the Galaxy Nexus, as I don't own that phone or know how its NFC chip operates or how sensitive it is. However, this issue does NOT exist on the Galaxy S III. Being a 'developer' of ROMs has of course made me have to flash numerous times to test things out on my ROM, all of which have been done with a wiping of /data and none of them have been done with a wiping of Google Wallet data. Now before you say "Well, you've been flashing the same ROM over and over again." This is true for the most part. However, I DID try CM9 and CM10 for a short time as well and my Google Wallet functions just fine, and with the latest update, I just added all of my current credit cards and debit card. I have purchased numerous things from CVS and McDs between the time I first bought my phone (stock) and now (rooted and flashed a lot of times). So those of you who are scared you're going to forget wiping your Google Wallet settings, don't be. It will have no effect on your ability to use NFC in the future.
That is all!
Click to expand...
Click to collapse
I'm proud and embarrassed for a number of reasons here, but mainly for Mr.Freeza posting here while being extra lucid and drunk. I'm not embarrassed for the truth Mr.Freeza is speaking.
He's a top notch developer, and he should be regarded and revered as such most of the time. Just don't take everything has says literally - even though he may be speaking gibberish, he's trying to make a valid point. Blame the alcohol, if you want... He speaketh the truth, and don't you forget it.
And even though my intention is to slightly discourage this epic programmer from letting alcohol running his life, I'm only here to explain what he meant to say and acknowledge his genius.
He says:
1) Wiping /data partition is used in "Factory Restore" function of any rom. So simply wiping /data in recovery or a recovery update script cannot be responsible for losing Wallet functions, or any official rom would have this problem also. Of course, the assumption here is that "factory restore" does no more than wiping the /data partition. But it is a very reasonable assumption, as many people have wiped /data and retained Wallet functions.
2) Wiping /system partition is used in many custom roms. So simply wiping /system in recovery or a recovery update script cannot be responsible for losing Wallet functions, or any custom rom would have this problem also. And of course, many custom roms, which wipe /system partition, don't have any Wallet problems.
In other words, we still don't know why people lose their Wallet functions... But this is not *directly* related to just rooting and flashing custom roms.
freeza said:
Let me start off by saying I was one of the people who were kind of scared about this myth when it first came to light. But then I used a bit of common sense in the matter and now i'm 100% sure this doesn't exist, at least on the Galaxy S III. Let me explain why:
The current myth is: Your NFC/Secure Element will cease to function properly if you don't wipe Google Wallet settings before flashing a ROM.
Let's just say you're on a stock ROM, and you happen to do a factory reset, which is about half the same as flashing a ROM. The same goal is accomplished, your /data partition gets wiped so that you can start over. The only difference being that /system doesn't get touched when doing a factory reset from a stock OR custom ROM. Flashing a ROM in recovery however will usually wipe your /system partition. Data wiping is still left up to YOU. Now that we know factory resetting and flashing a new ROM are almost the same, in that they both usually end up with you wiping your data, let's move along.
I'm sure Google and various OEMs wouldn't make the NFC chip or your secure element that easy to break from a "factory reset." This is a function that's available on every Android phone, and people do it all of the time.
Most ROMs will only wipe /system. Now you have to ask yourself what /system has to do with the NFC chip/Secure Element. Especially if in Stock situations the /system partition is R/O (read only). Are there NFC specific files for your particular device stored on your /system partition? No. But then again, those who have had issues with Google Wallet after a flash I can only assume either flashed a ROM that made other changes to the phone, or that particular phone had NFC issues to begin with.
Now, I'm not discounting the probability of this issue being present on the Galaxy Nexus, as I don't own that phone or know how its NFC chip operates or how sensitive it is. However, this issue does NOT exist on the Galaxy S III. Being a 'developer' of ROMs has of course made me have to flash numerous times to test things out on my ROM, all of which have been done with a wiping of /data and none of them have been done with a wiping of Google Wallet data. Now before you say "Well, you've been flashing the same ROM over and over again." This is true for the most part. However, I DID try CM9 and CM10 for a short time as well and my Google Wallet functions just fine, and with the latest update, I just added all of my current credit cards and debit card. I have purchased numerous things from CVS and McDs between the time I first bought my phone (stock) and now (rooted and flashed a lot of times). So those of you who are scared you're going to forget wiping your Google Wallet settings, don't be. It will have no effect on your ability to use NFC in the future.
That is all!
Click to expand...
Click to collapse
Haha i remember this chat! Glad you made the write up. People need to know lol.
My suspicion (and only a suspicion) is that there is nothing wrong with the NFC "chip" but rather once you negotiate the security settings between Citi Bank and Google Wallet an encryption key is negotiated which is made out of a unique device identifier (NFC serial number?) and a pseudo random key. By issuing a factory reset on the phone it will in turn destroy the negotiated encryption key and that Citi Bank (or whoever holds the encryption key for the server) never destroys that key preventing any further authentication since the bank says that NFC # xyz's encryption key doesn't have what I have on file.
I'm guessing this will eventually be fixed but my past experience working with IT departments (as a vendor) at banks and other financial institutions tells me that they unless a current problem causes a security issue or allows fraud or theft, they are very slow to move and once a problem is positively identified it could easily take a year or more to provide a solution.
I don't have Google Wallet setup on my phone, I was just wondering how hard is it to actually clear all the settings in Google Wallet? If it's not that difficult and if you can always remember to clear it, wouldn't it be just easier to clear it before you flash? I guess that is if you can remember to clear it first!
Sometimes we get so excited about flashing a new ROM we don't always do what we're supposed too!
None-the-less, reading this still left me very confused on to do it or not to do it
What!
Can or should I install Google Wallet on a rooted phone?
No, we do not support Google Wallet on rooted phones.
Click to expand...
Click to collapse
Ok so this may be old but I was probably one of the few that decided not to turn in my newly bought note 2 for a refurbished one just because my google wallet app wasn't working right. But I'm here to say there is a fix! Now I am no dev,and have no way to figure out exactly what fixed it but I can give you the steps I took. I actually was just upgrading to kitKat and accidently fixed it. So I deleted google wallet app and it's backup (in titanium backup)had my wallet account reset.(which google has to do, this alone did not fix the problem. Email them)I Waited two days, was flashing 4.3 roms while I waited. Coming from dirty unicorns3.8 I flashed the smrf tool and put Mk4 on my phone. Then used PA gapps 121513 4.4.2, cm11 121913, and plasma kernel for KitKat. Wiped everything besides external. EVERYTHING. Flashed the goods and did not restore any app data *.got dev tools enabled and changed run time to ART. wallet was installed with the gapps. I was about to delete it (like I always do)but I decided to our open it. And viola it is now up and working again. And just to recap I did have the secure element broken message for almost 5 months now. And without swapping my phone it now works. Hope this helps others like me who hung on to their notes when this happened to them.
I observed the exact same thing, but I do not believe any of the steps you outlined corrected the secure element issue. Kit kat now uses a different method that is software based to securely store Wallet information so the secure element is not needed/used. I decided to test that theory when I realized Wallet was working on CM11 by going back to stock rooted being careful to reset Wallet prior to the flashes. Sure enough on the stock rom, the secure element was still fried. Looks like for those of us wanting Wallet on a device with a non functioning secure element we will have to run a kit kat rom.
digida said:
I observed the exact same thing, but I do not believe any of the steps you outlined corrected the secure element issue. Kit kat now uses a different method that is software based to securely store Wallet information so the secure element is not needed/used. I decided to test that theory when I realized Wallet was working on CM11 by going back to stock rooted being careful to reset Wallet prior to the flashes. Sure enough on the stock rom, the secure element was still fried. Looks like for those of us wanting Wallet on a device with a non functioning secure element we will have to run a kit kat rom.
Click to expand...
Click to collapse
Good to know. I was under the assumption the secure element was directly tied to Google and that was tied directly to your device. I didn't think a different version of android would fix it. I have tried reverting back to 4.1,4.2,and 4.3 and saw no difference but when trying 4.4 it did work but that was after trying everything I described.
So, I am getting my phone replaced through ATT and I want to know what I did to cause the problem in the first place. so I don't do the wrong thing again. I have the H810 through ATT. I got the error on boot "Security Error. Authentication fail #9" and had to flash the PR firmware to get it back up and running which is undesirable. The three things I did before rebooting are as follows:
1) Remounted the system partition as rw,
2) Removed two system apps with titanium backup. (Not sure which ones but I am pretty certain they were ATT apps.)
3) Attempted to install the Xposed Frame work zip using flash gordon
I am assuming one of these three things did it. But which one? Any help will be appreciated. Thanks.
I'm going to go with 3.
xposed doesn't work on the g4...
sobertillnoon said:
So, I am getting my phone replaced through ATT and I want to know what I did to cause the problem in the first place. so I don't do the wrong thing again. I have the H810 through ATT. I got the error on boot "Security Error. Authentication fail #9" and had to flash the PR firmware to get it back up and running which is undesirable. The three things I did before rebooting are as follows:
1) Remounted the system partition as rw,
2) Removed two system apps with titanium backup. (Not sure which ones but I am pretty certain they were ATT apps.)
3) Attempted to install the Xposed Frame work zip using flash gordon
I am assuming one of these three things did it. But which one? Any help will be appreciated. Thanks.
Click to expand...
Click to collapse
I'll take #3 for $500, Alex.
That'll be a big ol #3!!
Eagle1337 said:
xposed doesn't work on the g4...
Click to expand...
Click to collapse
I tried looking into this but found nothing. This is well documented? Is it something that needs to be recompiled for the G4? Is this a 5.1 issue? I used the 5.1 arm 64 one specifically. Can you link me to something describing this?
http://forum.xda-developers.com/g4/general/wip-install-xposed-framework-t3140904
sobertillnoon said:
I tried looking into this but found nothing. This is well documented? Is it something that needs to be recompiled for the G4? Is this a 5.1 issue? I used the 5.1 arm 64 one specifically. Can you link me to something describing this?
Click to expand...
Click to collapse
the hassles of bricking a phone due to negligence. Lol. reading the forums and searching them is your best friend with root
I have the Sprint G4, and after rooting it, I started to uninstall all the bloat crap that kept running processes alive. Apparently, uninstalling key apps (including Google apps) will cause the security error boot.
I personally did not run into the boot error until I accidentally uninstalled Google Services Framework (Yes even experienced rooters and devs can make head-slapping mistakes). I personally have to go with #2, since that was the step that bricked my phone.
As of now, I sent my phone into LG for warranty service, even though I told them I caused the error myself by rooting and uninstalling google services framework. Knowing that, the person I chatted with insisted they would fix the "software failure" under my 1-year warranty. So if you don't have the KDZ/TOT files necessary to restore you phone (or are being charged for a phone replacement at your service provider, like Sprint charges $75 dollars for a swap), just send it into LG. I'll update when I hear back from them :fingers-crossed:
sobertillnoon said:
So, I am getting my phone replaced through ATT and I want to know what I did to cause the problem in the first place. so I don't do the wrong thing again. I have the H810 through ATT. I got the error on boot "Security Error. Authentication fail #9" and had to flash the PR firmware to get it back up and running which is undesirable. The three things I did before rebooting are as follows:
1) Remounted the system partition as rw,
2) Removed two system apps with titanium backup. (Not sure which ones but I am pretty certain they were ATT apps.)
3) Attempted to install the Xposed Frame work zip using flash gordon
I am assuming one of these three things did it. But which one? Any help will be appreciated. Thanks.
Click to expand...
Click to collapse
Thanks for the heads up on that. The apps or Xposed, it doesn't matter at this point. I got a replacement from AT&T and wound up bricking it within hours doing the same root method I did before. (though, this was Authentication fail #11). I am actually quite happy with the PR firmware and no root. Without xposed and unlocked boot loader, root doesn't really serve me that much and I can live without for now. Maybe one day someone will get a hold of the AT&T TOT and a more reliable root. Then again, I might just sell this thing on ebay and get an H815. choices.
Bondster45 said:
I have the Sprint G4, and after rooting it, I started to uninstall all the bloat crap that kept running processes alive. Apparently, uninstalling key apps (including Google apps) will cause the security error boot.
I personally did not run into the boot error until I accidentally uninstalled Google Services Framework (Yes even experienced rooters and devs can make head-slapping mistakes). I personally have to go with #2, since that was the step that bricked my phone.
As of now, I sent my phone into LG for warranty service, even though I told them I caused the error myself by rooting and uninstalling google services framework. Knowing that, the person I chatted with insisted they would fix the "software failure" under my 1-year warranty. So if you don't have the KDZ/TOT files necessary to restore you phone (or are being charged for a phone replacement at your service provider, like Sprint charges $75 dollars for a swap), just send it into LG. I'll update when I hear back from them :fingers-crossed:
Click to expand...
Click to collapse
OK so I smashed my s5, am a UDP verizon guy and hooked on the open bootloader, so i searched far and wide for another one with the 15 chipset...which I didn't find but I found a note 4 with it.
I bought it and unlocked it and loaded on a rom I loved. (5.0.1 og5). Well...no sense lying here...I was trying to do some less than kosher things regarding my ex's Facebook account with it. In the process I wasn't smart enough to cross check MD5s (a precaution I learned all too well) and opened an app that has me baffled.
It basically hijacked admin on my device completely. No Antivirus program can touch it, though many detect it. "Unknown sources" in my security folder is stuck permanently enabled, and I can't take over as admin on my own brand new note4.
I have tried flashing twrp and titanium backups to no avail, and also tried the safe stock og5 firmware through Odin but it never completes. I am stuck. I have logcat records and all the tools I would think might help, but I can't get rid of it...it seems to have used root and embedded itself into every facet of the device.
I am willing and ready to do anything including a full unroot and stock rom, I just don't want a locked update. Can anyone help me please?
As of now, no roms break it, only the stubborn malware CM app tries to get rid of it, but only identifies it as "suspicious file". My user admin and unknown sources are both locked, and a gaggle of bizarre log events happen constantly, forcing my device into crazy lag. As soon as it happened I received a couple random number-link blank text messages, but I never opened them. I don't have the numbers saved as I've flashed the phone like 30 times since trying to rid myself of this. Aside from the lag and locked unknown sources and admin, and an inability to clear trusted credentials, the phone seems to run normally, though I am scared to use it to log on to pretty much anything. The malware didn't come from a text, but from an app that I knowingly permitted thinking it was something else and I feel like a moron for it. It doesn't seem to have a name. It installed as an untitled app and I couldn't delete it with the root system app deleter, because it put a green bar over the check box in the app. I got rid of it with titanium, but to no avail. It still lurks.
Thanks in advance, and let me know of any screens hits or logs or tests I can provide to help.
At that point, I would recommend using Samsung's Smart Switch for PC program to do an emergency firmware upgrade & initialization. This will download a full copy of the stock firmware for the device (including a few bits that you won't find in stock firmwares available for download through sites like SamMobile) and will erase everything on the device and restore your phone to stock firmware.
If you are in the US and have a Best Buy nearby, you can see if one of their Samsung reps can perform a factory recovery using their SMART tool (which will do the same thing that Smart Switch's emergency firmware initialization will). Officially, rooted devices are not supported and they may rightfully refuse to do this, but it's worth asking if you don't have a computer to use for Smart Switch or don't want to wait.
You will need to redo the developer conversion, but that's the only thing I can think of that will definitely completely restore your phone to stock and eliminate all traces of whatever you installed.
thanks. that solved my problem and got it back to stock, rid of the malware completely. unfortunately, when i tried to return to the rom i had used, everything fell apart for me :/.
Hey all,
I've done heaps of searching here and the wider web but only found reference to rooted phones failing to take updates.
I can't get a screenshot on here right now as I'm at work so no wifibut:
- Android OS _______________3.04GB :silly:
- Chrome__________________434MB
- Google Services ___________24.13MB
- etc
When I read about the failed update I checked in there and sure enough I have a 2017-5 patches system update sitting there failed, when I retry it it will download successfully then do step 1/2 of the installation then fail.
So it seems this would be the problem but the phone is definitely NOT rooted, any ideas??
thanks
You speak in codes, man. Could you explain your issue simpler? Right now I see an Android OS usage of 3.04GB. That seems abnormally large times 10. No one should have that, really. So it seems like your Android OS process downloaded multiple copies of system updates in error. Is that your problem?
Your post is still largely incomprehensible, so I won't make a final conclusion.
These are just suggestions:
1) If your phone is downloading system updates over and over, just damn update so it stops, or factory reset your phone.
2) If this is some kind of a rogue app, you are literally funked. Good luck trouble shooting it.
In any case, GL!
Yes, android OS used 3.04GB in ~5 days, my best guess is it was due to repeated attempts at '2017-5 patches system update'
Sorry, when I did a search I got heap of references to rooted phones having this issue so I guess I just talked from that reference point? It seemed to be a known issue but for rooted phones.
I just wanted to be clear that my issue matched those symptoms but was not rooted.
1) I've tried a manual update (many times) fails at the same point, I assume this is what is causing the data usage, as mentioned above.
2) Pretty sure it's not a rogue app
I'll try a factory reset, it's only a couple of weeks old (warranty replacement) so I hadn't really thought to reset straight away.
The phone doesn't necessarily need to be rooted to fail the update. A previously rooted phone can also fail to update as described, but typically that would mean an unlocked bootloader. I would have figured that the phone would have been reimaged and the bootloader locked on a refurbished phone, but maybe that doesn't happen. Is the bootloader unlocked? If so you could image the phone yourself to see if that works to fix it. If the bootloader is locked and a reset doesn't work, then I figure you might need to contact support about getting a different phone.
https://developers.google.com/android/images
I think you've gotten good information from everyone so far but just to add some clarity.
I had this exact same issue and was not rooted but did have an unlocked bootloader.
A factory reset did not resolve it. At the time I had issues, there were questions about rooting the stock images so I flashed PureNexus and have never looked back or had the issue again. Also, Verizon did add data to my plan and credit my account for the additional charges to negate the cost. Hope this helps!
It sounds like an issue with your phone that Pixel support might be able to help you with but they will certainly suggest a factory reset so you should do that first. Since you have a refurbished phone you don't know how the previous owner was using it and its possible a modification he made is still on the phone and causing you problems. If the failed system update isn't actually causing the excess data usage it could also be a carrier issue. I know some Project Fi users had that problem and it was related to the service. Google gave people credit for the excess data. You could also have an app that is interfering with the update so a factory reset should definitely be your first step and I'm guessing it's fairly likely to fix your problem.