Related
Hey ya'll. I'm a NOOB who's currently using CM 7.0.3.1-Supersonic. My phone was randomly rebooting and I was told switching the kernel may alleviate that issue. Based on forum recommendations, I downloaded a SavageZen kernel - SavagedZen-2.2.1-CFS-HAVS-signed.zip MD5 thinking it would correct the problem. I must've selected the wrong kernel or something because my phone is stuck at the boot animation screen and I cannot get beyond it. I do have Titanium backing up my stuff nightly. I just really need some help.
Thanks in advance for your insight!
Cristal
MsCristal said:
Hey ya'll. I'm a NOOB who's currently using CM 7.0.3.1-Supersonic. My phone was randomly rebooting and I was told switching the kernel may alleviate that issue. Based on forum recommendations, I downloaded a SavageZen kernel - SavagedZen-2.2.1-CFS-HAVS-signed.zip MD5 thinking it would correct the problem. I must've selected the wrong kernel or something because my phone is stuck at the boot animation screen and I cannot get beyond it. I do have Titanium backing up my stuff nightly. I just really need some help.
Thanks in advance for your insight!
Cristal
Click to expand...
Click to collapse
It just keeps boot looping?
If so, and all of your information is backed up, it would probably just be easiest to formal all (system, data, boot, cache, dalvik cache) and then reflash the rom and kernel.
easy step is to restore NAND, if you don't have that, get into recovery either via ADB or by power button and volume. Once in recovery just flash the ROM overtop itself or if you have the correct kernel flash that
MsCristal said:
Hey ya'll. I'm a NOOB who's currently using CM 7.0.3.1-Supersonic. My phone was randomly rebooting and I was told switching the kernel may alleviate that issue. Based on forum recommendations, I downloaded a SavageZen kernel - SavagedZen-2.2.1-CFS-HAVS-signed.zip MD5 thinking it would correct the problem. I must've selected the wrong kernel or something because my phone is stuck at the boot animation screen and I cannot get beyond it. I do have Titanium backing up my stuff nightly. I just really need some help.
Thanks in advance for your insight!
Cristal
Click to expand...
Click to collapse
I know this may be a dumb question, but how would I do that if it's stuck in an endless loop? I don't think I can get to bootloader.
MsCristal said:
I know this may be a dumb question, but how would I do that if it's stuck in an endless loop? I don't think I can get to bootloader.
Click to expand...
Click to collapse
Hold down the volume down button (with the phone off) and press power while still holding the volume button down until you see the bootloader.
pull the battery, when you put it back on hold power + vol -
then select recovery
MsCristal said:
I know this may be a dumb question, but how would I do that if it's stuck in an endless loop? I don't think I can get to bootloader.
Click to expand...
Click to collapse
Thanks. I did manage to figure that part out. I also downloaded the most recent tiamat kernel and flashed it. Still stuck at the boot screen.
are you sure you have ROOT and full NAND unlock? did you try flashing the ROM overtop itself after you got into recovery?
MsCristal said:
Thanks. I did manage to figure that part out. I also downloaded the most recent tiamat kernel and flashed it. Still stuck at the boot screen.
Click to expand...
Click to collapse
No, I did not try flashing the ROM over itself. I'm sorry for being such a "girl." LOL. Should I try doing that too?
When you flash a kernel you generally have to do a full wipe. I recommend Calkulins format all zip file.
Then flash the ROM, then flash the kernel, then flash GAPPS.
If you get stuck in a boot loop while flashing a kernel make sure you didnt download a wrong kernel(like an incredible kernel). I have done that and didnt realize it said INC instead of EVO and got stuck at the boot screen.
Thanks for your help. I had to re-flash my ROM, but I'm back in business!
Hi,
I flashed the google edition rom a few weeks ago, all was working fine. This morning, I decided to flash a stock rom from sammobile (was this a bad idea)? I used CF autoroot and twerp custom recovery. It failed. So wiped everything, reflashed the google edition rom, but when I reboot the phone it gets stuck showing "Samsung galaxy s4" white text.
To boot it again i have to wipe data, cache and dalvik, then reflash the ROM, then qipe cache and dalvik, then it reboots. But when I turn it off then on again the whole process starts again.
Can anybody tell me what I'm doing wrong? This is the same ROM that worked faultlessly for weeks...
Thanks
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
richard2311 said:
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
dickson123 said:
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
Click to expand...
Click to collapse
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
mobileguynz said:
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
Click to expand...
Click to collapse
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
dickson123 said:
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
Click to expand...
Click to collapse
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
mobileguynz said:
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
Click to expand...
Click to collapse
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
dickson123 said:
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
Click to expand...
Click to collapse
If you flashed the latest stock ROM it maybe be one with Knox and that has a secure boot loader and kernel secure Selinux Knox stops you from modifying and installing.
Try using ausdims v16 kernel or wadams Adam kernel for stock roms. Note when I flashed the last ROM waited 10 minutes and had do a wipe and reset for it to boot see last pages for discussion http://forum.xda-developers.com/showthread.php?t=2250824
http://forum.xda-developers.com/showthread.php?t=2250824
So i have the I337m, canadian model S4 on Bell Mobility network, and I"m running SlimRoms with 2.5.0.2 twrp recovery.
Every other reboot, the phone gets stuck on the splash screen, I have no problem to go into recovery mode or anything, this is simply a problem when rebooting and gets stuck on the "Galaxy S4" screen. Here's what I've tried, tried both with TWRP and CWM and TWRP seems better, I don't get stuck on the splash screen as often as CWM. I've reverted back to the "stock ROM" and rerooted and loaded the TWRP recovery, and while it seems better at first, it slowly gets stuck more and more at the splash screen.
I'm running out of ideas, no knowing what do to to improve this problem...
Anyone else having this problem? I'm positive this is not a "ROM" related problem but a recovery problem, yet maybe it's just my phone that's being the problem.
JP
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
jproy12 said:
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
Click to expand...
Click to collapse
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
jd1639 said:
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
Click to expand...
Click to collapse
I'm not getting boot loops actually, I get stuck on the "splash screen" and when I hold the "power" button for +/-10sec it reboots and most of the time it's fine.
When I install any roms, I always do a factory reset... So I doubt it's that
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
h_khan said:
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
Click to expand...
Click to collapse
Yea, I had done this before, but I'm giving it another shot tonight to see if it'll fix my problem for good...
Still having the same problem... Running out of ideas
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Talabis said:
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
Click to expand...
Click to collapse
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
h_khan said:
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Click to expand...
Click to collapse
I've been running Slim for a year now, and won't go back to anything else, it's stable and fast, I doubt it's a ROM problem, but a recovery problem.
i think you're right. a problem with the recovery makes more sense.
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
Click to expand...
Click to collapse
So it seems like this wasn't exactly my problem... I've reverted back to stock and I'm doing a couple shutdowns and reboot and see if I still get stuck at the splash screen.
I've been doing reboots and shutdowns on the "stock" rom and "stock" recovery, and all is good, so I can rule out the fact that it's the phone and it's hardware issues...
Now, just need to figure out the actual problem
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "booscreen"?
Click to expand...
Click to collapse
So far so good. I rebooted many times since I made the post in this thread. Haven't got stuck on the splash screen yet.
I'm still having the problem, being on either the TWRP, CWM or Philz recovery, so I'm really not sure what it could be. I'm on the latest modem and still have the problem, is none else having these issues?
I'm getting annoyed and really want to get this fixed.
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
emckai said:
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
Click to expand...
Click to collapse
I've never seen anyone really mentionning this for the Galaxy S4 from my numerous searches...
jproy12 said:
I've never seen anyone really mentionning this for the Galaxy S4...
Click to expand...
Click to collapse
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
emckai said:
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
Click to expand...
Click to collapse
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
jproy12 said:
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
Click to expand...
Click to collapse
Yeah, but I don't think its a big deal anyway. How many times do you turn off your phone and turn it back on in a day?
Hello,
I know this has been asked dosens of times, but Im all out of guesses, after many searching.
I was running Pacman, and I wanted tt install a new kernel. I installed the JSS faux kernel. however, the colours went very weird, so I installed the cm10 colour fix.
Well, that didn't work out. It now stays stuck on the google logo, when booting up the phone. I tried going to factory reset in recovery, installing a fresh install of pacman, but I am still stuck on google screen....
does anyone knows what I gotta do? I'm stressing out..
thanks
Nielos said:
Hello,
I know this has been asked dosens of times, but Im all out of guesses, after many searching.
I was running Pacman, and I wanted tt install a new kernel. I installed the JSS faux kernel. however, the colours went very weird, so I installed the cm10 colour fix.
Well, that didn't work out. It now stays stuck on the google logo, when booting up the phone. I tried going to factory reset in recovery, installing a fresh install of pacman, but I am still stuck on google screen....
does anyone knows what I gotta do? I'm stressing out..
thanks
Click to expand...
Click to collapse
have you tried wiping data then reflashing pacman?
Seems like an issue with the kernel. Flash stock kernel. If you are unable to do it. Download the toollkit and flash stock image. Be warn you will lose all ur data in the phone. Yes all of it.
Sent from my Nexus 4 using Tapatalk
Hello there!
I wanted to try KitKat on my rooted stock JB G2, so I downloaded a modified 20D ROM and installed it on my device. However, I've been having problems: phone randomly rebooting, accelerometer not working since yesterday (a reboot or Dalvik wipe wouldn't fix it)... so I decided to start clean.
I went to TWRP and did a full wipe. I checked every box and wiped. My intention was to restart the phone, copying a ROM, going back to recovery and installing the ROM.
However, the phone won't boot. It gets stuck at the LG logo with a blinking LED (green/blue).
I can get to TWRP and to download mode, but haven't been able to go back to the system itself.
I've read about TOTs, kdzs, flashtools... But I don't have a clear idea of what should I do.
Could anybody give me a hint? Maybe saying "Follow this tutorial, but using this file instead", or something like that.
My main concern was that the phone could run out of battery, but I've checked that while in TWRP it's charging.
Thanks in advance.
Did the ROM zip flash completely? You could try installing a 4.4 kernel (like Dorimanx's) and also the kk baseband
Sent from my LG-D802
linjes said:
Did the ROM zip flash completely? You could try installing a 4.4 kernel (like Dorimanx's) and also the kk baseband
Sent from my LG-D802
Click to expand...
Click to collapse
Thanks a lot. I finally got it up and running following this guide: http://forum.xda-developers.com/showthread.php?t=2687929
reycat said:
Thanks a lot. I finally got it up and running following this guide: http://forum.xda-developers.com/showthread.php?t=2687929
Click to expand...
Click to collapse
No problem, and thanks for the link! I once d the same problem but I solved it from the recovery itself. This seems much faster though
Sent from my LG-D802
D802 bootloop
hi guys,
my phone get stuck at LG logo after installed cloudyflex 2.2 from 4.4.2 (D802).
i do clean flash with full wipe but after want to reboot system there are asking to install SU. And i just follow but after waiting 15 min my phone still bootloop. Please help me to find for solution for this..tq