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
Related
I tried flashing the Droid DNA Cubed Kernel 2.4.2, but forgot to flash the modules before rebooting. When the phone loaded up, all I got was a black screen with a title bar that would restart when I tried to unlock. I then restarted, flashed the modules, and I continued to get the same black screen. I even tried flashing back to the stock kernel with no luck. The only thing that fixed it was doing a factory reset. I had rooted stock with an unlocked bootloader. I didn't see mention of a required factory reset, so what went wrong? Thanks.
I'm not sure what went wrong, and factory reset is not required.
How did you flash the kernel?
I flashed the boot.img from fastboot, then installed the modules in TWRP after the blackscreen.
StormChaser46 said:
I flashed the boot.img from fastboot, then installed the modules in TWRP after the blackscreen.
Click to expand...
Click to collapse
That's normally what I do but I flash the modules before booting, which is how it should be done.
Exact same thing happened to me. I did the factory reset and started from the beginning again. It really scared me but now I have actual root access with superSU having no issues. So much happier now.
Anyways, the point is. If you mess that step up, just factory restore and do it again... The right way lol
Sent from my HTC6435LVW using xda app-developers app
Just flashed back to stock kernel from Flash Image GUI because I kept getting crashes/restarts on cubed, and no black screen this time. Not sure what the problem was, just hope it doesn't happen again lol.
StormChaser46 said:
Just flashed back to stock kernel from Flash Image GUI because I kept getting crashes/restarts on cubed, and no black screen this time. Not sure what the problem was, just hope it doesn't happen again lol.
Click to expand...
Click to collapse
So you did a factory reset and tried cubed again but still didn't work?
It did work after a factory reset, but I got crashes/reboots out of nowhere. I saw other people were also reporting occasional crashing, so I'll stick with stock til it's a little more stable.
Understandable, I get a random hangups every other day or so and it restarts... But the pro's outweigh the cons imo. But I agree with you as well .
Coming from a DX, I got used to random reboots here and there after rooting hahah
Sent from my HTC6435LVW using xda app-developers app
I've been trying to load a new rom onto my fascinate sch-i500v for a few hours now. I previously had a 4.1 build (milestone I think) and cwm 4.0.1.0 installed. I've tried every rom from cw10 to hellybean to avatar and they all do the same thing. I wipe the cache, factory reset. Then installed from the zip file. At this point, the install starts to initiate, but the phone suddenly reboots and after a few seconds tries to load up the old rom (unsuccesfully, hence why I said I'm seeing the "initiating swagger" load screen forever)
Yesterday, I did this exact upgrade successfully to my other fascinate sch-500 (no v on the end for that one, not sure if that makes any difference).
That one rebooted suddenly as well, but it went back into the clockwork recovery and completed the install without a hitch.
Anybody have any suggestions? I'm sort of a noob, but I have flashed over ten phones...
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. i fugured that was what I needed to do, but I was afraid of how complicated it would be. LMFAO, it was pretty simple!
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
Every time my phone dies, or I turn it off or I reboot, no matter what 4.3 rom I'm using, it stays on the boot animation until I either pull battery or hold power to turn off. I've flashed, reflashed, dirty flashed clean flashed (I format the system as well) I've tried CM10.2, PacMan, and Beanstalk and all three have this issue. I haven't read anywhere that someone else is having problems like this. Please advise!:fingers-crossed:
Aiekazie said:
Every time my phone dies, or I turn it off or I reboot, no matter what 4.3 rom I'm using, it stays on the boot animation until I either pull battery or hold power to turn off. I've flashed, reflashed, dirty flashed clean flashed (I format the system as well) I've tried CM10.2, PacMan, and Beanstalk and all three have this issue. I haven't read anywhere that someone else is having problems like this. Please advise!:fingers-crossed:
Click to expand...
Click to collapse
I have the same problem. Can't seem to figure it out either. The only way to fix it is to reflash. At first I thought it was an app or setting but after a clean install and boot I reboot without going through the setup but it still would not reboot.
Same
I'm having the exact same issue and as you have, I've tried everything I can think of.
Ive tried flashing CM 10.2 + GAPPS, just CM10.2, 3 different types of Google Edition Roms and in every case the initial boot is fine... It boots and works perfectly, however on first reboot, it wont boot back up.
It just sits on the SGS4 logo, have left it for 25 minutes.
I would really love to know how to fix this. The only way to get it working after it has been restarted once is to delete cache, dalvik AND data...
Cache and Dalvik don't fix it.
figured a little bit...
Well now that I've flashed it using TWRP instead if CWM touch, it does reboot back up. However with TWRP flashing I'm getting reboots while typing.
Aiekazie said:
Well now that I've flashed it using TWRP instead if CWM touch, it does reboot back up. However with TWRP flashing I'm getting reboots while typing.
Click to expand...
Click to collapse
I used Goo manager to install TWRP. Then used that to install the latest nightlies and latest gapps - 0813. So far so good!!
anandlal said:
I used Goo manager to install TWRP. Then used that to install the latest nightlies and latest gapps - 0813. So far so good!!
Click to expand...
Click to collapse
Gonna give this a try I'll post back.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Aiekazie said:
Gonna give this a try I'll post back.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Click to expand...
Click to collapse
If this works can you post a quick overview of what you did...
Because I've tried reinstalling TWRP and it didnt seem to help, but happy to try again if it works for you!
All is good!
Been running it since I installed using the method i mentioned above.
The ROM is running smoothly with no issues or reboots. I did reboot it a couple times to verify that it is booting properly.
Alright...I installed TWRP through Goomanager, when I did this I selected the manual option and booted into CWM and performed a BACK UP first...flashed the TWRP.zip file that goo downloaded for me. Version 2.6.0.1 I think it was? I rebooted into recovery and found it successfully flashed TWRP, I went into the wipe options and chose data cache system and dalvik, backed out and chose install and reinstalled Cm10.2 and GApps. I'm able to reboot and all but I'm still finding reboots here and there....I was able to go 18hrs on battery (awesome for stock settings!) And without a single reboot.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Yup that's the same for me. Random reboots here and there but overall very solid with great battery life.
Can't wait for more nightlies.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Ya know. Now that I've let 8.14.2013 nightly settle in I havent had a reboot in quite some time. I might stick here til some major change logs come..
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Try This Rom
[Rom][JellyBean][4.3][BeanStalk Build 4.3.05][updated 8.19]
I have Flashed it with no issues :fingers-crossed:
hope this will help you
Yeah, I posted in the dev thread, that particular one gives me reboots while typing if the vibrate on key press is on. Other than that it was working fine. I'm still digging the cm 14th nightly.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Aiekazie said:
Yeah, I posted in the dev thread, that particular one gives me reboots while typing if the vibrate on key press is on. Other than that it was working fine. I'm still digging the cm 14th nightly.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Click to expand...
Click to collapse
Yup same with me. Kinda surprised that there have been no more Nightlies for this though, The Note II has one updated to 18th.
I'm sticking with this.
My phone has begun draining rapidly. When it is plugged in, while booted up but screen off, it gets very hot and doesn't charge. If I turn it off, it will charge. Could this be Rom or kernel related or is something wrong with my phone or battery?
Sent from my GT-p511x
Best way to tell would of course be to flash back to Stock firmware and see how it does.
That is what i would do. And i would flash the Android 4.1.2 Stock i777ucMD8.
U could also get Root after Stock and install the BetterBatteryStats app to help ya see what is using ur battery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I tried to flash cooked but it wouldn't boot. I know it was a good download because I'd flashed it before. It also won't boot AOCP 7. In addition two nandroid backups failed to restore. Strangely, by flashing partitions separately I was able to get CM11 to restore even though it said system failed. I'm confused and frustrated right now. I'm going to flash RenderBroken's nightly tomorrow and see if I still have problems.
Btw, bbs hasn't been working for me either. It's been giving me weird numbers that don't make sense like 19 hours since boot when it's been around 2.
I wonder if it's just time for me to get an S4...
Sent from my SGH-I777 using xda app-developers app
sharonbw said:
I tried to flash cooked but it wouldn't boot. I know it was a good download because I'd flashed it before. It also won't boot AOCP 7. In addition two nandroid backups failed to restore. Strangely, by flashing partitions separately I was able to get CM11 to restore even though it said system failed. I'm confused and frustrated right now. I'm going to flash RenderBroken's nightly tomorrow and see if I still have problems.
Btw, bbs hasn't been working for me either. It's been giving me weird numbers that don't make sense like 19 hours since boot when it's been around 2.
I wonder if it's just time for me to get an S4...
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Do not give up the s2 i777 is a great phone try to solve problems and be happy with your device.
Sent from my SGH-I777 using xda app-developers app
What ROM were you using before? this happened to me after coming back from Kit-Kat. Id recommend flashing a CM-10.2 nightly. It could just be the battery. Maybe even the charger port! Id flash a new ROM first though.
I am on CM11. I wiped my phone but ended up just reinstalling the nandroid I had made so am still on CM11. Interestingly, the problem is not happening today. I believe it may have been a rogue app or process. I'm hoping the phone/battery is still good because I'm broke! Lol
Sent from my GT-p511x