Database Develop

[Q] Pattern lock -> Too many tries

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....

[Q] Trying to fix phone using adb or fastboot

My Verizon Wireless Droid 3 stopped booting normally on Tuesday evening. It has not been rooted or anything like that. When I boot it now, once the boot sequence has finished instead of displaying the home screen it stays stuck on the red animated boot screen for a little while and then goes completely blank. I cannot do anything with the phone - none of the buttons work. I can hear some audio notifications however so it seems to be booted completely, but locked to any user input. I get the same behavior when booting it in safe mode. If I call my cell phone from a landline, it receives the call, displays the incoming call on the screen, and I can accept or reject it using the normal screen swipe motions. When the call is answered, I can talk/hear as well as use the in-call dial pad. I cannot, however, use any of the 4 buttons at the bottom of the phone or access the notification bar at the top of the screen. As soon as the call ends, the screen becomes unusable/blank again.
Once booted in this state, after a couple of minutes it sort of resets, in that it sounds/displays the "Droid" message, followed by the red animated boot screen. However, if connected to my computer when this happens, the two external drives do not disappear, which seems to indicate that the phone is still at least semi-booted during this time? If left alone, that cycle repeats and repeats (every few minutes it sounds/displays "Droid" then the red animated boot screen).
When I connect a USB cable to my computer while the phone is up in this state, it displays two empty external drives.
Through research on this forum and others I have downloaded/installed adb and the Android SDK. I cannot get adb to recognize the phone, presumably because I'm quite sure USB Debugging was not enabled on my phone before it started acting up.
When booting via FastBoot and connecting via USB it recognizes a "Android ADB Interface" device in device manager, however adb itself still does not recognize the device.
Doing a factory reset is not an option at this point due to encrypted files/photos on the phone/sd card. I had to turn encryption on in order to use my corporate e-mail on the phone.
The boot menu gives me these options:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Boot AP
BP Tools
Can anyone give me some advice on gaining access to the phone via adb or anything else? I've seen mention of Early USB Enumeration on some other androids, but am not seeing this option on my phone anywhere.

Forgot to mention that I also tried wiping the phone's cache via the recovery menu, but to no avail.

jessman1128 said:
My Verizon Wireless Droid 3 stopped booting normally on Tuesday evening. It has not been rooted or anything like that. When I boot it now, once the boot sequence has finished instead of displaying the home screen it stays stuck on the red animated boot screen for a little while and then goes completely blank. I cannot do anything with the phone - none of the buttons work. I can hear some audio notifications however so it seems to be booted completely, but locked to any user input. I get the same behavior when booting it in safe mode. If I call my cell phone from a landline, it receives the call, displays the incoming call on the screen, and I can accept or reject it using the normal screen swipe motions. When the call is answered, I can talk/hear as well as use the in-call dial pad. I cannot, however, use any of the 4 buttons at the bottom of the phone or access the notification bar at the top of the screen. As soon as the call ends, the screen becomes unusable/blank again.
Once booted in this state, after a couple of minutes it sort of resets, in that it sounds/displays the "Droid" message, followed by the red animated boot screen. However, if connected to my computer when this happens, the two external drives do not disappear, which seems to indicate that the phone is still at least semi-booted during this time? If left alone, that cycle repeats and repeats (every few minutes it sounds/displays "Droid" then the red animated boot screen).
When I connect a USB cable to my computer while the phone is up in this state, it displays two empty external drives.
Through research on this forum and others I have downloaded/installed adb and the Android SDK. I cannot get adb to recognize the phone, presumably because I'm quite sure USB Debugging was not enabled on my phone before it started acting up.
When booting via FastBoot and connecting via USB it recognizes a "Android ADB Interface" device in device manager, however adb itself still does not recognize the device.
Doing a factory reset is not an option at this point due to encrypted files/photos on the phone/sd card. I had to turn encryption on in order to use my corporate e-mail on the phone.
The boot menu gives me these options:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Boot AP
BP Tools
Can anyone give me some advice on gaining access to the phone via adb or anything else? I've seen mention of Early USB Enumeration on some other androids, but am not seeing this option on my phone anywhere.
Click to expand...
Click to collapse
Since you said you can receive calls, during a call, place in speakerphone mode and hit the HOME button. It should background the call to the notification bar and unlock sliding down the notification bar and take you to the home screen. (using AT&T I can do this to stay in call and browse/do whatever on data while in a call).
Have someone (or you) call the phone, press home, then hit Menu > Settings > Applications > debugging and enable USB debugging. This should get you ADB, do NOT hang up during this just in case.

