Develop Bugs

Recovery won't stick with new OTA update.

The CWM or Team Win recoveries will not stick after rebooting the phone with w OTA update. There is a way of making recovery stick on the rooted OTA update. Does anyone know the correct files to freeze or erase for the new recoveries to stick?????
Is there another way of these recoveries to stick besides flashing a custom Rom??
Vinny

vinnyjr said:
The CWM or Team Win recoveries will not stick after rebooting the phone with w OTA update. There is a way of making recovery stick on the rooted OTA update. Does anyone know the correct files to freeze or erase for the new recoveries to stick?????
Is there another way of these recoveries to stick besides flashing a custom Rom??
Vinny
Click to expand...
Click to collapse
I definitely didn't have that problem. If you have root use google manager to install twrp
Sent from my SGH-T999 using Tapatalk 2

mikeyinid said:
I definitely didn't have that problem. If you have root use google manager to install twrp
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny

What methods did you use to install the ota and root?
Have you tried flashing the stock rooted version wildchld released?
Sent from my SGH-T999 using xda app-developers app

I waited for the OTA update then used Odin to flash root, did not reboot after flashing with Odin, pulled battery, then went right to recovery and flashed super user.zip file. I rooted my phone the right way. This is my 2nd SGS3 and didn't have this problem with the 1st one because it had the older build. This is not a problem if you are on a custom build. Only stock, rooted with latest OTA build.
Vinny
Sent from my SGH-T999 using Tapatalk 2

I honestly don't know if it would work but maybe try flashing the insecure stock kernel?
Sent from my SGH-T999 using xda app-developers app

Thanks for the input. (DocHoliday) is my favorite western character. Big western nut.
Vinny
Sent from my SGH-T999 using Tapatalk 2

vinnyjr said:
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
Click to expand...
Click to collapse
im stock, rooted on the latest ota and i dont have this issue. never had it on the other build either

vinnyjr said:
Thanks for the input. (DocHoliday) is my favorite western character. Big western nut.
Vinny
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I'm your huckleberry!
Sent from my SGH-T999 using xda app-developers app

mrmako777 said:
im stock, rooted on the latest ota and i dont have this issue. never had it on the other build either
Click to expand...
Click to collapse
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII

Please try this, http://forum.xda-developers.com/showthread.php?t=1821681
Hopefully it works. Mine is fine after update

vinnyjr said:
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
Click to expand...
Click to collapse
I'm on the stock rooted rom and this hasn't been a problem for me. I've installed recovery once since I got the phone. And flashed every stock and custom Rom.
Sent from my SGH-T999 using Tapatalk 2

ingenious247 said:
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
Lolol uh, I've done it a hundred times guy, no issues
Sent from my SGH-T999

You're right. You're the only guy in the world who's official stock update doesn't overwrite the recovery upon reboot. They special coded yours to preserve custom recovery.
Please...
I swear sometimes..
Sent from the current Heavy Weight Champ GALAXY SIII

Guys, I have seen this on my GF's GSII (Sprint) as well as on my nexus 7. They are placing a file called recovery-from-boot.p in the /system/ directory that overwrites recovery on every boot. I put a guide a few post up that outlines the issue when I saw it on my GF's phone.
Personally my T-Mobile has been fine, but this scenario I have dealt with before. So don't flame that bad.

The bottom line is that without some custom modding, if you're running the official stock OTA update, stock kernel, etc, standard CWM recovery is not going to stick.
Plain and simple.
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
cybrnook said:
Guys, I have seen this on my GF's GSII (Sprint) as well as on my nexus 7. They are placing a file called recovery-from-boot.p in the /system/ directory that overwrites recovery on every boot. I put a guide a few post up that outlines the issue when I saw it on my GF's phone.
Personally my T-Mobile has been fine, but this scenario I have dealt with before. So don't flame that bad.
Click to expand...
Click to collapse
Yeah, I'm going to try using that guide and report back. thanks
---------- Post added at 11:12 AM ---------- Previous post was at 11:07 AM ----------
Ok, both files were present as described in your guide.
Renamed both to:
recovery-from-boot.bak
install recovery.sh.bak
Reflashed CWM through ROM Manager. Rebooting now, then will try power off & booting into recovery. Hang tight
*Edit: Worked like a charm. Gentlemen, we have the solution. Thanks due (and given) to cybrnook both here and in the guide
sweet.

