Failed reboot? - Verizon Samsung Galaxy S 4

The issue I'm having is anytime I power off or reboot my device it fails to boot. thw phone will sit on the splash screen. I have tried flashing a new kernel but nothing. I usually have to end up formating internal data and factory reset and reflash to get it to boot.
So any idea why anytime I power off or reboot it won't reboot...........
Sent from my SCH-I545 using xda premium

What rom are you running, you still on stock? I'm running hyperdrive rls 4 and it doesn't like to be rebooted. Seems like it likes to freeze or get stuck in a boot loop. As long as I power the phone off and then back on it's ok. I haven't flashed any other kernels though

blwnv8 said:
What rom are you running, you still on stock? I'm running hyperdrive rls 4 and it doesn't like to be rebooted. Seems like it likes to freeze or get stuck in a boot loop. As long as I power the phone off and then back on it's ok. I haven't flashed any other kernels though
Click to expand...
Click to collapse
It has happened in everything. CM10.1, cleanrom, hyper, synergy
Sent from my SCH-I545 using xda premium

Odined back to stock and that fixed the iasue. Going to reroot and test a few roms to aee if it a possible issue with the loki patch
Sent from my SCH-I545 using xda app-developers app

Related

[Q] no boot after custom rom install

im having a problem here. rooted my s2 with odin, no problems there. i can boot up into my backed up stock rom. i have no problems installing any rom, its just that my phone will boot and load up to the roms boot animation but thats as far as it gets. left the phone for 30 minutes and still doesnt go. Using clock work recovery. not too sure what to do? any thoughts would be appreciated
Do a factory reset from the recovery.
Sent from my GT-I9100 using xda app-developers app
After flashing a rom? I always do before but don't think I ever have after. Will try as soon as I'm home, thanks
Sent from my GT-I9100M using xda app-developers app
Yeah, it's a factory reset, you can perform it at any time.
Sent from the little guy

International (UK) S3 stuck in reboot loop

So I was using an app on the phone and it rebooted.
It now just loops around the initial splash screen, only pulling the battery stops it.
I can get to the recovery menu and did a factory reset but it made no difference.
Not rooted / stock ROM.
I checked the power button and that operates normally.
Is there anything else I can try ?
Thanks
flash a stock rom
If you are not rooted you will have to use Odin and a stock rom for your device.
Sent from my MZ617 using xda app-developers app
thanks, I'll go and read up on odin.
I'd love to know what killed the OS, seems bizarre. I was only doing a crossword
I flashed the correct ROM via odin and its still doing the same thing, splash screen appears about every 5 seconds.
Any more ideas or is it going on a trip to the repair centre ?
non root apps cant really kill the os.
what fw we're you on? that app could have used the exynos exploit if your kernel is one of the older ones.
The FW is Vodafone UK, last had an update at the end of last month.
When it died there was nothing downloading etc, was just running an app I've had on there since I got the phone.
Sent from my Nexus 7 using xda app-developers app
have you done a factory reset from recovery after reflashing the stock ROM?
if yes, send it to Samsung
You my good sir have a brick bug only the great Sammy can help
Sent from my GT-I9300 using Tapatalk 2
Have you tried a custom recovery ie TWRP or Clockwork Mod, and then a custom ROM? Seeing that you did even have it rooted it probably isn't an option but it is an idea.
Sent from my SPH-L710 using xda app-developers app

[Q] Soft Brick on Padlock Screen

