Database Info

Tab not connecting to the internet?

I have the 3g version, P6800, and suddenly the tablet has lost the ability to connect to the internet. I was using the tab to read a blog a couple of hours ago and I've tried to use it again and nothing.
Posts won't load and YouTube app says no connection. Got home and connected to the WiFi and the same problem persists! My phone and my other tablet connect to the WiFi and connect to the internet no problem, so the problem less with the 7.7.
So I've cleared the cache and dalvik cache and still no connection! I'm going to try a fool data wipe next unless someone has any ideas?
Thanks for any help

w1ll1m said:
I have the 3g version, P6800, and suddenly the tablet has lost the ability to connect to the internet. I was using the tab to read a blog a couple of hours ago and I've tried to use it again and nothing.
Posts won't load and YouTube app says no connection. Got home and connected to the WiFi and the same problem persists! My phone and my other tablet connect to the WiFi and connect to the internet no problem, so the problem less with the 7.7.
So I've cleared the cache and dalvik cache and still no connection! I'm going to try a fool data wipe next unless someone has any ideas?
Thanks for any help
Click to expand...
Click to collapse
What ROM are you using?
Something here or a stock OS?

whitehawk66 said:
What ROM are you using?
Something here or a stock OS?
Click to expand...
Click to collapse
Using the JB ROM with Skyhigh kernel.
Well I formatted the tab via CWM and then it it was stuck in a boot loop. Then I used Odin to install the ROM from scratch and well, it kept boot looping.
Got it into recovery to install CM10, but it wasn't CWM just standard recovery. And then it wouldn't let me go into download mode because of low battery, and when I plugged it into the mains it came up with the charging icon and then say it was at 100℅ battery. A couple unplugs from the mains and reconnecting showed nothing different.
After a couple of times it began the sequence of showing how much battery it has before it charges with it flashing on and off before it died.
Now there is no response from the device. I've left it charging all night and this morning I held the power button for 20 seconds and it made no difference. The tab stayed dead.
What am I to do now?

w1ll1m said:
Using the JB ROM with Skyhigh kernel.
Well I formatted the tab via CWM and then it it was stuck in a boot loop. Then I used Odin to install the ROM from scratch and well, it kept boot looping.
Got it into recovery to install CM10, but it wasn't CWM just standard recovery. And then it wouldn't let me go into download mode because of low battery, and when I plugged it into the mains it came up with the charging icon and then say it was at 100℅ battery. A couple unplugs from the mains and reconnecting showed nothing different.
After a couple of times it began the sequence of showing how much battery it has before it charges with it flashing on and off before it died.
Now there is no response from the device. I've left it charging all night and this morning I held the power button for 20 seconds and it made no difference. The tab stayed dead.
What am I to do now?
Click to expand...
Click to collapse
I would start by holding the power button and the up arrow key to get it into CWM to restore your backup. Another option is to can get it to boot in the download mode and in either case i would hold the buttons longer than 20 seconds. After you get it to boot you may have to install the original software and start again. Good luck and I hope these suggestions help.:fingers-crossed:

Try a different AC charger with at least 2A capacity and leave it charging.
Sent from my GT-I9500 using xda premium

ColBill said:
I would start by holding the power button and the up arrow key to get it into CWM to restore your backup. Another option is to can get it to boot in the download mode and in either case i would hold the buttons longer than 20 seconds. After you get it to boot you may have to install the original software and start again. Good luck and I hope these suggestions help.:fingers-crossed:
Click to expand...
Click to collapse
Hmm, i would try to get into recovery/download mode if i could but nothing happens. Held the power button for 1 minute and if it hasnt worked by then, any more time is not going to make a difference.
UpInTheAir said:
Try a different AC charger with at least 2A capacity and leave it charging.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
I am trying the charger that I got with my other galaxy tab, P1000, and have left it charging for almost 18 hours.
Here's what's happening
https://plus.google.com/photos/113353682644068194312/albums/5903148559228012737/5903148559516627954

