• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Google Wallet Guide: Avoid Secure Element Brick

jmar

Nexican
Thought this might be useful and relevant...

Hey Y'all!

My guide to Google Wallet: Simple and fail-safe...here goes!

BACKGROUND

I have been using Google Wallet since December 27, 2011.

I have employed this method since December 27, 2011.

Other than Google's shutdown of the app when security issues disabled the app, I haven't had a single issue with Google Wallet.

GUIDE

1. Install Google Wallet: Google Wallet Thread on XDA: latest version always posted in OP

Credit: OneAn9ryN00b

2. Use Wallet.

3. When prepping for a ROM flash/factory reset first reset GWallet from within the app. After inputting your pin, tap the menu overflow button in the top right corner and choose Settings. Now, select Reset Google Wallet app. Confirm and let it do its thang!

This step is OPTIONAL. I do it because I'm weird like that.
4. Next, Navigate to Settings app--->Apps--->All--->Wallet: Wipe Data

5. Now, backup Google Wallet app using Titanium Backup (buy this app!; best tool for all app backups). Because this app requires root, you will have to find an alternative if you are not rooted. You could also just sideload Google Wallet as you did the first time you downloaded it.

6. Wipe data, et al/Factory Reset.

7. Restore (DO NOT restore data!)/sideload app

8. Setup Google Wallet from scratch.

Profit!

jmar

P.S. If I've made any errors, please let me know ASAP!

Ultimately, I take no responsibility for a Secure Element Error and am only trying to help my fellow Wallet users.

Hope I helped.

Contributions to this guide from: NSutherl, jova33, efApple, AndroidDad75, and AntimonyER.

THANKS Y'ALL!
 
Hey there.

Do you all think that this thread deserves to be sticked?

If any user feels like another topic should be stickied contact a Guide so that we can take care of it.

And like I said if you think this thread doesn't deserve to be sticked I will unstick it.

Thanks in advance,

jmar
 
I think it's become less of an issue since Google updated to cloud based payments. But basically the Secure Element brick kills your ability to use Google Wallet as a mobile payment system using nfc. Basically as an added security measurement in case a device was stolen, Google made it so that the Secure Element that contain the sensitive credit card info breaks if the system partition is reset or changed. This would happen if one flashed a new rom, unlocked the bootloader, or simply performed a factory reset from either the main menu or recovery. By doing this, a thief would therefore be unable to use it to fraudulently make purchases. However, many normal users fell victim to this when flashing new roms and there is no way to fix this issue other than getting a new device.
 
I do to be on the safe side. Same reason I make nandroid backups. Choose what works for you my friend. This guide has never failed me. Started it when I got the GNex 1.5 years ago.
 
Agreed. A little over a year ago, if you flashed a new rom while Wallet was set up, it was a guaranteed Secure Element Brick. These days, it happens less than 10% of the time I'd say. However it only takes one to ruin it forever. So it's better safe than sorry to just reset it every time.
 
That little warning at the top of the app is there because Wallet is not supported on carrier devices (except for Sprint). What makes the Nexus 4 and Galaxy Nexus before it strange is that Wallet is supposed to be on those devices and if so, can be used. But Google doesn't technically support it.

To answer your question:

Basically, payments stop working.

Now, keep in mind, there have been reasons in the past that rendered the app itself to not be fully functioning, but payments still worked. This was in the early Galaxy Nexus days.

I imagine that if you brick the secure element, no amount of flashing and wiping would allow a user to re-provision any debit/credit card to the app under any gmail account, ever.

This is my best understanding of how that all works.

Not an expert by any means.

Hope that was helpful nevertheless.

jmar
 
If you see this error, your secure element is bricked and cannot be fixed.

photo-12-1-300x291.jpg
 
Back
Top Bottom