I started having this problem after rooting and installing custom rom. It does not matter which rom you install. The only fix I have found is to unroot and return to stock..
Once you root and install your rom the phone works fine, until you reboot. Then it just hangs at the padlock screen. You have to pull the battery and reboot into recovery, format, and reinstall the rom, or go back to stock... HELP!!!!!!
When originally rooting did you let supersu update and select normal?
Sent from my SCH-I545 using xda app-developers app
I did update, not sure about selecting normal. I don't remember seeing that option. What does the normal do?
You need to select normal when updating supersu when you open the app. And what recovery are you using? Have you tried installing goo manager and installing the script which is twrp that has auto loki.
Sent from my SCH-I545 using xda app-developers app
Yea, I installed TWRP from goo.. I will root again and make sure I check normal.
I don't see the Normal setting. Could you point it out..
Ok... I'm a D.A. Both times I rooted, I missed the step of downloading SuperSU and updating it during the Root process. Thanks Black Hat.. Everything should be good now.
You're welcome. Let me know how you turn out!
Sent from my SCH-I545 using xda app-developers app
I spoke to soon.. No Joy.. I managed to get it to reboot one time. Now stuck at Custom Padlock, again.
i'm actually having the same issue. i followed the directions to root using the pre-release kernel and odin. i updated the SU binaries and selected Normal when it asked me. after that i installed the custom recovery using GooManager. now when i install a ROM and reboot it hangs. wonder whats going on. hopefully someone can help us out
trbman said:
i'm actually having the same issue. i followed the directions to root using the pre-release kernel and odin. i updated the SU binaries and selected Normal when it asked me. after that i installed the custom recovery using GooManager. now when i install a ROM and reboot it hangs. wonder whats going on. hopefully someone can help us out
Click to expand...
Click to collapse
You shoul be able to return to stock with one of the methods in the developers forum.
i'm going to try returning to stock than trying everything all over again. i'll report back on how it goes
I've seen another person reporting this issue in the hyper thread. I installed the hyper rom last night and rebooted fine like three to four times no issues but now I'm scared to reboot lol
Sent from my SCH-I545 using xda app-developers app
imablackhat said:
I've seen another person reporting this issue in the hyper thread. I installed the hyper rom last night and rebooted fine like three to four times no issues but now I'm scared to reboot lol
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
that other person was me. haha
I wonder what's going on. If you're missing a step or something. Idk I've installed last night upon release. Rebooted a couple times. Didn't have an issue. When I wiped. I wiped data system cache and dalvik twice. Then installed the rom and rebooted. Restored my apps and settings. Let it settle for a sec and rebooted again. Didn't have any issues.
People that are stuck at padlock screen. You're using the latest twrp autoloki? Can you get back into recovery even though you can't get past padlock. And how long do you wait at the padlock?
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
After rooting and updating supersu and hitting normal. you guys are going back and flashing the normal kernel not prerelease right through Odin?
Sent from my SCH-I545 using xda app-developers app
imablackhat said:
I wonder what's going on. If you're missing a step or something. Idk I've installed last night upon release. Rebooted a couple times. Didn't have an issue. When I wiped. I wiped data system cache and dalvik twice. Then installed the rom and rebooted. Restored my apps and settings. Let it settle for a sec and rebooted again. Didn't have any issues.
People that are stuck at padlock screen. You're using the latest twrp autoloki? Can you get back into recovery even though you can't get past padlock. And how long do you wait at the padlock?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
i installed TWRP using GooManager. it said it was version 2.5.0.2. yes, i can get back into recovery. and the padlock screen stays there indefinitely. i am in the process of odin-ing back to stock so i'm gonna start over and we'll see how it goes. hopefully this resolves it. can't live with Stock TouchWiz.
EDIT---
yes, i hit normal and flashed back to stock kernel from the pre-release.
So it booted fine once. How long were you in it? Did you install anything or configure anything or did you install boot it up. And reboot and notice it won't come back up and hangs?
Because I've been told X posed doesn't work yet even though it's in the rom and if you install it. It'll soft brick and you'll need to dirty flash or reinstall.
Sent from my SCH-I545 using xda app-developers app
trbman said:
i'm going to try returning to stock than trying everything all over again. i'll report back on how it goes
Click to expand...
Click to collapse
Already done that.. No help.. Maybe you will have better luck.
Two people so far with the same issue. Doesn't matter whatever rom?.. ;/
Sent from my SCH-I545 using xda app-developers app
imablackhat said:
I wonder what's going on. If you're missing a step or something. Idk I've installed last night upon release. Rebooted a couple times. Didn't have an issue. When I wiped. I wiped data system cache and dalvik twice. Then installed the rom and rebooted. Restored my apps and settings. Let it settle for a sec and rebooted again. Didn't have any issues.
People that are stuck at padlock screen. You're using the latest twrp autoloki? Can you get back into recovery even though you can't get past padlock. And how long do you wait at the padlock?
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
After rooting and updating supersu and hitting normal. you guys are going back and flashing the normal kernel not prerelease right through Odin?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Done all of that. Rerooted twice! I'm getting frustrated with it. I am now back to stock with no problems.. But yea, I was able to get into recovery after pulling the battery. :crying:

