New to this phone and I am running 4.1.2 there is a system update a 4.3 that's already downloaded and ready to install but I wanted to make sure the update didn't install any new locks on my phone before I accept. I plan on rooting soon.
Thanks
Rich
U get knox but there are ways to still root with knox so go ahead update
High Definition Note II
Uuum hold on. If you plan to root your phone there is no point in allowing the OTA which does install KNOX. Root now and save that extra trouble.
tx_dbs_tx said:
Uuum hold on. If you plan to root your phone there is no point in allowing the OTA which does install KNOX. Root now and save that extra trouble.
Click to expand...
Click to collapse
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..
I Would Accept It.
doubledragon5 said:
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..
Click to expand...
Click to collapse
If I was in this position, I would accept the update as doubledragon5 said and move forward with root, etc. I have 4.1.2 right now and want the 4.3 update, but I'm rooted and trying to figure out how to unravel this to get to 4.3 myself.
flashred said:
If I was in this position, I would accept the update as doubledragon5 said and move forward with root, etc. I have 4.1.2 right now and want the 4.3 update, but I'm rooted and trying to figure out how to unravel this to get to 4.3 myself.
Click to expand...
Click to collapse
If your rooted, go back to bone stock MC2 like I have mentioned in a few other threads. accept the 4.3 udate from sprint, re-root using the tookit, then flash away...
doubledragon5 said:
If the poster wants to install 4.3, then accept the update, root, then flash your 4.3 rom.. This way you won't have all those reboot, lock up issues, that people keep on having.. Plus most devs do not have knox filex in their roms.. And you won't have to flash the wifi fix..
Click to expand...
Click to collapse
doubledragon5 said:
If your rooted, go back to bone stock MC2 like I have mentioned in a few other threads. accept the 4.3 udate from sprint, re-root using the tookit, then flash away...
Click to expand...
Click to collapse
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.
flashred said:
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.
Click to expand...
Click to collapse
I'm wondering the same thing. But if we root then accept the OTA won't that enable the knox counter? So that if we now, "flash away".... won't every flash be counted?
Shouldn't we root, then install the custom roms without the knox? Or do the custom roms also include the knox counter tripping mechanism?
I would like to know how this works also.
Thanks.
I just recently came from 4.1.2 rooted running a deoxided stock rom. I didn't do the OTA update to 4.3. I used the TeamRejects Deoxidexed rooted deknoxed stock rom, the updated MK4 modem, and the WiFi fix. It took about 15-20 minutes to get everything done. I needed to download Odin too for WiFi fix. I didn't run the WiFi fix till I knew there was an issue.
Not much of complaint, but I wish there was a kernel like Perseus for TouchWix based roms. The only one I found was Devil Kernel, but for whatever reason, wasn't stable with TeamReject's ROM. I didn't really care for his custom Kernel ajdustment manager and STweaks didn't work with it at all. Ideally, I prefer a stock rooted deknoxed deoxidized bare bones rom (just phone, contacts, google play) so I have a working phone and can access Google Play so I can install the apps I prefer. The closest I found was Classic Rom but it freezes on initial rom load; Plus, I'm not a fan of the colors and the few things he choose to include.
Stock 4.3 Deodexed, deknoxed, Rooted Rom Available?
lovekeiiy said:
I just recently came from 4.1.2 rooted running a deoxided stock rom. I didn't do the OTA update to 4.3. I used the TeamRejects Deoxidexed rooted deknoxed stock rom, the updated MK4 modem, and the WiFi fix. It took about 15-20 minutes to get everything done. I needed to download Odin too for WiFi fix. I didn't run the WiFi fix till I knew there was an issue.
Not much of complaint, but I wish there was a kernel like Perseus for TouchWix based roms. The only one I found was Devil Kernel, but for whatever reason, wasn't stable with TeamReject's ROM. I didn't really care for his custom Kernel ajdustment manager and STweaks didn't work with it at all. Ideally, I prefer a stock rooted deknoxed deoxidized bare bones rom (just phone, contacts, google play) so I have a working phone and can access Google Play so I can install the apps I prefer. The closest I found was Classic Rom but it freezes on initial rom load; Plus, I'm not a fan of the colors and the few things he choose to include.
Click to expand...
Click to collapse
So, you came exactly where I did except you with a different ROM. I would like to get from my 4.1.2 rooted up to 4.3 rooted stock,deodexed, deknoxed if at all possible.
flashred said:
Thank you! You're the first to shed some light on this for me. To get back to stock using the toolkit, would I need to first flash stock recovery, then Stock Firmware, then bone stock MC2? Afterwards boot in, accept the update, then re-root using the toolkit.
Click to expand...
Click to collapse
Sorry for not getting back sooner. I have been busy with work, and family things.Use billards return to full stock with counter reset. It installs everything including recovery, boot loader,firemware etc... Then set up your phone, when prompt accept the ota update.. Once done retoot, and flash what ever 4.3 rom you want.. The knox counter will still be there, but if you need a trip back to Sprint, go back to Full MC2 stock, knox counter will no longer be there.. Most 4.3 room do not include the Knox files so no worries there.
flashred said:
So, you came exactly where I did except you with a different ROM. I would like to get from my 4.1.2 rooted up to 4.3 rooted stock,deodexed, deknoxed if at all possible.
Click to expand...
Click to collapse
Sounds like it. The odd part, I have been able to flash Reject's stock deoxidezed deknoxed rom with no problem. I tried to flash Classic 3, but it froze on Classic's initial loading page (the one after the Samsung boot loader). I had issues another rom, but turned out it was for the international model; I wasn't paying attention where I was in the forums.
If you do what I did, you'll need to flash modem update using Odin on the PC. So, you may need to download Odin.
---------- Post added at 05:04 AM ---------- Previous post was at 04:56 AM ----------
Depending on what you like to do, you may find 4.3 MK4 more limiting, espcially on the TouchWiz side. AOSP probably more mod friendly at this point. From what I've been able to find, there is only one custom kernal for 4.3 TouchWiz which is Devil's Kernal. It's solid, but my phone was unstable. Not sure if the phone since I may have taken out something it used when I was trying to debloat the phone. Didn't care for his Kernel Tweak manager. Neither the stock or devil's kernal supports Stweaks. Neither I could figure out how to change the boat loading animation.
I have nothing against AOSP projects. I like them. But as far as I know, none support the Spen, which I like to use with web browsers. Don't use the Samnsung Spen apps. Just wasn't that impressed with them, but I see how they can be useful. Although, SketchPro is really nice with it. I just find TouchWiz is more than sufficient for my needs and stock isn't as quirky.
Related
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Monoclypsus said:
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Click to expand...
Click to collapse
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
ok
topherk said:
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
Click to expand...
Click to collapse
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Monoclypsus said:
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Click to expand...
Click to collapse
Yeah, that same method should work. I personally like the custom recoveries, but understand your desires to leave it at stock recovery (not triggering the flash counter).
Like I mentioned before, Samsung hasn't (and most likely won't) locked their bootloaders, so any rooting method that has worked in the past should work in the future. Just make sure to read the last 3-4 pages of the thread for whatever method you're trying to use to see if there are any issues. I know an earlier version of mskip's toolkit was having issues with JB for a little bit (it's updated now).
Well I'm gonna give it a shot. Ill let you know how it turns out.
Sent from my SPH-L710 using xda app-developers app
Just went with cf autoroot. Worked fine.
Sent from my SPH-L710 using xda app-developers app
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
jkj said:
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
Click to expand...
Click to collapse
I replied to your thread. I hope it works for what you need.
Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
thunderstorm116 said:
Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
lordcheeto03 said:
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
Click to expand...
Click to collapse
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
thunderstorm116 said:
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
Click to expand...
Click to collapse
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
lordcheeto03 said:
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
Click to expand...
Click to collapse
Ah, okay. I think I understand that, I'll give that a try. Thanks for all your help.
Okay, so I tried doing everything you told me to do and got some weird results and thought I'd post them for anyone else that may run into this problem.
I flashed a custom recovery through Odin, then flashed the AOSP Liquid Rom like you said. I then flashe the stock MD5 file through Odin and let it do its thing. Once it was done, that's where the weird stuff started. The phone rebooted as it should, but then it got hung on the white T-mobile screen. It just sat there for a very long time. Now I've done this enough times to know when its taking too long and there's a problem.
So I did something that I know probably shouldn't have done and I held down the power button until it turned off. I then tried to boot it again to no avail, same thing.
After this I booted into the stock recovery and decided to do a factory data reset from there. (I was pretty sure there was nothing wrong with the stock Rom as I've used it before; there must have been something still there from the Liquid Rom causing problems.) When I rebooted from the recovery this way, it finally booted right up.
I now thought that I needed to flash CF-AutoRoot and then triangle away, but no, for some strange reason my device status now reads OFFICIAL!
I searched for the update and it is now in the process of downloading.
(Strangely enough though, the lock sound from wicked V8, is STILL there. I don't get it and I don't even want to know anymore.)
Sorry for the super long post, but I thought that if anyone else was having my same problem they should see this.
Thanks again for all your help and I hope you'e having a great Thanksgiving.
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.
Hello All
So i ended switching my phone m919 4.3 for m919 4.2.
I have a few questions since im a NOOB.
Do i benefit anything if i update to 4.3?
If i root my phone (m919 4.2) do i lose warranty?
Can i unroot 4.2, go to stock, than update to stock 4.3?
I know there is a version of 4.3 out there with no KNOX, if i were to install that, can i still go back to stock 4.2 ?
Thanks
Xx_Joe_Wireless_xX said:
Hello All
So i ended switching my phone m919 4.3 for m919 4.2.
I have a few questions since im a NOOB.
Do i benefit anything if i update to 4.3?
If i root my phone (m919 4.2) do i lose warranty?
Can i unroot 4.2, go to stock, than update to stock 4.3?
I know there is a version of 4.3 out there with no KNOX, if i were to install that, can i still go back to stock 4.2 ?
Thanks
Click to expand...
Click to collapse
#1: All the custom cwm/twrp flashable 4.3 zip file roms are KNOX free. (no knox)
#2: You will only get KNOX if you do a Kies update, Odin Flash 4.3 rom or allow the OTA update.
#3: As long as you don't have KNOX you can always flash back to any 4.2.2 zip file cwm/twrp roms.
#4: If you are rooted right now there is NO NEED to un-root before flashing a cwm/twrp flashable
zip file 4.3 custom rom like the Wicked or Darthstalker roms.
If you are on a 4.2.2 rom and you don't do any of the three things in #2 you do not need to worry about
KNOX at all.
I'm on stock 4.2.2 (not rooted), I've rooted my previous devices in the past. I'm coming from the t-mobile galaxy s2.
However, I personally love stock touchwiz with root, and a few bloatware items removed. But, I've read nothing but problems and issues from people having network connection issues to other things happening with their 4.3 flashes. And as to not discredit those people, I'm quite sure they have read and re-read directions several times, but still have issues. So, until those get worked out. I plan to stay right where I'm at. If I do end up rooting, it will be because I ran out of space on my phone and will be moving data to the sd card.
Hopefully you are a lucky one who doesn't suffer any data drops or sound issues when flashing to 4.3.
to each their own though.
HTCMDA said:
I'm on stock 4.2.2 (not rooted), I've rooted my previous devices in the past. I'm coming from the t-mobile galaxy s2.
However, I personally love stock touchwiz with root, and a few bloatware items removed. But, I've read nothing but problems and issues from people having network connection issues to other things happening with their 4.3 flashes. And as to not discredit those people, I'm quite sure they have read and re-read directions several times, but still have issues. So, until those get worked out. I plan to stay right where I'm at. If I do end up rooting, it will be because I ran out of space on my phone and will be moving data to the sd card.
Hopefully you are a lucky one who doesn't suffer any data drops or sound issues when flashing to 4.3.
to each their own though.
Click to expand...
Click to collapse
You missed the people who update just their radios to MK2 and no longer have those mobile data problems on 4.3. There's a guide in the General section that's N00B friendly.
lordcheeto03 said:
You missed the people who update just their radios to MK2 and no longer have those mobile data problems on 4.3. There's a guide in the General section that's N00B friendly.
Click to expand...
Click to collapse
I know, that's what I'm talking about. People who updated the radios and flashed 4.3, still have issues. still have data drops, sometimes wifi doesn't work, and tethering is broken.
HTCMDA said:
I know, that's what I'm talking about. People who updated the radios and flashed 4.3, still have issues. still have data drops, sometimes wifi doesn't work, and tethering is broken.
Click to expand...
Click to collapse
I have ZERO issues. I built my rom from stock 4.3 firmware. All Knox free. Flashed new modem.bin through Odin and all is good. Wifi is good. Data is good.
People who complain about data and whatnot is user related.
My S4 Is Insane
DEVIANT DEVELOPMENT
Misterjunky said:
#1: All the custom cwm/twrp flashable 4.3 zip file roms are KNOX free. (no knox)
#2: You will only get KNOX if you do a Kies update, Odin Flash 4.3 rom or allow the OTA update.
#3: As long as you don't have KNOX you can always flash back to any 4.2.2 zip file cwm/twrp roms.
#4: If you are rooted right now there is NO NEED to un-root before flashing a cwm/twrp flashable
zip file 4.3 custom rom like the Wicked or Darthstalker roms.
If you are on a 4.2.2 rom and you don't do any of the three things in #2 you do not need to worry about
KNOX at all.
Click to expand...
Click to collapse
im on 4.3 stock can i downgrade i dont care about warranty or knox
Just to point out, I never said EVERYONE. I just said people.
I'm sure some work flawless, and others not so much. But I know I read through page after page of issues. Some stated theirs worked, but I feel I read more non-working comments than working ones.
re: downgrade
mrej201 said:
im on 4.3 stock can i downgrade i dont care about warranty or knox
Click to expand...
Click to collapse
You cannot downgrade if you are on stock 4.3, whether you care about warranty or not.
well thank you !
Misterjunky said:
You cannot downgrade if you are on stock 4.3, whether you care about warranty or not.
Click to expand...
Click to collapse
I had a question also, if I am currently on MDL with the new radio, how would I update to 4.3 and then install custom recovery again and gain root? Is that possible?
I'd flash a stock rooted rom
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
I'd flash a stock rooted rom
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just wanted to update to the new bootloader with the new LTE modem, because I have been seeing some problems b/w switching with LTE when using the new radio without the new LTE modem.
I have a T-mobile Galaxy S4, SGH-M919 running android 4.2.2 and want to upgrade to android 4.3. Okay my question is can I remove knox from the update before updating? I HATE KNOX. I saw where over at s4 mini archive they showed a way that they say it can be removed. Any ideas? Anyone tried this? Any other ways to remove??? Any help would be great. I am sorry if this has been posted or asked before, I have not seen it. http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html
Just use this. http://forum.xda-developers.com/showthread.php?t=2544612 and install a custom rom. Any reason why you want 4.3? You can install 4.4.4 which just came out. Remember to just flash modem only and not the lte modem or you will break sound. If you want to stay completely stock and not have Knox there is no way.
+1 on custom rom. Something like this: http://forum.xda-developers.com/showthread.php?t=2876946
Sorry been a little busy. I'm currently using the MDL bootloader, no knox. I hear there is performance and feature advantage to updating to a newer bootloader. The reason I am looking at 4.3 is that some people have stated that you can remove knox from the bootloader in 4.3. The people stated that they have been able to do this to the S4 mini's 4.3 bootloader. I have looked at the links you two have given me, thank you. What bootloaders are you two using? Also have you seen this as this is what got me thinking. http://forum.xda-developers.com/showthread.php?t=2549357
Bootloader has nothing directly to do with performance. Be careful what you read.
lalec said:
Bootloader has nothing directly to do with performance. Be careful what you read.
Click to expand...
Click to collapse
True. But I would prefer to be 100% knox free. So not just a knox free rom, but the bootloader as well. Staying on android 4.2.2 will do that but at the same time I would like to upgrade to a newer android version. I have seen some nice custom roms with nice performance, but they are 4.3 and newer. And this is why I am looking.
Jamessr79 said:
True. But I would prefer to be 100% knox free. So not just a knox free rom, but the bootloader as well. Staying on android 4.2.2 will do that but at the same time I would like to upgrade to a newer android version. I have seen some nice custom roms with nice performance, but they are 4.3 and newer. And this is why I am looking.
Click to expand...
Click to collapse
You can keep MDL boot loader, and flash 4.3, 4.4.2, or 4.4.4 ROMs no problem. I've got an M919 with MDL boot loader and am currently running Dirty Unicorns (4.4.4-based) ROM.
I've got all the benefit of the latest version of Android (plus many customizations!) and no Knox.
The only think that you can't do on the MDL boot loader is run a newer LTE modem... the LTE modem (non-hlos.bin) is tied to the boot loader. However the GSM modem (modem.bin) is not, so you can update that part of it. It's something to keep in mind, but the LTE modem in MDL is fine and works for me quite well even in marginal signal areas.
Marc
Frankenscript said:
You can keep MDL boot loader, and flash 4.3, 4.4.2, or 4.4.4 ROMs no problem. I've got an M919 with MDL boot loader and am currently running Dirty Unicorns (4.4.4-based) ROM.
I've got all the benefit of the latest version of Android (plus many customizations!) and no Knox.
The only think that you can't do on the MDL boot loader is run a newer LTE modem... the LTE modem (non-hlos.bin) is tied to the boot loader. However the GSM modem (modem.bin) is not, so you can update that part of it. It's something to keep in mind, but the LTE modem in MDL is fine and works for me quite well even in marginal signal areas.
Marc
Click to expand...
Click to collapse
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.
HKSpeed said:
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.
Click to expand...
Click to collapse
A stock firmware? If it contains the bootloader, it will automatically replace your existing one.
tetakpatalked from Nexus 7 flo
HKSpeed said:
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.
Click to expand...
Click to collapse
Yes, it's based off AOSP. See the Samsung home page for Dirty Unicorns here. Also the G+ Community for it.
If you are looking for a TW ROM, I had a great experience with GoldenEye v. 38 over the summer. Very stable, and everything worked, even on my ATT version S4 I337 using SafeStrap. I got sick of SafeStrap limitations and eventually bought a M919 so I could do anything I wanted ROM wise... but GoldenEye was very nice. Debloated, very stable, felt good.
Being very satisfied with my current version of Dirty Unicorns, I'll probably not change any time soon, thought I've been tempted to install SlimKat and build up the features I want. I use SlimKat on a tablet, and like it's very light footprint. Quite zippy.
Marc
tetakpatak said:
A stock firmware? If it contains the bootloader, it will automatically replace your existing one.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Just something to remember: Bootloaders (all the bad KNOX junk) CANNOT be flashed via custom recovery. So if you are flashing a stock ROM (firmware?) via custom recovery you will NOT get KNOX. If, however you decide to flash a ROM/firmware via Odin chances are very good that you will be getting a new bootloader and all the KNOX garbage it brings.
TLR
If you flash via recovery you won't get KNOX, if you flash via Odin you probably will.
Modems must also be flashed in Odin, but as far as KNOX goes, it's the bootloader you don't want.
Okay, does this mean I have knox or do not have knox.
Jamessr79 said:
Okay, does this mean I have knox or do not have knox.
Click to expand...
Click to collapse
It seems to me like you're still knox-free
tetakpatalked from Nexus 7 flo
Jamessr79 said:
Okay, does this mean I have knox or do not have knox.
Click to expand...
Click to collapse
Yup.
No Knox there.
You would see a Knox warranty line in that bootloader screen if you had it.
Cool, so it worked.
question
lordcheeto03 said:
Just something to remember: Bootloaders (all the bad KNOX junk) CANNOT be flashed via custom recovery. So if you are flashing a stock ROM (firmware?) via custom recovery you will NOT get KNOX. If, however you decide to flash a ROM/firmware via Odin chances are very good that you will be getting a new bootloader and all the KNOX garbage it brings.
TLR
If you flash via recovery you won't get KNOX, if you flash via Odin you probably will.
Modems must also be flashed in Odin, but as far as KNOX goes, it's the bootloader you don't want.
Click to expand...
Click to collapse
So what you are saying is if I flash a stock zip via custom recover no KNOX? Has this been tested? I removed knox on 4.3 but got crazy and tried 4.4.4 now random restarts.
Jamessr79 said:
So what you are saying is if I flash a stock zip via custom recover no KNOX? Has this been tested? I removed knox on 4.3 but got crazy and tried 4.4.4 now random restarts.
Click to expand...
Click to collapse
Yes, what I'm saying has been tested and confirmed 100%. There is no way to flash a KNOX-implemented bootloader (or ANY bootloader for that matter) via custom recovery. You seem to have the misconception that the KNOX apps within the ROM is what all the KNOX talk is about. If anything, it's only a small part. Now, I'm not absolutely certain of how this works as I've only followed the technical posts in the Development only forum regarding this for the first 10 or so pages, so if I say something that isn't exactly accurate, please forgive me. The basic gist is that when you hear about KNOX and why it's not necessarily wanted in the updated firmwares isn't because of a few user-removable apps; it's something at the hardware level that, when during the boot up tests and checks, it notices that there is a custom kernel or custom recovery in place instead of the expected stock kernel/recovery, it blows an e-fuse and forever after tells anyone who looks at the download mode that the device has been modified at one point or another.
About the random restarts, without knowing whether you updated from 4.3 to 4.4.4 via custom recovery or other official means, all I can say is to try a factory reset and/or use Odin to re-flash the firmware and do a factory reset after that.
lordcheeto03 said:
Yes, what I'm saying has been tested and confirmed 100%. There is no way to flash a KNOX-implemented bootloader (or ANY bootloader for that matter) via custom recovery. You seem to have the misconception that the KNOX apps within the ROM is what all the KNOX talk is about. If anything, it's only a small part. Now, I'm not absolutely certain of how this works as I've only followed the technical posts in the Development only forum regarding this for the first 10 or so pages, so if I say something that isn't exactly accurate, please forgive me. The basic gist is that when you hear about KNOX and why it's not necessarily wanted in the updated firmwares isn't because of a few user-removable apps; it's something at the hardware level that, when during the boot up tests and checks, it notices that there is a custom kernel or custom recovery in place instead of the expected stock kernel/recovery, it blows an e-fuse and forever after tells anyone who looks at the download mode that the device has been modified at one point or another.
About the random restarts, without knowing whether you updated from 4.3 to 4.4.4 via custom recovery or other official means, all I can say is to try a factory reset and/or use Odin to re-flash the firmware and do a factory reset after that.
Click to expand...
Click to collapse
Okay, I misunderstood on what you said could be flashed, but will have to take a look. Could you please point me in the right direction for that forum. As far as the misconception goes I do know that KNOX is in the bootloader. I also know that KNOX app/software is found in the rom as well. As for KNOX being in the rom Titanium Backup helps to remove most of it. Or I can just installing a custom rom that has it removed. The main reason that I had started this forum was to remove the KNOX from the bootloader. The reason I pointed to http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html in the first post is because they stated it could be done. After doing some other looking around and talking to others I tried it. Seems like it works on android 4.3, but 4.4.2 and 4.4.4. when I try to do the same it is not happy. I updated via Odin. The first time was 4.2 to 4.3 after modding the bootloader and not the rom. It works fine no KNOX lines in download mode. Still KNOX in the rom but uninstalled using Titanium Backup. Currently I am running android 4.3 on my Galaxy S4 no issues and as far as I can tell no KNOX.
Jamessr79 said:
Okay, I misunderstood on what you said could be flashed, but will have to take a look. Could you please point me in the right direction for that forum. As far as the misconception goes I do know that KNOX is in the bootloader. I also know that KNOX app/software is found in the rom as well. As for KNOX being in the rom Titanium Backup helps to remove most of it. Or I can just installing a custom rom that has it removed. The main reason that I had started this forum was to remove the KNOX from the bootloader. The reason I pointed to http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html in the first post is because they stated it could be done. After doing some other looking around and talking to others I tried it. Seems like it works on android 4.3, but 4.4.2 and 4.4.4. when I try to do the same it is not happy. I updated via Odin. The first time was 4.2 to 4.3 after modding the bootloader and not the rom. It works fine no KNOX lines in download mode. Still KNOX in the rom but uninstalled using Titanium Backup. Currently I am running android 4.3 on my Galaxy S4 no issues and as far as I can tell no KNOX.
Click to expand...
Click to collapse
Wait.... your on 4.3 or 4.2 and have been able to unlock the bootloader on them?? Everything you said above is exactly what I have seen and heard also with the addition that the signatures not matching verification checks are what is blowing the q fuse or what Knox and the Samsung / att security freak out about right?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I was on 4.2 and downloaded the stock 4.3 to my Linux pc. I then did what was stated on the s4 mini forums and was able to remove Knox from the bootloader, then the rom via titanium backup. Note as far as I know you can't remove Knox once it is already there.