Database Users

Sam issue than others, different behavior HELP please!

Hey guys, i received a Samsung Focus i917 rev 1.3 from a guy who wanted to put that phone back to factory state. Im dont have a lot of experience on windows phones other than the HTC versions. Anyway, i performed a factory reset on the phone but the data didnt deleted at all. Now, i understand as far as i know that those phones need the SD card in order to work fine. That phone didnt have one, but it was working though. Thing is i decided to flash it with stock ATTJK2 and when i flashed it everything went fine. But the phone now stays on the Samsung logo for some minutes and reboots. When i say this case is different is because i can get to download mode as many times as i want, i can perform factory reset using hardware buttons and everything. In fact, i even installed MAGLDR and a custom rom trying to solve this but even though everything went well phone is still stuck on that logo. So my question is, should i insert a working SD for that phone and then flash it? Is it worth the try? Or is this phone just a brick? Cus my guess unbricking it wont solve it since the phone can reach download mode.... Help please and thanks for your help as always

enelyam said:
Hey guys, i received a Samsung Focus i917 rev 1.3 from a guy who wanted to put that phone back to factory state. Im dont have a lot of experience on windows phones other than the HTC versions. Anyway, i performed a factory reset on the phone but the data didnt deleted at all. Now, i understand as far as i know that those phones need the SD card in order to work fine. That phone didnt have one, but it was working though. Thing is i decided to flash it with stock ATTJK2 and when i flashed it everything went fine. But the phone now stays on the Samsung logo for some minutes and reboots. When i say this case is different is because i can get to download mode as many times as i want, i can perform factory reset using hardware buttons and everything. In fact, i even installed MAGLDR and a custom rom trying to solve this but even though everything went well phone is still stuck on that logo. So my question is, should i insert a working SD for that phone and then flash it? Is it worth the try? Or is this phone just a brick? Cus my guess unbricking it wont solve it since the phone can reach download mode.... Help please and thanks for your help as always
Click to expand...
Click to collapse
You can definitely try inserting a SD card and see. I'd say it's definitely worth trying. It would be best to match the original SD card it had, if possible. But even so, remember it's not guaranteed it will work.
If you'd search the forum for "stuck in loop" or "stuck at samsung logo" you'd see it's not a rare problem, unfortunately.

I have same problem with two different phones, the one started with be stuck in the loop. No matter what I have tried it will not break the loop, everything flashes fine but never boots. Second one started out working, but factory default wouldn't completely clear data. Very odd...

Well, seems like these phones are not worth a penny then. Its incredible that something like that could happen to a smartphone, So many things that go wrong with them, Im going to put them in the no no list togheter with the Razr. Worst phones to deal with... And yes ive seen its very common to find this issue. Which is why i think theyre worthless

enelyam said:
Well, seems like these phones are not worth a penny then. Its incredible that something like that could happen to a smartphone, So many things that go wrong with them, Im going to put them in the no no list togheter with the Razr. Worst phones to deal with... And yes ive seen its very common to find this issue. Which is why i think theyre worthless
Click to expand...
Click to collapse
I'd say that is your experience and your perspective. Normally, you are NOT supposed to flash custom ROMs and you have been warned that if you do it you RISK bricking your phone. This is a new platform and the process of flashing is not yet 100% understood.
I've warned folks several times about flashing MAGLDR, it seems that only *some* phones have this "stuck" issue and in 99% cases they are related to flashing custom roms. To add more, no one has a fix (not even the guru's), which tells me the issue is most likely unfixable by software (much like an old bios reflash, might require taking out a chip). It might be a later batch of phones that use a specific chip, it might be something else. Point is you're flashing something on your own risk. And saying the phones aren't worth a penny just because you don't want to accept the risk of doing something potentially dangerous is a bit stretchy. And that's my perspective. To add on that, all phones should be looked for the capabilities and what they do, not just for modding. Focus has a replacement for the custom roms, you can achieve the same by installing packages yourself, without unnecessary risks.

Well, im sorry if something was misunderstood. I didnt mean to hurt feelings in here M8. But the thruth is that the phone was completely stock, i just wanted to delete the old data. So decided to flash it with official ATT firmware, it wasnt custom firmware. But since the phone didnt wanted to delete the data after factory reset(which for starters its odd) i tried flashing it and it flashed perfectly according to the flashing software. But it was stock Att, and the phone got stuck in samsung logo after the flash. Never made it further, i mean its not an unusual issue around here so thats why i said that. After that happened is when i tried to install MAGLDR, which installed perfectly also. But when i tried to flash a rom the phone just did the same, stuck in samsing logo also. In fact, i can still flash whatever i want on it, it goes to download mode perfectly, but no matter what i flash on it, it will stay on the samsung logo after that... Anyway, my bad on saying that those phones are not worth it. There maybe more people willing to have a phone which they wont know if it will boot when they turn it off, or maybe not delete their data when they wan to factory reset the phone. Im not one of those thats all. But i do respect your work dont get me wrong, its just that some odd situations like this makes people think twice when buying a phone.

