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] Can't flash any ROM - help?

Hi there.
I have a Samsung Galaxy S4 GT-I9505 and I’m using TWRP Recovery 6.0.4.4.
I tried to flash a nightly-version of CyanogenMod (cm-10.2-20131101-NIGHTLY-jfltexx.zip). I did a Factory Reset before flashing, TWRP said it had been successful.
When I tried to boot my phone, I can see the "SAMSUNG GALAXY S4 GT-I9505" logo, here it got stuck. I can not see the cyanogen boot animation.
Though MD5 hashes and file sizes are ok, I tried another ROM: SuperNexus http://forum.xda-developers.com/showthread.php?t=2407616
Here it was exactly the same. My device gets stuck even before the boot animation.
I was so desperate, that I tried to format my complete internal storage. Flashing the ROMs was successful again, I could boot both ROMs CM and Supernexus then. But after I turned off my device I can't boot any more. Again I can not see the boot animation.
I have already tried it with PhilZ and CWM. I flashed them using my current recovery.
Any advice?
I am sorry for my English, if you need more detailed explanation, please ask. I tried to describe everything as detailed as I can.

Can you get into download mode? You may have to flash a stock ROM to get it to working again. Was the phone previously rooted?
And are you currently on a stock ROM or coming from a custom ROM?

Yeah, I can get into Download mode.
Well, I am not sure what ROM I'm currently using since I wiped everything. Previously I had FoxHound ROM, samsung-based pre-rooted custom ROM.

Have you tried flashing a custom Kernel?
Sounds like what I had when I tried to flash a TW Kernel for a AOSP ROM.
If you can't get into recovery, go into download mode and flash the latest CWM. Got my phone working.

FoxHound ROM installed a custom Kernel, "Ausdim Kernel" I think.
Now I have CWM 6.0.3.2 from here: http://forum.xda-developers.com/showthread.php?t=2279579
Not sure if this is the latest version ... I can't find an Odin-flashable *.tar
Anyway it doesn't work too. This recovery can't even flash CM, it gets stuck at "opening update package ..."

Sorry its a bit late.
http://forum.xda-developers.com/showpost.php?p=46312260&postcount=149
Use them. This may help as a tutorial to follow loosely but that was for non working WiFi.
http://forum.xda-developers.com/showpost.php?p=47076192&postcount=6

soft brick phone flashing rom

I downloaded twrp and CM 10.1 CR2 for my MK2 4.3JB galaxy S4.
I made nandroids on the extra then went in used the wipe feature in twrp then loaded cm and gapps. Worked great and I love the ROM.
Went to put back nandroids. Used the wipe feature again then restored nandroid. Bootleg and stuck on the yellow sprint screen. Tried to flash Odin .tar and it started with a ton of FC then said something about data partition.
I had no choice but to factory wipe and I wanted to keep all my internal stuff. The stock to CM worked fine but just doing general wipe did not work to restore my nandroid.
The CM I noticed is 4.2.2. Is this an issue going back to stock 4.3 nandroid ?
I'm restoring the phone completely so it's fresh out of the box then rooting then using twrp to try to get back my old nandroid.
What did I do wrong in the process that caused it to stall on the yellow sprint screen ?

Now that I think about it I did probably a "dirty" flash since. I did not completely factory wipe the phone just the dalvik cache, cache and the last item on TWRP.

Once you go to 4.3...aka MJA or MK2 you cannot go backwards. So that may have been your issue. Try stayin with 4.3 or up
If you say "Please"... be sure and "Hit Thanks!!!"

OK I tried again after wiping, flashing 4.3, rooting, setting up TWRP.
I wiped everything and when I made my nandroids I checked ALL the boxes. I'm currently on CyanogenMod which works fine but I cant restore my nandroid. I wiped all then used restore from my SD card. I have twrp 2.6.3.0 I think.
I'm still getting stuck on the sprint screen. Help !

