Develop Bugs

[Q] Questions about the new 4.3 ROM: downgrading, KNOX and others

Hi there, I'm about to flash the brand new official 4.3 ROM in my Note 2 N7105. I've read some concerns about KNOX and it changing the bootloader and making impossible to downgrade, it that true?
If I flash this new 4.3, can't I reflash the 4.1.2 ROM using a nandroid backup, or even with Odin?
What about using 3rd party ROMs, would I still be able to do it as I do now? Any risk of EFS / IMEI problems? I am currently using both the 4.1.2 and CM 10.3.1 (I alternate frequently using nandroid backups with CWM), don't know if it's worth the risk of upgrading to the official 4.3 right now before knowing this and if CF-AutoRoot can root the 4.3 ROM.
Note: I don't care about warranty and KNOX at all, if those are the only issues.

It is fairly simple - if you flash 4.3 with Knox, you can't ever again flash any other custom ROM without loosing Knox. What it means is that, once you flash anything else, Knox will burn something inside your chip - and this is irreversible - and it will know your device has been modded. And you can never again use Knox.
If you don't care about Knox - this is no issue....

dalanik said:
It is fairly simple - if you flash 4.3 with Knox, you can't ever again flash any other custom ROM without loosing Knox. What it means is that, once you flash anything else, Knox will burn something inside your chip - and this is irreversible - and it will know your device has been modded. And you can never again use Knox.
If you don't care about Knox - this is no issue....
Click to expand...
Click to collapse
I flashed with Odin and lost WiFi. I tried to install a patch from another thread, but it seems that doesn't work on for the N7105, as I lost my IMEI and the phone doesn't get signal. I have an EFS backup, gonna try downgrading to 4.1.2 and restore the EFS (it doesn't allow me to do it on 4.3, it says that "a dangerous action has been blocked").

Help, I can't get my IMEI back, it seems that the EFS backup was useless Have I bricked my phone? I think it hasn't really lost the IMEI, it just forgot how to search for it, because I installed the wifi correction .bin file for the n7100. Any help?

good questions.. waiting for replys?

topaloglu321 said:
good questions.. waiting for replys?
Click to expand...
Click to collapse
Managed it:
http://forum.xda-developers.com/showthread.php?t=2533822
Now I will stay away from the 4.3 ROM, because I can't make WiFi work with it.

[Q] Confused about downgrading 4.3 to 4.1.2

So my wife's S3 is SGH-i747M from Telus in Canada. Updated OTA to 4.3 (its unrooted) but turns out she doesn't like it at all and its buggy. I have read through several threads and am unsure how to go about downgrading safely.
I get that the MK5 modem in 4.3 updates EFS to v2, so I downloaded a .zip of MK5 modem to install after downgrading.
I downloaded MF1 firmware from sammobile with the intention of flashing in Odin.
My questions are:
Should I flash MF1 in Odin then flash a custom recovery, then flash back the MK5 modem? Or custom recovery first while on 4.3?
Also the MF1 4.1.2 firmware is 700+meg, I take it these are full firmwares, and I also read stuff about them including everything such as bootloader etc. If this has old bootloader and 4.3 had updated the bootloader would I be risking a brick?
Sorry if this has been explained elsewhere, seen alotta conflicting info and not sure what best way to proceed is. Thx alot!

I've heard it's impossible to downgrade. ...it's probably possible for those know-How but not to my knowledge.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

skurys said:
...Updated OTA to 4.3 (its unrooted) but turns out she doesn't like it at all and its buggy. I have read through several threads and am unsure how to go about downgrading safely...
Should I flash [sammobile] MF1 in Odin then flash a custom recovery, then flash back the MK5 modem? Or custom recovery first while on 4.3?!
Click to expand...
Click to collapse
see below
skurys said:
...Also the MF1 4.1.2 firmware is 700+meg, I take it these are full firmwares, and I also read stuff about them including everything such as bootloader etc. If this has old bootloader and 4.3 had updated the bootloader would I be risking a brick?
Click to expand...
Click to collapse
definitely!
danchoi704 said:
I've heard it's impossible to downgrade.!
Click to expand...
Click to collapse
definitely!
danchoi704 said:
...it's probably possible for those know-How but not to my knowledge.
Click to expand...
Click to collapse
In OP "Updated OTA" scenario, definitely not possible. Brick City

re: similar question
I am in a similar situation; a friend of mine has a i747M SGS3 from Telus and is having issues with performance and crashes since updating to official 4.3, and wants me to help him deal with it.
I want to be unambiguously sure of this before I take any actions: if we attempt to DOWNGRADE to 4.1.2, will we brick the phone?
If so, do we have other options? For example, can an official 4.3 i747M be safely sidegraded to a stable Cyanogenmod 4.3 equivalent, or to the Cyanogenmod 4.4.2 equivalent?

pc103 said:
see below
definitely!
definitely!
In OP "Updated OTA" scenario, definitely not possible. Brick City
Click to expand...
Click to collapse
Your core question is popular these days. I will say this once for all:
OTA 4.3 (with bootloader)
Downgrade=Brick
It's possible the buggy etc complaints can be remedied by (backup, wipe & reflash via Sammobile, Keis or Odin.
The sideflashing issues are best taken to the appropriate forum thread for your custom rom.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Once on 4.3 you CANNOT go back
Sent from my SGH-I747M using Tapatalk

jimchee said:
Once on 4.3 you CANNOT go back
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
These are the statements that cause all the confusion.
Once on the new bootloader (MJB) included with the 4.3 ota you can't downgrade the BOOTLOADER, you can only reflash the same or newer. You can still install any custom ROM that has added the bootloader to the assert but does not contain a bootloader itself, or simply remove the assert lines from the updater script and the bootloader (if the ROM contains one) yourself. You could also look around to see if anyone has taken the time to gut the older firmwares to remove the bootloader which would make it possible to install those as well. So to review, any ROM that doesn't attempt to install a bootloader and either a) passes the assert check for MJB or b) has the assert removed from the updater script will work just fine. Anything that attempts to change the bootloader OR doesn't have MJB in the assert code will fail....or worse. If you don't know what an update script or the bootloader assert check is then you shouldn't mess with them, just look for something that says it will work specifically with the MJB bootloader.

