Database Info

[Q] Brand New G-Tablet, powered on once

Hey everyone.
I just got a brand-new G-Tablet through Sears. I'm checking here to see if anyone has any ideas before their tech support opens in ~two hours.
I got it to my office, plugged it in and charged it until the light turned green. Then I turned it on and played with it a bit. I didn't have a method to put it on the network right then to sync anything, so I really just poked around and then set it to the side. One thing to note is that I wasn't presented with a setup screen at all, it booted straight to home.
Then later that afternoon when I went to go home, it wouldn't power on. I'm not sure if it went to sleep or powered off, but nothing happens no matter what button combination I press. I've tried just pressing power, holding it down for 4 seconds, holding it down for 30 seconds, power and volume + at the same time, and power and volume - at the same time.
I tried hooking it up to my computer last night, thinking that maybe the display didn't come back from sleep and maybe I could force a reboot via ADB, but it must be off alltogether since it didn't trigger a USB installation on the computer.
When I plug it in to charge, the little light turns red, then a while later turns green, indicating that it is fully charge, yet still no joy.
Your thoughts?

Press the power button for a really long time to see.
Sent from my GT-I9000 using XDA App

Just held it down for 90 seconds, no dice. I tried pressing it briefly afterwards too just in case.

I think Roebeet and a few others had a similar issue. I believe they had to wait 24+ hours for the battery to drain. I can't find the thread but the search button may help

You didn't update the firmware, correct? This is a known issue with the older firmware and it's happened to me.
I believe that the device is frozen - and yes, when it gets in that state you cannot reset it, even when holding down the power button. You have two choices, when this happens:
1- Open up the back of the device (and thus voiding the warranty) and press the reset button on the system board. That will fix it immediately. I know this probably isn't the best option, but I wanted to mention it.
2- Unplug the device and wait for the battery to completely drain. This takes about 24 hours. Once drained, you can press the power button and it will boot up for 10-15 seconds before stopping - that's your queue that the device is "fixed" so you can start re-charging it.
Fortunately, this probably seems to be resolved on newer firmware, tmk. I've only had this happen on a device with the original stock firmware.

The two of you are gentlemen and scholars. I'll let you know how it turns out. I was on the phone to get the RMA when the line went all fuzzy and I couldn't talk to them. Then it did the same thing when I called back. Then I saw this post. Divine Intervention...

Going on 28 hours now and still nothing...I'll probably give it at least 3 days before I send it back.

Give it a few more hours, and then plug it in for a minute and try powering it up. the battery could be so drained at this point that it needs to be plugged in to go on.
Mine took 24 hours to drain, but I wasn't sure if it was at 100% charged, at the time.

Almost to the 48 hours mark and still nothing. I tried plugging it in briefly just to check and the red light still comes on, but it won't power up. Anyone know the possible standby time of a fully charged batter on these things? I was thinking if the system locked up and it isn't hardly doing anything, it could last a while...

Maybe a return to the store you purchased it from at this point. The battery should be dead by now. You should be able to get an exchange or you can try the other route Roebeet suggested but that will definitely void your warranty

thebadfrog said:
Maybe a return to the store you purchased it from at this point. The battery should be dead by now. You should be able to get an exchange or you can try the other route Roebeet suggested but that will definitely void your warranty
Click to expand...
Click to collapse
The problem is that I'm in Guantanamo Bay, Cuba. Shipping time is at least 2 weeks and sears won't do an advance replacement. Neither will the Viewsonic support folks. So I'm either stuck having to buy a second one and waiting for them to get the original back before the refund, or waiting a month or more for a repair...
Are there any seals inside the case that get broken if you open it?

I don't know the answer but this may be of some help
http://forum.xda-developers.com/showthread.php?t=842354

thebadfrog said:
I don't know the answer but this may be of some help
http://forum.xda-developers.com/showthread.php?t=842354
Click to expand...
Click to collapse
I think I'm just going to give it anther day then send it in for repair.

Still nothing. Since its going to be over a month before I get a replacement, I'm just going to return it and wait for the new crop of tablets to come out. Thanks for the help guys.
Sent from my Dell Streak using XDA App

