Develop Bugs

[Q] Note II dying, Please help!

Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*

mrkupochan said:
Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*
Click to expand...
Click to collapse
Could you please specify what Rom and version that you flashed?
Sent from the rabbit hole.

Did you install one of the other custom recoveries manually yet? Btw. IMHO TWRP is the best anyways. Did you do a full wipe before installing new ROM? what kernel/version are you on?

I went from using the Android revolution HD 10.0 version with stock kernel, I changed to AllianceROM N7100 XXDMA6 JB V1.0 but didn't find it smooth enough so I swapped back to Revolution, thats when I found twrp had installed.
I've tried flashing the stock recovery and i'm still getting the same issue.
I've since reflashed cwm but this hasn't solved the problem unfortunatley.....No idea what to do

You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.

Martux76 said:
You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.
Click to expand...
Click to collapse
All done, several times, no difference

Have you considered it could be sudden death syndrome?
You should have nothing to worry about in terms of it dying, since you have a very recent base rom (dma6), which include safeguards against it.
When it freezes, have you tried waiting to see if the phone responds after you press the Home Button?
I ask this because I've read reports of people waiting for over 20 minutes for the phone to become responsive again after pressing the home button when in standby.
Another thing: have you ever flashed a full stock rom after DLL7 (including DMA6)? I ask this because DLL7 and later include a new bootloader that *supposedly* helps address the sudden death issue. It doesn't hurt to try anyway.
Sent from my GT-N7100

If ur pc recognises ur phone in download mode seaech the forum for rescue firmware (it comes with pit file) and flash it with odin..u should be sorted then.
Sent from my GT-N7100 using Tapatalk 2

[Q&A] [ROM/KERNEL][4.4.4] Quantum 5.2 & QuantumKernel 10/6

Q&A for [ROM/KERNEL][4.4.4] Quantum 5.2 & QuantumKernel 10/6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Simple question, from a simple user
singhz905 said:
Yep, Thanks. I just re downloaded the Kernel and it flashed perfectly.
Click to expand...
Click to collapse
First, want to say a big thank you to Pwn for the great ROM you created and the support you've given in the threads.
I've been keeping up with updates for about a year now, but wanted to ask the simple question about "flashing" a new ROM version or Kernel.
I use CW Mod recovery as well as titanium root to back up data and apps etc. When needing to flash a new kernel, what steps are required to ensure it is done correctly? I follow your directions on the home page, wiping everything a few times and installing fresh. From what I gather, that is only needed for flashing new rom's, is that the same process I must follow for Kernel's? Each time I return from the bootloader I install titanium backup from the play store and run my restore of apps etc, not sure that's the best practice, but I am looking for simple answers. I'm a father and work a lot of hours here in Bosnia and Herzegovina, and don't have a lot of time to dedicate to spending hours tweaking the device. I use your rom for it's simplicity and battery life. Any guidance is much appreciated.
Thanks,
Andrew

from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness

mrrocketdog said:
from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness
Click to expand...
Click to collapse
Great information as well as confirmation. I will take your advice and create the zip file. That will make things a lot easier for sure. And thank you for the quick response!

Quantum Kernel 10/11
I take it that bluetooth is working again on Quantum Kernel 10/11?

Thanks!
Hey pwn! Thanks for Quantum/ Quantum kernel! I used to always use CM10/11 and it was never that stable for me and the GPS wouldn't work most of the time. I installed Quantum kernel 9/8 and the rom and it was pretty stable I did get some restarts in apps once in a while. However, once you released the new 10/11 kernel everything has been running super smooth! Thank you so much for all your work. I only had one issue with the new kernel, when my battery was completely drained and then shut off, I then plugged in my phone to the AC adapter and it would stay at the boot logo with samsung and pwncakes at the bottom. However, once I let my phone charge for a couple minutes I was able to start it up without any problems. Thanks again!
---------- Post added at 06:29 AM ---------- Previous post was at 06:16 AM ----------
trent2 said:
I take it that bluetooth is working again on Quantum Kernel 10/11?
Click to expand...
Click to collapse
Yep, it's working for me. I'm using a pioneer head unit in my truck and stream audio and phone calls.

Quantum Kernel
Thanks, I'll have to try out the latest.

Hey all. I'm using latest philz touch recovery. For some reason I can't flash the 10/11 kernel with it. Status 7. Assert error. Any ideas?
Sent from my SGH-I747M using Xparent Cyan Tapatalk 2

