I'm not sure exactly where this goes, but I think it belongs here and I haven't been able to find any other threads about this issue.
It's going to seem like a WinMo issue, but I'm pretty sure it's Android related.
I have a ATT Tilt2 with a stock ROM (I think with Sense 2.5) that I recently (last week) installed FRX06 on top of an older BLAZN install that I hadn't tried in months.
Today, I shut down Android (properly) and turned the phone on to return to WinMo. On the 4 digit numeric PIN screen (I Activesync with Exchange at work and this is part of the security requirement; it's not the SIM or GSM PIN), I enter my pin and ... I get an error message that I've entered the wrong PIN and I just used 1 of 8 turns. I tried carefully to enter the PIN to make sure I didn't fat finger the button - strike 2. So, I open the keyboard to try using that, and still no dice. Now I'm worried about getting my device wiped and starting from scratch.
The reason I think this is Android related is that this has happened to me one other time. This problem was the main reason I stopped using BLAZN about 6 months ago. In the almost 2 years that I've had this phone, this hasn't happened when rebooting from WinMo back into WinMo.
Any suggestions or ideas about what's going on? I don't even want to touch my phone without having a plan of attack. My contacts are backed up (first thing I did before I installed FRX06), but would rather not have to re-install stuff if I don't have to.
By the way, until this little incident, Android had been running great - it's been a big improvement over where it was 6 months ago.
Thanks in advance for any help.
-David
LeStone08 said:
I have a ATT Tilt2 with a stock ROM (I think with Sense 2.5) that I recently (last week) installed FRX06 on top of an older BLAZN install that I hadn't tried in months.
Thanks in advance for any help.
-David
Click to expand...
Click to collapse
I think you need to rename/delete your data.img.
But first you need a real fresh start so don't install FRX06 on top of BLAZN. Delete the old and download the FRX06 package from the thread
Thanks for the reply. Those are some good suggestions in general, but doesn't address my immediate need: Is there any way to get past the PIN check now (maybe the PIN was reset to some default)? Or is there an explanation for what is going on? AS it is, there's nothing I can do with the phone if I don't get the PIN correct (can't reboot into Android).
Also, in order to get FRX06 to work, I did delete the data.img file, so that is fresh. Also, the first time a few months ago, I ran into this problem was on my original (clean) install of BLAZN. Until this problem happened, Android had been working great in most other respects.
You're not supposed to use PIN auth in WinMo if you want to use Android.
Although, that type of PIN should work, I wouldn't use it. So if your work requires it, I'd say don't use Android.
I wish I could help more, my company uses GroupWise and only allows BB's to connect...
arrrghhh said:
You're not supposed to use PIN auth in WinMo if you want to use Android.
Although, that type of PIN should work, I wouldn't use it. So if your work requires it, I'd say don't use Android.
I wish I could help more, my company uses GroupWise and only allows BB's to connect...
Click to expand...
Click to collapse
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
rpierce99 said:
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
Click to expand...
Click to collapse
Normally, I wouldn't think Android would impact my winMo setup. But this has only happened to my twice and both times occured after shutting down Android and rebooting the phone.
No one else has access to my phone - so I can't blame anyone else.
I did install the trial version of Touchdown in my Android installation, but I don't think that's part of the problem (the last time it happened, I used the standard Exchange functionality of Android).
Could the policies enforced by Exchange cause my WinMo PIN to reset when I registered the new Android connectivity? When I set up Touchdown, I used the same PIN that I set for WinMO.
Thanks for the comments. Looking for any suggestions to get the phone up without getting it wiped (any default PINS that I can try?).
LeStone08 said:
Could the policies enforced by Exchange cause my WinMo PIN to reset when I registered the new Android connectivity? When I set up Touchdown, I used the same PIN that I set for WinMO.
Thanks for the comments. Looking for any suggestions to get the phone up without getting it wiped (any default PINS that I can try?).
Click to expand...
Click to collapse
These are questions for your IT dept I would think...
rpierce99 said:
I don't know why PIN auth in WinMo would have anything to do with Android, and I know I never had any problems with my WinMo pin while running android. While I can't say for certain that Android wouldn't do anything to your WinMo PIN, I would put the likelyhood at .0000001%. It simply doesn't touch the built in storage. Android is run straight from the SD card, and WinMo doesn't store your PIN on the SD card, so the chance of any funny business between the two is very low. Someone who knows the ins and outs of the NAND better than I would probably tell you it is impossible for Android to write to NAND, seeing as how there was so much work that went into the NAND testing.
Long story short, it wasn't Android. Maybe someone is playing a joke on you.
Click to expand...
Click to collapse
I would agree with rpierce99. I use MS Exchange (2007) on both wm & frx06 with password policy enforced and never experienced this issue. I chose to use a 6 digit numeric pin on both OS.
I remember having this issue. Pissed me off beyond belief. Same thing happened, booted out of android, when I tried unlocking, it kept saying the password was incorrect. For some reason I can't remember what I did to fix it... I think I just did a forced hard reset (click reset button, hold send key + end key + power key all at once). I know it's not what you want to hear but hard reset might be the only/quickest fix.
If it's asking for a SIM PIN, then this isn't related to Android, and it's not a Win-Mo issue either. It's the PIN for your SIM card as it's always been - or someone's changed it on you (they need to know your old one first)
3? Wrong guesses on a PIN and you get a PUK lock. (Pin Unblock Key)
The PUK is provided to you from your mobile provider. 10 wrong goes of this and you brick your SIM permanently, and you'll need a new one.
PIN and PUK aren't supported in Android to my knowledge, and Win-Mo will only allow you to change the PIN if you knew the old one as I said. I don't know of any "hacks" that can up-and-change it.
Lastly, there's good old device "lock". I had this corrupt on my TP2 end of last year causing me a huge headache and a hard reset. I was NOT using Android at this time.
Hope that helps in some way.
Raa_1 said:
If it's asking for a SIM PIN, then this isn't related to Android, and it's not a Win-Mo issue either. It's the PIN for your SIM card as it's always been - or someone's changed it on you (they need to know your old one first)
3? Wrong guesses on a PIN and you get a PUK lock. (Pin Unblock Key)
The PUK is provided to you from your mobile provider. 10 wrong goes of this and you brick your SIM permanently, and you'll need a new one.
PIN and PUK aren't supported in Android to my knowledge, and Win-Mo will only allow you to change the PIN if you knew the old one as I said. I don't know of any "hacks" that can up-and-change it.
Lastly, there's good old device "lock". I had this corrupt on my TP2 end of last year causing me a huge headache and a hard reset. I was NOT using Android at this time.
Hope that helps in some way.
Click to expand...
Click to collapse
Nah, his first post specifies it wasn't a SIM or GSM lock. I believe he had the Winmo lock go crazy on him like me. You say you had it too but not with android... I think my battery was very low at the time, I have no idea if that has anything to do with it. Was your battery fairly low/close to dying?
Nah not at the time. But I ran a tweak program and set a setting that botched it - I think. I was never tempted to try again to find out though.
Also on a side note, just tested the latest updates today, "PIN incorrect" when trying to unlock in Android. Works in WinMo. Removing PIN on startup again until it's fixed. (bummer!)
slapshot30 said:
Nah, his first post specifies it wasn't a SIM or GSM lock. I believe he had the Winmo lock go crazy on him like me. You say you had it too but not with android... I think my battery was very low at the time, I have no idea if that has anything to do with it. Was your battery fairly low/close to dying?
Click to expand...
Click to collapse
You're right, it wasn't my SIM lock that was causing the problem. I don't remember if my battery was low or dying. I do know that the last thing I had running was the Youtube app that was having problems with buffering a video, then it started getting non-responsive, which was why I decided to shut down my phone and reboot.
I checked with our IT department and besides them trying not to support it because it's not an eye-phone, there were no known MS Exchange changes at our company that would have caused the problem. I did find out that the webmail client for Exchange now shows the clients that connected - I could see a listing for my WinMo install and a couple for my Android install (my original install from 6 months ago, and my current install - the different builds had different system names). There is a feature to request a recovery PIN there, but my HTC Sense simple PIN entry screen didn't have a recovery pin option that's needed - or I didn't see it in the last try I had to get my PIN correct. Maybe I'll play with that more if I start using WinMo again.
My phone did get wiped and so far, I haven't loaded anything back into WinMo - I've been running off my Android install (didn't reinstall - since my SD Card didn't get wiped) for the last 1.5 weeks.
I know it's not a large sample size, but the two times this has happened in the almost 2 year time period that I've had this phone occurred when booting out of Android. I'm glad to hear that I'm not the only one with this issue, but it would be nice to have the problem diagnosed.
I'm hoping that one of the brains doing all of this cool stuff will find the root cause and show us (at least me and Slapshot) how to avoid the problem.
Thanks. I'm still really happy about the state of the Rhodium projects.
Raa_1 said:
Nah not at the time. But I ran a tweak program and set a setting that botched it - I think. I was never tempted to try again to find out though.
Also on a side note, just tested the latest updates today, "PIN incorrect" when trying to unlock in Android. Works in WinMo. Removing PIN on startup again until it's fixed. (bummer!)
Click to expand...
Click to collapse
I've never set any type of PIN on my Android phones. What are you setting?
On any phone you can set it to "Request PIN on startup" and it will ask you for the SIM's PIN. (This is SIM dependant, I don't know if it works for CDMA).
Traditionally, it would boot up the phone fine, but won't activate the SIM until the PIN is entered, once that's entered and the SIM unlocks, it'll logon to the 3G network and work normally.
In XDAndroid, if I try to enter my PIN, it says it's incorrect (works fine in WinMo), but I did read somewhere that it wasn't supported, and it has to be left off. I don't like doing this, but no choice really!
Want to troubleshoot this issue too?
Raa_1 said:
On any phone you can set it to "Request PIN on startup" and it will ask you for the SIM's PIN. (This is SIM dependant, I don't know if it works for CDMA).
Traditionally, it would boot up the phone fine, but won't activate the SIM until the PIN is entered, once that's entered and the SIM unlocks, it'll logon to the 3G network and work normally.
In XDAndroid, if I try to enter my PIN, it says it's incorrect (works fine in WinMo), but I did read somewhere that it wasn't supported, and it has to be left off. I don't like doing this, but no choice really!
Want to troubleshoot this issue too?
Click to expand...
Click to collapse
I'll take your word on the SIM PIN business, as I've never actually set my SIM pin. I wouldn't do this in general, but also especially knowing that there's a conflict between SIM pins and the XDAndroid projects.
In WinMo (I believe there's a way to do this an Android also, but not quite sure), there are two ways that I know of to set up a startup PIN on your phone (at least on my Tilt2):
1) You can go into Settings, Security, Phone Lock: here you can set up your phone to lock itself after a set amount of time. You can use either a Simple PIN or a strong alpha-numeric PIN. Whenever your phone is idle for a time period exceeding the threshold you have set, the phone will lock itself so that you have to enter your PIN to access the phone again. Again, this is not the SIM pin.
2) Some of us work at companies that use this little email package called Exchange by a company called Microsoft . In order to protect employee's and (mostly) company data, some of these companies will leverage security features in Exchange to mandatorily set policies on any mobile devices that want to access the corporate email system. If you want access to the system, you have to accept whatever policies the company chooses to enforce. Some of these policies include: 1) Requiring a PIN (not a SIM pin) on your device; 2) requiring a max idle time before the phone locks itself; 3) requiring a phone reset (including data wipe) after a certain number of missed passwords; 4) allowing a phone wipe/clear on demand in case of theft; etc. My company requires all of these - there are more, but I'm not familiar with all of the options.
When I boot into Windows Mobile, Exchange sees my phone as one device and sets the policies accordingly (basically the email software has to be able to receive the policies and interpret them). When I boot into XDAndroid, Exchange sees my phone as a different device and sends the same set of polices. For my original problem, I set the PIN to be the same for both instances to make like easy for my tiny little brain.
I reiterate that this is not a SIM pin issue. I want to make it clear so we can keep this thread on topic in case anyone else has some insights into the problem. I don't want it to be derailed into a SIM PIN discussion since I'm sure there are lots of threads about that. (Now, I've probably polluted the index with that term and anyone looking for that will find this instead )
I would love to know if anyone gets any insights here.
Thanks for reading.
David
Yes I see what you mean now, and my issue is a different one (SIM not device PIN).
Since your work is issuing device policies, my thought would be it's a policy issue, and quite honestly, I wouldn't try and mess around with a device that's under I.T. direction.
Having said that, i'd likely say your problem is a corrupted WinMo password as Android has nothing whatsever to do with WinMo's side of things. And as mentioned before, it can happen with varying (mainly unknown - grr) reasons why.
So I've been trying to enter some of the 'Secret codes' from this page and have run into a weird problem. Basically some of the codes work (Not very many, IMEI being one that does) but the majority do nothing. The dialer simply sits there and when I then call the number, which I realise shouldn't be necessary, I get an error of Invalid MMI or connection problem.
There have been a significant amount of threads on XDA and the web but the most relevant ones seem to be from Galaxy Nexus owners. This thread for example highlights my problem exactly so it may be something to do with ICS/CM9 that I've overlooked. Another user in the fast dormancy thread also has the same issue so I don't think it's an isolated issue. I've also taken the following steps to try and resolve the issue (Worked for other devices/threads I came across):
- Turn off DTFM tones in Phone - Settings. I don't have this option.
- Turn off touch pad tones. Doesn't work.
- Turn off Speaker phone before entering codes. I don't have this option from within the phone app.
Has anyone else ran into this or know of any solution? Any help would be appreciated
Same here, using official Samsung ROM
It's because you use a custom ROM which does not have the Samsung dialer (or a service linked to this dialer).
In other terms, only Samsung dialer can "read" these secret codes.
Nojevah said:
It's because you use a custom ROM which does not have the Samsung dialer (or a service linked to this dialer).
In other terms, only Samsung dialer can "read" these secret codes.
Click to expand...
Click to collapse
Until I began using CM9 recently I only ever used stock based ROMs and couldn't get the codes working. A user above me seems to be the same. Some of the samsung specific codes did work from memory but a vast majority of them didn't. Seems to be hit or miss :/
Hollow.Droid said:
Until I began using CM9 recently I only ever used stock based ROMs and couldn't get the codes working. A user above me seems to be the same. Some of the samsung specific codes did work from memory but a vast majority of them didn't. Seems to be hit or miss :/
Click to expand...
Click to collapse
Thats what i found some work some don't even tried SGS tools etc .
I belive the posted codes came from SGS not SGS2 . Possible a difference ???
jje
I had misread your first post. Sorry. :/
Indeed, if you have one secret code working, it means you use Samsung dialer.
I guess Samsung did not implement all functionalities behind these codes. I don't think there's a workaround, but maybe I'm missing something.
Hollow.Droid said:
So I've been trying to enter some of the 'Secret codes' from this page and have run into a weird problem. Basically some of the codes work (Not very many, IMEI being one that does) but the majority do nothing. The dialer simply sits there and when I then call the number, which I realise shouldn't be necessary, I get an error of Invalid MMI or connection problem.
There have been a significant amount of threads on XDA and the web but the most relevant ones seem to be from Galaxy Nexus owners. This thread for example highlights my problem exactly so it may be something to do with ICS/CM9 that I've overlooked. Another user in the fast dormancy thread also has the same issue so I don't think it's an isolated issue. I've also taken the following steps to try and resolve the issue (Worked for other devices/threads I came across):
- Turn off DTFM tones in Phone - Settings. I don't have this option.
- Turn off touch pad tones. Doesn't work.
- Turn off Speaker phone before entering codes. I don't have this option from within the phone app.
Has anyone else ran into this or know of any solution? Any help would be appreciated
Click to expand...
Click to collapse
Just to let you know, I have had this issue since day one with CM9 (December). I have read and read and re-read and nothing is working. Afew codes are working, but no more. I have added * and/or # etc.. Nothing work. The best example is the Fast Dormancy one. But others do the same. Some people says its because we don't have stock ICS Dialer. Dont know what to do if you find, pls let me know.
Sorry if its been asked before, but is there any way to disable those extremely irritating confirmation prompts every time you turn on data? (hack, mod or otherwise)
I have to say SE really did not think that through. Do they really think every user really needs to be reminded absolutely every time they turn on data? The prompt warning me about turning it off makes me less likely to do so, cause turning it back in will result in the prompt again! (which is a problem when the phone is lagging for example, and you have to wait for the prompt to appear)
Any help would be appreciated
esist said:
Sorry if its been asked before, but is there any way to disable those extremely irritating confirmation prompts every time you turn on data? (hack, mod or otherwise)
I have to say SE really did not think that through. Do they really think every user really needs to be reminded absolutely every time they turn on data? The prompt warning me about turning it off makes me less likely to do so, cause turning it back in will result in the prompt again! (which is a problem when the phone is lagging for example, and you have to wait for the prompt to appear)
Any help would be appreciated
Click to expand...
Click to collapse
yes, next time please use SEARCH button or simply GOOGLE.
http://forum.xda-developers.com/showthread.php?t=1371117
I hope you are talking about the same as in the link, if not you have to search anyway
I did search several times. Didn't find any results.
I was unaware the X10 (in fairness it is a lot older) worked the same way so wouldn't have considered results for it.
Thanks anyway
if i were in your place...i may have done the same thing bro...how can we think that the answer of our query is in the forum of some other phone model.
unisol107 said:
how can we think that the answer of our query is in the forum of some other phone model.
Click to expand...
Click to collapse
well android is android, some stuff(read: most of them, which aren't related to hardware) are same across different phone models. have that in mind next time
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
m4ckys said:
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
Click to expand...
Click to collapse
please read how to get answer quickly in my signature
and provide logcat just after the error occurs
this will help
m4ckys said:
Hi,
I have posted this in the Questions thread but had no answer so I am trying here to find a hero to help me!!!!
I have got an S5380i as a work's phone and when I have my Bluetooth headset connected to it, when you answer incoming calls the phone resets after exactly 16 seconds into the call. Outgoing calls are fine, but this happens about 80% of the time.
I have searched the internet for info about this and cannot find anything.
I have tried using the Jellyblast Custom Rom, which actually fixed the problem, but I couldn't use it as my works software developed problems with me not being able to read the text as the letters were too similar in colour to the background.
I AM new to this and have bricked this phone about 50 times trying to fix the fault (and have learnt how to unbrick it!), but would REALLY like some input on how I might fix the issue.
I have tried about seven different Bluetooth headsets, including genuine Samsung ones, and the results have been the same.
Is that enough info for you?
Click to expand...
Click to collapse
First of all, JellyBlast is a banned rom here. So lets not have anymore discussion on that. As for the headset problem, you can use the SoundAbout app from Google Play. Do post the result. Hope I Helped
Thanks for the replies guys. I will have a go at the catlog later when I get home and post the results.
The problem doesn't happen every time so hear with me while I try to get it to do it so I can post the log.
Sorry for mentioning 'that' rom, I was just using that as a point of reference as it was the only rom I have tried.
The headset issue isn't that the headphones don't work though, it is that using the Bluetooth headset causes the phone to crash when answering a call (not making one though), and I thought that using the sounds out app was to fix the headphone socket issue?
Hey all. I originally posted this in the Mate 9 forum inadvertently but meant to post it here.
My wife and I both have the Mate 10 Pro. She lost hers at work several days ago. I located it using the Find My Device app. I also locked it so nothing in it was compromised just in case she didn't find it. She ends up finding the phone and can't unlock it. She brings it home for me to take a look at and I notice that I can't even input the whole password before it shows up as invalid. Apparently the input limit is 16 characters and the password I used when locking it remotely was 17 characters. I offered to factory reset it for her but she said no because she has a bunch of pictures on there she doesn't want to lose. Basically, her cloud photo storage is full and the last month and a half of pictures haven't been backed up. Is there anything I can do to at least retrieve her photos?
Has it ever been connected to a PC and ADB permission granted? If so connect to same pc and pull the content you want to back up. Otherwise it might be a question for Google. Also factory reset may not work in it's locked state due to recent Android anti theft measures.
Sent from my HUAWEI ALP-L29 using XDA Labs
Thanks for the reply. The only time it's ever been connected to a PC was using HiSuite to back up the phone before a factory reset a few months ago. I just feel bad and was hoping to fix it. I did post up a question on the Google help forum and haven't received a response. I guess I'll just give it several more days and if I can't figure out a resolution, I'll just factory reset the phone and see if I can at least get her phone back to her. I don't think she cares for the battery life of my old HTC 10... Thanks again.
If the password is too long then make her request a password change bro it's common sense.
I appreciate the input. I will try again when I get home but I'm almost positive you can only set the password one time through the "Find My Device" app. Once it's set, there is no changing it.
SerArris said:
I appreciate the input. I will try again when I get home but I'm almost positive you can only set the password one time through the "Find My Device" app. Once it's set, there is no changing it.
Click to expand...
Click to collapse
I think It uses the same password as the google account that locked it. also try to log in on another phone or computer and try to see if you can unlock it, also the limit is 100Characters for google password So I don't think that's the problem.
https://webapps.stackexchange.com/q...ters-permitted-for-the-password-of-a-google-a
https://youtu.be/Kic-A51Wqgk?t=60
Coreinsp said:
I think It uses the same password as the google account that locked it. also try to log in on another phone or computer and try to see if you can unlock it, also the limit is 100Characters for google password So I don't think that's the problem.
https://webapps.stackexchange.com/q...ters-permitted-for-the-password-of-a-google-a
https://youtu.be/Kic-A51Wqgk?t=60
Click to expand...
Click to collapse
So, just for the sake of clarity, I'll explain in more detail. My wife never uses a screen lock or password on her phone. When I "secured" the device using the Find My Device app, I put in a password to lock it. That password is 17 characters long. When the phone boots up, it asks for a password. The problem is, the phone will not allow me to input more than 16 characters. I tried truncating the password and that doesn't work either. I've tried her google password and it's a no-go. I've tried connecting it using the HiSuite software but the software doesn't see the phone. I've asked on the google help forums and haven't received any response.
Currently, my wife is using an old phone and I'm trying to find a workaround. Using the Find My Device app right now and it doesn't see the phone, so there is no option to relock with a different password (don't think that is possible anyway).
I have tried to do the same thing on my phone now and it is asking for the unlock PIN, the same PIN what I use after restarting the phone.
So, I can not believe that your phone does not accept that PIN/password because the password can be up to 32 characters long.
domy_os said:
I have tried to do the same thing on my phone now and it is asking for the unlock PIN, the same PIN what I use after restarting the phone.
So, I can not believe that your phone does not accept that PIN/password because the password can be up to 32 characters long.
Click to expand...
Click to collapse
yea something seems fishy here OP must have stole it or found the phone and the real owner have it locked it, so there's "supposedly" his wife is the owner of the phone she is the one who locked it first so I don't see the problem with her unlocking it because to lock it it must be done from a computer or a different phone.
Coreinsp said:
yea something seems fishy here OP must have stole it or found the phone and the real owner have it locked it, so there's "supposedly" his wife is the owner of the phone she is the one who locked it first so I don't see the problem with her unlocking it because to lock it it must be done from a computer or a different phone.
Click to expand...
Click to collapse
Thanks for the accusation. You sound like a fun person to be around. I, me, myself, locked the phone through "Find My Device". I only did that because she did not have any type of screen lock/password/PIN on the phone. Once the phone was rebooted, "Find My Device" couldn't even locate the phone again. As far as the other comments about password length, all I can say is I locked the phone with a password (using my computer) that was 17 characters long and when typing said password into the phone, as soon as I hit the 16th character, the phone said invalid password. Apparently I'm not the only person that's had this issue...
https://support.google.com/android/thread/22937630?hl=en
https://www.reddit.com/r/AndroidQue...droid_device_manager_password_is_too_long_to/
To everyone else, I appreciate the help. I just ended up wiping it. My "wife" isn't too mad at me. Just lost a bunch of pictures of our kiddo.