Related
Hi,
Every now and then i'll wake up in the morning with my Tytn II II prompting me to enter a password, i've tried entering everything and checked all security features and made sure the "prompt for password when not used" has not been selected but nothing works, my only choice is to reset the device.
My main problem is the alarm clock does not work when it enters this mode which means I have to set another alarm clock just incase the phone enters the "enter password" mode over night.
I've hard reset the device but still this doesn't help.
Any suggestions?
I also have this crazy problem. Every now and again every 1-2 days I'll switch on my phone and be prompted for a password. I've never set any and the only answer is to soft reset and then all is fine until it happens again. The only other notable thing is that after about 5 failed guesses is tells me to input a1b2c3. Has anyone any idea what's going on - it's driving me nuts!!!
(ps I've tried zenyee but still no joy)
Wow, that would be annoying. Sorry, no help here as I use a password after one of my former devices "mistepeared"
Along these lines, I get prompted for my password everytime I connect to my Vista machine at home. I have yet to find a way to turn this off either. good thing it isn't my work machine as it would drive me crazy. At least le me enter the password on the main computer's keyboard instead of forcing me to open up my phone and type it in...
Shafty said:
I also have this crazy problem. Every now and again every 1-2 days I'll switch on my phone and be prompted for a password. I've never set any and the only answer is to soft reset and then all is fine until it happens again. The only other notable thing is that after about 5 failed guesses is tells me to input a1b2c3. Has anyone any idea what's going on - it's driving me nuts!!!
(ps I've tried zenyee but still no joy)
Click to expand...
Click to collapse
That is well weird.. Someone gets the same thing with an HP iPaq here: http://forums11.itrc.hp.com/service...47626+1201639304018+28353475&threadId=1190832
Unfortunatly theres no solution offered there either..
edit: I just had a play round after reading something and I think its something to do with the encryption for the SD card.. are either of you using it? If not are you synced to a work exchange server? Remote Device Wipe uses this code as well by the looks of it.. Have a read of this: http://blogs.msdn.com/windowsmobile...ows-mobile-6-storage-card-encryption-faq.aspx
The comments are where it mentions that code but the whole thing is worth a read.. theres also a document linked that tells you about device wipe if you havent heard of it.. I suspect this is related to your problem (in fact im sure it is)
The other day my screen stopped responding to my touch completely (only about 2 months old). The phone would randomly put itself into airplane mode and when I turned that off I was still able to send and receive text messages. I was unable to view my contacts folder or make calls though because android.phone or various other processes would crash when I tried. So I did a hard reset on my phone to see if that would fix my screen problem and now I cannot even send or receive text because I am stuck at the startup for the device and am unable to complete the startup because I cannot touch the screen. The red light of death comes up briefly when the phone is plugged in but goes away very quickly even with the battery in. The phone boots normally although it seems to take a little bit longer than usual. Does anyone have any idea on what is going wrong and how I can fix my screen?
Thanks!
this sounds like a hardware issue. if your phone is covered by the warranty then just call your provider and they should send you a new one.
is your phone rooted?
My G1 is stuck like this too, although mine was waterlogged so it's no longer under warranty @[email protected]
no it's not rooted
You can try to reflash the stock rom to see if that will help or you can root it and load a custom rom and see if that will make any difference. You can always use your trackball to navigate. If all that doesn't work then like david said its a hardware problem and is covered under warranty.
I can't scroll to navigate because the initial setup after a hard reset requires touch. Where do I find the info on re-flashing the stock rom?
Just find the official t mobile rom and flash like you would any rom. Put the update.zip on root of sd card then power on phone with home + power then in your case I would wipe (alt + w) then update (alt + s). I would try to find you a link but I'm bout to be leaving work. A google search will come up with it or someone else might chime in and give you a link.
http://android-dls.com/wiki/index.php?title=OTA_Updates
Try this.
i'm going to need the rogers stock rom ,not the t-mobile one I can't seem to find it anywhere. also will reflashing the stock rom void the warranty in any way. i assume it won't since there would be no way for them to tell but just double checking.
KYLEFALL said:
i'm going to need the rogers stock rom ,not the t-mobile one I can't seem to find it anywhere. also will reflashing the stock rom void the warranty in any way. i assume it won't since there would be no way for them to tell but just double checking.
Click to expand...
Click to collapse
nope youre basically just re applying the ota update
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Do a hard reset / wipe. That's my suggestion.
Try booting into recovery (Home Button, Vol Up + Power), and resetting your cache and wiping it. Then try logging in with your Google account. If all else fails, try changing your Google password on the PC then logging in on the phone. And then if it still fails, looks like you need to flash the phone again. Next time, don't enter the thing wrong! Stop rushing haha .
I wasn't rushing, I was playing with the lock. It takes about 30 times before it's permanently requiring the username/password. But really...you can't blame me for not expecting this. :/
I'm currently trying to flash a new ROM but I've run into another problem - I can't get it to boot into downloader/recovery. It's not the lack of the 3 button combo - I've managed to reach Recovery and Downloader ONCE each in the past, but never again since.
And now with all my efforts to boot into recovery/downloader, it now cannot boot into normal usability mode (or in my case, locked mode). Instead, the Galaxy S logo loops endlessly.
Sigh.
Have you read the thread for the fix for Galaxy S variants that are lacking the 3 Button Combos? It's in Android Development. Maybe try that? Or, can you still connect the phone and connect with Kies?
I can't turn on the phone anymore, meaning no changing to USB debugging etc. And I'm having problem accessing recovery/download, even though I definitely HAVE done each of them once before and therefore do not have the 3 button problem.
Without turning on my phone, Kies can't detect it
So what happens when you power on?
Now, it shows the first Galaxy S splash screen, then shows the boot logo, then nothing. The boot logo continues to glow endlessly.
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
okpc said:
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah it's continuously shining. Haven't left it for up to five minutes though... And even then it probably won't help since I'm still locked out of the phone, and unable to access download/recovery mode to reflash it.
After waiting for a long time, the logo disappears, screen goes black. Menu and back buttons light up. Nothing else.
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
PaulForde said:
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
Click to expand...
Click to collapse
Good advice considering he said his 3 button combo stopped working =))
All I did when I got that black screen was adb reboot recovery and wiped and phone bootedup fine. But only if you have debuging enable and and sumsung drivers. Hopes this help.
Sent from my SGH-T959 using XDA App
Can't enable USB debugging when phone can't be turned on at all.
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
danamoult said:
Can't enable USB debugging when phone can't be turned on at all.
Click to expand...
Click to collapse
you need to be able to enter recovery mode for you to solve this problem
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
dear friend dont worry or panic... i'll tell you a trick , go to the samsung customer care and tell them that your phone gets heated up very often and today it just refuses to boot up normally...
since your device cannot get into recovery mode or download mode the company will never know that you had played with the system files in the device or not... (rooted )..
since the samsung people will also try to get your device in recovery mode.. but when it will not go to the recovery mode you will get a mother board replacement under warranty.....
this heating up of the device is a common problem in the galaxy here in india.. so use this excuse and i know it works 100% ... (just dont tell them that you had rooted and lagfixed your device )
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
OzzYGuY said:
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
Click to expand...
Click to collapse
distortedloop said:
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
Click to expand...
Click to collapse
chill my dear friend.... it cant be true.... its just his 1st post.. and samsung cannot be so dumb to leave a password protected keypad that can be cracked so easily.. even i tried the back key on a call with a password lock.. i cannot get passed the lock screen....
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
TNSM said:
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
Click to expand...
Click to collapse
You may try to pull off the battery for few mins, then with someone's help hold the 3 buttons for download mode and then plug in the battery...
If you can't turn it in download mode there's no way to fix it, except jtag maybe.
Phone starts with moving halo and "wissen"... "Is it wiping my phone?"
Just now I took my Nexus 6 out of my pocket because it was very warm.
The screen was all black with in the middle a big Halo moving with the disturbing message "wissen" beneath it.
"wissen" is Dutch for wiping, deleting or removing...
Turning the phone off is possible by holding down the power button for 6 seconds, but then it turns on again after 3 seconds showing that same screen again.
After some fiddling I was able to find a method to turn it off.
I can start the phone by holding down the power button and the volume button (down) which will start the recovery program.
There I can turn it off.
Although I have unlocked the phone and ran modded firmwares I switched to standard factory Nexus 2 years ago and haven't had a rooted phone for all that time.
Recently I installed the 7.1 OTA updated.
I'm afraid this is something like a remote wipe.
It also doesn't ask me to give my PIN which is normal for it to do.
What is happening?
Some more info: Yesterday I bought the "AIO All-in-one Toolbox " after using the free one for 3 weeks. Could that be involved?
It may be formatting and encrypting your data partition.
Yes, but why?
It just went into my pocket this morning....
I came one step further.
As I was still able to get it into fastboot loader I exited with "volume up"
Then it went into an almost normal boot. This didn't require the pin it normally needed.
The device went into a full factory reset.
I thought I would be up and running fast, but after entering my new gmail account/password I got the message that I needed to wait another 24 hours because I did a password reset.
I did this password reset of my Google account out of safety. Now I'm being punished for this....
Luckily I have a spare Motorola G3 with its own SIM, so I can at least use my phone.
I can't even use my Nexus as a phone nor can I go to settings. Maybe if use another Google-account.
Did some more research...
The last Exchange sync was while cycling to work.
Didn't use the phone then nor later.
Because my Google-account is locked I can't do anything with my Phone (not even phone), so I decided to flash an alternate rom on it.
I flashed lineagos and also rooted the device again.
Although I did root my Nexus 6 in the beginning this is the first custom ROM I have on it. I still need to install gapps.
Now I can start using my Titaniumbackup again that I bought several years ago.
I still have no idea how it could have gone into wiping. I put the phone in my pocket while it was screenlocked. The device needs a pincode to unlock.....
I am still unable to use Google Apps. I can run the app, but it doesn't let me install apps.
On the stock rom I was just stuck (stuck rom, haha)..... at the installation screen unable to even make a phone call....
Does someone have any idea???
frater said:
...
Does someone have any idea???
Click to expand...
Click to collapse
My idea is that you have the N6 unprotected in your pocket. Moving or cycling caused activation of a factory reset.