Database Info

[Q] Bricked --> Battery Drain

Hi all,
So my transformer is bricked... completely been trying hard reboot, APX mode, holding power button, HDMI output the list goes on.
My only final resort is what I've read is draining the battery down and trying to recharge it? (Just need some confirmation here please if possible).
I've kept it in the dock, what I've noticed is, in the morning it was green LED now its gone to the amber so something is draining the battery I"m hoping I can get this down to 0.
How long do you guys think with both dock + pad and most likely on standby. Not too sure of the issue here
Anyway, I'm really reluctant to send this back to Asus RMA because in short:
1. First time I sent it, it got returned like a squeaky box. Every where you held it you heard a creak like it was about to snap. They didn't fix some things, and more dust ended up in my camera lens... + had to pay postage..
2. Half fixed, came back with wrong firmware (TW --> US). Could never update ever again, so microsd card updates FTW. No way was I planning on spending an extra month sending my TF back and forth... I paid extra to get the first batch B40 lol.. They replaced everything inside my TF motherboard, screen, Inside LED!?, buttons. Close to the works..
This happened right after I upgraded to ICS, it was the US stock rom booted up fine. my apps were updating, and as everyone else was saying about how some apps caused ICS to slow down I wasn't aware so I thought I would shut it down and power it back up. Since then it's not been able to come up ever again... Any suggestions?
What do you think?
Thanks in advanced.

One other thing, could someone check.. when tablet is docked and OFF. Do the usb ports still work?
Right now, when docked but "bricked" I can still charge my phone via USB.. If someone could test this that would be much appreciated as that could at least eliminate that my TF's battery is dead, right?

get it off the dock, hold volup+pwr, count to six and leave it for a couple of days. You can test if it's empty when you plug it in your pc via the cable. If you get the device plugged sound it means there's still juice there - unplug and press again volup+pwr. when you unplug it from the pc the tab shuts itself down.
if you don't volup+pwr before you plug in the usb it won't turn itself on. but it turns off automatically at unplug, as I said.
after the battery is down, plug the tab to the charger. I don't have the dock so I can only speak about the tab itself. Don't know why, but it works for me everytime. Hope it fixes yours, then, if possible, root and flash something.

bigblondewolf said:
get it off the dock, hold volup+pwr, count to six and leave it for a couple of days. You can test if it's empty when you plug it in your pc via the cable. If you get the device plugged sound it means there's still juice there - unplug and press again volup+pwr. when you unplug it from the pc the tab shuts itself down.
if you don't volup+pwr before you plug in the usb it won't turn itself on. but it turns off automatically at unplug, as I said.
after the battery is down, plug the tab to the charger. I don't have the dock so I can only speak about the tab itself. Don't know why, but it works for me everytime. Hope it fixes yours, then, if possible, root and flash something.
Click to expand...
Click to collapse
Hi there,
Thanks, I'll that a try.

It's definitely charging and discharging, the battery brick is warm.. I've never had to connect my tablet to a windows PC. Today I did, it didn't make a sound.. Do I need to fully charge to be able to turn it on?

Normally not. I plug mine to the charger, I don't remember if it stats or I have to press power, when it boots the battery stays at 0% for several minutes.
Sorry for the late reply, did you manage to wake it? It's a long procedure of waiting mainly and can get annoying.

I'm still trying, earlier you had a thread about it poping up through the computer. What was the command you used in Linux?
Windows gives me nothign even when there was power in it.
Thanks.

Thank you sooo much!! It finally has powered back on, I hope this doesn't happen again.

[Q] Infuse bootloop

