[Q] Help stuck on Galaxy screen after reboot! - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

I have rooted my phone, then installed TWRP along with CM 12 unofficial. Next, I wiped everything and reflashed it down to CM 11, but I haven't been able to successfully reboot the phone at anytime. My phone will boot up to the Galaxy Screen, but won't doing anything unless it's a fresh install of the GAPPS and ROM. So it's hard to take pics when you have to restart and wipe your phone, and reflash it just to take a single pic! Is there anything that I could possibly do to fix this? Any help is greatly appreciated!

Related

[Q] Please help! Stuck on boot screen!

I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
danlk2 said:
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
Click to expand...
Click to collapse
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
irishrally said:
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
Click to expand...
Click to collapse
Wow, that didn't even cross my mind, I did this and I've got the rom up and running now. Thanks a lot.

[Q] Stuck in Bootloop (ROM: PA)

Trying to install a Custom ROM for the first time on Nexus 7 (3G).
I've been using the WF Nexus Toolkit.
I've rooted, unlocked and flashed ParanoidAndroid but I'm only getting a bootscreen loop. I waited 15 min before rebooting the device and attempted to boot into PA again. Still not getting past the Bootscreen.
I booted into recovery; did a full wipe then flashed the PA ROM again... Still not getting past the Bootscreen (waited 30 min before powering off the device)
I've tried to obtain help via IRC before posting here; as well as reading through other post directly related to the problem (even a few that were slightly indirect) but nothing I find is helping... so I've turned to you guys!
I would very much like to get this ROM working, so if there is anyone that can help I would greatly appreciate it.
I just don't know what to do next; I've never had this issue with any device in the past.. I've usually been able to figure the problem out and get it working. But now I'm just stuck.
What is your recovery? What steps did you do in recovery to install the rom?
Try these step may help.
1.Boot into recovery
2.Full wipe
3.Wipe Cache
4.Wipe dalvik cache
5.Flash ROM, GAPP
then reboot your N7.
...
If above method still doesn't work. make sure you have the right version of bootloader and stock image on your device for PA 3.15 or newer it should be 4.18 for bootloader and 4.2.2 for stock image (optional).
And if you've found that you have other version of bootloader than 4.18 check this http://forum.xda-developers.com/showthread.php?t=1907796 thread for how to get it right.
...
Finally if you've done all the solutions above and still in bootloop problem just try to do a factory reset (full wipe) again after finish flashing ROM, GAPP.
That's all I can thinks of about this problem base on my personal experience facing bootloop problem few months ago.
If you are still stuck after trying the above posts. You can just try to get back to stock. Nexus Root Toolkit maybe the easiest way to do that..
____________________________________________
Please press the thanks button if you find this helpful

OmniROM Annoying Bootloop

I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
matthewclso said:
I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
Click to expand...
Click to collapse
you can...try this!
@halfdevil said:
you can...try this!
Click to expand...
Click to collapse
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
FIXED
Turns out that I just had to flash the boot image through fastboot, works great now! Thanks
matthewclso said:
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
Click to expand...
Click to collapse
well you can try AOSP too, just remember all these projects are discontinued, so any support in case you break anything support won't be there..so always backup.
for AOSP!

G900F Bricked after update: cm-14.1-20161219-NIGHTLY-klte.zip

Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!

LineageOS 17.1 bootloop error.

Heyy. Could you help me with this.
So I installed LineageOS 17.1 some weeks ago on my G928F Samsung Galaxy s6 edge+. And have a little problem. My phone is stuck in a bootloop. My phone shutdown because it didn't have battery left. I put the phone to charge and when I tried to power on the phone it just went in a bootloop. I tried several things to make my phone come back. The closest I get was that my boot animation started. But it just went off and again in the bootloop. I tried to wipe cache and dalvik cache. I tried to install boot.img file from the custom Rom zip file. Also I tried to change the boot animation but I can't see the /system/media folder. And I don't want to lose my data. Other detail, I don't want to dirty flash LineageOS 17.1 every time my phone shutdown because there's no battery left. Could you help me?(Sorry my bad English, I'm from Spain)
Nevermind
No problem. I already installed the stock Rom. Because some of important things that the stock Rom has the LineageOs 17.1 don't and that way I make sure that I won't have problems again.

Categories

Resources