Hey guys. Im a new user (posting wise) so I cant post in development, but, I have a few questions.
I just got a Galaxy s4. rooted, installed teamwins recovery, and flashed infamous 6.0.
Att i337 ucuamdl
It flashes fine but at boot it says "System UI has stopped" and upon completing setup i get the "settings stopped" message and kicked back to entering my name. Endless loop.
Ive read earlier in the Infamous thread that this is caused by a lokidoki issue. The dev has stated that lokidoki doesnt need to be flashed anymore, but, I tried flashing it after the rom flash just in case. Still no dice. I've also tried rebooting, reflashing, and flashing lokidoki after and not.
Ive gotten Infamous 3.5 to flash fine but I love the tweaks and lcd density on the 6.0 version. Perhaps Im missing something very obvious?
Any ideas on what I can do to cure this? Thanks for your time guys.
here is the thread and the discussion theyre having.
http://forum.xda-developers.com/show...304792&page=38
fresh wipe everytime.
UPDATE: Flashed tmobile kernal and tmobile lcd density in the infamous 6.0 aroma installer using CWM from Rom manager. everything went great. Even though i have a i337, the tmobile kernal flashed fine . I loki'ed after the rom flash and it booted fine.
Related
Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
I just flashed this rom successfully yesterday. The rom was stable and working, however I wanted to get the hotspot to work. I used a hotspot mod on a previous 4.3 rom, so I tried it again on this rom. I flashed the MDC Hotspot Mod while in Philz Touch 5.18 recovery. After flashing the hotspot mod, I reboot the system and it is stuck at the "Kit Kat" splash screen. I went back to recovery, wiped everything (data reset, cache, davlik cache) and reinstalled the rom and it seemed to work fine. However, I wanted to get the hostpot working so later in the night I reinstalled a 4.3 rom, and now I can not get any rom to work. When I boot up I am not faced with the Galaxy S4 screen saying:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
It will not go to the Kit Kat splash screen, I can get to download mode and recovery mode. I tried completely re-rooting the device, Installing different roms and even a different kernel, but I can't seem to get anything to work. At this point, I just need my phone to work and will use any rom. I don't think this is a fully bricked device because I can get into recovery and download mode. I can live without hotspot for now, just need a working phone. If anyone can advise here or help please reply here or email me at [email protected]. This is my daily driver phone and I need it to work, hopefully it is an easy fix like getting a stock 4.4 kernel? BTW this was a brand new galaxy s4 which came with stock 4.4, so I am not sure if installing 4.3 had an issue with it. Maybe using ODIN to fix the problem, I am not sure. I have successfully rooted many phones including HTC EVO 4G, HTC EVO 3D and Galaxy S4( until now) and have never ran into this issue. Please advice anyone!! Thanks!
RE: S4 Sac Rom Issue Please Help
I ran into a similar problem and my device would not boot. I simply just reflashed clockwork 6.0.4 recovery from Odin and was able to get back into recovery to wipe and reflash a new rom. Hope this helps. Note: I selected PDA in Odin. Here is a tutorial to get recovery back.
http://jellybean-news.blogspot.com/2013/02/complete-guide-to-install-clockworkmod.html
Good luck.
I looked around and couldn't find a solution for this.
I flashed to the GPE ROM upon getting my new S4; everything went smoothly and the ROM worked. However, when I went to activate it with Ting this evening, I learned that I should have activated on stock firmware then flashed the custom ROM. I used ODIN to attempt to restore to stock and I ended up at a screen that said something along the lines of "Firmware upgrade has encountered an issue". I rebooted several times into download mode, but this message appeared every time I tried to boot to either revovery or Android. Conveniently when I went to see the error to provide the exact wording, it booted straight to the GPE ROM.
I still need to restore to a stock ROM though to activate on Ting. What is the process for this (even a link to a thread/post I overlooked will do)?
FlinderMouse said:
I looked around and couldn't find a solution for this.
I flashed to the GPE ROM upon getting my new S4; everything went smoothly and the ROM worked. However, when I went to activate it with Ting this evening, I learned that I should have activated on stock firmware then flashed the custom ROM. I used ODIN to attempt to restore to stock and I ended up at a screen that said something along the lines of "Firmware upgrade has encountered an issue". I rebooted several times into download mode, but this message appeared every time I tried to boot to either revovery or Android. Conveniently when I went to see the error to provide the exact wording, it booted straight to the GPE ROM.
I still need to restore to a stock ROM though to activate on Ting. What is the process for this (even a link to a thread/post I overlooked will do)?
Click to expand...
Click to collapse
Try a factory reset and then install stock ROM
i7vSa7vi7y said:
Try a factory reset and then install stock ROM
Click to expand...
Click to collapse
Could you point me in the right direction for that? Everything I have tried so far seems to fail...
Edit: I got back to the NAE stock rom, but I can't downgrade the modem from NG2 back to NAE...
Edit2: I didn't need the correct modem to activate, I guess. Flashing back to GPE, will update this again.
Final Edit: Once I activated on the stock ROM, everything seems to work perfectly on the GPE. Thanks for the suggestion, i7vSa7vi7y!
Hello, i recently purchased a samsung s5 900w8. I had one before rooted with alliance rom fully customized but i lost it at work in contruction. so i rooted my phone no problem got twrp on it and tried this with philz touch on it no problem. but when i go to install the rom i get ether one or two problems same on both recoverys, also tried different versions for alliance rom. It ether says it installed good i go to reboot and it keeps loop back to recovery when i boot it. Or when it installs and i go to reboot, it says root not detected will you root now (i've selected both options) and it gets stuck at the samsung powered by android logo. I've followed video and article how to's and for this mod and i still am having these problems please help.
tr0nic135 said:
Hello, i recently purchased a samsung s5 900w8. I had one before rooted with alliance rom fully customized but i lost it at work in contruction. so i rooted my phone no problem got twrp on it and tried this with philz touch on it no problem. but when i go to install the rom i get ether one or two problems same on both recoverys, also tried different versions for alliance rom. It ether says it installed good i go to reboot and it keeps loop back to recovery when i boot it. Or when it installs and i go to reboot, it says root not detected will you root now (i've selected both options) and it gets stuck at the samsung powered by android logo. I've followed video and article how to's and for this mod and i still am having these problems please help.
Click to expand...
Click to collapse
I would try installing a different kernel, Adam kernel by wanam works good for me.
http://forum.xda-developers.com/showthread.php?p=55526561
Also I would use ktoonsez latest version of twrp.
http://forum.xda-developers.com/showthread.php?p=53277016
And if all else fails, I would re-download the rom, just in case it is a bad download.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5
I have now tried to install Hyperdrive ROM three times. The first time I had found an old thread written well before much of the S4 debauchery got as thick as it is now and it was definitely the wrong version. I`m on NI1 4.4.2 and downloaded the latest HD rom file (21?) as well as the UI. Followed the instructions to a T and wound up with it stuck on the orange HD/Kit Kat animation for eleven minutes. Finally got it to shut off, wouldn`t reboot. Tried a few times hoping to get it to at least get me in a position to restore a backup. Nope. It would get to the setup procedure but every action on the screen resulted in a "Samsung key lock has stopped working" message. Ended up just installing an older Odin stock rom (4.3), rooting and reinstalling Safestrap and finally getting to load my backup. I~m really interested in the HD rom, so can I ask for (a) what I might be doing wrong and (b) how do I do it correctly? I`m on NI1 again, rooted, using safestrap.