Related
Hello. First and foremost i am noob, but i fee like i've given this site a fair scrub for my situation and i haven't found anyone in a similar situation. I have an htc thunderbolt, I am not sure about any of the software versions, but i am on verizons network. I recently rooted my phone. The rooting process went fine. I then went on to install the latest version of liquid thunderbolt using rom manager. The install seemed to go fine. IT go to the point where a graphic loaded on the screen. I think its the liquid thunderbolt loading graphic. It's like this vortex-like thing with a bunch of lightening in the middle and then a water drop surrounded by lightening. Either way it's been stuck on this screen for the past 4 hours. What should i do? Is my phone what htey call bricked? If so can i recover from it? Should i just yank out the batter?! PLEASE HELP!
What you are describing is happening to me right now as well. Have you found out any new information. btw My tb has been rooted for 4 months with no troubles. last night i put clockwork mod/rom manager on it went through the process step by step then selected a new rom I think it was from liquid thunder. Now no mater what i do the phone boots up to the htc screen and then to rotating screens just like you described. that's it nothing else. it will not power off without to pulling the battery. i have pulled the sd card. it will not boot into hboot. press down vol. then the power.
thanks,
Jarrad
Hi, this is Jarrad's wife and I have fixed his phone. I was asleep last night when he did this to his phone and he has been up all night working on it. He even went as far as to make me breakfast in bed in order to soften the blow I guess with regard to the information he was about to tell me about his brand new very expensive phone, since he knew it would piss me off. So anyway he had the phone off for about an hour and a half on the charger and stopped messing with it. After he told me his story of what he did to the phone I decided to take a look at it. He told me that when you go into recovery you push and hold the power button and the volume down button at the same time but, this is not true or at least its not what I did to get him to the recovery screen. I was going to turn it on but, forgot he said it had a problem, so after holding down the power button ALONE for about 5 seconds I then pushed the volume down button and held them both together and boom the recovery screen came up. Now it was not a fluke because he then used the wrong recovery option and locked it up again. So, again a pressed the power button ALONE for about 5 seconds and then added the pressing of the volume down control button and boom back to the recovery screen. I hope this works for you the way it worked for me. Good Luck.
Jarrad's Wife Liz
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.
Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.
I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.
In my mind, this validates my decision to go over to the CM11 nightlies and never look back.
Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.
I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk
It isn't necessary to hold both volume keys, just volume up and power.
Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.
andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.
This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.
This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app
Sounds like SOD.
Changing the thread around to reflect the current situation, new text at the bottom of the post.
While out to dinner with my family an hour or so ago, my phone suddenly stopped working. I had been checking some emails when the food arrived, so I pressed the power button to shut down the screen and set the phone to the side. About 30 minutes later, I tried to open my phone to continue where I had left off, only I got no response at all from the device. I immediately tried the normal troubleshooting actions (holding power button for 30+ seconds and attempting to go into recovery mode), but still got no response from the phone. I have since tried charging it at home with it's original quick charger, but even after 15 minutes on the charger, there isn't even a red light indicating it is charging. Is there anything that I can try to fix this on my own, or is it likely that I've got some technical fault that only Verizon can deal with?
Thanks.
PS: I'm 100% sure that no liquid came in contact with my phone during dinner. Even if I wasn't so sure, both the phone and case have been bone dry through the entire ordeal.
New situation:
The "techs" at Verizon were less than useless... While there, they tried fewer fixes than I was able to attempt before telling me that the only option they could offer is to replace the phone. The problem, as I've said a little lower in this thread, is that I've got some irreplaceable photos of my recently deceased cat of 19 years stuck on the phone that I never got the chance to back up before this event.
And so now I need options. I'm willing to do pretty much anything, up to and including tearing the phone apart to manually access the memory unit, but the end result absolutely has to be those photos recovered.
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
DroidXrei said:
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
Click to expand...
Click to collapse
I've tried soft reset (hold power only), hard reset, and recovery, all to no avail, and holding each for long after it's supposed to respond (at least 60 seconds).
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Theodric58 said:
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Click to expand...
Click to collapse
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
treblesum81 said:
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
Click to expand...
Click to collapse
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Theodric58 said:
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Click to expand...
Click to collapse
All of this was done before taking it to Verizon. All key combinations were tried unplugged then plugged into 3 different chargers and also my computer with 3 different cables and several different USB ports. When I went to Verizon, they tried the key combinations unplugged and then tried plugging it in and seeing if it would take a charge... hence the assertion that they tried less than I was able to attempt at home.
Time to find someone who can repair the phone locally. Any type of warranty or factory repair will cost you the pictures.
Sounds like it's safe to say the phone is beyond simple trouble-shooting. I found myself in a similar predicament last year when I busted the screen on my S4. I dropped my phone on some concrete steps and the screen (in addition to being shattered) went completely black, but I knew the phone was still working because I could still hear the person I was taking to on the phone lol.
I ended up replacing the phone through Verizon. They referred me to some third party company that agreed to replace the phone for $100 and sent me a replacement with a box to put the busted one in. At this point I found myself presented with a unique opportunity, given the fact that I had both a working S4 and my broken one.
Because I didn't have the chance to back up the phone before I lost access to it (it's pretty hard to unlock a phone without the screen) I looked up a guide on how to disassemble the S4 on YouTube in order to gain access to the motherboard. The whole process was relatively easy to carry out and I was able to disassemble both phones, switch the motherboards, backup the information I needed, and switch them back.
Sorry for the long-winded response. I realize this is a pretty drastic measure to take and that you may not have access to a second S6. It's also entirely possible that the motherboard on your phone is part of the problem so switching it wouldn't help much in that case (like I said, I knew my phone was still working despite the screen). Just wanted to offer another option =).
I am in a similar predicament, desperate to get my photos and videos back and have been watching your thread for some ideas. My 7 week old Verizon Samsung Galaxy S6 G920VVRU4BOG9, android version 5.1.1. ceased to do anything on Monday for reasons unknown. It is now back on but it has been wiped clean. I had to do a hard reset. Samsung & VZW tech support were not helpful. May I ask what model your phone is? Provided you are able to get yours back on, I'm wondering if you may have some success with some of the following:
Wondershare Dr Fone for Android
Asoftech Data Recovery
Kvisoft Data Recovery
Ease US data recovery.
I could not get them to work because you must first have a rooted phone to retrieve them and mine apparently can't be rooted. I apologize if this is redundant but I thought I'd throw that out there in case you might have a change of recovering those photos. I'm sorry for your loss. It's very hard to lose a beloved pet.
First thing this morning, my Note 5 was working fine. Used the navigation to get to the house I was working at today, as well as simultaneously using Autoguard dash cam app. I got to the job, exited the navigation and Autoguard, got out of my van, holstered the phone.
About 15 minutes later, I try to use my phone to take some pictures, but nothing would happen. Black screen. Couldn't restart by holding the power button. Tried getting into both recovery and download modes. Plugged in the phone to see if it would charge. I was getting absolutely nothing. It was like my device had just up and died. I just kept wondering, could the board have been fried or maybe the battery shorted?
I was dreading the thought of seeing if warranty would cover the device, even after having it for only 5 months. I've been screwed before by the insurance and warranty service on other phones. Making me pay the deductible for a new device, and them claiming that there was water damage, showing me the "damage", when it's obviously a fried board and the moisture sticker isn't activated.
But anyway, lunch time rolls around. I go sit in my van, start pressing the buttons again. Still no restart, still no recovery, but then I try download mode, and viola. Device got into download mode. I canceled out, and the device rebooted normally. I was at 100% power when I got to the job site, and after roughly 4 hours later of it being unresponsive brought it down to 60%.
My mind was put at ease. Charged up normally afterward. The rest of the afternoon there were no more hiccups. Has anyone else ever had something like this happen?
needmymorningcoffee said:
First thing this morning, my Note 5 was working fine. Used the navigation to get to the house I was working at today, as well as simultaneously using Autoguard dash cam app. I got to the job, exited the navigation and Autoguard, got out of my van, holstered the phone.
About 15 minutes later, I try to use my phone to take some pictures, but nothing would happen. Black screen. Couldn't restart by holding the power button. Tried getting into both recovery and download modes. Plugged in the phone to see if it would charge. I was getting absolutely nothing. It was like my device had just up and died. I just kept wondering, could the board have been fried or maybe the battery shorted?
I was dreading the thought of seeing if warranty would cover the device, even after having it for only 5 months. I've been screwed before by the insurance and warranty service on other phones. Making me pay the deductible for a new device, and them claiming that there was water damage, showing me the "damage", when it's obviously a fried board and the moisture sticker isn't activated.
But anyway, lunch time rolls around. I go sit in my van, start pressing the buttons again. Still no restart, still no recovery, but then I try download mode, and viola. Device got into download mode. I canceled out, and the device rebooted normally. I was at 100% power when I got to the job site, and after roughly 4 hours later of it being unresponsive brought it down to 60%.
My mind was put at ease. Charged up normally afterward. The rest of the afternoon there were no more hiccups. Has anyone else ever had something like this happen?
Click to expand...
Click to collapse
Yup, has something similar happen to mine. Locked up just like yours while it was in my pocket. No response to anything, even plugging it in to the charger. Just had to hold volume down + power. This is a soft reset and is like a battery pull. Try it out if you have this problem again.
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
thomasanderson said:
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Plug it into your computer (you'll notice that there will be a longer black screen in-between the bootloops) and hold down the power button for at least 10 seconds or more, then release it after the next vibration and the white BLU screen shows up. It might take a couple of tries.
If you manage to boot into at least recovery but can't boot into the system, then try clearing your cache/dalvik cache and try rebooting into system again.
If all of the above doesn't work for you, then your boot.img/system has gone bad, and you'll have to flash the stock images with SP Flash Tool (both of which can be found on other posts on this forum).
follow the instructions on the SP flash tool thread... sounds like what happened to me after bad flash... theres a lot of information in that thread that will set you up...
Thanks for the quick replies guys. The PC trick didnt work at all. I just called BLU and asked for a replacement(havent heard back from them ironically). I put the phone in the basement so I wouldnt have to deal with that incessant buzzing every 15 seconds. Eventually the battery died. Since I had it powered off finally, I plugged it in for about 10 minutes to give it enough of a charge to power on but not stay on to buzz for another 2 hours. This time I powered it on using the master reset button combo and was finally able to wipe the cache and restart the phone. Took a good 4 or 5 minutes to boot after that, but everything has been fine since. Really dont know what initially caused the issue, never happened before. Good thing too, cause BLU told me that they would send me a RMA within the hour and I still havent heard from them. Think this will be my last BLU phone. Thanks for the assist.
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
bolanoboyboom said:
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
Click to expand...
Click to collapse
??????
My phone is basically out of the box and I'm getting boot loop problems when I first boot. This happens like once a month
Sent from my PURE XL using XDA-Developers mobile app
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Update
num1greeter said:
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Click to expand...
Click to collapse
I tried to flash the phone, but the bootloop apparently wouldn't allow that. I had 0.0% progress after 3 hours. I then tried to go back into the menu you get from {Power}{Vol UP}: still no go. So, I started to take the phone apart again to get ready for shipping. The battery was still low so it didn't take long for it to die after I unplugged it from the computer. Out of curiosity, I tried to repeat finding the menu like I did earlier that day (conditions were that the phone had no charge when I connected it to the computer, and my SD card was removed.) No go. But, then I hit {Power}{Vol Up}{Vol Down} just to see what happened, and boom. My phone loaded up. No loop... Figured somehow the files had copied and the status bar was wrong. Turned the phone off, put my SD card back in and turned the phone on. Loop reappears ...I waited for the phone to die again, took out the SD, attempted to turn it on and the loop was there. Connected it to the computer and hit all 3 buttons, and the phone loads up. So, now I'm confused. Is there any way that the problem is some crappy connection to the SD?