ingenious247 said:
The bottom line is that without some custom modding, if you're running the official stock OTA update, stock kernel, etc, standard CWM recovery is not going to stick.
Plain and simple.
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
Yeah, I'm going to try using that guide and report back. thanks
Click to expand...
Click to collapse
I would argue, I have a stock rooted rom, stock kernel and I update to the new OTA update via Kies and TWRP has stuck every boot since then. I even tested it again when I saw this thread as it made me unsure.

cybrnook said:
I would argue, I have a stock rooted rom, stock kernel and I update to the new OTA update via Kies and TWRP has stuck every boot since then. I even tested it again when I saw this thread as it made me unsure.
Click to expand...
Click to collapse
Maybe the Kies version is different than the OTA.
Maybe TWRP overwrites or renames/deletes the files causing it.
But you can't argue with my posts, because I said official OTA update, and CWM.

ingenious247 said:
Maybe the Kies version is different than the OTA.
Maybe TWRP overwrites or renames/deletes the files causing it.
But you can't argue with my posts, because I said official OTA update, and CWM.
Click to expand...
Click to collapse
No worries, but for clarification to all the read this thread. The update from Kies is the exact same Official update as the OTA, so if you have not been prompted for the update yet from T-Mo, just install Kies on your PC and plus your phone in, it will prompt you for the update.
I have another guide I made for that:
http://forum.xda-developers.com/showthread.php?t=1842142
For the recovery, installing twrp or CWM wont remove the two files I listed. This is done manually. I know on the sprint side, they made a root Super User package that swiped those off specific to the sprint phone. But I opted away from that for my GF as I Prefer SuperSU and am anal retentive about installing something I don't want and uninstalling it.
---------- Post added at 08:26 PM ---------- Previous post was at 08:24 PM ----------
ingenious247 said:
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
ingenious, it's not present on all phones. Like mine for example, I have been fine since day 1 of owning the phone. But my GF's sprint phone had the persistent install present.
It's strange, some phones don't have it at all, some only have the .p file, and some have both. I have not found the common denominator yet.

ingenious247 said:
You're right. You're the only guy in the world who's official stock update doesn't overwrite the recovery upon reboot. They special coded yours to preserve custom recovery.
Please...
I swear sometimes..
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
My bad man, I didn't get the memo that you knew everything I guess all the other guys that haven't had this same issue are nuts too...
Sent from my SGH-T999

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

[Q] Stock

ok, i am running Lollipop 5.0.1 on SM-N910P, my question is if i go and get the current rooted .img and flash it using ODIN, would it trip my knox? sence it would be a stock Kernel. i have Tried KingoRoot, Pingpong root, Towelroot, Activeroot, SuperRoot, king-root. i am having such a hard time with this, only had the phone sence February and i dont want to trip knox.
or would it be possible to install a modified signature .ZIP of superuser and install it on normal recovery? thanks

Knox II will trip with any root method; none known that won't trip Knox for Note 4.
CF Auto Root will work in Odin for your OE1 build but you're limited to CM12 or Noterized Stable for custom ROMs; the others won't boot and full Odin stock tars won't work and there's no OE1 tar either. This is not a standard Sprint OTA; I don't think a OE1 tar will be released; it's long overdue.
If you're still interested, there's a request for stock OE1 recovery; it needs to be backed up and shared in order to help some other rooted OE1 users to take the next OTA to 5.1.1 whenever that releases. Without it, you would be waiting on a tar as well; stuck. To get the recovery backed up, root in Odin (root only), download Flashify in Google Play and backup the stock recovery before you upgrade to TWRP. Share that gem with others that need it. Here: http://forum.xda-developers.com/showthread.php?p=61456449
Still with me? Next you would need TWRP to backup your stock rooted OE1 for a backup if some flash or mod goes awry.
Finally, you could modify the stock Rom or flash Noterized and back it up as well. Keep all these recommended backups in a safe place like on your sdcard and duplicates on PC hard drive.
Read, be careful and ask the questions when you don't understand and you'll avoid the problems others have unexpectedly ran into or got stuck with. OE1 is basically a broken update that shouldn't have got pushed.
Sent from my SM-N910P using Tapatalk

