ZenPad 10 connection impossible after screen replacement

Solved
jeannets Posted messages 28371 Registration date   Status Contributor Last intervention   Ambassadeur -  
jeannets Posted messages 28371 Registration date   Status Contributor Last intervention   -
Hello,

I have changed the screen+digitizer and complete frame. The battery was disconnected for a week on an Asus Zenpad 10 Z300M.
I had to reset it, actually it did it by itself upon reconnecting the battery.
Process: country, language, Wi-Fi, accepted Asus terms, and then I come across....
This device has been reset. To continue, sign in with a Google account that has already been synced on this device...
So I enter the account and password... error on a black background... Message:
 Unable to connect to the device due to an unknown error. Please try again in 24 hours or try with another account.


And this happens every time... for two weeks.. when I try again.

I waited 24 hours, then 72 hours and a week, I attempted a factory reset, but it won't cooperate, won't even start from scratch..

If I try with another Gmail account, I get this message:
This device has been reset. To continue, sign in with a Google account that has already been synced on this device
as well... The account is valid; but has never been synced with this device.

The root of the problem is that the person does not remember the account and password they created when setting up their tablet.. But I don't understand how with a reset we can't start from zero..

There are many similar problems on the Web... what to do to get out of this endless loop...

Thank you in advance

Configuration: Windows / Firefox 57.0

3 answers

jeannets Posted messages 28371 Registration date   Status Contributor Last intervention   Ambassadeur 6 598
 
OK, my problem is FRP (Factory Reset Protection) from version 5.0 Lollipop.

Now that I know what it is, all I have to do is find the remedy...

If anyone knows the pharmacist, they will be welcome... even in private message.
7
jeannets Posted messages 28371 Registration date   Status Contributor Last intervention   6 598
 
Not resolved, but the path being winding, I will close the subject here.
0
jeannets Posted messages 28371 Registration date   Status Contributor Last intervention   Ambassadeur 6 598
 
So, here it is... the said tablet is working again... because the person gave me new clues to find the right password... and after a few attempts, the tablet came back to life...

So I won’t know the solution to overcome the blockage... with ADB or Fastboot or TWRP... I admit I tried, but it just never goes as indicated... Adding that it’s the holiday season and one needs to focus as much as possible, enjoy the moment, and be free of interruptions...

I’m still quite happy to be freed from this thorn in my side...

Happy holidays to everyone..
1
madmyke Posted messages 52304 Registration date   Status Moderator Last intervention   12 483
 
Hello

I come across the topic and the solution was?
Since my wife has the same tablet (which works)

Thank you.

--
"We swallow the flattering lie in one big gulp and we drink the bitter truth drop by drop."
0
jeannets Posted messages 28371 Registration date   Status Contributor Last intervention   6 598
 
OK, it's good because it's you...!

a) The real solution is to keep the account xxxx@gmail.com that was used to open Android warm and of course the password... The day it gets reset (even if you don't want it to), you'll need to enter that account again, otherwise you'll be stuck. It's not even possible to start over with a new account because Google recognizes your tablet at every login.

b) The technical solution to bypass the protection is not simple... it looks like hacking... not approved. Check here https://www.phonandroid.com/forum/threads/tuto-supprimer-frp-sur-asus-z300m-android-7-0.179257/ I've been working on it for a month and it still doesn't work... let's say I'm making progress and I've reached point 5 of the tutorial...
There is also an instructional video on how to access inaccessible menus https://www.youtube.com/watch?v=rQf8LqWDl4w&app=desktop

So be careful, I think the problem exists on all devices since Android 5 Lolipop.
0