Database Users

reboot loop

sometimes when i soft reset my mogul it goes into a sort of reboot loop, it will reset before loading the today screen
i have an app that lets me boot into a "safe mode" with all today plugins, autorun items and nonessential services disabled, however this too reboots (it resets before even loading the today screen, it resets at the wm6 splash screen)
any ideas? i suspect its some app i have installed, just seems weird that it would happen before anything else loads

When this happens, simply remove the SD card and the loop will stop.
Also, it seems that this has stopped if you have the most current ROM.

heh, i never even thought about pulling the SD card *kicks self*
ive been hesitent to get the latest rom because i dont want to reinstall all my apps and tweaks again, especially when i know ill have to do it for rev.A anyway, lol
thanks for the help, nice to see another chicagoan here (im in the south subs)

Did you recently install the HTC audio manager and/or the HTC Home?

Those programs aren't really the cause...there have been reports of users who don't have them installed that had the reboot loop anyways. I have actually had the reboot loop after a hard reset with no installed programs and reg tweaks...

ScottC said:
Did you recently install the HTC audio manager and/or the HTC Home?
Click to expand...
Click to collapse
no and no
havent had the problem again yet, so i havent been able to try the SD thing, but it makes sense since its happenening before autorun apps and services load

jamesus said:
Those programs aren't really the cause...
Click to expand...
Click to collapse
I didn't say they were the cause, I was just trying to run past some programs that are known to cause these symptoms.
To flatout say that they are not the cause is just wrong. There is a combination of HTC home and the Audio manager that'll force the unit into a reboot loop you can't get out of.

So no one has found a cause for this? How would this even be feasible if you have startup programs installed on the SD card? I also wanted to put all mail downloads and attachments on the SD, but if I have to pull it out, WM6 creates a Storage Card folder and my actual SD becomes Storage Card 2. It's a pain to have to delete and rename and such especially considering how often the device has to be reset...

Althought the cause is not exactly known, it has been speculated to be a ROM issue. Since flashing to the latest ROM, I have not one reboot loop, and this has been for a few months now.

Those experiencing this, what ROM version do you have?

sbddude said:
Those experiencing this, what ROM version do you have?
Click to expand...
Click to collapse
This was present in the 2.08 ROM and was fixed with the 2.09 ROM.

I installed the latest DCD rom no programs installed and it just keeps on looping sometimes it stops for a hr or two and than starts looping again

I tried re-installing the original sprint rom but the same thing keeps on hapening

Are you running Spb Pocket Plus? There are known issues by the developers regarding memory, battery, power meters in the Pocket Plus Today Plugin. For more info, go to Spb Club:
http://www.spbclub.com/forum/index.php

I tried everything, I put back the original Sprint rom didn't help. I went back to sprint they tried, coudlln't fix it, I got a new Phone out of the box.
They still have radio 1.32 and Rom 2.09 the blutooth works excellent on this.

I've had to return 2 phones in the last 2 months. My first phone would just freeze up for no reason. I could use the phone for a couple of hours then it freezed. Well the couple of hours soon became a few minutes than only for about a minute. If I took the battery out for awhile then I could turn it on again for a few minutes. It was as if the battery or cpu was getting hot and then freezing up.
The next phone worked good for 2 days and then all of a sudden it just died at the sprint logo. It boots up and shows the rom version with the sprint logo than the rom text disappears and its stuck at the sprint logo. It won't boot any further. It will stay on the sprint logo and the backlight will even go off after a few minutes. Strange... I am about to take this phone back tomorrow.
So far I've had nothing but bad experience with the durability of these phones. Once I get it set up properly it dies... :-(

i got a mogul aswell, nvr happened to me sorry can't help..

I just installed DCD2.3.2-Telus (several times) along with Titan_Radio_3.27.0. At first it worked wonderfully. The second I install anything to do with the GPS though, the system goes into a reboot loop. Actually it even started doing it last night without installing any navigation software.
- Google Maps
- TomTom 6
- Live Search
^^ Those are the 3 I've tried so far and all three have lead into reboot loops. I just flash the ROM again and everything is okay (for a while).
I've also tried running dcd_titan_2.1.0_telus and got the same problem once I installed one of the above Apps.
Does WM6 create dump files like in Windows so I can figure out what the hell is causing this? I want my GPS to work!!!!
After the reboot loops start, I tried removing the SD card as mentionned but it did nothing. Keep in mind I installed the programs to my internal memory.
Update: After flashing the ROM again to 2.3.2, the second I insert my SD card that also triggers the reboot loop.
Update #2: With the stock Rom, it seems to be working fine again. I think it's a problem with the GPS chip itself?

After spending the last few days trying to figure this out, I said the heck with it and contacted HTC to see what they have to say. Will post their reply once I get it. Hopefully there is a fix, because I hate this!! Now, I can't set my Spb Backup to run on auto, otherwise I wake up to the splash screen again....and again.....and again! I get so angry as I wait anxiuosly to see the result, today screen or verizon, and then *buzz*, I'm going crazy!