Skreelink said:
Since you said you can receive calls, during a call, place in speakerphone mode and hit the HOME button. It should background the call to the notification bar and unlock sliding down the notification bar and take you to the home screen. (using AT&T I can do this to stay in call and browse/do whatever on data while in a call).
Have someone (or you) call the phone, press home, then hit Menu > Settings > Applications > debugging and enable USB debugging. This should get you ADB, do NOT hang up during this just in case.
Click to expand...
Click to collapse
I can place the call in speaker mode, but the home button (plus the other 3) still do not work, nor does the notification bar (although I can see the notification bar). At some point it did delegate the call to the notification bar (although not immediately after placing it in speaker mode), but at that point the rest of the screen went black and only the notification bar was visible (but not accessible). I did receive a message this time, right before answering the call, that process Home Screen was stuck or something and it prompted me to either force close or wait. I told it to wait. And now it just initiated a partial reboot, even though I was still in-call.

Also, in case it's relevant, I am using LauncherPro as my home screen.

jessman1128 said:
Also, in case it's relevant, I am using LauncherPro as my home screen.
Click to expand...
Click to collapse
Sounds like something may have happened to LauncherPro, and since it's your default launcher, the home button isn't going back to regular motorola home. Try booting the phone and (hoping) if it has a data connection, on your PC go to https://play.google.com/apps login, it should display your devices, click on your Droid 3, find LauncherPro, and uninstall remotely. It should be the small trash-can next to where it says 'installed'
OR you can try installing another launcher, such as ADW, Go Launcher, etc. and remotely installing it, then hitting home, which SHOULD reprompt for default launcher/home.
Maybe do a combination of the two, just to insure you're not stuck without a launcher at all, though not rooting, MotorolaHome shouldn't have been affected.

Skreelink said:
Sounds like something may have happened to LauncherPro, and since it's your default launcher, the home button isn't going back to regular motorola home. Try booting the phone and (hoping) if it has a data connection, on your PC go to [] login, it should display your devices, click on your Droid 3, find LauncherPro, and uninstall remotely. It should be the small trash-can next to where it says 'installed'
OR you can try installing another launcher, such as ADW, Go Launcher, etc. and remotely installing it, then hitting home, which SHOULD reprompt for default launcher/home.
Maybe do a combination of the two, just to insure you're not stuck without a launcher at all, though not rooting, MotorolaHome shouldn't have been affected.
Click to expand...
Click to collapse
You are a lifesaver. You rock. You are awesome. I'd click Thanks on your post one thousand times if it would let me. I have my phone back!
I followed both suggestions - I loaded the Play store on my computer and installed ADW as well as removed Launcher Pro plus a few other apps. It took I think 3 boot cycles before it finished making all of those changes on my phone (because it would only stay up for 1-2 minutes each time), but once it was done I had my phone back.
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
In recent weeks I've been kicking around the idea of rooting my phone and installing a custom rom. Thinking this might be a good time to try it now that I have everything copied off of my phone now. I don't know much about custom roms though. Do you happen to know if any of the available ones for D3 will support corporate e-mail?

jessman1128 said:
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
Click to expand...
Click to collapse
Good news. But, do yourself a favor - try activating a service that automatically uploads all photos, such as Google+ or Dropbox or Sugrasync. That way if you ever get to a point where you need to factory reset you'll have copies of your photos somewhere else.

jessman1128 said:
You are a lifesaver. You rock. You are awesome. I'd click Thanks on your post one thousand times if it would let me. I have my phone back!
I followed both suggestions - I loaded the Play store on my computer and installed ADW as well as removed Launcher Pro plus a few other apps. It took I think 3 boot cycles before it finished making all of those changes on my phone (because it would only stay up for 1-2 minutes each time), but once it was done I had my phone back.
I could access my pics on my phone then, but not on my computer. Due to them being encrypted you have to connect in PC Mode for it to decrypt them properly when copying to the computer, but in PC Mode it wasn't registering the right drivers. Took me awhile to track down the proper ones online (I was looking at Verizon when it was actually Motorola drivers I needed), but I finally found them and installed them and just finished copying over all my pics to my computer - and verified they decrypted properly.
In recent weeks I've been kicking around the idea of rooting my phone and installing a custom rom. Thinking this might be a good time to try it now that I have everything copied off of my phone now. I don't know much about custom roms though. Do you happen to know if any of the available ones for D3 will support corporate e-mail?
Click to expand...
Click to collapse
Most likely any roms that are built on the D3 source will unless they stripped it. I use Maverick rom 4.0 myself, it is based on 906 with enhancements, debloat, themed, etc. There are still many bugs to work out on AOSP built roms (cyanogenmod, aokp, etc. Any ics/jb roms). I would suggest sticking with a stable gb rom if it is your business phone.

doogald said:
Good news. But, do yourself a favor - try activating a service that automatically uploads all photos, such as Google+ or Dropbox or Sugrasync. That way if you ever get to a point where you need to factory reset you'll have copies of your photos somewhere else.
Click to expand...
Click to collapse
That sounds like a good idea. I wonder, though, if those services would upload the encrypted or decrypted version of the photos. I'll have to test it and see.

