Database Info

[Q] samsung galaxy s3 root accidentyl updated help!

I have a rooted android device samsung galaxy s3 and it was running fine and everything till one day it said to install an update. i accepted it and while it was updating all of a sudden it went to that black screen and says, " system software not authorized by Verizon Wireless has been found on your phone. Please turn off you phone and go to the nearest Verizon Wireless store for help." Then thats where i couldn't do anything with my phone but go to download/ODIN MODE and rebooting system thing where you can reboot system. I am very new and i don't know much about rooting and the meanings of a lot of words like unlock bootloader. If i go to ODIN MODE it says
ODIN MODE
PRODUCT NAME: SCH-1535
CUSTOM BINARY DOWNLOAD: Yes (1 Counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty bit: 1
BOOTLOADER RP SWREV:1
I think this doesn't look good. What should I do to make my phone be working again and not showing that black screen?
I already wiped all data and tried to do that StockROm thing on my computer ODIN and still nothing.
Is my bootloader locked? if so do I need to unlock it to make my phone work again? Thanks so much for your time

Did you updated after rooting your SGS3 Verizon?
Games are a part of Life but Life is not a part of a game!

I am in the same position as a lot of people with the s3. I have the Verizon model and had it unlocked using Odin while it was on 4.2. I accepted the Verizon update to 4.3 forgetting that it unroots it. Some people are saying that the only way to get my phone unlocked again is to find a way to flash it back to 4.2 version. Is there ANYWAY to unlock it on the 4.3 without bricking it??? If there is, how so???? Please help!!
Sent from my SCH-I535 using xda app-developers app

Check modem version and your product code and massage me again!
Games are a part of Life but Life is not a part of a game!

Not sure what happened....PLEASE HELP

Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks

scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.

scottrf8 said:
Hey. So I have a note 2 on at&t. It was on 4.3. I used odin to downgrade to 4.1.1, then factory unlocked it and all was well. I tested with tmobile sim and it was on tmobile 4g and able to make calls using tmobile. I then went to update the version (I read once its unlocked it can be updated) Now, it gets stuck at "samsung galaxy note 2" when booting up and wont go past it. I tried to odin it again and successfully installed 4.1.1, but still wont get past samsung galaxy note 2. have disconnected phone and tried to boot up using vol+ (+) home button (+) power button, but nothing......PLEASE HELP
thanks
Click to expand...
Click to collapse
I start to wonder if people research before doing anything.
To say again. You can't downgrade. You have Knox. You possibly tripped the Knox flag. Reflash the 4.3 stock ROM. If that fails, It's most probably eFuse, if It's 4.3.
(Basically, eFuse messes up your phone aka bricks You phone aka @#%& it up.)
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
---------- Post added 5th January 2014 at 12:05 AM ---------- Previous post was 4th January 2014 at 11:59 PM ----------
mcgrabowski said:
I don't have a Note (I have the GS3 on TMO). Do you have any idea if the Note 2 has the same issue that the GS3 has, where with the 4.3 update you get a new locked bootloader that prevents you from going back to anything earlier than 4.3? That's the way it is on the GS3. I guess if you were able to actually boot up and make calls after you downgraded back to 4.1.1, then that must not be the case.
In any case, you're getting stuck on the boot logo when you power it on? Can you get into the recovery at all? Do you have the stock recovery or a custom recovery installed? Have you tried clearing cache/dalvik and fixing perms? That often fixes things for me when I'm stuck on the boot logo.
Click to expand...
Click to collapse
You're right. The locked bootloader messed those who didn't research about it's life's real bad. 4.3 supposedly has eFuse in it, which FU*CKS your phone. I read it up on the Samsung Knox website, and it said that eFuse "rewrites a read-only part of the phone, resulting in a unusable phone." If u triggered that, it'll be a hard brick, (in my knowledge)
Knox itself is irritating. The Knox Warranty Void counter, which max at 1, is unresetable, (even with JTAG, will brick if h try) so your warranty is *poof*
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.

I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?

scottrf8 said:
I did a fair amount of research before downgrading. In fact I didn't want to downgrade, but I did want to unlock it. It is unlocked and it's running on 4.1.1. So when you say that you can't downgrade, you mean you shouldn't downgrade cause then you will be stuck with 4.1.1?
Click to expand...
Click to collapse
When you were on 4.3, was that an OTA update or an ODIN flash of a stock firmware? Or did you just have a 4.3 ROM from the forums that you loaded (AOSP or rooted stock based ROM with Knox, etc., removed) with TWRP or CWM? Supposedly from what I've been reading if you take the 4.3 OTA or ODIN flash the stock 4.3, the bootloader gets updated, as Irwenzhao mentions above and I've experienced, where you CAN'T downgrade again to 4.1.2 or earlier. I believe that just means you can't go back to a fully stock pre 4.3. I THINK it just means you can't ODIN back to a factory image earlier than 4.3, which is what I experienced. But with TWRP or CWM, I believe I can still load other ROMs at will regardless if they are pre 4.3 or not.

yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?

scottrf8 said:
yeah, that sounds kinda like the same thing I have come across. 4.3 was OTA and downgraded to a stock 4.1.1 ROM. Guess this triggers KNOX cause now KNOX WARRANTY VOID is 1. which once that is triggered, you cannot go from a non KNOX version (4.1.1) to a version that has KNOX. My question now is does that apply to just the stock firmware? Would ANY of the ROM's created by the devs work?
There were some posts in the unlock thread that people were able to go from 4.1.1 (after downgrading) back up to 4.3. Just trying to figure out how that would be the case? Could the knox warranty flag not have been set for them?
Click to expand...
Click to collapse
Just to make it clear, Knox is a bootloader, which means u can flash anything that's not a bootloader, but your warranty would be history. Flashing anything trips the flag, even 4.1.1/2 stock ROMs.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.

Truthfully, that doesn't clear it up. Do the stock firmware through Kies or ota include a bootloader and that's why it won't install? Thanks

Flashing the stock firmware through kies, ODIN, or the OTA update will update the boot loader as far as I know and will ruin any chance of returning to stock and void your warranty. As long as you don't want to do that, I don't think it's too big of a deal.
At this point, I couldn't care less about the warranty. I would think it's expired now anyhow. As long as I can flash ROMs and boy the phone up and use it. I'm happy.
Sent from my SGH-T999 using xda app-developers app

Canadian Note 3 (N900W8) Knox Thread (0x0 can be maintained)

There are users here in Canada with Note 3's that have "Custom" in "Current Bianary" and "System Status".
This information has not been posted, I have NO idea why. I am guessing these people could care less about us (the people still in the dark).
I have only just obtained a Note 3 (Week ago) and I am trying to figure this stuff out.
We have a special Note 3 in our N900W8's. Apparently we can:
- Downgrade from 4.4.2 to 4.3 via Odin 3.09 without tripping Knox (not sure if this requires the Mexican bootloader first or if we can do it with our Canadian bootloaders)
- Keep Knox at 0x0 with Custom Everything else. From what I see, our bootloaders are unlocked allowing us to flash our phones in Odin with multiple files (not 1 file mode as this contains a bootloader) as long as we dont include the bootloader (theory from what I have seen, and read a few times, no confirmation).
However I can not get an answer out of anyone who knows anything. I cannot just blindly flash and see if Knox is tripped, I'll only get one shot. Not worth it IMO.
Can anyone chime in on this? Is it acceptable to call members out? I know exactly who the 2 people are that have Custom everything and Knox at 0x0. 2 Torontonians, younger guys, doesn't seem like they want to talk though. Can I call them in here, is that acceptable behavior? Never done that before. Hehe.

I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.

I PM'd you but yeah, I'm Knox 0x0 on X-Note 12 right now. Sorry about that, wasn't home.

kiru said:
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
Click to expand...
Click to collapse
That link notes that installing a custom recovery will trip knox. Could you please verify what you did to install custom recovery and still maintain knox 0x0? Will be very interested in your follow-up.

kiru said:
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
Click to expand...
Click to collapse
Could you also PM me the procedure? Knox is really bugging me and TW is bloated with too many craps. X-Note looks awesome! Thanks !

bingbinghaha said:
Could you also PM me the procedure? Knox is really bugging me and TW is bloated with too many craps. X-Note looks awesome! Thanks !
Click to expand...
Click to collapse
Actually, I would be interested too. Any chance of posting the procedue instead of PM to multiple users? If not, please PM me as well

I followed the guide in the link I posted as it is pretty detailed already. I have root and cwm recovery installed with Knox at 0x0.

kiru said:
I followed the guide in the link I posted as it is pretty detailed already. I have root and cwm recovery installed with Knox at 0x0.
Click to expand...
Click to collapse
Second that.
---------- Post added at 12:55 AM ---------- Previous post was at 12:38 AM ----------
Okay here. https://www.youtube.com/watch?v=Tks73wZH3qg&list=UU2FLZg9YNAr4YAd0VEDDKGQ
You have to pause to see it at the beginning, and in hindsight, I probably have should of started in CWM, then booted into recovery, but whatever.
Set it to HD and pause it at the beginning, you can see my Knox 0x0. Then watch the video and I boot into the ROM, then back into CWM, all in one cut.
Cheers.

Same here
Knox 0x0 here, after a few good reasons to trip it
Android newcomer here.
I have a Bell Canada SM-N900W8, and it came with 4.3. Rooted 4.3 with Kingo (noob style) and that was just perfect to start out. Then the OTA came out. I unrooted the device, reseted with Kies 3 update to 4.4.2 and then Kingo wasn't working anymore of course.
At that point I decided I didn't care about tripping knox and installed TWRP to start trying roms... Tried like 2-3 1+gb complete packed roms (bootloops, probably cauz im a noob) then I wiped from TWRP, restored my OTA backup, flashed with CF-Auto-Root international version (canadian is another bootloop) and then flashed a CivZ kernel +stock-modification rom that I now simply keep clean with Titanium Backup and some apps y'all know about.
Some more info :
My version is VLUCNB7
My current kernel [email protected]
My current SE state is Permissive
Again, Knox is 0x0. Even after bootloops of custom crap that was crashing and I'm custom-rom, custom-kernel.
Two facts to finish that off
1) That's weird
2) I'm a lucky *****
Have a great day

