First post. Tried searching for the desired info, to no avail. Braving any potential flame spray and asking anyway. Besides... this may entertain you. I've also posted this same question to a couple other forums, to no avail.
I have a P3113 that I had on me when I was caught in a rain storm. I was wearing a rain coat, and the tab was in one of the pockets. The pocket was zipped closed, so I thought the tab would be safe. It wasn't.
I did the regular stuff of turning it completely off right away, then put it in a bag full of rice for about 16 hours or so. When I tried to restart it, no dice. About a day later, it did turn on. It stayed on for about an hour letting me play Fruit Ninja. Then it shut itself down on low battery. I couldn't get it to charge at all during this period. I left it on the charger over night... didn't charge. At that point, I sort of wrote it off, but didn't pitch it.
Fast forward about 2 years. I get bored one night, pop the back off and wire the outermost wires to a freshly charged 3.7V battery from an OG Droid phone. Hit the power button... and it booted up!
While it was running, it wouldn't get very good WiFi, even sitting next to my router. It wouldn't open the Play Store app, and when I managed to log into Play through the browser, Play wouldn't recognize the device. That kept me from being able to download any app updates or any new apps.
Then the machine started running v e r y s l o w. At that point, I decided to throw caution to the wind (I did, after all write this thing off about 2 years ago) and do a factory reset.
Now, when I have the device in recovery mode, and I tell it to reboot, it will shut off and never turn back on. If I manually power on with the power button, it starts up in recovery mode.
The device isn't rooted, and I can't root it at all. At this point, I'm not even sure where the data cable is, not to mention it would never interface with a PC after the initial incident. I have, still, tried to do "apply update from external storage," using a few different roms I have found here and elsewhere. Most recently, I used Tab2Lite_P3113_RC2.zip, but it failed at about 75% complete and gave me a "signature verification failed" error message. In fact, I get the same message for every rom I've tried.
Anyone have any idea at all how to recover this thing? I'm only curious if I can get it running just to play games. I plan on getting a Tab 4 8.0 in March.
So you are using a different battery?
shsagnik said:
So you are using a different battery?
Click to expand...
Click to collapse
Electrically speaking, I'm running 2 batteries in parallel. The OG Droid battery is wired to the factory Tab battery. I can disconnect the Droid battery and the Tab still runs, but still doesn't reboot as it should.
When I select reboot, it powers down, and stays that way until I push the power button. Then it boots right into recovery mode.'
Sorry I can't help you as I don't have requisite knowledge
Sounds like you have a Frankenstein tab,you need a new tab. Time to put it out of its misery.
Pp.
Related
I'm scared that I may have lost one
I rooted with z4root, which seemed to go well. I downloaded rom manager (paid version) and flashed cwm. I had some trouble booting into cwm so i did a little investigating and ended up downloading bootstrapper as well. After enabling boot strapper I was able to get into CWM and do a nandroid backup.
I downloaded and flashed to newest CM nightly (8 I believe), and my phone seemed to be happy (it did want to power cycle when I was signing on to my google account at first, but after skipping the step in the set up wizard of the phone and just adding the account after it worked fine.).
I went to bed and did not plug the phone in. I woke up and saw that it was on still and proceeded to play a video game. I heard it beep across the room an hour later (no one around it) and figured it was getting low on battery since it had not been charged. When I picked it up to check the time, it would not start up. I have pulled the battery several times, tried to boot into cwm to flash my back up (could only get into the factory recovery), and I seem to be getting less and less response as time progresses. My power button doesn't seem to be producing any effect now and I can only get the screen to come up and display the big moto "m" if I plug the phone into a charging dock. I did charge my battery in my brothers OG droid since I heard that it wont charge the battery if it doesn't start up.
I'm by no means an expert, but I've had very successful rooting experiences with my Dinc (even soft bricked my Dinc, had a heart attack, then brought it back from the brink with help from this web site), a Thunderbolt, and a couple of fascinates. Never imagined a nightmare like this. Best part is this D2 is a loaner from my boss while I wait for my Charge to come in the mail!
Any help would be immensely appreciated.
ps. The only oddball variable that I can think of in this mix is that I'm using my micro SD card from my Dinc which had at least one nandroid left on it (which I deleted in Rom manager). I wonder if rom manager (or me... most likely me) got confused and possibly tried to flash cm7 for the Dinc from my SD card. User error, the story of my life.
try plugging the phone into a wall charger and leave it for a while. the charge window will come up
Yeah, battery power seems to be the simple answer to my power button not being responsive. I hijacked my brother's battery and my D2 powered up to the "M" screen and froze with just the power button press, or will boot into stock recovery (holding X on the keyboard while depressing the power after a battery pull), though I don't seem to be able to do anything effective from there. My battery is currently in my brothers droid charging as I continue to look for a solution/hope for more leads from this thread. Being able to consistently get a response from the phone is a step in the right direction though.
Have you tried powering up the phone into bootloader? That'd be a quick way to know if your data is corrupt. I went through that whole process last week. Only thing is that your battery can't charge in bootloader so make sure your battery isn't low.
Sent from my DROID2 using XDA App
If you're talking about holding the X key and power, then yes. This will bring me to the stock recovery menu. If there's an action that can be preformed from the stock recovery that will help me, I'm unaware of it. I know from cwm I would have the option to restore from a back up that I made (I have a stock back up and a back up from as soon as I got the phone up and running with a cm nightly rom).
I'm hoping that when I plug the phone into my computer it will be recognized. I read the instructions on how to run rsdlite here and aside from being able to navigate my phone menus to put it into usb mode, I should be able to take care of everything else. So now my real questions are; If my computer sees my device, is running the rsdlite program my best solution, and what's the next step if my computer does not see my phone?
try this
your phone will gharge if you put it in bootloader mode i know because ive done it now if you phones rom is jacked then flash it back to stock with rsd lite you can get the a955 stock rom from here this web site or my droid world also it will work there is noting wrong with your phone take care chris
Calling all Android Superheroes!!
I think I've done it. Turned my Charge into a paperweight. Was trying to flash the latest GummyCharged 1.91 package using Odin. It failed 3 times, but having read many accounts of similar failures I retried using different cables, different ports etc. After every "Fail" I unplugged the phone, rebooted, shut down Odin and started all over again.
After the last "Fail" message the phone simply stopped responding to anything. Won't boot, won't go into download mode, won't boot to recovery, doesn't show any sign of life when plugged into the wall.
All my reading about bricked Droids all seem to have some kind of responsiveness so don't seem to apply to my situation.
If anyone has suggestions or can point me in the direction of further resources I can research I'll be most grateful.
The worst part is going to be telling the wife when she asks what I'm doing.....
Thanks in advance for any / all help.
Call verizon tech support and give them some crap about how your phone was powering off by itself and you were dropping 4g, 3g, and 1x consistently and now your phone wont even turn on. They'll surly send you a like-new replacement phone.
I was having odin problems with my Charge as well, every rom failed... I figured out I had to uncheck 'reboot' and keep the battery in to get it to flash right. I know this doesn't really help but its similar
blazing through on my VZ Droid Charge
Thanks Sleek. I bought mine through Costco so I think I've also got the option to head back to Costco and get it swapped out. However, I've made my way through life believing that I should never surrender to the challenges presented by technology nor my own stupidity, so I'm pride-bound to at least try to make lemonade out of this situation.
anoninja118 said:
I was having odin problems with my Charge as well, every rom failed... I figured out I had to uncheck 'reboot' and keep the battery in to get it to flash right. I know this doesn't really help but its similar
blazing through on my VZ Droid Charge
Click to expand...
Click to collapse
Thanks anoninja - I'll keep those tips handy for the next flash attempt. And there WILL be further attempts....
I had this happen to me on the second day I had my Charge. What happened was, I was flashing what I thought was the latest version of Humble EE4, but it wasn't, it an old .md5 file for my Epic. I didn't even look at the file name, I just looked at the file extension and it would not turn on, wouldn't show that it was charging (no pun), or any sign of life other then the phone would get hot due to something with the battery.
My solution was that I called VZ customer care and said something like, "For some reason my phone will not turn on. I plugged it last night and when I awoke this morning, it will not come on. I tried pulling the battery and it still does nothing. Is there anything you can do to help me?"
So the customer care lady tried to walk me trough a factory/data reset, and you guess it, "it didn't work." After another five minutes or so of her "trying" to help me, she said that they would replace it under the warranty and she overnight-ed me a new phone and I had it the next day. I did have to send the bricked phone back to VZ, so for good measure I ran an electromagnet over it, you know just in case.
You can try it that way or go into the carrier store and play dumb (like you really shouldn't have a smart phone) and have them replace under the warranty.
Good luck!!!
Take out battery, plug into rear usb ports (if you're on a tower. If you're on a laptop it doesn't really matter. If you want to know why just ask, otherwise just do it). Fire up Odin3 with administrative rights (right click, run as admin). Hold down the lower volume button and cross your fingers. If it still won't power up into download mode, your phone has tapped out and needs to be replaced.
Sent from my Droid Charge running Humble 1.4
Some times the phone looses power during the flashing process even though it's connected to the computer. Keep the battery in the phone while flashing to alleviate this issue.
Sent from my SCH-I510 using XDA Premium App
kvswim said:
Take out battery, plug into rear usb ports (if you're on a tower. If you're on a laptop it doesn't really matter. If you want to know why just ask, otherwise just do it). Fire up Odin3 with administrative rights (right click, run as admin). Hold down the lower volume button and cross your fingers. If it still won't power up into download mode, your phone has tapped out and needs to be replaced.
Sent from my Droid Charge running Humble 1.4
Click to expand...
Click to collapse
Do everything he says but odin recovery.tar its in the humble ee4 section. After that reboot phone go to settings, then development, and turn on usb debugging. It took me 2 days to figure this out. Did the same thing. From now on before you odin make sure usb debugging is enabled. Hope this helps.
Sent from my SCH-I510 using XDA App
Just checked that forum and realized recovery.tar is not there. If you want it just pm me and ill email it to you. Its a lifesaver in your situation.
try this;
with battery out, keep the phone unplugged and hold down the volume down button and put the battery back in (not usb cable) and see if your phone responds to download mode this way. If it does, plug the phone in and see if odin now sees your device (with the battery still in).]
This worked for me in a similar situation.
My phone got hosed so bad that Odin would error out.
I finally found this and it managed to recover my phone:
http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
quarky42 said:
My phone got hosed so bad that Odin would error out.
I finally found this and it managed to recover my phone:
http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
Click to expand...
Click to collapse
Same here. It totally saved my butt.
Hi all. I appreciate all the suggestions. In the end I solved my problem by exchanging the phone. I couldn't get it to come back to life no matter what I tried. Thanks again to all.
Sent from my SCH-I510 using XDA App
Anyone come across this? I put it on standby last night after reading a bit of my book on it, and it had around 50% power remaining. This morning, it was totally unresponsive; pressing the power button does nothing at all. I've charged it for 12 hours in the meantime.
I've done the following all with and without the power attached:
- Pressed and held power for 15 seconds through to a minute
- Pressed and held volume up with power to attempt to get into recovery for up to a minute
- Pressed and held volume down with powerfor up to a minute
- Pressed and held power while touching screen (read that one off another forum)
I guess potentially it could be on and in a crashed state and unresponsive to the power, so maybe in a weeks time when it runs out of juice, I'll be able to charge it and power it back up, but in the meantime, I'd welcome suggestions.
A few weeks ago I updated it to the official ICS build that was released, but did the update myself rather than using KIES, as KIES didn't even recognise my Tab's firmware original version. It's been absolutely fine before the update, and since. I only mention it because I've read about the Samsung build of ICS being prone to self bricking itself, but I couldn't determine what the symptoms of this vulnerability were.
Thanks for any help offered,
Will
did you try connecting USB cable and plugging it into your PC? did u get any activity? can ADB recognize your tab?
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Had the same problem while on holidays. Once the battery goes below a certain level, you won't be able to charge it through USB any more. Instead you need to use the wall charger.
I think it's bad enough that the 7.7 doesn't have a micro USB port, but things like that are just stupid and Samsung made a big mistake here. It don't think it's the same with the newer tablets though. It's also not possible to just buy cables or chargers for this strange Samsung port, so when you forget your wall charger at home at some point you won't be able to use your tablet any more.
As long as you charge with the USB cable early enough, you can avoid it though.
A few months ago I experienced the same thing, the Tab just wouldn't turn on anymore.
I tried all there is without any luck.
Contacted amazon and they replaced it with a new one in less than 48 hours.
So far not Problems with the new device.
I have the P6800 and this morning I took it off charge. Put it into standby and only used it for about 20 mins then left in standby all day. It had about 95% remaining when I did so.
Picked it up this evening and the lower left area of the screen was warm and it would not switch on. Didn't think of the ADB idea but will try this next time but I had to reset it and when it powered on tonight after the reset, it was down to 15%. Within about 2 mins of checking stuff it was down to 3%.
Something is running when it is in standby but as I can't switch it on I can't check with BetterBatteryStats or CPUState to know what is wrong.
It does this every day. I am tempted to do a factory reset and reinstall only limited software.
Dave...
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Cluey said:
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Click to expand...
Click to collapse
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
TeeeJaay said:
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
Click to expand...
Click to collapse
hhmmm, interesting.
I was having trouble with wifi just before this happened. Both my GS2 and this have been claiming to connect to my wifi but aren't actually getting an IP address from it.
I can't remember if it was last night or the night before but I manually set an IP address, the signal strength is fine as my abode isn't very big.
After it has recharged I'll have a poke and see what I can find, thanks for the reply.
So my device seems to be working fine again. It had gone SO flat that the date and time were incorrect!
After I could power it on I had a look at Better Battery Stats and nothing looked wrong so I have no idea what happened. None of the apps I'd installed the day before it played up had long wakelocks and weren't running when I turned it off.
For reference they were:
My Tracks
MyTrails
Google Earth
AndSMB
I'd turned both of the GPS tracking devices off before I turned it off for the night.
It hasn't played up since but it hasn't been long so I'll see what happens.
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
A similar thing happens to me every once in awhile. The way i check to make sure everything alright is to see if it boots into download mode. I just leave it plugged in for a couple hours and it eventually comes back on.
someth1ng said:
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
Click to expand...
Click to collapse
this is why my 7.7 is the last tablet/phone from Samsung i'll never trust them they are just bombarding the market with new devices and leaving the old ones to dust
^thats what I thought too but that gs4 is really tempting. I've heard worse about HTC in that regard anyways so that why I'm not going with the one.
Finally.. i bought Sony xperia Z.
I'll sell my galaxy tab 7.7. I.m very disappointed with samsung.
Sent From XPERIA Z
kishd said:
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Unbelievable! ... this trick still works ... thank you very much for you help ...
^^ yo, this 'trickle charge' trick did NOT work on my (long) dead P6800... any other suggestions??
Quite strange because my Samsung GT-P6800 tablet was fully charged, it went completely blank dark as if it was off. To my amazement, SMS keeps dropping and calls kept coming in. Yet it is still as blank as though the tab was off. I pressed the power button and the volume up bottom for it to reboot. It rebooted without the screen coming up. It has been blank for two days now. What could be the cause? And what possible solution can be given?
This is going to be a long question/story thanks for your patience!
Whenever i try to reboot my phone, regardless of method, it takes an elaborate set of actions (elaborate as in it requires a power cord, a complex series of button presses, chanting, chicken blood, etc...) for the phone to turn back on.
I'm going to include a lot of details, relevant or not, i cannot decide.
I was using SlimBean Build 7 for weeks. I was able to reboot normally. I had heard about an app, WifiKill, installed it, caused short lived havoc at work, no issues so far. A few hours later, I attempted to tether my laptop using the hotspot function (something I've done many times before with no problem). The wifi turned off immediately and would not come back on. My exact thought was "Huh, that's weird" and attempted to reboot the phone, it seemed to shut off normally but did not come back on. At this point i believe the battery was at 60% or close to it.
No matter how I tried the phone would not power back on.
I charged the phone over night, and it actually came back on. Of course the first thing I tried to do was reboot the phone. Same result.
Now the phone is still not starting when turn off or rebooted with the power button command, it will not reboot when done with adb, it will not reboot when I try within the recovery. Any of these things cause the phone to act as if "hard bricked" with no response from any of the buttons or screen.
My first thought was to flash a stock rom with odin, when i plugged it into my PC (windows 7 ultimate 64bit) it asked for QHSUSB_DLOAD drivers. I tracked those down and installed them of course they did not work for odin.
I ordered but have not received a download mode jig.
I thought maybe it had to do with the act of charging the phone that sparked the brief show of life so i drained my battery using another phone and then charged it in the skyrocket for two days. Battery at 100% at this point.
At this point, I've discovered that if I hold the power button long enough while plugged in the phone will vibrate over and over until the button is released and by accident I learned that if i unplug the phone wile doing it's little vibro-trance it will start normally.
If I try to reboot the phone with any of the methods I listed above, I have to pull the battery, wait 10 minutes, plug in a power cord (not connected to a computer) hold the vol+ and vol- and power buttons, wait till it starts buzzing and insert the battery, if the charging icon appears the phone will power on, if not, I have to start again.
Once I learned that trick I was able to boot the phone into download mode and flashed back to stock JB and twrp.
I have since flashed slimbean build 8 and twrp 2.6.0.0. The phone is working fine but I don't have the guts to attempt WifiKill, tethering or reboot.
If you're still with me, good on you. I think the universe is mad at me for messing with people's wifi connection.
Anybody got any ideas?
THANK YOU!!!
ilike3point14 said:
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, I'm guessing that wifi kill app had something to do with it. I've tethered on slim bean 7 & 8, so I doubt it has anything to do with that or the ROM. Is say it's like you said, karma rearing its ugly head for playing wifi gatekeeper on unsuspecting individuals
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
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?