Long story short:
My goal is to root this TF201 (latest kernel&4.1.1).
A few weeks ago I successfully RMA:ed my bootloader unlocked transformer and got it back soon with a replaced motherboard.
Now when I try unlocking it through the ASUS Bootloader Unlocker app V6 it tells me something like "An unknown error has occured" every time I try to run through the procedure.
From what I've read in other threads it, the unlocker app, uses the devices' serial number and matches it with the ASUS servers, so my guess is that since i have the same SN as before it think that i'm trying to unlock an unlocked device which is neither allowed nor supported.
So my question now for you, more experienced and qualified, guys is: am i completely boned, or is there any other way to unlock via other software, or simply what would you recommend?
To me this device isn't really worth keeping unless it's rootable
I have a completely stock TF201 running 4.1.1.
I am unable to boot into recovery and end up with red exclamation error.
This has been RMAed three times due to charging issues and the ASUS unlock tool will not work (Getting the usual 'network connection issue' error).
I've talked with ASUS support multiple times with regards to the unlock tool and they dismiss it saying they will not support unlocking the device.
I have also tried asking ASUS support to get help with device tracker, even escalating the issue, and they have all said the same thing: "There is no problem on our end, we cannot help you."
Without being able to unlock the bootloader, is there any possible way to get 4.4 on this device?
So I installed a custom rom on my phone after unlocking BL and all that a while ago.
I recently got the unlock code from my service provider and was trying to sim unlock the L9. I get an error saying I have an invalid code (which it isn't). A quick google told me that custom roms sometimes won't let you use unlock codes.
I tried using the guide from @cmahendra to reset back to the original kdz/ROM for the phone but it stops at 15% and says phone not connected (even through all the drivers install/are installed correctly).
Does anyone know best way to unlock the phone with the unlock pin provided? Or at least how to reset it back to normal?
Phone: Asus Zenfone 3 ZC520TL
Hi all. So I have a frustrating issue with my phone after having updated to the last official firmware from the Asus website. I noticed that the phone operation was very slow, so I decided to do a factory reset from recovery. Everything went well until I am somehow locked out of my phone via FRP. The weirdest thing is that instead of asking for google credentials, it's asking for a pattern, which I am correctly inputting but it refuses to recognize it. So now I'm stuck with a locked out phone. Am I SOL at this point or is there a way to get past this other than taking it to a service center?
Things I've tried that haven't worked:
1. tried to erase user config in fastboot (returned error FAILED)
2. wiped all data in recovery
3. tried to flash to an older version via asus flashtool but didn't work as the device isn't recognized
Any help would be greatly appreciated.
xenoche said:
Phone: Asus Zenfone 3 ZC520TL
Hi all. So I have a frustrating issue with my phone after having updated to the last official firmware from the Asus website. I noticed that the phone operation was very slow, so I decided to do a factory reset from recovery. Everything went well until I am somehow locked out of my phone via FRP. The weirdest thing is that instead of asking for google credentials, it's asking for a pattern, which I am correctly inputting but it refuses to recognize it. So now I'm stuck with a locked out phone. Am I SOL at this point or is there a way to get past this other than taking it to a service center?
Things I've tried that haven't worked:
1. tried to erase user config in fastboot (returned error FAILED)
2. wiped all data in recovery
3. tried to flash to an older version via asus flashtool but didn't work as the device isn't recognized
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Look on YouTube for FRP bypass and your phone model
Sent from my Moto E (4) using Tapatalk
@xenoche
Look inside here.
Hey folks,
my girlfriend just sold her P6 to a work friend and I wiped the device and thought "thats it". (I even removed the device from the Google Account!)
Sadly thats not it
The phone wants to have a/the? PIN of the device. We never set any PIN (which the google account confirms). What PIN is the device referring to?! Its not the lock-pin she normally used.
Nevertheless the device allows for a recovery via phone number and/or the old google account. We tried that and the P6 even lists the Name of my girlfriend and she gets a login notificiation on her new Pixel 7. But after entering the Password the P6 just say "an error occured, try again." (Ein Fehler ist aufgetreten)
But it doenst matter what we try or how often. We get always back to that screen and into the "an error occured".
So basically we/she are stuck. Any chance I can fix it with some ADB command or anything (dunno if the developer options are even switched on).
Thanks
Bastian
did you try reinstall the stock firmware?
there could be a few different pins
P.U.K is an acronym for Pin Unlock Key
Some carriers also put a SIM PUK on your SIM card when they sell you the SIM card
SIM Network Unlock Pin (NUP) is a code used to unlock an Android phone or iPhone from its original carrier so that it may be used on other carriers
picture of the error might help
tutibreaker said:
did you try reinstall the stock firmware?
Click to expand...
Click to collapse
I only did a factory reset via bootloader thingy on the phone.
nutzfreelance said:
there could be a few different pins
P.U.K is an acronym for Pin Unlock Key
Some carriers also put a SIM PUK on your SIM card when they sell you the SIM card
SIM Network Unlock Pin (NUP) is a code used to unlock an Android phone or iPhone from its original carrier so that it may be used on other carriers
picture of the error might help
Click to expand...
Click to collapse
I only got one in german....
man1acc said:
Hey folks,
my girlfriend just sold her P6 to a work friend and I wiped the device and thought "thats it". (I even removed the device from the Google Account!)
Sadly thats not it
The phone wants to have a/the? PIN of the device. We never set any PIN (which the google account confirms). What PIN is the device referring to?! Its not the lock-pin she normally used.
Nevertheless the device allows for a recovery via phone number and/or the old google account. We tried that and the P6 even lists the Name of my girlfriend and she gets a login notificiation on her new Pixel 7. But after entering the Password the P6 just say "an error occured, try again." (Ein Fehler ist aufgetreten)
But it doenst matter what we try or how often. We get always back to that screen and into the "an error occured".
So basically we/she are stuck. Any chance I can fix it with some ADB command or anything (dunno if the developer options are even switched on).
Thanks
Bastian
Click to expand...
Click to collapse
During setup, the unit asking for the pin refers to the screen lock pin or password that was used, and no other. You can try 0000 and see if that works, but it likely won't. If the error persists, contact Google and explain it to them. Only don't be surprised if they can't help you.
The only ways to fix this are as follows: 1) contact Google as mentioned, since there is an error in the process, or 2) attempt to unlock the bootloader. If you can successfully unlock the bootloader, then FRP should not kick in the next time the unit is started. If neither option is available, then ADB will not help you here, as by design Google makes it so FRP cannot be bypassed in so simple a manner.
Strephon Alkhalikoi said:
During setup, the unit asking for the pin refers to the screen lock pin or password that was used, and no other. You can try 0000 and see if that works, but it likely won't. If the error persists, contact Google and explain it to them. Only don't be surprised if they can't help you.
The only ways to fix this are as follows: 1) contact Google as mentioned, since there is an error in the process, or 2) attempt to unlock the bootloader. If you can successfully unlock the bootloader, then FRP should not kick in the next time the unit is started. If neither option is available, then ADB will not help you here, as by design Google makes it so FRP cannot be bypassed in so simple a manner.
Click to expand...
Click to collapse
Ok thanks, I'll contact Google.
There has been one PIN and never any else and this doesn't work.