Database Users

[HELP] Every time I reboot, can't get past Samsung Unlocked Custom Screen.

Ok, so I've tried to replicate this with different ROM's and I still get the same result. I have an AT&T i337 Galaxy S4 rooted with Motochopper and installed TWRP 2.6.0 via Goomanager, and tried different google edition roms and stock touchwiz roms. I'll install a rom, get it up and running [install my apps,theme,etc]. Then I'll do a random reboot, and the phone just stays at the Samsung Unlocked Custom screen, for about 5 minutes, then it'll act as if I just installed the ROM i just previously set up as if it was a new setup...I don't understand any of this, am I missing something (are you not allowed to reboot the phone). Any help would be greatly appreciated!
Any questions as to how I install my roms. 1.Boot Into Recovery, 2.Wipe Data format data wipe cache 3.Select Install on TWRP, 4.Choose Rom, 5.Choose Loki-Doki, 6.Let it all install 7. wipe cache and dalvik again 8.boot system 9.Setup android, install apps, themes, 10.Reboot...then it goes back into the Samsung Unlocked Custom Screen, wait 5 mins and I will have to run through the android setup again, as if it forgot that I just installed it. All my apps, themes, customizations are gone.
Happens with ANY custom ROM i choose, google edition OR stock touchwiz roms.
do I need to flash loki doki everytime I reboot? So for example...reboot, go into recovery, flash loki-doki, boot? I've never encountered so much problems with rebooting my phone with any custom roms...
Thanks guys!

i dont use twrp but i've heard things about formatting /data causing problems. maybe someone with more twrp expertise can chime in with a fix.
you could consider some other possible options and if you dont have any success, you may want to consider starting over via stock firmware/odin. when you go through the root process again and twrp is installed in casual (i think 2.5.0.0), stay on it. dont update to a newer release. either that or change custom recoveries. after you've made a backup:
wipe data/factory reset
wipe cache & dalvik
format /system (not /data)
then flash the rom and loki-doki or an at&t loki'd kernel (like ktoosez).
wipe your caches again if you'd like and reboot.
let the phone sit for 5 or more minutes, reboot and just setup your gmail account stuff. not everything. give it another reboot to see if it stuck.

I have been having this same issue as of late, and I am using TWRP 2.5.0.2 and 2.6.0.0. It seems that the only thing I can use is a CM type ROM, I can't get TW to reboot at all after the initial boot. I am factory restoring now and going to use CWM and then try SHOshock 2.1
---------- Post added at 07:18 AM ---------- Previous post was at 06:42 AM ----------
Okay factory restoring through odin and using CWM or OUDHS works just fine. That's what you need to do.

i ran into this problem as well a few weeks back , the problem is twrp , if you do a full wipe where you type in "yes" and it resets to factory defaults , your phone will reboot 1 time only , after that it will get stuck on that screen , only way i found to fix it was to flash back to stock thyen reroot and install twrp again., then never do a full wipe where you have to type "yes"
hope it helps....

No Ax, not more of the SAME questions over and over, please, do not get...But...NO Ax, get outta here....
TRY A DIFFERENT LOKI KERNEL for your device.
WHY LOKI-DOKI?

Not sure if this is entirely the same problem (sorry Ax if this is a duplicate from something else) but for non AOSP ROM's I've tried using loki doki and for every subsequent reboot I get the screen where it says AT&T recognizes an unsupported software on my device.
This has happened on two different ROM's which just caused me to be gun-shy and go back to CM, which allows me to reboot whenever I want with no worries.
For non-AOSP ROM's do I need to loki doki after every single reboot?