Don know about checking everything?? I make sure that SE Linux is checked (i use philz) and then save to SD. Have had zero issues so far and I bounce from 4.3 TW to 4.4 AOSP daily. Sorry I've never used TWRP so I cannot begin to help troubleshoot.
If you say "Please"... be sure and "Hit Thanks!!!"

I just want to make sure you are not wiping before you create the nandroid backup. I reread your post and it was unclear. When creating the backup you should not wipe first. Next, when switching between AOSP and Touchwiz things can get tricky. Usually a failure to boot is after doing a nandroid is caused by the kernel not being correct for the rom installed. It would probably be best to keep an AOSP kernel and a Touchwiz Kernel on your sdcard so you can flash it after you restore the nandroid backup to ensure the proper kernel is in place.
Secondly, it was mentioned above that you can't go back to 4.2.2 after going 4.3. This is actually incorrect. You cannot flash a stock tar of an older 4.2.2 rom through odin if you have the MJA (AKA Knox bootloader). You can however flash a 4.2.2 rom using recovery since it does not attempt to change the bootloader.

cruise350 said:
I just want to make sure you are not wiping before you create the nandroid backup. I reread your post and it was unclear. When creating the backup you should not wipe first. Next, when switching between AOSP and Touchwiz things can get tricky. Usually a failure to boot is after doing a nandroid is caused by the kernel not being correct for the rom installed. It would probably be best to keep an AOSP kernel and a Touchwiz Kernel on your sdcard so you can flash it after you restore the nandroid backup to ensure the proper kernel is in place.
Secondly, it was mentioned above that you can't go back to 4.2.2 after going 4.3. This is actually incorrect. You cannot flash a stock tar of an older 4.2.2 rom through odin if you have the MJA (AKA Knox bootloader). You can however flash a 4.2.2 rom using recovery since it does not attempt to change the bootloader.
Click to expand...
Click to collapse
I don't think I wiped before making the nandroid, but I'm not sure. I have the Sprint GS4, and the nandroid was a 4.3 (Dec 2013) firmware.
Can you help me out here, I'm really lost. Do I need to flash a Touchwiz kernel on top of the nandroid through TWRP (flashing multiple zips) ? Where do I get the kernel ?

Made a nandroid of my Cyanogen Mod. Wiped phone and restored Cyanogen Mod nandroid. No problem. Worked fine. Just the original that I made is not working.

mikeprius said:
Made a nandroid of my Cyanogen Mod. Wiped phone and restored Cyanogen Mod nandroid. No problem. Worked fine. Just the original that I made is not working.
Click to expand...
Click to collapse
There are a lot of people that have had problems switching between Cyanogen Mod and Touchwiz using nandroid restores. It usually is the Touchwiz kernel not being restored when restoring the backup. When you boot up, you won't get past the initial boot screen. If this happens, you should just have to reboot back in to recovery and flash a TW kernel then reboot or after your restore your nandroid backup, just flash the TW kernel before rebooting. Look in the Android Development section for a custom TW kernel or you can try this kernel that unkownforce posted from his Triforce rom: http://www.androidfilehost.com/?fid=23321874045862620

cruise350- You are my hero. The nandroid DID come back and is working This has racked my brain all night and I am so so glad that I got my nandroid back.
I do have a few more questions:
1. The Wifi is not working ?
2. It appears that my Sprint is on 3G, and not going to 4G LTE ? Do I need to do something with this ? I also am getting errors trying to update my profile and PRL.
3. Is a custom TW kernel always required to be used, is there a stock Samsung TW kernel ?
Thanks a TON ! I couldn't figure out it for the life of me. Other than that I have been enjoying Cyanogen Mod. Using goomanager it looks like some CM versions are not flashable with TWRP and only by Clockworkmod.

on some roms i know that if you don't use the kernel that comes with it the wifi doesn't work. maybe try stock? in your mobile network settings, is your preferred network type "lte/cdma/evdo'? i'm sure there's a stock kernel on the forum somewhere.

