Stuck att logo aucu2coc5 - AT&T Samsung Galaxy Note 4

Hey guys im on AUCU2COC5 i just did ota update and phone is stuck on att logo. Anyone know a version to flash with odin that will still preserve my data (music, videos) and allow me to boot completely.
Can i safely flash N910AUCU2DOI2_ATT2DOI2_v5.1.1_Repair_Firmware.zip through odin as a fix? Shooting in the dark here...

Related

[Q] Galaxy S3 Bootloader stuck on a bad loop

Hey guys,
I have a Galaxy S3 AT&T that I was attempting to unroot via Odin 3, and am now currently stuck in a good bootloader loop. I have done my fair share of searching and research before starting this thread, and my problem seems to be unique. Or very bad.
I tried flashing the stock image/unroot file via Odin, it black screened and have a blue LED light on. Cannot access recovery, so I tried flashing a new recovery through Odin as well. (I made sure it was the correct device model and build, which is IMM76D ALG1.) Still nothing. Tried the same thing through download mode, rebooted, nothing. Battery pull, tried the same thing as before, and now I can't access my download mode.
So basically I'm stuck in a boot loop, with no access to recovery mode or download mode. Do I have a new fancy paperweight for my desk or is there a way out of this? Any help would be appreciated greatly, I'm pretty desperate right about now.

Stuck at Samsung splash screen.

Hi,
I recently tried installing the new 4.3 update onto my Samsung Galaxy S3 I747. Also, I never rooted my phone and my carrier is Telus if that matters.
When my phone finished updating, it lead to the lock screen. Just as I was about to enter my pin and unlock it, the phone restarts and gets stuck on the Samsung splash screen. I have tried entering into recovery mode and then wiping the cache and restarting it, but no luck.
I do not wish to restore my phone back to factory settings because I do not want to lose my music and apps. Is there a solution that can fix it without wiping the memory?
Thanks.
edit: i left it charging for a few minutes while it was stuck on the samsung splash screen, and then it went to the lockscreen and restarted it self
... i have to wait five minutes before i can save my edit
editedit: it just went to lockscreen for a second again
editeditedit: its going back to lockscreen quite often and restarting it self
aznpiggy said:
Hi,
I recently tried installing the new 4.3 update onto my Samsung Galaxy S3 I747. Also, I never rooted my phone and my carrier is Telus if that matters.
When my phone finished updating, it lead to the lock screen. Just as I was about to enter my pin and unlock it, the phone restarts and gets stuck on the Samsung splash screen. I have tried entering into recovery mode and then wiping the cache and restarting it, but no luck.
I do not wish to restore my phone back to factory settings because I do not want to lose my music and apps. Is there a solution that can fix it without wiping the memory?
Thanks.
edit: i left it charging for a few minutes while it was stuck on the samsung splash screen, and then it went to the lockscreen and restarted it self
... i have to wait five minutes before i can save my edit
editedit: it just went to lockscreen for a second again
editeditedit: its going back to lockscreen quite often and restarting it self
Click to expand...
Click to collapse
When you got it into recovery did you try to wipe data/factory reset??
But to be honest it sounds like your phone is soft bricked maybe. I'm experiencing the almost same problem with my AT&T sgh-i747. Mine is stuck at the Samsung Galaxy S III screen and doesn't go any further than that at all.
You will most likely have to do that same thing I am doing which is reflashing android 4.3 via odin. It may work for you, I'm pretty sure it'll work for mine. Head over here and read this thread and see if this can help if not let me know and we'll come up with somethin else to help you fix your phone. (If I'm correct following this thread and flashing via odin will not erase and of your data.)
Your only other real option is to install the 4.3 MJ2 leak via heimdall. http://forum.xda-developers.com/show....php?t=2496425
Heimdall will flash odin files. http://glassechidna.com.au/heimdall But odin will not flash heimdall files. It works much like odin flash in download mode so i'm told. I'm trying to figure it out now. I hope this helps.
I was never able to get the above Heimdall installed correctly on my pc. I am still stuck at the black and white galaxy s3 screen. I installed TWRP via odin to try my to run my nandroid i made earlier today and it says successful. But when I go to reboot It says No OS are you sure you want to reboot. I was already on 4.3.3 via the OTA update like you. And now i'm here turn phone on and it's going straight to download mode
Please HELP US BOTH Someone ANYONE