Im trying to explain everything to prevent unneeded questions
I have viewed several threads about this but absolutely none with an answer. My Samsung Infuse 4g with at&t (nonrooted) is in a bootloop. The cause of this was my every-other-day reboot. Once I turned it back on it goes to the samsung screen for about 5 secs, then goes black, then says samsung again and so on repeatedly. I pull the battery and as soon as it makes contact back with the phone it turns on by itself into the same Samsung screen over and over. When plugged into wall or computer it will show the charge screen where there is no battery life left, then it will flash and start up the charge screen again and so on just like the samsung screen. I cannot go into download mode (the buttons, at this point, do nothing. No response)
I have tried taking the battery out and plugging in usb cable to computer, then holding both volumes and putting battery in=charging loop
↑ with volume up=charging loop
↑↑ with volume down=charging loop
computer doesnt detect it, adb cant find it, cannot go into download mode, odin cant see it, heimdall cant see it, cant actually boot into anything, cant leave battery in or else phone will restart itself the entire time, and this was caused by my (already gbread) infuse 4g doing a regular reboot (aka power button, tap power off, after phone is confirmed off take battery out, battery back in, turn on)
Recommendations at this point? on a scale from 1=noob to 10=expert im a 7 on this type of thing. Ive always heard that as long as you can boot into a picture its only soft bricked but if i was right i wouldnt be here. Any and all help would be much appreciated. If you need me to post a video I would have NO problem doing that showing everything im doing.

oh, and by I have viewed several threads about this i meant that i have only been able to find 1 thread about it and 2 links that didnt work for me but might for you
link that worked- http://forum.xda-developers.com/archive/index.php/t-1354731.html
links that did not-
http://www.google.com/url?sa=t&rct=...ih1Zf_BvtcIbJXGEw&sig2=jjOcukFWr9sPWJZH1rlhnA
http://www.google.com/url?sa=t&rct=...ih1Zf_BvtcIbJXGEw&sig2=SZeMzIF2hnjdkk6GPDkovg

You might have already tried this way, but I've always held down both volume buttons first before plugging in the USB cord - not the other way around. You can also try different cords, different USB ports and/or different computers.

Mine was doing this the other day and it turned out to be my SD card being flaky. Maybe try taking it out and booting?

Radiotsar said:
You might have already tried this way, but I've always held down both volume buttons first before plugging in the USB cord - not the other way around. You can also try different cords, different USB ports and/or different computers.
Click to expand...
Click to collapse
Ive tried a hp touchpad cord, an atrix cord, and the original cord. I cant really do the button combo because as soon as the battery makes contact the phone turns on. thats why i had the usb cord in first to see if it worked. ive tried every usb port and 2 different laptops, the computer wont recognize it if the phone wont go past the samsung start up screen
J101 said:
Mine was doing this the other day and it turned out to be my SD card being flaky. Maybe try taking it out and booting?
Click to expand...
Click to collapse
I've taken the card out and used a different card, nothing. Tried taking sim card out, nothing.

I should have been clearer. Leave the battery out of the process until after attaching the cord and the screen coming up.
Sent from my SGH-I997 using xda premium

Radiotsar said:
I should have been clearer. Leave the battery out of the process until after attaching the cord and the screen coming up.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I do, every time.
1. battery out
2. hold down volume buttons (any combo)
3. attach cord (nothing happens, no screen, nothing)
4. put battery in
Results= Charging loop

lifetaker said:
I do, every time.
1. battery out
2. hold down volume buttons (any combo)
3. attach cord (nothing happens, no screen, nothing)
4. put battery in
Results= Charging loop
Click to expand...
Click to collapse
should be the same...wonder if you battery needs to be charged first, it should be fully charged at best...to do any flash/Odin/one click
this how I do it...basicly the same..
>take batt out
>plug in usb cable...to both phone and computer
>hold both volume buttons...NO NOT HOLD THE POWER BUTTON....
>put batt in...
and bam should see the android dude shoveling in yellow triangle...

If you get no response from the usb without the battery, and inserting the battery indicates the battery needs charging - I'd suspect the phone's usb port. Especially after trying different cords & computers.
Sent from my SGH-I997 using xda premium

Sorry for the sometimes choppy video recording.
http://www.youtube.com/watch?v=QWKdGS_5_Ps&feature=youtu.be

Have you tried a jig you can buy them on ebay for 6-12 bucks or you can donate one of you old cables and make it your self..
http://galaxys2root.com/galaxy-s2-hacks/how-to-make-a-usb-jig-for-your-galaxy-s2/
this will/should get you into download mode