this is certainly true enough but looking through the att development thread it is mostly impossible to tell what you can flash on what, I have an I747M from telcel and so far I have not found one rom that I can flash successfully to my device no matter what I have tried, but that is neither here nor there, so I stand corrected sorry I tried to help.
Sent from my SGH-I747M using Tapatalk
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------
Oh and the original post says his wife's phone is unrooted so I stand by my original post
Sent from my SGH-I747M using Tapatalk

i went from "MJB" bootloader to "MJ2" bootloader, thought they were the same but apparently not and now i am bricked. is there any fix for this or did i just make myself a fancy looking paperweight???

by bricked do you mean no response whatsoever or can you get to download mode
Sent from my SGH-I747M using Tapatalk

jimchee said:
by bricked do you mean no response whatsoever or can you get to download mode
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
no response what so ever!!!!

Have you removed the battery? try holding volume down, home, and power while inserting the battery, if you get nothing you will probably need a jag to fix
Sent from my SGH-I747M using Tapatalk
---------- Post added at 05:06 PM ---------- Previous post was at 05:06 PM ----------
jtag
Sent from my SGH-I747M using Tapatalk

I have downgraded from 4.3 to 4.1.1 on my SGH-1747 (AT&T) but using only the firmware and not the bootloaders I've gone so many times back to stock. I just stay away from flashing b ootloaders cause I'd hate a brick
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

