S4 mini Clean format - Galaxy S 4 Mini Q&A, Help & Troubleshooting

S4 mini Clean format - Galaxy S 4 Mini Q&A, Help & Troubleshooting

Hi All
First of all i am aware of the fact that - this question has been asked many time and I DID read about it on other threads but did not tell me exactly what i am looking for.:crying::crying::crying:
Here is the story -
i bought this S4 mini, liked it very much and installed few apps for daily use - since that moment battery starts to drain dramatically so i used ODIN to flash stock ROM I9190XXUAMF7_I9190OJVAMG2_PAK however when phone rebooted - it gave me all that normal new phone setup things but all the app were still there even the main screen have the same bird pciture. I am bit confused shouldnt it be totally cleaned like new OS?
Then i did factory reset which deleted everything but didnt solve the battery drain issue.
Please advise what should i do?

The user data isn't touched when flashing the rom. You need to clear /data yourself.
The battery drain issue is clearly something to do with something in that stock rom. You should install a battery monitor app that can detect wakelocks

Related

Answers to common questions about SyndicateROM Frozen

This is a guide I’ve put together from my (in)experience with flashing ACS. It mainly comes from the replies of k0nane and theimpaler747 in the SyndicateROM thread. However, since there’s so many pages that can be tricky to search for idiots like me who just throw up random posts for others to solve their problems, I thought it would be good to summarize it along with anything I happened to notice from flashing a couple of Epics. Consider it the FIBI guide.
Step 1: Read all posts by k0nane on page 1 of the SyndicateROM thread before doing a damn thing! http://forum.xda-developers.com/showthread.php?t=976194
Instructions for CWM are in this thread: http://forum.xda-developers.com/showthread.php?t=897612
Useful hotkeys:
Download mode - Hold down 1 on the keyboard when you power on the phone
Recovery mode - Hold Volume down+camera+power to power on the phone
Reset phone - Hold volume up+camera+power. This generally works when the phone is completely locked up.
Flashing:
When going between versions of ACS, check their notes to see if you need to do anything other than flash. You can go between some versions without wiping or losing anything. You can also flash between standard and fully loaded without wiping or losing anything.
Sdcard doesn’t mount in CWM, but shows up in Android - Format the sdcard in Android.
Boot hangs on the Samsung screen – Redownload, format your SD card and reflash
Boot screen flashed between different things – Wipe cache & data 3x and reflash
Journaling:
Enable journaling – In CWM, go to backup and restore. Backup, then restore using that backup. Journaling enabled!
Make it so you don’t need journaling – Keep a copy of the ROM on your phone at all times. Should you ever have data corruption, jump into CWM and flash the ROM again. It’s quick, no wipes needed.
If you restore a backup made in CWM and want to have non-journaled again – Flash the ROM after restoring.
Other issues:
FC in a specific app – Go into manage applications and clear data for that app
FC in several apps – In CWM > Advanced, try fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
If you have any major issues that seem unresolved, Odin everything back to stock with EB13, format your sdcard in android, re-download everything, re-install CWM, re-read all of k0nane’s posts on page 1 and try again.
If you want ads back – Install adfree from market and hit revert
If your phone is freezing often - Flash either the vision kernel found here: http://forum.xda-developers.com/showthread.php?t=1012136 or the Twilight 1.0.4 kernel found here: http://forum.xda-developers.com/showpost.php?p=12504067&postcount=5904. I haven't had the freezing issues, but I'd recommend trying the vision kernel first as it has some other potential benefits.
Recommended tweaks and add ons:
Fugutweaks – This will smooth out a few random things on the phone. I’ve noticed more responsiveness on the lock screen and icons on my homescreen. Small, but nice. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=981125
Impaled Keyboard – Makes the keyboard less likely to skip keys. Still have some, but they’ve gone down a lot. I use the Speed Demon Edition, still had a fair amount of dropped keys with standard one. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=1025533&page=18
SetCPU – Handles scaling the CPU and overclocking. Use ondemand setting for smooth performance. If you have issues when the phone is idle or it doesn’t wake up properly, set minimum CPU to 200Mhz. Free for XDA members, APK can be found here: http://forum.xda-developers.com/showthread.php?t=505419
Battery Calibration – If you want to calibrate your battery without going into CWM, grab the app from this thread: http://forum.xda-developers.com/showthread.php?t=1024867. It’s now available from the Android Market.
Vision Kernel – Pretty much Twilight + gives you 1.4Ghz and Voodoo colour which improves balance when brightness is at 100%. Flash in CWM, wipe dalvik. Kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1012136
And a final note that I'm now about 10 hours into testing... if you are using fully loaded and want better battery life, really try standard. It very easy to switch, it flashes over fully loaded with no wipes or data loss, the only thing you lose is that it resets your homescreens. But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.

