Develop Bugs

Phone stuck at Samsung Logo Screen

Hey guys i am completely stumped.
I tried flashing the aristodemos rom into my phone and ever since then i cant get past the logo screen.
I was running the paranoidandroid rom through the AOSP JB kt474 kernel before i flashed the aristodemos rom.
Since then i have tried flashing the stock kernel and the stock pre-rooted Rogers rom with no luck.
My last shot at it was downloading the Official stock firmware of the sgh-i747m for rogers from the samsung-updates website.
Can someone please help me out here i have tried to hold back and not start my own thread and just look around in the forums but i cant seem to find any solution.
So, if you have any idea on how i can get my phone back up and running please help!

Can you get into recovery mode or not?
Sent from my SGH-I747 using Tapatalk 2

amgpower63 said:
Can you get into recovery mode or not?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
i can get into download mode. but cant get into recovery.

update:
just tried flashing the stock i747mvlale8 rom followed by the stock i747mvlale8 kernel for the rogers version.
still no luck!

update:
after i flashed both stock kernel and rom i was finally able to boot into stock recovery.
did a factory reset and is now running!

Pauley04 said:
update:
after i flashed both stock kernel and rom i was finally able to boot into stock recovery.
did a factory reset and is now running!
Click to expand...
Click to collapse
Awesome man. Good to see it figured out
Sent from my SGH-I747 using Tapatalk 2

Gs3 stuck at second Logo.
amgpower63 said:
Awesome man. Good to see it figured out
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
HI, sorry to bother you guys. I formatted my system in recovery mode and now i cant get passed that dreaded samsung galaxy s3 logo. I can still go to download mode and i can still go to CMW-based recovery v5.5.0.4. I just cant figured out what rom? or firmware? i should download. (I am a noob here so hang in there.) Please help. My last resort is going to sprint and telling them i accidently formatted the system. Again if anyone can help please reply thanks!...:crying:

Gs3Nick said:
HI, sorry to bother you guys. I formatted my system in recovery mode and now i cant get passed that dreaded samsung galaxy s3 logo. I can still go to download mode and i can still go to CMW-based recovery v5.5.0.4. I just cant figured out what rom? or firmware? i should download. (I am a noob here so hang in there.) Please help. My last resort is going to sprint and telling them i accidently formatted the system. Again if anyone can help please reply thanks!...:crying:
Click to expand...
Click to collapse
Just download a rom and flash it with cwm... Att?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Pauley04 said:
update:
after i flashed both stock kernel and rom i was finally able to boot into stock recovery.
did a factory reset and is now running!
Click to expand...
Click to collapse
Had the exact same problem and this was the last step that got it working. Thanks! :victory:

Gs3Nick said:
HI, sorry to bother you guys. I formatted my system in recovery mode and now i cant get passed that dreaded samsung galaxy s3 logo. I can still go to download mode and i can still go to CMW-based recovery v5.5.0.4. I just cant figured out what rom? or firmware? i should download. (I am a noob here so hang in there.) Please help. My last resort is going to sprint and telling them i accidently formatted the system. Again if anyone can help please reply thanks!...:crying:
Click to expand...
Click to collapse
Download cm10 and the gaaps and flash them in that order in your recovery. Your phone should work afterwards. Makes sure you clear cache /dev before flash.
Sent from my SGH-I747 using xda app-developers app

messed up flash screen and no bootscreen

whenever i flash any custom rom whether the rom version is android 4.2/4.1.2/4.1.1 , my phone has no bootscreen and a messed up flashscreen when it sais (samsung galaxy note 2 GT-N7100) but then after waiting the appropriate time, the rom works fine but same problem when rebooting... i attached the flashcreen and how it looks like, i have no idea why this happens.i just press the lockscreen after rebooting and waiting and the rom works normally. i rooted using the Galaxy Note II Toolkit v3.0.0 GSM. i first experienced this right after flashing and entering recovery(cmw) but twrp worked fine then, now any rom i flash i experience this,
Is anyone faceing a similar problem or can help in anyway ?
stock rom works fine btw

try flashing Philz recovery

dr.ketan said:
try flashing Philz recovery
Click to expand...
Click to collapse
is philz recovery in the link u posted because i cant see it,
inorder to install it, i flash stock rec then philz via odin right?

http://forum.xda-developers.com/showthread.php?t=2028103
yes flash tar file with odin (no need to flash stock, straight way flash with odin)

dr.ketan said:
http://forum.xda-developers.com/showthread.php?t=2028103
yes flash tar file with odin (no need to flash stock, straight way flash with odin)
Click to expand...
Click to collapse
this is the second picture... i flashed philz and still same problem! stock works fine :S its making me crazy!

I have the same screen after installing cm 10.1 ... never tried to wait some time to boot.... tried several times with several recoveries... result the same. Before used s3 i9300 and never had such issue. Hope someone will help
Sent from my GT-N7100 using xda premium

