Database Info

Help

i have an htc sensation 4g t-mobile was running Android_Revolution_HD-Sensation_1.2.2_T-Mobile and was working fine i thought to change to viperS rom had low battery rom was flashed successfully it was on boot when the battery went dead luckly i had an external charger charged the battery overnight to make sure the battery show 4.2volts now but the mobile is not working when i power it on it just vibrates and flashes green light once and black screen nothing else and when i try to go to boot loader it turns on with some texture on screen + it is detected by pc as an MTP device unluckly i dont have another battery to check it with it

abbas93 said:
i have an htc sensation 4g t-mobile was running Android_Revolution_HD-Sensation_1.2.2_T-Mobile and was working fine i thought to change to viperS rom had low battery rom was flashed successfully it was on boot when the battery went dead luckly i had an external charger charged the battery overnight to make sure the battery show 4.2volts now but the mobile is not working when i power it on it just vibrates and flashes green light once and black screen nothing else and when i try to go to boot loader it turns on with some texture on screen + it is detected by pc as an MTP device unluckly i dont have another battery to check it with it
Click to expand...
Click to collapse
Basically when power runs out or there is disconnection for any reason when flashing or in the process of booting up, you will have bootloader crash, which will lead to what you are experiencing, that's why its important to have a fully charged battery when flashing . you need to go here to locate the files needed to recover your phone. Mind you you may have to locate T mobile ROM's as your phone may be network locked.
or use ADB or a reboot tool to get your phone into download mode
your forum is here
Check this out! You , YES! you are an " Android ". Not your phone but U.​

What do i have to do form these things ?
Regards

abbas93 said:
What do i have to do form these things ?
Regards
Click to expand...
Click to collapse
you should post in that forum and read the link about flashing the ROM again to solve it or if you had a Backup, restore it. , unfortunately I have no experience concerning HTC phones.
Check this out! You , YES! you are an " Android ". Not your phone but U.​

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

Weird sudden death

Hi all.
I have searched this forum (I know it's very frowned upon to start a thread without doing so) but the symptoms don't completely match my issue so I've resorted to asking.
I have a Nexus 5, which I was using as a hotspot, tethering to an Amazon fire stick, when it switched itself off.
It hasn't booted since, I've tried all possible button combinations for up to 2 minutes and still nothing.
If connected to a charger I get the white battery icon with the lightning bolt for a few seconds then blank screen, this will loop until unplugged.
When I have the battery icon on screen I can hold power button and it will display "Google" and vibrate as if starting to boot, then go blank again.
Have reinstalled original battery and the symptoms remain the same.
Am on marshmallow 6.0.1 totally stock am also out of warranty.
Any ideas would be greatly appreciated.
Thanks in advance.

Try to boot in bootloader mode if it boots connect to it comp and then unlock the bootloader if not and install latest Twrp if not then flash a custom rom and boot it then flash factory images .. Done. Back to Stock!
Try booting in bootloader mod while connecting it do the charger. (Wall charger )

pranavmali said:
Try to boot in bootloader mode if it boots connect to it comp and then unlock the bootloader if not and install latest Twrp if not then flash a custom rom and boot it then flash factory images .. Done. Back to Stock!
Try booting in bootloader mod while connecting it do the charger. (Wall charger )
Click to expand...
Click to collapse
Thanks for the suggestion but can't get into bootloader mode, it's only alive for about 3-4 seconds if plugged in then it goes off and then back to the white battery.

J_The_Nerd said:
Thanks for the suggestion but can't get into bootloader mode, it's only alive for about 3-4 seconds if plugged in then it goes off and then back to the white battery.
Click to expand...
Click to collapse
Mother board problem or change try changing ur battery... Surely Mother Board problem! Coz while u were connected to a hotspot and then u switched off it.. The battery would suddenly undervolt ur motherboard... And Undervolting id Very Very bad even if u change it from software or hardware...This had happen to my Sis nexus 5. .. So given it a chance changing the battery! Coz that helped Me.. But also try booting in bootloader mod and flashing twrp it will save couple of Bucks and Time
Press the thanks button if this helps

I would replace the battery first. It seems like the battery was completely drained while hotspotting.
Are you using the original USB cable and charger that came with the phone?

audit13 said:
I would replace the battery first. It seems like the battery was completely drained while hotspotting.
Are you using the original USB cable and charger that came with the phone?
Click to expand...
Click to collapse
Yes using the original charger, still does the same on power bank and old Samsung charger.
I'll give a battery swap another go.

pranavmali said:
Mother board problem or change try changing ur battery... Surely Mother Board problem! Coz while u were connected to a hotspot and then u switched off it.. The battery would suddenly undervolt ur motherboard... And Undervolting id Very Very bad even if u change it from software or hardware...This had happen to my Sis nexus 5. .. So given it a chance changing the battery! Coz that helped Me.. But also try booting in bootloader mod and flashing twrp it will save couple of Bucks and Time
Press the thanks button if this helps
Click to expand...
Click to collapse
If battery swap doesn't help is the motherboard easy to swap out? Providing I can find a replacement?

Motherboard is very easy to swap out.

Update, put original battery back in for the second time, first time didn't make a difference, possibly took longer this time. But all is good now.
Thanks to all

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

boot loop

Hello guys
my xiaomi got boot loop when i unlocked bootloader, and i have dm-verity corruption
HELP PLS
and when i trying to load to recovery phone is turning off

fafra228 said:
Hello guys
my xiaomi got boot loop when i unlocked bootloader, and i have dm-verity corruption
HELP PLS
and when i trying to load to recovery phone is turning off
Click to expand...
Click to collapse
Did u at least unlocked the bootloader? If yes, try to boot to fastboot and flash your phone rom.

Rares6567 said:
Did u at least unlocked the bootloader? If yes, try to boot to fastboot and flash your phone rom.
Click to expand...
Click to collapse
if not there is still hope for redmi 9a since there are ways to apparently bypass locked bootloader, just dont give up.

Ivan.Adriazola said:
if not there is still hope for redmi 9a since there are ways to apparently bypass locked bootloader, just dont give up.
Click to expand...
Click to collapse
Yea. If you can't unlock bootloader you can use Sp Flash Tool

Hey guys, anyone can help me please?!!!
I had an unsuccessful flash on my redmi 9a, now i can’t connect my phone to pc for start MTK bypass for flashing new rom, every time i connect, just turning on and shows redmi logo and next battery. Buttons aren’t working too.

amrrahimi.ar said:
Hey guys, anyone can help me please?!!!
I had an unsuccessful flash on my redmi 9a, now i can’t connect my phone to pc for start MTK bypass for flashing new rom, every time i connect, just turning on and shows redmi logo and next battery. Buttons aren’t working too.
Click to expand...
Click to collapse
Try disconnecting the battery and connect it again.

Rares6567 said:
Try disconnecting the battery and connect it again.
Click to expand...
Click to collapse
I did it, again same problem

amrrahimi.ar said:
I did it, again same problem
Click to expand...
Click to collapse
Buttons doesn't work? Let the phone reboot again and again to drain the battery. After that charge it. ( Idk what's the problem sry.)

