Database Users

[Q] i9505 reboots during boot or 10 sec after startup.

Dear XDA,
My phone has this weird problem since Foxhound v1.7 and i cannot figure out what the problem is.
When my phone starts up, after a few seconds the s4 looses modem connection (cannot call/sms). In result, the phone just shuts off.
I cannot do anything with my phone since it just desides to shut off.
I've installed stock firmware from Djembeys thread, but it would not fix my problem. I've did a data/cache factory reset but the problem stays.
Also when i flash other ROMS the problem stays. the phone just shuts off after booting up.
Is there anything else i can try to solve this weird problem? i'd post it in the Foxhound thread but it gets loaded with other questions after which no one sees mine.
Thanks allot in advance

J-r0en said:
Dear XDA,
My phone has this weird problem since Foxhound v1.7 and i cannot figure out what the problem is.
When my phone starts up, after a few seconds the s4 looses modem connection (cannot call/sms). In result, the phone just shuts off.
I cannot do anything with my phone since it just desides to shut off.
I've installed stock firmware from Djembeys thread, but it would not fix my problem. I've did a data/cache factory reset but the problem stays.
Also when i flash other ROMS the problem stays. the phone just shuts off after booting up.
Is there anything else i can try to solve this weird problem? i'd post it in the Foxhound thread but it gets loaded with other questions after which no one sees mine.
Thanks allot in advance
Click to expand...
Click to collapse
Hi,
Try HERE
Basically, get completely back to stock.
If the problem persists,you may have hardware failure.

malybru said:
Hi,
Try HERE
Basically, get completely back to stock.
If the problem persists,you may have hardware failure.
Click to expand...
Click to collapse
Well i tried that today and it worked, i thought. after 1 hour it just went back to 'abnormal' and shut off the phone. And when restarted, shut down again after few seconds xD
Guess i have to reset the flash counter and go back to the shop?
Or is there something else i can try to do.

J-r0en said:
Well i tried that today and it worked, i thought. after 1 hour it just went back to 'abnormal' and shut off the phone. And when restarted, shut down again after few seconds xD
Guess i have to reset the flash counter and go back to the shop?
Or is there something else i can try to do.
Click to expand...
Click to collapse
Hi,
Yes, sorry to say, but it looks like a hardware problem.
Sent telepathically from my S4

[Q] i9505 Somtimes boot, sometimes doesn't.

I had an S4 in for LCD replacement, everything went fine. Possibly the EASIEST phone repair possible.
The phone was reassembled and worked fine, put it up for sale and updated etc. After a few days of it sitting there I went to turn it back on and it wouldn't boot, just hung at the Samsung logo and wouldn't boot recovery.
I left it and thought i'd sort it the next day and went to proceed to flash with Odin until the battery charge logo came on so I knew it was working and then I turned it on and it all worked fine.
It was working fine so I thought it was a one off so turned it off and it happened again. Now im constantly flashing via Odin to try and get anything out of it, sometimes it will boot up get past the Samsung logo then it will freeze.
I have read near enough every threat on the subject, I doubt I'll get an answer here but I'll keep this bumped everyday in hope there's somebody who knows what's going on.
Here's what I've tried
- Flashed latest rom via odin
- Flashed 4.4.2 via odin (supposed to fix this issue)
- Flashed PIT & latest rom via odin
- Flashed PIT & 4.4.2 via odin
I don't know what else to do

Check hardware.

GDReaper said:
Check hardware.
Click to expand...
Click to collapse
What hardware...?
I have looked at the logic board and can't find anything wrong with it.

Well, it can't be the software because you already tried a bunch. The only constant thing is the hardware. May be a semi-functional power button. I don't know.

GDReaper said:
Well, it can't be the software because you already tried a bunch. The only constant thing is the hardware. May be a semi-functional power button. I don't know.
Click to expand...
Click to collapse
All buttons work fine.
Doesn't look like eMMC is the issue because it's writing to the NAND, there's probably an IC with a bad solder joint which explains why it randomly boots sometimes, the only problem is I don't know which IC it is.

Reflowed U800 IC 140c and i9505 booted up no problems

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

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?

my S7 edge is hard bricked

