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] Flashed SuperS4, stuck on Android logo

Well I flashed SuperS4 this morning. Wont ever make it past the flashing android screen right after the Samsung Galaxy S4 screen. So I go into recovery(TWRP) and it wont go past the dang TWRP logo screen.... Not good... Anyone have any advice? Phone is like a week old... TWRP worked perfectly before. I was using BeanStalk rom and decided to try out SuperS4.

I've always used the latest Philz recovery and never had a problem with it
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
Try flashing the latest Philz recovery with Odin and then reflash super s4

EliteN00b said:
Well I flashed SuperS4 this morning. Wont ever make it past the flashing android screen right after the Samsung Galaxy S4 screen. So I go into recovery(TWRP) and it wont go past the dang TWRP logo screen.... Not good... Anyone have any advice? Phone is like a week old... TWRP worked perfectly before. I was using BeanStalk rom and decided to try out SuperS4.
Click to expand...
Click to collapse
churchey360 said:
I've always used the latest Philz recovery and never had a problem with it
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
Try flashing the latest Philz recovery with Odin and then reflash super s4
Click to expand...
Click to collapse
As @churchey360 says - use the latest philz.
Also, you want to reboot recovery after doing wipes and before flashing the ROM.
Your steps should look like this:
1 - do all your wipes
2 - reboot recovery
2.1 - if asked to install Superuser say yes
3 - Flash ROM
3.1 wipe cache and dalvik if you want.
4 - reboot system and let it sit for 10 minutes before you do setup. If you cannot get past the splash screen after 10 minutes you messed up somewhere. Check the md5 hash of the ROM and verify it matches. You may want to boot to recovery from after a battery pull.
Holler back and let us know.

I have never messed with the s4 but,
EliteN00b said:
Well I flashed SuperS4 this morning. Wont ever make it past the flashing android screen right after the Samsung Galaxy S4 screen. So I go into recovery(TWRP) and it wont go past the dang TWRP logo screen.... Not good... Anyone have any advice? Phone is like a week old... TWRP worked perfectly before. I was using BeanStalk rom and decided to try out SuperS4.
Click to expand...
Click to collapse
On devices with unlockable bootloaders (non odin) such as samsung devices, i think you have to flash the boot image file somehow. (no fan of odin)
but if the device contains fastboot, then flash the boot.img in the rom. if odin, download a stock tar and flash it

I faced the same problem... But i solved it by flashing cwm 6.0.4.4 recovery then wipe system, data, cache and delvik cache... Then reboot recovery then wipe again.... Then flash the rom.
It will work with you.

i'm assuming you can get the phone in download mode (hold power + down arrow) and then use odin to flash a new recovery (preferably cwm 6,0.44) then go into recovery and do another wipe/reset/etc and install the rom again.

Accidentally wiped data....T_T

Hi all, so I got this nice S4 i9505 (telstra unlocked).
after a week I thought I'd try install pacman rom.
I installed openrecovery-twrp-2.5.0.1-jfltexx.tar
I wiped all caches, system, data, and than the fatal mistake, I wiped the WRONG data...... now I have nothing on my phone.
It wasn't rooted, I've lost everything, I need to get I9505XXUEMJ5 (stock) and flash it back on, and start again.
I tried CF-Auto-Root-jflte-jfltexx-gti9505.zip
than openrecovery-twrp-2.5.0.1-jfltexx.tar
right now I have twrp on there, and not much else.
basically, I've wiped the data and now i need to reinstall stock. than start again flashing pacman.
how can I get out of this situation?
I can't find I9505XXUEMJ5 ANYWHERE with a reliable download, the one I've got is 10KB/s and will take 30HOURS to download T_T T_T T_T I need help....
thanks in advance :3
I need my phone T_T it's brand new.
I'm assuming I9505XXUEMJ5 is the right firmware to flash on it, and that I don't need any extra modem or anything to flash?
to flash pacman rom I just need to install copy rom to phone after stock rom is on, reboot into twrp and flash rom??
what about root?
when I try install CWM-SuperSU-v0.99.zip from TWRP it works, but when I booted into the telstra firmware it said SuperSu crashed straight away.