REPORT: 3hrs post clean flash. att sghi747UCUFNE4.
twrp 2.6.3.1. superSU v2.0.
carbon nightly 10-16 with QK 10-11.
wifi , sound , gps all good. (never have used bluetooth, so dont know. srry).
NO : f/c , random reboots.
no calendar icon (?). & would like to request , if able and not too much trouble , the APN settings menu.(!?). unless i totally overlooked it , which i don't think i did. (please). thanks once again pwn for helping to keep our 'ol s3's up-to-date.
err on the side of kindness

:GOOD:
err on the side of kindness

That looks familiar
Sent from my SAMSUNG-SGH-I747 using Tapatalk

manfromgta said:
Hey all. I'm using latest philz touch recovery. For some reason I can't flash the 10/11 kernel with it. Status 7. Assert error. Any ideas?
Sent from my SGH-I747M using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
My guess is you have an unsupported version of recovery installed like d2can instead of d2att. Follow these steps to find the problem: http://forum.xda-developers.com/showthread.php?t=2302599

Update to my fellow Quantum members. Have flashed properly and wiped properly, reloaded Q5.2, QK10-11 and restored my apps/data from TIBU. Since this upgrade, my phone is discharging it's battery within minutes. I can't boot it properly when it is plugged into a charger and at times the screen is locking then unlocking itself then crashing. I have tried full wipes and factory reset's and then flash everything from scratch, but to no avail the battery life is still crashing. Any advice? I researched this problem in the threads and only saw a solution to go back to the nandroid or something like that, but did not see instructions, therefore I am lost like a proper noob.
Thanks,
A
mrrocketdog said:
from within Tibu you can create a zip flashable from recovery , and restore apps from there. (no need to re-download from playstore each time).
for flashing a new kernel , i personally just flash the kernel , wipe dalvik and cache , and then reboot. (i have read that wiping dalvik/cache is unnecessary after flashing the new kernel , but thats just my habit). hope this helps. remember : always have your backup and read read read.
good luck. :thumbup:
err on the side of kindness
Click to expand...
Click to collapse

Texan806 said:
Update to my fellow Quantum members. Have flashed properly and wiped properly, reloaded Q5.2, QK10-11 and restored my apps/data from TIBU. Since this upgrade, my phone is discharging it's battery within minutes. I can't boot it properly when it is plugged into a charger and at times the screen is locking then unlocking itself then crashing. I have tried full wipes and factory reset's and then flash everything from scratch, but to no avail the battery life is still crashing. Any advice? I researched this problem in the threads and only saw a solution to go back to the nandroid or something like that, but did not see instructions, therefore I am lost like a proper noob.
Thanks,
A
Click to expand...
Click to collapse
Some battery stats screen shots or a BetterBatteryStats log could help to diagnose your problem assuming it's a wakelock causing it. Try leaving your phone idle after unplugging or rebooting for a couple hours to get better stats.
Edit: This thread might help you out if it is a wakelock: http://forum.xda-developers.com/showthread.php?t=1179809

luckie10 said:
Some battery stats screen shots or a BetterBatteryStats log could help to diagnose your problem assuming it's a wakelock causing it. Try leaving your phone idle after unplugging or rebooting for a couple hours to get better stats.
Edit: This thread might help you out if it is a wakelock: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Thanks for your reply. There in lies part of the problem, I can't get it to stay on for longer than 20 seconds or so to take screen shots, download the battery stats log etc. It is constantly unlocking and relocking the screen over and over and then shuts down and doesn't reboot properly. Also, with the battery out or just on AC power it will not power on.

Quantum 5.2 is running very smooth on my phone. Quick question though, my bootloader is I747UCALG1 and modem is I747UCLG1. What bootloader and modem should I upgrade to in cwm, I've been hearing about this NE4. Or should I just go for the jellybean ones? Thanks!

Texan806 said:
Thanks for your reply. There in lies part of the problem, I can't get it to stay on for longer than 20 seconds or so to take screen shots, download the battery stats log etc. It is constantly unlocking and relocking the screen over and over and then shuts down and doesn't reboot properly. Also, with the battery out or just on AC power it will not power on.
Click to expand...
Click to collapse
Gents, it has been a few days now and I have no solution for even booting up the phone. Now when holding the power button down to restart it will begin to reboot, but then just shut off. I rarely can get it to the recovery screen, but then it crashes quickly. This limits anything I can try to do in recovery, so I'm open to any suggestions at this point.
Thanks!

have you put this on the general s3 Q & A thread ? more would see it there. just an idea.
err on the side of kindness