A little confused
I will start by saying that I do know that trying to go backwards from the UCDMJB bootloader WILL BRICK the phone. Been there and done that. Not fun. However the directions in this thread do work to get you unbricked - http://forum.xda-developers.com/showthread.php?t=2549068 You are just stuck at using the UCDMJB bootloader which hasn't been a problem with any of the 4.3 and 4.4 ROMS I have been playing with on this phone.
Now about my confusion. From what I am reading in various threads, it looks like you can go from say the UCDLK3 or UCDMG2 bootloader to the UCDMJ2 bootloader and still be able to ODIN back to stock without bricking your phone. Is this correct? I have one phone that is currently on the UCDMG2 bootloader. As mentioned above, my other phone is on the UCDMJB bootloader. Is it possible to move forward from the UCDMJB bootloader without bricking the phone?
So in other words -
UCDLK3 -> UCDMJB - NO DOWNGRADING TO OLDER BOOTLOADER WITHOUT BRICKING PHONE
UCDMG2 -> UCDMJB - NO DOWNGRADING TO OLDER BOOTLOADER WITHOUT BRICKING PHONE
UCDLK3 -> UCDMJ2 - Can downgrade to older bootloader without bricking phone?
UCDMG2 -> UCDMJ2 - Can downgrade to older bootloader without bricking phone?
UCDMJB -> UCDMJ2 - Will BRICK phone ????
Thanks in advance for any responses.

poppo101 said:
I will start by saying that I do know that trying to go backwards from the UCDMJB bootloader WILL BRICK the phone. Been there and done that. Not fun. However the directions in this thread do work to get you unbricked - http://forum.xda-developers.com/showthread.php?t=2549068 You are just stuck at using the UCDMJB bootloader which hasn't been a problem with any of the 4.3 and 4.4 ROMS I have been playing with on this phone.
Now about my confusion. From what I am reading in various threads, it looks like you can go from say the UCDLK3 or UCDMG2 bootloader to the UCDMJ2 bootloader and still be able to ODIN back to stock without bricking your phone. Is this correct? I have one phone that is currently on the UCDMG2 bootloader. As mentioned above, my other phone is on the UCDMJB bootloader. Is it possible to move forward from the UCDMJB bootloader without bricking the phone?
So in other words -
UCDLK3 -> UCDMJB - NO DOWNGRADING TO OLDER BOOTLOADER WITHOUT BRICKING PHONE
UCDMG2 -> UCDMJB - NO DOWNGRADING TO OLDER BOOTLOADER WITHOUT BRICKING PHONE
UCDLK3 -> UCDMJ2 - Can downgrade to older bootloader without bricking phone?
UCDMG2 -> UCDMJ2 - Can downgrade to older bootloader without bricking phone?
UCDMJB -> UCDMJ2 - Will BRICK phone ????
Thanks in advance for any responses.
Click to expand...
Click to collapse
To clarify your list there....
UCMJB - you are stuck here, the only way you can go is sideways (reflashing MJB) or up (doubt it will happen on this device). This is as far as bootloader goes anyways, this has no affect on recoveries, kernels, or ROMs*
UCDMJ2 - downgradeable like any other previous bootloader
The reason for this is MJ2 was from a leaked version of the 4.3 update that for whatever reason failed testing and was rebuilt. In this state the Qfuse that dissallows downgrading had not been implemented.
* There is a check built into most (probably all) custom, and every offical rom that checks the current bootloader against a list of acceptable bootloaders. If your device is loaded with one of these in the list, installation continues. If it is not, it fails the check and flashing is halted. Fundamentaly MJB is pretty much identical to several of the previous bootloaders with the exception of the new 'security' features, so in theory any current custom ROM CAN work if it doesn't pass the check by manually editing the updater-script in the rom.

[SOLVED] A little confused
dntesinfrno said:
To clarify your list there....
UCMJB - you are stuck here, the only way you can go is sideways (reflashing MJB) or up (doubt it will happen on this device). This is as far as bootloader goes anyways, this has no affect on recoveries, kernels, or ROMs*
UCDMJ2 - downgradeable like any other previous bootloader
The reason for this is MJ2 was from a leaked version of the 4.3 update that for whatever reason failed testing and was rebuilt. In this state the Qfuse that dissallows downgrading had not been implemented.
* There is a check built into most (probably all) custom, and every offical rom that checks the current bootloader against a list of acceptable bootloaders. If your device is loaded with one of these in the list, installation continues. If it is not, it fails the check and flashing is halted. Fundamentaly MJB is pretty much identical to several of the previous bootloaders with the exception of the new 'security' features, so in theory any current custom ROM CAN work if it doesn't pass the check by manually editing the updater-script in the rom.
Click to expand...
Click to collapse
So flashing MJ2 is not upgrading the MJB bootloader but actually a downgrade and will brick the phone that is on MJB if I flash MJ2. Correct? And the phone that is on MG2 will not brick if I flash MJ2 and will be able to be reverted back to stock via ODIN.
Thanks for the clarification. I knew MJ2 was from a leaked version of 4.3 but wasn't sure how it played into the scheme of things. So far I have had no issues flashing any of the 4.4 ROMS on the MJB bootloader.
Thanks button clicked.

