Develop Bugs

[Q] S3 freezes and basically dies at random times despite battery near full

So weird phenomenon started happening yesterday. I was on cm10.1 RC5 and hadn't done anything new to my phone but randomly throughout the day it would just go black and not respond to unlock and basically looked like it was in power off mode. Only way to get it back up is to reboot but then it will freeze in 5 mins to an hour and power off again.
I thought it was a rom issue at first so I flashed to cm10.2 the most stable one right now but it happened again. So I tried to restore to stock and after I fianlly got it to stock on android 4.12 and then when I was setting up the phone it happned again.
One thing though, I booted phone into recovery and kept it on for more than 2 hours without any random shutoffs or freezes which leads me to believe its still a software issue. Any help?

Ftwpker said:
So weird phenomenon started happening yesterday. I was on cm10.1 RC5 and hadn't done anything new to my phone but randomly throughout the day it would just go black and not respond to unlock and basically looked like it was in power off mode. Only way to get it back up is to reboot but then it will freeze in 5 mins to an hour and power off again.
I thought it was a rom issue at first so I flashed to cm10.2 the most stable one right now but it happened again. So I tried to restore to stock and after I fianlly got it to stock on android 4.12 and then when I was setting up the phone it happned again.
One thing though, I booted phone into recovery and kept it on for more than 2 hours without any random shutoffs or freezes which leads me to believe its still a software issue. Any help?
Click to expand...
Click to collapse
How are you wiping the phone? Which recovery are you using? it does sound ROM related, because you say it stays up in recovery. It could be what edfunkycold talked about before, Sudden Death Syndrome

joeyhdownsouth said:
How are you wiping the phone? Which recovery are you using? it does sound ROM related, because you say it stays up in recovery.
Click to expand...
Click to collapse
I'm wiping the phone through TWRP recovery. Cleaned out the cache,data,storage,system, factory reset basically.

Ftwpker said:
I'm wiping the phone through TWRP recovery. Cleaned out the cache,data,storage,system, factory reset basically.
Click to expand...
Click to collapse
When you say storage are you talking about internal or external? You should not wipe internal storage, some of these files are needed for the Operating System. It's not sudden death syndrome.

joeyhdownsouth said:
When you say storage are you talking about internal or external?
Click to expand...
Click to collapse
Its all internal. I only just put in an external sd card to flash the rom from. I flashed the stock using this method: http://forum.xda-developers.com/showthread.php?t=1904099. Don't know if that makes any different then say restoring from another method.

Ftwpker said:
Its all internal. I only just put in an external sd card to flash the rom from. I flashed the stock using this method: http://forum.xda-developers.com/showthread.php?t=1904099. Don't know if that makes any different then say restoring from another method.
Click to expand...
Click to collapse
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.

joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
mm shoot I didn't know that. Since its already wiped does that effect anything? I dont think wiping internal created the problem though since it was present before I started flashing to stock.

Ftwpker said:
mm shoot I didn't know that. Since its already wiped does that effect anything? I dont think wiping internal created the problem though since it was present before I started flashing to stock.
Click to expand...
Click to collapse
Before you flashed to stock, were you wiping internal, like when you flashed CM?

joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
joeyhdownsouth said:
Before you flashed to stock, were you wiping internal, like when you flashed CM?
Click to expand...
Click to collapse
Ya i did wipe the internal at least two times when I was flashing different CM roms.

Ftwpker said:
Ya i did wipe the internal at least two times when I was flashing different CM roms.
Click to expand...
Click to collapse
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------
joeyhdownsouth said:
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
Click to expand...
Click to collapse
When you flashed billiard's OTA stock, did you keep stock or you flashed custom recovery, and did you keep root? From my understanding, only stock recovery will erase and rewrite internal storage. I would try it again, and do not flash custom recovery or root access. Let the phone boot up without flashing root or custom recovery. If it boots, and doesn't freeze and die for awhile, then proceed with rerooting and installing custom recovery again.

joeyhdownsouth said:
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
Are you saying that is causing the phone to randomly die? Or do you mean its another problem?
---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------
When you flashed billiard's OTA stock, did you keep stock or you flashed custom recovery, and did you keep root? From my understanding, only stock recovery will erase and rewrite internal storage. I would try it again, and do not flash custom recovery or root access file.
Click to expand...
Click to collapse
I flashed custom recovery because I wasn't sure if I would be able to reflash or go into recovery again if the stock rom didnt work. Also I didn't root either.

