Hey all, My G1 was running ok on CM5 until I decided to try the zachattack052 sense rom. A day after that rom was loaded, the phone started shutting itself off and would not power back up unless it is plugged. The red led light blinks every two seconds or so when I try to power up with just the battery. Then I decided to completely do a wipe and re-install CM5 from stratch. That seemed to work for a day or two then the problem returned. I am now back to the generic G1 rom with 2.22.19.261 radio and latest G1 SPL and still having issues. With the phone plugged in to power, it boots up and says charging at 0% and would then shut off within a few minutes. I have also tried the battery calibration app and no dice.
Now you may be thinking that the battery is the issue, but it is not. I have an un-rooted stock G1 and that one is able to fully charge the batteries. Then I swap the batteries and still no luck....blinky red led. These two batteries are new 1400mah.
The weird thing is that the phone will stay running on battery power only when booted into recovery or fastboot mode (in other words, plugg power in, boot into recovery/fastboot, unplug power, phone lasts forever with battery)
What is wrong with my G1?
Would un-rooting it and going back help?
Here is the info from fastboot:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Apr 20 2009,15:30:43
Please help
Probably cleaning the battery stats may help you, only a hint
Sent from my Gingerbread on Dream using XDA App
Thanks for that info. When you say stats, you mean wiping battery info from recovery right? I have done that many times.
But now it really gets interesting....
I just flashed a donut rom (zachattact052) with 2.22.23.02 radio and Danger SPL and right away the phone booted up by itself (where previously it needed to be plugged in and manually be turned on) and the LED now showed orange indicating it is actually charging. However, within a few minutes of the phone being on and plugged in, the orange LED goes away, turns red and it begins to discharge while being plugged in.
...so confused.
Anyone else able to help me out/guide me?
I re-flashed the radio and it seemed like that fixed it. But shortly after that, the problem returned. I also tried the ohsaka superwipe, but still having issues and does not even re-boot automatically after flashing radio. Considering I am able to install a rom and run it for a minute or two, is my device considered bricked? If so, what would be the proper procedure to un-brick?
Thanks
sirminder said:
Anyone else able to help me out/guide me?
I re-flashed the radio and it seemed like that fixed it. But shortly after that, the problem returned. I also tried the ohsaka superwipe, but still having issues and does not even re-boot automatically after flashing radio. Considering I am able to install a rom and run it for a minute or two, is my device considered bricked? If so, what would be the proper procedure to un-brick?
Thanks
Click to expand...
Click to collapse
Phone is not bricked....You'll know when it's bricked when recovery, booloaders, and normal boot don't work. That's when you have a G1 paper weight. The problem could simply be that the batteries are not full of life...Most of the G1's avail batteries would have to be over 1 1/2 yrs of age. The cells in battery are suppose to die, even when it's not being used. If you were to buy a battery for a laptop that's 10yrs old today, you can't expect the battery to have the same life as when it was first made. No, instead you'll have under 30mins on that new batt you just got for it. Anyway my point is that this can't be helped, you could try calibrating too or get a new phone.
http://forum.xda-developers.com/showthread.php?t=1187698
Thanks Ace, I completely understand what you said about batteries not lasting.
However, why is it that my rooted G1 cannot boot on battery power, where my un-rooted G1 will boot and run on the exact same battery plus charge to 100%?
sirminder said:
Thanks Ace, I completely understand what you said about batteries not lasting.
However, why is it that my rooted G1 cannot boot on battery power, where my un-rooted G1 will boot and run on the exact same battery plus charge to 100%?
Click to expand...
Click to collapse
Try these
-Wipe battery stats in recovery, then calibrate battery
-Phone has hardware defect, causing some power issue
Thanks Ace.
I gave up on this G1 and walked way leaving it off while plugged in with the red led light. I don't know why, but 2 hours later, I decided to give it one more shot. It booted up, battery showed 99% and the led finally showed green....wtf????
I have then followed your advice (considering I had previously wiped the battery stats hundreds of times) and I am currently discharging the battery. Spare Parts shows battery has good health at 59% with 3.861v at 33.0 degrees C. Current ROM is zachattacks052 & xillius200's Donut with 2.22.23.02 radio and Danger SPL.
I have been running a few apps and stressing the phone for almost an hour....lets see how long it holds up for. The next test would be how it performs once the battery is completely drained and if it can boot up easily.
Related
Ok in short my battery is not charging at all. I have had this kaiser for a month mayb, but the battery for almost a year. I we away for the weekend and forgot my charger so my phone died. I plug into charger and charging light comes on but when i try and turn it on phone boots then dies as it has no power from cable or battery.
Phone is COMPLETELY stock + tf2d.
AT&T Tilt
Any ideas anyone?
I just updated my phone (even tho it has no battery...). So right i went into bootloader and flashed the offical rom, it died at 13% then retarted and finished flashing....idk if it was supposted to do that or not idk. but now it boots and does the samething as if it has no battery...idk what the deal is .
The battery is heating up like its charging...
It remained updating from 13%-100% and didnt die but i dont think it can charge while updating..but after updating when installing it dies as soon as it gets to "clearing storage"
update
i believe i have a mechanical issue now not a battery issue. This is because even tho it says its charging the battery the phone SHOULD be able to boot under power cable only without battery....but it does not....seems i shall be calling at&t....
jug6ernaut said:
This is because even tho it says its charging the battery the phone SHOULD be able to boot under power cable only without battery....but it does not....
Click to expand...
Click to collapse
Nope, HTC phones and most others can't boot just off the power cable with no battery.
I just updated my phone (even tho it has no battery...).
Click to expand...
Click to collapse
If you had read the warnings in the flashing application you'd have seen it says to ensure your battery is charged before flashing. If your battery is flat and the phone turns off during flash (which looks like it has happened here) it leaves you with an incomplete flash and unusable OS, no wonder it crashes randomly. If you have HardSPL you can recover from that, but as you said you're completely stock it might be a lot more problematic.
lol no no my friend you miss understand what im saying.
Trust me i know the warnings of flashing(300+ flashes many failed...happens when making ur own roms), and knowing these i flashed anyways. What i was trying to point out was that it went through the flash all the way even tho during the same amount of time it would have died during booting, the flash was successful but idky.
The phone is not crashing randomly it has no battery power lol. This problem has nothing to do with flashing because before this it was 100% stock...
Are you sure the kaiser can not boot purly off external power? I was almost positive i had done this before.
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 i'm new here and i've looked through the forums but i can't seem to find an answer. So i recently rooted and ran OE. i decided that it was a bit slow for me so i changed to Cyanogen's latest build, i have the latest radio and danger spl. but for some reason my phone will shut down out of no where. then even after pulling the battery literally tens of times my phone wont start up, once or twice it will start up so i usally start it up in recovery mode. i've wiped and re flashed the rom twice now and still the same thing happens. now i think it's the battery. but the battery i have looks fine, and i tried another one and same thing, no start up. do you think it's hardware or software related? and is there anything else i can do? thanks
Have you tried with any other rom's?
I would recommend WesGarner's or Super D's rom's cuz they are more indie
It might just be the rom.
its probably a hardware issue, that or your battery is dying?
i would try flashing another rom, but my phone won't boot. i can plug it in to charge and a red led comes on which is normal, but when trying to power it on, nothing happens.
Trinimass said:
i would try flashing another rom, but my phone won't boot. i can plug it in to charge and a red led comes on which is normal, but when trying to power it on, nothing happens.
Click to expand...
Click to collapse
If your led never changes from red, you should probably get a new battery. Mine doesn't start even when plugged in when the battery is completely dead. I have to let it charge for a minute or two before it will start. It could be that your battery isn't taking any charge at all.
Hmmm, you said in your OP that you tried another battery and had the same problem? I wonder if there is something wrong with the charging thing in your phone? If it happened with two different batteries and two different ROMs, there is something going on.
Does it keep running while plugged in with a different battery?
When i plug it in to the charger, should the led even try to come on, it only blinks red.
The other battery i used was at the tmobile store. so i can't test that. i believed the guy put it on the charger for a second with the new battery in when we were at the store, but still nothing.
I did just call and i'm getting it replaced. i think i'm going to buy a 1400 battery anyways. new battery & new phone. hopefully all shall be well
I'm glad you are getting a new phone and battery. If the battery is dead, it is usually solid red, then it switches to orange, then green when it is charged. What you described sounds like you needed a replacement.
Last night I went through the process of flashing Revolt 1.5 onto my phone. Whiel at work I was playing with the phone setting my pages and such back up. After a bit my phone started to get hot and the battery drained pretty rapidly. I didn't have a charger with me soe phone was dead for a little while, now when I plug it in I get no LED and it wont turn on at all. Tried charging it for over 30min on a wall charger.
Does it turn on without the battery? Just the charger plugged in?
Nope, I found a thread that said to plug it in with no battery for a while then put the battery back in. It is starting to warm right now.
Phone was still under warranty. They are swapping it out and gave me a new battery. With the new battery I got it to boot up so I am going to try a full recalibration of the battery to see if that stops the heat issue it still seems to be happening, either way new body for the phone is on its way.
grmncrsnbr said:
Phone was still under warranty. They are swapping it out and gave me a new battery. With the new battery I got it to boot up so I am going to try a full recalibration of the battery to see if that stops the heat issue it still seems to be happening, either way new body for the phone is on its way.
Click to expand...
Click to collapse
Had this happen on my original motorola droid... required a new battery. Also I learned the hard way always wipe data and cache a few times when upgrading roms...even if you are just coming from an old version. Had the same discharge problem/hot phone when updating from 1.4 to 1.5... also noticed under phone build still showed 1.4 lol... Did a few wipes of data/cache then reinstalled 1.5 and havent had any problems for about a week.
So I've had this phone for about a year now, the moment I got it I unlocked the bootloader, rooted it and flashed cyanfox (cm11 fork) onto it.
It's been serving me great ever since, no problems whatsoever with it.
But as of a few days back I found it with a black screen, unresponsive. I connected the charger and it light up the green led solid, tries to boot but can't get past the boot loader message
This continues in an almost endless loop until getting to a 'battery 1%' screen with it showing the battery. After that I'm able to boot it up without problem
I first thought that was the end of it.. I finally got it too boot all seemed fine, battery showed 3% at start up bit voltage was suggesting it was 100%. It flashed to 100% later.
Good, no problem until then. But when leaving it over night to charge and disconnecting it from the charger this morning it turned off again. And now it's back in the bootloop when on charger :crying:
also important to mention is that when it crashes and gets into the bootloop on charger(0% battery and all) it was at 50-100% before the crash.
If anyone has any ideas what might be the cause I'd be very thankful
Main problem(s):
-random crashes instantly rendering battery % as 0 while there is still charge
-getting atrix hd to turn on at <1% battery
Some maybe useful information:
-it does say 'battery OK' in fastboot while connected to the wallcharger
-after I get it to boot it will run just fine on battery and charge as normal, but will crash/brick again after some time
-I can get into boot selection screen and fastboot, but only on wallcharger
-I cannot get to fastboot when connected to use, pc doesn't see the phone
-It won't boot past the bootloader('Motorola logo' for you on not unlocked bootloaders) no matter the boot selection(recovery, bp tools etc)
-This is a second hand model already in use by me (the second owner) for over a year now
-no custom kernel, only rom, cyanfox 4.4.2 (cm11 based)
-the few times it got past the bootloop and I was able to boot was on my aftermarket charger (stock charger will make the green led light up but no proof of being able to get past bootloop over time on it)
I've had dead batteries before.. and since It looked good last time I got it on (it won't go on at all now) I was skeptic about the battery being dead. But a quick test of the multimeter gives me <1v :crying:
I know batteries can be drained pretty bad.. but this just seems a bit extreme.. I'll try to get it to boot for a while.
Thanks in advance for any helpful solutions or ideas on the matter
EDIT: Got it on again last night, turned off this morning when pulling out the charger, was at 100%. Checked battery and again read around 1V.
blaming the battery, ordered a new one just in case, should be here in a month or so. Still open for suggestions on the matter
Catblaster said:
I've had dead batteries before.. and since It looked good last time I got it on (it won't go on at all now) I was skeptic about the battery being dead. But a quick test of the multimeter gives me <1v :crying:
I know batteries can be drained pretty bad.. but this just seems a bit extreme.. I'll try to get it to boot for a while.
Thanks in advance for any helpful solutions or ideas on the matter
EDIT: Got it on again last night, turned off this morning when pulling out the charger, was at 100%. Checked battery and again read around 1V.
blaming the battery, ordered a new one just in case, should be here in a month or so. Still open for suggestions on the matter
Click to expand...
Click to collapse
Did you fix it somehow in the end?
My Atrix HD freezes after several minutes(sometimes even on wall charger). Bought new battery, tried to reset everything: usb storage, cash, system, factory reset. Went back to ROM I was using before(stable) but didn't help.
?
michael8s said:
Did you fix it somehow in the end?
My Atrix HD freezes after several minutes(sometimes even on wall charger). Bought new battery, tried to reset everything: usb storage, cash, system, factory reset. Went back to ROM I was using before(stable) but didn't help.
?
Click to expand...
Click to collapse
It ended up being the battery, all problems were gone after I changed the battery.
Which in the end wasn't so bad because I'd been wanting to upgrade my eb20 to an eb40
No Idea to what it could be in your case.
Everything working appart from that? no battery hickups or things not working properly?
Catblaster said:
It ended up being the battery, all problems were gone after I changed the battery.
Which in the end wasn't so bad because I'd been wanting to upgrade my eb20 to an eb40
No Idea to what it could be in your case.
Everything working appart from that? no battery hickups or things not working properly?
Click to expand...
Click to collapse
"0% battery after crashes" that is what was happening in the begging, so I thought it is the battery. I changed it to UB40
but everything's got worse. With the new battery I have crashes even when the battery is almost full.(but not always, for example I can play movie from youtube normally, but when I try to send sms or something else it crashes ).
Hard to believe that there is something with the new battery(I have it just one week+It took a month to ship from ebay).
I tried to flash another ROM, but still have freezes.
Last thing sometimes battery charges normally but then suddenly jumps to ~100%. Now I try to flash Stock ROM, but eventually soft bricked the phone. (+had "battery low" in fastboot, while charging animation was saying 100%)
Where did you buy EB40?
____________________________________
It turned out that EB40 battery was bad, after replacing it with another one everything work