Boot loop - Galaxy S6 Q&A, Help & Troubleshooting

I flashed a wrong kernel on my custom Rom and since then, my device won't priceed padt tge enlarged Samsung logo.
I subsequently flashed stock rom via Odin but the device still wont complete the boit cycle.
When I try ti access stock recovery, I get a blue screen and yellow triangle, with message, awaiting instructions.
Any ideas?

What is your device model number?

920w8

Related

Bricked recovery

I think I bricked the recovery for my phone. The OS does boot, and I can get to "download" mode. If I try to get in to recovery, whether its with vol-up+vol-down+power or rebooting to recovery from the OS, the phone just loops. It shows the Galaxy S logo than the screen goes black than back to the logo. I believe when I flashed the 2.3.3 ROM, it got screwed. It worked before hand. When I flashed the ROM via Odin, on the first attempt, it wiped something than failed. Than I got an icon on the phone (a phone icon with a ! and a computer screen icon) and wouldn't do anything past that. I again reflashed the ROM and the OS came up, but noticed the recovery doesn't work anymore. I've tried to flash the once more for good measures, and I tried the modified recovery binary, but same results. I'd greatly appreciate any help I can get with resolving this.
Thanks
I actually resolved this by flashing http://forum.xda-developers.com/showthread.php?t=1063696.

Stuck in Update boot loop Please Help!!!

I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
ej_424 said:
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
Click to expand...
Click to collapse
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
ej_424 said:
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
Click to expand...
Click to collapse
I flashed the stock n8000 recovery file via odin and it booted me out of the update loop. I had to do it twice tho. I rooted via odin so our fixes may be different.
I used file posted here http://forum.xda-developers.com/showthread.php?p=30450339#post30450339 post 45
Hope this helps a little
ej_424 said:
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
Click to expand...
Click to collapse
ej_424 said:
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
Click to expand...
Click to collapse
Ok I'm backup and running. I had to flash "HighonAndroidCWMRecovery" via odin to get past the update loop. Any ideas why this woudl be? I'm running stock with root and custom recovery. If I flash stock recvoery again and attempt the update do you think the same thing will occur?
ej_424 said:
Ok I'm backup and running. I had to flash "HighonAndroidCWMRecovery" via odin to get past the update loop. Any ideas why this woudl be? I'm running stock with root and custom recovery. If I flash stock recvoery again and attempt the update do you think the same thing will occur?
Click to expand...
Click to collapse
This need not be so complicated follow directions here http://forum.xda-developers.com/showthread.php?t=1847054&page=6 see post 58 and 39
Stuck, can't restore factory settings
I tried to unroot my Galaxy note 10.1 wi-fi and have caused such damage that it won't boot up. I have tried to press the power and down volume and I either get the Black welcome screen stuck, requesting I download the md5 file (which I have tried and doesn't work) or asks to use Kies to boot, but my laptops won't even pick up the device, they recognizes that there is a new device connected but it can't read it!
In the top left hand corner it reads
ODIN MODE (in red letters)
Product name: GT-N8010
Customer binary: yes (20 counts)
Current Binary: Custom
System status: Custom
PLEASE HELP!!!!
Thanks in advance
bee_rob said:
I tried to unroot my Galaxy note 10.1 wi-fi and have caused such damage that it won't boot up. I have tried to press the power and down volume and I either get the Black welcome screen stuck, requesting I download the md5 file (which I have tried and doesn't work) or asks to use Kies to boot, but my laptops won't even pick up the device, they recognizes that there is a new device connected but it can't read it!
In the top left hand corner it reads
ODIN MODE (in red letters)
Product name: GT-N8010
Customer binary: yes (20 counts)
Current Binary: Custom
System status: Custom
PLEASE HELP!!!!
Thanks in advance
Click to expand...
Click to collapse
I have same Problem
My only response would be to go to sammobile and download as close to shipped rom as you can (must be for your region and carrier, if from carrier), updated rom is fine. Make sure the download ISN'T corrupted by doing an MD5 check.. Also before f;lashing, make sure you exit KIES as this can screw up the connection in ODIN.
Put in Download mode, hold down volume and power until it says a scary warning, ignore the warning and press up volume.
Flash with ODIN making sure re-partition ISN'T ticked, when it finishes flashing turn off power.
Go to recovery by holding up volume and power button until it goes into recovery.
Wipe data/cache and then wipe dalvik cache.
Reboot and see what happens.
Good luck.
ultramag69 said:
My only response would be to go to sammobile and download as close to shipped rom as you can (must be for your region and carrier, if from carrier), updated rom is fine. Make sure the download ISN'T corrupted by doing an MD5 check.. Also before f;lashing, make sure you exit KIES as this can screw up the connection in ODIN.
Put in Download mode, hold down volume and power until it says a scary warning, ignore the warning and press up volume.
Flash with ODIN making sure re-partition ISN'T ticked, when it finishes flashing turn off power.
Go to recovery by holding up volume and power button until it goes into recovery.
Wipe data/cache and then wipe dalvik cache.
Reboot and see what happens.
Good luck.
Click to expand...
Click to collapse
Not working, not go the Recovery Mode, Only Samsung Logo.
I'm having similar issue as Odin keeps failing when trying to flash ROM.
Does anyone know the commands to do it through ADB? I've done it before on my nexus7 but don't know the commands to exactly use for the note. I still can't get into recovery. Only can get into that ODIN mode. I have all drivers and Android ADB installed on PC.
It seems like nothing will write to the NAND. Although my flash count changes now showing my attempts. I might have no choice but to call Samsung and file a warranty claim. I just don't want to lose all the pictures and info that's in my tablet.
Well I got my tablet back yesterday from Samsung. They fixed it. The report showed they replaced some piece that burned out. I forgot the name of it. Unfortunately all my info and stuff was erased. So I had to reinstall everything manually. At least my tablet working like new again. So glad to have it back. Been like a month or so since I've been able to use it. My nexus 7 and galaxy s3 was holding me down in the meanwhile.
This note is a great device. IM seeing again why I've missed it so much. Works flawlessly on stock Tom.

