Hi all!
So now i have this strange boot problem.
My i9000 came on FRoYO with totally drained battery. I charged to full and then could turn the phone on.
It connected to my WLAN and everything seemed fine. I did not test with my SIM card inserted but thought it would not be necessary because
i wanted to root it anyway.
So i got heimdall on my Linux and followed the instructions given here:
http://forum.xda-developers.com/showthread.php?t=1196179
I flashed the XWJVZ version and it seemed to be o.k. like above.
Now i followed the instructions on Cyanogen website on how to root the phone.
I got the Semaphore recovery kernel flashed and the CM11 M5 snapshot plus gaaps.
Everything turned out to be fine but only with the charger connected or the usb into the pc.
Finally i got everything up and running and inserted my SIM card and booted up again.
This time without charger.
I noticed the "empty battery symbol" flashing twice, blank screen, flashing etc..
Connected the charger, it starts charging and shows 90% charge.
Disconnected the charger. Booted, Everything fine.
So i began to read about the problem and tried a few things.
I used the battery from my second i9000, which is on CM10.2 running nicely.
I cleaned the battery contacts and the usb.
I re-inserted SIM several times.
No avail.
The phone sometimes shows empty battery but boots up on looong press of power on.
But anytime there is no cell communication, it shows "no baseband" and no IMEI.
I can connect a charger or a usb on the pc and -poof- SIM PIN is required to get on and everything is fine.
Baseband is shown. Correct IMEI as well.
So i thought maybe something had gone wrong during flashing. I removed "batterystats-files".
I wiped everything and flashed again.
I downgrade to stock rom with heimdall, see above and tested with SIM.
It seemed to be o.k. but i have to admit that i don't know if i had sit the phone in power off state long enough to see.
I upgraded to CM9 and got stuck with the problem.
I upgrade from CM9 to CM10.2 which was a drag because of the new partition layout.
Finally got it working with the same problem.
One difference: After shutdown the screen is blank and no "empty bat symbol" is shown.
If i connect the charger, the empty bat is shown flashing, going away, starts charging. Boots o.k. if done with charger.
Also:
A reboot alsways works if done immediately after shutdown!
State now:
I can make phone calls and everything after this until battery is low. I can charge in ON state and continue forever.
But every time i shutdown the phone and let it sit for some minutes it has the "inside empty bat situation" which will allow to boot
but does not recognize the SIM card.
I am really stuck on that.
My second i9000 came prerooted and ran on CM11 nightly which i downgraded to CM10.2 stable for productive use.
This is phone is fine with the battery from my problem child.
Any advice?
Thanks in advance,
Frank
found this thread, not sure if it'll help http://forum.xda-developers.com/showthread.php?t=1923225
Nearly, but not exactly
pryerlee said:
found this thread, not sure if it'll help http://forum.xda-developers.com/showthread.php?t=1923225
Click to expand...
Click to collapse
In between time i went back to 10.2 stable without gaaps. Nothing much changed...
Alas:
Thanks alot for the quick response.
Nearly the same case here. Maybe the solutiion is posted in #31. Charging and draining to empty or so.
As said if i connect a charger the device boots, i can enter my SIM Pin and everything is fine.
If it is booted up i remove the charger, battery still over 80%. Everything works.
I shutdown, wait for a minute, power on.
Now wait, after the last clean wipe and install: It does not bootloop to battery empty. It boots up to the lock screen but without asking for the SIM Pin.
If i do nothing the phone keeps booting after a short while.
If i unlock the screen i can use the phone, including WLAN etc..but cannot make a call because baseband is empty.
Connecting the charger or usb in that case immediately locks the screen and asks for SIM Pin. Everything is fine...
Strange.
So is it an original Samsung battery or 3rd party? And it works perfectly fine in another i9000?
tetakpatalked from the legendary i9000
tetakpatak said:
So is it an original Samsung battery or 3rd party? And it works perfectly fine in another i9000?
tetakpatalked from the legendary i9000
Click to expand...
Click to collapse
Yes, both batteries are Samsung. Old, though.
Well, during the day, after some more testing i can reproduce as follows:
Stock firmware either flashed with Heimdall or ODIN result in no problems at power-up.
Rooting no problem
CM works fine with CM 9.1 stable. No more empty battery sign and every boot SIM Pin is asked.
Going from CM9.1 to CM10.2 stable results into trouble. Something happens on repartitioning.
The phone boots several times .
After that, reboot system, the system starts but forgets to aks about SIM instead giving me the message
to read the manual on how to insert a SIM
I am just going to give it a shot again flashing stock to CM11 M6 built in one big leap.
Wait: It just boots into the new system.
Wow: It is asking for a SIM Pin. I give it and the rest of the primary setup is localized to German.
What is this? Do i dare to reboot after the ROM has settled? I guess i must...
This time something is different. The whole process from going stock to CM11 was done without charger applied.
It works flawlessly.
Hold your breath: I am going into shutdown.
Will a nandroid backup BEFORE next reboot.
SOLVED: Battery empty loop etc.
Dear readers: My issue has been solved.
To sum it up:
1.
The flashing battery symbol has not necessarily something to do with the battery state.
If you notice that your charge is good either when connecting a charger and check the bat symbol or if the system is up than it
is not the cause of trouble.
2.
Wiping batteriestats files is senseless. I see them on adb or on the file browser. They are always made new on time
a charger is disconnected. Maybe if one wants to calibrate the battery notifier it makes sense.
Not for this problem.
3.
If the battery is charged and you see some kind of battery bootloop then it really is a bootloop.
The only remedy is to go back to stock and see if it is there, too.
IF it is there, then most probably there is something worng in the hardware, i guess.
So clean your battery poles with a fine grain of sandpaper (carefully!!!) or use a sort rubber we use in school to erase
uneraseable ink (do not know the word for "Tusche", sorry).
Clean the usb port with pressurized air used for cameras. Apply a small (!) amount of TESLANOL or Tuner spray or something else
for gold contacts.
Do this also for the contacts of the SIM and battery inside the case. Use Q-Tipps to apply and dry thoroughly.
Replace your battery if nothing helps.
On stock firmware no battery bootloops ever occur, i guess otherwise cellphones would not sell.
4.
After going back to stock root your phone as usual.
You should confirm that one of the first stable CM or other mods reported to work fine work fine for you, too.
Go back to stock again and try large leaps through your ROMs.
I guess this is the way to go, finally.
In my case coming from CM 9.1 to 10.2 did something. I noticed the phone boot several times during flashing, due to repartitioning always
coming back without fault but in the end not fully functioning.
So my solution, after the battery bootloop went away which i tend to say is the result of charging and cleaning and going back
to stock WITH SIM and testing is:
Make huge leaps. It has to work or dump it.
If anything new occurs i will post in this reply.
Hope someone else can find valuable information in this thread.
Make yourself familiar with Heimdall. I found it to be much easier to use than Odin. But it depends on if you find the proper files to flash...
Best reagrds,
Frank
Related
I'm trying to get my Dream back to where it was just after rooting and flashing CM 4.2.8. I wiped my rooted Dream and flashed "signed-dream_devphone_userdebug-ota-14721.zip" then flashed "update-cm-4.2.8-signed.zip". That all went fine.
But a strange problem... The battery stays at 0% (The battery's voltage is 3.92v out of phone on DMM, a 3.7v nominal Li-Ion should be 4.2v when full) and if I unplug the USB cable it shuts down, the phone will also ONLY boot when connected to USB.
Also if I select reboot from the OS, it will switch off but not restart.
Do I have to discharge the battery out of the phone? (I have Li-Ion/Li-Po charger/discharger)
Or is there another way to get the phone to recognize the full battery?
Weird, my Battery Info (in spare parts) reports that the battery voltage is 2.465v whereas I've measured it at 3.92v...
EDIT: Battery Info reports 2.480v when battery fully charged at 4.2v and 2.465v when discharged to 3.0v???
Please can someone send me a copy of their batterystats.bin file, I want to see if changing it makes a difference, I've tried everything I can think of to get this right including 'rm'-ing the file and/or wiping immediately after/before unplugging, otherwise the phone shuts down within a few seconds.
It's 13KB, please send it to conanony[at]gmail[dot]com
I would like to help you, but i dont know how to get that file lol
pardus what recovery do you use for the phone?
if you use RA's recovery you can delete the battery info, i believe this may help your problem. also try cycling your battery
charge full to 100%
drain full to 0% where your phone wont turn on.
keep turning it on untill the G1 logo wont popup anymore
that's just my problem, the second I remove the charge/USB cable the phone shuts down, before that it never charges to full despite the battery actually being at 4.2v (shows charging(0%)) and can't drain it to 0% as it reports it's at 0% and immediately shuts down, so catch 22.
>djluis48: you can use Droid Explorer (http://de.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=37999) to get the file, it's in /data/system/
Tried to flash RA's recovery from fastboot and get this: writing recovery.... FAILED (remote: battery low)
managed to flash RA's recovery and wipe the battery stats with it, however it still had it's not charging problem, then I left it over night and it charged to 30% but after removing the battery to put the sim back in the battery went back to 0%.
(btw, Battery was fine before the flash)
I suspect that this problem is the cause of many "black screen" and "I think my phone is bricked" issues.
The phone sees a full battery as empty and therefore won't boot, one way to test is to try boot into recovery with power/usb connected. One symptom I have is very short red LED flashes when trying to boot without power/usb connected and when connected a continuous red LED, then when trying to boot with power/usb > longer red flashes before eventually booting.
Well seeing as I'm talking to myself I might as well carry on...
Have managed to get the phone to boot 3 times (over 3 days) showing the correct battery values including temperature BTW, which shows as 67.7°C (153.8°F!) continually (with battery at room temp.) however when removing the battery to replace the sim which was in an old phone it was back to square one
I can't seem to replicate the actions I did to get the normal values back, one occasion was after I pressed power, menu and send together which then flashed the fastboot screen very briefly and booted after that.
Very weird, wish someone with a working knowledge of the Android system would chime in here?
pardus said:
Well seeing as I'm talking to myself I might as well carry on...
Have managed to get the phone to boot 3 times showing the correct battery values including temperature BTW, which shows as 67.7°C however when removing the battery to replace the sim which was in an old phone it was back to square one
I can't seem to replicate the actions I did to get the normal values back, one occasion was after I pressed power, menu and send together which then flashed the fastboot screen very briefly and booted after that.
Very weird, wish someone with a working knowledge of the Android system would chime in here?
Click to expand...
Click to collapse
try to wipe m flash different rom
BrutalHoe said:
try to wipe m flash different rom
Click to expand...
Click to collapse
Wiped and tried original ROM - RUU_DREAM.exe, reports voltage below 30%, can't continue (I know the battery is full, I just charged it from empty and it took 1153mAh), I then tried wiping (everything) and flashed CM 4.2.12 from 4.2.8 - still the same. Voltage on phone reads 2.442v, DMM on battery reads 4.157v...!!
Wiped and flashed SuperD 1.5.1 ROM, still the same problem
Phoned local HTC agents, they say must bring it in but if it doesn't have the original ROM on it then it's out of warranty...
but I can't load the original ROM using RUU_dream.exe because it won't let you flash when the phone reads a full battery as flat...and despite searching high & low I can't find a Leaf (local distributer) DREAIMG.nbh file which may be similar to a rogers but I don't want to take the chance, anyway I can't find an original DREAIMG.nbh for a rodgers only a RUU_dream.exe.
So that's it, not a brick but unusable unless connected to power...
Tried DREADIAG.nbh (HTC's diagnostic program) from the sd card via hboot, no luck, reports battery too low but I know it's charged, seems my options are running out...
same problem
most interesting information in the second paragraph.
hey dude, im having exactly the same problem, but im in a bit of an odder situation still. i've been trying to get back to factory setting so that i could see if it works then.. (i've had mine so long its out of warranty anyway) i've never even gotten mine to say it has any battery since this problem started, i even went to the trouble of ordering a second battery from ebay to see if it works.. i mean i had two batteries to begin with one extended one regular. i thought maybe my extended battery went bad so i put the regular one in but still no luck, but i thought maybe it went bad from less than ideal sorage conditions, so i've got another one on the way. sucks to know its probably just wasted money.
Anyway, heres my situation. I was trying to get back to factory so i started by flashing the original recovery image (since i was coming from an inofficial one, it was no big deal) i know know i should have flashed the spl first.. because now the recovery wont let me flash anything unofficial, and i dont know that i have an offical update.zip from t-mobile. also i dont know if the hard spl somehow requires an unofficial rom to be flashed. anyway right now my recovery image wont let me flash anything it seems. i have the hard spl, official recovery image, and my rom is dream_devphone-userdebug 1.6 DRC83 14721 test keys.. i have no idea who even made that one.. i think haykuro or the dude???? (my humblest of appologies for not giving proper credit if this is someone else's work)
i think at this point my phone may just be a usb modem and nothing else. im also like a year away from an upgrade so im back to my old hp 6315 or mda.. but i've lent that to a friend.... i also have an old mpx 200 with some awesome firmware (also thanks to xda developers love you guys) or a super old sony-ericsson t86i... i really wish there was a way to put android on my hp 6315 but i think pigs have a better chance at flying than that coming to fruition. anyway if anybody else has this problem and figures it out, please let us know what to do.
My phone started to do this a few days ago, it's driving me nuts. I don't know what the heck is wrong with it.
One way to tell for sure if it is this problem, try the steps here: http://forum.xda-developers.com/showthread.php?t=614987
I am in the same boat. It just came out of no where. I have flashed roms, changed sp,l wiped battery stats, and tried to change back to DREAIMG and like you guys said it says low voltage.
Has anyone had any luck at all with this?
Hey guys, recently I've been having a problem with my battery. I've tried different roms and still have the same problem.
if the battery is fully charged, half etc and the phone is restarted, the battery screen shows up and shows an empty battery, turns off, restarts and shows the empty battery screen again, turns off, restarts and keeps doing this until I plug the charger in. once I plug it in, the battery shows full, or what ever the current charge is and phone starts up fine again.
I've noticed that sometimes the battery percentage goes up without being on charge or even sticks at a percentage for a few hours then drops a lot.
Has anyone else had this problem or know how to solve?
Sent from my GT-I9000 using xda app-developers app
supersteve939 said:
Hey guys, recently I've been having a problem with my battery. I've tried different roms and still have the same problem.
if the battery is fully charged, half etc and the phone is restarted, the battery screen shows up and shows an empty battery, turns off, restarts and shows the empty battery screen again, turns off, restarts and keeps doing this until I plug the charger in. once I plug it in, the battery shows full, or what ever the current charge is and phone starts up fine again.
I've noticed that sometimes the battery percentage goes up without being on charge or even sticks at a percentage for a few hours then drops a lot.
Has anyone else had this problem or know how to solve?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I have found alot on my problem surfing through the forums with many saying they have solved the problem by flashing CM10 mod. Another that i found was a flash with "param.lfs". Apparently this solves boot problems but I cant see how to use this file.
Any help with a step by step guide or just any help at all is very much appreciated
supersteve939 said:
Any help with a step by step guide or just any help at all is very much appreciated
Click to expand...
Click to collapse
just select it as PDA and flash with Odin3 , download from My Android Solutions
Thanks for your reply, param fix didn't solve my problem. The first rom I installed ( before I found the wonderful world of xda developers ) was this one:
aokp_galaxysmtd_jb_build-2.zip
Which I got from a site called "ibtimes"
(I've tried to post the exact link but I need to make 10 posts within the forums to get this option)
Since then I've had this battery boot loop problem. Restart works fine, but power off and powering back up gives this infinite boot loop. is it possible that this first rom has corrupted my phone?
Sent from my GT-I9000 using xda app-developers app
supersteve939 said:
is it possible that this first rom has corrupted my phone?
Click to expand...
Click to collapse
Doubt it, it would more be due to wrong flashing procedures , anyway have a number of options to get over bootloops in My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card...make sure you have more than 50% battery charge before you attempt any sort of flashing.
I have looked in depth through the "My Android Solutions" and tried flashing a 512.pit and also tried a new semephore kernel without success, I still had the battery bootloop.
My phone does work if started with charger plugged in but its a worry if im out and about and the phone dies. theres no way i can restart it without the charger boost.
so.....
Im looking at the Recovery Kit now.
"i9000 Rescue Rescue Kit for i9000 using heimdall packed by ldq"
I have never used heimdall and the files within the rescue kit are confusing to know how to use them correctly.
I have looked within the forums for a "how to" guide using Heimdall but it feels like its over my head, and to be honest, it seems that if i make any kind of mistake i could hard brick my phone which scares me :crying:
:fingers-crossed: A total NOOB guide would be so greatly appreciated, or if there are any other solutions besides using the rescue kit Id love to know about them.
Thank you very much for your assistance
supersteve939 said:
I
I have never used heimdall and the files within the rescue kit are confusing to know how to use them correctly.
Click to expand...
Click to collapse
You can use the EZbase with root or Darkys, it uses Odin and has guide , all of them are rescue kits or even a JVU upgrade ROM (also mentioned in the top)
I tried quite a few stock roms with the same result, darkys 10.2 EE and darkys 11, 4.0.4 ICS and again same results. This morning I went back to the GB stock rom ( " I9000XXJVU_I9000OXAJVU_OXA " with root file " CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS " ) and had the same results, battery screen bootloop after power down. :crying:
however...
After 7 hours normal use i powered the phone down and powered back up ( thinking another vain attempt ready to see the dreaded battery loop screen again ) and found the problem had completely cleared!!! Phone started like it normally should!!!
Very strange. I was ready to try a new battery and now there is no need. I'll keep powering down and powering up over the next 24 hours with different charge percentages to make sure the problem has 100% cleared it's self. :victory:
Will post back in 24 hours to confirm for anyone interested.
Thanks for the guidance xsenman, seems as though going to and from different roms with the 3 wipes each time actually solved the problem!!!
Too hasty with my last post.
Phone has started looping up at boot again with empty battery screen.
Tried another battery with the same results.
For it to work for most of the day normally booting up and to suddenly start playing up again leads me to believe that its some kind of battery stat problem.. maybe??
it powered down and powered up again fine from 100% full down to around 16%. lower than 16% and the phone looped with empty battery screen on powerup.
The battery percentage jumps quite alot after a restart, sometimes as much as 40%
surely it has to be battery stats being messed up?????
There are alot of procedures to reset battery stats on the net and a few in these forums.
I'll give some a try.
If anyone has a sure way to reset batt stats then i'd like to know please.
Thanks to anyone with help.
suggest you clean your Battery contacts on phone and Battery with cleaning alcohol and try to keep battery firmly in place with scotch tape or folded paper and give it a try
Hi!
I had the same problem.
I fixed with a sheet of paper that do pressure under the the battery for better contact with pines of the phone.
Good luck.
Enviado desde mi GT-I9000 usando Tapatalk 2
Thanks for the replies.
I've cleaned with electrical contact cleaner and also tried the paper trick having the paper under and around different parts of the battery, still the same, empty battery screen loop.
It only happens after power down then attemped power up, fine when just a reboot is selected though. When powering down it actually doesn't shut down, it goes into this infinite empty battery loop. I'm beginning to think some kind of hardware issue??
But also, i only started to get battery issues after my first ever custom rom install Cm9 jellybean which was not from xda. Sorry for repeating myself, im just completly stumped with this issue.
Sent from my GT-I9000 using xda app-developers app
i have the same problem and i dont know what to do to solve it!!! :-S
it started when i flash a official cm10 nightly... then i flashed the stable cm9.1 and the problem disappeared... after a few days i decide to give cm10 another try and the problem started again... now i cant make this go away... i've tryed flashing other roms, even a GB JW4, and the same thing happen. I dont know what to do anymore!!!!!!
I feel the same way. It must be quite a rare problem.
Its very frustrating.
I just tried flashing that first rom i used. aokp_galaxysmtd_jb_build-4.zip which is a CM rom thinking maybe the first time i flashed was an improper flash.
still have same results.
Then tried Darkys 11 as they claim to fix bootloop problems but still have the same result. So im back to 2.3.6 GB JVU stock.
I really think we have somehow damaged the hardware by installing these CM roms.
Its as though the part in the phone which looks for battery charge in order to boot up fails and just shows battery empty until the charger is used, and also refuses to shut down.
How strange. How frustrating!!!
kilas_bff... I think we're stuck with our problem my friend. I have just brought a portable charger which i'll carry around incase my phone needs started after these battery screen loops, just to give it that initial boost of power to restart. Got mine from Ebay for £8 GBP which is about $12.50USD.
I just dont like the thought of really needing my phone while its in a battery loop. this portabe charger will be very handy and give me peace of mind.
Any more ideas on this is greatly appreciated. I'll try anything. :fingers-crossed:
As with all things funny have you gone back to a clean install of a stock rom via Odin? Run it stock for a bit and see what happens?
sent using my fat fingers from the robot eating the apple...
Stock is back in as of today. will take your advice and run it for a while and see what happens.
Another thing ive just noticed.... before going back to stock i performed the usual 3 wipes a couple times and even went as far as formatting system.
The picture I have attatched with my reply is what I was confronted with:
could these failures be causing my phone to act as it is?
I have searched about for clues and didnt come up with much. My forum searching skills need sharpened I think.
Thanks for the replies.
think it was just a bad flash initially...
stock rom and pit flash should see you right. leave it on stock for a day or so to see what happens then flash a kernal with cwm and begine the update to JB.
try this
http://forum.xda-developers.com/showthread.php?t=1418135&page=2
or make a google search for: format_volume rfs format failed
kilas_bff said:
try this
http://forum.xda-developers.com/showthread.php?t=1418135&page=2
or make a google search for: format_volume rfs format failed
Click to expand...
Click to collapse
Hello, Thanks for the reply.
Before I go on.....the factory format method I used before was not from recovery mode but from the dial pad *2767*3855# (PLEASE DO NOT TYPE THIS CODE IN UNLESS YOU ARE PREPARED TO HAVE THE PHONE COMPLETELY RESET TO FACTORY)
That's when I got those 4 failures mentioned before.
I tried your suggested solution but not sure it has solved the problem, its basically reset the phone to Factory settings but had alot of unexpected errors and app shutdowns. Before I flashed the stock back on I went into CWM recovery, went to 'mounts and storage' and formatted every option apart from the 'Format Boot' option. All formats successful.
After another flash with 2.3.6.GB stock I tried the dial pad factory format again out of interest to see if I got those same 4 errors and BINGO!! all went without any problems!!!
So that problem is solved.
But my initial issue remains.....After power down it doesn't actually power off completely, just infinite empty battery screen loop until charger is used. :crying:
I'll stick with the suggestions from 'creative0100' and stay with stock for a few days to see what happens then flash a kernel, thinking semaphore kernel and go from there.
:fingers-crossed:
its been nearly 5 days since stock has been on, rooted today and put semaphore kernel on and still have that empty battery bootloop. Won't power up without the charger boost to kick start it back into life.
Does anyone have anymore suggestions please? I've looked quite deeply within the forums and some have had a similar problem but no real solutions as yet.
Just editing my post as it seems that the phone powers down and powers up totally fine when the charge is below 35% - 40%. If its above it'll bootloop showing the empty battery screen.
Ive tried charging to 100% overnight and then resetting batt stats as the charge percentage jumps about alot. seems very confused showing different charge values now and again and even charging when it aint plugged in!!!
Seems something in the phone is not reading the battery correctly.
I really am stuck on this and cant figure out how to recalibrate the battery so it acts normally again.
Sent from my GT-I9000 using xda app-developers app
I have the I9000 . Until this morning I haven't had any problems with my phone. I was on C-ROM KK 5.8 (not that it affects my problem) and last night I left my phone to recharge. This morning I've unplugged my phone from the wall charger and made a reboot (my morning routine). Strange thing happened. The phone went into the phone off connected to wall charger screen mode but showing that the battery is empty. I took my battery out and now every time I place it back in my phone, the screen goes on showing empty battery or it's checking for battery level, without even touching any buttons. If I try to go from that screen to make my phone boot using the power button it does not react. I can't go in recovery mode , only I can go into Download Mode from that screen. I went back to 2.3.6 JVU using Odin and rooted it, phone booted fine. Now the thing is : When I am turning off my phone the phone keeps doing that battery screen problem. It turns screen on, acts like it's in a wall charger or it's checking for battery level or something and keep showing me an empty battery for a second then the screen goes off and back on again and only way to make my phone usable is to flash using Odin , the 2.3.6 stock ROM again and not take my battery out. If I try to flash CM 11, it goes into a recovery loop (because it's changing partitions sizes and the recovery version) and I have to take my battery out and it does it again. If I turn my phone off, my phone does it again and only way to boot it is to flash something from Odin so it forces it to boot.
Please Help ! What could be the problem and it's there a way to fix it?
Edit: I've been using my phone for an hour with on the Stock 2.3.6 and the battery level dropped just a bit . So The battery is not draining completely, and that fast. Also I've tried with a different battery and the problem persists. And my battery works just fine on a friend's GT-I9000. I've also successfully flashed Mackay CM9 2014 1.7, the situation didn't change. Also tried with Samsung 2.3.6 JW4
idCyber said:
I have the I9000 . Until this morning I haven't had any problems with my phone. I was on C-ROM KK 5.8 (not that it affects my problem) and last night I left my phone to recharge. This morning I've unplugged my phone from the wall charger and made a reboot (my morning routine). Strange thing happened. The phone went into the phone off connected to wall charger screen mode but showing that the battery is empty. I took my battery out and now every time I place it back in my phone, the screen goes on showing empty battery or it's checking for battery level, without even touching any buttons. If I try to go from that screen to make my phone boot using the power button it does not react. I can't go in recovery mode , only I can go into Download Mode from that screen. I went back to 2.3.6 JVU using Odin and rooted it, phone booted fine. Now the thing is : When I am turning off my phone the phone keeps doing that battery screen problem. It turns screen on, acts like it's in a wall charger or it's checking for battery level or something and keep showing me an empty battery for a second then the screen goes off and back on again and only way to make my phone usable is to flash using Odin , the 2.3.6 stock ROM again and not take my battery out. If I try to flash CM 11, it goes into a recovery loop (because it's changing partitions sizes and the recovery version) and I have to take my battery out and it does it again. If I turn my phone off, my phone does it again and only way to boot it is to flash something from Odin so it forces it to boot.
Please Help ! What could be the problem and it's there a way to fix it?
Edit: I've been using my phone for an hour with on the Stock 2.3.6 and the battery level dropped just a bit . So The battery is not draining completely, and that fast. Also I've tried with a different battery and the problem persists. And my battery works just fine on a friend's GT-I9000. I've also successfully flashed Mackay CM9 2014 1.7, the situation didn't change. Also tried with Samsung 2.3.6 JW4
Click to expand...
Click to collapse
Two questions for clarification:
-Do the symptoms differ depending on whether you run stock or custom ROM? Or symptoms are 100% identical?
-If you shutdown your phone, keep the battery in position and do not connect the phone to the charger, it still shows the battery-crazy stuff? Because that would lead me to believe it is a hardware thing....
If there is a difference between stock & custom:
Maybe the hardware is dealt with differently between stock & custom ROMs making it look different, but I am not sure about that. You could try whether CM7 has the problem as well, as that one had a kernel that was much closer to stock.
kasper_h said:
Two questions for clarification:
-Do the symptoms differ depending on whether you run stock or custom ROM? Or symptoms are 100% identical?
-If you shutdown your phone, keep the battery in position and do not connect the phone to the charger, it still shows the battery-crazy stuff? Because that would lead me to believe it is a hardware thing....
If there is a difference between stock & custom:
Maybe the hardware is dealt with differently between stock & custom ROMs making it look different, but I am not sure about that. You could try whether CM7 has the problem as well, as that one had a kernel that was much closer to stock.
Click to expand...
Click to collapse
Thank you for replying.
1. it's 100% identical on stock and custom ROMs only the battery icon shape is changed but the problem is the same.
2. The screen turns on by itself, without being plugged to anything.
3. Just tried CM7 and it's the same.
This is what is displayed when I put the battery and the phone is turned off, without being connected to anything. The picture is an example, found on the net, I don't have a camera to take a photo of my phone but the image shows exactly what I see for a second then it turns the screen off and back on forever, phone reacts only to download mode.
http://forums.androidcentral.com/attachments/samsung-galaxy-tab-2/83680d1380495982t-android-ota-updates-never-fail-brick-my-galaxy-tab-2-10-1-img_20130929_185629_413.jpg
idCyber said:
Thank you for replying.
1. it's 100% identical on stock and custom ROMs only the battery icon shape is changed but the problem is the same.
2. The screen turns on by itself, without being plugged to anything.
3. Just tried CM7 and it's the same.
This is what is displayed when I put the battery and the phone is turned off, without being connected to anything. The picture is an example, found on the net, I don't have a camera to take a photo of my phone but the image shows exactly what I see for a second then it turns the screen off and back on forever, phone reacts only to download mode.
http://forums.androidcentral.com/at...galaxy-tab-2-10-1-img_20130929_185629_413.jpg
Click to expand...
Click to collapse
I'm afraid this may be hardware related if the symptoms occur on different types of ROMs. The charging animation with screen off is triggered by the charging hardware of the phone, which thus seems to give wrong signals...
Verstuurd van mijn Nexus 5
kasper_h said:
I'm afraid this may be hardware related if the symptoms occur on different types of ROMs. The charging animation with screen off is triggered by the charging hardware of the phone, which thus seems to give wrong signals...
Verstuurd van mijn Nexus 5
Click to expand...
Click to collapse
Thank you for your help and clearing it for me that it is not a software issue. Guess you are right it's a hardware problem probably caused by the wall charger, after 2 years of usage I think it starts to break and "took something from the phone with it as a heads up" . I have to make a visit to the "phone doctor".
Hello,
About 4 days ago I started having an issue where my HTC One M7, would just shut down randomly when not plugged in. I had installed ViperOne 6.2.1 and everything was working fine. I then tried to remove apps thinking this was the issue. There was no pattern to it. It just shuts down. I have to hold down the power button until the phone starts up. It would shut down at all different times and tasks that I might be doing. I thought maybe it was the battery, so I searched online and did the battery reset, maybe it was a calibration issue. What I did notice is every time the phone would fully charged but when it would shut down, I would then plug in the phone and start it up it would give a battery life of say 78%, or 48%, again no pattern. So I decided to reinstall the ROM. Tried that and still the same thing even with no apps installed, the phone would just shut down. The only way to get it on was to plug it in. THen I tried other ROMS, such as CM11 ROM, LiquidSmooth, i also tried Android HD Revoluton this one wont get past the HTC quietly brilliant screen, thats another issue. I did reinstalls while just wiping of data. Then I finally decided to format the whole and reinstall the CM11 mod. Still the same issue. The phone works fine as lonas its plugged in, this only happens when it is not plugged in.
I am assuming that the battery needs to be replaced. Since everything works fine while charged. I would like to ask others if this is the logical next step, or are there other steps that I could try.
Thanks in advance
samton99 said:
Hello,
About 4 days ago I started having an issue where my HTC One M7, would just shut down randomly when not plugged in. I had installed ViperOne 6.2.1 and everything was working fine. I then tried to remove apps thinking this was the issue. There was no pattern to it. It just shuts down. I have to hold down the power button until the phone starts up. It would shut down at all different times and tasks that I might be doing. I thought maybe it was the battery, so I searched online and did the battery reset, maybe it was a calibration issue. What I did notice is every time the phone would fully charged but when it would shut down, I would then plug in the phone and start it up it would give a battery life of say 78%, or 48%, again no pattern. So I decided to reinstall the ROM. Tried that and still the same thing even with no apps installed, the phone would just shut down. The only way to get it on was to plug it in. THen I tried other ROMS, such as CM11 ROM, LiquidSmooth, i also tried Android HD Revoluton this one wont get past the HTC quietly brilliant screen, thats another issue. I did reinstalls while just wiping of data. Then I finally decided to format the whole and reinstall the CM11 mod. Still the same issue. The phone works fine as lonas its plugged in, this only happens when it is not plugged in.
I am assuming that the battery needs to be replaced. Since everything works fine while charged. I would like to ask others if this is the logical next step, or are there other steps that I could try.
Thanks in advance
Click to expand...
Click to collapse
What recovery version # are you using?
probably an hardware defect, you should try to go back to stock and see if it helps
I am using the following
TWRP 2.7.1.1
CM 11
I didn't mention but the phone is not 2 years old. I think its past the warranty.
I don't know hot get it back to stock. Haven't tried that yet! I will have to research and try that.
samton99 said:
I am using the following
TWRP 2.7.1.1
CM 11
I didn't mention but the phone is not 2 years old. I think its past the warranty.
I don't know hot get it back to stock. Haven't tried that yet! I will have to research and try that.
Click to expand...
Click to collapse
2.7.1.1 is required to flash CM11 correctly but for ARHD you must use 2.6.3.3, You might want to try before returning to stock. If you want to return to stock, follow nkk71's guide linked in my signature.
The fact that your phone is not rebooting while plugged in makes me believe its an hardware issue
(Please see post #4 as the issue has evolved)
I recently updated my husband's HD from CM 11 to CM 12.1 (the one build in @amaces obsolete folder). This restored some functionality to a few apps that had "moved on" beyond KitKat and preserved the HMDI functionality. Everything else is essentially the same. Except.
Too often on starting the tablet up in the morning it shows about the same battery level as at shutdown the prior evening (maybe 50-ish) and then in a matter of minutes nosedives to 1%. You can see the behavior on the power usage graphic in Settings and it's pretty shocking. There's a vertical line for when it booted up and then *bam*, it drops to essentially nothing. If the tablet is plugged in for just a moment, the battery level returns to normal and everything is fine. It can be disconnected from the power supply and behaves normally the rest of the day.
So this is annoying (moreso because I need to hear about it every time it happens ). I've read the entire (unofficial) CM 12 thread. This issue comes up once or twice and seems to be "resolved" by "calibrating" the battery either with an app from the PlayStore or without. The app seems to just delete a file that would be overwritten at boot anyway from what else I have read on the subject, but the main idea is to drain the battery to an actual 1%, shut down and charge (the tablet remains "off" although the screen is on) until you've got 100% (which has to be judged by the green LED since the tablet is off).
I tried this (with the app), beginning by wiping cache and dalvik cache. It seemed to work for awhile. Then I foolishly suggested doing a backup. I did this with the emmc TWRP and everything seemed to go well except the battery indicator issue started up again...
So we did the battery thing again.... And it was just fine until this morning (not what you want to hear as you sit down to breakfast).
Clearly one could live with this if you always have the charger close at hand, but it's pretty lame. The tablet behaves beautifully in all other respects. I don't think it's a hardware issue as it started right after flashing the new ROM.
One person in the CM 12 thread actually praised the ROM as eliminating this issue which he had from CM 11!
Is this a flashing glitch which might be fixed by reflashing the ROM? I'm loath to do a clean install and reconstruct everything again after such a short time, but I wonder if a "dirty" install (don't wipe data, right?) would be enough. If I reflash the ROM do I have to reflash GApps also?
Suggestions? I'm really at a loss here.
nmyshkin said:
...
Is this a flashing glitch which might be fixed by reflashing the ROM? I'm loath to do a clean install and reconstruct everything again after such a short time, but I wonder if a "dirty" install (don't wipe data, right?) would be enough.
Click to expand...
Click to collapse
I doubt if a dirty flash would change anything, but there does not appear to be any penalty to try it out as a shot in the dark.
If I reflash the ROM do I have to reflash GApps also?
Click to expand...
Click to collapse
Not if you don't wipe /data -- basically same as in the case of a dirty upgrade.
digixmax said:
I doubt if a dirty flash would change anything, but there does not appear to be any penalty to try it out as a shot in the dark.
Not if you don't wipe /data -- basically same as in the case of a dirty upgrade.
Click to expand...
Click to collapse
I finally got around to this after much complaining about the issue and now I've managed to make it much worse. Before, the tablet would drop from the 50's (or lower) to 1% on boot. Higher percentages of charge were usually safe. Now it goes through the boot process up to the animation and then abruptly shuts down UNLESS the power cable is connected, regardless of the state of battery charge. If the cable is connected boot occurs normally and you can disconnect after boot is complete and everything is "fine".
Except, of course, it's not "fine" at all. Unless you have the charger and cable with you at all times, the tablet has to be left on when you're on the go.
Ugh. Any ideas besides going back to stock and starting over?
nmyshkin said:
I finally got around to this after much complaining about the issue and now I've managed to make it much worse. Before, the tablet would drop from the 50's (or lower) to 1% on boot. Higher percentages of charge were usually safe. Now it goes through the boot process up to the animation and then abruptly shuts down UNLESS the power cable is connected, regardless of the state of battery charge. If the cable is connected boot occurs normally and you can disconnect after boot is complete and everything is "fine".
Except, of course, it's not "fine" at all. Unless you have the charger and cable with you at all times, the tablet has to be left on when you're on the go.
Ugh. Any ideas besides going back to stock and starting over?
Click to expand...
Click to collapse
I came across a post that suggested returning all the way to stock and doing a factory reset, then rebuilding the system.
Once at stock I had no trouble completing a boot without being plugged in. So that is not a hardware issue. I didn't stay on stock long enough to see if the battery indicator behaved, but I'm guessing it did. I prepared a completely new SD card with newly downloaded files and proceeded to do the needed flashing for CM 12.1 w/GApps, using CWM 6.045. It all seemed to go well--even no screen flashing--until I unplugged the tablet so I could easily remove the SD card and reboot. As soon as I removed the power cord the periodic screen flashing that seems to be common during CWM use started up.
I rebooted and got only so far with the CM logo before the tablet shut down.
I don't get it. It worked fine before. What about this process could be causing this odd behavior?
Edit: in desperation I tried flashing The ROM again right over the prior installation. This time I booted into the emmc CWM (6.0.4.6) and waited for the tablet to calm down. Then I unplugged it and flashed the ROM from the ext.SD card. No error messages. I held my breath and rebooted. I got to several iterations of the cyan android face and then it shut down again.
Next I flashed TWRP 2.8.7.4 to emmc and tried flashing the ROM from the ext.SD card that way. Same result.
The battery charge shows 80% so it's not like the tablet is running on fumes and it's hard to believe the problem is the battery or the indicator since none of this happens on the stock ROM.
I just don't get it. We don't want to go back to stock but I don't understand any of what is going on. Initially CM 12.1 was working beautifully. Then the battery indicator issue started. I addressed that as best I could and when it seemed like we had that on the run I did a backup. That resulted in this shutdown issue. You can use the tablet just fine if you never turn it off and keep either the charger or a portable power pack handy (don't forget the cable!).
I really need some help troubleshooting. I'm willing to try just about anything.
Edit: indeed, the last resort was to buy another HD... But it turns out the booting issue was caused by an SD card that somehow was not properly prepared as 0x0C FAT32 LBA but was instead something else which I don't remember now (something with a "b"). Anyway, once a new card was carefully prepared, the tablet booted fine without being plugged in. Whether this also solves the battery indicator issue remains to be seen.