Develop Bugs

[Q] Plz Help 4.3 down to 4.1.2. rooted tried a few

So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon

mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.

eletendre84 said:
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
Click to expand...
Click to collapse
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.

mentorkyrom said:
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
Click to expand...
Click to collapse
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.

eletendre84 said:
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
Click to expand...
Click to collapse
Tethering is available on CM11 just like it was on 10.2; would strongly recommend latest Philz Touch Recovery over either TWRP or CWM though. Although it is based on CWM, it has proven to be pretty much the superior recovery option for flashing any Android build number, plus it is highly customizable.
Philz Touch Recovery

this is how to downgrade
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones

smuther22 said:
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
Click to expand...
Click to collapse
Do you realize that this thread hasn't been used in a couple of months? I would assume the author has no more need of advice based on the inactivity. Also, once Knox is installed, it is on the phone to stay. PERIOD. NO DOWNGRADING POSSIBLE VIA ODIN. Custom ROMs of any build are fine via custom recovery, but any attempt to change the bootloader will trigger Knox and brick the phone. Dangerous info to be posting here, especially since someone else who doesn't know better might try this.

[Q] Samsung galaxy s3 i747M unroot on 4.3

Hi, im new on XDA but have quite a lot experience whit phone.
I tryed to root my samsaung galaxy s3 from Rogers (same as att) i747M whit CF-Auto root (im on android 4.3 jellybean).
I did it my phone is still working. I didnt flash a new recovery or anything.
Now i woudlike to remove root finally.
*the counter of the new Knox is set now to 0X1 but personnally i dont really mind.
The problem is that i woudlike to remove the root. I dont whant to downgrade i like 4.3 jellybean. (Anyway Att s3 cant be downgraded it will result to a soft brick)
I dont know how to remove the root and i woudlike to learn how to do it on my Samsung galaxy s3.
Thanks
(i was wondering about if i download the 4.3 stock Rom and i flash it will odin will it brick even if its on the same bootloader? because thats not downgrading...)
Thank you in advance for helping me out fast!

killer0123 said:
Hi, im new on XDA but have quite a lot experience whit phone.
I tryed to root my samsaung galaxy s3 from Rogers (same as att) i747M whit CF-Auto root ( su in the app itself4.3 jellybean).
I did it my phone is still working. I didnt flash a new recovery or anything.
Now i woudlike to remove root finally.
*the counter of the new Knox is set now to 0X1 but personnally i dont really mind.
The problem is that i woudlike to remove the root. I dont whant to downgrade i like 4.3 jellybean. (Anyway Att s3 cant be downgraded it will result to a soft brick)
I dont know how to remove the root and i woudlike to learn how to do it on my Samsung galaxy s3.
Thanks
(i was wondering about if i download the 4.3 stock Rom and i flash it will odin will it brick even if its on the same bootloader? because thats not downgrading...)
Thank you in advance for helping me out fast!
Click to expand...
Click to collapse
Im having the same problem. Cant downgrade to any version. Can't unroot phone, I have yhe the s3 i747 also on 4.3. Im kind.of.sad nobody has.replied to this. I tried unrooting removing.supersu via inapp permanent unroot option, then using rootbrowser to delete su files from system/bin and system/xbin. ( there wasnt any), root checker said my phone didny have root access.all I wanna do is upgrade to thr newest version lol then root that. Why does it.habe ti be so hard?

Nico de Pontiac said:
Im having the same problem. Cant downgrade to any version. Can't unroot phone, I have yhe the s3 i747 also on 4.3. Im kind.of.sad nobody has.replied to this. I tried unrooting removing.supersu via inapp permanent unroot option, then using rootbrowser to delete su files from system/bin and system/xbin. ( there wasnt any), root checker said my phone didny have root access.all I wanna do is upgrade to thr newest version lol then root that. Why does it.habe ti be so hard?
Click to expand...
Click to collapse
This will get you to the 4.4.2 stock update: http://forum.xda-developers.com/showthread.php?t=2789917
It depends on you having a custom recovery. It does provide a way to go back to the stock recovery once you are updated. I believe the same devolper has also posted the most recent update to NJ1 in a separate thread.

