I've been using multirom without problems for the past week (even loaded webOS and Ubuntu on it). However, today I flashed Franco r47 kernel and after rebooting, the rom selection screen would not display anymore. And instead, it would boot the internal rom immediately after the Google logo.
Checking TWRP, it still has the multirom option under Advanced.
Has anyone else experienced this or knows what I can do?
no one? can't really post this in the multirom thread
I have got the same question, any other solutions?
thunderbolt.dash said:
I have got the same question, any other solutions?
Click to expand...
Click to collapse
I've flashed multirom_v8_n7-signed.zip again and it seems to have fixed the issue. :good:
I just flashed back to MDL stock then upgraded to MF9 and installed TWRP 2.6.0.0 and about half the time when I boot into TWRP it hangs at the initial teamwin screen. I have to reboot by phone 3-4 times to get it load in to TWRP when this happens. Anyone have any ideas what could be the issue? I previously had TWRP 2.5.0.2 installed and never had these issues so I am not sure if its something with the new version of TWRP or possibly an issue with the new firmware.
masterosok said:
I just flashed back to MDL stock then upgraded to MF9 and installed TWRP 2.6.0.0 and about half the time when I boot into TWRP it hangs at the initial teamwin screen. I have to reboot by phone 3-4 times to get it load in to TWRP when this happens. Anyone have any ideas what could be the issue? I previously had TWRP 2.5.0.2 installed and never had these issues so I am not sure if its something with the new version of TWRP or possibly an issue with the new firmware.
Click to expand...
Click to collapse
I thought this was the issue with the 2.5.0.3 that was subsequently pulled. I'm still on 2.5.0.2 (and I guess I'm going to stick with this version as long as I can)
Dude the same thing happened to me. It also sometimes took EXTREMELY long to flash files and wipe dalvick/cache. Like it would literally take 1 minute to wipe dalvick/cache sometimes. I reverted back to 2.5.0.2 and loving it. I don't think I'll switch back anytime soon because it runs perfect and I've literally never had any issues with it!!
jj14 said:
I thought this was the issue with the 2.5.0.3 that was subsequently pulled. I'm still on 2.5.0.2 (and I guess I'm going to stick with this version as long as I can)
Click to expand...
Click to collapse
Joe0113 said:
Dude the same thing happened to me. It also sometimes took EXTREMELY long to flash files and wipe dalvick/cache. Like it would literally take 1 minute to wipe dalvick/cache sometimes. I reverted back to 2.5.0.2 and loving it. I don't think I'll switch back anytime soon because it runs perfect and I've literally never had any issues with it!!
Click to expand...
Click to collapse
Thanks for the info... I'll flash 2.5.0.2 back
masterosok said:
Thanks for the info... I'll flash 2.5.0.2 back
Click to expand...
Click to collapse
just FYI, other people reporting similar issues with 2.6
http://forum.xda-developers.com/showthread.php?t=2262999&page=24
Always had that issue with TWRP. Switched over to CWM, I prefer CWM anyway.
Sent from my SPH-L720 using xda app-developers app
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?
So I installed the latest radio before flashing the odex rom. The Google screen just hangs on boot. Any appreciated help would be welcome.
oxxshadow said:
So I installed the latest radio before flashing the odex rom. The Google screen just hangs on boot. Any appreciated help would be welcome.
Click to expand...
Click to collapse
it could be there up to 15 minutes after flashing a radio
I did it like this, and I assume it would also be a fix for your problem.
I downloaded the 4.4 factory image and used the flash all command from the bootloader. This installed stock 4.4 and new bootloader and radio and everything. Then I installed the latest CWM and then installed the port ROM. Works flawlessly.
simms22 said:
it could be there up to 15 minutes after flashing a radio
Click to expand...
Click to collapse
Not the Google boot animation, just the screen that says GOOGLE in white hangs there. I am not sure what to do, restoring a Nandroid does not seem to help. I still have access to TWRP
oxxshadow said:
Not the Google boot animation, just the screen that says GOOGLE in white hangs there. I am not sure what to do, restoring a Nandroid does not seem to help. I still have access to TWRP
Click to expand...
Click to collapse
i flashed the new radio today, and it hung at google for nearly 10 minutes, then booted.
simms22 said:
i flashed the new radio today, and it hung at google for nearly 10 minutes, then booted.
Click to expand...
Click to collapse
Wow very strange... maybe i will wait it out for a bit. I got so scared that I bricked my nexus 4
simms22 said:
i flashed the new radio today, and it hung at google for nearly 10 minutes, then booted.
Click to expand...
Click to collapse
It finally booted, but has been stuck on the boot animation for 10 minutes now
simms22 said:
i flashed the new radio today, and it hung at google for nearly 10 minutes, then booted.
Click to expand...
Click to collapse
Ok, so here is the problem. I managed to boot into my 4.3 backup, but now every time I reboot the device it takes 10 minutes to boot, just like the situation before. Any ideas? Thank you very much for helping me out btw.
oxxshadow said:
Ok, so here is the problem. I managed to boot into my 4.3 backup, but now every time I reboot the device it takes 10 minutes to boot, just like the situation before. Any ideas? Thank you very much for helping me out btw.
Click to expand...
Click to collapse
im using the new radio, but a modified version so that i can use lte. so its not the full regular .97 radio. but from what ive read about people using the regular .97 radio is that it takes longer to boot.
Will the hybrid .27/.97 work on 4.3, currently on PSX V8.5 awaiting for the good devs there to release there kitkat PSX version.
Dear all,
I followed the CM webpage wiki to install the latest stable ver 10.2 on my S4 i9505.
Heimdall in download mode to install CWM
then boot into CWM to flash CM10.2
It didn't went smooth at start so I did a few times with the Heimdall and flash CM10.2 a few times.
Now everything works except once a while when reboot the Bootup screen hangs there before entering the CM loop logo. It only happen once a while and need to long press power button to reboot. There was once the 2nd reboot also hang there.
Any idea what's the possible cause and how to fix it?
Thanks a lot.
phileasx said:
Dear all,
I followed the CM webpage wiki to install the latest stable ver 10.2 on my S4 i9505.
Heimdall in download mode to install CWM
then boot into CWM to flash CM10.2
It didn't went smooth at start so I did a few times with the Heimdall and flash CM10.2 a few times.
Now everything works except once a while when reboot the Bootup screen hangs there before entering the CM loop logo. It only happen once a while and need to long press power button to reboot. There was once the 2nd reboot also hang there.
Any idea what's the possible cause and how to fix it?
Thanks a lot.
Click to expand...
Click to collapse
revert to stock rom and then flash cwm and then latest cm 10.2 and have fun :good::laugh:
aditya rathee said:
revert to stock rom and then flash cwm and then latest cm 10.2 and have fun :good::laugh:
Click to expand...
Click to collapse
Thank you for the reply. I doubt that can solve the issue..
Could this be related to knox bootloader? I checked I got this void line 0x1 in download mode.
phileasx said:
Thank you for the reply. I doubt that can solve the issue..
Could this be related to knox bootloader? I checked I got this void line 0x1 in download mode.
Click to expand...
Click to collapse
no i don't think that may be a problem
try me method if that does not help then again tell me
aditya rathee said:
no i don't think that may be a problem
try me method if that does not help then again tell me
Click to expand...
Click to collapse
I think I might figured out the problem.
Might because I didn't do properly during rom flash. I forgot to wipe the system when flash cyanogenmod.
Could be because of this. I've switched to a different rom now, so won't be able to verify until decide switch back to cyanogen.
phileasx said:
I think I might figured out the problem.
Might because I didn't do properly during rom flash. I forgot to wipe the system when flash cyanogenmod.
Could be because of this. I've switched to a different rom now, so won't be able to verify until decide switch back to cyanogen.
Click to expand...
Click to collapse
so is everything all right now ??
aditya rathee said:
so is everything all right now ??
Click to expand...
Click to collapse
Yes, the bootup process is smooth, so far so good now. Quite happy with the new rom also
phileasx said:
Yes, the bootup process is smooth, so far so good now. Quite happy with the new rom also
Click to expand...
Click to collapse
well buddy enjoy and if have some problem ask me or pm me
have fun :laugh::good: