Hello I recently bought a brand new in box Moto x4 Android one I think and when I got the phone it lasted two days before it went full black, wouldn't cut on, wouldn't light on the charger and acted pretty much dead.
The first time it happened after I unlocked the bootloader, wiped my phone and installed lineage on and TWRP on it from a cmd booted up TWRP.
I got a replacement phone and this one didn't last a night as I tried to do the same thing but I payed attention and noticed the screen darkening as I unlocked the bootloader as a sign of things to come but the same thing happened after I installed lineage and tried to reboot.
I sent the phone back again today and wanted to ask experts here if I might have done anything wrong as I followed instructions from the lineage website and bootloader unlock instructions from Motorola.
This also isn't my first time rooting or installing custom order as I have a 3 year old Moto g4 play rooted with lineage os that's been rough but has been good to me but it's showing it's age(Sim slot went out, speaker messed up, weak antenna).
Related
I rooted when the phone first came out, did the forever root method days ago, was using ROM manager to boot into recovery and BAM!!! phone went completely dead. I had just taken it off the docking station about 15 minutes prior, had a full charge, tried swapping with my original battery, nothing...took it to verizon store, they couldn't do anything and ordered me another phone to come on Tuesday. What do you guys think??? I haven't installed any roms, radio changes, NOTHING!!!... pulled the battery a hundred times, nothing comes on
Dude, first of all, if you mess up your phone by rooting it, DO NOT take it to Verizon. Cardinal rule #1.
Second, a quick view of the threads here and you would have found this:
http://forum.xda-developers.com/showthread.php?t=1279825
Do this and you'll be fine.
Sent from my DROID BIONIC using xda premium
That's the thing
I can't get to fastboot or any boot screen. Phone is completely lifeless, doesn't even show when plugged in, tried multiple chargers, batteries, everything...nothing.
Sorry bro, sounds like a hard brick to me. if you cant power it on and holding VolumeDown+Power or holding both volume buttons+power does nothing at all, you're hard bricked (you cant fix it)
You need to buy a new device. Tell verizon you lost it or somebody stole it or something, but DO NOT take it into verizon.
Happened to me too over the weekend. Was playing Greedy Spiders and the phone froze. Rebooted and got the dual core screen twice then kaput. Tried everything and it won't turn on. Did some research and this isn't a one off problem. Took it VZW and they replaced but I have to wait for it to ship. I love how if you are buying the phone, they have them at the store, if you BOUGHT the phone and need it replaced due to warranty you have to wait.
Of course because they make more money that way
Hey guys..so my moto x gen 2 whent on the blink a month ago the same day google did there ota update..
called motorola and made me go thru tons of combinations to restore it..
it seems like there is a corrupt image..so sent it out for repaire..
telus says that there is a broken chip and charged me 150$...
so refused since the phone is almost new and looking new also..
sent it to a local ubreakifix...they say they scanned the phone has nothing broken at all it is firmware related but only moto can flash it...
so called moto and complained..lol they gave me a pre-paid pkg to there repaire center,,(furture tel)..
got the phone back not repaired saying tampered boot [email protected]#$%%
i know that the web site says the warrantie is voided when boot loader is unlocked..but even the 3 reps from moto and telus never mentioned it...
so long story short it is not repaired and woundering if there a way to recover,flash or what ever..
1-tried the volume up power combos.gets to recover recovers but does not reboot.
2 -went thru all features one by one and still does not reboot...
This is why I don't bother rooting mine. There seems to be too many issues with these phones that you just never know when you'll be required to return them for a warranty repair.
true never again..sticking to my Samsung...i just want to repair it for my son..
As I am visiting my parents, my mother hands me her phone and says turn it on. I did all the normal hold down the power and volume down buttons for 15 secs all the way to 3 minutes, hoping to be greeted with the bootloader screen. I never was.
I have had the phone plugged into various wall chargers, and the phone vibrates every 1 minute i would say. The vibrating was taunting me so i unplugged it, and it still vibrated every minute or so. So i decided to try and charge it form a laptop, vibrating continues. I figured well lets see what happens when i try to boot into the bootloader while plugged into pc. I was surprised to hear that a devices was connected. On PC i entered the fastboot devices command and it is listed as connected (T070600102C). Only device connected so I know it is the moto x. I tried the reboot, and reboot bootloader command hoping to see the screen turn on, it never did. At this point I am stuck.
She said the device was not drained when it happened and was about 60% battery.
It was recently updated to android 5.1.1 a few days ago. The bootloader was never unlocked, nor were any system files tampered with or rooting.
I left the phone stock for her, and got her the dev edition to be able to fix any problems that may arise, but I do not know where to go from here.
I was going to try and flash the factory image but motorola does not have the 5.1.1 system images available for download
EDIT- the vibrating occurs every 40 seconds when not in the bootloader.
I'm wondering if maybe the battery has become defective and iff replacing the battery would solve this issue?
Please any information you can provide will be greatly appreciated.
I should also mention i purchased this device from motorola, on july 22 2014, thus being out of warrenty
I also need to ask this because i can;t remember. This moto X was on 5.1.1 if I attempt to flash the latest image available form motorola (MOTO X, GSM Dev Edition:
L-5.1-LPA23.12-15 (Retail) LMR1) which is older, will there be any problems? I requested the download form moto so it will be awhile before I get it. Just concerned if there are any issues from fastboot recovering from 5.1.1 to 5.1.
I should also note that the phone seems to respond well to fastboot commands. I was able to get OEM unlock data code, and may try to install 5.1
wow nothing?
I would certainly try mfastbooting the latest image. But since it is stock, go ahead and try to see if Motorola will help you. Just because it's out if warranty doesn't mean that they won't help you.
Sent from my Moto X using XDA Free mobile app
moto x 2013 doesnt have 5.1.1. Go ahead and flash 5.1 and you will get it back to life.
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
The title speaks for it self.
At the time of the original problem I was using...
OS: Android N Preview 5 (stock, rooted)
kernel: Elementalx 4.07 (default settings)
My N6 is about a year and a half old. It all started when I was punching an address in to google maps, and the screen goes dark out of the blue. No back light, nothing. Through process of elimination I am able to tell that the phone works, but the screen doesn't. Later on I'm in a phone conversation (was able to call using moto 360) and once the call is disconnected, the screen powers back up. Now everything is fine and dandy for about another week. The other day I am browsing and again out of no where the screen goes dark.
Failed troubleshooting attempts include:
Blindly rebooting into recovery and wiping cache/dalvik
Blindly rebooting into bootloader and re-flashing boot.img
Blindly doing a hard factory reset
Blindly re-flashing 6.0.1 (mob30w) and Elementalx 4.07
Disassembling phone and verifying connections on display assembly
I'm 90% sure I was able to correctly execute all the failed attempts above with a non-working screen - albeit it was not easy.
Any how, I'm still stuck. Someone help me
I have Project Fi so I almost NEED a nexus device. I ordered a 5x, but I'd hopefully like to return my N6 to it's working condition so I can return the 5x to the factory. I really wanted to use that money for one of the new nexuses (nexi?) when they come out in a month or so.
The one thing I stupidly didn't do was call motorola (whom I purchased the phone through) before dis-assembling the phone and I imagine voiding any sort of warranty claim I could take.
nioletmc said:
The title speaks for it self.
At the time of the original problem I was using...
OS: Android N Preview 5 (stock, rooted)
kernel: Elementalx 4.07 (default settings)
My N6 is about a year and a half old. It all started when I was punching an address in to google maps, and the screen goes dark out of the blue. No back light, nothing. Through process of elimination I am able to tell that the phone works, but the screen doesn't. Later on I'm in a phone conversation (was able to call using moto 360) and once the call is disconnected, the screen powers back up. Now everything is fine and dandy for about another week. The other day I am browsing and again out of no where the screen goes dark.
Failed troubleshooting attempts include:
Blindly rebooting into recovery and wiping cache/dalvik
Blindly rebooting into bootloader and re-flashing boot.img
Blindly doing a hard factory reset
Blindly re-flashing 6.0.1 (mob30w) and Elementalx 4.07
Disassembling phone and verifying connections on display assembly
I'm 90% sure I was able to correctly execute all the failed attempts above with a non-working screen - albeit it was not easy.
Any how, I'm still stuck. Someone help me
I have Project Fi so I almost NEED a nexus device. I ordered a 5x, but I'd hopefully like to return my N6 to it's working condition so I can return the 5x to the factory. I really wanted to use that money for one of the new nexuses (nexi?) when they come out in a month or so.
The one thing I stupidly didn't do was call motorola (whom I purchased the phone through) before dis-assembling the phone and I imagine voiding any sort of warranty claim I could take.
Click to expand...
Click to collapse
I have had the same problem quite a few times. I thought it was the layers that i had installed. I eventually had to reboot to recovery, clear cache and dalvik. Then the phone booted in to Android with screen active. I have now disabled my lock screen pattern. Hopefully that stops it.