wifi not working now, and didnt update.
dawgdoc said:
This will get you to the 4.4.2 stock update: http://forum.xda-developers.com/showthread.php?t=2789917
It depends on you having a custom recovery. It does provide a way to go back to the stock recovery once you are updated. I believe the same devolper has also posted the most recent update to NJ1 in a separate thread.
Click to expand...
Click to collapse
it let me flash from mjb or whatever to the ne4. all that did was **** up my wifi. switch it to on and it just goes right back off. plus the files for the stock recoveries were spam.

Nico de Pontiac said:
it let me flash from mjb or whatever to the ne4. all that did was **** up my wifi. switch it to on and it just goes right back off. plus the files for the stock recoveries were spam.
Click to expand...
Click to collapse
Check that your bootloader and modem/baseband are matching in version number, this seems to be important in some of the newer kernels. If they do not match, flash the modem to correspond to the bootloader. If they are matching you may want to reinstall the modem on the off chance that it flashed incorrectly the first time.
Since you didn't mention any issues with calling or data I take it that the correct APNs are installed.
I don't understand why you call the stock recovery files spam. The link at 4. leads directly to the androidfilehost page to download the file. The other is an attachment to directly download the file from xda. To each his own.

questions about knox

So i have some questions about knox. I'm new to it and sadly had the 4.3 bootloader thrust upon me.
1. Is there a way to remove it/return to a different bootloader? Not just hide it like Billards thing does
2. One way I restore my phone if it freaks out is to run a 1 click stock rooted ljc program. I was reading in a Verizon forum flashing a stock version will brick my phone does this apply for sprint? They said mk3 not mk4
3.if I no longer can use that and need to fix say a soft Brick with no recovery what should I use/do
4. What are the main things i need to be aware or with knox?
I've been reading around and all I'm finding is its security. I know that it's bootloader related but every time I odin a tar file I didn't know that affected a the bootloader. This knox cap has me not even wanting to touch my phone.
Any help would be appreciated and you will get your thanks

Anyone?

I thought all this to but I took the plunge to root and did so with kingo root it went flawless and upon boring l booting just open super su and it will ask you if you want to disable knox just click Yea and you're done and to flash roms flash philz touch recovery with odin and make sure to make a backup is stock and flash away
Sent from my SPH-L900 using xda app-developers app

[Q] How to root

Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?

itsfredo said:
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
Click to expand...
Click to collapse
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.

The Sickness said:
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
Click to expand...
Click to collapse
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.

itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
I don't know if towelroot will root 4.2.2, but it doesn't install a recovery.
Rob

itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.

lordcheeto03 said:
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
This.
You really don't need CF Auto Root at all until all you want to do is root the stock rom.
If you want to install a customer rom, use Odin to install a custom recovery and flash whatever you want from there.

lordcheeto03 said:
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?

Use cf autoroot and flash clockworkmod through Odin. Download rommanager. Download a rom. Hit install rom from SD card. Pick your ROM from downloads.

itsfredo said:
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Click to expand...
Click to collapse
I understand your apprehension, i really do. What I've said to do has worked for me when i got the phone over a year ago, and has worked here recently when i did it again. I'm trying to tell you there is no need for an updated way of doing what you want. If you want root, use CFauto root. Like i said, that method was done specifically for MDB and MDL firmwares, there is no better choice. Newer yeah, but better? Not a chance. Your firmware is equally outdated and it's worked for millions of users without fail.
As far as a custom ROM goes, find one you want to use, put it on your SD card, pick a recovery (CWM, Philz, or TWRP), flash that in Odin, boot to recovery (power+volume up) , do a full wipe (system, data, and cache) select the ROM, and flash. No need to root at all if you want to go straight to a custom ROM.
EDIT: Obviously, you might want to perform a nandroid backup once you flash your recovery... but that's really optional as long as you have the stock Odin-flashable firmware. Totally up to you.
Sent from my SGH-M919 using XDA Premium 4 mobile app

Knox on hold?

I just got the note. Love the hardware but the software is pissing me off. I was waiting to root until I get the lollipop but I can't handle the lack of control and all the advertisements. I gave my S4 to my son and it is still running better than this new machine that should be a Monster.
So... Can I root without a custom recovery? If so what can I do about the knox before it unroots. If it's disabled or gone will I still get my 5.0?
More preferably can I get the stock recovery so I can get a copy of the 4.4.4 before it upgrades?

