I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar
durantala said:
I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar
Click to expand...
Click to collapse
Did you try to just uninstall supersu and redownload it from the play store?
Lennyz1988 said:
Did you try to just uninstall supersu and redownload it from the play store?
Click to expand...
Click to collapse
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/
durantala said:
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/
Click to expand...
Click to collapse
Right now I don't see any other choice than flashing a stock rom.
Or you could try reflashing the recovery.
Make sure you are using the back USB ports and the original cable. Odin is quite sensitive with this.
Related
i have a problem that just showed up. Its on my rooted atrix4g, and its says " The application Luancher (process com.koushikdutta.luancher2) has stopped unexpectedly. Please try again"
Im a total noob and i think it has do with clockworkmod that I might have installed, not sure tho. I really didnt even mean to install it, i saw it and clicked on it then it said app installed. Any help would be much appreciated.
Had this problem before and I just had to pull the battery. Hopefully that's all the damage you did. If it still force closes in loops after restarting, I think you're going to have to flash a ROM via CWM.
taking the batter wont work, first thing i tryed.
Is this the CWM your talking about?
http://forum.xda-developers.com/showthread.php?t=1019143
so i can get into the phone, tryed to do recovery via volume, but gives me failed to boot 2 and then hangs.
its only when it goes to home screen that the problem exsists.
okay so i wondering if this work help me at all?
http://forum.xda-developers.com/showpost.php?p=16093882&postcount=4
I would like to flash to stock, thats the only way this will go away. But i dont wanna brick the phone.
Im not sure which flash is correct for me atm. The phone is a week old
Help is MUCH appreciated.
Got rsdlite and a stock rom and flashed it, + wipe. Then the error was still there, so i was bummed. So i tried Android Recovery and it WORKED!
Factory reset fix all my problems!
Hi everyone,
Full blown Android noob here, coming from BlackBerry.
Here's my story:
I rooted my AT&T D800 G2 using ioroot25 today and installed apps like Titanium Backup, Wakelock Detector, and Greenify. None of which caused any problems.
The issue started when I found this thread http://forum.xda-developers.com/showthread.php?t=2664507 which explains that there are two .so files related to carrier iq in /system/lib. So using the adb tools with ioroot25, I was able to remove these two files. Afterwards, I rebooted my phone and the persistent error message that "Unfortunately, the process diagandroid.iqd has stopped." Okay, luckily I had kept the two carrier iq files on my computer, so I put them back into /system/lib (which was a serious pain in the a** for me because I kept getting permissions errors that I didnt understand).
This error message doesn't let me use the phone at all. When I hit OK, it immediately pops back up, rendering the phone almost useless. If I'm stubborn, I can get to one button or something on screen within about 10 minutes.
I don't think the two carrier iq files are causing this because I put them back and the problem still exists.
Thinking it would help, I booted into I guess what would be called "recovery mode" (there's no custom recovery installed on my phone) and I used it to perform a hard reset. This was clearly a mistake because now I can't get into the menu to enable developer options and usb debugging.
Now I'm stuck and don't know what to do, any suggestions to get rid of the "diagandroid.iqd" error would be extremely appreciated.
Thanks for your help
Bump? Any help at all would be appreciated.
Bump again
Currently I have no way of turning USB debugging on so I can access ADB.
Also when I go to download mode, it gets stuck on "Firmware update" and the progress bar stays at 0% and does nothing.
If there's a way to remotely enable USB debugging, I'll love you forever.
Please help
yeah, I need this can't use phone lol.
rancur3p1c said:
yeah, I need this can't use phone lol.
Click to expand...
Click to collapse
I just used this thread: http://forum.xda-developers.com/showthread.php?t=2663369 and completely wiped the phone to fix the issue. I don't have a fix other that this nuclear option, sorry. Good luck.
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
RawSynergy said:
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
Click to expand...
Click to collapse
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
DeadlySin9 said:
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
Click to expand...
Click to collapse
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
RawSynergy said:
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
Click to expand...
Click to collapse
NB1 is the only one you can get, just try downloading either one again.
DeadlySin9 said:
NB1 is the only one you can get, just try downloading either one again.
Click to expand...
Click to collapse
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
RawSynergy said:
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
Click to expand...
Click to collapse
When you plug in the phone in Download Mode, does the blue box in Odin light up? If not, reinstall samsung drivers
Sent from my SM-N910G using Tapatalk
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Ghujii said:
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Click to expand...
Click to collapse
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Ghujii said:
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Click to expand...
Click to collapse
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
I will attempt to do this, since nothing since has work. I am about to get a new logic board for the system in the next 2 weeks. Towel root DOES typically work on this system, however the last time I attmpted it it failed to work outright. Im not sure what has changed with the device, but i believe reflashing stock is the best method. The phone now, will boot up, then skip the lock screen and go straight to the home screen, which is black with no pull down bar, or with no signal and there is no way to rectify it. Even if there were, it boots back down and launches back up and becomes locked at the ATT logo.
After a fair bit of messing with it, and recovery mode it will sometimes boot normally where it tells me that processes has failed and askes me to cancel the ''app''. This is the best option to update the phone and attempt root, but getting it here is so difficult because it reboots itself and the mode is rare to acquire. This problem either is due to the kernel, or the rom i believe. I also am to believe the powercell may have some issue, as i replaced the battery a few weeks back and it worked fine for about 1 week.
Booting into safemode doesnt work either as it skips over the lock screen straight to the home screen. Outsidce of replacing the logic board, or attempting another flash im at the end of the short rope i was already on in terms of options.
sway8966 said:
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
Click to expand...
Click to collapse
UPDATE: I found therein two methods to flashback to stock. I did so, then proceeded to attempt to flash from nb1 to nj4. Progress stopped there when it flung an error 7 at me. So this means either something in my phone is corrupted or the file i downloaded from the above mentioned forum is corrupted. I also attempted flashfire, but seen as it STILL crashes at random due to process errors thats almost impossible to attempt.
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
engwee said:
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
Click to expand...
Click to collapse
read this - http://forum.xda-developers.com/note-4/help/note-4-issues-t3453048
there are links to more threads related to your issue.
Short version though:
it is dying. install wake lock application, add it to start up and set settings to #4.
accept the fact that your phone will eat the battery faster and one day WILL die completely
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
engwee said:
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
Click to expand...
Click to collapse
no need to be rooted, just download, install and set it to autostart
I'll try it if I somehow manage to get the phone working again, Smart Switch just fails now midway through.
golden_m said:
no need to be rooted, just download, install and set it to autostart
Click to expand...
Click to collapse
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
engwee said:
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
Click to expand...
Click to collapse
yes, that is the app.
i've read it does not allow your phone to go to sleep mode.
drains the battery faster, but this is the only way to keep note 4 working without swapping its motherboard...
I have a question, my gf recently bought a note 4 and we may swap our phones and if we do, i'll flash CM and tinker with it because i find this phone very interesting, just a question, does this bug affect the N910C (exynos) model? Do i have something to worry about? Because the phone is warrianty protected and if it's the case, i don't want to break it. I hope someone will shed some light on this