Please Help.(Individually bizzare Problem...I think.) DHD - Desire HD Q&A, Help & Troubleshooting

Hello all,
I made this thread in hopes of getting an explanation and maybe a bit of guidance to my problem. My problem is that my Desire HD(T-Mobile UK) crashes all the time. I have had this phone for just over a year, and had it rooted for the past 8 months with little problem, however only recently, in the past 3-4 months it would just turn off at random points and then need restarting. It has not made a difference what ROM I have had, whether it was Cyanogen, Android Revolution, RCMix3d, ClearDroid, or MIUI, after a few days of having the new ROM it would crash throughout the day, with any amount of battery on it. I followed the most respected guides put on this site, and still it made no difference.
At first I thought it was the way I'd been flashing my ROM's, so as I have never been able to get HTC Sync to recognize my phone, I re-flashed a fresh stock 1.32 and then manually installed the ADB Drivers, the phones USB Drivers, and rooted the phone with Visionary+ all over again. This made no difference.
So then I moved on to thinking it was my Battery, so I bought a new battery and that made no difference either. This made me assume it is a software issue.
I then began thinking that it could be the Overclock/Undervolt settings, even though I hadn't touched them, I thought it might fix my phone if I made the minimum it could reach 350+mhz instead of 280+mhz, thus keeping the phone running at a faster speed and not crash.But this made no difference either.
The only thing I have been able to do has been to flash the 1.32 Stock and that seems to get it working, battery drains a bit quicker but doesn't die while still saying 55% left. I have also tried charging the phone til 100% using Elixir's mA widget, deleting the battery stats file(re calibrating the battery), and letting it reach 0 and charging again. But no luck.
If you have any advice I will gladly listen, I'm baffled as to what has happened, and am not sure what to do next.
Apologies as well if this thread is posted in the wrong section, I am quite new with this site.
Thank you very much in advance guys.
ponl1882

pride_ofnorthlondon1882 said:
Hello all,
I made this thread in hopes of getting an explanation and maybe a bit of guidance to my problem. My problem is that my Desire HD(T-Mobile UK) crashes all the time. I have had this phone for just over a year, and had it rooted for the past 8 months with little problem, however only recently, in the past 3-4 months it would just turn off at random points and then need restarting. It has not made a difference what ROM I have had, whether it was Cyanogen, Android Revolution, RCMix3d, ClearDroid, or MIUI, after a few days of having the new ROM it would crash throughout the day, with any amount of battery on it. I followed the most respected guides put on this site, and still it made no difference.
At first I thought it was the way I'd been flashing my ROM's, so as I have never been able to get HTC Sync to recognize my phone, I re-flashed a fresh stock 1.32 and then manually installed the ADB Drivers, the phones USB Drivers, and rooted the phone with Visionary+ all over again. This made no difference.
So then I moved on to thinking it was my Battery, so I bought a new battery and that made no difference either. This made me assume it is a software issue.
I then began thinking that it could be the Overclock/Undervolt settings, even though I hadn't touched them, I thought it might fix my phone if I made the minimum it could reach 350+mhz instead of 280+mhz, thus keeping the phone running at a faster speed and not crash.But this made no difference either.
The only thing I have been able to do has been to flash the 1.32 Stock and that seems to get it working, battery drains a bit quicker but doesn't die while still saying 55% left. I have also tried charging the phone til 100% using Elixir's mA widget, deleting the battery stats file(re calibrating the battery), and letting it reach 0 and charging again. But no luck.
If you have any advice I will gladly listen, I'm baffled as to what has happened, and am not sure what to do next.
Apologies as well if this thread is posted in the wrong section, I am quite new with this site.
Thank you very much in advance guys.
ponl1882
Click to expand...
Click to collapse
To me it really sounds like a hardware problem which is bad news. Try phoning HTC directly and ask them what to do. Don't mention at all that you have rooted it

Scottymeuk said:
To me it really sounds like a hardware problem which is bad news. Try phoning HTC directly and ask them what to do. Don't mention at all that you have rooted it
Click to expand...
Click to collapse
Oh bumsicles.

Related

[Q] Advice needed on whether to flash or not