T511 said:
I have the same screen after installing cm 10.1 ... never tried to wait some time to boot.... tried several times with several recoveries... result the same. Before used s3 i9300 and never had such issue. Hope someone will help
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
tell me a rom you tried that works fine with the bootanimation and everything please! because so far ive tried several! non have worked. and what recovery are you using?

karlada said:
tell me a rom you tried that works fine with the bootanimation and everything please! because so far ive tried several! non have worked. and what recovery are you using?
Click to expand...
Click to collapse
I tried rom managers cwm and twrp manager and cm 10.1 rom only. Tried several times and no luck. Same screen after install.
Sent from my GT-N7100 using xda premium

A desperate plea for help. Recovery will ONLY backup

I am running the latest CM11 nightly on my I747 with the KT747 kernel and I have no hope left. I have searched everywhere and cannot find this issue. Everytime I boot into recovery, all it will do is backup the rom. It will not let me do anything else, so I have no access to recovery options to flash anything. Can someone please help.

Have you try flashing recovery via Rom Manager?

mrsubway said:
I am running the latest CM11 nightly on my I747 with the KT747 kernel and I have no hope left. I have searched everywhere and cannot find this issue. Everytime I boot into recovery, all it will do is backup the rom. It will not let me do anything else, so I have no access to recovery options to flash anything. Can someone please help.
Click to expand...
Click to collapse
One you are in the wrong forum this is I9300 only

Sorry. I actually resolved the issue by flashing TWRP in Odin. I'm done with cm.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

[Q] wiped os

After ota 4.3 on stock att I747 Itried cf autroot and installed trp successfully. Somehow wiped the os off and now stuck n Samsung screen. I can get into download mode and recovery please help

You can load a custom recovery in Odin and flash a custom ROM.

Brandon136 said:
After ota 4.3 on stock att I747 Itried cf autroot and installed trp successfully. Somehow wiped the os off and now stuck n Samsung screen. I can get into download mode and recovery please help
Click to expand...
Click to collapse
Annoying, but not that hard to fix. You have two or three choices. If you made a backup, you can restore that from recovery mode.
You could go to download mode and flash a stock ROM onto the phone, then root it again.
Or you can go with a custom ROM as the poster above suggested. You generally need a custom recovery for that, so you'd go to download mode and install a custom recovery first. Followed by the custom ROM. If the custom ROM is a tar file, you'd also flash that with Odin in download mode. If it is a flashable zip file then the custom ROM would be flashed after you boot to the custom recovery mode first.
If flashing a stock image, ensure that it is a version 4.3 AT&T image. Trying to flash an earlier version will do bad things to your phone.
.

fffft said:
Annoying, but not that hard to fix. You have two choices.. you can go to download mode and flash a stock ROM onto the phone, then root it again.
Or you can go to download mode and install a custom recovery, followed by a custom ROM as the poster above suggested. If the custom ROM is a tar file, you'd also flash that with Odin in download mode. If it is a flashable zip file then the custom ROM would be flashed after you boot to the custom recovery mode first.
If flashing a stock image, ensure that it is a version 4.3 AT&T image. Trying to flash an earlier version will do bad things to your phone.
.
Click to expand...
Click to collapse
As far as I know, there is no stock 4.3 AT&T image available because one was never released by AT&T. However, I think there may be some 4.3 based ROMs that can be flashed.
Mobile Odin can also be used to flash an image since mobile Odin does not flash a bootloader or modem.

audit13 said:
As far as I know, there is no stock 4.3 AT&T image available because one was never released by AT&T. However, I think there may be some 4.3 based ROMs that can be flashed.
Mobile Odin can also be used to flash an image since mobile Odin does not flash a bootloader or modem.
Click to expand...
Click to collapse
It can be painful to be an AT&T customer at times. If a full factory 4.3 ROM wasn't released, the OP could still flash a properly formatted backup of someone's stock AT&T 4.3. But it would of course be easier to adopt a custom ROM as you suggested. One choice would be S3Rx 3.0.
.

Thanks for the help. However I tried to flash several 4.3 stock based roms and got nothing. I had an older s3 with a busted screen so I took the mother board out and put in this. I then flashed twrp and rooted. Im on the ota 4.3 and would really like a custom rom. Im currently on the hunt.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Brandon136 said:
Thanks for the help. However I tried to flash several 4.3 stock based roms and got nothing. I had an older s3 with a busted screen so I took the mother board out and put in this. I then flashed twrp and rooted. Im on the ota 4.3 and would really like a custom rom. Im currently on the hunt.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You didn't give us nearly enough details to really know what you tried, let alone why it might have failed. AT&T is much more restrictive than most carriers and is locking their bootloader, so you have to be careful not to flash someone else's bootloader or a pre 4.3 version.
But since you have a rooted phone again.. installing a custom ROM wouldn't be hard to do.. I gave you a link to decent custom ROM that would work for you. Or you can browse other custom ROMs if you prefer. There are detailed instructions in the thread to guide you. Basically confirm that you have one of the listed AT&T bootloaders and modems, download the custom ROM to your phone, boot to twrp, do a "factory wipe", then install the custom ROM (flashable zip file) from the twrp install menu.
.