mazzafox said:
Hi all, so I got this nice S4 i9505 (telstra unlocked).
after a week I thought I'd try install pacman rom.
I installed openrecovery-twrp-2.5.0.1-jfltexx.tar
I wiped all caches, system, data, and than the fatal mistake, I wiped the WRONG data...... now I have nothing on my phone.
It wasn't rooted, I've lost everything, I need to get I9505XXUEMJ5 (stock) and flash it back on, and start again.
I tried CF-Auto-Root-jflte-jfltexx-gti9505.zip
than openrecovery-twrp-2.5.0.1-jfltexx.tar
right now I have twrp on there, and not much else.
basically, I've wiped the data and now i need to reinstall stock. than start again flashing pacman.
how can I get out of this situation?
I can't find I9505XXUEMJ5 ANYWHERE with a reliable download, the one I've got is 10KB/s and will take 30HOURS to download T_T T_T T_T I need help....
thanks in advance :3
I need my phone T_T it's brand new.
I'm assuming I9505XXUEMJ5 is the right firmware to flash on it, and that I don't need any extra modem or anything to flash?
to flash pacman rom I just need to install copy rom to phone after stock rom is on, reboot into twrp and flash rom??
what about root?
when I try install CWM-SuperSU-v0.99.zip from TWRP it works, but when I booted into the telstra firmware it said SuperSu crashed straight away.
Click to expand...
Click to collapse
You can get the telstra rom from sammobile.com (the latest is ND1), but it will probably have the knox bootloader crap on it. As long as you have trwp installed and running, you can install any custom rom from that, root will be done by the custom rom, you don't need to root first and you will find most custom roms will have superuser installed as well.
I have a telstra S4, but I am running Echoe rom v29, when installing it gives you the option to wipe cache and things.

dwarfer66 said:
You can get the telstra rom from sammobile.com (the latest is ND1), but it will probably have the knox bootloader crap on it. As long as you have trwp installed and running, you can install any custom rom from that, root will be done by the custom rom, you don't need to root first and you will find most custom roms will have superuser installed as well.
I have a telstra S4, but I am running Echoe rom v29, when installing it gives you the option to wipe cache and things.
Click to expand...
Click to collapse
Every time I try flash anything, it all fails straight away..

mazzafox said:
Every time I try flash anything, it all fails straight away..
Click to expand...
Click to collapse
So you cant boot your phone at all? If not you will have to go to telstra or samsung and get them to fix it.
I am wondering if you need a pit file to also flash in odin, you can get a i9505 pit file from this site.
With trwp the latest is 2.7.1.0.

dwarfer66 said:
So you cant boot your phone at all? If not you will have to go to telstra or samsung and get them to fix it.
I am wondering if you need a pit file to also flash in odin, you can get a i9505 pit file from this site.
With trwp the latest is 2.7.1.0.
Click to expand...
Click to collapse
I can get into recovery and download mode, but can't boot. it stays at Samsung GALAXY S4 GT-I9505 screen with KERNEL IS NOT SENDROID ENFORDING Set Warranty Bit : kernel
when in TWRP 2.7.1.0 all zip's I try install always fail.
I'm trying this;
http://forum.xda-developers.com/showthread.php?t=2594483
I'm going to try install I9505XXUEND1 through TWRP.
Got from sammobile

From what I read flashing stock should fix the problem.
I dont think you can flash that through recovery, you will have to use odin.

dwarfer66 said:
From what I read flashing stock should fix the problem.
I dont think you can flash that through recovery, you will have to use odin.
Click to expand...
Click to collapse
So that means I should be able to install pacman after installing stock?
Yeah I need to use odin. no problem.
Downloading stock rom now, will take an hour with the slow option on sammobile.
The stock rom I downloaded from some random place that took 30hours!!!!!!!!!! didn't work so I hope this stock one works.
I'll let you all know how it goes.

