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.
Related
I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
tannerw_2010 said:
I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
Click to expand...
Click to collapse
I used to get it too. It stopped after I flashed (from hboot) the new radio, pri, and rpm, then updated ROM base to sense w/2.3.4 base. Try that, and of course, full wipe, sometimes random reboots is from dirty flashing oh yeah, and try making sure your VM heap is 42m or less in the /system/build.prop
tannerw_2010 said:
I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
Click to expand...
Click to collapse
il Duce said:
I used to get it too. It stopped after I flashed (from hboot) the new radio, pri, and rpm, then updated ROM base to sense w/2.3.4 base. Try that, and of course, full wipe, sometimes random reboots is from dirty flashing
Click to expand...
Click to collapse
If the above steps don't work to clear the issue, I would suggest loading the latest stock system and kernel. If you still have random reboots on the latest stock system and kernel, it definitely sounds like it could be a possible hardware issue triggering a kernel panic causing the device to reboot.
This level of troubleshooting, determining what is causing the kernel panic and rebooting the device is beyond and most users and goes a bit deeper. Generally, on a fully stock system, this would indicate a serious programming error which should affect many users, or some type of hardware flaw in the specific device.
Random reboots are hard to prove. The best route would be to take the device back to where you purchased and/or Sprint and see if they are able to help you.
Hopefully the steps quoted above by updating the firmware and software to the most recent versions resolve the issue as it could have been a programming bug on HTC/Sprint's part.
Hope the extra information and details help!
here is the reboot fix
http://forum.xda-developers.com/showthread.php?t=1253126&page=2
download it and rename it to PG86IMG and goto bootloader problem solved
---------- Post added at 02:58 AM ---------- Previous post was at 02:07 AM ----------
follow the above link, then follow the link in the post. i would recommend installing the eniter zip package m the one that says nohboot, it has everything in it including the rpm update.
I've had 3 3D's, each running the same software at the time, only one ever did this. I personally think the freezing and reboots are more hardware related than not.
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
I left my phone on the counter near the dish drainer and smoked the usb/mhl port. Another time, I filled the thing with crushed banana. I can charge the battery using an external charger (hasn't burned my house down yet), but can't use the usb port at all. So I set the phone aside for a while.
S-On, rooted, was running Scrosler's Cleanrom DE 1.4. I got tired of my wife's iPhone 4 and started using the ReZound again recently, but got myself into trouble flashing the clockworkmod recovery over my AmonRA and can't go back. I'm stuck on CarbonROM (used HTCDumlock) with no stability unless wifi and mobile data are disabled.
Is it possible to get AmonRA back (or at least restore the nandroid I made with AmonRA) without a usb? What about S-Off without any USB connection?
yimpierre said:
I left my phone on the counter near the dish drainer and smoked the usb/mhl port. Another time, I filled the thing with crushed banana. I can charge the battery using an external charger (hasn't burned my house down yet), but can't use the usb port at all. So I set the phone aside for a while.
S-On, rooted, was running Scrosler's Cleanrom DE 1.4. I got tired of my wife's iPhone 4 and started using the ReZound again recently, but got myself into trouble flashing the clockworkmod recovery over my AmonRA and can't go back. I'm stuck on CarbonROM (used HTCDumlock) with no stability unless wifi and mobile data are disabled.
Is it possible to get AmonRA back (or at least restore the nandroid I made with AmonRA) without a usb? What about S-Off without any USB connection?
Click to expand...
Click to collapse
Kind of a pickle without a working USB port...
You can not gain S-OFF without a working USB connection using any known (Juopunutbear, rumrunner, or firewater) S-OFF method, sorry. Although JTAG may be a possibility.
If Carbon is running and root is working, you could use Goo Manager to install TWRP, it has HTC Dumlock built in, and you could flash in Evervolv or something else more stable (later incarnations of Carbon caused me lots of issues as well). The backups are not compatible between Amon Ra, CWM, and TWRP though.
As far as getting Amon Ra installed without a working USB connection, it MIGHT be possible, but it is over my head... The real issue would be even if you did get it back on and restored your nandroid, being S-ON means you still need to flash your boot.img manually, even from a nandroid restore, which would be another issue altogether and probably highly difficult (if possible at all).
Although, if we are talking water damage and possible banana damage (did I really just type that?!?!) a different ROM may or may not help, this could all be a exercise in futility that one wrong move could brick you.
Hmmm. I did have the phone working well with CleanROM DE, so I know it's at least worth trying. I'm also not afraid of a brick seeing as what I have now is basically no better. Good point about the boot.img. I hadn't thought of that.
Carbon is working and moderately stable when wifi and mobile data are off. When I enable wifi, I tend to go into a boot cycle with 1-2s before reboot to disable it again. When enabling mobile data, I get frequent popups saying something like android.com.phone stopped working, and not data anyways. I do have a working recovery right now in CWM (up to date non-touch). But, I don't think that has HTCDumlock built in.
yimpierre said:
Hmmm. I did have the phone working well with CleanROM DE, so I know it's at least worth trying. I'm also not afraid of a brick seeing as what I have now is basically no better. Good point about the boot.img. I hadn't thought of that.
Carbon is working and moderately stable when wifi and mobile data are off. When I enable wifi, I tend to go into a boot cycle with 1-2s before reboot to disable it again. When enabling mobile data, I get frequent popups saying something like android.com.phone stopped working, and not data anyways. I do have a working recovery right now in CWM (up to date non-touch). But, I don't think that has HTCDumlock built in.
Click to expand...
Click to collapse
Have you tried just booting into CWM, wiping everything except external SD twice, and reflashing Carbon again, the same one so you don't have to try to flash the kernel?
Probably too late now but did you try drying it out via the bag of rice trick?
I found this nice app for getting files on and off via wifi, not doing you much good if your wifi makes you bootloop though.
https://play.google.com/store/apps/details?id=com.dmitril.droidoverwifi
At this point, an SDcard reader would be my investment and store your backups on the internal SDcard. This would allow you to use PH98IMG's. As far as your mobile data and wifi is concerned. It really sounds like you havent flashed the boot.img matched with the rom. If you still have the rom zip about place it on your external sdcard while in rom in a folder called lunar. Run sysrw in terminal emulator then invoke a script named "menu". Choose option 4, then choose the SAME zip you flashed. You might auto-reboot to recovery, just reboot back to system without any changes.
Thanks. I got wifii to run stable. Did a couple more wipes and re-flashed. ES file explorer disappeared, so maybe my previous wipes were insufficient. Also changed from "Launcher" to "Trebuchet", so a couple variables working together. Either way I flashed TWRP now, so I have HTCDumlock again.
Snuzzo, I'll try and follow your steps to see if that fixes mobile data. Not working right now with mobile roaming enabled, LTE or 3G. I can place calls now, though!
EDIT:: ran the Lunar Menu script and flashed the boot.img (seemed successful). wifi is stable, but no data.
At least you now know how to use LunarMenu and can flash a ROM using that instead also with using dumlock. Option 4 reboots you into recovery, let's you do your normal wipes which you then flash the matching ROM zip. Dumlock basically flashes recovery to your boot partition so to flash a rom , you would be flashing boot partition twice. My implementation flashes it only once.
Sent from my Nexus 7 using xda app-developers app
You guys have been a great help. Thanks a lot
It seems my data connectivity issue is unrelated to the ROM i'm using. I must have caused it while tinkering or trying to update firmware. Now I'm on Evervolv with the same issues. Both Carbon and Evervolv are mostly stable with cell signal for calls and wifi, but no mobile data.
TWRP 2.6.3.0
HBOOT 2.21.0000
Radio 1.22.10.0310r/1.22.10.0308r
Is there something I can flash via a PH98IMG.zip that might fix this issue? Or maybe it's an issue with Verizon that they could fix?
I've a feeling it isn't your own Rez. I have a rom cooked with updsated Telephony. If things go right, release is imminent and very soon. No eta promised tho.
Sent from my Nexus 7 using xda app-developers app
yimpierre said:
You guys have been a great help. Thanks a lot
It seems my data connectivity issue is unrelated to the ROM i'm using. I must have caused it while tinkering or trying to update firmware. Now I'm on Evervolv with the same issues. Both Carbon and Evervolv are mostly stable with cell signal for calls and wifi, but no mobile data.
TWRP 2.6.3.0
HBOOT 2.21.0000
Radio 1.22.10.0310r/1.22.10.0308r
Is there something I can flash via a PH98IMG.zip that might fix this issue? Or maybe it's an issue with Verizon that they could fix?
Click to expand...
Click to collapse
you are on a VERY old hboot and radios....that is what could be causing your mobile data issues
REV3NT3CH said:
you are on a VERY old hboot and radios....that is what could be causing your mobile data issues
Click to expand...
Click to collapse
Thanks for joining in! I tried to update these, but was having a hard time. When I was looking at firmware update PH98IMG.zip's, it looked like you need to relock to flash these up, then unlock again (both requiring usb). Is it possible to update hboot and radios without doing this?
yimpierre said:
Thanks for joining in! I tried to update these, but was having a hard time. When I was looking at firmware update PH98IMG.zip's, it looked like you need to relock to flash these up, then unlock again (both requiring usb). Is it possible to update hboot and radios without doing this?
Click to expand...
Click to collapse
also need to be s-off to do this....with broken usb though only possibility i would say is on pure stock youd have to do all the updates givin by them...including stock recovery as well...and relocked bootloader is required...im wondering if theres a way around this that can be possibly worked in somehow...this is a tight predicament with the phone having no usb function and s-on though
1I went back to an old ICS rom (CleanROM DE 1.4) and got the same issue. Everything works except no data. I thought I'd post an update, but it's not so pressing here: LG G2 is in the mail!
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Messed_sensation said:
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
es0tericcha0s said:
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
Click to expand...
Click to collapse
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Messed_sensation said:
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Click to expand...
Click to collapse
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Thank you for all your help and suggestion:good:. I am now running the Android Revolution HD.
This is a huge change from my iphone 4.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Messed_sensation said:
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Click to expand...
Click to collapse
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
es0tericcha0s said:
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
Click to expand...
Click to collapse
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Messed_sensation said:
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Click to expand...
Click to collapse
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
es0tericcha0s said:
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
Click to expand...
Click to collapse
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Messed_sensation said:
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Click to expand...
Click to collapse
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
es0tericcha0s said:
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
Click to expand...
Click to collapse
I think it is my battery. I picked up an Anker and the phone is now at 20% after 21hrs. Is there a way to get Emoji to work on my phone? When people SMS me, on the lock screen they show up as a question mark in a box but when i go to read the text message there is nothing there.
Using a different keyboard will let you send Emojis, but not really sure about enabling the view from other people's messages off the top of my head, sorry. I recommend SwiftKey for a great keyboard replacement with lots of built in Emojis.
So my girlfriend's EVO 4G LTE is a bit of.. well, I'm gonna say bastard. I'm not new when it comes to rooting devices but I've never had to deal with one that fought me so much.
I've been through this adventure many times with it, and it gets more complicated each time. Here is what's happened with it so far.
It was stock, and it was terrible. It lagged so much, despite factory resets, that apps like google maps were completely unusable. It got no battery life AT ALL, and was generally freeze-happy and miserable.
So then I s-off'd it and after learning all its quirks, installed recovery and CM 11.2 (I think? It's been a year)
This worked great! For.. a few days. The phone worked, we went on vacation to a roaming area where Sprint had no coverage. We come back, and only the data works, texts and calls do not, and the phone acts like it's not activated. Yay. All attempts to get it activated are met with failure, much to the confusion of the poor sprint person on the line. The phone just will not take, at all. (damn lack of real sim cards..) We tried recovering back to a backup from twrp of the stock firmware but that won't work either? It wouldn't register with sprint even on the backed up version of stock sense. The phone seemed dead at this point. Bricked radio?
So we give up. We bring it to the sprint store, and they do some magic to it, and its back to stock, slow and terrible, but functional. We don't touch it until about three weeks ago.
But, my girlfriend is tired, again, of the terribleness, and asks me to try again. Okay, sure.
I install TWRP again, so far so good. The phone is still S-OFF from last time, which is nice. I go to install CM11.2 from the files used from last time (the MD5 does check out correct) But, the phone complains about not having a new enough bootloader. ???? (So I assume sprint downgraded the bootloader in the process of fixing it. somehow)
I forget the exact numbers, but we can't install CM11.2, only 10. or 10.whatever. the newest 10. Okay, fine. I gather a new set of cyanogen files, gapps, whatever, and flash all of that, so far so good.
This time it works, and stays working! Yay! So I thought.
As it turns out, its on a very old version of android (so old that it goes into a special usb file host mode when usb is plugged in) and more importantly, the camera is TERRIBLE. I've read that the evo 4g lte uses a special ImageSense chip to boost camera performance, and that cyanogen 10 does not support it. I can tell, because the camera is absolutely terrible. The battery life also is terrible, presumably because it lacks optimizations. It had way better battery life on CM11.2 when it worked. Other then that, its working just fine, but the camera is just unacceptable.
So, I want to know what to do from here. I see a few paths.
plan A:
update HBOOT to a newer version to allow the install of CM11.2
(how do I do that? I heard you have to use an RUU, but which RUU? I read that there is some touchscreen driver that is an issue depending on what version you run)
(Once I install the ruu is it business as usual, install twrp and then flash cyanogen like normal? Will it do the crazy not activation thing again? was that a fluke??)
plan B:
update HBOOT, but to a much newer one that allows the install of CM12 or whatever the newer ones are. Presumably updating past the touch screen driver issue and not allowing us to go back to an old version.
(once again, what do I need to do that? Is this advisable? I quite prefer the idea of running a newer version. So if this is the better idea, I will do it.)
I thank you greatly for your help. I'm not used to it being this complicated. I've read a lot of things about this phone and it seems very conflicting at times. I just want to get straightened out.
yeah, it's probably running like crap because the firmware is so out of date.
use this RUU http://forum.xda-developers.com/showthread.php?t=2653730
then re-flash twrp and another ROM if you want (i've been running cm12.1 for MONTHS) but she might be able to survive just like that. only fear would be staying vulnerable to security threats, but you've been living in that house this whole time anyway.
for a good while i was running this stock 4.3 with root and some xposed modules installed to get the cm functionality that i missed. but seriously, run the RUU, let it activate, then go under settings and update profile and PRL, fire up maps/navigation with GPS on so that it gets a good lock and its cache populated, then you should be good from there.
Thank you!
Can I use the same utility that I used to flash twrp (that one-click thing that seems to support a half million phones) or do I need something special? This sounds very easy to do. Almost too easy, given that the story of this phone's life is that the easiest thing I've ever done to it was take it completely apart to replace its battery.
never used the one-click stuff. flashing recovery via fastboot is simple enough.
get the adb tools, here's some easy instructions for that http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
get the latest twrp from here https://dl.twrp.me/jewel/
then follow these directions to flash twrp https://wiki.cyanogenmod.org/w/Install_CM_for_jewel#Installing_a_custom_recovery_using_fastboot
if not installing cm or any other rooted rom (you want to root stock) get supersu from here http://forum.xda-developers.com/showthread.php?t=1538053 and use the twrp installable zip
If you've gone through the trouble to S-Off, then fastboot flash the latest TWRP (3.0.2.0, I believe), which supports the new partition layout (extra 4gig of internal SD space).
From there, flash the official 651.4 developers version, go through the device setup which updates your PRL, then shut it down and reboot to TWRP and flash the latest CM12.1 and a proper gapps package (I use "stock", which is a bit much for some, but I like having everything available to me).
The one thing I do that most don't is to disable zRam and enable swap with my own script I wrote specifically for the external SD I formatted as vFat/ext4/swap.
After doing all this, I do not have the issues you seem to have, and the PRL seems to stay from the last install of stock Sense 5. Even with all the apps I have installed, it's still fairly snappy. Facebook/Messenger, and other memory hogging apps run smooth with no discernable lag, unless there's network issues.
YMMV, but look into using an app like "Ampre" to measure battery life and gauge if the battery is going bad or not.
Outside of that, there's not much left to do with these older devices that hasn't been done already.