Great info! I recently installed the newest SyndicateROM 1.1.0 on my Epic and the only trouble I had was with the included Twilight 1.1.0 kernel. My phone kept freezing and I would have to pull the battery to reboot.
This is an issue that has been documented with the ROM and is said to be caused by the kernel and its adjustments to voltage and overclocking, not all phones handle this well.
To fix the issue I flashed the Twilight 1.0.4 kernel, as suggested by k0nane, and I am about a day into testing without any freezing issues. The only problem is that the Twilight 1.0.4 kernel has a known issue with video recording and it does not work.
Let me say that the performance increase from installing SyndicateROM and ext4 are well worth the trouble.

Have you tried the vision kernel? That might fix your freezing without breaking video recording.

is your brightness at 100%??? what was the difference between standard and fully loaded again??

VeNoM vZ said:
is your brightness at 100%??? what was the difference between standard and fully loaded again??
Click to expand...
Click to collapse
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
k0nane said:
SyndicateROM Standard includes LauncherPro. All Samsung and Sprint bloatware are completely gone!
SyndicateROM Fully Loaded - the choice of ACS team lead rjmjr69 - features TouchWiz instead of LauncherPro, and adds in Social Network Sync, Facebook, BuddiesNow, Program Monitor, and the stock live wallpapers. All the rest of the bloat is still gone!
Click to expand...
Click to collapse

Catalyst Shift said:
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
Click to expand...
Click to collapse
The brightness for battery life.

No, brightness is not at 100%. I generally use 0-25%, though I'll kick it to 100% when viewing photos or when I'm outside. Even with the lower brightness setting, I'd always have to recharge in the afternoon. I'm still doing a lot of testing for ways of having the battery last longer, today is longest it's ever gone for. I'll be adding more information when I feel like I've got a solid way of having it all setup.

OP, could you add the freezes and "terrible battery life" solutions? Namely, flash the kernel in the second post or VisionKernel. It's the most annoying one to answer multiple times daily.
Thanks much for this! Hopefully people read it.

I want to get the battery situation on my phone sorted out before adding it to the list. I was having pretty bad battery life, but switching to standard and removing gallery has made my phone last all day for the first time ever. I want to do some experiments between setcpu options, juicedefender and the vision kernel to see what works best. Hopefully by this weekend I'll have a more detailed idea as to how to get better battery life.
But for now, anyone having battery issues my current setup is using ACS standard and replacing gallery with quickpic. This has doubled my battery life.

Hey wassup everyone, first time writer long time viewer, and first let me say thanks to all the great people that have provided us with great roms for the epic and the syndicate team as well, Im currently using a Epic 4G with sindicate rom freeze 1.1.0 and i must say its awesome, aside from my battery dying really quickly when im runing it at 1.3ghz its actually great, usually i end up operatig it at 800mhz to actually save some battery life last me for 3 days at a time, and when i have it pluged in or show off my awesome epic i raise it back upto 1.3ghz, big difference cuz when i raise it up there my battery drains rather quickly like 3 percent a minute or so.....
well anyways now that, thats says, I have CWM 3..0.5 with syndicaterom twilight 1.1.0 and ive been sucessful at loading custom boot animation, but one thing is that im having trouble is loading the animation with sound? any idea onhow i can od that?, what are the steps, cuz so far ive been using root explorer to transfer and change bootanimation to load up on my screen, but i have no idea where to put the sound or how to even get it to load with the bootanimation any one have any ideas? please help, i do all his trought my phone, put the bootanimation on my sd and work from there and trasfer it to the system/media, most bootanimation that do have sound on them say to put it on the system/custimization/resources but i look every where and the syndicate rom doesnt have that archieve just the system/media, how can i load the sound into my boot? and how can i change the power off animation as wll?

Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals..
This might.. just maybe (crosses fingers) alleviate the never ending repeating of questions in the main sfr thread