Sorry to hear that. I think the reset button on the board would have worked, but I understand why you wouldn't want to open the device up. We shouldn't have to void our warranty to be able to do a hard reset.

Rhodizzle said:
Still nothing. Since its going to be over a month before I get a replacement, I'm just going to return it and wait for the new crop of tablets to come out. Thanks for the help guys.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
You might try nvflash.... worked on a friends.

GTO777 said:
You might try nvflash.... worked on a friends.
Click to expand...
Click to collapse
But was your friend's responding at all? I get absolutely nothing. the only thing the tablet does is give me a red light when it's charging and a green light when it's done. The power button does nothing and volume down + power does nothing. doesn't nvflash require a connection over USB before it can do anything?

Completely Stock 19020T Bricked?

So I haven't used my Nexus for somewhere around 2 months since I got a new phone. The Nexus S was working fine prior, I had actually just got it back from Samsung after them fixing an issue related to my top volume button. After, I received it, the phone was in a complete stock condition, like it was just bought from a store (no unlocked bootloader, fastboot, Clockwork, etc.). A bit later, the OTA Jelly Bean update comes in, but I don't use it too much as I just got my new phone.
I left it on and ignored it for the past 2 months. I just assumed the battery would run out, and if I wanted to use it I would just plug it back in and that would work. Now the Nexus S won't show any sign of life. I've tried removing the battery and trying to turn it on while plugged in, when it's plugged in with my battery in, the charging indicator it used to show never shows up. Plugging it into my computer with or without a battery does nothing, it doesn't even show up in my device manager as "Unknown". I've also tried holding VOLUP + PWR for 10 seconds with all these different situations. Nothing. The phone is essentially dead. Any clue why this happened and how I should go about fixing it?

Nevermind. After leaving it plugged in with the battery for ~20 minutes it finally powered on! Hopefully this thread helps out someone in the same situation. It just seems as though it takes a long time to get it to a state in which it'll power on.

[Q] Rooted 4.1.1 GS3 Possible Sudden Death Syndrome?

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.

[Q] ~Guessing SDS?~

So about 2 weeks ago, i rooted my phone and flashed over the nightly version of CWM. Ran fine for about a week, afterwards i noticed a big battery drain. Then started the freezes, and finally the random restarting. During this time, it would commonly get my battery percentage wrong( Ex: It would say 20% but then die. I would turn it back on and it would say 5. Take out the battery, put it back in, and it would say something like 12%.) Yesterday, i had about 20% left, and it just turns off. Wont turn back on. I get home, plug it up, and its in a charging screen boot loop. Plug in-Go to charging screen-Turn off-repeat. It will do that repeatedly, as long as it's plugged in. I've looked it up, and it looks like it's the SDS (Sudden Death Syndrome) and that Samsung can only fix it under warranty. The problem is, I didn't get this through a carrier contract, i bout it basically new online. Any help? Anyone have advice on how to fix it, or what to do?

Odin back to stock and see if it still happens.
Sent from my SCH-I535 using Tapatalk 4

Bcaraway14 said:
So about 2 weeks ago, i rooted my phone and flashed over the nightly version of CWM. Ran fine for about a week, afterwards i noticed a big battery drain. Then started the freezes, and finally the random restarting. During this time, it would commonly get my battery percentage wrong( Ex: It would say 20% but then die. I would turn it back on and it would say 5. Take out the battery, put it back in, and it would say something like 12%.) Yesterday, i had about 20% left, and it just turns off. Wont turn back on. I get home, plug it up, and its in a charging screen boot loop. Plug in-Go to charging screen-Turn off-repeat. It will do that repeatedly, as long as it's plugged in. I've looked it up, and it looks like it's the SDS (Sudden Death Syndrome) and that Samsung can only fix it under warranty. The problem is, I didn't get this through a carrier contract, i bout it basically new online. Any help? Anyone have advice on how to fix it, or what to do?
Click to expand...
Click to collapse
Why are you double posting? You already posted this in the Q&A section, you're causing more work for moderators by doing this. Posting once is enough.
Sent from my SCH-I535 using Tapatalk 2

Damn phone stuck in bootloop!

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?