You can root stock without custom recovery but you'd need custom recovery for a nandroid backup or custom ROM or kernel.
Chain Fire auto root will disable Knox enough for root and Knox would not disable root. It's an Odin tar flash so no custom recovery required for root.
As far as upgrading, you'd have to fully un-root for OTA upgrade but there's always Kies or Odin for updates which would mean rooting again. As far as having a stock backup, the stock NK2 tar is available for download both in the Sprint Note 4 XDA forum and sammobile.com or even Kies. Voiding the warranty with Knox trip and risking root are the only true risks to consider. I'd suggest having the tools you need in a folder before you begin. CF auto root includes Odin; have a backup of NK2 stock tar and TWRP in case you need them. It wouldn't hurt to also have a custom ROM on hand to flash if you run into root issues.

samep said:
You can root stock without custom recovery but you'd need custom recovery for a nandroid backup or custom ROM or kernel.
Chain Fire auto root will disable Knox enough for root and Knox would not disable root. It's an Odin tar flash so no custom recovery required for root.
As far as upgrading, you'd have to fully un-root for OTA upgrade but there's always Kies or Odin for updates which would mean rooting again. As far as having a stock backup, the stock NK2 tar is available for download both in the Sprint Note 4 XDA forum and sammobile.com or even Kies. Voiding the warranty with Knox trip and risking root are the only true risks to consider. I'd suggest having the tools you need in a folder before you begin. CF auto root includes Odin; have a backup of NK2 stock tar and TWRP in case you need them. It wouldn't hurt to also have a custom ROM on hand to flash if you run into root issues.
Click to expand...
Click to collapse
Sprint's OTA is disabled with root or with out Knox. I rooted my daughter's S3 a week ago. Just used Odin to TWRP and flashed superuser. Chains asked if he could fight back and I said no. within 12 hrs Sprint sent an update and on reboot it was full un root. I was hoping if I was able to just put Superuser in that things would be manageable until I get 5.0.
If you have the stuff to unroot that would be awesome. It's impossible to say when I'll get the update. I can't get KIES to work on stock devices much less anything with root. Sprint doesn't use a serial number that samsung recognizes for a push. Does a Knox trip really void the Warranty if the phone is broken?

Root/Knox trip voids warranty as far as Samsung is concerned. Sprint and other extended warranties may not check but it's a warning that gets reiterated often for non liability reasons.
Odin the stock tar is only true un-root method that should work to restore OTA updates but also Odin the lollipop stock tar, when available, would be an option many rooted users would choose.

When I say root with stock ROM I don't mean install a ROM. I just want to have root control over apps. If I can just get super user unstalled things would be great. I"m lost where it comes to the knox though. and there seems to be a whole lot of it on this ROM. Can knox be disabled with out a trip. I know it can on the S4 and earlier. I just sent TWRp in with ODIN 3 or 4 times in a row then booted straight to recovery flashed superuser then as soon as it booted back in into Andoid I gave superuser permission to jump on knox.
I downloaded an app that says it can make ADB work with out root. But I can't get it to work on my pc

Knox trips now; no way known to undo that.
The stock kernel blocks ADB access. I haven't tried it but I thought I had read that ADB will work if phone is in recovery. Don't hold me to it.
Edit: reading your earlier post about Knox undoing root for OTA if flashing superuser and keeping Knox enabled, many rooted users found that they could un-root and download the NK2 update but it wouldn't flash due to "modified" system. I think Knox is evolving more complex in Note 4. Your method may be simpler but may not work as intended to OTA to lollipop. Odin is the method you'd have to be comfortable with before rooting.

