I'm sure this won't apply to many people, as most have already installed a custom recovery and rooted through other means, without worrying about the KNOX counter.
However, I previously used the method muniz_ri posted here: http://forum.xda-developers.com/tmo...ow-to-update-to-stock-rooted-ob1-5-0-t3049676, so the phone is currently on 5.0 (G900TUVU1DOB1) and rooted without needing a custom recovery (KNOX status 0x0).
As I understand, 5.0 was the last version that allowed downgrading and Kitkat was the last rom that provided a root method that leaves KNOX intact.
So, I was wondering if the following method might work:
Downgrade to 4.4.2 stock using Odin v3.0.9.
Root with Towelroot.
Use Flashfire and the steps outlined in the post above, but substitute the OB1 rom for the 6.0.1 PE1 rom in this thread.
Flash PE1 Bootloader and Modem with Odin.
Any chance this could work?
Related
My phone would not show that an OTA update was available for the Lollipop 5.0.1 update so I had to use Odin for the update.
-I did a full unroot.
-Using Odin I flashed the OC1 Neutered full odin rar file
- The update was successful and I now have 5.0.1.
My questions begin here. How can I regain root access using Odin now that I have the update.
Can I flash the NC5 kernel, use towelroot, SU, without tripping Knox?
From what I have researched so far I believe i would have to go back to KitKat to get root access. I am just trying to confirm.
Any and all help is appreciated. I have a good bit of experience I am just new to the forums. I would love to have Root access with this new OS.
I was wondering if I could use flashfire to flash XtreStoLite Deo-Mod Edition 2.1 ROM without tripping knox. Any help would be appreciated!
As far as I know in order to flash a rom needs changes to bootloader as soon as you touch the bootloader it trips knox. You can only root without tripping knox
Sent from my SM-G925F using Tapatalk
I had rooted via Pingpong root fine (no knox tripped) and then downloaded Echoe rom with standard kernel after being told that it would not trip knox (it worked for that guy) but it tripped knox anyway. So I though well, why not go all the way.
dwarfer66 said:
I had rooted via Pingpong root fine.
Click to expand...
Click to collapse
Ping Pong root uses an exploit in the 5.0.2 Stock rom to get root access, without flashing.
Anytime the bootloader partition gets written to, the Knox counter gets incremented.
Flashing with Flashfire will trip Knox.
I do not believe there is a way to flash without accessing the Bootloader.
Hi everyone, I haven't been active in awhile, and decided to upgrade from 4.4.4 to 5.0.1.
Device is:
Verizon Galaxy S4
MDK / Loki
TWRO 2.8.7.0
was on 4.4.4
I used the FlashFire upgrade method, because I wanted to have that upgrade modem, baseband etc. everything I needed.
Prior to root, I upgraded my TWRP, I did a TWRP backup.
I downloaded Odexed 5.0.1 stock update from the thread, and followed the instructions, it installed but on final reboot, it just got stuck at the Samsung / Custom screen. When I went to boot into recovery, it's now the stock system recovery LRX22c.I545VRUG0C1
Gives an error on the bottom as
Code:
#MANUAL MODE#
Appling Multi-CSC
Applied The CSC-code: VZW
remove failed file /system/csc_contents/ (read only file system)
If I try to apply update via external storage, using stock update I get:
Code:
footer is wrong
signature verification failed
Anyway I can flash TWRP via adb, then just re-flash the rom with loki manually? Or anyway without having to use odin and downgrade? I won't lose loki root will I? What do I do? Thanks in advanced.
well I'm trying to flash back to MDK via odin, and I keep getting aboot.img failure.. i'm really at a loss here, I can't even odin back to MDK.
notstevek said:
well I'm trying to flash back to MDK via odin, and I keep getting aboot.img failure.. i'm really at a loss here, I can't even odin back to MDK.
Click to expand...
Click to collapse
What instructions did you use? SS and FF were made specifically for locked bootloaders so they require a different instructions for flashing. You basically ignored the benefits of being on MDK by doing whatever you did. Doesn't sound like you're on MDK anymore and I need more details to help. Someone else might be able to help you.
If all you wanted was the OC1 modem, could have just flashed it from here. People have reported issues with TWRP versions above 2.8.4.0-jfltexx.
Neffy27 said:
What instructions did you use? SS and FF were made specifically for locked bootloaders so they require a different instructions for flashing. You basically ignored the benefits of being on MDK by doing whatever you did. Doesn't sound like you're on MDK anymore and I need more details to help. Someone else might be able to help you.
If all you wanted was the OC1 modem, could have just flashed it from here. People have reported issues with TWRP versions above 2.8.4.0-jfltexx.
Click to expand...
Click to collapse
The tutorial said for mdk, I followed it exactly and it didn't work. I then ****ed up by flashing lollipop through stock recovery so it flashed the new baseband, and I removed loki. That's my bad, however I did follow the instructions and it didn't work. I should have just flashed 5.1 manually. Oh well. Is there safestrap for lollipop, or a way to downgrade to me7 to use safestrap?
Sent from my SCH-I545 using Tapatalk
SS isn't compatible with Lollipop. Recommend switching to FF, apparently it can flash Stang's ROM on stock OC1. Still need root. Or look into MultiSystem but I'm not knowledgeable with them but hear of success with them.
Sent from my SCH-I545 using Tapatalk 2.4.15
You can use king root to get root, then search for instructions to swap to supersu. From here should be able to install FF.
Good luck.
Sent from my SCH-I545 using Tapatalk 2.4.15
Just got my GS5 today. Rooted it using this method with towel root and a kernel downgrade
http://forum.xda-developers.com/tmobile-galaxy-s5/general/how-to-root-s5-firmware-knox-0x0-t2909352
SuperSU is stuck on 'disabling knox'
I am wondering what is a way to avoid setting the timer when generally when updating ROMS and Kernels since...from what I understand, I can't have TWRP without tripping nox
Solution: just reset and try su again
Flashed stock Lollipop 5.1.1 ROM using ODIN, Device binary & status are CUSTOM? Help!
Hey guys! First time poster!
A few months back, I tried using CF-Auto root in order to gain root access on my phone, but I flashed something incorrectly and I was never able to get root working correctly. I know because of this, I tripped KNOX, and whenever I rebooted, there was a "Set Warranty Bit: Kernel" at the top of the device.
Due to the recent Marshmallow 6.0.1 upgrade, I want to unroot and get stock firmware, so I decided to do some research and go ahead and try to flash the stock G900T 5.1.1 FOJ4 firmware (tar.md5 file), so I can get my ability to update my phone via OTA updates. I looked up my matching firmware (FOJ4) through Android File Host and then unzipped it to my desktop.
I followed a guide and used ODIN 3.10.7 to flash the stock firmware file onto my phone. I also wiped cache/ factory reset before and after flashing the stock image.
Everything went well and I no longer see the "Set Warranty Bit: Kernel" when I boot. The problem I have is that when I go into download mode, the CURRENT BINARY and SYSTEM STATUS are both CUSTOM.
I was under the impression as long as you flash a stock firmware to your device, you will unroot and your device will be official, and then you'll be able to do OTA updates. Maybe its because I have KNOX tripped? Maybe can someone clarify that for me?
My main questions/concerns are:
1.) Is there anyway to make my device status/binary as OFFICIAL, in order to regain OTA updates?
2.) If I want to download the 6.0.1 Marshmallow update, should I just try through KIES or downloading the tar.md5 file to flashing via ODIN like I did with stock?
3.) Will there be any risk of bricking since my device is still "custom", if I go the above route?
4.) As a last ditch effort, should I just try downloading a different stock Lollipop firmware, and try flashing with ODIN again?
5.) What does this sub think of Marshmallow 6.0.1 update? Is it worth it?
Thank you guys in advance! Hope you have an awesome day!
@Root_S5_Please
#2 with Odin will work and is the correct way to go, #3 will not happen as long as you use Odin, you can't untrip Knox but that's OK since it doesn't have any effect on functionality. #4 is unnecessary and won't do anything to help. Someone else will have to answer #5, I Odined the update and immediately went back to CM13