the_liv80 said:
Not sure if this is entirely the same problem (sorry Ax if this is a duplicate from something else) but for non AOSP ROM's I've tried using loki doki and for every subsequent reboot I get the screen where it says AT&T recognizes an unsupported software on my device.
This has happened on two different ROM's which just caused me to be gun-shy and go back to CM, which allows me to reboot whenever I want with no worries.
For non-AOSP ROM's do I need to loki doki after every single reboot?
Click to expand...
Click to collapse
No prob, we cool, this is exactly why I stress a loki kernel, why? because you know that kernel works EVERY TIME. I have never used loki doki yet, nor am I about to start, I listed what, some 50 roms in my guide and I flashed every one of them with 1 kernel and 1 only. The wrong kernel does numerous things like, the unsupported screen, hangs at samsung logo, throw you into a bootloop, and in some instances will throw you into the recovery loop. I have seen many when I flashed the roms, but I worked my way out of 3/4 of them with out having to odin back to anything. Now no one get confused, loki kernels for att/verizon, your carriers kernel for all others.

Thanks @TheAxman - tried using the Loki kernel from your guide on both Omega ROM and Mint Jelly. Got a boot loop again on MJ and couldn't get passed the stupid acore process failure on Omega...plus, I had the added benefit of Omega wiping Data after I chose not to.
So.....ended up having to format and reflashed CM.

I got into this issue just now I was trying to wipe it clean cause I'm about to sell it now it's stuck on the Samsung Galaxy S4 screen. I'm running on the Canadian variant I337M. I too was using TWRP. What do I do?

xBeerdroiDx said:
i dont use twrp but i've heard things about formatting /data causing problems. maybe someone with more twrp expertise can chime in with a fix.
you could consider some other possible options and if you dont have any success, you may want to consider starting over via stock firmware/odin. when you go through the root process again and twrp is installed in casual (i think 2.5.0.0), stay on it. dont update to a newer release. either that or change custom recoveries. after you've made a backup:
wipe data/factory reset
wipe cache & dalvik
format /system (not /data)
then flash the rom and loki-doki or an at&t loki'd kernel (like ktoosez).
wipe your caches again if you'd like and reboot.
let the phone sit for 5 or more minutes, reboot and just setup your gmail account stuff. not everything. give it another reboot to see if it stuck.
Click to expand...
Click to collapse
thats most likely his issue.

Slade8525 said:
thats most likely his issue.
Click to expand...
Click to collapse
Seems like it.
---------- Post added at 11:47 PM ---------- Previous post was at 11:44 PM ----------
th3xeroeagle said:
I got into this issue just now I was trying to wipe it clean cause I'm about to sell it now it's stuck on the Samsung Galaxy S4 screen. I'm running on the Canadian variant I337M. I too was using TWRP. What do I do?
Click to expand...
Click to collapse
What device do you have? I337m?

TheAxman said:
Seems like it.
---------- Post added at 11:47 PM ---------- Previous post was at 11:44 PM ----------
What device do you have? I337m?
Click to expand...
Click to collapse
Yup can I use ODIN too?

th3xeroeagle said:
Yup can I use ODIN too?
Click to expand...
Click to collapse
Sorry, was on my phone lastnight, did not see that.
Odin stock, after it finishes do a factory reset. You should be ok after that.
samsung-updates.com

[Q] Factory reset every time ROM update?

Hi!
I use Google edition s4 ROM, and i really like it. But when it receives an update do i have to factory reset everytime? Im on 20150614, with CWM 6,0,4,7.
Id really really appreciate a fast answer
Also, if i wish to switch Kernel from Alucard to Googy-Max, is it ok to Wipe dalvik cache, and then flash kernel?
EDIT: the rom: http://forum.xda-developers.com/showthread.php?t=2557353

bump?

Dirty flashes should be OK, however the ROM thread you linked to should have provided the answer. Regardless, you really should change that recovery to TWRP. Clockworkmod is no longer being supported and people are having difficulty installing some custom ROMs with it.
Wiping cache is fine when changing kernels.

Thanks for the help
Btw. I dont know how to change recoveries? XD. Is it Just using Odin like with cwm? And do i have to remove cwm first / wipe device?

No, u can just flash ur new recovery through cwm

Okay. What is the preferred TWRP? Do you possibly have a link ?
Asking because i cannot find the S4 i9505 on their site?
EDIT: I managed to install it via the App they've made. It is much nicer than CWM. Thanks for the help both of you