samep said:
Root/Knox trip voids warranty as far as Samsung is concerned. Sprint and other extended warranties may not check but it's a warning that gets reiterated often for non liability reasons.
Odin the stock tar is only true un-root method that should work to restore OTA updates but also Odin the lollipop stock tar, when available, would be an option many rooted users would choose.
Click to expand...
Click to collapse
How do you get he tar for Odin? Your totally right. about Odin and the tar. I really don't have to wait to get the OTA when I can just find it myself.
How did you root, a recovery and Odin? I'm trying to get the ADB to work first. I guess ADB unlock OEM will wipe everything you have but opens the firmware also. I'm not going to try that way right now I just want to shoot superuser in that way.
Sorry didn't word that very well. How do you use Odin to root without installing a custom recovery?

http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Find the 910P link and download it; open the archive and placed the contents into a folder placed and named something like Odin or Note 4 root.

There are many users around xda that have sent their phones to samsung for a warranty repair with Knox tripped and had no problem. If you really look around you'll see this Knox bit thing is really no big deal. Just don't truly brick your phone and you'll be fine

Voiding Samsung warranty isn't an issue for most people anyways. I don't warranty through Samsung. I purchased my phone from Sprint and Sprint handles the warranty.

samep said:
http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Find the 910P link and download it; open the archive and placed the contents into a folder placed and named something like Odin or Note 4 root.
Click to expand...
Click to collapse
Thanks for the instructions here. It worked like a charm. I had no idea I could root with out a custom recover.

planb234 said:
Thanks for the instructions here. It worked like a charm. I had no idea I could root with out a custom recover.
Click to expand...
Click to collapse
You're welcome. If you want to backup stock recovery and use custom recovery and go back to stock recovery without flashing the the stock tar in Odin, try Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
You'd need custom recovery for backup nandroid or flashing custom ROMs, kernels, and mods (remember stock Rom is Odexed and some mods are intended for the ROM it was based on and may also be deodexed).
Flashify can also backup the stock kernel but I'd recommend the stock kernel flash because custom kernel will swap some modules that Flashify won't restore. You could skip the custom kernel unless you enjoy fiddling with custom apps and settings. The custom kernel will also have to be worked around for some video streaming and games. The stock kernel is quite capable and in my experience holds it own in benchmarks and battery savings.

planb234 said:
Voiding Samsung warranty isn't an issue for most people anyways. I don't warranty through Samsung. I purchased my phone from Sprint and Sprint handles the warranty.
Click to expand...
Click to collapse
You pay the extra $$ for sprints protection plan?

jhill110 said:
You pay the extra $$ for sprints protection plan?
Click to expand...
Click to collapse
Yes I pay 11 a month for insurance. Everything is covered for 6 months or something like that. The insurance is for breakage.
samep said:
You're welcome. If you want to backup stock recovery and use custom recovery and go back to stock recovery without flashing the the stock tar in Odin, try Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
You'd need custom recovery for backup nandroid or flashing custom ROMs, kernels, and mods (remember stock Rom is Odexed and some mods are intended for the ROM it was based on and may also be deodexed).
Flashify can also backup the stock kernel but I'd recommend the stock kernel flash because custom kernel will swap some modules that Flashify won't restore. You could skip the custom kernel unless you enjoy fiddling with custom apps and settings. The custom kernel will also have to be worked around for some video streaming and games. The stock kernel is quite capable and in my experience holds it own in benchmarks and battery savings.
Click to expand...
Click to collapse

I'm going to give this method a shot. I'm sick of waiting on v Sprint to delivery anything but hidden costs. I thought it would be cool to have the original lollipop delivered to my phone but honestly I wouldn't use it long anyways. There is bound room for outside influence in a 700 dollar device. I'm going with the deodexed 5.0 on xda. I'll let you know how the flashify toy recommended goes. Your your saying it can be used to back entire stock device without custom recovery so i can lock it down before i start sending repeated knox trjps to Samsung? In putting all good Samsung apps into backup and then locking Samsung from my device indefinite