Rares6567 said:
Buttons doesn't work? Let the phone reboot again and again to drain the battery. After that charge it. ( Idk what's the problem sry.)
Click to expand...
Click to collapse
It wouldn’t drain the battery because every time it starts charging and every time i connect, i see the capacity is more and more.

amrrahimi.ar said:
It wouldn’t drain the battery because every time it starts charging and every time i connect, i see the capacity is more and more.
Click to expand...
Click to collapse
Can you tell me step by step how do you get your device bricked?

Rares6567 said:
Can you tell me step by step how do you get your device bricked?
Click to expand...
Click to collapse
When i bought this phone officially it had russia rom, it worked too slow because of so many unusable apps, i flashed a china rom and it worked very good but i can’t install google play on him, i decided to flash global rom and again i flashed russian flash not specially. I flashed global rom and phone bricked.now when i connect USB for use bypass phone just turning on and shows redmi logo and then battery capacity and then screen off and no one buttons aren’t work.

I think u flashed something wrong and that's why the buttons aren't working?

Try flashing with sp flash tool without bypass tool.
Try kurdish sp flash tool too.

Rares6567 said:
Try flashing with sp flash tool without bypass tool.
Try kurdish sp flash tool too.
Click to expand...
Click to collapse
I tried this too, nothing.
Is there any way to flash without battery?!

amrrahimi.ar said:
I tried this too, nothing.
Is there any way to flash without battery?!
Click to expand...
Click to collapse
Hmmm. I don't think so because the phone can't boot without battery?

My phone did absolutely nothing, not even unrecognized by computer, it didnt even show up as something, IIRC the device manager gave me error 44, I gues you can try what I did.
Leave your phone charging for a while with the battery connected, at least an hour, but I did it a full night, then get some toilet paper and wire tape, wrap one or two turns of tp around the phone and butons (just so it doesnt get stained with the wire tape glue, you can skip this if you dont care, but its easy enough and its a lot easier), then over that tightly wrap wire tape so that the on/off button and the vol- buttons are pressed, leave it alone for a while, after like 5 hours I recall the phone started vibrating every 10 minutes or so, after that the phone was unrecognized by the pc, but no longer as error 44, this allowed me to flash.
after succesfully flashing the battery behaved weirdly for one charge cycle and then fixxed itself, it discharged about 50 % of the battery in around 5 minutes or less, like 3 minutes from 40 to 50, and the rest was discharging faster and faster, after fully charging it went back to normal, my guess is there was an issue where the phone did not actually know how much charge it had, wich screwed with it somehow.

Ivan.Adriazola said:
My phone did absolutely nothing, not even unrecognized by computer, it didnt even show up as something, IIRC the device manager gave me error 44, I gues you can try what I did.
Leave your phone charging for a while with the battery connected, at least an hour, but I did it a full night, then get some toilet paper and wire tape, wrap one or two turns of tp around the phone and butons (just so it doesnt get stained with the wire tape glue, you can skip this if you dont care, but its easy enough and its a lot easier), then over that tightly wrap wire tape so that the on/off button and the vol- buttons are pressed, leave it alone for a while, after like 5 hours I recall the phone started vibrating every 10 minutes or so, after that the phone was unrecognized by the pc, but no longer as error 44, this allowed me to flash.
after succesfully flashing the battery behaved weirdly for one charge cycle and then fixxed itself, it discharged about 50 % of the battery in around 5 minutes or less, like 3 minutes from 40 to 50, and the rest was discharging faster and faster, after fully charging it went back to normal, my guess is there was an issue where the phone did not actually know how much charge it had, wich screwed with it somehow.
Click to expand...
Click to collapse
Isn't it easier to just disconnect the battery?

Rares6567 said:
Isn't it easier to just disconnect the battery?
Click to expand...
Click to collapse
didnt want to take out the screen

Ivan.Adriazola said:
didnt want to take out the screen
Click to expand...
Click to collapse
The screen?? Wdym, take out the back....

amrrahimi.ar said:
Hey guys, anyone can help me please?!!!
I had an unsuccessful flash on my redmi 9a, now i can’t connect my phone to pc for start MTK bypass for flashing new rom, every time i connect, just turning on and shows redmi logo and next battery. Buttons aren’t working too.
Click to expand...
Click to collapse
Flash the phone in BROM mode with proper flash file for your device.