Upgrading my TMo S4 firmware/baseband/radio from AMDL (Pre-KNOX) - Galaxy S 4 Q&A, Help & Troubleshooting

I have an older TMobile S4 still on firmware M919UVUAMDL, which I think was the version before KNOX was introduced (it definitely has no KNOX now).
I plan on upgrading the firmware with heimdall soon. Before I do, is there anything I should know, or any devs want to experiment before I blow it?
I am under the impression that there was never discovered a way to prevent KNOX bit from being blown.
I use a custom ROM, of course.

I think you can update the modem and bootloader without flashing the entire firmware.

GDReaper said:
I think you can update the modem and bootloader without flashing the entire firmware.
Click to expand...
Click to collapse
Yes, I think that too. I have seen some howto/blogs on how to do it with heimdall/odin and I will have to read them before I do the task.
I am under the impression that some hardware, like the Note 4, can have it KNOX bit reset via software. It is unfortunate that no method for this was ever found for the Qualcomm based S4.

denverjoe72 said:
Yes, I think that too. I have seen some howto/blogs on how to do it with heimdall/odin and I will have to read them before I do the task.
I am under the impression that some hardware, like the Note 4, can have it KNOX bit reset via software. It is unfortunate that no method for this was ever found for the Qualcomm based S4.
Click to expand...
Click to collapse
I don't think Knox flag 0x1 can be reset to 0x0 ever.
You can reset the flash counter but not the flag.
Same applies for the Note 4. Knox works the same, regardless of device.
You can use triangle away to reset the flash counter, but once Knox status is 0x1, it stays 0x1.

Good info here for the T-Mo version of the s4: http://forum.xda-developers.com/galaxy-s4-tmobile/help

Related

tripped knox flag to 0x1 what now?

Guys, I'm on stock 4.2.2 MGG firmware. That's how my devices came out of the box.
I rooted it just out of the box even before I put the screen protector, so now the knox flag is 0x1.
What will happen now? Will I be ever able to update to 4.3? or install ANY custom roms from the devs?
I rad the QA thread about knox, but its really unclear and there's some cross information.
The device is I9505
Thanks in advance.
bidav1 said:
Guys, I'm on stock 4.2.2 MGG firmware. That's how my devices came out of the box.
I rooted it just out of the box even before I put the screen protector, so now the knox flag is 0x1.
What will happen now? Will I be ever able to update to 4.3? or install ANY custom roms from the devs?
I rad the QA thread about knox, but its really unclear and there's some cross information.
The device is I9505
Thanks in advance.
Click to expand...
Click to collapse
The flag won't stop you doing anything with your phone at all, the only difference is that Samsung may now not honour any warranty claims for your handset.
There's also the few issues with root access not working properly with KNOX installed, but that happens with or without the flag being tripped, it's just a feature of KNOW.
Dan1909 said:
The flag won't stop you doing anything with your phone at all, the only difference is that Samsung may now not honour any warranty claims for your handset.
There's also the few issues with root access not working properly with KNOX installed, but that happens with or without the flag being tripped, it's just a feature of KNOW.
Click to expand...
Click to collapse
Dan,
From what I understand I won't be able to downgrade or upgrade to knox enabled firmwares at all since my device is now compromised.. 4.3 HAS knox in it. Am I wrong?
bidav1 said:
Dan,
From what I understand I won't be able to downgrade or upgrade to knox enabled firmwares at all since my device is now compromised.. 4.3 HAS knox in it. Am I wrong?
Click to expand...
Click to collapse
Ah, yes I forgot about that. You won't be able to downgrade (at least not easily) to non-KNOW firmwares. However there's not really any reason to now that you've already tripped the flag, so you're not missing out on anything there.
I think that's all there is, although I could be wrong.
Dan1909 said:
Ah, yes I forgot about that. You won't be able to downgrade (at least not easily) to non-KNOW firmwares. However there's not really any reason to now that you've already tripped the flag, so you're not missing out on anything there.
I think that's all there is, although I could be wrong.
Click to expand...
Click to collapse
Thing is that I'm on 4.2.2 now, and want to UPGRADE to 4.3. but 4.3 is a knox enabled firmware so it seems from what I understand is impossible?
I was also on 4.2.2 with knox status 0x1. I have flashed the leaked 4.3 firmware with knox without any problems so dont worry
Sent from my GT-I9505 using xda app-developers app
Upgrading to a higher fw will always work, even if knox is triggered. Only downgrade won't work or maybe will hardbrick your device.
Sent from my flying Galaxy S4 GT-I9505

