Develop Bugs

How are you guys getting TWRP to install?

Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium

mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".

SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium

mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!

mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?

SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium

Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?

Did you ever get TWRP on your phone?

I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==

wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.

Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.

wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)

Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.

Cwm on sg3 not working properly?

Hi,
I'm experiencing some issues with cwm recovery. When I try to do anything in rom manager it says that I must have cwm recovery installed but when I try to flash cwm recovery via rom manager my phone isn't listed (sg3 att) I have the latest version straight from Google play.
I would greatly appreciate some assistance with this very annoying problem.
Thnk you!
Steve.
Sent from my SGH-I747M using xda premium

nevetsgtI9100 said:
Hi,
I'm experiencing some issues with cwm recovery. When I try to do anything in rom manager it says that I must have cwm recovery installed but when I try to flash cwm recovery via rom manager my phone isn't listed (sg3 att) I have the latest version straight from Google play.
I would greatly appreciate some assistance with this very annoying problem.
Thnk you!
Steve.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Get twrp does the same exact thing but a better ui and everything!!! Install goo manager and just choose a random rom to flash (you dont really have to flash the rom) its just so it prompts you to ask if you have a custom recovery say no and it will install twrp! Trust me on this one TWRP is one flawless custom recovery and always seems to work with me

Hey thanks for that reply. Just a couple of questions. I went ahead and installed twrp recovery and you're right its very easy to use. I tried flashing cm10 stable (at&t) on Rogers sg3 and I keep getting error 7. I factory reset the phone just like I would have with cwm.
Also, while in twrp when I select browse all compatible rims nothing comes up.
Any ideas?
Thanks again.
Sent from my SGH-I747M using xda premium

nevetsgtI9100 said:
Hey thanks for that reply. Just a couple of questions. I went ahead and installed twrp recovery and you're right its very easy to use. I tried flashing cm10 stable (at&t) on Rogers sg3 and I keep getting error 7. I factory reset the phone just like I would have with cwm.
Also, while in twrp when I select browse all compatible rims nothing comes up.
Any ideas?
Thanks again.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Wierd. CM10 always says Cwm is the only one that works to flash its rom .. but its wierd cuz i flashed cm10 perfectly with twrp many times before
Heres a thread to fix your error 7 though.. http://forum.xda-developers.com/showthread.php?t=1932975

Did you install ROM Manager from the market (Play Store)? EDIT: Just re-read your OP stating that you did a fresh install. At any rate, it should work fine, there is an option to select the AT&T version of the S3 (see attached screen shot).
TWRP is good too, I'm just more accustomed to cwm so I tend to stick with it.

nevetsgtI9100 said:
Hi,
I'm experiencing some issues with cwm recovery. When I try to do anything in rom manager it says that I must have cwm recovery installed but when I try to flash cwm recovery via rom manager my phone isn't listed (sg3 att) I have the latest version straight from Google play.
I would greatly appreciate some assistance with this very annoying problem.
Thnk you!
Steve.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I had the same issue as you. I'm on a Rogers GS3 and the S3 ATT wasn't showing up in the Rom Manager menu.
I installed CWM using this toolkit: http://forum.xda-developers.com/showthread.php?t=1746665
I then had to update CWM to a more current version using these instructions: http://andr0idtech.blogspot.ca/2012/09/how-to-install-latest-clockworkmod.html
Once I updated CWM I was able to flash CM10 with no problems.

skrambled said:
Did you install ROM Manager from the market (Play Store)? EDIT: Just re-read your OP stating that you did a fresh install. At any rate, it should work fine, there is an option to select the AT&T version of the S3 (see attached screen shot).
TWRP is good too, I'm just more accustomed to cwm so I tend to stick with it.
Click to expand...
Click to collapse
That is weird!
The "S3 (AT&T)" shows up in your screenshot but it is nowhere in sight on my copy of CWM... (Bell S3)
I am running ROM Manager Premium v5.0.2.4 (current version, no?) and yet, the phone model list skips from the "Samsung Galaxy S Blaze 4G", to the "Samsung Galaxy S3 (MetroPCS)" and then on to the "Samsung Skyrocket"...
Could this be a regional lock sort of thing? or maybe CWM differentiates between the i747 and the i747m ? Either way, it is NOT showing up in the list...
Any thoughts??