eankk said:
ok, i am running Lollipop 5.0.1 on SM-N910P, my question is if i go and get the current rooted .img and flash it using ODIN, would it trip my knox? sence it would be a stock Kernel. i have Tried KingoRoot, Pingpong root, Towelroot, Activeroot, SuperRoot, king-root. i am having such a hard time with this, only had the phone sence February and i dont want to trip knox.
or would it be possible to install a modified signature .ZIP of superuser and install it on normal recovery? thanks
Click to expand...
Click to collapse
I don't think so without root access
Sent from my SM-N910P using XDA Premium HD app
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
There is no oel stock recovery no one has it
Sent from my SM-N910P using XDA Premium HD app

Yeah I only want root for the WiFi tether for root and sound boost, o well I will just stick with PDAnet. I was hoping there was something out there. But I am familiar with rooting very well, this is the 1st time that I am stumped and getting frustrated with it. But at least I asked though

eankk said:
Yeah I only want root for the WiFi tether for root and sound boost, o well I will just stick with PDAnet. I was hoping there was something out there. But I am familiar with rooting very well, this is the 1st time that I am stumped and getting frustrated with it. But at least I asked though
Click to expand...
Click to collapse
It's still just as simple; just fewer choices with OE1. Some have said Bluetooth is broken in some applications of its purpose, IDK for sure.
I made the request for the stock recovery which would add an extra step if you chose to help.
If Knox trip is a concern, sorry to be the bearer of bad news. Just to clarify...
I could post some links if that helps? Want them posted?
Sent from my SM-N910P using Tapatalk

samep said:
It's still just as simple; just fewer choices with OE1. Some have said Bluetooth is broken in some applications of its purpose, IDK for sure.
I made the request for the stock recovery which would add an extra step if you chose to help.
If Knox trip is a concern, sorry to be the bearer of bad news. Just to clarify...
I could post some links if that helps? Want them posted?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I will help, but I don't know coding or any development things, yeah knox trip is a big concern, (when I had my s4 I rooted and tripped knox, the SIM card error poped up and sprint said sorry we can't do anything Warrinty is void, only had it 9 months).... yes Pease

eankk said:
I will help, but I don't know coding or any development things, yeah knox trip is a big concern, (when I had my s4 I rooted and tripped knox, the SIM card error poped up and sprint said sorry we can't do anything Warrinty is void, only had it 9 months).... yes Pease
Click to expand...
Click to collapse
Did it still have custom recovery or root or mods installed when warranty was denied? Backing up these may help, if needed. Can't guarantee that but I'd try another service facility if turned down initially. Just tell them we never had this conversation. Lately, I'm hearing Sprint is cracking down on root. I've had conversations with tech and admitted I root as a right. It's not illegal but warranty is becoming another subject.
I'll post the links here shortly if someone doesn't beat me to it.
Sent from my SM-N910P using Tapatalk

samep said:
Did it still have custom recovery or root or mods installed when warranty was denied? Backing up these may help, if needed. Can't guarantee that but I'd try another service facility if turned down initially. Just tell them we never had this conversation. Lately, I'm hearing Sprint is cracking down on root. I've had conversations with tech and admitted I root as a right. It's not illegal but warranty is becoming another subject.
I'll post the links here shortly if someone doesn't beat me to it.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Nope everytime I took it to a sprint store I flashed it back to complete stock and made sure that the newest version of Android was on it. He is like your knox sensor is tripped. Then I said. "I messed up my phone bad and had to flash stock firmware back on it (when I got the note 4, the chick who sold it to me used to work for Samsung and we where talking about rooting, and then I asked about the sensor if it can be reversed she said, once it is tripped not even samsung can fix it) and damn I did not know sprint was cracking down on root. That's crappy

Links and steps to root OE1, backing up stock recovery
CF Auto root Download SM-N910P; follow OP for instructions. (Use Odin)
Flashify use to backup stock recovery. (Share using link in post 2 above; thanks in advance.)
Use Flashify app to get TWRP recovery (select latest tar, not zip; Odin tar is optional and TWRP Manager is optional: ) You'll need to make a stock nandroid backup once you have custom recovery.
Noterized stable 2 follow OP for install instructions; it will flash over OE1. (If so inclined to stay with TouchWiz custom ROM) TWRP/nandroid backup again; label these backups and keep safe.

samep said:
CF Auto root Download SM-N910P; follow OP for instructions. (Use Odin)
Flashify use to backup stock recovery. (Share using link in post 2 above; thanks in advance.)
Use Flashify app to get TWRP recovery (select latest tar, not zip; Odin tar is optional and TWRP Manager is optional: ) You'll need to make a stock nandroid backup once you have custom recovery.
Noterized stable 2 follow OP for install instructions; it will flash over OE1. (If so inclined to stay with TouchWiz custom ROM) TWRP/nandroid backup again; label these backups and keep safe.
Click to expand...
Click to collapse
^^ Sticky this beautiful answer to the ever lasting-never ending redundant OE1 question. Eventually we'll need some thread pruning.