Catalyst Shift said:
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
Click to expand...
Click to collapse
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
The first sign of trouble came when I installed a fresh version of SyndicateROM 1.1.0 and then flashed Vision kernel 1.1. The phone booted-up fine but when I went to shut down it immediately froze and I had to pull the battery.
Im going to stay on Twilight 1.0.4 kernel for a while until I find something else.
I have tested Twilight 1.0.4 kernel for about a day or two and have not had any problems so far. I even overclocked with SetCPU to 1.2GHz without any issues.
tmspyder said:
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals.
Click to expand...
Click to collapse
I would be more than happy to contribute my experiences if this gets up and running. PM me with any updates to the "SyndicateROM [TSG] WiKi"

Please Help a Novice
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen. Have I bricked my phone? How do I recover? Please please please help...Haven't even had my phone for a day...

By the way, the error I'm getting is:
ClockworkMod Recovery v2.5.1.0
E:Can't open /cache/recovery/log
I backed up before I installed this ROM, and Restore brings me back to this same screen / message

mercerma said:
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen.
Click to expand...
Click to collapse
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.

Hey, great idea for the thread.
Something I learned:
I was having AWFUL freezing problems. Tried all the fixes (vision kernel, old twilight) to no avail. If these don't fix your problems, try Genocide Kernel (on these forums). Solved my problems.

Catalyst Shift said:
But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Click to expand...
Click to collapse
Ok, so im thinking of switching to the standard edition of he rom cuz im currently using the fully loaded added the 1.0 kernel vision on it to get the 1.4ghz, and its pretty smooth its stable at times so im keeping it at 1.3 for now until its set more stable..... however when u said that ure at 10 hours and u still have 62% whats the speed u have ure epic set at and whats the brightness?

Nolyrics2 said:
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
Click to expand...
Click to collapse
Fix permissions in CWM/etc.
Kernels cannot cause that. It's that simple.

Nolyrics2 said:
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Click to expand...
Click to collapse
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
I installed CWM previous to transferring the rom to my sd card
I did not the first time, but per instructions on the page where I downloaded the ROM, I reformatted my sd card, redownloaded the ROM, wiped everything 3x's and tried to reinstall. Same result. I keep getting the error on just about everything I do that states "E:Can't open /cash/recovery/log"
And thank you for your advise, any more would be greatly appriciated. I did search the forum, but there is so much information, hard to find what I really want, especially as a novice. I plan to not be a novice for long thanks to xda!

mercerma said:
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
Click to expand...
Click to collapse
I could probably answer that question, im still a noob, but from what i know u need to install CWM version 3.0.5/6 in order for u to run does roms, thats why ure having trouble flashing it, since Syndicate roms are EXT4 Base Roms anything lower then CWM3 wont support since they are RFS files, go here and follow the steps
http://forum.xda-developers.com/showthread.php?t=976194
download the CWM3 and root it again, u can run the CWM Root over the previous 1 so dont worry, i did it that way and i had no problems what so ever, as to check to see what modem u had, go to settings, about phone, under base band version check to see if the last 4 letters says EB13, or DK28, or if u have the ECO5 which is the newest stock base update that came out.
Also its best to know if ure phone is from stock, or if u updated from any of the first 2 version updates, EB or DK, if u where like me that waited for the update and stayed at Eclair then updated when the ECO5 OTA came out then u should be fine....
Just incase u are from a update of EB or DK here is the link for does 2 versions of CWM3
http://forum.xda-developers.com/showthread.php?t=897612
if im wrong then someone please correct me im still a noob learning.
EDIT: just noticed that u said ure phone is messed at that point, umm u can try to do a factory reset then restart ure phone see if that fixes the problem, then try follow the steps above, if that doesnt work, u will have to download odin, which is also in that link and reflash back to stock, everything is there so if u follow does instrunctions u wont have a problem.....its actually pretty easy.....

