I am collecting information on if and how it is possible to flash CyanogenMod 11 to the Galaxy S5 without setting the Knox Warranty Void flag to 0x1 (which mostly means loosing your warranty). Please feel free to contribute!
Definitely possible is:
Root Galaxy S5 (G900F) while keeping Knox 0x0. This works via Towelroot method.
Install some custom ROMs (NeatROM or ALEXNDR) while kepping Knox 0x0. This works via flashing with Mobile Odin PRO. Instructions are available in both ROM threads.
Now the question is if we can use the Mobile Odin PRO flash method for CyanogenMod ROM and what has to be done to avoid Knox 0x1.
In the CM11 zips there are folders for recovery, system and META-INF as well as boot.img and file_context files.
system: flashing ok
The system folder contains the contents of the system partition and should be fine to flash as the other ROMs with Knox 0x0 have that, too. I don't think any checks on the contents of the system partition are done by Knox (please correct me if i'm wrong!).
boot.img: flashing not safe
The boot.img file contains primarily the kernel image and the ramdisk; details can be found here and instructions on modifying are for example here.
I think at least the kernel image is checked by Knox (i don't know how and when, maybe if it is signed by samsung or if the checksum matches known kernels; any information on that would be helpful!). The ALEXNDR ROM for example uses the same boot.img as the stock G900FXXU1ANG2 firmware. CM11 uses a different kernel (CAF), which quite certainly would not pass any Knox checks. In conclusion i think it is advised NOT to flash the CM11 boot.img if you want to keep Knox 0x0.
This leads to the question if you can use a stock kernel in combination with CM11. It has been reported to work with earlier versions of CM on other devices, but i could not find much information on this, it might or might not work. If anyone has better information on this, please post it!
recovery: flashing not safe
Flashing custom recoveries will trigger Knox 0x1 (as far as i know). I could not yet find out when the recovery is actually installed, the ROM installer only copies the recovery installer into /system/etc/install-cm-recovery.sh and the recovery image to /system/recovery-from-boot.p. My guess is it will be installed on first boot.
As the recovery should not be necessary to run CM11, it should not be flashed. More detailed information welcome!
META-INF: only flash with modiffications
This contains primarily the ROM installer script at /META-INF/com/google/android/updater-script. This is run when you 'flash a zip' (see here for details) and is pretty straightforward to read. Most actions seem harmless, but 2 or 3 might have to be removed/modified, like package_extract_dir("recovery", "/system"); or package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");.
/system/bin/backuptool.sh seems safe, it only backs up and restores addon /system files.
file_contexts: flashing ok
Not sure about this, i don't think it is actually flashed or anything. The other ROMs with Knox 0x0 don't have it, but i don't know how it would trigger Knox 0x1. This seems to be a SELinux config file containing types and ranges for system files etc.
So atm the following would be interesting (DON'T DO THIS, IT WOULD MOST DEFINETELY NOT WORK OR EVEN BRICK YOUR DEVICE! This is just hypothetic.):
Rooted S5 with stock G900FXXU1ANG2 firmware.
Remove the boot.img and recovery part from CM11 zip.
Flash the modified zip via Mobile Odin PRO.
I tried this and it failed. Had to restore device with stock rom and Odin, still Knox 0x0 though.
Has anyone tried something similar? Do you have additional information that might be helpful? Then please contribute!
DISCLAIMER: I can NOT guarantee any of this information to be correct! Whatever you do with this information is completely YOUR OWN RESPONSIBILITY.
aregvadfbg said:
I am collecting information on if and how it is possible to flash CyanogenMod 11 to the Galaxy S5 without setting the Knox Warranty Void flag to 0x1 (which mostly means loosing your warranty). Please feel free to contribute!
Definitely possible is:
Root Galaxy S5 (G900F) while keeping Knox 0x0. This works via Towelroot method.
Install some custom ROMs (NeatROM or ALEXNDR) while kepping Knox 0x0. This works via flashing with Mobile Odin PRO. Instructions are available in both ROM threads.
Now the question is if we can use the Mobile Odin PRO flash method for CyanogenMod ROM and what has to be done to avoid Knox 0x1.
In the CM11 zips there are folders for recovery, system and META-INF as well as boot.img and file_context files.
system: flashing probably ok
The system folder contains the contents of the system partition and should be fine to flash as the other ROMs with Knox 0x0 have that, too. I don't think any checks on the contents of the system partition are done by Knox (please correct me if i'm wrong!).
boot.img: flashing not safe
The boot.img file contains mainly the kernel image and the ramdisk; details can be found here and instructions on modifying are for example here.
I think at least the kernel image is checked by Knox (i don't know how and when, maybe if it is signed by samsung or if the checksum matches known kernels; any information on that would be helpful!). The ALEXNDR ROM for example uses the same boot.img as the stock G900FXXU1ANG2 firmware. CM11 uses a different kernel (CAF), which quite certainly would not pass any Knox checks. In conclusion i think it is advised NOT to flash the CM11 boot.img if you want to keep Knox 0x0.
This leads to the question if you can use a stock kernel in combination with CM11. I could not find much information on this, it might or might not work. If anyone has better information on this, please post it!
recovery: flashing not safe
Flashing custom recoveries will trigger Knox 0x1 (as far as i know). As the recovery should not be necessary to run CM11, it should not be flashed. More detailed information welcome!
META-INF: ?
Not sure about this. I guess it could be ok since the other ROMs with Knox 0x0 have that, too. This seems to contain the AROMA installer etc. When and where is this executed/applied?
file_contexts: ?
Not sure about this. The other ROMs with Knox 0x0 don't have it, but i don't know how it would trigger Knox 0x1. This seems to be a SELinux config file containing types and ranges for system files etc.
So atm the following would be interesting (DON'T DO THIS, IT WOULD MOST DEFINETELY NOT WORK OR EVEN BRICK YOUR DEVICE! This is just hypothetic.):
Rooted S5 with stock G900FXXU1ANG2 firmware.
Remove the boot.img and recovery part from CM11 zip.
Flash the modified zip via Mobile Odin PRO.
Has anyone tried something similar? Do you have additional information that might be helpful? Then please contribute!
DISCLAIMER: I can NOT guarantee any of this information to be correct! Whatever you do with this information is completely YOUR OWN RESPONSIBILITY.
Click to expand...
Click to collapse
You'll never flash cm11 and keep the Knox 0x0 in any way, shape or form. And once again to all people worried about warranty your clearly on the wrong forum
thatsupnow said:
You'll never flash cm11 and keep the Knox 0x0 in any way, shape or form. And once again to all people worried about warranty your clearly on the wrong forum
Click to expand...
Click to collapse
Could you give reasons why you think that it will never be possible?
I do not think using custom software and being concerned about hardware warranty does exclude each other, but that's only my opinion.
aregvadfbg said:
Could you give reasons why you think that it will never be possible?
I do not think using custom software and being concerned about hardware warranty does exclude each other, but that's only my opinion.
Click to expand...
Click to collapse
Because once a custom recovery or kernel is flashed by no matter what means or app KNOX will be triggered to 0x1. If it we`re possible it would have been done a long time ago.
gee2012 said:
Because once a custom recovery or kernel is flashed by no matter what means or app KNOX will be triggered to 0x1. If it we`re possible it would have been done a long time ago.
Click to expand...
Click to collapse
But why do you assume that you have to flash a custom recovery or kernel?
A custom recovery seems only necessary for flashing, which can be done with Mobile Odin PRO.
CM11 may ship with a custom kernel, but that does not mean you can not use another kernel. For example you could try to use the stock kernel instead which has been reported to work with earlier versions of CM on other devices, so it's at least possible. If the stock kernel does not work out of the box, then there would still be the possibility to build CM from source against the stock kernel sources.
aregvadfbg said:
But why do you assume that you have to flash a custom recovery or kernel?
A custom recovery seems only necessary for flashing, which can be done with Mobile Odin PRO.
CM11 may ship with a custom kernel, but that does not mean you can not use another kernel. For example you could try to use the stock kernel instead which has been reported to work with earlier versions of CM on other devices, so it's at least possible. If the stock kernel does not work out of the box, then there would still be the possibility to build CM from source against the stock kernel sources.
Click to expand...
Click to collapse
Don`t want to waste too much time on this discussion, start coding and building an post the solution here on this forum and you`ll get the XDA Nobel prize. Good luck mate
gee2012 said:
Don`t want to waste too much time on this discussion, start coding and building an post the solution here on this forum and you`ll get the XDA Nobel prize. Good luck mate
Click to expand...
Click to collapse
so you are saying it might be possible?
For the Galaxy Note 3 there is a thread where people are doing just that, flashing custom roms via Mobile Odin PRO without the kernel and recovery, and it is working for them. Those ROMs are not CM11 and they use the AROMA installer to skip kernel and recovery flashing, but the principle should be the same.
..
It's so simple:
CM11 is working only along CM kernel, there is no way to run CM11 on Samsung kernel. End of story.
fffft said:
You asked if CM 11 can be installed without affecting the Knox flag. And the answer is no.
Can you install CM 11 without incrementing the Knox flag? No
Can you carefully select bits and pieces to install and keep your Knox flag at it's original 0x0? Yes
Once you start eschewing the CM kernel, recovery, etc you are no longer talking about a CM install anymore. You can't gut the important pieces and pretend that it is still CM.
Click to expand...
Click to collapse
I look at it this way: if i have a system that is looking and behaving like cm11, then i don't care if it's theoretically not exactly cm11.
fffft said:
If Knox is so important to you, you are definately on the wrong site.
Click to expand...
Click to collapse
If there is a reversible way to achive my goal i will first try that, and only then consider a non-reversible way.
lukas77 said:
CM11 is working only along CM kernel, there is no way to run CM11 on Samsung kernel. End of story.
Click to expand...
Click to collapse
Unfortunately this might be true. Do you have information what the differences between those kernels are and why they are incompatible?
I have tried the following and it didn't work:
Removing boot.img and recovery from cm11 zip and removing the corresponding parts from the installer script, also removing device checks and signature checks as the functions are not available if you are flashing through MOP. Device went black during flashing of /system, wouldn't boot afterwards, had to flash stock rom through Odin to restore device. But still Knox 0x0.
aregvadfbg said:
I look at it this way: if i have a system that is looking and behaving like cm11, then i don't care if it's theoretically not exactly cm11.
If there is a reversible way to achive my goal i will first try that, and only then consider a non-reversible way.
Unfortunately this might be true. Do you have information what the differences between those kernels are and why they are incompatible?
I have tried the following and it didn't work:
Removing boot.img and recovery from cm11 zip and removing the corresponding parts from the installer script, also removing device checks and signature checks as the functions are not available if you are flashing through MOP. Device went black during flashing of /system, wouldn't boot afterwards, had to flash stock rom through Odin to restore device. But still Knox 0x0.
Click to expand...
Click to collapse
Much brighter minds then you thought, coded, build and experimented with what you are thinking off now and it simply cannot be done for various reasons:
1. KNOX will always be triggered when a modified custom kernel is installed, there is no fix atm and there will most likely never be one.
2. CM is following the CAF tree which means their kernels aren`t compatible with AOSP.
I`am sure there are more problems but above 2 are the most important ones imo.
Now either live with it or buy a Nexus device for instance which doesn`t have KNOX.
..
Related
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
wethestill said:
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
Click to expand...
Click to collapse
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
wethestill said:
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
Click to expand...
Click to collapse
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Gage_Hero said:
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Click to expand...
Click to collapse
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
wethestill said:
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
Click to expand...
Click to collapse
If your coming from 4.3 there are a number of good roms... unfortunately they are all around 1.2 to 1.4 GB so if you have a slow connection it will take a while... I run Danvh's 4.4 http://forum.xda-developers.com/showthread.php?t=2537495 , there is also this one that people seem to like but I haven't tried it.... http://forum.xda-developers.com/showthread.php?t=2375180 you will need a custom recovery.... both of these suggest twrp.... I flashed with 2.6... 2.7 is out now and I don't know how it reacts but you will need a custom revovery to flash the zip file....
I guess the issue is you have to restore to stock via odin but you don't know what version bootloader you have? Guess you'll have to use samsung tool which will probably install knox?
Can you install custom recovery via odin?
Try with the new 4.4 files
sent from my mobile device
Knox is already tripped. I'd go into recovery, do a factory restore again and then plug it into the computer and do a restore with Kies.
Sent from my SGH-I337M using Tapatalk
So back in the day I used a pre-Knox GNote2 in which there used to be a few variables in the bootloader that listed the system status (number of ODIN downloads, system status, something counter about binaries and so on). With the S5 these seem to be largely replaced by the KNOX counter.
That said we used to be able to use Triangle Away to reset those variables via a special boot mode which reset everything and you could end up with a 100% stock phone that no one could pick up on.
I want to play around with the system.img partition in the stock firmware and push the su files in and pull some other stuff out. As far as I understand from other modified stock firmwares this should be possible to do without tripping Knox (if you flash from ODIN without any bootloader, recovery or kernel images).
However, is it possible to reset the "CURRENT BINARY" and "SYSTEM STATUS" variables by simply reflashing stock firmware (and doing a full reset) or will those remain locked and easily noticeable by an officious technician?
Thanks in advance
(PS: I did look on the forums, didn't see anything that really answered this question though. Sorry if it is already answered. My model is a G900H for anyone interested, shouldn't make any different though.)
hexd said:
So back in the day I used a pre-Knox GNote2 in which there used to be a few variables in the bootloader that listed the system status (number of ODIN downloads, system status, something counter about binaries and so on). With the S5 these seem to be largely replaced by the KNOX counter.
That said we used to be able to use Triangle Away to reset those variables via a special boot mode which reset everything and you could end up with a 100% stock phone that no one could pick up on.
I want to play around with the system.img partition in the stock firmware and push the su files in and pull some other stuff out. As far as I understand from other modified stock firmwares this should be possible to do without tripping Knox (if you flash from ODIN without any bootloader, recovery or kernel images).
However, is it possible to reset the "CURRENT BINARY" and "SYSTEM STATUS" variables by simply reflashing stock firmware (and doing a full reset) or will those remain locked and easily noticeable by an officious technician?
Thanks in advance
(PS: I did look on the forums, didn't see anything that really answered this question though. Sorry if it is already answered. My model is a G900H for anyone interested, shouldn't make any different though.)
Click to expand...
Click to collapse
The "SYSTEM STATUS" can be faked with the Wanam Xposed module, I don't know about the "CURRENT BINARY" though.
Hi,
after reading a lot of thread here, or in android developement, about galaxy note 3, I am wondering if there is any way to know if a rom is knox free or not.
a lot of time, it is not clearly listed in the thread.
I saw some post saying that if you use odin mobile, or odin on PC, or rom without kernel, or rom without boot loader etc...
but I find easily some information which says the opposite (specially odin mobile, which I bought, and tell clearly when I launch it that it can trip knox counter)
my galaxy note 3 N9905 is under 4.4.2, xxxUGNG1.
I rooted it without modifying knox (I checked it, it is not set to 01, it is still = 0)
I would like to undertsand what I can flash without "any" risk, and whant method to use :
odin on PC ? custome recovery ? original recovery (renaming the rom by update.zip is working, no ?)
no kernel ? with kernel ? no bootloader ???
thanks for any help to understand.
Olivier
ROM has nothing to do with KNOX trigger. You strike the flag only if you flash custom recovery or custom kernel.
You need custom recovery to install custom ROM. Or Mobile Odin Pro. The only way to install custom ROM without affecting the KNOX flag is by installing via Mobile ODIN Pro and NOT installing custom kernel, should the ROM installation include one.
Hi,
thanks for the feedback.
I try to have more information please.
let me sumarize your answer, and add more question :
I have a N9005, under stock rom, 4.4.2, xxxUGNG1.
note : I never launched knox in the device. I don't know if it change things or not...
I can flash a rom, using mobile odin pro, and not set knox flag to 01 if the rom do not contain any kernel.
I cannot flag any recovery at all : if I do it, knox flag will be set to 01.
if the rom I want to flash contain a kernel, I have to remove it from the package (or may be mobile odin pro has a setting to load the package, and not flash the kernel) ?
I cannot change the modem, for the same reason than for the recovery, right ?
if I want to flahs CM11, I will set the knox flag to 01, in all case, because the kernel need to be changed. right ?
so, the result is :
if I want to play with my note3 (play for me is testing CM, or all rom not starting from a samsung rom), I will set the knox flag to 01... right ?
thanks for any feedback
Olivier
It is no guaranty that custom rom will work with the stock kernel.
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
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.