Ftwpker said:
I flashed custom recovery because I wasn't sure if I would be able to reflash or go into recovery again if the stock rom didnt work. Also I didn't root either.
Click to expand...
Click to collapse
The only thing I can tell you is to try flashing again, without custom recovery, it should wipe and reformat internal storage for you. I don't think custom recovery allows internal storage to be rewritten. As long as you can get into download mode, you can always use ODIN to reflash stock image, should anything happen and the stock ROM didn't work. If your not familiar with ODIN, you can try mskip's toolbox here.

joeyhdownsouth said:
The only thing I can tell you is to try flashing again, without custom recovery, it should wipe and reformat internal storage for you. I don't think custom recovery allows internal storage to be rewritten. As long as you can get into download mode, you can always use ODIN to reflash stock image, should anything happen and the stock ROM didn't work. If your not familiar with ODIN, you can try mskip's toolbox here.
Click to expand...
Click to collapse
Do you have a link on how to use odin to reflash? Want to have it handy in case I get stuck in a bootloop again.

Ftwpker said:
Do you have a link on how to use odin to reflash? Want to have it handy in case I get stuck in a bootloop again.
Click to expand...
Click to collapse
Try the toolbox I posted above. It will open ODIN and flash the needed files for you. YOU MUST FOLLOW DIRECTIONS VERY CAREFULLY. The thing most people miss when using this toolbox, is make sure your phone's serial number shows up, before trying anything else this toolbox will do.

Or you can watch this video from QBKING77 https://www.youtube.com/watch?v=nHpqK6D3P_Y&feature=youtube_gdata_player
Sent from the future via Tapatalk 4

edfunkycold said:
Or you can watch this video from QBKING77 https://www.youtube.com/watch?v=nHpqK6D3P_Y&feature=youtube_gdata_player
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Totally forgot about this

joeyhdownsouth said:
Totally forgot about this
Click to expand...
Click to collapse
Alright thanks. Will try if needed. Can i install custom recovery if everything woks?

Ftwpker said:
Alright thanks. Will try if needed. Can i install custom recovery if everything woks?
Click to expand...
Click to collapse
Yes, root 1st, then custom recovery. But, to me, the easier way, toolbox will do all these things for you. Let me know how it goes!

joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
Incorrect, nothing that the OS uses gets stored on the internal storage, it all goes to system... It is completely safe to wipe your internal storage when moving between ROMs, I and many others do it with every flash

flastnoles11 said:
Incorrect, nothing important that the OS uses gets stored on the internal storage, it all goes to system... It is completely safe to wipe your internal storage when moving between ROMs, I and many others do it with every flash
Click to expand...
Click to collapse
I fixed your post for you

AOSP roms will NOT run! Driving me crazy...

So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?

I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app

iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.

Do you by chance have a refurbished s2?

The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?

es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app

es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.

Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!

es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?

UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.

es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?

tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...

I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.

DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?

TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/

Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk

yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways

wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.

DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.

Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte

Replacement GS3

I have received a replacement GS3 2 days ago. I rooted the phone no problems and it came with MK3 already on it. But no matter what rom I flash, they all cause a lot of random reboots and lockups. TW and CM based roms ive tried with the same results. I do multiple wipes before installing any rom so I know that cant be the problem. It got so annoying that i just flashed the stock tar in odin even though i hate not being rooted. Can anyone shed some light on this?

cbond007 said:
I have received a replacement GS3 2 days ago. I rooted the phone no problems and it came with MK3 already on it. But no matter what rom I flash, they all cause a lot of random reboots and lockups. TW and CM based roms ive tried with the same results. I do multiple wipes before installing any rom so I know that cant be the problem. It got so annoying that i just flashed the stock tar in odin even though i hate not being rooted. Can anyone shed some light on this?
Click to expand...
Click to collapse
Are you flashing 4.3 TW ROMs? Do you format system before flashing the ROMs (if they do not say that they do it for you)?

Yes, I'm flashing 4.3 roms. I do wipe the system, I don't know if that is the same as formatting the system though(?)
kennyglass123 said:
Are you flashing 4.3 TW ROMs? Do you format system before flashing the ROMs (if they do not say that they do it for you)?
Click to expand...
Click to collapse