So I understand.
Samsung is the one who would release the tar right and you are saying they have not released it because it is buggy?

Mship said:
So I understand.
Samsung is the one who would release the tar right and you are saying they have not released it because it is buggy?
Click to expand...
Click to collapse
Consider the facts as we know them. Sprint shouldn't have released it; it's the ugly duckling of a long string of unlocked bootloaders for dancing phones on Sprint. There's a new OS lock intended to protect the owner of a lost phone from easily being written over to bypass a screen lock with a battery pull and Odin tar. But there should also be a user switch to momentary bypass this so Odin wouldn't have been totally broken to rightful owner. Maybe Samsung didn't intend for that to happen and Sprint didn't know better? But since as some have reported that Bluetooth is not fully functional; Sprint should have caught that. I'd say they both collectively hold the blame since it wasn't immediately addressed. I'd blame Sprint more for not halting the update, infecting more users. Hopefully, they're trying to fix that. Maybe they were but decided to work on 5.1.1 update instead?
If it walks like a duck, quacks like a duck...; it must be a duck. It sounds odd to many here, from what I've read. But this is an ugly one. They both should own it, admit it, fix with an immediate update and move on. Until then, make the most of it; apparently, you can't expect a fix by taking it back to Sprint and some warranty replacements had the update pre-installed or quickly updated. Just plain wrong; a definition of insanity.
Maybe mostly opinionated but specifically, are there exceptions to the above for those that got OE1? I think there were some that said the only drawback is not being able to downgrade or recover a soft bricked phone. I could be wrong but just impressed by those OE1 users that have commented.
Edit: short answer is yes because users could update in KIES and that would make Samsung directly to blame for those users. Silence seems to indicate the bugs exist. And may signal a user need to wait for tars to be released which indicates Samsung deems the release as stable.
Sent from my SM-N910P using Tapatalk

Update
So I just got a new update, does anyone know anything about it?

[Q&A] [ROM|Stockish|NO KNOX] 8/7/15 Sprint TouchWiz Lollipop 5.1.1 (N910PVPU4COG5)

[Q&A] [ROM|Stockish|NO KNOX] 8/7/15 Sprint TouchWiz Lollipop 5.1.1 (N910PVPU4COG5)
Q&A for [ROM|Stockish|NO KNOX] 8/7/15 Sprint TouchWiz Lollipop 5.1.1 (N910PVPU4COG5)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM|Stockish|NO KNOX] 8/7/15 Sprint TouchWiz Lollipop 5.1.1 (N910PVPU4COG5). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Flashing Kernel on OG5 5.1.1
I recently updated to the Sprint 5.1.1 and tried to root using odin and did not achieve root. However, now the phone gives an error when trying to do OTA update. How do I flash this kernel? Do I use odin to flash it or do I use the regular recovery

VIPDMERC said:
I recently updated to the Sprint 5.1.1 and tried to root using odin and did not achieve root. However, now the phone gives an error when trying to do OTA update. How do I flash this kernel? Do I use odin to flash it or do I use the regular recovery
Click to expand...
Click to collapse
The kernel is flashed in TWRP recovery. Odin that, making sure you've selected the option to disable OEM lock in Odin 3.10.6 and do not select auto reboot. When done with the TWRP Odin flash, pull USB and battery, wait 30 seconds, reboot to recovery and flash kernel.
Are you having trouble with Odin or boot? CF Auto Root is not used to root OG5. After flashing the kernel, flash the rooted ROM or root with SuperSU zip if just wanting to root stock and boot.
Sent from my SM-N910P using Tapatalk

Getting Root
Not to familiar with everything, however I tried flashing CF Autoroot, i downloaded the beastmode kernel already. Just tryung to figure out how to get root with SU and how to flash TWRP. Recetly got this new phone from sprint, got the last one stuck in a bootloop.
Downloading the deodex file now, just need to k ow what to do step by step if possible. I really appreciate your assistance