Try Philz Touch recovery instead of TWRP. If it doesn't work with Philz, let us know the error messages you're getting.

Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Brandon136 said:
Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You can't find custom rooms cause you're blind or can't read. Backup out of the Q&A forum to the s3 page with all the forum listing then click on the forum that says AT&T galaxy s3 development. If you can't find one there you need to stop trying...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Brandon136 said:
Can you post a link where I can find custom roms for att i747. Sorry for the noob question I have looked and cannot find one. Thank you. Im on rooted ota 4.3 with twrp currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have had better luck flashing ROMs with CWM than TWRP.
There are lots of ROMs here: http://forum.xda-developers.com/galaxy-s3-att/development

Couldmyou point me in the direction to switch over. I have read alot on that same issue
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Download Philz Touch zip from here and flash in TWRP. Reboot into recovery and you should have CWM installed.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att

Sammobile.com has the stock images don"t they? Thats where i got my Fido factory image.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I know thats right. This is my first so needless to say its all new. I looked for just custom roms and not delelopment. Sorry, thanks for the help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Brandon136 said:
I know thats right. This is my first so needless to say its all new. I looked for just custom roms and not delelopment. Sorry, thanks for the help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Any luck?

Yes I have cwm and titanium back pro, busy box pro, and a few other goodies. So I made me a backup and flashed 4.4.2. I'm playing with it now. It seems really solid and way better customizations. I'm about to head over and give the developers thanks. Thank you as well for your advice.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Note 3 issues with CWM/Goo Manager recovery bootloops

Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info

I posted a few days ago about my bootlooping in the recovery. I finally fixed it by these 3 steps.
1) Odin flashed Stock 4.4.2 complete as this sets the correct boot loader.
2) I downloaded Twrp 2.7.0 the one that list KitKat (Must say this) 4.4 version.
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
3) Right from Odin when flashing this you set it not to reboot, Once finished you then unplug the usb cable and pull the battery. Let is sit for about 10 sec. Then with the upVlm,Home and Power it will boot to the recovery. It first will post what you said but wait about 10 sec more twrp will come up.
4) Now you should be able to flash any rom you want. I am using axmans N3 for now works great. I will be trying CM 11 later.
5) make a backup once in Twrp
Hope this helps.

helterkelter said:
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
Click to expand...
Click to collapse
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.

dragonstalker said:
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
Click to expand...
Click to collapse
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?

helterkelter said:
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
Click to expand...
Click to collapse
The kernels you can use are listed in the general thread. A user posted a very good listing of what's what. TWRP 2.7 or Philz Touch are the 2 recoveries i would recommend using. Whichever one you decide will overwrite the other. you can never have 2 recoveries.

OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app

helterkelter said:
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You are already on the 4.4 bootloader so you can no longer use the Darthstalker rom, you can only use Kit Kat 4.4.2 and above roms from here on out. Next question would be have your rooted your phone since the update and have a custom recovery. If you have not rooted, then you will need to use Odin to run the CF_Autoroot, but that will trip your Knox to 0x1. Thus voiding your warranty.

Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app

helterkelter said:
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Which cwm and twrp are you trying to flash. The only 2 that will work on Kit Kat are PHilz touch latest one, and TWRP 2.7

Twrp 5.7.3
Sent from my SM-N900T using xda app-developers app

So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app

helterkelter said:
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
oh sorry for the late response. Just got back from boy scouts. Anyway. No you don't need to flash back to stock, Your just flashing the wrong version of TWRP. You can go to the android originial development thread and download the TWRP 2.7 and flash via recovery and you will be all good to go. Also, download the latest Wootever kernel just to make sure you have both angles covered. Both downloads are found in the same section.

Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app

helterkelter said:
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yes, odin the custom recovery and you should have no more issues. As for the bootloops with TWRP, you only had issues with that, because the version you were trying to use was outdated and does not work on Kit Kat

Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app

helterkelter said:
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You have already upgraded to Kit Kat, that part is done. and you ran CF_Autoroot correct in Odin correct? If you have done both steps all that is left is to Odin the Philz Touch Recovery that you downloaded.

Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app

helterkelter said:
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
As long as they are AOSP Roms that support both bootloaders yes, and as i've been told most if not all the AOSP Roms do support the Kit Kat bootloader that you are already on.

Ok thank you again. I will likely flash philz tonight (if hubby allows me to cuz I usually stay up all night til I got my phone the way I want it, ie no boot loops lol) I will report back to let you know if it works. This phone has been through hell and back with me but I've learned a lot!! Especially from contributors such as yourself. :thumbup:
Sent from my SM-N900T using xda app-developers app

Cool. I'm glad I read this thread. I too had same problems.
Sent from my NOTE 3 using Tapatalk