Develop Bugs

Root Access Possibly Lost Fix Root?

I have my N7 on bone stock, rooted with superSU 1.60 installed. I flashed the .zip made by Chainfire, and no matter the recovery CWM non-touch , CWM, or TWRP after making a backup , I hit reboot system, and I get this message every time.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
I've selecting option 1 multiple times and I still get the same message after a backup ,and before rebooting!! Root access works fine on all my apps and everything else I'm just curious as to why I'm seeing this via any recovery thanks. I'm sure its silly and an easy fix.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Try v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip

Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app

I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app

Jewveeski said:
Disabled auto-update SuperSU in the playstore , flashed v1.55 ,and problem solved . Thank You!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done this, i disable auto-update, flashed the v1.55 in CWM and rebooted. Now i cant use SuperSU anymore? tells me i have to update binaries. And i know that if i do the "root access possbibly lost" error comes again? any solutions?

In settings there is an option for reinstall as seen in the pic below click that then reboot your device , then reboot to recovery flash version v1.55 and make sure you still have the auto update feature in the play store unchecked. See if that works.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Same issue on a Galaxy Nexus running 4.3 stock rooted... SU requires an update and then the recovery thinks root has been lost (this is not actually the case)... any ideas?

lost root and twrp
so i first discovered i lost root when it said no binary found then when i was going into twrp to reflash the zip all i get is a dead android on its back with a red triangle hovering over it. Went back into adb and flash recovery twrp.img and it says successful but i still get the same thing. any one know the correct thread to point me to? ive looked but cant find this problem. my device boots fine and i can get to the boot loader just not recovery.

Same thing happens with my Nexus 4, I always hit No because it says root may have been lost even if I just enter CWM without flashing any rom or doing any action but rebooting to system

Jewveeski said:
I tried the latest version today, and It seems as though the problem still exists in SuperSU v1.65. I just flashed back to v1.55
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same message on my SGS4 with stock Android 4.3 and SuperSU v1.80.