Ok ive tried to flash 2 different kernels multiple times now.
Tried Googy-Max, and the phone wont boot android ?
Tried Hulk, and it took forever to boot, then rebooted immediately etc.
Am i flashing kernels wrong?, i did dalvik/cache wipe after the flash

Samsung s4 i9505 bootloop

Every time I flash cyamogenmod rom in clockwork mod or twrp on my s4 I get stuck on boot symbol. I follow instructions but always fail please help.

Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!

JaguarBeast said:
Every time I flash cyamogenmod rom in clockwork mod or twrp on my s4 I get stuck on boot symbol. I follow instructions but always fail please help.
Click to expand...
Click to collapse
1. You have to wipe all (system, data, cache and dalvik) before flash Cyanogen Mod.
2. Boot symbol needs time normally (~ 10 min loading the config).

In what order do you wipe everything ?
I do a factory reset, then wipe cache and finally wipe the dalvik cache

That's it, buddy. With emphasis on "FACTORY RESET".
Let's us know if that worked for ya...

Does it matter what custom recovery you have ?
thundastruck said:
That's it, buddy. With emphasis on "FACTORY RESET".
Let's us know if that worked for ya...
Click to expand...
Click to collapse
Is clockworkmod or team win better ?

TWRP. Certain ROMs will not install with Clockworkmod as the recovery.

I want cyamogenmod 12.1 nightly on my s4
Strephon Alkhalikoi said:
TWRP. Certain ROMs will not install with Clockworkmod as the recovery.
Click to expand...
Click to collapse
I have already downloaded the file and placed it on my internal sd card. Which gapps should I chose ?

Android 5.1.1. Which package you desire is up to you. I personally use the nano package.

Bootloop once again
Strephon Alkhalikoi said:
Android 5.1.1. Which package you desire is up to you. I personally use the nano package.
Click to expand...
Click to collapse
I did a factory reset, wiped the cache and dalvik cache. I flashed cyamogenmod alone and it hasn't booted in 20 minutes. Please help

Let's clarify something. What model number shows up when you enter download mode? Also, is it hanging on the Samsung logo or the boot animation?

Stuck at cyamogenmod logo
Strephon Alkhalikoi said:
Let's clarify something. What model number shows up when you enter download mode? Also, is it hanging on the Samsung logo or the boot animation?
Click to expand...
Click to collapse
It gets stuck at cyamogenmod logo and the download mode model number is Samsung MSM8960

Umm, no. The model number should be GT-I9505 or something similar. Regardless, what GApps package are you using? CM12.1 has trouble with some of the GApps packages and bootloops occur because of it.

Sorry the model is i9505
Strephon Alkhalikoi said:
Umm, no. The model number should be GT-I9505 or something similar. Regardless, what GApps package are you using? CM12.1 has trouble with some of the GApps packages and bootloops occur because of it.
Click to expand...
Click to collapse
I have tried to install cyamogenmod 12.1 alone without gapps but had no success.

Something with your phone isn't right. Either you're missing a step in installing Cyanogenmod, or else your phone's internal storage spaces are not configured correctly. I would recommend starting from scratch, meaning installing the latest stock ROM from your carrier. Once you're satisfied that the S4 is working properly with the stock ROM, install TWRP and then install Cyanogenmod.

Already done that XD
Strephon Alkhalikoi said:
Something with your phone isn't right. Either you're missing a step in installing Cyanogenmod, or else your phone's internal storage spaces are not configured correctly. I would recommend starting from scratch, meaning installing the latest stock ROM from your carrier. Once you're satisfied that the S4 is working properly with the stock ROM, install TWRP and then install Cyanogenmod.
Click to expand...
Click to collapse
I've installed the stock rom(lollipop), rooted my phone and used flashify(Google play app) to download and flash recovery(TWRP). Should I use a cyamogenmod nightly or a stable version ?

That's up to you. Development channel ROMs have a greater possibility of bugs that could stop you cold. Release channel ROMs have fewer bugs but generally lag behind the Development channel in terms of bug fixes and, occasionally, features.
I personally use Optimized CM12.1 from AntaresOne.