Interesting Bootloop

Whether I try to turn my phone on or boot into recovery mode I get a strange bootloop. It goes between the Samsung Galaxy Note2 logo and the custom recovery in this case clockwork mod recovery screens. Never saw this before and Google isn't helping. If anyone knows what's going on any help is appreciated because as of now my phone is completely unusable.
I already tried switching custom recovery via Odin but the same thing happens it bootloops between the Samsung Galaxy Note2 logo and the new custom recovery start up screen. Really weird.
I am able to get into download mode.
Again any advice would be greatly apprecaited
Update: Attempted to Odin back to stock ROM and according to Odin it passed but now stuck in stock bootloop and still unable to get into recovery mode

[Q] Update ran and stuck in att logo

We my son was using my phone GS3 and pressed on to update. he thought it was a game update, but once it ran it boot then it will be stuck in the ATT logo. I kept tying to reset nothing it boots but once in att logo it stops. i also went in to clear the cach anf reset to factory and still no responds please help.....
Was the phone rooted? Does it have a custom recovery? These two things can cause an ota to fail.

Not your Usual Boot Loop

Hi Guys hoping someone can help me out.
One of my friends who should know better decided to try and flash a custom rom to his N7105 trouble is he used a n7100 twrp which apparently installed and then tried to flash a n7100 rom .
Now his phone is stuck in a boot loop, it sometimes gets as far as the animated boot logo with the blue led pulsing depending on what I last did to it lol. I can get into both download and recovery and the power button isn't stuck.
I don't know what stock version the phone was one when he started messing with it and he is vague about everything HE tried to do to fix it before I got my hands on it. Its entirely possible it was on 4.1.2 to start off with and he's tried to go straight to lollipop does the 7105 need to update in increments? or could he have put a n7100 bootloader on somehow but flashing stock via Odin should fix that right?
I have a memory of people having this sort of problem years ago with HTC and it ended up being a mismatch between the modem and baseband versions or something like that, thoughts?
Here's what I've tried
Odin flash CF-Auto root as it restores stock recovery at least now the PC detects it as t0lte not t03g
1) Recovery wipe data and cache - now only gets as far as the initial samsung galaxy note II screen
2) Odin flashing a 4.1.2 rom from sammobile - no go "unsupported" so has a knox bootloader
3) Odin flashing a 4.3 rom from sammobile - hangs on animated boot logo with the blue led pulsing
tried 1 again same result
4) Odin flashing a 4.4.2 rom from sammobile - hangs on animated boot logo with the blue led pulsing
tried 1 again same result
5) Install firmware via Kies - hangs on animated boot logo with the blue led pulsing
tried 1 again same result
Odin Flash proper version of twrp 2.8.7.0
6)Fix permissions in TWRP - says sucessfull but also has "E: unable to mount data" etc back to the initial galaxy note II screen
7) Flash custom rom via twrp - hangs on animated boot logo with the blue led pulsing
tried 1 again same result
I'm running out of ideas and patience with this thing does anyone have any other ideas for me to try?
After leaving the phone for a while to prevent me from smashing it into a million bits with the biggest hammer I could find I got it working tonight.
Charged the phone up I had to disconnect and reconnect a few times as it said it was 100% on the full screen battery picture then in recovery it said 18% or something
I re-flashed N7105XXUFNL2_N7105H3GFOD1_H3G from sammobile using Odin 1.85 along with the PIT file from this thread checking re-partition (I used a pit file otherwise I'd leave this alone), Auto Reboot, F.Reset time and Phone Bootloader update. This seemed to take longer than previous flashes.
Flashed TWRP 2.8.7.0
formatted Data in TWRP (the advanced one where you have to type yes to confirm). Previously Data was unmountable so I assume the long flash fixed something there.
Wiped cache in TWRP
and rebooted and waited ages and it came to life

Categories

Resources