Stuck in boot loop/and or freezes - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

I have had this start about 2 weeks ago. started bootlooping.....if and when it came back on it would just work BUT I wouldnt be able to use stock camera or shut it off or it goes into bootloop again
NOW today it started again so when it came back on I just updated it to 5 Lollipop....then got stuck on restart and freeze and now back into bootloop
I tried Odin but it doesnt do anything and then says failure
I AM SO STRESSED OVER THIS CAN SOMEONE PLEASE HELP ME
SPRINT NOTE 4 UNROOTED

nicolemiles said:
I have had this start about 2 weeks ago. started bootlooping.....if and when it came back on it would just work BUT I wouldnt be able to use stock camera or shut it off or it goes into bootloop again
NOW today it started again so when it came back on I just updated it to 5 Lollipop....then got stuck on restart and freeze and now back into bootloop
I tried Odin but it doesnt do anything and then says failure
I AM SO STRESSED OVER THIS CAN SOMEONE PLEASE HELP ME
SPRINT NOTE 4 UNROOTED
Click to expand...
Click to collapse
You could try factory resetting your phone and wiping all the cache and dalvik cache. One possibility why it's saying error on odin is because your cable dosen't work properly or you don't have the phone properly installed on your pc. Try installing the samsung mobile phone drivers.exe and see if it helps!
Sent from my SM-N910P using XDA Free mobile app

You could also take it into a Best Buy to the Samsung desk and have them fix it.

Related

[Q] please help have tried evrything phone stuck on boot screen

hi i just recently got my Samsung galaxy s3 i tried rooting it thru odin bbut it froze up i left it alone for like 30 minutes then got tired of waiting so i unplugged it then it told me i had an error and to go to kies i have tried that even tried downloading a stock rom and flashing it nothing works im on 8 counters currently i even tried to factory reset it bbut it is still frozen i have only had the thing for 4 days plz if anyone can help me would greatly be appreciated
Go Into recovery factory reset and try flashing a stock rooted file again. Don't unplug it this time let it finish.
Sent from my SAMSUNG-SGH-I747 using xda premium

(HELP) Possible soft brick

Okay here is the problem guys. I have my note three for three weeks now. Rooted it day one. But It seems with every phone I have addiction with flashing roms. I change around a lot. I have owned four devices this year. S4, note 3, nexus 4 and galaxy nexus. Rooted every device never had an issue that couldn't be fixed by flashing the stock tar via odin. The other day I flashed compulsion kernel and put me in a boot loop. So I did the natural thing and download the stock tar and flash via odin. First time was a bust. It said it was successful. Still put me in boot loop so I downloaded the stock tar from another location and tried again. Still no dice and still have boot loop. Tried flashing a custom rom after flashing the stock tar. Nothing still boot loop and I've also tried different recoveries and still nothing. I know its not hard bricked because I can still boot into recovery. I am actually a sales rep at a corporate tmobile store and did a warrarnty exchange and they are overnighting me another note three and I am going to send this one back. Little concerned as to having the rooted status on the device is going to go over. A couple times after I flashed the stock tar I got it to boot but then it would say "process system stopped responding wait or ok" then after clicked okay it reboots. I really hope there is someone out there with a solution.
HELP
This isnt your usual soft brick. If someone could please help I would appreciate it!!
Dude my phone out of nowhere bricklooped today like literally. I installed different roms no dice. 3 backups including the stock one and nothing still bootlooped I tried the brickloop fixer on jovys darthstalker v6 and I'm back up and running but if I reboot or turn off phone and reboot it goes into same bootloop he's a smart, brilliant dev I'm sure he can help me out as well as you
Sent from my SM-N900T using xda app-developers app

[Q] Help: Samsung i927 crashes on boot.

