About 9 months ago, I bricked my Blaze, and after giving up, I've been using a new phone in the interim.
Here's what happened:
Battery dies while flashing some rom, get boot loop, fix by flashing stock rom etc.
Flash Kit Kat Rom, phone immediately shuts off when unplugged, works fine plugged in.
Flash stock ROM, infinite boot loop, can get in the CWM recovery, but flashing stock rom, etc. dont stop boot loop
boot loop description : SGSB4G T-Mobile 4G Green Android Rocket Animation --> Glowing Samsung Logo ---> Repeat
I've tried numerous solutions since then but none have worked.
Please help. Winner gets $5.00 paypal bc this is literally the only problem I've never solved.
Your battery is probably bad, replace it and you won't have a problem.
Sent from my XT1045
Somcom3X said:
Your battery is probably bad, replace it and you won't have a problem.
Sent from my XT1045
Click to expand...
Click to collapse
I will see if I can try out a new battery at the store and test the results.
I have been skeptical as to whether the battery was the issue, as the boot loop animation would still work when it was unplugged.
Thanks for the response!
Related
Hey all , Look I've been looking around the forums looking and following solutions..
At first my P500 started to get no service.
Than the phone got really hot, Than left it on charge over-night because the battery was draining heaps !
(Found out the battery went dead. got a new battery etc)
Woke up , and my phone was repeatedly displaying the "LG" logo.
It'll idle on that for about 3 seconds, than restart and it'd come up again.
I cannot access recovery mode or any other mode, BUT only emergency mode.
I flashed the 10A firmware on my p500 , worked fine, than installed Facebook, Than it turned off again and is currently doing the same "LG LOGO"
thing.
I have tried and tried repeatedly to reflash the firmware again (USING KDZ)
Is there any hope i can get my phone up and running? thanks guys.
LayALAD said:
Hey all , Look I've been looking around the forums looking and following solutions..
At first my P500 started to get no service.
Than the phone got really hot, Than left it on charge over-night because the battery was draining heaps !
(Found out the battery went dead. got a new battery etc)
Woke up , and my phone was repeatedly displaying the "LG" logo.
It'll idle on that for about 3 seconds, than restart and it'd come up again.
I cannot access recovery mode or any other mode, BUT only emergency mode.
I flashed the 10A firmware on my p500 , worked fine, than installed Facebook, Than it turned off again and is currently doing the same "LG LOGO"
thing.
I have tried and tried repeatedly to reflash the firmware again (USING KDZ)
Is there any hope i can get my phone up and running? thanks guys.
Click to expand...
Click to collapse
Using KDZ is dangerous. Word of advice: NEVER EVER INTERRUPT THE FLASH OR TAJE OUT THE BATTERY. Use lgdmp if you have to reflash.
Sent from my LG-P690 using xda premium
Will i be able to flash it using "emergency mode" ?
edit: Flashed, But still constant "lg logo"
Nevermind that, Checked the ERASE EFS ALL Option, Phone is now charging and past the Lg logo !
But restarts sometimes, and constantly has the lg logo when i remove the usb cable.
LayALAD said:
Nevermind that, Checked the ERASE EFS ALL Option, Phone is now charging and past the Lg logo !
But restarts sometimes, and constantly has the lg logo when i remove the usb cable.
Click to expand...
Click to collapse
Are you able to boot your phone into system? Which ROM, kernel and baseband you are using?
rishabhgangwar said:
Are you able to boot your phone into system? Which ROM, kernel and baseband you are using?
Click to expand...
Click to collapse
The phone will not turn on without it plugged into power.
I turn on wifi.. Instant turn off.
I cannot get past the android logo now, leaving it on to charge over-night (charges fine)
It aint the battery (got 2)
The android sound plays than turns off,
Anything i should do before the next step?
I flashed the stock virgin mobile australia v20E firmware.
Kernel is 2.6.35.10-perf (managed to reflash it to boot it up again)
/bump.
Hi, my Nexus 5 was just powered off as i clicked the power button to browse the web. I tried to boot it but it just went to multiboot and restarted after 2 seconds.
It kept restarting like it was bricked but shut off after a few times. Then i booted into bootloader but the screen went off after 2 secs. I removed the battery and put it on the charger but it just boot loops the google logo.
I am on Xtrasmooth v9.0 if you want to know but i dont think that this has any importance since my phone doesnt stay in the bootloader which has nothing to do with my rom (i think):good:
But maybe it has to do with multiboot? I have to say that my phone kept randomly restarting over the last week.
AkaHantz said:
Hi, my Nexus 5 was just powered off as i clicked the power button to browse the web. I tried to boot it but it just went to multiboot and restarted after 2 seconds.
It kept restarting like it was bricked but shut off after a few times. Then i booted into bootloader but the screen went off after 2 secs. I removed the battery and put it on the charger but it just boot loops the google logo.
I am on Xtrasmooth v9.0 if you want to know but i dont think that this has any importance since my phone doesnt stay in the bootloader which has nothing to do with my rom (i think):good:
But maybe it has to do with multiboot? I have to say that my phone kept randomly restarting over the last week.
Click to expand...
Click to collapse
Have you tried restoring to 100% stock with a factory image?
_MetalHead_ said:
Have you tried restoring to 100% stock with a factory image?
Click to expand...
Click to collapse
Heya, I found out that my power button was broken so i had to remove it from the board and started the device with a screw driver :victory:
This is me story, flashed a OTA to my cel and all the sudden my phone reboots loads up to the Oneplus logo and then nothing... Boot loop, so trying not to worry that much, noticed I could still boot to fastboot, I tried flashing CM11 praying that would get my phone back... Boot loop, Flashed CM12 and I got a low battery message boot loop, then going back to fastboot just got me a qualcomm brick, used the Color Os fix... Yay no more qualcomm brick but phone stuck on red icon, does someone have a clue what happened to my phone or if I would ever get it back to normal? :crying:
How long did you let the phone sit for (wait) and you assume it's stuck? As I know if you use the Qualcomm downloader will flash back to ColorOS and it will wipe everything automatically and your phone should be able to boot normally.(Last time when I revive my OPO if I remember correctly it will show the red 1+ logo for at least 30-45 sec.
It just sits there waited for a couple minutes, all the flashing goes ok, even with CM12S the flasing seems to be good, but it just boot loops, and the other thing when I flash a recovery it does flash it, but I cant make it boot to recovery what so ever... I just hope and pray there is a way to recover my phone since it would be a shame if someone told me, you have to buy a new motherboard... hopefully someone would just say replace the battery XD, because when I flash CM12s it does say the battery is too low to power and it keeps power cycling
Hi everyone. My Nexus 5 was running good until some days ago. Then it started bootlooping. It wasn't turning on , so I unlocked the bootloader and flashed the stock image. Nothing happened,so I flashed stock KitKat rom and after 2-3 hours it booted and lasted 30 minutes. I mean, after thirty minutes, it stucked to Google screen again. Then I somehow managed to flash lineage 14 and it booted again successfully.But as you all know that GOD Hates me a lot, after 2-3 hours it started the same drama again. And that's the story, I tried lineage,RR,aokp ... everything flashed successfully but doesn't last more than 4-5 hours or even less.But If I try stock, that never boots.
I just can't understand where is the problem.The power button is ok, I installed a kernel and underclocked it to see if there is problem with processor. No luck. This thing can boot ,but can't hold on that very long.
Another thing,when it start looping, it forget about TWRP too. I have to flash stock first,then install TWRP,then lineage /RR.
Can anybody say where is the problem??
I have used some nokias, samsung, even some Chinese phones,none of my phones died themselves, it was my only Google/LG and I faced this.
If the phone boots on a stock 4.4.2 room but gets stuck on the boot animation with a 5 or 6 stock ROM, the internal memory chip is probably failing or will fall.
audit13 said:
If the phone boots on a stock 4.4.2 room but gets stuck on the boot animation with a 5 or 6 stock ROM, the internal memory chip is probably failing or will fall.
Click to expand...
Click to collapse
What can I do?? Is it recoverable with pertitioning softwares or I should think about buying a grave plot for it?
Anyway,thanks a lot, man. You are the only one who atleast tried to help me.
Hello!
I recently flashed my Moto G with the unofficial LineageOS 16 rom by allstargaurav. Kudos to him for his work.
I unlocked my bootloader, got TWRP, flashed the rom, flashed Gapps,Magisk and started using it normally.
One night, after using it with the battery at 30%, I left it as it was and did not charge it.
The next day, I saw that it was not booting up at all. I plugged it in and the white led light started and did not go off.
The light was constantly on. I searched on google to no avail.
Nothing works and I have pressed the power button and power+volume down for more than 5 minutes.
I cant get to the fastboot menu or the TWRP, the phone doesnt power on at all so I cant do anything or get a logcat.
Please help!!!!
I also got the watchdogs boot animation. That is all I have modified.
Please tell me what is wrong and how to rectify it.
Please help quickly.
I am at wit's end and helpless. I should also mention that this was my first time flashing a rom on any device, but I followed the instructions very carefully.Before this the phone was on stock Lollipop rom, stock recovery and locked bootloader.
Thanking anyone who helps or even replies in advance.
:crying::crying::crying::fingers-crossed::fingers-crossed:
Also
Alphacube111 said:
Hello!
I recently flashed my Moto G with the unofficial LineageOS 16 rom by allstargaurav. Kudos to him for his work.
I unlocked my bootloader, got TWRP, flashed the rom, flashed Gapps,Magisk and started using it normally.
One night, after using it with the battery at 30%, I left it as it was and did not charge it.
The next day, I saw that it was not booting up at all. I plugged it in and the white led light started and did not go off.
The light was constantly on. I searched on google to no avail.
Nothing works and I have pressed the power button and power+volume down for more than 5 minutes.
I cant get to the fastboot menu or the TWRP, the phone doesnt power on at all so I cant do anything or get a logcat.
Please help!!!!
I also got the watchdogs boot animation. That is all I have modified.
Please tell me what is wrong and how to rectify it.
Please help quickly.
I am at wit's end and helpless. I should also mention that this was my first time flashing a rom on any device, but I followed the instructions very carefully.Before this the phone was on stock Lollipop rom, stock recovery and locked bootloader.
Thanking anyone who helps or even replies in advance.
:crying::crying::crying::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Being unsure what the problem is, I also followed FabioSan's guide on unbricking the phone, but I got stuck on the part where we go to the device manager console as my PC would not recognise the phone no matter what I did.
Also, the warranty has expired long ago as the phone was bought in 2014 and it was only a 1year warranty.
Therefore, I am considering giving the phone to the moto support centre. I will also try replacing the battery as it may be a battery problem considering my symptom of the white light does not fit any hardbricked phone's symptoms. Will notify if it works.
Till then, please help and suggest what the problem might be.