[Sorted out] I did not root, however my s7 edge does not allow me to use s health claiming root after reinstalat stock via odin. Any solution for that?
Did you trip the Knox counter? If you did, there's no way back
The knox was changed, but I wonder how could that be that it was a stock rom?
Br9 said:
The knox was changed, but I wonder how could that be that it was a stock rom?
Click to expand...
Click to collapse
Did you install TWRP or made any changes in the bootloader.
Once the boot loader has been modified in any way. \it will trip knox.
No. I just reinstalled stock via odin, there was no twrp installation.
Br9 said:
No. I just reinstalled stock via odin, there was no twrp installation.
Click to expand...
Click to collapse
why did you have reinstall stock /
if you have reinstall stock that means something was done to your phone, which caused your phone to think knox is tripped.
So what happened that you ned to reflash your phone ?
System crashes with crashes
Are you the original owner of this phone?
If you try to root it or install anything non-Samsung, it will trip knox and there is no turning back.
Flashing Samsung ROMs via Odin won't trip knox....
I'm his first owner. I saw in a post that it is possible to continue using s health if dowgrade to marshmallow and then upgrade via OTA to 7.0. Do you know if it's possible?
Br9 said:
I'm his first owner. I saw in a post that it is possible to continue using s health if dowgrade to marshmallow and then upgrade via OTA to 7.0. Do you know if it's possible?
Click to expand...
Click to collapse
I think you just have to add or modify a line in system/build.prop and it will work. For that, you have to be rooted.
Take a look here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Sorted out. I was able to reuse the app by going back to 6.0 via odin, configuring the app and upgrading via OTA to 7.0
Related
Hi.
I don't know if someone can help me, but I really don't know what to do with this problem.
I bought one G900M (version from Brazil) on the release date and after a few weeks I install a custom rom and the TWRP recovery.
The problem is: I tried to go back to the stock ROM, but I still have the recovery with the CUSTOM "mark".
I tried to re install many times, do a wipe/format from the recovery, with no success.
I always receive the message when I try update the phone by OTA what say "The operating system on your device has been modified in an unauthorized way. Try downloading...
I appreciate any help.
mrhizzo said:
Hi.
I don't know if someone can help me, but I really don't know what to do with this problem.
I bought one G900M (version from Brazil) on the release date and after a few weeks I install a custom rom and the TWRP recovery.
The problem is: I tried to go back to the stock ROM, but I still have the recovery with the CUSTOM "mark".
I tried to re install many times, do a wipe/format from the recovery, with no success.
I always receive the message when I try update the phone by OTA what say "The operating system on your device has been modified in an unauthorized way. Try downloading...
I appreciate any help.
Click to expand...
Click to collapse
You tripped Knox when you rooted. There's no way to undo this.
dynospectrum said:
You tripped Knox when you rooted. There's no way to undo this.
Click to expand...
Click to collapse
But I'm not talking about Knox. I'm talking about the OTA update.
I reinstall the original firmware, stock version. Should work, no? Or Samsung changed the things again?
Im with a similar problem... root my device now OTA dont work... i think maybe someone has a flashable original firmware and you patch the same way you root your device.... Other option is ODIN restore to default :/ wich nobody want that
Its true
You tripped Knox when you rooted. There's no way to undo this.
If you want to update Just download the stock firmware ( samobile ) and flash with odin
Not true. My knox is still 0x0, I have root, but i have the same message from OTA.
The ART is the problem.
So, a long time ago I towelrooted my gs5 on 4.4.2 and just left it like that (no custom rom , kernel, or bootloader). I recently upgraded to an N6 and would like to sell the old phone now. I'm trying to return to stock, but my craptop died and I'm not able to Odin a stock .tar file. I've already used 'full unroot' in SU, but I'm still showing 'Custom' status. I can't OTA and I can't find a stock rom to flash from the factory recovery, so are there any other options I'm missing?
Thanks in advance!
Just factory reset it from stock recovery
*Detection* said:
Just factory reset it from stock recovery
Click to expand...
Click to collapse
Thanks for the reply. I actually tried factory resetting through the settings menu and the stock recovery. Both leave me with a 'custom' status and unable to OTA.
I'd suggest using ODIN to flash a stock ROM from sammobile dot com, but with it being Verizon, it's likely got a locked bootloader, and I'm not sure if you can flash anything with ODIN when the bootloader is locked, worth a try though, it'll just fail with an AUTH! if it doesn't work
Instructions are under the download on their site
if u rooted and trip your knox into 0*1 your are nvr getting OTA updates for my knowledge
vinura kithmal said:
if u rooted and trip your knox into 0*1 your are nvr getting OTA updates for my knowledge
Click to expand...
Click to collapse
Wrong, I tripped KNOX ages ago and can still receive OTA updates fine if I'm on 100% stock
*Detection* said:
Wrong, I tripped KNOX ages ago and can still receive OTA updates fine if I'm on 100% stock
Click to expand...
Click to collapse
i did not get any
thts why
sorry
Plz Help to Root Samsung Galaxy S5 SM-G900F stock Marshmallow 6.0.1
I'm interested too. If it was also knox 0x0 would be perfect.....
@yassinmixpro, did you try @Azar_98's suggestion? If yes, does it work well? Thanks.
It works very well ever since.
tapatalked
Is it possible to install supersu with flashfire while keeping knox 0x0?
IceBlizzard said:
Is it possible to install supersu with flashfire while keeping knox 0x0?
Click to expand...
Click to collapse
flashfire needs root, how do you want to grant flashfire root access if you don't have root?
Tkkg1994 said:
flashfire needs root, how do you want to grant flashfire root access if you don't have root?
Click to expand...
Click to collapse
Flash alexandr 4.4 old version, root it, use flashfire to install 6.0 and keep root? It worked for me before 4.4 to 5.0 0x0 knox and xposed and root etc
IceBlizzard said:
Flash alexandr 4.4 old version, root it, use flashfire to install 6.0 and keep root? It worked for me before 4.4 to 5.0 0x0 knox and xposed and root etc
Click to expand...
Click to collapse
M is different, requires a modified bootloader.
Sent from my SAMSUNG-SM-G900A using Tapatalk
I had root on my g900f on 5 but flashed 6 and lost root - if i flash twrp and superuser files from above will i b atight ? Thanks in advance
NexusCrazy said:
I had root on my g900f on 5 but flashed 6 and lost root - if i flash twrp and superuser files from above will i b atight ? Thanks in advance
Click to expand...
Click to collapse
Just flash this trough odin. https://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Wipe the ****ing cache before asking questions!
---------- Post added at 09:42 AM ---------- Previous post was at 09:41 AM ----------
yassinmixpro said:
Plz Help to Root Samsung Galaxy S5 SM-G900F stock Marshmallow 6.0.1
Click to expand...
Click to collapse
https://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Flash this trough odin. Add it to AP then while phone is is download mode plug it to pc and hit start
Wipe the ****ing cache before asking questions!
Hi i want to root Stock 6.0.1 mm and keep stock recovery. So do we have to flash TWRP in order to root stock 6.0.1 mm? Or just flashing the cf-root file via odin alone will give root access? Thanks
Sent from my GT-I9100 using xda premium
CF-root via odin will root your device and you'll keep stock recovery.
I wonder what's the point of keeping stock recovery by the way
vorta251 said:
CF-root via odin will root your device and you'll keep stock recovery.
I wonder what's the point of keeping stock recovery by the way
Click to expand...
Click to collapse
Thanks, i tend to use stock samsung rom always, but just like root to remove crap, titanium backup and some apps that require root permissions. Btw what options on odin do we tick when flashing the cf-root file?
Sent from my GT-I9100 using xda premium
Hmm, I guess if you never need to flash anything then keeping the original could be OK.
I'd say trwp is still useful to perform backup (entire rom at a time).
Well normally, you don't need to tick any options (the useful ones are ticked already).
So, only auto reboot and F.Reset time should be ticked.
vorta251 said:
Hmm, I guess if you never need to flash anything then keeping the original could be OK.
I'd say trwp is still useful to perform backup (entire rom at a time).
Well normally, you don't need to tick any options (the useful ones are ticked already).
So, only auto reboot and F.Reset time should be ticked.
Click to expand...
Click to collapse
When i had the S4 a few years ago, i had clockworkmod recovery which was great and i was familiar with, but was not ever a fan of twrp even then, so decided to stay stock with the s5 but thanks for the help mate.
Sent from my GT-I9100 using xda premium
vorta251 said:
Hmm, I guess if you never need to flash anything then keeping the original could be OK.
I'd say trwp is still useful to perform backup (entire rom at a time).
Well normally, you don't need to tick any options (the useful ones are ticked already).
So, only auto reboot and F.Reset time should be ticked.
Click to expand...
Click to collapse
Hi mate, just rooted my s5 via odin and cf-root file. However every time I reboot the phone, i get a "Set warranty bit" message in yellow at the top of the screen, I did do a wipe cache after I rooted. How do i remove that message? thanks
To my knowledge, you can't get rid of this message which was tripped by the rooting process.
But it doesn't make any difference anyway so you might as well leave it!
Then, you can run the root to the Galaxy S5 SM-G900F Android 6.0.1 and Kernel of May 31, 2016 without triggering this blessed knox 0x1?
I still have not figured out if it is feasible, and if you can do as you progress? Towelroot works?
ExileTM said:
[...]Towelroot works?
Click to expand...
Click to collapse
It doesn't. I installed all these automatic upgrades and tried to use towelroot, but it said, that the device isn't supported. :crying: :crying: :crying:
do i need to unlock the boooader before or after
do i need to unlock the boooader before or after?
or not at all?
obviously the first file that i need to flash (twrp) is the custom recovery.
do i unlock the bootloader before this?
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)...
so a family member asked me to downgrade his samsung galaxy s5 from android 6.0.1 to the previous version.
i've googled it a bit but only found ways where you either lose your data or need root and he won't let me root his phone.
is it still possible and could someone either explain or link me how to do this?
thnx
Backup photos and videos then downgrade via odin but i am not sure if knox will trip and make wipe to dont get bootloop
Backup using Smart Switch
Downgrade by flashing the ROM you want over the top with ODIN
Got a feeling you'll get a load of FCs / errors on boot with MM apps trying to run on LP, if yes, factory reset from recovery and restore with smart switch
It's won't trip KNOX, that's only tripped by flashing custom
*Detection* said:
Backup using Smart Switch
Downgrade by flashing the ROM you want over the top with ODIN
Got a feeling you'll get a load of FCs / errors on boot with MM apps trying to run on LP, if yes, factory reset from recovery and restore with smart switch
It's won't trip KNOX, that's only tripped by flashing custom
Click to expand...
Click to collapse
kool, i just got access to his phone and he told me he doesn't care about his warranty so i've just rooted it for him. is there a better way to do this and keep all data now that its rooted?
and are you sure this will save my app data too?
*Detection* said:
Backup using Smart Switch
Downgrade by flashing the ROM you want over the top with ODIN
Got a feeling you'll get a load of FCs / errors on boot with MM apps trying to run on LP, if yes, factory reset from recovery and restore with smart switch
It's won't trip KNOX, that's only tripped by flashing custom
Click to expand...
Click to collapse
Hi there! I just this post of your's that perfectly fits for my objective.
Is it really possible to downgrade From official stock Marshmallow 6.0.1 to official stock kitkat 4.4.2 without tripping knox? Also does the bootloader will allow you to downgrade?
Just saw this forum and he said that secure bootloader will block any downgrade
"If on Marshmallow 6.0.1 you will probably not be able to downgrade.
Odin will fail at s.boot - the secure bootloader that will block the downgrade."
Source of quote from greenman's post:
http://www.sammobile.com/forum/showthread.php?t=24635&page=2