Hello.
I have the same problem... tried also everything now i gave it to cellphone shop, i hope you guys can give me answer before i am gonna waist $100

HELP?1
Help me please

I was in this state. There are two options I can think of. A JIG as mentioned previously or the Heimdall One-Click-Unbrick. The one-click unbrick did it for me and got me back to cmw and download mode, then i could flash to stock, root and flash up to ICS. It was really easy and I stopped sweating once it booted to cmw instantly after running it.
Joe

hello.
The problem is when i connect it to my computer its keep disconnecting and doing terreble noise, (windows noise) when you keep connecting and disconnecting USB cable
JIG DIDNT WORK, because the same problem.... maybe the chargging connect is broken? or has a corrosion?

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

Sounds/Looks like a hardware issue...
Did it get any water damage in the past?
Hope you got warranty or still under warranty.

I am having exactly the same problem. My Infuse has never been rooted or unlocked (quite ironically, I was about to root it for the first time).
Boot loop when not plugged in, charge loop when plugged in. Absolutely no combination of buttons, inserting/removing the battery, and/or plugging/unplugging the USB has gotten it to do anything.
This has happened several times over the past few days. The first few times it sorted itself out in an hour or two. Today I couldn't get it to do anything at all.
I found several posts by people who have this problem, and it has never been conclusively solved from what I've seen. Finally one person said they fixed it by lightly smacking the phone with their hand. Lo and behold, it came on for about 5 minutes before looping again. So I smacked it again, and before it could re-loop, I factory reset it. A few hours went by and I was convinced that it was fixed.
A few minutes ago I had it plugged in to my computer via USB and was getting ready to SuperOneClick it. Then it went back into loop. I can't get it to come on this time. Again, no combination of buttons will send it into download mode. The computer can't see it. The battery is charged. The USB cable and port are fine. The software was reset earlier today. Does this mean that I have a hardware problem, or is there a software issue that could be fixable?
EDIT: So I decided to try hitting the power button, something that had never worked to this point, and the device came on. A couple minutes later it went back to boot loop. On a whim I tried download mode, which had stubbornly refused to work all day. Of course it immediately worked. Not really knowing what to try, since I'd already wiped user data, I wiped cache data and formatted the internal SD. Then I told it to reboot. Back to boot loop. A few minutes later, it came back on with the power button. Two minutes later, boot loop again. Then it restarted of its own accord. And now back to boot loop. I just don't even know anymore.
EDIT2: Just a thought... Something is weird with the power button. Whenever the phone is on and I hit power (briefly, not holding it down), it goes to the shutdown menu as though I'd held it down. A few seconds later, I'm always back in boot loop.

Infuse loop
I have found the problem. It is, in my case, the power button. I removed the case and crossed terminals with a paperclip. BAM. Booted up, and when I removed the paper clip.... back to boot loop at Samsung logo.
There is a place to send the phone. Ive see great reviews.
mobiletechvideos.mybigcommerce.com/samsung-infuse-4g-power-button-repair/

Seems like there has been a string of power button malfunctions going around lately. There are a few threads going on where people have had this issue. Sometimes its just the terminals needing to be cleaned or dust blown out.

[Q] Did I just brick my Evita One X?