VIPDMERC said:
Not to familiar with everything, however I tried flashing CF Autoroot, i downloaded the beastmode kernel already. Just tryung to figure out how to get root with SU and how to flash TWRP. Recetly got this new phone from sprint, got the last one stuck in a bootloop.
Downloading the deodex file now, just need to k ow what to do step by step if possible. I really appreciate your assistance
Click to expand...
Click to collapse
Maybe this will help?
http://forum.xda-developers.com/showthread.php?p=62241848
Sent from my SM-N910P using Tapatalk

Im on the deodexed version can i use viper sound mod or 3 minit battery mod?

5.1.1 lollipop stockish rom
Help!! Is it possible to flash this rom to my note 4. Im coming from cm12.1. I really hate this rom and i really want stock back. Does anybody have detailed instructions to flash this to my phone? I am currently running cm 12.1 5.1.1

What baseband are u on

Note 4
Boe1

Will it work to go from boe1 to cog5? From cm12.1?

U have to flash the baseband so u can flash this rom
---------- Post added at 11:40 AM ---------- Previous post was at 11:37 AM ----------
dvtmg704 said:
U have to flash the baseband so u can flash this rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3174350

5.1.1 lollipop stockish rom
Thanks soooooo much! Now i have the baseband version i need. So now can you wqlk me through the steps of wiping and installing? I know how to do everything else but not the wiping. I know that you dont wipe the sd card. Bu i still need help thanks!

U have to use odin to flash it

No wiping or anything? Just flash it. Wont that brick?

Just flash the og5 baseband in odin select AP then select the baseband then flash then u can flash this rom

knoxjosh39 said:
No wiping or anything? Just flash it. Wont that brick?
Click to expand...
Click to collapse
Did u get it working

samep said:
The kernel is flashed in TWRP recovery. Odin that, making sure you've selected the option to disable OEM lock in Odin 3.10.6 and do not select auto reboot. When done with the TWRP Odin flash, pull USB and battery, wait 30 seconds, reboot to recovery and flash kernel.
Are you having trouble with Odin or boot? CF Auto Root is not used to root OG5. After flashing the kernel, flash the rooted ROM or root with SuperSU zip if just wanting to root stock and boot.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Uh oh. Lol. I did not see or tick any oem lock etc. I just pulled battery and flashed the kernel in twrp. All seems well. About to flash the odex rom. If i should worry please let me know? Afak im ok?
Sent from my SM-N910P using XDA Free mobile app

Droid2drummer said:
Uh oh. Lol. I did not see or tick any oem lock etc. I just pulled battery and flashed the kernel in twrp. All seems well. About to flash the odex rom. If i should worry please let me know? Afak im ok?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
AFAIK you may be OK despite that. I keep seeing that on the web so I thought maybe that's why OE1 thru OG5 bootloaders are giving fits and bricks (semi-bricks).
It may only apply to full tars; did you OTA or KIES to OG5?
The saga continues... feedback like this helps. Thanks!

samep said:
AFAIK you may be OK despite that. I keep seeing that on the web so I thought maybe that's why OE1 thru OG5 bootloaders are giving fits and bricks (semi-bricks).
It may only apply to full tars; did you OTA or KIES to OG5?
The saga continues... feedback like this helps. Thanks!
Click to expand...
Click to collapse
Seem fine. Just flashed this rom. Freeza stock. ..so far great. But for the love of android, still my weather animations in stock weather are frozen. Not moving. Anyone??
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 06:03 AM ---------- Previous post was at 06:01 AM ----------
Droid2drummer said:
Seem fine. Just flashed this rom. Freeza stock. ..so far great. But for the love of android, still my weather animations in stock weather are frozen. Not moving. Anyone??
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
This is pissing me off now...since ota of 5.1.1 officially ota 'd. Ive had great everything for a change. But weather animations borked. Nobody else mentioned it anywhere. So i dont get it. Ive wiped flashed reset etc.
Sent from my SM-N910P using XDA Free mobile app

Droid2drummer said:
Seem fine. Just flashed this rom. Freeza stock. ..so far great. But for the love of android, still my weather animations in stock weather are frozen. Not moving. Anyone??
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 06:03 AM ---------- Previous post was at 06:01 AM ----------
This is pissing me off now...since ota of 5.1.1 officially ota 'd. Ive had great everything for a change. But weather animations borked. Nobody else mentioned it anywhere. So i dont get it. Ive wiped flashed reset etc.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Since you have a OG5 tar, now you can wipe it and clean install Odin to fix that.
Maybe try that oem lock disabled this time? Odin 3.10.6
Sent from my SM-N910P using Tapatalk

