Database Info

Moto G XT1033 won't connect to PC, charge or boot :(

Hi!
I had installed cyannogenmod 12.1 on my device and it worked, then I went on to install another kernel eXPerience and that made my wifi and usb port on the phone to stop working. It only connects via fastboot but I can't get it to charge. (Tried the reboot loop thing, it just depletes the battery.) If I do get it to charge, I could reflash a working recovery, format cyannogen and use it to push a backup i made on my PC via bluetooth (ADB doesn't work.) Solutions?

If it connects in bootloader mode then I think your phone should be charging simultaneously
If not try using different charger or cable.

Paradox♀ said:
If it connects in bootloader mode then I think your phone should be charging simultaneously
If not try using different charger or cable.
Click to expand...
Click to collapse
Tried, it doesn't, powers off and won't boot afterwards (Only tried this with 2 cables, but somehow the battery magically gains a small amount of charge the next day.

RayonDeLumiere said:
Tried, it doesn't, powers off and won't boot afterwards (Only tried this with 2 cables, but somehow the battery magically gains a small amount of charge the next day.
Click to expand...
Click to collapse
So it seems either the battery is not working properly or the charging pin I is damaged recommend you to go to the mobile repairing shops.

RayonDeLumiere said:
Tried, it doesn't, powers off and won't boot afterwards (Only tried this with 2 cables, but somehow the battery magically gains a small amount of charge the next day.
Click to expand...
Click to collapse
Try charging via wall socket.

Paradox♀ said:
So it seems either the battery is not working properly or the charging pin I is damaged recommend you to go to the mobile repairing shops.
Click to expand...
Click to collapse
It's cause I changed the kernel I think, I believe the hardware's fine
lost101 Yea I tried that too - in 2 whole days it got a small amount of charge enough to boot into fastboot but shuts off if I load the OS or recovery.

RayonDeLumiere said:
lost101 Yea I tried that too - in 2 whole days it got a small amount of charge enough to boot into fastboot but shuts off if I load the OS or recovery.
Click to expand...
Click to collapse
The phone will charge if left on the fastboot screen.

lost101 said:
The phone will charge if left on the fastboot screen.
Click to expand...
Click to collapse
Tried that yesterday, completely lost charge and now it won't boot to fastboot either

It could be the kernel, drivers, rom. Go back to stock rom, do a total wipe.

gabriel96torres said:
It could be the kernel, drivers, rom. Go back to stock rom, do a total wipe.
Click to expand...
Click to collapse
I would if it charged! At this state, the battery's too low for me to flash anything.

Yoou didn t do backup before? How many % are left? There is enougth to flash another kernel?

144556 said:
Yoou didn t do backup before? How many % are left? There is enougth to flash another kernel?
Click to expand...
Click to collapse
Did, but it's on my PC, and I can't transfer it(except via bluetooth, which will take really long). Battery's at 0% now so no.

I ve read that for someone work to turning it on in boot mode then plugging into computer

Moto E is stuck in boot loops. Please help.

Hi,
I own a Motorola Moto E XT1022 (1st gen), which I bought from Flipkart India.
It came with KitKat 4.4.4, and I had put a soak test version of android L 5.0.2 , officially released by Motorola in May or something.
It worked fine until December 2015- then it started having issues. It would lock its screen automatically. When pressed the power button, it will show the screen that was on before locking. When touched, it will make me type the password. After typing it, it would work fine. Same thing would happen after 30 min. But that was not a big issue.
3-4 days after facing this issue, it restarted automatically. And it stuck on the Motorola M logo.
I shut it down, tried starting it again. No luck. One time, it started. I immediately performed a factory reset by going in settings. At that time, the soft keys (back, home and recent apps) didnt appear on the screen. That was strange. After factory reset, it restarted itself. Started working normally, all clean phone. (Still on 5.0.2 soak test obviously) But it didnt show the soft keys as I said before.
Then it restarted, again. And since then it is stuck in boot loops. I stormed the internet, and found how to factory reset using recovery, wipe data, even flash stock OS 4.4.4 from official Motorola website. I have done all that. I have-
1) Factory reseted using hard reset method
2) Wiped Cache partition
3) Flashed stock firmware from official website (KitKat 4.4.4)
It is still stuck in boot loops. It shows the M logo at startup, and stays like that forever. Only shuts down when all battery is drained. Now it is not charging either. It is stuck at 0%. But I think charging issue will be fixed by charging it for some hours.
Now, the phone is running stock OS, is completely cleaned, and is stuck in boot loops.
I cannot afford to buy another phone. When I asked Motorola for help using the Chat function of the Help app, they suggested me showing it to the closest service centre. I showed it to them but they were giving excuses that they will see if they can do...and didnt do anything. (PS I'm from India, and it is like this for most of the service centres here.)
So please, can anyone, please please please help me?
All the help is appreciated. Thank you!
PS. I have tried hard reset and wiping cache partition over 8 times now. It's still not working. Please suggest some other method if possible.

I guess it is because of the faulty soak test ROM.. Would you be interested in rooting? I guess flashing a different stable ROM would help.. Even a factory image..

WickedCool19 said:
I guess it is because of the faulty soak test ROM.. Would you be interested in rooting? I guess flashing a different stable ROM would help.. Even a factory image..
Click to expand...
Click to collapse
Sir,
I am ready to do anything to make it work. If rooting is the solution, or maybe flashing a different OS, or both, I am ready to do anything.
Please tell me what should I do next.
Thank you for your valuable reply!

Alright .. First of all, can you access your phone right now? I mean, does it actually boot up?
Hit thanks if I helped!

WickedCool19 said:
Alright .. First of all, can you access your phone right now? I mean, does it actually boot up?
Click to expand...
Click to collapse
Here is the current state of my phone-
It is completely out of charge.
When I charge it, after about ten minutes or so, it shows a symbol of pulling the wire out of the socket.
First time when I saw this, I switched off charging and pulled it off. Then the phone shut down as it had no charge.
Second time when I saw this symbol, I kept it charging. After 30 minutes, it showed the battery charging symbol, with 0%.
And I forgot to mention one thing. When I plugged in the charger and started charging the phone, the LED notification light glowed and it stayed on. No idea why. After some time, it stopped glowing. Battery showed 0% even after charging for about an hour. ( Note- LED notification light glowed up and went out randomly.)
( Then I got depressed and stopped charging the phone. Then it switched off as it didnt have any charge.)
Now, I think charging it for a long time will make it start again.
But I think I will get into boot loops after I start the phone. And it will stay like that until the battery is drained out completely.
Thank you!
PS. Should I start charging it right now? Its 12 midnight here, maybe I should keep it overnight. (Is it safe? The battery won't explode or anything right? Sorry I'm a little paranoid, since my uncle's micromax phone burst while charging.)

Same time zone
Now look this happens in my moto e too.. There was an issue with my power button, it restarted when ever i unlocked or locked my device.. I rooted, flashed a kernel which supports gesture wake and now i use the button rarely..
Now coming to ur problem, don't charge it overnight, might harm the battery at the most.. Charge it for an hour.. And try to boot the device up.. Only then, can i help you out..

WickedCool19 said:
Alright .. First of all, can you access your phone right now? I mean, does it actually boot up?
Hit thanks if I helped!
Click to expand...
Click to collapse
Its midnight. I have to sleep. But I will reply to your posts as soon as I wake up.
(Just telling this in case if you wonder why am I not replying. I actually have to log off now. I will reply tomorrow. Please do not close this thread. Thanks and sorry too. Good night from India! I appreciate your help!)

WickedCool19 said:
Same time zone
Now look this happens in my moto e too.. There was an issue with my power button, it restarted when ever i unlocked or locked my device.. I rooted, flashed a kernel which supports gesture wake and now i use the button rarely..
Now coming to ur problem, don't charge it overnight, might harm the battery at the most.. Charge it for an hour.. And try to boot the device up.. Only then, can i help you out..
Click to expand...
Click to collapse
Ok, I will charge it when I wake up tomorrow. It might not get enough charge in 1 hour, so I may have to charge it for 2-4 hours to start it. Thank you for your kind help! We will talk tomorrow. Good night!

PhantomCode31 said:
Ok, I will charge it when I wake up tomorrow. It might not get enough charge in 1 hour, so I may have to charge it for 2-4 hours to start it. Thank you for your kind help! We will talk tomorrow. Good night!
Click to expand...
Click to collapse
Charge it.. One hour just might do it..
What ever you do.. Just try to boot it up or else i might not be able to help you..
Cheers..

How can root

WickedCool19 said:
Charge it.. One hour just might do it..
What ever you do.. Just try to boot it up or else i might not be able to help you..
Cheers..
Click to expand...
Click to collapse
Hi.
I have started charging the phone just now. Let's see how much it charges after an hour.
Right now its LED Notification light is blinking randomly, and battery charging 0% symbol is showing up on start screen.
The screen wakes up and sleeps randomly. Lets see what happens.

WickedCool19 said:
Charge it.. One hour just might do it..
What ever you do.. Just try to boot it up or else i might not be able to help you..
Cheers..
Click to expand...
Click to collapse
Hi,
I have charged the phone for about an hour. Its still charging.
It now shows the recovery menu, giving me options such as
Normal Powerup
Recovery
Factory etc.
And under all the options, this is what I see-
hab check failed to boot
failed to validate boot image
Fastboot Reason: Fall-through from not-charger boot
ode
What do I do now? I tried Normal Powerup, it showed M logo and showed the above screen again.
PLEASE REPLY URGENTLY. Thanks

<<UPDATE>>
Phone is charging. About 28% battery right now and still charging normally.
Now should I try starting it? Please reply.

Yes.. Try starting it. Or else nothing can be done..

WickedCool19 said:
Yes.. Try starting it. Or else nothing can be done..
Click to expand...
Click to collapse
When I start it, its no longer in a boot loop.
It shows Motorola M logo for a second and automatically opens recovery mode.
there I get this message at the bottom (in pink or some color like that)
hab check failed for boot
failed to validate boot image
(in yellow/green color) Fastboot Reason: Fall-through from normal boot mode

A question.. Had u enabled usb debugging from dev settings by any chance?

WickedCool19 said:
A question.. Had u enabled usb debugging from dev settings by any chance?
Click to expand...
Click to collapse
When this issue started, I had soak test android L 5.0.2, and yes I had enabled USB Debugging from it.
But, after the issue, I flashed stock rom 4.4.4 on it. But I havent been able to access the phone normally since that. So I had it enabled in 5.0.2, but now it has 4.4.4, which I never operated.
Hope I didnt confuse.

PhantomCode31 said:
When this issue started, I had soak test android L 5.0.2, and yes I had enabled USB Debugging from it.
But, after the issue, I flashed stock rom 4.4.4 on it. But I havent been able to access the phone normally since that. So I had it enabled in 5.0.2, but now it has 4.4.4, which I never operated.
Hope I didnt confuse.
Click to expand...
Click to collapse
How did u flash? Using recovery?

WickedCool19 said:
How did u flash? Using recovery?
Click to expand...
Click to collapse
I shut down the phone.
Connected to laptop.
Hold down the power and volume key.
Factory Reseted using recovery menu.
I had official kitkat 4.4.4 ROM in laptop.
I flashed it using command prompt.
Now im sure it has kitkat, the word "Android" at boot animation has changed, like it did on kitkat.
So I'm sure it has KitKat.
<<UPDATE>>
Phone is not stuck in boot loops anymore.
It switches off, I can stop the draining of the battery.
When I turn it on, it shows motorola M logo for 1 second.
Then it takes me automatically to recovery mode. And gives the hab error as I mentioned above.

So you do know how to flash using ADB...
---------- Post added at 03:52 PM ---------- Previous post was at 03:45 PM ----------
Then just get on with it..
Here's a link of cm 12.1.. Download a zip and flash using ADB (as you did from Command prompt for kitkat)
---------- Post added at 03:55 PM ---------- Previous post was at 03:52 PM ----------
http://download.cyanogenmod.org/?device=condor

My Mi4c only works when charging

After my phone bricked I installed latest Chinese Stable ROM in EDL mode. I chose EDL mode for two reasons (1. I suspected that the phone only works while plugged in to charge and 2. the EDL mode turns off the phone after flashing so I can plug in the charger before booting). Turns out I was right. After the flash was over I tried to boot it without charging it first and it didn't work. After I connected it to the charger it booted normally and the ROM installed successfully.
I tried it again this morning after it fully charged. Few seconds after Ii disconnected it, it turned off. When I tried to turn it back on it was just rebooting to the MI logo screen. I plugged it in the charger and it rebooted 2 times (both times it got to those three dots at the bottom of the screen) and the third time it booted normally.
I also just noticed that the phone is curved a bit (maybe less than 1mm difference between upper left edge and rest of them), maybe from wearing it in tight pockets or something like that.

I think your battery might be dead. Try checking the voltage or the quality.
Replaceable batteries are pretty cheap.
Trimis de pe al meu Mi-4c folosind Tapatalk

Might be faulty battery, might be bad kernel, might be anything. Best way to check is to try to flash latest dev china rom via fastboot, if it still doesn't work try flashing stable 5.1.1 rom, again, via fastboot. If none of the solutions above doesnt work might be bad battery or worse, the controller on mobo died.

timipisoboy said:
Might be faulty battery, might be bad kernel, might be anything. Best way to check is to try to flash latest dev china rom via fastboot, if it still doesn't work try flashing stable 5.1.1 rom, again, via fastboot. If none of the solutions above doesnt work might be bad battery or worse, the controller on mobo died.
Click to expand...
Click to collapse
Well I hope it's a battery, because I just bought one to replace it. What is that mobo controller? Is it replaceable?

I have the same issue,
Battery replacement and stock rom of android 7 didn't help
I'm afraid is another hardware issue /:

I do have a similar problem, flashed xiaomi.eu and something have been broken.
I dont know how and why but its very strange.
Unplugged from supply i can boot up the phone, can see the miui logo and boot into fastboot but NOT into recovery and not boot up os.
As soon as i plug in supply it works quit normally, can boot up everything seems to be working, booting into twrp and flashing rom. No problem at all.
If i unplug while running os it imediately shut down.
The battery bar inside twrp show strange jumps.
What happens did somehting break ? Id like to gift the phone my mother for christmas.

Danny94 said:
I do have a similar problem, flashed xiaomi.eu and something have been broken.
I dont know how and why but its very strange.
Unplugged from supply i can boot up the phone, can see the miui logo and boot into fastboot but NOT into recovery and not boot up os.
As soon as i plug in supply it works quit normally, can boot up everything seems to be working, booting into twrp and flashing rom. No problem at all.
If i unplug while running os it imediately shut down.
The battery bar inside twrp show strange jumps.
What happens did somehting break ? Id like to gift the phone my mother for christmas.
Click to expand...
Click to collapse
Hi how did you resolved this. Facing same problem. Will replacing battery solve this.

visharagp said:
Hi how did you resolved this. Facing same problem. Will replacing battery solve this.
Click to expand...
Click to collapse
I purchased a new battery and it was working normally again and still working.

Danny94 said:
I purchased a new battery and it was working normally again and still working.
Click to expand...
Click to collapse
Great then I have to purchase a new battery ss well

S7 Exynox charging problem when OFF

Hi,
already searched and found that I am not alone, but a solution I did not find so far.
I Flashed the Oreo Lineage 15.1 via TWRP.
Before flashing, I did not change anything else, the bootloader is factory-versioni, which probably is from Nougat OS.. So this might be the cause..
Anyway, when plugging the charger when phone is off, I got the battery-symbol with a "flash" sign. If I disconnect, it remains as-is. Have to force reboot by holding the buttons 8 seconds.
Charges normally if kernel is running..
Any idea?
Please help.
Thanks
Joe

joe535 said:
Hi,
already searched and found that I am not alone, but a solution I did not find so far.
I Flashed the Oreo Lineage 15.1 via TWRP.
Before flashing, I did not change anything else, the bootloader is factory-versioni, which probably is from Nougat OS.. So this might be the cause..
Anyway, when plugging the charger when phone is off, I got the battery-symbol with a "flash" sign. If I disconnect, it remains as-is. Have to force reboot by holding the buttons 8 seconds.
Charges normally if kernel is running..
Any idea?
Please help.
Thanks
Joe
Click to expand...
Click to collapse
My old s4 did this on occasion. I think the fix was to let it charge fully, reboot with usb attached, then pull cord. Next charge power off before connecting usb and should charge normally. One other time I think I had to fix via external SD format then full wipe and reflash rom but that was for force closes I think. Sorry was so long ago now hard to remember!
Sent from my SM-G930W8 using Tapatalk

joe535 said:
Hi,
already searched and found that I am not alone, but a solution I did not find so far.
I Flashed the Oreo Lineage 15.1 via TWRP.
Before flashing, I did not change anything else, the bootloader is factory-versioni, which probably is from Nougat OS.. So this might be the cause..
Anyway, when plugging the charger when phone is off, I got the battery-symbol with a "flash" sign. If I disconnect, it remains as-is. Have to force reboot by holding the buttons 8 seconds.
Charges normally if kernel is running..
Any idea?
Please help.
Thanks
Joe
Click to expand...
Click to collapse
AOSP ROMs for S7 are bugged and not ready for daily usage in my opinion. Better try stock based ROM like Helios (excellent battery life) or SuperMan (tons of useful tweaks and mods - ROM I personally use and recommend)

If you still want to stay on AOSP download latest build of LOS 15.1 3.3.2018 from changelog: "Fixed charging with device powered off"

OnePlus one only showing OnePlus logo and turning off

My OnePlus one is only showing OnePlus logo screen and turning off, I flashed stock ROM through my computer as I thought it got soft bricked, nothing worked, when I connect it to the battery charger it shows battery charging, I guess there's some hardware problem, any suggestions will be helpful, thank you

Samruddhi123 said:
My OnePlus one is only showing OnePlus logo screen and turning off, I flashed stock ROM through my computer as I thought it got soft bricked, nothing worked, when I connect it to the battery charger it shows battery charging, I guess there's some hardware problem, any suggestions will be helpful, thank you
Click to expand...
Click to collapse
option 1 : Do a complete wipe in TWRP (system,data,cache,dalvik) and then flash the stock rom again.
option 2: use the "back to stock/restore soft bricked device" option on bacon root toolkit using your pc
If this dosen't work only then it could be a possible hardware issue.

i have the same problem, but it survived with a simple things.
Fully charged your phone,try installing twrp (i think the newest one) and try to full wipe data,and installing new rom.
I installed lineage os 14.1 everything work.
And if it still bootloop,try to replacement the battery, and fully charged. Then try flash twrp and new rom.
good luck

malcolmm21 said:
option 1 : Do a complete wipe in TWRP (system,data,cache,dalvik) and then flash the stock rom again.
option 2: use the "back to stock/restore soft bricked device" option on bacon root toolkit using your pc
If this dosen't work only then it could be a possible hardware issue.
Click to expand...
Click to collapse
I tried installing ROM through TWRP but when I used to start the installation the process used to suddenly stop and the device used to boot for no reason, and now it is not showing any recovery, I flashed stock recovery still nothing

bedgja said:
i have the same problem, but it survived with a simple things.
Fully charged your phone,try installing twrp (i think the newest one) and try to full wipe data,and installing new rom.
I installed lineage os 14.1 everything work.
And if it still bootloop,try to replacement the battery, and fully charged. Then try flash twrp and new rom.
good luck
Click to expand...
Click to collapse
Tried everything what you said except replacing the battery, it still shows OnePlus logo and turns off, guess the problem is with the hardware (battery or motherboard)

Samruddhi123 said:
Tried everything what you said except replacing the battery, it still shows OnePlus logo and turns off, guess the problem is with the hardware (battery or motherboard)
Click to expand...
Click to collapse
try to replacing the battery, cause many thread said the oneplus one always bootloop and back to normal when it charged or in power bank. i have tried and yup...replacement the battery is simple ways to check there is no problem with the board.
good luck