Hey guys,
Firstly, Thanks for taking the time to look at this post.
I bought a Desire HD last month and have been reading about how the battery adapts to your usage and eventually improves within two to three weeks. This hasnt been the case for me unfortunately. I take my phone off the charger exactly at 12 30pm before going to work and by the time I leave work around 9pm, my battery is usually sitting around the 40 - 45% mark with literally two to three minutes of usage throughout my shift! I tried JuiceDefender but didnt help at all. Also, I uninstalled all the apps I installed when I first got the phone just to check if that made a difference - it did not.
Now I'm no expert at this but from what I could make out from other threads, flashing my rom sounds like a promising option.
My question to the experts is, I have only had this phone for a month, I know it will void my warranty if I flash the rom but do I really need the warranty? I mean I never used any warranty before on any of my phones and since this is such a promising phone, I highly doubt it that something could go wrong (ofcourse with the exception of human error like dropping or losing the phone etc.) If I plan on flashing, which rom would you recommend to a rookie with almost no knowledge about flashing and roms etc but very eager to learn? Any tips, advice, anything at all would be really appreciated.
Thanks in advance to anyone thats going to contribute!
Hello,
First I am no expert . I have rooted and flashed just recently but I have learned a few things or two by hanging around excessively on the forum .
In my opinion battery life does improve ,Before rooting n flashing my overnight battery drain on standby mode was abt 9-10% n Now its abt 2-3%.
I started off with CM7 , though it is a very good ROM you won't get battery fix which you are looking for..still you should give it a try..may be it will work for you..
I tried 3-4 More ROMS before settling on MIUI..I keep coming back to it coz the battery life on it just amazing!!!...I get 20 hours+ on moderate usage..
Also radio for a ROM matters a lot...your battery life depends hugely on it...I tried about 6 different radios tll I found the correct one..
Also If you like Sense too much then you can try LeeDroid n RcMixHD both are very good Roms...though RcMicHD is better acc. to me..
So I think you should try these 3-4 Roms n see which suits you best.Hope I helped
Hi, I wholeheartedly agree with aradhyat.
MIUI IMO has all the benefits of Android & Cyanogen + Excellent UI Design.
Your warranty is safe. jkoljo contacted HTC and confirmed that software modifications do not void the warranty. Your carrier/network maybe a bit funny though.
Thanks heaps guys for such quick responses!
If flashing the rom doesnt void warranty, thats just superb. So I will give the mentioned rom a go and see how it works for me. Any tips for a guy who has never flashed a rom or anything like it? I'm pretty good with computers but just havent had any experience on this side.
Also, one question that was unanswered, is this normal for a battery to act this way on a stock rom? I mean the way its acting up for me, drains almost 60% while just sitting in my pocket or on my desk. Did any one of you also experience such a sucky battery life before flashing your roms?
No, your battery should not drain that fast under those conditions. It could be simply a misconfigured app that's hogging your juice.
What firmware are you currently using?
Andriod Version:
2.2
Baseband Version:
12.28b.60.140eU_26.03.02.26_M
Kernel Version:
2.6.32.21-g66cfb7a
[email protected] #1
Tue Oct 26 15:58:17 CST 2010
Build Number:
1.32.861.5 CL277010 release-keys
Software Number:
1.32.861.5
Browser Version:
WebKit 3.1
well, no, not really, its not normal for the battery to act like that with Stock ROM.
I think it depends on your initial first battery charge time.
::The following story is copyrighted!::
me and my 3 brothers all got the Desire HD.
my first brother charged for approx 20hrs at the first time with the phone being closed, and his battery is fine.
my 2nd brother charged till the battery got full with the phone on, and his battery finishes in half a day without alot of usage.
They both warned me, 1st brother told me to charge for 20hrs, second told me to charge for 24hrs, i charged inbetween (22hrs), and my battery is good!
(but true story)
:::::::
my overnight battery drainage is 3%. once i didnt use it for a whole day, and it was still in its 90's.
I think it depends on how you intially charge your phone, it matters greatly (HTC recommends 8hrs charge at first)
Great, your firmware is Ok for rooting directly.
Follow this thread -- > HERE
Then this one --> HERE
There is some overlap, i.e Visionary so no need to perform that twice.
Once done. Install ROM Manager from the market, and flash Recovery from there.
Use 3.x.x.x for Gingerbread based ROMs
Or 2.x.x.x for FroYo based ROMs.
Now you are ready to flash some ROMs!
I turned it on the second I unboxed it (being the impatient pr**k I am). Does that mean I need a new battery? Or is there a remedy?
If you are experiencing such huge battery drain, I think you should get it checked b'coz Even when on stock I never had that much problem.t
Lol..I did the same but did you let it discharge it completely before charging it again or charged it right away after playing with it a little ..
coz I switched mine on as soon as i bought it but let it drain before charging for about 10-12 hours for the first time...
Yea, need new battery.
(try charging battery for a long time, i dont know if it'll help, but it wont hurt to try - IF that doesnt work, then i strongly recommend a new battery)
I was going mad waiting 22hrs!!!, but that meant wayy better battery power!
Search google or something on how to use the battery properly. i've had many issues in the past with batteries, but after reading articles, my batteries last longer now
Not sure if I remember what I did after playing with it, the excitement was so great I forgot about anything and everything else that mattered at that time
Sweet, thanks heaps for your help guys. Will be calling HTC and my service provider today just to double check with them too and afterwards flashing. I'm thinking of going for RcMixHD as alot of people have only good things to say about that rom. Any thoughts or ideas?
Turns out I had 28 days from date of purchase to get it swapped on the spot if there were any issues with the handset. Today was the 28th day, how fortunate!
Anyway, had it replaced and its on charge now, wont be turning it on any time soon though
just some advice
hey just a few words of advice from someone that has done a lot of flashing on numerous phones with numerous software types.
i reccomend getting a few little apps;
1. Titanium Backup (for safety i only back up apps I install + data)
2. SMS Backup and Restore (specifically for backing up sms/mms and works across different roms and even handsets)
3. Faster Fix (just in case if your phone doesnt set gps pool correctly causing a delay in time for fix
and just generally its pretty straight forward how to flash different roms especially after you do it a few times. but i do reccoment patience and time, and you will be fine and if anything happens just ask, everyone ehre is happy to help
Regards
Sent from HTC DHD MIUI 1.4.29 SUPER MR GARAK ROM using tapatalk
BEFORE POSTING QUESTIONS CHECK THE FORUM / THREAD
consideration and moderation is vital to the community
just because something works for you doesn't mean it will for someone else
DHDRookie said:
Turns out I had 28 days from date of purchase to get it swapped on the spot if there were any issues with the handset. Today was the 28th day, how fortunate!
Anyway, had it replaced and its on charge now, wont be turning it on any time soon though
Click to expand...
Click to collapse
Hahaha, lucky u! And good luck with ur new battery
Sent from my Desire HD
Started charging at 5pm yesterday and now its 1 30pm, think I'll take a nap before I get down to some serious flashing business. Thanks heaps for your help guys, some day I'll pay back in the form of experience and maybe add something to this community.

[Q] Fix/avoid network process 0 eating the battery on root

I suppose some of you have encountered this problem before, some might not even know about it. Found a few threads on other device forum, but none for the Wildfire.
The problem stands like this. Have rooted my Wildfire and installed a custom ROM. Changed to SunAbh after a while and used it happily for a month or so. Four days ago got my battery drained of 60% in 20 minutes. Got shocked, but hoped it will fix with time. Noticed an unusual process in the network tab for battery history(*#*#4636#*#*). Flashed another CM7 in hope of fixing it. No effect at all except extending the battery life from 6 hours to 7, in stand by!! According to other threads this is a root problem. Could any of the devs explain it and give some ideas for fixing it?
Flashed the RUU today in hope it will fix at least the battery life. Still, root was nice, and I don't really want to get stuck with 2.1 Sense.
Edit: Seem slike flashing the RUU didn't help either. Got no ideea what to do next....

(Mcgyver: FIXED) MB525 BL7 and Battery: Ongoing

ok long story short. never flashed a kernal before but i decided to try cm10 and went with the gingerbread build and so i flashed the kernal and cm10 compatible rom. it wasnt running very well so i flashed back to the froyo kernal and the compatible cm10 rom.
all was ok but i wanted to go back to cm7 because the phone was considerably faster and so...
today tried to restore one of my cm7 kang back ups from recovery and the phone died. i think what happened is i got mixed up with the back ups and i must have restored the gingerbread cm10 first and without realiszing it flashed the cm7 with a froyo kernal and bang we have a dead phone. it simply wouldnt boot past the google lettering and so when i got home i decided to flash a full sbf and start from scratch however when i tired i got the dreaded battery low error so i followed this
http://forum.xda-developers.com/showthread.php?t=892026
and it worked but rsd lite didnt show my phone. there was simply nothing there when i started it. all very annoying so i uninstalled everything and by the time i started again i got the message battery low.
so my question is can mcgyver work if the battery is actually really low say 10-20 per cent or less?
is it worth buying a new fully charged battery and using that?
why wouldnt rsd lite recognize my phone?
is there anyway to charge the battery when it is like this?
nb. i am running windows 7 sp1 and have installed the latest drivers and rsd lite am my phone is a moto defy m525 red lense.
all very annoying and in five years of rooting and flashing i have never been in a situation where i couldnt recover it. too be honest i have been here before with the defy but i had a spare battery and a proper wall charger and so that was problem solved but i dont own them anymore and i am now not sure/ cant remember if a simple full battery will help hence the questions.
In theory it should work. You are supplying the terminals with the intended 5V and a ground.
However it is recommended to charge your battery, use an external battery charger and then flash the SBF. Its hell of a risk trying to flash SBF with low battery. The phone may actually brick with no way to restore it.
it is strange but using the mcgyver method i can get the bootloader ready to program i simply cant get rsd lite to see my phone and neither does windows. there are loads of posts and threads on this but not many (none actually when the situation i am is mentioned) offer a solution.
so i have ordered a new battery which will hopefully arrive tomorrow and i will see how we get on from there.
rockmonkey1973 said:
it is strange but using the mcgyver method i can get the bootloader ready to program i simply cant get rsd lite to see my phone and neither does windows. there are loads of posts and threads on this but not many (none actually when the situation i am is mentioned) offer a solution.
so i have ordered a new battery which will hopefully arrive tomorrow and i will see how we get on from there.
Click to expand...
Click to collapse
do u have blank flash mode enabled in rsd?
does defy show up in device manager?
try switching usb ports
Sent from my MB526 using xda premium
nogoodusername said:
d
try switching usb ports
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
doh!
amazing i simply used another cable and usb port and then i had to unplug it and plug it again and drivers started to be installed. (i had already installed motos drivers but hey windows wanted more!).
i also went back to the older 4.9 version of rsd lite. it has been a long long time since i have had to do this. installing nordic and will try and install one of my other back ups. all should be well very soon fingers crossed.
looks like the spare battery i bought will be going back then. oh well.
cheers mate your post prompted me to try again and just tinker and it worked so appreciate that.
edit: seems a bit stuck and i am now a little unsure what to do. the android bootscreen is stuck and rsd lite is saying maually power up this phone. i am a little concerned because it is still saying in process even though it has flashed the sbf. i have tried turning it off and nothing happens. it looks like i am actually going to have to unplug the cables remove the mgyver wires and take out the battery and boot it.
bollox. it is dead again so i have to start again. trying a different sbf this time. not sure what happened there. maybe i was too impatient?
honestly not sure what is happening here. i have tried a standard blurred sbf 2.2 and the phone is now stuck on the m animation and rsd lite iks omce again saying manually start this phone. what in the world do i do next?
ah god i will have to do some more reading because it is ****ed. i now have a white light and black screen. rsd lite just remained stuck at 100 per cent in process and manually boot your phone. have tried it three times and that is all i get. not sure if it is because i am flashing froyo sbfs when i have had a 2.3 kernal on the device? it is why i have avoided flashing them in the first place and the first time i ever do bang i get a bricked phone when i try to restore it back to cm7. the phone came with 2.1 so should i be flashing them?
very boring and very very annoying.
getting quite tired of this little game and am on the brink of buying another phone.
ok i have a red lense defy and after much reading i have realised that i must be flashing the wrong sbfs now call me stupid but i actually am very confused about which one i need to flash.
i started on 2.1 originally then i flashed 2.2 and then stuck cm7 on the phone with a froyo kernal. however when i upgraded to cm10 i tried the 2.3 kernal.
so with this background in mind will this work???
http://forum.xda-developers.com/showthread.php?t=1595013
can i follow this to flash the sbf and get root?
or is there another sbf i need to flash. all i need to be able to do is root the phone and install cwm and then i can flash one of my back ups (properly this time).
rockmonkey1973 said:
ok i have a red lense defy and after much reading i have realised that i must be flashing the wrong sbfs now call me stupid but i actually am very confused about which one i need to flash.
i started on 2.1 originally then i flashed 2.2 and then stuck cm7 on the phone with a froyo kernal. however when i upgraded to cm10 i tried the 2.3 kernal.
so with this background in mind will this work???
http://forum.xda-developers.com/showthread.php?t=1595013
can i follow this to flash the sbf and get root?
or is there another sbf i need to flash. all i need to be able to do is root the phone and install cwm and then i can flash one of my back ups (properly this time).
Click to expand...
Click to collapse
Thats for BL7.. Some Defy+ with 2.3.6 were BL7. You definitely don't need to flash it..
Just flash the last SBF that worked for you..
neo.ank said:
Thats for BL7.. Some Defy+ with 2.3.6 were BL7. You definitely don't need to flash it..
Just flash the last SBF that worked for you..
Click to expand...
Click to collapse
yes mate i did the last sbf i flashed over a year ago was nordic and i got the error as listed above. have no idea what i am doing wrong but i must be doing something. trouble is the new battery has arrived and i have already tried a new sbf and still getting the same problem... manually need to reboot the phone.
bit worrying because obviously i will only have a certain number of tries before this new battery dies on me.
edit: absolutely annoying. part of the problem with the guides on here are that they are mostly incomplete. they dont actually tell you everything you need to do. take for instance this the guide for unbricking
http://forum.xda-developers.com/showthread.php?t=1828639
it is totally useless because what he fails to mention is that
to boot into stock recovery you need to hold down the volume button when you power on the phone and you will get a droid with an exclamation mark and then you need to hold down both the volume up and down buttons which after a few seconds will take you to stock recovery. then you can wipe cache etc and the phone will boot. i found this out here (notice how people are telling the guy to simply flash a new sbf!)
http://forum.xda-developers.com/showthread.php?t=1608812
the mad thing is if i had found that simple post just above and knew about the up and down volume buttons i would have fixed the defy on the very first try. that is what is so annoying about this situation.
ok
red lense defy.
long story short i flashed one of the bl7 defy plus gingerbread sbfs.
so i have gone through the root procedure by installing the rooted sbf in rsd lite and then i can install 2nd init 2.0.3 and can get a custom recovery installed.
but every time i try to install cm7.2 euro skank it reverts back to the bootloader. here is what i have done twice in recovery with the exact same result.
wipe cache, data, dalvik and battery stats/ flash cm7 froyo kernal/ then flash the rom/ then flash gapps and then wipe again and then reboot.
when the phone starts again i am once again back to the bootloader and i have to start all over again.
so a very simple question from the position i am in what exactly do i need to do to get cm7 running on the phone.
double post but there are worse crimes!
ok so i have realised that i am stuck on the gingerbread kernal and that any froyo based rom is not gonna work.
wow how did i end up here! bloody hell that is what happens when you start getting ****ed off with the phone not doing what you think it should. anyways it is done now and i have cm7 all up and running and have even been able to make a back up so that if anything happens in the future when i am experimenting then i have a decent base from which to start. everything is working including the camera data wifi calls and well everything except...
i have one all rather serious problem that i really need to get sorted (this is it if i can fix this then i can leave the phone alone).
my battery is not recognized. now the phone runs on the battery which is a big step up from before where i was literally having to leave it plugged in just to keep it on. but the battery icon at the top is displaying a question markn and i dont know if it is charging or not. i also have no idea how much battery is left.
i have flashed both the defy red lense ics battery zip and the defy plus battery fix and i wiped cache dalvik and battery stats before i flashed them and the cache after but neither of these worked.
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
cheers.
rockmonkey1973 said:
yes mate i did the last sbf i flashed over a year ago was nordic and i got the error as listed above. have no idea what i am doing wrong but i must be doing something. trouble is the new battery has arrived and i have already tried a new sbf and still getting the same problem... manually need to reboot the phone.
bit worrying because obviously i will only have a certain number of tries before this new battery dies on me.
edit: absolutely annoying. part of the problem with the guides on here are that they are mostly incomplete. they dont actually tell you everything you need to do. take for instance this the guide for unbricking
http://forum.xda-developers.com/showthread.php?t=1828639
it is totally useless because what he fails to mention is that
to boot into stock recovery you need to hold down the volume button when you power on the phone and you will get a droid with an exclamation mark and then you need to hold down both the volume up and down buttons which after a few seconds will take you to stock recovery. then you can wipe cache etc and the phone will boot. i found this out here (notice how people are telling the guy to simply flash a new sbf!)
http://forum.xda-developers.com/showthread.php?t=1608812
the mad thing is if i had found that simple post just above and knew about the up and down volume buttons i would have fixed the defy on the very first try. that is what is so annoying about this situation.
Click to expand...
Click to collapse
rockmonkey1973 said:
double post but there are worse crimes!
ok so i have realised that i am stuck on the gingerbread kernal and that any froyo based rom is not gonna work.
wow how did i end up here! bloody hell that is what happens when you start getting ****ed off with the phone not doing what you think it should. anyways it is done now and i have cm7 all up and running and have even been able to make a back up so that if anything happens in the future when i am experimenting then i have a decent base from which to start. everything is working including the camera data wifi calls and well everything except...
i have one all rather serious problem that i really need to get sorted (this is it if i can fix this then i can leave the phone alone).
my battery is not recognized. now the phone runs on the battery which is a big step up from before where i was literally having to leave it plugged in just to keep it on. but the battery icon at the top is displaying a question markn and i dont know if it is charging or not. i also have no idea how much battery is left.
i have flashed both the defy red lense ics battery zip and the defy plus battery fix and i wiped cache dalvik and battery stats before i flashed them and the cache after but neither of these worked.
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
cheers.
Click to expand...
Click to collapse
First of all Stop whining about the guides being incomplete. They have helped a lot of people before you and are still helping.. If you mean every post should mention trivial stuff like booting into recovery and wiping data then just imagine the redundancy of the stuff.
If only you were patient enough to read before reacting. Defy Beginner's guide clearly mention 'bout booting into recovery & bootloader so its your folly for not collecting the info before processing..
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
Click to expand...
Click to collapse
Don't know what you've wasted your day on, but all I can suggest is flash the battery fix for Defy+. Search for it. not difficult to find.
neo.ank said:
First of all Stop whining about the guides being incomplete. They have helped a lot of people before you and are still helping.. If you mean every post should mention trivial stuff like booting into recovery and wiping data then just imagine the redundancy of the stuff.
If only you were patient enough to read before reacting. Defy Beginner's guide clearly mention 'bout booting into recovery & bootloader so its your folly for not collecting the info before processing..
Click to expand...
Click to collapse
whining! i didnt think i was whining although i can get annoyed and sometimes my frustration is vented without thinking. i accept that the phone being where it is is indeed my fault. in fact if i had just left it alone then it would have been running as well as it ever did. i am also a great advocate of the developers who spend there time providing us roms and tools for us to use and i can say hand on heart i appreciate the fine work they do often for free. i am also an avid reader of the guides being a simple bod with very little knowledge of flashing hacking and what not and they have saved my bacon more times than i care to remember over the last four or five years. and so you are spot on the guides help a lot... not just me but many before me and most likely many after and give us mere mortals the chance to stay current with firmware long after the manufacturer has abandoned the phone. so while i may have been complaining rather angrily i was not whining.
the fact is that guide is incomplete. not only is it incomplete but it is the one that is linked to on the wiki as the guide to follow on how to unbrick your phone.
if you are like me a tinkerer who every once in a while likes to try out a new rom and who doesnt know the every inner workings of the procedures and who needs to follow instructions then i think the least you can expect is for the definitive guide to be correct! i mean that isnt too much to ask for is it.
so yes i do expect them to list every basic important step one must follow to fix the phone because that is what instructions do they guide people who dont know what they are doing. that is there sole purpose and if they dont do that job then they should either be edited so they do or deleted.
and yes yesterday i was very annoyed at the fact that the guide i was following does not actually tell you exactly what one should do and i can promise you if it had of done then i would not be in the position i am in it is as simple as that. i mean you cant seriously expect people to think oh right these are the instructions for unbricking the phone but i bet you they aint right so i had better read some more instructions for the same thing... and hey they might not be complete as well so i had better read yet another set just in case. leave it out will you.
at the end of the day it doesnt matter and at the risk of repeating myself i know that if i had left well alone the phone would be fine so ultimately i have no one else to blame but myself. if i had been a little more patient and less stressed wondering why the phone wouldnt boot after what appeared to be a successful flash then i would have got there in the end without being stuck on a gingerbread kernal.
neo.ank said:
Don't know what you've wasted your day on, but all I can suggest is flash the battery fix for Defy+. Search for it. not difficult to find.
Click to expand...
Click to collapse
well if you had read through this thread then you may have seen i have wasted a day and a half on quite a lot of reading as it goes. you may have also seen that i have flashed 2 battery fixes and that they havent helped. so i am wondering if you know what else i could do to fix the problem? if you do and you dont mind telling me then i would be grateful. if you dont then no big deal... i will read through a few more threads and see if i cant get to the bottom of it.
EDIT: I have reread what i wrote and i take that back the guide is far from useless in fact it is excellent and i mean that. in every other way it is spot on and is the de facto guide to sorting yourself out of a hole. but it does miss out some vital information that (i think at least) really should be there. still water under the bridge and all that. we are were we are and one must move on. bottom line it is only a phone and if it comes to it i will buy another. the only reason i havent actually bought another so far is the buld quality and form factor of the defy is still yet to be bettered. but maybe it is a sign a message from above telling me to move on to pastures new.... although i would still like to fix the battery issue.
ok it is fixed. as i was writing this reply i installed the white rabbit rom (which i read included red lense battery fixes). true to its word there are five downloadable files. i got four (one woudnt download) and rebooted the system and hey presto.
well what a difference a day and a decent nights kip make. and colour me impressed. this rom is a work of genius. i see it is based on euro kangs cm7 effort with a few nice (well actually loads) extras thrown in for good measure. have to say i am really liking it. calls data wifi camera and battery all work and it looks and feels swift and very polished.
so all is well that ends well. and what a journey. man all i wanted to do was restore cm7 from my back ups. flashing the gingerbread based cm10 before i did it i reckon screwed me and i didnt realise what i had done until after when it wouldnt boot. however xda saved the day as it always does (even if it did take me quite a lot time to get there this time round). i may even write a mini guide but then either no one would bother reading it or i would get loads of people whining at me telling me how it aint right so i think i will avoid that little task and leave it to people more brave and knowledgeable than i.
cheers all for the help in this thread, the time taken by others to write stuff down and the people who provide us with some great software for our ageing but still great phone.
me to
pls help
jalal-jap said:
me to
pls help
Click to expand...
Click to collapse
if you need help mate then a little bit more info is gonna be required.
i will say this that i havent quite fixed it completely. i have the rom running sweet as a pie and the phone will work away from a power source but the battery percent/ icon remains locked at 100 per cent so i have no way of knowing if the phone is charging. when i plug it in to my laptop it says usb connected but again it doesnt list it as charging. so i have no way of knowing if the battery is actually getting charged or how much is really left.
i am also far from an expert more a bumbling old timer who rarely posts here unless desperate.
bear all that in mind and i will do all i can to help (provided you specifically say what you want help with)
edit: lmao... i couldnt have picked a worse sbf to flash. amazing. i have been so so careful in all the time i have owned this phone (over a year i reckon now) and i may have finally actually broken it.
i aint even certain i can charge the battery and once it runs down it will simply die. obviously there is hope that someone will come up with a downgrade method at some point in the future but for the time being i think the phone is ****ed.
i will try ics tomorrow and see if i can get any joy there but i think the only way i can now use the phone is to buy an external battery charger. funny really i used to own both a spare battery and a charger for this very reason and yet i sold them when i got rid of the old defy. so i am gonna have to buy one off ebay tomorrow and use it that way. at least then i will be able to use the phone.
rockmonkey1973 said:
if you need help mate then a little bit more info is gonna be required.
i will say this that i havent quite fixed it completely. i have the rom running sweet as a pie and the phone will work away from a power source but the battery percent/ icon remains locked at 100 per cent so i have no way of knowing if the phone is charging. when i plug it in to my laptop it says usb connected but again it doesnt list it as charging. so i have no way of knowing if the battery is actually getting charged or how much is really left.
i am also far from an expert more a bumbling old timer who rarely posts here unless desperate.
bear all that in mind and i will do all i can to help (provided you specifically say what you want help with)
edit: lmao... i couldnt have picked a worse sbf to flash. amazing. i have been so so careful in all the time i have owned this phone (over a year i reckon now) and i may have finally actually broken it.
i aint even certain i can charge the battery and once it runs down it will simply die. obviously there is hope that someone will come up with a downgrade method at some point in the future but for the time being i think the phone is ****ed.
i will try ics tomorrow and see if i can get any joy there but i think the only way i can now use the phone is to buy an external battery charger. funny really i used to own both a spare battery and a charger for this very reason and yet i sold them when i got rid of the old defy. so i am gonna have to buy one off ebay tomorrow and use it that way. at least then i will be able to use the phone.
Click to expand...
Click to collapse
You're on BL7 now and there's a reason people advise to avoid it. Most of the fixes and scripts doesn't work with BL7 including the battery fixes.
I'd suggest you to go for Quarx's build for GB kernel (along with the battery fix), Randomly flashing ROMs and fixes won't help.
Moreover, I strongly recommend you to search and read carefully. You're not the first one to face the problem, and there's a solution. Even if you waste(?) a couple of days reading 'bout it, it won't kill your phone, but if you do something out of desperation it might.
neo.ank said:
Moreover, I strongly recommend you to search and read carefully. You're not the first one to face the problem, and there's a solution. Even if you waste(?) a couple of days reading 'bout it, it won't kill your phone, but if you do something out of desperation it might.
Click to expand...
Click to collapse
i take it you mean this like in retrospect? of course you are right a deep breath and a walk does wonders for a fuddled head and is far better than simply rushing into the next desperate attempt to repair. however it is easy to say this after the event yes!
the battery wont charge and if i flash another rom it gives me the big battery icon with question mark so i am once again stuck in a corner with no where to go. basically it is ****ed because none of the battery fixes work. the battery works when there is power in it but it just wont charge when in the phone. because the battery ran down last night the only way i can use my phone at the moment is tethered to the mcgyver trick.
so the plan is to buy a separate charger and use that to charge the battery. then i reckon i should be at least able use the phone (although this yet to be tested).
amazing seriously amazing. a year of owning this phone a year of flashing and hacking and being ultra conservative and then all it takes is a few minutes of madness and it is royally screwed. the crying shame about it is that i have installed the best rom i have ever seen in the white rabbit and if the external charger doesnt work i wont get to play with it! still live and learn.
edit: by the way do you know if the mcgyver trick actually charges the battery?
.
rockmonkey1973 said:
i take it you mean this like in retrospect? of course you are right a deep breath and a walk does wonders for a fuddled head and is far better than simply rushing into the next desperate attempt to repair. however it is easy to say this after the event yes!
the battery wont charge and if i flash another rom it gives me the big battery icon with question mark so i am once again stuck in a corner with no where to go. basically it is ****ed because none of the battery fixes work. the battery works when there is power in it but it just wont charge when in the phone. because the battery ran down last night the only way i can use my phone at the moment is tethered to the mcgyver trick.
so the plan is to buy a separate charger and use that to charge the battery. then i reckon i should be at least able use the phone (although this yet to be tested).
amazing seriously amazing. a year of owning this phone a year of flashing and hacking and being ultra conservative and then all it takes is a few minutes of madness and it is royally screwed. the crying shame about it is that i have installed the best rom i have ever seen in the white rabbit and if the external charger doesnt work i wont get to play with it! still live and learn.
edit: by the way do you know if the mcgyver trick actually charges the battery?
.
Click to expand...
Click to collapse
The battery fixes replace your battd.bin binary file which stores the info about the battery. Surprisingly there isn't a single binary that work with each phone, it acts weirdly and not sure what fix will work for a particular phone.. I again suggest you, every battery fix you find. You're not the first one to face the problem and its been sorted for many..
Mcgyver just supply the device with intended charge as the battery does. It doesn't charge the battery.
Don't know if you tried this one.
Defy Red Lens Battery Fix
neo.ank said:
The battery fixes replace your battd.bin binary file which stores the info about the battery. Surprisingly there isn't a single binary that work with each phone, it acts weirdly and not sure what fix will work for a particular phone.. I again suggest you, every battery fix you find. You're not the first one to face the problem and its been sorted for many..
Mcgyver just supply the device with intended charge as the battery does. It doesn't charge the battery.
Don't know if you tried this one.
Defy Red Lens Battery Fix
Click to expand...
Click to collapse
i have tried it mate. i have also tired the ics defy red lense and the white rabbit rom had four of them available to download. none of them have worked. basically as it is now the phone will not stay on without the mcgyver leads and the battery wont charge. i have flashed 6 different battery fixes.
edit: it is strange once i have given it a blast on mcgyver for an hour or so i can then use the phone normally. however the battery is locked at 100 per cent and there is no indication it is charging when a usb lead is plugged in. seriously i have tried 6 of the fixes and none have actually worked.
if you are saying there is a fix for this then i would love to know what it is because i havent found one yet.
edit again!!!: ok this is strange because now when i plug it in to a usb lead the green light appears as if it was charging. very very strange this. i mean like really ****ing weird.
final edit: ok i am officially giving up. it has beaten me and for the first time ever i have got myself into a situation that i cant get out of. who would have thought a simple battery would be the cause of so much ****ing grief. anyway. for total clarity.
i am now running white rabbit rom runs great highly recommended and way quicker than the cm10 efforts that are being worked on at the moment. i have tried 6 battery fixes. none work. i am sometimes able to use the phone without being connected to the mcgyver leads but the battery remains locked at 100 per cent. other times the phone dies and the only way to boot it again is the mcgyver leads. if i do that then battery may change to say 25 per cent or even 75 per cent. basically it is all over the shot. i have tried to install another rom and this leads to the exact same thing. if i turn it on without the mcgyver leads i get the battery error. sometimes when connected to the usb port the phone has the led green light like it is charging then other times it doesnt. it is basically well and truly ****ed up.
so i am giving up. i have wasted quite enough time on a phone i have been thinking of changing as it is. i am gonna buy a sensation as a short term replacement. not as nice as the defy form wise but far faster and with a decent modding community so it will do for now. i will return here every now and then to see if someone comes up with a way to downgrade the bl7 but until that happens the phone is gonna gather dust in my drawer.
i think this thread serves as decent guide as to what shouldnt be done if you want to unbrick your phone (and also includes a few little things that may be missing elsewhere) so hopefully someone can learn from it. cheers all and see you later.
ok well this is the end of this thread (unless i find a proper working solution).
i was unable to charge the phone unless i used the mcyver trick. basically the only way it would accept a charge was if the mcgyver leads were connected. however the battery would charge once the mcgyver leads were in place but stays locked at 100 per cent no matter what i do. it may be the rom i am using but every time i tried another i got the battery error.
i have now bought an external battery charger and spare battery. it works a treat. i simply use the charger to charge one battery and use the other battery to power the phone. when the battery dies i simply switch them around and use the phone as normal.
this way i am no longer having to boot the phone using mcgyver and the only thing i am missing is the ability to charge the battery internally or tell how much battery life is actually left.
so all told all is well that sort of ends well. at least i can carry on using the defy. i was looking at buying another phone but they are all either too big or too slippy/ fragile in the hand. the only one i would like to buy is the orange san diego but there is no root and even worse there is no sim unlock. so for the time being i will stick with the nearly indestructible defy and hope that moto see sense and release a four inch, 8mp onboard camera and better screen carbon copy. fingers crossed.

[Q] M7VZW Died twice, after installing cm11. Over heating and battery draining fast.

Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
ccarr313 said:
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
Click to expand...
Click to collapse
Are you using the stock charger?
Try a different charger on the next phone. Many people have flashed CM11 and don't have those issues so it appears to be your charger that's killing the phones.
Don't think it's the charger. I am seeing more and more threads of people running cm11 a d getting this overheat issues then phone dying. I think it's best that people leaves cm11 alone until it can be fixed. As I have never seen any other Rom act like this.
Sent from my HTC6500LVW using Tapatalk
The only thing i can think of, after resting on it, is that i turned on the DSP manager EQ shortly before it happened each time. Not going to customize the one I am getting today. Just thankful I know enough that I managed to get them both back to s-on / locked / stock RUU before sending them back.....so my warranty will cover them.
And yes, i was using the stock HTC charger that came with the device. Wish i had a meter.
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
peteschlabar said:
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
Click to expand...
Click to collapse
Both phones are dead. Will not charge, will not turn on. They only worked for a few hours after the over heating issue started. Battery continued to drain even after being turned off, and after it was drained it would not charge at all. It was lucky i could even get them back to s-on / locked / stock. And the issue continued after going back to stock. Hardware damaged for sure. So no more testing on those. lol
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Fu5ion said:
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Click to expand...
Click to collapse
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
ccarr313 said:
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
Click to expand...
Click to collapse
They'll let you send as many as you want as long as its under warranty haha. I remember I had to send in the droid bionic 4 times and the droid RAZR twice, both times without any hassle from them. I just had awful luck with those phones, mostly screen-lifting.
Haha. Good to hear. Because I have 10 months of warranty left, and I am a computer modder at heart.....and that has turned me into a custom rom loving phone crazy person. :laugh:
Yeah you've got nothing to worry about there. Just make sure its back to stock. They honestly probably wouldn't say anything if it weren't, but we don't want to give them even more reasons to lock us down more.
I'm having the same issues. I'm on my 4th phone now.
This happened to me on several ROMs. SlimBean 4.3, SlimKat 4.4 now.. and I flashed back to stock while I had a phone that wasn't dead yet.. but it's still happening.
I'm not sure what the deal is. Just happens without rhyme or reason out of the blue one day.
Can anyone recommend flashing anything that might help?
What's responsible for the battery management even if there's no ROM installed? HBoot? Should I re-flash an HBoot to attempt to fix? It's not the ROM, I don't think. If it is, it's something that permanently screws up the phone. I've completely wiped my phone and went to stock. Same issue.
I got my new phone, and s-off'ed / unlocked / flashed cwm recovery, then updated it to 4.3 ota, no issues so far. Scared to put any custom rom after what happened to the last two. But having no issues yet with it, with only a custom recovery and s-off. Have rom manager loaded also, and made a back up since it seems to be running fine now. If anyone isolates this problem and can get a fix going, would make me very happy.
I've noticed that trickster and some of the other CPU performance apps are locking the min CPU speed at the max speed so the phone always stays at top speed. If it stays like that for an extended period of time it will damage the phone. The heat can cause the battery to drain really fast and damage the CPU. If you are on any ROM with a custom kernel I would be on the lookout for this.
Sent from my HTC6500LVW using Tapatalk
I was running CM11 on my nexus Galaxy and I thought my battery was bad. My phone would die after a few hours. I got a new battery and it did the same. I installed slim ROM and now I am getting 10+ hours no problem. Also my phone does not feel like it is going to melt.

Official random rebooting fix

I've read 10 pages on this subforum, random talks about updates, LTE fixes, etc...I've yet to find a single thread giving an official fix for random rebooting? I get this at least 4x a day...regardless of charging or not, SD card installed or not, all the latest updates are installed. I can't be the only one and if so, why isn't this a Sticky issue at the beginning?
I and few have others have the unpleasant experience with rebooting. But it was a little relief that this issue is not just with my Note4.
Laughter is the key to happiness
I had this problem with the early 6.01 stock roms, but it eventually calmed down. Now I get a reboot about once a week. I just assumed the first couple 6.01 stock roms were buggy.
I suppose lots of hardware issues could also cause it.
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
m5james said:
I bought this phone used for $140, I don't know how long it's been running 6.01, but I'm guessing he knew it had this issue. It happens 3-4 a day for the past two weeks. It'll do it while at rest on or off a charger, middle of use, etc. Aren't they're apps that can log what's going on when it fails so this can be resolved, like acatlog? These phones aren't new anymore, it seems there should be a fix out by now...root and overclock while undervolt, remove bloatware from Sprint Normal Apps or whatever it's called, etc
Click to expand...
Click to collapse
So, what rom is the phone running?
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
m5james said:
Bone stock at the moment. I'm going to let a Sprint store give it a looking over, but I'm not hopeful as they're usually useless vs what I can find here myself. At minimum I'm going to root it and remove bloatware, but I haven't reviewed roms yet. Unless this thing stored it in memory, but I was doing a copy and paste last time it froze and rebooted, yet I was still able to paste when it came back on...safe to assume that means it's only a soft reboot?
Click to expand...
Click to collapse
What version of stock? If it's old, some of the early 6.01 roms were pretty buggy. The current stock rom is QC1, which just began to roll out this week. Make sure you are on the most current rom.
Last update I received was this week which turned out to only be a security patch.
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
So I hope I don't jinx myself, but I think a new battery has solved my issue...with some extra steps Let me explain.
Bought the phone used, it'd reset about 3-4x a day...being charged, being used, whatever. It'd reboot anywhere from 80% down to 40%, no rhyme or reason. Sometimes it simply wouldn't allow me to turn it back on, the light would flash blue while dimming in and out, but wouldn't power up the screen. Plugging it back in and it'd be at 30%-45% no matter what. I downloaded an app called Battery Calibration from Meza (sp?) that had a little Android logo with a % on his chest. Resetting may or may not have completely solved the problem had it not soft reset when trying to get battery stats to refresh themselves. It's my understanding that if it reset, it rewrote a battery stat upon reboot, making this step useless.
I got two new batteries from eBay (http://www.ebay.com/itm/112344168032?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT), I charged one in the phone and one on an external charger. Even after running with the new battery, it still reboot once and shutoff around 43% reported on the phone itself. Once plugged in and phone still off, it said it was at 15%. I swapped in the other new and charged battery, powered on the phone, plugged it in until it read 100%. I fired up the Battery Calibration app, unplugged the phone as directed and then to force the battery to drain faster, I let YouTube play uninterrupted for about 4hrs. NOT A SINGLE REBOOT!! For the first time with this phone, it actually stayed on and dipped below the 30%'s and gave me a warning when the battery was getting low (yellow icon) and getting critically low (red icon) before it finally powered itself off at 1%. The phone is now charged on the factory fast charger, this time playing Pandora with the screen off and uninterrupted as well...it's currently sitting at around 57% last I checked.
Once it's fully charged, I'll run it like any normal user (texting, music, etc) without being plugged in and if all works well, it won't reboot.
Hopefully this helps someone with the same issue and is a $8 fix since I bought two batteries.
poit said:
So, you're on most recent rom. Only suggestion I have is full reset. If that doesn't do it you've got a hardware problem.
Click to expand...
Click to collapse
I reset the phone the day I got it.
if your phone often reboot many times in a day, make sure that you don't use Ram kernel V6 or v7 for your Rom, V5 is only version that not make your phone randomly reboot. I try Ram kernel v6 and v7 in Note 7 port rom, note 5 port rom and stock either, and this kernel version always make my phone reboot many many times, unless i flashed v5 or stock kernel, the problem had gone.
I had this problem. I replaced the battery with an official Samsung battery I ordered from Sprint, and the problem went away. Simple as that. No reboots ever since.
Purchased a new battery from Amazon, Samsung OEM, problem solved. Put back old battery guess what it started again but only when battery reached 70% of the original charge. So it must be the battery memory problem.
Sent from my SM-N910P using Tapatalk
Four batteries later and this still happens. Can this be addressed via rooting and then undervolting? I remember phones of the past where people would overclock for speed and undervolt for battery life, but one way too high or too low and you'd either get random rebooting or freezing. This is so god damn annoying!!!!!!

Categories

Resources