Related
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
muellersmattes said:
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
Click to expand...
Click to collapse
If it is the SIM then try a different SIM, or put a folded piece of paper between the holder and the SIM - I always do that with phones just to make sure it keeps good contact at all times.
Other than that, no real idea mate - sorry
I think it should also work without a SIM. But as said, it just shows the lockscreen for ~2 seconds and then shuts down. I have tried without a sim, it's the same. I'll try with a different one, but I suppose that won't help much. I think i'll also try a kdz reflash, but i'll have to set up my father's PC to do so. Just thought maybe someone knows a quick solution.
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
muellersmattes said:
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
Click to expand...
Click to collapse
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
RuedasLocas said:
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
muellersmattes said:
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
Click to expand...
Click to collapse
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
RuedasLocas said:
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
Click to expand...
Click to collapse
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
muellersmattes said:
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
Click to expand...
Click to collapse
You can try to downgrade before factory reset... some apps won't work but, maybe the phone just don't turn OFF and you'll be able to save your data.
So downgrading didn't work either. I'll use the LG Support Tool to upgrade and factory reset now (with data loss). That should hopefully fix it.
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
muellersmattes said:
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
Click to expand...
Click to collapse
Once that data is gone, just reflash the phone.
My advice, like always is, downgrade, factory reset, upgrade , root, factory reset.
hope you don't tell me that you have problems with flash method...
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
muellersmattes said:
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
Click to expand...
Click to collapse
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
RuedasLocas said:
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
Click to expand...
Click to collapse
Thanks, I thought the Emergency Recovery was still different. So no chance to fix this now. LG's support won't work on Christmas, so three more days stuck with it.
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
muellersmattes said:
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
Click to expand...
Click to collapse
It goes down when charger is connected?
Yes, it does. And it recognises the battery as full, that's why I don't suppose it's because of that. But one never knows.
mines done it a couple times recently too! just living with it till the update!
Problem solved. A new battery did the trick. But I still don't know why it would shut down with the old one.
Verizon Moto X
Every time an incoming or outgoing call is made, audio output is only on the speaker. If I hit the button to turn off speaker, it goes back to speaker seconds later. Can anyone help?
EDIT: No ROM, pure stock from Verizon. I reset the device and cleared cache already.
G00gle26 said:
Verizon Moto X
Every time an incoming or outgoing call is made, audio output is only on the speaker. If I hit the button to turn off speaker, it goes back to speaker seconds later. Can anyone help?
Click to expand...
Click to collapse
Are you using a ROM? Xposed? Stock? First off you could try clearing cache and data of the phone app. If you are using a ROM, search the ROM thread. If you are using Xposed, uninstall it and see if the problem goes away. If the problem persists try a factory reset after backing up your data.
PiousInquisitor said:
Are you using a ROM? Xposed? Stock? First off you could try clearing cache and data of the phone app. If you are using a ROM, search the ROM thread. If you are using Xposed, uninstall it and see if the problem goes away. If the problem persists try a factory reset after backing up your data.
Click to expand...
Click to collapse
Sorry I should I specified that info.
No ROM, pure stock from Verizon. I reset the device and cleared cache already.
G00gle26 said:
Sorry I should I specified that info.
No ROM, pure stock from Verizon. I reset the device and cleared cache already.
Click to expand...
Click to collapse
Boot in safe mode: hold volume down at the first splash screen. From a power on. But if you did a data reset then I suspect a hardware failure.
---------- Post added at 06:37 AM ---------- Previous post was at 06:35 AM ----------
Do a RSD restore of the XML/FXZ.
two issues i have dealt with on the same problems across multiple devices. Main two options causing this are:
1. you downloaded some weird app that did some weird stuff with the speaker phone, even uninstalling the app could still be causing the problem. For this issue (if you can think of any apps you downloaded and possibly used for a day or a minute then uninstalled) go download the app again, look for any setting that could have delt with car mode, or plugged in mode, or docking mode, or speakerphone mode, or something similar and disable it, clear data and cache on app, then uninstall and see if it works.
2. you have dust or some debris in the charging port that is causing the phone to think that it is in dock mode where speaker phone automatically turns on. use air blaster or a toothbrush if the dirt is bigger in there.
those are the two main ones i have seen. see if they work it out. one phone that downloaded an app that caused this was an app about speed velocity while travelling, it had some weird settings for some docking thing i think and i had to check an uncheck it before unsinstalling to get the problem fixed
jayboyyyy said:
two issues i have dealt with on the same problems across multiple devices. Main two options causing this are:
1. you downloaded some weird app that did some weird stuff with the speaker phone, even uninstalling the app could still be causing the problem. For this issue (if you can think of any apps you downloaded and possibly used for a day or a minute then uninstalled) go download the app again, look for any setting that could have delt with car mode, or plugged in mode, or docking mode, or speakerphone mode, or something similar and disable it, clear data and cache on app, then uninstall and see if it works.
2. you have dust or some debris in the charging port that is causing the phone to think that it is in dock mode where speaker phone automatically turns on. use air blaster or a toothbrush if the dirt is bigger in there.
those are the two main ones i have seen. see if they work it out. one phone that downloaded an app that caused this was an app about speed velocity while travelling, it had some weird settings for some docking thing i think and i had to check an uncheck it before unsinstalling to get the problem fixed
Click to expand...
Click to collapse
Didn't download any new apps. I won't through them all and the only ones that are related to the speaker or phone calls is:
eCID
AutomateIt
I did what you said on both apps and cleaned the charging port with an air duster, didn't fix it.
G00gle26 said:
Didn't download any new apps. I won't through them all and the only ones that are related to the speaker or phone calls is:
eCID
AutomateIt
I did what you said on both apps and cleaned the charging port with an air duster, didn't fix it.
Click to expand...
Click to collapse
it might not be an app that you would think is related to phone calls. any app that may change its settings if it is in dock mode could cause. such as moto assist. it could also just be a faulty charger port. I haven't seen anyone else say anything about this issue on an x so i would assume it is either HW related and you need to return it or it is app related. even dusting out the port though might not have gotten some gummy stuff out that could be causing it fyi. but these are the first reports that i have seen so thats all that i got.
jayboyyyy said:
it might not be an app that you would think is related to phone calls. any app that may change its settings if it is in dock mode could cause. such as moto assist. it could also just be a faulty charger port. I haven't seen anyone else say anything about this issue on an x so i would assume it is either HW related and you need to return it or it is app related. even dusting out the port though might not have gotten some gummy stuff out that could be causing it fyi. but these are the first reports that i have seen so thats all that i got.
Click to expand...
Click to collapse
First thing I did was I cleared out Moto Assist and turned off it's features. Thank you for trying though.
G00gle26 said:
First thing I did was I cleared out Moto Assist and turned off it's features. Thank you for trying though.
Click to expand...
Click to collapse
If you are willing to try, attempt to flash the FULL SBF for your carrier (the same version you are currently on) using RSD Lite or manual method (instructions in the General sub-forum, "Return to 100% Stock" thread).
You see, using an SBF to return to stock can actually repair a corrupted or damaged filesystem because it *replaces* the partitions. A "factory restore" cannot. It only erases userdata and cache.
It will erase everything, so copy anything important (pictures etc.) to your PC before doing this. It is your best hope of recovering. If this does not fix it, it is almost certainly a hardware issue.
Good Luck :good:
If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones (they usually make them worse). The 4.4.4 image doesn't wipe data, and when manually flashing, you can exclude the erase userdata command. For manual flashing, use mfastboot and follow the flashing order and commands in the XML. RSD will do it automatically.
Some people have also had no front or rear camera access too, and that's hardware related (usually a ribbon cable connection or defective sensor).
Jason.DROID said:
If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones (they usually make them worse). The 4.4.4 image doesn't wipe data, and when manually flashing, you can exclude the erase userdata command. For manual flashing, use mfastboot and follow the flashing order and commands in the XML. RSD will do it automatically.
Some people have also had no front or rear camera access too, and that's hardware related (usually a ribbon cable connection or defective sensor).
Click to expand...
Click to collapse
The new 4.4.4 "image" -does- erase data. The original leaked FXZ posted by @SamuriHL didn't include the erase userdata command, but the new leaked FXZ does include it. SamuriHL only hosted the first leak temporarily until the new was posted to the droid-developers website.
The actual "images" inside both leaks are 100% identical though. The only difference is the new one contains the erase userdata command, and (I think) the "<step operation="getvar" var="max-download-size" />" command as well. Before anyone asks, NO you don't need to use the new one if you already used the original one. Other than the stated commands, they are completely identical.
I'm only putting this out there so someone doesn't flash the new one thinking their data will be saved -- it will not. That is, of course, unless you use SamuriHL's excellent tools made for this purpose....they allow you to preserve your userdata.
:good:
Jason.DROID said:
If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones they usually make them worse!
Click to expand...
Click to collapse
I always thought so. I got my first Official Moto refurbished phone when Moto sent me a Maxx for my X. Totally different packaging.
---------- Post added at 08:31 AM ---------- Previous post was at 08:14 AM ----------
Oh, & the Maxx is flawless!
I solved it! I isolated the problem to the app AutomateIt. There was a rule that was enabled by default when the app installed that turned the speaker on when away from the ear but the second rule to turn it off when it goes back next to your ear never triggered. So it's not a hardware issue thank GD. Case closed folks, thanks for all your help and the tip for safe mode. :good:
I use ClockworkMod's RecoveryInstaller, ran the .apk, installed it then opened it. There was a large button labeled "flash recovery" and when I pressed it, the phone turned off and won't turn on.
I plugged the phone into my computer and it continuously plays the "plugged in" sound. If I hold down the volume down and the power button, the "plugged in" sound plays more often and has another sound playing right after it, but the phone won't turn on.
I haven't unlocked my bootloader, but I have rooted the phone.
I believe it is in a boot loop or something, because the "plugged in" sound keeps repeating itself, or something like that.
I have an SD card if that is required in fixing the device.
I can't boot into recovery at all, screen keeps black.
rft2149 said:
I use ClockworkMod's RecoveryInstaller, ran the .apk, installed it then opened it. There was a large button labeled "flash recovery" and when I pressed it, the phone turned off and won't turn on.
I plugged the phone into my computer and it continuously plays the "plugged in" sound. If I hold down the volume down and the power button, the "plugged in" sound plays more often and has another sound playing right after it, but the phone won't turn on.
I haven't unlocked my bootloader, but I have rooted the phone.
I believe it is in a boot loop or something, because the "plugged in" sound keeps repeating itself, or something like that.
I have an SD card if that is required in fixing the device.
I can't boot into recovery at all, screen keeps black.
Click to expand...
Click to collapse
Try this
SubliemeSiem said:
Try this
Click to expand...
Click to collapse
I've been trying that, but I can't access my IMEI to get a KDZ file, and I've tried my IMEI on that thread before, and I didn't get any download. I've gotten an IMEI for my model from another thread, but that thread you sent me needs for my phone to connect to my computer, which it can't.
rft2149 said:
I've been trying that, but I can't access my IMEI to get a KDZ file, and I've tried my IMEI on that thread before, and I didn't get any download. I've gotten an IMEI for my model from another thread, but that thread you sent me needs for my phone to connect to my computer, which it can't.
Click to expand...
Click to collapse
Right, you already said that, sorry. In that case I'm afraid there's nothing else you can do, that phone is dead.. I do believe other users who had this kind of problem had to rely on the warranty to get a new phone, so you should go back to the store. And from now on, don't use one-click solutions to do this kind of stuff, the process isn't that hard and there is less risk involved when you just follow a step-by-step guide.
SubliemeSiem said:
Right, you already said that, sorry. In that case I'm afraid there's nothing else you can do, that phone is dead.. I do believe other users who had this kind of problem had to rely on the warranty to get a new phone, so you should go back to the store. And from now on, don't use one-click solutions to do this kind of stuff, the process isn't that hard and there is less risk involved when you just follow a step-by-step guide.
Click to expand...
Click to collapse
I am sending this phone in for a warranty repair. But since I rooted the phone, will they accept it? Keep in mind, I have rooted it with TowelRoot, but I haven't unlocked the bootloader.
rft2149 said:
I am sending this phone in for a warranty repair. But since I rooted the phone, will they accept it? Keep in mind, I have rooted it with TowelRoot, but I haven't unlocked the bootloader.
Click to expand...
Click to collapse
Not sure, in theory they wouldn't have to, since trying to install the bootloader caused your problems in the first place. But I've also heard of other people who did the same kind of thing and could still use the warranty. I just wouldn't tell them how it got bricked, play dumb and say the phone suddenly wouldn't boot up any more Best of luck, mate!
SubliemeSiem said:
Not sure, in theory they wouldn't have to, since trying to install the bootloader caused your problems in the first place. But I've also heard of other people who did the same kind of thing and could still use the warranty. I just wouldn't tell them how it got bricked, play dumb and say the phone suddenly wouldn't boot up any more Best of luck, mate!
Click to expand...
Click to collapse
The main issue I told them, was that it wouldn't boot or turn on. Somehow, battery issues played into it, but I told them that the MAIN issue was that it wouldn't turn on. I don't think they can turn it on if I can't. They have the money and power to try, but I'm pretty sure they're not going to spend a load of time trying to figure it out.
rft2149 said:
The main issue I told them, was that it wouldn't boot or turn on. Somehow, battery issues played into it, but I told them that the MAIN issue was that it wouldn't turn on. I don't think they can turn it on if I can't. They have the money and power to try, but I'm pretty sure they're not going to spend a load of time trying to figure it out.
Click to expand...
Click to collapse
They can easily find out is it rooted or not....................?
If u connect ur phone via usb by pressing vol down button..
U'll enter into download mode..
It clearly says ROOTED.........
But instead u have to try to update phone using B2CAppSetup.exe (official software update tool)
I have a lg d415 it just cut off yesterday n won't turn on i have no clue what to do
Hello, I've had my G Watch R for not quite a full week so far and I've really enjoyed it. Two days ago, I believe that I let the battery die so I placed it on the charger before going to bed. When I woke in the morning i grabbed the watch off the charger without looking at it. Just before i stepped out the door i noticed that it wasn't waking up and It wouldn't even power on. I ran back and slapped it on the charger thinking that it would be more than charged by lunch time. Thats when i noticed the apparent boot issue you can see in the video attached. It hasn't been dropped at all and I have the basic apps installed; facer, watchmaker etc. At this point, Is there anything that I can try short of sending it back?
I've left it on the charger for 24+ hours, it gets slightly warm and stays in the boot loop. As soon as its taken off the charger it has no visible charge and refuses to respond to anything. I purchased it through amazon, so I'm thinking it shouldn't be an issue for me to return it...
http://youtu.be/GgF3iXAhTTI/
Sorry i tried to embed the video but the youtube link for xda seems to be breaking the url somehow
So I have already initiated the return process with amazon and it should be pretty painless. I have almost 3 weeks to send it back, so if anyone has any tips/tricks or ideas I'm more than open to try them....The watch is 100% stock as far as firmware or root is concerned.
Any luck with this? I just got back an RMA for a broken touch sensor, I don't want to have to RMA it again.
try to see if you can get in to the bootloader, and restart the watch from there
i have notice when i charge the watch from empty (so thewatch boots up while charging) it causes problems, usually boot loops as well
I just watched the video (should've done this before hijacking the thread, sorry) and it seems like I'm having a different issue. Instead, mine does the android boot animation, the goes to "Starting Apps" and counting ("x of y Apps"; the y value seems to be different every time), then "Staring Apps" with no count, then it says "Powering Off" and shuts off. But I will post my experience in case someone else with my issue finds this thread.
I'm back up & running today. I got it into the bootloader last night and put it on the charger before I went to sleep (to avoid battery rundown by bootlooping while it charges). I woke up this morning to it bootlooping again. I'm guessing that it restarted itself sometime during the night. I took it off the charger and let it sit for a while (it was pretty warm, so I figured it would be better to let it cool down before trying anything else). I tried to restart it again after about a half hour, but it still only got to "Starting Apps" before shutting off. I reflashed the stock boot, recovery & system images found here: Stock Boot, Recovery and System for G Watch R . I restarted it and completed the initial pairing process (due to wipe when I unlocked it in order to flash system image) and it is now working.
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
To workaround the bootloop while charging, you can boot into recovery (swipe 10 to 4 a clock while Logo is shown, select and press okay to recovery), than charge battery for a while, after that, you can boot to as normally to AW-system and charge to fully battery!
You can charge with USB on PC, it's work fine for me.
scidon37 said:
I just watched the video
I don't know if what I did actually fixed anything or if it just decided to start working, but I will post again if something happens again. If you don't see any more replies from me, then all is still OK.
EDIT 6/22/15 9:53 pm EDT: No good, see below.
Click to expand...
Click to collapse
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Have you tried taking it off the charger and booting it? Also are you running custom software?
bricked watch
atmosphrericks said:
So your gwatch r started doing the same thing again? I have the same problem and it won't connect to the computer via fastboot or adb. How did you get on with the RMA? I cant send mine back due to voided warranty. Still hoping for a solution.
Click to expand...
Click to collapse
Ever find a fix for this? I've been searching like mad the last few weeks. :/
biohazard1150 said:
Ever find a fix for this? I've been searching like mad the last few weeks. :/
Click to expand...
Click to collapse
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
atmosphrericks said:
So i took off the back plate, and found that the spring contact pins inside the watch weren't making good connections to the connect points on the inside of the back plate. Be careful, they are fragile, but you want to bend them out slightly. If you can source parts, get a new contact pin module.
After this, i was able to connect my watch and flash over stock firmware.
I can't guarantee this is what is happening with yours, but let us know if it does work.
I've scince broken the screen and can't find where to get parts!
Click to expand...
Click to collapse
I still haven't found a fix. My charging works fine, but no PC connection. The bootloader/fastboot wont come up, no logo or anything. I'm sure the EMMC chip is fried, it sounds like many are seeing this issue, some with a black screen and some with a snowy screen. I've had several galaxy phones do the exact same so I'm doubting it can be fixed without going to the manufacturer which mine came from redflagdeals and LG wont service the random online store purchases
I had to take the back off and clean and adjust the contacts that make contact through the back panel. Then I could connect via fastboot.
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This solved my problem. As soon as I plugged it into my PC it booted just fine
ouranos2k said:
You can charge with USB on PC, it's work fine for me.
Click to expand...
Click to collapse
This works for me too! Thank you!
Sent from my SM-N920C using Tapatalk
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.