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.
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
For future use
For future use
{
"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"
}
4.3 bootloader/No knox/no binary count/wi-fi working (Alternative) for Note 2
ONLY FOR THE GT-N7100 INTERNATIONAL MODEL(GSM)
This package is only for devices that still have old bootloaders or are using patched bootloader including wi-fi patches.
SEE POST 2 FOR MORE INFO
1. Download the package from the link.
2. Extract the package.
3. Boot your device into download mode.
4. Flash the final tar via odin PDA mode.
DEVICE WILL ENTER RECOVERY MODE,PRESS THE POWER BUTTON TO REBOOT.
5. Use triangle away to remove the binary if you have it.
This package will not fix already Knox triggered devices.
This will not help you if you already flashed the 4.3 official rom with Knox bootloader.
This package contains 4.3 bootloader, recovery, kernel and modem.
Package will add a new entry to download mode called warranty bit: 0
Package has been tested many times by me.
You will be able to downgrade with this package.
I will not be held responsible for any arising divorces due to you yelling at your device and spending too much time trying to fix it when flashing this package, do so at your own risk. Do not flash if you don't know what i'm on about.
How to use:
Flash this package before flashing any custom 4.3 rom.
Other uses:
Flash this package then a custom recovery, install all your zip update files. Once your done reflash the package and run triangle away to get rid of the binary count.
Now you can have a device with a 4.3 without random reboots, working wi-fi and no binary count.
Thanks to all the XDA users that made this possible.
Package with mj5 bootloader and mj9 modem [BTU] UK
************************************************************************************
Requested Packages with custom Modems
Package with mj5 bootloader and mj5modem
You can find a prior way of achieving the above in this thread by Robalm,Minus recovery and modems.
How to set SELinux from enforcing to permissive
How to set SELinux from enforcing to permissive.
YOUR DEVICE MUST BE ROOTED
First you need SuperSU from chainfire, xposed framework and wanam exposed module.
Download the xposed framework and follow the instructions on how to install it, then install the wanam xposed module and activate it within the xposed framework.
Open SuperSU, go to settings, tick enable SU during boot and tick trust system user.
Open the wanam xposed module and press the security hacks tab and then tick disable SEAndroid box.
Reboot your device.
Your SElinux will now be set to permissive.
http://selinuxproject.org/page/SEAndroid
FAQ:
Package is made simple so you can fix 4.3 bootloops, wifi problems and downgrade to 4.1 without any additional steps.
This is only applicable to devices that have never been flashed with the official 4.3 update.
How to downgrade to 4.1?
Flash the Package then flash the official 4.1 rom
Can i use this package to upgrade to a 4.3 custom rom?
Yes and its a must. Flash it before or after flashing custom rom.
Can i use this package to Set my device to OFFICIAL status?
yes, After flashing it use Triangle away to Fix your Status.
can i flash this if i have problems with wifi on 4.2?
Yes
Can i flash this to fix my boot-loops in 4.3 ?
Yes
Can i use this package with 4.1?
NO!
Can i use this package to revert Knox to X0?
NO.
Will this package Trigger my binary?
No.
Q. I have already flashed a 4.3 custommrom, can i still flash this?
Yes
Package can be also be flashed to any official rom as long you never had a Knox bootloader. (eg. a offical rom flashed by mobile odin.)
Package is not compatible with mobile odin so dont even try, it won’t work.
good news
Thx 4 this. Anyone tried it?
Sent from my GT-N7100 using Tapatalk 2
Doesn't work with mj5 bootloader....... Right?
Obviously with knox counter not active...
Inviato dal mio GT-N7100 utilizzando Tapatalk
Great News
Well done! Is it possible to post a version with only the bootloader?
crisgen said:
Doesn't work with mj5 bootloader....... Right?
Obviously with knox counter not active...
Inviato dal mio GT-N7100 utilizzando Tapatalk
Click to expand...
Click to collapse
the package contains an mj5 bootloader so i guess it will be fine.
TITAN-23 said:
Well done! Is it possible to post a version with only the bootloader?
Click to expand...
Click to collapse
Yes but i rather not post it here to avoid issues/problems (thinking of new users etc)give me a few minutes and i will pm you a link.
Edit.... in order to have reset the binaryi need to include the stock kernel,is this ok or you just want the boot loader?
Thanks so much. Just the bootloader please.
TITAN-23 said:
Thanks so much. Just the bootloader please.
Click to expand...
Click to collapse
Pm sent.
faria said:
Pm sent.
Click to expand...
Click to collapse
thanks for this. could i get the bootloader only as well? id like the fix but keep my current modem. no one seems to deal with the mj4 modem for my region (TPA) thanks.
KoKoMaster said:
thanks for this. could i get the bootloader only as well? id like the fix but keep my current modem. no one seems to deal with the mj4 modem for my region (TPA) thanks.
Click to expand...
Click to collapse
+1
tegben said:
+1
Click to expand...
Click to collapse
if you post your modem i will repackage for you,meanwhile i will send you the link to boot loader only.
Heres link to the mj4 modem I made
https://www.dropbox.com/s/kap2bde6bgv03i2/mj4 modem.zip
I followed the instruction from this link so I hope I did it right
http://forum.xda-developers.com/showthread.php?t=2044937
KoKoMaster said:
Heres link to the mj5 modem I made
https://www.dropbox.com/s/kap2bde6bgv03i2/mj4 modem.zip
I followed the instruction from this link so I hope I did it right
http://forum.xda-developers.com/showthread.php?t=2044937
Click to expand...
Click to collapse
that's fine, it 2 am here, I will do it tomorrow.
Seems will not work with MJ9 bootloader then why the screenshot having MJ9 bootloader?
lontu said:
Seems will not work with MJ9 bootloader then why the screenshot having MJ9 bootloader?
Click to expand...
Click to collapse
Mj5 bootloader mj9 modem.
{
"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"
}
4.3 Stock Firmware for Australian S34G (I9305T) users
WARNING !! DO NOT USE THIS ON ANY OTHER I9305 DEVICE, IT MAY CAUSE PROBLEMS !!
INFORMATION
The official 4.3 Firmware has now been released for the Australian S34G (I9305T).
Here's a safe way to update your phone and not be forced to install the KNOX (4.3) Bootloader.
The whole ROM has been taken apart so you can easily choose what you want to flash.
REQUIREMENTS
- Samsung S34G I9305T
- About 840mb - 1.5gb on your SDCard to copy the files
- Custom Recovery (CWM, Philz, TWRP, Mobile ODIN)
INSTALLATION INSTRUCTIONS
- Copy required zip files to your internal SD Card
- Reboot into recovery
- Perform a full wipe (Optional, but recommended)
- Install ROM
- Reboot and enjoy
If you wish to use addional files, the best order to flash them is this:
Kernel - Recovery - CSC - Odex - KNOX (make sure you used the Odexed KNOX version if you are using the Odex patch)
DOWNLOADS - DVUENC1
Main ROM: DOWNLOAD HERE - MD5: CC0EE566F8BA28FCEC909785898B3D48
- Boeffla 5.3 Beta 3 Custom Kernel *FIXED* (Built 2014-05-20)
- Deodexed, Zipaligned, SU, BusyBox, init.d
- No apps have been removed (except for KNOX protection)
- Extra CSC apps from TEL and XSA added
Odex Patch: DOWNLOAD HERE - MD5: 319A753F4FA8662A2201719BC2660008
- Turns the ROM into an Odexed ROM (like it originally comes stock)
KNOX: DOWNLOAD HERE - MD5: 0232AD5E46E2D812FE25DA851778D4B8
KNOX (Odexed): DOWNLOAD HERE - MD5: 913B85F228BF449A3B9668976ACB64F3
- Use this if you are one of the unfortunate ones with the 4.3 Bootloader
Stock Kernel: DOWNLOAD HERE - MD5: DE1EBF4A99FE6E763F3613B6EF191FA8
DOWNLOADS - DVUEMK4
Main ROM: DOWNLOAD HERE - MD5: 94FC96B7F9136049B3C245971CF3C431
- Boeffla 5.2 Custom Kernel (Built 2014-04-24)
- Deodexed, Zipaligned, SU, BusyBox, init.d
- No apps have been removed (except for KNOX protection)
- Extra CSC apps from TEL and XSA added
Odex Patch: DOWNLOAD HERE - MD5: 017AB49D9144D5581DBD7A55918EB0FB
- Turns the ROM into an Odexed ROM (like it originally comes stock)
KNOX: DOWNLOAD HERE - MD5: 4646030A29E68C8DF1163BC85099D581
KNOX (Odexed): DOWNLOAD HERE - MD5: D9FE90293427C774B5365D82CE9320D9
- Use this if you are one of the unfortunate ones with the 4.3 Bootloader
Stock Kernel: DOWNLOAD HERE - MD5: EA9AAEA3D20F6DD8A59E20A36742942D
DOWNLOADS - OTHER
SDCard Files: DOWNLOAD HERE - MD5: 8B67AFAC39C5D8A223B245898E1CDAC8
- Unpacked hidden.img installed to your SD Card
- Includes data for Navagon plus some sample music and video
Stock Recovery: DOWNLOAD HERE - MD5: 794C3C42C455E9D5C9AB63628A138028
- Just in case anyone needs them
CSC (TEL): DOWNLOAD HERE - MD5: 9C337956C923A9C614327449731278BC
CSC (XSA): DOWNLOAD HERE - MD5: 2D2C9A5DEE10B7F80F10E9C33681ED37
- The specific Australian CSCs. TEL is for Telstra CSC, and XSA is for the generic Australian CSC.
- With some recoveries, you may have to manually mount the /system partition as these original CSC files don't seem to do that automatically
Modem (DVUEML1): DOWNLOAD HERE - MD5: E6B263802912EF2B43759B31D336FED2
Modem (DVUEMK2): DOWNLOAD HERE - MD5: 561DFD09A7011566B63E406354526C8E
Modem (DVUENC1): DOWNLOAD HERE - MD5: DB088658B5025D679721EA66FB42E690
- DVUEML1 and DVUENC1 came with the TEL Firmware, and DVUEMK2 came with the XSA Firmware.
Reserved...
Cheers man!:good::laugh:
Added the OPS CSC
djb77 said:
[
ORIGINAL ODIN FILES
These should only be used for development purposes, or if you have already installed a previous 4.3 Firmware on your phone via ODIN
I9305TDVUEMK4-TEL - DOWNLOAD HERE
I9305TDVUEMK4-XSA - DOWNLOAD HERE
Click to expand...
Click to collapse
what's the difference with the 2 odin files?
Thanks heaps by the way
billyhoyle said:
what's the difference with the 2 odin files?
Thanks heaps by the way
Click to expand...
Click to collapse
Different CSC's in them.
djb77 said:
Different CSC's in them.
Click to expand...
Click to collapse
Sorry for the stupid questions -
CSCs?
Does it matter which I flash?
billyhoyle said:
Sorry for the stupid questions -
CSCs?
Does it matter which I flash?
Click to expand...
Click to collapse
Use the TEL CSC if you're a Telstra user, OPS for Optus, and XSA for Australian generic.
Like I said before, DONT flash the ODIN files unless you already have previously flashed a 4.3 FW via ODIN. Use the zips I made instead.
djb77 said:
Use the TEL CSC if you're a Telstra user, OPS for Optus, and XSA for Australian generic.
Like I said before, DONT flash the ODIN files unless you already have previously flashed a 4.3 FW via ODIN. Use the zips I made instead.
Click to expand...
Click to collapse
Thanks heaps.
Hadn't flashed 4.3 via ODIN (just Telstra update), trying to flash other rom, got stuck in recovery mode, flashing this via ODIN worked.
billyhoyle said:
Thanks heaps.
Hadn't flashed 4.3 via ODIN (just Telstra update), trying to flash other rom, got stuck in recovery mode, flashing this via ODIN worked.
Click to expand...
Click to collapse
And now you have the 4.3 bootloader flashed to you phone.
The whole point of this thread was to save people from doing that and installing KNOX on their phone (which is a new protection from Samsung).
It's too late now to go back to a 4.1.2 bootloader now too.
I updated with stock Optus 4.3 through Odin. Got the Knox apps but managed to disable it then froze it intitanium backup.
Perhaps silly question but what does the CSC mean and what does it do?
Sent from my GT-I9305 using Tapatalk
harlz said:
I updated with stock Optus 4.3 through Odin. Got the Knox apps but managed to disable it then froze it intitanium backup.
Perhaps silly question but what does the CSC mean and what does it do?
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
CSC is a sales code and its different for each country and some providers.
Do a google search and you'll find some more info
djb77 said:
And now you have the 4.3 bootloader flashed to you phone.
The whole point of this thread was to save people from doing that and installing KNOX on their phone (which is a new protection from Samsung).
It's too late now to go back to a 4.1.2 bootloader now too.
Click to expand...
Click to collapse
Ive just upadate from 4.1.2 to 4.3 does it mean I have the 4.3 bootloader? thanks
dbp said:
Ive just upadate from 4.1.2 to 4.3 does it mean I have the 4.3 bootloader? thanks
Click to expand...
Click to collapse
Depends on if you flashed the update with ODIN or not, if you did, you'd have the 4.3 bootloader
djb77 said:
Depends on if you flashed the update with ODIN or not, if you did, you'd have the 4.3 bootloader
Click to expand...
Click to collapse
I've have updated it from the device and there is KNOX app but haven't installed it yet and is there rooting for this version?
dbp said:
I've have updated it from the device and there is KNOX app but haven't installed it yet and is there rooting for this version?
Click to expand...
Click to collapse
Just for the fact there is a sign of KNOX isnt good. A custom kernel still might be able to save you and SuperSU for root.
djb77 said:
Just for the fact there is a sign of KNOX isnt good. A custom kernel still might be able to save you and SuperSU for root.
Click to expand...
Click to collapse
I must have a bad rooting last version because when I run SystemApp Remover it prompted my device is not rooted, don't know what to do, very much appreciated
dbp said:
I must have a bad rooting last version because when I run SystemApp Remover it prompted my device is not rooted, don't know what to do, very much appreciated
Click to expand...
Click to collapse
Try flashing the latest version of SuperSU
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
djb77 said:
Try flashing the latest version of SuperSU
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Click to expand...
Click to collapse
damn the security blocked the superSU
The way I rooted my stock 4.3 Optus (with Knox)
I used the cf root recovery that you flash through Odin. Once that's done and you reboot you so don't have root because of Knox. Go to app store and update SuperSu.
From there open SuperSu and it should now ask if you want to have Knox disabled. It worked for me. Then use titanium and delete or freeze all Knox related rubbish.
Sent from my GT-I9305 using Tapatalk
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
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.