Develop Bugs

Am I safe to update to Kitkat?

I Got this phone in the mail off Ebay today. And within the first hour I updated it to 4.3 and rooted it. And now I'm getting another OTA update notification. I'm not new to rooting and stuff but I am new to Samsung. So I'm a little worried if I should do the update or not. I don't wanna get stuck in a bootloop or anything.
I'm rooted
I'm running 4.3
I have Clockwork flashed
Rom is stock
All I'd like to know is if I am safe to update? I heard you are and then I've heard you're not.

not sure but if you can unroot you can allways re root in 4.4

If no one else has done so yet, ive got a modded ota that should allow you to flash via cwm or twrp, and should preserve root.
Its uploading now.

DocHoliday77 said:
If no one else has done so yet, ive got a modded ota that should allow you to flash via cwm or twrp, and should preserve root.
Its uploading now.
Click to expand...
Click to collapse
Alright thanks! let me know when it's up. And are you from Huntsville Alabama too?

Ok, here is the modded OTA!
It should allow you to flash via TWRP or CWM recoveries, and it should also preserve root!
You will still need to be full stock for it to work as it still will go through its checks before flashing. It is not recommended to remove these checks because it could cause problems when patching files. Especially if the files being patched have been modded.
THIS IS UNTESTED! I do not have a working device at the moment, (dont have the I747 anyway), so I am unable to test on my own before releasing. I do not foresee any problems, but there just is no way to be positive until its been tried. If there is an issue, it should still just fail before the flash like it always has been supposed to do.
Please post back ASAP after trying this out so we know if it is working or not.
Modded_OTA_UCUEMJB-UCUFNE4.zip
Hope this proves helpful for some of you!
Doc

DocHoliday77 said:
Ok, here is the modded OTA!
It should allow you to flash via TWRP or CWM recoveries, and it should also preserve root!
You will still need to be full stock for it to work as it still will go through its checks before flashing. It is not recommended to remove these checks because it could cause problems when patching files. Especially if the files being patched have been modded.
THIS IS UNTESTED! I do not have a working device at the moment, (dont have the I747 anyway), so I am unable to test on my own before releasing. I do not foresee any problems, but there just is no way to be positive until its been tried. If there is an issue, it should still just fail before the flash like it always has been supposed to do.
Please post back ASAP after trying this out so we know if it is working or not.
Modded_OTA_UCUEMJB-UCUFNE4.zip
Hope this proves helpful for some of you!
Doc
Click to expand...
Click to collapse
I would test it but I just can't. I'm pretty sure it wouldn't break anything. But I haven't had this phone for 24 hours yet, I just bought it and it's the only one I got. I even paid my bill today too. And I'm looking for another job and you have to have a phone for that lol. Post it up on the forum and let someone who knows more than I do test it because I'm just gonna have to wuss out on this one. I appreciate it though!:good::good:

No sweat. I completely understand! I may go ahead and make a thread for it, but was hoping to verify it works first. Ill post it in the other ota thread for now.
And yes, I am close to Huntsville. Good luck on your job hunt!

Questions and Help issues belong in Q&A and Help section..thanks
Thread moved
FNSM

[Q] Root now or wait? Tab S

I really new to android and switch from apple to android But I saw the risks of flashing to get root vs with apple Ive never seen a hard brick happened. I was wondering if I should wait till theres an app/application to root my samsung galaxy tab S 10.5 or flash a rooted rom to get root? I also heard that Android L is gonna be out soon so.. should i wait till Android L is out to root also? Im scared to flash because I dont want to turn my tab s a brick D: Like some how i seem to mess the easy stuff up.
Thanks!
p.s Im not sure if im posting this in the right place or... yeah. Pretty new to android.