What if I want to use a custom 4.3 ROM (just to get BT Tethering) without tripping KNOX?
The guides seems to push you to install the 4.4 ROMs.

I have the Bell version of N900W8.
Started at MI5, rooted de la vega, then wanted to upgrade to 4.4.2.
Used polishpats way of upgrading with the leaked 4.4.2, flashed all the AP,CSC,CP,PIT, then installed TWRP and autorooted, both with Odin 3.09 - no knox trip
Wanted to try X-note, installed it using TWRP, and no knox trip
Upgraded the kernel using TWRP, no knox trip
Did not like X-note, wanted to go back to 4.4.2, and reflashed it - no knox trip
Downgraded back to 4.3, no knox trip
upgraded to offical 4.4.2, no knox trip
rooted via chainfire and odin - no knox trip
now sitting at rooted 4.4.2 with 0x0 still

Are you basically saying Bell's N900W8 is KNOX untripable?
I'm on MJ4 (UDLV Rooted) with remaining with MJ1 Bootloader
Since I don't want a KITKAT rom, can I just install a custom recovery (TWRP) without doing all that Mexican instruction stuff?
I really just want a 4.3 ROM with BT Tethering.

klau1 said:
Are you basically saying Bell's N900W8 is KNOX untripable?
I'm on MJ4 (UDLV Rooted) with remaining with MJ1 Bootloader
Since I don't want a KITKAT rom, can I just install a custom recovery (TWRP) without doing all that Mexican instruction stuff?
I really just want a 4.3 ROM with BT Tethering.
Click to expand...
Click to collapse
Hello,
My friend has just the same phone as me, he bought it a few weeks before me, and he used his own techniques and got 0x1 knox tripped, so I just can't warn you enough : not all N900W8 are "untrippable"
...but...I didn't trip mine and I'm not alone.
Without more information you can't just say canadian w8's are untrippable, cauz they are.

