My Tab won't boot up. It gets to the Samsung logo and then turns off (or at least the screen goes blank). I can get it to the download/recovery option but neither seems to work. When I select recovery, it goes blank. When I select download, it gets to "Waiting USB Cable" but my PC doesn't see it. When it's plugged in to an outlet, the battery icon appears on the screen and then it starts to loop that every 30 seconds or so. I've confirmed I have USB drivers loaded. I've tried bringing up Odin but it does not see the device. I've depleted the battery and attempted to recharge. I've even opened it up and disconnected the battery. Is it time to start looking for a new one? Thanks in advance for any response.
Which version of Odin are you using?
Sent from my VS910 4G using xda premium
Odin3 v1.85
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-8-9-brick-repair/
Related
the sgs, when switched off, thinks that it is connected to a charger and that big battery screen shows up, at first the phone wasnt turning off after that.
ive since flashed using odin and 3 files hoping it would help. the phone now turns on but once switched off it continues to think that it is charging.
when i try and reboot, which i must do by plugging in a charger then pressing the power button once charging actually starts a minute later, the phone goes into a boot loop. Once it managed to get through after around 15mins.
I can get into both download and recovery mode. main problem is that the phone doesnt ever turn off (charging screen comes on), and that booting up is difficult and is hit or miss.
I have looked for other threads on this but havent found anything, so any help will be appreciated.
Thanks,
Felleese
Try a factory reset...
Thanks for the tip but it hasn't helped.
Anything else I should try?
Sent from my GT-I9000 using XDA Premium App
Hello all,
I searched around, but didn't find anything quite like my issue so figured I'd create a new thread.
I work for a company that uses Galaxy Tabs for various purposes. One of our men brought back their VZW Galaxy Tab (SCH-i800) and it was in an infinite boot loop.
I went to recovery and attempted to do a full wipe. This did not work (partitions were all jacked up) so I couldn't get it fixed. I'm not sure if the guy tried to root the thing and broke it or what.
Anyway, I was attempting to root then fix the partitions (then was going to flash a stock unrooted rom) and ended up soft bricking it (Phone Icon -- /!\ -- Computer Icon). The issue I'm having is the only time that screen comes up is when the device is plugged into the wall. It turns on, then off, then on, then off. If I unplug the device, it shuts down with no way of bringing it back up. I've tried holding power for 5 minutes, the same amount of time with power + vol up and power + vol down. Plugging it into the computer's USB ports does not help either.
It's like the battery is drained but it won't charge when it's on the soft brick screen. I've had it plugged in to the wall for almost 6 hours now with no hope in sight. When it's plugged in, I feel heat on the back of the device like it would normally be charging. The AC adapter is also the standard warmth after a lengthy charge.
I was wondering if anybody has had similar issues with this device and if there is any way to correct it.
--- EDIT 8/10/2012 ---
Another thing of note is when the device is charging, I can power it down by holding power for a few seconds, but the Soft Brick screen pops back up almost immediately upon release of the button.
I cannot boot into recovery or the standard download mode even when it's plugged in.
As long as you can get the Phone ! PC screen, your'e good, because this screen IS as a download screen. Go to this screen and flash a known good ROM.
ableeker said:
As long as you can get the Phone ! PC screen, your'e good, because this screen IS as a download screen. Go to this screen and flash a known good ROM.
Click to expand...
Click to collapse
You must not have read the whole thing. Not a problem.
The only time I get the Phone ! PC screen is when it's plugged in to the wall. As soon as I unplug it, it goes away and the device won't start up no matter what I try.
When you connect the tab to the pc, is it recognized by Odin.
Sent from my GT-P1000
salahmed said:
When you connect the tab to the pc, is it recognized by Odin.
Sent from my GT-P1000
Click to expand...
Click to collapse
No... When the device is unplugged from the wall it is shut down and won't boot back to the download screen, recovery, nothing. It doesn't turn on. There are occasions where the download screen stays up but it appears to just be frozen. The computer doesn't recognize it and neither does Odin.
I left it plugged in when I left work on Friday... Going to see if charging for the weekend does anything.
MaskedDriver said:
No... When the device is unplugged from the wall it is shut down and won't boot back to the download screen, recovery, nothing. It doesn't turn on. There are occasions where the download screen stays up but it appears to just be frozen. The computer doesn't recognize it and neither does Odin.
I left it plugged in when I left work on Friday... Going to see if charging for the weekend does anything.
Click to expand...
Click to collapse
No dice.. still jacked.
I determined the following scenarios may have happened:
1) The battery died (bad battery) during a software update and messed up the partitions
2) The battery died (bad battery) while he attempted to (unauthorized) root or flash the device, messing up the partitions.
The only thing I'm sure of is the battery is fried so any kind of hacking I can do to the device are for naught. I was able to get it to connect to Odin this morning for about 3 minutes (after having it plugged in to the wall all weekend). During the flash it shut down again bricking it even worse. Now the device won't turn on when plugged in to the wall.
Thanks for the suggestions and help. I'm calling this a lost cause at this point. We're just swapping out the device for a new one. Once that's complete, I may tear the device down and try to do a reset on the main board to see if that does anything, though I doubt that's the case.
Right I had exactly the same problem as you (exactly the same symptoms) but I have now fixed my tablet.
Like you I got to the point where the Tablet had enough charge to actually unplug it and connect it to my PC where I then tried to flash a stock ROM using Odin. About three quarters of the way through flashing the stock ROM the tablet died, disconnected from Odin and I got a message in the task list in Odin advising me that the process had failed. Even weirder my PC did an emergency shut down and restarted in safe mode.
Anyway I tried it again but when I started my machine, once I'd logged onto my desktop I started up Odin as quickly as possibly, selected the .tar file and pressed start as quickly as possible....it worked and my tablet was flashed with a stock ROM. However my battery was still pretty much dead and the first time of charging once it had been flashed with the ROM took about 24hrs plugged in at a mains charger for the battery to reach 100%.
My point is persevere with it and you will fix it. I was at the point where I was about to send it off to be un-bricked but obviously I'm glad I didn't now.
It is a ***** of a brick though, this 'coma brick'.
I've been having these same issue with my friends i800 galaxy tab. Can you chime in and offer some advice?
Sent from my Galaxy Nexus using Tapatalk 2
same problem-solved
I was having the exact same issue. the device screen was completely black when plugged into the computer. I was just about to give up when, all of a sudden the device went to the boot error screen while plugged into my computer. Apparently, it must remain plugged into the computer for about 20-30 minutes. Once this screen appeared, I ran the Heimdall one-click unbrick utility, and like magic, my galaxy tab was working again. Give it a try, and good luck.
MaskedDriver said:
Hello all,
I searched around, but didn't find anything quite like my issue so figured I'd create a new thread.
I work for a company that uses Galaxy Tabs for various purposes. One of our men brought back their VZW Galaxy Tab (SCH-i800) and it was in an infinite boot loop.
I went to recovery and attempted to do a full wipe. This did not work (partitions were all jacked up) so I couldn't get it fixed. I'm not sure if the guy tried to root the thing and broke it or what.
Anyway, I was attempting to root then fix the partitions (then was going to flash a stock unrooted rom) and ended up soft bricking it (Phone Icon -- /!\ -- Computer Icon). The issue I'm having is the only time that screen comes up is when the device is plugged into the wall. It turns on, then off, then on, then off. If I unplug the device, it shuts down with no way of bringing it back up. I've tried holding power for 5 minutes, the same amount of time with power + vol up and power + vol down. Plugging it into the computer's USB ports does not help either.
It's like the battery is drained but it won't charge when it's on the soft brick screen. I've had it plugged in to the wall for almost 6 hours now with no hope in sight. When it's plugged in, I feel heat on the back of the device like it would normally be charging. The AC adapter is also the standard warmth after a lengthy charge.
I was wondering if anybody has had similar issues with this device and if there is any way to correct it.
--- EDIT 8/10/2012 ---
Another thing of note is when the device is charging, I can power it down by holding power for a few seconds, but the Soft Brick screen pops back up almost immediately upon release of the button.
I cannot boot into recovery or the standard download mode even when it's plugged in.
Click to expand...
Click to collapse
I am having this issue with my sch-i800.... phone /!\ pc screen only when plugged into the wall, and no recognition of it on the pc. Any way of fixing it?
Searched but not found a similar problem that has a solution. I ran my battery dead by mistake and now all it does is restart after a few seconds on semaphore logo if unplugged, or keep looping buffering circle/battery charge symbol when plugged in. 3BC takes it to download mode but it again restarts after a few seconds...no way near enough to flash anything. Any Ideas?
I was running latest makay rom (2.8.0) and Semaphore 2,9,15s......this seems pretty fatal to me but if someone knows better ill be a very happy man.
Thanks.
Keep it plugged in for a few hours and see if this fixes it.
I have quite the same issue with my SGS i9000. Im running on slim bean 4.1.2 i think and semaphore (quessing the same as above)
So the battery got drained to zero. I charged the battery to full capacity while my phone was turned off. It did this okay and charged battery to 100%. Then i booted my phone only to find out it to start looping in boot. (Start screen to semaphore and then restarts.)
i removed the battery for about an hour, and rebooted the phone but it didn't help at all.
Can't get into recovery (vol up + home + power), though it did go into download mode.
snapper.fishes Keep it plugged in for a few hours and see if this fixes it.
Click to expand...
Click to collapse
As i plugged my phone in in to charger it shows as the battery would be empty,but it doesn't begin to charge it.
Ill be happy to answer if i forgot to mention something important according this matter.
If you can go into download mode but not recovery mode, there is only one thing that you can do - flash an odin rom.
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
If you can go into download mode but not recovery mode, there is only one thing that you can do - flash an odin rom.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
ill try that.
Thanks for the quick answer. Now lets see if that helps..
Tried keeping it plugged in for a few hours but with no joy, odin still recognises the device for the tiny bit of time that the phone it stays on, seen a few comments suggesting it's a battery problem. Have ordered a new one and will see what happens then. The old one was made in Sept 2010 and rarely been turned off since,so i guess its probably to be expected. Will post back when i get the new battery for other peoples future reference.
jwpil said:
Tried keeping it plugged in for a few hours but with no joy, odin still recognises the device for the tiny bit of time that the phone it stays on, seen a few comments suggesting it's a battery problem. Have ordered a new one and will see what happens then. The old one was made in Sept 2010 and rarely been turned off since,so i guess its probably to be expected. Will post back when i get the new battery for other peoples future reference.
Click to expand...
Click to collapse
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
banid0 said:
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
Click to expand...
Click to collapse
I also can't enter recovery, doesn't have time to boot that far. If it is like mine then you will be unable to stay in download mode for long enough to flash anything...if you can get to download and it not reboot again, you have some hope. You could possibly flash a different kernel via odin, semaphore possibly, and see if that helps, but if not you would have to flash back to stock and re-root etc (data will be lost). I will report back when i get a new battery and see if that is the issue (Friday Hopefully), I feel it might be battery issue because my ROM had been running perfectly for days and it started when i let battery completely discharge.
banid0 said:
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
Click to expand...
Click to collapse
Flashing will only delete app data. All your photos and music files will remain.
Just an update... Battery hasn't arrived yet due to snow here. But just by chance I left the phone bootlooping without charger in and it randomly decided to not bootloop. Was able to flash stock with odin root, upgrade to CM 10.1 and restore my nandroid. Oh well.
Sent from my GT-I9000 using xda premium
jwpil said:
Searched but not found a similar problem that has a solution. I ran my battery dead by mistake and now all it does is restart after a few seconds on semaphore logo if unplugged, or keep looping buffering circle/battery charge symbol when plugged in. 3BC takes it to download mode but it again restarts after a few seconds...no way near enough to flash anything. Any Ideas?
I was running latest makay rom (2.8.0) and Semaphore 2,9,15s......this seems pretty fatal to me but if someone knows better ill be a very happy man.
Thanks.
Click to expand...
Click to collapse
[SOLVED]
I recovered my Galaxy Y(s5360) by flashing another kernel from recovery mode in those few seconds for which recovery mode was starting...
I tried that but got soft brick, not enough time to flash kernel image. My power button is now broken so I feel that it may have been stuck in the on position. Think it's stuck in off now. Oh well
Sent from my GT-I9000 using xda premium
Hi I have the same problem on my Asus tf101 the battery ran out during upgrade and now it is looping on Asus title screen pls help me
Well my GF had a lot of trouble with this phone, we replaced the battery 3 times due to them failing. Anyway I updated it to official 4.3 for her and left it totally stock, no root or anything. All was well for a few days. One night we left it charging, when we woke up it was still pretty dead. She used it for about 5 mins then it died, now it won't charge or switch on! Got it charging offline but still didn't take any juice. Flashed in flashmode several times, now if I connect to anything it goes straight into flashmode and still won't charge! I bought her a galaxy s2 for now but is there anything we can do? Is it possible it needs yet another new battery?
Just to add I tried all the fixes such as leave it on charge, remove battery, button combo etc. When it does "charge" it doesn't take any charge
Sent while my supervisor wasn't looking
Try replacing the battery again and if this happens again it is definitely a hardware problem
Sent from my EndeavorU using XDA Premium 4 mobile app
I don't want to start a new thread, so I will post it here. My Xperia T is a dead phone in the moment and I was searching the web and of course xda to find a fix (like for Xperia Z).
How it happened: Yesterday my phone was working like a charm with CM11. I wanted to sell it and so I was trying to flash a stock rom. The flashing aborted with error every single time (Processing system.sin). I was able to flash all the .sin except for system.sin
After the phone was a soft brick I could enter fastboot/flashmode and flash the kernel from CM11 and install it without any problems.
I tried several times to flash stock until my phone bricked. Now it is charging and nothing happens, no fastboot, no flashmode, no sign of life. Only when the battery is detached the LED flashes one time (red) when cable is connected
Edit: The phone was able to go in flashmode but after few seconds it disconnected, in reconnected in flashmode. Also the phone is now recognized by the computer as "qhsusb-dload"
Edit Update: When I connect the phone to the computer an press Vol+ and Power Button for a longer time, the LED turn on (red color) and the qhsusb-dload disappears from device manager. After 2-3 seconds the LED turns of and the device manager shows qhsusb-dload again.
Now I have connected the phone to wall charger with a rubber band on the power button and sometimes the red LED turns on and stays for a few seconds
My SM910T was working fine, and suddenly the screen froze for a few seconds, then blanked.
From that point on, the phone has done nothing but a brief vibration.
After a battery pull, starting up with 1) normal power switch 2) download startup 3) recovery startup 4) inserting USB cable
all result in the same: A short delay, a brief buzz from the vibration, which may repeat again every few seconds. The screen remains black.
When connected to a Windows computer with USB, the phone is enumerated. It shows up as these devices:
SAMSUNG_Android SAMSUNG Mobile USB Component,
trtlemo
Port #0004 SAMSUNG Android ADB Interface.
ADB does not work. The command "adb devices" returns the null list (List of devices attached)- it does not see any device attached.
Windows sees the phones internal file system as an MTP drive, and shows the file structure, but the files are not accessible.
ODIN sees there is a phone attached (it says <ID:0/004> Added!!)
What mode or state is the phone in, and what should be done to restore normal operation?
You may simply have a bad battery. Have your tried another?
Sent from my SM-N910T using Tapatalk
rcobourn said:
You may simply have a bad battery. Have your tried another?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I don't have another battery, but I can order one. I can't prove that the battery is not bad, but I don't think that is the issue. It runs the phone and is only down to 65 to 75% at the end of a day under normal use. At the time this problem started it was a bit lower, I think about 50%.
Even though the display was black and didn't show the charging logo, I left the phone on the charger with the battery inserted for 8 hours. It still didn't boot normally.
Assuming the phone had a hardware problem, I initiated a warranty replacement process. I wanted to see if any of my existing software tools could wipe the internal data before returning it so I tried a few (as described above). One I hadn't tried was Kies. I connected the phone to USB, and let it settle (USBdeview showed the phone connected and disconnected about 8 times before stabilizing). Then I ran Kies3, and saw the Emergency Recovery on the tools menu. I opened it to see if it would recognize the phone. The phone did not appear in the "list of devices requiring emergency recovery". However, after doing that, the phone booted normally. I don't know what Kies3 does, or if it did anything - maybe it was just a coincidence. But the screen activated, and the phone booted normally. The battery was charged, so it appears that charging does take place even if the system does not boot.