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
Related
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.
Hey there, I'm an idiot... I tripped KNOX and now phone is stuck on Tmobile boot screen. With so many different ways to do things and so many variants of this frickin phone and Android it seems the rules are every changing.
So my questions:
1.) How can I get this thing back to working? Can I flash a factory image with ODIN? If so which factory image do I use and what version of ODIN and what boxes need to be ticked in ODIN?
2.) Will #1 reset KNOX? Can KNOX be reset?
3.) Whats the best method to get the thing rooted so I can put a ROM on it. I hate TouchWiz. I tried using this method but it landed me here... http://www.androidrootz.com/2014/04/how-to-root-galaxy-s5-recovery-root.html
Thanks in advance....
Can I just flash the corresponding firmware with ODIN? Is it that simple? Does the firmware version displayed in factory recovery always correspond to the firmware to flash with ODIN? Any insights would help!!!! Thanks for your time!
sammobile dot com, grab a stock ROM for your model S5 (G900T), flash with ODIN
KNOX is permanently tripped now, no way to reset
your knox is permanently tripped, so might as well do what you want with the phone.
if you can get into download mode, you should be able to flash a recovery through ODIN, and then flash the rom of your choice. if that doesn't work, follow Detection's post above and flash a factory Tmobile rom through ODIN and start again.
That's all great thanks all, but does the firmware have to match the version that corresponds to the recovery that is currently on it? For instance, if I flashed 5.1.1 me thinks I wouldn't be able to root it or downgrade it thereafter, correct?
[bor]Its the loosey goosey instructions for multiple methods of doing the same thing for various android versions that make this sketchy. I found it easier to flash my HTC magic with jesus freak and a gold card than it is to flash this thing...or maybe my brain is decaying. Anyway, not what I expected for a common android phone. [/eor]
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)...
[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