dntesinfrno said:
...So to review, any ROM that doesn't attempt to install a bootloader and either a) passes the assert check for MJB or b) has the assert removed from the updater script will work just fine...
Click to expand...
Click to collapse
After further reading, apparently in mobile odin you can flash stock 4.1.2 and it will ignore the bootloader. Don't know if such a method would still require passing an assert check or if it bypasses this requirement. Haven't found enough success stories confirming yet to risk an angry wife if things go south

skurys said:
After further reading, apparently in mobile odin you can flash stock 4.1.2 and it will ignore the bootloader. Don't know if such a method would still require passing an assert check or if it bypasses this requirement. Haven't found enough success stories confirming yet to risk an angry wife if things go south
Click to expand...
Click to collapse
I've heard the same thing but have never used mobile odin to flash anything so i can't say for sure about the assert. I can say it wont hurt to try. Best case it bypasses the check, doesn't mess with the bootloader and flashes the remainder of the stock image. Worst case it does check the assert script and it fails before it ever writes anything.

4.4.2 bootloader

Where do I go to flash the new 4.4.2 bootloader and baseband
Sent from my SGH-M919 using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2677252
Sent from my SGH-M919 using XDA Premium 4 mobile app

How do I flash with mobile odin
Sent from my SGH-M919 using Tapatalk

Can I ask...
I've been reading thru some of these threads, and I'm coming to the conclusion that even with KitKat the bootloader is still unlocked, is this true? I have at&t version and they started locking that down with 4.3 JB.
Thanks.

MoodSwinger said:
I've been reading thru some of these threads, and I'm coming to the conclusion that even with KitKat the bootloader is still unlocked, is this true? I have at&t version and they started locking that down with 4.3 JB.
Thanks.
Click to expand...
Click to collapse
Correct, fortunately still unlocked.

muniz_ri said:
Correct, fortunately still unlocked.
Click to expand...
Click to collapse
This caught my eye. How is that possible with the bootloader unlock, is that just for AT&T? I am on T Mobile GS4 running 4.3 and I can see the knox counter on it 0x0 and I was informed that once updated from 4.2 to 4.3 and above the bootloader is now locked. Please clarify I would like to know. I am rooted though on stock through using this forum and have not tripped knox using this method. http://forum.xda-developers.com/showthread.php?t=2565758
I would love to find a way to install CWM without tripping the counter and trying other roms again but I here I can use bootstrap to run a custom rom, but no word on getting CWM installed without tripping the counter......unless I am wrong and I hope I am!
Thanks,
Mr Wizard

mr wizard said:
This caught my eye. How is that possible with the bootloader unlock, is that just for AT&T? I am on T Mobile GS4 running 4.3 and I can see the knox counter on it 0x0 and I was informed that once updated from 4.2 to 4.3 and above the bootloader is now locked. Please clarify I would like to know. I am rooted though on stock through using this forum and have not tripped knox using this method. http://forum.xda-developers.com/showthread.php?t=2565758
I would love to find a way to install CWM without tripping the counter and trying other roms again but I here I can use bootstrap to run a custom rom, but no word on getting CWM installed without tripping the counter......unless I am wrong and I hope I am!
Thanks,
Mr Wizard
Click to expand...
Click to collapse
I want to know that too.