Well, are older the better?
I got mine the first week it came out.

klau1 said:
Well, are older the better?
I got mine the first week it came out.
Click to expand...
Click to collapse
I doubt it.
Will look into this. I am positive all N900W8's are the same.
Surely your friend missed something or did something improperly to trip Knox.
Taking this all in. Thanks for the posts guys!

@nexxusty
in your opinion, do you have to go thru installing KITKAT rom from Mexico if you just want to install another 4.3 ROM that has BT Tethering without tripping KNOX?

klau1 said:
@nexxusty
in your opinion, do you have to go thru installing KITKAT rom from Mexico if you just want to install another 4.3 ROM that has BT Tethering without tripping KNOX?
Click to expand...
Click to collapse
Klau you took the question right out of my head brother. LOL.
I am not sure... this also pains me as I want to try CF-auto Root right now on 4.4.2 Rogers.
From my knowledge of technology, I dont think it will. Not positive though. I am hoping you do not need to flash this.
I will test for us. Here is hoping I wont lose my warranty. Will report back.

nexxusty said:
Klau you took the question right out of my head brother. LOL.
I am not sure... this also pains me as I want to try CF-auto Root right now on 4.4.2 Rogers.
From my knowledge of technology, I dont think it will. Not positive though. I am hoping you do not need to flash this.
I will test for us. Here is hoping I wont lose my warranty. Will report back.
Click to expand...
Click to collapse
Flashed CF-Auto-Root, flashed TWRP 2.6.3.0, 0x0 still!
Now for the info on my phone.
I have done as follows.
Phone came with 4.3 stock --> Root De La Vega --> Flashed 4.4.2 Stock (Rogers) with Odin 3.09 --> CF Auto-Root --> TWRP 2.6.3.0 = Rooted 4.4.2 with TWRP 2.6.3.0 Recovery and Knox @ 0x0.
I'm not stopping here. Will flash everything DrawntoLife has.
Appreciated my man. Thanks again! Easy to Follow Step By Step Tutorial **WILL** be written tonight after I am done at a LAN I am already late for figuring this out.
Talk soon everyone! Happy flashing!

