Develop Bugs

[Q] knox and rooting questions

Hey everyone. Im relatively new to this forum and rooting. I have some background knowledge in programming and other related aspects, unfortunately nothing related to Android. As well as some Linux OS experience. Now as far as i know ROM's could be compared to OS builds. Android 4.1.2, 4.3, 4.4, etc. Rooting makes you a super user/sudo like Linux. I think i have that pretty much correct. Now for the things i know little about.
-KNOX so far it seems its mostly used for enterprises and to see if we have installed a custom ROM. I've seen a lot of different information about Knox. What exactly else does it do/change? As of 4.3 i see we could no longer roll back or we will brick our device. What should i be wary of? I could care less about tripping the knox counter.
-Stock OTA is another thing i was curious about. This simply means an update was installed post factory by user, correct? My girlfriend has an S3 and i cant remember if 4.3 was stock or 4.1.2. I just wanted to clear up if my OTA updated S3 was covered under this.
-i saw one root method which kept the stock recovery but installed the superuser. What is the benefit for having a stock recovery? Would i be able to use a custom one with Knox in place? I was thinking of using a 4.4 cyanogenmod rom.
Sorry if this seems a bit noobish, but my schedule is tight and i spent maybe 6 hours trying to find exact information. Kind of hidden lol.
I appreciate any answers!
Sent from my SPH-L710 using xda app-developers app

All your questions are probably answered here-http://forum.xda-developers.com/showthread.php?t=2541343- read the whole thing and let us know if you have anymore questions
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

And to answer some if them.
There is no advantage to stock recovery, you can't do anything with it.
Yes you can do anything the same with Knox but installing a custom recovery triggers the warranty bit in Knox. If you bring in your phone to be repaired or something, if they put the phone in Download Mode they could tell whether you installed a custom recovery because Warranty Bit would say 1 instead of zero. There's also no way to reset the flash counter with Knox.
And the biggest thing, if you have Knox do not try to downgrade the firmware. Aka don't try to Odin anything other than 4.3+. It will brick your device.
Other than those things it won't effect you at all.
And yes an OTA is Over The Air update. When the device scans for firmware updates and it find one it automatically downloads it and persistently bugs you about it until your firmware is the most current version. Done by the user or sometimes the techs at phone stores like to do it without asking you.

So to clarify (at work, ill read your link, appeciate it) Knox wont affect anything BUT the counter and downgrading? So i could root the old way with odin and cwm for 4.1.2 without problems?
Stock recovery is just worse in general or similar? Lastly "stock" ota is what i meant lol. I guess that means a non-custom ROM from your carrier?
I personally dont care for my warranty, i have a few months left in my contract and could upgrade now to a new phone if i wanted.
Thanks. I hate to sound like i did no research, i appreciate the link.
Sent from my SPH-L710 using xda app-developers app

Can I disable Tell HTC completely

I had a n Orange locked device and have since supercided, s-offed and now running latest stock WW Rom. However, I get the below and wondering if there's anyway to disable the reporting whilst staying otherwise stock or stock and rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One_M8 using Tapatalk

stuart0001 said:
I had a n Orange locked device and have since supercided, s-offed and now running latest stock WW Rom. However, I get the below and wondering if there's anyway to disable the reporting whilst staying otherwise stock or stock and rooted.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I am having the same issue, the best I could do is freeze udove which is apparently the app that does the reporting. When I did this I could no longer open the Tell HTC section in settings so I am assuming it freezes the reporting.

Alaris said:
I am having the same issue, the best I could do is freeze udove which is apparently the app that does the reporting. When I did this I could no longer open the Tell HTC section in settings so I am assuming it freezes the reporting.
Click to expand...
Click to collapse
Thanks for that. After a quick search it seems mybreeze.apk is also a potential culprit so I've frozen that too. :good:

Just remember to back up udove and don't get rid of it as you will need it in place for OTA

Is it actually reporting or is that message just the result of an unlocked boot loader? I haven't seen any activity from any of those apps.

ashyx said:
Is it actually reporting or is that message just the result of an unlocked boot loader? I haven't seen any activity from any of those apps.
Click to expand...
Click to collapse
As your phone is S-OFF it's technically deemed a test device, hence the warning being permanent. It does nothing to the use of the phone so just ignore it

