I've got an i727R
It was rooted with TWRP and CyanogenMod 10.1.3 and it was fine.
This afternoon I noticed the battery dropping,rapidly. then it went off and could come back on.
I can't boot it with or without the battery, with or without the usb in (I suspect the battery is totally flat).
Prior to going crazy I:
- enabled encryption a couple of days ago
- noticed intagram had consumed 35% battery (i subsequently uninstalled instagram to try and stop the drain
When I plug the usb in it buzzes about once every two seconds
help
Wrong forum, belongs here. I've asked mods to move your thread, sit tight until they do.
MistahBungle said:
Wrong forum, belongs here. I've asked mods to move your thread, sit tight until they do.
Click to expand...
Click to collapse
Thanks. I noticed after I posted but couldn't delete (or find?) my post.
Good news, I was able to get it into download mode eventually. Once I was there I was good.
I re-flashed to stock with Odin; reformatted with default recovery to strip encryption; Odin'd it again; installed TWRP; finally CM 10.2.
It still seems to be having battery-drain issues, which I am investigating.
the_darkwing_duck said:
Thanks. I noticed after I posted but couldn't delete (or find?) my post.
Good news, I was able to get it into download mode eventually. Once I was there I was good.
I re-flashed to stock with Odin; reformatted with default recovery to strip encryption; Odin'd it again; installed TWRP; finally CM 10.2.
It still seems to be having battery-drain issues, which I am investigating.
Click to expand...
Click to collapse
Try a new or battery that has worked fine for you. also, clean flash your phone on a stock ROM and don't install any apps for a hour or so. See if the drain still exist. Best way to test it out!
Hit thanks if that helped!
Related
Hello,
I'm truly hoping someone can help me. I spent all night installing new roms on my phone. Ok let me back up. This is bout the tenth phone I've rooted. I rooted my blaze about 2 months ago using a one step(I think can't remember.) I never really installed a custom Rom until last night. The first Rom I installed was cm10, which I liked. Only problem was I couldn't mount my sd card because I am no where near a computer. So I decided to install the baked Rom. I was ecstatic to find that everything worked. However, the cm10 Rom seemed to be running at the same time. I found that very weird. So I tried to figure out a way to get the cm10 off my phone. For hours I tried wiping and reformatting different things from recovery. My problem is the last time I rebooted my blaze out wouldn't go past the Samsung screen. I've tried all combos of the volume up down and power key and it never goes past Samsung. I'm assuming I've bricked my. It will show the battery charging screen. 1st it'll show the stock screen then the baked screen for charging. Please help me. I've searched xda for help and can't find anything to help.
Ps. I'm not at a computer now but please list help for when I'm able to get to one. And yes I've only gotten about 3hrs of sleep in the last 20hrs from messing with my phone.
Assuming you'll be at a computer soon. You need to Odin back to stock blaze firmware. Using the blaze uvlh5.(I think that's it.) From samfirmware.com
Sent from my SGH-T769 using xda app-developers app
Thanks I will try
Moved...due to not a Development Thread. Please hit the report button next time, Thank You.
Hello, I was reflashing a ROM (Sultan's CM10.2 w/ PMEM) but it seems to be stuck on Installing update...
It's been going for about 30 minutes now, much longer than the other times I've flashed it.
My question is, since it clearly isn't going anywhere, is it safe to remove the battery to start over again? I don't want to brick it.
(Not sure what went wrong, I think my SD card's going bad. I've flashed a few roms before successfully including this one, and I'm S-OFF'd and rooted already)
GoodOlTarvis said:
Hello, I was reflashing a ROM (Sultan's CM10.2 w/ PMEM) but it seems to be stuck on Installing update...
It's been going for about 30 minutes now, much longer than the other times I've flashed it.
My question is, since it clearly isn't going anywhere, is it safe to remove the battery to start over again? I don't want to brick it.
(Not sure what went wrong, I think my SD card's going bad. I've flashed a few roms before successfully including this one, and I'm S-OFF'd and rooted already)
Click to expand...
Click to collapse
HI
Greetings
i assume you have made a nandroid backup as if somthing goes wrong thats the thing which will help you
secondly you can try again just remove the battery and try againg
do a clean installation
Alright then. I took out the battery and reflashed it and nothing bad happened.
Thanks.
Since I cannot yet post in the development section, I'll hope to have some response here. Upon installing the unofficial CM11 mod in combination with pink kernel, I came across a stubborn bug: the battery indicator is invariably stuck at 1%.
A clean reflash (even /system format) did not help. I flashed back the stock ROM, wiped everything and reflashed the CM11 with no difference so far.
Has anybody got an explanation/bug fix? Thanks in advance..
parabol4 said:
Since I cannot yet post in the development section, I'll hope to have some response here. Upon installing the unofficial CM11 mod in combination with pink kernel, I came across a stubborn bug: the battery indicator is invariably stuck at 1%.
A clean reflash (even /system format) did not help. I flashed back the stock ROM, wiped everything and reflashed the CM11 with no difference so far.
Has anybody got an explanation/bug fix? Thanks in advance..
Click to expand...
Click to collapse
i have this problem as well battery indicator stuck at 1percent.
parabol4 said:
Since I cannot yet post in the development section, I'll hope to have some response here. Upon installing the unofficial CM11 mod in combination with pink kernel, I came across a stubborn bug: the battery indicator is invariably stuck at 1%.
A clean reflash (even /system format) did not help. I flashed back the stock ROM, wiped everything and reflashed the CM11 with no difference so far.
Has anybody got an explanation/bug fix? Thanks in advance..
Click to expand...
Click to collapse
I had this same issue even in stock ROM... just let the battery drain completely til the phone switches off and then charge the phone and boot... it worked for me... :fingers-crossed:
I had this happen to me on stock as well the first day I owned the phone. Left it on the charger all night and on less than ten minutes of use the battery showed 1%. Charged back to full and haven't seen it again. I think server people have experienced this bug.
Sent from my XT1034 using XDA Premium 4 mobile app
find the battery apps in apps setting then try clear the cache. once happen to my old s2's cm11.
From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly
talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.
When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita
Recovery: Custom TWRP 2.6.3.0 w/selinux support
And what errors did it give you when trying to install Gummy?
Sent from my Evita
The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.
timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.