I have just updated my rooted 4.3 i9505 to 4.4.2 using mobile odin Pro v4. Here are the steps i followed:
1) Download firmware for your region from sammobile.com
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
3) Use Mobile Odin Pro v4 to flash firmware from step 1 above. It will not update bootloader in firmware. Make sure you tick:
a) Enable Everoot
b) Inject Superuser (SuperSU)
c) Inject Mobile Odin
d) Download mode after flash (so that it will boot straight to download mode)
4) Use PC Odin 3.09 to flash bootloader tar file made in step 2 above. Tick Phone Bootloader Update. DO NOT tick Auto Reboot and F. Reset time.
5) Boot again into download mode to check Knox flag which should remain 0x0
6) Reboot device and wait up to 5mins.
Device will be updated to 4.4.2 and retains root and Knox remains 0x0.
Enjoy.
Edit: I used the information here to transform my S4 into S5:
www.androidpit.com/how-to-transform-your-galaxy-s4-into-an-s5
Thanks for the post
I'm curious why it's a two step process. Does mobile Odin not flash the bootloader?
I guess you could do the whole thing with desktop Odin, would I be right in saying you use mobile odin as it does the root for you?
[hello
i have in my s4 i9505 a 4.4.2 rom , no root
is possible use this method to root without tripping knox?
karmac1970 said:
[hello
i have in my s4 i9505 a 4.4.2 rom , no root
is possible use this method to root without tripping knox?
Click to expand...
Click to collapse
you need root first because mobile odin requires root, you are late bro because the new 4.4.2 bootloader has already fix for root de la vega knox 0x0
Upgrading gt-i9505 from 4.2.2 to 4.4.2 WanamLite
I updated from 4.2.2 stock rooted to WanamLite (4.4.2 Touchwiz pre-rooted) yesterday. It was pretty easy:
0) Titanium backup and Nandroid backup. I forgot to back up text messages and a few little things, but no big loss.
1) Flash this from Odin 3.07 (GSM + LTE modem) (as Phone not PDA)
2) Flash XXUEMK9 from here.
3) Install TWRP via custom recovery
4) Flash Wanam as PDA in Odin.
Seemed to work fine
Confusion
To avoid confusion I think people should know this only works if you already have root on 4.3 prior to MKF, it allows you to keep root without tripping knox.
http://forum.xda-developers.com/showpost.php?p=51488982
commandonz said:
Thanks for the post
I'm curious why it's a two step process. Does mobile Odin not flash the bootloader?
I guess you could do the whole thing with desktop Odin, would I be right in saying you use mobile odin as it does the root for you?
Click to expand...
Click to collapse
Mobile Odin does not flash Bootloader. That's why the second step is necessary. Yes, you are right. If you are already rooted, then mobile odin allows you to update the firmware and keep root. You will lose root after updating with desktop odin.
Cheers
Bordo_Bereli51 said:
you need root first because mobile odin requires root, you are late bro because the new 4.4.2 bootloader has already fix for root de la vega knox 0x0
Click to expand...
Click to collapse
You are right. No root method for 4.4.2 (for now) without tripping Knox flag.
I went from 4.2.2 quite easily to 4.4.2 using the steps above. I guess most people are on 4.3 though, 4.2.2 made it easier as Knox isn't on the phone at all.
commandonz said:
I went from 4.2.2 quite easily to 4.4.2 using the steps above. I guess most people are on 4.3 though, 4.2.2 made it easier as Knox isn't on the phone at all.
Click to expand...
Click to collapse
What's your current Knox flag? 0x0?
shayind4 said:
What's your current Knox flag? 0x0?
Click to expand...
Click to collapse
I stayed on a pre-knox bootloader as I went from 4.2.2 to 4.4.2, so I have no knox flag.
commandonz said:
I stayed on a pre-knox bootloader as I went from 4.2.2 to 4.4.2, so I have no knox flag.
Click to expand...
Click to collapse
Lucky you. I'm on 4.4.2 bootloader, Knox flag 0x0, rooted.
shayind4 said:
Lucky you. I'm on 4.4.2 bootloader, Knox flag 0x0, rooted.
Click to expand...
Click to collapse
I deliberately didn't upgrade to 4.3 and held of on 4.4 purely to avoid Knox. It probably wouldn't matter much because I never plan to use Knox, and I think you can still do most things with the knox flag tripped, but it seemed better to avoid.
4.4.2 isn't much different from 4.2.2 really. I'm hoping for a stability increase, maybe a slight performance increase and battery savings. But I mostly just wanted to come up to date.
Hi, you wrote that we need to make .tar file from this files:
shayind4 said:
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
Click to expand...
Click to collapse
I found another tutorial for this and that user wrote this:
3. Package 2 Tar files, one with the bootloader ( aboot.mbn,sbl1.mbn,sbl2.mbn, sbl3.mbn), the second one with everything else.
Click to expand...
Click to collapse
Are this files- tz.mbn and rpm.mbn important too? Or it doesn't matter?
pRo_lama said:
Hi, you wrote that we need to make .tar file from this files:
I found another tutorial for this and that user wrote this:
Are this files- tz.mbn and rpm.mbn important too? Or it doesn't matter?
Click to expand...
Click to collapse
Hi
All the 6 mbn files are bootloader files needed for the bootloader tar file.
You need 2 tar files:
A) Downloaded firmware= tar file with all the contents (you dont have to open it). You can make a copy to use in step 2 below for extracting mbn files (bootloader files). You will notice that step 2 in OP says make a copy of downloaded firmware.
B) Bootloader tar = all the mbn files
Mobile odin (OP step 3) does not flash bootloader when you use the downloaded full firmware (in A above). That's why you need the bootloader tar to be flashed via PC odin (OP step 4).
Both tutorials are similar.
Cheers
shayind4 said:
I have just updated my rooted 4.3 i9505 to 4.4.2 using mobile odin Pro v4. Here are the steps i followed:
1) Download firmware for your region from sammobile.com
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
3) Use Mobile Odin Pro v4 to flash firmware from step 1 above. It will not update bootloader in firmware. Make sure you tick:
a) Enable Everoot
b) Inject Superuser (SuperSU)
c) Inject Mobile Odin
d) Download mode after flash (so that it will boot straight to download mode)
4) Use PC Odin 3.09 to flash bootloader tar file made in step 2 above. Tick Phone Bootloader Update. DO NOT tick Auto Reboot and F. Reset time.
5) Boot again into download mode to check Knox flag which should remain 0x0
6) Reboot device and wait up to 5mins.
Device will be updated to 4.4.2 and retains root and Knox remains 0x0.
Enjoy.
Edit: I used the information here to transform my S4 into S5:
www.androidpit.com/how-to-transform-your-galaxy-s4-into-an-s5
Click to expand...
Click to collapse
Thank you for your explanation. But I have some questions:
1. Can you use the same method to update keeping root from a 4.3 rooted version to a more recent 4.3 not safe-rootable version (not rootable without triggering the knox)?
2. Can you first flash the new bootloader with PC Odin and then all the rest with Mobile Odin?
3. What happens if you only flash with Mobile Odin everything except the new bootloader (new firmware/old bootloader)? Does the device boot?
4. What happens instead if you only flash the new bootloader with the PC Odin (new bootloader/old firmware)? Does the device boot?
5. Can you use your method (adequately adapted) to downgrade the firmware? That is, after an update to 4.4.2 or a newer 4.3, can you just flash the old firmware with Mobile Odin, keeping the new bootloader so that you do not trigger the knox (new bootloader/older firmware)?
Thank in advance.
odicamillo said:
Thank you for your explanation. But I have some questions:
1. Can you use the same method to update keeping root from a 4.3 rooted version to a more recent 4.3 not safe-rootable version (not rootable without triggering the knox)?
2. Can you first flash the new bootloader with PC Odin and then all the rest with Mobile Odin?
3. What happens if you only flash with Mobile Odin everything except the new bootloader (new firmware/old bootloader)? Does the device boot?
4. What happens instead if you only flash the new bootloader with the PC Odin (new bootloader/old firmware)? Does the device boot?
5. Can you use your method (adequately adapted) to downgrade the firmware? That is, after an update to 4.4.2 or a newer 4.3, can you just flash the old firmware with Mobile Odin, keeping the new bootloader so that you do not trigger the knox (new bootloader/older firmware)?
Thank in advance.
Click to expand...
Click to collapse
Hi
1) Yes. Just update Supersu and disable Knox. I used it safely to update from rooted 4.3 to rooted 4.4.2, nox flag 0x0.
2) No. You need to flash firmware with Mobile odin first so that root can be injected at the same time (before flashing bootloader with PC Odin).
3) The device may boot but not sure with this tutorial. Some people have updated from 4.2.2 (no knox bootloader) to 4.4.2 keeping old bootloader, and they have no KNOX using a different method. Check post #5.
4) It may boot but you will lose root. You cannot safely root afterwards.
5) NO. Flashing older firmware or older bootloader will trigger Knox flag.
regards
nickp27 said:
To avoid confusion I think people should know this only works if you already have root on 4.3 prior to MKF, it allows you to keep root without tripping knox.
Click to expand...
Click to collapse
currently I have MKF, rooted via saferoot, knox 0x0.
spamtrash said:
currently I have MKF, rooted via saferoot, knox 0x0.
Click to expand...
Click to collapse
Hi ,
I wonder the same thing, if the tutorial is working from a MKF 4.3 with saferoot
Thanks for your answers
lukvdb78 said:
Hi ,
I wonder the same thing, if the tutorial is working from a MKF 4.3 with saferoot
Thanks for your answers
Click to expand...
Click to collapse
When I said prior to, I meant including. If you have knox 0x0 and root either through saferoot or kingo then this should work.
i am thinking to get the s6 and i dont think i can give up on root so i heard there is a root method pingpong does not trip knox if i do it
can i install custom recovery on it without tripping knox or anything else on download mode
if i restore to stock will everything stays the same?
thank you in advance
You can root without tripping the KNOX with Ping Pong Root , but if you flash unsigned software like custom recovery or custom ROM the knox will trip and you will loose the warranty.
Vixa said:
You can root without tripping the KNOX with Ping Pong Root , but if you flash unsigned software like custom recovery or custom ROM the knox will trip and you will loose the warranty.
Click to expand...
Click to collapse
if i install TWRP through the phone will it trip knox ?
installing XPOSED?
sorry for these stupid questions but i need to know the safe sides of modding the phone
Iloudsan said:
if i install TWRP through the phone will it trip knox ?
installing XPOSED?
sorry for these stupid questions but i need to know the safe sides of modding the phone
Click to expand...
Click to collapse
Your answer is in post number 2
Iloudsan said:
if i install TWRP through the phone will it trip knox ?
installing XPOSED?
sorry for these stupid questions but i need to know the safe sides of modding the phone
Click to expand...
Click to collapse
I am talking about using flashify to flash twrp not odin
Iloudsan said:
if i install TWRP through the phone will it trip knox ?
installing XPOSED?
sorry for these stupid questions but i need to know the safe sides of modding the phone
Click to expand...
Click to collapse
Xposed does not work on 64bit
Sent from my SM-G920F using Tapatalk
There is something strange about knox. I flashed BTU(UK) stock ROM on my XXV(vietnam) SM-920F brand new phone using odin 3.10.6. And hell, knox is tripped now. Strange? Anybody any clues?
sstiwari said:
There is something strange about knox. I flashed BTU(UK) stock ROM on my XXV(vietnam) SM-920F brand new phone using odin 3.10.6. And hell, knox is tripped now. Strange? Anybody any clues?
Click to expand...
Click to collapse
I'm so glad i saw this, i was about to do the same. Got all my backups ready to flash and wipe to change the CSC to BTU (from EVR). So your KNOX has tripped, how was this confirmed?
Were you able to do anything since tripping it?
Thanks
sohail_ahmad said:
I'm so glad i saw this, i was about to do the same. Got all my backups ready to flash and wipe to change the CSC to BTU (from EVR). So your KNOX has tripped, how was this confirmed?
Were you able to do anything since tripping it?
Thanks
Click to expand...
Click to collapse
Nothing much. Once knox is tripped. Its tripped. There is nothing one can do about it.
Can I Update S6 via Odin
I have S6 (SN-G92F)
Made in Vietnam
Original CSC code "ECT"
Active CSC code "ECT"
Knox Warranty void 0*0
CSC Country Nigeria/NG
CSC version
G920FOJV1AODE
Android version 5.0.2
When I tried to OTA update, it shows "already latest OS installed"
I have tried to update it through smart switch, but it updated to the same version.
I have checked in sammobile that 5.1.1 stock available for the same CSC of Nigeria.
Can I update my mobile to 5.1 through odin with out Knox trip.
Knox tripping is very important for me.
any one can help me
I hope it's allowed to ask this, but would there be a use for me to flash engineering bootloader if I've already tripped my KNOX?
I'm more familiar with HTC devices, so would it be like getting S-OFF? Would I be able to flash unsigned PIT-files, or change the size of the volumes on the phone in other ways?
Cheers
if you have already tripped knox, there is any reason to use engineering bootloader.
that is used only when you haven't tripped knox and you want to however use custom rom without tripping it
erghetto said:
if you have already tripped knox, there is any reason to use engineering bootloader.
that is used only when you haven't tripped knox and you want to however use custom rom without tripping it
Click to expand...
Click to collapse
So what you're saying is that an engineering bootloader would not allow me to flash an unsigned PIT-file?
i don't know about this.
But i repeat.. the point is that you absolutely don't need to use engineering bootloader. it is used only when your knox is 0x0 and you want to however use custom rom (but to do this, your firmware has to be older than OI9)
you have already tripped your knox (from what you have said in first post), so go and flash every rom you want.
erghetto said:
i don't know about this.
But i repeat.. the point is that you absolutely don't need to use engineering bootloader. it is used only when your knox is 0x0 and you want to however use custom rom (but to do this, your firmware has to be older than OI9)
you have already tripped your knox (from what you have said in first post), so go and flash every rom you want.
Click to expand...
Click to collapse
Thanks for trying to help, but this isn't about flashing ROMs nor tripping knox. I'll go ahead and try it.
hi
bit of a noob question but ill give some context first...
My s7 (g930f) is on android 7.0, ive successfully installed twrp , magisk and samsung anti root removal via odin.
Knox counter has not been activated as far i can tell .
Snapchat still works. Knox app says warranty is still valid
so far so good
Now i wish to back up my phone in its current state
Now to my question , with my phone rooted, twrp installed with knox still intact ..
Could i make a backup with twrp , then later recover with twrp and STILL have knox with a counter of 0?
I'm not sure how you have managed to flash custom without tripping KNOX
But KNOX is not part of anything that TWRP backs up, so if you somehow have not tripped it, back up, then trip it and restore, it will remain tripped, it is a permanent hardware change
magisk hides the true state of the knox.
Actually his knox is not 0x0
guillefs said:
magisk hides the true state of the knox.
Actually his knox is not 0x0
Click to expand...
Click to collapse
Yea, thought something like that was happening, no-one has managed custom flashing without tripping KNOX yet
Before flashing the supersu, my knox is 0x0 (magisk installed) via download mode.