Related
Well guys, I may have finally destroyed my phone. I'm getting random powerdowns from recovery; it vibrates 5 times and flashes a green notification light until I pull the battery. USB is completely out the window, and booting to bootloader is hit or miss.
Any insight to this matter is greatly appreciated. Trying frantically to fix this before I head off to school.
shuts-off-vibrates-5-times-green-light-flashes.html , hope this helps as far as info goes. Dosen't look like anyone has recovered from this. found this at the incredible forums
Yeah I was reading through that thread last night. There is something I have noticed, however. I am no longer S-OFF. Don't know wtf caused that, but I'm instantly 10x more confused. lol.
Background: Very familiar with the Eris, rooted it, flash ROMs frequently, never had an issue.
So I bought the phone on eBay, only issue was the phone was a bit beat up and the screen had been replaced. No big deal. Turned it on everything was fine, worked for about a day, then I decided to flash another ROM. Flashed the ROM and the phone would reboot every time I got to the lock screen UNLESS I had signal, then it would work. This issue happens to EVERY ROM I flash. I wiped cache,dvlik-orwhatever, full wipe, everything each time I would flash a ROM, and none of them have been stable. After flashing the first ROM I also ran into the turn off and vibrate 5 times with a flashing green light problem. I have gotten out of this twice with the USB pull method. I have researched these issues, I have tried flashing quite a few ROMs, and nothing seems to work flawlessly. Is the DI just a terrible phone or do I just have a bad unit? The main issue seems to be with signal, such as if I go from airplane mode on to off it will reboot and then get stuck in a boot cycle and the issue with flashing the phone and having to have signal before I can unlock the phone.
I am currently about to flash the PB31IMG to see if it will resolve the issues and then attempt to re-root. Any advice would be greatly appreciated as nothing has seemed to work so far. I would key you into what I have tried but I don't remember. Basically all the things to fix the 5 vibrate issue and general flashing woes.
Update:
Still no good. Flashed the PB31IMG via vol. down and power and it still did a reboot. Unlocked, got to the white HTC screen, and restarted. Booted the second time, got to the lockscreen, and rebooted before I could even slide down the unlock. Third reboot, got to activation this time, then it rebooted. Fourth reboot, go to activation, then rebooted. Fifth reboot, got to lockscreen, then rebooted before I could slide down.
So yeah. basically you can see what I am dealing with. And it is not fun. I have tried SD card in, SD card out. Just did its 6th reboot, didnt even get to the unlock screen before rebooting.
UPDATE 5/3:
Link to the video of whats happening. Nothing special and I recorded it with my Eris, but you'll at least see the timing of the reboots and what not. And ignore the breathing. lol. Just turn off the sound. Right after the video ended it did a 5 vibe. Pulled the battery and now it's just doing bootloops.
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
As for the flashing green light and 5 vibrates, I have so insight on this. It can happen if you press power and Vol+. I think it puts it in a safety mode and the only way to get out of it is a battery pull. So if you ever get stuck in a situation like this wait 10 minutes and try to turn it back on normally. If this doesn't work try booting into hboot (power + vol down) if this doesn't work power + vol up has worked for some people too.
There are cases however, where battery pulls don't help either. And no matter what the person tries the phone won't turn back on. This is a hardware problem and the only way to fix this is getting a new phone.
Dhessler5 said:
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
snipped.
Click to expand...
Click to collapse
Would flashing the PB13IMG in Hboot unroot it or would I need to follow the guide? Just curious as I have never unrooted before, but I do know there is a guide for it.
The 5 vibrate thing is under control, it just has happened so I wanted to make it known.
And thanks for the info.
I would follow the guide for it, it would be the easiest and safest way and if you run into any problems they would be able to help you out and know exactly what to tell you. I have yet to unroot too so I don't want to tell you something without being 100% sure so I recommend the guide.
Alright, so it turns out flashing the image I flashed via Hboot is a way to unroot. :/ And that is when I got all the reboots in the beginning (the ones specifically posted, its not the first time). I am going to flash again once more to see if I can get a flawless start.
Still no good, flashed it again via Hboot and it restarted again. This timeat the white HTC screen after unlocking but before activation. :? Hm. Better than nothing, after the first reboot it fully loaded and everything is fine so far. Lets just home it doesn't slowly begin to degrade like last time.
A while ago while running the peanut stock ROM, every time my phone would reboot some apps would loose information (such as log in) and I was eventually unable to access the EPST settings.
If you rerooted your phone you could try to go into hboot and then recovery and "fix permissions." I am not sure if this will do any good but it couldn't hurt.
Also if it is unrooted you could try to bring it in to Verizon and see if they will give you a new phone or a restored one.
Make sure you have the stock Rom if you bring it back to Verizon also
sent from my dinc
sorry to hear this happened on an ebay phone... I've had it happen to 3 of mine... warranty took care of it since I'm still within my date. but after one year what do I do? luckily I bought my bros early upgrade meaning the Inc2 will suffice until april 2012
ohh yea my point sorry: I had an Eris before the Inc. //////had many problems after 5 they gave me the Inc if I agreed to drop my current one year contract and get a new two year paying the two year price PLUS got credited $199 for the Eris, and got to keep it, so I thought I made out until I realized this phone isn't gunna last two years. ANYWAY. I bought the Eris off Ebay, they gave me warranty after warranty no problem, best of luck
I have had my Inc for a year and have not had any issues. I would say you bought a bad model from someone on eBay. The 5vibration green light is indicative of a hardware failure and I have not seen anyone have a fix for it.
Sorry to say but I have seen no one, NO ONE recovery from the 5 vibs of death. From what I have gathered it is some sort of qualcomm download mode and I know of no way out. I have a feeling it is caused by pressing the vol + and vol - and power while trying to get into hboot.
This is just an uneducated guess. If your willing to part with the device I would love to get my hands on a 5 vibs phone.
Since it happens when the phone loses the signal, I'm wondering if it might be a radio issue. Which radio version is installed? It could be incompatible for your area/ROM/whatever.
Another thought: you said the screen was changed out. It is very possible that the kernal installed won't work for an lcd screen.
Anyway, more things to check and to test. Good luck!
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
ACD168 said:
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
Click to expand...
Click to collapse
That should be 3 vibs, not the 5.
they both won't work after wards thought as far as my testing.. had to get warranty replacements
I remember reading Chingy fixed 5 vib. It's not the end. I've seen other people fix it with ruu.
I couldnt fix mine when I got the 5 vibrations and I tried everything. My theory is that it has something to do with a messed up kernel flash since the baseband and kernel are apparently linked and I saw somewhere that flashing the same baseband 2x will cause this. It happened to me when I tried to flash a kernel twice (the first time it failed), some people could be getting this when flashing roms since they install new kernels also.
You can flash radios and kernals twice. There was one leaked radio in the past that caused problems from being flashed twice, but it isn't typical
Edit: I think chingy said something about trying a hundred different things, but eventually he got it to work by connecting to PC with battery removed. I could be wrong though because I read that post months ago. I know he got it working again by wiping system and starting fresh
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Trifurcated said:
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I think the 3, vibrate and 5 vibrate are connected because both times I had the 3 vib I had the same problems, would turn on when connected to usb then 3 vib and green flashing light... weird.
I am hoping you all can help me wihth some troubleshooting on my EVO
The trouble started saturday night (7/16) when I was standing up for a wedding. It was very hot that day, and the phone was acting funny. I pulled the phone out of my pocket late int he day and found the battery was completely dead.
I tossed it on the samsung charger I could find int he car, and it wouldn't recharge. I eventually found an HTC charger at home, and plugged it into that. the screen popped to the white htc EVO 4G screen, stayed a minute then shut off.
I left the phone on the charger, where it periodically booted to the white screen and then would throw itself into a boot loop.
I did finally manage to get it into H boot, and it says TOUCH PANEL-fail in the diagnostics section in the upper left.
I was able to access recovery and wipe it back to the last OTA, but cannot unroot it.
Sometimes the phone will boot to the lock screen and sit there, other times, it will show the lock screen, and then shut off, and other times it will boot loop.
The phone was manufactured on 8/30/2010 and is running h boot 0.76.2000
I have tried using the unrevoked S-on so I can take it in, but no luck.
If anyone knows what is happening or can help me unroot it, i would really appreciate it.
you need to buy a external charger for the battery. once charged it'll start charging again. It ONLY CHARGES while the phone is COMPLETELY booted. look it up on ebay or goto a sprint store and they will FREELY give you a battery to switch it with.
edit I have this thing. http://cgi.ebay.com/Battery-home-AC...553493?pt=PDA_Accessories&hash=item3f017793d5
But I actually got a package deal. once in a while if you let your phone die too low, THIS HAPPENS. it is completely normal. has nothing to do with rooting or anything. just a bad charging design.
This seems pretty strange . . . I would call a sprint store, or talk to online customer support, and tell them what's going on with the battery. Just don't say that it's rooted, and if it turns out that battery death really is this catastrophic, pitch a fit about it and make someone give you a brand new battery, because having to buy extra equipment just to charge your battery is absolutely not okay.
So, I did tkae it in to sprint over lunch, the guy said they have seen weirdness with the 2.3 update, and then saw the S-Off and refused to go further.
He did recommend replacing the touch panel though, as it booted to lock screen for him.
I did get a battery swap, and the problems persist.
I did open a ticket with HTC, we will see what they will do.
saigashooter said:
So, I did tkae it in to sprint over lunch, the guy said they have seen weirdness with the 2.3 update, and then saw the S-Off and refused to go further.
He did recommend replacing the touch panel though, as it booted to lock screen for him.
I did get a battery swap, and the problems persist.
I did open a ticket with HTC, we will see what they will do.
Click to expand...
Click to collapse
Run the s-on tool and update the hboot to anything but 0.76. Since 0.76 is the engineering boot itll still show s-off even though its not.
lmao. you let some ass at sprint to look to see if it was rooted?! are you an idiot!? wow. hahahahaha. and I thought I was an idiot. sorry. can't help myself. now you know he just noted your account right?
But btw, I'm right on the battery. I'm shocked that not a single person in this thread even knows this. It should be common sense by now.
runcool said:
lmao. you let some ass at sprint to look to see if it was rooted?! are you an idiot!? wow. hahahahaha. and I thought I was an idiot. sorry. can't help myself. now you know he just noted your account right?
But btw, I'm right on the battery. I'm shocked that not a single person in this thread even knows this. It should be common sense by now.
Click to expand...
Click to collapse
I don't know about you but I've never had a single issue with charging my phone while it was completely dead and off?
runcool said:
lmao. you let some ass at sprint to look to see if it was rooted?! are you an idiot!? wow. hahahahaha. and I thought I was an idiot. sorry. can't help myself. now you know he just noted your account right?
But btw, I'm right on the battery. I'm shocked that not a single person in this thread even knows this. It should be common sense by now.
Click to expand...
Click to collapse
Thanks for bringing something useful to this thread. For the record no account details were provided. Go troll someplace else.
Anyway, the phone is now S-ON running H Boot 0.93.0000. Touch Panel-Fail error persists, and the phone is still mostly a brick. It will sometimes boot to lock screen, others not so much. Phone does charge normally now, no need for special charging adapters.
My question to all of you, is would a failed touch panel show the behavior above? The boot failures and so on. Is there a POST process or diagnostic that the phone runs on start up?
saigashooter said:
Thanks for bringing something useful to this thread. For the record no account details were provided. Go troll someplace else.
Anyway, the phone is now S-ON running H Boot 0.93.0000. Touch Panel-Fail error persists, and the phone is still mostly a brick. It will sometimes boot to lock screen, others not so much. Phone does charge normally now, no need for special charging adapters.
My question to all of you, is would a failed touch panel show the behavior above? The boot failures and so on. Is there a POST process or diagnostic that the phone runs on start up?
Click to expand...
Click to collapse
This sounds like a problem I had with mine last year. It turned out to be a bad chip and the only fix was to send it in to HTC for warranty repair. They were pretty quick getting it back, but it was still six days with an old MinMo 6.1 phone. Be prepared for the withdrawls if you haven't got a decent standby phone!
saigashooter said:
So, I did tkae it in to sprint over lunch, the guy said they have seen weirdness with the 2.3 update, and then saw the S-Off and refused to go further.
He did recommend replacing the touch panel though, as it booted to lock screen for him.
I did get a battery swap, and the problems persist.
I did open a ticket with HTC, we will see what they will do.
Click to expand...
Click to collapse
Again. Sprint services rooted phones it's company policy.
Forum Noob here, I was using my Galaxy S3 (Wind) and all of a sudden the screen went black and it turned off. Something similar had happened a couple hours before and the phone wouldn't turn on through the power button so I simply took out the battery and put it back in and it worked. Then when it happened for a second time I tried the same thing but to no avail the phone stayed dead.
So far I've tried:
Using another GS3 Stock Battery
Tried getting into download and recovery mode
Tried charging it (I do know that the battery is charging since I checked it on another phone. The red light is not on but it turns on when I take out the battery and then plug it in. After 20-30 seconds of battery insertion the red light goes away and is completely unresponsive all that time)
Tried Keeping the battery out of the phone for a couple of hours (Suggested by a friend)
Also Tried connecting it to a pc, and it only connects when I keep the battery out. When it finally connects it tries to install drivers for "QHSUSB_DLOAD" but fails.
I have no idea what's happening to my phone and I would like to get it fixed as soon as possible. After some searches I've narrowed down to either a Hard Brick or a Sudden Death Syndrome but it doesn't completely match with all the characteristics of either problem. I greatly appreciate any help and I would like to know what exactly the problem is and what my best viable option.
Thank you.
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
TheSoldierDude said:
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
Click to expand...
Click to collapse
Only reason I suspect the power button is you mentioned you couldn't get it to turn on using the button, but removing/replacing the battery worked. And it can work perfectly and then fail out of nowhere. So goes when you have plastic parts! But lots of people have had issues with this button recently.
Wasn't trying to convince you that was the problem, just letting you know it's a potential culprit.
But if you think it's ok, then try to use KAsp3rd's debrick thread and see if that gets you going again.
Sent from my SGH-T999 using Tapatalk
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
ssingh0247 said:
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Click to expand...
Click to collapse
Since they are seeing the QHUSB_DLOAD (which is technically a hard brick) a simple USB jig wouldn't work, however they can attempt to use my recovery method. It's at no cost and just takes some time and reading.
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Remove and reinsert battery. If it turns on by itself, you are probably right about the button.
Sent from my SGH-T999N using Tapatalk
You're Right I believe
tomy1986.nt said:
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
Click to expand...
Click to collapse
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Nope
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Nothing happens at all.. its completely dead, simply a paper weight.. a very bad one of sorts
TheSoldierDude said:
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Click to expand...
Click to collapse
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Thank you
Perseus71 said:
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Click to expand...
Click to collapse
Nope.. xD 3 months off warranty, and yes I got it repaired from Samsung.. Motherboard was replaced, $300.. :|
Thanks to everyone helping out though
I can't believe I didn't know about these forums before :good:
Samsung Galaxy S3 died-black screen
my s3 gone black,its not getting turned on.there was red light(indicator) for some time before i tried to restart but when i tried to switch on. it's completly died,i am not getting any display.i have purchased in UK, unlocked using it now in India.some guys told me it would because of motherboard issue (if i replace motherboard it in India will it work normal,is there any possibility?)how to fix it?please give me some solutions.
screen not working
Hi all. In my s3 the red light is flashing fast. Also the screen is black but it works. Also the phone works and I can receive phone calls. Every few minutes the screen turns on for a sec and goes off again. I can feel the vibration when I touch the screen. Pkease help me.
Thanks
hard bricked
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
syben7 said:
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
Click to expand...
Click to collapse
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
yea, sry about that, was actually trying to get 10 posts in so that i could go post in the dev thread concerning this, gonna check out the method you sent, thanks a ton man!
STUCK
Well my s3 (us cellular r530u), has no boot but has a red led without the battery. Is there a debricking procedure? And if so..where can i find a debrick file.
There is for us. But you need to be in Sprints forums. Theres nothing for your device here, and I dont know what they have over there. Good luck though!
Sent from my SGH-T999 using Tapatalk
Hello everyone,
I'm trying to fix a Galaxy Tab 3 (p5220) for someone. The problem is that the tablet, when turned on, goes into a bootloop.
First of all I see the "Samsung Galaxy Tab" screen, then it jumps to the android robot standing (I believe this is the screen you see when you boot into recovery mode). The problem is that I can't do anything when I see this screen, it immediately jumps to the android robot laying on its back with a big red exclamation mark above him. Within one second this screen also goes away and the tablet reboots and starts doing the same thing.
I have already tried using the button combination to boot into recovery mode, when I do that the tablet reboots directly after the Samsung screen. So then I don't even see the android robot at all.
Then I tried booting into download mode, and this does work. I tried putting the stock firmware on it using Odin (not 100% sure if I used the right firmware though.). Anyways, this seemed to go as its supposed to go, but after Odin gave the "Pass" notification it rebooted, and started doing the exact same thing.
Does anyone have any idea if this is a hardware problem or can I still fix this?
ps. The person that I'm trying to fix this tablet for borrowed it to someone, and when it returned it did this. The person doesn't have any idea what has been done with the device. But we can be pretty sure that the person who borrowed the device tried to do something with it, but failed hard.
Thanks in advance for any kind of help!
I have the same scenario here as well. I have a friends Galaxy Tab 3 (SM-T310) and it seems to sit at the splash screen and never goes anywhere. I am unable to boot into recovery. I've tried Power+Vol Up, and Power+Vol Up+Home and nothing seems to be working. I am able to get into Download Mode. I have tried flashing TWRP 2.8.3.0 and TWRP 3.1.0 via ODIN, but I am still unable to get it to boot into Recovery.
I have also downloaded the Stock ROM from SAMMobile (I didn't see a US version, so I went with Canada? I figured, why not?) Flashed that via ODIN and I am still stuck at the splash screen.
I even took the back off and unplugged the battery and left it off for a few hours, since that is what the internet told me to do, and it still does the same thing.
I did just stumble across this thread: https://forum.xda-developers.com/showthread.php?t=2618798 so I am going to try CMW and see if anything changes. I figure once I can get into the recovery I'll be golden, but I haven't gotten that far yet. Any assistance would be greatly appreciated as well.
Mantics said:
I have the same scenario here as well. I have a friends Galaxy Tab 3 (SM-T310) and it seems to sit at the splash screen and never goes anywhere. I am unable to boot into recovery. I've tried Power+Vol Up, and Power+Vol Up+Home and nothing seems to be working. I am able to get into Download Mode. I have tried flashing TWRP 2.8.3.0 and TWRP 3.1.0 via ODIN, but I am still unable to get it to boot into Recovery.
I have also downloaded the Stock ROM from SAMMobile (I didn't see a US version, so I went with Canada? I figured, why not?) Flashed that via ODIN and I am still stuck at the splash screen.
I even took the back off and unplugged the battery and left it off for a few hours, since that is what the internet told me to do, and it still does the same thing.
I did just stumble across this thread: https://forum.xda-developers.com/showthread.php?t=2618798 so I am going to try CMW and see if anything changes. I figure once I can get into the recovery I'll be golden, but I haven't gotten that far yet. Any assistance would be greatly appreciated as well.
Click to expand...
Click to collapse
Someone with the exact same problem as me, with the exact same tablet, told that he fixed it by replacing the battery. To me it makes absolutely no sense that the battery would cause this, but I've literally tried everything software related to get this fixed. So I figured, why not give it a try! I'll post here as soon as I get the battery here.
Thanks for your reply, and let me know if you get it fixed!
musknl said:
Someone with the exact same problem as me, with the exact same tablet, told that he fixed it by replacing the battery. To me it makes absolutely no sense that the battery would cause this, but I've literally tried everything software related to get this fixed. So I figured, why not give it a try! I'll post here as soon as I get the battery here.
Thanks for your reply, and let me know if you get it fixed!
Click to expand...
Click to collapse
I have seen people pull the battery connector out, and leave it be for a few hours, and I tried that first, but that didn't appear to work for me. Maybe you can try that first before ordering the battery, but if you do get a new battery and that resolves the issue, let me know! You rock!
Mantics said:
I have seen people pull the battery connector out, and leave it be for a few hours, and I tried that first, but that didn't appear to work for me. Maybe you can try that first before ordering the battery, but if you do get a new battery and that resolves the issue, let me know! You rock!
Click to expand...
Click to collapse
I had the battery out for multiple days already, so I tried what you said just now. Still did the same thing.. I'm hoping to get the battery today or tomorrow! I'll let you know.
musknl said:
I had the battery out for multiple days already, so I tried what you said just now. Still did the same thing.. I'm hoping to get the battery today or tomorrow! I'll let you know.
Click to expand...
Click to collapse
You Sir (or Ma'am, I don't want to assume gender) are amazing! I hope that works, and if so, I'll have the guy order a battery and then I'll throw it in for him as well. Hopefully we can figure this thing out!
Mantics said:
You Sir (or Ma'am, I don't want to assume gender) are amazing! I hope that works, and if so, I'll have the guy order a battery and then I'll throw it in for him as well. Hopefully we can figure this thing out!
Click to expand...
Click to collapse
I identify as an attack helicopter
Anyways, got the battery and unfortunately it didn't solve the problem
I'm going to see if I can fix it any other way, but I wouldnt know where to start...
You got any luck yet?
musknl said:
I identify as an attack helicopter
Anyways, got the battery and unfortunately it didn't solve the problem
I'm going to see if I can fix it any other way, but I wouldnt know where to start...
You got any luck yet?
Click to expand...
Click to collapse
Thanks for your reply!
I haven't really tried anything else yet, I was waiting to hear back from the battery. I had high hopes for that. Does your battery ever look like it is charging? The one I have here just kind of sits there and doesn't appear to display the "Charging Screen" it just has a battery symbol with a circle on it, but nothing moves. It isn't mine so I don't know if that is "normal" behavior. The stock battery doesn't look swollen or anything, and even though it doesn't appear to charge, it still holds a charge. I will start posting links to things I try. Maybe we can figure this thing out?
Mantics said:
Thanks for your reply!
I haven't really tried anything else yet, I was waiting to hear back from the battery. I had high hopes for that. Does your battery ever look like it is charging? The one I have here just kind of sits there and doesn't appear to display the "Charging Screen" it just has a battery symbol with a circle on it, but nothing moves. It isn't mine so I don't know if that is "normal" behavior. The stock battery doesn't look swollen or anything, and even though it doesn't appear to charge, it still holds a charge. I will start posting links to things I try. Maybe we can figure this thing out?
Click to expand...
Click to collapse
My tablet doesn't even show a battery icon.. I think yours has more chance of getting repaired than mine hehe.
Yours sounds very likely to be the battery btw. You flashed a custom recovery right? How did you do that?
musknl said:
My tablet doesn't even show a battery icon.. I think yours has more chance of getting repaired than mine hehe.
Yours sounds very likely to be the battery btw. You flashed a custom recovery right? How did you do that?
Click to expand...
Click to collapse
I can get into Download Mode, and Odin will tell me it is flashing things, I even get the little progress bar along the bottom and it will reboot the device once finished...it just never boots into the OS, and I can't get it to boot into the recovery once flashed...so I have no idea what is going on. It makes me angry, like a clown! (Also, clowns are angry.)
I haven't played around with anything today since I'm a little bummed out since they shorted me about 96 hours from my last 3 paychecks at work, so I'm kind of on strike. Anyway, I will play around with it on Monday and post everything I try, and get back to you. Maybe I'll even pull the battery out again and let it sit all weekend before I duck out 2 hours early.
---------- Post added at 02:24 PM ---------- Previous post was at 02:16 PM ----------
So, I just pulled off the back, undid the battery, and plugged a USB cable into the device for power. Do you happen to know if these will boot without a battery? I ask because it appears to be doing the same thing, so it may well be the battery, but the battery doesn't look swollen or anything, so idk? Thought?
I'm sure you've probably tried this but just wanna be sure... I've been watching this thread to see what things were tried.
When you boot to recovery it is by holding power, vol+, and home...but once the splash screen shows up let off of power but keep vol+ and home pressed...if not it will just reboot. Hope this helps, though I know it is unlikely.
Sent from my XT1609 using Tapatalk