So my Eris has gotten bad with the "trackball always moving left" problem, and I'm taking it back in to Verizon. I currently have GSB v1.6, and I need to put it back to stock. I dl'ed the RUU (2.36.605.1) and every time I run it, following the instructions, it gives me an error saying I have less than 30% battery power, when the battery is fully charged. Occasionally it just gets stuck on the verifying information screen.
I've tried wiping the battery stats from the recovery, I've tried reinstalling two different versions of HTC Sync, which seemed to get it past the "verifying" screen. I even tried restoring a nand backup of Sense I did before I started flashing roms.
I'm stuck. What would cause it to read 100% as less than 30? Also, while I'm on my stock Sense rom, is there any way to just unroot it without using RUU? It's in the condition it was in the day I rooted.
Edit: It's Error(120) not 220. I typed the wrong one in the title.
prsguitaruser said:
So my Eris has gotten bad with the "trackball always moving left" problem, and I'm taking it back in to Verizon. I currently have GSB v1.6, and I need to put it back to stock. I dl'ed the RUU (2.36.605.1) and every time I run it, following the instructions, it gives me an error saying I have less than 30% battery power, when the battery is fully charged. Occasionally it just gets stuck on the verifying information screen.
I've tried wiping the battery stats from the recovery, I've tried reinstalling two different versions of HTC Sync, which seemed to get it past the "verifying" screen. I even tried restoring a nand backup of Sense I did before I started flashing roms.
I'm stuck. What would cause it to read 100% as less than 30? Also, while I'm on my stock Sense rom, is there any way to just unroot it without using RUU? It's in the condition it was in the day I rooted.
Edit: It's Error(120) not 220. I typed the wrong one in the title.
Click to expand...
Click to collapse
This should be what you want. Good luck! No idea about the battery % issue unless it's just severely out of calibration.
roirraW "edor" ehT said:
This should be what you want. Good luck! No idea about the battery % issue unless it's just severely out of calibration.
Click to expand...
Click to collapse
I didn't even know this existed. Downloading now. Thanks.
prsguitaruser said:
I didn't even know this existed. Downloading now. Thanks.
Click to expand...
Click to collapse
You're welcome!
It worked perfectly. I'm back to unrooted Stock 2.1.
prsguitaruser said:
It worked perfectly. I'm back to unrooted Stock 2.1.
Click to expand...
Click to collapse
Woot! Glad it went smoothly for you.
Related
Hello all,
I've recently rooted my device and flashed eclipse 1.3. Since I've had the device (2 weeks), it has been dropping wifi randomly. It will drop it and pick it up at totally random times. I've tried reflashing, clearing cache and dalvik, flashing mods having to do with wifi, and anything else I can think of.
I've checked all my settings that deal with wifi, and everything checks out. The only thing I haven't tried is a factory reset, but when I purchased the device, it was already done. Does this mean that it is defective? Is there anything else I can try save a factory reset?
Thanks for your help guys.
I would suggest doing this instead:
Get the 2.3.4 SBF and put that onto your phone. This does wipe out everything, so do a backup of your apps and settings before you SBF.
Download Eclipse again to ensure that the previous image wasn't corrupted and flash it after rooting your device
I guess my big question is, what version were you running BEFORE you flashed Eclipse? Was it 2.3.4? If it wasn't, that may be your problem right there, possibly, although most people experience a lot of FCs when they do this.
is it dropping it while the screen is off or on?
I am was running 2.3.4 blur stock rooted. And it happens when the screen is on and off, even when you're using it.
are you running any sort of battery saver application that could possibly be shutting off you wifi
amancini92292 said:
are you running any sort of battery saver application that could possibly be shutting off you wifi
Click to expand...
Click to collapse
No. None. I have battery set to the least saving lol.
mustbepbs said:
No. None. I have battery set to the least saving lol.
Click to expand...
Click to collapse
well with that being said your best bet would be to do what iBolski mentioned and back up contacts and data and do an sbf.
amancini92292 said:
well with that being said your best bet would be to do what iBolski mentioned and back up contacts and data and do an sbf.
Click to expand...
Click to collapse
I'll try that when the 2nd unit work is done and we get cyanogenmod. Thanks fellas. I'll let you know how it goes then.
Well, I sbfed to 2.3.4 and flashed the new update, plus flashed the new eclipse and all the tweaks and it still drops. It has to be hardware. Oh well, eBay bastards.
Update: turned out to be the router. Got a new one and it's all set!
Sent from my Galaxy Nexus using Tapatalk
I'm not sure if other X2's do this, but my battery runs fine. I get a solid 10 hours of hard use out of it.
But lately I noticed that if I simply reboot I get another 20%-50% out of it. Yesterday, it was down to around 30%, restarted, went back up to 80% and drained normally the rest of the night.
Is this normal? Is there a fix or something I can do? I wish I could just get the most out of the battery without having to restart.
I'm just running rooted 2.3.4. I do the whole drain it to 0% once a month thing & fully charge.
--
P.S. I'm not making this up. Lol.
2.3.4 is the problem. There is a battery bug in the software where it reports less battery power than you have. Then, when you reboot, it might shoot up 5% to 10%.
Many custom ROMs have a fix in it. Not sure what the fix is or if you can apply it to the stock ROM.
Eclipse 2.0.x has the fix, but it also requires updating to the unofficial 2.3.5 OTA upgrade.
CM7 is based on 2.3.4 kernel and seems to have the issue resolved as well.
I see. Well, thank you for your help. Sorry if this is a repeated topic.
I just got started in the whole root/flashing "scene" so I'll have to see what I can do about CM7 now.
For those that want to stay on the stock rom, the fix is here.
Thanks, I'll try this out later.
I could use it too but the download link is dead. Thanks
Tried using new file from updated link but it would not work. Hung up at installing. Had to pull battery to restart phone. Any ideas?? Thanks
Probably something wrong with Peppermint's script. I have the original one from my phone. You can give it a try if you want.
http://www.mediafire.com/?a52x45m3dou19us
Thanks. It installed OK this time. I'll be checking to see if it makes a difference. Thanks again for the help.
You're welcome. Hope it works for you.
xtel said:
I see. Well, thank you for your help. Sorry if this is a repeated topic.
I just got started in the whole root/flashing "scene" so I'll have to see what I can do about CM7 now.
Click to expand...
Click to collapse
I bought my mother an x2, rooted and flashed CM7, she gets around 15 hours on the stock battery.
You will notice a huge change in performance, battery and more while you flash any ROM... Good luck, just follow the tutorials here in the forum.
SMILE It's Not Illegal Yet
Hey can anyone help with my battery prob? I got the extended battery from verizon I wiped battery stats after draining it fully and recharging fully twice. I'm running eclipse 1.3, speedy v7, and the cdma unthrottle mods. For some reason my phone eats this battery faster than my stock battery.
Sent from my DROID X2 using Xparent Cyan Tapatalk
I'm trying to test my battery life so I downloaded a 2.17 RUU.exe (Freeza's all in one crashes mid-install for me, it always has...maybe related to eng hboot? probably not but idk) so I could run a stock ROM for the tests (I had intermittent reboots on the ROM I was running previously). I got the ROM all set up, installed my apps, flashed and updated superuser, installed busybox, and updated superuser binary, then I installed a team d3rp skin and leedroid tweaks. I wiped cache, dalvik and rebooted after the leedroid tweaks and when my phone booted up, I saw that wifi just said "error" on it. I didn't think anything of it since all I'm doing is using this ROM to try to drain my battery and I'm going back to another ROM soon and I figured it was something wrong with the kernel (I did not flash a kernel btw), but then I tried to turn on 4g as well (just to drain battery faster) and the 4G wouldn't turn on either; I got the message "4G was unable to start"
Anyone else have this issue? The only thing I can think of is maybe it could be leedroid tweaks was the odexed version, which I had read was what stock ROMs normally "use" (that's probably not the correct terminology, sorry if it isn't.)
Why would you do all of that just to drain your batter?
You could of searched "Battery Drainer" on the play store.
But to answer your question.
It is probably leedroid tweaks. I had this problem once and had to do a full wipe and flash a new Rom,
iTzLOLtrain said:
Why would you do all of that just to drain your batter?
You could of searched "Battery Drainer" on the play store.
But to answer your question.
It is probably leedroid tweaks. I had this problem once and had to do a full wipe and flash a new Rom,
Click to expand...
Click to collapse
Well I have a Seidio 4000 mAh battery and I want to have the ROM somewhat customized since I'll be on it a couple days minimum since I want to record battery history from multiple charges using battery monitor widget. I'll try a reinstall, thanks.
Also, I didn't think to check the store for battery draining apps, I guess I didn't expect there to be apps specifically designed for draining batteries only...
Thank you for the info
I know if a kernel wasn't flashed right can cause borked 4G and WiFi. If your hboot 1.5 . What was the last thing you did new when it happened?
Sent from my PG86100 using xda premium
w0rdOo said:
Well I have a Seidio 4000 mAh battery and I want to have the ROM somewhat customized since I'll be on it a couple days minimum since I want to record battery history from multiple charges using battery monitor widget. I'll try a reinstall, thanks.
Also, I didn't think to check the store for battery draining apps, I guess I didn't expect there to be apps specifically designed for draining batteries only...
Click to expand...
Click to collapse
heres one i used before.
https://play.google.com/store/apps/details?id=com.batterydrainer&hl=en
Drained my 99 percent battery in one hour. (without the vibrate option in the app)
reaper24 said:
I know if a kernel wasn't flashed right can cause borked 4G and WiFi. If your hboot 1.5 . What was the last thing you did new when it happened?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
The last thing I did before it broke was install the skin apk, then I rebooted to recovery, wiped cache+dalvik, then flashed leedroid tweaks odexed
I didn't think a bad kernel flash would bork 4g too. I've never had s-on though. Also, after wifi/4g broke but before trying to do a fresh install, I decided to flash one of chad's stable anthrax kernels, no luck with 4g/wifi, and I tried ziggy's kernel that virus posted in his thread a few days ago, no luck with that either. I'm going to do a fresh install and I'm actually going to add one mod in at a time this time, so I know what breaks it (assuming something actually goes wrong this time around).
How do I check if a ROM is odexed/deodexed if it's already on my phone? I can't exactly pull apart the windows RUU.exe to check, so is there any way of checking thru adb or root explorer, maybe something else similar?
iTzLOLtrain said:
heres one i used before.
https://play.google.com/store/apps/details?id=com.batterydrainer&hl=en
Drained my 99 percent battery in one hour. (without the vibrate option in the app)
Click to expand...
Click to collapse
thanks for the link I'll download that. The guys over in the 3rd party battery database thread would probably like to see this too
Hmm, I still haven't done a fresh install yet but I just installed system tuner...Apparently, neither of the kernels I tried actually flashed, but I have flashed the same exact zips successfully on other ROMs. I'm thinking it may have been the RUU itself that I downloaded, I'm just going to try a 2.08 RUU, take the OTA, then root, recovery, etc as that's the only way I've successfully used an executable RUU in the past without any issues.
Please, nobody else post in this thread, just let it die. Thanks to those who posted to help me out though
I flash a lot. I also have noticed my CM10.1 running like total crap lately. I also went back to Sense about a week ago but came back to CM.
I have done this once before and had great success, and just did it again today and my phone is running super smooth.
1) Back up anything you care about (pics, music, docs, titanium backups, etc)
2) boot into recovery
3) FORMAT EVERYTHING.
4) Copy ROM to storage (might have to mount it)
5) Flash
I did not restore everything from TiBU, but installed most of my apps from the Play Store. I decided to install things as I needed them because I realized I don't use probably half of the apps I have backed up. I did about 20 apps from TiBU (no data).
Copy stuff back to your phone that you want to have on it...for me it was just pics and a few eBooks.
I know a factory reset and a flash would normally do the trick, but I think perhaps something got screwy when I went to the Sense ROM. Since did these steps this morning, my phone has not rebooted, crashed system ui, screen always wakes up, no proximity issues, and battery life is pretty good (stock CM kernel from Fly)
Edit: statement that proximity sensor issue did not occur has been revoked.
3)FORMAT EVERYTHING
mind to explain this step
Sent from my GT-I9100G using xda app-developers app
nainaabd said:
3)FORMAT EVERYTHING
mind to explain this step
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
I don't just wipe data and factory reset. I format the storage media and the system partition. If you have TwRP go to Wipe, advanced, check everything and wipe. Basically your phone is a clean slate.
I used to use AmonRa and I know you can do the same, but can't recall the actual steps.
Sent from my ADR6425LVW using Tapatalk 2
I've been having FC and reboot problems for almost 3 months, and I can not figure out whats going on. I thought this was going to be the solution, but I followed the steps you listed (even flashed a stock RUU and wiped again for good measure), and I'm still having problems. I have alot of problems when trying to wake the device. Any other ideas? I'm really getting sick of flashing every other day!
jcdrummr said:
I've been having FC and reboot problems for almost 3 months, and I can not figure out whats going on. I thought this was going to be the solution, but I followed the steps you listed (even flashed a stock RUU and wiped again for good measure), and I'm still having problems. I have alot of problems when trying to wake the device. Any other ideas? I'm really getting sick of flashing every other day!
Click to expand...
Click to collapse
First, backup all your files, including your SD Card.
@D8nkE posted these in the Infection thread
Boot into Amon Ra
Format data, system, cache Ext4 | Ext3 > Format all to ext3
Then Upgrade all to ext4
Hopefully this helps
gleggie said:
First, backup all your files, including your SD Card.
@D8nkE posted these in the Infection thread
Boot into Amon Ra
Format data, system, cache Ext4 | Ext3 > Format all to ext3
Then Upgrade all to ext4
Hopefully this helps
Click to expand...
Click to collapse
I had wiped everything, but changing the formatting made me nervous. I'll give it a shot today. Thanks!
jcdrummr said:
I had wiped everything, but changing the formatting made me nervous. I'll give it a shot today. Thanks!
Click to expand...
Click to collapse
I have noticed a lot depends on what you are flashing and what you are doing with it. I use FlyHalf's CM build and kept getting myself into trouble with custom kernels. I have been running incredibly stable for about a week now on stock kernel with no tweaks. I do have Autokiller Memory Optimizer installed now however. Not sure if it's helping, but it definitely is not hurting.
Sent from my ADR6425LVW using Tapatalk 2
So I've been on Infection 2.7 since Sunday. Formatted as instructed, installed very little apps, all from the play store. Didn't restore anything (including my Nova backup, which I did almost every time before this), and I kept the stock kernel (Funky 3.4) without making ANY changes to the settings.
I have noticed that it is much more stable, as I have only gotten 1 or 2 FCs since flashing...I used to get 2-3 per hour. I am still getting the "hot reboot" on manual wake though. The scenario is this: "Notification!", I press the power button, the soft keys light up but the screen stays black, a few seconds later I get the infamous spinning matrix android. To me, because it happens almost exclusively on wake, it has to be related to the kernel/governor and have something to do with it pulling out of deep sleep.
I am following the Infection, SenseXP and Funky AOSP threads, and will try each of the new ROMS/Kernel/Recovery combos this weekend and post some results as soon as I get something definitive.
As always, post if you have anything else I can try, but for anyone wondering if its worth formatting....it certainly appears to have made my phone alot more stable, so give it a shot.
I have another user that is getting very similar symptoms -sans the FC's on a different rom I dev for. Best me and him could come up with is that it is a signal issue, causing a crash at low end. Try a minimum clock @ 432mhz.
Snuzzo said:
@jcdrummr
S on or s off?
Get with me via pm. We will figure this out.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
jcdrummr said:
S-Off
HBOOT 2.27
Click to expand...
Click to collapse
Snuzzo said:
http://forum.xda-developers.com/showthread.php?t=2205469
Try that out. Are you able to get any recovery to flash at all?
@Luke1213
You tried Hiro out lately? My buddys work has been flawless as of late!!! Half tempted to ditch the current CPU table in my base and revert back to the old one.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
jcdrummr said:
I was able to flash CWM and AR fine with fastboot. Just flashed the zip, and it sits on the HTC logo, then reboots.
Should I try HIRO, with Amon Ra, or is TWRP worth the hassle?
PM Sent, in case you want to pull this off thread.
Click to expand...
Click to collapse
This may be another issue altogether.
Snuzzo said:
I have another user that is getting very similar symptoms -sans the FC's on a different rom I dev for. Best me and him could come up with is that it is a signal issue, causing a crash at low end. Try a minimum clock @ 432mhz.
Click to expand...
Click to collapse
Is there a way to prevent deep sleep? I know this would destroy battery life, but it might help determine if its related to waking from deep sleep. In the mean time, I'll bump the min to 432.
Snuzzo said:
This may be another issue altogether.
Click to expand...
Click to collapse
Yeah, I'm on RA, HIRO, and Infection 2.8.1 right now, so we'll see how it goes.
You don't want to disable deep sleep. At max you will only get 2hrs of battery also could even trigger thermal throttling. Try a sense ROM with my kernel version 3.4 and report back that's if 432 doesn't work out.
Also try switching to Br0kens vanilla aokp.
Sent from my Nexus 7 using Tapatalk HD
Snuzzo said:
You don't want to disable deep sleep. At max you will only get 2hrs of battery also could even trigger thermal throttling. Try a sense ROM with my kernel version 3.4 and report back that's if 432 doesn't work out.
Also try switching to Br0kens vanilla aokp.
Click to expand...
Click to collapse
UPDATE
Increasing to 432 did not solve the problem, but then I thought that my screen brightness app Lux may have something to do with it. After disabling the app, I didnt have a single quick reboot in 2 or 3 days. Just re-installed it this morning and rebooted on my first wake. I did not have any reboots on the stock live wallpaper or a replacement wallpaper, but I was on a non-live wallpaper when I got the reboot from the app.
If I have any more issues, I'll try the Sense or Br0ken roms and report back.
OP: Sorry for the thread jack, and thanks again for the tip to wipe. That plus what I mentioned above has given me the most stable experience I've had since March!
Things were getting wonky with more than usual reboots, no matter what rom I loaded. So I backed up pics, formatted everything in recovery (all partitions and storage, flashed (Beanstalk) and treated the phone as if it were new. No app or data restores, etc.
Phone is running super solid without any issues, not a single blip.
It's like formatting a hard drive and reinstalling the OS and rebuilding from scratch.
Sent from my ADR6425LVW using Tapatalk 4 Beta
Upgraded a couple days ago and here are the issues I'm having. Any help or suggestions appreciated by those of you who have been through this:
Battery life about half what it was on KitKat
Recharging VERY slow. MORE than twice as long as with KitKat
Pandora won't shut off when I exit car mode. Keeps coming back. Eventually it quits.
Voice in car mode is different - and like fingernails on a chalkboard!
I have done a factory reboot, which was alot harder than any other time I've done it, and that hasn't helped. Called both TMob and Samsung only to get the humma humma run around. "Replace the battery", "Do another factory reset", "Give it time to 'adjust' to the new OS". Nothing that helps much. Plus they said I could NOT re-install KitKat because of some changes made to the phone with then new update. Not sure if that ones true or not!
So for those who haven't upgraded yet - give it a bit. See what comes up in the next couple months. I sure didn't see this coming!
It is definitely more power hungry and inefficient, but not so much of the other issues you're talking about.
If I were you, I'd try to flash the stock lollipop ROM one more time, and do a factory reset right after flashing for good measure either by grabbing the stock ROM from sammobile and loading it by Odin or even flash using Samsung kies if it picks up your phone! (Sometimes Kies would give you error messages if you've loaded custom roms in the past)
Commodore 64 said:
It is definitely more power hungry and inefficient, but not so much of the other issues you're talking about.
If I were you, I'd try to flash the stock lollipop ROM one more time, and do a factory reset right after flashing for good measure either by grabbing the stock ROM from sammobile and loading it by Odin or even flash using Samsung kies if it picks up your phone! (Sometimes Kies would give you error messages if you've loaded custom roms in the past)
Click to expand...
Click to collapse
Well, I"m giving that a shot under the "It can't get worse" theory. Hopefully that's true. I'll let you know how it goes!
rogerperk said:
Well, I"m giving that a shot under the "It can't get worse" theory. Hopefully that's true. I'll let you know how it goes!
Click to expand...
Click to collapse
Well, it didn't get worse but it didn't get better either. After 6 days with Lollipop I can report a major loss of utility with the loss of battery life. I went from 15-18 hours of battery to 5-6. With that sort of battery life its not worth it. And its Samsungs fault for deploying this POS with inadequate testing.
Anyone successfully gone back to KitKat?
My contacts force close, led notifications don't work for texts or missed calls (yes it's on). Pretty disappointed too. Would like to downgrade to 4.4. Anyone dove this successfully.
Sent from my SM-G900T using XDA Free mobile app
That IS the big question!
Well. I reinstalled KitKat using Odin and it went fine. Got my battery life back and that's a big deal. Couldn't see anything with Lollipop that was worth losing that! I'll think about an upgrade when I see what they do to fix this AND how well it works but right now I need battery life.