Database Users

[Q] Rooted S4 GT-I9505, How to update from 4.2.2 to more recent ? - keep root

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

[Q] Restore factory image after tripping KNOX on 900t

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]

downgrade from 6.0.1 without root and without losing data?

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

rooting i9505 with XXUPPI1

Hello to all ..
is there any chance to root my S4 with the i9505XXUPPI1 version installed on it Or is there any other Way to Downgrade it to an earlier version and root it thereafter?
greetingz from Germany
HouseMeischda

You could try cfautoroot or flash TWRP and then flash supersu from TWRP.

CF-Auto-Root is your best option.

Thanks for your help.
For all i9505 Users with the same Problem ..
First i've flashed the original I9505XXUHOJ2 Firmware who listed on chainfire's Page, to be on the safe way =). Then i've flashed the cf-root Kernel from Chainfire. After that i installed the newest TWRP recovery and then the Resurrection Remix Rom 5.5.9.
Now i will test everything but seems to be nice till this moment =)
Thread can be closed .. Thanx

BTW, rooting is not required to install TWRP with Odin.

audit13 said:
BTW, rooting is not required to install TWRP with Odin.
Click to expand...
Click to collapse
True. But some people (including me) have had problems getting TWRP to stick with the Odin install.
I had to use an app to flash it when I took to the custom software world.
A user had the same problem few days ago. Also solved it with the app method.

I've never had a problem with getting TWRP or CWM to stick on the s2, s3, s4, note 1, note 2, or note 3 by unchecking auto reboot in Odin before flashing recovery. Once recovery has been flashed, I remove the battery and immediately boot into recovery. I found that not booting into recovery right after flashing will cause the stock recovery to overwrite the custom recovery when the phone boots normally.

Thats right. But in my case and first of all i wanted to test the stock rom with only root Access. But then i decided to install a custom one very quickly =)
After all i installed latest twrp via twrp-app, backed up everything, perform a full wipe and flashed ResurrectionRemix 5.5.9. Now i went to dirty unicorn rom on Android 6.0 base. Very nice performance, very clear Design and absolutely stable.
One more word to overriding the Recovery. In many other Posts, this Problem seems to be normal, if the S4 was already updatet to an official lollipop rom(with the new knox Bootloader, that verifies signatures of recovery and kernel) in the past. I think this issue was not present with kitkat and oder versions.
But with my little detour, i also was not effected from that override
Hope this can help others with similiar reservations who i had before. Not the fear of loosing warranty(because phone is anyway too old) but fear of tripping the bad eFuse and thus hardbricking the phone. BUT WELL DONE !!!
Many thanks for the support .. And greetingz to all =)

There is no eFuse that will hard-brick the S4.
It only has an eFuse for Knox, which simply prevents you from resetting the Knox counter back to 0x0, but it won't hard-brick anything.

i9505 Set Warranty Bit: Kernel

Welcome guys,
I have Galaxy S4 and I wanted to install Custom ROM. Unfortunately when I installed TWRP (the newest build), my phone displays "Set warranty bit: kernel" and then it boots into Recovery Mode (twrp works fine), but stock ROM doesn't boot. I don't know how to deal with it. Will custom ROM install fix that problem? I don't want to brick it.
I have access to download mode, TWRP (as I said before, when I turn phone on, it boots into TWRP instantly), but unfortunately ODIN doesn't recognize phone at all.
Please help :crying:

Does the computer recognize the phone?
After installing, did you select the option to allow changes to the internal memory?
Tried different USB cables and USB ports?
If you get the phone recognized by Odin, I suggest flashing a stock ROM via Odin and checking the phone to ensure complete functionality. Once you know the phone is working on a stock ROM, maybe start with an older version of TWRP such as 2.87.
Flashing a custom recovery should not prevent the phone from booting a stock ROM.

audit13 said:
Does the computer recognize the phone?
After installing, did you select the option to allow changes to the internal memory?
Tried different USB cables and USB ports?
If you get the phone recognized by Odin, I suggest flashing a stock ROM via Odin and checking the phone to ensure complete functionality. Once you know the phone is working on a stock ROM, maybe start with an older version of TWRP such as 2.87.
Flashing a custom recovery should not prevent the phone from booting a stock ROM.
Click to expand...
Click to collapse
I'm such an idiot. When knox is tripped you cant run stock ROM, so basically I just installed LineageOS and it works hah

Tripping knox does not prevent a phone from running a stock ROM.

audit13 said:
Tripping knox does not prevent a phone from running a stock ROM.
Click to expand...
Click to collapse
So it's strange though. I couldnt boot stock ROM and the only thing I had to do was install a custom one. Anyway, thanks for the answer

I've flashed TWRP to a number of Samsung phones which cause Knox to trip and the warranty bit to change from 0x0 to 0x1. Despite this, I have been able to flash and use stock ROMs with a tripped Knox indicator.
Maybe the phone needed a factory reset using the stock recovery after being flashed with Odin?

audit13 said:
I've flashed TWRP to a number of Samsung phones which cause Knox to trip and the warranty bit to change from 0x0 to 0x1. Despite this, I have been able to flash and use stock ROMs with a tripped Knox indicator.
Maybe the phone needed a factory reset using the stock recovery after being flashed with Odin?
Click to expand...
Click to collapse
Aaaand here we got the problem. I tried to install twrp many times and unfortunately the stock one stopped running (dont ask, i dont know how it happened). Despite this everything worked but I wanted to install custom ROM and then that problem happened. It was just the lack (??) of stock ROM or knox blocked the availability to boot it.
Oh, completely forgot. I installed TWRP by LineageOS' tutorial on their page

It all worked out in the end which is the important part.
Thanks for sharing your solution.