Right mate, I get your point. No harm
If it makes any difference, happened to my wife's phone during normal Zune update, got the logo-loop. Was fixed by reflashing stock rom. Painful, but it worked. In your case it seems something was wrong with the flash, not being able to delete data after factory reset is indeed at least weird. Sorry you had a bad experience, I guess some of those happen every now and then...

[Q] Galaxy S4 restarts every 10 minutes

Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.

sounds like a voltage prob....or mem prob... id redownload a new rom..wipe wipe wipe..reinstall and that should fix it
Sent from my SPH-L720 using xda app-developers app

Insufficient voltage at idle was my first thought too, but if you haven't undervolted (since you aren't even rooted), that seems less likely. If I were you, I'd root the phone so I could do more to figure things out. Maybe try bumping up the voltage a little on the lower clock speeds.

Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Edit: did you buy this phone new or used? If you bought it used, more than likely somebody ruined it for you. And more than likely, you can fix it. If this was a new device, more than likely it will be a warranty issue. That's why you shouldn't do anything to void the warranty.

If you're going to use odin for anything, just make sure you follow someone's directions step by step. Otherwise very bad things can happen.

im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!

I'll look into Odin before I root. The phone was also purchased new. I spent most of today monkeying around with different settings to see if I could trigger the issue as well. As it turns out, the phone will only restart at idle if it's plugged into the charger, or the wifi is on. If wifi is off and it's not plugged in it's fine. I am also using the stock Samsung charger that came with the phone. Again though, if I'm actively using the phone it doesn't happen (charging or connected to wifi). I did turn the phone off earlier to charge it but would keep freezing at the sprint logo upon boot up. I thought it was bricked for a second... I wiped the cache (didn't do a factory reset) and that fixed it, but now I have that stupid issue where videos won't play on wifi, only on 4G or 3G. It's an issue I thought I had solved.
Le sigh. This is frustrating. The Odin option is looking to be my best bet it seems.

Tizamarou said:
im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!
Click to expand...
Click to collapse
Since you are running a custom source-built ROM, first thing to do would be to ODIN a stock ROM. If the problems go away, you have your answer. If not, this would likely be a warranty issue. Of course you tripped KNOX most likely already.

sputnik767 said:
Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Click to expand...
Click to collapse
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?

Dfeeds said:
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?
Click to expand...
Click to collapse
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.

rebooting
i had this problem once and it was related to a corrupt file on my sdcard believe it or not. there are Defraggers out there for your android file system and internal SD card but your Ext sc you would have to do on your PC. it worked for me. the one i used is called CLEAN i got it off amazon app store.
cyberweasal
Dfeeds said:
Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.
Click to expand...
Click to collapse

sputnik767 said:
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.
Click to expand...
Click to collapse
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.

Dfeeds said:
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.
Click to expand...
Click to collapse
Great, I am glad it worked out, and hopefully your problem is resolved. I doubt that your old battery failed due to a bad partition, and I have to wonder how your partition got messed up in the first place, but that's just a curiosity and is irrelevant in the grand scheme of things. Just remember that if you decide to root, cf_autoroot works but will trip the KNOX bootloader and potentially void your warranty.

Phone rebooting randomly

Hi everyone, I'm new to the forum with an account but before today I've always read the forum without an account.
About 1 month ago, I rooted my SM-N9005 (it was GNG1 with Italian Vodafone ROM) then installed Safestrap and then I installed a Custom ROM (Galaxy S5 by IKINDER_BUENO). With the custom rom, the phone had no problems except the initial ones (apps started auto-closing randomly), but after 2 days of use the problem flew away autonomously.
Last wednesday I removed Safestrap and the custom rom flashing the phone with the original nobrand rom (ITV-GNG1), after that my phone started to do the weirdest things (auto-closing apps, very excessive battery drain ecc.), then this morning I turned off the phone due to school things, when I rebooted it hadn't any anomaly, but after 30/40 mins (no use, just in the pocket) it auto-rebooted so I thought that maybe the system crashed or maybe something similar happened, but after it booted correctly, after only 5 min it auto-rebooted 3 times in a row without any user interaction (reboot->boot->30sec ----> reboot->boot->30sec ----> reboot->boot->30sec ----> reboot->boot), it made me worry about that, so as soon as i got home I reflashed it with the original Vodafone ROM, but nothing changed.
Now, my phone reboots randomly and also the proximity sensor doesn't work (probably is a ROM issue, I'm downloading another version of the Vodafone ROM because the one I've downloaded has German Apps, now I'm downloading it with Italian apps (I hope so).
Could someone help me resolving this issue?
I asked also Vodafone support if they could change my phone (they repair only but in case that the phone came back 3 times from SAMSUNG assistance without resolving the problem, they will change it).
Ah, my KNOX Warranty Void is 0x1 due to the root.
Sorry if I've done grammatical errors, I'm Italian.

Install TWRP, flash a custom ROM then wipe data, cache (not internal SD) reboot into the custom ROM, set it up and see what happens after 24 hours. It's possible the device just needs cleaned. You could reflash stock again and do a complete wipe but since you've tripped KNOX to 0x1 already may as well wipe manually via recovery.
Sent from my Spectrum ZX +2

radicalisto said:
Install TWRP, flash a custom ROM then wipe data, cache (not internal SD) reboot into the custom ROM, set it up and see what happens after 24 hours. It's possible the device just needs cleaned. You could reflash stock again and do a complete wipe but since you've tripped KNOX to 0x1 already may as well wipe manually via recovery.
Sent from my Spectrum ZX +2
Click to expand...
Click to collapse
Hi man, thank u for your very fast answer, so schematizing the process:
1) Install TWRP through Recovery;
2) Flash a Custom ROM (I will use again S5 Port by IKINDER_BUENO);
3) Wipe data and cache from TWRP, right?
4) Use custom ROM and test if the issue is resolved;
Is it right? Correct me if I'm wrong, I don't want to trip anymore my phone.
In case the issue is solved, and I want to came back to the original Recovery and ROM, how should I do?
Thank u again.