did you consider extracting the ODIN package and leave out the Bootloader?
Remember we had to do that upgrading from MJ1 to MJ4. Reportedly, it was the newer bootloaders that trip KNOX.

klau1 said:
did you consider extracting the ODIN package and leave out the Bootloader?
Remember we had to do that upgrading from MJ1 to MJ4. Reportedly, it was the newer bootloaders that trip KNOX.
Click to expand...
Click to collapse
When I updated to 4.4.2? I did, but I was not sure if that would trip Knox so I left it in the package.
It's irrelevant now anyway, the bootloader in 4.4.2 Rogers is the one I am on now and allowing me to do all this still.
I suggest you update to it. Use the package labeled "N900W8VLUCNB7_N900W8OYACNB7_RWC". That is 4.4.2 for a Rogers Note 3.
I can safely assume you can flash this at any point and be fine. Even if you are already on a hacked 4.4.2 or something. There would be no issue updating the bootloader to the same version, would just overwrite it.

[Q] Will Samsung KNOX be preloaded to Galaxy Note 10.1 4.4.2?

Will Galaxy Note 10.1 4.4.2 Firmware get KNOX?
I saw KLMS Agent in Leaked 4.4.2 ROM, so I am asking....

alpha5793 said:
Will Galaxy Note 10.1 4.4.2 Firmware get KNOX?
I saw KLMS Agent in Leaked 4.4.2 ROM, so I am asking....
Click to expand...
Click to collapse
I never hear anything about this possibility...