Power on issue

Hi , I'm using a custom rom (Revolution 9.3) and have a strange issue.
I normally turn my phone off on a night to put it on charge. When the phone is fully charged it now turns itself back on. Is this normal and is there a way to stop it doing it. I have not had this problem either with the official rom or with other phones i have had with custom roms installed.
The other issue is when i wake the phone in the morning it has the "people" app open.To get rid of this i have to press the home button which crashes Sence .Once Sence reloads all is fine all day .Apart from this im very impressed with the Rom so dont really want to change it.
These are minor issues and not the end of the world but i would like to know if there is a cure. I'm fairly experienced in flashing roms but have been unable to locate any reference to this on this site. I have had to post on here as i havent the 10 posts to allow me to put in the developers section for this ROM. Thanks

I think it's clockworkmod recovery that turns the phone on when nearly charged.

Martintxx said:
Hi , I'm using a custom rom (Revolution 9.3) and have a strange issue.
I normally turn my phone off on a night to put it on charge. When the phone is fully charged it now turns itself back on. Is this normal and is there a way to stop it doing it. I have not had this problem either with the official rom or with other phones i have had with custom roms installed.
The other issue is when i wake the phone in the morning it has the "people" app open.To get rid of this i have to press the home button which crashes Sence .Once Sence reloads all is fine all day .Apart from this im very impressed with the Rom so dont really want to change it.
These are minor issues and not the end of the world but i would like to know if there is a cure. I'm fairly experienced in flashing roms but have been unable to locate any reference to this on this site. I have had to post on here as i havent the 10 posts to allow me to put in the developers section for this ROM. Thanks
Click to expand...
Click to collapse
did u perform full wipe, erased cache and dalvik cache before flashing ROM

vivek_bhoj said:
did u perform full wipe, erased cache and dalvik cache before flashing ROM
Click to expand...
Click to collapse
Yes did full wipe with super wipe as per instructions .Also did a cache wipe and dalvik cache wipe before and after install.
Thanks for the info about clockwork - it hasn't had this effect on previous phones plus when i flashed back to stock rom but still with clockwork recovery it doesn't turn on when it reaches full charge. Presuming it is clockwork is there a way to stop it ?
Open to any more suggestions though.
It's one of those things that is bugging the hell out of me but i can live with it for the extra functionality the rom gives me and the better battery life.
Little worried that the extra on time it is giving me will have a long term effect on battery life and also dont want the phone going off with text at two in the morning.

[Q] SDS- EMMC DATA Corrupt, ROM RE-FLASH OR SEND BACK TO SAMSUNG FOR MB-REPLACING?