Update. So I finally had some time to scour the forums for a possible solution and troubleshoot further. Turns out the power button was shorted, had to watch a tutorial and removed it. After getting to recovery I was able to flash 5.2 and latest kernel etc. So far so good, it needs a full charge and hopefully that will go smooth. As this problem started it was discharging the battery so incredibly fast I couldn't keep it charged. Thanks for your help everyone, crossing my fingers it stays up!

Texan806 said:
Gents, it has been a few days now and I have no solution for even booting up the phone. Now when holding the power button down to restart it will begin to reboot, but then just shut off. I rarely can get it to the recovery screen, but then it crashes quickly. This limits anything I can try to do in recovery, so I'm open to any suggestions at this point.
Thanks!
Click to expand...
Click to collapse
Sounds like it is hardware related I'm guessing faulty power switch. I've had two go bad on me and that's exactly the symptoms you describe. $20 fix unless you do it yourself
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
aircooledbusses said:
Sounds like it is hardware related I'm guessing faulty power switch. I've had two go bad on me and that's exactly the symptoms you describe. $20 fix unless you do it yourself
Click to expand...
Click to collapse
Well glad you got it sorted out any way

[Q&A] [ROM][L900] Cyanogenmod 12.0 [12/14/14]

Q&A for [ROM][L900] Cyanogenmod 12.0 [12/14/14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][L900] Cyanogenmod 12.0 [12/14/14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

keyboard ?
works Good to what i see but there's no keyboard . Any fix for that ?

Working great no issues with phone, gps or camera. Great job and I look forward to the updates. Seems great so far.

Thanks
I just installed the new build I am only wondering how do I turn off my mobile data. This ROM is amazing and everything works except for data turning off and front camera

Battery Life
When i flashed this rom onto my device, i noticed a significant drop in battery life. Has anyone else noticed this and is there a fix for this?

thnx
Thank you sooooooooooo much man ,,, its sooooooo cooool ROM
working Perfectly on my sprint Note 2 SPH-L900
camera works fine ,,, everything is cool ,,, downloading now gapps

So I'm relatively new to the forums, I mostly just read, learn and try to stay out of way. Just flashed latest nightly last night. So far very smooth and stable. I did some poking a prodding this morning to answer some questions I had coming from CM11 which I was also new to.
Nice to see Sprint carrier billing back in this version. I know I saw it posted that NFC was not working but everything but Tap & Pay seems to work fine for me. Beam and Tags all function okay.
On top of Netflix not working yet, Play Movies 3.6.16 FCs on launch and after reverting to 3.4.23 it waits until you press play to FC.
I did have the keyboard issue that has been mentioned but was prepared with SwiftKey apk on my sdcard just in case. After finishing setup ALL keyboards seem to function just fine.
BT and GPS both working great.
All in all very usable and I'm going to give it a go as a daily for as long as possible though I may have to revert back to CM11 just for the Netflix/Play Movies since we only stream in my household. We'll see.
Not sure if this thread was the best place to share (I can't seem to comment on the main thread) but if there's a more appropriate place to provide feedback that someone wants to point me at, happy to do it.
Nice work everyone who's contributing. Thanks for your efforts keeping my Note 2 relevant.?

GPS
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.

k3v0 said:
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
Click to expand...
Click to collapse
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."

So I've been following the change log for this Rom, and I can't understand much.
I'm still on the 1/5/15 non nightly version and it's pretty much functional as a daily driver. What I'm wondering is are there any major differences for the newer nightlies?
Perhaps in addition to being a Q&A on these nightlies, everyone can post which version they're on, how it is (what's broken/what's been fixed), and what's new if anything.....

Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.

The Commish said:
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
Click to expand...
Click to collapse
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app

t4d73 said:
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.

The Commish said:
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
Click to expand...
Click to collapse
Lol. Yeah I wouldn't get your hopes up too high for that. It might happen but I guess we'll see. I don't think any device has gotten a milestone just yet anyway.
Sent from my SM-N910P using XDA Free mobile app

Keeps restarting on cm12 boot screen
Hey guys,
I have a situation I've never come across and wanted to see if someone might be able to point me in the right direction. I have two Samsung Note 2(l900) and running on cm12 as of this morning. I installed the new nightly on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
It seems to work just fine if I flash to stock touchwiz but recovery seems to have issues.

Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?

The Commish said:
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
Click to expand...
Click to collapse
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.

KAZETARO said:
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
Click to expand...
Click to collapse
Sorry, I'm probably not the most knowledgeable. If it wasn't for these forums I wouldn't know how to do any of it. I haven't had any issues flashing, but I followed the steps I quoted from the get go and do that every time. Currently I'm back on the last KitKat nightly because Netflix/Play Movies is still not working on CM12. Have you tried any of the CM11 builds? Im currently using:
http://download.cyanogenmod.org/get/jenkins/98444/cm-11-20150118-NIGHTLY-l900.zip
and I use the 20140606 GApps package found here:
http://wiki.cyanogenmod.org/w/Google_Apps#Downloads

The Commish said:
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
Click to expand...
Click to collapse
Odd that Netflix and Play Movies don't work. Plex, Amazon Instant Video, MX Movie Player, and Chromecast all work.
Sent from my SPH-L900 using Tapatalk

Deleted

New to GN2

Hi folks,
Just decided to retire my old S3 and when looking for a new phone my main requirement was to get a good DAC built in without breaking the bank or renewing my contract, ended up with the Sprint Note 2. Naturally I was excited but quickly put off by the stock ROM so I decided to root/flash, etc. This is what happened so far;
-Rooted with newest TWRP and root verified on stock rom (followed NK2 instructions)
-Made the big mistake of flashing now without backup, after trying a couple of roms I kept having the same problem (phone gets stuck in load animation indefinitely regardless of rom flashed)
-Gave up on custom roms so I flashed a rooted stock NE2 rom and phone turned on wooohooooooo
-But wait, no network connection, no voice or data, tried to flash modem zip file from http://forum.xda-developers.com/showthread.php?t=2139889 but it keeps saying zip is corrupt, redownloaded & recopied to SD with the same result.
Now I have a working phone but not so working since I can't place calls. What went wrong? any help is very very appreciated.

Phone works after flashing Alliance ROM but somehow now TWRP recovery is gone and phone is UnRooted which is less than ideal but it works nevertheless...
Now before I go off wasting a whole day flashing & waiting for battery to recharge can anyone please point me in the right direction?
I need to figure out the following:
-Root method that works, I'm on Alliance NE2 now
-Which recovery is best recommended for current ROMs?
-Need a kernel that enables audio features like Direct DAC & upsampling
-ROM that actually works with said Kernel and functions at least 90% with wifi tethering etc.?
Surprised it's this difficult with this phone coming from the S3 which took me no more than an hour first time rooting/flashing.

hhmmm 63 views and nobody able to help?
Currently stuck on this ROM, which is horrible because maps doesn't work well, pandora crashes, UI fc's left & right and to top it off the phone is sluggish in every way possible.
Unified Toolkit not working, drivers installed properly, ADB visible in device manager, debugging enabled yet phone can not be seen by Toolkit.
I really don't want to switch back to my cracked S3 but I'm not left with many options considering my note 2 is barely usable now.
Is anyone out there... there.... ere... ere... ere.....
lol seriously feeling like I'm the only person left in these forums.

Use odin to flash recovery but make sure you uncheck reboot option. Once flashed remove battery and while doing the recovery hotkeys insert battery. Now wipe everything and flash another rom.
Sent from my GT-N7105 using XDA Premium 4 mobile app

here's what I've done now;
-Flashed newest TWRP via Odin
-Wiped & flashed Rwilco12's NE2
-Rebooted and phone booted yipeeee
-No cellular connection, crap phone i hate you
-Rebooted to recovery & flashed NE2 Modem
-Rebooted again and recovery is now gone
So either I get root but can't use the phone as a PHONE
or I loose Root and get basically the same POS I started with.
I've given up on eye candy, custom rom, custom settings and my expectations have dwindled down to just ANY ROM + Root + Tether yet that can't even be accomplished. I know I'm doing something wrong but at this point I'm over 10 hours into trying to figure this out and have no idea what to do next. Anything?

Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM

oceanisbleu said:
Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM
Click to expand...
Click to collapse
Twrp 2.8.6.x works for almost every rom but you will find most users recommend philz. I as a wantabe dev will suggest philz 6.0.7.9 expect in a few rare cases with aroma installer needing twrp. Personally I have philz 6.9.7.9, twrp 2.8.6.0, shift dual recovery and devil dual recovery zip on my external sdcard. This way I always have what I need depending on what I am doing.
All this info along with solutions to every problem is here on xda already. It may take some time to find everything but really the users should do his homework before doing anything to the phone anyways.
Also if you read the rom thread (Alliance) you would know why you lost root. Simply put you updated supersu app and binary. It is a known issue on every ne2 based custom rom for this device.
Sent from my GT-N7105 using XDA Premium 4 mobile app

Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!

oceanisbleu said:
Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!
Click to expand...
Click to collapse
I will read every page myself even if it takes a week. You say reading it is more trouble than it is worth which is why you had that issue with Alliance. Same goes for your omni issue.
If you don't want to read that is up to you. A google search will normally help with common issues. I dont mind helping but you have to help yourself first. Not to be rude but I wont answer your omni question because you have not looked. Ypir issue is the number 1 issue omni users have.
Sent from my GT-N7105 using XDA Premium 4 mobile app

won't argue with your opinion as I have my own

oceanisbleu said:
won't argue with your opinion as I have my own
Click to expand...
Click to collapse
I see you edited that a bunch. I dont mind helping. I have been helping so far. Now about the omni gps. I only know on possible fix bit it is a pain.
1. Flash stock/stock based rom
2. Get gps lock
3. While locked and in app reboot to recovery
4. Wipe and install aosp rom & gapps or restore aosp backup
Then you might get gps lock.
Sent from my GT-N7105 using XDA Premium 4 mobile app

reading back I realized some clarity on my part would have been helpful rather than make a general statement.
So the issue with reading 25, 50 or a 100 pages isn't by choice (may have sounded arrogant the way I said it at first) but I work 50 hrs a week, I do work on my home myself, I rent out rooms to students, I have other projects going, etc. so a very very busy lifestyle. Not to mention the daily crap that tends to come up all the time the moment I get home from work so in short, I really can't afford the time to read in that much detail whether I want to or not.
Regardless, by no means am I lazy when it comes to research, notice my post count? yet I've been here since 2009, and since 09 I've had at least 8 different phones (windows phones too) I really try to figure out everything I need on my own so in this case I spent 3 days working on my initial issues, after that I posted this thread which was 8 days ago and had it figured out and finished yesterday (a few bugs aside), that's easily 10 days I spent at least an hour or two a day working on one thing. Surely you understand how frustrating that must begin to feel.
Regarding my last reply, haha I had to delete most of it because I realized I was beginning to take my frustration out on you when in fact you're the only person who actually offered help (still very very thankful) and to top it off I screwed up the rest of the reply when I mentioned GPS, got that mixed up with the topic we were actually discussing (losing root) this happened because I was reading through the GPS issues before I got to your reply and yah mixed it all up, so again apologies for the lack of clarity and thanks for your last reply, it's more straight forward than all the comments I found on that issue.
You won't have to explain anything else I promise haha and I did all this just now but want to verify I did it correctly so I don't come back to it again. After flashing ROM/Gaps/Kernel & supersu, never update supersu after running rom correct?. Root verified as of 30 minutes ago.
GPS, this one is a big big deal because I use it for work but I had already found the answer pretty quickly as I had read something about it before I even flashed Omni.

I do know how frustrating it can be. I have been in worse spots and had to create my own fixes which I have shared here. As far as time goes I understand that being a parent of 7 children.
I am still active here and always willing to help others long as they help themselves also. We seem to have gotten off badly. While some of your post seemed you had done nothing to help yourself. So lets forget earlier stuff and move on.
Yes you seem to have all the steps correct.
FYI android 5.0-5.0.2 all have gps issues but there is a flashable fix. Most new 5.1.1 builds have gps fixed.
If you run into any issues feel free to ask but include steps you have taken to fix the issue. The more you tell the better help you can get. Plus others wont think you are wanting to be spoon fed.
Sent from my GT-N7105 using XDA Premium 4 mobile app

haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn

oceanisbleu said:
haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn
Click to expand...
Click to collapse
Well I personally have a Frankenstein device. It started out as a sprint l900 but I removed the sdcard/sim board and put a n7100 board so I can use a cricket sim. This causes issues with calls on aosp so I run modified t0lte (n7105 international) roms.
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Sent from my GT-N7105 using XDA Premium 4 mobile app

jlmancuso said:
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile, I believe Phill'z CWM download link is down as well.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Click to expand...
Click to collapse
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:

oceanisbleu said:
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:
Click to expand...
Click to collapse
Well the donation would be nice but understand when you hit my donation button/link it will take ypu to the Red Cross donation site. That is not a mistake. I personally dont take donations and feel of someone wants to donate something it should go where it can be used by those who need it.
Sent from my GT-N7105 using XDA Premium 4 mobile app

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.