EDIT: Total NOOB moment here, the phone doesn't come with the battery installed, it's sitting at the bottom of the box under the documentation. I was thrown off by the fact that the bootloader said battery ok.
Just got the Amazon Prime edition Moto G Play (Model XT1607) in the mail today and it's just in a continual boot loop cycle; the Moto splash screen flashes for a few seconds and then reboots. I'm able to get into the bootloader, but any option I select just reboots the device. I assume it's hardware issue because it only even turns on if I have the charger plugged in (although the bootloader screen does say battery is ok), it shuts off immediately after removing the cord (yes, I've let it sit plugged in for a while). Is there anything I can try without being able to get into recovery? I assume I'm out of luck until they post the factory images for this model?
Hahaha it's okay bro, we've all made some kind of noob mistake at some point.
I once spent four hours trying to root a phone, everything went perfectly, I'd reboot the phone and still not have root. Turns out, I didn't realize my GF plugged her phone into the back of my computer to charge and adb was only picking up her phone instead of mine.
Sent from my Moto G Play using XDA Labs
Related
First off, I did search.
Second, My N7 wouldnt wake up today, so I assumed it was dead. I plugged it into the charger, and sure enough, the little charging indicator came on the screen. I gave it 30 mins and tried to fire it up. The Google screen came up, but it never moved past that. I tried force restart multiple times, but it just goes to the Google screen, and if I leave it there the thing gets hot. I tried to go into recovery, but same thing, hangs at Google. I know there is a bug in the bootloader about being plugged in via USB, but my computer doesn't even find it. I deleted the drivers and restarted, searched for new hardware and nothing. Google screen. It is all stock, minus an unlocked bootloader. And I tried two different cables that both work with my MoPho. My concern is that I won't be able to return it if the bootloader is unlocked. Any suggestions?
Thanks in advance.
98snakebite said:
First off, I did search.
Second, My N7 wouldnt wake up today, so I assumed it was dead. I plugged it into the charger, and sure enough, the little charging indicator came on the screen. I gave it 30 mins and tried to fire it up. The Google screen came up, but it never moved past that. I tried force restart multiple times, but it just goes to the Google screen, and if I leave it there the thing gets hot. I tried to go into recovery, but same thing, hangs at Google. I know there is a bug in the bootloader about being plugged in via USB, but my computer doesn't even find it. I deleted the drivers and restarted, searched for new hardware and nothing. Google screen. It is all stock, minus an unlocked bootloader. And I tried two different cables that both work with my MoPho. My concern is that I won't be able to return it if the bootloader is unlocked. Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
You can give it a try to return it. Where did you buy the tablet? If it was a retailer store, just try and return it.
Sent from my Nexus 7 using xda premium
Try this bro http://theunlockr.com/2012/09/25/how-to-unroot-the-nexus-7-tablet/:D
Sent from my Nexus 7 using xda premium
Can you get to fastboot at all? Did you flash anything prior to shutting it down last time?
so i got my nexus 7 back around january and right when i got it i unlocked and rooted it with the tool kit. I was flashing many ROM's and kernals too but im a college student and got busy around march and so i wasnt using it and it was just sitting in my drawer. At the time it was in my drawer i remember it was working and powering on. So last month it came to my mind that i wanted to use the nexus 7 since i have time now. I go and look for it and when i found it and tried to turn it on it just wouldnt turn on.
First i plugged it into the charger with the ORIGINAL cable and plug for the whole day but when i plugged it in the screen started flashing every 3 seconds with a plain white light. So i tried booting into recovery using the power and volume buttons and that didint work. So i searched around the web and found that pulling out the battery and re connecting it works for most people. So i tried that and nothing changed. Right now its sitting plugged into the charger...flashing a white light every 3 seconds. So what else can i try? Idk if i have warranty too so im worried right now. The original owner received it as a gift and he was like 45 years old and didin't have the receipt to return it. My brother knows this guy because hes a regular customer and he bought it off of him and gave it to me knowing i like android devices. So i don't have a receipt for a RMA so idk what to do. Another thing is that the bootloader was unlocked last time i used it.
Please dont ignore this post and give me an opinion on what to do. Recommend me trying to give it to a electronics place to have them look at it and quote me how much would it cost me to get i fixed?
Your battery has discharged too low and your tablet has entered a form of hibernation to prevent it from becoming permanently damaged. Plug it in and hold all three hardware buttons to boot to the bootloader. From there, select power off. You should then be able to charge and use your device normally. These instructions are among the potential steps to take posted in the sticky thread at the top of this forum. http://forum.xda-developers.com/showthread.php?t=2090826
- I saw the Android L dev preview ported over to the nexus 4, so i decided to root my phone.
- Here is what i did at first I downloaded an app and did a one click root it did work but being a novice I also wanted to have a custom recovery without any hassle.
- So I downloaded Wugs Nexus root toolkit and firstly I undid the previous root, then using this program I re-rooted and installed a custom recovery.
- I went on to install "L-Mako-b5-bunny-stew-and-kool-aid.zip" at first my playstore wouldn't work and I was getting a persistent error (error 920) so I reinstalled the rom and it started working.
- So here I am thinking I'm done and there aren't any other problems left to fix.
- Last night I went to sleep while my phone battery was at 3%, I think it fully drained and now it won't boot or even charge. Have I hard bricked my phone and what can I do to fix this?
thanks, please help me!
Edit: I've also charged the phone for
- 1 hour
-Over night
- There is no response while charging, holding power, holding power & vol down, connecting to computer gives nothing
I might have messed up big time?
mufc786 said:
- I saw the Android L dev preview ported over to the nexus 4, so i decided to root my phone.
- Here is what i did at first I downloaded an app and did a one click root it did work but being a novice I also wanted to have a custom recovery without any hassle.
- So I downloaded Wugs Nexus root toolkit and firstly I undid the previous root, then using this program I re-rooted and installed a custom recovery.
- I went on to install "L-Mako-b5-bunny-stew-and-kool-aid.zip" at first my playstore wouldn't work and I was getting a persistent error (error 920) so I reinstalled the rom and it started working.
- So here I am thinking I'm done and there aren't any other problems left to fix.
- Last night I went to sleep while my phone battery was at 3%, I think it fully drained and now it won't boot or even charge. Have I hard bricked my phone and what can I do to fix this?
thanks, please help me!
Edit: I've also charged the phone for
- 1 hour
-Over night
- There is no response while charging, holding power, holding power & vol down, connecting to computer gives nothing
I might have messed up big time?
Click to expand...
Click to collapse
1. Hold power+both volume buttons, while charging, for 10 seconds.
2. Try using a different charger.
3. Go to a gsm service...
abaaaabbbb63 said:
1. Hold power+both volume buttons, while charging, for 10 seconds.
2. Try using a different charger.
3. Go to a gsm service...
Click to expand...
Click to collapse
I bought it 2nd hand from Cex (second hand retailer in UK). Luckily I still had 2 months of warranty left so they've taken it in for repairs. I don't know if they'll find out it's hard bricked (if it is), or not.
Unfortunately happened to me, too, yesterday, while rebooted my Nexus 4. It doesn't boot. The LED blink once, red, and nothing. The worst thing is it's the Service page from LG Romania website "is not available". Now I'm digging the web to find a solution
okay guys screw CeX (second hand UK retailer with 1 year warranty on ALL electronics). I took my supposed dead nexus 4 to them and the guy took it in for repairs (I'm 2 months from the end of my warranty). So they take it in and I go in 2 weeks later as they haven't updated me on the progress.
Get into the store and the guy pulls my phone out. He says because it has a crack on the back they can't book it in for repairs. I ask him why did they take it in if it wasn't going to be booked in, his reply, well its obvious no one would fix a phone with a crack in it! This guy was the goddamn manager.
So since about 2/3 weeks my phone's been dead I haven't touched it. I'll try again tomorrow but hopefully it will start working. Wish me luck.
And is it possible to hardbrick a phone because its battery dies out AND the ROM/Bootloader can't allow the device to charge?
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
That's a tough one. Usually with a soft brick, if you can make it to recovery, your phone can be saved but since you can't... I hope you get it working!
Sent from my SPH-L720 using XDA Free mobile app
puresublimie said:
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
Click to expand...
Click to collapse
Go to sprint galaxy s4 thread. All answers there. You need Odin 3.09 then stock ng2 tar. To flash through computer.
Sent from my SPH-L720 using XDA Free mobile app
I already have odin and the tar files for stock. When plugged into my computer it will not even register that it is connected and so I can't use odin to flash it.
The same thing is happening to me. I get to the Galaxy S4 splash screen, then it shuts off. Even if I try to boot into recovery
I'm going to pile on in here as I seem to be having a similar issue. I had my S4 (not rooted, stock rom) on my dock streaming google music. A phone call came in and the phone started vibrating like crazy and wouldn't stop. The screen shut off and the phone was still vibrating. Finally it stopped and was shut off. When I try to start it a few things happens. It will sometimes boot to my lock screen and the screen goes black and I think it is powered off. Sometimes it will get past the lock screen and then die shortly after. After like 2 or 3 times of that it won't even boot. It loads the Samsung screen but never gets to the Sprint screen or boots. If I leave it for some time shut off with battery out it will go back to booting to the lock screen then dying etc... When I press the buttons to get into recovery it says recovery is loading and then the screen goes black. I swapped batteries and that didn't do anything. I tried pressing the menu button or the home button to try and boot safe mode and it just loads normally not that I think that would help anyway.
Any ideas on things I can try next? What is this odin thing? Would that work for me?
---------- Post added at 07:09 PM ---------- Previous post was at 06:16 PM ----------
Ok... I can get into recovery now and will try a factory reset. Are you sure you are going into recovery correctly. Apparently I was not. Hold volume up power and menu button and when the phone vibrates let go of power only.
Before I do a hard wipe is there any way to get data off the internal memory from recovery mode?
So I got a custom recovery installed, reinstalled stock rom, things worked ok for awhile. Then it started random reboots every 10 mins or so. Now it is back to instant crashing and rebooting. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?
So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.
So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=
Hello there!
I recently got my hands on stock Moto G4 from my cousin. The thing is, he fell with it on his pocket and now when you try to power it on it show the Motorola logo screen briefly, turns off, then turns on again and shows the logo screen again and so on. The phone charges up normally, enter fastboot mode just fine (although I can't enter recovery, only little droid with exclamation mark, but maybe it's because it's locked).
I searched throughout the xda forums and google for solutions and tried everything that looked like it could work. Nothing did. I tried the following:
1 - Change the battery;
2- Install another stock rom via fastboot and adb;
About the phone state: the display is just fine. The only things that were damaged with the fall were a part of the back that was a little kneaded, a little below of the sim slot. As I disassembled the phone I noted that the metal shield in that place of the motherboard was a little bit kneaded too.
I am afraid it might be more of a hardware issue, but if you guys could give me some light or some other ideas, it would be really appreciated.
Thanks!