Database Info

AT&T Fuze stuck in endless reboot loop

Well after searching and not finding anyone with the same problem I am having I decided to share. Last night after changing the battery in my Fuze the device got stuck in a power cycle loop. Startup splash screen for about 30 seconds and then reboot. I thought maybe SD card (throwback to the old days when SDHC could screw up the device), no luck. I read a thread where a dead battery was causing a similar behavior so I tested the battery and it was full (also tried two other batteries just in case), again no dice. Tried hard reset, and the device let me perform the hard reset fine but when it completed and I "Press Vol Up to boot" the cycle started again. At this point, my ideas were exhausted. I put the phone in BL mode and flashed stock ROM and SPL so I can return it. My only thought is that the power button on top of the device is stuck somehow and that is causing the phone to turn off and on constantly.
Anyway, AT&T customer (lack of) service can't get me refurb replacement for 2 days (and they are charging me the shipping on that). What a PITA!
Sorry to be so long winded. Anyone got any ideas on what might have happened so I can avoid it with the replacement? I was using Energy 2.0 v3/15/09 at the time of problem although I'm pretty sure the ROM had nothing to do with problem (it had been stable and fast for 3 weeks before the problem occurred).
Thanks

http://forum.xda-developers.com/showthread.php?t=501470
That came up when I did a raphael search for Boot Loop .... looks like a similar issue.

[Q] XT925 hard bricked - battery failure during factory reset. Halp

Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?

metal man007 said:
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
Click to expand...
Click to collapse
SOLUTION:
Turns out my phone was stuck in a "boot loop"
Followed Champdood's instructions:
http://forum.xda-developers.com/showthread.php?t=2144101
Thanks everyone.

Random restarts

Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks

OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?

Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?

Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?

So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?

I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.

TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor

I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app

TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.

harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...

Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.

Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.

I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.

Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/

Stuck in a bootloop, but I didn't do anything to my phone

Hello, Nexus 5 forums. This is my first post on here, because I never even tried to root or install a custom ROM on my Nexus 5, having bought it for the official updates from Google and all that stuff (I had a Galaxy SII before this phone, and I frequently visited the XdaDev GSII forums because I installed CyanoGenMod on it).
I'll go straight to the point. My phone suddenly started rebooting randomly today, and by the end of the day it was stuck in a weird kind of bootloop. The Google logo would pop up, and right as the MM boot animation started the phone would reboot and the Google logo would show up. Right now, the phone's battery is probably dry, so that's why the phone isn't bootlooping, but it has done so for 3-4 hours before shutting down. I tried opening the phone, removing the battery and putting it back in, but the phone just kept bootlooping. I tried both getting into the stock recovery and into download mode, but the phone keeps on rebooting as soon as I get into download mode.
Can I do anything to fix this or is my phone doomed to the eternal bootloop?
Thanks in advance for any and all replies.

Sounds like there may be a problem with the power button.

Same thing happened to me like 5 times now. It is the power button. What I do is knock it on the side of a table below the power button. I just need it to last until the new nexus is released, so I never investigated the proper fix.

I understand, so my problem is more a hardware than a software issue. I tried knocking the phone on the side of a table like @NicksSpleen said, but maybe my problem is more serious. What can I do to fix this? I need it to last until Christmas, as I'm going to get a new phone then (maybe the Nexus Sailfish, if the price is acceptable).

EDIT: Double post.

I disassembled my phone and fixed the problem by cleaning the power button. Works like a charm. Thanks for all your suggestions!

Anything other than the power button?

Poco X3 NFC - Can't access bootloader, fastboot or system (bootloop)

Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])

Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.

Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway

Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...

Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.

CaptainFedora, did you solve the problem? I have the same issue...

Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.

Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.