EddyOS said:
As your phone is S-OFF it's technically deemed a test device, hence the warning being permanent. It does nothing to the use of the phone so just ignore it
Click to expand...
Click to collapse
It wouldn't bother people if it were just device related. If you read the statement, it clearly states that it will collect "personally identifiable information such as your name, phone number, precise location..." you get the point. WTF do they need all of this for just for turning off the security of these devices? That's ridiculous and a great infringement to our human rights and privacy and nobody says a thing about it. They don't need our personal information, just device info, so why would they need to know who **** Murcy or Horace P. is? Secondly, why is S-Off a nice automatic way of considering the device a "test device" if its not like we're probing the thing or anything, just flashing roms and enabling features that can be pulled off on any other non HTC device once the boot loader is unlocked. Who gives a company born in the late 90s so much rights over the privacy of their users?
Anyways, can anyone give me a thorough way of disabling this? I'm not scared of a bootloop or failure of the alarm app, I just feel that if they have such right, we have a right to get rid of it.

Stock Rom Stripped of Bloatware from Samsung Repair Center

I recently got my S6 back from Samsung. They untripped knox, and installed a very slim rom without any of the sprint bloatware, and no sprint splash screen. Is there some way I can back up this rom to be able to flash it in odin if/when I need to?
Thanks!

TWRP
bert1983 said:
I recently got my S6 back from Samsung. They untripped knox, and installed a very slim rom without any of the sprint bloatware, and no sprint splash screen. Is there some way I can back up this rom to be able to flash it in odin if/when I need to?
Thanks!
Click to expand...
Click to collapse
You can back up everything if you flash TWRP recovery and select the backup option it comes in hand but other than that i dont believe you can do it without tripping Knox again

Thanks for the reply, that's unfortunate news. I really don't feel like tripping Knox since I would like samsung pay to continue working.

bert1983 said:
Thanks for the reply, that's unfortunate news. I really don't feel like tripping Knox since I would like samsung pay to continue working.
Click to expand...
Click to collapse
You can try ADB Backup. A good set of instructions can be found at:
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
No guarantee that this will work, but it should not trip Knox.

Please post a system dump of this b3fore you do anything. PLEASE
Sent from my SM-G925P using Tapatalk

Is it oi1 build ? Ive sent plenty phones back for warranty and samsung never did that before . Trip knox , so what? Samsung warrantys phones like that all the time . Just tell them you took it to the samsung experience shop at "BestBuy" and they tried to flash the operating system to get the phone working properly again. Id tell them it kept rebooting after you updated it through wifi to 5.1.1 . Youll never have an issue with them if you explain it to them that way . Give us a new build lol

bert1983 said:
They untripped knox....
Click to expand...
Click to collapse
That's the real goal there....

OK I'll work on it this week. I don't want to not be able to use the Samsung pay feature though

I am curious if its the same build number as mine, I have this screenshot so tell me is yours the same or different? Mine is Stock Sprint
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MindTrix said:
I am curious if its the same build number as mine, I have this screenshot so tell me is yours the same or different? Mine is Stock Sprint
Click to expand...
Click to collapse
That's the same build I have after updating my device. Have you had any luck rooting yours yet?
Sent from my SM-G920P using Tapatalk

gimmeitorilltell said:
That's the same build I have after updating my device. Have you had any luck rooting yours yet?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
I have yet to Root the phone, been waiting and think I will try soon, as I might not need Samsung Pay, been playing with Google 's " Android Pay " not sure what if I will even use these services, I might just root now... LOL

Return to stock issue - "bootloader is already unlocked"

Hi Everyone,
I'm trying to re-lock my bootloader but the OEM Unlock toggle is stuck to the left position whilst displaying the message "Bootloader is already unlocked".
If I try to switch the toggle to the right position, the device will factory reset and then when it powers back up, the toggle is in the left position again.
Is this a result of knox being tripped?
In DL mode it displays both FRP and OEM lock as OFF.
Thanks for the help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Just ignore it, it causes no problems and others have had the same problem since unlocking theirs

