Database Users

Note 4 hard brick which resolves on its own

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..

So... I softbricked my A2017G! Any help?

Yeah. I was trying to unlock my bootloader using Controllerboy's guide, and I managed to install TWRP. I also managed to unlock my bootloader. When I tried to restore my phone using the backup I put on my computer and back to my A7, it won't boot - it's stuck on the "ZTE powered by android" boot screen.
I think that the problem is that when I was copying the backup from my phone to my computer it said "unspecified error" but still let me copy the files (the files and the sizes remained the same) so I just ignored it. Whoops!
So I tried to install CM13 in hope that it will somehow fix things, and unsurprisingly everything is still the same.
So. What do I do? I think that the problem was that I backed-up system and tried to restore system (probably).
Anyone got a solution? Or even a system restore that will cure my phone?
Any help will be greatly appreciated! Thanks in advance!

I managed to solve the problem myself by re-wiping dalvik and installing CM 13! Odd that it worked this time and not the other time I tried it, but at least it works

[SM-G531F] (problem) Rebooting phone after root.

Hi, I have a problem. It occurs after the root of the phone. I started rooting the phone by Odin and uploaded the rooted ROM and all with success. TWRP doesn't work for me (with SuperSu).
Okey, after flash ROM my phone normally rebooted. Everything was fine until I started updating my apps. Then, he started rebooting when I'm installing and uninstalling applications / games.This is annoying.
How do I solve this problem? Has anyone already had such a situation?
Please help!
Sorry for my English. I hope you've understood my problem.
Do you have any questions, please.....

Samsung Note 4 N910F is not stuck in bootloop, still doesn't really boot

Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!

Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.

Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?

Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.

eMMC failure, snapdragon models are susceptible to this.

Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.

Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.

KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?

Need help. Boot loop on J320P that was a friends.

Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped

Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?