You will have to install the custom recovery again, but after that flash away!

dwarfer66 said:
You will have to install the custom recovery again, but after that flash away!
Click to expand...
Click to collapse
I installed stock rom, it is still stuck at samsung logo...
what can I do???
I'm very poor I can't afford a new phone...... this one is brand new!! T_T
EDIT:
finally got to the second SAMSUNG logo. I think it'll make it through the first boot soon I hope .

How long has it been stuck for, I remember it took over 5 minutes to boot, and even then I had to press the power button for it to finish booting.

dwarfer66 said:
How long has it been stuck for, I remember it took over 5 minutes to boot, and even then I had to press the power button for it to finish booting.
Click to expand...
Click to collapse
It finally finished booting!
so I should now flash TWRP than pacman yeah?

mazzafox said:
It finally finished booting!
so I should now flash TWRP than pacman yeah?
Click to expand...
Click to collapse
Fantastic mate, yep go right ahead. In recovery goto wipe, advanced wipe, only wipe cache, dalvik, data, system.
---------- Post added at 07:30 PM ---------- Previous post was at 07:23 PM ----------
Are you flashing the black power edition RC1 or a nightly?

dwarfer66 said:
Fantastic mate, yep go right ahead. In recovery goto wipe, advanced wipe, only wipe cache, dalvik, data, system.
---------- Post added at 07:30 PM ---------- Previous post was at 07:23 PM ----------
Are you flashing the black power edition RC1 or a nightly?
Click to expand...
Click to collapse
RC1, gotta save that power
It booted flawlessly.
now which gapps to install for RC1.. what's the extra features on nightly?
scratch that, found the gapps and such, pacman forum. thanks for the help man, I was at witts end!!! THANK YOU!!!
hugs all round.

No prob mate anytime. Enjoy your rom!

cant flash to any other ROM.. aside from CM13

Was using an CM13 unofficial build for months... then i decided i needed SPen and Heartbeat sensor
so i was hoping to try Erobots rom ( did full wipe ) , after successfull install... got boot loop... just keeps restarting on the Note 4 Logo
so i tried reflashstock rom(s) with both odin and kies 3 , after every flash , i always get the installing system update... erasing... and then boot loops
i though i got a perma soft brick.. till i tried using Cm13 again.... and it works ??
so what's causing this ? me not being able to use TouchWiz based roms ? both stock at custom

up

Try going to Recovery via the 3-button combo. Then wipe cache and data/factory reset.
If it didn't help, flash the official stock rom via odin. Then do the wipe cache/factory reset again in Recovery after flashing the stock rom.

yup tried those... i always ended up.. installing system update... then erasing... then boot loops

I have the exact same issue, I was stupid enough to not backup my system with TWRP when I had first rooted the device, so I cant just 'restore' my backup. I would like to use another rom but cannot due to this issue.
---------- Post added at 08:36 AM ---------- Previous post was at 08:24 AM ----------
try this: http://forum.xda-developers.com/note-4/help/n910c-stuck-frustrating-bootloop-t3301750

Slaid_ said:
I have the exact same issue, I was stupid enough to not backup my system with TWRP when I had first rooted the device, so I cant just 'restore' my backup. I would like to use another rom but cannot due to this issue.
---------- Post added at 08:36 AM ---------- Previous post was at 08:24 AM ----------
try this: http://forum.xda-developers.com/note-4/help/n910c-stuck-frustrating-bootloop-t3301750
Click to expand...
Click to collapse
have edited my original post ,

I've had something similar when I tried CM. It uses a not so generic recovery.
Try to flash a different recover with Odin - TWRP for example.

Softbrick Nexus 6P