I've posted earlier in one of the SDS/Freeze topics the exact story what did happen with my (roughly 7-month old phone).
A short summary:
I was running a 4.1.2 DLK7 -ROM together with the Perseus 36.3 kernel. I've changed kernel since I knew that I was vulnerable for the SDS. I got a INSANE Fx01 chip.
I've did ran eMMc many times to check if any memory was corrupted, it did pass the tests fine. About 4 weeks ago I had my first phone crash (reboot) while updating a Google Play Store application. Afterwards the phone was alright for roughly two weeks. Then suddenly another crash (reboot). Not even a day later I had a phone-freeze. Only option was pressing Power-button. Then the phone-freezes started to increase, the times became shorter and shorter. A new eMMC test caused a error this time and made my phone do a re-boot. Last time the phone did freeze before even seeing the log-in screen. The next day I tried to power it on, it did not respond! I removed the battery and put it back in. Then it started, but it would not go past the Samsung LOGO Screen. I could still enter the download-mode but it also says : binary counter 1 that means that the OS- is now really broken. I could also still access the recovery TWRP-modus.
I could give it a shot the flash the latest 4.1.2 ROM with Odin (if it doesn't give a nan-d error). But do you guys think it is worth it?
Is it not better to visit a repair-center and let the motherboard replaced?
My concern:
There are also many topics to find here that even with the soft-rom/kernel fix the phones start to act like this : freezes / reboots. It is the SDS-fix kicking in, that saves it from dying but the data-memory-corruption cannot be repaired. So sooner or later even with the latest rom and this chip you will have this problem, lose your data?
Thanks for the advice in advance.

Iriseyoufall said:
I've posted earlier in one of the SDS/Freeze topics the exact story what did happen with my (roughly 7-month old phone).
A short summary:
I was running a 4.1.2 DLK7 -ROM together with the Perseus 36.3 kernel. I've changed kernel since I knew that I was vulnerable for the SDS. I got a INSANE Fx01 chip.
I've did ran eMMc many times to check if any memory was corrupted, it did pass the tests fine. About 4 weeks ago I had my first phone crash (reboot) while updating a Google Play Store application. Afterwards the phone was alright for roughly two weeks. Then suddenly another crash (reboot). Not even a day later I had a phone-freeze. Only option was pressing Power-button. Then the phone-freezes started to increase, the times became shorter and shorter. A new eMMC test caused a error this time and made my phone do a re-boot. Last time the phone did freeze before even seeing the log-in screen. The next day I tried to power it on, it did not respond! I removed the battery and put it back in. Then it started, but it would not go past the Samsung LOGO Screen. I could still enter the download-mode but it also says : binary counter 1 that means that the OS- is now really broken. I could also still access the recovery TWRP-modus.
I could give it a shot the flash the latest 4.1.2 ROM with Odin (if it doesn't give a nan-d error). But do you guys think it is worth it?
Is it not better to visit a repair-center and let the motherboard replaced?
My concern:
There are also many topics to find here that even with the soft-rom/kernel fix the phones start to act like this : freezes / reboots. It is the SDS-fix kicking in, that saves it from dying but the data-memory-corruption cannot be repaired. So sooner or later even with the latest rom and this chip you will have this problem, lose your data?
Thanks for the advice in advance.
Click to expand...
Click to collapse
would suggest to take to Samsung Service rather you giving a try coz this seems to be a Hardware problem .

aukhan said:
would suggest to take to Samsung Service rather you giving a try coz this seems to be a Hardware problem .
Click to expand...
Click to collapse
Yes, I know it is a hardware problem and I do not really trust those Soft-SDS fixes. Many report that even with the latest Rom and a kernel with the fix, eventually the same happens. Data just becomes corrupt. Freezes and Reboots occur. Also the loss of data-settings did happen to me. On a re-boot I suddenly had to re-config Swiftkey , Whatsapp + etc :S.
Guess I will visit the repair-center then and ask them to replace the motherboard and flash the latest rom. Only **** part is that I have to root it again and install my 190+ apps, flash perseus or redpill and do a couple of hundred settings. I got a titanium back-up of my apps but I do not trust the back-up anymore. Maybe some data of the apps became corrupt or something.
Btw perseus or redpill with the original stockrom? what do you advice atm? both support the 64gb-micro sd cards right?

Iriseyoufall said:
Yes, I know it is a hardware problem and I do not really trust those Soft-SDS fixes. Many report that even with the latest Rom and a kernel with the fix, eventually the same happens. Data just becomes corrupt. Freezes and Reboots occur. Also the loss of data-settings did happen to me. On a re-boot I suddenly had to re-config Swiftkey , Whatsapp + etc :S.
Guess I will visit the repair-center then and ask them to replace the motherboard and flash the latest rom. Only **** part is that I have to root it again and install my 190+ apps, flash perseus or redpill and do a couple of hundred settings. I got a titanium back-up of my apps but I do not trust the back-up anymore. Maybe some data of the apps became corrupt or something.
Btw perseus or redpill? what do you advice atm? both support the 64gb-micro sd cards right?
Click to expand...
Click to collapse
Yea its Painful to re do the entire process again , and also nice thought dont restore backup do a fresh install rather restore.

STUCK on welcome screen & Dying batteries

hello
i have installed a custom ROM I don't know which ROM specifically, but the ROM was 4.3
anyhow i did not feel comfortable with the rom the keyboard did not work , so I installed 4.3 stock rom through ODIN.
the stock rom did not work perfectly sometimes the device reboots itself ...and when i call the screen turns black and I can't use it until i finish the call.
I had four good batteries....
now I can't use two of them ( when I plug them in charger they make the big battery logo fully green , but they keep charging and never shows fully charged unplug message) ..when I turn the phone on its keeps rebooting and never stops .
the other two batteries shows incorrect percentage reading ,like when i charge the phone after its completely run out of battery Its instantly become 40% charged but it's actually less than 1% .
I don't know if its a hardware issue or the system capable of ruining the batteries.( all four batteries had the problem on the 4.3 stock rom) I've tried the batteries on different phone and i experienced the same issue.
i installed 4.4.2 stock rom through ODIN and i did not had the previous (non-battery) issues with it ...but today i turned the phone on and it displayed the samsung galaxy welcome screen (like if it got factory reset) !
and it displays (Unfortunately, S suggest has stopped) when i press ok it displays (Unfortunately,the process com.google.process.gapps has stopped) >ok> ( Unfortunately google play services has stopped) >ok> ( Unfortunately,the process com.android.phone has stopped) ..... and its keep doing that !
i did cache wipe and downloaded and installed other version of 4.4.2 stock rom and i experienced the same issue.
if i connect the phone to PC the it shows that the total capacity is only 107MB !!
i did not try factory reset i don't want to lose the data if it's there.
is there a way to recover the data?
how can i fix the phone?
what is it with the dying batteries?

TALBR said:
hello
i have installed a custom ROM I don't know which ROM specifically, but the ROM was 4.3
anyhow i did not feel comfortable with the rom the keyboard did not work , so I installed 4.3 stock rom through ODIN.
the stock rom did not work perfectly sometimes the device reboots itself ...and when i call the screen turns black and I can't use it until i finish the call.
I had four good batteries....
now I can't use two of them ( when I plug them in charger they make the big battery logo fully green , but they keep charging and never shows fully charged unplug message) ..when I turn the phone on its keeps rebooting and never stops .
the other two batteries shows incorrect percentage reading ,like when i charge the phone after its completely run out of battery Its instantly become 40% charged but it's actually less than 1% .
I don't know if its a hardware issue or the system capable of ruining the batteries.( all four batteries had the problem on the 4.3 stock rom) I've tried the batteries on different phone and i experienced the same issue.
i installed 4.4.2 stock rom through ODIN and i did not had the previous (non-battery) issues with it ...but today i turned the phone on and it displayed the samsung galaxy welcome screen (like if it got factory reset) !
and it displays (Unfortunately, S suggest has stopped) when i press ok it displays (Unfortunately,the process com.google.process.gapps has stopped) >ok> ( Unfortunately google play services has stopped) >ok> ( Unfortunately,the process com.android.phone has stopped) ..... and its keep doing that !
i did cache wipe and downloaded and installed other version of 4.4.2 stock rom and i experienced the same issue.
if i connect the phone to PC the it shows that the total capacity is only 107MB !!
i did not try factory reset i don't want to lose the data if it's there.
is there a way to recover the data?
how can i fix the phone?
what is it with the dying batteries?
Click to expand...
Click to collapse
I had that situation of storage earlier.
u have no choice but to wipe all.
if u still can connect ur device to a pc, i would suggest to copy ur data on ur internal storage to ur pc.
after that, earlier what I did was flash the zoot script from cwm and do a custom mega wipe. of course ur internal storage will be wiped. clean until all the folders nd files.
then reboot back to recovery to flash custom rom again.
if u r not rooted the only way is to factory reset full wipe system data nd cache.
wipe cache only won't solve the problem of internal storage.
to be frank, u jump from 4.3 to 4.4.2, u have to factory reset. too many users try to avoid this because lazy to resetup nd backup. but u have no choice.
Sent from somewhere under the sky, at the corner of this rounded earth.
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Irwenzhao said:
OK... so ODIN is working, eh? That helps the situation. Now...
1) If you can get ADB working, probably.
2) By flashing a pit file through either ODIN or (custom) recovery. (I prefer using recovery as it's safer.)
3) Not completely sure, though it (might) be a hardware issue.
P.S. You should NEVER flash stock ROM unless you have a bricked device. I rather you flash CM11 even if you have a bricked device. I never trust stock ROM.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
not all ppl like Cm / aosp.
and stock rom is not bad. it is just most ppl don't like to do a clean flash.
without stock rom, u can't use the full feature of spen, and it defeat the purpose of having spen.
Sent from somewhere under the sky, at the corner of this rounded earth.