cbond007 said:
Yes, I'm flashing 4.3 roms. I do wipe the system, I don't know if that is the same as formatting the system though(?)
Click to expand...
Click to collapse
In CWM the option is format /system. Is wipe system an option in TWRP? And when you flashed the ROMs and the FCs show up, have you tried a factory data reset to clear all data?

Yes, in TWRP in the wipe options, (wipe system) is an option. I haven't gotten any FC's on the 4.3 roms i were flashing. Moar's rom is the main one i used after i got the replacement. Wicked's rom in recovery when I tried to flash would always say unable to mount \system. I can flash CM 11 nightlies fine, but they just have too many random reboots for my liking. I havent tried to factory reset after flashing a rom yet though.
kennyglass123 said:
In CWM the option is format /system. Is wipe system an option in TWRP? And when you flashed the ROMs and the FCs show up, have you tried a factory data reset to clear all data?
Click to expand...
Click to collapse

cbond007 said:
Yes, in TWRP in the wipe options, (wipe system) is an option. I haven't gotten any FC's on the 4.3 roms i were flashing. Moar's rom is the main one i used after i got the replacement. Wicked's rom in recovery when I tried to flash would always say unable to mount \system. I can flash CM 11 nightlies fine, but they just have too many random reboots for my liking. I havent tried to factory reset after flashing a rom yet though.
Click to expand...
Click to collapse
The thing is with Knox in the bootloader you are stuck with and the warranty bit in the secondary bootloader you need to stick with 4.3 and above ROMs as they include compatible kernels. Your options are more limited now than they were. If the Wicked ROM is 4.3 you might try flashing with CWM.

Cool. I will try it with CWM. This sucks because my replacement phone came with Knox already on it. I just wish CM 11 roms werent so buggy on my phone so I could stick with that. Thanks for all your help.
kennyglass123 said:
The thing is with Knox in the bootloader you are stuck with and the warranty bit in the secondary bootloader you need to stick with 4.3 and above ROMs as they include compatible kernels. Your options are more limited now than they were. If the Wicked ROM is 4.3 you might try flashing with CWM.
Click to expand...
Click to collapse

cbond007 said:
Cool. I will try it with CWM. This sucks because my replacement phone came with Knox already on it. I just wish CM 11 roms werent so buggy on my phone so I could stick with that. Thanks for all your help.
Click to expand...
Click to collapse
I would also suggest trying Philz Touch recovery instead of CWM or TWRP.
http://forum.xda-developers.com/showthread.php?t=2446393
---------- Post added at 10:36 AM ---------- Previous post was at 10:25 AM ----------
If you do decide to try Philz (highly recommended!), the option for wiping prior to a ROM install is under Wipe Data/Factory Reset and then choose "Clean to Install New ROM" this will take care of everything you need to start properly. CM11 has run flawlessly for me since its release in early December, but I also am Knox-free. I don't believe that should make a difference though, sounds more like you are not getting a good install, as @kennyglass123 is suggesting. Additionally, some users find that you need to let the ROM "settle in" before doing anything. This means flash just the ROM, and once it boots up don't do anything-no WiFi setup, no fiddling around with apps, nothing for a few minutes. Then, boot back into recovery, flash GApps, boot back into system, and let it sit for a few minutes more. Then, go ahead and setup WiFi connection, Google account, etc.

At wits end (Possible brick?)

So, I was benchmarking various kernels today, and my phone decided that it doesn't want to function anymore. To be more specific, I went from Faux's kernel, to Lean kernel, and back to Faux; and after returning to Faux, I've gotten nothing but "SystemUI has stopped responding". Since this happened I've wiped both cache and dalvik cache, re-flashed stock firmware via Odin, and wiped my internal memory--all to no avail. If anyone has any advice regarding this matter, it'd be greatly appreciated.

bardock123 said:
So, I was benchmarking various kernels today, and my phone decided that it doesn't want to function anymore. To be more specific, I went from Faux's kernel, to Lean kernel, and back to Faux; and after returning to Faux, I've gotten nothing but "SystemUI has stopped responding". Since this happened I've wiped both cache and dalvik cache, re-flashed stock firmware via Odin, and wiped my internal memory--all to no avail. If anyone has any advice regarding this matter, it'd be greatly appreciated.
Click to expand...
Click to collapse
So what happens now? Does it boot at all? Boot-looping? When plugged into computer is it recognized? Were you on 4.3 or 4.4? We need some more information before everyone starts chiming in.