mr wizard said:
This caught my eye. How is that possible with the bootloader unlock, is that just for AT&T? I am on T Mobile GS4 running 4.3 and I can see the knox counter on it 0x0 and I was informed that once updated from 4.2 to 4.3 and above the bootloader is now locked. Please clarify I would like to know. I am rooted though on stock through using this forum and have not tripped knox using this method. http://forum.xda-developers.com/showthread.php?t=2565758
I would love to find a way to install CWM without tripping the counter and trying other roms again but I here I can use bootstrap to run a custom rom, but no word on getting CWM installed without tripping the counter......unless I am wrong and I hope I am!
Thanks,
Mr Wizard
Click to expand...
Click to collapse
I think you have a definition difference. The bootloader is unlocked on the TMO S4. That is you can use the bootloader to update and install modems, roms, recoveries, etc. It is not locked and will let you do this.
However, if you use the 4.3 and above bootloader, it will set a flag if you flash a recovery. This is known as the Knox Warranty flag. And, this is what is shown on the ODIN or bootloader screen.
BTW, if you update to NB4 (Kit Kat) with a 4.3 bootloader or later, the SafeRoot method will not work. The only known rooting method at this time is the CF-Auto-Root which will trip the Knox flag. So, if you are fully stock 4.4.2 you will trip your Knox flag if you root the phone.
However, you can do it. It doesn't lock you out of doing it. It just records that you've done it.
Rob

rlichtefeld said:
I think you have a definition difference. The bootloader is unlocked on the TMO S4. That is you can use the bootloader to update and install modems, roms, recoveries, etc. It is not locked and will let you do this.
However, if you use the 4.3 and above bootloader, it will set a flag if you flash a recovery. This is known as the Knox Warranty flag. And, this is what is shown on the ODIN or bootloader screen.
BTW, if you update to NB4 (Kit Kat) with a 4.3 bootloader or later, the SafeRoot method will not work. The only known rooting method at this time is the CF-Auto-Root which will trip the Knox flag. So, if you are fully stock 4.4.2 you will trip your Knox flag if you root the phone.
However, you can do it. It doesn't lock you out of doing it. It just records that you've done it.
Rob
Click to expand...
Click to collapse
So if Knox counter doesn't matter you can still root device..are you still able to install custom roms? or isn't that possible ATM? Trying to get rid of the severe lag 4.4.2 OTA update has bestowed upon my gf's phone.

PaSsAtDrOiD said:
So if Knox counter doesn't matter you can still root device..are you still able to install custom roms? or isn't that possible ATM? Trying to get rid of the severe lag 4.4.2 OTA update has bestowed upon my gf's phone.
Click to expand...
Click to collapse
You can flash anything you want with the TMO S4.
However, if you need to return it for warranty, they MAY check the Knox flag, and they MAY not do the warranty service for free. That hasn't been shown to be a fact, but it is the reason for the flag in the first place.
It has been stated by a few people that re-flashing back to full stock will remove the Knox flag. I cannot verify it, since I haven't tried it.
Rob

Can anyone shed some light on a couple of points? I currently have the MDL bootloader along with the NB4 modem. This all runs fine with my daily driver (LightSpeed) 4.2.2 ROM, as well as the (Insane Kit Kat) 4.4.2 I've been experimenting with. I do understand that I can't go back to the MDL bootloader if I update. Knox issues aside, is there any actual advantage to having the new bootloader? Since my warranty is running out soon anyways, I'm not too worried about tripping Knox. So, does the NB4 bootloader offer any real performance or feature advantages? Can I still run 4.2.2 or 4.3 ROMs with it, or will it limit me to 4.4.2+ ROMs? Does it impact the usage of different kernels? Thanks!

rlichtefeld said:
You can flash anything you want with the TMO S4.
However, if you need to return it for warranty, they MAY check the Knox flag, and they MAY not do the warranty service for free. That hasn't been shown to be a fact, but it is the reason for the flag in the first place.
It has been stated by a few people that re-flashing back to full stock will remove the Knox flag. I cannot verify it, since I haven't tried it.
Rob
Click to expand...
Click to collapse
It won't remove the Knox flag although they MAY not check it or they MAY when I did my warrenty return they did not but that doesn't mean it will always be the case
Sent from my SGH-M919 using Tapatalk

