Related
Dear all,
I had a note 3 n9005 white which worked fine in the first 5 days. After that, it starting shutting down randomly. The next day, when i start the phone, the screen freezes after 2-3 touches and it shuts down after 5 secs. If you plug the charger, it keep rebooting but does not work past few touches. If I boot the phone in download mode or recovery, it work flawlessly for as much time as you want. Sometimes you cannot start the phone without removing and reinserting the battery. I tried safe mode, hard reset, cache clears etc etc but no avail
I even flashed leaked polish kitkat rom just to see what happens but the issue is the same. Is it a hardware issue or a software/kernel issue ? Please HELP
If it's doing it after a clean flash of new firmware then I'd say it is a hardware issue and you may want to return it and/or get it replaced.
manee said:
Dear all,
I had a note 3 n9005 white which worked fine in the first 5 days. After that, it starting shutting down randomly. The next day, when i start the phone, the screen freezes after 2-3 touches and it shuts down after 5 secs. If you plug the charger, it keep rebooting but does not work past few touches. If I boot the phone in download mode or recovery, it work flawlessly for as much time as you want. Sometimes you cannot start the phone without removing and reinserting the battery. I tried safe mode, hard reset, cache clears etc etc but no avail
I even flashed leaked polish kitkat rom just to see what happens but the issue is the same. Is it a hardware issue or a software/kernel issue ? Please HELP
Click to expand...
Click to collapse
Can you use this app Phone INFO to check for the validity?
manee said:
Dear all,
I had a note 3 n9005 white which worked fine in the first 5 days. After that, it starting shutting down randomly. The next day, when i start the phone, the screen freezes after 2-3 touches and it shuts down after 5 secs. If you plug the charger, it keep rebooting but does not work past few touches. If I boot the phone in download mode or recovery, it work flawlessly for as much time as you want. Sometimes you cannot start the phone without removing and reinserting the battery. I tried safe mode, hard reset, cache clears etc etc but no avail
I even flashed leaked polish kitkat rom just to see what happens but the issue is the same. Is it a hardware issue or a software/kernel issue ? Please HELP
Click to expand...
Click to collapse
try to flash compatible firmware of ur phone
download it from sammobile.com/firmwares.
flashing leak firmwares are not helping cause they seems to be beta and have lots of bug.
anyway there s some threads about random restarting note3 but ur situations is worse.
almost of them as i know take their phone for replacement and if u can do it as well.
if not, search for more stable firmware of course JB 4.3
:good:
If this is true:
"boot the phone in download mode or recovery, it work flawlessly for as much time as you want"
maybe I would lean towards software, but since you loaded leaked KK, you can't go back to factory and probably tripped Knox?, you don't have many options left, especially that you tried just about everything.
IMO loading leaked software on a broken phone was not a good idea, in your case I would try to go stock as much as possible, instead.
Me too, i had this problem several times with 4.3 and after wiping my telephone to install the new kit kat 4.4.2 (polish), i Also had freeze,black screen and non responding screen forcing me to reboot my phone.
I also have lines sometimes when i use my camera!
meanwhile, i have again flashed complete polish 4.4.2 with BL , AP, CSC , Modem and PIT File . IT flashed successfully but the problem still persists. No use . any more suggestion. I think now i cannot downgrade and should i try custom recovery with custom firmwares.
I case of hardware issue, i have no choice as N9005 is not officially launched in Pakistan.So no choice .
@joexda75, my screen also dithers and shows different colors some times on portions and some times it is flawless. So you and i have the same problem but my phone is not powering up and freezing after not more than 6 sec. Recovery and download mode works perfectly as i flashed the Polish ROM again via download mode and it worked flawlessly
Did you make an complete wipe of your Phone? Otherwise you have to contact Samsung.
Gesendet von meinem SM-N9005 mit Tapatalk 2
It sounds like your phone is what we call boot looping mine showed the same symptoms as yours at the beginning and it would also come up with a messege saying that some process had unfortunately stopped working lol
Sent from my SM-N9005 using xda app-developers app
it can be fixed using Mirek190's method just check your IMEI CERTI says pass when you type *#0011# into the keypad if it comes up with PASS then follow mirek190's method without flashing block 12 or block 13 here at http://forum.xda-developers.com/showthread.php?t=2567133
Careful using mireks method. It bricked berrgs note which is currently not working.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hi,
My N910F has recently been acting weirdly. It either randomly reboots itself, or just freezes for several seconds when switching screens or scrolling/tapping buttons. This started a couple of weeks ago on stock 5.0.1 (this version, I think) running Emotion kernel. This was running fine for a while; I didn't flash any new mods during this time, although I did switch between AEL kernel and Emotion once or twice without much success.
Thinking it was just one of those situations that called for a clean slate; I backed up my important stuff, booted into TWRP to wipe all partitions, then flashed stock 5.1.1 via Odin (this version, which I'm currently running). But even before I rooted it once again the phone was displaying the same aforementioned symptoms, both during and after going through the built-in setup wizard. This behaviour continued after flashing TWRP and AEL kernel v8.2, which I'm currently on at the moment. If it makes any difference I've also noticed that the lower my battery level, the more often it reboots itself. The battery level also "yo-yos" sometimes, usually at lower levels.
I've uploaded the relevant logs as advised elsewhere for anyone who can decipher them, as I otherwise don't know what to look for. This includes my last three kmsg dumpstate logs (just in case it's a slightly different cause each time), as well as my logcat and dmesg files (whatever they are lol) which I got using the SysLog app.
Any help would be appreciated, and if you need any more info please let me know.
Thanks .
*bump*
I have the same problem. Help would be highly appreciated. : )
*bump*
[UPDATE]: Once or twice when it's crashed as above, it would try and boot again but then reboot into download mode with the following text at the top of the screen above all the other info:
Code:
Could not do normal boot.
ddi: mmc_read failed
If I then pull the battery and turn it on again, it boots up as normal (at least until the next crash). Is this something that can be fixed with a fresh flash in Odin (or some other method), or is my phone on the way to its death?
Got the same issue + loses Wifi password after random reboot. Sent the phone back to the operator I bought it from 1 week ago and they did a repair. They replaced the USB-flex, did a firmware upgrade(?? ..was already updated to latest) and sent it back. I got it this morning and at first the phone now works fine and no more "mmc_read fail". But after some time the random reboots started again. Not so often now but still 4 times over the day and twice the wifi-password is lost and I had to retype it. Now I'm on the fence and just waiting for the first mmc_read fail" to happen before I complain and send it back for a second repair. I can not imagine this beeing beeing other than a hardware fail coming from a weak spot on the phone. I got the impression many people has the same issue and it really comes to life after upgrading to 5.1.1.
I also think the problem at the service shop ist that they just do a quick system test on a clean wiped phone and can't find the issue and think the phone is fine. After reinstalling my 200 apps and setting up my phone all over again, the workload causes the issue to reappear and I now have to ask the service shop for a deeper check. They accepted this as a warranty fix all though my phone has a knox trip (0-1)x4...
I've also faced random reboots on Lollipop. How i solved that? Simple. I downgraded to Kitkat. Lollipop still having lots of battery drains and bugs even on 5.1.1
[UPDATE]
I've decided to go through my network provider to get a replacement sent out to me, which they were happy to do after going through their line of questioning over the phone ("have you tried turning it off and on again", "did you try taking out your memory card and see if that helped", "did you try doing a factory reset", etc). They say it will get here tomorrow so fingers crossed for the replacement.
The ddi mmc_read fail has not reappeared yet..
It's strange.. Lately the random reboots are not wiping my wifi passwords anymore, but now after every random reboot the multiwindow is enabled and I've got to untick it in quick settings..
Latest: It seems that the random reboot may come from heavy account sync workload. I did have 5 Google accounts syncing on my phone + 6 excange accounts and when i disabled syncing alltogether the phone ran a lot smoother and the reboots stoped. So i deleted all Google accounts except my main account and for now thing seems to be fairly stable. I've also uninstalled all for me unimportant 3'rd party apps, reducing 3'rd party app count from aprx 200 to 150..
If things develop further I'll come back with more
Sent from my ****in' phone!
Thanks fot starting this thread Jointfcfan...i am using 910P and have same issue of your post 1 and 4!!!!
Loosing hope on Samsung, it is really frustrating...
Tried cleaning cash, dalvic, reboots, on latest 5.1.1 k version...frozen all not neede games and apps ...only 1 google and 1 exchange account no auto sync
At next stage while rebooting it sometime going an error stating kernel panic and i have to pull battery to restart
Replacing USB-flex board at service shop has cured the "ddi. mmc_read fail" boot issue for good.
So to me it seems that when many people experiences this, the USB-flex board may have a built in design flaw making it a weak spot on the Note 4.
Also I found that the phone works A LOT smoother if using Nova launcher instead of TW. Random reboot count is way down and phone works almost normally. Still some lag, mostly when unlocking screen, but reboots happens only 2-3 times a day now. Still random rebooting enables "multi window" option every time..
I've also rooted the phone now using CF-autoroot. I've flashed Philz CWM recovery and using it to install Wanam Xposed. So now I can run Greenify properly in Xposed mode and automaticly hibernate apps including system apps..
NB! Be aware, flashing root and custom recovery trips Knox counter 0x1 permanently and MAY void warranty
I have also mailed my operator asking them to take in the phone a second time for check/repair, alt. replacing the phone. I guess when they did system check 1st. time without issues after replacing the USB-flex, it was done when phone was reset to factory and under no significant workload.
Sent from my ****in' phone!
Hello there xda.
I have a Samsung Galaxy Note 4 SM910F.
So what is happening to my phone is that whenever I am in any random app lets say reddit or even chrome for example. It will like freeze for a minute or two and then unfreeze.
In more extreme cases it will reboot.
So this happened randomly because I flashed a Stock unbloated 5.1.1 ROM from here back in december and everything was working smoothly and stuff. I had xposed installed and all my apps. Then in February it started with this random freeze/reboot. I had not installed anything else apart from what I had for the last 3 months.
So I restarted the phone, changed the battery and stuff to see whether that will fix it. However it didn't. So I formatted the phone (the soft type) just so I can install another ROM. So I tried another ROM, flashed the correct CP and BL and stuff and then just installed chrome and whatsapp. After an hour or two the same thing happened. So this time I factory reset he phone, like a complete wipe and I installed the unbloated ROM once again with few apps. Same thing happened...
So my last resort was to install Cyonagen Mod. After an hour or two same thing happened...
I don't know what is the problem. I read about some peoples phones emmc failing and thus the freezing, but I am not sure yet.
Please could you guys explain what I should do to fix this?
Thank in advance!
I have the same problem. Starting on mid january. I'm on stock 5.1.1 with root and twrp recovery
Tried backup and factory reset
I went back to stock after I factory reset the phone. And still had the same problems.
People say that its a hardware problem... So I guess I'll have to send it back to Samsung soon.
I think I tripped the knox. I just have to unroot and get it back once again to stock and send it back. I hope that they accept it.
i have the same problem. my model is SM-N910W8 and I bought it from 2nd hand, so no receipt and no prove of purchase.
can I still send it back to samsung to fix it?
same problem as you and now my phone died completely .
my phone was 4 months and he has not supported any longer he died naturally lol.
my operator gave me another free under warranty because the phone had a faulty motherboard and after several back galaxy note 4
This started happening to me a week or so ago and my phone just got stuck in a boot loop after it froze and rebooted. I'm on the latest stock firmware. Tried factory reset, reflashed stock firmware, nothing helps. It still reboots (sometimes it almost gets booted completely, other times it reboots after 2 seconds.
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
EclipseX said:
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
Click to expand...
Click to collapse
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
HXOY said:
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
Click to expand...
Click to collapse
EclipseX said:
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
Click to expand...
Click to collapse
Spoke too soon, it's started rebooting itself again.
Same problems here since 2 days. I was on original 5.1.1 software... Very strange all those people with the same problems
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Davids said:
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Click to expand...
Click to collapse
Still having the same issue around the same time everyone else started experiencing it.
I also was rooted and had xposed installed on 4.4.4 before the issue started happening.
Try the solution provided here & report back..
http://forum.xda-developers.com/note-4/help/note-4-sm-n910f-freeze-restart-issue-t3439111
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.
Hi everyone
I own a galaxy note 4 n910g running 5.0.1 rooted and have installed TWRP
I have pretty much learned about rooting and everything i know from youtube and various other how to do posts
I have been facing a peculiar problem
I had over heating issues and i found that indexservice was the culprit and disabled it...did not have the issue again
I had emmc read failed error again and again - i disabled the facebook app - i did not receive the error again - i do not know how to explain that, but i feel that is an observation that i made
So now the real issue
I am unable to go into recovery mode.
If i restart the mobile the mobile behaves as if it is hard bricked- Literally no response at all
I keep pressing all the hard keys in different combinations, but nothing seems to work at all
Now Here is the interesting fact
I remove the battery for bout six hours and try restarting it - it works
But if i switch off my mobile or try to go into recovery mode - my phone just becomes a brick for about 8- 12 hours
and i have to go through the tedious process of waiting
i m really stuck here -
i am unable to go into recovery mode to flash my rom
Neither am i able to restart my phone - so i have a charger in pocket always worrying when my phone would go poof
i am sick of this
i just want to flash my rom to the stock android and be happy with it
I have been reading a lot of ways to unbrick my mobile - i am unable to find it
This has been troubling me for atleast 20 days
i really hope if someone would be kind enough to put me out of my misery
can someone help me find what is the problem with my phone
and how to fix it
Thanks guys for taking the time to read this
same here
harishjkhv said:
Hi everyone
I own a galaxy note 4 n910g running 5.0.1 rooted and have installed TWRP
I have pretty much learned about rooting and everything i know from youtube and various other how to do posts
I have been facing a peculiar problem
I had over heating issues and i found that indexservice was the culprit and disabled it...did not have the issue again
I had emmc read failed error again and again - i disabled the facebook app - i did not receive the error again - i do not know how to explain that, but i feel that is an observation that i made
So now the real issue
I am unable to go into recovery mode.
If i restart the mobile the mobile behaves as if it is hard bricked- Literally no response at all
I keep pressing all the hard keys in different combinations, but nothing seems to work at all
Now Here is the interesting fact
I remove the battery for bout six hours and try restarting it - it works
But if i switch off my mobile or try to go into recovery mode - my phone just becomes a brick for about 8- 12 hours
and i have to go through the tedious process of waiting
i m really stuck here -
i am unable to go into recovery mode to flash my rom
Neither am i able to restart my phone - so i have a charger in pocket always worrying when my phone would go poof
i am sick of this
i just want to flash my rom to the stock android and be happy with it
I have been reading a lot of ways to unbrick my mobile - i am unable to find it
This has been troubling me for atleast 20 days
i really hope if someone would be kind enough to put me out of my misery
can someone help me find what is the problem with my phone
and how to fix it
Thanks guys for taking the time to read this
Click to expand...
Click to collapse
I have an exactly same problem with my SM-N910G..
And the fact is System partition detected, recovery partition detected, boot partition detected, but All about Data or Internal Storage were UNDETECTED...
Really, both of us need some help.. :crying:
Entering Recovery mode bricks phone for 8 hours? Feeling sorry for you guys. But i don't understand why phone needs 6 hours after battery is removed to come back to sense and work? Anyway, have you tried accessing the download mode, If yes just download a stock rom and flash it with odin.
scorpienez said:
Entering Recovery mode bricks phone for 8 hours? Feeling sorry for you guys. But i don't understand why phone needs 6 hours after battery is removed to come back to sense and work? Anyway, have you tried accessing the download mode, If yes just download a stock rom and flash it with odin.
Click to expand...
Click to collapse
Okay, i'll try that STOCK..
Have you any suggestion whether i should "repartition" it or not??
As my internal storage and data partition weren't detected (unreadable)
wawa9292 said:
Okay, i'll try that STOCK..
Have you any suggestion whether i should "repartition" it or not??
As my internal storage and data partition weren't detected (unreadable)
Click to expand...
Click to collapse
Give a try without repartitioning. Good luck.
I have tried flashing with stock...
Nothing seems to work...
It doesnt go into download mode
It doesnt go into recovery mode
i know i cant seem to explain whats the issue with my phone
The samsung service centre people are also baffled as to what to do
ill keep u updated if there is any
harishjkhv said:
I have tried flashing with stock...
Nothing seems to work...
It doesnt go into download mode
It doesnt go into recovery mode
i know i cant seem to explain whats the issue with my phone
The samsung service centre people are also baffled as to what to do
ill keep u updated if there is any
Click to expand...
Click to collapse
Hi harishjkhv,
If you are able to reboot after 6 hours by removing the battery, then try to reboot into download mode by using any super user app.
Then try to flash the stock firmware using Odin.
harishjkhv said:
I have tried flashing with stock...
Nothing seems to work...
It doesnt go into download mode
It doesnt go into recovery mode
i know i cant seem to explain whats the issue with my phone
The samsung service centre people are also baffled as to what to do
ill keep u updated if there is any
Click to expand...
Click to collapse
I've try flashing stock MM ROM from samfirmware with repartition checked..
But before i do that, i set my phone off while battery pulled out of the phone and charged separately using universal dock charger for 3 days..
My phone successfully boot and even i use for daily gaming like before, but the problem still remains..
Sometimes my phone got freeze (ended up with SOD), and when i pulled the battery off and on again, i failed to turn my phone on..
It have to wait for at least an hour without a battery..
And sometimes it says "ddi : mmc read failed" , no boot..
EDIT : oh yeah i forgot one thing, someone on the other forum encountering the same problem and suspect the power IC or mmc itself as the culprit..
And i myself think maybe because of overheating (on me is for games) those component became improperly attached to the curcuit board,and as the result is this hardbrick issues.. Will try some experiment..
I'll post here the result..
Its a software issue. I had the exact same issue with my T-Mobile version SM-N910T. I was able to resolve it by using ODIN to install the stock EPE3 along with the modem of COD6. After the phone restarted I placed the phone in download mode again and from there went on ODIN to install the EPE3 modem. After the phone restarts it should boot straight to the home screen.
Thanks guys. ..
Tried a lot of things
Nothing seemed to work...
I gave my phone to the service centre and they replaced my mother board
Cost me a lot. ..but still note 4 is worth it
Thank you guys for taking the time to help me and for your inputs
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
NYiCoN said:
Its a software issue. I had the exact same issue with my T-Mobile version SM-N910T. I was able to resolve it by using ODIN to install the stock EPE3 along with the modem of COD6. After the phone restarted I placed the phone in download mode again and from there went on ODIN to install the EPE3 modem. After the phone restarts it should boot straight to the home screen.
Click to expand...
Click to collapse
Already tried this one too, but no luck..
harishjkhv said:
Thanks guys. ..
Tried a lot of things
Nothing seemed to work...
I gave my phone to the service centre and they replaced my mother board
Cost me a lot. ..but still note 4 is worth it
Thank you guys for taking the time to help me and for your inputs
Click to expand...
Click to collapse
Do by a lot experiments, I've got some result that the Chips is already in the verge of death..
So replacing motherboard is the only solution for now, if someone having a same problem..
But, I hope no one encountering this problem anymore..