Related
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!
OK so i noticed over the course of about 6 days my phones screen would glitch, when i say glitch i mean crazy colors and sometimes just go dark. a reboot would sometimes fix it other times it would take a few reboots. Now the screen doesnt come on at all. I have tried everything. Removing the built in battery for some time, charging, connecting to PC, wiggling the LCD etc etc.
I have about 4 years of pictures and videos on this phone with unfortunately no backups anywhere!!!!
I have got to get them off this phone one way or another.
Is there anyway i can work around a dead screen to copy files from the phones internal memory.
I have ADB, Fastboot, CentOS, Kubuntu, Kali, Winders 7,XP, and 8 to work with here so whatever it might take im down to try anything if anyone has any good ideas. Heck ill even take bad ideas at this point!!! ANYTHING would be better than what i got now.
(i should give a few details. when the phone boots up i hear the "DROID" boot animation sound the soft keys used to light up, the keyboard backlight comes on after sliding the screen out. All with no luck!!!
Please let me know if there is anything i can try here!!
Thanks
Evan Calo
Just 2 options quickly:
1) After the phone boots up, just plug it on a Windows PC through USB. If it recognizes the phone in mass storage mode, you should see the internal and external storage, then you're golden.
2) If that doesn't work, try to plug it on a TV or monitor through HDMI. You can use screen mirroring or webtop to reach the phone interface (if you are on stock ROM). Even if the LCD is bad, the digitizer should work so it recognizes the touch, helps you navigate.
I hope that helps.
Sent from my DROID4 using XDA Free mobile app
EvanCalo said:
Please let me know if there is anything i can try here!!
Click to expand...
Click to collapse
Hi Evan, you might want to give this thread a read, it contains the same problem and how I recovered my data from my phone.
http://forum.xda-developers.com/showthread.php?t=2552978
Hi everyone.
A few days ago a non tech-literate friend of mine told me that he had dropped his phone in the sink (clean, cold water, about three weeks ago). He had since bought another rolleyes: shame to not even try to repair it!) but had precious data on it. I agreed to try and recover it from him as he's quite a good friend. Since I only got the phone long after the incident, it is as far as I can know perfectly dry. I have never had any dealings with Sony before (phone-wise)... I think the data should be attainable, I just don't have the knowledge yet.
Symptoms :
When plugged off, the phone just sits there with really nothing happening.
When plugged on to a power cord (France), there's a softly blinking red light on the left of the top front speaker.
When plugged to a computer, the same soft red light is flashing. (I therefore imagine it indicates charging)
What I have tried :
Holding the power button
Unplugged, for 2, 3, 5, 10, 20, 30 seconds, to no avail
Plugged, and it vibrates shortly after about 6-8 seconds or 2-3 seconds (am I turning it on and off/long press to get the power menu?)
Connecting it to a computer (Windows 7 and Arch linux):
On Arch, there's nothing. No disk/drive of any kind is detected (/dev stays unchanged...)
On windows, the first time I connected I got the pop up indicating a driver install for an "unknown device", and the install failed. Browsing this forum I learned about PC companion, which I installed. Windows then successfully installed a driver for "usb device". Windows explorer does not detect the phone as a media device of any kind and PC companion refuses to connect to the phone : when manually prompted to connect, it recognizes something is plugged, but tells me it "fails(ed) to connect to the pone/tablet. Please refer to the guide", guide of course which is worthless. (No logs or smthng? geez, windows!)
What I have not tried :
I have *no* idea on how to remove cover to access battery and so on. As the back is perfectly smooth I am afraid to break smthng if I try with a knife blade or so...
Sacrificing chicken and/or blond virgins to the blood overlords while chanting black magic
My guess is the screen is dead ( as it shows no sign whatsoever) but the phone seems to be partly working. 1337 guyz out there, ideas, help? (actually anyone is welcome of course :laugh
The main objective is only to recover data, not get it back working (would've sent it for repair otherwise!) If you need more info, I'll be happy to provide it.
G'day to yall!
(As I am currently undergoing heavy fire from my engineering study teachers, I will check this post about once a week. sorry for the answering delays...)
Phenitei said:
Hi everyone.
A few days ago a non tech-literate friend of mine told me that he had dropped his phone in the sink (clean, cold water, about three weeks ago). He had since bought another rolleyes: shame to not even try to repair it!) but had precious data on it. I agreed to try and recover it from him as he's quite a good friend. Since I only got the phone long after the incident, it is as far as I can know perfectly dry. I have never had any dealings with Sony before (phone-wise)... I think the data should be attainable, I just don't have the knowledge yet.
Symptoms :
When plugged off, the phone just sits there with really nothing happening.
When plugged on to a power cord (France), there's a softly blinking red light on the left of the top front speaker.
When plugged to a computer, the same soft red light is flashing. (I therefore imagine it indicates charging)
What I have tried :
Holding the power button
Unplugged, for 2, 3, 5, 10, 20, 30 seconds, to no avail
Plugged, and it vibrates shortly after about 6-8 seconds or 2-3 seconds (am I turning it on and off/long press to get the power menu?)
Connecting it to a computer (Windows 7 and Arch linux):
On Arch, there's nothing. No disk/drive of any kind is detected (/dev stays unchanged...)
On windows, the first time I connected I got the pop up indicating a driver install for an "unknown device", and the install failed. Browsing this forum I learned about PC companion, which I installed. Windows then successfully installed a driver for "usb device". Windows explorer does not detect the phone as a media device of any kind and PC companion refuses to connect to the phone : when manually prompted to connect, it recognizes something is plugged, but tells me it "fails(ed) to connect to the pone/tablet. Please refer to the guide", guide of course which is worthless. (No logs or smthng? geez, windows!)
What I have not tried :
I have *no* idea on how to remove cover to access battery and so on. As the back is perfectly smooth I am afraid to break smthng if I try with a knife blade or so...
Sacrificing chicken and/or blond virgins to the blood overlords while chanting black magic
My guess is the screen is dead ( as it shows no sign whatsoever) but the phone seems to be partly working. 1337 guyz out there, ideas, help? (actually anyone is welcome of course :laugh
The main objective is only to recover data, not get it back working (would've sent it for repair otherwise!) If you need more info, I'll be happy to provide it.
G'day to yall!
(As I am currently undergoing heavy fire from my engineering study teachers, I will check this post about once a week. sorry for the answering delays...)
Click to expand...
Click to collapse
Not realla an idea, but maybe a little help. In the attachement you find a pdf. (Working Instructions for Assembly and Disassembly the phone). Hope, it helps a little. Good luck :fingers-crossed:
Thanks mate! Will look at it this weekend
One of the first thing you should try is to access fastboot. For this you have to hold volume down button while plugging it in to the computer. If the phone is a Xperia SP your led should be blue then (I'm not sure you have this model regarding the description you gave). If this works then we make a small step !
Right I'll try that. Looking at the pdf given by reinipic, it seems it is one, as the phone corresponds to the photo of the Sp C5303/5302/5306/M35h.
Oops my bad!! You are, good sir, perfectly right, the phone is not an SP, as all Sps seem to have the front Camera as well as three sensors on the left of the top speaker. The model I'm working on only has a camera on the right side. ...
Erm as such I'm quite into the wild as to how to guess what model it is (google image is not really being helpfull...), any tips on that?
attached are front, back, and side photographs of the phone.
I have as well tried to long press the down button while connected to a computer (windows 7). The led changed it's pattern : it blinked shortly red twice,then green! :good: The screen still stays off though (which may confirm my hypothesis that it's dead), and the computer does not react.
As always, thx for the help!
Phenitei said:
Right I'll try that. Looking at the pdf given by reinipic, it seems it is one, as the phone corresponds to the photo of the Sp C5303/5302/5306/M35h.
Oops my bad!! You are, good sir, perfectly right, the phone is not an SP, as all Sps seem to have the front Camera as well as three sensors on the left of the top speaker. The model I'm working on only has a camera on the right side. ...
Erm as such I'm quite into the wild as to how to guess what model it is (google image is not really being helpfull...), any tips on that?
attached are front, back, and side photographs of the phone.
I have as well tried to long press the down button while connected to a computer (windows 7). The led changed it's pattern : it blinked shortly red twice,then green! :good: The screen still stays off though (which may confirm my hypothesis that it's dead), and the computer does not react.
As always, thx for the help!
Click to expand...
Click to collapse
:highfive: Bravo man! As pecOra said, you hae done a grat step - the phone is alive! LED blinking red then green, means, that´s ready for flashing a rom with Flashtool! The problem now is to clarify, what Xperia-model it is, after this you can seach in the right thread for a Rom to flash it on the phone with Flashtool
Cool! This has me ask two questions though :
- wouldn't flashing a ROM erase the data I'm trying to retrieve? As it's not on the sd card (whose slot is on the outside, and empty).
- I'm afraid I'm slow here, but how would flashing a ROM help retrieve the data, as the main obstacle is that the data on the internal sd card is not readable
[UPDATE] : if, while connected to a computer, the up-volume button is long pressed, then the del becomes a stable and unchanging blue!
Phenitei said:
Cool! This has me ask two questions though :
- wouldn't flashing a ROM erase the data I'm trying to retrieve? As it's not on the sd card (whose slot is on the outside, and empty).
- I'm afraid I'm slow here, but how would flashing a ROM help retrieve the data, as the main obstacle is that the data on the internal sd card is not readable
Click to expand...
Click to collapse
STOP! Flashing a Rom ALWAYS deletes all data on the internal SD. In the current situation you can make again a functional phone. To readout the data from the SD is an other thing. For this experiment I am to less competent. Maybe another member is smarter than I am, sorry.
No probs! That's also my experience with my phone (wiping I mean), and is why I asked why I would want to flash a ROM. No worries, we all have different skills[emoji41] . I'll help you the day you mess up a samsung [emoji6]
Thx for trying!
Phenitei said:
No probs! That's also my experience with my phone, and is why I asked why I would want to do that. No worries, we all have different skills. I'll help you the day you mess up a samsung
Thx for trying!
Click to expand...
Click to collapse
:good: hope, pecOra can help you!!! He is a great man.
Ok that's good news, it means your phone isn't totally dead. The next step is to look if there is any way to access the data partition or sd from fastboot mode (when the blue led was on, it's generally used to access kernel/recovery partitions from the computer.) I'll make some search today and look in fastboot manual to see if I find something. You should try to find something too.
If there is no way with fastboot we'll try with adb but unless your friend was some kind of developer he probably kept it deactivated.
The phone looks more like a Xperia Z or a Xperia Z1 I think. Our xsp has a big led at the bottom.
Edit :
I found another thread with a similar problem. The solution is to flash a recovery and access adb from the recovery.
forum.xda-developers.com/galaxy-nexus/help/to-recover-data-fastboot-t1871698
The problem is that I'm pretty sure the phone must have an unlocked bootloader.
Is the phone rooted?
pec0ra said:
Ok that's good news, it means your phone isn't totally dead. The next step is to look if there is any way to access the data partition or sd from fastboot mode (when the blue led was on, it's generally used to access kernel/recovery partitions from the computer.) I'll make some search today and look in fastboot manual to see if I find something. You should try to find something too.
If there is no way with fastboot we'll try with adb but unless your friend was some kind of developer he probably kept it deactivated.
The phone looks more like a Xperia Z or a Xperia Z1 I think. Our xsp has a big led at the bottom.
Edit :
I found another thread with a similar problem. The solution is to flash a recovery and access adb from the recovery.
forum.xda-developers.com/galaxy-nexus/help/to-recover-data-fastboot-t1871698
The problem is that I'm pretty sure the phone must have an unlocked bootloader.
Is the phone rooted?
Click to expand...
Click to collapse
:good: +1
Right. I'll look into fastboot and confirm the phone model this we, and will look at the thread you dug out tomorrow (gitta get some maths and physics done first ). (Great job finding the thread by the way! I hadn't seen that one)
I'm certain the phone os neither rooted nor was usb debugging enabled, as my friend is absolutely not into tech.
As always, your help is much appreciated, thank you.
Phenitei said:
Right. I'll look into fastboot and confirm the phone model this we, and will look at the thread you dug out tomorrow (gitta get some maths and physics done first ). (Great job finding the thread by the way! I hadn't seen that one)
I'm certain the phone os neither rooted nor was usb debugging enabled, as my friend is absolutely not into tech.
As always, your help is much appreciated, thank you.
Click to expand...
Click to collapse
Mmmh this is not good. The solutions use adb so you must have it enabled but that's not really a problem because if your phone boots until adb mode, it will probably boot until usb storage mode too. So if you don't have usb storage when booting, you probably won't have adb mode either.
The second solution was to use adb (or usb storage) in another environment which is much less complex and easier to flash without losing any data : the recovery. The problem is that you can only flash a recovery with fastboot when your bootloader is unlocked. The other ways to flash it use adb and as we've seen we don't have it.
I'm pretty sure you can't access any partition from fastboot if your bootloader is unlocked because otherwise it would open easy exploits to gain root without losing your warranty unlocking your BL.
Now what you still have available is flashtool. This is the (copy of the, with more possibilities) official way to flash firmwares. You use it from your computer when your phone is in the mode with the green light. The problem is that with this you can only flash official firmwares. They might still repair your phone depending on the problem but you must be careful not to erase the data. If you want to try this I can help you in the procedure (you can even pm me en français if you want)
By the way, are you trying to access data like app data/ contacts / messages or data of the external storage?
I personally agree the solution of pec0ra to flash a stockrom with the flashtool, without erasing date. It should be the only successful procedure. Good luck man!
---------- Post added at 01:07 PM ---------- Previous post was at 12:40 PM ----------
reinipic said:
I personally agree the solution of pec0ra to flash a stockrom with the flashtool, without erasing date. It should be the only successful procedure. Good luck man!
Click to expand...
Click to collapse
Edit:
btw. when you are opening the flashtool and connect the phone with the pc, than you can see in the flashtool, which Xperia Model it really is, then you can search for the right stockrom and ... buuuuuum :laugh:
Right thanks a lot! I'll take the time to document my self a bit on all that and then I'll be happy to accept your proposal. Merci!
put it in a box of rice 4 days without touching.... you will see the results.
Kmiloxdxd, thanks for your proposal, I'll try! But as I said in the question, I got the phone at least a week after it fell into water, maybe more (up to 3 max) As such, I'm quite sure it's too late for that kind if trick... (which did save a few phones and watches of my own ^^)
You have 2 options..the first one is to reflash stock rom via flashtool without wiping data and the other one which requires a recovery, you can move this zip (http://forum.xda-developers.com/showthread.php?t=1646108) to your sd and move files from internal to external memory.
Hello,
I am looping for assistance and advices.
I wanted to upgrade the phone of my son, for a game, Xperia sp was in 4.3 official Sony, I read several tutorial and I had the idea to pass it into 6.01. So firstly, I did a safeguard with PC software companion but impossible to install it without error (failure configuration) I triée to use titanium as sight in several tutorial, but impossible to use it because it needs that the phone is rooted. I search for a rooter and I find the towelroot application which I install on the phone, and which I launch. I again launch titanium to control that the phone is rooted and it is the case. I start the safeguard of the applications and it is there that begins my problems, the screen remains blocked and the progression of the safeguard remains to zero % and the tactile does not answer any more. I wait a little but nothing changes. I rebooted on the first time with the button power but nothing happens, then with power + volume+ always nothing and finally with the button off in the back of the phone. It shut down, I turn it on it thinking that it was ok but after a few seconds it is blocked again. I tested several times and I always have the same problem.
I dont know what to do anymore.
is the phone recoverable, so yes how?
can I still recover the data of the phone?
I think of a solution, it is to try to install twrp with Fastboot to carry out wipes but if I could have advices before making other mistakes.
I will add that I am beginner on Android (I think that you understood it), I have iPhones of my job.
thank you in advance for your Advices.
Sorry for my bad english.
problem solved.
It is the card SD which blocked the phone
So i suppose you wanted to do a backup of data right? And what do you mean "Blocked"? Phone cannot be turned on?
The phone starts correctly with access to the applications and after a few seconds the screen jams. Solved problem it was the card SD which did not appreciate the use of titanium.
I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions
There is no chance for you to recover your data in this mode.
WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again
Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...
How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...
mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.
First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.