Yip that's correct but install TWRP recovery through ODIN. Once you have tripped KNOX you cannot trip it anymore.
In order to go back to complete stock afterwards, find your firmware for your country and model number. The. Flash via ODIN
Sent from my Spectrum ZX +2

radicalisto said:
Yip that's correct but install TWRP recovery through ODIN. Once you have tripped KNOX you cannot trip it anymore.
In order to go back to complete stock afterwards, find your firmware for your country and model number. The. Flash via ODIN
Sent from my Spectrum ZX +2
Click to expand...
Click to collapse
Thank you for the very useful infos, tomorrow I'll do that.

Hey man, I've noticed something very unusual... Every time the phone autoreboots battery stats resets, it's very strange.
Have u ever had/read a problem like this?

radicalisto said:
Yip that's correct but install TWRP recovery through ODIN. Once you have tripped KNOX you cannot trip it anymore.
In order to go back to complete stock afterwards, find your firmware for your country and model number. The. Flash via ODIN
Sent from my Spectrum ZX +2
Click to expand...
Click to collapse
Hey man, I've tested your method and some issues seems to be resolved (auto-reboot), but other issues are arrived (any sensor isnt working, no one not just the proximity one and sometimes the phone shuts off and wont turn on, and I've to remove and reinsert battery and then then the phone goes).
Waiting your instructions.

facechico said:
Hey man, I've tested your method and some issues seems to be resolved (auto-reboot), but other issues are arrived (any sensor isnt working, no one not just the proximity one and sometimes the phone shuts off and wont turn on, and I've to remove and reinsert battery and then then the phone goes).
Waiting your instructions.
Click to expand...
Click to collapse
Hmm, there was an issue where one ROM killed the sensors on a Note 3, but that was last year.. There is a post somewhere about how to fix them. Can't remember where it was. But, it's possible you may have faulty sensors :crying: . I'll have a look in the morning (just finished work now) -and try and find out where the post is and what the fix was.

radicalisto said:
Hmm, there was an issue where one ROM killed the sensors on a Note 3, but that was last year.. There is a post somewhere about how to fix them. Can't remember where it was. But, it's possible you may have faulty sensors :crying: . I'll have a look in the morning (just finished work now) -and try and find out where the post is and what the fix was.
Click to expand...
Click to collapse
Thank you for your interest, I can prove that my sensor aren't fault (I hope so, but 2 weeks ago they were working!)
What about the battery problem?
UPDATE:
Hi again, this morning phone started rebooting autonomously, during 6 hours it rebooted somewhat like 3 o 4 times. Sensors are still dead, none working and as I anticipated yesterday, phone sometimes turns off and wont turn on unless I remove battery.
Now I'm installing Cyanogenmod, and try what happens.

I've also searched for the post of the note 3 with that dead sensors, but I haven't found it.

N910F problems - emmc read fail/ flashing stock no longer boots the phone.

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

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?