hella356 said:
Can anyone shed some light on a couple of points? I currently have the MDL bootloader along with the NB4 modem. This all runs fine with my daily driver (LightSpeed) 4.2.2 ROM, as well as the (Insane Kit Kat) 4.4.2 I've been experimenting with. I do understand that I can't go back to the MDL bootloader if I update. Knox issues aside, is there any actual advantage to having the new bootloader? Since my warranty is running out soon anyways, I'm not too worried about tripping Knox. So, does the NB4 bootloader offer any real performance or feature advantages? Can I still run 4.2.2 or 4.3 ROMs with it, or will it limit me to 4.4.2+ ROMs? Does it impact the usage of different kernels? Thanks!
Click to expand...
Click to collapse
If you don't care about knox you better off going to the new bootloader ,the NB4 wifi driver is not present on the MDL bootloader so you still using the old wifi. I notice very strong wifi signal after upgrade to kitkat bootloader to flashed modem and wifi fix.The best way is to flash the NB4 firmware through Odin so you can get everything needed and go from there.

Thanks, makomek. I've been wondering about that, but haven't really found much info beyond the Knox implications. I have gotten an improvement in general phone call stability and download speed with the NB4 modem. Is what your're talking about related to the NON-HLOS.bin being installed? As I recall, that was to improve LTE, but I apparently it's actually related to WiFi. Or could be both? At least it's good to hear there are positive reasons to update the bootloader. Any idea if doing this would lock me into only using KitKat ROMs/kernels, or would 4.2/4.3 still work? Your input is much appreciated.
makomek said:
If you don't care about knox you better off going to the new bootloader ,the NB4 wifi driver is not present on the MDL bootloader so you still using the old wifi. I notice very strong wifi signal after upgrade to kitkat bootloader to flashed modem and wifi fix.The best way is to flash the NB4 firmware through Odin so you can get everything needed and go from there.
Click to expand...
Click to collapse

PaSsAtDrOiD said:
So if Knox counter doesn't matter you can still root device..are you still able to install custom roms? or isn't that possible ATM? Trying to get rid of the severe lag 4.4.2 OTA update has bestowed upon my gf's phone.
Click to expand...
Click to collapse
If your girlfriend's phone is stock, unrooted, and she took the OTA, the easiest way to get rid of lag is to factory reset. If she doesn't care about being rooted and just wants the stock rom, this is the easiest way to improve performance. Just start over. OTAs, in my opinion, are like a dirty flash.

[Q] Is it possible to install a stock ROM if 4.3 and a locked bootloader is in place

Is it possible to install a stock ROM once 4.3 and a locked bootloader is in place. I've looked all over and I seem to read conflicting stories. So...
I have a Samsung S3 Telus (AT&T) version running the latest 4.3 as of May1st, my bootloader is locked and I have a tripped flash counter.
If someone actually posts a I747MVLUEND2 rooted image can I flash it?
Can I flash an older version I747MVLUEM series?
Oh yeah my phone is NOT rooted.

Check post #5, 11, 27 here Guide: How I unlocked my ATT S3 [ 1 2 3 ... Last ]
Thread By: Jasonator

I think you didn't understand the question. You pointed me to a thread about unlocking.

With a 4.3 bootloader, you will need to install a custom recovery to flash ROMs. If you want to restore a stock 4.3 ROM, try this: http://forum.xda-developers.com/showthread.php?t=2658486
With a 4.3 bootloader, you cannot use Odin to flash a stock ROM unless that ROM was specifically compiled for flashing via Odin.

No this is not possible. I have a LOCKED boot loader. I can't flash a custom recovery as far as I know.
Also how would one know a ROM is made to be flashed by Odin even if it was possible? Maybe I missed something here.

I re-read your original post and I'm a bit confused. You have a Telus s3 (i747m) or AT&T s3 (i747)?
I have never heard of an s3 having a locked bootloader. All of the phones with a stock 4.3 ROM have a bootloader that cannot be downgraded.

audit13 said:
I re-read your original post and I'm a bit confused. You have a Telus s3 (i747m) or AT&T s3 (i747)?
I have never heard of an s3 having a locked bootloader. All of the phones with a stock 4.3 ROM have a bootloader that cannot be downgraded.
Click to expand...
Click to collapse
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.