I had the same problem as you with my XV-6800 using the stock ROM and it always would go into reboot mode unless I ejected the sd card first. I could only put the card back in after it booted up. I also removed two programs from the device's main memory (Microsoft Voice Command 1.6 and a task switcher).
I'm currently running SPB mobile shell and SPB Pocket Plus (for the task manager) and it's working fine now.
The only thing I can suggest is to remove one program at a time and reboot to see if maybe there is software conflict

SKTools Bricked My Phone

ran the freeRAM service that comes with sktools, and the phone froze. No biggy, so first instinct was to let it sit, which i did let it do. After a few minutes i soft reset the phone and it just hung at the htc mobile splash screen. I tried several times to soft reset, but nothing was working. I was in the end forced to hard reset and loose all my data.
Any1 know what the heck happened?

Ummm...if you were able to hard reset and get the phone to come back, it's not bricked.
Title is a little misleading, don't you think???

I have been running SKTools on my WM devices for 4 years now and have never encountered such a conflict. It is possible that as FreeRam attempted to close dormant program(s) that the program(s) themselves reached conflict and therefore froze your device.
In my experience with SKTools, it has flawlessly maintained my device and I have found that 95% of the time that the conflict resides within apps/programs not playing well with each other. Have you recently installed apps/programs?

Continuous looping rebooting

I am about to got nuts. Though I love my HD2, it has this one bug that is driving me cracy:
Sometimes, when it crashes and I remove the battery or push the little red "Reset" button in the back, the phone goes into an endless restart or reboot cycle. It will power up, go through the start up procedure until it is time for "Sense" to start and then just turn itself off and start the whole reboot procedure over. There is nothing I can do to stop this, except remove the battery - if I were to let it continue, it would keep rebooting itself all day long or until the battery is dead.
Does anybody have a suggestion as to what may be causing this problem?
P.S.: Up to now, the only thing I can do to stop this cycle, is to do a Hard Reset and reinstall everything.
(Still on the 1.43 ROM, since T-Mobile in Germany has not supplied the update to 1.48)

Looks like HTC Tech-Support has no clue and recommends returning the phone for service.

Are there any programs in your Windows/startup folder?

I've had a similar problem a long time ago with my previous HTC Phone (a wizard WM5) the phone was not faulty, it was one of the programs I had installed, so after a Hard reset everything wa fine until I installed again the program (sorry, I forgot what it was) and at the next soft reset...It took me a long time to find it out, since I tend to have a list of favorite programs which I install first thing after each hard reset.

If you do a hard reset but don't install any software, does it still happen?
I only ask as it may be some software that's installed on the phone that is causing the problem, rather than a fault with the phone itself.

Thanks everyone
I do not really know if it does the same thing without software, but it does come at different times. The last time it happened for example, I had just selected a new ringtone from the pre-installed ones and hit "Accept". Prior to that time I was installing .net 3.5 when it crashed and started looping, prior to that I was playing the pre-installed Teeter game.

lrsthmp said:
I do not really know if it does the same thing without software, but it does come at different times. The last time it happened for example, I had just selected a new ringtone from the pre-installed ones and hit "Accept". Prior to that time I was installing .net 3.5 when it crashed and started looping, prior to that I was playing the pre-installed Teeter game.
Click to expand...
Click to collapse
If it's that random, I'd recommend getting in touch with the manufacturer and arranging a replacement.
Must be damn annoying

reboot cycle - same problem on my HD2
Hello lrsthmp
I have the same problem with my HD2.
Did you find a solution?
Do you have any advice?
Thanks
best wishes Uli

Regrettfully...
... no. I am living with it and have become very religious about backing up. "MyPhone" from Microsoft has become a very important tool for me as a result, because I am having to reinstall quite often.

I had the same thing happen to me after the system froze and I pulled the battery, here is what I found.
There are 3 power pins and during the battery pull and put back in I must have slightly bent one of the pins out of position. I gently put it in line with the other pins, put the battery back in and it started right up.
Careful pulling that battery, it sucks that we even have to do this.

mmc_read failure Note 4 n910w8 Rogers!!

Here is the story,
I flashed Marshmallow on my note 4 n910w8 via odin (I had 5.1.1). After it was done I noticed that the phone got laggy and warm. It would sometimes not boot/restart or it would shut down after it freezes for sometime. I would get the download page with mmc_read failure in red, I would pull out the battery and try again.
What I did:
*Unrooted the phone through SuperSu and flashed Twrp throughout (because it gave other errors and I had to do it again and again after each attempt)
*I tried flashing through twrp but I got the "no md5" error
*Flashed the stock ROM 6.0.1 with PIT since it gave the PIT error on odin
*Wiped cache/data/factory reset multiple times.
*I used both Kies and Smartswitch and was not successful (either read or write failure)
*Flashed the stock 4.4.1 (the original, It could not boot up once) so I returned to the stock 6.0.1
*The phone boots up 3 out 5 times and I was able to watch a full movie on Netflix and browse the web and google maps. But as soon as I locked it, It shut off and did not power up (until i took out the battery and let it cool down).
Where I went:
*A Samsung repair agent here in Montreal said that most of the time it is the Mob and that it would cost 300-400$ CAD to replace
*I went to other repair shops, a few hinted that it might just a matter of reprogramming the Mob and that it involved a risk of bricking the phone for good.
N.B: It is not under warranty and I'm not on contract, It is my own phone.
My question(s): Is there something else I could try? Is there someone who fixed the issued (Assuming it is not hardware) maybe and unbrick fix or something? And also, it there anyway to thoroughly wipe out the old installations so I could start anew?
Also I consider myself pretty knowledgeable. Or I at least learn quick. Do not hesitate to suggest something coarse for me to try. Worse comes to worse, Ill sell it on eBay for part, since it it in mint condition.