It was set on global, so I switched it thanks for the heads up. Wifi still out of commission though. Once I get this set up, I'm eager to try new ROMs. I'm still on the fence about TWRP though. It's a nice interface vs. Clockwork, but it seems like most files out there cater more to CWM

mikeprius said:
It was set on global, so I switched it thanks for the heads up. Wifi still out of commission though. Once I get this set up, I'm eager to try new ROMs. I'm still on the fence about TWRP though. It's a nice interface vs. Clockwork, but it seems like most files out there cater more to CWM
Click to expand...
Click to collapse
i can't really give advice on that since all i've used is cwm. idk what kernel that one is, but i think it now comes with kt-sgs4. maybe the one from before? i looked around and i couldn't find a stock kernel by itself for mja or later. if you extract the boot.img from a stock rom the kernel and ram disk are in there. how easily you could screw up your phone doing that is beyond my experience, so maybe try a different custom kernel and wait for somebody else's advice for the boot.img thing?

Wifi AND booting (as @cruise350 mentioned) are almost always a kernel issue.
What ROM are you actaully on?
How did you get there, your nandroid?
What kernel are you now using and how did you flash it?
Have you tried gonig into settings, turning off wifi, wait a moment and then trying to turn back on?
Sounds like you should flash a stock(based) TW ROM and go from there. That often clears up connection issues.
Also might want to set your 'network type' back to automatic.
As for CWM and TWRP both are superb just make sure you follow the ROM developers recommendation as to which to use. (Philz is a CWM based recovery). There are .tars and zips of the latest of each here in these forums.
Please spend some time here reading, searching and then reading some more. You will find all the answers to your questions and it will give you a huge grasp of what is what and how to do things properly.
Good luck.

I am currently on the L720VPUEMK2 ROM 4.3 for Sprint. Android version 4.3 (Dec 2013 update).
I used TWRP 6.2.3.0 to flash Cyanogen Mod 10.2 nightly version (not sure if matters specifically which one).
My kernel was from TriForceKernel on the link above. It says 3.4.0-gb72521e-dirty. I flashed it after I flashed my recovery after wiping the device including internal data, cache, dalvik cache via install .zip in TWRP then rebooted.
The phone has loaded up but does not seem to be toggling between 4G LTE and the wifi is busted. I checked my nandroid and it says there is a boot file in it.
When I created my nandroid, I checked all the boxes, then slide the toggle which was supposed to create a back up for all 6 segments. I'm not sure why the boot.img isn't loading, it's part of the recovery that saved it. The settings seem to be as I left them....there are just some little things that are problematic.
I have a boot.emmc and boot.emmc.win both that are part of the nandroid recovery that has been flashed yet it gets stuck on the splash screen.