noobtoob said:
So what happens now? Does it boot at all? Boot-looping? When plugged into computer is it recognized? Were you on 4.3 or 4.4? We need some more information before everyone starts chiming in.
Click to expand...
Click to collapse
It boots, but every rom that I try installing an alternate rom, it either freezes after a few minutes, or it doesn't boot at all. I can still get into download mode, so ADB/Odin/recovery isn't ruled out. I'm still on the 4.3 bootloader.

Alright. What recovery are you running?
Sent from my SM-N900T using Tapatalk

noobtoob said:
Alright. What recovery are you running?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
TWRP

Sorry, got called away from my desk.
What version of Odin are you using? I know you stated you wiped cache and internal storage. Just to rule everything else out right now, please try and follow my heimdall guide. Since you are on 4.3 it will still work. Perform both the recovery and stock restore guide. It seems to have done a lot of people a solid when Odin wouldn't wipe it properly. In my instructions (in the recovery zip) it says for best results to wipe things in a particular order. Try out the heimdall recovery zip and then the full restore. Heimdall instructions are in their own files, but basically you use zadig.exe that they provide to replace the usb driver. After all is said and done, let me know what happens. You may have a corrupt portion of the emmc that doesn't provide i/o very well any longer.

noobtoob said:
Sorry, got called away from my desk.
What version of Odin are you using? I know you stated you wiped cache and internal storage. Just to rule everything else out right now, please try and follow my heimdall guide. Since you are on 4.3 it will still work. Perform both the recovery and stock restore guide. It seems to have done a lot of people a solid when Odin wouldn't wipe it properly. In my instructions (in the recovery zip) it says for best results to wipe things in a particular order. Try out the heimdall recovery zip and then the full restore. Heimdall instructions are in their own files, but basically you use zadig.exe that they provide to replace the usb driver. After all is said and done, let me know what happens. You may have a corrupt portion of the emmc that doesn't provide i/o very well any longer.
Click to expand...
Click to collapse
That did the trick. Thanks again for the help!

bardock123 said:
That did the trick. Thanks again for the help!
Click to expand...
Click to collapse
Awesome. That is why I like heimdall. Now if only i could get it to work on the 4.4 bootloader...?
Sent from my SM-N900T using Tapatalk

No ROMS will boot

So I was running CM11 M8 and restored back to stock(Root66) BNC1 on my T999L.Ever since that not one single ROM will boot regardless of which recovery I try to flash it with(CWM,TWRP,PhilZ,Multiboot).I can Odin back to BNC1(Root66 or Straight Stock) with no issues and the ROMS never give any error's while installing they just hang at the boot screen.I've tried factory reset with dalvik and cache after flashing as well and get nothing still.My phone works fine still no issues there just not able to sucessfully boot a flashed ROM.Any advice would be greatly appreciated.

How long did you leave it on the boot screen? It can take a while at times

serio22 said:
How long did you leave it on the boot screen? It can take a while at times
Click to expand...
Click to collapse
Of course I waited. When I install CM 11 it was almost 30 minutes before I said screw it and restored my nandroid.

Have you tried factory resetting from stock recovery? It will wipe internal sd just so you know.

DocHoliday77 said:
Have you tried factory resetting from stock recovery? It will wipe internal sd just so you know.
Click to expand...
Click to collapse
Yes I have also tried that Doc.

Try flashing another rom from recovery. Before trying to reboot, select Copy Log to SD. See if it has any clues. (It'll be towards the end of the file)
You can post it here if you can't find anything.
Aside from that, all I can think to try is flashing with Odin again and select re-partition.

DocHoliday77 said:
Try flashing another rom from recovery. Before trying to reboot, select Copy Log to SD. See if it has any clues. (It'll be towards the end of the file)
You can post it here if you can't find anything.
Aside from that, all I can think to try is flashing with Odin again and select re-partition.
Click to expand...
Click to collapse
Did that as well and looked at the log.Did another restore through Odin to complete stock then to Root66 and that seems to have fixed the issue...hmmm no idea what was wrong.

Sometimesbtheres just no good way to know the cause.
Glad to hear it seems to be ok now! For the next several flashes you do, just kerp an eye on how its acting and copy the log to sd each time, just in case. If it still is working ok after a few times it should be ok to go back to doing things like normal.