I put DL09 on and then added stupidfast v1.54. Worked fine at first but now it thinks its plugged in all the time and if i turn it off it wont boot unless plugged in. Is this a hardware issue or an issue with the kernel? Thanks for your help.
Had the same thing too. Started from scratch with Odin. Good as new now.
So i plugged my phone in and the notification for the USB went away. I havent tried to reboot yet, but the battery meter keeps going from 68% which the phone is at to 100%. Its very odd.
Is there a way to reset the battery? That might be way off but i dont know enough about it really.
see this thread
http://forum.xda-developers.com/showthread.php?t=919770
My computer sees my phone. The battery stopped jumping too. Im gonna try to clean the port when i get home from work. I still need to plug it in to get it to boot. I was gonna try reverting to stupidfast 1.98 to see if the kernel is the issue. If it makes a difference i had flashed the circle battery and it started about 12 hours after i did so. I reverted to a backup i had saved. As this didnt completely fix the problem i assumed it was the kernel. Battery life is good with the kernel as expected but the phone just seems a little testy, some things are just a little laggy like its struggling. Any additional help would be greatly appreciated. If i cant find a solution im just gonna have to re-odin everything.
Well, seems it was a dirty port. Throughout the night things got better. Got home didnt have any rubbing alcohol so i stuck some heavy paper in there to try to rub off the port. When i tried to reboot it was hit or miss, when i held the power button the battery charging screen would come up as if i was plugging the phone in while it was off to charge. Could be due to weather here maybe i had salt on my fingers from the snow and i touched the cable before i plugged it in. However GPS isnt locking in any better than it did with DI01. Ill take it for now, vast improvement over this afternoon.
Related
Alright, so i sat down and did my first ROM flash (the clean update based off the DI01), then immediately downloaded ROM manager, and flashed the voodoo v0.2 with stock clock and voltage. Now every time I plug in the USB cable, I get the "battery is not connected" error. I have tried:
turning off phone, unplugging cable, pulling batt. then turning on, then plugging in cable
unplugging cable, pulling batt. while on, putting batt. in, turning on, then plugging in cable
... and every other possible configuration. I have left the battery out for 10 minutes now, and still no luck when I put it in.
suggestions?
EDIT:
waited a while longer, and it randomly worked. mods, feel welcome to delete this thread
It's been known to be related to phone being too hot.
hey..
That's what exactly what happened to me, so i actually flashed back to the stock rom
through the odin and wipe everything and started all over man..
I don't know..
Something is gotta be wrong with Voodoo kernel..
But in this way, i fixed it..
So i think im gonna stick with the lagfix for now..
and i guess when Dev comes out a different fixed verison, i'll take it again..
Good luck man
My phone was running at a fine temp to the touch, and I think the Battstat widget said it was at 30c, which should be fine. I think today i will flash over to a 1.1 or 1.2 Ghz voodoo kernel
Aidman...try this unplug the usb cord and shutdown pull the battery , then replace battery fire it up and charge....
post back results....
Voodoo busted my phone too. I could get the battery disconnected message to go away if I took the battery out and let it sit for a few minutes, but then it would come back later. It's a pain in the ass getting the message every time I try to charge my phone. Went back to stock until a fix can be found. My battery is nowhere near being hot when this happens, and I have only seen the message when using voodoo. I think I'll just wait for a later release. Too buggy for now...
Alright: for those of you who never read the full first post: THE PROBLEM IS SOLVED, thanks for everyone who decided to chip in. I had to try the battery pull about 10 times before it worked
Edit: I feel like an asshole after rereading my own post. I am sincerely sorry for my incredible stupidity.
aidman said:
Alright: for those of you who never read the full first post: THE PROBLEM IS SOLVED, thanks for everyone who decided to chip in. I had to try the battery pull about 10 times before it worked
Click to expand...
Click to collapse
I did read your post and understand the the problem wa solved for you, but not for me. I wanted to include my experience in case others are having the same issue. I was unable to fix the problem.
SnrSuave said:
Voodoo busted my phone too. I could get the battery disconnected message to go away if I took the battery out and let it sit for a few minutes, but then it would come back later. It's a pain in the ass getting the message every time I try to charge my phone. Went back to stock until a fix can be found. My battery is nowhere near being hot when this happens, and I have only seen the message when using voodoo. I think I'll just wait for a later release. Too buggy for now...
Click to expand...
Click to collapse
Not a lot of people get that error. I never did. And it never appeared either.
I had this issue too with the "no battery" indicator, and so did another individual in the lagfix release thread. No our phones were not hot, my own battery was nowhere near being hot, and we tried battery pulls, but that never worked. What worked for me was reflashing the voodoo 0.2 kernel on top of itself, the other guy tried that and had success with that too. You may give that a try, but I must say, that was only a temporary fix because after a while I got that annoying message back again.
I seem to have gotten rid of it for good, backed up all my apps in titanium, re-removed voodoo (be sure to get rid of "remove_lagfix" file when it's no longer needed), did a factory wipe, reflashed the stock Odin Kernel, did another factory wipe for the heck of it, then applied Voodoo, then reinstalled my data + app data using titanium backup (keep in mind I never wiped, restored, or returned system back to stock). Been running for a while, and I have yet to have the "no battery" annoyance and to be honest my phone boots quicker. So up to you, worked for me if you wanna give it a try.
Just wanted to update this thread. I have noticed that after flashing the voodoo kernel I too am getting the battery not connected error. However, I ONLY get this error when I have the usb cable plugged in when shutting down and starting back up again. If there is no usb cable plugged in when powering the device on, I have no problems with battery errors.
2 things stick out for me...
1. I had USB debugging on when doing the fix.
2. I removed the battery to go into initial Odin flash...PDA, etc.
The guide said my phone would reboot on its own, but it just sat at a blank screen. I had to unplug the cord and turn the power on. So do we have a fix for this yet?
i know earlier today my battery reading according tot he widget for setCPU said 66 degrees F.......which is kinda hard to believe seeing as the outside air temp is 80 degrees F outside and the inside air temp is 73 degrees F and my phone, although it had been sitting untouched for hours pluggen in inside, it was still on.....i cant believe the battery was running the best part of 10 degrees below ambient...even in idle state
Just flash the 1200 voodoo kernal u won't have that problem
Sent from my SCH-I500 using XDA App
Ok this will be a bit lengthy but please bare with me and read...
Ive been running Darkyy 10.1 EE for months now and every has been fine.
Easily a couple of days battery, no force close issues of any sorts... Everything has been perfect.
Then the other day i noticed my battery started dropping fast. NO THIS IS NOT A BATTERY DRAIN THREAD SO PLEASE READ ON.
I took my phone off charge the other night within seconds of hearing the beep for battery full and the fully charged icon in the top right of the bar stayed there for a few seconds ( like maybe 10 ) and then the battery level dropped to 80%.
I thought hhmmm thats not right but left it and went to bed.
6 hours later i woke up to 31% battery.
I thought something must be running killing my battery so i did a reboot...
Now this is where it gets weird. Read on my friends...
after i rebooted the phone it kept rebooting itself every 2 minutes or so.
I pulled the battery of for 30 minutes and put it back but i had the same problem.
When i got home i did a factory rest and wipe cache partition and decided to flash Darkyy 10.2...
I had the same problems as above only now when my phone rebooted the battery lvl would drop by 20% then next time raise by 5% etc etc
NOW THIS BIT IS SCARY BUT READ ON!!!
I decided to flash back to froyo with ezbase using repartition to see if that would help.
I plugged my phone into the computer and nothing happened!!!! My computer wouldnt recognise my phone at all neither would my phone start charging whilst plugged into the computer.
I managed to get my computer to see my phone by booting into recovery and and then download mode and flashed ezbase.
Again same problems. So i thought OK this might be an insurance job so i flashed it back to stock JPY from samfirmware.com. I plugged it back into my computer and my PC says "the USB device you have connected has malfunctioned and windows cannot recognise..."
I have had my phone unplugged over night but the icon on the bar is still there showing USB connected, and in the pull down shade there is still the option to connect USB to copy files.
I have plugged it in this morning and it started charging but windows didnt even recognise that there was anything attached at all! No beep no fault deviced attached message... Nothing!
Oh i would also like to mention that when i flashed ezbase and tryied to do a reboot i would get the battery icon for a second like if you charged while the phone was off and then it would power down again... The only way i could get the phone to boot back up was to flash EZbase again with auto reboot ticked!
Yes that was very long sorry and thankyou to those who took the time to read it.
If anyone has any thoughts on why this would have happened please post.
Do you think this is something caused by the custom rom or is this a hardware issue completely out of my hands?
Thank you again for reading!
Have you tried another battery?
Sent using geek power
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
gsw5700 said:
Have you tried another battery?
Sent using geek power
Click to expand...
Click to collapse
I dont think its a battery issue because the battery wouldnt prevent the computer from seeing the device would it?
mammenj said:
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
Click to expand...
Click to collapse
Im running stock JPY right now and have the same problem
Could it be a damaged usb port, so that it doesn't always charge properly, and doesn't always detect the phone correctly when connected to the computer? That might explain the problems... Especially if that port is getting worse all the time.
Can you get it to detect on the computer if you wiggle the usb plug to the phone? Have you tried a replacement usb lead?
It does sound weird. Hope you manage to sort it out.
Mike
Garbled meaning induced by swype!
don wadte time if ur phone dosnt work on stock then its the port tht got damaged and the hardware,,,,something wrong .....better go to a service center..don expirement ,cause it might damage it more
I have just dropped it off at the shop i bought it from and they are sending it away for repair.
2 weeks of nokia 3210 magic for me!
Thanks for replies guys.
Hey guys
Im looking for some help, although im not sure theres much that can be done...
These are the steps i did on an Australian p6810 stock device:
Install ICS using odin
Using temporary CWM, root the device
Flash CM9 to it
Wiped dalvik, batt stats, cache, factory restore (in both stock and cwm)
Boot to CM9 fine, but wifi doesnt work
Apply the wifi.zip fix as well as gapps
Boot to CM9 fine, but wifi doesnt work and gapps arent visible (or installed)
Applied the fix and gapps again, still didnt fix
So i decided to reflash CM9
Flashed CM9 and straight after did gapps and wifi.zip
Did a CWM factory reset
During the reset process (which took a loooong time), my device turned off (pretty sure it had plenty of battery)
BRICK
Now i cant turn my tab on at all. The screen doesnt respond, no matter how long or how many times i press the power button
Any help?!
have you try to charge your tab... then try to go to download mode... if it still working... flash stock ics again...
edan1979 said:
have you try to charge your tab... then try to go to download mode... if it still working... flash stock ics again...
Click to expand...
Click to collapse
its been charging for about half an hour. still not turning on so cant get to download mode!
I was reading a post on here about bricking and battery issue with the tab 7.7 which should be easy for you to find...Google it
On that post they spoke about taking the tab to any cell shop and having different battery packs put to it and this had revived the tab, the two guys who had got it working again said they had used a bigger voltage / amp battery to kick it back to life again. do a search and see what you find.
Now dont get me wrong, I have no idea how they got to do that as the battery is built in and the power connection is through the 30pin cable....maybe they plugged in the 30pin and used a transformer on the USB side to jump the battery back to life, I have done something like that before on a old phone that didnt charge and it worked, but its not the safest as wrong voltage could pop something.
Or the only other thing I can think of is the battery is totally dead or broken, in that case I would suggest a repair shop....but thats last on the list!
I am sure it might not have been enough charge before you strated...I had my battery die over night and it took a good 30min on charge to start showing any charge life at all.
Once you get the power working, I am sure we can un-brick your baby for you
slide200sx said:
I was reading a post on here about bricking and battery issue with the tab 7.7 which should be easy for you to find...Google it
On that post they spoke about taking the tab to any cell shop and having different battery packs put to it and this had revived the tab, the two guys who had got it working again said they had used a bigger voltage / amp battery to kick it back to life again. do a search and see what you find.
Now dont get me wrong, I have no idea how they got to do that as the battery is built in and the power connection is through the 30pin cable....maybe they plugged in the 30pin and used a transformer on the USB side to jump the battery back to life, I have done something like that before on a old phone that didnt charge and it worked, but its not the safest as wrong voltage could pop something.
Or the only other thing I can think of is the battery is totally dead or broken, in that case I would suggest a repair shop....but thats last on the list!
I am sure it might not have been enough charge before you strated...I had my battery die over night and it took a good 30min on charge to start showing any charge life at all.
Once you get the power working, I am sure we can un-brick your baby for you
Click to expand...
Click to collapse
Thanks for the advice! I'm not sure it's a battery problem though? Is there anyway I can tell?
To be honest, the only way you are going to know if the battery is the issue is if you take it for a battery swop....will be a samsung outlet and cost you. I have heard that some 7.7's that have done wipes from in CWM and not the 3e recovery have caused bricking, it may be that this has happened to you. please check the other brick posts on here and I am sure after reading them all you will have a better idea of what is going on. before I do anything on mine I check all the bricking posts to see what could cause the problem and stay away from those changes or mods....if possible
sometimes plugging it in and out of the wall charger and then computer and back again to wall might help, I dont promise anything.
how long have tried holding the power button, and have you tried holding the power button while pluggin it in....
let me know what happen's please....
slide200sx said:
To be honest, the only way you are going to know if the battery is the issue is if you take it for a battery swop....will be a samsung outlet and cost you. I have heard that some 7.7's that have done wipes from in CWM and not the 3e recovery have caused bricking, it may be that this has happened to you. please check the other brick posts on here and I am sure after reading them all you will have a better idea of what is going on. before I do anything on mine I check all the bricking posts to see what could cause the problem and stay away from those changes or mods....if possible
sometimes plugging it in and out of the wall charger and then computer and back again to wall might help, I dont promise anything.
how long have tried holding the power button, and have you tried holding the power button while pluggin it in....
let me know what happen's please....
Click to expand...
Click to collapse
So i took apart my tab in hopes i could do a battery pull:
http://www.jtagbox.com/jtag-news/ri...y-tab-77-unbrick-boot-repair-supported-world/
and no luck, it doesnt auto power on
Im considering doing jtag... but hmmmmm
https://www.dropbox.com/sh/rqhhgs34vuzt4u4/fGwL0TiSYc
i pulled out the power/battery cable, plugged the tab into the computer and then plugged the power in. nothing.
it also didnt work when i plugged it into the wall
When plugged in my wifi chip gets warm... hmmm
@Scottyn...
Dude, you need to do the swopping of power from wall socket to computer then back again and again and again......all the time while doing this holding the power button in.....try it
Also, if you have puled the thing apart now you should be able to test the battery for power with a volt meter or something....
does the battery have power...
does the battery get power from the cable or pin running to the battery?
Can you turn the tablet on with a different power source to the battery terminal on the phone?
I would check these things first, then hold thumbs....I dont know, if it's not the battery then it may very well be a dead hardware issue and not a data issue or fried memory as they will normally boot the tablet to a point.....
May very well be the battery cooked
Im too scared to attach a an external powersource to replace the battery. I have the equipment, but it could easily fry the rest of the board
Ive closed the device back up, so ill have to reopen it before i chuck a voltmeter on the batteries
and ive swapped from computer to the wall about 10 times (swapping every 5 seconds). Nothing
Plus; if i diagnose the problem as a fried battery then cant really do anything about it
scottyn said:
Hey guys
Im looking for some help, although im not sure theres much that can be done...
These are the steps i did on an Australian p6810 stock device:
Install ICS using odin
Using temporary CWM, root the device
Flash CM9 to it
Wiped dalvik, batt stats, cache, factory restore (in both stock and cwm)
Boot to CM9 fine, but wifi doesnt work
Apply the wifi.zip fix as well as gapps
Boot to CM9 fine, but wifi doesnt work and gapps arent visible (or installed)
Applied the fix and gapps again, still didnt fix
So i decided to reflash CM9
Flashed CM9 and straight after did gapps and wifi.zip
Did a CWM factory reset
During the reset process (which took a loooong time), my device turned off (pretty sure it had plenty of battery)
BRICK
Now i cant turn my tab on at all. The screen doesnt respond, no matter how long or how many times i press the power button
Any help?!
Click to expand...
Click to collapse
We had a similar faith. It was when this wiping thingy messed up my Tab. My only consolation was that my Tab is under warranty and did some make up story at the service center. Had replaced the motherboard and now up and running. I'd promised myself that I'll limit my "genius" with rooting and flashing an official fw. Custom rom is a big no for me, no matter how great and stable it was. The wiping part is like kiss of brick. Yes, i know...there's a disclaimer.
sweet. Ive decided to send it all back over to australia. annoying, but ill get a guaranteed fix
I think ill stick to stock ICS from now on
scottyn said:
So i took apart my tab in hopes i could do a battery pull:
http://www.jtagbox.com/jtag-news/ri...y-tab-77-unbrick-boot-repair-supported-world/
Do you mean you opened up the tabs case?
how did you do this?
any pics?
I ve read you have to lift the screen from the back cover..
It scares me to think about levering it and cracking the screen or something..
Click to expand...
Click to collapse
Hello all,
I recently installed Cyanogenmod JB (v5 then to v6, issue happened on both) for the transformer and it seemed to have some really bad battery issues. It would die really fast and the dock stopped charging. I was able to get it charging again after a hard reset, but then it stopped after a full drain again and hasn't been able to get it to take a charge since. The tablet as well has been acting really flaky as well. It stopped taking a charge and wouldn't turn on, but randomly would start taking a charge again, completely drain, take charge, drain , etc. and now it will only randomly turn on while plugged in for a few minutes then die (about once a day). I have done numerous hard resets when I can catch up powered up, taken apart the tf101 and unplugging the battery and plugging back in, holding down every possible combination of buttons, and even tried freezing the power brick. I also tried booting into APX, thinking I managed to get into a loop somehow, but nada. I can tell the tf101 is getting power from the wall because if I put my ear really close to the port on the tf101 I can hear the distinct hiss of power being delivered to the battery and lack-there-of when it is not plugged in.
I've run completely out of ideas at this point. I feel like it has to do with the fact that the tablet battery went to 0%, but I'm not positive. Considering it happened damn near in toe with the Cyanogenmod install, I feel that has played a role in it as well.
I'm wondering if anyone else has something I can try. If I can catch it randomly powered on (who know if it will even do that anymore) I was going to try and flash a new rom and kernel really fast and hope I don't lose it. But I feel that is very risky. So I'm open to all suggestions anyone has.
Thank you in advance! =D
Just an update:
I was able to flash the AOKP ICS rom and it seems to boot more regularly, but the battery is still refusing to charge. Wiped battery stats, cache, factory reset, cold boot, the works. Just says "Charging, 0%" on the homescreen.
Thanks again!
Another update. I was able to start getting a charge on my tf101 after flashing the ICS aokp rom. However, it is doing a trickle charge. Not sure why or how, but I suppose my power brick decided to die at the same time of me flashing the JB rom. I've tried the freezer trick, but no go on that. I was reading around and I saw that you need a usb 3.0 cable to get the 15v charge, but that didn't seem quite right, considering I was getting 15v with my USB 2.0 cable. Anyway, looks like I'm heading over to Amazon to pick up a new charger.
Thanks to everyone who checked out my issue. I'll leave this here as a brain dump for anyone else who may have this issue.
It's most definitely your charger man. It seems to be a common problem with these tablets. Mine died too so I just made my own from a spare 12V power supply I had laying around and a piece of USB cable.
The title says it all. For extra information:
So I got the battery full using universal direct battery charger and put it back. Switching it on without the charger plugged in won't work but switching it on with a charger plugged in does. You can even unplugged it after that vibration when turning on. That means, it's not the battery... you can even see the battery's full after booting successfully.
Not only that, with or without the charger, the S4 would heat up so much. No it's not the apps, even in safe mode or just while booting it would start to heat up. It wouldn't stop heating.
At first I thought the problem was the switch cause it won't turn on. Then I figured out it would turn on... but with the charger plugged.
Hmmm, any idea what cause it? It just happen all of a sudden one day. I'm thinking that, even if the switch or the port looks fine they may be the cause. Short-circuit I guess. Or I don't know, just my wild guess. If you experienced this one before, please share you experience and how you fixed it.
I'll add the edit I made on my reply here to make it easier to read.
EDIT: The heat is coming from the upper right area. Very close to where the switch is and sd card slot. Do you think it's the switch? If it's the switch, it's working well. No sudden reboots or shutdown due to the button acting like it's pressed when it's not, etc etc
EDIT: FIXED​
Flashed Albe95's LolliRom http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564 and also flashed Imperium Kernel (afterwards... because I thought I already did -_- )
At first I thought I would switch ROM to see if it's really the ROM that caused my problem (Stock with AEL kernel).
I downloaded Albe95's ROM and it took some time before it really boot successfully. On the thread it says that it would after 15mins, but mine after 15mins is still not booting. I flashed many times thinking that I made a mistake, like I forgot to wipe, etc etc.
The overheat problem was still there while it boots. It gets really really hot. I thought it is really a hardware problem now, I flashed a new ROM and therefore the kernel was changed, and if it was changed and it still has that problem my conclusion was right.
BUT...
I put it in the freezer to battle the heat. When I took it from the freezer, the phone's off. I thought the coldness what made it turned off. I took it, charged, and turned it on. And when it turned on after plugging it in... the battery's empty. It was around 50% when I decided to boot again and wait.
While it is still cold, I tried to turn it on again and wait now this time for it to boot.
Albe95 said it would take around 15mins only, but mine did boot past 15 mins. Can't blame me why I thought it's stuck on bootloop for many times. Now I'm thinking if I have only given Imperium ROM a chance... HAHAHAHA too lazy to flash and wait for a long time again.
Please hit thanks if I helped someone in the future with these issues.
what s4 model, rom and kernel do you have ? any mods ?
the battery could still be the problem. can you test it with another one, a friends maybe ?
Maybe a short circuit by sweat water that got into the phone. Open it up, take the board and other other easily removable components out and clean them with Isoprophyl(cleaning alcohol) and a new/clean soft brush, reassemble and see if it helped.
Backe888 said:
Maybe a short circuit by sweat water that got into the phone. Open it up, take the board and other other easily removable components out and clean them with Isoprophyl(cleaning alcohol) and a new/clean soft brush, reassemble and see if it helped.
Click to expand...
Click to collapse
This might do. Did not thought of this.
It's more on hardware I guess... Not kernel or ROM problem. Or, ok fine, just to be sure I'll try to flash Albe95 ROM. I am on Stock before and accidentally wiped the system partition also while trying to factory reset via recovery instead of data, cache, and dalvik only. Even without the ROM, it overheats very much.
EDIT: The heat is coming from the upper right area. Very close to where the switch is and sd card slot. Do you think it's the switch? If it's the switch, it's working well. No sudden reboots or shutdown due to the button acting like it's pressed when it's not, etc etc