I managed to unlock the bootloader and root the phone using the All-In-One-ToolKit. I'm running Viper ROM, after installing the ROM i installed the Kernel "Stock DSB System Write Boot.img" from their instructions. After i downloaded and extracted the Kernel "HTC DNA LK_DNA 0.9.4" I flashed the boot.img trough the Toolkit and then flashed the modules.zip folder trough Recovery Mode. I have two noob questions =/
1) Did i flashed the Kernel Correctly?
2) My current battery is at 92% with the History showing [1h 14m on Battery] Is it normal that i used up 8% already in such a short amount of time? I haven't used the phone at all after i charged it, no txt,calls,facebook,internet....nothing.
Painkiller006 said:
I managed to unlock the bootloader and root the phone using the All-In-One-ToolKit. I'm running Viper ROM, after installing the ROM i installed the Kernel "Stock DSB System Write Boot.img" from their instructions. After i downloaded and extracted the Kernel "HTC DNA LK_DNA 0.9.4" I flashed the boot.img trough the Toolkit and then flashed the modules.zip folder trough Recovery Mode. I have two noob questions =/
1) Did i flashed the Kernel Correctly?
2) My current battery is at 92% with the History showing [1h 14m on Battery] Is it normal that i used up 8% already in such a short amount of time? I haven't used the phone at all after i charged it, no txt,calls,facebook,internet....nothing.
Click to expand...
Click to collapse
Only thing you didn't mention is wipe cache and dalvik cache before or after modules flash. Wonder if battery drain due to initial Google synchronization, etc. If that usage persists, it's definitely abnormal, barring bad reception, etc.
yearn2burn said:
Only thing you didn't mention is wipe cache and dalvik cache before or after modules flash. Wonder if battery drain due to initial Google synchronization, etc. If that usage persists, it's definitely abnormal, barring bad reception, etc.
Click to expand...
Click to collapse
I wiped the cache and dalvik after flashing the modules. So I went home yesterday and flashed the boot.img provided in the Viper thread, then flashed the boot.img from LK followed by the modules and a wipe of the cache and dalvik cache. Seems to be running fine now, battery is currently at 31% with 9h 34m on battery. That should be good battery life right?
Check the thread in DNA development original, there is screen shots of what people get with their battery, that way u can compare.
droid DNA
Painkiller006 said:
I wiped the cache and dalvik after flashing the modules. So I went home yesterday and flashed the boot.img provided in the Viper thread, then flashed the boot.img from LK followed by the modules and a wipe of the cache and dalvik cache. Seems to be running fine now, battery is currently at 31% with 9h 34m on battery. That should be good battery life right?
Click to expand...
Click to collapse
What type of usage did you do in the 9.5 hours? There are pics of under the LK thread in the DNA original dev section. Hope things work out.
I have on it the LK 0.9.4 with the LRS GSM Rome and I am very happy with it, but if you do nothing and just 9.5 hours get along then something is wrong, so I'm from even 20-24 hours and make it something Internet, XDA app, SMS and calls.
On the night in standby do I need only 6-8%
I´have the XT912. Ive been on 4.1.2 OTA for about 6 weeks. Recently I have been having some odd battery issues. When the phone is off and plugged into the wall it rarely shoes less than 80% charge. If I charge it to 100%, then boot up the phone, the battery meter will sometimes be at 100%, and at other times be at 50% or so. The phone will then quickly discharge, or at least give low battery warnings (usually the 5% warning comes out of nowhere). Sometimes the phone will abruptly shut off. If Im lucky I will get 20 mins of use. When I plug it back into the wall I again get 80% or something like that.
I tried factory resetting the phone, with basically no luck, though I do seem to get a bit more use out of the phone unplugged. In the process of resetting the phone I lost root (I have the superuser app but it fails to gain root access).
Some things to note:
I recently started using an external RavPower battery, which roughly coincides with these issues, though I used it fine for quite a while with no problems.
Im travelling in Peru and some of the outlets may be operating at odd voltages
Im thinking I need to use the JellyBean utility to reflash to stock (wipe data) then go from there. Any advice?
Thanks
Nobody has anything to say? Might reflashing help or is my battery just toast?
Please, any advice would be greatly appreciated. Im worried about going forward with the flash with the battery issues looming. The device isnt very usable now, but if I brick it Ill have no phone/computer for 6 weeks.
Thanks.
use matt utility and gain root
then install BMM and after a night left plugged in, enter recovery and wipe battery stats, reboot and unplug
heblu said:
use matt utility and gain root
then install BMM and after a night left plugged in, enter recovery and wipe battery stats, reboot and unplug
Click to expand...
Click to collapse
Thanks! So I should use option 3 (RAZR Blade) first, right? No need to reflash with option 1?
nlhaines12 said:
Thanks! So I should use option 3 (RAZR Blade) first, right? No need to reflash with option 1?
Click to expand...
Click to collapse
didn't use it before, I'm a gsm user
follow tutorial
heblu said:
didn't use it before, I'm a gsm user
follow tutorial
Click to expand...
Click to collapse
Gained root, installled BMM, wiped battery stats, but still had issues.
Uninstalled BMM, installed safestrap 3.11 + LiquidSmooth 2.3 - still having issues.
Tried dumping battery stats since then with "Battery Calibration" app.
Battery quickly drains from 100% to 50% then shuts off shortly thereafter, however, I can boot into recovery and run the screen for another 1-2 hours, but as soon as I boot into a rom it shuts itself down.
I'm guessing 1 of 2 things is going on:
1) The roms are somehow getting a bad read on how much "juice" is left and shutting down prematurely
2) The battery is shot and cant supply enough current to run the phone+full OS unless its close to fully charged.
Without any knowledge of how batteries work it's hard for me to say which is more likely, or if (2) is even feasible at all. If (1) is a possibility is there a way for me to reflash the stock boot partition to possibly fix the problem?
Any help would be greatly appreciated. I would go ahead and do the Razr Maxx mod, but I am travelling and wouldn't be able to receive the parts, therefore if there is any reasonable chance for a software fix I'm all for making the attempt.
Thanks!
I have read that there is a bug reading batt stats on 4.2.2 roms
Try on a stock rom
heblu said:
I have read that there is a bug reading batt stats on 4.2.2 roms
Try on a stock rom
Click to expand...
Click to collapse
What would be considered a stock ROM? A pure OTA grab or something debloated like WDSEA?
nlhaines12 said:
What would be considered a stock ROM? A pure OTA grab or something debloated like WDSEA?
Click to expand...
Click to collapse
both
heblu said:
both
Click to expand...
Click to collapse
Flashed WDSEA 1.9.16 to ROM slot 1, problem persists.
Do the ROMs in ROM slot x (in safe strap) rely on the ROM loaded in the system slot in any way? Might reflashing the System slot with 4.1.2 OTA fix anythinig? Would reflashing this slot be risky?
Heblu you have been a huge help by the way.
nlhaines12 said:
Flashed WDSEA 1.9.16 to ROM slot 1, problem persists.
Do the ROMs in ROM slot x (in safe strap) rely on the ROM loaded in the system slot in any way? Might reflashing the System slot with 4.1.2 OTA fix anythinig? Would reflashing this slot be risky?
Heblu you have been a huge help by the way.
Click to expand...
Click to collapse
No to all your questions
Noob android modder...
HTC unlocked and rooted my Rez back in late Dec 13. I have had battery issues ever since. I know (through extensive reading these forums and others) this isn't due to root. And my issues are beyond battery, No ROM I have tasted has been stable. Tachyon ION, Paranoid Android, Cyanogenmod 11....similar issues with each, some worse than others. I downloaded BetterBatteryStats yesterday to try and diagnose this, but I am skeptical this is the problem. Biggest issue: battery doesn't give a true reading of its charge, or the rom running (again, all of them) can't accurately read the battery. Case in point: yesterday I wiped phone and installed the cyanogenmod 11 from NEO. I installed better battery stats and fully charged. Battery lasted less than 2 hrs. Plugged in at 10% and let charge for a few hrs. When I unplugged, cyanogen tells me that battery has 44% charge. After immediate reboot, battery shows 94% charge. This has been consistant over the different ROMS.
The other big problem is the constant reboots I experience. Many apps seem to overload the system and forced reboots happen. I realize that I am likely the problem, but I can't seem to figure out why.
I apologize, I know its an old bit, complaining about battery life after root, but compounded with the instability of the ROMS...I suspect I am doing something wrong that I haven't figured out.
Questions:
1. Do I need to manually flash a kernel after/before flashing a ROM?
2. Does being S-ON have anything to do with this?
3. Any tips?
I appreciate any help
loswr86 said:
Noob android modder...
HTC unlocked and rooted my Rez back in late Dec 13. I have had battery issues ever since. I know (through extensive reading these forums and others) this isn't due to root. And my issues are beyond battery, No ROM I have tasted has been stable. Tachyon ION, Paranoid Android, Cyanogenmod 11....similar issues with each, some worse than others. I downloaded BetterBatteryStats yesterday to try and diagnose this, but I am skeptical this is the problem. Biggest issue: battery doesn't give a true reading of its charge, or the rom running (again, all of them) can't accurately read the battery. Case in point: yesterday I wiped phone and installed the cyanogenmod 11 from NEO. I installed better battery stats and fully charged. Battery lasted less than 2 hrs. Plugged in at 10% and let charge for a few hrs. When I unplugged, cyanogen tells me that battery has 44% charge. After immediate reboot, battery shows 94% charge. This has been consistant over the different ROMS.
The other big problem is the constant reboots I experience. Many apps seem to overload the system and forced reboots happen. I realize that I am likely the problem, but I can't seem to figure out why.
I apologize, I know its an old bit, complaining about battery life after root, but compounded with the instability of the ROMS...I suspect I am doing something wrong that I haven't figured out.
Questions:
1. Do I need to manually flash a kernel after/before flashing a ROM?
2. Does being S-ON have anything to do with this?
3. Any tips?
I appreciate any help
Click to expand...
Click to collapse
Answers to your first two questions:
1) After (although it S-ON it technically shouldn't matter)
2) No
Here are some tips, this could be as simple as a battery going bad, i consider a replacement one, either original HTC or Laza would be my recommendation. Also, I would consider going S-OFF, then going through @REV3NT3CH's full downgrade/upgrade guide from start to finish, this seems to be fix for many "odd" issues in the Rezound, I can't really explain why and it somewhat defies logic to downgrade to the oldest version of software available and then upgrade step-by-step through every version, but it has definitely shown it's value as a working solution to many issues.
I kind of suspect a battery, charger, charge port, bad cable, or even dirty/tarnished contact here though... three hours on the charger on a good stock battery that is charging correctly should bring it near full after 3-4 hours, if you are only getting it to 44% something is not right.
acejavelin said:
I kind of suspect a battery, charger, charge port, bad cable, or even dirty/tarnished contact here though... three hours on the charger on a good stock battery that is charging correctly should bring it near full after 3-4 hours, if you are only getting it to 44% something is not right.
Click to expand...
Click to collapse
That's the thing, it says 44% when I pull it off the charger, but if I reboot it, it says 90%+. Multiple cables/ports have been used. Same issue.
Regarding your statement about flashing a kernel post ROM flash, I attempted this with Tachyon and the fuzzy kernel yesterday. ROM installed as expected, it crashed a few times while installing backups from Titanium, and then I flashed the Fuzzy kernel. After the kernel flash the phones screen wouldn't work....I believe the phone was booting, but no screen, just LED notificaion light. Thats when I started over with the Cyanogenmod 11 ROM, which has been the most stable.
Thanks for the advice, I will likely attempt your suggestion about downgrading/upgrading.
loswr86 said:
That's the thing, it says 44% when I pull it off the charger, but if I reboot it, it says 90%+. Multiple cables/ports have been used. Same issue.
Regarding your statement about flashing a kernel post ROM flash, I attempted this with Tachyon and the fuzzy kernel yesterday. ROM installed as expected, it crashed a few times while installing backups from Titanium, and then I flashed the Fuzzy kernel. After the kernel flash the phones screen wouldn't work....I believe the phone was booting, but no screen, just LED notificaion light. Thats when I started over with the Cyanogenmod 11 ROM, which has been the most stable.
Thanks for the advice, I will likely attempt your suggestion about downgrading/upgrading.
Click to expand...
Click to collapse
Always use the kernel that comes with a ROM, until you know it's stable and unless you have a good reason to switch... it is the best match to the ROM and the benefits you get from another kernel are generally marginal at best unless you need a specific feature that is not included in the ROM's kernel.
Proper sequence when installing a ROM when S-ON would be to wipe everything but external SD, then flash ROM, immediately reboot into bootloader and start fastboot, flash the boot.img with "fastboot flash boot boot.img" then reboot. Any other sequence could give questionable results.
Using Titanium backup to restore information in between JB and KitKat (either way) is not recommended, even with root access TiBu has issues restoring into /system in KitKat. It is highly recommended to reinstall all apps from the Play Store and use something like SMS Backup & Restore to handle text message migration.
I would again recommend a new battery, and going S-OFF especially now that the "wire trick" is no longer required using Rumrunner or Firewater S-OFF, then going through the downgrade/upgrade process I mentioned earlier.
So I have been unsuccessful at getting Windows drivers working for my rez. HTC sync and Windows used to identify it, but after I originally rooted it back in Dec, I wiped my laptop clean and set up a dual boot. Since then I haven't been able to get HTC sync to identify the phone, and ADB only works if I am in the TWRP or bootloader. Same with mounting and moving files, recovery only. Since the rumrunner S-OFF exploit needs me to be in Android, I'm in a pickle.
Things I have tried:
Current HTC sync software (Doesn't recognize the phone)
Downloaded and installed the driver from the Rav3nt3ch guide mentioned earlier
Also tried the old version of HTC sync that is mentioned in the same article
acejavelin said:
I can't really explain why and it somewhat defies logic to downgrade to the oldest version of software available and then upgrade step-by-step through every version, but it has definitely shown it's value as a working solution to many issues.
Click to expand...
Click to collapse
to make sense of it. the reason it works is through some flashings or wrong deleteion of files the files that are integrated in system that a ROM does not have these RUU.exe files and OTA (ph98img.zip) files do have and repairs the phone to its neccesary needed state again. a good example to prove it is a typical rom is about 160mb in size and only contains bare necessities really..where as the ruu or ota is usually around 600mb in size and also full flashes the phone to proper partitions and such...as stated in my guide be sure to let phone fully boot and go through first setup of those particular roms....some people skip this step thus not activating their verizon service
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
loswr86 said:
So I have been unsuccessful at getting Windows drivers working for my rez.
Click to expand...
Click to collapse
Are you using windows 8? if so thats your issue.... drivers and programs only fully work and recommended for Windows 7 only bud
Edit: As for your battery issue...is your phone getting rediculously hot....if so this is a hardware issue based on the HT1 motherboards and is not fixable for anyone....my current rez has this issue and is an HT1 motherboard...also very typical issue for this version of the rez...also after a full charge have you tried wiping the battery stats in recovery? this will help give a much more accurate reading
REV3NT3CH said:
Are you using windows 8? if so thats your issue.... drivers and programs only fully work and recommended for Windows 7 only bud
Edit: As for your battery issue...is your phone getting rediculously hot....if so this is a hardware issue based on the HT1 motherboards and is not fixable for anyone....my current rez has this issue and is an HT1 motherboard...also very typical issue for this version of the rez...also after a full charge have you tried wiping the battery stats in recovery? this will help give a much more accurate reading
Click to expand...
Click to collapse
Windows 7. The drivers worked fine back in December prior to me wiping my HDD and setting up a Ubuntu/Win 7 dual boot. I can use ADB just fine if the phone is at the bootloader/recovery. Its only the OS the causes a problem.
Yes, the phone does get quite warm, though since switching to CM11 both heat and battery have improved. Still unacceptable, but improved.
I'll attempt to wipe the battery stats after it charges back up, but I don't see that option in the TWRP 2.5.0.0 I have installed.
**//After being out this evening, I got home and plugged the phone in about 30 min ago. It was at 8% according to CM11. After rebooting into the recovery, TWRP informs me that there is a 66% charge.
loswr86 said:
Windows 7. The drivers worked fine back in December prior to me wiping my HDD and setting up a Ubuntu/Win 7 dual boot. I can use ADB just fine if the phone is at the bootloader/recovery. Its only the OS the causes a problem.
Yes, the phone does get quite warm, though since switching to CM11 both heat and battery have improved. Still unacceptable, but improved.
I'll attempt to wipe the battery stats after it charges back up, but I don't see that option in the TWRP 2.5.0.0 I have installed.
**//After being out this evening, I got home and plugged the phone in about 30 min ago. It was at 8% according to CM11. After rebooting into the recovery, TWRP informs me that there is a 66% charge.
Click to expand...
Click to collapse
wait your on twrp 2.5.0.0 theres a big issue there and prolly why battery stays showing at 66%....you need to be on 2.6.3.0 for jb or kitkat bud....as for wiping battery stats i believe that may be cwm
REV3NT3CH said:
wait your on twrp 2.5.0.0 theres a big issue there and prolly why battery stays showing at 66%....you need to be on 2.6.3.0 for jb or kitkat bud....as for wiping battery stats i believe that may be cwm
Click to expand...
Click to collapse
Clockworkmod 6.0.3.1 is now my recovery, fully installed on the phone. I had been using cwm as the recovery img that I would fastboot boot, then install a ROM. But the actual recovery installed on the phone was TWRP 2.5. Might this be the underlying cause of much of my boggle?
loswr86 said:
Clockworkmod 6.0.3.1 is now my recovery, fully installed on the phone. I had been using cwm as the recovery img that I would fastboot boot, then install a ROM. But the actual recovery installed on the phone was TWRP 2.5. Might this be the underlying cause of much of my boggle?
Click to expand...
Click to collapse
could be...but why a low version of clockworkmod too.... http://forum.xda-developers.com/showthread.php?t=1914215 this is what you want....and if flashing plain andy that uses philz touch and a certain install method
The battery power can not be recognised by the phone?
REV3NT3CH said:
could be...but why a low version of clockworkmod too.... http://forum.xda-developers.com/showthread.php?t=1914215 this is what you want....and if flashing plain andy that uses philz touch and a certain install method
Click to expand...
Click to collapse
Thanks for the link. I simply dl'd what was at the cwm website for the Rez.
loswr86 said:
Thanks for the link. I simply dl'd what was at the cwm website for the Rez.
Click to expand...
Click to collapse
eh...always search the threads bud...all of what you need and updated is here
---------- Post added at 07:50 PM ---------- Previous post was at 07:49 PM ----------
Hermosa said:
The battery power can not be recognised by the phone?
Click to expand...
Click to collapse
on older twrp or miscompiled recoveries it will simply just read as 66% and stay there....a good example...phils touch needs this battery reading part fixed as well as it shows 66% for battery currently
6.0.3.6 installed. Hopefully this oversight is what it takes to improve my experience with android modding. Thanks for your help fellas.
I don't remember having this much trouble modding my old HTC tilt back in the day.
Flashing clockworkmod 6.0.3.6, reinstalling CM 11 via CWM and then flashing the boot.img seems to have fixed my battery issues. After a few days of use, battery is holding charge much better. A note on what I think I was doing wrong, for others:
-I had originally flashed TWRP 5.X
-Then I followed this article explaining how to install custom roms whlie s-on
-I then loaded the various custom roms via the above method with the CWM 6.0.3.1 (Listed on their website)
-Chaos insued
Don't do this.
Hi, in this days I've flash the last miui eu dev rom, then my battery start to discharge 3% in a minute, so I change the ROM to global stable, but the problem still there, so can someone help me with this? What can I do? Help me plase, and thanks for reading my problem
1. if you have root then install gsam battery monitor see how is the battery lost
2. if not then factory reset
3 if not use twrp flash asop extended rom