I do apologize for filling up this forum with yet another "Did I brick..." question, but I'm really at my wits end and need some guidance.
This morning I decided to update my kernel to ElementalX 5.0. Prior to this I was using the 4.5b kernel and had no issues, but I wanted to move to the stable release and hadn't had any issues in the past. I have ViperXL 3.2.3 installed on this as well. I have yet to apply S-Off as I haven't had any real issues at the time and wanted to wait for the weekend when I had enough time to dedicate to the process (life is hectic blah blah blah).
I downloaded and installed the 5.0 kernel as I had previously, making a nandroid prior to the install. I decided to try some of the overclocks/undervolts that everyone raves about so during the install I chose the 2.1GHz overclock (because I can always step it down if it gets flaky, right?) as well as overclocking the GPU and undervolting to 850. I also went with zRAM as usual. After this was done and the phone rebooted twice (a common occurrence) I was brought to the window where Android was optimizing my apps. After that completed, I was brought to my home screen where I saw the clock and everything else. It looked like yet another successful install....and then the phone went black. Since then I have been unable to get it to boot. Pressing and holding the Power + Volume Down does nothing. I've held it for over a minute and no blinking capacitive lights or anything. The charge light does not come on when it's plugged in and, while my computer first tried to install the drivers when I plugged it in, I received an error saying the device was unplugged and no matter what I do I cannot get it to try to install again. Device Manager doesn't show it as being plugged in and it no longer comes up in Windows Explorer. Prior to the install the batter was at 83% and I have had it plugged in now for almost 20 minutes and still the charge light has not illuminated.
I never thought it would be possible to kill this phone, but I think I successfully did. Does anyone have any insight, suggestions, or helpful pointers. Yes, I know this was a risk I took doing this and I am not going to bemoan the fact that I did this to myself...I just really want to know if it's possible to resurrect this phone.
HTC OneXL
Hboot 1.14
S-On

Leave it plugged in to a wall charger for a while

a box of kittens said:
Leave it plugged in to a wall charger for a while
Click to expand...
Click to collapse
So do that as opposed to plugging it into a PC? Asking since I don't have a cube with me at the moment and will need to run home at lunch to grab one if the case.

Yes into the wall charger...and hold power for thirty seconds does anything light up?

As for my own experience I have had trouble getting my phone to reboot or get into the bootloader when it plugged in. The charger seems to keep the phone turned on while it charging. Try unplugging it from the charger and try again.
Sent from Xparent Red using my Venomized Evita

This happened to me too, but I got it to reboot by holding down the power button. What's happened is that the phone thinks the battery is dead. When it comes back up, you'll probably show 1% charge. Somehow or another, the battery monitor data gets corrupted. I think it's related to the general battery data bug that's plagued this phone from the beginning.
Your phone clearly can't handle 2.1 and undervolting (I increased my voltage to run 2.1). Bump up the voltage when you get it back up.

Pdj7969 said:
So do that as opposed to plugging it into a PC?
Click to expand...
Click to collapse
Definitely. The wall charger is much faster than USB from a computer.

IT LIVES!!!!
I ran home and grabbed my wall charger and brought it back to work. I plugged the phone into the charger and let it sit. After about 2 minutes, the charging LED lit up. I gave it about 15 minutes and then tried to power it on but it was no go, turning off the charging light and not doing anything, so I let it charge for another 30. When I thought it should be good and ready, I decided to go ahead and attempt to boot into the bootloader, as my fear was that the undervolt and massive overclock would most likely bring me back to square one. Holding down Power and Volume Down, I said a silent prayer to the device gods.....and the capacitive buttons began flashing.
Once I got into the bootloader, I quickly booted into TWRP, cleared cache and Dalvik, and then reinstalled ElementalX 5, this time choosing the stock voltage and not overclocking the GPU. I kept the overclock at 2.1 because, like I said before, if the phone is flaky, I can dial back the speed and restore functionality. I like the idea of having the option to go balls-to-the-walls if I WANT to, but not necessarily will I go that route.
After the lengthy kernel install and the normal 2 boots, I was met with my beautiful Viper lock screen. Thank you guys so much for the insight into needing to charge from the wall instead of the PC. I never imagined the computer would refuse provide a charge to it if it was completely dead (or the phone thought it was completely dead...once I got into TWRP it stated battery life was 86%). I am calibrating the battery now as I just realized it hasn't been done in probably 6 ROM installs.....derp!
Since this issue is resolved now, the thread can be closed. Thanks again, all!

Pdj7969 said:
I never imagined the computer would refuse provide a charge to it if it was completely dead
Click to expand...
Click to collapse
USB charging might still work, it would just take a lot longer. Some folks have had to plug there wall charger for hours or overnight, even on the wall charger, to get their phone booted again. So the wall charger is just better since its faster.