Please help me. I'm using a Google Nexus 6P. I'm in a softbrick state (bootloop). At first, i taught a simple flash of stock factory image from google with help. But nothing helped. I tried everyhting from the internet asked me to do. I used adb, fastboot, nexus toolkit, but nothing helps. The phone keep on bootlooping. I can go to bootloader and recovery. The bootloop starts when i was flashing a nandroid backup (PureNexus Rom) from a BenzoRom. When i finished flashing the nandroid backup, the bootloop starts. I even did a factory reset, wipe everything, flash a fully stock rom (7.0.0), but the phone won't start..please help me XDA..i really need your help!

Are the android versions of Benzo and PureNexus the same?

CharliexCharger said:
Are the android versions of Benzo and PureNexus the same?
Click to expand...
Click to collapse
Yes it was 7.0 for both of them

afdhalzaed said:
Please help me. I'm using a Google Nexus 6P. I'm in a softbrick state (bootloop). At first, i taught a simple flash of stock factory image from google with help. But nothing helped. I tried everyhting from the internet asked me to do. I used adb, fastboot, nexus toolkit, but nothing helps. The phone keep on bootlooping. I can go to bootloader and recovery. The bootloop starts when i was flashing a nandroid backup (PureNexus Rom) from a BenzoRom. When i finished flashing the nandroid backup, the bootloop starts. I even did a factory reset, wipe everything, flash a fully stock rom (7.0.0), but the phone won't start..please help me XDA..i really need your help!
Click to expand...
Click to collapse
Welcome to the club..
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page38
---------- Post added at 07:50 PM ---------- Previous post was at 07:44 PM ----------
Same thing happened to a lot of us. Some were able to recover and some were not, unfortunate I couldn't no matter what I tried. And believe me I tried everything possible. Fastboot , toolkits no go , as for me I couldn't even access recovery. So I did the next best thing, as I was able to flash factory images and lock bootloader I had to rma the device. Waiting on the new one now.

BIGSAMDA1ST said:
Welcome to the club..
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page38
---------- Post added at 07:50 PM ---------- Previous post was at 07:44 PM ----------
Same thing happened to a lot of us. Some were able to recover and some were not, unfortunate I couldn't no matter what I tried. And believe me I tried everything possible. Fastboot , toolkits no go , as for me I couldn't even access recovery. So I did the next best thing, as I was able to flash factory images and lock bootloader I had to rma the device. Waiting on the new one now.
Click to expand...
Click to collapse
that's hard..your device was in hardbrick state yes? mine is in softbrick..that's why im so stressed out why this thing cant be fixed..because usually soft brick is easy to be fix..

afdhalzaed said:
that's hard..your device was in hardbrick state yes? mine is in softbrick..that's why im so stressed out why this thing cant be fixed..because usually soft brick is easy to be fix..
Click to expand...
Click to collapse
I was able to flash all factory images manually, I was able to use a toolkit which I normally won't use to download all the images fine. Just that when it came to booting up or even accessing recovery it was a no go. Everything flashed fine via fastboot or toolkit.

I actually did it! oh my god i actually did it! i got out from the freaking bootloop! and trust me i tried EVERYHTING else. Only this method, for me at least, helped. I will described exactly what i did.
1. You need a nandroid backup. Any nandroid backup for your phone is good i think. You NEED to know what version of nandroid backup you are having, and what version of ROM.
2. Wiped, erased everything on my phone.
3. Reverted my phone to stock version of the nandroid. (Google Factory) (For me i reverted to MTC20F full stock because my nandroid backup was on PureNexus MTC20F, used flash all.bat)
4. Tried booting to system but failed, still bootlooped.
5. Flashed TWRP, for me, TWRP 3.0.2.0 works. My suggestion, don't go above this version of TWRP, lots of problems!
5. Flashed the custom ROM the nandroid you had (for me, the nandroid backup was PureNexus MTC20F 6.0.1, so i flashed the PureNexus ROM running MTC20F vendor)
6. I tried rebooting to system, but not to avail.
7. I restored the nandroid backup i had earlier.
8. Progress, the boot animation appeared. Before, only Google logo poped out and then it restarts again.
9. Flash back to full stock MTC20F. (flash all.bat without wiping anything)
10. The phone fully boots!