Develop Bugs

[Q] OTA 4.1.1 JB and other questions!!!!

Hey XDA! I recently perm-rooted my SGS3 T-mobile versionT999 using the QCOM Toolkit and Odin and I flashed custom CMW recovery 6.(whatever) and did backups of all my stuff like data, system, EFS partition and more. It also renamed my recovery restore files. I read a few things regarding the OTA update of JB coming out soon and heard that if it is updated it could actually turn s-off back on and mess up your root and mess up a bunch of other things that I've done.
First off I would like to ask for some clarification on this subject as to what exactly will happen if the OTA updates to JB and if it will automatically be prevented or if I have to do something to keep my phone from automatically upgrading to JB on its own. Also if it turns out that I cannot do the OTA JB update should I just flash a custom JB rom or possibly flash a stock release of the JB rom?
Secondly I wanted to ask about the flash counter. Currently I have not flashed anything but CWM (twice cause I tried to flash touch but it failed) I have not flashed any roms or kernels or radios yet. Has my flash counter already been tripped? What exactly will trip the counter? I also read something about resetting the trip meter and flashing everything back to stock including unrooting. Can someone post a link to a guide(s) that have steps for that? (Trust me I've been looking on XDA for a few hours trying to answer all these questions myself but I cant find some of them and I figured asking and having them answered all in one place would be much easier and helpful to me and others as well). In the future I may look into flashing another kernel so I can overclock and also some other roms. Another question arises though: What exactly is and insecure kernel ( I believe thats what they're called) and also what is an insecure boot img? Sorry I have so many questions but theres a lot of information to take in when a new phone receives root and gets a bunch of new possibilities!
One final question until new ones arise. What exactly are these new builds I keep reading about? Ive seen "T999UVALEM", "uvalh2", "uvalh3" , "UVLI2,3 & 4", "UVDLI3", "UVDLH3", "UVALG1", and "ULVH2" and I assume there are many more haha.
What exactly even are these??? Its just too much to keep up with. Thanks to anyone who can clear up the confusion
Well I believe that about sums up my questions so if you can help me out I would greatly appreciate it! Thanks guys!

If you have cwm installed the OTA will fail.
Sent from my SGH-T999
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
We don't have S-on/off either. That is an HTC thing.
Sent from my SGH-T999

flashing using Odin trips the counter
Flashing using cwm does not
You can use triangle away (an app) to reset your flash counter
Sent from my SGH-T999 using xda premium
---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------
the uvl stuff is different leaks (builds)
The different builds came with new basebands (modems) as Samsung tries to increase reception
Look in development for the modem thread
For example I'm running the latest cm10 nightly and using the latest modem. So my baseband is T999UVLI8
Sent from my SGH-T999 using xda premium

Android_Monsters said:
flashing using Odin trips the counter
Flashing using cwm does not
You can use triangle away (an app) to reset your flash counter
Sent from my SGH-T999 using xda premium
---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------
the uvl stuff is different leaks (builds)
The different builds came with new basebands (modems) as Samsung tries to increase reception
Look in development for the modem thread
For example I'm running the latest cm10 nightly and using the latest modem. So my baseband is T999UVLI8
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So when I used the toolkit (which used Odin) to root and flash CWM the counter was tripped? Oh well I'm sure there will be workarounds later

Yes go ahead and flash a custom Rom. The developers will have a rooted version of the ota once it drops. And you can just flash that.
Sent from my SGH-T999 using xda premium
---------- Post added at 06:44 PM ---------- Previous post was at 06:42 PM ----------
jtl_777 said:
So when I used the toolkit (which used Odin) to root and flash CWM the counter was tripped? Oh well I'm sure there will be workarounds later
Click to expand...
Click to collapse
You can download triangle away on xda website or buy it in the play store
It resets the counter to zero.
Sent from my SGH-T999 using xda premium