*Detection* said:
Just ignore it, it causes no problems and others have had the same problem since unlocking theirs
Click to expand...
Click to collapse
Yeah I know that it's not technically an issue but I want to sell the phone and would like to lock the bootloader before doing so.
Is there no way to re-lock it?
If not... would it stop the phone from passing safetynet/google pay checks?
Thanks
EDIT: I've just tested and google pay won't work on it in this state.

You tripped KNOX, many things won't work on it again anyway

*Detection* said:
You tripped KNOX, many things won't work on it again anyway
Click to expand...
Click to collapse
I'm quite aware of that. What i'm specifically trying to ascertaine is whether or not the bootloader is re-lockable.
If need be I'll just install magisk on stock and put the info in the eBay listing.
Thanks for the assistance anways!

As I said, other members have already posted about the same problem, I have not seen a solution yet, although you could read through a few of those threads and see if they were updated

Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!

Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?

MadSilence said:
Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!
Click to expand...
Click to collapse
why in gods green earth would you actually WANT Citrix? Kidding, i use it 40 hours a week and its abysmal, as if you didnt already know that.
naztam said:
Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?
Click to expand...
Click to collapse
So, the bootloader is unlocked, have you guys tried flashing the Odin files with a newer revision of the bootloader?

Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.

naztam said:
Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.
Click to expand...
Click to collapse
what firmware version are you on currently? if your bootloader is revision 5, flash a rev 6 and see what happens

I am in the last firmware
I have the rev6, I can only flash the firmware of July and August

naztam said:
I am in the last firmware
I have the rev6, I can only flash the firmware of July and August
Click to expand...
Click to collapse
[email protected] then. maybe a ver 7 will release soon?

Unrooting Samsung Galaxy A5

Good Morning,
I have searched for this thread but could not find one that answers my question which is:
Is it possible to unroot my phone and go back to stock android?
The reason being is that I would like to get the phone repaired under warranty which it is still covered by.
I would be grateful for any help. If you need anymore information about the phone the please let me know.
The phone was rooted when I bought it. SM-A520F.
I'm UK based if this helps towards getting the right fw.
Thanks
EDIT: - I have magisk v18.0 installed and also TWRP 3.0.2-0 if that helps.

Just flash official rom

qseyqd said:
Just flash official rom
Click to expand...
Click to collapse
Thanks for the response.
I'll try that. But I think Knox may have been tripped but I can't clarify.
When I boot in Odin Mode I can see on the screen it says:
warranty void: 1 (0x020c)
However when checking with an app it states the phone warranty is still valid. See images.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you have root then you have KNOX 1: 0

arex76 said:
If you have root then you have KNOX 1: 0
Click to expand...
Click to collapse
I know that's why I needed clarity over whether Knox has been tripped.
In Odin mode it says warranty void: 1 (0x020c) but the images show that Knox hasn't been tripped.
Which is correct?

thebestrc said:
I know that's why I needed clarity over whether Knox has been tripped.
In Odin mode it says warranty void: 1 (0x020c) but the images show that Knox hasn't been tripped.
Which is correct?
Click to expand...
Click to collapse
Once tripped Knox has been forever tripped.
I have not heard that KNOX can be reset.

What are the cons of the galaxy root A5 2017
In addition to the loss of the guarantee, what else is lost?

arex76 said:
What are the cons of the galaxy root A5 2017
In addition to the loss of the guarantee, what else is lost?
Click to expand...
Click to collapse
Nothing apart from data when you first flash the the new rom.
Aside from that you might brick your phone if you don't install the rom correctly.

thebestrc said:
Nothing apart from data when you first flash the the new rom.
Aside from that you might brick your phone if you don't install the rom correctly.
Click to expand...
Click to collapse
When I have root all apk from samsung work properly?
---------- Post added at 07:31 AM ---------- Previous post was at 06:53 AM ----------
KingRoot supports A5 2017 with Oreo ?

arex76 said:
When I have root all apk from samsung work properly?
---------- Post added at 07:31 AM ---------- Previous post was at 06:53 AM ----------
KingRoot supports A5 2017 with Oreo ?
Click to expand...
Click to collapse
Samsung health and s pay won't work. S health is pretty easy to get working though. S pay requires a kernel designed to make it work on root.
Kingroot or any other one click root won't work.