DUHAsianSKILLZ said:
I really new to android and switch from apple to android But I saw the risks of flashing to get root vs with apple Ive never seen a hard brick happened. I was wondering if I should wait till theres an app/application to root my samsung galaxy tab S 10.5 or flash a rooted rom to get root? I also heard that Android L is gonna be out soon so.. should i wait till Android L is out to root also? Im scared to flash because I dont want to turn my tab s a brick D: Like some how i seem to mess the easy stuff up.
Thanks!
p.s Im not sure if im posting this in the right place or... yeah. Pretty new to android.
Click to expand...
Click to collapse
I would wait if you are new to the scene. It seems that depending on your current OS version, 4.3 (open) vs 4.4.x (locked), we have a looked bootloader. So flashing sth might leave you with a bootloader that denies loading the images because of failed hashes.
As to really bricking it, I don't think it is that easy as long as you know your way with software and IT. But DON'T flash sth or toggle some switch you don't know about. simple. I tried flashing TWRP to the recovery partition and rooting from there with SU as suggested in a thread here, BUT it wouldn't accept TWRP because of a lock...still tripped the KNOX though

JoeRifle said:
I would wait if you are new to the scene. It seems that depending on your current OS version, 4.3 (open) vs 4.4.x (locked), we have a looked bootloader. So flashing sth might leave you with a bootloader that denies loading the images because of failed hashes.
As to really bricking it, I don't think it is that easy as long as you know your way with software and IT. But DON'T flash sth or toggle some switch you don't know about. simple. I tried flashing TWRP to the recovery partition and rooting from there with SU as suggested in a thread here, BUT it wouldn't accept TWRP because of a lock...still tripped the KNOX though
Click to expand...
Click to collapse
Oh Didnt know all that stuff until now All this is very different from jailbreaking which I know alot of. Thanks for the help! I only plan on getting root and not any of the custom roms yet since im trying to not get knox tripped and the fact that i cant return my tab s for any reason because of walmarts 15-day return. I guess ill stay unrooted for now thanks again

It sucks that they try so hard to cage us in but just wait a bit, people will find out how to root even the new OS 4.4.x. Although I am not sure whether it will ever be possible to do it without KNOX tripping. Maybe you can somehow restore a tripped KNOX to 0 though...but that is over my head If you are @4.3 Android though, you might just try going ahead and flashing TWRP with Odin, and then install appropriate SuperUser .zip. Your call

JoeRifle said:
I would wait if you are new to the scene. It seems that depending on your current OS version, 4.3 (open) vs 4.4.x (locked), we have a looked bootloader. So flashing sth might leave you with a bootloader that denies loading the images because of failed hashes.
As to really bricking it, I don't think it is that easy as long as you know your way with software and IT. But DON'T flash sth or toggle some switch you don't know about. simple. I tried flashing TWRP to the recovery partition and rooting from there with SU as suggested in a thread here, BUT it wouldn't accept TWRP because of a lock...still tripped the KNOX though
Click to expand...
Click to collapse
Are you sure you know what you're talking about? All our Tablet S came with Android 4.4.2, and they are rooted just fine.
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
DUHAsianSKILLZ said:
Oh Didnt know all that stuff until now All this is very different from jailbreaking which I know alot of. Thanks for the help! I only plan on getting root and not any of the custom roms yet since im trying to not get knox tripped and the fact that i cant return my tab s for any reason because of walmarts 15-day return. I guess ill stay unrooted for now thanks again
Click to expand...
Click to collapse
You're being given wrong info. Rooting is easy, as is installing a custom recovery. But yes, if you don't wish to trip knox then there is currently no way to do so.

kenkiller said:
Are you sure you know what you're talking about? All our Tablet S came with Android 4.4.2, and they are rooted just fine.
Click to expand...
Click to collapse
Well, I thought I was sure, wouldn't have said it else. My Tab S did not come with 4.4.2, as it installed some OTA when first connected.
You're being given wrong info. Rooting is easy, as is installing a custom recovery. But yes, if you don't wish to trip knox then there is currently no way to do so.
Click to expand...
Click to collapse
Please share your info on how to root it or install custom recovery. If I was babbling away, being mostly PC/new tab user, please correct my mistakes. No harm intended.
EDIT: Thinking about it. Do you by chance mean flashing the CF Auto t800 image from the development thread? That is not a t805 image so it did not really appeal to me, and it said in the same thread that it is not needed...since you can odin TWRP...which did not work for me. Mean that?

