Note 4 stuck at AT&T logo after factory reset - AT&T Samsung Galaxy Note 4

Every few months I usually wipe my phone to give it that fresh running feeling. I wiped my AT&T note 4 from recovery and wiped cache today and the phone boots and gets stuck at the AT&T logo. I thought it was strange and so I booted into recovery again and again tried to factory reset and wipe cache.
If it matters my phone is currently on version U2EPK1 and I've never encountered anything like this before on this phone.
Any tips for progression?

HobsonA said:
Every few months I usually wipe my phone to give it that fresh running feeling. I wiped my AT&T note 4 from recovery and wiped cache today and the phone boots and gets stuck at the AT&T logo. I thought it was strange and so I booted into recovery again and again tried to factory reset and wipe cache.
If it matters my phone is currently on version U2EPK1 and I've never encountered anything like this before on this phone.
Any tips for progression?
Click to expand...
Click to collapse
Try installing a firmware via odin

Related

I need help please!

Hi,
I just got the S3 on Mobilicity in Canada. I rooted it and installed cyanogenmod 10 on it but didnt like it so I tried to install this (http://forum.xda-developers.com/showthread.php?t=1771687) stock back to my phone. Now my phone is stuck at the samsung logo. I can still get into download mode but cant get into CWM. Im really worried. Please oh please someone help me!
jd402 said:
Hi,
I just got the S3 on Mobilicity in Canada. I rooted it and installed cyanogenmod 10 on it but didnt like it so I tried to install this (http://forum.xda-developers.com/showthread.php?t=1771687) stock back to my phone. Now my phone is stuck at the samsung logo. I can still get into download mode but cant get into CWM. Im really worried. Please oh please someone help me!
Click to expand...
Click to collapse
Odin back to stock
Sent from my SGH-T999 using xda premium
funziebear said:
Odin back to stock
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried but I still get the same problem. Maybe Im doing something wrong. I put the phone in download mode, open Odin, plug it in, click PDA, choose the stock I got from the SamMobile site, and it runs completely but then gets stuck on reboot at the Samsung logo still.
go into stock recovery by powering on the phone while holding home and volume up, then choose the option to wipe cache, then reboot.
Agreed. I had a similar issue the other day. I ended up wiping cache in samsung recovery, and if that doesn't work, wipe data factory reset. I tried rebooting, but it still got stuck at the samsung logo. I then flashed CWM recovery or TWRP recovery through ODIN and then download another rom. Do a factory reset within the new recovery / wipe cache/ wipe dalvik/ wipe system/ and then flash the new rom. That will get it to boot.
Moral of the story is to not freak out too much. You're not in trouble.
bstapley said:
Agreed. I had a similar issue the other day. I ended up wiping cache in samsung recovery, and if that doesn't work, wipe data factory reset. I tried rebooting, but it still got stuck at the samsung logo. I then flashed CWM recovery or TWRP recovery through ODIN and then download another rom. Do a factory reset within the new recovery / wipe cache/ wipe dalvik/ wipe system/ and then flash the new rom. That will get it to boot.
Moral of the story is to not freak out too much. You're not in trouble.
Click to expand...
Click to collapse
Yep if u can still get into
Download mode there is plenty of hope of booting back up I had same issue and most the tars I was using held up till I found one that worked I have it saved if u need it lmk
Sent from my SGH-T999 using xda premium
bstapley said:
Agreed. I had a similar issue the other day. I ended up wiping cache in samsung recovery, and if that doesn't work, wipe data factory reset. I tried rebooting, but it still got stuck at the samsung logo. I then flashed CWM recovery or TWRP recovery through ODIN and then download another rom. Do a factory reset within the new recovery / wipe cache/ wipe dalvik/ wipe system/ and then flash the new rom. That will get it to boot.
Moral of the story is to not freak out too much. You're not in trouble.
Click to expand...
Click to collapse
+1
The wiping is key
Sent from my SGH-T999 using xda premium

stuck at galaxy s4 screen please help

Yesterday I tried installing Danvh's 4.4.2 Google Edition ROM and I guess it must have went wrong. I backed up my current ROM and data before the installation. I did a full wipe (davick / data / cache etc.) and I also did a format of internal SD. I installed Danvh's ROM fine but when I rebooted after the installation it will not get past Galaxy S4 screen. So I figured there was something wrong with the ROM so I flashed back to my back up but when I restart my phone it will still be stuck at the S4 screen so I have to keep flashing back to the backup file. I used TWRP 2.6.1.0 for recovery and I also fixed the permissions with TWRP. Any ideas? What should I do? If my phone ever crashes I will have to restore to my only back up.
re: stuck
ragingazn628 said:
Yesterday I tried installing Danvh's 4.4.2 Google Edition ROM and I guess it must have went wrong. I backed up my current ROM and data before the installation. I did a full wipe (davick / data / cache etc.) and I also did a format of internal SD. I installed Danvh's ROM fine but when I rebooted after the installation it will not get past Galaxy S4 screen. So I figured there was something wrong with the ROM so I flashed back to my back up but when I restart my phone it will still be stuck at the S4 screen so I have to keep flashing back to the backup file. I used TWRP 2.6.1.0 for recovery and I also fixed the permissions with TWRP. Any ideas? What should I do? If my phone ever crashes I will have to restore to my only back up.
Click to expand...
Click to collapse
You forgot to do a "factory reset" in twrp before restoring your Nandroid backup.
Most likely after doing that the phone will fully boot.
Be sure to wipe data, system, cache, dalvik cache and
do a factory reset before restoring your backup.
Good luck!
Good luck!
Nope I did do factory reset as well...

Beta 4.2 20140318 hangs during boot

Hi,
I started using PA on my Galaxy Nexus with a fresh install of 4.0 Beta 6 about 4 weeks ago (unlocked and rooted via nexus root toolkit, recovery is teamwin).
Since then, I installed every update through Paranoid OTA, so I am on current 20140318 now with GAPPS stock 20140318.
Everything was great.
Suddenly, a few hours ago, the phone started rebooting again and again until I decided to take out the battery.
Since then, it hangs during boot at the PA logo.
I tried reinstalling pa_maguro-4.0-BETA6-20140217.zip and pa_gapps-stock-4.4.2-20140217-signed.zip through recovery (after backup of course), but this changed nothing.
Fun thing is... I am moving to a new flat tomorrow and really need my phone to organize things.
So if anybody has an idea what I can look at or how this may be fixed, I would really appreciate it.
Thanks!
Stephan
Edit: wiping cache and dalvik cache did not help...
Factory reset and reinstall
felt0r said:
Hi,
I started using PA on my Galaxy Nexus with a fresh install of 4.0 Beta 6 about 4 weeks ago (unlocked and rooted via nexus root toolkit, recovery is teamwin).
Since then, I installed every update through Paranoid OTA, so I am on current 20140318 now with GAPPS stock 20140318.
Everything was great.
Suddenly, a few hours ago, the phone started rebooting again and again until I decided to take out the battery.
Since then, it hangs during boot at the PA logo.
I tried reinstalling pa_maguro-4.0-BETA6-20140217.zip and pa_gapps-stock-4.4.2-20140217-signed.zip through recovery (after backup of course), but this changed nothing.
Fun thing is... I am moving to a new flat tomorrow and really need my phone to organize things.
So if anybody has an idea what I can look at or how this may be fixed, I would really appreciate it.
Thanks!
Stephan
Edit: wiping cache and dalvik cache did not help...
Click to expand...
Click to collapse
Seems like you got stuck in a bootloop. bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence
Try doing a fresh install (use latest recovery version of your recovery)
- wipe data/factory reset
- wipe cache partition
- format system and data
- wipe dalvik cache and flash the rom and gapss again

[Q] Stuck in recovery mode bootloop!

Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
chortiman said:
Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
Click to expand...
Click to collapse
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Mr.201 said:
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Click to expand...
Click to collapse
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
chortiman said:
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
Click to expand...
Click to collapse
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Mr.201 said:
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Click to expand...
Click to collapse
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
chortiman said:
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
Click to expand...
Click to collapse
Glad it worked, make sure you untick 'system' in filter in titanium backup so that you can only see your user apps .

lineage-14.1-20170116-tilak-n7100.zip boot loop issue

I hope everyone is fine. I am facing an issue. I installed lineage-14.1-20170116-tilak-n7100.zip this rom in my samsung galaxy note 2 and it ran into boot loop....i wiped data, factory reset, cache etc and it worked fine...after sometime i restarted the phone again and it ran into boot loop again and i wiped everything again but this time it did not work and the boot loop is still there....... I used Phillz recovery for flashing.

Categories

Resources