I have a used Samsung Galaxy S3 Mini GT-I8190 . When I shut down the phone the battery still drains. The longer I leave the battery in the shut down phone the more charge it looses. Typically the battery looses between 1% and 2% charge per hour when inside the shut down phone. After a few days without turning the fully charged phone on the battery is completely dead so that I cannot turn on the phone again without charging first. I don't know the previous owner and cannot ask them if they had the same problem. ### Things I tried so far: - Tried to spin the battery on a table to see if the battery is bloated. The battery did not spin at all. Its completely flat on both sides. - Removed the fully charged battery from the phone, let it sit outside for a few days, put it back in, turned on the phone to read the battery level: The battery was still full – so the battery shouldn't be the problem. - Bought a new battery from another vendor anyways and did the same tests as before. - Factory reset (multiple times) - Update to the latest available OS (Android 4.1.2) provided by the vendor. - Update to the latest available custom ROM (Lineage OS 14.1 / Android 7.1.2). - After the factory resets and after flashing I did not install or customize anything apart from the following things. Of course, they had no effect since the phone was turned off — I read about these things in some forums and tried them anyway. - Only on the vendor's OS: Stop the pre-installed Mail service (even though I didn't sign into anything). - Turn off everything (Wifi, GPS, ...) - Enable (extreme) power save mode Neither did I insert a SIM card nor an SD card into the phone, so these two can also be ruled out as the culprit. ### Question Why does the battery drain when the phone is shut down? Can I do anything about this?