Well I'd just wipe and try any one of the FIVE TW ROMs that have been dropped in the last 7 days.
Trying to fix whatever is your issue could take hours or days.
Wiping completely (as per whichever dev's ROM you choose), installing said ROM, and starting from scratch will assure you phone works AND give you the best chance to get stuff working.
I dirty flash, restore and install ROMs all the time.
However When I absolutely want to know I'll have a good working ROM I clean flash. Wipes, setup, let Google restore apps, debloat restored (and stock apps!) then setup each setting and app to my liking. Titanium comes in real handy - after all my apps are re-downloaded I can selectively restore data to those that need it (Kindle, newsreader, SMS, Call Logs etc.)
Try that - installing clean new ROM and see what happens. Then go from there. Or don't and spend another couple days without a completely working phone.

[Q] E:failed to mount /sdcard

Having some issues getting a recovery to be flashed on this new device, I am not use to a phone that when rooted doesn't have some stock recovery that actually works. And by that I mean, allows me to install zip from file. All I get is the option to reboot, flash from adb, install from external, wipe factory reset, wipe cache, and install from cache.
Sorry if this has been asked a few times before, but with my searching I didn't find any one answer that solved my problem. Tried flashing a recovery via odin but it said Auth fail for the recovery. Going to try a few other things and see what I can come up with.
Thanks in advanced!

What recovery are you trying to flash? I believe the closet thing we have to a custom recovery is safestrap. Is that what your trying to install?

Ysosrslawl said:
Having some issues getting a recovery to be flashed on this new device, I am not use to a phone that when rooted doesn't have some stock recovery that actually works. And by that I mean, allows me to install zip from file. All I get is the option to reboot, flash from adb, install from external, wipe factory reset, wipe cache, and install from cache.
Sorry if this has been asked a few times before, but with my searching I didn't find any one answer that solved my problem. Tried flashing a recovery via odin but it said Auth fail for the recovery. Going to try a few other things and see what I can come up with.
Thanks in advanced!
Click to expand...
Click to collapse
It sounds like you flashed philz touch recovery witch will not work with the VZW S5 you need to flash SafeStrap Recovery. You might need to Odin back to stock and re root your device to get it back to normal first.

chrisbass said:
What recovery are you trying to flash? I believe the closet thing we have to a custom recovery is safestrap. Is that what your trying to install?
Click to expand...
Click to collapse
I didn't flash anything when I first started rooting the phone I just used towelroot, then when the OTA messed it up I went and did the NCG to NE9 method using odin and towelroot. But every time I went into recovery, it has been the same. It wasn't until I used the toolkit from the forums that installed safestrap and busybox did I actually get a different recovery, but even if I reboot into recovery it still takes me to the stock one first and then on reboot i can access safestrap.

Yes, that's how safestrap works, through a process called "bootstrapping". It never replaces your stock recovery so when you boot into recovery it'll always be stock but upon boot you'll be presented with the safestrap option.....totally normal

On another note, my Supersu binaries wont update so I'm going back to stock anyway. I think I may leave it at stock for a while until I see some more ROMs come out.

Ysosrslawl said:
On another note, my Supersu binaries wont update so I'm going back to stock anyway. I think I may leave it at stock for a while until I see some more ROMs come out.
Click to expand...
Click to collapse
Your other option is what I have done. I first went the safestrap route but installed rom on rom slot before finding out about the bugz in safestrap. So I odined back to stock. Instead of installing something with bugz in it I rooted, installed supersu and Xposed framework with some modules. Wanam module gives you most of the customizations found in custom roms. Tons of other modules for pretty much anything you want to tweak. Works like a champ on stock system.

How do i install teamwin ?

I have a i9000 and i would like to install twrp so i can install a 7.0 rom but i dont know how to install twrp can someone tell me how?

I would also like to know this as well. I've tried CWM through odn but it's a zip so wont flash. I've tried it in stock recovery but obviously get the signature fail msg.

TWRP comes with the kernel and hence the ROM.
It gets automatically installed if you're on older BML/MTD device..
In which case you should have rebooted after acceptign wipe..

Ahh right, so I flash a new kernel to it and that comes with the recovery built in.
Do I flash the kernel from odin or stock recovery. Got the stuff to unbrick the phone if that happens, just wanted to know the right way before flashing stock rom back and starting again.

MrGRiMv2 said:
Ahh right, so I flash a new kernel to it and that comes with the recovery built in.
Do I flash the kernel from odin or stock recovery. Got the stuff to unbrick the phone if that happens, just wanted to know the right way before flashing stock rom back and starting again.
Click to expand...
Click to collapse
The kernel is flashed by the ROM zip... I dont remember if it automatically reboots to recovery or not..
However it does create a file in cache that makes it boot to recovery.. Since the /system is not yet installed.
You should flash the ROM after it boots to new recovery.. then install the zip file again..
All this is described in https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh

I got there in the end.
I flashed CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar with odin, then installed cm-10.2.0-galaxysmtd.zip which also updated my older CWM. It had a spam, so I wiped/factory/dalvik etc from the updated CWM and then reinstalled cm-10.2.0-galaxysmtd.zip - now running the rom just fine.
Will be trying out some more over next few days now I have a nandroid of CM10.
Thanks for pointing me in the right direction.