kirkenshrir said:
That is weird!
The "S3 (AT&T)" shows up in your screenshot but it is nowhere in sight on my copy of CWM... (Bell S3)
I am running ROM Manager Premium v5.0.2.4 (current version, no?) and yet, the phone model list skips from the "Samsung Galaxy S Blaze 4G", to the "Samsung Galaxy S3 (MetroPCS)" and then on to the "Samsung Skyrocket"...
Could this be a regional lock sort of thing? or maybe CWM differentiates between the i747 and the i747m ? Either way, it is NOT showing up in the list...
Any thoughts??
Click to expand...
Click to collapse
If you really want cwm use this toolkit http://forum.xda-developers.com/showthread.php?t=1746665 Only for your att Galaxy s III though make sure its the right device that you flash it on !!!!

Well after ALOT of trial and error(which thankfully did not result in a bricked phone) and the helpful comments I finally got CM10 intalled!
Thank you for all the help and comments!
Steve

Cm10 has a check in it that looks for d2att, doesn't it? I think that's why you guys get that error when flashing.
Sent from my SGH-I747 using xda app-developers app

Only issue I have had with cwm is that fix permissions doesnt work. It just sits on it saying fixing for forever.
Sent from my A510 using Tapatalk 2

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

[Q] How to get CWM to work on Tab3 7 T210R

I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k

Wolfgar2k said:
I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k
Click to expand...
Click to collapse
did you check auto reboot in odin? if you do, just try to flash cwm again w/o checking auto reboot. it happens to my tab coz i've check auto reboot.

Just tried that. Same results. Everything looks good when flashing, but when I boot into recovery it's the stock recovery.
Sent from my Galaxy Nexus using xda app-developers app

Wolfgar2k said:
I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k
Click to expand...
Click to collapse
1.Dont check the autoreboot. Ketut.kumajaya said something about the system is restoring recovery when rebooting
2. Try to redownload the cwm recovery.
3. If that didnt work, What odin are u using? Try 3.07 ..
4. You can also try twrp. I am using twrp and it is working great
Sent from my SM-T210R using xda app-developers app

I've been using Odin 3.07 the whole time. I tried twrp as you suggested and that worked. Not sure why cwm didn't work, but at least now I'm rooted. Thanks.
Sent from my Galaxy Nexus using xda app-developers app

I will recreate an autoroot package for you in my spare time. Samsung Android boot image has a known feature to patch the boot image and use it to overwrite the recovery image on every boot. This feature disabled in blackhawk kernel, some recovery has a capability to disable this feature as well.

ketut.kumajaya said:
I will recreate an autoroot package for you in my spare time. Samsung Android boot image has a known feature to patch the boot image and use it to overwrite the recovery image on every boot. This feature disabled in blackhawk kernel, some recovery has a capability to disable this feature as well.
Click to expand...
Click to collapse
Can I flash your kernel on the stock rom while having cwm recovery or do I need Infamous 1.1?
I would like to stay at german on my tablet but also want to use USB OTG

Wolfgar2k said:
I've been using Odin 3.07 the whole time. I tried twrp as you suggested and that worked. Not sure why cwm didn't work, but at least now I'm rooted. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Got to hear that u have twrp. Im happy 4 u
Sent from my SM-T210R using xda app-developers app

Jediritter said:
Can I flash your kernel on the stock rom while having cwm recovery or do I need Infamous 1.1?
I would like to stay at german on my tablet but also want to use USB OTG
Click to expand...
Click to collapse
Yes, you can flash it on stock rom (with CWM), but OTG isn't functioning yet.

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