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.
Related
Yesterday I picked the phone from my pocket, and on the display it said that the unlock code had been entered incorrectly. As I always do I entered the code, but this time it said that I would have to wait 30 seconds for my next attempt as I had entered the wrong code five times. I did, but still it won't accept the code. I know it is the right one because I use the same code as my SIM PIN, which works perfectly fine. Also, my SO knows the code, and when asked to unlock the phone she correctly responded with "it doesn't seem to work?"
I'm using Lite'ning ROM, and on other foras I've read that it is possible to have the device reset through the same screen where the code is entered. On my screen the only option is to type the code, and a button for emergency calls. No "recover password" button. Still, by accident I found out that I could access the phone by pressing the home button twice, which would take me to the voice dialing menu, and it would then be possible to use it as normal until the screen is locked again.
Today, I did a CWM factory/data/cache reset, and reflashed an old backup. Still, it asked for the pin, and said that I had entered the incorrect one. I searched, and found out that to get rid of this I would have to flash a stock ROM. I did, and ended up in the notoric boot loop. The fix for this is apparently to wipe user data from stock recovery, but this requires the password mentioned earlier. Which means I'm stuck.
I tried reflashing the backup I had of the Lite'ning ROM, and wipe data/factory reset from there, but it still does not work with the stock rom.
So:
Any ideas? Is my only option to go to a service center and have it fixed? Will it be a problem that I've unlocked and reflashed it?
Are there other ways to do the data/factory reset? (Through Odin?)
Thanks a ton for any help!
TL;DR: Unlock code entered incorrectly in pocket, phone locked, unable to access wipe functionality and therefore not able to reflash stock rom -> ****ed.
If it's the same issue experienced by someone else on these forums, the solution given here was to keep typing wrong passwords.
oinkylicious said:
If it's the same issue experienced by someone else on these forums, the solution given here was to keep typing wrong passwords.
Click to expand...
Click to collapse
It seems to be related, but I now did 50 attempts (where one has to wait 30 sec between every 5 failed passwords), and nothing happens. Will try to repost in the thread you mentioned, and see if they can provide a better explanation.
Anyone else have any clue?
Got it to work!
Basically, the post oinkylicious linked to had the solution. The password/PIN they are referring to is the one that we are prompted to enter when trying to do a data/factory reset from stock recovery. After a number of tries it will say that if you type the password wrong once more it might delete contents on your SD card. What I did was remove the SD card, and continue to enter wrong passwords. After a while it will the show some text (can't remember what), and let you go through with the data/factory reset.
Just as the title states...
I have completed the process on the HTCDev site many many times. The process itself works fantastic. Each step responds exactly how they state it should. I submit the token code and get a Bin file. Using fastboot to flash the Bin file results in the phone prompting me to unlock the bootloader. I select yes using the volume up and then hit power. The phone powers off and reboots restoring everything to factory. So it would seem that everything works correctly. I get no error messages during the process. I get nothing but the results that I should be expecting...EXCEPT...
The bootloader remains locked.
I'm beyond frustrated at this point. I've followed every single set of instructions just thinking maybe there's a step missing in one of them. Yet they all perform the same. End result...Bootloader still locked. No idea what is going on. Called HTC Tech Support and they weren't any help at all. Basically they said to leave a comment on the HTCDev site.
Any ideas???
Have you tried flashing anything even though it still says locked? It is a longshot, but there is a chance it is unlocked but just still says locked.
rultin said:
Just as the title states...
I have completed the process on the HTCDev site many many times. The process itself works fantastic. Each step responds exactly how they state it should. I submit the token code and get a Bin file. Using fastboot to flash the Bin file results in the phone prompting me to unlock the bootloader. I select yes using the volume up and then hit power. The phone powers off and reboots restoring everything to factory. So it would seem that everything works correctly. I get no error messages during the process. I get nothing but the results that I should be expecting...EXCEPT...
The bootloader remains locked.
I'm beyond frustrated at this point. I've followed every single set of instructions just thinking maybe there's a step missing in one of them. Yet they all perform the same. End result...Bootloader still locked. No idea what is going on. Called HTC Tech Support and they weren't any help at all. Basically they said to leave a comment on the HTCDev site.
Any ideas???
Click to expand...
Click to collapse
Since it's getting wiped anyway, exchange the phone for a new one.
MrSmith317 said:
Since it's getting wiped anyway, exchange the phone for a new one.
Click to expand...
Click to collapse
I second that, I had a problem Unlocking my Rezound, I called HTC they said they dont replace phones and to call VZW. I called VZW told them that HTC told me to call for a replacement, they gave me a hard time. I told them as a developer, not being able to unlock my phone is a detrimental to my livelyhood. They sent me a refurb (standard) and I had no problems unlocking it. I posted my saga over in general you can see it here http://forum.xda-developers.com/showthread.php?t=1416472
I know this seems like a dumb question but I assure you there is some logic to it.
My dopey friend started to unlock his Prime, but his connection via USB came undone and he says that the unlocking "failed". He came to me asking if it worked or not. I'm no expert, but I am curious.
Here are the variables:
1. When I attempt to run Unlock Device, everything prompts you like it's never been done.
2. When booting with power and voldown, it quickly flashes something like "android userh bootloader version 1.20 us_eepad blah blah" then gives the option for cold boot or wipe data.
3. ROM manager doesn't have CWM installed and when selecting boot into recovery, it simply restarts the device.
The device seems to be rooted though.
Thoughts?
Contact Asus through e-mail or phone call, give them the serial number and ask if it's unlocked.
Or see if you can download the OTA update, if it bricks, then it's unlocked.
If it does not give you the fastboot option together with wipe data and cold boot it is not unlocked
There should be a file called Unlock_Time.txt on your tablets memory.(at least I think that's created when you unlock the device)
My T-Mobile HTC ONE M7 had very low battery life and eventually died before I could get to my charger. When I plugged it in and attempted to turn it on this screen appeared on my phone:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jun 21 2013,20:19:45:9912
After doing quite a bit of research it appears as if my phone is stuck in a "bootloader loop". I left the phone on the charger last night and I have tried rebooting from this menu and even a factory reset however all the phone does is power off and return to this screen. I have NOT tampered with the phone, have not attempted to unlock or root it, or any other type of modification. I work for T-Mobile and know well enough that doing so would void any warranty. Which is why I am troubled by the fact that it states *** TAMPERED *** (otherwise I would have just performed a simple warranty exchange, however due to the tampered tag I have feeling they would reject my claim)
Any assistance would be greatly appreciated! Has this happened to anyone else with a critically low battery?
ohbeeasy said:
My T-Mobile HTC ONE M7 had very low battery life and eventually died before I could get to my charger. When I plugged it in and attempted to turn it on this screen appeared on my phone:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jun 21 2013,20:19:45:9912
After doing quite a bit of research it appears as if my phone is stuck in a "bootloader loop". I left the phone on the charger last night and I have tried rebooting from this menu and even a factory reset however all the phone does is power off and return to this screen. I have NOT tampered with the phone, have not attempted to unlock or root it, or any other type of modification. I work for T-Mobile and know well enough that doing so would void any warranty. Which is why I am troubled by the fact that it states *** TAMPERED *** (otherwise I would have just performed a simple warranty exchange, however due to the tampered tag I have feeling they would reject my claim)
Any assistance would be greatly appreciated! Has this happened to anyone else with a critically low battery?
Click to expand...
Click to collapse
I just exchanged my first One for case issues, but it also happened to crash to 0% battery several times (due to Google services wakelocks). In no instance did it crash hard enough to ruin the entire phone.
So...I'm going to be cynical first:
TAMPERED usually comes up once you have flashed a custom partition (recovery, so on...), and the Security Warning *typically* occurs when you try to re-lock your HTCDev-unlocked phone while you still have your custom recovery installed (you have to reflash a stock recovery before attempting a re-lock). If you had done something in the past and relocked your bootloader to bring it back to 'stock' without restoring your recovery, you would see things like this. The solution would be to unlock the bootloader again, flash stock recovery, then relock.
But since you have never done anything like that:
It's *possible* that your phone shut down in a very awkward/damaging way and now doesn't recognize the signature of your never-modified OS--that would require that there was damage or corruption across the non-OS partitions. If that's the case, then you could try to reload an official RUU yourself (if you had the appropriate software to do so, which you would need to get...), or take it to a T-Mobile location and ask them to try to push a new stock image to your phone. As long as you are able to see menu options under those warnings that you can navigate with the volume buttons, then the stock ROM should be able to reload all those 'tampered' partitions. If that doesn't work, though, you'd have to take your chances with T-Mobile support.
tuxkamen said:
I just exchanged my first One for case issues, but it also happened to crash to 0% battery several times (due to Google services wakelocks). In no instance did it crash hard enough to ruin the entire phone.
So...I'm going to be cynical first:
TAMPERED usually comes up once you have flashed a custom partition (recovery, so on...), and the Security Warning *typically* occurs when you try to re-lock your HTCDev-unlocked phone while you still have your custom recovery installed (you have to reflash a stock recovery before attempting a re-lock). If you had done something in the past and relocked your bootloader to bring it back to 'stock' without restoring your recovery, you would see things like this. The solution would be to unlock the bootloader again, flash stock recovery, then relock.
But since you have never done anything like that:
It's *possible* that your phone shut down in a very awkward/damaging way and now doesn't recognize the signature of your never-modified OS--that would require that there was damage or corruption across the non-OS partitions. If that's the case, then you could try to reload an official RUU yourself (if you had the appropriate software to do so, which you would need to get...), or take it to a T-Mobile location and ask them to try to push a new stock image to your phone. As long as you are able to see menu options under those warnings that you can navigate with the volume buttons, then the stock ROM should be able to reload all those 'tampered' partitions. If that doesn't work, though, you'd have to take your chances with T-Mobile support.
Click to expand...
Click to collapse
Thanks for your response, I probably should have mentioned that this device is not new, it was a replacement device through Asurion as the result of the insurance claim. So it sounds like whoever may have had the phone previously may have done some "tampering". The phone eventually cut off and has refused to turn on entirely. I went to T-Mobile and had an assistant manager memo the account with the information I provided above. I'm familiar with the bootloading screen but have never seen it not respond like mine was doing. I'm going to read up on the forums and see if I can become a little more familiar with the process so I can learn how to fix something like this in the future. Thanks for your quick reply!
ohbeeasy said:
Thanks for your response, I probably should have mentioned that this device is not new, it was a replacement device through Asurion as the result of the insurance claim. So it sounds like whoever may have had the phone previously may have done some "tampering". The phone eventually cut off and has refused to turn on entirely. I went to T-Mobile and had an assistant manager memo the account with the information I provided above. I'm familiar with the bootloading screen but have never seen it not respond like mine was doing. I'm going to read up on the forums and see if I can become a little more familiar with the process so I can learn how to fix something like this in the future. Thanks for your quick reply!
Click to expand...
Click to collapse
Try flashing the RUU. but since you are 1.44 can your revone and s-off first?
I would s-off before RUU.
Hoping someone can help because my phone is completely unusable. I was in work yesterday and decided to restart my phone because the battery was draining and I didn't have a USB-C cable. It got to the "enter PIN" screen, and the PIN I've always used was invalid. I'm pretty sure I never changed my PIN, but I've used 15 of 30 guesses trying any number that I might have changed it to, and none work. I usually unlock my phone with my finger print, but that isn't possible because this isn't the standard unlock screen, it's the screen before the phone even fully boots up. It's not connected to the internet yet so I can't reset it via Google and there's no "forgot PIN" option.
To further complicate things, the power button on my phone doesn't work (though the finger print sensor still does.) The phone was in my pocket and got moist from sweat on a hot day, and hasn't worked since. So I'm not even able to get into recovery mode. I can turn the phone on by holding volume-down and connecting then disconnecting the charger. I can also get into "download mode" to flash firmware by doing the same thing holding volume-up.
I have my camera photos backed up, but nothing in my downloads directory is saved, nor any pictures received in text messages. I'm sure there's plenty of other stuff that's not backed up too. I hadn't enabled encryption. Is there any way to transfer files off my phone? I'm assuming no, especially since even "adb" doesn't see the phone in either download mode or the PIN entry screen. USB debugging was enabled, but it seems like it's only connecting in "charge only" mode.
I'm not even sure how to get the phone working again, even if I have to wipe it. Should I try flashing a stock ROM (it's not rooted or un-bootlocked)? What happens when I enter the invalid PIN 30 times?
Thanks for any help.
Edit: If it helps, it's the AT&T model, H820
think you must reflash the Rom with fatory reset option. not the best, but you have a usable devive again. Bad you cant root the device and delete just the two *.key files
gesendet von meinem LG G5 H850 V10E
What happens after 30th attempt to unlock Secure Boot?
I have forgotten the unlock pattern for my G5, which has been sitting in a drawer for the last couple of months.
What happens when I fail to correctly enter the unlock pattern for the 30th time? Will it clear the data and reset itself, if so, no biggy, or will it turn itself into a brick, which would be a biggy?
Regards,
SpudULike said:
I have forgotten the unlock pattern for my G5, which has been sitting in a drawer for the last couple of months.
What happens when I fail to correctly enter the unlock pattern for the 30th time? Will it clear the data and reset itself, if so, no biggy, or will it turn itself into a brick, which would be a biggy?
Regards,
Click to expand...
Click to collapse
It clears all data and factory resets itself. The only other thing is that you need the password for the Google account it was associated with, in order to use it after it resets. I think it's to prevent phone theft. I remember hearing you shouldn't try to change your Google password within ~3 days of resetting the device either, because it might not work.
Note that if it's the actual screen lock pattern you forgot instead of the startup/boot PIN, you can probably just reset it through Google's Android Device Manager website.
LG G5 SE H840 stuck on secure startup
Hi everyone.
I've tried to flash TWRP on my phone using fastboot and it seems to have worked, but when I reboot, my phone is asking for a secure startup code.
I don't have it because I don't remember setting one up... Each reboot uses 2 of the 30 try allowed and now I'm at 12 left.
I tried default_password, and some other things... not working.
I tried fastboot -w to do a factory reset, but it doesn't want to write "userdata" : "cannot flash this partition in unlocked state"...
Code:
Created filesystem with 11/32000 inodes and 4110/128000 blocks
erasing 'userdata'...
OKAY [ 0.609s]
sending 'userdata' (138917 KB)...
OKAY [ 4.361s]
writing 'userdata'...
FAILED (remote: cannot flash this partition in unlocked state)
finished. total time: 4.989s
For what it's worth : I'm french and the secure startup is in french... Is it because the initial stock rom that I used is still behind whit my settings ? Factory reset should have brought me back to English at least ?
Any help please ?
New problem, new thread.
I remember that I set a secure startup pin in my Lenovo TB3- x70L . But when I typed the pin the tab displayed incorrect pin . So I restarted it a black display appeared to enter the pin.
I tried many times typing the pin what I set . It shows all are incorrect pin . And after many attempts it says "your tab will be wiped after 7 attempts with incorrect pin".
My debugging is off ,OEM is off.(Initially).
But I some how activated debugging.
Pls help me guys if you can.
Same issue
Have you guys ever solved this issue? I am facing the same with my LG G5...
Hey i have a lg aristo 2 and forgot my lockscreen passcode i have tried multiple tips off the web and me and my fiance are both logged into her google account what can i do to get into my phone....
Lg vs087 g5
Had the same problem....Secure boot enter pin. After exceeding the 10 attempts it factory reset itself and went into setup.
I have the exact issue also on my LG G5 H830. it recognizes my fingerprint but the pin ive been using for years says its wrong pattern. I can only unlock my device with my fingerprint. f**king weird.