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 all, thanks for taking your time to read and possibly help me out with my problem. Yesterday I've tried rooting my droid in order to put cyanogen mod on it later. The reason I was interested in doing that was because I felt as droid was not working to it full potential and constantly crashing apps on me (browser, games, weather, etc). A friend of mine suggested cyanogen as he himself owns it. Being that I've did plenty of CFW on PS2, psp, xbox and mp3s/ipods, I thought there shouldn't be a hassle with this.
I followed the procedures listed on cyanogen's wiki page in order to complete the rooting process. But on the step where it asked to instal .sbf file trough RSD lite and wait till it says "pass" I've ran into trouble.
During the unpacking of that file to the phone using RSD lite the phone was undergoing several reboots, and after finally finishing the reboots on my PC screen in the RSD Lite window it showed 100% complete "please reboot the phone manually". I had no idea how to do that manually as the phone just kept going on and off by itself. (also for some reason it kept saying "error" force close/wait/send notice. But I thought it was probably just the process. After trying to reboot the phone a couple of times nothing worked. I didn't receive any "pass" signs on the droid screen.
I've got a little worried about the whole process and decided to shut the phone off and during that close the RSD Lite on my computer. Doing that made no further improvements for me. The phone just kept going on and off like crazy while in USB and not turning on at all while not plugged into either USB or AC. I've decided to go to recovery mode and just reset everything to stock as I was running out of time and had to get some sleep before work next day. After reseting the cache/data files I rebooted the phone but the same things kept happening to it. Now it was asking me to reconnect with gmail account and all that intro stuff. But the phone would always end up locking up and shutting off somewhere in the process of reconnecting the account.
Fast forward to today I've read that its possible to complete reset everything to stock version trough .sbf file once again. But now the problem consists of the phone not having enough batter life. (I'm not sure what the screen is called where the process of dumping .sbf trough RSD lite starts) but that screen keeps saying battery is too low to do anything with it. And mind me it has been charge for a very long time now in the AC adapter.
Now it also appears as the problem has worsened. The phone does not start up at all in either USB or without connection. It only starts up in AC adapter but then it shuts off in 2 minutes and back on and off , on and off. Recovery mode can't be accessed in any way, at least any way known to me. The black .sbf screen can only be accessed while the phone is not connected to anything but still keeps saying the battery is too low. And I've noticed the phone getting extremely hot during AC charge. (another small detail that sometimes when the phone does turn on and goes to home screen opening up the landscape view does not increase the length of the top (pull down) bar in horizontal view.
I've tried taking out both battery and sdcard and putting them back but no luck. I'm really lost as to what I can do next in order to fix this problem.
If you need any further information please let me know and thank you again for trying to help me!
I don't really see how you managed to get a fc with rsdlite.
Did you reboot your phone (turn off) then boot into usb recovery (power on while holding up, for the droid)?
Sent from my Droid using XDA App
I am by no means an expert and could be just wasting your time but in the absence of expert opinions something is better than nothing right? It sounds to me like maybe you have a bad battery that as luck would have it failed during the update/rewrite. Have you tried getting into recovery with the battery pulled running straight off the ac adapter? Hopefully you made a clockwork/nandroid backup before you started?
sent from a random hobo's droid on xda's app
I'm not an expert either, but having just successfully rooted my droid and installed cyanogen I feel the need to ask: did you hold up on the d-pad while RSD rebooted the phone the first time? If not then you needed to immediately restart the process.
I think you need to use a separate battery charger (meaning that charging battery without a phone) to charge the battery.
Sometimes, battery won't hold a charge when your phone is a brick.
BTW, it appears that you are having the same issue with mine.
(I can't post a URL because I am new here, but you can take a look at my article in this section, called "[S.O.S] A rare MILESTONE brick situation". )
I had the same problem (battery won't charge and phone won't start-up), I had to purchase a separate battery charger, and then flashed another SBF, to make the phone charging normal. (Although my phone is still a brick, but not a problem with battery. )
Hello.
I'll get straight to the facts.
I had my phone rooted with Odinv3 using "busybox" (is all i can see on my downloads).
I then went to update to Gingerbread today, but didn't realise I had to un-root the phone!
So this made the phone keep refreshing the samsung galaxy S screen.
I then went to reboot to stock using this thread. Said it passed etc.
Now my phone is completely dead. It won't turn on. Nothing at all when i get it into download mode. No lights turn on. Odin *does* recognise it when I plug it in, the yellow box lights up.
The computer makes a noise to recognise that somethings been plugged in.
But alas nothing on the phone. I've left the battery out and tried it in but nothing.
What can I do please?! I am stuck here. And fear i just have wasted a great sum of money...
Will I be able to take it back on warranty? I haven't had it long, 3 months or so. Would they recognise it has been rooted despite it being put back to stock software.
Thanks. Daniel
You are a bit unclear, can you get download mode with 3 button combo?
Sent from my GT-I9000
tried many times to remove and replace the battery worked for me
sorry for the google translation
I managed to get into download mode by doing a 3 button combo earlier, can't remember what it was but I had to hold three buttons *THEN* fit my battery. THen it went into download mode. I can't remember which combo it was though as i've tried loads before and they didn't work!
It won't do anything now though.
Could i have booted it with a wrong ROM and that's why it won't load?
How come Odin picks it up and it goes through that passing etc?
THis si so annoying.
Volume down/power/home hold til galaxy s logo then release a yellow logo should appear
Sent from my GT-I9000
Sorry for opening an old thread. But i have aproximately the same problem with one exception:
Odin won't regognize my phone.
I was just in the process of installing this rom:
http://forum.xda-developers.com/showthread.php?t=1136449
It got to the first step: "DO NOT POWER OFF DEVICE!!".. and then nothing. Sat there for 15 minutes untill i unplugged it.
shut down the phone using the power button, but now.. its completely dead.
This was offcourse before I realized i had just tried to install a ROM for SGS.. not SGSII.
So.
Odin doesnt recognize the phone.
The phone won't turn on, no matter what I do.
Nothing happens when I try to charge the phone.
I've tried pulling the battery several times, but its just .. dead.
However, when I plug in the battery, the phone seems to get hot. Not very hot, but just slightly above 25 degrees (aprox).
I'm afraid i've f*cked up big time, and have to send it in for a repair..
Anyone have a tip of what I can do ?
(Yes, the battery is charged - not empty).
Have you tried going into download mode again? does the screen power up at all?
My advice is try to leave the battery out for 15-30 minutes, then try getting into Download mode again, with the USB cable already plugged in and ODIN running on your machine.
See if ODIN can detect it and work from there... May be better than nothing. Hope this helps.
kragebein said:
Sorry for opening an old thread. But i have aproximately the same problem with one exception:
Odin won't regognize my phone.
I was just in the process of installing this rom:
http://forum.xda-developers.com/showthread.php?t=1136449
It got to the first step: "DO NOT POWER OFF DEVICE!!".. and then nothing. Sat there for 15 minutes untill i unplugged it.
shut down the phone using the power button, but now.. its completely dead.
I've tried pulling the battery several times, but its just .. dead.
However, when I plug in the battery, the phone seems to get hot. Not very hot, but just slightly above 25 degrees (aprox).
I'm afraid i've f*cked up big time, and have to send it in for a repair..
Anyone have a tip of what I can do ?
(Yes, the battery is charged - not empty).
Click to expand...
Click to collapse
Did you know how to flashing the rom (via CWM) ? You have to notice your battery percentage first.
What exactly were you flashing? CF-root? where did you get it from?
I had the battery out through the night and tried again this morning.. didnt work..
It SEEMS to be completely dead.. (with exception from that the cpu gets hot when battery is plugged in.. )
I tried flashing this:
http://www.multiupload.com/6QNW8P7DTY
I came as far as "Setting PIT file.." "DO NOT TURN OFF" in odin, and then everything stopped.
The battery was at 70% when i started the process.
The phone have only been on for about 20 minutes since.
Today my phone suddenly died on me and refuses to boot up. I came home from work and the phone was working fine. Made a few phone calls, checked a few apps etc. Battery was about 70%.
I left the phone aside and when I picked it up at bed time, it had shut down. Now it doesn't boot at all. I thought maybe the battery had suddenly died down and put it to charge but it isn't turning on at all. Can't even get to the LG logo. Anyone have any clue what to do?
I thought I was one of the lucky few to get a handset which didn't reboot
Edit: Thought I should mention that I was running stock ROM, rooted, with CWM recovery installed
Can you bring up recovery mode? Did you try NVFlash?
Sent from my LG-P990 using XDA App
Remove and replace the battery first and then try charging trough your usb cable and pc. Let it charge for a few minutes and try to boot.
Sent from my LG-P990 using XDA Premium App
mparack said:
Today my phone suddenly died on me and refuses to boot up. I came home from work and the phone was working fine. Made a few phone calls, checked a few apps etc. Battery was about 70%.
I left the phone aside and when I picked it up at bed time, it had shut down. Now it doesn't boot at all. I thought maybe the battery had suddenly died down and put it to charge but it isn't turning on at all. Can't even get to the LG logo. Anyone have any clue what to do?
I thought I was one of the lucky few to get a handset which didn't reboot
Edit: Thought I should mention that I was running stock ROM, rooted, with CWM recovery installed
Click to expand...
Click to collapse
had the same problem.
nvflash fixed it, once the problem was solved I kept getting reboots 20x a day so I nvflashed again and flashed CM7 and havent had a reboot/ BSOD since. I also thought I was one of the lucky ones that didn't reboot at first btw
Thanks guys. Wouldn't power up at all in normal or recovery so couldn't nvflash it. Tried usb, charging etc etc.
However after countless battery pulls just started up again and working perfectly since. I've powered up my trusty htc magic as a backup meanwhile. No idea what went wrong at all.
Sent from my LG-P990 using XDA App
by recovery you ment CWM or Upgrade mode? (that is remove battery, hold volume down button and plug in usb while holding it)
mikee2185 said:
by recovery you ment CWM or Upgrade mode? (that is remove battery, hold volume down button and plug in usb while holding it)
Click to expand...
Click to collapse
Not tried upgrade mode just the volume+power. Maybe something to keep in mind for next time.
ok, i just wanted to make sure that upgrade mode works even if the phone is completely ****ed up
I flashed CM 12.1 a while ago and it would sometimes freeze up so I would pull the battery if vol down + power didn't work (which it usually didn't) and then last night it just turned off and never came back on. Sometimes it would boot into download mode and say "failed to do normal boot mmc_read failure" and others it would boot back up no problem. Now I can't get it to boot into Recovery or Download, I've taken the battery out and help down power for a while, then put it back in and help power for a while, tried charging with two cables that both charge my tablet just fine and in two outlets. When I plug the phone into the computer it dings so the PC recognizes a device is being plugged in but it doesn't show up under the file browser. Am I hard bricked? Can I fix it? Should I try to get a new phone?
It's a T-Mobile Note 4 if that helps. I'm still making payments on it but I passed the year mark in February.
shadow105720 said:
I flashed CM 12.1 a while ago and it would sometimes freeze up so I would pull the battery if vol down + power didn't work (which it usually didn't) and then last night it just turned off and never came back on. Sometimes it would boot into download mode and say "failed to do normal boot mmc_read failure" and others it would boot back up no problem. Now I can't get it to boot into Recovery or Download, I've taken the battery out and help down power for a while, then put it back in and help power for a while, tried charging with two cables that both charge my tablet just fine and in two outlets. When I plug the phone into the computer it dings so the PC recognizes a device is being plugged in but it doesn't show up under the file browser. Am I hard bricked? Can I fix it? Should I try to get a new phone?
It's a T-Mobile Note 4 if that helps. I'm still making payments on it but I passed the year mark in February.
Click to expand...
Click to collapse
I looked up that error and there was multiple articles thatvsaid it could be a flash memory error of an EFS problem. Hopefully its something different, as both of those are tricky at best. Its a place to start though.
Install Kies and try the emergency firmware recovery.
Sent from my SM-N910T using Tapatalk