Database Users

[ROGERS SGH-1337M] Wont Reboot Without FULL WIPE

INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!

Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Which ROMs are you installing? On I337M your best bet is T-Mobile ROMs and Kernels. I have Bell I337M and have no issues.

Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping

kiru said:
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
Click to expand...
Click to collapse
i just went through this all last night what a pita , problem is twrp , if you do a full wipe when you type the word yes , you can only bootup 1 time then it gets stuck next time you boot , theres no way to fix it , even going back to old version of twrp wont do it , you have to compleatlly remove root and return to stock , re root and install twrp again , then if your luck your nandropid backup will work , it took me 5 hrs to fuger this all out , stupid twrp drove me nuts .,...
in short , return to stock and reroot , then never do a full wipe where you have to type yes

Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
i had the same problem, im with rogers so i downloaded the rogers rom 4.2 and i cant make any phone calls or listen to music or watch videos. my phone came with 4.3 does anyone have any ideas to help me?

Phone won't boot past "Galaxy S4" splash screen

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

Stuck after encryption ?

Dear Experts,
I just got a brand new Note 3 with Android 5. I started encrypting the phone as brand
new, so that it would contain as less data as possible. It rebooted, then it showed the
picture with percentage. After reaching 100%, it rebooted again and is now for almost 1 hour showing the SAMSUNG logo with some stars flying around it.
Please kindly let me know if this is normal ? I think that when the stars are moving on the screen, the CPU must be working in order to display that...
Also, the blue LED is flashing... Please kindly advise on what to do.
Thank you!

It's flashing blue because the phone is trying to boot but it's not having any luck. You may have to boot into recovery, perform a factory wipe, and start over.
Personally, I do not encrypt my phone because it becomes a pain to get data off the phone if the data is encrypted.

Thank you. So you think it makes no sense to wait any longer ?
But how can this happen with a brand new phone ????
Btw. this is why it's being encrypted - to not be able to get the data out of it

You could wait but the flashing blue led means the phone is in the process of loading the ROM with the associated apps and data partitions. If it can't load the data, it will hang the phone.

OK, THANK GOD I was able to reset it and it finally booted! I had been doing a few little things with the phone, just the few minutes after I started using it. Maybe this made the encryption fail.
I am relaunching the whole process once again and we'll see. If it fails again. I'll have to be using it unencrypted :-/
Unless someone has a better idea...

Nope, still the same !!! What to do ??????? Please advise...

Come on, anyone, anything, PLEASE ???

Is the phone running a pure stock ROM, including recovery?

I always avoid encrypting phones. Too many risks and issues. I recommend just having a strong password lock.
Sent from my LG-D801 with CM13 using Tapatalk

darkman088 said:
Come on, anyone, anything, PLEASE ???
Click to expand...
Click to collapse
Simplest solution. Is to try to boot into recovery. Perform data wipe. Do a clean boot
If that fails.
Try to go into download mode. Flash stock rom. Clean boot.
If that fails.
Do emergency recovery in kies or smart switch. After that clean boot
After that. Disable encryption. Yeah it's more secure but also as you experience now. When it fails a pain to solve.
Sent from my SM-G935F using Tapatalk

@audit13 - yes, it was running stock Android 5.0, which btw. looks much nicer than 6.0.
Today I have flashed Marshmallow on it and it looks TERRIBLE :-/ I'm sooooo unhappy with the design!
Perhaps I should find a Jelly Bean ROM to flash to my phone :-/
@aquatarkus - why ? You don't think that anyone will unsolder the chips from your phone in order to read them out ? Is the screen lock really so strong ? No way to go around it through some USB attacks ?
And what about your SD card ?
@Michel - it's more or less what I did, but still no solution for that stock ROM that the phone came with.
Thank you for answering!

darkman088 said:
@audit13 - yes, it was running stock Android 5.0, which btw. looks much nicer than 6.0.
Today I have flashed Marshmallow on it and it looks TERRIBLE :-/ I'm sooooo unhappy with the design!
Perhaps I should find a Jelly Bean ROM to flash to my phone :-/
@aquatarkus - why ? You don't think that anyone will unsolder the chips from your phone in order to read them out ? Is the screen lock really so strong ? No way to go around it through some USB attacks ?
And what about your SD card ?
@Michel - it's more or less what I did, but still no solution for that stock ROM that the phone came with.
Thank you for answering!
Click to expand...
Click to collapse
So could you please state the current problem again? Because if I'm correctly you van boot into the rom atm, but encryption fails? Or you are still stuck in the boot process?
What is it exactly what you want right now?
Sent from my SM-G935F using Tapatalk

I no longer have the note 3 but I have the Nexus 5 running stock MM and it looks fine to me.
Maybe encryption needs a stock ROM with stock recovery? I never use encryption on any phone as I don't have anything that is that confidential on my phone.