alexs784 said:
I never hear anything about this possibility...
Click to expand...
Click to collapse
I found KNOX Agent apk in German 4.4.2 Official KK Firmware...
The 4.4.2 firmware contains KNOX.
Sent from my SHW-M480W using Tapatalk

alpha5793 said:
I found KNOX Agent apk in German 4.4.2 Official KK Firmware...
The 4.4.2 firmware contains KNOX.
Sent from my SHW-M480W using Tapatalk
Click to expand...
Click to collapse
I think Knox is gonna be present in all new firmwares from Samsung, hopefully though with the older models it is only a software flag, not a (suspected) efuse like for the S4/5 and Note 3/10.1 2014...
Question though, does the KK rom update the bootloader so you can't get back to JB and has anyone successfully rooted a KK rom?

ultramag69 said:
I think Knox is gonna be present in all new firmwares from Samsung, hopefully though with the older models it is only a software flag, not a (suspected) efuse like for the S4/5 and Note 3/10.1 2014...
Question though, does the KK rom update the bootloader so you can't get back to JB and has anyone successfully rooted a KK rom?
Click to expand...
Click to collapse
I don't know well... because I'm using SHW-M480W (Korea Edition) so I didn't updated my Note 10.1....
Sent from my SHW-M480W using Tapatalk

Let's suppose this new firmware does contain KNOX. If the tablet has a flash counter value higher than 0, would the new bootloader detect that and trigger the KNOX flag too on the first boot? In other words, should the flash counter be reset to 0 before upgrading to the new firmware or is it irrelevant?

Using the Samsung phone info app (available on play store) software I checked if Knox was triggered, it wasn't. Seems like it relies on another counter to check if you have rooted your Note 10.1...

ultramag69 said:
Using the Samsung phone info 9available on play store) software I checked if Knox was triggered, it wasn't. Seems like it relies on another counter to check if you have rooted your Note 10.1...
Click to expand...
Click to collapse
Same here, Knox wasn't detected on mine either. Even checked in the applications manager, no sign of knox is there too. Anyone got any ideas to make sure it doesn't have knox?

link6155 said:
Same here, Knox wasn't detected on mine either. Even checked in the applications manager, no sign of knox is there too. Anyone got any ideas to make sure it doesn't have knox?
Click to expand...
Click to collapse
The application manager can be a bit deceptive because I think it only shows KNOX as installed if you have created a secure container. The actual KNOX flag must be stored somewhere else on the device and handled only by the bootloader. Have you tried booting into download mode to check? If there is a KNOX flag, this is most likely where it'll be displayed, like on the Note 3 and other devices.

teh_geek said:
The application manager can be a bit deceptive because I think it only shows KNOX as installed if you have created a secure container. The actual KNOX flag must be stored somewhere else on the device and handled only by the bootloader. Have you tried booting into download mode to check? If there is a KNOX flag, this is most likely where it'll be displayed, like on the Note 3 and other devices.
Click to expand...
Click to collapse
Tried that too, there is no KNOX flag on the download mode screen.

