Hi guys, long story here, but i will make it as short as i can.
I m using an international version galaxy s3, gt-i9300, was running under leak version 4.1.1.
The phone encounter a boot loop no matter which root method i used, CF-Root-SGS-v6.4.tar nor CF-Auto-Root
No matter i clean davuk, set it to factory setting under recovery, the phone just wont start.
Anything on the internet showing how to unbrick the phone didn't work, the only option to make it working is to re flash 4.1.1
Upon my last flash, which is about the 5th time I flashed, I notice battery drain WAY much faster than usual, drops 50% in 8 hours of standby (while i was sleeping)
All the apps were closed.
Then I flashed my phone with 4.1.2 pre rooted, http://forum.xda-developers.com/showthread.php?t=1835931
It is functioning properly, however unusual battery draining persist, drop from 95% to 50% in 8 hours.
Did I break my phone/battery or is there anything I can do to improve its efficiency??
Thanks a lot!!!
NO there are like 20 threads on battery issues already.. Check in those threads instead of a new post. Good luck
So I had this SGP321 for over a year now.Bought it brand new from this guy on the internet for a suspicious low price.Not a real shop or anything so no waranty. It worked very well for a few months then I noticed it started rebooting every now and then.After a OS update that was rolling out at that time (can't remember the version) the reboots were more often.After the KitKat update arrived and I downloaded it,after the process was over and the phone had to reboot,it entered a reboot loop that could not be stoppped (apart from forced shut down,but with same thing when trying to turn back on). I repaired the OS with the PC tool,no changes.I flashed older versions of stock OS with flashtool,reboots every couple of minutes. Then I installed Cyanogenmod 11.That worked very well,no reboots,but had many bugs and battery draining fast in stand by (about 1% per hour no matter what I deactivated,or with various apps to induce deep sleep). The new CM12.1 does not work,keeps rebooting.
Now,yesterday I tried again and again to get the tablet to work with a stock ROM. I only intend to use it for reading comic books,so all I want is a stable ROM with good battery life.So I would like to have a stock one. But why does a custom one run fine on it and a stock one keeps rebooting? I tried Sony forum but they were at a complete loss and sent me here for help.Any ideas?
rammstein_08 said:
So I had this SGP321 for over a year now.Bought it brand new from this guy on the internet for a suspicious low price.Not a real shop or anything so no waranty. It worked very well for a few months then I noticed it started rebooting every now and then.After a OS update that was rolling out at that time (can't remember the version) the reboots were more often.After the KitKat update arrived and I downloaded it,after the process was over and the phone had to reboot,it entered a reboot loop that could not be stoppped (apart from forced shut down,but with same thing when trying to turn back on). I repaired the OS with the PC tool,no changes.I flashed older versions of stock OS with flashtool,reboots every couple of minutes. Then I installed Cyanogenmod 11.That worked very well,no reboots,but had many bugs and battery draining fast in stand by (about 1% per hour no matter what I deactivated,or with various apps to induce deep sleep). The new CM12.1 does not work,keeps rebooting.
Now,yesterday I tried again and again to get the tablet to work with a stock ROM. I only intend to use it for reading comic books,so all I want is a stable ROM with good battery life.So I would like to have a stock one. But why does a custom one run fine on it and a stock one keeps rebooting? I tried Sony forum but they were at a complete loss and sent me here for help.Any ideas?
Click to expand...
Click to collapse
Seems that it has hardware problem like corrupting internal Flash memory or smth else, that is very difficult or imposible to fix by reflashing.
Hello,
As we know Marshmallow update arrived , I had no problem recieving MM update to my E2353. i updated the phone using sony companion and it updated normal, nothing occured , i didn't made any mistakes..nothing.
So after update it turned off and boot up like normally it do,
First boot up took long time , like 20-30 mins and phone heated for some extent.
I did normal stuff such as connecting wifi etc, after that i restarted and it took around 20-40 mins to turn on again...
after turning on battery life is very poor..also every sensor of the phone are not working, no auto rotation, nothing.. now every time i turn it on it take 20-40 mins, battery is awful, it feel like its dieing after the MM update
couldnt find anyone with this problem with official update at all.
NOTE : i did rooted this an year ago without any problems and unrooted it after doing so without any problems.
i recieved MM original update.
current build no - 26.3.A.0.131
i've reinstalled (resetted) using sony update service which redownload the MM . it had no effect
Thank u very much !
Try flashing the marshmallow rom from XperiaFirm, it's a pretty easy process, look it up on google
DarkerJava said:
Try flashing the marshmallow rom from XperiaFirm, it's a pretty easy process, look it up on google
Click to expand...
Click to collapse
Did that, it's still the same... boot up takes long ass time still :/
factory reset
and if not working, try to shut down your phone for a minute and power on again
Hey everyone. redoing my thread now that we have tried alot of solutions, hopefully someone has a vague idea of what we can do to my phone lol.
So then, my phone (redmi note 3 snapdragon) refuses to go into deep sleep no matter what combination I've tried.
Tried Combos
1. RR+ radon and agni
2. Miui 8 stable and dev preview (7.1.5 and 8.1.1.0)+ stock, radon, and neon kernel (flashing using miflash with unlocked bootloader official)
3. Cm13 latest nightly+ radon, stock, and agni
4. Nitrogen os+ nagato kernel (current rom)
All combinations we're tried with clean installs (factory data, system,cache and internal storage)
Hardware methods tried
1. Physically disconnecting fingerprint sensor (goodix)
now then, with wakelock detector, we can see im troubled with a 99% awake time, along with 100,00's of event wakelocks over 6hours, now event wakelocks deal with the actual hardware of the phone from what i've seen, which makes little sense to me because the screenshot i am attaching was just over an entire night of not touching the phone. so why it has any activity is bizarre to me. so heres what we have tried so far on my previous thread.
Tried methods of fixing event wakelocks
1. Greenify, force doze, wakelock blocker and blocking everything in frustration. deep sleep battery saver.
2. physically deleting events one by one (going into dev/input/eventx (x being wakelocks 1-10) after deleting some my display eventually stopped working, most likely because i just deleted the event that controls the lcd i assume. rebooting fixed the problem and remade the events in their directory so no harm done.
3. removing zram usage figuring it was a thrashing problem (saw a thread in the hd desire of the same issue. didnt help sadly.
4. flashing modem in radon thread, ended up making my phones earpiece not work for calls and still had the wakelocks.
5. disabling gps, along with auto brightness and auto rotate
so then if anyone needs any other information just let me know, currently using an iPhone for the time being so im desperate lol. but still id rather fix and find the problem then go for returning the phone. better to solve a problem for future people in my shoes then just thrust it away is how i see it. also someone bug the strix and darkstrix about this maybe they know the solution. anyway thanks for reading and i hope we can fix my phone soon
^Update^ now using epic rom 7.1.12 from the xda thread, still got wakelocks on stock without any other apps.
I have same problem in all versions of stock MIUI Rom. I too tried all sorts of combination but the problem remains. Finally I'm using RR Rom 5.7.4 (20161113 build) + radon Kernel. My deep sleep problem have been solved (though not 100%). Now my phone looses very little battery in standby time like 1-2% over a night. Before RR Rom I tried many custom Rom but had same problem. If you have not tried the ROM (RR Remix 20161113) I've mentioned above give it a try. Best Of Luck.
Thanks rj I'll install and post logs after work. Fingers crossed that it fixes my problem.
use the rom android 6.0.1 with module powernap , u can fix it !!
http://repo.xposed.info/module/net.jzhang.powernap
Small update: testing stamina mod currently with xposed. ressurection remix will be next only because xposed seemed a bit easier lol
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Then once try nexus rom i am getting good battery life in this rom too.
rjrulz007 said:
Then once try nexus rom i am getting good battery life in this rom too.
Click to expand...
Click to collapse
surer rj which one?
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
That happens to me when background data enabled . when i disable backround data through data usage settings , the battery backup gets better, but sure my social apps wont sync.
It seems the wakelock come from android system itself , go check logcat and you will get messages like "ANDR_PERF_RESOURCES FAILED TO APPLY PERFORMANCE" , the likes of "decided to move IRQ from cpu0 to cpu1" , and the likes of "FPC listener : waiting..." , thats all that i notice and thats happening every single milisecond on every MM roms i have tried so far....
Well when i used miui 7 LL global didnt get that much messages on logcat , but its LL ...
I guess the problem is related to source code , i dont know .
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
D4xel said:
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
Click to expand...
Click to collapse
yes sir still nothing
rohit4kk said:
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
Click to expand...
Click to collapse
hey dont worry man you'll be the first when we find an answer lol
Zaccary said:
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Click to expand...
Click to collapse
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
deltatux said:
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
Click to expand...
Click to collapse
thanks for the tip but we are running on airplane mode only at this point just to make sure we don't have more things to worry about battery drain. i appreciate the information though ^_^
Mine kenzo, tried all miui version, always the same.
sbor-si said:
Mine kenzo, tried all miui version, always the same.
Click to expand...
Click to collapse
I'm not alone!!!
Hey hopefully we find an answer buddy
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
sbor-si said:
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
Click to expand...
Click to collapse
i believe last time i tried 7.3.2.0 it gave me constant reboots and lagged quite a bit. but i also heard it was the best for battery so i can try flashing through miflash again after work. im also going to be trying this rom here https://forum.xda-developers.com/re...nzo-lldlm18-1-3m866beta-real-factory-t3375250. since it uses edl mode instead of fastboot so hey maybe that will knock something lose?
Well, right now I'm trying to get it working - without luck. I can flash 7.3.2. with miflash via edl without troubles, phone started normaly, all seems good, until "No service" for gsm signal. Bad luck. I think that modem version from that old flash is not compatible with hardware.
But it looks so good - Android takes 20% and Android system 6%...
So, since the past few days my i9300 keeps randomly rebooting. At first it was not that much of an issue but today it started to go into a boot loop.
Sometimes it finishes booting but before I can go into the settings to factory reset it, it crashes.
I also tried to get into TWRP but as soon as the logo shows up, it crashes.
I can't even use the download mode because, guess what happens: it crashes.
I really don't know what to do right now. I still have a spare motherboard but I'm not able to access it for another week. It would be a shame to throw away a perfectly fine motherboard if it is just a software thing.
Currently it is running the last version of SlimKAT that was released, I don't know which version of TWRP it is running, but I updated it just a few weeks ago. It is not using the original battery fom Samsung but one from Anker which should be fine.
If anyone needs more or specific information, I'm more than happy to provide it.
Hi,
just want to ask, you're stuck in bootloop at the "samsung" Logo or where?
Because I am having bootloops, too since 2 days. Phone kept restarting one or 2 times since last 3 days and when i got home on 1. november i put my phone to the charger and got back 20min later and saw it was rebooting.
Mine is stuck in optimizing apps or if i wait long time then it is at starting android: starting apps and i see when the color temperature of the phone changes (i think of the light sensor) it gets stuck and reboots.
just for docu (even if its not the same problem):
i have a 2nd spare s3 for testing here and to test ag. hardware issue i made a twrp backup and both are dying. after facory reset and installing apps i recognized that it is dying at the installation of telegram app and after that its going to the same bootloop on both phones. i checked telegram and seems to fit in, they updated their app at 1. november. and date code of last changes before the bootloop: telegram was modified. so for my problem it seems to be caused by telegram.
I am using bliss rom 6.1 (Andoid 6 Marshmallow, CM13 based) at i9300
sorry for maybe not beeing a help. I now found out that it happens to other app installations, too. so seems to be a problem deeper in android/interfering with this specific rom - maybe its play store . So far since it happens on 2 identical s3 with this rom I will have to change the rom now. :crying: (was stable >1year)
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Niggyminator said:
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Click to expand...
Click to collapse
good luck!
But if you'r stuck at the samsung logo, sounds even worse than mine. if your having a new board could at least be an option to check if its really not a hardware issue (you mentioned that its getting again unstable after some time)
for my problem I managed to backup most things out of the nandroid image and moved to ressurection remix with android nougat. the new rom is running fast and so far without any problem - hope it stays like that .