redpoint73 said:
USB charging might still work, it would just take a lot longer. Some folks have had to plug there wall charger for hours or overnight, even on the wall charger, to get their phone booted again. So the wall charger is just better since its faster.
Click to expand...
Click to collapse
And it may have, but the thing I noticed in the 90 or so minutes it was connected to my work PC was that the phone was the coldest it had ever been since I got it, meaning that the usual warmth caused by charging was not present at all. I did notice in Device Manager that when I plugged in the phone, it would register the phone as an HID (Human Input Device) and then it would disappear, only to reappear again and then disappear once more. This would happen non-stop until I disconnected it, so perhaps that's why it didn't charge at all during the time it was plugged into the computer? In any event, good ol' wall current supplied the juice necessary to bring this sucker back to life, so I'll file this info in my memory banks and make sure I have a wall charger at my desk from now on.

Battery completely dead or other hardware issue? [semi-resolved]

Hi All, my wifes s6 (using xtrestolite rom) has stopped taking a charge. Im trying to figure out what the issue is. Unfortunately im travelling for the next month so have limited trouble shooting options.
Background
- wife has been complaining that her phone battery dies quickly. I kind of dimissed her assuming it was in her head. she said it loses 10percent in standby mode in 1hr roughly. Shes been complaining about this for a week.
- yesterday at the airport her battery was at 12% and when we plugged it in to charge it wouldnt take a charge. Bolt icon did not come up and still said "connect charger" on the screen. Normally when connected the red Led comes on, but now it doesnt.
-our normal chsrging method is using and aukey 3port charger as fast charging mode.
Troubleshooting/diagnosis
- i have an s6 as well so i tested all the cables and chargers on my phone and it works. We even had the official samsung charger and cable but same issue.
- after the phone was completely dead, if you plug in the charging cable the charging bolt icon comes on for a few sec, the top left says "kernel is on seandroid enforcing" for a sec and then everything goes blank. Red charging led doesnt come on. So it seems like it detects the cable but wont charge enough to boot up.
- i was able to boot into twrp recovery but where its supposed to have a battery level its completely blank. Originally i was able to do this without any canles but then it wouldnt. My guess is that i orginally had a bit of juice and then it was completely dead.
-after leaving it plugged in for a sec, im able to turn it on where it boots and i can see it says 0% battery. It stays on for 5sec before turning off itself.
- i also tried plugging it into laptop, but laptop does not detect it. The phone does detect the power though and does the same as above but this time bolt charging icon stayes on for 1-2min before going off and seeing the "kernel is on seandroid icon". Once the seanadroid goes away nothing seems to happen. After doing this i was able to turn it on and it showed 1%. I thought this was promising but after trying this a few times ive never been able to get to 1percent again.
- with the brief charge thst i guess its getting, i was able to go i to twrp recovery and do a factory reset. This was with cable plugged in the whole time. Without cable in i dont think it would complete the action.
That about summarizes whats happened.
Ive concluded the following:
- charger and cables are ok and not the issue
- it is not the charging port since the phone does seem to be getting some juice bacause charging icon comes on for 2sec whenever cable is plugged in.
- its not a software/app issue since it wont charge even in recovery mode. Also factory reset was done and no luck.
My best guess is that the battery can only hold a 0-1% charge which is enough to register it being plugged in but not enough to do anything else. But if everything else is ok shouldnt it work when if the cable is just left in. This makes me think theres something else going on.
Any suggestions or theories would be much appreciated trying to decide if i should pay to get battery replaced.
Sorry for the long post. Figured it is best to give all info.
Thanks in advance!
Update June 3:
Hey everyone, just a correction on the above. It looks like it is able to charge in recovery (slowly). I realized that although there is no battery level during recovery, no charging led, and not booting up after being charged for a bit, maybe its just going slowly.
So i went into recovery and left it overnight on the non-fast charging and woke up after 8hrs and it was at 78percent!!!
Im not sure why it didnt go to 100% in 8hrs.
The phone still doesnt charge regularly when plugged in, so still need to fix that.
Do you guys think its a rom issue (only factory reset done before) ? I will see if i can get a rom for flashing.
Update 2:
Reflashed xtrestolite rom but still no luck. It wont charge.

