Related
alrights guys I didn't see this anywhere in ur forum so here it is, after exchanging my s4 for a replacement, I got it with 4.3 and all this Knox nonsense already installed, Now I don't really care that much for samsung's warranty but I went out and look for a way to root our latest without triggering Knox counter just head on to the thread below and check it out... it has a catch but I would say it's worth the trade off.
http://forum.xda-developers.com/showthread.php?t=2565758
lol Dude, we just discussed this in another forum and this has been discussed in many forums. :silly:
Anyways... I've used this Verizon method on my buddies ATT Galaxy S4 with a locked bootloader on a 4.3 MK2 baseband. It does not trip the KNOX flag. There are no "trade-offs." It functions well. Chainfires AutoRoot works as well.
So with this method you cannot make a nandroid backup OR even restore one?
HTCMDA said:
So with this method you cannot make a nandroid backup OR even restore one?
Click to expand...
Click to collapse
I have not tried to make a nandroid with a locked BL and will try tomorrow (damn sure it won't work). Best bet is to try Online Nandroid Manager. Nandroid backups require a custom recovery, it has nothing to do with having root.
Ive been out of the rooting world for a while, but with research, Ive caught up a little. However I do have a couple of questions;
With this method, can I still install a custom vanilla rom with 4.3/4.4?
If not, what are the benefits?
knipp21 said:
Ive been out of the rooting world for a while, but with research, Ive caught up a little. However I do have a couple of questions;
With this method, can I still install a custom vanilla rom with 4.3/4.4?
If not, what are the benefits?
Click to expand...
Click to collapse
No, this will only root your phone (give your apps su/superuser access). You will still need to flash a custom recovery (i.e., PhilZ, TWRP, CWM) to flash roms like a custom Vanilla ROM. If you are on 4.2.2 bootloader, you can simply flash a custom recovery and flash the ROM. If you are on 4.3, you will be on the KNOX bootloader and if you flash a custom recovery to flash the ROM, you will void your KNOX warranty. If you don't care about the warranty or has expired, there is no difference.
1) Download Vanilla Rom,
2) Flash custom recovery tar (i.e., PhilZ, TWRP, CWM).
3) Go into recovery and flash rom.
4) ????
5) ??
6) Profit.
xdapowerapps said:
No, this will only root your phone (give your apps su/superuser access). You will still need to flash a custom recovery (i.e., PhilZ, TWRP, CWM) to flash roms like a custom Vanilla ROM. If you are on 4.2.2 bootloader, you can simply flash a custom recovery and flash the ROM. If you are on 4.3, you will be on the KNOX bootloader and if you flash a custom recovery to flash the ROM, you will void your KNOX warranty. If you don't care about the warranty or has expired, there is no difference.
1) Download Vanilla Rom,
2) Flash custom recovery tar (i.e., PhilZ, TWRP, CWM).
3) Go into recovery and flash rom.
4) ????
5) ??
6) Profit.
Click to expand...
Click to collapse
I dont really care about the warranty, if its samsung and not t mobile.. But that isnt a def answer yet.
And ok, I guess Ill hunt the threads to see how to install the recovery. Thanks man
knipp21 said:
I dont really care about the warranty, if its samsung and not t mobile.. But that isnt a def answer yet.
And ok, I guess Ill hunt the threads to see how to install the recovery. Thanks man
Click to expand...
Click to collapse
Well, even some of the T-Mobile apps now recognize if you have root and could possibly use that as proof that you voided your warranty. Tmobile/Samsung, vice versa, won't be much difference. You'd just have to find a store person that isn't knowledgeable on the subject and get a replacement. Good luck.
yea about that!
Yea I notice after I posted LOL.. a and here I was thinking I found the "holy grail" of rooting LOL!! but anyway those that Need to know just like it has been said.. this will get u rooted with out triggering Knox. this only applies to those that upgraded OTA or got their S4 already with JB 4.3 in it.. like I did after a warranty exchange... HOWEVER if u install any Custom Recovery u will trigger the counter VOIDING ur warranty FOREVER!!! LOL well maybe not but at least til someone (and who knows if someone ever will) figures Knox out. So think twice before you do anything, cause no here will take responsability for your actions...
HAPPY FLASHIN!!
Just did this to my T-Mobile SGS4. It worked just as described. The Knox counter wasn't tripped, but Custom is indicated on the Download screen (Vol Down+Home+Power).
Here's what my Download screen now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
Thanks for the link to the other thread. :good:
Now I can use Titanium Backup, Greenify, ADB - rooted, esFile Explorer - rooted. Not needing a Custom Rom or Custom Recovery yet. And, to get it back to un-rooted, there are instructions in the other thread about that.
Rob
rlichtefeld said:
Just did this to my T-Mobile SGS4. It worked just as described. The Knox counter wasn't tripped, but Custom is indicated on the Download screen (Vol Down+Home+Power).
Here's what my Download screen now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
Thanks for the link to the other thread. :good:
Now I can use Titanium Backup, Greenify, ADB - rooted, esFile Explorer - rooted. Not needing a Custom Rom or Custom Recovery yet. And, to get it back to un-rooted, there are instructions in the other thread about that.
Rob
Click to expand...
Click to collapse
Just remember, you won't be able to make full nandroid backups (give Online Nandroid Manager a shot if you want to try).
xdapowerapps said:
Just remember, you won't be able to make full nandroid backups (give Online Nandroid Manager a shot if you want to try).
Click to expand...
Click to collapse
IFAIK, until I plan to flash a custom ROM I shouldn't need a full Nandroid. I can always flash a stock ROM, and between the Google Backup/Restore and TiB, I should get almost everything back. Music/Video, etc are all on the MicroSD.
Unless I'm sadly mistaken. This is my first foray into messing with the SGS4. I was very active flashing on my HTC HD2, starting with various builds for WM6.5, and then moving on to SD builds of Android and then NativeSD with cLK, etc. I was running Tytung's KitKat until I got this phone in December. I work for a small company and the SGS4 was my Christmas Bonus. The HD2 was just too long in tooth to keep up with all the advances in Android. But, since you could flash everything - radios, bootloaders, recoveries, builds, etc., I could change out/update my version of Android almost daily.
Rob
rlichtefeld said:
IFAIK, until I plan to flash a custom ROM I shouldn't need a full Nandroid. I can always flash a stock ROM, and between the Google Backup/Restore and TiB, I should get almost everything back. Music/Video, etc are all on the MicroSD.
Unless I'm sadly mistaken. This is my first foray into messing with the SGS4. I was very active flashing on my HTC HD2, starting with various builds for WM6.5, and then moving on to SD builds of Android and then NativeSD with cLK, etc. I was running Tytung's KitKat until I got this phone in December. I work for a small company and the SGS4 was my Christmas Bonus. The HD2 was just too long in tooth to keep up with all the advances in Android. But, since you could flash everything - radios, bootloaders, recoveries, builds, etc., I could change out/update my version of Android almost daily.
Rob
Click to expand...
Click to collapse
The beauty of a nandroid backup is that it takes a snapshot of your phone as it stands. Within five to eight minutes, you can restore your phone as it stood before it messed up. No re-downloading apps, changing settings, replacing system apps (i.e., installing Note 3 My Files and Gallery), etc. It saves the hassles of slow TiB/Helium restoration, especially if you have hundreds of apps. Sure, you can start fresh and manually restore things, but having it done within eight minutes without lifting a finger is extremely nice to have in your arsenal. Has come in handy several times for me since I test ROMs very frequently.
Congrats on your bonus, a very nice bonus indeed. It is a great phone. I was thinking about switching to a Note 3 or waiting for the S5 but this phone is perfect for my hands. Note 3 with an Otterbox Defender case is too big for my taste and the S5 is still a ways off. Plus, the development for this phone has far exceeded my expectations so I'm a happy camper for now.
xdapowerapps said:
No, this will only root your phone (give your apps su/superuser access). You will still need to flash a custom recovery (i.e., PhilZ, TWRP, CWM) to flash roms like a custom Vanilla ROM. If you are on 4.2.2 bootloader, you can simply flash a custom recovery and flash the ROM. If you are on 4.3, you will be on the KNOX bootloader and if you flash a custom recovery to flash the ROM, you will void your KNOX warranty. If you don't care about the warranty or has expired, there is no difference.
1) Download Vanilla Rom,
2) Flash custom recovery tar (i.e., PhilZ, TWRP, CWM).
3) Go into recovery and flash rom.
4) ????
5) ??
6) Profit.
Click to expand...
Click to collapse
What method did you use to install a custom recovery? I saw this in the thread:
Important - please read
If you fail to read this, you will be taunted.
1. You can't install custom recovery and custom ROMs using this technique. See Safestrap for a way to install some custom ROMs.
2. Resetting the "Custom" and open padlock indication during boot can be worked around using the Xposed Framwork and Wanam Xposed. Get those two from the Play Store.
In Wanam, tick "Security Hacks", "Fake System Status".
Click to expand...
Click to collapse
Did you use the safestrap like he suggested? I just got a replacement from t-mobile, i can't be stuck on tw lol.
root is still better then no root lol thank you for the info.
This is all great info, on rooting 4.3....
but how do you UNROOT ?
Xx_Joe_Wireless_xX said:
This is all great info, on rooting 4.3....
but how do you UNROOT ?
Click to expand...
Click to collapse
Go into SuperSU, then click permanent cleanup.
You have to make sure busy box is removed as well, or system will show custom
Sent from my SGH-M919 using XDA Premium 4 mobile app
Is there a way to get back to the stock rom???
Sent from my SGH-M919 using xda app-developers app
KRAZYADROIDMASTER said:
Is there a way to get back to the stock rom???
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
If the only mod you did was to follow the instructions in this thread, then you aren't changing the ROM, you are only giving yourself Root privileges.
To Unroot, go to the thread in the original post, and look at the second message in that thread.
Here's the link to that exact message:
http://forum.xda-developers.com/showpost.php?p=48392024&postcount=2
You will be
1) removing BusyBox
2) Using SuperSU to "Full Unroot"
If you've done more than was laid out in the original message in that thread, then you will probably need to
3) Remove any Custom Recovery
4) Flash an original ROM
There are several threads discussing getting back to a Stock ROM.
Rob
I've installed the latest Tmobile 4.4.2 Firmware via SamMobile. I came from M17 4.3. Updated via Odin to Tmobile 4.4.2, I then rooted via CF Auto root (Don't care about Knox at this point) successfully and following that flashed Philz recovery with success.
Everything is all good, as I am familiar with other devices and rooting and booting into recovery. At this point I downloaded the latest SlimKat and Lean Kernel to flash onto my system. Reboot into recovery, flash is a success, however when I reboot the system I start to get a bootloop saying Kernel is not seandroid enforcing set warranty bit: Kernel..I've tried to JUST flash SlimKat with the same results. Following this It continues to bootloop so I am forced to Odin from my PC back to Tmobile stock 4.4.2.
Can someone assist me with a solution? TLR, Custom ROMs/Kernels are not allowing me to boot due to Kernel is not seandroid enforcing set warranty bit: Kernel bootloop
My guess would be that slimkat doesn't support 4.4 bootloader yet.
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
Custom kernels will ALWAYS show that on boot.
Dev's turn off the SEANDROID permission crap because not all root apps deal with that permission properly.
Bootloop on the other hand would be a different issue doubtfully related to this.
t3tr1s_ said:
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
Click to expand...
Click to collapse
You have to read the op of the rom you're interested in. If it doesn't say it supports both bootloaders then it's most probably for 4.3 bl only.
Anthem here says it supports both bl.
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
I am not a technical person but how I understand it is that custom recovery/rom flashes doesn't load/replace the bl.
Cm and aosp-based roms were dev'd for 4.3 until a month or two ago when they start supporting both bl and even then not all roms do.
t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
Yes, it sure can.
If you're fully upgraded to the KK package completely, ex: through odin, you have to use a KK rom that has the 4.4.2/Kernel bootloader components.
If you don't fully want to commit to KK completely you can flash a KK rom that has a kernel with the older boot loader. That will allow you to go back to 4.3.
I suspect given time, 4.3 support will be slowly dropped in favor of a full KK implementation on this forum. In the transition period, be careful what you pick and choose to install.
I, like many others, have gone full KK inc. bootloader, etc for full compatibility with everything. When you go full update, you get the updated firmware and bits for the modems, etc.
Thank you very much for all your help, it was the bootloader issue. Just me not reading into things fully, very glad that I asked. I am now running Beanstalk on my Note!
Now that I have all of that cleared up, my next question is the S-PEN. I'm assuming all CM/AOSP ROMs will not support it, thus making me switch to TouchWiz. Is that true? Or are there Apps that I can still use in conjunction with my S-PEN?
As far as TouchWiz is concerned, is Xnote updated to the KK BL and compatible with our Tmobile version? I searched the thread but did not find any answer. If not, what is a suitable replacement to maintain funcionality of the S-PEN while having bloatware removed?
There are apps but it won't give you the full Samsung spen experience like on stock.
Sent from my SM-N900T using Tapatalk
As long as I have a note taking app I think i would be good to go. It's really the only feature I use.
also having this problem
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.
I've been waiting for months for an official samsung kitkat update for my phone. (i9195L). Today I checked on sammobile and saw that the update has arrived, for Trinidad and Tobago.
Now that it has been released, I want to know if I can flash it over my Carbon Rom, which has Android 4.4.4.
I want to know if I can go back to stock and flash this new firmware with kitkat on my device via Odin, or if I will have any problem considering I'm actually downgrading to 4.4.2.
Thanks in advance.
rolo143 said:
I've been waiting for months for an official samsung kitkat update for my phone. (i9195L). Today I checked on sammobile and saw that the update has arrived, for Trinidad and Tobago.
Now that it has been released, I want to know if I can flash it over my Carbon Rom, which has Android 4.4.4.
I want to know if I can go back to stock and flash this new firmware with kitkat on my device via Odin, or if I will have any problem considering I'm actually downgrading to 4.4.2.
Thanks in advance.
Click to expand...
Click to collapse
Good rule of thumb with OTAs. Don't perform then on a custom rom. I would use Odin to report to stock. Then see if you can get the update via OTA. However keep in mind that the newer update may not have a root method so if that is important to you, check into that. And always back up in recovery! Flashing back to stock should not harm you device.
Sent from my SGH-I337 using XDA Free mobile app
U won`t really downgrade But take into consideration this :
Do u have Knox bootloader active ? 0x0 or 0x1 in download mode ? Once u flash KitKat u can`t downgrade to samsung jellybean. U can flash aosp again if stock samsung won`t fit u . If u don`t have Knox bootloader i woyld flash an older firmware that does not contain Knox, 2 3 times in a row until u bring your phone to Official not custom and after that flash samsung kitkat. That way u will sure have knox not triggered, all flashed good modem and so and no problems. I think i write too much and u won`t understand a thing ( i`m bad at explaining stuff )
SilviuMik said:
U won`t really downgrade But take into consideration this :
Do u have Knox bootloader active ? 0x0 or 0x1 in download mode ? Once u flash KitKat u can`t downgrade to samsung jellybean. U can flash aosp again if stock samsung won`t fit u . If u don`t have Knox bootloader i woyld flash an older firmware that does not contain Knox, 2 3 times in a row until u bring your phone to Official not custom and after that flash samsung kitkat. That way u will sure have knox not triggered, all flashed good modem and so and no problems. I think i write too much and u won`t understand a thing ( i`m bad at explaining stuff )
Click to expand...
Click to collapse
Yes, you write too much, lol. But I get your point. Thanks for the reply.
I have Knox set to 0x1 so I guess it's activated, but I don't have any plan going back to jelly bean. i will stay with kitkat.
Besides I think there's already a way to root stock with kitkat via Towel root, so I guess it's a lot of help.
rolo143 said:
Yes, you write too much, lol. But I get your point. Thanks for the reply.
I have Knox set to 0x1 so I guess it's activated, but I don't have any plan going back to jelly bean. i will stay with kitkat.
Besides I think there's already a way to root stock with kitkat via Towel root, so I guess it's a lot of help.
Click to expand...
Click to collapse
Towelroot works only on roms made before july i think. Older won`t work
SilviuMik said:
Towelroot works only on roms made before july i think. Older won`t work
Click to expand...
Click to collapse
I don't completely agree. Towelroot worked on stock 4.4.2 for me fresh after an Odin restore. I believe it doesnt work on HTC phones and something else. Don't hold me to that I could be wrong. But Towelroot should work great for the OP
Sent from my SGH-I337 using XDA Free mobile app
I'm currently on DU Rom, if I want to test offical Kitkat I have to flash it with odin? And if I want to go back to DU how can I do it? With a backup?
Flatric said:
I'm currently on DU Rom, if I want to test offical Kitkat I have to flash it with odin? And if I want to go back to DU how can I do it? With a backup?
Click to expand...
Click to collapse
Yes if you stock kit kat without root and such you will need to use odin. Using odin will give you a complete stock. Recovery, kernel, etc. Meaning you won't have a custom recovery to restore a back up. Back up your current setup using your custom recovery and keep the back up on your external storage. If you choose to go back if stock doesn't work for you, you may be able to restore the back up once you re-root and install the custom recovery, but it may cause some errors. I'm not 100% sure that the restore will work or not. My suggestion is to find a stock rom that is only rooted and not modded. Less hassle that way. And much easier to go back to your current rom if you don't want the stock rom.
Sent from my SGH-I337 using XDA Free mobile app
One question: If I already installed this firmware (kitkat) How can I root it? Towelroot? I don't want to trigger Knox, I want to Root it workout having to enable Knox and put that message with yellow letters..
Edit: I rooted it by installing recovery and flashing the rootkit. So far so good.
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.