JoeRifle said:
Well, I thought I was sure, wouldn't have said it else. My Tab S did not come with 4.4.2, as it installed some OTA when first connected.
Please share your info on how to root it or install custom recovery. If I was babbling away, being mostly PC/new tab user, please correct my mistakes. No harm intended.
EDIT: Thinking about it. Do you by chance mean flashing the CF Auto t800 image from the development thread? That is not a t805 image so it did not really appeal to me, and it said in the same thread that it is not needed...since you can odin TWRP...which did not work for me. Mean that?
Click to expand...
Click to collapse
Read through the thread again.....many reports from users who got T805 rooted using the T800 cf-auto files without any problems.

kenkiller said:
Read through the thread again.....many reports from users who got T805 rooted using the T800 cf-auto files without any problems.
Click to expand...
Click to collapse
you are right. I did not find the image "elegible" as it was not based of a t805, and I tried the "other", "slicker" method which did not work. The only reason I could see as to why it did no accept the flash, INet research confirmed suspicion too btw, was that 4.4.x has a hash check at boot up. This would make it extremely hard to root/install TWRP by flashing w/out overcoming this check first.
My comments were based on these assumptions. So sry for the confusion @DUHAsianSKILLZ

JoeRifle said:
you are right. I did not find the image "elegible" as it was not based of a t805, and I tried the "other", "slicker" method which did not work. The only reason I could see as to why it did no accept the flash, INet research confirmed suspicion too btw, was that 4.4.x has a hash check at boot up. This would make it extremely hard to root/install TWRP by flashing w/out overcoming this check first.
My comments were based on these assumptions. So sry for the confusion @DUHAsianSKILLZ
Click to expand...
Click to collapse
If 4.4.2 has this so called hash check at boot up, why would it not matter in using cf-root for T800 then using Flashify to install TWRP? Think about it.

@DUHAsianSKILLZ
flashing the CF Auto for the t800 from the dev thread did the trick for me too. Rooted and can't seem to find problems. Knox tripped oc. Check this thread for more info if you like http://forum.xda-developers.com/gal...cf-autoroot-t800-t2802916/page17#post54769521
@kenkiller
I don't know. It should detect changes to system partition...at least.

kenkiller said:
But yes, if you don't wish to trip knox then there is currently no way to do so.
Click to expand...
Click to collapse
Is any way to delete trip knox? How about warranty after tripping knox?

szfagir said:
Is any way to delete trip knox? How about warranty after tripping knox?
Click to expand...
Click to collapse
Worrying about warranty? Don't root.
---------- Post added at 02:55 PM ---------- Previous post was at 02:54 PM ----------
JoeRifle said:
@DUHAsianSKILLZ
flashing the CF Auto for the t800 from the dev thread did the trick for me too. Rooted and can't seem to find problems. Knox tripped oc. Check this thread for more info if you like http://forum.xda-developers.com/gal...cf-autoroot-t800-t2802916/page17#post54769521
@kenkiller
I don't know. It should detect changes to system partition...at least.
Click to expand...
Click to collapse
Don't assume next time.

kenkiller said:
Worrying about warranty? Don't root.
Click to expand...
Click to collapse
Now know that

kenkiller said:
Are you sure you know what you're talking about? All our Tablet S came with Android 4.4.2, and they are rooted just fine.
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
You're being given wrong info. Rooting is easy, as is installing a custom recovery. But yes, if you don't wish to trip knox then there is currently no way to do so.
Click to expand...
Click to collapse
Yeah I thought so to since I saw the thread about rooting the tab s. I'll guess I'll wait till there's a one click app to root like towel root since towel root isn't gonna be updated no more.