antique_sonic said:
I had that situation of storage earlier.
u have no choice but to wipe all.
if u still can connect ur device to a pc, i would suggest to copy ur data on ur internal storage to ur pc.
after that, earlier what I did was flash the zoot script from cwm and do a custom mega wipe. of course ur internal storage will be wiped. clean until all the folders nd files.
then reboot back to recovery to flash custom rom again.
if u r not rooted the only way is to factory reset full wipe system data nd cache.
wipe cache only won't solve the problem of internal storage.
to be frank, u jump from 4.3 to 4.4.2, u have to factory reset. too many users try to avoid this because lazy to resetup nd backup. but u have no choice.
Sent from somewhere under the sky, at the corner of this rounded earth.
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
not all ppl like Cm / aosp.
and stock rom is not bad. it is just most ppl don't like to do a clean flash.
without stock rom, u can't use the full feature of spen, and it defeat the purpose of having spen.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Or Ditto N3, stock ROM has loads of bugs (kitkat)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!

Irwenzhao said:
Or Ditto N3, stock ROM has loads of bugs (kitkat)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
I agree that DN3 is great rom.
I also agree that sometimes official firmware also have bugs.
but, I don't agree that custom rom will free of bugs that official have it.
certain bugs will still remain.
don't forget, custom rom is build on Samsung stock base with some enhancement to feel better in smoothness, functions, battery life, as well as user interface.
Sent from somewhere under the sky, at the corner of this rounded earth.

