[Completed] Can somebody help me fix my Note 4 SM-N910T that keeps getting stuck in a boot loop? - XDA Assist

So i purchased a Note 4 SM-N910T about a year ago. It worked fine but last month shortly after the 5.1.1 update I did it started randomly restarting for no reason. First i taught it was Snapchat because I red somewhere that there are camera problems, so I stopped using it. But it kept restarting even after that. From then I have made a factory and a master reset, rooted the phone and even installed CM 12. No mater what i do it keeps on restarting. The only way to get it out of the boot loop is to connect it to a charger that is not a fast charger. Then it starts charging and works normally and you can do everything normally. After you remove it from the charger it works as long as you do not use it. When you start using it and want to do something with it it starts restarting again. I hope somebody can help me fix this issue. My last resort is to wait 3 hours for the stupid free 5.0.1 official firmware and flash it using the TWRP Recovery or Odin. If that does not work I would have t give it to a service.
Merry Christmas!
Looking forward to your answer!

Hello,
Welcome to XDA.
As long as it isn't a hardware issue then flashing the stock firmware via Odin should fix it.
You can also try using Samsung Kies on it before you resort to Odin. There are various things Kies can do to correct little issues and update devices, even emergency recovery. Its not always effective but if it works it will keep your update. If it doesn't work then flash via Odin.
You can post your questions in the forum linked below.
http://forum.xda-developers.com/note-4-tmobile/help
The experts there may be able to help
Register an XDA account to post and reply in the forums.

Related

[Q] Galaxy S2 Soft Bricked after root....

Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.

[Q] S3 stuck at FIrmware upgrade encountered an issue

So I have had my S3 rooted for a long while. But the past few weeks it's been running a bit slower. This week it started randomly turning off. I thought it was my battery at first. But then when I tried to turn it back on it got stuck at the Galaxy s3 screen and would not get into the OS.
I tried to get into recovery, it froze on the splash screen. I made sure both were actually frozen by leaving it sitting there for 30 min to an hour.
Tried to flash using this thread: http://forum.xda-developers.com/showthread.php?t=1974114
It kept just sitting at writing NAND.
Now my phone says "Firmare Upgrade encountered an issue, please select recovery mode in kies and try again"
Kies will not connect my device. It sees it but will not complete the connection. I tried using the model and IMEI number to upgrade firmware but it still would not connect to do that.
More searching lead me to this: http://forum.xda-developers.com/showthread.php?t=2581166&page=11
But I can't get into OS or recovery so I don't think this would work.
Any suggestions on what I can do from here? I only really need the phone to work for a few more months. My old Droid incredible just doesn't cut it at this point.
Sorry to bump, but nobody has anything for this? I haven't really found any other options.
Your bootloader is fine so that thread won't help you. What was the last version of touch wiz that was on your phone before you ran into problems?

[Completed] Nexus 4 random shut off...please help

Hey Everyone,
Okay so about a month ago I was running Stock 4.4.4 with no root. The problems started. My phone's screen started blacking out and shutting down when it hit around 50-60%. Then I would have to turn it back on where I realize that I cant connect to my phone network and I have to re-enter my WiFi credintils My phone would keep shutting down unless I connect to a power source.
Then I decided I try to change the software so I install LiquidSmooth 5.0.2 with HellsCore Kernal. The problem was still occurring and everyday it was getting worse. Now I cant let my phone get under 85% or it will never turn off. If it does get under 85 then it will go in a bootloop or wont turn on without a power source. One odd thing is that it does not shut off/blackout when I go into my recovery mode.
Help would be appreciated, Thank you very much
Hi, thank you for using XDA Assist. I'd try flashing the factory image in fastboot. See this, http://forum.xda-developers.com/nexus-4/general/google-nexus-4-sticky-roll-t2183555. If you still have a problem it's most likely a hardware issue. Don't forget to register on XDA to post questions.
Thread closed.

[Completed] LG G3 Stuck in bootloop after Flashing Stock Rom