[Q] Cant flash and overwrite with stock rom on M919

I need help
I have a Tmobile Galaxy s4 M919.
After the 4.3 update, i am not able to completely flash a stock rom in order to have my phone working again.
Tried root, tried CWM ot TWRP, Odin stock, Kies, but every attempt got stuck for ever on the boot logo screen with blue letters on the left hand up corner saying recovery booting.
I can't access download mode but not recovery.
Only onceworked, and i could flash thru KIES and the download screen after that shown:
System Official Samsung
Binary Official.
After that i start to have an issue with SIMCARD non detected, and had to restart and never worked again.
Seems like Knox is dealing with custom rom or bootloader and keeps on bootlogo screen.
Any help will n]be very appreciated.
Augusto.Nascimento75 said:
I need help
I have a Tmobile Galaxy s4 M919.
After the 4.3 update, i am not able to completely flash a stock rom in order to have my phone working again.
Tried root, tried CWM ot TWRP, Odin stock, Kies, but every attempt got stuck for ever on the boot logo screen with blue letters on the left hand up corner saying recovery booting.
I can't access download mode but not recovery.
Only onceworked, and i could flash thru KIES and the download screen after that shown:
System Official Samsung
Binary Official.
After that i start to have an issue with SIMCARD non detected, and had to restart and never worked again.
Seems like Knox is dealing with custom rom or bootloader and keeps on bootlogo screen.
Any help will n]be very appreciated.
Click to expand...
Click to collapse
Best thing to do is use odin on your pc and get the stock rom from samsung or another source, then completly flash it so it will wipe out you phone completly and then reinstall stock. This happened to my m919. If you need more help on how to completly replace the stock rom using odin there are plenty of videos that show you step by step. You just soft bricked your phone so it's fixable.
Olycius said:
Best thing to do is use odin on your pc and get the stock rom from samsung or another source, then completly flash it so it will wipe out you phone completly and then reinstall stock. This happened to my m919. If you need more help on how to completly replace the stock rom using odin there are plenty of videos that show you step by step. You just soft bricked your phone so it's fixable.
Click to expand...
Click to collapse
I have flashed several times via odin and kies, but everytime i still with Binary Official and System Custom.
Seems like the flash does not overwrite the kies bootloader, thats why i am stuck on boot revovery.
Once it worked, the system and binary became official, then i flashed knox free stock rom via recovery.
As i told, i can acces download but not recovery.
Does anyone know any knox free stock rom flashable via odin???

Huge problem with rooting my phone!

I had a huge problem with my phone after trying to flash a new rom, my phone got brick and i was able to fix it by flashing with odin a firmware and right after the firmware finish going into recovery mode (which is no longer TWRP) and doing a factory reset.
now, everytime that i try to root my device, either with cf-root or twrp my phone goes into boot loop, and the only why to fix it is by doing what i did the first time! (flashing the firmware etc).
Im pretty sure that the problem is somehow related to the red lettering sentece i get in the top left conrer once the phone is in the boot screen (Recovery is not seandroid enforcing) I had this message also everytime well having the old rom but the phone worked fine.
what can I do to fix it, and is it possible that the problem doesnt related to the red message.
P.S - after flashing the firmware and doing factory reset and booting the phone, the message in the top left corner doesnt appearce
which model are you using and are you on the latest android update ? I'm pretty sure you are in DOL5 , if yes then you have to download dok9 and flash that firmware then proceed with root

Galaxy S7 stuck in bootloop

I've been trying to flash TWRP recovery via Odin on my S7 (G930W8), however I would constantly get the verification error. Now I'm trying to reflash the stock firmware but it gave me a Fail on Odin. This is probably my fifth time reflashing the stock rom, and it worked previously today but then it decided it had enough and started giving me a bootloop I guess lol. But yeah, everytime I try reflashing the stock now it fails to do so. I'm absolutely sure I have the right firmware.
My phone is stuck on a bootloop now with the Samsung text and black screen. I can get to TWRP recovery via volume up, power button, and home button, but I can't really do anything there, not even full wipe as it tells me it couldn't mount or something. I can get to Download mode though.
Any advice? I'm really stuck right now.
EDIT: So it looks like this worked: I turned off the device via recovery mode, and then flashed my stock firmware.

Categories

Resources