horga_83 said:
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.
Click to expand...
Click to collapse
sir, the one who got the wrong idea is you
the only S3 with locked bootloader is the verizon version
i747/M doesn't regardless of which version
which occurs to me that you might have done something wrong trying to root your device
though i've never tried this tool to root but many people succeeded rooting their phone with this http://forum.xda-developers.com/showthread.php?t=1963790
so try it out
but again, you said to flash a stock rom... you can do it via Kies(is that how it is called? it had been so long since i last used it) or you can just use ODIN to flash it

Regardless of the subject of that thread, the posts I indicated directly speak to your 747m downgrade question.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

horga_83 said:
Sorry, I have a Telus I747M.
It seems all AT&T and Telus S3's have a locked boot loader after the upgrade to 4.3. This means you cannot flash CWM recovery to the phone anymore.
So, I beleive I can't fix it to put CWM recovery on but I may be able to flash a stock rom, I'm just not sure at this point what I can do. Based on your response it is not surprising I'm confused, there seems to be a LOT of conflicting information.
There are some stock ROMS that have already been rooted and I'm hoping I can flash one of those without bricking my phone.
Click to expand...
Click to collapse
Can understand why some may be confused about the question. If you have stock 4.3 already (which is the latest version available), why would you want to flash another stock ROM? If you are talking about flashing an older stock ROM, yes it is possible, and there have been several posts on how you can successfully downgrade the system only without altering the bootloader. Attempting to downgrade the bootloader will, of course, cause a brick so downgrading ROM only is a rather complicated process that should be attempted only if there is a very worthwhile reason for this. So far, there are very few arguments, if any, for downgrading from 4.3 to any older stock ROM version. If you are trying to flash a rooted version of the same stock, you need to be sure it's one with the same bootloader. You may, however, find it easier simply keeping the current system and rooting via Safe Root. You can, however, flash a custom ROM if it won't attempt to mess with your bootloader . As far as recovery goes, even if you have stock 4.3, you can still flash custom recovery via Odin or other prescribed installation route. I'm not aware of 4.3 preventing the flashing of a custom recovery. I have an AT&T i747 with stock 4.3 and I've flashed custom recovery several times.

pcshano said:
sir, the one who got the wrong idea is you
the only S3 with locked bootloader is the verizon version
i747/M doesn't regardless of which version
which occurs to me that you might have done something wrong trying to root your device
though i've never tried this tool to root but many people succeeded rooting their phone with this http://forum.xda-developers.com/showthread.php?t=1963790
so try it out
but again, you said to flash a stock rom... you can do it via Kies(is that how it is called? it had been so long since i last used it) or you can just use ODIN to flash it
Click to expand...
Click to collapse
So when my bootloader says Qualcomm secure boot = 1, that means what exactly?
I haven't tried to root my phone yet.
Well actually it's a stock ROM that has been rooted. As per this page:
http://forum.xda-developers.com/showthread.php?t=1739426&__utma=248941774.1179961654.1399404439.1400082744.1400099749.11&__utmb=248941774.1.10.1400099749&__utmc=248941774&__utmx=-&__utmz=248941774.1400099749.11.3.utmcsr=forum.xda-developers.com|utmccn=%28referral%29|utmcmd=referral|utmcct=/galaxy-s3-att/&__utmv=-&__utmk=261245838

horga_83 said:
So when my bootloader says Qualcomm secure boot = 1, that means what exactly?
I haven't tried to root my phone yet.
Well actually it's a stock ROM that has been rooted. As per this page:
http://forum.xda-developers.com/showthread.php?t=1739426&__utma=248941774.1179961654.1399404439.1400082744.1400099749.11&__utmb=248941774.1.10.1400099749&__utmc=248941774&__utmx=-&__utmz=248941774.1400099749.11.3.utmcsr=forum.xda-developers.com|utmccn=%28referral%29|utmcmd=referral|utmcct=/galaxy-s3-att/&__utmv=-&__utmk=261245838
Click to expand...
Click to collapse
I think that means secure booting has been enabled. Secure booting has nothing to do with having a locked bootloader. From what I have read in other forums, a locked bootload would not allow you to load a custom kernel.

[Q] Atempting to remove Knox from firmware befor update.

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.