Not sure why there's an asop vs tw debate going on here... anyway, assuming the op's history is accurate, this sounds like hardware failure

Best ROM for S4 Mini?

Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.

Aztek92 said:
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Click to expand...
Click to collapse
You must have had a bad install as I've not heard of anyone else with those sorts of issues. Though it could be an incompatible app or bad/old data etc Z you might want to ry fixing first eg wiping all app data or factory reset or fresh install (backup your files first )
Sent from my Galaxy S4 Mini using XDA Labs

@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx

Aztek92 said:
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Click to expand...
Click to collapse
1. I see from your link you have the 3g version of the mini, I didn't think that one supports NFC, only the LTE (I9195) has it I think. As NFC needs the right hardware you won't be able to get it. But I don't have the 3g version so I'm not 100% certain if it has support or not.
2. Ii don't think the battery is related to CM13 directly otherwise there would be lots of people with the issue. What is the exact date of the snapshot? There was one that had battery issue but they updated it a few days later is it definitely 20160820 and not the one from a few days before you are running?
Else: If there any app showing high battery usage that doesn't normally? Or is there a problem white a wakelock? You can install an app like Trepn that will show you apps with high cpu usage (even when they are showing in about the usual place in battery stats, my browser recently locked into some sort of loop and was using a high % of cpu occasionally)
3. Always possible but unlikely it's due to Heimdal flash. TWRP should do fine. More likely the wrong Gapps causing instability, you should be on Open Gapps 6 for CM13
Sent from my Galaxy S4 Mini using XDA Labs

