Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[WARNING] Google Music and Root [MEGA UPDATE--FIXED]

OP Amphibliam

16th May 2012, 12:25 AM   |  #11  
ragnarokx's Avatar
Senior Member
Flag GMT-5
Thanks Meter: 486
 
2,132 posts
Join Date:Joined: Sep 2010
More
Quote:
Originally Posted by codesplice

I think it has to do with how the app authenticates with your Google account. Each time you click "allow" on the prompt to allow the Music app access to your account counts as an activation.

Last time I changed ROMs and restored Google Music with data via MyBackup, it didn't ask me to authorize - it was already authorized. Potential work around?
16th May 2012, 12:41 AM   |  #12  
Amphibliam's Avatar
OP Senior Member
Thanks Meter: 413
 
1,915 posts
Join Date:Joined: Feb 2011
More
Possibly. Doesn't help me at this point. My tenth device was reached when I upgraded to build 36. I forgot to flash gapps, so it killed all my google accounts. I tried restoring data from the Music app on my Inc2, but no dice. My guess is once this s**t really hits the fan, people are gonna find a fix. If this happens again with no workaround, my fix is called Amazon MP3.
16th May 2012, 12:50 AM   |  #13  
Anthonok's Avatar
Senior Member
Flag St. Cloud
Thanks Meter: 211
 
1,384 posts
Join Date:Joined: Jul 2010
More
http://support.google.com/googleplay...answer=1230356


Sent from my Galaxy Nexus using xda premium
The Following User Says Thank You to Anthonok For This Useful Post: [ View ]
16th May 2012, 12:52 AM   |  #14  
Amphibliam's Avatar
OP Senior Member
Thanks Meter: 413
 
1,915 posts
Join Date:Joined: Feb 2011
More
"Please note that you can only revoke access to four devices per year."
16th May 2012, 12:52 AM   |  #15  
adrynalyne's Avatar
Recognized Developer
Thanks Meter: 5,723
 
9,714 posts
Join Date:Joined: Dec 2008
They can't provide an AOSP supported device and then limit Google services to it and not expect an uproar.

Seems to me a simple data wipe would do the same thing.
Last edited by adrynalyne; 16th May 2012 at 12:54 AM.
16th May 2012, 12:57 AM   |  #16  
Amphibliam's Avatar
OP Senior Member
Thanks Meter: 413
 
1,915 posts
Join Date:Joined: Feb 2011
More
Honestly, the only reasons why this isn't widespread is because people just haven't flashed enough ROMs yet. This won't just affect the Nexus, but ANY rooted Android device that flashes 15 or more ROMs in a year. Which is like 99% of the rooted population. My guess is that within 1-2 months, this will be all over the internet. I was just unlucky enough to be one of the first. But this really is absurd. What is the reasoning behind limiting the # of devices that can be revoked? Absolutely ridiculous.

And yes, any data wipe would do the same thing, so I imagine if you have a phone with issues (like the Nexus) and you buy the first one, then try 2-3 data wipes/different ROMs to get signal drops/color/whatever fixed. That's 3 devices. Then, they get 2 more Nexuses, and try the same thing on the first, but the second device is fine, so they flash a ROM. That's already 7-9 devices right there. That means you can only flash 5-7 ROMs before you encounter this issue.
Last edited by Amphibliam; 16th May 2012 at 01:00 AM.
16th May 2012, 01:00 AM   |  #17  
adrynalyne's Avatar
Recognized Developer
Thanks Meter: 5,723
 
9,714 posts
Join Date:Joined: Dec 2008
Quote:
Originally Posted by Amphibliam

Honestly, the only reasons why this isn't widespread is because people just haven't flashed enough ROMs yet. This won't just affect the Nexus, but ANY rooted Android device that flashes 15 or more ROMs in a year. Which is like 99% of the rooted population. My guess is that within 1-2 months, this will be all over the internet. I was just unlucky enough to be one of the first. But this really is absurd. What is the reasoning behind limiting the # of devices that can be revoked? Absolutely ridiculous.

Wiping a device has the same effect.

You don't need to flash a rom, because it doesn't change your esn, meid, or even your android_id.
16th May 2012, 01:00 AM   |  #18  
Amphibliam's Avatar
OP Senior Member
Thanks Meter: 413
 
1,915 posts
Join Date:Joined: Feb 2011
More
I updated my post.
16th May 2012, 01:03 AM   |  #19  
adrynalyne's Avatar
Recognized Developer
Thanks Meter: 5,723
 
9,714 posts
Join Date:Joined: Dec 2008
Quote:
Originally Posted by Amphibliam

I updated my post.

I am sure that once this issue is out in the open, it will be a rule that you can only deauthorize 4 unique devices each year. As of right now it is not differentiating between multiple instances of the same device.

I have no idea who to bitch at, but I'll support anyone who starts a complaint, petition, or whatever.
The Following 2 Users Say Thank You to adrynalyne For This Useful Post: [ View ]
16th May 2012, 01:18 AM   |  #20  
quick_'s Avatar
Senior Member
Flag Houston
Thanks Meter: 37
 
204 posts
Join Date:Joined: Jul 2010
More
It was mentioned earlier but, what I do is restore my "accounts/sync" with titanium backup.

That way you don't have to authorize the device each time.

Be sure to:
  1. After backing up all apps and system data, then after flashing a new ROM on first boot, install titanium backup (pro or not) VIA APK
  2. Then run Titanium Backup and restore the accounts
  3. Then restore the google music app with DATA via Titanium Backup
  4. Then use the market and music like normal without any need for autorizing a new device etc..

The Following 5 Users Say Thank You to quick_ For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes