[Q] flashfire 5.1.1 possible? - T-Mobile Samsung Galaxy S 5

Does anyone know if you can update to 5.1.1 from rooted 5.0.1 with knox not tripped using flashfire?
I have tried it with the s6 and it didn't work. Had to flash back to stock after trying.
Normally I just flash the stock file with Flashfire then flash again the same file with system removed and that got 5.0.1 up and running.
Do you think this is possible?
Right now samfirmware is not working for me to download the update. My internet connect here is too slow I think. Gets about halfway then breaks.

M9x3mos said:
Does anyone know if you can update to 5.1.1 from rooted 5.0.1 with knox not tripped using flashfire?
I have tried it with the s6 and it didn't work. Had to flash back to stock after trying.
Normally I just flash the stock file with Flashfire then flash again the same file with system removed and that got 5.0.1 up and running.
Do you think this is possible?
Right now samfirmware is not working for me to download the update. My internet connect here is too slow I think. Gets about halfway then breaks.
Click to expand...
Click to collapse
Yes, see here: http://forum.xda-developers.com/tmo...l/how-to-update-to-g900tof6-5-1-1-pc-t3141404

so since I am knox not tripped I flash the stock 100% rom without injection and the other partitions using odin, downgrade the kernel and use towelroot to root it again?
That is how to get around the bootloop issue?

Related

SGH-M819N (Metro PCS) Mega update via Kies

I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Installed Update, Re-rooted, re-installed TWRP
curgervending said:
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Click to expand...
Click to collapse
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
curgervending said:
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
Click to expand...
Click to collapse
never mind I got it. I had a brain fart and was doing the process back words. I put it in download mode for the root.
hotspot mod
I am rooted with stock rom just looking for a hotspot mod for my sgh m819n been searching and searching
reesemtk60 said:
I am rooted with stock rom just looking for a hotspot mod for my sgh m819n been searching and searching
Click to expand...
Click to collapse
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Deodex or odex
thanks one more question how can i tell if my phone is deodex or odex
reesemtk60 said:
thanks one more question how can i tell if my phone is deodex or odex
Click to expand...
Click to collapse
well easiest way is. if its your stock ROM that came with the phone when you bought it. it is odex.
if you are rooted, you can use root explorer to go into your system/app file and see if it shows odex settings for apps
I did and had no problem rooting with kingo. What I cannot find is a way around sim lock without going through metro and that sucks.
curgervending said:
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Click to expand...
Click to collapse
bnb25 said:
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Click to expand...
Click to collapse
is that rom odex of deodex because my is odex
reesemtk60 said:
is that rom odex of deodex because my is odex
Click to expand...
Click to collapse
deodex
curgervending said:
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
Click to expand...
Click to collapse
Almost had a heart attack from this upgrade. My phone was already rooted when I applied the update from Kies. Everything went through fine except when it restarted, I couldn't turn on Wifi at all and I was getting an E in the cell signal. I managed to download the TWRP tar file and Kingo app to root again. I was able to restore my previous backed up image and everything was when I last left it! WHEW!
That's strange. I had no problem. wifi worked and I haven't seen E at all (only 4g lte or 4g). My signal appears to be stronger and more stable with this update than with the original firmware (most of the time I have full bars). As mentioned I don't know what changes were made (no change log around) but this is my observation so far.
Sent from my SGH-M819N using xda app-developers app
Can somebody running MK7 please boot into download mode quickly to check whether this update has a new Knox bootloader?
(Vol - , Home, Power)
Need to know if the following strings are present or not:
KNOX KERNEL LOCK:
KNOX WARRANTY VOID:
BOOTLOADER RP SWREV:
Thanks in advance.
[QUOT1.0razykipa;50763526]Can somebody running MK7 please boot into download mode quickly to check whether this update has a new Knox bootloader?
(Vol - , Home, Power)
Need to know if the following strings are present or not:
KNOX KERNEL LOCK:
KNOX WARRANTY VOID:
BOOTLOADER RP SWREV:
Thanks in advance.[/QUOTE]
This string is present on my phone in download mode:
BOOTLOADER RP SWREV: 3
I have no lines displaying anything about KNOX.
In titanium backup I froze knox 1.0, knox notification manager 1.0, and knox store 1.0.
So it appears that knox is in the rom somewhere but it's had no impact on me. I'm rooted, have twrp installed and have flashed multiple custom roms on my device (both tw and aosp based roms).
Perfect, thanks! Glad you guys got spared from the horrid new Knox bootloaders. There's a small chance that the M819 can be downgraded to the older bootloader to remove Knox entirely, but if the update came with the newest bootloader (I got stuck with it on my i527M) there is no hope at all of downgrading.
Thanks to whoever posted this and the creator of this rom
bnb25 said:
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Click to expand...
Click to collapse
I have the sgh-m819n metro pcs model running the mk7 firmware. This was the only rom that worked 100% for me. Im running twrp recovery,super user and free hotspot. Not to mention all the extra cool apps that it comes with. Big props to the developers of this software may your days be blessed with many more hacks.
Must be unrooted to perform update thru kies without errors..
Galaxy Mega 6.3 On Liquidsmooth rom posted this
question to everyone....
ok not sure if am in the right area to post this but. I have a metro galaxy mega 6.3 (sgh m819n) successfully rooted with kingo. what im trying to find is how to put a custom recovery like twrp and how to do it like step by step. help would be greatly appreciated. or to point me in the right direction. thanks guys.
http://forum.xda-developers.com/showthread.php?t=2608110 this is a great rom for our mega(metropcs) imho. now in order to install CWM or TWRP you simply need to download the version thats for meliusltexx which is for the i9205 version of the mega.. These Roms and procedures are compatable with the M819n(metropcs) mega
thanksss
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=2608110 this is a great rom for our mega(metropcs) imho. now in order to install CWM or TWRP you simply need to download the version thats for meliusltexx which is for the i9205 version of the mega.. These Roms and procedures are compatable with the M819n(metropcs) mega
Click to expand...
Click to collapse
ok thanks and this will work correct.... also before I add a new rom on the m819n I have another question... I used to get 4LTE every where and now I get only 4G or edge after rooting with stock rom. signal apps dont do crap. is there a way to fix this... I miss my LTE data speeds. if you know how to fix or anything please point me in the right direction thanks.