@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.

Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Click to expand...
Click to collapse
edit: see arco's reply below,
The 3g CM ROM will not have the NFC code I guess
No do not check "update recovery" as you might lose your current recovery
gotta go get my son now!
Sent from my Galaxy S4 Mini using XDA Labs

Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
Click to expand...
Click to collapse
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.

arco68 said:
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
Click to expand...
Click to collapse
Thanks Arco!
(I was trying to say toggle the "signature verification" option but that could lead to more problems if he has the wrong recovery!)
Sent from my Galaxy S4 Mini using XDA Labs

Yup, its GT-I9195, maybe that's from all the problems comes, wrong rom, wrong recovery. I feel kinda dumb, that i didn't check under battery before, sorry for that.
I have work to do today i guess.

@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom

Aztek92 said:
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Click to expand...
Click to collapse
Hi, sorry for bringing up this somehow old thread, but I have the exact same battery issue on my wife's serranoltexx.
I just installed CM13 on her phone, and after a reboot battery dropped from 40% to 5%. This happened twice, so no coincidence here.
Have you found where the problem came for ? Was your battery dead or have you found a fix ?
Also, I have seen your post about sview cover, very interesting. Will try it out tonight !

Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it

Aztek92 said:
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Click to expand...
Click to collapse
Thanks for your answer !
If changing ROM and calibrating did not help, then I guess it's a hardware problem. That was my first thought when I saw this drop yesterday and I already told my wife that we'll have to buy a new one. Cheers to Samsung for building phones with replaceable batteries !
Even a geeky workaround for the sview cover might suit her needs. I think she just wants to check the time and her notifications with the cover on, I don't think she even needs to answer calls (she said it never worked for her, a touchscreen sensitivity issue I believe).
If she doesn't like it, I still have the possibility to downgrade her to CM11. It seems that sview worked fine on this release. And I'm sure she won't mind kitkat as she's not as geeky as I can be

I've been using CM13 nightly (latest) for 4 days or so.
Pros:
Battery last much longer, you have many battery profiles which is nice.
External SD can be integrated as Internal (nice that some apps are automatically installed onto SD)
Cons:
Can't find tar file which is backup I made using CWM recovery rom. Looked everywhere!
Icons dissappear from home after every bootup
Can't move sys apps or preinstalled apps to ext sd card. Can't use Link2SD once you configure External SD as internal. Not so flexible.
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.

kennyk09 said:
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
Click to expand...
Click to collapse
Look in /data/media it should be there somewhere. Need root access though.
I recommend using TWRP instead of CWM.

arco68 said:
I recommend using TWRP instead of CWM.
Click to expand...
Click to collapse
Yes, but TWRP can't flash CM11 if I'm not mistaken. Old ROM, I know, but it's the latest one with S-View Cover support.
Also yesterday, I tried to restore my stock ROM backup with TWRP but could not get it to work. Stuck on "starting apps" during boot. Wiping Dalvik and cache did not help.

@thewild
If changing ROM and calibrating did not help, then I guess it's a hardware problem.
Click to expand...
Click to collapse
Not nessessary. Please notice, that i moved from CM13 (i9590) to... CM13 (i9595). I had an issue with wrong recovery. I also didn't have any problem on stock rom. If you're still gonna change battery, tell me how it worked for you.
Btw. there is something called hall monitor https://github.com/durka/HallMonitor But still i have no idea how and if it (still) works.

Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10€, so I'll give them a try and let you know.

thewild said:
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10â?¬, so I'll give them a try and let you know.
Click to expand...
Click to collapse
€10, they would have to be fake! (or used)
What is the screen on time (battery>screen) you are getting? I bet it's low & that is the reason for your sudden drops, with my old battery (original Samsung) I was lucky to get 3hrs and that had sudden drops, new battery gives me 6hrs SOT.

Can't tell you the sot because it's not my phone, but it sure is very low. And the battery drops from ~50% to 0% in seconds.
10€ seems to be the right price. They are 20€ on samsung's store, but 10€ is on Amazon, sold by Amazon. I never got fake / used items from them.
Anyway, it's worth a try. I can send it back for free if it's not OK.

Develop Bugs

welcome