Related
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....
So my HTC Hero has bit it. It has had a bad touch digitizer for about a week now. Is there ANY way to remove my text messages off the phone, perhaps with ADB? My phone will turn on and I can look at the screen but cannot touch anything. As such, I cannot unlock it.
Does anyone have any suggestions?
rjhall said:
So my HTC Hero has bit it. It has had a bad touch digitizer for about a week now. Is there ANY way to remove my text messages off the phone, perhaps with ADB? My phone will turn on and I can look at the screen but cannot touch anything. As such, I cannot unlock it.
Does anyone have any suggestions?
Click to expand...
Click to collapse
If it's rooted, you could conceivably pull the database file from it if you knew where it was, someone here should know that and this should bump your post back to the top.
aiwetir said:
If it's rooted, you could conceivably pull the database file from it if you knew where it was, someone here should know that and this should bump your post back to the top.
Click to expand...
Click to collapse
It's not rooted, but with the screen off, I could always do so. I think USB debugging is on... Not actually sure.
rjhall said:
It's not rooted, but with the screen off, I could always do so. I think USB debugging is on... Not actually sure.
Click to expand...
Click to collapse
If USB debugging is enabled, you can get a root shell (soft root) with the rageagainstthecage exploit and do what you need to do.
jasonmaloney said:
If USB debugging is enabled, you can get a root shell (soft root) with the rageagainstthecage exploit and do what you need to do.
Click to expand...
Click to collapse
Alright, do you know where the text messages are saved?
rjhall said:
Alright, do you know where the text messages are saved?
Click to expand...
Click to collapse
Dialer storage. Don't remember the exact path offhand.
jasonmaloney said:
Dialer storage. Don't remember the exact path offhand.
Click to expand...
Click to collapse
Would it be possible for me to get to it in ADB without rooting the phone?
the path is /data/data/com.android.providers.telephony/databases/mmssms.db
I'm not sure if root access is required, but good luck
Sent from my HERO200 using XDA Premium App
The Fer-Shiz-Nizzle said:
the path is /data/data/com.android.providers.telephony/databases/mmssms.db
I'm not sure if root access is required, but good luck
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Sorry, my experience with ADB is limited. What are the commands I would need, or where would I find a list of commands/functions? I tried the official Android Developer pages and found nothing helpful.
EDIT: Sorry, just got off third shift a couple hours ago and my brain doesn't want to work. I managed to figure out the commands but...
!!!A new challenger appears!!!
I don't have USB debugging enabled. My touchscreen doesn't work. I am in quite a pickle, I believe. I can't get the PC to recognize the phone without USB debugging on. Is there a way to turn it on without a screen?!
rjhall said:
Sorry, my experience with ADB is limited. What are the commands I would need, or where would I find a list of commands/functions? I tried the official Android Developer pages and found nothing helpful.
EDIT: Sorry, just got off third shift a couple hours ago and my brain doesn't want to work. I managed to figure out the commands but...
!!!A new challenger appears!!!
I don't have USB debugging enabled. My touchscreen doesn't work. I am in quite a pickle, I believe. I can't get the PC to recognize the phone without USB debugging on. Is there a way to turn it on without a screen?!
Click to expand...
Click to collapse
Wait... you said just the digitizer is broken? As in, the screen is intact but you just can't make any touch selections?
Are you on the stock (HTC Sense) firmware? If so, you can unlock the phone by pressing MENU on the lockscreen. From there, press MENU again, and use the trackball to navigate to Settings. Turn on USB debugging and root the phone. Install a custom recovery image, then reboot into recovery and do a nandroid backup. Then you'll be able to keep everything, not just your text messages.
jasonmaloney said:
Wait... you said just the digitizer is broken? As in, the screen is intact but you just can't make any touch selections?
Are you on the stock (HTC Sense) firmware? If so, you can unlock the phone by pressing MENU on the lockscreen. From there, press MENU again, and use the trackball to navigate to Settings. Turn on USB debugging and root the phone. Install a custom recovery image, then reboot into recovery and do a nandroid backup. Then you'll be able to keep everything, not just your text messages.
Click to expand...
Click to collapse
It's hard to explain the problem I'm having. The screen doesn't turn on or respond to touch inputs. If I squeeze the phone's sides hard enough, I can get the screen to come on. Soon as I let up, it goes dark. Keys still light up, though. If I do anything with the keys, it doesn't show up on the screen. I have no idea how to get past this.
I am on stock HTC firmware now. I completely reflashed the entire phone with the 2.1 utility. That is, before it randomly stopped working.
After USB debugging is enabled, I can just pull the entire system directory, no? No need for nandroid or anything?
cracked screen
Hey guys My screen is being repaired for the next couple days and I reallly need to check my text messages....Can I get more clearification on what you guys are tallking about because im lost but Im up for anything as long as I can see my texts,
I don't know if it's possible to do this, but it's worth a try. Have you heard of "Air Droid"? It allows you to interface with your phone via a WiFi connection. If you can download an apk file of Air Droid, then flash it to your phone, you might be able to run it. Although your screen digitizer isn't working, your trackball can still select screen items. If it works, you can do a connect to WiFi, see the code, then use the browser interface. I think through that you can access data on the phone, including text messages.
Also, there are some apps that perform SMS to email. You could theoretically have your text messages sent to your email account.
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!
Need someone with tons of knowledge here to help me out
I'm currently dealing with a Nexus 6, unrooted, stock.
The phone was dropped and the screen was destroyed. During the drop something internally must have been damaged as the phone starts the At&t music up and resets immediately and will keep looping until the power dies or I put it into the fastboot screen to shut it up, in which the phone stays on that screen. (or at least theres where im assuming its going)
The thing is, my computer recognizes the phone as an android device and shows the android device bootloader on my device manager on my cpu. Every time I try to get into recovery (or at least how I recall doing it without a screen to assist) the phone just restarts to the at&t music once again...
Is there any hope here for retrieving my data on this thing? I figured I could do something with adb although im not too savvy with it. Just assuming since the computer does recognize the device in some way, it is possible hopefully.
Btw I dont think debugging is on atm.
Any help would be super appreciated. Even willing to donate to anyone that may be able to assist me in this.
If and when Mobiletechvideos gets back up and running, they can more than likely save the entire device and if not at least get your data. But unfortunately because of the high demand for their services, they have gone into a temporary work hold until all current orders are complete. Either way, I would try to get ahold of them and see if they can assist or can point you in the right direction.
If it is unrooted with stock recovery and not booting up to android, there will be no easy way to get your data off.
It is possible, though very unreliable and extremely difficult to unlock the bootloader, flash a custom recovery, create an image of the data partition and scan that on a computer with data recovery software, but that really isn't worth doing.
hi ... how r u .... i have this problem too .... broken screen ... screen totally black ..... stock rom no root no recovery ...... debuging not enabled
http://forum.xda-developers.com/showthread.php?t=2786395&nocache=1
this guy said in his thread i can access the phone via computer but i need to enable debugging which i donno how to do with screen totally black
any suggestions is really appreciated
Hi,
I dropped my phone on the corner and the LCD broke and leaked through the screen. As a result the phone works, but the screen is dead.
I was able to check ADB USB in dev tools prior to the screen leaking through.
Is there any computer way to access and copy over the sms to another droid turbo, or does it make more sense to just replace the screen? The phone is currently turned off, has a pattern lock screen (since digitizer works, i can technically unlock the phone - i think )
Thanks,
Chris
you should be able to make a backup of the entire phone using ADB, But I don't know the exact steps to do it. Ive seen it done on nexus devices
use this
https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en
I used it to migrate all my messages from my old phone to the new one and it worked good
it was the pro version though
£ngland said:
use this
https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en
I used it to migrate all my messages from my old phone to the new one and it worked good
it was the pro version though
Click to expand...
Click to collapse
That may be difficult to use with a dead screen.
As for using adb, there's an issue. Although you enabled adb, a confirmation screen will still pop up on your phone the first time you use it. So if you've never used it before, you'll still need to accept that confirmation screen, which is a problem. I'm pretty sure that sms messages are stored in /data/data/com.android.providers.telephony/databases/mmssms.db and /data/data/com.android.providers.telephony/databases/mmssms.db-journal. I'm running RR, so I'm not sure if this is the correct location on the stock rom, but I think it's pretty standardized. If you can get adb working, I think the correct commands would be the following:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db <path to where you want it to show up on your PC>
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db-journal <path to where you want it to show up on your PC>
There's also a chance that you might need to be rooted to do this, but I think you should be okay. Good luck.
my thought is running it on 2 devices at same time sa to know where to click
Chris