My wife has an ATT gs5 g900a. It was on one of the later versions of the MM firmware (unsure which one.) She was attempting to take a picture when the phone rebooted. After reboot she attempted again to take a picture, then it began bootlooping. Could not resolve with factory reset in recovery menu. Since then I've tried re-flashing MM firmware, including the latest, then attempted to go back down to OI5 L. Every time I flash anything it goes into a bootloop as soon as odin returns successful and reboots.
The only time I can get it to boot is if I flash the experimental OF1 firmware in odin, but then when I flash the prerooted OF3 it bootloops again. Any ideas to bring this phone back to life?
I am having the exact same issue, came out of nowhere. Everything was completely stock, phone froze and got bootloop fever, reset to factory and wiped cache. No change. Learned how to use odin and reflashed latest firmware, then did the reset and cache again, still bootloops. Tried the next firmware down the list, no change. I am thinking about trying the downgrade to NCE .tar, but i have no idea if that is even supposed to work from marshmallow all the way back. Any info on this topic would be greatly appreciated, by and and by RN_ReFlux above im sure. Thanks
Related
Was running looper just fine on my 920t when system started fc/ing . Flashed latest kt kernal. Still f/c . Wiped chash nothing. Odin back to stock, STILL system F/C! Wiped / Factory reset , retried odin stock , still F/Cing.. Is there ANYTHING else that I can try? I can get into Download ,
Cummins4 said:
Was running looper just fine on my 920t when system started fc/ing . Flashed latest kt kernal. Still f/c . Wiped chash nothing. Odin back to stock, STILL system F/C! Wiped / Factory reset , retried odin stock , still F/Cing.. Is there ANYTHING else that I can try? I can get into Download ,
Click to expand...
Click to collapse
If it's still happening after two Odin flashes something is seriously wrong with your phone. It started force closing out of the blue? Your sure you weren't poking around in partitions other than system and data?
No, everything was working fine on looper. I flashed Alliance in the 925t thread. Let it boot, went back twrp then flashed latest kt kernel. That's when I started to get the fc. Figured I did something wrong, so Odin stock tar. Still getting the fc. Sorry for the miss post. Just frantic..
So it turns out by dirty flashing a 925t rom with a 920t kernel over a 920t rom some how caused a system wide fc loop from hell. Completely wiped everything in Stock recovery, also tried twrp. Odin stock tar several times.... I finally threw in the flag and ordered a replacement.. Just thought I'd share,
Cummins4 said:
So it turns out by dirty flashing a 925t rom with a 920t kernel over a 920t rom some how caused a system wide fc loop from hell. Completely wiped everything in Stock recovery, also tried twrp. Odin stock tar several times.... I finally threw in the flag and ordered a replacement.. Just thought I'd share,
Click to expand...
Click to collapse
The weird part is odin *should* have fixed any problems a rom could cause. Good luck with your next phone, really sucks you had to replace it.
ThePagel said:
The weird part is odin *should* have fixed any problems a rom could cause. Good luck with your next phone, really sucks you had to replace it.
Click to expand...
Click to collapse
Thanks, lesson learned.. Been flash dozens of ROMS since my s2, first-time ever I couldn't save a device. Just so weird. Tried stock tar right from Sammy with everything wiped. Wish someone had an idea what would've caused it. Right Odin, right tar, Samsung cable, different computers... Just think I'll leave it alone from now on. Too expensive to mess around with this device, especially without a reliable fall back.
Just wondering if anyone had any idea on how to fix a force close loop after stock Odin flash? I bought a new device. Obviously my warranty is void. I didn't have insurance. I'm left with a really shiny paperweight. I'm willing to try anything, thanks in advance.
Classic case of bootlooping.
Recently used Flashfire to install rooted stock version of Lollipop 5.0. After trying to reinstall X-posed framework by flashing through flashfire, phone became bootlooped at At&t logo, remaining bricked after factory reseting and clearing cache.
Used odin to try and downgrade back to a stable version of 4.4 kickat. However, phone now bootloops after shuddering at samsung logo, before blipping to black screen with blue indicator light permently on. Trying to install current version of OTA rom through default recovery made no change. Suspecting bootloader my be root of issue, as trying to flash stock version of 4.4 bootloader in odin fails.
Currently looking for options to simple get phone back complete factor reset at this point. Links to other threads that have already solved this problem welcome.
SkunkID said:
Classic case of bootlooping.
Recently used Flashfire to install rooted stock version of Lollipop 5.0. After trying to reinstall X-posed framework by flashing through flashfire, phone became bootlooped at At&t logo, remaining bricked after factory reseting and clearing cache.
Used odin to try and downgrade back to a stable version of 4.4 kickat. However, phone now bootloops after shuddering at samsung logo, before blipping to black screen with blue indicator light permently on. Trying to install current version of OTA rom through default recovery made no change. Suspecting bootloader my be root of issue, as trying to flash stock version of 4.4 bootloader in odin fails.
Currently looking for options to simple get phone back complete factor reset at this point. Links to other threads that have already solved this problem welcome.
Click to expand...
Click to collapse
If you installed the 5.0 rooted then I'm guessing you seen this thread. If you have the s5 then scroll down to the notes section and flash the nce downgrade file in odin. That'll put you back to stock.
http://forum.xda-developers.com/showthread.php?t=3076803
dirtydodge said:
If you installed the 5.0 rooted then I'm guessing you seen this thread. If you have the s5 then scroll down to the notes section and flash the nce downgrade file in odin. That'll put you back to stock.
http://forum.xda-developers.com/showthread.php?t=3076803
Click to expand...
Click to collapse
Thank you so much! I had been trying to download this file from another source for hours. This thread had a mirror that got me taken care of in only a few minutes. Everything's up an running perfect again.
dirtydodge said:
If you installed the 5.0 rooted then I'm guessing you seen this thread. If you have the s5 then scroll down to the notes section and flash the nce downgrade file in odin. That'll put you back to stock.
http://forum.xda-developers.com/showthread.php?t=3076803
Click to expand...
Click to collapse
What section of Odin do you flash it in? Like AP, CSC...?
Philpro said:
What section of Odin do you flash it in? Like AP, CSC...?
Click to expand...
Click to collapse
Flash in odin 3.09 in the ap slot
Don't flash this file if you took the ota to 5.0 or if the phone came with 5.0 on it. You will brick the phone.
Anyone have any thoughts on what might be going on with my note? i was coming from tekxodus rom back to a stock firmware and now i cant seem to get out of this bootloop. i downloaded firmware and flashed it using odin... it passed. then just goes from samsung note 4 logo to samsung circle logo to tmobile freezes for 3 minutes then repeats. Its odd
That happened to me as well. I had forgotten to turn on OEM unlock. Pull battery and renter download mode. Use Odin to reinstall TWRP then restore a backup. Turn on OEM unlock and then flash the firmware again with Odin
i happened to me going from cog2 to dok2. i was not planning to stay unrooted on stock.
i pulled battery.. flashed twrp... pulled battery... then flashed a rooted rom and all was well with the world.
i assumed it was because i did not unroot and do full internal wipe.. but then as i was mostly just updating baseband i did not do any further troubleshooting
Ok im going to flash old one unlock oem and get back to you guys
didnt work tried two roms on 5.1.1 both didnt have oem unlock inside developer options so weird. then i when to twrp hit factory reset then flashed firmware and that worked. im glad i lucked out with that method weird how you have to factory reset to flash an entirely new firmware you would think the script running would do that.
Glad you got it working. I thought Odin wiped everything including internal storage but it did not. When I flashed the stock firmware I still had my settings and storage was untouched. Not what I remember from my Note 3 days
Greetings all
I went ahead and rooted my T-Mobile Variant NOTE 5 using Nobel Kernel everything worked out great at first I went ahead and installed Xposed installer and flashed the sdk22arm64 and that's where the issue came the phone will not boot up past T-Mobile screen it restarts and restarts it also states that KERNEL IS NOT SEANDROID ENFORCING
I tried to flashing the same kernel file again via Odin says it flashes but bootloops still persist this is the file I used Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
I tried to flash stock firmware but for some reason every time I select any file other than the one above Odin freezes and closes ( Not responding) could anyone point me in the right direction to fix this issue I still have TWRP installed unfortunately no back up is there
all the help is appreciated my device is useless at the moment
I've wiped everything from TWRP / WipeCache and even factory reset and lost all data now still nothing, deleted TWRP and factory reset hoping it'll just go back to stock and same thing happened just bootloops
Anyone help ?
Phone has been in the ****ter for the past day. Stuck on boot loop. I tried flashing the most recent stock firmware. It would not do it and kept throwing auth failed signs at me. I tried other stock firmwares for tmobile with no sucess. I Tried throwing them on my sdcard and installing through there in TWRP, but I keep getting md5 auth failures. I have wiped, factory reset, and cleaned house many times. Nothing works. Im at my wits end. Someone please help
Figured it out on my own. Flashed CF autoroot. Then flashed 5.1.1 which is the most up to date firmware. Im not sure if the issue was because I was doing 5.1.0 and didnt realize that was the most UTD version, or if CF to 5.1.1 was the trigger. Either way, it worked.