link6155 said:
Tried that too, there is no KNOX flag on the download mode screen.
Click to expand...
Click to collapse
Looks like Samsung did us a favour and didn't include that obKNOXious thing in the new firmware :laugh: That's great news. I wonder if it's because of missing hardware or simply because they don't care enough about their old devices (spoiler alert: they don't) to add features from their newer ones.
If they had added KNOX however, that could lend more credibility to the theory that even on new KNOX-enabled devices the flag is NOT an efuse and that it's actually stored somewhere in the emmc. Oh well, I'd rather enjoy my tablet unrestricted than be concerned about triggering a stupid flag. Thanks for checking guys :highfive:

It is possible, as with the Note 3 3G version, Knox was included but there is no counter. It seems only on the 4G Qualcomm variants that the "Knox counter" is apparent. If you checkout the N9000 part of the Note 3 forums this seems to be true. I wonder if it is CPU specific? They only trigger a physical change on the CPU that isn't Samsung's own...

ultramag69 said:
It is possible, as with the Note 3 3G version, Knox was included but there is no counter. It seems only on the 4G Qualcomm variants that the "Knox counter" is apparent. If you checkout the N9000 part of the Note 3 forums this seems to be true. I wonder if it is CPU specific? They only trigger a physical change on the CPU that isn't Samsung's own...
Click to expand...
Click to collapse
I've been looking into this matter quite a bit lately since I also own a Note 3 (Qualcomm LTE version - N9005) and from what I've gathered, the Note 3 N900 does have a KNOX flag and counter. However, a while ago a special service bootloader was leaked specifically for that variant, which apparently wipes this flag altogether and allows users to flash custom roms freely and downgrade to earlier software versions. The security implementation likely differs between Note 3 variants but I'm not really convinced that the flag is stored in an efuse on the Qualcomm chip. Even if that's the case though, I think Samsung so far have failed to add efuse-equivalent technology to their Exynos chips and this means that the only way for a KNOX flag to exist would be on the device memory, probably somewhere within the sboot partition or a partition of its own maybe. I don't think they would go into so much trouble to add all these security features to an almost 2 year-old device that probably also lacks the proper technologyNot to mention that many original Note 10.1 devices are not covered by warranty anymore (ie outside the EU where warranty is valid for only a year in some places) so they wouldn't really care about users voiding their warranties at this point and thus no need for the KNOX flag.
We got lucky with the Note 10.1 actually. Only a custom flash counter that's easy to reset thanks to TriangleAway and now we also get KitKat. Very nice :laugh:

[Q] root for 4.4.2

hey rooters and devs is there a stable 4.4.2 root out right now for verzion without tripping knox?
i took the update to 4.4.2 and i cant even touch mu phone since it sucks makes random noises like a dot when clicking something.
Also, when will be able to start flashing custom roms or 4.4.2. i bricked my phone like 3 times since i didnt unlock the boot loader but now i can actually flash the roms.
TL,DR root for 4.4.2 without tripping know
when will we be able to flash cyanogenmod

broazny said:
hey rooters and devs is there a stable 4.4.2 root out right now for verzion without tripping knox?
i took the update to 4.4.2 and i cant even touch mu phone since it sucks makes random noises like a dot when clicking something.
Also, when will be able to start flashing custom roms or 4.4.2. i bricked my phone like 3 times since i didnt unlock the boot loader but now i can actually flash the roms.
TL,DR root for 4.4.2 without tripping know
when will we be able to flash cyanogenmod
Click to expand...
Click to collapse
The only root exploit for VRUDNE1 4.4.2 that works on our phone is "Towelroot" by Geohot which is in the S5 section.
Once rooted, these things apply to everyone on VRUDNE1 4.4.2 as well as anyone on 4.3 VRUCML1 or VRUCNC1 OTAs:
a) You can NOT install a custom recovery (No CWM, No TWRP, nothing)
b) You can NOT install any AOSP rom
c) You can NOT install a custom kernel
d) Only an unofficial version of Safestrap can be used on VRUDNE1. This is not a custom recovery, Safestrap is NOT a custom recovery.
e) As of 8:50 EST, there is no custom VRUDNE1 TouchWiz rom to install. Safestrap hijacks the bootprocess and only uses the stock kernel, in your case stock VRUDNE1 4.4.2 kernel, in order to boot other custom TouchWiz roms. Only VRUDNE1 roms would be able to successfully flash on your phone. But none exist yet.
Literally all that you can do as of this post is root, debloat, install Safestrap, and hope that you will be able to use custom VRUDNE1 based TouchWiz roms.