It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.

The Sponge said:
It's definitely a hardware issue, trust me.
But all the problems can be bypassed by rooting your device and installing Wake Lock app from the playstore and activate PARTIAL_WAKE_LOCK, enable the notification and start on boot. This will fix all the lag and the crashes.
This will not, however, fix the boot problems. So if your device ever runs out of battery or turns off, booting it is gonna be a hassle still as before. If you ever get stuck trying to boot it properly to homescreen however, I discovered a foolproof method for that with 10/10 success rate.
I know it might sound weird, but I'm seriously not trolling you. Take out the battery and place the phone & the battery in your fridge for at least 5 minutes until your device gets cold. Put the battery back in and boot into 'download mode'. You'll notice that it'll goes into download mode perfectly. Take out the battery again and just boot normally. You'll be back into homescreen in no time. This is how I know it's a hardware problem, lol.
With these alternative fixes, I'm hoping that I can keep my phone alive for at least another 2 years. Better than forking out another $500~ for a new device imho.
Click to expand...
Click to collapse
Thank you very much for your reply, I take it you have the same problem? I will try Wake Lock. And also I'm way ahead of you in the freezing game. Leave for 10mins in the freezer and you can basically flash anything. Also, do you a custom ROM would help?

Droid turbo 2 stuck in boot loop

I bought a droid turbo 2 about a year ago, and after a few months of use it was dropped into a sink causing minor water damage. Other than minor screen bleed everything seemed to have been in working order after a few days of drying.
About a week and a half after it finished drying and was in use, the phone shut down and went into a boot loop. It will boot to the motorola M but after 30 seconds it shuts down and restarts.
I have tried doing a verizon update from my computer but after the program says "updated" my phone is unable to restart dissallowing the update. I do have the ability to boot the phone in "fast boot" or "recovery mode", But if i go into recovery mode and do a factory reset the problem persists through it.
I figured the best way to try and fix my phone would be to flash a factory android version onto the phone, but that is where i am running into issues. Maybe it is my lack of understanding of ADB and flashing, but i dont understand how i am supposed to allow debugging on my phone if it is already stuck in a boot loop? I also am running into the issue of my phone not being recognized by the ADB daemon. even though the verizon updater recognizes it and allows for an update. Please any help from somebody with experience with these sorts of things would be extremely appreciated.

Bootloop after disconnecting charger, tried everything
I am having same problem after disconnecting charger from phone, went into bootloop. Did you ever fix yours?
Same problem, different reason.
Goes to Motorola logo and restarts until battery dead. I have flashed up-to-date stock ROM both with "Verizon Software upgrade" program with windows 10(once) and 7(several times), and have flashed with old "RSD lite" in win 7. Both flashing methods worked flawlessly and says "successful". but still looping. Have tried draining battery to totally dead and full recharge, no joy. Can boot into recovery fine. Did full factory resets, etc. Thought battery may be problem, but battery lasted full day or more before needing recharge before problem, and drains normally now with constant restarts, but gets hot. (plugging in to check % charge after restarts says still in 90+% range after many restarts).
I know this is an old thread, but any suggestions are appreciated. Cant understand if flashes good, why cant restart.

Old thread, old problem -- my problem, as well. (In my case it's a hand-me-down phone for experimentation; all my own androids are rooted starting with my first.)
This 'Droid Turb'o 2' worked fine until left alone a while, after which time its battery then seemed to lose its "elasticity" as it were, resulting in poor charging/capacity characteristics, and then shortly thereafter, this annoying and horrid bootloop. (It's also a Verizon phone, they like to "tighten-up" the phones they sell to one, or so I have read.)
All I have to offer really, are my observations, and possibly some insight. My suspicions of something to do with the current flow/battery-drain are also pure conjecture, and perhaps an educated guess at best. I, too, continue to solve this mystery because it's somewhat atypical of my own android experiences, and this is the sort of knowledge that broadens the spectra of engineering as a whole (and the suspense sometimes can give one a hell of a headache).
For now, my conclusion is that this appears to be a problem specific to a particular model that is no longer made, and perhaps for good reason. I still hope to find this mystery solved some day.
73 DE N6BHU