For some time now (I think it's from the latest Android update) I have this problem, that time to time (on daily basis) people can not reach me, like I would lose connection to the Network. I get an SMS after some time about all the calls I did miss. Sometimes I have a hard time to call as well. I did call my operator, and they didn't had any report like this so far, and I did call Samsung service, and they didn't know about this issue, so I guess is on my side. If you have any idea what would the problem be let me know.

I've got a S3 Mini (i8190N) & I tried to install a custom ROM to it which failed. My phone will boot but then before the ROM/OS starts it reboots so it's stuck in a Bootloop. I cannot get into Recovery 'cause when I try that it simply just reboots. I can get into download mode! I'vve had enough messing about trying to find a custom ROM; I don't think there is any out there. (The one I tried was mentioned later on in the thread that it isn't compatible with the model I've got.)

I tried to flash I8200XXUAPB1_I8200OXXAPC1_I8200XXUAPC1_HOME.tar.md 5 from Sammobile on Odin latest version and it failed... I also tried to reinstall the drivers, reboot PC and I also tried other odin versions like : 3.7 3.9 , 3.10 but still... no luck. So I need help here Screenshot :

I installed KINGroot and regretted it. Now I can't remove all of its files because of permissions only KINGroot has. My friend tried to remove it by using towelroot and other methods but my phone crashes them. I need a PC method to remove all KINGroot files but also having my phone permanently rooted. The friend I mentioned and my other friend have rooted phones without KINGroot. Can you please help me solve this issue. I have: - Samsung Galaxy S3 mini - model number: GT - I8190 - version 4.1.2 - Phone manufacturing date: Jul 28 2013 If you require any other information about my phone please let me know. I messed up.

I'm trying to do a data recovery on a Samsung mini that was dropped in water (I think). The phone won't boot past splash screen and developer access isn't enabled. The best idea I've come up with so far is to do a hard resent and then try to some data recovery software on the phone after it's reset. I just wanted to try and double-check before I did something stupid? Many thanks, Niall

I have recently bought a Samsung galaxy s3 mini and there is no haptic feedback on my soft buttons or typing a message, there is only a vibration key press on my lock screen. I have tryed going into settings, language and input, keyboard setting but there is no vibration on key press option in any of the settings I have looked through. Can someone help me please?

Recently I installed a number of Cyanogenmod11 Themes from the Android Market. Now I want to uninstall some of then But whenever I try to uninstall it my phone soft reboots. And the theme is still in the phone. The phone I'm using is Samsung Galaxy S3 Mini GT-i8190 running CyanogenMod11.

So basically me, the stupid idiot, rooted my phone using Kingroot. Bad choice. Now I want to completely factory reset my phone. My friend suggested flashing it twice and then resetting it. How do I do it? Phone: Samsung Galaxy S3 mini Model: GT-I8190 Version: 4.1.2 Baseband version: I8190XXAMG4 Kernel Version;: 3. 0. 31 - 1332988 se.infra@SEP-110 #2 SMP PREEMPT Sun Jul 28 14:54:47 KST 2013 Build number: JZO54K.I8190XXAMG4

I woke up to find My Samsung Galaxy s3 mini asking me to select a language and time and sign into my Samsung account, like it was a brand new phone. As I tried to do this it kept rebooting. eventually I managed to sign in, but it continues to reboot every minute or so and a few of my widgets are missing. After researching I uninstalled the Samsung push app but it keeps going back to the sign in start page, but it reboots before I can sign in and there is no way to skip it. I have removed my battery, SIM card and SD card, but it is still happening. I also tried a factory reset, but every time I click on it me phone restarts and nothing has changes. Does anyone know what is going on or what I can do to stop it rebooting?

I've got a Samsung S3 mini. It keeps telling me that I have insufficient space. I have just deleted loads of photos and videos, I only have a few apps. Instagram, pinterest, watsapp and picsart. I deleted two of the apps but it's still saying insufficiant space. I have no idea what i'm doing wrong? I have restarted the phone to see if that helps but NOTHING. When I've gone into storage it says that I have 810mb in the downloads...so i clicked on it and cleared the two things that I had in there, it's cleared them but is still saying 810mb.. HELP

Hi and thanks in advance Samsung Galaxy S 3 Mini, gt-i8190n, android 4.1.2 **My problem:** there are preinstaled/default/built in images for sound files that appear in Music Player (they're ugly for me) That's what I write about. **My question:** where can I find them, what is the path to the folder with them, can they be accessed without rooting, can they be switched? I don't need to nor I want to change album artwork with any app, I don't need to have album artwork matched with every sound file, I'd just like to switch up those random built in images to some that don't hurt my eyes with their ugliness :P And I'd really, really like to know where they are and what is path to them, even if I won't be able to change them, but at least to satisfy my curiosity, and I'd appreciate an answer with those informations the most. Please and thank You :)

I am [updating my Galaxy S3 Mini with Android 5](http://www.android.gs/update-galaxy-s3-mini-with-android-5-0-lollipop-firmware/) . Here is my steps: 1. Copy the Lollipop firmware and Google apps package downloaded in the page above into phone (not sd card). 2. Because I meet the fail to verify whole-file signature error, I need to install ClockworkMod Recovery. I used Odin 3.10. The name of the recovery file is recovery-clockwork-touch-6.0.2.7-golden.tar.md5. I downloaded it from [the #4 comment in this page](http://forum.xda-developers.com/showthread.php?t=2232278) . However when I checked back, it gave me 404 error :-/ 3. Everything seems to be ok, the Lollipop was installed successfully. Nevertheless when I installed Google apps, I got the [set_metadata_recursive: some changes failed](https://android.stackexchange.com/questions/62982/flashing-cm-11-i-get-set-metadata-recursive-some-changes-failed) error. The best answer suggested me to install a higher version of CWM, however when I go to the [ROM Manager page of ClowkworkMod website](https://www.clockworkmod.com/rommanager) , I see that the highest version of CWM for my device is 6.0.2.7, the version that I'm using. So should I use the higher version of CWM, even though it's not build for my device? --- After Matthew Read suggests me to recover, I repeat step 2. This time, I can't access the recovery mode. The phone screen keeps being black and after a while it restarts to normal mode.

# Issue # TWRP start and still looping. After tried to encrypt my device (Samsung Galaxy S3 Mini - i8190L) from Settings menu in Cyanogenmod rom. It started to encrypt but in some point it stop and said that encrypt end unexpected and data cannot be accesible anymore until I reset device (factory settings), after that TWRP did not start as is expected, it still restarting in a loop. I do not know what else say, if you need more details, please ask me! ### Tests ### After this error, I have tried: 1. Reflashing the same Cyanogenmod rom. 2. Reflashing TWRP recovery img. 3. Flashing CWM recovery img.

I've had the Galaxy S3 Mini for about two weeks and I can't take screenshots anymore. I hold down the home and power button but it just takes me to the task manager window. I also can't seem to be able to turn off or reset my phone.

I have Galaxy S4 mini and it showed a message that the Android is optimizing apps, then it hanged at second app, later the phone is not able to boot/Start. Nothing gets displayed on the screen, it just shows a blank black screen. I tried the Volume up + Power + Home button but nothing happened except that the phone vibrated. I need to reset the phone, how do I do it? I think the cache/RAM is overloaded.

I tried to flash a custom ROM on my old Samsung GT-I8190N. It's the first time so I need some advice. The steps I followed are as follows: - I downloaded the ROM zip file Jellybean 4.1.2 (CyanogenMod 10) 20130727 - I installed Heimdall on my Ubuntu 14.04 machine - I turned on the device on Development mode with Volume Down + Home + Start Button - I connected the device to my Ubuntu machine - I ran in terminal heimdall detect and got back the message 'Device detected' - I ran the command heimdall print-pit and I got the list of ROM partitions - I extracted the files included in the ROM zip file and got the following files and folders: - folder 'META-INF` - folder 'system' - file boot.img - As I did not know how to flash the ROM I checked some tutorials. I then checked the PIT file and noticed that there was a file called boot.img in the partition called kernel. So I decided to flash the ROM in that partition. - I navigated to the folder where I unzipped the ROM zip file ran the command heimdall flash --Kernel boot.img - the device rebooted but went into a boot loop I know I did something wrong and I would like to know if I can still fix the problem. In particular I would like to know in what partition I should flash the boot.img file that I get from the ROM zip file. When I start the device in Development mode I now get the following info:

ODIN MODE
Product Name: GT-I8190N
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Official

When I run the command heimdall print-pit I get the following output:

Heimdall v1.4.0
[removed irrelevant info]
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Entry Count: 25
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 28519
Unknown 4: 25708
Unknown 5: 28261
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MBR,GPT
Flash Filename: 
FOTA Filename: 


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 256
Partition Block Count: 768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MasterTOC
Flash Filename: STE_boot.bin
FOTA Filename: 


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1024
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: goldenxx.pit
FOTA Filename: 


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6144
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename: 


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEboot1
Flash Filename: STE_boot1.img
FOTA Filename: 


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 9216
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEboot2
Flash Filename: STE_boot2.img
FOTA Filename: 


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10240
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Dnt
Flash Filename: dnt.ssw
FOTA Filename: 


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 11264
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: reserved
Flash Filename: 
FOTA Filename: 


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CSPSAFS
Flash Filename: cspsa.img
FOTA Filename: 


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 18432
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CSPSAFS2
Flash Filename: cspsa2.img
FOTA Filename: 


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 20480
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: EFS.img
FOTA Filename: 


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 53248
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ModemFS
Flash Filename: modemfs.img
FOTA Filename: 


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 86016
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ModemFS2
Flash Filename: modemfs2.img
FOTA Filename: 


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 118784
Partition Block Count: 102400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Fota
Flash Filename: ssgtest.img
FOTA Filename: 


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 380928
Partition Block Count: 128
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IPL Modem
Flash Filename: ipl.bin
FOTA Filename: 


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 385024
Partition Block Count: 28672
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Modem
Flash Filename: modem.bin
FOTA Filename: 


--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 417792
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Loke4
Flash Filename: normal.bin
FOTA Filename: 


--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 421888
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: 2ndLoke4
Flash Filename: normal2.bin
FOTA Filename: 


--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 425984
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename: 


--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 458752
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Kernel
Flash Filename: boot.img
FOTA Filename: 


--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 491520
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: Kernel2
Flash Filename: recovery.img
FOTA Filename: 


--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 524288
Partition Block Count: 2457600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename: 


--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 2981888
Partition Block Count: 1720320
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHEFS
Flash Filename: cache.img
FOTA Filename: 


--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 4702208
Partition Block Count: 655360
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename: 


--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5357568
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash Filename: userdata.img
FOTA Filename: remained

Ending session...
Releasing device interface...
Re-attaching kernel driver...

I've got a strange problem on my S3Mini; two weeks ago has started to behave strangely, emitting the sound of charge/discharge while not connected to the AC adapter and setting the battery icon in the status with the "loghtining" as it was connected on charge. I've cleaned up the mini usb connector, thinking that maybe it was dirty and it was making some strange contacts but it has not solved anithing. Two days later it has started to not recognise when attached or disconnected to the charger; it recognize the status only if connected or disconnected while rebooting. The battery is fine; charging up, even if the phone says it is on battery, and then rebooting show then the real value of the battery. If I reboot with the charger attached the phone charge and then says for the rest of the day "100%, disconnect from the charger" even when I've detatched from the charger; if i reboot with the charger disconnected the percentage of the battery goes down fine and when I attach the charger it doesn't starts to increase and doesn't recognize that it has been set on charge. I've tested the battery, cleaned up the contacts on the usb mini and on the motherboard everything is fine: my phone isn't rooted. I haven't tryed to restore fattory setting at this time cause I've got of ton of things to save before. I don't think is an hw fault because at the reboot it would not recognize that the phone is on charge or not in this case. Anyone of you have got any idea how to solve this? If you need more informations just let me know, Thanks. UPDATE: the phone doesn't recognize when attached to a pc usb port ant the pc doesn't recognize the phone; I eat my words about my hypotesys for an hw fault......

I was playing yesterday geometry dash with my headphones (because the music is so good!) on my Samsung galaxy s3 mini value edition (i8200) and suddenly, without any interaction, the music weakened by half - but the output, so when I press vol+, hasn't changed. Therefore when my volume is maximum, I can scarcely hear the music. That's the first time. What I tried: * rebooting. Didn't change anything * removing almost all xposed module. * changing volume steps from 15 to 30 in gravitybox I have rooted the device and my superuser app are Kinguser and SuperUser. Help me please :)

Does anybody know how to root the Samsung Galaxy S3 Mini? * Model Number : GT-I8190 * Android Version : 4.1.2