[Q] Stock 4.3, KNOX and rooting

Alright, where to begin.
I've owned quite a few Samsung phones by now and I've rooted every single one of them and installed custom recovery and ROMs. But with KNOX on the S4 this has made me unsure...
What will happen to my device when I root it now? I figure it'll trigger the Knox flag to 0x1. What are the drawbacks of that? Will it affect the function of my device?
And is the rooting procedure done as usual with Odin like on the S3?
And maybe most of all, is it worth rooting the S4 and installing custom ROMs?
Many questions, but I haven't found any real answers to any of them...
Nothing will happen to your device when counter z 0×1
Drawback z you'll void ur warranty & youll not get official updates if u r on I9500.If ur on I9505 then triangle away can solve both problems.No function gets hampers until you really mess with ur phone but that's after root
Yes the procedure z same
Well if ur on I9500 then there r only customised stock version nothing much only debloated or deodexed.If ur on I9505 then definitely worth it
Sent from my GT-I9500 using XDA Premium 4 mobile app
Triangle away dont do much with the knox . Once trigger there is no way at the moment to reset this.
hjertis said:
Alright, where to begin.
I've owned quite a few Samsung phones by now and I've rooted every single one of them and installed custom recovery and ROMs. But with KNOX on the S4 this has made me unsure...
What will happen to my device when I root it now? I figure it'll trigger the Knox flag to 0x1. What are the drawbacks of that? Will it affect the function of my device?
And is the rooting procedure done as usual with Odin like on the S3?
And maybe most of all, is it worth rooting the S4 and installing custom ROMs?
Many questions, but I haven't found any real answers to any of them...
Click to expand...
Click to collapse
What happens when you actually get Knox flagged to 0x1?
You basically lose the ability to install Knox softwares, and your device will be flagged as 'insecure', which means if your company allows employees to bring their own device to work for accessing corporate emails etc and they use knox to keep security, your device will not allow this. However, you will still have the ability to use future samsung firmware releases even though you have the knox flagged.
How do you trigger Knox?
You still can root your phone with CFautoroot, but that will trigger knox to flagged to 0x1. If you try to downgrade your firmware, knox will also trigger to 0x1, therefore, once you upgrade to new bootloader, there is no way to go back to old bootloader without knox. (I would suggest if you do not want knox, but you want the new firmware, you've got to manually flash the modem.bin files using Odin)
Lastly, there is still a big question mark as to whether Samsung will actually service devices with knox 0x1
kenshi08 said:
What happens when you actually get Knox flagged to 0x1?
You basically lose the ability to install Knox softwares, and your device will be flagged as 'insecure', which means if your company allows employees to bring their own device to work for accessing corporate emails etc and they use knox to keep security, your device will not allow this. However, you will still have the ability to use future samsung firmware releases even though you have the knox flagged.
How do you trigger Knox?
You still can root your phone with CFautoroot, but that will trigger knox to flagged to 0x1. If you try to downgrade your firmware, knox will also trigger to 0x1, therefore, once you upgrade to new bootloader, there is no way to go back to old bootloader without knox. (I would suggest if you do not want knox, but you want the new firmware, you've got to manually flash the modem.bin files using Odin)
Lastly, there is still a big question mark as to whether Samsung will actually service devices with knox 0x1
Click to expand...
Click to collapse
I agree with you except last words. Modem has nothing to do with knox... flashing a different modem version from rest of FW version (ROM and CSC) will probably give some data or voice problems, and he will still have the same android 4.2.2 version....
What I suggest if he wants last FW, is just flash it, root it, delete all knox files, assume he will have knox bit activated, and enjoy it.

[Q] i9505 "clean" stock Android

Hello guys,
I’m aware this has been discussed many times before, but this information is "old" most of the times. My Galaxy S4 (i9505) is now running stock Touchwiz Android 4.3 (i9505XXUEMJ7).
What I want to do is the following: flash my phone to a i9505G, but with some research I've found that that isn't possible. Are there any other ways to get the clean i9505G 4.4.2 ROM without any changes (like root) on my i9505? (I know there are much custom ROM's, but if possible I'd like to keep it "stock".)
Since I'm running 4.3 with Knox I'm a little scared about the Knox 0x1 status, is this already "resolved" or will this still be a problem?
Thanks.
Broodplank's AOSP rom is the way to go:
http://forum.xda-developers.com/showthread.php?t=2397511
You still need to flash a custom recovery to flash it, though. I recommend CWM. Simply works.
tsphere said:
Broodplank's AOSP rom is the way to go:
http://forum.xda-developers.com/showthread.php?t=2397511
You still need to flash a custom recovery to flash it, though. I recommend CWM. Simply works.
Click to expand...
Click to collapse
Thanks for your reply. Rooting and flashing a custom recovery shouldn't be a problem, however I'm still a little worried about Knox, there simply isn't a way to reset it after it goes to 0x1?
The HTC One can be "changed" into a HTC One Google Edition: http://forum.xda-developers.com/showthread.php?t=2358781
But as far as I can tell this isn't possible for the Galaxy S4?
As far as i seen, once you flash something with odin, your knox flag gets changed. However it's not clear to me whether it changes the warranty actually...
tsphere said:
As far as i seen, once you flash something with odin, your knox flag gets changed. However it's not clear to me whether it changes the warranty actually...
Click to expand...
Click to collapse
It's not just the warrenty I'm worried about. If I want to sell the phone later I want it to be fully working, I assume with Knox 0x1 Knox isn't working anymore?
JoeyLe said:
Thanks for your reply. Rooting and flashing a custom recovery shouldn't be a problem, however I'm still a little worried about Knox, there simply isn't a way to reset it after it goes to 0x1?
The HTC One can be "changed" into a HTC One Google Edition: http://forum.xda-developers.com/showthread.php?t=2358781
But as far as I can tell this isn't possible for the Galaxy S4?
Click to expand...
Click to collapse
In theory every non G device can be converted into a G device if the hardware model is the same but in practice is not always accomplished 100%. The problem here is Knox, for waht I understand it has 2 layers: The knox bloatware that comes stock on sammys ROM and the off rom portion included in the bootloader. The bootloader is basically what the system loads up first
. so it can't bypassed. So to kkep it simple, if you flash ANYTHING (not sure however if re flashing the stock original ROM activates the flag) on the knox bootloader (AKA: new bootloader) the ''flag'' will change to 0x1, this flag is called eFuse so basically 0x1 means is burned and it can't be changed ANYWAY. If you don't plan to use your phone for work you shouldn't care about the flag.
For more information you can check this thread
http://forum.xda-developers.com/showthread.php?t=2447832
JoeyLe said:
It's not just the warrenty I'm worried about. If I want to sell the phone later I want it to be fully working, I assume with Knox 0x1 Knox isn't working anymore?
Click to expand...
Click to collapse
1. It isn't clear if Knox 0x1 voids warranty or not.
2. If you have Knox 0x1 your phone will work fine, but you won't be able to use Knox security enhancements.
3. You can't convert the 9505 to the 9505G, the Google Play edition has different bootloader, modem and pit partition.
Enviado do meu Xposed Galaxy S4 4G LTE
dclarkg said:
In theory every non G device can be converted into a G device if the hardware model is the same but in practice is not always accomplished 100%. The problem here is Knox, for waht I understand it has 2 layers: The knox bloatware that comes stock on sammys ROM and the off rom portion included in the bootloader. The bootloader is basically what the system loads up first
. so it can't bypassed. So to kkep it simple, if you flash ANYTHING (not sure however if re flashing the stock original ROM activates the flag) on the knox bootloader (AKA: new bootloader) the ''flag'' will change to 0x1, this flag is called eFuse so basically 0x1 means is burned and it can't be changed ANYWAY. If you don't plan to use your phone for work you shouldn't care about the flag.
For more information you can check this thread
http://forum.xda-developers.com/showthread.php?t=2447832
Click to expand...
Click to collapse
Thank you very much! That was very interesting to read. I personally don't care about Knox, all the Samsung bloatware is the main reason I want to have stock Android on my S4.
dandroid13 said:
1. It isn't clear if Knox 0x1 voids warranty or not.
2. If you have Knox 0x1 your phone will work fine, but you won't be able to use Knox security enhancements.
3. You can't convert the 9505 to the 9505G, the Google Play edition has different bootloader, modem and pit partition.
Enviado do meu Xposed Galaxy S4 4G LTE
Click to expand...
Click to collapse
Thanks for the information. I see there are many custom roms which are very close to stock Android, that should be fine as well.
JoeyLe said:
Thanks for the information. I see there are many custom roms which are very close to stock Android, that should be fine as well.
Click to expand...
Click to collapse
Sure, but the 4.4 roms (Google Play) have one main issue, random reboots.

[Q] Knox warranty, weird situation

As I know it is impossible to revert a tripped knox on an i9500 ...
But Today I switched to Note Edge, and I will hand over S4 i9500 to one of my family members so I just flashed I9500UBUGNJ1_I9500UUBGNJ1_I9500UBUGNJ1_HOME.tar.md 5 via odin..
And what i see now on the download mode is Knox Warranty Void : 0
I have rooted and installed unlimited number of custom roms. Is it really what I am thinking? My knox counter really reset itself?
If yes, how is it possible?
Are you sure that it says knox 0x0? otherwise i'll call an exorcist because it's impossible.
Rare.
If this attachment tells it is knox 0x0...
After the firmware flash which I have mentioned in the first post, my phone is back in warranty again...
weird.. exorcism...
is it reality or just time pass?
this is real.
I couldn't beleive that's why I have posted it...
I bought the phone when it was famous.. there were like tens of roms weekly.. I have started with Wanam and a lot of others.. perseus kernel etc.. basically there is no way that the knox was not tripped...
before last flash, I had one of omega roms with omega kernel (SELinux = permissive).. then I have flashed the rom in the first thread without any special action.
and magically it is knox = 0 again
gurc4n said:
As I know it is impossible to revert a tripped knox on an i9500 ...
But Today I switched to Note Edge, and I will hand over S4 i9500 to one of my family members so I just flashed I9500UBUGNJ1_I9500UUBGNJ1_I9500UBUGNJ1_HOME.tar.md 5 via odin..
And what i see now on the download mode is Knox Warranty Void : 0
I have rooted and installed unlimited number of custom roms. Is it really what I am thinking? My knox counter really reset itself?
If yes, how is it possible?
Click to expand...
Click to collapse
The rom you flashed it's kitkat. Maybe it has updated the bootloader and... voila. Who knows?!
After flashing official lollipop via ODIN from sammobile knox warranty changed from 0x1 -> 0
And rooting again changed knox from 0 -> 1
Reflashing again via odin knox remained 1 only.
Wierd...
May someone of you try downgrading and then upgrading and see if it untripps?
Excuse me for my horrible English.
I read 2 weeks ago,that is possible to reset the knox counter on the s4 exynox processor model because the KNOX Flag is on the emmc (Flash card) Maybe this on its possible to reset it.
By flash a new rom most files get erased and new one get rewriting.
On the Snapdragon S4 the Knox Flag is standing in a area of the processor.
Sent from my GT-I9505 using XDA Free mobile app
There is a .TAR file reportedly on XDA in the Note 3 forums that when flashed through Odin resets the bit for the Note 3. However, whether that actually is the case is a matter of speculation. I saw a video showing it in action, but take the video with a grain of salt.
Strephon Alkhalikoi said:
There is a .TAR file reportedly on XDA in the Note 3 forums that when flashed through Odin resets the bit for the Note 3. However, whether that actually is the case is a matter of speculation. I saw a video showing it in action, but take the video with a grain of salt.
Click to expand...
Click to collapse
Are you talking about the Exynos Note 3?, this S4 version that this man was talking has a Exynos processor too. It seems that it is writiable.
gurc4n said:
If this attachment tells it is knox 0x0...
After the firmware flash which I have mentioned in the first post, my phone is back in warranty again...
weird.. exorcism...
Click to expand...
Click to collapse
Can't see anywhere that you had 0x1 before. You only show what state is after flash NJ1.
Custom ROM, kernel or recovery don't update/downgrade bootloader where Knox is based and should not trip anything but possible flash counter.
themetapirate said:
Are you talking about the Exynos Note 3?, this S4 version that this man was talking has a Exynos processor too. It seems that it is writiable.
Click to expand...
Click to collapse
Yeah, I was talking about the Exynos version. There's people who dispute whether it works or not, despite a YouTube video showing it in action.
Shouldn't knox be '0x0' instead of '0'?
SuperThomasLab said:
Shouldn't knox be '0x0' instead of '0'?
Click to expand...
Click to collapse
Certainly a 0 or a 1 on Lollipop now, so it changed over at some point.

Consequences of tripping knox?

Hey,
I've heard that tripping knox might disable the ability to use Samsung Pay in the future.
Do you know any other consequences of tripping knox - like being unable to use the fingerprint scanner or updating OTA on stock rom?
Yes.....OTA will more than likely be broken.
If your employer asks you to bring your device to work, you won't be able to connect to their secure server network.
Samsung *are* using tripped knox to deny warranty repairs....even if the fault is hardware based and couldn't possibly have been caused by modified software. (Some users will say that they have had a repair with tripped knox, but that's down to nothing more than pure luck.....Samsung's official line is that tripping knox WILL void warranty)
There may be other effects from tripping knox that I don't know about....best to see if anybody else answers.
http://i.imgur.com/rVnFwJM.jpg
The S5 won't have Samsung Pay. Not the way the S6 does it. It's missing the MST chip.
Might as well root.
OTA still works after tripping KNOX (Stops working once you root or flash anything custom but starts working again once you're back on stock), I haven't found anything that doesn't work, fingerprint and private mode etc all still work
Haven't used Samsung Pay, possible things like that might stop working, but I have my doubts it breaks anything other than warranty
keithross39 said:
Yes.....OTA will more than likely be broken.
If your employer asks you to bring your device to work, you won't be able to connect to their secure server network.
Samsung *are* using tripped knox to deny warranty repairs....even if the fault is hardware based and couldn't possibly have been caused by modified software. (Some users will say that they have had a repair with tripped knox, but that's down to nothing more than pure luck.....Samsung's official line is that tripping knox WILL void warranty)
There may be other effects from tripping knox that I don't know about....best to see if anybody else answers.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
What do you mean about not being able connecting to a secure server network? I've never heard about that before :/
s3nr1 said:
The S5 won't have Samsung Pay. Not the way the S6 does it. It's missing the MST chip.
Might as well root.
Click to expand...
Click to collapse
Yeah, considering the age of the phone, I'm also thinking about doing it without worrying about those thing - not sure yet though.
*Detection* said:
OTA still works after tripping KNOX (Stops working once you root or flash anything custom but starts working again once you're back on stock), I haven't found anything that doesn't work, fingerprint and private mode etc all still work
Haven't used Samsung Pay, possible things like that might stop working, but I have my doubts it breaks anything other than warranty
Click to expand...
Click to collapse
And you're positve that OTA and all the other stuff still works like if it was 0x0?
Thanks for the answers
Daabeck said:
And you're positve that OTA and all the other stuff still works like if it was 0x0?
Click to expand...
Click to collapse
Of course, that's how I update, I just flash back to stock, and OTA update, then root again
OTA only stops working if it sees you have modified the OS, such as root or adblocking etc, that's why I flash back to stock for the OTA
If you've never heard of a secure server network (also called a 'business enterprise' network) and your employer has never asked you to/will never ask you to bring your device to work, tripping knox is not an issue.....The main thing you have to consider is what if you need a warranty repair?.......
http://i.imgur.com/rVnFwJM.jpg
I will attest to the fact that it does. However if you reflash the factory image no Knox
Sent from my SM-G920P using Tapatalk
p0krf2ce said:
I will attest to the fact that it does. However if you reflash the factory image no Knox
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Do you even understand what KNOX is?
Attest to the fact that it does what?
Flashing stock does NOT reset KNOX
*Detection* said:
Do you even understand what KNOX is?
Attest to the fact that it does what?
Flashing stock does NOT reset KNOX
Click to expand...
Click to collapse
Totally agreed.......
One of the most experienced, highly respected developers on XDA (Chainfire) is of the informed opinion that knox is an eFuse.
As such it CANNOT be reset, and that once tripped, it REMAINS tripped........forever......
http://i.imgur.com/rVnFwJM.jpg
I have tripped KNOX and the finger scanner does not work. Samsung Pay does not work (B.A. at least).
When I fash back to stock counter reads 0x0. Forgive my ignorance of the efuse.
Sent from my SM-G920P using Tapatalk
---------- Post added at 11:47 AM ---------- Previous post was at 11:43 AM ----------
*Detection* said:
Do you even understand what KNOX is?
Attest to the fact that it does what?
Flashing stock does NOT reset KNOX
Click to expand...
Click to collapse
Sent from my SM-G920P using Tapatalk
p0krf2ce said:
I have tripped KNOX and the finger scanner does not work. Samsung Pay does not work (B.A. at least).
When I fash back to stock counter reads 0x0. Forgive my ignorance of the efuse.
Sent from my SM-G920P using Tapatalk
---------- Post added at 11:47 AM ---------- Previous post was at 11:43 AM ----------
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
If it says 0x0, then you never tripped KNOX in the first place
And the fingerprint scanner works fine with tripped KNOX, something else is wrong
Or you don't have an S5
*Detection* said:
If it says 0x0, then you never tripped KNOX in the first place
And the fingerprint scanner works fine with tripped KNOX, something else is wrong
Or you don't have an S5
Click to expand...
Click to collapse
I am using the S6 but have had the S 5 and S 4. I have tripped KNOX using TWRP method purposely. Flashed stock and I read 0x0. Ping-pong works fine. I have soft bricked, bootlooped, ended up with just battery symbol. And stock has always brought me back to life. I am not arguing but as far as the software is concerned it looks like I haven't tripped KNOX. So I must not understand somethong else. I thought the efuse was hardware?
Sent from my SM-G920P using Tapatalk
p0krf2ce said:
I am using the S6 but have had the S 5 and S 4. I have tripped KNOX using TWRP method purposely. Flashed stock and I read 0x0. Ping-pong works fine. I have soft bricked, bootlooped, ended up with just battery symbol. And stock has always brought me back to life. I am not arguing but as far as the software is concerned it looks like I haven't tripped KNOX. So I must not understand somethong else. I thought the efuse was hardware?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
To put it very simply, if you had EVER tripped KNOX on the S5 (Can't speak for other devices) then 1000% you have never ever reset it from 0x1 back to 0x0, guaranteed
KNOX is a hardware eFuse yes, once it burns out, that's it, gone, forever on 0x1
Flashing stock does absolutely nothing to repair KNOX 0x1, nothing, so get that out of your head
Bricking your phone, and recovering it by flashing stock again, has no connection to KNOX 0x1 > 0x0
It's easy as pie to unbrick an S5, it's impossible to reset KNOX 0x1
In fact, last I heard, there was a substantial reward for anyone who managed to reset KNOX back to 0x0
*Detection* said:
To put it very simply, if you had EVER tripped KNOX on the S5 (Can't speak for other devices) then 1000% you have never ever reset it from 0x1 back to 0x0, guaranteed
KNOX is a hardware eFuse yes, once it burns out, that's it, gone, forever on 0x1
Flashing stock does absolutely nothing to repair KNOX 0x1, nothing, so get that out of your head
Bricking your phone, and recovering it by flashing stock again, has no connection to KNOX 0x1 > 0x0
It's easy as pie to unbrick an S5, it's impossible to reset KNOX 0x1
In fact, last I heard, there was a substantial reward for anyone who managed to reset KNOX back to 0x0
Click to expand...
Click to collapse
I have tripped on the s4 variant repeatedly and reset the counter. And if there is a reward I deserve it. Because i have tripped the KNOX counter and reset as many other developers have. Here's a link to a great discussion on XDA about Locke and how to reset the counter if you're worried about your warranty. http://forum.xda-developers.com/showthread.php?t=2738175
I am not arguing the validity of some efuse but I can make the software say 0x0 after 0x1.
Sent from my SM-G920P using Tapatalk
No you can't, not on the S5, which is the forum you are in right now, while talking about S6 and S4s....
If you do not own the S5, leave
You deserve nothing other than being put on iggy tbh
Read the thread you just linked to, all of it, show me the part that has the tutorial on resetting the S5 KNOX eFuse...
Go away troll
In fact, make an uncut video, showing the S5 with 0x1, and show how you reset it back to 0x0 - go ahead
Here's Chainfire's Google+ blog for additional info.......
https://plus.google.com/+Chainfire/posts/LCfF5A9fsTG
http://i.imgur.com/rVnFwJM.jpg
Wow, people nowadays, somehow lollipop managed to bring on such ignorance, he just doesn't understand.
Frost009 said:
Wow, people nowadays, somehow lollipop managed to bring on such ignorance, he just doesn't understand.
Click to expand...
Click to collapse
Um excuse me? Who EXACTLY are you calling ignorant? Chainfire by any chance?
If it is.....YOU stand to be corrected, as he KNOWS and UNDERSTANDS a damn sight more about android than 95% of members on here EVER WILL......including you or me.
http://i.imgur.com/rVnFwJM.jpg
I read it as him talking about "p0krf2ce" - at least I hope he was
EDIT -After reading some other of his posts, I'm beginning to wonder...

Categories

Resources