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?

Infinite Bootloop in every ROM - Solved

Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?

ChameleonGeek said:
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
Click to expand...
Click to collapse
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/

acejavelin said:
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
Click to expand...
Click to collapse
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.

ChameleonGeek said:
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
Click to expand...
Click to collapse
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.

acejavelin said:
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
Click to expand...
Click to collapse
I wait several times more than 10 minutes. I wipe data/cache after restart the phone. I found the solution in Google Forum: https://productforums.google.com/forum/#!topic/nexus/D2vKK9rLgh8[1-25-false]

You should only have to wipe /cache from recovery to get out of it. I believe wiping /data is unnecessary (so you can avoid losing your data if you are concerned.

Massive softbrick (haven't found a solution yet)

Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!

Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?

To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".

DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.

DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.

try safe mode

mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.

After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.

I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!

Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!

Note 3 sm-n9005 stuck in boot(not loop) after xposed flashing.

Hi. Goodday and i want to start of by thanking everybody for reading this and taking your time in advance.
My problem is very clear. I have rooted my phone with odin. Installed the recovery from TRMP?(ik think that's what it's called). Flashed the ROM CyangenMod 12.1. Now i tried flashing the Xposed software which is not a problem (i wipe dalvik before hand). After a reboot and then letting my phone boot up, i just keeps the boot up animation going for around 5 minutes. Didn't try longer then that. After that i booted in recovery again an flashed the uninstalled Xposed and me phone boots normally again (not taking into account it has to optimise the apps again which makes sense after a dalvik whipe).
Any ideas on a solution? Any information you might need ect. Ps, i am not super skilled or anything. I understand a little more then thr basics and thats it.
Again, thanks for your time and help!!

Can I flash stock recovery back?

Hi Guys,
Hoping someone can help and tell me that Ive not bricked my brand new S7 edge
I have experience in rooting / flashing a number of android devices so I was quite confident in what I was doing.
So I was trying to root my stock rom, I flashed TWRP using Odin which worked fine then I flashed the Super SU. When I booted it then asked for a PIN to boot, it definitely wasn't what I set and would have only set it to 1 thing. So I did some googling and found that I could clear data or remove the pin key files but in TWRP it couldnt mount data and I tried re-formatting but it sat there for over half an hour and I had to hard reboot. TWRP now just freezes at the splash screen during boot which confuses me cause even if I switched off during re-formatting, I was only on the userdata so surely that shouldnt affect TWRP? I then got to the stage where I thought entering the max PIN attempts would just wipe data but no it tried to boot into TWRP which is useless cause it doesnt get past the splash screen.
I can still get into Odin mode, is there something else I can try flash? I had tried reflashing TWRP before but it was still freezing at the splash screen
I thought of maybe wiping data over adb but I dont think I can do that unless the phone boots or gets fully into TWRP?
Any help much appreciated.
Thanks
Stewart