Hi to everyone, I have a galaxy A5(2016) A510F and I want to root it but this will trip knox so I want to ask if we root a stock rom and flash it via odin does this detect root and trip knox ? (we will modify the system.img that we find in.tar file)
It probably won't trigger KNOX, but root access would be unstable, at best. Try using KingRoot instead - if it works on your device, it will root it and keep the KNOX counter the same, and if it doesn't, it'll just tell you that it can't root your phone.
I don't want try it because my phone it's new so can someone try it and post the result ? Maybe someone that have already trigger knox, this don't want to be a problem for him/her
EDIT: I think Kingroot don't work http://forum.xda-developers.com/sam...ment/galaxy-a5-2016-success-kingroot-t3400564
Up
I tried king root, but after reebooting my phone was unrooted. I suggest you to flash cf autoroot because, yes, it trips knox counter, but If u soft-brick your device in any way, you can always solve it using odin and flashing stock firmware/PIT...
They are two different things, maybe you are confused because it doesn't mean that if you flash cf autoroot and soft-brick your devices you can unbrick it just flashing stock rom, yes this is true but you can unbrick you phone in anytime without having cf autoroot!
I didn't mean that, i know odin doesn't request root permission, I said that if he flashes cf autoroot and he soft-bricks his device ( I know it's almost impossible ) he will resolve the problem by flashing stock formware (or a custom ROM after wiped cache, dalvik, data and system)
Unfortunately not possible to pre-root a stock Samsung 5.1.1 or 6.0 rom and preserve knox. It will boot loop your device. Selinux will block root and prevent the device from booting unless the boot.img is patched to remove the selinux root restriction.
However patching the boot.img trips knox, catch 22 situation.
Keep hoping for kingroot or Kingoroot if you want to preserve the knox counter.
Thanks for the reply
Can anyone try this http://www.samsungsfour.com/tutorials/how-to-root-all-samsung-galaxy-smartphones-without-pc.html ? I don't want to trip my knox!
If it works it wont trip knox as it doesn't touch the binaries.
Unfortunatelly, I can't try because i've already tripped the knox
Related
Hi, i have note 3 sm n9005 or something and rooted my phone for some stupid reason, its still on stock the only thing that i think happened was i have supersu, i paniced and factory reset, now supersu has a error thing with something to do with binary settings or something. All i want to do it fully reset my phone, if its any help im british with EE... does flashing supersu trip knox counter? Am i actually rooted for if i were to flash stock? Will that trip it? Iv knly had phone few months and im scared... if i flash stock can i then update legally coz i cant update because the device is modified? I used odin... can someone help please, i know nothing and yes, i should look into what im doing more before hand. Can you explain everything and what to do please? Every little thing, please and without tripping knox and as if it was out the box new. Please
Firstly, flashing SuperSU trips KNOX. In the first place, to install SuperSU you need a custom recovery which would ALSO trip KNOX. Flashing back to stock unroots your phone too.
If you are convinced that you have not tripped KNOX, just re flash your phone back to stock with ODIN.
This_Guyse said:
Firstly, flashing SuperSU trips KNOX. In the first place, to install SuperSU you need a custom recovery which would ALSO trip KNOX. Flashing back to stock unroots your phone too.
If you are convinced that you have not tripped KNOX, just re flash your phone back to stock with ODIN.
Click to expand...
Click to collapse
I dont have a clue what i first did but what i did magically apeared with supersu. Can i flash stock which will get rid of supersu and can i reset my knox counter? And am i actually rooted seen as i factory reset?
MarkDyer1 said:
I dont have a clue what i first did but what i did magically apeared with supersu. Can i flash stock which will get rid of supersu and can i reset my knox counter? And am i actually rooted seen as i factory reset?
Click to expand...
Click to collapse
Flashing stock will get rid of SuperSU and root but you cannot reset KNOX. It is permanently 0x1 and will always be.
This_Guyse said:
Flashing stock will get rid of SuperSU and root but you cannot reset KNOX. It is permanently 0x1 and will always be.
Click to expand...
Click to collapse
What about the fact i factory reset? Is it still rooted to flash stock? And doesnt it have to be a unrooted stocked rather than flashing rooted stock? And where do i got stock and do i need to unzip files and stuff?
MarkDyer1 said:
Hi, i have note 3 sm n9005 or something and rooted my phone for some stupid reason, its still on stock the only thing that i think happened was i have supersu, i paniced and factory reset, now supersu has a error thing with something to do with binary settings or something. All i want to do it fully reset my phone, if its any help im british with EE... does flashing supersu trip knox counter? Am i actually rooted for if i were to flash stock? Will that trip it? Iv knly had phone few months and im scared... if i flash stock can i then update legally coz i cant update because the device is modified? I used odin... can someone help please, i know nothing and yes, i should look into what im doing more before hand. Can you explain everything and what to do please? Every little thing, please and without tripping knox and as if it was out the box new. Please
Click to expand...
Click to collapse
Reboot in download mode I. E. Volume down+home+power, check the knox counter if it's 0x1 then it has already been tripped and you have been set free ?? and if it's 0x0 you are still locked in a cage.
Report back with what you see.
saadramiz said:
Reboot in download mode I. E. Volume down+home+power, check the knox counter if it's 0x1 then it has already been tripped and you have been set free ?? and if it's 0x0 you are still locked in a cage.
Report back with what you see.
Click to expand...
Click to collapse
I know i have done something coz when i want to update it says this device has been modified. But i havent flashed any roms so surely knox should be 0x0 and flashing stock keeps it 0x0 doesnt it?
MarkDyer1 said:
I know i have done something coz when i want to update it says this device has been modified. But i havent flashed any roms so surely knox should be 0x0 and flashing stock keeps it 0x0 doesnt it?
Click to expand...
Click to collapse
Yes, if your Knox is still 0x0, flashing stock keeps it 0x0.
Use Phone INFO ★Samsung★ app to check for the Knox Warranty Void status (in the GENERAL INFO section).
Hello,
I'm using a SGS4 rooted since more than one year and a half (odin, flash a small root bin file if I remember well, flash counter set to 1, no custom recovery and no nandroid backup)
Since I want to implement NFC card emulation now avaliable in android 4.4 in one of my apps, I'd like to update.
I've seen few threads on the subject, and most of them date from a long time (am I late ? ). I'd like to know how I could update normally my actual rom (provided by Orange, precisely I9505XXUAME2), or move to another slightly modified rom like the base rom provided by samsung without all these apps that you can only remove with root.
I don't want to have any data issue I've read about, I don't want to lose my actual apps and their data. (Nandroid backup then restoring apps and their data through nandroid manager?)
Also, if possible i'd like to update without losing my start screen, my parameters, etc... (in the worst case I'd re-set them manually). And finally of course I want to have it rooted at the end of the process.
In fact I want it to be just like if I had done an OTA update, then rooted it.
Also, How to update without setting the Knox counter to 1 ? (My flash counter is set to 1, should I use Triangle Away?)
Is there any simpler way than flashing the new firmware and then importing everything from my old data to the new and reinstalling the changes I made to the system (like avast & such) ?
Also, maybe there exists newest versions of the firmware, but without the new bootloader that has the knox counter ?
Thanks in advance!
tboss1995 said:
Thanks in advance!
Click to expand...
Click to collapse
1. You can't receive OTA updates if you have rooted your device. You have to flash the firmwares via ODIN.
2. You don't need wipe nothing if you flash new stock firmware. Instructions: Flash new firmware (if you don't have wifi flash it one time more), root it again then and you're done. Your data don't have to be affected (maybe you only have to reinstall some app if the data/cache was moved to the SDCARD).
3. Flashing one new stock firmware don't modify KNOX. You actived KNOX rooting your device or flashing one custom recovery. Knox: 0x1 can't be reset. Triangle away only reset the flash counter.
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
tboss1995 said:
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
Click to expand...
Click to collapse
1. Updating via ODIN or Kies don't set the KNOX counter. Downgrading YES.
2. Root dissapear if you flash new update via ODIN.
3. You can flash latest firmware and root them without KNOX. Take a look for the method: HERE.
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
tboss1995 said:
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
Click to expand...
Click to collapse
1. Take a look: HERE.
2. Nobody know it.
3. - KNOX free: This therm is used for the custom ROMS normally. This mean that flashing this ROM dont touch the KNOX counter.
- KNOX counter: You still having your device in warranty if you have KNOX:0x0. You void your warranty if you have KNOX:0x1 in DOWNLOAD MODE.
So it means I'll still have the new bootloader ?
For those who may come to read this article and don't want to watch a video, I've found an article explaining what kernels are. http://m.androidcentral.com/android-z-what-kernel
Hi, I accidently rooted and installed cwm on my galaxy s4 gt i9-505, without disabling knox, and now I want to go back to the orginal samsung bootloader, (I don't not want to know how to get the stock firmware), I want to unroot and restore the bootloader, really need help asap, would be apperiated thanks.
Update: I'm on Android L 5.0.1, and installed cwm before rooting which was a silly mistake, because knox then countered that, and it's conflicting root problems when I tryed to root afterwards, but now I just want to go back to the Samsung bootloader, root issue fix but still don't know how to fix bootloader.
Not sure what is there to fix - if phone boots correctly it is good.
If you try to revert back to knox 0x0 I'm afraid it is not possible.
Flashing root and cwm doesn't replace your bootloader
How do you accidentally flash root and a customised recovery?
Imtigerclaw said:
Update: I'm on Android L 5.0.1, and installed cwm before rooting which was a silly mistake, because knox then countered that, and it's conflicting root problems when I tryed to root afterwards, but now I just want to go back to the Samsung bootloader, root issue fix but still don't know how to fix bootloader.
Click to expand...
Click to collapse
You are really mixing things up.
A custom recovery has nothing to do with Knox. A custom recovery gives no problems with Knox. It's impossible.
You are on the samsung bootloader. You cannot change it to a custom (there isn't even any).
If you want root just flash cf auto root and then delete knox. That's all.
Hi
I have a new Samsung S4 (i9505) (yep - new with waranty, apparently). The phone came with Lollipop but I downgraded to Kitkat (4.4.2) to root without tripping Knox.
I have successfully rooted (after several soft bricks) and my Knox counter remains at 0x0 - but I cannot boot to recovery (the phone says "recovery booting..." in blue small text at the top but then goes to a normal boot with boot loop). I can boot in to the normal mode, and can boot to safe mode, and can boot to download mode - but not to recovery. And cannot factory reset the phone (from settings - the procedure just leaves the phone as it is). I have tried (successfully) to flash the Lollipop bootloader, and have tried (unsuccessfully) to flash the image file extracted from the stock lollipop ROM (extracted recovery.img, used 7zip to create a tar file, and tried flashing as AP with Odin 3.09 but it fails to write the file)... I also tried the OTA update back to Lollipop (using the settings, update option on the phone) but that too failed.
The phone seems to work but I just cannot get in to recovery mode (and cannot factory reset the phone). I am using the original usb cable and a usb port directly connected to the mother board (and have successfully flashed other components). Any suggestions as to how to re-enable or restore the recovery (without tripping Knox warranty counter)?
Many thanks for any help
Flash the whole firmware with Odin.
Custom recovery is a no-go as it will trip Knox.
GDReaper said:
Flash the whole firmware with Odin.
Custom recovery is a no-go as it will trip Knox.
Click to expand...
Click to collapse
Thanks for that.
I was leaving a complete reflash to Lollipop (with Odin) as a last resort - as this would cause me to lose root. However, yesterday I chose the backup function on FlashFire to backup (to the external SD card) the phone with Kitkat and root and... following the backup, all apps (system and user) fail on boot so I have no option but to reflash anyway (worked without issue). Not sure what happened with FireFlash - all I did was to select backup - but is must have affected the phone in some way... I guess it is incompatible with the S4 or Kitkat (or both).
I am still confused: what will have prevented the phone from booting to recovery with the Kitkat image (and prevented me from reflashing the stock Lollipop recovery via Odin)? And what is the issue with FireFlash (I can not understand why taking a backup should cause a problem when rebooting the phone).
I will start again trying to gain root without tripping Knox (downgrading to Kitkat, using TR to root, then, hopefully, upgrading via Mobile Odin with everroot)...
Thanks again for your help.
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
GDReaper said:
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
Click to expand...
Click to collapse
Thanks again for your response. When I tried removing Knox with the Knox removal script in Mobile Odin having downgraded my device to Kitkat, I got a soft brick which did take a while to fix (but did get fixed eventually). I had thought of perhaps trying to upgrade from rooted Kitkat to Lollipop using FireFlash but was a bit disconcerted at the way it crashed my device when I only tried backing up the phone (and not flashing anything at all) using it.
Do you know whether the issue I had with FireFlash is indicative of FireFlash being incompatible with my device or is the symptom I had just something that may randomly occur (ie is there any point trying to use FireFlash upgrade from rooted but not Knoz tripped 4.4.2 to rooted and not Knox tripped 5.01)?
Many thanks for all your help and best wishes, Boris.
bprtzel said:
Thanks again for your response. When I tried removing Knox with the Knox removal script in Mobile Odin having downgraded my device to Kitkat, I got a soft brick which did take a while to fix (but did get fixed eventually). I had thought of perhaps trying to upgrade from rooted Kitkat to Lollipop using FireFlash but was a bit disconcerted at the way it crashed my device when I only tried backing up the phone (and not flashing anything at all) using it.
Do you know whether the issue I had with FireFlash is indicative of FireFlash being incompatible with my device or is the symptom I had just something that may randomly occur (ie is there any point trying to use FireFlash upgrade from rooted but not Knoz tripped 4.4.2 to rooted and not Knox tripped 5.01)?
Many thanks for all your help and best wishes, Boris.
Click to expand...
Click to collapse
Sorry - FlashFire not FireFlash!
Mobile Odin and bricked phone?
GDReaper said:
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
Click to expand...
Click to collapse
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
bprtzel said:
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
Click to expand...
Click to collapse
I tried to update my modem and bootloader with it. I also was on a custom ROM.
bprtzel said:
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
Click to expand...
Click to collapse
Just to say I finally got my phone to Lollipop (5.01) rooted with Knox guarantee void remaining at 0x0.
I downgraded (again) to 4.4.2 with Odin, installed the GF1 kernel, used towel root (my wifi was still working though it would not remember the wifi passwords), the used FireFlash to upgrade back to stock 5.01 plus SU beta.zip as OTA/ZIP. All worked great - except I now cannot get the wifi to switch on. Used Odin to load the Lollipop BL and also Lollipop kernel, and did a factory reset for good measure too but still no wifi... (can't switch the switch to on). Guess I will try the GSM modem to just to see if that helps (unless anyone has other suggestions)...
Morning everyone,
I have searched and searched, is it possible to root these A3's as yet?
I bought this s a replacement for my son as he broke his s5 mini sitting on it lol.
Best wishes
If tripping KNOX is not a worry, you can flash TWRP, and flash the SuperSU package. (Optionally, you can flash back the stock recovery, and retain the root.)
There is no solution without tripping KNOX yet, CF-AutoRoot has not been updated for A300FU Marshmallow yet.
PlutoDelic said:
If tripping KNOX is not a worry, you can flash TWRP, and flash the SuperSU package. (Optionally, you can flash back the stock recovery, and retain the root.)
There is no solution without tripping KNOX yet, CF-AutoRoot has not been updated for A300FU Marshmallow yet.
Click to expand...
Click to collapse
Hi,
I tried downgrading to lollipop without success, as it would stay on samsung logo.
So i had to use smart switch to re-install marshmellow.
Tripping knox is no issue, Therefore as supersu not been updated it would leave me with only option to go back to lollipop?
If so, is there a tut i could follow as doing usal way with odin etc did simply not work.
The A3 is on 02 network
Best wishes
Go for the 4 file package then, it is the only thing that keeps saving peoples phones around here.
Use SamFirm for to download them (make sure you tick binary update)