So I rooted my s6 a few months ago, everything has been fine up till now, but, the phone is no longer able to boot past the 'Three' loading screen. I've tried rebooting and factory resetting. I have even tried to install the original firmware but Odin fails every time. Can anyone help?
Update: managed to install the stock firmware with Odin after installing TWRP, still having the same issue though. Going to retry it.
Related
Hello Everyone,
I have been trying to help my friend with his soft-bricked G3. He wasn't rooted and had never even played with flashing anything, it just stopped booting one day and would display the "LG Life's Good" boot screen for a few seconds before going black and then just repeating this endlessly. I was able to get into recovery and download mode so I used the tot method to flash back to stock after a hard reset just produced the same results.
When I flashed the stock firmware, everything appeared to work fine, it went through the MiniOS bootup and everything, said success, gave me the hard reset status screen so when it finished I pulled the battery as instructed and rebooted but the phone still has the same issue. I have tried to run factory reset through recovery now that I flashed the new firmware and it still does the same thing, just hangs at the boot screen for a few seconds before going black and then trying again, endlessly.
Has anyone encountered this before? Is it bricked?
Thanks.
The_mamba said:
Hello Everyone,
I have been trying to help my friend with his soft-bricked G3. He wasn't rooted and had never even played with flashing anything, it just stopped booting one day and would display the "LG Life's Good" boot screen for a few seconds before going black and then just repeating this endlessly. I was able to get into recovery and download mode so I used the tot method to flash back to stock after a hard reset just produced the same results.
When I flashed the stock firmware, everything appeared to work fine, it went through the MiniOS bootup and everything, said success, gave me the hard reset status screen so when it finished I pulled the battery as instructed and rebooted but the phone still has the same issue. I have tried to run factory reset through recovery now that I flashed the new firmware and it still does the same thing, just hangs at the boot screen for a few seconds before going black and then trying again, endlessly.
Has anyone encountered this before? Is it bricked?
Thanks.
Click to expand...
Click to collapse
Pretty common prob plug it in to the wall charge see if it boots sometimes it still wont but most of the time it will the battery quality on the g3 is crap they last at most a year with a few exceptions i would first order a battery.
Hi guys, so recently I bought a Galaxy S6 Verizon off of eBay. I got it for fairly cheap because it was stuck in a boot loop. I usually have no problem fixing stuff like this, but this time is different. So the first thing I tried when I got the phone was to do a reset and cache wipe from recovery. I rebooted the phone and it showed a screen that said "Android is starting, optimizing app 9 out of 31." when it got to 21 the phone rebooted and went back to 9. It did this several times before I attempted to wipe/reset again. I then downloaded the tar file G920VVRU4CPH1 and flashed it in Odin. I did a manual reset before the phone booted, and it is doing the same thing again. reboots to a green screen where it tries to optimize apps, stays there for about 20 seconds, and reboots over and over again in the same cycle. I have tried all other stock marshmallow roms that i can find, Odin won't flash older ones, (assuming its not letting me downgrade). Also another weird thing, every time I flash, the blue update screen goes to 32%, stops, erases, and reboots. Phone is on 6.0.1 version MMB29K.G920VVRU4CPH1 as seen in recovery. Any help would be gladly appreciated. Thank you!
I am having a similar problem with loading new rom. The farthest it gets is 32%. Sometimes it doesn't get even that far.
I ended up just buying a trashed s6 and swapping the motherboards. Only way I could fix it
Hello;
several days ago, suddenly my N8013 restarted. After rebooting, it stuck at Samsung logo, and I couldn't go to Recovery mode. I flashed an official rom from sammobile. the process was passed but my N8013 problem didn't solve.
What's the solution? Is it a hardware problem??
I don't know exactly what happened, mine did the same thing. I fiddled around with it enough that i got it to reload back to samsung 'new' but it never recovered where it was at the time it went haywire. I installed Kies on my PC and let it update the kernel to the latest stock. I had not rooted or anything up to that point. it just went kapuut. Now I am rooted and tried a couple ROMS, but so far I keep coming back to stock because I can't get something or another to work right (or at least the way I am used to)
Hey guys,
My wife's Galaxy S6 - SM-G920P has been stuck in a boot-loop the last few days. I am unable to get past the login screen before it restarts. I cleared the cache and tried everything from the youtube link below, but I am running into a problem with the ODIN firmware update. I am using ODIN v3.12 and I am trying to install the below firmware update. Everything works fine, the firmware is uploaded to the phone. However, when the phone reboots and the blue screen comes up with installing updates, it keeps freezing at 32%, followed by an erasing of the update. The phone then repeats the boot loop again.
I am out of ideas and was hoping someone has encountered this issue before and can point me in the right direction.
Thanks in advance.
youtube.com/watch?v=YJi_w4c0KyE
FIRMWARE UPDATE
.sammobile.com/firmwares/galaxy-s6/SM-G920P/SPR/confirm/G920PVPS4DQF1/178566/
Bump...still having the problem
Try to change the version of ODIN and the firmware
did both, and now I can't even get to the login screen...any ideas on how to get out of the boot loop?
bump....still having the issue
Ok I will admit it, I screwed up royally this time. My SM-N9150 (Hong Kong version) was slowing down and draining the battery fast. I could not get the downloader of a new stock ROM to work in Sammobile (tried multiple times, with adblock off but no go) and so I bit the bullet and used Kies to upgrade to Marshmallow. Of course this lost root but I figured I could just re-root (I had rooted using Odin with my old phone, but this one I had rooted using KingoRoot). However, none of the 1-click systems like KingoRoot worked, and neither did Chainfire via Odin (which caused problems on its own). So I flashed the latest CWM via ODIN. It said pass, so I went into recovery, did a backup, then did factory reset, installed SuperSu, wiped the caches and rebooted.
I kept getting weird errors where it would not let me boot into recovery or boot at all. so I thought that maybe CWM was not a good choice. I tried the newest version of TWRP but that gave me the "recovery is not seandroid enforcing" error. So I went back the CWM and tried wiping again.
After a very long Samsung logo bootloop, it eventually showed gearings turning but with instructions in Chinese. It then showed the logo again for long time and then showed something that had only 1 English word "system" and the rest in Chinese. There seemed to be 2 choices at the bottom of the dialog box. When I chose the one of the right, the phone showed a grey progress bar with Chinese letters above, but then went back into a bootloop; when I chose the one on the left, the phone turned off for a long time then restarted but again seems to be stuck at the Samsung logo screen before returning to the message with the word "system".
After it going into a bootloop that lasted over 1 hour, I pulled the battery and then went into recovery and tried restoring the backup I had made at the start. That just left me in the endless Samsung logo bootloop. I left it plugged in overnight hoping it would do something but nada. At one pint I did get a message "unfortunately, the system UI has stopped working" but screen was unresponsive to press OK, and it just went back into the bootloop.
I realize I did not do anything to unlock the bootloader. Would using KIES have locked the bootloader again? Could this be my problem, and if so, how do I fix it?