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.
Related
I would like to report that at least we have SUCCESSFULLY flashed and rooted MJ7 UK firmware using Mobile Odin Pro 3.85.
This is for the SM-N9005 Qualcomm Snapdragon model.
We were originally rooted on MJ1 by using Root de la Vega, with Knox 0x0, which made the Mobile Odin flash possible.
SUCCESSFUL FIRMWARE VERSIONS ROOTABLE: MI7, MJ1, MJ3
UNSUCCESSFUL ROOT :MJ6 and later
NOTE: THIS DOES NOT RESET YOUR KNOX if it is 0x1.
Originally reported in a Malaysia forum here: - XDA user williamyi (WiLyi on Lowyat.net forum) was the first user to report trying this method with success. Thank him in post 2 !!
Success 1 - williamyi
https://forum.lowyat.net/index.php?showtopic=3020868&view=findpost&p=64477527
Success 2 - joytest
https://forum.lowyat.net/index.php?showtopic=3020868&view=findpost&p=64477946
Success 3
https://forum.lowyat.net/index.php?showtopic=3020868&view=findpost&p=64482052
Success 4
https://forum.lowyat.net/index.php?showtopic=3020868&view=findpost&p=64493286
Success 5
https://forum.lowyat.net/index.php?showtopic=3020868&view=findpost&p=64494080
Knox remains 0x0
All we need to do is to to reinstall Xposed and its mods.
Thanks @Chainfire !!!!!
Many other XDA users are also now reporting success by flashing to MJ7 using this method.
Steps: (thanks to WiLyi of Lowyat.net forum) aka @williamyi in XDA
1. Download UK MJ7 firmware.
2. Extract the tar.md5 (I placed in internal SD - not sure if this make any differences)
3. Open the tar.md5
4. Check:
i. Everroot
ii. Inject SuperSU
iii. Inject Mobile Odin
5. Flash
NOTE: Mobile Odin will throw a standard warning about tripping Knox. That can be ignored (we did). Remember to tick Everroot so that you will be rooted immediately upon flashing.
NOTE: Mobile Odin "A compatible device was detected, but with an unexpected partition layout. Mobile ODIN cannot operate. This is a common error on CM and MIUI ROMs on some devices."
This can be solved by uninstalling and reinstalling SuperSU or its updates.
joytest said:
I would like to report that at least 2 users have SUCCESSFULLY flashed and rooted MJ7 UK firmware using Mobile Odin Pro 3.85.
More to come as it was reported in a Malaysia forum here
Success 1
https://forum.lowyat.net/index.php?showtopic=3020868&view=findpost&p=64477527
Success 2
https://forum.lowyat.net/index.php?showtopic=3020868&view=findpost&p=64477946
Knox remains 0x0
All we need to do is to to reinstall Xposed and its mods.
Thanks @Chainfire !!!!!
Steps: (thanks to WiLyi of Lowyat.net forum)
1. Download UK MJ7 firmware.
2. Extract the tar.md5 (I placed in internal SD - not sure if this make any differences)
3. Open the tar.md5
4. Check:
i. Everroot
ii. Inject SuperSU
iii. Inject Mobile Odin
5. Flash
Click to expand...
Click to collapse
You beat me on posting this. Hopefully this could help those who which to update to latest firmware without tripping the Knox. Happy flashing everyone
But you can't run mobile odin without root it says?
Sent from my SM-N9005 using Tapatalk
Drizzy xS said:
But you can't run mobile odin without root it says?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I had initially rooted with the Root de la Vega method, and Knox was still 0x0. I wanted to test a newer ROM MJ7 so after @williamyi had succeeded I tried as well.
We're all happy campers now.
Drizzy xS said:
But you can't run mobile odin without root it says?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I have rooted the firmware using Root De La Vega since day the early days and gotten the root access without tripping the knox.
This time I flash the UK's MJ7 firmware using Mobile Odin Pro 3.85 and successfully update the firmware from the first MJ1 to the latest MJ7 without tripping the knox as shown in the first link in the first post
joytest said:
I had initially rooted with the Root de la Vega method, and Knox was still 0x0. I wanted to test a newer ROM MJ7 so after @williamyi had succeeded I tried as well.
We're all happy campers now.
Click to expand...
Click to collapse
Dam is there no way to root mj7? I tried to root it using odin and URDLV but every time I try I get the odin fail error and it doesn't work
Sent from my SM-N9005 using Tapatalk
*realised you need to be rooted first to be able to flash via mobile odin
Drizzy xS said:
Dam is there no way to root mj7? I tried to root it using odin and URDLV but every time I try I get the odin fail error and it doesn't work
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Maybe this guide will help
https://forum.lowyat.net/index.php?showtopic=3020868&view=findpost&p=64362662
credits @antt00
Will work only for people with old bootloader and yet rooted
geek78 said:
Will work only for people with old bootloader and yet rooted
Click to expand...
Click to collapse
Which firmware are you in now? As far as I know firmware later than BMJ1 comes with a new bootloader.
You may try to root it using URDLV first before flashing to later firmware using Mobile Odin. Alternatively you may try method in post 8
williamyi said:
Which firmware are you in now? As far as I know firmware later than BMJ1 comes with a new bootloader.
You may try to root it using URDLV first before flashing to later firmware using Mobile Odin. Alternatively you may try method in post 8
Click to expand...
Click to collapse
Thanks but it was not a question
For SM-N9005 only
Please do mention that it is only for SM-N9005 only. I hope that N900 gets some good stuff as well
um009 said:
Please do mention that it is only for SM-N9005 only. I hope that N900 gets some good stuff as well
Click to expand...
Click to collapse
Ok done.
joytest said:
Ok done.
Click to expand...
Click to collapse
Also add that this is tested on MJ1 bootloader only. URDLV will definitely trip MJ3 bootloader and above. Dunno about MOP.
Add another to the success stories, still had/have the MJ1 bootloader, now up to MJ7.
Sent from my SM-N9005 using Tapatalk
awww I was actually hoping you mean like flashing a recovery or kernel with mobileodin and keeping the knox 0x0 ;P... too much wishful thinking I guess.....
I was running MI7 firmware with root but after flashing to MJ8 firmware, I lost root. Knox is still 0x0
Can I downgrade the firmware back to MI7 and root it again with RDLV method and then use mobileodin to update firmware?
MCube74 said:
I was running MI7 firmware with root but after flashing to MJ8 firmware, I lost root. Knox is still 0x0
Can I downgrade the firmware back to MI7 and root it again with RDLV method and then use mobileodin to update firmware?
Click to expand...
Click to collapse
MJ8? Are you using HK firmware? Not sure if the bootloader is the same in MJ7 or not, but if they are using a new bootloader, then I believe there is no way to downgrade the bootloader
MCube74 said:
I was running MI7 firmware with root but after flashing to MJ8 firmware, I lost root. Knox is still 0x0
Can I downgrade the firmware back to MI7 and root it again with RDLV method and then use mobileodin to update firmware?
Click to expand...
Click to collapse
No..you cannot as you already have new bootloader when your flash the MJ8 firmware. Even if you use RDLV..you will still trip your Knox as RDLV meant to those who still on the old bootloader.
MCube74 said:
I was running MI7 firmware with root but after flashing to MJ8 firmware, I lost root. Knox is still 0x0
Can I downgrade the firmware back to MI7 and root it again with RDLV method and then use mobileodin to update firmware?
Click to expand...
Click to collapse
If you flashed the MJ8 file as it comes straight from Samsung then no, you can't downgrade without triggering the Knox counter.
If it was a URDLV version then yeah.
Sent from my SM-N9005 using Tapatalk
Hey Guyz,
This is a rooting and upgrading guide for the SAMSUNG GALAXY NOTE 3 SM-N9005 (INTL). This is for people with MJ1 or lower AP versions ONLY.
Please make sure you have the latest Samsung USB Drivers installed. To get it please install KIES or use google.
AP: N9005XXUBMJ1
CP: N9005OJVBMI2
MODEM: N9005XXUBMJ1
After the Upgrade my AP version is:
AP: N9005XXUDMJ7
CP: N9005XXUDMJ7
MODEM: N9005OJVDMJ4
These were my settings when I got my phone. I rooted my phone using the URDLV Method. (Credits go to DESIGNGEARS).
For rooting with URDLV (ONLY FOR MJ1 OR LOWER AP).
Please download the URDLV Script, ODIN v3.09 and SD CARD files. (Attached at the bottom)
Download your FIRMWARE from http://www.sammobile.com
Cook your firmware using these steps:
Also make sure you do not have an External SD card inside.
1). Place the TAR.MD5 file after extracting the Zip to the root of your C Drive.
2). Open up a command prompt in the URDLV directory. To do this, hold the right shift key and right-click on the screen and click open command window here.
3). Input the complete command (without Quotes) "urdlv full C:\XXXX.tar.md5" (where XXXX is the name of your firmware).
4). Wait for the process to complete.
5). It will create another TAR.MD5 file with the name XXXX_VEGA.tar.md5.
6). Put your phone into Download Mode
7). Flash the firmware using ODin v3.09 and placing it under the AP tab.
Now make sure you have adb setup and enter download mode and connect your phone with ODIN v3.09.
In the AP tab just locate your XXXX_VEGA.tar.md5 file and flash your firmware.
8). Reboot your phone. (Very Important).
9). Place the root_de_la_vega.sh files into the Phone Storage.
i.e: Extract the files and place them directly into the root of the Phone Storage (Internal Memory).
My Computer/Myphonename/Phone/root_files
My Computer/Myphonename/Phone/root_de_la_vega.sh
10). Reboot (Very Important).
11). After reboot delete the root_files folder and the root_de_la_vega.sh files from the Phone Storage (Internal Memory).
12). Reboot Again. (Very Important).
13). Viola..... You now have root.
Please note this is only for MJ1 or lower firmwares. I have not tried it with MJ7 or greater firmwares.
Now to upgrade your phone. Please follow these steps to MJ7 or greater.
Please note that for my region MJ7 is currently the latest and I have done it only with that.
Also No, data will be wiped and you will have root + latest baseband and Firmware.
Install Mobile ODIN Pro v3.85 and upgrade the addon and after the upgrade of Mobile ODIN Pro, a popup will come up stating that you can trip KNOX. Disregard it.
Now, you should have already downloaded your MJ7 or greater firmware.
Please place it in the INTERNAL MEMORY(PHONE STORAGE).
Click the "Open File" option and locate your latest firmware. (Please make sure it is in TAR.MD5 Format). (If not then unzip and place it there).
And have the following options checked.
1). Everroot
2). SuperSU
3). Inject Mobile ODIN Pro
And click Flash Firmware.
That's it. Keep your fingers crossed and enjoy.
Once you have gained root and your KNOX Warranty Counter is 0x0. HIT THANKS.
Download your MJ7 Firmware and Flash it via Mobile ODin Pro v3.85. (Download it from Playstore - Credits to Chainfire for this).
Please note that I havent tested upgrading again after this method as their is currently no update for me. If someone can confirm that it still works after upgrading once, I will appreciate it.
This will not update your bootloader
Disclaimer: I'm not responsible for anyone using this guide. If you trip your KNOX Counter then you are out of luck. I can in no way be held responsible. Use this guide at your own risk.
DOWNLOAD:
ODin v3.09
Root De La Vega SD Card Files
URDLV Script
Device Info APK
Credits to Chainfire, Design Gears and all other great developers out their. If I forgot something please leave a comment and I will update the guide.
Credits to this thread SUCCESS !!! Knox 0x0 with Mobile Odin Pro 3.85 !!! By JoyTest
Please hit "Thanks" if I have helped. It takes a few seconds to say thanks, but days/weeks to write a guide.
This guide was written by XxXKINGMAKXxX
My firmware is N9005XXUBMJ2, can I not use this? Thanks
From what I know, MJ2 has the same bootloader as MJ1. So it can most definitely work. Please do not use OTA Updates to update your phones. Only download the Complete firmware and flash it.
MJ3 onwards have been reported to have bootloader upgraded and you can potentially trip KNOX.
This is all the information I have been able to gather from XDA
Yes you can. But at your own risk
From what I know, MJ2 has the same bootloader as MJ1. So it can most definitely work. Please do not use OTA Updates to update your phones. Only download the Complete firmware and flash it.
MJ3 onwards have been reported to have bootloader upgraded and you can potentially trip KNOX.
This is all the information I have been able to gather from XDA
Hi mate, i my firmware N9005XXUBMJ1, after used script URDLV it created a file name like this "N9005XXUBMJ1_N9005OLBBMI3_N9005XXUBMJ1_HOME_CSC.tar.md5" and the size only 88mb. Its posibble or there are something wrong of what i'm doing?.
#01. Is it possible update via Kies after doing a root and upgrading to latest rom (not custom) or I always have to do it manually?
#02. After I had done root, is there chance to trip Knox?
#03. Do I have to select my country vendor & rom from SamMobile, or I can select any of newest from other vendors?
#04. Can I do a root if my bootloader is locked?
THX
You have to do it manually or else you can trip knox.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Rizalh75 did you first extract the firmware from the zip file ? And use the proper commands ?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Btw if people use this method. They will not upgrade their bootloader and it will be at MJ1 OR LOWER. Now you can keep upgrading without tripping knox. I will add this post to the guide once I reach home
Sent from my SM-N9005 using XDA Premium 4 mobile app
Yes you must select from all the four scroll tabs in the sammobike website or else you will most likely brick your phone.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Very nice... THX...
So, still, if my Write Protection is: Enable (I can asume that is bootloader), I can still root my Note 3 & get a custom rom, or am I wrong?!
Thank you very much! I'm going to try this out later
Sent from my SM-N9005 using Tapatalk
XxXKINGMAKXxX said:
Rizalh75 did you first extract the firmware from the zip file ? And use the proper commands ?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sir, yes of course i did extract the zip file that i downloaded from sammobile. Maybe something missed when i'm did in command. I'll try again after work. Anyway i liked your guide to help this communities. :good:
Hi, how can I know the version of my bootloader? I think I have mj8 or mj4, how can I be sure?
Thnx in advice
Enviado desde mi SM-N9005 mediante Tapatalk
Well for most of the people. If you have followed this method while having previous roms of MJ1 or lower then performing this will not at all upgrade your bootloader
Well write protection is something that I think shouldn't be a cause of any problems.
To check your bootloader plz download Device Info from play store as it is free and it will let you know which bootloader you have.
This guide can be used for further upgrades too.(hopefully)
Sent from my SM-N9005 using XDA Premium 4 mobile app
Please do not opt for custom roms other than the VEGA roms that are created as you will for 100% trip knox unless the custom rom is a modified VEGA rom
Sent from my SM-N9005 using XDA Premium 4 mobile app
Dear OP,
I must highlight that you need to credit this thread http://forum.xda-developers.com/showthread.php?t=2522729 for the Mobile Odin Pro flashing of MJ7. This is the "SUCCESS !!! Knox 0x0 with Mobile Odin Pro 3.85 !!!" thread
As far as I'm aware, MOP flashing to retain Knox 0x0 was first tested by users in Malaysia, especially @williamyi, and the steps for MOP flashing from MJ1 to MJ7 were also written by him first.
Please credit the thread in your credits in addition to all the great devs who made this all possible.
XxXKINGMAKXxX said:
Well for most of the people. If you have followed this method while having previous roms of MJ1 or lower then performing this will not at all upgrade your bootloader
Well write protection is something that I think shouldn't be a cause of any problems.
To check your bootloader plz download Device Info from play store as it is free and it will let you know which bootloader you have.
This guide can be used for further upgrades too.(hopefully)
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
now I see, I have the mj8 bootloader, to root I have to trip knox? how to do it?
thnx a lot
XxXKINGMAKXxX said:
Hey Guyz,
This is a rooting and upgrading guide for the SAMSUNG GALAXY NOTE 3 SM-N9005 (INTL). This is for people with MJ1 or lower AP versions ONLY.
Please make sure you have the latest Samsung USB Drivers installed. To get it please install KIES or use google.
AP: N9005XXUBMJ1
CP: N9005OJVBMI2
MODEM: N9005XXUBMJ1
After the Upgrade my AP version is:
AP: N9005XXUDMJ7
CP: N9005XXUDMJ7
MODEM: N9005OJVDMJ4
These were my settings when I got my phone. I rooted my phone using the URDLV Method. (Credits go to DESIGNGEARS).
For rooting with URDLV (ONLY FOR MJ1 OR LOWER AP).
Please download the URDLV Script, ODIN v3.09 and SD CARD files. (Attached at the bottom)
Download your FIRMWARE from http://www.sammobile.com
Cook your firmware using these steps:
Also make sure you do not have an External SD card inside.
1). Place the TAR.MD5 file after extracting the Zip to the root of your C Drive.
2). Open up a command prompt in the URDLV directory. To do this, hold the right shift key and right-click on the screen and click open command window here.
3). Input the complete command (without Quotes) "urdlv full C:\XXXX.tar.md5" (where XXXX is the name of your firmware).
4). Wait for the process to complete.
5). It will create another TAR.MD5 file with the name XXXX_VEGA.tar.md5.
6). After this, place the root_de_la_vega_sdcard_files inside the phone directory.
i.e: Extract the files and place them directly into the root of the Phone Storage (Internal Memory).
My Computer/Myphonename/Phone/root_files
My Computer/Myphonename/Phone/root_de_la_vega.sh
7). Reboot your phone. (Very Important).
8). After reboot delete the root_files folder and the root_de_la_vega.sh files from the Phone Storage (Internal Memory).
9). Reboot Again. (Very Important).
10). Viola..... You now have root.
Now make sure you have adb setup and enter download mode and connect your phone with ODIN v3.09.
In the AP tab just locate your XXXX_VEGA.tar.md5 file and flash your firmware.
Please note this is only for MJ1 or lower firmwares. I have not tried it with MJ7 or greater firmwares.
Now to upgrade your phone. Please follow these steps to MJ7 or greater.
Please note that for my region MJ7 is currently the latest and I have done it only with that.
Also No, data will be wiped and you will have root + latest baseband and Firmware.
Install Mobile ODIN Pro v3.85 and upgrade the addon and after the upgrade of Mobile ODIN Pro, a popup will come up stating that you can trip KNOX. Disregard it.
Now, you should have already downloaded your MJ7 or greater firmware.
Please place it in the INTERNAL MEMORY(PHONE STORAGE).
Click the "Open File" option and locate your latest firmware. (Please make sure it is in TAR.MD5 Format). (If not then unzip and place it there).
And have the following options checked.
1). Everroot
2). SuperSU
3). Inject Mobile ODIN Pro
And click Flash Firmware.
That's it. Keep your fingers crossed and enjoy.
Once you have gained root and your KNOX Warranty Counter is 0x0. HIT THANKS.
Download your MJ7 Firmware and Flash it via Mobile ODin Pro v3.85. (Download it from Playstore - Credits to Chainfire for this).
Please note that I havent tested upgrading again after this method as their is currently no update for me. If someone can confirm that it still works after upgrading once, I will appreciate it.
Disclaimer: I'm not responsible for anyone using this guide. If you trip your KNOX Counter then you are out of luck. I can in no way be held responsible. Use this guide at your own risk.
DOWNLOAD:
ODin v3.09
Root De La Vega SD Card Files
URDLV Script
Credits to Chainfire, Design Gears and all other great developers out their. If I forgot something please leave a comment and I will update the guide.
Please hit "Thanks" if I have helped. It takes a few seconds to say thanks, but days/weeks to write a guide.
This guide was written by XxXKINGMAKXxX
Click to expand...
Click to collapse
From your instruction, you said flashing the XXXX_Vega.tar after you delete the root files from sdcard?? Why would you flash again if you have rooted.
From what i read from DESIGNGEARS thread, we have to flash the XXXX_Vega.tar first, then copy those 2 files into sdcard, restart, delete those 2 files, restart, then viola you have rooted...
I have added the credits to the thread as well.
You first gain root on the older MJ1 or lower bootloader and then flash the original New (or updated) firmware from sammobile using Mobile ODin pro.
EDIT: The guide needed editing, it was mistake on my part. You only need to flash the VEGA Rom only once.
Thus you end up with the old bootloader and yet you have root and the latest firmware as well as all your data is safe without getting wiped.
For MJ8 bootloader, You can try it at your own risk. Since the VEGA Root only works for MJ1 or lower bootloaders (though this is a speculation) you can still give it a try and post your results and help me in updating the GUIDE at the very same time.
Sincerely,
XxXKINGMAKXxX
So today Kitkat update for Samsung Galaxy Note 3 SM N9005 has leaked and to update and download we have made a simple and short guide.
NOTE
-Your data will be wiped. So, back it up!
- You are doing this at your OWN risk. We are not responsible if you brick your device or your cat eats your phone.
- It will NOT increase your binary counter NOR void your warranty.
- This test firmware is a pre-release build and not official from Samsung.
Download
N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX.zip
Odin3_v3.09.zip
INSTRUCTIONS
Step 1
Extract (unzip) the firmware file
Extract Odin v3.09.ZIP file
Step 2
Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
Step 3
Connect phone and wait until you get a blue sign in Odin
Step 4
Add AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 to AP
Add BL_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 to BL
Add CP_N9005XXUENA2_REV03_CL1277177.tar.md5 to CP
Add CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar.md5 to CSC
Note No need to update bootloader as suggest in #2
Step 5
Make sure re-partition is NOT ticked
Step 6
Click start button, relax and wait a few minutes and phone will restart.
ENJOY YOUR KITKAT NOTE 3
CREDITS: EASY HOWTO UPDATE NOTE 3 to latest leaked kitkat build
Please remove the BL step or people will be stuck in 4.4.2 leak without being able to revert.
Has anybody tried on a US Carrier Device?
Sent from my SM-N900T using Tapatalk
Skander1998 said:
Please remove the BL step or people will be stuck in 4.4.2 leak without being able to revert.
Click to expand...
Click to collapse
This ^^^
Upgrading bootloader means you cannot revert to 4.3! -- EDIT: You MUST upgrade bootloader to install this
from the 'leaked kitkat' thread, it seems that if you dont flash BL step, this updated wont work and will cause errors.
http://forum.xda-developers.com/showthread.php?t=2608178&page=18
:highfive:
aliguu said:
from the 'leaked kitkat' thread, it seems that if you dont flash BL step, this updated wont work and will cause errors.
http://forum.xda-developers.com/showthread.php?t=2608178&page=18
:highfive:
Click to expand...
Click to collapse
Yup 100% confirmed, Need Bootloader to install KK
radicalisto said:
Yup 100% confirmed, Need Bootloader to install KK
Click to expand...
Click to collapse
ok updated
Sir,
I'd like to ask. I just updated my device to 4.4. I noticed that it is no longer rooted.
I tried rooting again my device, but it is not working because of bootlooping problem.
Is there any remedy for this in order for me to be able to root my 4.4 device?
Thanks in advance.
Have you got the right cf autoroot file? - if not head over to chainfire.eu and grab the latest for Kitkat
Sent from my SM-N9005 using XDA Premium 4 mobile app
Skander1998 said:
Please remove the BL step or people will be stuck in 4.4.2 leak without being able to revert.
Click to expand...
Click to collapse
BL step is a must! without update the BL, your flash will fail and phone stuck.
KitKat 4.4.2 ROM must update the BL and they is no chances revert back to older 4.3 ROM.
Andrewtst said:
BL step is a must! without update the BL, your flash will fail and phone stuck.
KitKat 4.4.2 ROM must update the BL and they is no chances revert back to older 4.3 ROM.
Click to expand...
Click to collapse
That was corrected shortly after - I'm aware of this.
why did you guys need to update BL ??! i was on MJ7 and just went to Sammobile got the file and simpley flash it with odin now my phone is on kitkat :good: maybe because you were not in MJ7 hmm ??
btw how to root this kitkat version ??? konx doesn't matter.
I've just downloaded the Firmware from here http://www.sammobile.com/2014/01/13/breaking-android-4-4-2-kitkat-rolling-out-to-galaxy-note-3-sm-n9005/ and flashed it. Now Im on KitKat WITHOUT WIPING DATA! All My Apps,Music,Photos..are still there
hapticc said:
So today Kitkat update for Samsung Galaxy Note 3 SM N9005 has leaked and to update and download we have made a simple and short guide.
NOTE
-Your data will be wiped. So, back it up!
- You are doing this at your OWN risk. We are not responsible if you brick your device or your cat eats your phone.
- It will NOT increase your binary counter NOR void your warranty.
- This test firmware is a pre-release build and not official from Samsung.
Download
N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX.zip
Odin3_v3.09.zip
INSTRUCTIONS
Step 1
Extract (unzip) the firmware file
Extract Odin v3.09.ZIP file
Step 2
Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
Step 3
Connect phone and wait until you get a blue sign in Odin
Step 4
Add AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 to AP
Add BL_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 to BL
Add CP_N9005XXUENA2_REV03_CL1277177.tar.md5 to CP
Add CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar.md5 to CSC
Note No need to update bootloader as suggest in #2
Step 5
Make sure re-partition is NOT ticked
Step 6
Click start button, relax and wait a few minutes and phone will restart.
ENJOY YOUR KITKAT NOTE 3
CREDITS: EASY HOWTO UPDATE NOTE 3 to latest leaked kitkat build
Click to expand...
Click to collapse
Even easier just download this http://live.samsung-updates.com/det...e_3_Snapdragon/SM-N9005/XEO/N9005XXUENA6.html
step to unzip and open odin 3.07 or 1.85
put in pda
flash and all is good!
Do you sure this way OK with Note 3 N9005 16G HongKong ver?
Please continue any discussion here. Thanks.
Hello Everybody.
I have finally successfully rooted Note 3 N9005 on Android 5.0 Dev Base (DB) only, without tripping knox. The Dev base (DB) is made or compiled by Alexander on OB6 (the latest firmware). It has Multi-CSC feature and hence you will not have to worry about the CSC feature being a reason for holding you back from Rooting Note 3 N9005.
Disclaimer: I am not responsible if you mess up any of the steps and neither am I responsible for anyone bricking their phone. I have personally tested this step 3 times over to confirm its validity.
UPDATE: We have finally been able to root all LOLLIPOP without dev base. The new guide is on its way. All your data can remain, you will be able to root without having to worry about losing your DATA.
UPDATE: Here is the link to my ROM, you can replace this rom with Alexander's Dev Base in the Instruction Steps and all will be fine.
:: MEGA DOWNLOAD ::
:: DROPBOX DOWNLOAD ::
UPDATE: Added updated Links for Alexander DevBase, Bootloader and CP File.
NOTE: KNOX apps have been disabled by default by Alexander himself. Thank you Alexander.
NOTE: Moderators please move this thread to the right section. Also, please note, I will be giving credits to the original Devs for the rom and the root methods which I used common sense and made them work. All these changes will be released in the final Guide. In a few hours the whole guide with the complete step-by-step procedure will be uploaded here.
NOTE: I have written this guide on my own and have not copied anything from anywhere except the rooting process provided by W0lfDroid. If required, I will remove it and replace it with the link to the page to make it easier. But, in my opinion my steps are simpler
Things you will need.
Precautionary step: Make a backup of your PIT File just in case. You might need it though I had no need for it and its simply taking up a few KBs of Space on my PC
1). Official Stock 4.4.2 Firmware. (Grab it via Sammobile).
2). N9005XXUGBOEA_DevBase_alexndr.zip (Grab it HERE).
3). ODin v3.09. (Grab it HERE).
4). Mobile ODin Pro. (Buy it and support Chainfire).
5). SuperSU 2.46 APK. (Grab it from Google Playstore).
6). Towel Root APK v3 Offline. (Grab it HERE)
6). Device drivers. (My suggestion would be to just install Kies 2 and Kies 3).
7). ADB should be set up and accessible via CMD.
8). Root Kernel
9). Stock Kernel: NF4, NG1, NG2, NH1, NI4, NJ1, NJ2, ZTFUNJ1, NK1
10). Bootloader File (OEA – Latest as of now).
11). CP File (OD3 – Latest as of now).
Credits:
The Root Kernel and Stock Kernels are all credited to W0lfDroid.
SuperSU, Mobile ODIN Pro 4.20 are credited to Chainfire.
DevBase Rom, Bootloader File, CP File are credited to Alexander.
Towel Root is credited to Geohot.
Instructions:
Part 1: Downgrade 5.0 >> 4.4.2 (Skip this if you have 4.4.2 and move over to Part 2).
Procedure:
1). Run ODin v3.09 as Administrator.
2). Unzip the stock rom zip package that you downloaded for 4.4.2 and you will get a ".TAR.MD5" file. That is the one that you require.
3). Attach your phone in “Download Mode”. To enter this mode, turn off your phone. Press and hold POWER + MENU (Home Button) + Volume Down keys. Then a confirmation dialogue will pop up and ask you to continue to enter the mode by pressing the Volume UP key.
4). Click on AP and select the “.TAR.MD5” file extracted.
5). Make sure only "Autoreboot" and "F.Reset Time" are "checked".
6). Flash the Firmware by clicking "Start".
7). Once flashed, let your phone reboot. Should take about 10-15 mins.
NOTE: If your phone doesn't boot up after a considerable amount of time. Turn it off. Pull out the battery. Re-insert the battery and boot your phone into “Recovery Mode” by holding the Power + Menu (Home Button) + Volume UP keys. Wipe your data and cache partitions.
8). Setup your phone but better not connect it to Google/Samsung/Dropbox or any other accounts because you are going to get those wiped again.
Part 2: Rooting Note 3 on 4.4.2 (Skip this is you have a Rooted 4.4.2 phone and move over to Part 3).
Procedure:
Before starting this find your kernel version and build number, the last 3 letters/digits matter such as NG1 or NH1, etc.
Install SUPERSU 2.46 APK
1). Run Odin v3.09 and connect your phone in “Download Mode”
2). Click AP on the ODin screen and navigate and select the file Root Kernel.
3). “Auto-reboot” and “F.Reset Time” are selected and click “Start”.
4). Let it flash and reboot.
5). Install Towel Root v3 Offline APK.
6). Open the Towel Root APK now and tap “Make it rain”.
7). Install SuperSU from Playstore.
8). Update the SU Binary and Disable KNOX.
9). Reboot your phone.
10). Now flash the Stock Kernel, Follow the same steps 1 – 4 but just replace the Root Kernel with the Stock Kernel to allow you to have full functionality as Wi-Fi gets disabled with the root Kernel.
Part 3: Upgrading to Android 5.0 Lollipop Dev Base Alexander OEA.
Procedure:
1). Install Mobile ODIN Pro 4.20
2). Move the N9005XXUGBOEA_DevBase_alexndr.zip to your Internal SD Card.
3). Run Mobile ODIN Pro and choose the option OTA/Zip Update.
4). Select the N9005XXUGBOEA_DevBase_alexndr.zip file.
5). Uncheck (untick) the “Everroot” Option.
6). Flash Firmware. If it asks to verify the checksum let it, if it does not then don’t worry.
7). Let Mobile ODIN Pro do it’s thing.
8). The Aroma Installer will pop up. Leave every option as-is. The only extra options we have to select are “Wipe Data” and “Update Stock Recovery”.
9). Let it install.
10). Uncheck (untick) the “Reboot Device” option.
11). If your phone reboots, then let it start up and then DO NOT set up your phone, just hold the power button and turn it off.
12). Enter “Download Mode”.
13). Run ODin v3.09 and click on BL and select the OEA Bootloader File and click on CP and select the OD3 CP File.
14). Make sure Auto-reboot is not checked.
15). Now, hold down the power key and turn off your phone.
16). Boot into “Recovery Mode” by holding the POWER + MENU (HOME BUTTON) + VOLUME UP keys. You will see a msg at the bottom Applying Multi-csc which is essential to prevent your phone from entering boot-loop or crashing after the Samsung LOGO.
17). “Wipe Data/Factory Reset” and “Wipe Cache Partition”.
18). Reboot your phone and set it up. But DO NOT install any app, my opinion or suggestion is not to connect your google account just yet.
19). After the phone has booted, open play store and connect your GMAIL Account and install Root Checker from Playstore.
20). Do not open any app and do not install anything.
21). Turn off your phone and wait for 2 – 5 mins.
22). Turn it back on and open Root Checker and grant it SU permission.
23). Then open SuperSU, update the binary if asked and set it up as you like.
24). Have fun, you now have a Rooted Lollipop 5.0 Phone on the latest Build Number OEAwithout Tripping KNOX
Updated and Maintained as of 19th June 2015.
Consider buying me a couple of beers for my contribution
Nice job! I was waiting for this to update my note 3 to use new kernels. Is it possible to compile the same thing for n900w8, NB7 ? http://www.sammobile.com/firmwares/download/26653/N900W8VLUCNB7_N900W8OYACNB7_BMC/
Thanks a lot
I think my team has been able to come up with the solution.
patate331 said:
Nice job! I was waiting for this to update my note 3 to use new kernels. Is it possible to compile the same thing for n900w8, NB7 ? http://www.sammobile.com/firmwares/download/26653/N900W8VLUCNB7_N900W8OYACNB7_BMC/
Thanks a lot
Click to expand...
Click to collapse
We are trying to figure this out. If we can get this kind of rom for any phone then we will have better luck getting all lollipop phones rooted. Also I'm in the process of getting the official stock firmware installed on top of this to allow us to have official kernel installed to. But I might just flash the original kernel to avoid the hassle and check it out
XxXKINGMAKXxX said:
We are trying to figure this out. If we can get this kind of rom for any phone then we will have better luck getting all lollipop phones rooted. Also I'm in the process of getting the official stock firmware installed on top of this to allow us to have official kernel installed to. But I might just flash the original kernel to avoid the hassle and check it out
Click to expand...
Click to collapse
Nice! Sounds very good. If I understand everything about your developpement, we will be able to root it but not to flash custom rom without tripping. Is that right?
patate331 said:
Nice! Sounds very good. If I understand everything about your developpement, we will be able to root it but not to flash custom rom without tripping. Is that right?
Click to expand...
Click to collapse
Well yes. Flashing a stock rom with pre-root seems like the only case right now.
Sounds good enough for me! Awesome what you guys did, keep up the good work!
UPDATE
All variants (possibly) root knox 0x0
Thanks. worked like a charm. Just 1 suggestion. After point (14). Make sure Auto-reboot is not checked.) you can add "start odin flash" to avoid confusion. IMHO.
Yes very true. I will add it.
Also please note that I have tripped my knox in the learning process and will not continue any new guides regarding knox 0x0.
I'm quite satisfied and will now move forward towards hardcore development of Custom ROMS or development of stock ROMS with addition to more development of apps.
Check for new updates regarding new development apps that I am working on. I hope these apps become a game changer
thnks a ton KINGMAK.
Hey is there a way to saferoot stock Lollipop ROM rather than using the dev based one? Will u post a guide on that regardless of the post u added recently that u wont write guides on knox 0x0, since ur Knox is tripped I am eagerly waiting for that guide frnd.
Also, how to enable knox apps, container and all that on this dev based ROM? Is that possible?
If not, will I be able to use Knox apps, container in future? I suppose that a stock ROM should be flashed to get that. Is that?
sword_fish89 said:
thnks a ton KINGMAK.
Hey is there a way to saferoot stock Lollipop ROM rather than using the dev based one? Will u post a guide on that regardless of the post u added recently that u wont write guides on knox 0x0, since ur Knox is tripped I am eagerly waiting for that guide frnd.
Also, how to enable knox apps, container and all that on this dev based ROM? Is that possible?
If not, will I be able to use Knox apps, container in future? I suppose that a stock ROM should be flashed to get that. Is that?
Click to expand...
Click to collapse
Yes it is possible. The dev_base is not entirely different from the Stock ROM. You would need to use the same procedure but the only change that would be required is the flashing of the Stock Based ROM.
I can make a rom with KNOX apps enabled but the root in the system will always remove/disable the KNOX apps since knox tries to reset the root.
Since the very beginning of KNOX system, the security is lost when you root your device. KNOX cannot be used and I doubt anyone will ever try to make them work.
Sincerely,
KINGMAK
XxXKINGMAKXxX said:
Yes it is possible. The dev_base is not entirely different from the Stock ROM. You would need to use the same procedure but the only change that would be required is the flashing of the Stock Based ROM.
I can make a rom with KNOX apps enabled but the root in the system will always remove/disable the KNOX apps since knox tries to reset the root.
Since the very beginning of KNOX system, the security is lost when you root your device. KNOX cannot be used and I doubt anyone will ever try to make them work.
Sincerely,
KINGMAK
Click to expand...
Click to collapse
So that means should I add Stock rom from sammy (BOB6.zip) in Mobile Odin pro as mentioned in step 4. of part 3 instead of N9005XXUGBOB6_DevBase_alexndr.zip file?
If so, do i need to flash BOB6's bootloader and modem again via desktop Odin? Plz clarify..
sword_fish89 said:
So that means should I add Stock rom from sammy (BOB6.zip) in Mobile Odin pro as mentioned in step 4. of part 3 instead of N9005XXUGBOB6_DevBase_alexndr.zip file?
If so, do i need to flash BOB6's bootloader and modem again via desktop Odin? Plz clarify..
Click to expand...
Click to collapse
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Thank you. Followed your guide and managed to get Lollipop into my phone with root privileges. Flashed Xposed alpha via mobile odin and now my phone is stucked in a bootloop. Went to recovery to do a factory reset but it is still the same. What should I do to restore my phone?
Would it be fine following part 1 and 2 , although I am running the newest bootloader?
if i already trip my knox 0x1 can it be changed to 0x0 with this method?sorry newbie question
XxXKINGMAKXxX said:
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Click to expand...
Click to collapse
erevoz said:
if i already trip my knox 0x1 can it be changed to 0x0 with this method?sorry newbie question
Click to expand...
Click to collapse
No. This is to preserve 0x0. It won't change 0x1 to 0x0.
arvin2212 said:
Thank you. Followed your guide and managed to get Lollipop into my phone with root privileges. Flashed Xposed alpha via mobile odin and now my phone is stucked in a bootloop. Went to recovery to do a factory reset but it is still the same. What should I do to restore my phone?
Would it be fine following part 1 and 2 , although I am running the newest bootloader?
Click to expand...
Click to collapse
Flash the CP and Bootloader files. Then wipe your data and cache partitions am all should be fine.
Once the whole setup is complete and i wanted to debloat the rom, can i just install thru mop the dev base rom? Is it necessary to do the bl and cp again?
XxXKINGMAKXxX said:
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Click to expand...
Click to collapse
Thnx for the reply KingMak. But i hav few mre doubts.
1. Suppose if i use stock rom bob6.tar.md5 in mobile odin, how do we get that Rom rooted?
Should i tick everroot option and add supersu zip file and then flash to do that?
2. Does dev base (by alexndr) zip package include root installer? Is everroot option unticked for this reason?
3. Can we saferoot(knox 0x0) note 3 sm 9005 using the same method for s4 as posted by xda member Tyxerakias? Plz have a look>> forum.xda-developers.com/galaxy-s4/general/rooted-stock-lollipop-5-0-1-knox-0x0-t3061536
So the idea is this:
I have a rooted S6 920F with 5.1.1 OH2 EUR and engineering bootloader & Unikernel.
1. Being rooted, you flash 6 MM with mobile odin, ticking everroot and reboot into download mode. After this procedure, and while being in download mode, you have a 6.0.1 rooted, with an engineering bootloader.
2. Using Odin, you flash the official bootloader of 6.0.1 by extracting it from the tar file.
3. Reboot, and you have a 6.0.1 rom with official bootloader and kernel.
jastonas said:
So the idea is this:
I have a rooted S6 920F with 5.1.1 OH2 EUR and engineering bootloader & Unikernel.
1. Being rooted, you flash 6 MM with mobile odin, ticking everroot and reboot into download mode. After this procedure, and while being in download mode, you have a 6.0.1 rooted, with an engineering bootloader.
2. Using Odin, you flash the official bootloader of 6.0.1 by extracting it from the tar file.
3. Reboot, and you have a 6.0.1 rom with official bootloader and kernel.
Click to expand...
Click to collapse
it worked?
reddevil82 said:
it worked?
Click to expand...
Click to collapse
Never tried it
Sent from my SM-G925F using Tapatalk
It won't work. Here is why;
Here it how KNOX counter works; If the bootloader detects an unsigned bootable image (recovery.img or boot.img) while booting the device, it trips to 1.
We need patch sepolicy since Android 6.0 (since Android 5.1 for Samsung devices) to apply the root which requisites patch the boot.img. Patching the boot.img makes it an unsigned bootable image. So, if we try to boot it, KNOX will trip to 1 anyway.
And there's no way to apply root without patch boot.img on Android 6.0
So, no luck until there's a new engineering bootloader which compaitable with Android 6.0 boot.img.