I had BlackDiamond.N8.PIE.V2.0 over a year on my phone and it was working with no problem.
today I decided to update my phone, first updated the TWRP to the latest version "TWRP-3.4.0-0-hero2lte" updated without any problem,
then I downloaded BlackDiamond N8 Port V10.0, wiped everything (even internal storage), and installed the ROM,
it installed successfully, wiped the caches, reboot to the system, android loaded without any issue,
after loading into android, I added my google account, and I was testing the phone, after 10min of working with the phone,
while I was testing the camera app (it's was a little laggy) my phone freezes and after a couple of seconds, the screen went black! I thought it's gonna reboot, but nothing happened.
I tried to hard reset the phone by pressing "power+volume down+home key", but it didn't work, connecting to the charger is nothing happen, there is no LED light, my phone is completely dead
does anyone have any idea why this happened? installation and booting to android was completely fine, everything worked fine, and suddenly my phone freeze and hard bricked.
you know this is not the first time I'm installing custom ROM, I'm done it before and I've always been careful, never had any issue like this, but this time really I don't know what happened and to be honest, I really love my S7 Edge, I don't want to replace it.

aalireza439 said:
I had BlackDiamond.N8.PIE.V2.0 over a year on my phone and it was working with no problem.
today I decided to update my phone, first updated the TWRP to the latest version "TWRP-3.4.0-0-hero2lte" updated without any problem,
then I downloaded BlackDiamond N8 Port V10.0, wiped everything (even internal storage), and installed the ROM,
it installed successfully, wiped the caches, reboot to the system, android loaded without any issue,
after loading into android, I added my google account, and I was testing the phone, after 10min of working with the phone,
while I was testing the camera app (it's was a little laggy) my phone freezes and after a couple of seconds, the screen went black! I thought it's gonna reboot, but nothing happened.
I tried to hard reset the phone by pressing "power+volume down+home key", but it didn't work, connecting to the charger is nothing happen, there is no LED light, my phone is completely dead
does anyone have any idea why this happened? installation and booting to android was completely fine, everything worked fine, and suddenly my phone freeze and hard bricked.
you know this is not the first time I'm installing custom ROM, I'm done it before and I've always been careful, never had any issue like this, but this time really I don't know what happened and to be honest, I really love my S7 Edge, I don't want to replace it.
Click to expand...
Click to collapse
Possibly a hardware problem. You will have to take some technician for a more accurate analysis.

Dark Stranger said:
Possibly a hardware problem. You will have to take some technician for a more accurate analysis.
Click to expand...
Click to collapse
if it's hardware, why I didn't have any problem before updating the ROM? is it possible updating damaged the phone?

one more thing, I saw some people use a dongle called USB-JIG on dead Samsung phones, that enter phone to download mode and after that flashing with Odin.
do you think it's work on my phone?

aalireza439 said:
if it's hardware, why I didn't have any problem before updating the ROM? is it possible updating damaged the phone?
Click to expand...
Click to collapse
It can occur, despite being very difficult. I already corrupted the xperia bootloader I had, but it never happened on my samsung devices. I even have a s7 edege and I am changing his rom and I never had any problems. As I said, you should take the device to an assistance center to get an idea of what really happened. Perhaps it could be a hidden problem, which was only expressed by changing the rom, or it could give the same problem with the old rom. What I can say is that a simple exchange of rom, would hardly cause a hard brick in a device.
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
aalireza439 said:
one more thing, I saw some people use a dongle called USB-JIG on dead Samsung phones, that enter phone to download mode and after that flashing with Odin.
do you think it's work on my phone?
Click to expand...
Click to collapse
You can also try, because if your device is not completely dead, it can come back to life with this procedure. But I still recommend taking the device in for a technical assistance.

There are 3 cases in this:
1. If you flashed a corrupted/wrong bootloader in twrp/flashfire or anything that doesn't blocks a wrong flash like odin. Your phone is dead for good. Only a usb jig/repair box or a local mobile technician can fix that.
2. Your phone is bugged with black screen. Installing a custom rom can cause weird things. Sometimes hard stuck with screen off/black .. now you need to wait for battery draining itself completely and then plugging in charger and trying to get in download mode. If you could go in download mode then you can reflash through odin and it will be back to normal. Although sudden turn off and then complete deadness is often a hardware failure.
3. If phone after draining completely doesn't shows life when connected to charger and can't go in dl mode then its either hardware failure or bootloader problem like in no.1 point. You will need to take it to a mobile repairer or use a repair box/jig nevertheless.
Sent from my hero2lte using XDA Labs