Hi ...
So about Tuesday (14th) morning, my G4 rebooted itself, and went into perpetual bootloop. I bought it on 3/10/2016, so it was out of warranty by a few days. I'd heard, various places online, that people were getting their G4s fixed even out of warranty, but ....
First, I went to the T-Mobile store where I bought the phone. The rep there didn't know about the bootloop issue, and said he wasn't able to help me.
Next, I contacted LG live chat online, and they said they were unable to help because the camera lens is broken. (That happened within a month or so after getting the phone. Even if I didn't tell them up front, they still would have found out when they got it. I'd considered buying a replacement & installing it myself previously, but never could figure out which was the exact OEM model or where to get it.)
I really need to preserve the data that's on the phone. I'm not just talking about pictures, documents, downloaded files, etc (I think camera pics are backed up automatically, but idk about screenshots for example) ... I also mean Wi-Fi credentials, my 60-70+ open Chrome browser tabs & history, txt/mms messages, call logs, voice mails (stored in the T-Mo Visual Voicemail app) - basically everything.
Both T-Mobile and LG, if I understood right, told me that if they took the phone in for repair, one of the first things they'd do is factory reset it, which would wipe out that data, and I can't have that.
I'm at a loss for what to do right now. I really want to get my specific phone's bootloop / motherboard issue fixed, with its data retained, and not get it replaced, at no cost to me. (Don't care so much about the camera, it's still working fine even with the external lens busted off.) If I have to replace the phone, I still need to preserve the data I mentioned above, plus anything else I may have forgotten. (Basically a full system image/clone.) Also I haven't rooted / installed a custom OS.
If replacing with a new phone is in order, I'll want a really good one without breaking the bank. (I was going to keep the G4 until 2020 or 2021, if not longer - my T-Mobile G1 lasted 4.5 years and was a then-lower-end phone at the time than the G4.) I'm still trying to figure out what all I want in the phone, or what my budget is. (I *do* know I don't want anything by Apple, or an equivalent of the G4 or Note 7 of course.) My initial budget idea (ONLY for complete phone replacement, NOT if repair is involved), subject to modification, would include taking the $ I would have used to upgrade my 4790K desktop PC to Ryzen 7, and instead getting a new phone. I'm thinking anywhere from $300 to $800. A few preliminary models that popped up in my search are the LG G6, Galaxy S8, Note 8, 1+5, Pixel/2, and a few other Asian-sounding brands I'm not sure about yet. If it's decided I have to get a new phone, I'll be making another post/thread asking for more advice in detail on that.
pianoplayer88key said:
Hi ...
So about Tuesday (14th) morning, my G4 rebooted itself, and went into perpetual bootloop. I bought it on 3/10/2016, so it was out of warranty by a few days. I'd heard, various places online, that people were getting their G4s fixed even out of warranty, but ....
First, I went to the T-Mobile store where I bought the phone. The rep there didn't know about the bootloop issue, and said he wasn't able to help me.
Next, I contacted LG live chat online, and they said they were unable to help because the camera lens is broken. (That happened within a month or so after getting the phone. Even if I didn't tell them up front, they still would have found out when they got it. I'd considered buying a replacement & installing it myself previously, but never could figure out which was the exact OEM model or where to get it.)
I really need to preserve the data that's on the phone. I'm not just talking about pictures, documents, downloaded files, etc (I think camera pics are backed up automatically, but idk about screenshots for example) ... I also mean Wi-Fi credentials, my 60-70+ open Chrome browser tabs & history, txt/mms messages, call logs, voice mails (stored in the T-Mo Visual Voicemail app) - basically everything.
Both T-Mobile and LG, if I understood right, told me that if they took the phone in for repair, one of the first things they'd do is factory reset it, which would wipe out that data, and I can't have that.
I'm at a loss for what to do right now. I really want to get my specific phone's bootloop / motherboard issue fixed, with its data retained, and not get it replaced, at no cost to me. (Don't care so much about the camera, it's still working fine even with the external lens busted off.) If I have to replace the phone, I still need to preserve the data I mentioned above, plus anything else I may have forgotten. (Basically a full system image/clone.) Also I haven't rooted / installed a custom OS.
If replacing with a new phone is in order, I'll want a really good one without breaking the bank. (I was going to keep the G4 until 2020 or 2021, if not longer - my T-Mobile G1 lasted 4.5 years and was a then-lower-end phone at the time than the G4.) I'm still trying to figure out what all I want in the phone, or what my budget is. (I *do* know I don't want anything by Apple, or an equivalent of the G4 or Note 7 of course.) My initial budget idea (ONLY for complete phone replacement, NOT if repair is involved), subject to modification, would include taking the $ I would have used to upgrade my 4790K desktop PC to Ryzen 7, and instead getting a new phone. I'm thinking anywhere from $300 to $800. A few preliminary models that popped up in my search are the LG G6, Galaxy S8, Note 8, 1+5, Pixel/2, and a few other Asian-sounding brands I'm not sure about yet. If it's decided I have to get a new phone, I'll be making another post/thread asking for more advice in detail on that.
Click to expand...
Click to collapse
the safe way is to do the freezer method search and youll find tutorial.. get you data and stuff. use titanium to back up apps with data with the paid app..
raptorddd said:
the safe way is to do the freezer method search and youll find tutorial.. get you data and stuff. use titanium to back up apps with data with the paid app..
Click to expand...
Click to collapse
I've heard of the freezer method. I did pop it in the fridge and it almost started to work for a minute, but maybe I should try the freezer. I've also heard of people heating it and getting some temporary use out of it.
I have the paid Titanium Backup on my rooted Galaxy Relay 4G, but I haven't rooted the G4. And, once I went to a new phone, how would I restore without root? (I'd decided not to root until the warranty expired, but it'd be nice to get one that's more friendly to that in the future, also have better full backups, etc.)
Also I've heard there's a way to disable a couple cores & get it working that way, but I have Marshmallow and I hear it requires Lollipop.
pianoplayer88key said:
I've heard of the freezer method. I did pop it in the fridge and it almost started to work for a minute, but maybe I should try the freezer. I've also heard of people heating it and getting some temporary use out of it.
I have the paid Titanium Backup on my rooted Galaxy Relay 4G, but I haven't rooted the G4. And, once I went to a new phone, how would I restore without root? (I'd decided not to root until the warranty expired, but it'd be nice to get one that's more friendly to that in the future, also have better full backups, etc.)
Also I've heard there's a way to disable a couple cores & get it working that way, but I have Marshmallow and I hear it requires Lollipop.
Click to expand...
Click to collapse
we have antirollback in h811 if you are in 20i you are okey to downgrade if higher then 20i say 20o then you cant downgrade to lollipop.
not sure how you would go about restoring. your data..
raptorddd said:
we have antirollback in h811 if you are in 20i you are okey to downgrade if higher then 20i say 20o then you cant downgrade to lollipop.
not sure how you would go about restoring. your data..
Click to expand...
Click to collapse
Hmm... well since I can't boot (for now) past the LG screen, idk if I can even get TO a place where I can attempt a rollback.
And even if I have to use other methods to get the data back (so long as it doesn't cost much, as in less than the cost of an SD card) ... then another important criteria for my next phone is automatic backup of *everything*, either to the cloud, or to a second removable micro SD card, or something. (And, by backup of everything, I mean full system image basically.)
And the data I'm talking about includes, but is not limited to, call logs, browser history & open tabs (chrome was my primary browser on that phone), sms/mms messages, saved voicemails (in the T-Mobile Visual Voicemail app), and other things that aren't saved in places like Documents, Downloads, DCIM, Pictures, etc.
pianoplayer88key said:
Hmm... well since I can't boot (for now) past the LG screen, idk if I can even get TO a place where I can attempt a rollback.
And even if I have to use other methods to get the data back (so long as it doesn't cost much, as in less than the cost of an SD card) ... then another important criteria for my next phone is automatic backup of *everything*, either to the cloud, or to a second removable micro SD card, or something. (And, by backup of everything, I mean full system image basically.)
And the data I'm talking about includes, but is not limited to, call logs, browser history & open tabs (chrome was my primary browser on that phone), sms/mms messages, saved voicemails (in the T-Mobile Visual Voicemail app), and other things that aren't saved in places like Documents, Downloads, DCIM, Pictures, etc.
Click to expand...
Click to collapse
is bootloopng . thats a hardware issue.. i would suggest to do the freezer method .making sure no moist gets in phone.. i think people put in frezzer with cable and recovers their data.
So ... the freezer method has worked (with the phone in a Ziploc bag), at least partially. After turning off WiFi, a few days ago I was able to use ES File Explorer (already installed) to copy the internal phone memory to a 128GB SD card which was only about 10-20% full or so. (I couldn't copy absolutely everything, as my G4 isn't rooted yet.) I did it in stages - first copied several user data folders just in case it croaked mid-backup (it didn't), then did the rest.
Just earlier this morning, I used SuperBackup+ (or whatever it's called, I forget atm & the phone's charging again) to back up a few more things.
Then I went into the settings to see if anything was set to back up to the cloud, or could be backed up. Under "Backup and Reset", it was set to back up to my Google account. I also checked a few other settings.
Right before turning on WiFi again, I opened CPU-Z, to find most of the temps around 8°C. After turning WiFi back on, within seconds most of the temps shot up to the 30s to 60s °C, and the top 2 on the list (which included battery) pegged at 140°C, then the phone rebooted itself. So apparently turning WiFi on quickly overwhelms the phone. (I can't use mobile data, as I took the SIM card out and am using it in my SGH-T699 for now.) It then started up briefly, and while I *think* I may have been able to turn off WiFi again before it rebooted again, it started looping, from what I could tell. (Was probably time to take a break anyway, as I'd been standing there for a good 10-15 minutes or so with the freezer door open.)
I'm still hoping I might have a little bit of life left for backing up, after giving the phone a rest, battery a charge, letting the freezer settle down, and refreezing the phone.
One more thing I'd like to do with the phone - root it. Is there a way to do it without an internet connection, if possible without a computer (although maybe I could shut the freezer door on the USB cable), and for sure without wiping the device? I'd really like to use Titanium Backup Pro (already installed) to back everything up to the 128GB SD card.
Also I've heard about possibly disabling the two fast CPU cores, but also heard that may only work on Lollipop. (My G4 has Marshmallow installed.)
Anyway, right now the phone is plugged in (out of the freezer) and charging again. Interesting thing though ... while it was powered on in the freezer, it was saying I had 51% battery left. (This was right after I'd pulled it off the charger and it said 98-100% or so - the powered-off battery meter.) Then, plugging it back in (again powered off), it said 78%. Is the huge discrepancy in battery percentages temperature related, or indicative of another issue like a weakening battery? (The battery hasn't swelled at all, from what I can tell.)
I think it's time for a new phone soon, though. I might make another topic with more details, but a few I'm looking at maybe are the Asus Zenfone AR, Google Pixel, OnePlus 3T, Samsung Galaxy S7, maybe a few others. (I'm not as sure about the LG G6 or V20.) Other brands under consideration include HTC, Huawei, LeEco, Motorola, Oppo, vivo, Xiaomi & ZTE.
Basically I'd like something that
officially supports rooting / custom ROMs (and stock ROM is as close to vanilla Android as possible),
is officially supported for updates for a good while (for example if it comes with Android 7, I can upgrade to 9 or if possible 10 OTA, and beyond with community-made ROMs),
has a decent CPU/GPU (like SD 820/821/835 & Adreno 530/540),
plenty of RAM (6+ GB),
a decent amount of internal storage (64+ GB),
has either a micro SD slot or supports USB OTG or both,
among other things.
I'm guessing the 1+3T might be the best compromise? (Or stretch the budget & get the Pixel?) Or should I maybe consider waiting for the Pixel 2 or the OnePlus 4/5? Or get one of the other options / something else entirely? (I'd like to buy within the next month or two, if not sooner.) I had been planning to upgrade my desktop PC to AMD Ryzen 7, but figured I'd use the $ I would have spent on that, on the phone instead. (I can limp along on my i7-4790K a while longer, or my laptop's i7-6700K, etc, it'll just be somewhat slower in video editing, multitasking, etc. From what I hear my i7s are maybe faster at 1080p gaming, but I don't game all that much.)
I'm on T-Mobile - the $30/month 5GB+100min plan for now, but eventually tentatively plan to upgrade to unlimited with the unlimited hotspot addon.
Related
This is a bad week. Yesterday I dropped my Xperia Z onto the pavement, and it got a major damage at the polyamid frame on the upper right corner. It could have benn worse. no display or back glass broken. Oh, and the cover for the headset plug has to be replaced, too. See the sad picture attached. Repair will cost about 112 Euros (and I think another 100 Euros for spare parts) Today my SanDisk 32GB micro SDHC died from one second to another. Completely dead. It's not even recognized anymore, regardless in which PC or Android Device I put it in.
However, enough self-pity, my question is: How do I secure my whole phone from curious repair-workers? My smartphone is essentially full of sensible and private Data. Emails, Texts, Photos, all the Apps with stored Logins (Facebook and the likes).
My first idea is the Android built-in Encryption under Settings > Security > Encrypt Phone. I've never done that, because it says it takes a whole hour, and there is no information about this encryption can be reverted. Because maybe some App stops working, or it makes the whole phone slow. And now the most important question: Is it worth the effort? Is it really secure facing an autorized sony repair staff member?
Secondly I came up with the thougt of doing a backup. Maybe the Repairman calls me and says he has to do a full service test to ensure every internal bit an piece is still working after repair. Which might mean he has to have access to the phone (and the service menu). Since I have encrypted and locked my phone, this can only be done via factory reset. So I should have an complete backup. Has anyone ever tried the built in backup and restore? Does it really backup everything? Every App, evry Data, every setting (widgets and stuff), well plain and simple - a copy of my phone current state? At the moment it only offers me to backup system files and data, might be due to the fact that there is no sd-card and the internal memory has not enough space.
Any other backupsolutions? My phone is not rooted, and rather shouldn't be (warranty issues)
besserde said:
This is a bad week. Yesterday I dropped my Xperia Z onto the pavement, and it got a major damage at the polyamid frame on the upper right corner. It could have benn worse. no display or back glass broken. Oh, and the cover for the headset plug has to be replaced, too. See the sad picture attached. Repair will cost about 112 Euros (and I think another 100 Euros for spare parts) Today my SanDisk 32GB micro SDHC died from one second to another. Completely dead. It's not even recognized anymore, regardless in which PC or Android Device I put it in.
However, enough self-pity, my question is: How do I secure my whole phone from curious repair-workers? My smartphone is essentially full of sensible and private Data. Emails, Texts, Photos, all the Apps with stored Logins (Facebook and the likes).
My first idea is the Android built-in Encryption under Settings > Security > Encrypt Phone. I've never done that, because it says it takes a whole hour, and there is no information about this encryption can be reverted. Because maybe some App stops working, or it makes the whole phone slow. And now the most important question: Is it worth the effort? Is it really secure facing an autorized sony repair staff member?
Secondly I came up with the thougt of doing a backup. Maybe the Repairman calls me and says he has to do a full service test to ensure every internal bit an piece is still working after repair. Which might mean he has to have access to the phone (and the service menu). Since I have encrypted and locked my phone, this can only be done via factory reset. So I should have an complete backup. Has anyone ever tried the built in backup and restore? Does it really backup everything? Every App, evry Data, every setting (widgets and stuff), well plain and simple - a copy of my phone current state? At the moment it only offers me to backup system files and data, might be due to the fact that there is no sd-card and the internal memory has not enough space.
Any other backupsolutions? My phone is not rooted, and rather shouldn't be (warranty issues)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2116920
There you go.
But anyways, I'd say root your phone install cwm and do a nandroid backup. Save the backup file(s) somewhere else (not on your phone duh). Then do a factory reset and send the phone like that.
Dsteppa said:
http://forum.xda-developers.com/showthread.php?t=2116920
There you go.
Click to expand...
Click to collapse
I wasn't sure if my question concerning encryption is right in the Troubleshooting forums. But if so, maybe an admin can move the thread?
According to your answer I assume the aformentioned stock backup solution isn't that useful at all?
What's with the encryption security?
As of right now I'm missing pretty much every file on my Internal Storage. No TiBu, no SMS Backups, no pics. However under storage in the settings menu it still shows 9 Gigs Free, which leads me to believe that its there, just not visible... There are some folders, but they are empty or don't contain the files it used to.
I noticed it at 2 AM when SMS backup & Restore notified me that it wouldn't backup because it couldn't find the SMS.xml file. I used Astro and ES File Manager to find it manually and I couldn't, at which point I noticed everything was missing.
Prior to that my phone was plugged into my PC, simply to charge. I was on the phone walking a friend through a Windows update and installing some software, and I plugged into my USB 2.0 port to charge the phone (3 hour phone call), which I've used multiple times. While it was plugged in I didn't really us the PC much other than google searches and reading news\posts\forums. I did however install Avast Antivirus cause I was walking her through it and I've never used it before. I'm hoping that had nothing to do with it. I googled Avast wiped my phone, and various similar phrases and didn't find any similar forum posts.
At this point, I could write a whole book about what might have caused it. I really have no clue. I'm looking for either anyone with a similar experience, or more importantly, anyone with a resolution.
Edit: I have a GSM Dev, Unlocked Rooted. Tmobile 4.4.2 using Faux Kernel.
That sucks dude! I haven't heard of this randomly happening on any phone I've had. Aside from recovery wipe accidents.
Drag!
Sent from my N5 cell phone telephone....
Haven't even been in recovery for a while. Even the backups made in recovery aren't there or aren't visible to the recovery either. I'm not even upset, I've lost things before due to my flashaholic tendencies, but I don't even flash stuff on this phone. That was one of the main reasons I kept this instead of my Nexus5, figured I'd be more productive not having to flash all the time. Might as well get a different phone...
More importantly I want to know the cause so that I and others can avoid it happening again. Almost makes me wish I kept my Nexus5, which now that I think of it, I have a fairly recent backup of on my PC. Who hoo!
Anyone with any thoughts or input, greatly appreciated.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
Hello all, wanting to use ADB to do a backup of my device. Running OSX 10.9, Moto X 4.4.2 VZW, unrooted, stock. I've downloaded the Android SDK, ran it, and updated it; downloaded and installed the Motorola drivers; enabled USB debugging; navigated to adb and can run commands, but when I run adb devices, it does not list my device. Any thoughts?
Thanks!
Its your drivers. They aren't letting your PC see the phone.
Now, I know nothing of Mac....so not sure what you can do. Except uninstall them completely. Download again and be sure they're the right ones. Also, try another cable perhaps.
KJ said:
Its your drivers. They aren't letting your PC see the phone.
Now, I know nothing of Mac....so not sure what you can do. Except uninstall them completely. Download again and be sure they're the right ones. Also, try another cable perhaps.
Click to expand...
Click to collapse
The phone is being recognized by the computer. I can transfer data and connect to Android File Transfer, etc. Just isn't being recognized by ADB. I'll try reinstalling the drivers, though.
patheimata said:
The phone is being recognized by the computer. I can transfer data and connect to Android File Transfer, etc. Just isn't being recognized by ADB. I'll try reinstalling the drivers, though.
Click to expand...
Click to collapse
Sometimes adb has issues while booted into android. Try this: Unplug the phone from the usb cable. Power it off.
Now, hold down the VOL DOWN button, and power it back on. You should boot into the bootloader. The screen will say something about "AP Fastboot Mode".
Now, plug the usb cord back in. adb devices should now respond with your connected phone, and your adb commands should work.
May I ask why you are backing up your phone via adb? Or more aptly, what do you plan to do with the backup? With a locked bootloader, there should be no way you will be able to restore whatever backup you plan to make. What am I missing?
Good Luck
samwathegreat said:
Sometimes adb has issues while booted into android. Try this: Unplug the phone from the usb cable. Power it off.
Now, hold down the VOL DOWN button, and power it back on. You should boot into the bootloader. The screen will say something about "AP Fastboot Mode".
Now, plug the usb cord back in. adb devices should now respond with your connected phone, and your adb commands should work.
May I ask why you are backing up your phone via adb? Or more aptly, what do you plan to do with the backup? With a locked bootloader, there should be no way you will be able to restore whatever backup you plan to make. What am I missing?
Good Luck
Click to expand...
Click to collapse
Thanks, I had intended to try the bootloader and quite frankly forgot as I got caught up troubleshooting other methods. I'll try that shortly and post results.
Meanwhile, you may be right. I've found lots of conflicting information. At least one person in the Motorola forums claims to have been able to do an adb backup and then restore it on his locked device after a FDR. I need to do one to try to deal with some battery issues. I was trying to find the path of least resistance for backup and restore, although I'm two days into researching this, so I can pretty well say this is no longer the path of least resistance, but I haven't wanted to give up, either, if it's possible...
patheimata said:
Thanks, I had intended to try the bootloader and quite frankly forgot as I got caught up troubleshooting other methods. I'll try that shortly and post results.
Meanwhile, you may be right. I've found lots of conflicting information. At least one person in the Motorola forums claims to have been able to do an adb backup and then restore it on his locked device after a FDR. I need to do one to try to deal with some battery issues. I was trying to find the path of least resistance for backup and restore, although I'm two days into researching this, so I can pretty well say this is no longer the path of least resistance, but I haven't wanted to give up, either, if it's possible...
Click to expand...
Click to collapse
My best advice would be to make a list of all the apps you need, save any pictures or files you need, do FDR, then use the list to re-install your apps, and copy your pictures / files back, and set everything back up the way you want it.
Even if you are able to 'backup via adb', and do a FDR, once you subsequently do your 'restore', you will have the exact same issues you are having now. Battery issues are usually caused by misbehaving apps, but even if you assume the issue is caused by something else, the method you are pursuing is ill-advised.
Ok, so when you do a FDR, it clears the data and cache partitions, essentially returning the device to factory assuming you haven't tried to do root exploits or similar.
If you do a restore, it writes to....(you guessed it!) the data and possibly cache partitions. You'll essentially be right back at square 1 so to speak because -whatever- the problem is, you'll RESTORE it...
EDIT: What kind of battery life are you getting on your X? Can you give us an idea how long it is lasting, and tell us a little about your usage patterns. How much time do you spend on calls, and how much of the time is the screen on?
With what I would consider 'average' usage, I normally get 14~18 hours between charges. This includes very little talk time, but regular internet usage, and usually 1-3 hours of internet radio streaming.
I'm just curious how long yours is lasting between charges.
samwathegreat said:
My best advice would be to make a list of all the apps you need, save any pictures or files you need, do FDR, then use the list to re-install your apps, and copy your pictures / files back, and set everything back up the way you want it.
Even if you are able to 'backup via adb', and do a FDR, once you subsequently do your 'restore', you will have the exact same issues you are having now. Battery issues are usually caused by misbehaving apps, but even if you assume the issue is caused by something else, the method you are pursuing is ill-advised.
Ok, so when you do a FDR, it clears the data and cache partitions, essentially returning the device to factory assuming you haven't tried to do root exploits or similar.
If you do a restore, it writes to....(you guessed it!) the data and possibly cache partitions. You'll essentially be right back at square 1 so to speak because -whatever- the problem is, you'll RESTORE it...
EDIT: What kind of battery life are you getting on your X? Can you give us an idea how long it is lasting, and tell us a little about your usage patterns. How much time do you spend on calls, and how much of the time is the screen on?
With what I would consider 'average' usage, I normally get 14~18 hours between charges. This includes very little talk time, but regular internet usage, and usually 1-3 hours of internet radio streaming.
I'm just curious how long yours is lasting between charges.
Click to expand...
Click to collapse
Absolutely.
First, agreed on the app and cache situation. I was going to exclude apps on the adb backup and just use it for pictures, settings, text messages, etc., and leave out of the backup would be potentially corrupting it after the FDR. I've used other apps in the past to back those things up, but the promise of adb seemed easier (and more fun), thus going that route. I think I've thrown in the towel on that plan at this point, but it has been a good learning experience as I learned a lot commands and troubleshooting methods in that department.
As far as battery life goes, I've had two devices. Started with a dev edition, and while I had that, I was really impressed that it would make it all day long and still have some battery leftover at the end of the day. I exchanged it for a MotoMaker edition, though. I'm not sure I ever remember this one getting as good as battery life as the other, although it's been 5 months, so it's hard to tell. Nevertheless, 18 hours would be fantastic for me.
GSAM says my average fully charged battery lasts 14 hours, with 7 hours and 4 minutes active time. That sounds pretty on par with you, but looking at the charts, I believe they're projecting from 100%–0% as I wouldn't say I typically make it from 100%–20%, which is when I always try to recharge by. The 7 hours active is where I assume my problem lies, and thus the desire to try an FDR. I use my phone a lot, but I'm not active on it for over 7 hours a day. GSAM says my average screen on time is 2h 8min, max of 2h 33min. (These averages are over a 2 month period.) In light of that, I'm regularly charging midday to make sure I can make it through the end of the night.
Regular usage patterns include very little by way of voice calling. I felt like I was on the phone a lot today, that was probably no more than 10–15 minutes. Most of the rest of the SOT time split between texting and internet/light app usage.
Android OS is of course the far and away process consuming battery, which I realize tells us nothing and isn't that uncommon, especially when the phone isn't in use.
Over the past few months, I've tried isolating the typical likely suspects (Facebook and Facebook Messenger, Google+, location services, etc.), uninstalling them, and looking for battery improvements to no avail. The only time I ever really saw a direct correlation with a particular app that I could trace has been with Google Camera. I haven't reinstalled it since they're most recent update, but while it was installed, after it's first update I dropped to about 6–8 hours of battery life.
I've also participated a good amount in this forum on the issue: https://forums.motorola.com/posts/6675cef7e3?page=31 which also happens to be where I read of user jason.motox's experience backing and and restoring with adb.
Alright, I think that's a good start from there. Would love anyone's thoughts on best practices, etc. As much as I hate the thought of adding a few apps at a time every few days, I know that's the best way to go to ensure it's not an app. But anything else that anyone else is aware of to watch out for would be useful. Also happy to post a list of currently installed apps if that would be useful.
EDIT (A thought I started and never completed in the original post): I have read in the Motorola forums of at least one user eventually having the cellular radio replaced in theirs, which solved their battery life. In a 31 page thread, I had only seen one user have a FDR actually fix their battery problems, so I haven't exactly been hopeful that it would help mine. In addition to that, since I remember my Dev Edition getting better battery life all things being equal, it does make me wonder if mine is more hardware related than app or software/firmware.
patheimata said:
Absolutely.
First, agreed on the app and cache situation. I was going to exclude apps on the adb and just use it for pictures, settings, text messages, etc., and leave out of the backup would be potentially corrupting it after the FDR. I've used other apps in the past to back those things up, but the promise of adb seemed easier (and more fun), thus going that route. I think I've thrown in the towel on that plan at this point, but it has been a good learning experience as I learned a lot commands and troubleshooting methods in that department.
As far as battery life goes, I've had two devices. Started with a dev edition, and while I had that, I was really impressed that it would make it all day long and still have some battery leftover at the end of the day. I exchanged it for a MotoMaker edition, though. I'm not sure I ever remember this one getting as good as battery life as the other, although it's been 5 months, so it's hard to tell. Nevertheless, 18 hours would be fantastic for me.
GSAM says my average fully charged battery lasts 14 hours, with 7 hours and 4 minutes active time. That sounds pretty on par with you, but looking at the charts, I believe they're projecting from 100%–0% as I wouldn't say I typically make it from 100%–20%, which is when I always try to recharge by. The 7 hours active is where I assume my problem lies, and thus the desire to try an FDR. I use my phone a lot, but I'm not active on it for over 7 hours a day. GSAM says my average screen on time is 2h 8min, max of 2h 33min. (These averages are over a 2 month period.) In light of that, I'm regularly charging midday to make sure I can make it through the end of the night.
Regular usage patterns include very little by way of voice calling. I felt like I was on the phone a lot today, that was probably no more than 10–15 minutes. Most of the rest of the SOT time split between texting and internet/light app usage.
Android OS is of course the far and away process consuming battery, which I realize tells us nothing and isn't that uncommon, especially when the phone isn't in use.
Over the past few months, I've tried isolating the typical likely suspects (Facebook and Facebook Messenger, Google+, location services, etc.), uninstalling them, and looking for battery improvements to no avail. The only time I ever really saw a direct correlation with a particular app that I could trace has been with Google Camera. I haven't reinstalled it since they're most recent update, but while it was installed, after it's first update I dropped to about 6–8 hours of battery life.
I've also participated a good amount in this forum on the issue: https://forums.motorola.com/posts/6675cef7e3?page=31 which also happens to be where I read of user jason.motox's experience backing and and restoring with adb.
Alright, I think that's a good start from there. Would love anyone's thoughts on best practices, etc. As much as I hate the thought of adding a few apps at a time every few days, I know that's the best way to go to ensure it's not an app. But anything else that anyone else is aware of to watch out for would be useful. Also happy to post a list of currently installed apps if that would be useful.
I have read in the Motorola forums of at least one user eventually having the cellular radio replaced in theirs
Click to expand...
Click to collapse
Who is your carrier? Are you rooted, or are you able to unlock your BL? There is a root app called "Greenify" that many people swear by. It helps identify potential 'problem apps', and actually allows you to 'hibernate' them.
This basically 'hides' the app from the system completely, but you don't notice. When you explicitly launch the app it functions 100% normally, but a short time after you exit it, it gets hibernated again so it can't suck any power.
If you are rooted, or if you may consider unlocking, I would suggest giving Greenify a try. It always sucks to have to charge mid-day.
Also remember that even if moto won't unlock your BL, the gentleman from China will...for a small fee of course
samwathegreat said:
Who is your carrier? Are you rooted, or are you able to unlock your BL? There is a root app called "Greenify" that many people swear by. It helps identify potential 'problem apps', and actually allows you to 'hibernate' them.
This basically 'hides' the app from the system completely, but you don't notice. When you explicitly launch the app it functions 100% normally, but a short time after you exit it, it gets hibernated again so it can't suck any power.
If you are rooted, or if you may consider unlocking, I would suggest giving Greenify a try. It always sucks to have to charge mid-day.
Also remember that even if moto won't unlock your BL, the gentleman from China will...for a small fee of course
Click to expand...
Click to collapse
Sadly I'm a Verizon user, and since I didn't keep my Dev Edition, my bootloader is locked down hard core. I'd love to use Greenify. Had it on my GNex (speaking of atrocious battery life!), but no such luck here. I've contemplated unlocking and rooting, but I have read a lot of horror stories of OTA updates with the X for those who are unlocked and/or rooted and just didn't want to deal with all that. In moments like these, though, it makes me want to send a few bucks to that Chinese gentleman...
patheimata said:
Sadly I'm a Verizon user, and since I didn't keep my Dev Edition, my bootloader is locked down hard core. I'd love to use Greenify. Had it on my GNex (speaking of atrocious battery life!), but no such luck here. I've contemplated unlocking and rooting, but I have read a lot of horror stories of OTA updates with the X for those who are unlocked and/or rooted and just didn't want to deal with all that. In moments like these, though, it makes me want to send a few bucks to that Chinese gentleman...
Click to expand...
Click to collapse
There are just a few caveats to being unlocked:
If a new OTA comes out, it is recommended to return to stock before accepting the OTA. This is because OTAs include a "manifest" of the files that SHOULD be present on the device, along with their checksums. A modified device often won't match the manifest.
Don't let this scare you though. We may not be updated past 4.4.2 heck, 4.4.3 hasn't been released on anything yet. And if we do get another OTA, you can SBF back to stock, take the update, and then re-install everything.
In my humble opinion, the ability to use root apps (especially TETHER) is much more important to me that the minor inconvenience of possibly having to set everything back up again in the future.
If you're considering it, I recommend you take the plunge. You will get your money back if he doesn't have your code. I was able to unlock my device using the China method this 2nd time around and my device is from Nov 2013 - he still had my code. So there ARE some 2013 models in his database for sure....or I wouldn't have gotten one.
If you suspect this is a hardware problem, unlocking is ill-advised as your warranty will be void. Even if you re-lock the bootloader, it will never show "LOCKED" - it will say "RE-LOCKED" instead......and they will know you had unlocked it.
Good Luck
Hello,
My wife dropped her moto X last night.
It is bone stock and on kitkat.
The screen is now black and has no use. nothing has brought it up including fast reboot.
When I plug it into the computer I get unknown device called fast reboot. I do have the motorola driver software installed.
I took the phone to a repair shop, I also have a moto X and they took both phones apart and plugged her motherboard into my screen. From there he said it was an android logo with a question mark and the phone is screwed.
Having gone through issues with my tf101 in the past and learning info on this site, I have brought stuff from the dead before and dont believe it is totaled.
Seeking threads for similar issues on how to get into the hard drive and move photos and etc to my computer even while screen is dead and cannot turn on USB debugging if any are out there.
The photos on the phone are every single photo my wife has taken of our 3 month old baby including her first thanksgiving. She is devastated and I have to find a solution. Motorola will likely replace it for free but I need the data first.
I am in Tempe.
Hi,
I will have your thread moved to your device section. But I'll say that unless your computer can see it as a storage device, there will be nothing you can do unfortunately.
Hopefully someone has some ideas though. And always backup pics to computer or online storage down the road... Using phones as permanent storage is far too risky...
Good luck!
The simple solution would have been what you already tried, switching the motherboard over. Assuming that is for sure not an option then only thing I can think of is trying to get data off of the Nand flash chip, depending on how far you want to go with it.
- See the Moto X iFixit teardown article, Step 15 : https://www.ifixit.com/Teardown/Motorola+Moto+X+Teardown/16867
- Watch YouTube videos like this one: http://m.youtube.com/watch?v=37wHcIQKUlk
- Read a similar question on iFixit: https://www.ifixit.com/Answers/View/112224/Can+memory+on+board+(16GB)+be+removed+and+accessed
So far information suggests it's doable. But maybe not diy. In that case, look for companies that do this kind of thing. Google search something like "nand flash data recovery" get a few results like: http://www.eprovided.com/nand-flash-data-recovery.php
Good luck.
Note: I've never tried this myself. I have my data in double backups. terabytes of external storage are cheap nowadays.
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.