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?

[Q] Doesn't boot

Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?

ricomana said:
Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
Click to expand...
Click to collapse
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.

malybru said:
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
Click to expand...
Click to collapse
Thanks for replying
I followed the instructions and succesfully installed the official stock rom for my device and region.
But it's still stuck at the samsung boot screen.
And now i can't boot into TWRP anymore either, is that correct?
After that I flashed with the .pit file. But still stuck on bootscreen.
Is there any other way to solve this problem?
idgaf about custom roms or CM10.2 anymore, i just want my phone to work.
Wether it's with custom or with stock firmware.
Really hope I didn't break my phone. :crying:
EDIT:
I wiped cache after flashing, but no data wipe/factory reset. That did the trick.
God i can't be happier my phone finally works again. Now i'm scared to flash a custom rom again. I think i need to install TWRP or CWM again too I'll just wait for now.

[Q] Galaxy S4 Sacs Rom Issue Please Help

I just flashed this rom successfully yesterday. The rom was stable and working, however I wanted to get the hotspot to work. I used a hotspot mod on a previous 4.3 rom, so I tried it again on this rom. I flashed the MDC Hotspot Mod while in Philz Touch 5.18 recovery. After flashing the hotspot mod, I reboot the system and it is stuck at the "Kit Kat" splash screen. I went back to recovery, wiped everything (data reset, cache, davlik cache) and reinstalled the rom and it seemed to work fine. However, I wanted to get the hostpot working so later in the night I reinstalled a 4.3 rom, and now I can not get any rom to work. When I boot up I am not faced with the Galaxy S4 screen saying:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
It will not go to the Kit Kat splash screen, I can get to download mode and recovery mode. I tried completely re-rooting the device, Installing different roms and even a different kernel, but I can't seem to get anything to work. At this point, I just need my phone to work and will use any rom. I don't think this is a fully bricked device because I can get into recovery and download mode. I can live without hotspot for now, just need a working phone. If anyone can advise here or help please reply here or email me at [email protected]. This is my daily driver phone and I need it to work, hopefully it is an easy fix like getting a stock 4.4 kernel? BTW this was a brand new galaxy s4 which came with stock 4.4, so I am not sure if installing 4.3 had an issue with it. Maybe using ODIN to fix the problem, I am not sure. I have successfully rooted many phones including HTC EVO 4G, HTC EVO 3D and Galaxy S4( until now) and have never ran into this issue. Please advice anyone!! Thanks!

RE: S4 Sac Rom Issue Please Help
I ran into a similar problem and my device would not boot. I simply just reflashed clockwork 6.0.4 recovery from Odin and was able to get back into recovery to wipe and reflash a new rom. Hope this helps. Note: I selected PDA in Odin. Here is a tutorial to get recovery back.
http://jellybean-news.blogspot.com/2013/02/complete-guide-to-install-clockworkmod.html
Good luck.

Soft brick - Need some guidance

It's been awhile since I changed anything on this phone, I've been running CM11 with no issues. The wife was playing with my phone which is on cm12 and wanted me to upgrade it. Great, I hate having to touch her phone but ok.
1. Did a straight upgrade to CM12 nightly (couple nights ago build) with gapps from CM site. After the install everything crashes on the initial load, it's like the baseband is jacked and doesn't know how to handle the new google play services because everything crashes.
2. Went back and wiped internal everything this time, re installed nightly and gapps. No change.
3. Tried step 2 a couple more times and different gapps from PA and other random sites (micro, light, stock versions) and then TWRP just died on me. It's asking for a password when I first go in so now I'm stuck there. Tried to use ODIN to install the latest TWRP after converting it with another script found here (i'll find the link).
so, I'm probably going to have to use ODIN to restore some stock version of S4 ATT but I really don't know which one is stock that would work with CM12. I don't want to get caught in the safestrap crap of dual boot and whatever else. Any help is greatly appreciated.

You'll need to Odin the mdl firmware in Odin. Be careful as it will want to update itself after you flash it. See sammobile.com for the firmware.
Sent from my Nexus 9 using XDA Free mobile app

Awesome, thanks!
Flashed the stock, towelroot, twrp from google play and cm12 nightly. Perfect and back where I left off. Thanks!!

Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?

kronikwisdom said:
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app

Ok, factory reset worked on the second try. Sent it in to a boot loop on the first go around, odd. Thanks!

Galaxy Note 3 Bootloop

Good morning,
I'm stuck with a big problem on my Note 3 HLTE.
Here's the story : I was previously on the PAC Rom 5.1 and I wanted to change to get the CM13.0 that was just released. So I've performed the full wipe (dalvik, cache and factory reset) and then when I wanted to update the OS, it didn't work. I ended up with a phone in recovery, telling me that there was no OS installed on it.
after several attempts, I then tried to revert back to a stock ROM based on 4.4.2 with Odin. The installation went on without any problems, I was able to get through the first install with my Gmail account and then the phone rebooted, and that's where I got the bootloop curse.
what I did then, was to redo an install via Odin with my carrier stock rom, and I got a FAIL message. So, I retried an install with Odin by adding a PIT file and another ROM still based on 4.4.2. the install worked, as I was able to set up my Gmail account and so on. At this stage, I wasn't able able to get any signal for calls, 4G . In parameters, the baseband was identified as "Unknown". Then, the phone rebooted again, and I got the bootloop curse again...
My last attempt has been to install my carrier stock ROM after performing a full wipe, with ODIN. The install was successful and I got the phone rebooted to stuck on bootloop.
So, here's where I am, and I would like to solve this problem, please. What I think is that, due to the fact that I was on Lollipop, the bootloop might be due to the downgrade attempt to KK. So if there's any way to solve this problem, I'm eager to take it.
Thank you !
Hey Guys,
I've been able to resolve my bootloop problem.
I've installed TWRP with Odin, made a full wipe including data (I've saved them before), and I installed the CM12.1 by Temasek, and way to go, the phone is running fine ^^
Now, I'm just stuck with the lost IMEI thing and baseband. SO my question now is : if I want to install my operator stock ROM for getting back, should I just choose the Lollipop ROM, or can I take the KK one without getting stuck in bootloop again ?
Thank you !