planb234 said:
I'm going to give this method a shot. I'm sick of waiting on v Sprint to delivery anything but hidden costs. I thought it would be cool to have the original lollipop delivered to my phone but honestly I wouldn't use it long anyways. There is bound room for outside influence in a 700 dollar device. I'm going with the deodexed 5.0 on xda. I'll let you know how the flashify toy recommended goes. Your your saying it can be used to back entire stock device without custom recovery so i can lock it down before i start sending repeated knox trjps to Samsung? In putting all good Samsung apps into backup and then locking Samsung from my device indefinite
Click to expand...
Click to collapse
I believe I was saying you could backup stock recovery, Odin flash a custom recovery, perform a nandroid backup, flash a custom ROM.
Not sure who it was that asked but attempting to restore a nandroid and restore stock recovery in order to gain OTA update of lollipop may not be a sure thing. I'm not sure if it would work coming from CM12 because the partitions may be different; unsure myself. It's also no guarantee that the update feature wouldn't still flag the system as modified and refuse to install the update. Don't hold me to that; I'd recommend Odin stock tar to come back to KitKat but still unsure if OTA would be possible, if that is your goal. And most, if not all developers, recommend a full wipe/clean install before flashing custom ROMs and updates. Odin to stock tar is also a common suggested troubleshooting step as well. There is Kies and Odin for Samsung lollipop that would still give you the update for rooted devices.
I'd also recommend having CF Auto Root that includes Odin downloaded and standing by along with tar for TWRP, and NK2 stock tar. If things go wrong, you'll recover quicker with less stress. And wait until you have some to time to recover before attempting. Gotta be comfortable with Odin and have the Samsung PC drivers pre-installed and willing to risk the consequences. Others and myself can offer helpful advice, if needed.
The rooted warranty concerns have been explained away by a few. But if you feel more comfortable taking a phone in for repair with stock recovery and a restored stock nandroid go for it. You at least have to accept the notion that your custom ROM may be flashed over if taken in as well.
As far as skipping the CF auto root, I think you can if flashing a rooted ROM in custom recovery but I don't know for sure you can. I'm guessing you can because there's a flashable SuperSU that you can flash to root stock after Odin of custom recovery. A rooted ROM shouldn't be different.
Sorry if I've made assumptions. Just wanted to be clear and not misleading. Flashify can simplify things, especially stock recovery backup and restore. But don't use Flashify to backup and restore kernels unless you're also manually restoring the lib modules along with it; Flashify won't do that for you.

The flashify worked i doubt i will ever put my device back to stock. Waitng for the ota i noticed that Samsung was running updates to my device at least 10 times a day. Security updates meaning they are securing their own interests. yes it says warranty voided but I'm not sure what that means. Samsung won't sell me a phone they would rather let sprint sprint fiscally rape me in the deal. I've not seen on any Samsung site where i can purchase or warranty a device. there access is denied. The only company i allow is Google. True they market some of my information but the majority of their interest is bug reports which is used for improvement. Improvement warrants bandwith. I had the lollipop on my s4 months ago and Samsung is not even releasing it in the us. In short Samsung is left wanting in support. I rooted my device this morn and will install deodexed lollipop when i get off work. Your advice has been helpful and i lookforward to more on upgrading my kernel.

Here's my experience this past week. I flashed the stock tar and hit update now. I got the up to date message. Rooted, tried again... No dice system has been blah blah blah. I unrooted system update : system up to date. Rerooted flashed twrp of course no go. Unrooted flashed stock recovery and.... No go. Re-flashed stock rom... System up to date. Flashed twrp no go. Flashed stock recovery and still no go.
So, it seems once you flash custom recovery there's no going back without flashing the stock rom. Whew, that was a mouth full.
It's mho this Knox thing is blown way out of perportion. Hardware warranty repairs will be done even if Knox is tripped. Plenty of members have done so. If one were to brick their phone flashing that might be a different story.

I don't want the stock ROM anyways. Samsungs overkill with the Knox is equivalent to Microsoft Security update. Samsung makes some sweet hardware but fails the open source. Their trying to be Steve Jobs or Bill Gates. If wanted a to not upgrade I would stick with a Nexus. Google is the only company who agrees that your device is yours and you should always try and improve it. I was seriously getting angry being put last in the world for the newest software. Samsung saying they are updating my device which basically meant Knox was spying and correcting any changes I made. Bricking is most likely to occur if you upgrade with stock recovery.

I will say this for sprint warranty. They don't care. As long as they are able to slip in a several hidden costs with any change or purchase they are satisfied. Sprint repair are all 3rd party representatives. If you happen to find an actual sprint location you will be sent to a third party sprint store. The 3rd party will fix you up as of they don't they don't get paid.