DUHAsianSKILLZ said:
Yeah I thought so to since I saw the thread about rooting the tab s. I'll guess I'll wait till there's a one click app to root like towel root since towel root isn't gonna be updated no more.
Click to expand...
Click to collapse
You're gonna be in for a long wait.

kenkiller said:
You're gonna be in for a long wait.
Click to expand...
Click to collapse
Wow this was long ago... I rooted a week later after this thread was made.. . I do not regret tripping Knox. Ive installed many many roms and built one myself. I learned a lot since I got my tab s. Just wanted to say thank you and everyone else for their help I've done so many things and know a whole lot about Android now Currently working on a theme now. I can't believe I was still subscribed to this thread

[Q&A] Root attempt #1, anyone want to try it..

Q&A for Root attempt #1, anyone want to try it..
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Root attempt #1, anyone want to try it... If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

mrnick81 said:
did you fo this? what did it achieve?
Click to expand...
Click to collapse
Will this work for AT&T. I have the 910a and would be willing to give it a try

Drewsdad said:
Will this work for AT&T. I have the 910a and would be willing to give it a try
Click to expand...
Click to collapse
It won't hurt anything to try it. It is an overflow routine that would apply to many devices, so I would say give it a try, the worst thing that could happen is that it just doesn't work.

Trying
Tried the first step and I keep getting cannot start root no such file exists. Am I missing a step?

Tried and no Su binary
Followed commands from the post and this is what I came up with

Drewsdad said:
Followed commands from the post and this is what I came up with
Click to expand...
Click to collapse
O.k., not bad, it looks like the rest, which for me is good, but am still working on it.

Have you looked into CVE-2014-5207? Looks like something that could hold promise from my very limited experience, and should not be patched in our kernel.

i would like to be a testervas well

Maybe something interesting... doesn't appear to get root access, but uid 1000 system access which could be exploited. Just throwing that out there.
packetstormsecurity.com/files/129170/android-escalate.txt

I tried the srs root it said at the end that it was successful yet it wasn't and I don't really know any of details of writing these exploits which achieve root for our devises but I would think that that may be a place to start
Sent from my SM-N910V

i am tired of this..........

It was said on the other thread that you can Odin back to NI1 from the OTA. How do we know this, exactly? (I'm buying the phone in seven days, and if it's updated, that being true would be helpful.)
Edit: If anyone is interested, it was confirmed here: http://forum.xda-developers.com/showthread.php?t=2908919

nh97103 said:
It was said on the other thread that you can Odin back to NI1 from the OTA. How do we know this, exactly? (I'm buying the phone in seven days, and if it's updated, that being true would be helpful.)
Click to expand...
Click to collapse
======
It has been reported ...tried and confirmed in a couple of threads....
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.1.1 trltevzw

this proves nothing
I didn't push anything and i could install them

Dale2x2 said:
I didn't push anything and i could install them
Click to expand...
Click to collapse
You can but you still don't have root. You need to install the binary. Try to run expose. Or even supersu will tell you you don't have root. You can install any apk you want, but if the app wants to read/write to system it can't. SuperSU is just an app to manage what can access administrative privileges. Its not root.
Sent from my bandaid smelling s-pen

I know
My point in that screenshot was to prove that the guy that's our only hope for root today wasn't even close to evidence of root and i installed those apps workout adb or anything

Dale2x2 said:
My point in that screenshot was to prove that the guy that's our only hope for root today wasn't even close to evidence of root and i installed those apps workout adb or anything
Click to expand...
Click to collapse
I got you. Didnt know that's what you were going for
Sent from my bandaid smelling s-pen

This Q&A thread is being closed. The original thread has been moved into General section as it is now more of a discussion thread. Please refer to that Original thread here;
http://forum.xda-developers.com/showthread.php?p=56532390
Edfunkycold
Have a great day! from my LG G3