I flashed my LG G3 Because i felt that the sound was not working anymore and that it can be a software issue which it was a hard ware issue ( loud speaker wasnt connected because of screw) Anyways preformed the stock FW Flash following the guide that highonandroid provided to go completely back to a stock rom. After flashing i restart phone and the boot takes forever until it finally hangs on the tmobile screen. there was a point where i left it over night to see if it will turn on but it still hung for a good 8 hours. Ive done everything i can which can be that i preformed atleast hundreds of hard resets but nothing is working.. there was a point where i did manage to turn it on then i tried updating to lolipop and when it reboots the bootloop is back.. Please help!
Pluesik said:
I flashed my LG G3 Because i felt that the sound was not working anymore and that it can be a software issue which it was a hard ware issue ( loud speaker wasnt connected because of screw) Anyways preformed the stock FW Flash following the guide that highonandroid provided to go completely back to a stock rom. After flashing i restart phone and the boot takes forever until it finally hangs on the tmobile screen. there was a point where i left it over night to see if it will turn on but it still hung for a good 8 hours. Ive done everything i can which can be that i preformed atleast hundreds of hard resets but nothing is working.. there was a point where i did manage to turn it on then i tried updating to lolipop and when it reboots the bootloop is back.. Please help!
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble. Fortunately there is an XDA area dedicated to the LG G3 at http://forum.xda-developers.com/tmobile-lg-g3 which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/tmobile-lg-g3/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.

[Completed] Bricked Galaxy Trend Plus GT-S7580 issue

Hey guys, sorry if this is in the wrong place, I just want some help as I'm almost out of ideas.
So, the thing is that I have a rooted Galaxy Trend Plus GT-S7580 that was working perfectly up until 2 days ago, when it crashed while watching an ad in a game, and I had to take out the battery as the whole phone was frozen for a long time. After restarting the phone, I noticed a weird behaviour that no apps started up, no matter which one I tapped, and I could barely get into settings and so on either.
I tried restarting afterwards, but the phone couldn't even turn off, and just stayed on a grey screen, while both hardware buttons were light up. This state remained indefinitely, while the phone randomly vibrated at times for a second. I restarted and pulled the battery multiple times, but the apps were still not working and the same issue remained.
What I did afterwards was to try to factory reset and reset cache the phone from recovery mode, which was cwm recovery. Then as the phone was about to reboot, it got stuck on the Samsung Logo with the phone name, and couldn't move on from it. I tried reflashing ROMs and recovery modes since then, but it always stays on the boot screen. I can't even enter recovery mode anymore either, as it just keeps being stuck on the boot logo. I can enter download mode though, and Odin knows my phone is there, but for examples Samsung Kies can't connect to it.
I thought maybe flashing a ROM in Odin along with the additional files such as BL, AP, CP and CSC and PIT could help, but I'm not sure if I should do that yet, especially because I couldn't find all of those correct files for my region so far. So I'm asking for help here. Thank you if you have any useful insight to my issue!
Additional information: I successfully rooted the phone according to this guide a year ago: http://forum.xda-developers.com/showthread.php?t=2621087
littlezoe said:
Hey guys, sorry if this is in the wrong place, I just want some help as I'm almost out of ideas.
So, the thing is that I have a rooted Galaxy Trend Plus GT-S7580 that was working perfectly up until 2 days ago, when it crashed while watching an ad in a game, and I had to take out the battery as the whole phone was frozen for a long time. After restarting the phone, I noticed a weird behaviour that no apps started up, no matter which one I tapped, and I could barely get into settings and so on either.
I tried restarting afterwards, but the phone couldn't even turn off, and just stayed on a grey screen, while both hardware buttons were light up. This state remained indefinitely, while the phone randomly vibrated at times for a second. I restarted and pulled the battery multiple times, but the apps were still not working and the same issue remained.
What I did afterwards was to try to factory reset and reset cache the phone from recovery mode, which was cwm recovery. Then as the phone was about to reboot, it got stuck on the Samsung Logo with the phone name, and couldn't move on from it. I tried reflashing ROMs and recovery modes since then, but it always stays on the boot screen. I can't even enter recovery mode anymore either, as it just keeps being stuck on the boot logo. I can enter download mode though, and Odin knows my phone is there, but for examples Samsung Kies can't connect to it.
I thought maybe flashing a ROM in Odin along with the additional files such as BL, AP, CP and CSC and PIT could help, but I'm not sure if I should do that yet, especially because I couldn't find all of those correct files for my region so far. So I'm asking for help here. Thank you if you have any useful insight to my issue!
Additional information: I successfully rooted the phone according to this guide a year ago: http://forum.xda-developers.com/showthread.php?t=2621087
Click to expand...
Click to collapse
Hi,
Thanks for using XDA Assist.
There's no dedicated forum for your device here in XDA. Try posting your query in Android Q&A,Help and Troubleshooting or in one of the noob friendly Q&A thread here->[Ask Any Question][Newbie Friendly] .Experts there may be able to help you
Good luck.

Categories

Resources