[Q] Stock 4.3 Kingo rooted to 4.4.2 problems

I was stock rooted with Kingo and marked official with Wanam Xposed so I unrooted with Kingo and ran Xposed Disabler. So far I have downloaded the official update three times, it goes through the motions of rebooting and installing, but at the end it says it failed.
How can I get this installed? Will Odin'ing Freeza's tar fix it? If not, do I need to install an official MJ4 tar first? Will either of these tars wipe my data? Any other suggestions? I'd like to end up stock rooted on KitKat without tripping Knox if possible.
JimSmith94 said:
I was stock rooted with Kingo and marked official with Wanam Xposed so I unrooted with Kingo and ran Xposed Disabler. So far I have downloaded the official update three times, it goes through the motions of rebooting and installing, but at the end it says it failed.
How can I get this installed? Will Odin'ing Freeza's tar fix it? If not, do I need to install an official MJ4 tar first? Will either of these tars wipe my data? Any other suggestions? I'd like to end up stock rooted on KitKat without tripping Knox if possible.
Click to expand...
Click to collapse
I was getting a fail at 27% I flashed the stock Tar for Kitkat from Freeza and it worked great all data in tacked. I was not rooted but I am guessing you will loose root.

I545VRUGOF1 need help with root or downgrade to COF1

Flashed GOF1 by mistake from sammmobile using Odin. Now can't find a root method that works. Tried to flash COF1 using Odin but get fail message. Anyone have any suggestions? I'm really just needing root to get backups restored from TiBu. Much appreciated if anyone has suggestions.
Same here. Looking for a way to root OF1. Tried to downgrade to OC1 using method here:
http://forum.xda-developers.com/gal...-to-update-to-i545of1-5-0-1-keeproot-t3182544
It starts to install, but then fails and soft-bricks the phone and I have to use Repair Assistant get reinstall OF1. Any help to root from OF1 appreciated. TIA
I was able to downgrade to oc1 baseband and build. I got the idea from how I use to jump from android to Tizen on my first generation watch. I ran the of1 md5 and intentionally pulled the cord from my phone about 3/4 of the way through the install. Rebooted and had the white monitors telling me to hook up to kies. Then I loaded the PIT file in Odin, and put I545_OC1_Bootloader.tar.md5 in pda, ticked Re-Partition, Auto Reboot, and Nand Erase All boxes in options, and flashed it. After my bootloader flashed sucessfullly, I ran a stock md5 of the OC1 rom. Once flashed I booted into recovery, wiped cache, wiped system data both two times just to be safe, rebooted and I was on stock OC1 baseband and build ready to root with kingroot.
So you tried to reflash of1 using kies? Would you posible have the files you used to go back?
Thanks, really good idea
HeeyMaan said:
I was able to downgrade to oc1 baseband and build. I got the idea from how I use to jump from android to Tizen on my first generation watch. I ran the of1 md5 and intentionally pulled the cord from my phone about 3/4 of the way through the install. Rebooted and had the white monitors telling me to hook up to kies. Then I loaded the PIT file in Odin, and put I545_OC1_Bootloader.tar.md5 in pda, ticked Re-Partition, Auto Reboot, and Nand Erase All boxes in options, and flashed it. After my bootloader flashed sucessfullly, I ran a stock md5 of the OC1 rom. Once flashed I booted into recovery, wiped cache, wiped system data both two times just to be safe, rebooted and I was on stock OC1 baseband and build ready to root with kingroot.
Click to expand...
Click to collapse
This is exactly what i need. I have just lost root by taking OTA to OF1, and i think what you mentioned might work to get me back to OC1 Rooted until someone comes up with something better. Sound feasible? Does this method only work when you pull the plug like that? still not sure what white monitors is, sorry.
I am on OF1 and was rooted, flashed the stock rooted ROM and it didn't take. I Odin flashed this - http://forum.xda-developers.com/galaxy-s4-verizon/development/odin-i545vrugof1-neutered-bl-t3203361 and it got me back to unrooted OF1. I then went and did the re-root process for OF1 and am back rooted again. I think this file is a stock OF1 image, just doesn't have the bootloader which if you're on OF1 already then you have the OF1 bootloader.
What options do we have if we have the OF1 bootloader.
Sent from my SCH-I545 using Tapatalk
shiz0id said:
What options do we have if we have the OF1 bootloader.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As far as I know stang5litre has a OF1 compatible ROM and of course the stock deodex ROM/stock ROM. I'm not sure of any past those.

