Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Same problem on same phone
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
I was using a CM10.1 nightly build for my i9505 and attempted to install the AVAST Anti-Theft feature using the root install method. On the first attempt at installation there was a free-space error, in which the amount of free space shown in the /system partition had overflowed and showed negative free space. To work around that error I filled up my /system partition until there was only 100mb free and then the install worked. All went well until I did a reboot; the phone hung at the i9505 screen.
I tried rebooting the phone and removing the battery for a short while, but nothing worked - the phone still hung at the i9505 screen. However, all other functions worked, so I just reflashed CM10.1 after wiping /cache, /data (but not /data/media), /system, and the Dalvik-cache (though that is in /cache AFAIK so pretty redundant). All was fine after that reflash, other than the annoyance of having to set everything up again (didn't make a backup recently).
Obviously the Anti-Theft wasn't very secure if it could be removed by a simple reflash. But to be fair, I highly doubt any software can protect itself from a format!
Anyway, just letting people know that I can confirm this this problem exists, and how I fixed it on my phone.
ingvarr_zaag said:
Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock firmware using odin
Go to stock recovery there factory reset and wipe
Reboot
Note all data will be lost take backup b4
.
sheomualjy said:
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
Click to expand...
Click to collapse
I had Clockwork Recovery installed but I couldn't use it, because after reboot the screen was black. I managed to get to android recovery and flashed stock Samsung ROM by Odin. It didn't help.
After 2 weeks in service it's possible that today I get my phone back. Finally, because two weeks with Samsung Galaxy Advance were miserable.
Actual status on service's page says, that they replaced main board in my phone.
BTW: no Avast Anti Theft ever again.
Hi,
I have a SMN910F rooted on stock kitkat downloaded from sammobiles, also having TWRP and a few xposed modules. A couple of weeks back after my phone's battery died, I couldn't get it past the samsung logo when trying to reboot after connecting the charger. I suspected a s/w malfunctioning and performed a clean flash, rooted again and installed TWRP. It has been working fine since then until the battery ran empty again this morning. The same problem seems to occur again now. On a normal reboot it works just fine.
I have tried removing sd card and trying, restarting through TWRP and connecting to PC for the restart and none of these helped. I bought the phone from UK and have now moved to India so am not sure if I can claim warranty even if I managed to reset the Knox counter to 0.
I came across a similar thread for i9300 where the asker says he had an empty /efs folder. Is that likely to cause this problem and how can I check the /efs on my system now without factory reset. I'm having to reconfigure the phone with every factory reset and is tiresome. Also if /efs was the problem should the clean flash last time not have fixed it?
Thanks in advance,
Vish
Vishwa308 said:
Hi,
I have a SMN910F rooted on stock kitkat downloaded from sammobiles, also having TWRP and a few xposed modules. A couple of weeks back after my phone's battery died, I couldn't get it past the samsung logo when trying to reboot after connecting the charger. I suspected a s/w malfunctioning and performed a clean flash, rooted again and installed TWRP. It has been working fine since then until the battery ran empty again this morning. The same problem seems to occur again now. On a normal reboot it works just fine.
I have tried removing sd card and trying, restarting through TWRP and connecting to PC for the restart and none of these helped. I bought the phone from UK and have now moved to India so am not sure if I can claim warranty even if I managed to reset the Knox counter to 0.
I came across a similar thread for i9300 where the asker says he had an empty /efs folder. Is that likely to cause this problem and how can I check the /efs on my system now without factory reset. I'm having to reconfigure the phone with every factory reset and is tiresome. Also if /efs was the problem should the clean flash last time not have fixed it?
Thanks in advance,
Vish
Click to expand...
Click to collapse
Go to download mode by pressing and holding volume down+home+power, then try flashing the stock firmware again, or if you want boot to recovery first and wipe cache and dalvik and try to boot it again, if not go back to step 1, cheers:fingers-crossed:
Thanks for your reply. I have done it and it's now back to working condition.
But worried that this is continuing to happen every time my battery drains out.:silly:
Vishwa308 said:
Thanks for your reply. I have done it and it's now back to working condition.
But worried that this is continuing to happen every time my battery drains out.:silly:
Click to expand...
Click to collapse
Good to hear mate, you should try calibrating your battery also, use your phone until it reaches 15%, then charge it to 100%, reboot into recovery wipe caches, boot it again, and let it on the charger 20-30 min after its fully charge, and repeat step 1, keep doing this as much as you can, your battery will calibrate and it will improve in longevity, cheers:fingers-crossed::highfive:
Thanks mate. Will do that!!
Sent from my SM-N910F using XDA Free mobile app
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Sounds to me like there''s something physically wrong with the phone, probably the battery. Time for a new one anyway. Lithium batteries degrade with use. After ~500 charge cycles it'll have lost upwards of 20% of its original capacity and might show other signs of wearing out like inconsistent voltages. After 2 years of use, you'll be well beyond 500 cycles. A new battery off eBay is pretty cheap, and some sellers include the needed tools.Go to ifixit.com for a tear-down guide. A hair drier can help soften up the adhesive. The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
And FYI, the whole "optimizing app" thing is the OS rebuilding the cache. When you flash your GAPPs package or a zipped Titanium backup it has to build the cache for the new apps. Same as when you do the "wipe Dalvik and cache" part of standard flashing procedure to avoid conflicts. In order for apps to load quickly, Android stores a lot of the necessary data in cache, so when you clear it or have new apps, it has to rebuild the cache. On Lollipop this takes a loooooooong time because of the way ART works.
Planterz said:
The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
Click to expand...
Click to collapse
How can i be completely sure that it's the battery which needs to be replaced? The battery shows charge. When i plug in and boot up it shows enough battery power left.
Currently, without external power it does not go past the google screen on boot. When i plug in power while device is off, the battery meter shows just a little depletion from full charge. When turned on, battery level is 82 %
After all , all this hardware mess up can be the consequence of a bad cm flash ?
the whole "optimizing app" thing is the OS rebuilding the cache.
Click to expand...
Click to collapse
I know this. Earlier it was happening on each boot. Now it seemed to be stopped.
By any chance did you have your phone charging while flashing and booting up your ROM?
ChainFires Son said:
By any chance did you have your phone charging while flashing and booting up your ROM?
Click to expand...
Click to collapse
May be? But not the the first time
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Click to expand...
Click to collapse
Exactly same problem is started with my Nexus 4 ... I really wonder, what is causing this. Meanwhile, have it sorted for you ? is that hardware (Battery) issue?
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself...
Click to expand...
Click to collapse
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
shazR00t said:
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
Click to expand...
Click to collapse
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
I also got the same problem. I thought this is battery problem, so I replaced the battery but problem still there. I thought this is problem of lollipop, never installed CM or anything. It is always running stock android. After that I even downgrade to Kitkat stock version still it is not working. One more thing I noticed is If I don't unlock the device than it will be powered on, but as soon as I unlock it and if it is not plugged in to charger it will be switched off. Any suggestion what should I do?
I have the same thing for several month now.
Always thought it is the dying battery.
theminikiller said:
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
Click to expand...
Click to collapse
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
shazR00t said:
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
Click to expand...
Click to collapse
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
theminikiller said:
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
Click to expand...
Click to collapse
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the image files. If you did that then u don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 20:42 ---------- Previous post was at 20:41 ----------
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the images. If you did that then I don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
I m too facing the similar issues. Phone is getting turned off suddenly when not charging, on charging it is working fine. i have done factory reset and also done factory image reset to 5.1.0. i m still facing the same issues. I don't think so it is related to battery. if anyone have the solution then please let me know.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Try the very basic flash technique by double clicking the flash-all.bat. It's not the same as flashing the imgs one by one.
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
gautam.is.sharma said:
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
Click to expand...
Click to collapse
Ok so Battery was the problem!! Got it changed, phone working fine now. Thanx all!
Ok guys i confirm that this is a battery issue. I took it to the service center and the guy temporarily replaced battery to show me issue solved... But... there i saw another issue due to which i did not buy the battery. I saw half the touchscreen not working (including the navigation buttons ). The guy at the center told its a h/w issue and i would have to spend 7K on it so i left my phone dead for now. The Question is ... can this be a s/w issue.. or result of bad flash which can solve on reflashing ??
same problem with my nexus ,but one thing i noticed that the phone does not power off while in recovery...Any idea??
I updated OTA my Note 4 n910f to the latest built. It was something about Samsung Cloud. Since then i haven't been able to use my phone for even a minute. It keeps rebooting every 1 minute. When plugged in it reboots but for like every 3 minutes. And it doesn't charge, my battery was 66% when i plugged it on AC, and it keeps going down like 64% plugged it. I don't know if any of you had this issue before or are having now but i cant use my phone for 2 days now. I tried to clear cache data via recovery, also wiped storage, factory reset, wiped everything but no luck. Where is my problem, is my battery dead or software issue. I didn't have this before the last update. Help !
ArnisHoti said:
I updated OTA my Note 4 n910f to the latest built. It was something about Samsung Cloud. Since then i haven't been able to use my phone for even a minute. It keeps rebooting every 1 minute. When plugged in it reboots but for like every 3 minutes. And it doesn't charge, my battery was 66% when i plugged it on AC, and it keeps going down like 64% plugged it. I don't know if any of you had this issue before or are having now but i cant use my phone for 2 days now. I tried to clear cache data via recovery, also wiped storage, factory reset, wiped everything but no luck. Where is my problem, is my battery dead or software issue. I didn't have this before the last update. Help !
Click to expand...
Click to collapse
Flash stock firmware via odin and do a factory reset after flashing firmware.hopefully it should fix the problem. Go to (www.sammobiles.com/firmwares) choose your model number and download latest firmware.
Already did that, no luck. !
ArnisHoti said:
Already did that, no luck. !
Click to expand...
Click to collapse
Try flashing lollipop .
If the problem still persists after lollipop, then go to a service centre .
If they repair it ,well-n-good but if they don't then try rooting your device and then change the kernel.
Sent from my SM-N910G
So.. 2 weeks ago. I locked my bootloader with stock rom. Miui 11.0.9.0 Android 9 Indian version. Everything went well. Miui 11.0.1.0 update was not showing in updater so I manually updated from updater. Everything went well again. I played pubg and used normally. 3 days later. I put my mom's oppo Neo 7 sd card in my lavendar. I tried copying files from internal storage to sd card but it showed some kind of error. I erased memory card from storage. But it won't get erased. Tried formatting from pc. It said couldn't format.
I removed the sd card becouse i thought there's virus in it.
Then my lavendar started rebooting when I open any app or get a call. I performed factory reset. Still the same problem. I wiped data from mi recovery. Still same. It rebooted when I open an app. I unlocked bootloader and flashed superior os. Still same problem. I locked the bootloader again. Still same...
Finally I took it to authorised service center. They checked and flashed stock rom via mi flash tool becouse why not‽ Still the problem persists. Today a guy from telegram group told me to check opening the app while phone is charging. I tried and it didn't reboot. He said the battery is damaged. I called service center technican and told him the scenario but he said the battery is totally fine. You have to replace the motherboard.
Can anyone help me fix this problem please. Thank you and sorry for so long explanation but it was necessary.
PS: I used to flash a different rom every 4-5 days. Once I flashed 3 different roms within an hour.
Video for reference
https://t.me/AEXUNOFICIALlavender/22152
https://t.me/AEXUNOFICIALlavender/22153
Rifaldi34 said:
Yeah its 100 percent the battery, the battery got broken and cant provide power to the phone while opening some heavy apps, thus the phone reboots
Click to expand...
Click to collapse
Amulya sir and Martin sir suspected that emmc was broken so I was worried. But changed battery and issue's gone now.
Also the reason for my battery getting damaged so early is QC 3.0 charger. I would suggest using it only when you're in a hurry.
Update: Replaced battery from local mobile repairing shop. Tested a full day. No reboots. Seems it was the battery after all.
Andrio said:
Update: Replaced battery from local mobile repairing shop. Tested a full day. No reboots. Seems it was the battery after all.
Click to expand...
Click to collapse
Yeah its 100 percent the battery, the battery got broken and cant provide power to the phone while opening some heavy apps, thus the phone reboots