Seems like a dead battery.
Sent from my SM-G920F using XDA-Developers mobile app

Battery.

Hey everyone, just a correction on the above. It looks like it is able to charge in recovery (slowly). I realized that although there is no battery level during recovery, no charging led, and not booting up after being charged for a bit, maybe its just going slowly.
So i went into recovery and left it overnight on the non-fast charging and woke up after 8hrs and it was at 78percent!!!
Im not sure why it didnt go to 100% in 8hrs.
The phone still doesnt charge regularly when plugged in, so still need to fix that.
Do you guys think its a rom issue (only factory reset done before) ? I will see if i can get a rom for flashing.
Update 2:
Reflashed xtrestolite rom but still no luck. It wont charge

Bump.
Went to the phone store and they said its probably not the battery but the ic chip for charging? This will cost 150, but doesnt include the screen if they break it...
Does this make sense since i can charge in recovery.
Thanks. Any direction or input is much appreciated.

Go on the local store and change your battery (if isn't in warranty)

Hi all, just wanted to update the post that the issue is semi-fixed.
I brought it into a repair shop who offered to diagnose the problem for free before paying to replace the battery.
He told me there was nothing wrong with it and not sure what my issue was. Plugs in the charger and lo and behold it was charging. He said he didnt do anytning to it except blow some compressed air on the port.
Im guessing the comporessed air cleaned out a short? So now it charges properly.
The issue remaining is that the pc doesnt detect the phone. It shows as charging on the phone but no conmection. Tried to install the latest samung driver (1.5.4xxx?) but no luck. On occation sometimes it says "usb port has malfunctioned" but other times nothing.
My s6 does actually connect, so definitely my wife's s6 itself and not comp. Im tempted to buy some comlressed air and give it ankther blow, but dont want to risk messing it up again. im pretty happy that it at least charges up.
Hope this helps others that might have similar issue.

Duraforce E6560 boot loop

I've had this phone 3 years and it worked well. It's an unlocked ATT phone so no OTA updates other than the standard app updates. It's on Lollipop 5.1. Been working perfectly fine until yesterday, I was watching the CBS app, when the phone rebooted. Now it's stuck on a boot loop and initally went to optimizing apps which it rarely finishes but the times it does, the phone just powers off. It then got into another loop later last night where it'd get to the Kyocera logo then reboot over and over. I let it do that until the battery died 2.5 hours later. Then I kept attempting to boot until the batter was entirely drained to the point it wouldn't attempt to power up any more.(battery is not removable on this model). I've now charged it up, trying to enter recovery mode with power+volume down. That doesn't seem to register. Tried volume up+volume down+power with no effect. Now after charging, it will do the reboot loop mentioned earlier to the Kyocera logo. If I plug it into a charger, it will go to the optimizing apps portion and repeat the above. At the optimizing apps screen, if I unplug the charger, the phone powers off immediately. It appears to be holding a charge according to the charge indicator and the fact that I can try to boot over and over unplugged. Any suggestions? Phone wasn't dropped or damaged in anyway. Very weird what could have happened.

An update: Phone finally got past the "optimizing app" phase last night sitting on the charger. Out of no where the phone booted completely. However, it only works while plugged in. If I remove the charging cord, the phone shuts down after about 2 seconds. Booting without charging cord results in the same boot loop. I've considered the battery has failed however when plugging in the charger, battery shows 100% and it will decrease appropriately over time. I'm thinking there must be a hardware issues at this point. Somewhwere in the charging/power circuit. Any other suggestions?

Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.

djhurt1 said:
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
Click to expand...
Click to collapse
I have the same exact problem. It started the crazy booting process in my pocket, and I did all the same things you did. Factory reset didn't correct the problem, so I'm think the battery has had a stroke. Sine your problem and my problem are very close to the same time frame, our phones are also probably about the same age, and its a quality control issue. Not bad quality control, just that these batteries were designed to last X number of months or cycles, and probably they died. Too bad, because my E6560 is the very best cell phone I have ever owned. Built like a tank and thank God for that.