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
Related
I am a noob & have had issues with UVJK6 charging my battery. Sometimes it does not charge when the phone shows it is charging. Can I just use CWM to flash from this to obsidian?
Thanks for any help.
rpolito73 said:
I am a noob & have had issues with UVJK6 charging my battery. Sometimes it does not charge when the phone shows it is charging. Can I just use CWM to flash from this to obsidian?
Thanks for any help.
Click to expand...
Click to collapse
im assuming you mean the JK6 modem....
you MUST use ClockworkMod Recovery to flash anything....
download the JK6 modem from the Team Whiskey website....put the zip on the root of your sd card....reboot into recovery and select install zip from sd card...
i doubt if that will fix your charging problem...
The charge problem only happens about once a day. I pull the battery for about 10 mins then its fine. I'm not sure about the kernel thing.
My phone reads Firmware version - 2.2 Baseband version T959UVJK6 Kernel version 2.6.32.9 Build number FROYO.UVJK6
Is there a place I can learn more basic information about these mean?
I really have no knowledge about kernels, basebands or builds but know enough to look on here to understand how to use CWM to flash to what I thought was the stock froyo rom.
I like it and the only prob is that it makes me nervous with the daily prob with the charge. Everything was fine until about 4 days after I flashed.
It has the lightning bolt on the battery, says charging on Battery Status Pro but it actually loses %....
I just started using Launcher Pro - could this be it?
rpolito73 said:
The charge problem only happens about once a day. I pull the battery for about 10 mins then its fine. I'm not sure about the kernel thing.
My phone reads Firmware version - 2.2 Baseband version T959UVJK6 Kernel version 2.6.32.9 Build number FROYO.UVJK6
Is there a place I can learn more basic information about these mean?
I really have no knowledge about kernels, basebands or builds but know enough to look on here to understand how to use CWM to flash to what I thought was the stock froyo rom.
I like it and the only prob is that it makes me nervous with the daily prob with the charge. Everything was fine until about 4 days after I flashed.
It has the lightning bolt on the battery, says charging on Battery Status Pro but it actually loses %....
I just started using Launcher Pro - could this be it?
Click to expand...
Click to collapse
it could not be LauncherPro....alot of things could be the cause of a battery drain....simple things like changing your wallpaper to a darker/black one can improve battery life.....reconditioning your battery can reduce battery drain....one of the main causes of battery drain is the modem...the JK6 is the battery killer in my eyes....try a battery recondition...if all else fails you could Odin back to stock and see if that solves your problem
I'm using the Aokp m6 rom but from my understan
ding, it doesn't come with a recovery? it says I have stock recovery in my recovery tools apk. I have the glitch kernel/recovery that I use on M5 but last night when I wiped my cache/dalvik cache it threw me for a bootloop and I apparently didn't have any recovery installed? I have the twrp open script recovery that I can use on the m6 rom but I like all of the extra options on the devil recovery. thanks in advance!
are you using the old official M6 with Glitch or the Devil M6? you might want to use the devil m6 build if you want devil
Well I have the Milestone 5 that is glitched and the milestone 6 that comes with the devil kernel but I'm looking for the devil kernel/recovery that's in a zip file that I can flash through cwm recovery like I have for aokp m5 which contains the glitch recovery and what not. Because when I did a factory reset on the aokp m6devild rom,i was stuck with no recovery. Or did I just do something wrong?
GarrettVW67 said:
I'm using the Aokp m6 rom but from my understan
ding, it doesn't come with a recovery? it says I have stock recovery in my recovery tools apk. I have the glitch kernel/recovery that I use on M5 but last night when I wiped my cache/dalvik cache it threw me for a bootloop and I apparently didn't have any recovery installed? I have the twrp open script recovery that I can use on the m6 rom but I like all of the extra options on the devil recovery. thanks in advance!
Click to expand...
Click to collapse
Best of my recollection, that version came with the cwm recovery but the devil kernel build inside.
are you talking about this tool? http://forum.xda-developers.com/showthread.php?t=2334554
as far as I know, most of those type will not work for the fascinate,,, but I have not looked at that one,,,
our recovery is also packaged with the boot partition and cannot be flashed/installed separately, which is how most of these tools work.
going off my menory this should be what you want...
Devil3_1.6.1
.zip for install thru current recovery
Devil3_1.6.1_zip_fas_CFS_BLN_CMC_20120930.zip
http://www.androidfilehost.com/?fid=23043426517778454
.tar for install by ODIN
Devil3_1.6.1_tar_fas_CFS_BLN_CMC_20120930.tar
http://www.androidfilehost.com/?fid=23043426517778453
.
thanks hhp, that's what I was looking for. Actually it was a collection of old roms you uploaded that I've been getting everything from. Am I crazy for wanting to use ICS? I read reports of people loving their jb roms on their fassy and claiming 2days without charging but I literally have to walk arounaround with my charger on every jb rom I've tried. Do you have any suggestions on whether I should use gb or ics for the most battery life? I don't care so much about tweaks anymore, I just want my phone to not die on me everywhere I go. And is glitch or devil better for battery life?
GarrettVW67 said:
thanks hhp, that's what I was looking for. Actually it was a collection of old roms you uploaded that I've been getting everything from. Am I crazy for wanting to use ICS? I read reports of people loving their jb roms on their fassy and claiming 2days without charging but I literally have to walk arounaround with my charger on every jb rom I've tried. Do you have any suggestions on whether I should use gb or ics for the most battery life? I don't care so much about tweaks anymore, I just want my phone to not die on me everywhere I go. And is glitch or devil better for battery life?
Click to expand...
Click to collapse
yay i'm not alone. been using ICS for a while now and I myself have been trying different things for.. gee some time. right now i'm running the official milestone 6 (glitch, devil doesn't like my phone) and i've been trying to get decent battery life for a while.. trying calibration crap even though that's been confirmed a myth, wiped battery stats too many times to count, ugh... i did get 2 days of moderate usage at one point with AOKP.
but yeah as i said devil doesn't like my phone so i'm stuck (even though glitch is amazing). i'm not too much of an overclocker and i haven't even changed governors and i get 2 days of light usage usually.
how much battery do you get? apparently you use gummy.. i've never been a big gummy person. just my 2 cents
@GarrettVW67 I really got nothing for you on that one. I get 4-6 hours of heavy usage. And I'm 98% time beside a power outlet and usually less than 2 hours without charging access.
And I like having compatibility with all the current apps
hhp_211 said:
@GarrettVW67 I really got nothing for you on that one. I get 4-6 hours of heavy usage. And I'm 98% time beside a power outlet and usually less than 2 hours without charging access.
And I like having compatibility with all the current apps
Click to expand...
Click to collapse
ics is compatible with all the current apps. hell, gingerbread is still compatible with most things these days.
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 guys,
A couple days ago I installed CM10 with the installer and then CM11 over the air. However I have some problems with the ROM apart from the battery drain and heat, my phone sometimes just randomly freezes, turns itself off and when I turn it back on, the battery dropped at least 20%. My very first question would be, if anyone has a fix for this? I already tried wiping system cache, but it did not fix the issue.
I googled around to find some solution, and it seems that CM 10 is more stable and there are fewer issues with it. I would like to go back to this version, however I'm not entirely sure what should I do. My first step would be wiping everything and factory resetting the phone, as there might be stuff left from the previous ROMs on the phone. I reckon I have two options from this point:
1. Running the CM installer again and have it install CM 10. Is this even possible? Or the installer won't even start given that I have a fresher version of CM?
2. Downloading the latest official ROM from sammobile, flashing that with ODIN and then running the CM installer. If I have to do this method, is there anything that I should extremely be cautious about? Also, I bought the phone in Hungary, but now I'm in England, and I installed CM here. I reckon I'll have to download the Hungarian ROM from sammobile for my phone, could someone please confirm this? The phone is not locked to a carrier anymore (they removed it), can I just flash the general (XEH) Hungarian ROM?
Thank you very much for the help in advance, and sorry for the noob questions!
gravisone said:
Hi guys,
A couple days ago I installed CM10 with the installer and then CM11 over the air. However I have some problems with the ROM apart from the battery drain and heat, my phone sometimes just randomly freezes, turns itself off and when I turn it back on, the battery dropped at least 20%. My very first question would be, if anyone has a fix for this? I already tried wiping system cache, but it did not fix the issue.
I googled around to find some solution, and it seems that CM 10 is more stable and there are fewer issues with it. I would like to go back to this version, however I'm not entirely sure what should I do. My first step would be wiping everything and factory resetting the phone, as there might be stuff left from the previous ROMs on the phone. I reckon I have two options from this point:
1. Running the CM installer again and have it install CM 10. Is this even possible? Or the installer won't even start given that I have a fresher version of CM?
2. Downloading the latest official ROM from sammobile, flashing that with ODIN and then running the CM installer. If I have to do this method, is there anything that I should extremely be cautious about? Also, I bought the phone in Hungary, but now I'm in England, and I installed CM here. I reckon I'll have to download the Hungarian ROM from sammobile for my phone, could someone please confirm this? The phone is not locked to a carrier anymore (they removed it), can I just flash the general (XEH) Hungarian ROM?
Thank you very much for the help in advance, and sorry for the noob questions!
Click to expand...
Click to collapse
If you want to downgrade to CM10, just download the cm10.zip and flash it on recovery (remember to wipe /system and all user data first).
If you want the stock rom you can flash a stock rom from any country, althrough it's recommended to flash the rom for the country you are in now.
Also, the battery bug is a device specific bug and cannot be fixed, maybe wiping the battery stats can help.
Thank you! Do you have a Galaxy SII? If yes, do you think that it's worth going back to 10.2 or should I just stick with 11, regardless of the bug?
gravisone said:
Thank you! Do you have a Galaxy SII? If yes, do you think that it's worth going back to 10.2 or should I just stick with 11, regardless of the bug?
Click to expand...
Click to collapse
I'm using cm11 m12 snapshot latest over i9100 .. I dont find any battery bugs as you've explained above !! Battery life is pretty good actually gives me life of around 5-7 hours with wifi on always !! Try this
I'm on a rather older rom: http://forum.xda-developers.com/showthread.php?t=2544790 Omnirom 4.4.4 with TWRP
I have been having issues with the phone Endlessly rebooting while charging and this causes it to drain the battery instead of charging it (Started happening a few months ago). Now even with different batteries they get nuked from this same reboot while charging process. The phone would work as long as I didn't fully drain a battery, but once I did I couldn't get power back in them because of this rebooting/charge issue.
I bought an external battery charger today (I have three batteries already) so hopefully the phone will boot on a fully charged battery. I'm using the OEM Samsung wall charger and Samsung USB cable that came with the phone.
I would like to upgrade my rom but I know there was an issue with extending the internal partition and my chip being "possible to brick" when extending the partition.
My phone doesn't have the stagefright bug fixed so that was another reason I wanted to upgrade. Anyone who's had my phone and upgraded from kitkat to the newer rom's I'd appreciate some advice. I've been through many rom's before but the last couple (upgrading from cwm to twrp and now needing to extend the partition to actually be able to use it) are more advanced than what I've done so far.
Sorry for my vague post, it's been a long night/morning and I'd appreciate any guidance.
Lastly, I forgot to add- Over all these years of switching rom's and upgrading I have dozens of folders, paths and directories and God knows what that I'm fairly certain are redundant and taking up space, any way to clean that out (without bricking my phone- no I won't randomly delete stuff) safely when moving to a more recent rom?
Dang, no updates? I know it's holiday's and all. I just don't wanna brick my phone trying to upgrade from kitkat because of the emmc brick bug. Ebay said my external battery charger should arrive between today (Jan 5th, and January 25th) ... So I have some time lol. Been without a phone for two months.
Update, got the external charger, it worked and the battery is charged. Phone's power button still not working, looking for an assist to wipe and upgrade to newest rom >.>
Edgarhighman said:
Update, got the external charger, it worked and the battery is charged. Phone's power button still not working, looking for an assist to wipe and upgrade to newest rom >.>
Click to expand...
Click to collapse
The latest stock ROM for the i777 is jelly bean 4.1.2 and the latest unofficial ROM is CM 13 I think. I suggest using cook's rom wipe files (just search the galaxy s2 section here for them) and jeeboo kernel to boot wiz cat ROM which is kit kat based. It's a stock based ROM. Or just ODIN the jelly bean stock ROM and start from scratch to boot whatever ROM you want.