i just got my warranty replace atrix and i was trying to unlock it with the guides on here. i did it correctly last summer but for some reason the phone didnt take the fix too well. now rsd lite is saying error code unable to retrieve interface handle and says theres no os. what can i do to fix this? thanks in advance
can't factory reset = lock pattern + unknown gmail + "*** LOCKED ***" bootloader
First off, let me clear the obvious: this phone isn't stolen. I purchased it a few days ago off of eBay (item #271070275773) and took it to Verizon who verified that it hadn't been reported stolen. The LCD was smashed so the previous owner sold it for parts and was unable to reset/un-lock the pattern. (And the seller says they don't know it.)
I fixed the LCD/digitizer and discovered this infuriating pattern lock. I assumed that, like my other Thunderbolt, I could simply do a factory reset or throw some PG05IMG.zip onto it, or SOMETHING... but nothing I've tried so far works. (That is to say, it just does a normal boot to the lock screen -- or goes into an equally infuriating reboot loop that just repeatedly ends at the green-on-white HTC logo.) I assume it has everything to do with the fact that, at the top of the "skateboarding" screen, it says in capital pink letters: *** LOCKED *** -- please note it doesn't say "security warning" as I've seen in most of my searching. But then again, I could be totally completely wrong.
Can anyone shed some light on my situation? I'm new to modding Android devices, but am good friends with Google when I know what exact terms to ask him.
I think you would need to take it a step further than just a factory reset as that would leave behind some system information such as security. It sounds like you would need to completely wipe everything and flash a rom but to do that you would need to enable USB debugging which you cannot because of the pin. I have heard there are ways to get past it but I don't know how many retries you would get in order to do that.
Sent from my Thunderbolt using Tapatalk 2
I think this might help you out: http://forum.xda-developers.com/showthread.php?t=1310014
Basically, you use adb and fastboot to flash a full RUU which will completely unroot, wipe, destroy everything you've done. The post has a lot of information and some seems a little confusing, but follow along and I think you will be OK.
I thought I would post this here as its not really phone specific but i have a ZTE (kis lite v790)
I've found ROMs for it but they are from other providers. the signed update.zip checks if your phone is from the right provider and exits if it doesn't match. All the rooting attempts on my phone have failed and if i edit the update.zip\META-INF\com\google\android\updater-script it fails the signature check.
how on earth am i supposed to update my phone?
nobody has any advice?
Hey guys!
I just bought a new phone and when I try to root, the adb doesn't give the code to unlock bootloader, just show the message "Could not get unlock data". Anyway, other thing is that I never saw the yellow message saying "device is unlocked status code 1"... Code 1!?
What thats mean? I just know about code 0 and 3, anyone can help me?
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.