I rebooted my device and then it went in to a boot loop. I have been trying to flash via Odin, but to no luck. I believe it is because I still have the lock screen on but I'm not completely sure. Thanks for your time.
Related
I rooted my GS4 and tried to install PureG but ended up in a boot loop at the Samsung Galaxy S4 screen. I fixed it by flashing the stock image through ODIN following. I then went to root it again using the guide by open1your1eyes0. I am now stuck in a boot loop yet again, however this time it says "Samsung" then underneath that is an open padlock, and under that it says "custom". I have tried everything I could think of with no luck. I have tried looking around for people with similar problems but again no luck.
Can you boot into recovery?
Flash-oholic on my SCH-I545
I got it. It was just being glacially slow booting up. I thought it was stuck so I kept resetting it. It was a dumb mistake. Thanks for the reply though.
No problem, if it hangs up in the future you may have to fix the permissions from recovery mode. FLASH ON!
Flash-oholic on my SCH-I545
Phone took a dump today. Was fine, then shut down, then wouldn't boot past boot screen. Enter safestrap, wipe all, no boot. Odin to stock mj9, no boot. Factory reset after doing in stock recovery, no go. After Odin the phone will get to the Verizon splash screen then shut down. Subsequent attempts to boot after that will not make it past the Samsung logo. It doesn't stick there, it just shut off. Odin completes succesfully. Any ideas?
vlx600d said:
Phone took a dump today. Was fine, then shut down, then wouldn't boot past boot screen. Enter safestrap, wipe all, no boot. Odin to stock mj9, no boot. Factory reset after doing in stock recovery, no go. After Odin the phone will get to the Verizon splash screen then shut down. Subsequent attempts to boot after that will not make it past the Samsung logo. It doesn't stick there, it just shut off. Odin completes succesfully. Any ideas?
Click to expand...
Click to collapse
Sounds like a partition curroption..Have you tried using Heimidall and flashing each image separately?
Also, you might want to bring it Verizon tell them it won't turn on..
But you can try what I suggested above..
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...
Hey everyone! Big problem..
I have installed CM12, Android 5.1 it's been all fine up until now, I was planning on selling the phone, so I factory reset it, that went well until it tried to turn itself back on afterwards.
My Samsung Galaxy S3 i9300t is stuck in a bootloop. I can not do absolutely anything.
I've tried taking the battery out, holding the three buttons, putting it back in, doing that with a USB, As soon as I turn it on, holding buttons or not it goes straight into a bootloop. I can't use odin to install the custom firmware again as I can't get into recovery or download mode or anything, once it's in the boot loop it stays there..
Any help is appreciated.
Bump?
I have an S6 Edge Canadian Variant (SM-G925W8) that will not boot past the logo.
It will boot into download mode, but not recovery or safe. If you hook the charger up to it, it immediately powers on and goes into the boot loop. I have tried to reflash stock, flash TWRP, and flash stock with a PIT file. Nothing has changed its behavior.
I have noticed multiple older threads with similar problems, but no concrete resolutions. Is this an issue with older S6's?
i`m also interested in this because there is one for sale with a bootloop and i'm thinking of risking it.