[Q&A] [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.

[Q&A] [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.
Q&A for [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.5/8.4 ]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.5/8.4 ]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Can this method be used Straight out of the box?
Hey guys, just wanna make sure that this method can be used straight out of the box? only ever rooted LGs so just want to check that I'm doing the right thing here?
Thanks

As long as you have the Samsung usb drivers installed on your pc you're good.

ashyx said:
As long as you have the Samsung usb drivers installed on your pc you're good.
Click to expand...
Click to collapse
Great stuff Thanks, got a bit confused with the CFAutoRoot page saying I needed to unlock the bootloader first, then I stumbled on your Method.
Thanks

AgentCP said:
Great stuff Thanks, got a bit confused with the CFAutoRoot page saying I needed to unlock the bootloader first, then I stumbled on your Method.
Thanks
Click to expand...
Click to collapse
Only Verizon and AT&T models have locked bootloaders. If you don't have one of these you should be fine.

Why root wifi only device?
I have rooted a couple of devices. I get it's purpose of unlocking hotspot, modifying cpu clock, adblocking, etc. I have the Tab S 10.5 and I am trying to find the benefit to rooting this device. Looks simple enough. But What will I gain? I think I have already answered my question though, maybe. I am rooting my note 3 so I can use that for a hotspot for this. But it seems the only real benefit is adblocking? Am I missing something. It has been a while since I have done this so maybe I have...
Anyways, thanks for the input.

Bdozier said:
I have rooted a couple of devices. I get it's purpose of unlocking hotspot, modifying cpu clock, adblocking, etc. I have the Tab S 10.5 and I am trying to find the benefit to rooting this device. Looks simple enough. But What will I gain? I think I have already answered my question though, maybe. I am rooting my note 3 so I can use that for a hotspot for this. But it seems the only real benefit is adblocking? Am manufacturers I missing something. It has been a while since I have done this so maybe I have...
Anyways, thanks for the input.
Click to expand...
Click to collapse
The way to look at is that rooting gives YOU control over your device not the manufacturer. Think of it as like administration rights on a PC.
Would you like it if pc manufacturers told you what you could and couldn't install on your pc?
Rooting allows you to install custom recoveries so you can back up your device, fix problems, try new custom or stock software, install root only apps such as titanium backup. You can modify system files and add back functionality that the manufacturer has decided to remove or disable. Add new functionality, maybe something that is found on another device. Speed up your device by overclocking to make it run smoother.
Change how things look and install apps such as xposed which reveals a ton of hidden features allowing you to customize your device to your liking.
Once you realise what root can do you'll never want a another device that isn't.

Confused
Hi, I have downloaded the file for the T800. However, when I unzip it there are only two files :cache.img & recovery.img. Am I missing something? Please excuse my ignorance, newbie!!

Blythlad said:
Hi, I have downloaded the file for the T800. However, when I unzip it there are only two files :cache.img & recovery.img. Am I missing something? Please excuse my ignorance, newbie!!
Click to expand...
Click to collapse
Yep you certainly are a nooby as you made the rookie mistake of not actually reading the first post.
Go back to the original thread and read the bit under the smiley face.

ashyx said:
Yep you certainly are a nooby as you made the rookie mistake of not actually reading the first post.
Go back to the original thread and read the bit under the smiley face.
Click to expand...
Click to collapse
Sorry, I read that bit,downloaded odin as well, however, I recall reading something somewhere about needing a .tar file? Maybe some full instructions would be nice for us new to rooting a device. Thanks for the reply

Blythlad said:
Sorry, I read that bit,downloaded odin as well, however, I recall reading something somewhere about needing a .tar file? Maybe some full instructions would be nice for us new to rooting a device. Thanks for the reply
Click to expand...
Click to collapse
The tar file is the file you have downloaded.
Just leave it as it is and flash with Odin.
I shouldn't have to provide step by step instructions, this is what XDA search and Google is for. This info is everywhere.
Basically:
Install Samsung usb drivers.
Disable Samsung kies if installed.
Boot your device into download mode - Hold POWER + VOL DOWN + HOME.
Run ODIN , connect USB cable, look for 'added' message.
Load the tar file into the AP slot, click START.
Wait for flash to complete, device will reboot and root.
Enjoy your rooted device with custom recovery.

New build posted: http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488

I tried on my t800 running latest BRI firmware and worked fine. Thanks a lot.

Cannot complete root on T-800 (Lollipop 5.0.2)
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,

chanukya said:
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
Click to expand...
Click to collapse
Have you actually read the original thread? The answer is in that thread.
http://forum.xda-developers.com/showpost.php?p=60324046&postcount=33

Works now!
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.

chanukya said:
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
Click to expand...
Click to collapse
That did it! Thanks bro, made my night!
Sent from my Galaxy S5

chanukya said:
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
Click to expand...
Click to collapse
Did you see the red android after rebooting?
Supersu should have already been installed before booting into twrp.

chanukya said:
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
Click to expand...
Click to collapse
I have an apology to make. Your troubles seemed to have been due to the SuperSu script not running because it had become corrupt. I realised something was wrong when you said you had to install SuperSu with TWRP.
All fixed now.
Sent from my SM-T805 using XDA Free mobile app

No clue... any help?
Sorry for the questions....
I have SM-T805 with 4.4.2 and build KOT49H.T805XXU1ANH1...
1 - Can i root without tripping knox? (i've done it on GS3 and GS4, no issues on knox, counter remains 0x0);
2 - The cf.auto root files are locked at specific builds? Or can i use the sm-t805 on chainfire page?;
3 - Can i update to lollipop or any other official firmware? And without tripping knox?
Thanks, in advance.
---------- Post added at 08:23 PM ---------- Previous post was at 08:18 PM ----------
Sorry for the questions....
I have SM-T805 with 4.4.2 and build KOT49H.T805XXU1ANH1...
1 - Can i root without tripping knox? (i've done it on GS3 and GS4, no issues on knox, counter remains 0x0);
2 - The cf.auto root files are locked at specific builds? Or can i use the sm-t805 on chainfire page?;
3 - Can i update to lollipop or any other official firmware? And without tripping knox?
Thanks, in advance.

Bounty for rooting method for A5 2017 (SM-A520F), bounty insidie.

Hey, so I really want to root my A5 as I have a few issues with it unrooted (mostly with wakelocks) and just generally dislike using it unrooted but as far as I can see there's isn't an option yet.
I'm offering a $50 bounty in BTC to whoever creates the tools and a short guide to root it without tripping Knox.
I know it's not much but others might chip in as well.

There is already root available since yesterday.
Unfortunately only with cwm look at this link.
https://m.youtube.com/watch?v=YtvJU9aDnHM&feature=youtu.be

bassbounce said:
There is already root available since yesterday.
Unfortunately only with cwm look at this link.
https://m.youtube.com/watch?v=YtvJU9aDnHM&feature=youtu.be
Click to expand...
Click to collapse
I see, nice. And do we know who made it?
I'll wait for a few replies if it's really works without tripping Knox though.
I'm out of the loop why people hate CWM.

bathrobehero said:
I see, nice. And do we know who made it?
I'll wait for a few replies if it's really works without tripping Knox though.
I'm out of the loop why people hate CWM.
Click to expand...
Click to collapse
CWM will trip knox for sure. Only way without knox tripped would probably be to get a hold of engineer sboot/boot combination from samsung and be able to root it through ADB.

https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622

I used this method today ive also used in the past the twrp method prefer the cwm one though far less steps found though cwm has a lot more chance of bootlooping but far easier ... so to sum up cwm version easy 2 steps really but very finicky... twrp lot more stable but a little more complicated dmverity etc... will again comment in a couple of days let you know how cwm is going now i have stabilized it....
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622 is thread for twrp method