So I've been running the TEKHD 5.1 stuff for about a month now. I thought I had my model correct, it reads sm-n910t. Recently though I've had very wonky behavior. I frequently get system hanging when I turn the screen on and use apps. Yesterday, I pulled my phone from my pocket and it was at a screen similar to Odin download and was giving an error message that it couldn't read the system partition. After freaking the **** out for an hour, Odin flashing kept failing. I finally got it to take and then got installed again, booted up, and the freezing is still there, while searching through about phone, it reads sm-n910t3 so my question is, am I rocking the t3 or the t? Also could roms/kernels built for a different model give me those issues
Sent from my SM-N910T3 using Tapatalk
Install samsung phoneinfo app from playstore maybe it can help you?
Related
Service Provider - Sprint
Model no. SPH-L720
Just picked up my Galaxy S4 from Bestbuy with stock 'Build no.' (MDC). As soon as i started using my phone, sprint pushed a 'over the air' (OTA) update. Had it downloaded, installed, and rebooted.
As I started using the phone more by clicking on the stock app. the phone starts to reboot itself. Long story short. I thought i'll fix it by rooting the phone. Same issue and reboot itself more, kept crashing.
I now unrooted the phone using Odin-OC for FULL ERASE since i have nothing on the phone to begin with. I'm guessing this is a hardware issue. I'm wondering if anyone out there that is having the same issue.
Thanks.
If the Galaxy s4 is faulty (hardware issue), the phone vibrate twice before samsung logo appear.
so from what you are saying as soon as you booted you got the MDL update correct? what "stock app" are you clicking on that is causing the phone to reboot? random reboots are commonly linked to specific software malfunctions most of which can be corrected easily. not saying you didnt get the bad one from the batch but if you provide more info we should be able to work out the kinks if its software related.
l3et9jwh2000 said:
Service Provider - Sprint
Model no. SPH-L720
Just picked up my Galaxy S4 from Bestbuy with stock 'Build no.' (MDC). As soon as i started using my phone, sprint pushed a 'over the air' (OTA) update. Had it downloaded, installed, and rebooted.
As I started using the phone more by clicking on the stock app. the phone starts to reboot itself. Long story short. I thought i'll fix it by rooting the phone. Same issue and reboot itself more, kept crashing.
I now unrooted the phone using Odin-OC for FULL ERASE since i have nothing on the phone to begin with. I'm guessing this is a hardware issue. I'm wondering if anyone out there that is having the same issue.
Thanks.
Click to expand...
Click to collapse
i also have this problem but i have no solution, samsung told me either i need a new battery or get my phone replaced pronto
xxaddictedxx said:
so from what you are saying as soon as you booted you got the MDL update correct? what "stock app" are you clicking on that is causing the phone to reboot? random reboots are commonly linked to specific software malfunctions most of which can be corrected easily. not saying you didnt get the bad one from the batch but if you provide more info we should be able to work out the kinks if its software related.
Click to expand...
Click to collapse
Sorry for the late respond, my phone will automatically reboot itself. While in any apps, game app and while using the camera to take pictures; my phone reboot itself. Once it is on, the phone will not respond (freezes) and reboot itself again and again. This usually stop by the forth or fifth time of continues self booting.
l3et9jwh2000 said:
Sorry for the late respond, my phone will automatically reboot itself. While in any apps, game app and while using the camera to take pictures; my phone reboot itself. Once it is on, the phone will not respond (freezes) and reboot itself again and again. This usually stop by the forth or fifth time of continues self booting.
Click to expand...
Click to collapse
i know you said that you are no longer rooted but have you tried rerooting and flashing a differant rom?
Typically random reboots are kernel related. When rooted did you try flashing any custom kernels, mods, try OC/UV, or anything along those lines?
Otherwise, sounds like a faulty device, maybe bad memory.
Same problem
A week after getting the galaxy s4 my phone started rebooting typically 2 times a day sometimes none at all, contacted sprint they said to come in and there fix was a factory reset lol, so decided to root and install triforce rom with kt kernel , still getting random reboots, im playing with the kt kernal settings hoping to find a sweet spot
Honestly... I think it's the MF9 update. It hasn't happened to me, but I've seen it for plenty of people. Everyone here running build no. MF9??
I am now, but my reboots started right when the phone came out
Sent from my SPH-L720
I don't even know what I did, but my phone is basically useless now. I tried to install the PAC ROM over the summer but I got stuck ina boot loop and had to emergency reset flash back to what I thought was stock firmware using RSD Lite. I don't know if it was actually stock because when I booted up my phone, everything seemed to be in order; but then I found that the play store was not working. Whenever I opened the play store, I got the message "Unfortunately, Google Play Store has stopped." I tried a bunch of methods from here from people who had similar problems, but nothing worked so I decided it must have been the firmware that I used. So then I went and took a 4.04 firmware from the same place I got the first one and went to flash it. The flash on RSD Lite did not work. I tried a bunch of different firmwares and none of them seemed to work. And now, my phone has gotten even worse. Recently, I got a message saying that my storage space was getting low, when I could see in my settings app that it wasn't. And then, this morning, I got a message saying that storage space is too low, you will not be able to receive messages. Then about fifteen minutes later my wireless service dropped and I can't get any service now. I don't think that it is a carrier problem because I have been in the same place as I was yesterday and I was getting full 4G bars the whole time. Anybody know what I can do? I am unrooted an my bootloader is unlocked.
Have you tried Matt's utility? Option 1 I believe found here http://forum.xda-developers.com/showthread.php?t=2249773
Sent from my XT907 using xda app-developers app
indeed, mikes utility should get you back up and fully functional
Also, factory reset will help. Sounds like lots of stuff is messed up...
Sent from my XT907 using Tapatalk
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.
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
Hello people of the world,
after reading a lot of posts here I still can't fix my phone's issues, so I need to post. Bear with me...
I have an N910F which was entirely stock and functioning without problems. Two days ago I accepted the official update. After that, the phone regularly lost connection to the mobile net, froze, and restarted. It would work for a short while until it froze and restarted again and again. When I tried to use the camera, the live picture was completely distorted. The phone crashed and has then gone into a bootloop.
I pulled the battery, did a recovery start and wiped the cache. No difference. Factory recovery next, no difference.
I have since tried several stock and custom firmwares, always taking care to follow instructions and use the correct bootloaders, modems, etc. TWRP is working.
When I flash a stock firmware, it will go into a bootloop. With any custom ROM, it will crash during startup (logo) and switch off.
Any help would be greatly appreciated!
Protect the eMMC?
So, after more reading I began to suspect that the eMMC had moved on to the valhalla of electronics. Sent my phone to service where my suspicion was confirmed. Luckily, they were able to replace the chip without having to put in a new board.
Is there any way to prevent this kind of failure again, or at least make it less likely?
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
nicholes said:
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
Click to expand...
Click to collapse
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
tullian said:
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
Click to expand...
Click to collapse
installing power wakelock and setting up on partial wake lock is enough.if you get trouble in starting your phone remove its battery and put your phone in refrigerator for five min.and try to start your phone.this problem also related and happens after the latest update