Same message with my GT-i9300, CWM 6.0.4.4 Touch (i've tried also with CWM 6.0.4.3 NO Touch) and SuperSU v.1.80

I have the same problem too on my Galaxy Nexus GSM 4.3 build JWR66Y with SuperSu by Chainfire v1.8.6 and CWM Touch Recovery v6.0.4.3
Is there a solution?
Thanks in advance
Happy Holidays and Merry Christmas

Same message, S4 mini GT-I9195 4.3 su 1.86

Same message here...
I am running CM 10.2 with CWM Touch and SuperSUv1.86
Is this a big problem?
I think CWM should work just fine regardless of this message right?
If anyone has truly found a "recent" fix please let us know.
Oh i tried reinstalling CWM Touch and that did not fix the problem..
Thank you all for your time and assistance.

Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195

kamikaze702k said:
Same, CM10.2 cwm, SuperSU 1.86, S4 MINI, GT-I9195, never got this message with CM10.1.3, nor with any other 4.2 ROM. I think it's a 4.3 issue not just with CM, I tried 2 other 4.3.1 ROMs, they all said the same thing, yrs the device still works fine when selecting "yes fix root"
My concern is to WHY does this message appear?? And it's there a way to fix this permanently?
Sent from my GT-I9195
Click to expand...
Click to collapse
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow

droidshadow said:
I figured that my device was okay, I mean root still worked just fine.
I bet it has to do with SELinux...
Thanks for the response. I also would love to find a way to fix this permanently. I just did a ROM backup with CWM Touch and I didn't have any issues so this just must be some warning message that doesn't affect anything. Was a bit scary though...
Hopefully someone will find a universal fix soon...
-droidshadow
Click to expand...
Click to collapse
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195

maybe we should switch to TWRP?...
kamikaze702k said:
See, I did a rom backup also with rom manager, after the backup was complete the message still appears, it's more scary if your using a custom recovery because officially my device isn't on rom managers list of supported devices. Hopefully we can get a fix for this.
I'm sure we will it's only a matter of time I guess, I've flashed 4 roms in 3 days just to check the roms and this message came upon after installing 3. However it didn't appear with 4.2.2 so it has to be something with 4.3.x roms
Sent from my GT-I9195
Click to expand...
Click to collapse
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow

droidshadow said:
Has anyone gotten this message with TWRP Recovery Manager? I am thinking that this might only be a problem with ROM's running Android 4.3+ with CWM Recovery Manager.
I have a Nexus 7 2013 tablet which runs like 3 different KitKat ROM's and one JB ROM (4.3.1) and I have never gotten a message like that on TWRP.
Maybe we should just switch to TWRP until CWM works this out or unless someone comes up with a permanent solution...
-droidshadow
Click to expand...
Click to collapse
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195

TWRP is the way to go!
kamikaze702k said:
Your right, my other device I'm using TWRP recovery and few days ago I installed a 4.3 liquid smooth ROM and never got this message!
It's an issue with CWM combined with 4.3 ROMS from what I've tested.
I only thought it was happening on my GT-I9195 because i was using a custom based CWM recovery, but now I know it's across most devices this message is occurring
Sent from my GT-I9195
Click to expand...
Click to collapse
So i just switched my Verizon SGS3 (d2vzw) from CWM Touch to TWRP Touch 2.6.31 and i go to error message/warning about the SU binary being corrupted. This seems to be just an isolated incident with CWM and Android ROM's running 4.3+
With all of the work I have been doing with my Nexus 7 FLO + TWRP Recovery I decided to go ahead and switch my phone to TWRP. It was kind of hard to switch because I started out with CWM but I have just quickly become such a fan of TWRP.
If you don't want to wait for CWM to fix this issue which i am sure they will in their next update try out TWRP i think you will like it!
If you want an easy way to install TWRP recovery manager use the app "GooManager" from the Google Play store and use the your menu button on your phone and choose the open install open recovery script.
Or you could just as easily download the recovery image file from the official TWRP website and flash it with the app flashify.
Don't you just love technology!?
-droidshadow

[Q] Need help. Can't get phone to boot.

Hey all, I've been in the android game for a long time now, so I'm not new to any of this, but this s3 here has me totally stumped.
It is my cousins (telus i747m), and we had it stock rooted 4.1.1 until yesterday.
I updated it to 4.3 with kies, and then he opted for a custom rom. So I flashed TWRP in Odin, and tried to flash gummy 4.4.2
It failed with a assert fail as well as a status 7. I tried old TWRP, New TWRP, Old CWM, New CWM, many different roms ranging from 4.3 and upwards. Still failing with the stupid status 7.
Kies no longer connects to the phone, so I can't restore through there. I will have to install through Odin and the download is horribly and painfully slow.
So is there any way to get a custom rom flashed? I have searched and no one seems to have an answer. Any help appreciated.

What assert failure were you getting?

I'd start back from scratch so go back to stock, then root and flash latest version of TWRP or CWM. Make sure when you flash a Rom it's for that specific device for example if its for the AT&T it's for the AT&T. Also make sure to do a factory wipe before installing any me roms
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

xSharpi said:
I'd start back from scratch so go back to stock, then root and flash latest version of TWRP or CWM. Make sure when you flash a Rom it's for that specific device for example if its for the AT&T it's for the AT&T. Also make sure to do a factory wipe before installing any me roms
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
See my posts #2 & #5 here: http://forum.xda-developers.com/showthread.php?t=2585493

pc103 said:
See my posts #2 & #5 here: http://forum.xda-developers.com/showthread.php?t=2585493
Click to expand...
Click to collapse
Also see THIS post for a more detailed description of the updater-script and bootloader assert.

W03 Slim Rom V7 - Boot Loop

I am trying to install the W03 Slim ROM V7 on my Tmobile Galaxy Note 3 through Philz recovery and I am getting stuck in a boot loop.
These are the steps I tried
1. Used Chainfire's root method to root Kitkat 4.4.2 (which was updated through kies). Used the N9005 and not N900T like the instructions asked me to
2. Flashed Philz Recovery through Odin
3. Copied the ROM and Gapps to my Phone.
4. Rebooted into recovery
5. Wiped Data/Factory reset, Install from Zip, wipe cache, wipe dalvik and reboot.
This is where I get stuck. The phone boots with these words on the top left, "Recovery not enforcing seandroid" or something along those lines and keeps booting. I booted back to Recovery and 'Re'wiped' the phone/did a factory reset, but nogo
So I downloaded the right stock firmware from Sammobile, installed through Odin and repeated the steps and still the same issue.
What am I doing wrong? I made sure I am flashing hltetmo (for TMo Note 3).

Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app

nikhilnagaraj24 said:
I am trying to install the W03 Slim ROM V7 on my Tmobile Galaxy Note 3 through Philz recovery and I am getting stuck in a boot loop.
These are the steps I tried
1. Used Chainfire's root method to root Kitkat 4.4.2 (which was updated through kies). Used the N9005 and not N900T like the instructions asked me to
2. Flashed Philz Recovery through Odin
3. Copied the ROM and Gapps to my Phone.
4. Rebooted into recovery
5. Wiped Data/Factory reset, Install from Zip, wipe cache, wipe dalvik and reboot.
This is where I get stuck. The phone boots with these words on the top left, "Recovery not enforcing seandroid" or something along those lines and keeps booting. I booted back to Recovery and 'Re'wiped' the phone/did a factory reset, but nogo
So I downloaded the right stock firmware from Sammobile, installed through Odin and repeated the steps and still the same issue.
What am I doing wrong? I made sure I am flashing hltetmo (for TMo Note 3).
Click to expand...
Click to collapse
Sounds like a Recovery issue to me. Please look one more time and make sure if you used PHILZ TOUCH that you did in fact flash 6.19.3 HLTE. and not HLTETMO. Im also using philz and no problems flashing. However before it was known that this was the version to use, I did loop at the same point when experimenting with other versoins. Also, check your MD5 and verify that it is a good download.... maybe re download just for gits and shiggles.
---------- Post added at 02:10 AM ---------- Previous post was at 02:07 AM ----------
willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think the new slimKat is 4.4?

willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Had the same bootloop issue when I just tried it out. I updated my bootloader when I updated to stock KK through odin. I am assuming by 4.3 you mean the bootloader on SlimRom is the 4.3 bootloader even though it is a 4.4.2 rom?

willham said:
Correct me if im wrong but if you flashed the new bootloader I don't think you can go back to 4.3 roms anymore.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep.... you are correct sir. 4.3 bootloader. No el flashy 4.3 roms if you updated to 4.4 Bootloader.... im running Echoe rom. Maybe give that a try. Its an international.

Found this on page 78
Sent from my SM-N900T using XDA Premium 4 mobile app

willham said:
Found this on page 78
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks everyone. It does look like it is the bootloader issue.
How do we determine if a particular ROM supports a particular bootloader version? At least the ROMs I have sort of explored and wanted to try, dont mention that anywhere. Or maybe they use some geek term to reference that but I dont understand it. How do noobs like me determine the bootloader version and compatibility of a particular ROM (before flashing and finding out the hard way)???

nikhilnagaraj24 said:
Thanks everyone. It does look like it is the bootloader issue.
How do we determine if a particular ROM supports a particular bootloader version? At least the ROMs I have sort of explored and wanted to try, dont mention that anywhere. Or maybe they use some geek term to reference that but I dont understand it. How do noobs like me determine the bootloader version and compatibility of a particular ROM (before flashing and finding out the hard way)???
Click to expand...
Click to collapse
Not really an answer to your question but I did flash pac-rom without issue. So there is one safe one.
Sent from my SM-N900T using Tapatalk

I think w03 slim rom v4 works with 4.4 bootloader
Enviado desde mi SM-N900T mediante Tapatalk

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

Losing root after reboot

I am on MJ9 omega v23
Problem with my note 2 is when I reboot I lose root ( twrp recovery says that) I try re rooting after that it stucks on SAMSUNG GALAXY NOTE 2 screen....
Re installing rom fixes this issue
How to make my phone normal

premve said:
I am on MJ9 omega v23
Problem with my note 2 is when I reboot I lose root ( twrp recovery says that) I try re rooting after that it stucks on SAMSUNG GALAXY NOTE 2 screen....
Re installing rom fixes this issue
How to make my phone normal
Click to expand...
Click to collapse
I think this is twrp's fault, install clockworkmod

Root in Samsung ROMs is different from AOSP.
TWRP will always think you are on AOSP, so just don't root again and skip the warning and you'll be fine! However if that didn't work, use philz recovery instead. But I don't think twrp is a problem.
Sent from my GT-N7100 using Tapatalk

Mohammed779 said:
Root in Samsung ROMs is different from AOSP.
TWRP will always think you are on AOSP, so just don't root again and skip the warning and you'll be fine! However if that didn't work, use philz recovery instead. But I don't think twrp is a problem.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
i tried installing omega v23 from philz..installed it successfully...but at time of reboot...it again stucked at SAMSUNG GALAXY NOTE 2 logo

pleaseeeeeee helppppppppp.........!!!!!!!!!!

premve said:
pleaseeeeeee helppppppppp.........!!!!!!!!!!
Click to expand...
Click to collapse
Update philz to latest version or version specified with rom.
Do a 'Clean to install a new ROM' from Philz, then flash the zip you wanted to. After installation clean the cache and Dalvik cache from recovery menu.

If I was in your situation, I would move my important files to safe place, reboot to twrp, "fully" format the phone.
Then start it cleanly, this usually fixes every issue.
Sent from my GT-N7100 using Tapatalk

try to flash supersu again.

flash SuperSu as mentioned above by @proxyneo, here is my db link for supersu-
https://www.dropbox.com/s/ylh5ckorv089e4h/UPDATE-SuperSU-v1.93.zip
And also download dr.ketan multi tool advance v6, flash it and from aroma select root and leave others.
you'll find the tool here
http://forum.xda-developers.com/showthread.php?t=2531965
Hope it'll be solved.
Regards.
Sent from my GT-N7100 using XDA Premium 4 mobile app