jtl_777 said:
So when I used the toolkit (which used Odin) to root and flash CWM the counter was tripped? Oh well I'm sure there will be workarounds later
Click to expand...
Click to collapse
I don't know what the toolkit is but there was a guide in the development section on rooting without tripping the counter. Essentially it used Odin to flash a stock rom that had root injected and from there you could install cwm. As long as u flash roms with cwm it shouldn't trip the counter to my knowledge but if u use Odin to flash roms it will trip the counter
Sent from my SGH-T999 using xda app-developers app

Here is a guide on reseting ect, and making it look stock just found.
http://forum.xda-developers.com/showthread.php?p=31890397

mystycs said:
Here is a guide on reseting ect, and making it look stock just found.
http://forum.xda-developers.com/showthread.php?p=31890397
Click to expand...
Click to collapse
Thanks matey I'll give it a look

mystycs said:
Here is a guide on reseting ect, and making it look stock just found.
http://forum.xda-developers.com/showthread.php?p=31890397
Click to expand...
Click to collapse
holy mackerel this is GOLD!!! Clears SOOOOO much up! many thanks dude!!!

Full 4.3 M919UVUEMK2 Succesfull Flash

hope this is the correct place to post this. i wanna post this to help those that are/were in the same boat that i was in prior to flashing the full 4.3 MK2 tar file. excuse my noobness as i'm not sure if the 4.3 M919UVUEMK2 is bootloader or baseband. if you know what it is, please correct me. thank you.
current rom i'm using is the infamous alpha s4 12.04 12.14.2013 (release date i think) --> http://forum.xda-developers.com/showthread.php?t=2362636. after flashing this rom, there are countless issues regarding loss of data, call drops, etc. prior to flashing the full 4.3 M919UVUEMK2 tar, my issue was more on the side of not sending and receiving mms w/o having to disable wi-fi (after flashing 4.3's modem.bin to change baseband from MDL to MK2). unfortunately, this didn't really help me at all, honestly, til i read:
http://forum.xda-developers.com/showpost.php?p=48668326&postcount=4395
http://forum.xda-developers.com/showpost.php?p=48668416&postcount=4396
http://forum.xda-developers.com/showpost.php?p=48668634&postcount=4397
i've also searched about getting KNOX'd. sure i was scared about voiding warranty, because i have this s4 for about 3-4 months only, lol. in any case, i downloaded the full 4.3 M919UVUEMK2 tar file (read this post from same thread above: http://forum.xda-developers.com/showpost.php?p=48669487&postcount=4399), and flashed it, rooted my s4, flashed philz recovery (the latest), clean/wipe phone, and re-install alpha s4 12.04. after doing all of this, i was worried again about getting KNOX'd so i double check and triple check and no KNOX -- me very happy. the only downside is that triangle away doesn't seem to work on MK2, so my counter is 4 and, yes i can send and receive mms w/o having to disable wi-fi . i will constantly test calls on this rom to see if there will be any drops or what not, so we'll see how it goes.
hope this isn't TL;DR lol. i'm still very new at this rom scene, and i hope to get better as a user because i can't program worth a damn :laugh: also, i hope that this will help or lead others to help them in finding their solution in other 4.3 roms out there.
peace

TL;DR
Sent from a Carbon'd Galaxy KitKat
---------- Post added at 03:50 PM ---------- Previous post was at 03:47 PM ----------
I'm kidding haha
To answer your question, the mk2 is a firmware version. But if you break it down you have a mk2 boot loader, mk2 modem, etc etc. The firmware contains all these things and their all mk2 version. So you can have mk2 firmware, mk2 bootloader, mk2 modem/baseband etc etc. Mk2 is just the firmware they came from
Sent from a Carbon'd Galaxy KitKat

isamudysan said:
hope this is the correct place to post this. i wanna post this to help those that are/were in the same boat that i was in prior to flashing the full 4.3 MK2 tar file. excuse my noobness as i'm not sure if the 4.3 M919UVUEMK2 is bootloader or baseband. if you know what it is, please correct me. thank you.
current rom i'm using is the infamous alpha s4 12.04 12.14.2013 (release date i think) --> http://forum.xda-developers.com/showthread.php?t=2362636. after flashing this rom, there are countless issues regarding loss of data, call drops, etc. prior to flashing the full 4.3 M919UVUEMK2 tar, my issue was more on the side of not sending and receiving mms w/o having to disable wi-fi (after flashing 4.3's modem.bin to change baseband from MDL to MK2). unfortunately, this didn't really help me at all, honestly, til i read:
http://forum.xda-developers.com/showpost.php?p=48668326&postcount=4395
http://forum.xda-developers.com/showpost.php?p=48668416&postcount=4396
http://forum.xda-developers.com/showpost.php?p=48668634&postcount=4397
i've also searched about getting KNOX'd. sure i was scared about voiding warranty, because i have this s4 for about 3-4 months only, lol. in any case, i downloaded the full 4.3 M919UVUEMK2 tar file (read this post from same thread above: http://forum.xda-developers.com/showpost.php?p=48669487&postcount=4399), and flashed it, rooted my s4, flashed philz recovery (the latest), clean/wipe phone, and re-install alpha s4 12.04. after doing all of this, i was worried again about getting KNOX'd so i double check and triple check and no KNOX -- me very happy. the only downside is that triangle away doesn't seem to work on MK2, so my counter is 4 and, yes i can send and receive mms w/o having to disable wi-fi . i will constantly test calls on this rom to see if there will be any drops or what not, so we'll see how it goes.
hope this isn't TL;DR lol. i'm still very new at this rom scene, and i hope to get better as a user because i can't program worth a damn :laugh: also, i hope that this will help or lead others to help them in finding their solution in other 4.3 roms out there.
peace
Click to expand...
Click to collapse
So after doing what you just said, your KNOX Warranty Void is 0x0?

Vigz said:
So after doing what you just said, your KNOX Warranty Void is 0x0?
Click to expand...
Click to collapse
yes. don't have another phone to take a pic of my sgs4 in it's download mode; but on the top left of the screen, in download mode, it tells me this:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0X30
WRITE PROTECTION: Enable
ofc, please correct me if i'm incorrect about these things. i'm assuming that from this pic on this thread, http://forum.xda-developers.com/showthread.php?p=47878403, indicates the phone is in download mode and that that is where to check for KNOX. again, correct me if i'm wrong
thx.

Hate to break it to ya, but that is not the mk2 Knox enabled bootloader.
If it was , under system status it'd say Knox kernel lock 0x0 and under that Knox something else 0x0.
The link you got the firmware from, which was on Jamesons AFH, must of contained the mdl bootloader
Sent from my SGH-M919 using Tapatalk 4

ShinySide said:
TL;DR
Sent from a Carbon'd Galaxy KitKat
---------- Post added at 03:50 PM ---------- Previous post was at 03:47 PM ----------
I'm kidding haha
To answer your question, the mk2 is a firmware version. But if you break it down you have a mk2 boot loader, mk2 modem, etc etc. The firmware contains all these things and their all mk2 version. So you can have mk2 firmware, mk2 bootloader, mk2 modem/baseband etc etc. Mk2 is just the firmware they came from
Sent from a Carbon'd Galaxy KitKat
Click to expand...
Click to collapse
lol...i truly appreciate your explanation of the MK2 :good:

ShinySide said:
Hate to break it to ya, but that is not the mk2 Knox enabled bootloader.
If it was , under system status it'd say Knox kernel lock 0x0 and under that Knox something else 0x0.
The link you got the firmware from, which was on Jamesons AFH, must of contained the mdl bootloader
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
interesting. here's my screenshot of About Device:

isamudysan said:
interesting. here's my screenshot of About Device:
Click to expand...
Click to collapse
Yeah , just saying you have the modems and running mk2 based. But that's not the mk2 bootloader.
Sent from my SGH-M919 using Tapatalk 4

ShinySide said:
Yeah , just saying you have the modems and running mk2 based. But that's not the mk2 bootloader.
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
i appreciate your insights, shiny. thx much. so not having the mk2 bootloader is a good thing? lol

KNOX Warranty Void is 0x0...?
isamudysan said:
yes. don't have another phone to take a pic of my sgs4 in it's download mode; but on the top left of the screen, in download mode, it tells me this:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0X30
WRITE PROTECTION: Enable
ofc, please correct me if i'm incorrect about these things. i'm assuming that from this pic on this thread, http://forum.xda-developers.com/showthread.php?p=47878403, indicates the phone is in download mode and that that is where to check for KNOX. again, correct me if i'm wrong
thx.
Click to expand...
Click to collapse
You avoided the real question by Vigz !
Show us the line in your Download mode that the "KNOX Warranty Void" is: 0x0 & not 0x1 !

isamudysan said:
i appreciate your insights, shiny. thx much. so not having the mk2 bootloader is a good thing? lol
Click to expand...
Click to collapse
Yeah. No Knox flag. Personally I don't care if I trip it. I pay insurance for the ability to "lose" my phone if some catastrophic event happens to it Ahaha
Sent from my SGH-M919 using Tapatalk 4

itzik_man said:
You avoided the real question by Vigz !
Show us the line in your Download mode that the "KNOX Warranty Void" is: 0x0 & not 0x1 !
Click to expand...
Click to collapse
i thought i did reply correctly. like previously stated, i don't have another phone or camera on hand to take a pic of my Download mode, what i listed is all that i saw on when i'm in download mode. so, there is no KNOX Warranty Void: 0x0, or 0x1 on that screen.
pretty much like shiny said above, the mk2 tar file that i flashed from jamison904 did not have the 4.3 bootloader in it; and it seems to be a good thing lol. hope that helps.

I am not sure that it did not trip the Knox security..
isamudysan said:
i thought i did reply correctly. like previously stated, i don't have another phone or camera on hand to take a pic of my Download mode, what i listed is all that i saw on when i'm in download mode. so, there is no KNOX Warranty Void: 0x0, or 0x1 on that screen.
pretty much like shiny said above, the mk2 tar file that i flashed from jamison904 did not have the 4.3 bootloader in it; and it seems to be a good thing lol. hope that helps.
Click to expand...
Click to collapse
The only way to find out if it 0x0 or 0x1, is to install the Knox app itself !
Yes, it will let you install it to a certain point & when you try to set it up (if your Knox is tripped) it will tell you that it can't be installed !
Then you can uninstall the app.
---------- Post added at 11:14 AM ---------- Previous post was at 10:45 AM ----------
There is no much discussion on this application (for none rooted or custom ROMS), but if you manage to not trip the Xnox security flag, this app is somewhat a nice to have.
It creates a second UI (User Interface) on your phone with ability to customize it completely differently from you regular settings with some Samsung (I know, many will considered it as bloatware) specially design apps for Knox.
It is useful especially, if you intend to keep some concealed info, documents & videos...etc.

itzik_man said:
The only way to find out if it 0x0 or 0x1, is to install the Knox app itself !
Yes, it will let you install it to a certain point & when you try to set it up (if your Knox is tripped) it will tell you that it can't be installed !
Then you can uninstall the app.
---------- Post added at 11:14 AM ---------- Previous post was at 10:45 AM ----------
There is no much discussion on this application (for none rooted or custom ROMS), but if you manage to not trip the Xnox security flag, this app is somewhat a nice to have.
It creates a second UI (User Interface) on your phone with ability to customize it completely differently from you regular settings with some Samsung (I know, many will considered it as bloatware) specially design apps for Knox.
It is useful especially, if you intend to keep some concealed info, documents & videos...etc.
Click to expand...
Click to collapse
thank you for the info itzik_man :good:

itzik_man said:
The only way to find out if it 0x0 or 0x1, is to install the Knox app itself !
Yes, it will let you install it to a certain point & when you try to set it up (if your Knox is tripped) it will tell you that it can't be installed !
Then you can uninstall the app.
Click to expand...
Click to collapse
Not true.... The flag is displayed in download mode. Just like the flash counter. So to see if you tripped it you do exactly what the op did. Boot into download mode and you'll see 2 lines regarding knox with values. 0x0 if not tripped 0x1 if tripped
Sent from my SGH-M919 using Tapatalk 4

My response was directed to the user with a diffrent boot loader !
ShinySide said:
Not true.... The flag is displayed in download mode. Just like the flash counter. So to see if you tripped it you do exactly what the op did. Boot into download mode and you'll see 2 lines regarding knox with values. 0x0 if not tripped 0x1 if tripped
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
The user that couldn't have the same Download menu because of his none a MK2 bootloader !
If you would read my previews post carefully you would see the your answer is redundant (you repeat what I already said to the user).
What I meant is, in case you don't see the Knox warranty void 0x0 / 0x1 in your download menu, then the only way to find out, is to install the app !

itzik_man said:
The user that couldn't have the same Download menu because of his none a MK2 bootloader !
If you would read my previews post carefully you would see the your answer is redundant (you repeat what I already said to the user).
What I meant is, in case you don't see the Knox warranty void 0x0 / 0x1 in your download menu, then the only way to find out, is to install the app !
Click to expand...
Click to collapse
If it's not displayed in the bootloader, said user doesn't have the Knox infused bootloader. So there's nothing to check. I think you're referring to the other flag. The flash counter. Which isn't the same thing as the Knox.
Sent from my SGH-M919 using Tapatalk 4

My question really is how did this happen? I thought if you flash that Tar file you automatically pickup the 4.3 baseband and knox with it. Could this be remaining from you updating just the modem? For me the problem is that I cannot seem to update the modem to mk2. I do not really see any advantage of locking the bootloader with Knox and if my screen stops working stupid T-Mobile will find a way to refuse to fix the phone!

alextop30 said:
My question really is how did this happen? I thought if you flash that Tar file you automatically pickup the 4.3 baseband and knox with it. Could this be remaining from you updating just the modem? For me the problem is that I cannot seem to update the modem to mk2. I do not really see any advantage of locking the bootloader with Knox and if my screen stops working stupid T-Mobile will find a way to refuse to fix the phone!
Click to expand...
Click to collapse
How'd he flash 4.3 and avoided the Knox bootloader? Package he flashed wasn't official. Either the aboot.img was removed or was replaced with mdl aboot.img
Sent from my SGH-M919 using Tapatalk 4

ShinySide said:
How'd he flash 4.3 and avoided the Knox bootloader? Package he flashed wasn't official. Either the aboot.img was removed or was replaced with mdl aboot.img
Sent from my SGH-M919 using Tapatalk 4
Click to expand...
Click to collapse
Do you think you can point me to a package like that where I will not pickup the bootloader? I have been trying to just update the modem using odin and keeps failing. Maybe flashing a non knox tar file will do the trick to get everything to work properly so that I flash 4.3 finally!
Maybe the OP can also post a link to the package he flashed using Odin!

Help Bricked,after tring to root 4.4.2 ota

I found a link with comments backing up the http://true-android.blogspot.com/2014/03/root-n900tuvucnb4-t-mobile-galaxy-note.htmlroot
Now I'm bricked and Kies not connecting,
Trying to Odin CF-Root 9005 and 900 notworking. Odin fails on "NAND WRITE"
Can someone please point me in the right direction,

starscrean said:
I found a link with comments backing up the http://true-android.blogspot.com/2014/03/root-n900tuvucnb4-t-mobile-galaxy-note.htmlroot
Now I'm bricked and Kies not connecting,
Trying to Odin CF-Root 9005 and 900 notworking. Odin fails on "NAND WRITE"
Can someone please point me in the right direction,
Click to expand...
Click to collapse
I found that if I tried to odin a recovery (I was using team win) it will work again. First you need to pull the battery and get it back into download mode. Then try to install recovery via odin. It didnt give me root nor a custom recovery but it brought me back to a non brick phone.

Download stock firmware, put your phone in Odin mode and flash that. Then you will need to flash the cf file again for root
Sent from my SM-N900T using Tapatalk
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
I have a thread that explains exactly what to do because I had the same issue you are
Sent from my SM-N900T using Tapatalk

Anonymous777 said:
Download stock firmware, put your phone in Odin mode and flash that. Then you will need to flash the cf file again for root
Sent from my SM-N900T using Tapatalk
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
I have a thread that explains exactly what to do because I had the same issue you are
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I Will be trying al this now

Odin is always failing on NAND Write Start
I've downloaded 4.4.2 stock firmware
I don't know what else to try.
Knox Warranty Void 0X1
f I take it maketo Tmobile I hope they over look the knox
Seeing how I just purchased 2 days ago. Might have to pay restocking fee ;-(

You wont have a restock for a warranty swap. But it really isnt warranth when you caused it.
Sent from my SM-N900T using xda app-developers app

starscrean said:
Odin is always failing on NAND Write Start
I've downloaded 4.4.2 stock firmware
I don't know what else to try.
Knox Warranty Void 0X1
f I take it maketo Tmobile I hope they over look the knox
Seeing how I just purchased 2 days ago. Might have to pay restocking fee ;-(
Click to expand...
Click to collapse
What version of odin are you using? and what do you have checked? Auto-reboot should be the only one checked and you should be using odin 3.9

Anonymous777 said:
What version of odin are you using? and what do you have checked? Auto-reboot should be the only one checked and you should be using odin 3.9
Click to expand...
Click to collapse
Yea I actually tried Odin 3.7/3.8/3.9 I also tried unzipping .tar directly to the C:/ drive instead of desktop. In case of any administration issues.
But in the end I was able to put in the model and serial number into Kies, put phone in download mode to get firmware from Kies.
The funny thing is, just by me trying and unsuccessfully rooting the phone. I tripped the Knox warranty 0x1. Odin only 25% uploaded Cf-root before failing. Lol
Sent from my SM-N900T using xda app-developers app

Odin the stock 4.4.2 file to the phone. Then root it after since Knox is already voided.

imaleecher said:
Odin the stock 4.4.2 file to the phone. Then root it after since Knox is already voided.
Click to expand...
Click to collapse
You shouldn't have to use Kies. just follow these steps. 1- put your phone in download (odin) mode. 2- connect it to your computer and run odin 3..09. 3- The only thing that should be checked is 'Auto Reboot' and as far as files it should say 'TMB-N900TUVUCNB4-20140305155920. Once you extract the file (I just put it on my desktop so it was easy to find) Then it should be about 2,178,541 KB in size....so like 2.1 GB. Choose that file after extracted and click the option of AP. His start and you should be back to factory settings, then worry about re rooting your phone. . Does that make more sense?
---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------
I should of read your title more carefully, is your phone still bricked? Or are you just trying to root it now?

Safestrap for Tmobile Galaxy S4?

I saw that the galaxy s4 Verizon version have this safestrap recovery, why there is no tmobile s4 safestrap? Thanks.

Short answer: because we don't need it. The M919 already has an unlocked bootloader which allows us to replace the stock recovery with custom builds such as CWM and TWRP.
Also, nb4lock.

HampTheToker said:
Short answer: because we don't need it. The M919 already has an unlocked bootloader which allows us to replace the stock recovery with custom builds such as CWM and TWRP.
Also, nb4lock.
Click to expand...
Click to collapse
Well as far as I know the jelly bean 4.3 update comes with Knox which has a locked bootloader. And you can't downgrade, check out this http://forum.xda-developers.com/showthread.php?t=2544503 that's why asking if there is a safestrap for Tmobile Galaxy S4.

htcp85 said:
Well as far as I know the jelly bean 4.3 update comes with Knox which has a locked bootloader. And you can't downgrade, check out this http://forum.xda-developers.com/showthread.php?t=2544503 that's why asking if there is a safestrap for Tmobile Galaxy S4.
Click to expand...
Click to collapse
I am interested in someone answering this question - I am selling off by i337 and have bought m919. Will appreciate if someone explains because I read that m919 has Knox, but when I asked I was told its ok to flash recoveries. It confuses me

Basically knox is there to void your warranty. You can root, flash new kernels, and ROMS, but it will flag knox. Doesn't mean you can't do it, it just means that you'll no longer be able to send your phone back to samsung or tmo for warranty service. Flash away!

I tried safestrap while I was on 4.3 just to mess around and it worked fine for me, but as mentioned you don't need it.
Sent from my SGH-M919 using Tapatalk

Peñaran561 said:
I tried safestrap while I was on 4.3 just to mess around and it worked fine for me, but as mentioned you don't need it.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
So you was on 4.3 with Knox locked bootloader and try safestrap, but you said we don't need it like they said above because the bootloader is unlocked, so that means you have an unlocked bootloader with the 4.3. I don't get it .

Also how you installed safestrap

I found the instructions on the Verizon S4 forum
Sent from my SGH-M919 using Tapatalk
---------- Post added at 05:26 PM ---------- Previous post was at 05:23 PM ----------
No locked bootloader, I just tried it out to root my phone
Sent from my SGH-M919 using Tapatalk

Peñaran561 said:
I found the instructions on the Verizon S4 forum
Sent from my SGH-M919 using Tapatalk
---------- Post added at 05:26 PM ---------- Previous post was at 05:23 PM ----------
No locked bootloader, I just tried it out to root my phone
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Well as far as I know you can root it with a locked bootloader but you void Knox Warranty 0x1. Or I'm wrong that's what I read.

Only if you flash a custom recovery or rom then yes you get 0x1
Sent from my SGH-M919 using Tapatalk

So what do you do to your phone so far

I never upgraded to the full 4.3 firmware, so I'm free to flash any ROM and GSM modem as long as I don't flash the 4.3 or 4.4 LTE modems. Those LTE modems are tied to KNOX and render your phone basically useless if you don't flash the full firmware. But, even if you do flash the full firmware with KNOX, you can still root and flash recovery. The consequence is that the KNOX counter will be tripped and Samsung or T-Mobile will take note of this if the device is ever returned for repair or replacement because tripping KNOX voids your warranty.
KNOX doesn't prevent root or lock your bootloader. Because I never upgraded to KNOX enabled firmware, I can still send my device back at no cost to myself for a warranty claim if I ever need to do so.

I installed six axis controller app to play GTA San Andreas with my PS3 controller, install Xposed to do some modding on my phone
Sent from my SGH-M919 using Tapatalk

[Q] Changing operating systems?

Ok yall I have a brick It was a Tmobile SGH-M919 and the rirmware was M919UVUFNB4. Question, since it only boots into download mode, not even recovery, can I change between M919UVUFN4B and M919UVUEMK2 and M919UVUAMDL?
Just wondering cause I'm trying to learn how to change an operateing system on phones
I've gotten pretty good at rooting and roms now its time to learn something new

M919UVUFN4B and M919UVUEMK2 are both knox enable firmwares. You can change between then but never go back to M919UVUAMDL. Putting on a different rom is changing the os on the phone.

Thanks. Can I simply root and remove Knox? I hate that app as much as my ex wife's cat.
Right now I have 12 hours left downloading the 4.4.2 one so after installation it will be rooted and recovery will be changed to cwm
Oh and why not go back to MDL? Is there a problem with that is or is it just incompatable?
Sent from my A200 using XDA Free mobile app

MDL is incompatible with the boatloader, if you have installed MK2 o NB4. You can brick your phone if you downgrade to MDL.
Sent from my SGH-M919 using XDA Premium 4 mobile app

wolfen1086 said:
Thanks. Can I simply root and remove Knox? I hate that app as much as my ex wife's cat.
Right now I have 12 hours left downloading the 4.4.2 one so after installation it will be rooted and recovery will be changed to cwm
Oh and why not go back to MDL? Is there a problem with that is or is it just incompatable?
Sent from my A200 using XDA Free mobile app
Click to expand...
Click to collapse
The Knox apps and the Knox flag are 2 different things. They are both security related, but the Knox flag is what gets tripped/set if you every flash a non-stock recovery to the phone.
The Knox apps are what can be used to Shut down/wipe a phone if stolen, etc
If you have ever had the MK2 or NB4 bootloader on the phone, you now have the Knox flag. You can not go back to a bootloader that doesn't have the Knox flag. MDL bootloader doesn't have the flag, so you can't flash it once you've had MK2 or NB4.
Rob
---------- Post added at 04:28 PM ---------- Previous post was at 04:23 PM ----------
wolfen1086 said:
Ok yall I have a brick It was a Tmobile SGH-M919 and the rirmware was M919UVUFNB4. Question, since it only boots into download mode, not even recovery, can I change between M919UVUFN4B and M919UVUEMK2 and M919UVUAMDL?
Just wondering cause I'm trying to learn how to change an operateing system on phones
I've gotten pretty good at rooting and roms now its time to learn something new
Click to expand...
Click to collapse
Just FYI, the phone has multiple bits of software. The bootloader and the recovery are in their own partitions. The firmware is like device drivers under Windows, and there is the radio(s). And then there is the OS. It's made up of the kernel and the interface/apps.
When you download the stock ROM from Sammobile, you are getting a partition table, a radio, a recovery (stock), the firmware and the OS. Which is why everyone on several threads has suggested you to download and install that with ODIN. It should get you back to a working phone.
Rob

Mine trips the counter that says I have changed to a custom rom, so that means I have the knox flag right? Cause when I rooted I uninstalled and deleted the knox app, tried that once before I was rooted and wound up doing a hard reset because of that app

wolfen1086 said:
Mine trips the counter that says I have changed to a custom rom, so that means I have the knox flag right? Cause when I rooted I uninstalled and deleted the knox app, tried that once before I was rooted and wound up doing a hard reset because of that app
Click to expand...
Click to collapse
No, the Custom ROM flag is different than the Knox flag.
If you boot into the Bootloader, if you have a Knox bootloader, it will say the words Knox and then have a 0x0, or 0x1, next to the word Knox.
No Knox shown, you have a bootloader that doesn't have Knox.
If 0x0 shown, the the Knox counter is NOT tripped. If 0x1 is shown, then you have a Knox bootloader and the Knox flag has been tripped.
Rob

mguzman0971 said:
MDL is incompatible with the boatloader, if you have installed MK2 o NB4. You can brick your phone if you downgrade to MDL.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
THIS IS INCORRECT! I keep seeing this all the time. THIS IS WRONG. It will NOT brick your device if you try to flash MDL firmware to a NB4 firmware. Odin will simply say "fail" and nothing will get written.
About your issue OP, you need to flash the NB4 tar file in Odin to recover from your soft brick. Then you can flash a recovery or what have you to get back to however you wish. You cannot go back to the MDL firmware after taking the MK2 or higher firmwares. The bootloader will block any attempts(as stated above).

I flashed nb4. Took me all day and night yesterday to download it, but I flashed it this morning and the spare phone is now back in its box safe and sound, I put my gmail address in it simply to make sure it worked, installed cwm recovery and chain fires root, whoever (if anybody) ends up needing it, I'll just do a factory reset and load her up again.
Sent from my A200 using XDA Free mobile app