Hello.
First off all, my i've had this phone for about 4 months. I bought it and inmediately updated from 2.3 to 4.0.4 and then installed Cyanogenmod 4.3 and it worked just perfect. But, two days ago it started to crashing in a weird way so i had to remove the battery and put it on again for the phone to work. But now, the phone just won't start. It crashes it cyanogenmod logo and just stucks there for ever or simply re-starts and then again, freezes in cyanogenmod. It started a couple of times by just removing the battery and turned on again, but now it got worse. Now the just doesn't start never, just get stuck in the CM logo.
I triyed wipping /cache /system /data /dalvik everything but it did not worked. Next, i triyed installing stock 4.0.4 rom and the phone started (YAY!) but, after installing my apps and sync-ing my accounts i rebooted my phone and, then again, it crashed on the start up again. I've try a lot of things and no one seems to work. It just get stuck in the logo after SAMSUNG.
Help.​
Which apps did u install...any system tuner apps...
Sent from my GT-N7000 using Tapatalk
I did not install anything before the issue.
But, like two weeks ago i installed: Clean Master (Without root permissions) and Go launcher Theme.
I am being honest, i did not do anything for this to happen. Then again, i repeat to you my problem: My phones crashes in the logo after samsung. It started two days ago, crashing while using my phone. Then it started to crash in the booting. I wiped and nothing happened. I Installed Stock rom deoxed and it started but just lasted the first boot. Then, when i restarted the phone, it would crash in the booting again. Now, i flashed the PURE STOCK ROM 4.0.4 and it have not passed trought the "Think possible" logo
Try flashing the basic stock firmware from Samsung using Odin... Then re-root and check
Sent from my GT-N7000 using Tapatalk
try to remove battery and wait at least 4 minutes, and put back.
It helped on my old phone.
bubor said:
try to remove battery and wait at least 4 minutes, and put back.
It helped on my old phone.
Click to expand...
Click to collapse
I removed all night and still nothing. At the begining of the issue removing the battery helped, but now it seems like it got worse.
grtsarav said:
Try flashing the basic stock firmware from Samsung using Odin... Then re-root and check
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
I did it in the morning. It flashed correctly and when the ODIN re-booted my phone it crashed in the logo, like i have not done anything. I have been triying to turn it on for like 4 hours and nothing.

[Q] I need all the help i can get !! Soft-Bricked Note 2 stuck Bootloop

Ok so i will try and explain step by step what is the matter here.... Since i have been trying to fix my Note 2 since 2 weeks now and i got nowhere.
I was running 4.4.2 and i had TWRP on it but it wasnt Rooted. (Bought it like that) Had some custom Rom on it etc...
Used it for 2 months with no problems whatsoever,decided to root and went on installing AGNI Kernel for better audio (Eargasm ON). Everything worked as a dream for 4-5 days...was enjoying the crazy sound. Till one morning i woke up,received a call and i had to swap my sim cards,after i did this i had Emergency calls only on screen. BAFFLED !! Went on factory restoring the phone,still Emergency calls only on screen. JUST LIKE THAT !! All of a sudden,with no reason at all !! o.0
Anyway,after that i tried again factory restore and wipe cache and something else from TWRP i think it was a FULL DELETE or something like that,including System and all... so i can install a new fresh ROM on it (As i thought it`s the ROM). Well that didnt went well for me,as the phone got stuck into Samsung bootloop. AGAIN AND AGAIN AND AGAIN !!!
I gave up on TWRP and connected it to the laptop so i can use ODIN and flash stock ROM. Worked !! It went pass the Samsung boot,i set it up,still had the same `Emergency calls only` error,BUT THEN as soon as i unplugged my usb cable from it,BOOM !! Phone restarts itself,and gets stuck on Samsung boot. I connected the charger,works fine. Stays in menu,apps work,etc. As soon as i unplug the charger or the usb cable,it kept on restarting itself and going into Samsung Bootloop.
Went on different threads,tried a lot of ROMS and Kernels,nothing worked,so i gave up and BOUGHT A NEW BATTERY.
With the new battery,phone worked ok,no more bootloops,but still the same `Emergency calls only` issue.
Tried installing the modem fix with twrp,phone got stuck on samsung boot,tried installing nb4_N7100_Patched Modem_CWM with philz_touch_6.46.3-n7100 phone got stuck on samsung boot.
Then tried installing back the Android that Worked as a dream before (TWRP-Android Revolution HD) but this time i had the philz CWM and guess what,whatever Rom i install with philz,the same Samsung boot comes on.
Right now i tried installing Phoenix ROM,got stuck on bootloop,then cleaned the WHOLE DEVICE by a MEGA WIPE with Zoot's-Wipe-Scripts_SGS_N-II then tried installing again Phoenix Rom with philz,phone still NOPE,stuck on Samsung bootloop.
I am dead !! Please somebody give me some hope here,as i am dying.
I will put back TWRP now,and install again the only ROM that worked for me that is Android Revolution HD and stay with the bloody Emergency Calls Only on screen till somebody will be able to help me out here.... Please guys... i dont know what to do anymore,i am actually loosing my hope,it`s been 2 weeks since i am REALLY REALLY trying to get it back working....i feel i am growing white hair !!
use odin and go back to stock
HERE
there is factory firmware with pit file.
do everything as said in instruction

[Q] help - i think my phone is temporary bricked

hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)
Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though

Categories

Resources