Could you recommend a custom rom specifically for s4 i9505 ?
Strephon Alkhalikoi said:
That's up to you. Development channel ROMs have a greater possibility of bugs that could stop you cold. Release channel ROMs have fewer bugs but generally lag behind the Development channel in terms of bug fixes and, occasionally, features.
I personally use Optimized CM12.1 from AntaresOne.
Click to expand...
Click to collapse
So I download the rom zip I want in the root of internal storage, go into recovery and do factory reset, wipe cache + dalvik cache. I choose install and select zip I downloaded. What else did I miss ?
P.S Can you flash gapps later on cyamogenmod if it boots ?

Nothing from what I can see. I simply think that the Cyanogenmod ROM you downloaded didn't like your phone. I've had no issues with Optimized CM12.1, which is why I recommended it.
Re GApps: Yes.

Strephon Alkhalikoi said:
Nothing from what I can see. I simply think that the Cyanogenmod ROM you downloaded didn't like your phone. I've had no issues with Optimized CM12.1, which is why I recommended it.
Re GApps: Yes.
Click to expand...
Click to collapse
Boot loop again XD. I followed the instructions exactly in the link below.
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
Must be bad luck or something.

Acquiring root after Temasek's CM 13 marshmallow install

Hello, I've recently installed Temasek's CM 13 nightly marshmallow build to my bootloader unlock note 3. I'm having a difficult time acquiring root after the install. I've flashed SuperSu to no avail. I've even tried the Aramaic tool method with no luck. Is there anything I can do to get root back on this phone or am I screwed?

Look for SuperSU in the settings menu.
Not sure if you need to turn on developer options for it to appear there or not.
[Edit]Did you install CM with a custom recovery, or with flashfire?
Your post doesn't say one way or another, but if you have an unlocked bootloader you can flash a custom recovery using Odin... meaning that you always have root, so long as you preserve the unlocked bootloader.
Having only a single root (locked bootloader and no custom recovery) and using FlashFire to install a ROM puts you at constant risk of root loss.
.

Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.

cblendz said:
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
Click to expand...
Click to collapse
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.

bftb0 said:
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
Click to expand...
Click to collapse
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.

cblendz said:
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
Click to expand...
Click to collapse
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.

bftb0 said:
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
Click to expand...
Click to collapse
Thanks a lot that was it. Finally got root. I wish CM would bake root in their Roms but all is good now. Thanks.

Questions about bootloader and downgrading on s4, help

Okay, please bear with me as i am new to this flashing custom ROM's game.
I got a intl Galaxy s4 (gti9505) a month back. After reading a lot, i flashed TWRP, and installed a custom ROM (Lineage Optimized 14.1) It runs absurdly great, and i dont think i'll need to replace this OS. BUT if i need to downgrade for whatever reason (im sure i will soft-brick the phone soon, because im testing a lot.) I have some questions:
- Some posts says i can flash back to 5.0 and upper, because the bootloader is the same (???)
- Some posts says i cant flash back to anything below my actual OS (android 7.1) (?????)
- Some posts says i cant flash STOCK ROMS because the bootloader is different. (???????)
- Could i HARD BRICK the phone, wrongly installing stuff via TWRP? or is TWRP functional "forever?''
- I did a big ass backup of android 5.0 before, when i installed TWRP. Can i reflash back to this, at any time?
I'd like to avoid any kind of brick, so help is very much appreciated. Thank you very much for helping a fellow android fan :good:

You can always flash the latest stock ROM to the phone using Odin. There is no stock ROM beyond 5.01 as far as I know.
Yes, you can hard brick the phone by flashing files through TWRP.
How did you create the 5.0 backup?

Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?

neru21 said:
Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?
Click to expand...
Click to collapse
It should not softbrick if you are flashing a custom ROM that is designed for your phone's model #.
If it does softbrick, there are two major causes: a full wipe of the data and cache partitions is required before installing the ROM or a full wipe of the phone (system, data, cache) using recovery is required before installing the custom ROM.