!! Help unbrick OF1 and keep root?

Apologies if this has been posted, but I couldn't find it. Thanks for any help!
Before softbricking, my VZW S4 had OF1 with root (rooted while on OC1 and flashed via FlashFire to OF1).
While trying to set up new payment cards with Android Pay, I tried to temporarily uninstall Xposed framework by flashing the Xposed uninstaller with FlashFire. Android Pay apparently checks for su and Xposed and blocks addition of payment cards if present. After flashing the uninstaller, boot sticks on verizon screen.
I did not have a bootloader like safestrap present to restore backups before boot.
I do have a full backup from FlashFire stored to my SD, but I don't know how I can restore it when stuck in boot...
I'm currently downloading Stock OF1 found here http://forum.xda-developers.com/galaxy-s4-verizon/general/of1-stock-tar-t3216417
...but I expect that will take root from me, if it even works to unbrick it. Then of course, I won't be able to restore my backup via FlashFire...
Any chance I can unbrick and keep root?
Thanks!
Can you give me you number and I write with wa
im in the same boat man. Got phone back up but now kingroot cant root.
EDIT. Used this http://www.wondershare.com/mobile-p...teID=je6NUbpObpQ-lm5T20.ZhJbL1BJ3RULuew#part2 to root OC1. Try it on of1. Otherwise your only choice is to odin back to stock bloated nonroot of1 and have a functional phone. Or wait perhaps
nemisans13 said:
im in the same boat man. Got phone back up but now kingroot cant root.
EDIT. Used this http://www.wondershare.com/mobile-p...teID=je6NUbpObpQ-lm5T20.ZhJbL1BJ3RULuew#part2 to root OC1. Try it on of1. Otherwise your only choice is to odin back to stock bloated nonroot of1 and have a functional phone. Or wait perhaps
Click to expand...
Click to collapse
Nice job figuring out a solution! I gave up and flashed a downgrade oc1 to unbrick, then accepted the of1 OTA out of frustration. No more s4 root for me. A little bittersweet...
Sent from my SCH-I545 using Tapatalk
mercerudy said:
Nice job figuring out a solution! I gave up and flashed a downgrade oc1 to unbrick, then accepted the of1 OTA out of frustration. No more s4 root for me. A little bittersweet...
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Bro all u needed to do was root oc1 with my link, download root file explorer and browse to system/apps/ delete sdm.apk
That disables ota updates. Hold on i found a thread here with a oc1 downgrade tar to use with odin
Yeah, I know. I did it before you posted your solution. That tar is the one I used to unbrick. I doubt it will work now that I OTA'd.
Sent from my SCH-I545 using Tapatalk
mercerudy said:
Yeah, I know. I did it before you posted your solution. That tar is the one I used to unbrick. I doubt it will work now that I OTA'd.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showpost.php?p=62472003&postcount=65
I used a similar method to root kitkat ng6 by flashing nc1 kernel rooting and flashing back to ng6 kernal. They're actual Samsung signed kernals so odin should have no issue flashing them. Root using wondershare then flash back to OF1 kernal. Keep in mind oc1 kernal on of1 can cause your phone to run weird make sure u enable usb debug prior to putting the phone in download mode for oc1 kernal flash then root with wondershare and flash back to of1
nemisans13 said:
Try this http://forum.xda-developers.com/showpost.php?p=62472003&postcount=65
I used a similar method to root kitkat ng6 by flashing nc1 kernel rooting and flashing back to ng6 kernal. They're actual Samsung signed kernals so odin should have no issue flashing them. Root using wondershare then flash back to OF1 kernal. Keep in mind oc1 kernal on of1 can cause your phone to run weird make sure u enable usb debug prior to putting the phone in download mode for oc1 kernal flash then root with wondershare and flash back to of1
Click to expand...
Click to collapse
Ok, I may give that a try when I have some time. Will post back with the results. Thanks man!
If this worked, then it would probably help a lot of people. I haven't seen anyone go back from the OTA of1 yet.
Sent from my SCH-I545 using Tapatalk
mercerudy said:
Ok, I may give that a try when I have some time. Will post back with the results. Thanks man!
If this worked, then it would probably help a lot of people. I haven't seen anyone go back from the OTA of1 yet.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
There's no downgrading from of1 because your bootloader was flashed to of1 when u updated BUT you should SHOULD NOT WILL BE ABLE TO be able to root it with oc1 kernal and flash back to of1 kernal then proceed to flashfire of1 DeOdexed and xposed it. Don't take my word for it though do your research you could always brick and that's all on you I'm only suggesting what rocks to look under I've read of people having rooted of1 with xposed working. The kernal switch rooting is fairly new to of1 it was common on kitkat
---------- Post added at 08:33 PM ---------- Previous post was at 08:32 PM ----------
In other words you're stuck on of1 but shouldn't be a big deal if u have root and xposed working then you're better off than oc1 because of1 got some bugs fixed over oc1
I had rooted of1 with xposed before I softbricked. Rooted oc1 with kingroot then flashfired the "rooted" deodexed of1 to maintain root and xposed it. It worked but was a little buggy compared to xposed on kitkat. I think I'm just going to hold off anyway. I actually accepted the OTA as a way to futureproof me from messing with it anymore I was spending too much time tinkering.
Sent from my SCH-I545 using Tapatalk
Try this http://www.wondershare.com/mobile-ph...J3RULuew#part2 rooted my phone when nothin else would. Download mobile go and use the one click root. Ten minutes later bam! Verizon Samsung Galaxy s4 i545 oc1 rooted baby!
mercerudy said:
I had rooted of1 with xposed before I softbricked. Rooted oc1 with kingroot then flashfired the "rooted" deodexed of1 to maintain root and xposed it. It worked but was a little buggy compared to xposed on kitkat. I think I'm just going to hold off anyway. I actually accepted the OTA as a way to futureproof me from messing with it anymore I was spending too much time tinkering.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
My rooted oc1 with xposed is running flawless. Battery life is also better than before I soft bricked. Weird. Screw that. I got an s3 on jellybean rooted for backup. I still got unlimited so an unrooted phone is useless to me. I don't have home Internet I tether all day errday
So I softbricked my verizon galaxy s4 of1 bootloader using flashfire to install a rom. It's stuck on the screen with the unlock and custom sign. How did you get your phone back to normal?
Flash the OF1 tar file in Odin. Use the AP slot and make sure it's checked. http://forum.xda-developers.com/showthread.php?t=3203361 That's the tar file thread.
problem with fire flash
hi guys,i have problem with flashing via fire flash...i have of1 rom,root,su app,all what i need....i instal fire flash from google play vs 0.55.1....i set up all with fire flash,but when i push fire button,only restart my device,led blinking blue and only restarting to verizon rom...root i have from xda discussion,i flash oc1 kernel,then root with wondershare and then i flash back of1 kernel....i use flash fire 0.55.1,i search for oldest version,but any work in my phone,still fall

Flashed stock Lollipop 5.1.1 ROM using ODIN, Device binary & status are CUSTOM? Help!

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

Categories

Resources