back to 4.3
will i be able to odin back to 4.3 without tripping knox and locking the bootloader?
SlimSnoopOS said:
The only root exploit for VRUDNE1 4.4.2 that works on our phone is "Towelroot" by Geohot which is in the S5 section.
Once rooted, these things apply to everyone on VRUDNE1 4.4.2 as well as anyone on 4.3 VRUCML1 or VRUCNC1 OTAs:
a) You can NOT install a custom recovery (No CWM, No TWRP, nothing)
b) You can NOT install any AOSP rom
c) You can NOT install a custom kernel
d) Only an unofficial version of Safestrap can be used on VRUDNE1. This is not a custom recovery, Safestrap is NOT a custom recovery.
e) As of 8:50 EST, there is no custom VRUDNE1 TouchWiz rom to install. Safestrap hijacks the bootprocess and only uses the stock kernel, in your case stock VRUDNE1 4.4.2 kernel, in order to boot other custom TouchWiz roms. Only VRUDNE1 roms would be able to successfully flash on your phone. But none exist yet.
Literally all that you can do as of this post is root, debloat, install Safestrap, and hope that you will be able to use custom VRUDNE1 based TouchWiz roms.
Click to expand...
Click to collapse

broazny said:
will i be able to odin back to 4.3 without tripping knox and locking the bootloader?
Click to expand...
Click to collapse
No, you can not downgrade once on 4.4.2 VRUDNE1.

thank you very much, do you know when the devs will be able to find a way to downgrade or unlock the bootloader
SlimSnoopOS said:
No, you can not downgrade once on 4.4.2 VRUDNE1.
Click to expand...
Click to collapse

broazny said:
thank you very much, do you know when the devs will be able to find a way to downgrade or unlock the bootloader
Click to expand...
Click to collapse
I'll be blunt with you, I sincerely doubt that's being actively worked on for our 2 year old device. The bootloader has yet to be unlocked on the S4 which has had an active bounty with numerous devs so its not happening here. If AOSP means that much to you, sell your S3 for a bootloader unlocked S3 or get another device which has less hurdles to get AOSP.
Edit: Or you can email these guys at MobileTechVideos and see if their S3 bootloader downgrade process works on 4.4.2. It is a paid service either way, but some people have considered this when on 4.3.

SlimSnoopOS said:
I'll be blunt with you, I sincerely doubt that's being actively worked on for our 2 year old device. The bootloader has yet to be unlocked on the S4 which has had an active bounty with numerous devs so its not happening here. If AOSP means that much to you, sell your S3 for a bootloader unlocked S3 or get another device which has less hurdles to get AOSP.
Edit: Or you can email these guys at MobileTechVideos and see if their S3 bootloader downgrade process works on 4.4.2. It is a paid service either way, but some people have considered this when on 4.3.
Click to expand...
Click to collapse
Is there any successes to this downgrade of the bootloader of the link that you sent? I'm not on a s4 I'm on a SCH-I535 sgs3 same as s4 if I'm correct.. Correct me if I'm wrong s4 and s3 have a lot of the same stuff

jcbjoe said:
Is there any successes to this downgrade of the bootloader of the link that you sent? I'm not on a s4 I'm on a SCH-I535 sgs3 same as s4 if I'm correct.. Correct me if I'm wrong s4 and s3 have a lot of the same stuff
Click to expand...
Click to collapse
I haven't seen anyone report back on having used this. I figured someone would have done so and posted on xda but, nothing. That link is for the Verizon S3 btw. The S4 was mentioned just for comparison purposes only.
Sent from my SCH-I535 using Tapatalk 4

SlimSnoopOS said:
I haven't seen anyone report back on having used this. I figured someone would have done so and posted on xda but, nothing. That link is for the Verizon S3 btw. The S4 was mentioned just for comparison purposes only.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I originally saw it on XDA. Josh inadvertently reverted one while doing a JTag service. He was able to reproduce it several times in testing. Most don't even know about it till they brick their device and need JTag service.