[Q] Odd battery Issue

Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
---Edit---
I should note that I can have all the radios on when it is plugged in, I just can not have them on when unplugged right now.

mikeoconnor said:
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not?
If you're rooted/on a custom ROM, I would make a backup of all non-system apps and settings and try to start over. The fact that you dont get that when in recovery is the biggest indicator.
First, back up all NON-SYSTEM apps/settings with Titanium backup (or something similar).
Then follow my fix >>>HERE<<< and see if that helps

I am currently on CM-10-20130728-NIGHTLY, I should also note one thing I did try was to update the ROM yesterday AFTER the problem started (problem started at 4pm I updated the ROM at 7pm), it use to be CM-10-20130526-NIGHTLY. I will look at your link and see if that works.

To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I hope you are wrong, but I fear you are right. But I am going to do the steps cited above and see if that helps, right now I am doing a second back up (first was Titanium backup, now is the CWRM backup) and I am going to do the flashing stuff who knows. Don't have much to loss, and I am still open to other ideas, if any one else has them.

tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
That's a distinct possibility, but not the only cause for what he's experiencing. Jumping the gun and buying new hardware usually results in money spent on hardware that wasn't needed a good portion of the time.

Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)

mikeoconnor said:
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
Click to expand...
Click to collapse
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is

jparnell8839 said:
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
Click to expand...
Click to collapse
It is white (indicating no water damage) also the other indicators on the phone are white. I hope you are right on that that would be sweet, I will stop by the tmo store before I head home tonight. And thanks for all the help (I now have to go back and "Thank" all the posts by you two, it is appreciated)
Funny part is I took the battery out to double check the sticker (even though I was sure it was still white) and the phone died even though it was still plugged in (so I guess I need both the battery and power plug for now)

mikeoconnor said:
It is white (indicating no water damage) also the other indicators on the phone are white.
Click to expand...
Click to collapse
you might get lucky and get a free one out of it. cant hurt to ask

Thanks all I picked up a new battery today and I looks like it is working. Sadly T-Mobile did not replace it for free but the phone is working again.
Sent from my Thrive using Tapatalk 2

[Q] Rebooting phone causes pseudo-brick

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

[Q] Scary Experience With HTC One M8

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.

Battery?

So I just picked up this s3, it will turn on but shuts off halfway through galaxy splash screen. Boots into recovery and Odin mode just fine, prior to purchasing we plugged it in, got it to boot and did a factory reset, to clear privious owners data, and it went fine, did it reboot and took me to setup. Satisfied with its performance I went ahead and made the purchase, upon unplugging it shut off, as I expected if battery was indeed shot. What gets me is I let it charge, unplugged, booted, shut off at splash screen, plug back in and says its still fully charged. Boot into recovery and indeed, 100% battery. I haven't gotten around to flashing twrp or rooting, was wondering if anyone has experienced this?
Sent from my HTC Desire HD using XDA Free mobile app

Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.

Phone was already on 4.4 when I got it, I downloaded and flashed stock firmware (ne1) via odin, I got the whole way to the end of setup and as soon as it started loading the homescreen it cut off and went to the green battery charge icon when phones off. Everytime I try and boot it, she'll go through all the splash screens and ill catch a very short glimpse of the homescreen and it shuts off. Also it HAS to be plugged in still, or else it just shuts off halfway through initial "galaxy s3" splash.. I don't understand...

Have you tried a new battery? Even if it's plugged in it won't run if the battery is completely shot.
Also if you indeed have a Verizon S3 on NE1 firmware you will not be able to install TWRP as the bootloader is locked. You will be able to root, however.

Muhff said:
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Click to expand...
Click to collapse
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app

XdrummerXboy said:
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.

Muhff said:
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Click to expand...
Click to collapse
I'm glad you fixed the problem!
Sent from my SCH-I535 using XDA Free mobile app