OK, let me put this together very quickly:
2 days ago I got my brand new Note 3. I played with it a little and said - let's encrypt the phone, till I didn't put much stuff on it, so it will be faster. Once it got to 100%, it rebooted and stayed at the SAMSUNG logo with stars flashing around it and the diode flashing blue. I was waiting and waiting and waiting and nothing! I reset it to factory settings from the original recover, repeated the process - the same! I also tried the fast encryption option - again the same!
Then I have flashed the latest TWRP recovery and tried:
1. The VisionX ROM - Android 5. When I selected encrypt, the screen went completely black. I went to sleep. The next morning it was only showing the SAMSUNG logo in fire and that kept on for another couple of hours till I decided to kill it by taking out the battery.
2. The Slim ROM Android 5.0 - when I select encrypt, it immediately reboots. It kept showing just circles for 2.5 hours with no change. Then I decided that it makes no point to wait longer and I killed it by taking out the battery.
3. The TouchWiz Marshmallow for Note 3 ROM - SUCCESS !!!
The question is - why all the Android 5 ROMs are failing to encrypt the phone ? I prefer to stay on Android 5, as Android 6 is extremely ugly, I can't stand its looks with all the white background and round icons. Perhaps I should flash a ROM with Jelly Bean 4.3, just don't know how it looks with encryption there - pretty miserable I guess...
Thank you!

darkman088 said:
OK, let me put this together very quickly:
2 days ago I got my brand new Note 3. I played with it a little and said - let's encrypt the phone, till I didn't put much stuff on it, so it will be faster. Once it got to 100%, it rebooted and stayed at the SAMSUNG logo with stars flashing around it and the diode flashing blue. I was waiting and waiting and waiting and nothing! I reset it to factory settings from the original recover, repeated the process - the same! I also tried the fast encryption option - again the same!
Then I have flashed the latest TWRP recovery and tried:
1. The VisionX ROM - Android 5. When I selected encrypt, the screen went completely black. I went to sleep. The next morning it was only showing the SAMSUNG logo in fire and that kept on for another couple of hours till I decided to kill it by taking out the battery.
2. The Slim ROM Android 5.0 - when I select encrypt, it immediately reboots. It kept showing just circles for 2.5 hours with no change. Then I decided that it makes no point to wait longer and I killed it by taking out the battery.
3. The TouchWiz Marshmallow for Note 3 ROM - SUCCESS !!!
The question is - why all the Android 5 ROMs are failing to encrypt the phone ? I prefer to stay on Android 5, as Android 6 is extremely ugly, I can't stand its looks with all the white background and round icons. Perhaps I should flash a ROM with Jelly Bean 4.3, just don't know how it looks with encryption there - pretty miserable I guess...
Thank you!
Click to expand...
Click to collapse
I can't answer the question why the encryption keeps failing. What I do know is that marshmallow offers a lot more then lollipop. And that with the option of the theme store and or a custom launcher and icons packs. You can customize the white background and icons to your liking.
Sent from my SM-G935F using Tapatalk

There is no stock mm rom for this phone so we are stuck with LP for a stock rom.

Michel, as you started the topic about themes - can you pls briefly describe how that works ?
I googled it a bit, but didn't find a simple method. Many thanks!

darkman088 said:
Michel, as you started the topic about themes - can you pls briefly describe how that works ?
I googled it a bit, but didn't find a simple method. Many thanks!
Click to expand...
Click to collapse
Samsung included the home store for later end flagships.
I know that through the use of the phoenix rom the galaxy S5 which didn't had support for the theme store got access to it.
You should check with the developer of the rom. Or the Op of the rom if the mm rom available on here comes with support for the theme store.
If it includes that.
You can access the Samsung theme store from touchwiz and download another skin for touchwiz.
This will affect the icon set, notification / dialer and contacts page.
Sent from my SM-G935F using Tapatalk

Help - Freeze / Reboot Issues G935F

Hope someone can help. I had an issue with an app the other day which I think caused my phone to overheat.
Since then I have had a major issue with the phone freezing. I tried to install stock through odin which was fine but the phone freezes during the boot logo sequence, and the stock Rom won't load.
The phone freezes in the Rom, recovery and when booting.
I have managed to install lineage Rom as this doesn't take long to install or boot up. So I have the Rom running for anything from 10secs to about 40secs then it freezes and eventually reboots.
I have had red messages come up saying cannot mount or demount data and system when factory resetting when in recovery.
Is it a faulty part inside or does anyone have any ideas on what I can Do?
Thanks in advance.

Duck4Cover said:
Hope someone can help. I had an issue with an app the other day which I think caused my phone to overheat.
Since then I have had a major issue with the phone freezing. I tried to install stock through odin which was fine but the phone freezes during the boot logo sequence, and the stock Rom won't load.
The phone freezes in the Rom, recovery and when booting.
I have managed to install lineage Rom as this doesn't take long to install or boot up. So I have the Rom running for anything from 10secs to about 40secs then it freezes and eventually reboots.
I have had red messages come up saying cannot mount or demount data and system when factory resetting.
Is it a faulty part inside or does anyone have any ideas on what I can Do?
Thanks in advance.
Click to expand...
Click to collapse
Bro post in s7 edge help section, this is for news, guides etc. Btw you can try smartswitch emergency recovery, put your serial no. and model no. there. If it fails too then reflash stock rom with normal CSC and repartition ticked in options, it will delete all data, so back it up before. If it still freezes and reboots after fresh stock rom install, then there is surely something wrong with your phone.
Sent from my S7 Edge using XDA Labs

Need help. Boot loop on J320P that was a friends.

Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped

Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?