Related
Last night, while I was reading a text message, my phone rebooted itself. When it came back on, it told me that my memory card was invalid and that I would need to reformat my phone. It gave me two options: Emergency Call and Reboot. I pressed Reboot, and it turned back on normally.
Everything was fine until it rebooted itself yet again. This time, when it came back, none of my apps/games/anything work. The phone is on, but I can't do anything with it. The only apps that open are 3rd party apps that I sideloaded.
I tried connecting to Zune to roll back to a restore point, but all I get is connection errors. I even tried going into my Settings>about>reset your phone. This told me it would reset my phone back to factory settings. After doing this and having it reboot, my phone is still the same. All the apps are still there and not working, and even my custom theme is still there.
Someone please help me.
AT&T Samsung Focus
I just did the hard reset by holding Power+Camera+Volume. It seems to have worked.
Any idea what could have caused this? I mean yeah I did a lot of registry tweaks, probably making it somewhat unstable, but this isn't cool...now I have to re-unlock it, re-force NoDo to install, etc...
EDIT: Well, the factory reset is still...resetting. It's just sitting on the Samsung splash screen not doing anything. I'll report back if it never leaves this screen.
im guessing you are usig a samsung focus? if you are you would have better luck posting is the focus forum but it sounds like you are using or you used an incompatible sd card with it.
check this thread out http://forum.xda-developers.com/showthread.php?t=834144
and im personally using a samsung 16gig sd card bought from ebay seller nikolai1778(or something like that) since december and i havent had any issue so that card is certified. hope that helps
Yes, I am using a Focus, but I have had this card in my device for months and months. It has never given me any issues.
I took the card out, factory reset it again, and it is giving me the same "Storage card not working" message. The card isn't even in my phone anymore.
rmcgraw said:
Yes, I am using a Focus, but I have had this card in my device for months and months. It has never given me any issues.
Click to expand...
Click to collapse
what size is the sdcard? you probably just now recently used up all the space on the card and thats when you started getting the random reboot and data loss. read the thread i pointed out to you a lot of the issues you are having are documented there and the only known fix is to get a certified sd card or take out that sd card and hard reset the phone.
Again, I took the card out, hard reset it, and it's just stuck on the Samsung screen.
It's an 8 GB Sandisk Class 4
rmcgraw said:
Again, I took the card out, hard reset it, and it's just stuck on the Samsung screen.
It's an 8 GB Sandisk Class 4
Click to expand...
Click to collapse
im out of ideas here, thats the 1st time i have heard of that hopefully someone else can help u out. you can try calling or taking your phone to at&t
Yeah, I still have my warranty (I think?). I left it sitting on the Samsung boot screen for about half an hour and it wouldn't budge. Seems to be bricked, although if I just try to turn the phone on normally, it shows the storage card error (without the storage card present). It gets stuck while reformatting.
if you can go to settings/about/reset your phone do it whitout your sd and again with your sd card
Sent from my WP7 Trophy
I don't think that is the problem. From what rmcgraw has described, it sounds like the phone is bricked, with or without the card installed. I don't think this is something that is a user-serviceable problem. My guess is that the phone needs to be replaced.
Yeah, I can't even get into the phone to go to the settings. As I had said, I tried hard resetting from the settings menu twice, to no avail. I have no idea why this happened, it was completely out of the blue. Hadn't changed any registry values that day or installed any new apps. At the time it happened, I had my phone plugged into my PC to charge and I was reading a text message.
I'm leaving for the AT&T store right now, I'll let you know how it goes.
Well, after about an hour of standing in the AT&T store on the phone with the warranty department (they couldn't even do anything in the store to help me), they told me they had no idea what was wrong and that they'd send me a replacement. I have to send my original phone back to them obviously, and if they determine that it's my fault, I have to pay $410. Oh yeah, and I have to wait a week for my phone.
I am having the same problem with my surround. Got my first one warrantied out because it was bricked at the HTC splash screen after getting the memory card error. Now my second surround is giving the error every couple of days and has needed a hard reset for the same reason you mentioned. I haven't done anything to my phone. No jailbreaking or whatever. And both have the original sd cards.
Sent from my T8788 using XDA Windows Phone 7 App
Maybe your computer over volted in some way and the memory card ( not the removable one, the internal one) got damaged. I know that when I plug my Samsung focus into an Apple usbwall adapter that the touchscreen doesn't work (capacitive buttons do tho?) and it may reboot its self. I assume this happens because the Apple charger releases an incorrect voltage to the phone- ie; more or less than the phone needs and it causes the device to stop working properly. Never had any lasting effects on my phone, but I just can't use an Apple USB adapter
Sent from my mailbox
UPDATE
Received my new Focus on Monday. Everything was fine until a couple of days ago. Just so you know, I did NOT re-install my 8 GB Sandisk Class 4 microSD, and I did NOT unlock my new device. Everything is stock on it, except for the apps I've installed.
Now back to the issues: It started crashing randomly a couple of days ago. It would do it when I plugged my phone in, as I entered apps, and sometimes just completely out of the blue. Yesterday, I got the "Storage card isn't working" error, even though a storage card has NEVER been in this device. That error actually froze, the phone re-booted itself, and has been working normally since. This is how the my other Focus was acting before it bricked.
So, my question: Is it the battery or my SIM card (those were taken from the other device)?
rmcgraw said:
UPDATE
Received my new Focus on Monday. Everything was fine until a couple of days ago. Just so you know, I did NOT re-install my 8 GB Sandisk Class 4 microSD, and I did NOT unlock my new device. Everything is stock on it, except for the apps I've installed.
Now back to the issues: It started crashing randomly a couple of days ago. It would do it when I plugged my phone in, as I entered apps, and sometimes just completely out of the blue. Yesterday, I got the "Storage card isn't working" error, even though a storage card has NEVER been in this device. That error actually froze, the phone re-booted itself, and has been working normally since. This is how the my other Focus was acting before it bricked.
So, my question: Is it the battery or my SIM card (those were taken from the other device)?
Click to expand...
Click to collapse
If i had to guess is the battery .....
This may be completely unrelated, but I found it interesting...
I had installed the "Drive On" GPS app on my old device. I didn't like it so I never used it. I had made a list of all of my installed apps right before my phone bricked to reference for when I got a new one. When I got my new Focus, I did not install Drive On.
After I started having problems with my new device, I noticed that Drive On had appeared in my app list without me installing it. However, it wouldn't open. I uninstalled it and my phone hasn't crashed since. I haven't gotten the storage card error since then, either. In fact, my phone has been running flawlessly and maybe even better than before.
I could be crazy, but Drive On seemed to be a rogue, phone bricking app that I will never install again.
Phone was acting up again last night.
5-7 crashes/reboots, and I got the "Storage card not working" message again.
It's strange how these problems seems to come in waves. The phone will work perfectly for days straight, then will go crazy and have tons of reboots and errors within half an hour, and then will go back to working perfectly fine for a while.
I want this to stop.
Ugh, it just restarted itself and is now showing the "Let's get started" screen, as if it formatted itself. I took the battery out and I'll try to boot it back up in a few...
Why am I having such bad luck with these phones?
EDIT: Yep, the memory is completely wiped and everything is back to stock. All I did was plug my phone in because the battery was about to die. Every single one of these problems has occurred while the battery was extremely low and the icon would stay at the top of the screen reminding me to charge it. As soon as I plug it in while on low battery, the problems begin.
rmcgraw said:
This may be completely unrelated, but I found it interesting...
I had installed the "Drive On" GPS app on my old device. I didn't like it so I never used it. I had made a list of all of my installed apps right before my phone bricked to reference for when I got a new one. When I got my new Focus, I did not install Drive On.
After I started having problems with my new device, I noticed that Drive On had appeared in my app list without me installing it. However, it wouldn't open. I uninstalled it and my phone hasn't crashed since. I haven't gotten the storage card error since then, either. In fact, my phone has been running flawlessly and maybe even better than before.
I could be crazy, but Drive On seemed to be a rogue, phone bricking app that I will never install again.
Click to expand...
Click to collapse
A day after re-formatting itself, my phone suddenly fully re-installed (by itself) Drive On again. It opens and runs. I uninstalled it again. It is the only app that keeps reappearing after I have issues with my phone.
Hello All!
Three days ago I updated my GS3 to JB 4.1.1. I also ODIN'd TWRP onto my phone as a recovery and loaded SuperSU with an unlocked bootloader onto my phone along with BusyBox. I fell in love with my phone again as JB ran smoothly and I was even able to use Wallet Installer to get Google Wallet onto my phone. However, tonight, my phone seemed to experience a case of Sudden Death Syndrome. A common issue found by googling why my phone's failure to respond to boot commands and power commands.
It will not respond to attempts to boot into ODIN mode, my TWRP recovery and the only sign of life on my phone is a solid red LCD that lights up only if I remove the battery and leave the device plugged into a wall charger. Once I try to reinsert the battery, however, the LCD goes away and the phone once again turns into a coffee coaster. It's taking a lot of strength not to throw it against the wall. (I picked the worst week to quit smoking.)
I don't believe I hardbricked the device because three hours ago at the time of this post, I went to sleep and the phone was working and I was able to send and receive messages. I believe that rooting my phone actually made it even more stable than normal. I just can't believe my phone could just suddenly die. Could it be another case of Sudden Death Syndrome? (Corrupted NAND?) I bought this phone in August and many cases of SDS for the GSIII seem to occur within 150-200 days of activation, which would put me in that window. If I answered my own questions, please feel free to tell me. I'm just trying to explore all options as an exasperated user dealing with what seems frustration after frustration and the one release I have from that stress just **** a brick.
I am covered by Asurion Insurance (and if the crack on my screen will not be enough I plan on running it over with my car for good measure to get my money's worth) but I really do not want to have to file an insurance claim unless it is absolutely necessary.
Phone died just last night 12/29/12. The battery was running down, then beeped once like a warning to charge it. Plugged into the charger and no light whatsoever! The battery icon would come on for a second and then nothing. Left it on the charger over night. Nothing. No red charging light, no boot. Pulled the battery and re-plugged into charger. Same charging icon on screen but nothing else. Tried every combination of removing battery, sim card, memory card, and plugging it in to the charger and still won't boot. Tried a different charger and also my laptop. Nothing. The S3 is a USA Verizon variant. 16gb. Black. I guess it's off to Verizon this morning to get a new phone. Phone is only 45 days old!!!
You could try leaving it on the charger for a couple hours then booting into recovery and reflashing your rom. I've seen a couple instances reported on xda where the battery simply just gave up below 23% and refused to turn back on.
Edit: example, not even a couple weeks old...
http://forum.xda-developers.com/showthread.php?t=2056539
Sent from my SCH-I535 using xda app-developers app
If it is a case of "sds" Samsung will replace the board for free.
Ryno77 said:
If it is a case of "sds" Samsung will replace the board for free.
Click to expand...
Click to collapse
Only reports of SDS in the 150-200 day time frame that I saw was with the International Version and it is completely different motherboard.
What do you kids do to your phone? How old are you? I'm going to start a survey. Age please?
Sent from my SCH-I535 using Tapatalk 2
Update: Brought the S3 into Verizon. They pulled the battery (Like I did a few times!) and somehow got it working again!! FM ! Phone reboots and turns off and then back on. BUT..... if you turn it completely OFF and plug it in to charge then the same as I mentioned happens again. STRANGE. The only way to get it to reboot is to pull the battery and keep it out for about 30 seconds. Put the battery back in and it'll reboot again!!!! Is it me or is this a strange quirk???? The previous times I pulled the battery it was out then back in. This time I took it out, waited 30 seconds and VOILA! It works. Thought you might like an update. Verizon S3 bought on 11/17/12. Rooted and not oc/uc'd. Using Clean Rom 5.5.1
h
prdog1 said:
Only reports of SDS in the 150-200 day time frame that I saw was with the International Version and it is completely different motherboard.
Click to expand...
Click to collapse
That's good news..thanks for the correction.
About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.
Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.
The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.
Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.
----------------------------------------------
The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).
I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.
Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).
The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks
Armando Penblade said:
About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.
Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.
The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.
Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.
----------------------------------------------
The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).
I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.
Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).
The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks
Click to expand...
Click to collapse
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This doesn't seem to have any effect on the proceedings.
I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.
Armando Penblade said:
This doesn't seem to have any effect on the proceedings.
I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.
Click to expand...
Click to collapse
But that's what it's supposed to look like when it's hard bricked, keep trying to write it then boot with it. Eventually it's going to work, unless you somehow fried your motherboard.
Sent from my SCH-I535 using Tapatalk 2
Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.
Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?
Armando Penblade said:
Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.
Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?
Click to expand...
Click to collapse
Not really, if you're getting that error message I'm assuming this should work. At the very least you could get a jtag repair and that'll definitely fix it. You could always try the other debrick file available from that thread also.
Sent from my SCH-I535 using Tapatalk 2
Hello
Yesterday I was trying to migrate to a 32GB SD card from a 8GB SD card and I thought I had bricked my HTC Explorer (I don't recall what I did or what happened, but I was running Flyrom v4, and the phone all of a sudden wouldn't turn on) - I was getting 3-7 vibrations and nothing else when I tried to power the device on. I found a thread here about resolving the same issue on a Wildfire S and I mistakenly flashed the rom linked in that thread, following the instructions in that thread, not realising I should be using a rom for the Explorer (if a similar rom exists?).
I'm not even sure what was described in that thread worked but my device suddenly turned on again after following that advice - something like copy the rom to the SD card, wait 2-3 minutes whilst holding vol up+power, then press vol up, then wait another 2-3 mins.
I've now gone back to a locked/unrooted official rom state by using the RUU for the HTC Explorer because I thought doing so would resolve the issues. However since I've done what I did to try to resolve what I thought was a brick, but even before using the RUU, I've developed further problems with the phone.
What is currently happening is that the phone is heating up more than usual, especially while on charge via USB, and thus the battery stops charging, due to the inbuilt safety feature - the phone gets incredibly warm all round, even on the screen, it didn't before.
Also this morning when my battery did have some charge left in it (approx 50%) the phone would turn itself off after about 3.5 minutes and I had to pull the battery and reinsert to get it to boot up again.
I'm not sure why the phone is now heating up so much or what is/was causing it to turn off after 3.5 minutes.
I've tried checking CPU frequencies, suspecting the Wildfire rom I flashed messed with the firmware somehow at a level that hasn't been resolved by using the RUU, using SetCPU (device is not currently unocked/rooted so I can't set anything) but they seem normal, at 600/480 (this is what they've always been at since I got the phone?!), with governer on "ondemand" and the other option on "deadline".
I hoped flashing the RUU rom would resolve the problem(s) but it hasn't.
I don't have another battery to test (nor funds to buy one), but I don't see how it could be a battery fault when the whole phone is getting warm and everything was fine yesterday.
Please could someone advise me on what could be the cause of the issues I've now got with the phone and point me in the direction of a fix for these two issues (probably 2 parts of the same big issue), if there is one, as I can't use the phone unless it's plugged in via USB, which effectively renders it useless.
Really hope someone here can help otherwise I will either need to buy a new battery, or as I suspect will be the case, a new phone, and I have funds for neither.
Thanks in advance.
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?