Custom Recovery after 4.4.2?

Hello XDA community,
So I've owned the Note II since it came out basically. I used to ODIN custom recoveries and flash ROMs to it all the time. After the last update (4.4.2), I ODIN my phone back to stock to get the update; which of course included the dreaded KNOX. Afterwards, I just left it be due to the KNOX security and fear of messing up the phone. Long story short, I've been out of the loop for a couple of years and recently I've had the urge to try some of the newer ROMs and what not. More than likely this urge has spawned from the fact that I'll be doing away with my Note II soon, as it's very old and dated. So the fear of messing it up, has some what diminished.
So my question is... Is there anything special that I have to do before attempting to load a custom recovery after the 4.4.2 firmware update? Do I have to downgrade my current stock firmware first? Or is it still the same as it was before 4.4.2, just using ODIN to push the recovery and reboot? Any help is greatly appreciated! :victory:

Even with knox there is a chainfire setup. Trips knox but your out of warranty anyway. Just follow threads for your note 2. Mine is att.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
Even with knox there is a chainfire setup. Trips knox but your out of warranty anyway. Just follow threads for your note 2. Mine is att.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Wow, Thanks for the quick response! Would you mind looking through these instructions right quick, and see if I'm safe to go with this method?
ROOT AT&T GALAXY NOTE 2 AND INSTALL TWRP RECOVERY
1.) Download and extract CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.zip to your PC. You’ll get an Odin flash-able file in the .tar.md5 format.
2.) Flash the CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin. You can follow our exclusive guide on flashing firmware using Odin
3.) During the CF Auto-root process, if the device is stuck at bootlogo, remove the battery and boot into recovery mode manually to start the rooting process.
4.) Once the flashing process is finished, reboot the device and open the SuperSU app. If you encounter any KNOX warnings, then follow the instructions given in our KNOX disabling guide
5.) If everything is fine on the rooting end, download the latest Odin flash-able TWRP recovery from the Official TWRP page
6.) The recovery is in the form of .tar package, flash it using the Odin guide
7.) Reboot the device into recovery mode and check if the recovery is installed properly.

That looks like the right one. Been awhile my note is still going. Getting oppo r7s soon. But yes looks correct. Good flashing.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
That looks like the right one. Been awhile my note is still going. Getting oppo r7s soon. But yes looks correct. Good flashing.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Oh Nice! A guy I work with was just telling me about the oppo. He's also talking about getting it. It looks like a beast, from what I've seen on it.

Looks nice...metal body. 1/2 price of new note . lol and a flip phone beats an I device. Ha ha haaa
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
That looks like the right one. Been awhile my note is still going. Getting oppo r7s soon. But yes looks correct. Good flashing.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Not sure where I went wrong. I factory reset my phone before I even started. Pushed the ROOT using ODIN 3.10. Everything went fine, the phone rebooted and came back with "SuperSU stopped working" ,"Youtube stopped working", "Maps stopped working." Unable to open any of those apps. I factory reset again, and cleared the cache, but still no luck. Any suggestions for me?

Only thing I can think is su needs to be re flashed
Sent from my SAMSUNG-SGH-I317 using Tapatalk
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
I had once during root nothing opened. I flashed stock again then re flash SU then all good
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
Only thing I can think is su needs to be re flashed
I had once during root nothing opened. I flashed stock again then re flash SU then all good
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Tried to re-flash SuperSU, but still no luck. However, after all the other apps finished updating - I can use youtube and maps again. yay! lol.
By re-flashing stock, do you mean using ODIN to push a stock firmware back over to the phone? Did the stock 4.4.2 firmware ever leak out after release?
By the way, I really appreciate your advice on all this.

I did a 4.3 stock. Then I flashed DN3. But yeah gapps can be a pain too. Slipped my mind lol.
Yw for the tips but you're doing it . lol Have fun.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

abonides said:
I did a 4.3 stock. Then I flashed DN3. But yeah gapps can be a pain too. Slipped my mind lol.
Yw for the tips but you're doing it . lol Have fun.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
I ended up going about it a different way, but I don't think I would of tried it without you talking me through some of it. Although it's not a lot, I donated to you so you could at least have a beer on me. Thanks brother. KCCO.

Greatly appreciated & good luck with everything. We are all here to help each other.
Sent from my SAMSUNG-SGH-I317 using Tapatalk