Related
My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.
n19htmare said:
My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.
Click to expand...
Click to collapse
What's funny is, I am running the Task650 AOKP rom and Goldeneye rom and my custom padlock icon went away on its own. Many others have reported the icon randomly showing up too. I'm betting it will go away. Try rebooting your device a couple of times and if it really bothers you do a factory reset.
It's really not that big of a deal. Your're still running the samsung recovery.
Interestingly, my phone did this for the first time last night as well. I've been rooted since the beginning. Since you mentioned it I'm also using Nova launcher but can't imagine that matters.
Well my concern is when it happens at the wrong time, say during a warranty repair/replacement. A message like that is show and bam, no warranty.
I went to the AT&T Device Support Center for my Note II and they booted the phone, and then into download mode to see if it was modified or not (obviously I had returned to stock). So they do check
Nova launcher in not the culprit, because I am on TW and it does the same, in and out that message appears, haven't seen it in a week or 2, but it will pop up occasionally. I think anytime you approach the bootloader with a modification, that will show, and then disappear. I could be wrong, but there has been no certain pattern confirmed by anyone.
do any of you guys have a 64gb Sandisk microsd?
polish_pat said:
do any of you guys have a 64gb Sandisk microsd?
Click to expand...
Click to collapse
no. I have a 32GB Samsung micro-sd.
n19htmare said:
no. I have a 32GB Samsung micro-sd.
Click to expand...
Click to collapse
then try this: http://forum.xda-developers.com/showthread.php?t=2296014
polish_pat said:
then try this: http://forum.xda-developers.com/showthread.php?t=2296014
Click to expand...
Click to collapse
He can't do that if he's not rooted.
CZ Eddie said:
He can't do that if he's not rooted.
Click to expand...
Click to collapse
he can root and then unroot. Or he can do the following: take our SD card, reboot twice and check if your system status is still custom
polish_pat said:
he can root and then unroot. Or he can do the following: take our SD card, reboot twice and check if your system status is still custom
Click to expand...
Click to collapse
Just an update. rebooted a few times and CUSTOM message was still there. then I turned the phone off and left it off for a few minutes rebooted and it was gone.
WEIRD!
I did a bit of research and seems like this issue (If you wanna call it that) has been lingering around on GS3 too. Wonder what the cause is.
If someone knows or figures it out, please update this thread. THanks.
n19htmare said:
My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.
Click to expand...
Click to collapse
Same thing happen with me by replacing the battery. Just now. Nova launcher was acting up earlier. Galaxy S4 AT&T I was trying to keep this virgin I guess I now have to root and unroot.. But is this an option actually because they have protected the firmware so far to say that you cannot make yours virgin anymore without the original virgin firmware??
i have a sgh i337 at&t.. my phone suddenly freezed and went to bootloop
It suddenly freezed and after some minutes, it automatically went to bootloop.. All I see is the at&t logo for hours.. After that, I wiped data n cache from recovery and the phone started to work well, but after 30 minutes or more , same things are repeated.. Freezes and Wents to bootloop.. And the option I only have is to do a hard reset which works only for 30 minute.. And when I use the phone for 5 minutes after reset and then I restart it, it freezes on lock screen and goes to bootloop.. Please help.. Will flashing a custom ROM will work?.. I want to change the carrier and remove at&t.. Please help..
I had this same exact problem, with stock S5. One thing I noticed with mine that no one else mentioned was if I went into settings and then storage it would say SD Card - READING I believe and I couldn't access my pictures. Nor could I format it or erase it when i was doing a factory reset through the settings options. My phone would also freeze, and then there was times the screen would go black and on the very top of the screen would only display the time and battery life the time would change as well as the battery percentage but I was unable to leave that screen except if I would hold the power button down it would show me all the normal reset, power off options and I was able to select any one the options available. What ended up working for me was, removing the SD Card and replacing it. Then I did a factory reset through the settings options menu. Once it finished I instantly ( did not proceed with setup) I turned the phone off and then held the power button the volume up and home button and reset it that way as well. Once it rebooted I noticed the problem was gone and everything was back to normal.
So I recently purchased my AT&T Galaxy S4 with MDL baseband. I rooted and installed TWRP via motochopper. I then loaded Kangabean 4.2.2 and everything was great. Got notification for OTA update to 4.3 and decided might as well load Kangabean 4.3 as opposed to dealing with the OTA notification. I did so (after formatting internal SD and performing factory reset) and now my phone won't boot beyond the Galaxy S4 splash screen. I restored a nandroid backup of the original software and was able to boot the phone once, but couldn't load the custom rom again, nor can i load into the stock rom anymore either. Does it sound like my phone may have a hardware failure? Would attempting to restore through odin be the next logical step? I'm by no means an expert with these sort of things but my S2 has never given me any sort of grief when flashing various roms in the past. Any advice would be greatly appreciated. Thanks in advance!
Try a different kernel, also, pull the battery for 5 min, it will boot.
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
Yeah I left the phone off with the battery removed all night - didn't want to boot this morning. I'm also noticing an oddity with TWRP - it's for some reason asking for a password on startup even though I've never set one. It also gives an error when attempting to wipe the phone or re-flash
id try odin
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
jd1639 said:
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
Click to expand...
Click to collapse
It will not let you past the password, been there, it will only do simulated flashes.
Odin is his only option.
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Squidbert said:
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Click to expand...
Click to collapse
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
//
Squidbert said:
.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
Click to expand...
Click to collapse
If you're on the stock AT&T rom and you're getting stuck on the AT&T boot logo try the following:
Power off your phone and hold down Volume Up, Center Home, and Power buttons together.
Once you see the Galaxy S4 splash - Keep holding down Volume Up and Center Home buttons but let go of Power button.
Choose the wipe datafactory reset. This will wipe your phone completely but it should boot after.
Hope that helps.
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Squidbert said:
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Click to expand...
Click to collapse
TWRP does not now and has never added LOKI to any ROM or Kernel. Only OUDHS CWM auto-LOKIs. You have to use A pre-LOKIed Kernel or flash the LOKI DokI script to LOKI anything with TWRP. You can do a search to find the LOKI DOKI script and how to use it.
fatah
hi my phone is galaxy s4 at&t i337 rooted but not installed recovery the phone was working good suddenly i deleted at&t software updater after that the phone rebooted it's self and then stuck in at&t boot logo won't bootup please help
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
galaxy s4 i337 stuck on at&t bootAnimation
i tried everything but still same please help my phone is not booting up
fatahmusse said:
i tried everything but still same please help my phone is not booting up
Click to expand...
Click to collapse
Flash the stock firmware.
samsung galaxy s4 i337
thank you i flashed to mf3 everything is ok
fatahmusse said:
thank you i flashed to mf3 everything is ok
Click to expand...
Click to collapse
Glad to hear
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
RawSynergy said:
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
Click to expand...
Click to collapse
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
DeadlySin9 said:
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
Click to expand...
Click to collapse
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
RawSynergy said:
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
Click to expand...
Click to collapse
NB1 is the only one you can get, just try downloading either one again.
DeadlySin9 said:
NB1 is the only one you can get, just try downloading either one again.
Click to expand...
Click to collapse
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
RawSynergy said:
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
Click to expand...
Click to collapse
When you plug in the phone in Download Mode, does the blue box in Odin light up? If not, reinstall samsung drivers
Sent from my SM-N910G using Tapatalk
I'm usually fairly good at troubleshooting my own stuff but this really has me stuck in the same place for a few hours now.
So basically Flipboard has been nagging me(well play store is, not the app itself but anyway) so I said to myself why don't I uninstall it since I've never used it and don't plan to, and besides I hate to have pointless apps installed. So I open TitaniumBackup and I see it is installed as a system app, I thought what's the worst that can happen? so I do uninstall it and a minute later my phone shuts off. I try to turn it on and it doesn't go past the Samsung Galaxy Note 4 flash screen, it either reboots or stays like that.
I try to go into recovery to restore a backup and I can't, it is stuck at Recovery Booting and again it either stays like that or reboots and does it again and again and again.
Now, I haven't made any changes or installs on my phone for weeks now, so this is either because I unistalled Flipboard(I know I shouldn't have risked it since it was a system app but I really could not see it going this way) or the hardware is on it's way out(don't see what else could it be).
I figured I should flash a stock rom with odin, I can get into download mode, and reinstall everything from scratch.
I took a stock image from xda and flashed it and it does exactly the same thing.
Right now I'm downloading another stock image from sammobile for my country/provider to see if this will change anything.
What else can I try? I'm completely stuck and I really don't want to send the phone back like this, I doubt amazon is gonna be happy about it.
Specs:
N910F
Emotion Revolution 12.1 Rom
POK1 BL&CP
TWRP 2.8.7.0
Really sorry for the double-post. I'm quite desperate and need my phone for work.
Since last post I've tried flashing N910FXXU1COH4_N910FH3G1COH3_H3G.zip through Odin from SamMobile and it did the same thing with rebooting constantly.
Then I've installed Kies and went to Tools -> Firmware Upgrade and Initialisation and gave it the model and S/N and it downloaded something and everything went all right, the phone reboots and I'm back in the same circle, it just shows me the splash screen(in some video's I've seen that after this procedure they get the splash screen and then the android bot with a progress bar, I don't get that, I only get the splash screen and reboot) and reboots.
I thought this was a last resort thing? Is the phone completely dead or is there something I can try?
Again sorry for the double-post.
Update: still no progress so I've contacted Amazon and they said to send it back so hopefully this works out in the end, no matter how annoying the waiting time will be, if you do have any suggestions on what I should try please let me know as I haven't posted the phone yet.
Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.