Skreelink said:
Most likely any roms that are built on the D3 source will unless they stripped it. I use Maverick rom 4.0 myself, it is based on 906 with enhancements, debloat, themed, etc. There are still many bugs to work out on AOSP built roms (cyanogenmod, aokp, etc. Any ics/jb roms). I would suggest sticking with a stable gb rom if it is your business phone.
Click to expand...
Click to collapse
Hmm, ok. I'll have to give it some more thought then. It's my personal phone, but I do have my work e-mail setup on it and access it fairly regularly. I don't absolutely need to have my work e-mail on my phone, but it's certainly very helpful to have it setup there.
I've also been thinking about doing a factory reset, as the phone in general has gotten progressively slower as time goes on. Thinking the factory reset might help in that regard. I wonder if there's any way to remove some of the stock Verizon apps I never use when doing a factory reset. I'll have to look into that. I guess I should go search these forums again!

jessman1128 said:
That sounds like a good idea. I wonder, though, if those services would upload the encrypted or decrypted version of the photos. I'll have to test it and see.
Click to expand...
Click to collapse
I setup FolderSync to upload my photos to Google Drive and it is successfully uploading them in decrypted form. Thank you for the suggestion!

Recovering from the dead

So, I was clean flashing Titan Prime back into my XT1064 after testing CM12.
Everything went well, same apps, same configurations as always, no major changes.
I was about to reboot the phone when it did it by itself.
The boot screen (you know, the white one that burns your eyes) showed up, then it went away, and then oh surprise!, it came back again.
So the phone was in this bootloop within the boot screen.
I tried to enter to the Bootloader and the key presses (Power + Volume Down) did not work.
Every time I would try that, the phone screen would stay off for as long those keys were pressed down, and then, Bootloop.
After many tries I was about to let the phone stay in the bootloop until I find a solution here on XDA.
But I tried one more time, and lo and behold, it went into the Bootloader.
From there everything went as normal.
Now, the question is, could I have bad sectors?, could the Bootloader be corrupted?, could I have a ghost trapped?.
Thank you for answers and/or ideas.
And if any of you happens to be in my same situation, do not give up, let it be, try many times, and it finally will work (hopefully)

Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.

Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.

Tel864 said:
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Click to expand...
Click to collapse
You do everything right, the phone gets screwed, it gets fixed, and the problem is something no one else has had so you have no freaking idea of why or what it was.
It is not my power button, the only times I use it is when I turn the screen on, and it would not be the reason because it made a difference when it was pressed.
I will try some fastboot commands to scan sectors, but I need to remember how they worked. The last time I used them it was when I had a Galaxy Note 1.
Lars124 said:
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Click to expand...
Click to collapse
As noted on the first post, I did not do anything out of the ordinary. Same apps, same configuration as always.
The good thing is that I now can say I have every app that I need, with the configurations that I need, so I almost never need to change.
Let's hope it will not happen again.

Phone starts with moving halo and "wissen"... "Is it wiping my phone?"

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.

[Solved] :p Fastboot menu not working, no recovery, no factory, system still works

Hello, first time posting. I have an interesting Moto X, internal test device, confidential property n all that. Bought it on eBay. It's been working fine but I have a very strange problem. I have flashed many devices, many phones, none of this is new to me. I'm now reminded why I like access to the ENTIRE memory, and I get really frustrated with the consumer grade bs we are often forced to endure. That said, my phone works, system partition works, boots up, the main device is normal. So here's what happens- I enter fastboot, I select recovery, nothing. The phone shuts off. So I enter fastboot, select factory, nothing. Phone shuts off. So I enter fastboot, select BP tools... You get the idea. I can flash from Windows command line, all partitions read and write, but when I flash TWRP and try to enter recovery... Yep, you guessed it, nothing. When the phone is plugged in, it goes directly to the charging screen, confirming that the phone is turned off. I can fastboot boot twrp.img and it works, but it's not booting off the device directly, and I have no idea what happened. I installed lineage, installed xt1095 factory t mobile rom, it all worked fine, and then one day it didn't. Seems like it's just not entering the partitions since the device works fine otherwise. But I honestly have no idea on this one, and I can usually figure these things out. Please tell me it's not the phone, because it's a MOTOROLA CONFIDENTIAL PROPERTY NOT FOR SALE internal device, a cool find for a techie like me. HELP PLEASE!

oops
K since I've had views... lol. dumb mistake...thought something went wrong. VOLUME selects, POWER cuts the phone off. Like a pc, when in BIOS the power cuts instantly. Too used to having to hold the power button down on phones, instead of it being immediate. I basically never use TWRP now, I do all my flashing from windows. I only use recovery to flash a custom OS so it's been a LONG time since I've had to use the buttons to enter recovery. My mistake! Too much going on in my life I guess. I'll leave this up just in case it helps someone else. Thanks for your help! lol. phone works fine
Also, here's what mine looks like. I don't think they care now, since it's been a few years. But pretty cool find, there can't be many of these in the world.
https:// goo.gl/images/hDNepV