Issues with stuck at custom splash screen??

Ok guys I'm on stock rooted right now. Was on rls 7 hyper and the blue kubatan* rom and when rebooting trying mods it froze on custom splash. So I boot into twrp and wipe dalvik and cache. Reboot from twrp and no issues. Restore to stock no problem. Swap batteries on stock and boom custom splash. Went through wipe in recovery and fine but any reboot from stock tw goes straight to custom splash. Did the kernel get messed up or recovery what? Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Fixed it by odin
Sent from my SCH-I545 using Tapatalk 2
oneandroidnut said:
Ok guys I'm on stock rooted right now. Was on rls 7 hyper and the blue kubatan* rom and when rebooting trying mods it froze on custom splash. So I boot into twrp and wipe dalvik and cache. Reboot from twrp and no issues. Restore to stock no problem. Swap batteries on stock and boom custom splash. Went through wipe in recovery and fine but any reboot from stock tw goes straight to custom splash. Did the kernel get messed up or recovery what? Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I'm having a similar issue. I did a full wipe and installed Hyper Rls 7 and it was working great. I made no changes or flashed anything new, but when trying to reboot it gets stuck at the Samsung Custom screen. I've waited 30 minutes with no change. I wiped with CWM and reflashed the rom with the same results multiple times. Any ideas short of going back to stock would be appreciated.
rickt1152 said:
I'm having a similar issue. I did a full wipe and installed Hyper Rls 7 and it was working great. I made no changes or flashed anything new, but when trying to reboot it gets stuck at the Samsung Custom screen. I've waited 30 minutes with no change. I wiped with CWM and reflashed the rom with the same results multiple times. Any ideas short of going back to stock would be appreciated.
Click to expand...
Click to collapse
I don't think there is another way. I flashed numerous roms in hope of something that would work and no. Phone also ran hot like over 100°+ at idle or screen off and lagged bad when I did get it to boot. After flashing back to stock rerooting and restoring my backup it runs like brand new. Wonder is rls 7 is screwing with something?
Play it safe and go back to stock man
Sent from my SCH-I545 using Tapatalk 2
You must flash your Verizon loki kernel after you flash any rom, not all of the roms are loki'ed, so it will hang at the boot screen.
Thanks you...
TheAxman said:
You must flash your Verizon loki kernel after you flash any rom, not all of the roms are loki'ed, so it will hang at the boot screen.
Thanks you...
Click to expand...
Click to collapse
Doesn't apply to us or rom wouldn't have booted first time after install. And a quick wipe of cache boots it so can't be that issue thanks though
Sent from my SCH-I545 using Tapatalk 2
Wrong, it is a kernel issue, try another. I have seen it boot once, then hang the next. Whatever.
TheAxman said:
Wrong, it is a kernel issue, try another. I have seen it boot once, then hang the next. Whatever.
Click to expand...
Click to collapse
Then why would wipe cache make it work? & no issues before with it. Had to be a mod we tried to install
Sent from my SCH-I545 using Tapatalk 2

I don't know what I did

OK so here's the story. Gonna be as detailed as possible. So I been running 4.3 Meanbean lately, and it's been running great. So I decided to flash Devil kernel and all was well. Well this morning my phone froze so I did a battery pull, wiped cache and dalvik and rebooted into a bootloop. Weird thing is the pick language screen flashes for a split second and back into a bootloop. I've tried 3 different TW ROMs all with clean flashes with the same result. Here's the kicker, AOSP boots just fine. Trying to avoid having to ODIN and CASUAL if possible. I don't know to try next. Thanks in advance to anyone willing to attempt.
Sent from my GT-P3110 using xda app-developers app

Categories

Resources