Procedure for installing stock Samsung Lollipop firmwares with Knox 0x0. (I9505)
You can do the upgrade from your 4.4.2 KitKat, already rooted with Peppe130's method, as described here. You need Mobile Odin Pro and Odin 3.09 for Windows (this is the version that worked for me, I can't say whether different versions work equally well, they might). You also need the bootloader .tar for the version you are installing. The tar needs to include 6 .mbn files, aboot, rpm, tz, and sbl1-3. @ambassadii has included the bootloader .tar for the OB7 firmware in his post here. Then:
Download the firmware you want (e.g. OB7) and the latest SuperSU v.2.46 from @Chainfire's page, and copy both of them on your external SD card.
Factory reset your phone, and only install SuperSU and Mobile Odin Pro from the Play Store (you can obviously backup what you want beforehand with Titanium).
Run Mobile Odin Pro, accept the download of the required file, and then press OTA/Update ZIP and locate the UPDATE-SuperSU-v2.46.zip file you saved on your external SD.
Now press Open File... and choose the .tar.md5 firmware file you also saved a minute ago. Mobile Odin will automatically find and separate the different parts.
Tick only Enable EverRoot, leave the other options (inject odin etc.) unticked. Then press Flash firmware.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It will ask to check the md5 file, say yes. Mobile Odin will then do the job automatically, and will upgrade your firmware to lollipop 5.01, the phone will then enter recovery, and then it will upgrade all your applications (about 215 of them). All this will take about 5 minutes.
After reboot, turn the phone off and enter Download mode. Run Odin 3.09 on your PC and put the bootloader file in the BL field (see picture).
Connect the phone, press Start and wait for the Pass.
After reboot, do another factory reset, and redownload SuperSU from Play Store after you go through the initial setup.
That was all; you now have a clean stock Samsung Lollipop firmware which is rooted, and the Knox flag remains at 0x0.
Two things are remaining,
1) Disable the Knox apps, you can do this with Titanium Backup by freezing all the Knox-related things, or you can delete the files manually (e.g. with adb), the forum is full of Knox-removal instructions..
2)Using a root editor, edit the file /system/build.prop, and change the line ro.securestorage.support=false (it is normally set to =true). This solves various problems related to SELinux, also documented in the forum.
Enjoy your rooted Lollipop phone!
Great work man
can you show us your knox status?
I don't understand it. For using mobile odin pro we need to have root access.. right? Then how can I use mobile odin pro to root my phone when I already don't have root access? Do we need to be on kitkat to do this? Or can we do this on lollipop flashed via odin as well?
khsh97 said:
I don't understand it. For using mobile odin pro we need to have root access.. right? Then how can I use mobile odin pro to root my phone when I already don't have root access? Do we need to be on kitkat to do this? Or can we do this on lollipop flashed via odin as well?
Click to expand...
Click to collapse
Yes, if you read more carefully I say that you have to start from a rooted 4.4.2 (kitkat) phone.
c.ozzy said:
Great work man
can you show us your knox status?
Click to expand...
Click to collapse
Sure, attached
Dear Tyxerakias,
YOU SIR, ROCK!!!!!
After following the procedure, I started with my i9505 UK version at 4.4.2 with no root, KNOX 0x0, and now I have latest and greatest Lollipop with root, Titanium, Mobile ODIN, and KNOX 0x0.
System status Modified is the only giveaway, and as we all know that is easily fixed (mine is more than 1 year out of warranty so I don't give a monkey's arse either way).
But this is a very nicely done hack. Also great thanks, of course, to peppe130.
GREAT WORK!
// Descore
Descore said:
Dear Tyxerakias,
YOU SIR, ROCK!!!!!
After following the procedure, I started with my i9505 UK version at 4.4.2 with no root, KNOX 0x0, and now I have latest and greatest Lollipop with root, Titanium, Mobile ODIN, and KNOX 0x0.
System status Modified is the only giveaway, and as we all know that is easily fixed (mine is more than 1 year out of warranty so I don't give a monkey's arse either way).
But this is a very nicely done hack. Also great thanks, of course, to peppe130.
GREAT WORK!
// Descore
Click to expand...
Click to collapse
Thanks, enjoy it By the way, you should now uninstall Mobile Odin, as it doesn't yet work on Lollipop.
Tyxerakias said:
Procedure for installing stock Samsung Lollipop firmwares with Knox 0x0
You can do the upgrade from your 4.4.2 Jellybean, already rooted with Peppe130's method, as described here. You need Mobile Odin Pro and Odin 3.09 for Windows (this is the version that worked for me, I can't say whether different versions work equally well, they might). You also need the bootloader .tar for the version you are installing. The tar needs to include 6 .mbn files, aboot, rpm, tz, and sbl1-3. @ambassadii has included the bootloader .tar for the OB7 firmware in his post here. Then:
Download the firmware you want (e.g. OB7) and the latest SuperSU v.2.46 from @Chainfire's page, and copy both of them on your external SD card.
Factory reset your phone, and only install SuperSU and Mobile Odin Pro from the Play Store (you can obviously backup what you want beforehand with Titanium).
Run Mobile Odin Pro, accept the download of the required file, and then press OTA/Update ZIP and locate the UPDATE-SuperSU-v2.46.zip file you saved on your external SD.
Now press Open File... and choose the .tar.md5 firmware file you also saved a minute ago. Mobile Odin will automatically find and separate the different parts.
Tick only Enable EverRoot, leave the other options (inject odin etc.) unticked. Then press Flash firmware.
View attachment 3223407 View attachment 3223408 View attachment 3223942
It will ask to check the md5 file, say yes. Mobile Odin will then do the job automatically, and will upgrade your firmware to lollipop 5.01, the phone will then enter recovery, and then it will upgrade all your applications (about 215 of them). All this will take about 5 minutes.
After reboot, turn the phone off and enter Download mode. Run Odin 3.09 on your PC and put the bootloader file in the BL field (see picture).
Connect the phone, press Start and wait for the Pass.
View attachment 3223409
After reboot, do another factory reset, and redownload SuperSU from Play Store after you go through the initial setup.
That was all; you now have a clean stock Samsung Lollipop firmware which is rooted, and the Knox flag remains at 0x0.
Two things are remaining,
1) Disable the Knox apps, you can do this with Titanium Backup by freezing all the Knox-related things, or you can delete the files manually (e.g. with adb), the forum is full of Knox-removal instructions..
2)Using a root editor, edit the file /system/build.prop, and change the line ro.securestorage.support=false (it is normally set to =true). This solves various problems related to SELinux, also documented in the forum.
Enjoy your rooted Lollipop phone!
Click to expand...
Click to collapse
You forgot to specify in the title that this is only for i9505.
Enviado desde mi SM-T520 usando Tapatalk 2
Tyxerakias said:
Yes, if you read more carefully I say that you have to start from a rooted 4.4.2 (kitkat) phone.
Sure, attached
Click to expand...
Click to collapse
You have made typo mistake. In your post, it is written "4.4.2 jelly bean" instead of "4.4.2 kitkat".
Tyxerakias said:
Thanks, enjoy it By the way, you should now uninstall Mobile Odin, as it doesn't yet work on Lollipop.
Click to expand...
Click to collapse
Yeah, thanks for letting me know - I felt a bit stupid as I bought Mobile ODIN Pro yesterday just to do this upgrade with your guide, but then I looked in the Mobile ODIN thread and I can see that Chainfire is working on a new app as a replacement, and will give it FREE to all owners of Mobile ODIN Pro :good:
So I don't feel stupid after all :laugh: What a great community.
Hello, this procedure works with a model I9515 ?
I am on 4.4.2 I9505XXUFMB8 rooted with towelroot only and knox 0x0.
Can I follow this guide or do I have to root again with Peppe130's method ?
Thanks
Plumber_Gr said:
I am on 4.4.2 I9505XXUFMB8 rooted with towelroot only and knox 0x0.
Can I follow this guide or do I have to root again with Peppe130's method ?
Thanks
Click to expand...
Click to collapse
Same question here, i'm on I9505XXUGNF1 towelrooted, may i proceed or do i have to update and/or reroot?
update: if it can help you, i just factory resetted, rerooted and followed instructions, all went smooth and now i'm running lollipop.
i guess it won't be a problem if you have the latest 4.4.2 update (i was on GNF1, previous one)
Plumber_Gr said:
I am on 4.4.2 I9505XXUFMB8 rooted with towelroot only and knox 0x0.
Can I follow this guide or do I have to root again with Peppe130's method ?
Thanks
Click to expand...
Click to collapse
Er... Peppe's method IS towelroot... So no, you don't have to root again.
Sent from my GT-I9505 using Tapatalk
I did the root changing the kernel 4.4.2 for a kernel prior to June, the towelroot work in this kernel. After the root back the kernel of the newest room. It is possible to upgrade to lollipop, change the kernel by the kitkat, use towelroot to root, then return lollipop kernel?
n3n3 said:
I did the root changing the kernel 4.4.2 for a kernel prior to June, the towelroot work in this kernel. After the root back the kernel of the newest room. It is possible to upgrade to lollipop, change the kernel by the kitkat, use towelroot to root, then return lollipop kernel?
Click to expand...
Click to collapse
No it's not.
Sent from my GT-I9505 using Tapatalk
Well .. Whats the advantage of keeping the KNOX 0x0 & rooting ??
** A - R ** said:
Well .. Whats the advantage of keeping the KNOX 0x0 & rooting ??
Click to expand...
Click to collapse
Keeping your warrenty
XDAcube said:
Keeping your warrenty
Click to expand...
Click to collapse
Coz my knox is triggered .. and it every time bootloops for CM rom !! ..
.
currently i'am on danvdh's gpe rom ..
.
i eagerly need cm !!..
leonov said:
Hello, this procedure works with a model I9515 ?
Click to expand...
Click to collapse
can some1 explain, if its working with model i9515???
thanx. in advance.
suemer
** A - R ** said:
Well .. Whats the advantage of keeping the KNOX 0x0 & rooting ??
Click to expand...
Click to collapse
If KNOX is 0x0 you can always flash back to a fully non-rooted stock firmware and hand in to warranty repair. Once KNOX triggers, you can never get back to 0. If you don't care about warranty, or having a "clean" device, then you might as well use CF-Root, which is much easier and faster. But this method rocks as you can get your device back to "pristine" as-new condition, should you ever want to for some reason.
---------- Post added at 01:01 AM ---------- Previous post was at 12:54 AM ----------
suemer said:
can some1 explain, if its working with model i9515???
thanx. in advance.
suemer
Click to expand...
Click to collapse
All of the files used for this root are stock, so if you can find the similar ones for i9515 it should probably work. If you can get root using Towelroot, you can probably do the similar steps but with the firmware and bootloader tar's replaced with the appropriate ones for the i9515. There's no guarantee, but if you start with a rooted 4.4.2 my bet is that it would work.
Related
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
Update: Mobile Odin Pro 4.0+ is fully working with KitKat too! So you can upgrade your 4.3 to 4.4.2 with no problem and flash custom KK ROMS too! Don't forget to upgrade your bootloader though, and be careful, after upgrading you'll have a secure bootloader that will trip Knox if you ever lose root and want to root back again.
ZeAuReLiEn said:
Installing from a rooted 4.3 with knox 0x0 the stock 4.4.2 rooted with Mobile Odin Pro + installing the BL through Odin PC + installing X-Note 8 through Mobile Odin Pro WITHOUT INSTALLING ANY KERNEL OR BOOTLOADER = X-Note 8 with knox 0x0 !
Thanks for the usefull tip !
Click to expand...
Click to collapse
How to do the same:
Mwyann said:
Tested on European phone, not tested on US branded:
Download N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5, N9005XXUENA6_BL-Only.tar.md5 and Odin 3.09. Place the first file in your phone's memory. Do some backups and when you're ready, fire up MOP, load the HOME.tar.md5 in it, enable EverRoot, choose After flashing and select Download mode. Start flashing. When in download mode, hook your phone to the computer, run Odin 3.09, load he BL-Only.tar.md5 in the BL section, check Phone Bootloader Update, uncheck Auto Reset and Start. When Odin says RESET!, turn off your phone, and then press VOL UP+HOME+POWER to run recovery. Wait... and here you go!
Click to expand...
Click to collapse
Hello guys,
I'm posting a new thread as this is an extension of both using Mobile Odin Pro 3.85+ to flash stock firmwares and installing a custom ROM without flashing a custom recovery (preventing tripping knox).
This guide will show you how to flash a custom ROM and keeping Knox at 0x0 (it will NOT revert a 0x1 though, still not possible).
MAKE SURE THE ZIP FILE YOU PLAN TO INSTALL WILL NOT FLASH ANY RECOVERY OR ANY NON-STOCK KERNEL !!!
For your information, I tripped my Knox by flashing a ROM with its "Stock Kernel", which in fact wasn't. So, just to be on the safe side, do NOT flash kernels unless you're 100% sure this is an official and signed kernel. If unsure, just skip kernel installation, and you should be fine!
soloilmeglio said:
sorry the stock kernel was modified in ramdisk to enable init.d .... it will trip knox...
Click to expand...
Click to collapse
Some Aroma installers let you choose before installing, but others just do it without a warning. If you flash a wrong recovery or wrong kernel, you'll be screwed! So be aware of that. If you can, just check what the installer script is doing and remove the offending flashing parts, or ask the ROM's OP.
Also some ROMs (like AOSP) rely on some kernel's functionnalities that are not present in the stock kernel, or use a different version of the kernel. You would need to flash their custom kernel, which will trip Knox. There's nothing you can do about that for now. Same thing if you want to use modified kernel like SElinux permissive or more UC/UV/governor options. Those need a custom kernel, and will trip knox too.
Chainfire said:
Update ZIPs
Support for this means you can flash complete custom ROMs, or simple updates (like SuperSU's distribution ZIP file). This doesn't automatically mean all Update ZIPs are compatible. The environment in Mobile ODIN's temporary recovery is slightly different from CWM or TWRP, this can cause problems in some cases.
Click to expand...
Click to collapse
I'm of course not responsible for what you do. I'm trying to make it clear enough for you to understand, but if you don't fully understand that flashing a wrong recovery/kernel will trip your Knox, then you'd better keep stock.
Also, all this process can be totally reverted simply by flashing a stock ROM, either with MOP or with Odin on your computer (but it will not revert Kn0x of course...).
Anyway, here is the thing...
You need to turn Reactivation Lock off for the whole rooting/flashing part (just to be on the safe side).
First you have to safely root your device, for example with Root De La Vega. There is enough tutorials and how-tos out there, just look by yourself
Then, purchase and install Mobile Odin Pro.
Let's say you want to install a ROM based on firmware version ML2, I recommend (but it's not mandatory) to flash the corresponding stock firmware first (after you've flashed the custom ROM, I think you won't have to do that again, you can always update modem with standalone zip updates). Personally, as no stock ML2 was out at the time of doing this, I just installed MK2 then X-Note ML2 (with stock ML2 kernel), and that was it
Download the ROM from sammobile (choose the right one for your country, if you mix CSC you can trip Knox), load it on the phone's memory or the sdcard, and set up MOP like this (don't pay attention to the warning saying that you will trip Knox by using MOP, it does not if you follow these instructions carefully) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Load the .tar.md5 with the "Open file..." option, check EverRoot, SuperSU, MobileOdin and wipe dalvik cache, and start flashing.
After rebooting, download the custom ROM you wish (for example X-Note), load the zip into the phone's memory or the sdcard, run MOP and set it up like this:
Load the .zip file with "OTA / Update ZIP" this time, uncheck EverRoot (your ROM should be already rooted), uncheck wipe dalvik cache (already done by the ROM installer) and start flashing.
If the Zip is an Aroma installer or similar, you'll be presented to your ROM's installation menu. Here is the most important part, so listen carefully: When asked, choose not to install any recovery, and don't install any custom kernel either (you can still flash stock kernel). Finish the installation, let it reboot, and enjoy your ROM with Knox 0x0
Note: You can also flash any zip mods you want with that method (you just have to put the .zip into "OTA / Update ZIP", uncheck EverRoot and start flashing). Of course, I'll repeat once more, but you still cannot flash any custom recovery nor non-stock kernel (well you can, but then you'll trip Knox).
I'd be glad if we could also do nandroid backup/restores with MOP, that way we wouldn't have to flash a recovery at all
Hit Thanks if this helped you, and of course let us know how it went for you.
Yann
Great, you have made a thread. Thank you!
and2 said:
Great, you have made a thread. Thank you!
Click to expand...
Click to collapse
Time to udpate your signature I guess (and mine too btw).
Mwyann said:
Time to udpate your signature I guess (and mine too btw).
Click to expand...
Click to collapse
Ha, you are right ??
Gesendet von meinem SM-N9005 mit Tapatalk 4
"First you have to safely root your device, for example with Root De La Vega. There is enough tutorials and how-tos out there, just look by yourself "
I am on MJ7 no root. If i use RDLV Knox will become 0x1. What about Chainfire?
this is working in a SG4 i337M?
megatooth said:
"First you have to safely root your device, for example with Root De La Vega. There is enough tutorials and how-tos out there, just look by yourself "
I am on MJ7 no root. If i use RDLV Knox will become 0x1. What about Chainfire?
Click to expand...
Click to collapse
Good question.
AFAIK, Chainfire's auto root on MJ7 and MK2 turns your Knox into 0x1....
So take it easy. Cheers
?
Sent from my NOTE 3 monster
Latest firmware for my country is:
PDA: N9005XXUDMK2
CSC: N9005NEEDML2
MODEM: N9005XXUDMJ7
I want to install X-Note ML2 rom.
How should I do it? First install ML2 firmware without CSC and modem? Or is it even possible to flash only PDA with MOP?
Sent from my SM-N9005 using Tapatalk
piats said:
Latest firmware for my country is:
PDA: N9005XXUDMK2
CSC: N9005NEEDML2
MODEM: N9005XXUDMJ7
I want to install X-Note ML2 rom.
How should I do it? First install ML2 firmware without CSC and modem? Or is it even possible to flash only PDA with MOP?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
You can flash PDA only with MOP, but it will be totally erased when you'll install X-Note, so it's useless. You can upgrade Modem only (if needed) and then flash X-Note directly if you want. I told to flash latest firmware first to get latest official upgrades before going to custom ROM, but that's not mandatory, it depends on what you already flashed.
Mwyann said:
You can flash PDA only with MOP, but it will be totally erased when you'll install X-Note, so it's useless. You can upgrade Modem only (if needed) and then flash X-Note directly if you want. I told to flash latest firmware first to get latest official upgrades before going to custom ROM, but that's not mandatory, it depends on what you already flashed.
Click to expand...
Click to collapse
My point was that I want to install latest X-Note rom and keep my country csc and modem. So can I first flash X-Note ROM and after that flash csc and modem via MOP?
Thanks for your patience
Sent from my SM-N9005 using Tapatalk
piats said:
My point was that I want to install latest X-Note rom and keep my country csc and modem. So can I first flash X-Note ROM and after that flash csc and modem via MOP?
Thanks for your patience
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
X-Note doesn't update Modem anyway. If you want to reflash CSC you can, but I'm quite sure it doesn't change anything either. Not 100% sure but shouldn't be a problem to reflash CSC, nor not reflashing it at all too
Thanks a lot for your information! I was not sure what would change after flashing ROM which is different than your country's latest firmwares. Nor I wasn't sure what MOP could flash. I will test and report back soon when I have enough time
Sent from my SM-N9005 using Tapatalk
Just downloaded Singapore firmware and flashed on Australian Note 3, I cleared the Cache section on MOP and flashed it.It didn't trip Knox.
Installed X-Note and had to choose BTU CSC in aroma installer. Now I have wrong CSC for my region. I'm just wondering would it be possible to flash correct csc for my country via odin?
Sent from my SM-N9005 using Tapatalk
How did you guys get Mobile Odin to work? When I try to run it, it says device not supported.
Sent from my SM-N900T using Tapatalk
nyflyguy said:
How did you guys get Mobile Odin to work? When I try to run it, it says device not supported.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Install mobile odin and then reboot.
tobia996 said:
Install mobile odin and then reboot.
Click to expand...
Click to collapse
Tried but still can't get Odin to load up. Cdn note3
imsiin said:
Tried but still can't get Odin to load up. Cdn note3
Click to expand...
Click to collapse
You're rooted, right ? (And Odin has root priviledges). You have a genuine device, not a clone?
Mwyann said:
You're rooted, right ? (And Odin has root priviledges). You have a genuine device, not a clone?
Click to expand...
Click to collapse
I hope to God it's genuine lol I got it from best buy through Rogers.. Yes rooted and odin does have privileges. Thx
Sent from my SM-N900W8 using Tapatalk
imsiin said:
I hope to God it's genuine lol I got it from best buy through Rogers.. Yes rooted and odin does have privileges. Thx
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
nyflyguy said:
How did you guys get Mobile Odin to work? When I try to run it, it says device not supported.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Not sure it will work on SM-N900W8 or SM-N900T though, I only tested this on my SM-N9005. Check the compatibility between your device and MOP.
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.
WARNING! ONLY USE THIS ON THE GT-I9192 MODEL!
hello there,
this is my first post here..
This is a guide to root s4mini gti9192 with 4.4.2 SAMSUNG STOCK ROM
don't try this on any other models, I don't know what happens!!
if you want to root s4mini with 4.2.2 rom visit:
guide1 to root 4.2.2 guide 2click to see how to root gti9192 4.2.2 (youtube)
Now to ROOT the 4.4.2 rom
well you may be wondering why cant to you root with the old recovery via odin?? well i tried to flash with clockworkmode recovery and odin failed... i dont know it may work for you...
ALSO You cant DOWNGRADE to the earlier 4.2.2 now.. as xda senior member @F4k told
AFAIK you can't downgrade to ROM with different knox bootloader version, you can only downgrade to a 4.2.2 ROM if that ROM have the same knox bootloader.
AFAIK KitKat stock ROMs have knox bootloader 2.0, so you need find any other 4.2.2 ROM with this bootloader version.
Click to expand...
Click to collapse
downloadthe rom from Russian Firmware gt i9192 click to download
no problems will be there flashing with odin
for more info how to flash click: http://forums.androidcentral.com/ambassador-guides-tips-how-tos/300296-guide-samsung-how-flash-stock-rom-via-odin.html
After flashing the rom download these files
Cf root by chainfire
Super SU vr 2.01 by Chainfire
Philz touch recovery
so first copy the super su file into your sdcard
Then Plug into Odin mode( by holding volume down+lock+home key)
you must found the odin in the cfroot.zip you downloaded earlier.. open it as administrator
connect your phone, switch to download mode by pressing volume up (you can see that in the screen).
select PDA and select that CF-Auto-Root-serranods-serranodsxx-gti9192.tar.md5 and select start.
your phone must restart
before restarting hold volume up+home+lock buttons and enter into recovery
select install update from sd card, and select that supersu that you have downloaded earlier ..
after that boot phone normally and you will see that supersu is installed, open it and select YES to the option to disable knox..
Now to install the recovery..
Actually you can do this anytime...
switch phone back to odin mode (download mode) and select PDA in odin again,
this time select that philz recovery and click start
SUCESS you must have phils touch recovery by now..
i dont know any other recoveries may work or not.. test and post it if you find any..
actually i haven't worked much behind this methods.. all thanks goes to
F4k
alexax66
SilviuMik
without you guys nothing will be possible :good:
Thanks for this manual, but one question: what happened with the knox flag? After flash 4.4.2 i have 0x0.
mariockr said:
Thanks for this manual, but one question: what happened with the knox flag? After flash 4.4.2 i have 0x0.
Click to expand...
Click to collapse
if your knox status is 0x0 that means you haven't triggered the knox bootloader yet.. it becomes 0x1mainly when you try to downgrade
refer to this: http://forum.xda-developers.com/showthread.php?t=2447832
Thanks for the guide
mariockr said:
Thanks for this manual, but one question: what happened with the knox flag? After flash 4.4.2 i have 0x0.
Click to expand...
Click to collapse
This root method will trigger Knox
fburgos said:
Thanks for the guide
This root method will trigger Knox
Click to expand...
Click to collapse
yeah it will,
i think he has just flashed the official update..
Yes i flash only official rom for rusia, i flash with odin. Now i want root, and don't need costom recovery, only root if posible without knox flag.
mariockr said:
Yes i flash only official rom for rusia, i flash with odin. Now i want root, and don't need costom recovery, only root if posible without knox flag.
Click to expand...
Click to collapse
sure, you can root by reading the guide..if you don't need recovery skip that part.. use cfroot then flash supersu..
I suggest you use a custom recovery because it will be useful many times..
I don't think you Can root without tripping the knox flag.. sorry for that case, anyway I heard Samsung's many service centers don't care about knox at all..
and if you need repair or something because of a brick, you can flash the firmware back again...
It seems that my knox is still 0x0 after upgrading from SilviuMik rom to Russian 4.4.2
4.4.2 is working great, I dont have overheating issues, battery with screen 4-4.5h, fast GPS
I had to flash this rom 5 times....yes 5 times ...cos I had bootloop after flashing only 4 times....
Odin always said - successed!!!
qwerty1q said:
It seems that my knox is still 0x0 after upgrading from SilviuMik rom to Russian 4.4.2
4.4.2 is working great, I dont have overheating issues, battery with screen 4-4.5h, fast GPS
I had to flash this rom 5 times....yes 5 times ...cos I had bootloop after flashing only 4 times....
Odin always said - successed!!!
Click to expand...
Click to collapse
I don't know why you have to flash 5 times.. this update have made battery life better, than ever
and knox will be 0x0 after flashing official update because the stock firmware don't seems to be tripping knox
niwia said:
I don't know why you have to flash 5 times
Click to expand...
Click to collapse
neither do I
HI, thanks for the guide. I was able to flash the Russian ROM and root also with no problems but somewhere in the process the Knox has got triggered. Too bad for me .............
I don't know what happen I tried the old method and the CF one with Odin. It wasn't working. So I manually installed supersu and now it is rooted. It seems the method works but the app is not being automatically installed. So just go to play store and install your root app. Worked for me.
mad_hat said:
HI, thanks for the guide. I was able to flash the Russian ROM and root also with no problems but somewhere in the process the Knox has got triggered. Too bad for me .............
Click to expand...
Click to collapse
Hmm rooting does trigger knox... Anyway can't do root without the trigger
Pangadaywalker said:
I don't know what happen I tried the old method and the CF one with Odin. It wasn't working. So I manually installed supersu and now it is rooted. It seems the method works but the app is not being automatically installed. So just go to play store and install your root app. Worked for me.
Click to expand...
Click to collapse
Mmm.. Anyway thanks for sharing the new alternative.... I'll update my post after I get some more confirmation on that methord! Normally the use work
niwia said:
Hmm rooting does trigger knox... Anyway can't do root without the trigger
Click to expand...
Click to collapse
I rooted the previous one running 4.2.2 but Knox did not get triggered but anyway no problems. I really like the Russian ROM - the battery life is superb. And I think that loosing the Knox is not such a problem for me anyway. I wonder if it is of any use on a practical level for the end user.
niwia said:
Hmm rooting does trigger knox... Anyway can't do root without the trigger
Click to expand...
Click to collapse
Rooting doesn't always trigger KNOX.
Take a look here
http://forum.xda-developers.com/showpost.php?p=53200581&postcount=33
Right now I am on CarbonRom 4.4.4 with F4k kernel and my KNOX is still 0x0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you are right. but I think knox vr. 2 is different than before.. although i'm not sure there is another way without triggering it
i used root option in philz recovery without using cf root
but i dont if that the reason i cant change permissions at all from root browser
Sent from my GT-I9192 using XDA Premium 4 mobile app
aness zurba said:
i used root option in philz recovery without using cf root
but i dont if that the reason i cant change permissions at all from root browser
Sent from my GT-I9192 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry, I don't know what you are talking.. english
you must root to use a custom recovery.. else... i don't know what happens
niwia said:
sorry, I don't know what you are talking.. english
you must root to use a custom recovery.. else... i don't know what happens
Click to expand...
Click to collapse
i flashed philz using odin
then there is a root option in recovery, i used it.thats it
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